As per Relevance of the word provides, we have this rfc below:
Network Working Group S.
Request for Comments: 2699
Category: Informational May 2000
Request for Comments
RFC Numbers 2600-2699
Status of This
This RFC is a slightly annotated list of the 100 RFCs from RFC 2600
through RFCs 2699. This is a status report on these RFCs. This
provides information for the Internet community. It does not
an Internet standard of any kind. Distribution of this memo
unlimited
Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
Many RFCs, but not all, are Proposed Standards, Draft Standards,
Standards. Since the status of these RFCs may change during
standards processing, we note here only that they are on
standards track. Please see the latest edition of "Internet
Protocol Standards" for the current state and status of these RFCs
In the following, RFCs on the standards track are marked [STANDARDS
TRACK].
RFC Author Date
--- ------ ---- -----
2699 Ginoza Apr 2000 Request for Comments
This memo
2698 Heinanen Sep 1999 A Two Rate Three Color
This document defines a Two Rate Three Color Marker (trTCM), which
be used as a component in a Diffserv traffic conditioner. This
provides information for the Internet community
Ginoza Informational [Page 1]
RFC 2699 Summary of 2600-2699 May 2000
2697 Heinanen Sep 1999 A Single Rate Three Color
This document defines a Single Rate Three Color Marker (srTCM),
can be used as component in a Diffserv traffic conditioner. This
provides information for the Internet community
2696 Weider Sep 1999 LDAP Control Extension
Simple Paged
This document describes an LDAPv3 control extension for simple paging
search results. This memo provides information for the
community
2695 Chiu Sep 1999 Authentication Mechanisms
ONC
This document describes two authentication mechanisms created by
Microsystems that are commonly used in conjunction with the ONC
Procedure Call (ONC RPC Version 2) protocol. This memo
information for the Internet community
2694 Srisuresh Sep 1999 DNS extensions to
Address Translators (DNS_ALG
This document identifies the need for DNS extensions to NATs
outlines how a DNS Application Level Gateway (DNS_ALG) can meet
need. This memo provides information for the Internet community
2693 Ellison Sep 1999 SPKI Certificate
This document gives the theory behind SPKI certificates and ACLs
going into technical detail about those structures or their uses.
memo defines an Experimental Protocol for the Internet community
2692 Ellison Sep 1999 SPKI
The SPKI Working Group first established a list of things one might
to do with certificates (attached at the end of this document), and
summarized that list of desires into requirements. This
presents that summary of requirements. This memo defines
Experimental Protocol for the Internet community
Ginoza Informational [Page 2]
RFC 2699 Summary of 2600-2699 May 2000
2691 Bradner Sep 1999 A Memorandum of
for an ICANN Protocol
This is the text of the Memorandum of Understanding (MoU) that
signed by ICANN, the IETF, the ITU-T, W3C and ETSI on July 14, 1999
Oslo. This MoU creates the Protocol Support Organization (PSO)
the Internet Corporation for Assigned Names and Numbers (ICANN).
memo provides information for the Internet community
2690 Bradner Sep 1999 A Proposal for an MOU-
ICANN Protocol
This is a copy of the proposal for an MOU-based Protocol
Organization that was submitted to ICANN on April 23, 1999. This
provides information for the Internet community
2689 Bormann Sep 1999 Providing Integrated
over Low-bitrate
This document describes an architecture for providing
services over low-bitrate links, such as modem lines, ISDN B-channels
and sub-T1 links. This memo provides information for the
community
2688 Jackowski Sep 1999 Integrated Services
for Low Speed
This document defines the service mappings of the IETF
Services for low-bitrate links, specifically the controlled load
guaranteed services. [STANDARDS-TRACK
2687 Bormann Sep 1999 PPP in a Real-time
HDLC-like
This document proposes the suspend/resume-oriented solution for
real-time encapsulation format part of the architecture. [STANDARDS
TRACK
Ginoza Informational [Page 3]
RFC 2699 Summary of 2600-2699 May 2000
2686 Bormann Sep 1999 The Multi-Class Extension
Multi-Link
This document proposes the fragment-oriented solution for the real-
encapsulation format part of the architecture. [STANDARDS-TRACK
2685 Fox Sep 1999 Virtual Private
This document proposes a format for a globally unique VPN identifier
[STANDARDS-TRACK
2684 Grossman Sep 1999 Multiprotocol
over ATM Adaptation Layer 5
This memo replaces RFC 1483. It describes two encapsulations
for carrying network interconnect traffic over AAL type 5 over ATM
[STANDARDS-TRACK
2683 Leiba Sep 1999 IMAP4
The IMAP4 specification describes a rich protocol for use in
clients and servers for storage, retrieval, and manipulation
electronic mail. Because the protocol is so rich and has so
implementation choices, there are often trade-offs that must be made
issues that must be considered when designing such clients and servers
This document attempts to outline these issues and to
recommendations in order to make the end products as interoperable
possible. This memo provides information for the Internet community
2682 Widjaja Sep 1999 Performance Issues in VC-
Capable ATM
This document investigates the impact of VC merging on the
buffer required for the reassembly buffers and other buffers. This
provides information for the Internet community
Ginoza Informational [Page 4]
RFC 2699 Summary of 2600-2699 May 2000
2681 Almes Sep 1999 A Round-trip Delay Metric for
This memo defines a metric for round-trip delay of packets
Internet paths. [STANDARDS-TRACK
2680 Almes Sep 1999 A One-way Packet Loss
for
This memo defines a metric for one-way packet loss across
paths. [STANDARDS-TRACK
2679 Almes Sep 1999 A One-way Delay Metric for
This memo defines a metric for one-way delay of packets across
paths. [STANDARDS-TRACK
2678 Mahdavi Sep 1999 IPPM Metrics for
This memo defines a series of metrics for connectivity between a pair
Internet hosts. [STANDARDS-TRACK
2677 Greene Sep 1999 Definitions of Managed
for the NBMA Next
Resolution Protocol (NHRP
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community
[STANDARDS-TRACK
2676 Apostolopoulos Aug 1999 QoS Routing
and OSPF
This memo describes extensions to the OSPF protocol to support
routes. The focus of this document is on the algorithms used to
QoS routes and on the necessary modifications to OSPF to support
function, e.g., the information needed, its format, how it
distributed, and how it is used by the QoS path selection process.
memo defines an Experimental Protocol for the Internet community
Ginoza Informational [Page 5]
RFC 2699 Summary of 2600-2699 May 2000
2675 Borman Aug 1999 IPv6
This document describes the IPv6 Jumbo Payload option, which
the means of specifying such large payload lengths. It also
the changes needed to TCP and UDP to make use of jumbograms
[STANDARDS-TRACK
2674 Bell Sep 1999 Definitions of Managed
for Bridges with
Classes, Multicast
and Virtual LAN
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP based internets
[STANDARDS-TRACK
2673 Crawford Aug 1999 Binary Labels in
Domain Name
This document defines a "Bit-String Label" which may appear
domain names. This new label type compactly represents a sequence
"One-Bit Labels" and enables resource records to be stored at any bit
boundary in a binary-named section of the domain name tree
[STANDARDS-TRACK
2672 Crawford Aug 1999 Non-Terminal DNS
This document defines a new DNS Resource Record called "DNAME",
provides the capability to map an entire subtree of the DNS name
to another domain. [STANDARDS-TRACK
2671 Vixie Aug 1999 Extension
for DNS (EDNS0)
The Domain Name System's wire protocol includes a number of fixed
whose range has been or soon will be exhausted and does not
clients to advertise their capabilities to servers. This
describes backward compatible mechanisms for allowing the protocol
grow. [STANDARDS-TRACK
Ginoza Informational [Page 6]
RFC 2699 Summary of 2600-2699 May 2000
2670 St. Johns Aug 1999 Radio Frequency (RF
Interface
Information Base
MCNS/DOCSIS
RF
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it defines a basic set of managed objects for SNMP-
management of MCNS/DOCSIS compliant Radio Frequency (RF) interfaces
[STANDARDS-TRACK
2669 St. Johns Aug 1999 DOCSIS Cable Device
Cable Device
Information Base
DOCSIS compliant
Modems and Cable
Termination
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it defines a basic set of managed objects for SNMP-
management of DOCSIS 1.0 compliant Cable Modems and Cable
Termination Systems. [STANDARDS-TRACK
2668 Smith Sep 1999 Definitions of Managed
for IEEE 802.3
Attachment Units (MAUs
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community
[STANDARDS-TRACK
2667 Thaler Aug 1999 IP Tunnel
This memo defines a Management Information Base (MIB) for use
network management protocols in the Internet community. In particular
it describes managed objects used for managing tunnels of any type
IPv4 networks. [STANDARDS-TRACK
Ginoza Informational [Page 7]
RFC 2699 Summary of 2600-2699 May 2000
2666 Flick Sep 1999 Definitions of
Identifiers for
Ethernet Chip
This memo defines OBJECT IDENTIFIER values for use with
management protocols in the Internet community. This memo
information for the Internet community
2665 Flick Sep 1999 Definitions of Managed
for the Ethernet-
Interface
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community
[STANDARDS-TRACK
2664 Plzak Aug 1999 FYI on Questions and
Answers to Commonly Asked "
Internet User"
This memo provides an overview to the new Internet User. The
audience is the common Internet user of today, thus it attempts
provide a more consumer oriented approach to the Internet rather
going into any depth about a topic. This memo provides information
the Internet community
2663 Srisuresh Aug 1999 IP Network Address
(NAT) Terminology
This document attempts to describe the operation of NAT devices and
associated considerations in general, and to define the terminology
to identify various flavors of NAT. This memo provides information
the Internet community
2662 Bathrick Aug 1999 Definitions of Managed
for the ADSL
This document defines a standard SNMP MIB for ADSL lines based on
ADSL Forum standard data model. [STANDARDS-TRACK
Ginoza Informational [Page 8]
RFC 2699 Summary of 2600-2699 May 2000
2661 Townsley Aug 1999 Layer Two Tunneling
"L2TP
This document describes the Layer Two Tunneling Protocol (L2TP).
[STANDARDS-TRACK
2660 Rescorla Aug 1999 The Secure HyperText
This memo describes a syntax for securing messages sent using
Hypertext Transfer Protocol (HTTP), which forms the basis for the
Wide Web. This memo defines an Experimental Protocol for the
community
2659 Rescorla Aug 1999 Security Extensions For
This memo describes a syntax for embedding S-HTTP negotiation
in HTML documents. This memo defines an Experimental Protocol for
Internet community
2658 McKay Aug 1999 RTP Payload Format
PureVoice(tm)
This document describes the RTP payload format for PureVoice(tm) Audio
[STANDARDS-TRACK
2657 Hedberg Aug 1999 LDAPv2 Client vs. the Index
LDAPv2 clients as implemented according to RFC 1777 have no notion
referral. The integration between such a client and an Index Mesh,
defined by the Common Indexing Protocol, heavily depends on
and therefore needs to be handled in a special way. This
defines one possible way of doing this. This memo defines
Experimental Protocol for the Internet community
Ginoza Informational [Page 9]
RFC 2699 Summary of 2600-2699 May 2000
2656 Hardie Aug 1999 Registration Procedures
SOIF Template
The registration procedure described in this document is specific
SOIF template types. This memo defines an Experimental Protocol for
Internet community
2655 Hardie Aug 1999 CIP Index Object Format
SOIF
This document describes SOIF, the Summary Object Interchange Format,
an index object type in the context of the CIP framework. This
defines an Experimental Protocol for the Internet community
2654 Hedberg Aug 1999 A Tagged Index Object for
in the Common
This document defines a mechanism by which information servers
exchange indices of information from their databases by making use
the Common Indexing Protocol (CIP). This document defines the
of the index information being exchanged, as well as the
meanings for the headers that are defined in the Common
Protocol. This memo defines an Experimental Protocol for the
community
2653 Allen Aug 1999 CIP Transport
This document specifies three protocols for transporting CIP requests
responses and index objects, utilizing TCP, mail, and HTTP
[STANDARDS-TRACK
2652 Allen Aug 1999 MIME Object Definitions
the Common Indexing
(CIP
This document describes the definitions of those objects as well as
methods and requirements needed to define a new index type
[STANDARDS-TRACK
Ginoza Informational [Page 10]
RFC 2699 Summary of 2600-2699 May 2000
2651 Allen Aug 1999 The Architecture of the
Indexing Protocol (CIP
This document describes the CIP framework, including its
and the protocol specifics of exchanging indices. [STANDARDS-TRACK
2650 Meyer Aug 1999 Using RPSL in
This document is a tutorial on using the Routing Policy
Language (RPSL) to describe routing policies in the Internet
Registry (IRR). This memo provides information for the
community
2649 Greenblatt Aug 1999 An LDAP Control and Schema
Holding Operation
This document describes an LDAP message control which allows for
retrieval of digitally signed information. This document defines an
v3 based mechanism for signing directory operations in order to create
secure journal of changes that have been made to each directory entry
This memo defines an Experimental Protocol for the Internet community
2648 Moats Aug 1999 A URN Namespace for
This document proposes the "ietf" namespace, which consists of the
family of documents (RFCs, STDs, FYIs, and BCPs) developed by the
and published by the RFC Editor and the minutes of working groups (WG
and birds of a feather (BOF) meetings that occur during
conferences. [STANDARDS-TRACK
2647 Newman Aug 1999 Benchmarking Terminology
Firewall
This document defines terms used in measuring the performance
firewalls. It extends the terminology already used for
routers and switches with definitions specific to firewalls
[STANDARDS-TRACK
Ginoza Informational [Page 11]
RFC 2699 Summary of 2600-2699 May 2000
2646 Gellens Aug 1999 The Text/Plain Format
This memo proposes a new parameter to be used with Text/Plain, and,
the presence of this parameter, the use of trailing whitespace
indicate flowed lines. This results in an encoding which appears
normal Text/Plain in older implementations, since it is in fact
Text/Plain. [STANDARDS-TRACK
2645 Gellens Aug 1999 ON-DEMAND MAIL RELAY (ODMR
SMTP with Dynamic IP
This memo proposes a new service, On-Demand Mail Relay (ODMR), which
a profile of SMTP, providing for a secure, extensible, easy to
approach to the problem. [STANDARDS-TRACK
2644 Bradner Aug 1999 Benchmarking Methodology
Network Interconnect
This document discusses and defines a number of tests that may be
to describe the performance characteristics of a network
device. In addition to defining the tests this document also
specific formats for reporting the results of the tests. This
provides information for the Internet community
2643 Ruffen Aug 1999 Cabletron's SecureFast
Operational
Cabletron's SecureFast VLAN (SFVLAN) product implements a
connection-oriented switching protocol that provides fast forwarding
data packets at the MAC layer. The product uses the concept of
LANs (VLANs) to determine the validity of call connection requests
to scope the broadcast of certain flooded messages. This memo
information for the Internet community
2642 Kane Aug 1999 Cabletron's VLS
VLSP provides support for equal-cost multipath routing, and
routes quickly in the face of topological changes, utilizing a
of routing protocol traffic. This memo provides information for
Internet community
Ginoza Informational [Page 12]
RFC 2699 Summary of 2600-2699 May 2000
2641 Hamilton Aug 1999 Cabletron's VlanHello
The VlanHello protocol is part of the InterSwitch Message
(ISMP) which provides interswitch communication between switches
Cabletron's SecureFast VLAN (SFVLAN) product. Switches use
VlanHello protocol to discover their neighboring switches and
the topology of the switch fabric. This memo provides information
the Internet community
2640 Curtin Jul 1999 Internationalization of
File transfer
This document addresses the internationalization (I18n) of FTP,
includes supporting the multiple character sets and languages
throughout the Internet community. This is achieved by extending
FTP specification and giving recommendations for
internationalization support. [STANDARDS-TRACK
2639 Hastings Jul 1999 Internet
Protocol/1.0: Implementer'
This document contains information that supplements the IPP Model
Semantics and the IPP Transport and Encoding documents. It is
to help implementers understand IPP/1.0 and some of the
that may assist them in the design of their client and/or IPP
implementations. This memo provides information for the
community
2638 Nichols Jul 1999 A Two-bit
Services Architecture
the
This document presents a differentiated services architecture for
internet. This memo provides information for the Internet community
Ginoza Informational [Page 13]
RFC 2699 Summary of 2600-2699 May 2000
2637 Hamzeh Jul 1999 Point-to-Point
Protocol (PPTP
This document specifies a protocol which allows the Point to
Protocol (PPP) to be tunneled through an IP network. This memo
information for the Internet community
2636 Gellens Jul 1999 Wireless Device
(OTASP/OTAPA) via
This paper describes a viable and attractive means to
OTASP/OTAPA via IS-707, using the ACAP protocol. This memo
information for the Internet community
2635 Hambridge Jun 1999 DON'T SPEW A Set of
for Mass Unsolicited
and
This document explains why mass unsolicited electronic mail messages
harmful in the Internetworking community. This memo
information for the Internet community
2634 Hoffman Jun 1999 Enhanced Security Services
S/
This document describes four optional security service extensions
S/MIME. [STANDARDS-TRACK
2633 Ramsdell Jun 1999 S/MIME Version 3
This document describes a protocol for adding cryptographic
and encryption services to MIME data. [STANDARDS-TRACK
Ginoza Informational [Page 14]
RFC 2699 Summary of 2600-2699 May 2000
2632 Ramsdell Jun 1999 S/MIME Version 3
S/MIME (Secure/Multipurpose Internet Mail Extensions), provides a
to send and receive secure MIME messages. Before using a public key
provide security services, the S/MIME agent MUST certify that the
key is valid. S/MIME agents MUST use PKIX certificates to
public keys as described in the Internet X.509 Public Key
(PKIX) Certificate and CRL Profile. [STANDARDS-TRACK
2631 Rescorla Jun 1999 Diffie-Hellman Key
This document standardizes one particular Diffie-Hellman variant,
on the ANSI X9.42 draft, developed by the ANSI X9F1 working group
[STANDARDS-TRACK
2630 Housley Jun 1999 Cryptographic Message
This document describes the Cryptographic Message Syntax. This
is used to digitally sign, digest, authenticate, or encrypt
messages. [STANDARDS-TRACK
2629 Rose Jun 1999 Writing I-Ds and RFCs using
This memo presents a technique for using XML (Extensible
Language) as a source format for documents in the Internet-Drafts (I-Ds
and Request for Comments (RFC) series. This memo provides
for the Internet community
2628 Smyslov Jun 1999 Simple Cryptographic
Interface (Crypto API
This document describes a simple Application Program Interface
cryptographic functions. This memo provides information for
Internet community
Ginoza Informational [Page 15]
RFC 2699 Summary of 2600-2699 May 2000
2627 Wallner Jun 1999 Key Management for Multicast
Issues and
This report contains a discussion of the difficult problem of
management for multicast communication sessions. It focuses on two
areas of concern with respect to key management, which are,
the multicast group with a common net key and rekeying the
group. This memo provides information for the Internet community
2626 Nesser II Jun 1999 The Internet and
Millennium Problem (Year 2000)
The Year 2000 Working Group (WG) has conducted an investigation into
millennium problem as it regards Internet related protocols.
investigation only targeted the protocols as documented in the
For Comments Series (RFCs). This investigation discovered little
for concern with regards to the functionality of the protocols. A
minor cases of older implementations still using two digit years (
RFC 850) were discovered, but almost all Internet protocols were given
clean bill of health. Several cases of "period" problems
discovered, where a time field would "roll over" as the size of
was reached. In particular, there are several protocols, which have 32
bit, signed integer representations of the number of seconds
January 1, 1970 which will turn negative at Tue Jan 19 03:14:07
2038. Areas whose protocols will be effected by such problems have
notified so that new revisions will remove this limitation. This
provides information for the Internet community
2625 Rajagopal Jun 1999 IP and ARP over Fibre
The purpose of this document is to specify a way of encapsulating IP
Address Resolution Protocol(ARP) over Fibre Channel and also to
a mechanism(s) for IP address resolution. [STANDARDS-TRACK
2624 Shepler Jun 1999 NFS Version 4
This design considerations document is meant to present more detail
the working group charter. Specifically, it presents the areas that
working group will investigate and consider while developing a
specification for NFS version 4. This memo provides information for
Internet community
Ginoza Informational [Page 16]
RFC 2699 Summary of 2600-2699 May 2000
2623 Eisler Jun 1999 NFS Version 2 and Version 3
Security Issues and the
Protocol's Use of RPCSEC_
and Kerberos V
This memorandum clarifies various security issues involving the
protocol (Version 2 and Version 3 only) and then describes how
Version 2 and Version 3 of the NFS protocol use the RPCSEC_GSS
flavor protocol and Kerberos V5. [STANDARDS-TRACK
2622 Alaettinoglu Jun 1999 Routing Policy
Language (RPSL
RPSL allows a network operator to be able to specify routing policies
various levels in the Internet hierarchy; for example at the
System (AS) level. At the same time, policies can be specified
sufficient detail in RPSL so that low level router configurations can
generated from them. RPSL is extensible; new routing protocols and
protocol features can be introduced at any time. [STANDARDS-TRACK
2621 Zorn Jun 1999 RADIUS Accounting Server
This memo defines a set of extensions which instrument RADIUS
server functions. This memo provides information for the
community
2620 Aboba Jun 1999 RADIUS Accounting Client
This memo defines a set of extensions which instrument RADIUS
client functions. This memo provides information for the
community
2619 Zorn Jun 1999 RADIUS Authentication Server
This memo defines a set of extensions which instrument
authentication server functions. [STANDARDS-TRACK
2618 Aboba Jun 1999 RADIUS Authentication Client
This memo defines a set of extensions which instrument
authentication client functions. [STANDARDS-TRACK
Ginoza Informational [Page 17]
RFC 2699 Summary of 2600-2699 May 2000
2617 Franks Jun 1999 HTTP Authentication: Basic
Digest Access
This document provides the specification for HTTP's
framework, the original Basic authentication scheme and a scheme
on cryptographic hashes, referred to as "Digest Access Authentication".
[STANDARDS-TRACK
2616 Fielding Jun 1999 Hypertext Transfer Protocol --
HTTP/1.1
HTTP has been in use by the World-Wide Web global information
since 1990. This specification defines the protocol referred to
"HTTP/1.1", and is an update to RFC 2068. [STANDARDS-TRACK
2615 Malis Jun 1999 PPP over SONET/
This document describes the use of PPP over Synchronous Optical
(SONET) and Synchronous Digital Hierarchy (SDH) circuits. [STANDARDS
TRACK
2614 Kempf Jun 1999 An API for Service
This document describes standardized APIs for SLP in C and Java.
memo provides information for the Internet community
2613 Waterman Jun 1999 Remote Network Monitoring
Extensions for
Networks Version 1.0
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets.
particular, it defines objects for managing remote network
devices in switched networks environments. [STANDARDS-TRACK
2612 Adams Jun 1999 The CAST-256 Encryption
This document describes an existing algorithm that can be used
satisfy this requirement. Included are a description of the cipher
the key scheduling algorithm, the s-boxes, and a set of test
(Appendix A). This memo provides information for the
community
Ginoza Informational [Page 18]
RFC 2699 Summary of 2600-2699 May 2000
2611 Daigle Jun 1999 URN Namespace
This document lays out general definitions of and mechanisms
establishing URN "namespaces". This document specifies an Internet
Current Practices for the Internet Community, and requests
and suggestions for improvements
2610 Perkins Jun 1999 DHCP Options for
Location
The Dynamic Host Configuration Protocol provides a framework for
configuration information to hosts on a TCP/IP network. Entities
the Service Location Protocol need to find out the address of
Agents in order to transact messages. Another option provides
assignment of scope for configuration of SLP User and Service Agents
[STANDARDS-TRACK
2609 Guttman Jun 1999 Service Templates and Service
This document describes a formal procedure for defining
standardizing new service types and attributes for use with
"service:" scheme. [STANDARDS-TRACK
2608 Guttman Jun 1999 Service Location Protocol
Version 2
The Service Location Protocol provides a scalable framework for
discovery and selection of network services. Using this protocol
computers using the Internet need little or no static configuration
network services for network based applications. This is
important as computers become more portable, and users less tolerant
able to fulfill the demands of network system administration
[STANDARDS-TRACK
2607 Aboba Jun 1999 Proxy Chaining and
Implementation in
This document describes how proxy chaining and policy implementation
be supported in roaming systems. This memo provides information for
Internet community
Ginoza Informational [Page 19]
RFC 2699 Summary of 2600-2699 May 2000
2606 Eastlake Jun 1999 Reserved Top Level DNS
To reduce the likelihood of conflict and confusion, a few top
domain names are reserved for use in private testing, as examples
documentation, and the like. In addition, a few second level
names reserved for use as examples are documented. This
specifies an Internet Best Current Practices for the Internet Community
and requests discussion and suggestions for improvements
2605 Mansfield Jun 1999 Directory Server Monitoring
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community
[STANDARDS-TRACK
2604 Gellens Jun 1999 Wireless Device
(OTASP/OTAPA) via
This paper describes a viable and attractive means to
OTASP/OTAPA via IS-707, using the ACAP protocol. This memo
information for the Internet community
2603 Davison Jun 1999 ILMI-Based Server
for
This memo defines how ILMI-based Server Discovery, which provides
method for ATM-attached hosts and routers to dynamically determine
ATM addresses of servers, shall be used to locate NHRP servers
[STANDARDS-TRACK
2602 Davison Jun 1999 ILMI-Based Server
for
This memo defines how ILMI-based Server Discovery, which provides
method for ATM-attached hosts and routers to dynamically determine
ATM addresses of servers, shall be used to locate MARS servers
[STANDARDS-TRACK
Ginoza Informational [Page 20]
RFC 2699 Summary of 2600-2699 May 2000
2601 Davison Jun 1999 ILMI-Based Server
for
This memo defines how ILMI-based Server Discovery, which provides
method for ATM-attached hosts and routers to dynamically determine
ATM addresses of servers, shall be used to locate ATMARP servers
[STANDARDS-TRACK
2600 Reynolds Mar 2000 Internet Official
This memo is published by the RFC Editor in accordance with Section 2.1
of "The Internet Standards Process -- Revision 3", RFC 2026,
specifies the rules and procedures by which all Internet standards
set. This memo is prepared by the RFC Editor for the IESG and IAB
Please see http://www.rfc-editor.org for later updates to this document
[STANDARDS-TRACK
Security
Security issues are not discussed in this memo
Author's
Sandy
University of Southern
Information Sciences
4676 Admiralty
Marina Del Rey, CA 90292
Phone: (310) 822-1511
EMail: ginoza@isi.
Ginoza Informational [Page 21]
RFC 2699 Summary of 2600-2699 May 2000
Full Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Ginoza Informational [Page 22]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
