RFC Abstracts
RFC2655 - CIP Index Object Format for SOIF Objects
This document describes SOIF, the Summary Object Interchange Format, as an index object type in the context of the CIP framework. This memo defines an Experimental Protocol for the Internet community.
RFC2654 - A Tagged Index Object for use in the Common Indexing Protocol
This document defines a mechanism by which information servers can exchange indices of information from their databases by making use of the Common Indexing Protocol (CIP). This document defines the structure of the index information being exchanged, as well as the appropriate meanings for the headers that are defined in the Common Indexing Protocol. This memo defines an Experimental Protocol for the Internet community.
RFC2653 - CIP Transport Protocols
This document specifies three protocols for transporting CIP requests, responses and index objects, utilizing TCP, mail, and HTTP. [STANDARDS-TRACK]
RFC2652 - MIME Object Definitions for the Common Indexing Protocol (CIP)
This document describes the definitions of those objects as well as the methods and requirements needed to define a new index type. [STANDARDS-TRACK]
RFC2651 - The Architecture of the Common Indexing Protocol (CIP)
This document describes the CIP framework, including its architecture and the protocol specifics of exchanging indices. [STANDARDS-TRACK]
RFC2650 - Using RPSL in Practice
This document is a tutorial on using the Routing Policy Specification Language (RPSL) to describe routing policies in the Internet Routing Registry (IRR). This memo provides information for the Internet community.
RFC2649 - An LDAP Control and Schema for Holding Operation Signatures
This document describes an LDAP message control which allows for the retrieval of digitally signed information. This document defines an LDAP v3 based mechanism for signing directory operations in order to create a secure journal of changes that have been made to each directory entry. This memo defines an Experimental Protocol for the Internet community.
RFC2648 - A URN Namespace for IETF Documents
This document proposes the "ietf" namespace, which consists of the RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETF and published by the RFC Editor and the minutes of working groups (WG) and birds of a feather (BOF) meetings that occur during IETF conferences. [STANDARDS-TRACK]
RFC2647 - Benchmarking Terminology for Firewall Performance
This document defines terms used in measuring the performance of firewalls. It extends the terminology already used for benchmarking routers and switches with definitions specific to firewalls. [STANDARDS-TRACK]
RFC2646 - The Text/Plain Format Parameter
This memo proposes a new parameter to be used with Text/Plain, and, in the presence of this parameter, the use of trailing whitespace to indicate flowed lines. This results in an encoding which appears as normal Text/Plain in older implementations, since it is in fact normal Text/Plain. [STANDARDS-TRACK]
RFC2645 - ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP Addresses
This memo proposes a new service, On-Demand Mail Relay (ODMR), which is a profile of SMTP, providing for a secure, extensible, easy to implement approach to the problem. [STANDARDS-TRACK]
RFC2644 - Changing the Default for Directed Broadcasts in Routers
This document discusses and defines a number of tests that may be used to describe the performance characteristics of a network interconnecting device. In addition to defining the tests this document also describes specific formats for reporting the results of the tests. This memo provides information for the Internet community.
RFC2643 - Cabletron's SecureFast VLAN Operational Model
Cabletron's SecureFast VLAN (SFVLAN) product implements a distributed connection-oriented switching protocol that provides fast forwarding of data packets at the MAC layer. The product uses the concept of virtual LANs (VLANs) to determine the validity of call connection requests and to scope the broadcast of certain flooded messages. This memo provides information for the Internet community.
RFC2642 - Cabletron's VLS Protocol Specification
VLSP provides support for equal-cost multipath routing, and recalculates routes quickly in the face of topological changes, utilizing a minimum of routing protocol traffic. This memo provides information for the Internet community.
RFC2641 - Cabletron's VlanHello Protocol Specification Version 4
The VlanHello protocol is part of the InterSwitch Message Protocol (ISMP) which provides interswitch communication between switches running Cabletron's SecureFast VLAN (SFVLAN) product. Switches use the VlanHello protocol to discover their neighboring switches and establish the topology of the switch fabric. This memo provides information for the Internet community.
RFC2640 - Internationalization of the File Transfer Protocol
This document addresses the internationalization (I18n) of FTP, which includes supporting the multiple character sets and languages found throughout the Internet community. This is achieved by extending the FTP specification and giving recommendations for proper internationalization support. [STANDARDS-TRACK]
RFC2639 - Internet Printing Protocol/1.0: Implementer's Guide
This document contains information that supplements the IPP Model and Semantics and the IPP Transport and Encoding documents. It is intended to help implementers understand IPP/1.0 and some of the considerations that may assist them in the design of their client and/or IPP object implementations. This memo provides information for the Internet community.
RFC2638 - A Two-bit Differentiated Services Architecture for the Internet
This document presents a differentiated services architecture for the internet. This memo provides information for the Internet community.
RFC2637 - Point-to-Point Tunneling Protocol (PPTP)
This document specifies a protocol which allows the Point to Point Protocol (PPP) to be tunneled through an IP network. This memo provides information for the Internet community.
RFC2636 - Wireless Device Configuration (OTASP/OTAPA) via ACAP
This paper describes a viable and attractive means to provide OTASP/OTAPA via IS-707, using the ACAP protocol. This memo provides information for the Internet community.
RFC2635 - DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and Postings (spam*)
This document explains why mass unsolicited electronic mail messages are harmful in the Internetworking community. This memo provides information for the Internet community.
RFC2634 - Enhanced Security Services for S/MIME
This document describes four optional security service extensions for S/MIME. [STANDARDS-TRACK]
RFC2633 - S/MIME Version 3 Message Specification
This document describes a protocol for adding cryptographic signature and encryption services to MIME data. [STANDARDS-TRACK]
RFC2632 - S/MIME Version 3 Certificate Handling
S/MIME (Secure/Multipurpose Internet Mail Extensions), provides a method to send and receive secure MIME messages. Before using a public key to provide security services, the S/MIME agent MUST certify that the public key is valid. S/MIME agents MUST use PKIX certificates to validate public keys as described in the Internet X.509 Public Key Infrastructure (PKIX) Certificate and CRL Profile. [STANDARDS-TRACK]
RFC2631 - Diffie-Hellman Key Agreement Method
This document standardizes one particular Diffie-Hellman variant, based on the ANSI X9.42 draft, developed by the ANSI X9F1 working group. [STANDARDS-TRACK]
RFC2630 - Cryptographic Message Syntax
This document describes the Cryptographic Message Syntax. This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary messages. [STANDARDS-TRACK]
RFC2629 - Writing I-Ds and RFCs using XML
This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series. This memo provides information for the Internet community.
RFC2628 - Simple Cryptographic Program Interface (Crypto API)
This document describes a simple Application Program Interface to cryptographic functions. This memo provides information for the Internet community.
RFC2627 - Key Management for Multicast: Issues and Architectures
This report contains a discussion of the difficult problem of key management for multicast communication sessions. It focuses on two main areas of concern with respect to key management, which are, initializing the multicast group with a common net key and rekeying the multicast group. This memo provides information for the Internet community.
RFC2626 - The Internet and the Millennium Problem (Year 2000)
The Year 2000 Working Group (WG) has conducted an investigation into the millennium problem as it regards Internet related protocols. This investigation only targeted the protocols as documented in the Request For Comments Series (RFCs). This investigation discovered little reason for concern with regards to the functionality of the protocols. A few minor cases of older implementations still using two digit years (ala RFC 850) were discovered, but almost all Internet protocols were given a clean bill of health. Several cases of "period" problems were discovered, where a time field would "roll over" as the size of field was reached. In particular, there are several protocols, which have 32 bit, signed integer representations of the number of seconds since January 1, 1970 which will turn negative at Tue Jan 19 03:14:07 GMT 2038. Areas whose protocols will be effected by such problems have been notified so that new revisions will remove this limitation. This memo provides information for the Internet community.
RFC2625 - IP and ARP over Fibre Channel
The purpose of this document is to specify a way of encapsulating IP and Address Resolution Protocol(ARP) over Fibre Channel and also to describe a mechanism(s) for IP address resolution. [STANDARDS-TRACK]
RFC2624 - NFS Version 4 Design Considerations
This design considerations document is meant to present more detail than the working group charter. Specifically, it presents the areas that the working group will investigate and consider while developing a protocol specification for NFS version 4. This memo provides information for the Internet community.
RFC2623 - NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5
This memorandum clarifies various security issues involving the NFS protocol (Version 2 and Version 3 only) and then describes how the Version 2 and Version 3 of the NFS protocol use the RPCSEC_GSS security flavor protocol and Kerberos V5. [STANDARDS-TRACK]
RFC2622 - Routing Policy Specification Language (RPSL)
RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK]
RFC2621 - RADIUS Accounting Server MIB
This memo defines a set of extensions which instrument RADIUS accounting server functions. This memo provides information for the Internet community.
RFC2620 - RADIUS Accounting Client MIB
This memo defines a set of extensions which instrument RADIUS accounting client functions. This memo provides information for the Internet community.
RFC2619 - RADIUS Authentication Server MIB
This memo defines a set of extensions which instrument RADIUS authentication server functions. [STANDARDS-TRACK]
RFC2618 - RADIUS Authentication Client MIB
This memo defines a set of extensions which instrument RADIUS authentication client functions. [STANDARDS-TRACK]
RFC2617 - HTTP Authentication: Basic and Digest Access Authentication
This document provides the specification for HTTP's authentication framework, the original Basic authentication scheme and a scheme based on cryptographic hashes, referred to as "Digest Access Authentication". [STANDARDS-TRACK]
RFC2616 - Hypertext Transfer Protocol -- HTTP/1.1
HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068. [STANDARDS-TRACK]
RFC2615 - PPP over SONET/SDH
This document describes the use of PPP over Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) circuits. [STANDARDS-TRACK]
RFC2614 - An API for Service Location
This document describes standardized APIs for SLP in C and Java. This memo provides information for the Internet community.
RFC2613 - Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices in switched networks environments. [STANDARDS-TRACK]
RFC2612 - The CAST-256 Encryption Algorithm
This document describes an existing algorithm that can be used to satisfy this requirement. Included are a description of the cipher and the key scheduling algorithm, the s-boxes, and a set of test vectors (Appendix A). This memo provides information for the Internet community.
RFC2611 - URN Namespace Definition Mechanisms
This document lays out general definitions of and mechanisms for establishing URN "namespaces". This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2610 - DHCP Options for Service Location Protocol
The Dynamic Host Configuration Protocol provides a framework for passing configuration information to hosts on a TCP/IP network. Entities using the Service Location Protocol need to find out the address of Directory Agents in order to transact messages. Another option provides an assignment of scope for configuration of SLP User and Service Agents. [STANDARDS-TRACK]
RFC2609 - Service Templates and Service: Schemes
This document describes a formal procedure for defining and standardizing new service types and attributes for use with the "service:" scheme. [STANDARDS-TRACK]
RFC2608 - Service Location Protocol, Version 2
The Service Location Protocol provides a scalable framework for the discovery and selection of network services. Using this protocol, computers using the Internet need little or no static configuration of network services for network based applications. This is especially important as computers become more portable, and users less tolerant or able to fulfill the demands of network system administration. [STANDARDS-TRACK]
RFC2607 - Proxy Chaining and Policy Implementation in Roaming
This document describes how proxy chaining and policy implementation can be supported in roaming systems. This memo provides information for the Internet community.
RFC2606 - Reserved Top Level DNS Names
To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
This document describes SOIF, the Summary Object Interchange Format, as an index object type in the context of the CIP framework. This memo defines an Experimental Protocol for the Internet community.
RFC2654 - A Tagged Index Object for use in the Common Indexing Protocol
This document defines a mechanism by which information servers can exchange indices of information from their databases by making use of the Common Indexing Protocol (CIP). This document defines the structure of the index information being exchanged, as well as the appropriate meanings for the headers that are defined in the Common Indexing Protocol. This memo defines an Experimental Protocol for the Internet community.
RFC2653 - CIP Transport Protocols
This document specifies three protocols for transporting CIP requests, responses and index objects, utilizing TCP, mail, and HTTP. [STANDARDS-TRACK]
RFC2652 - MIME Object Definitions for the Common Indexing Protocol (CIP)
This document describes the definitions of those objects as well as the methods and requirements needed to define a new index type. [STANDARDS-TRACK]
RFC2651 - The Architecture of the Common Indexing Protocol (CIP)
This document describes the CIP framework, including its architecture and the protocol specifics of exchanging indices. [STANDARDS-TRACK]
RFC2650 - Using RPSL in Practice
This document is a tutorial on using the Routing Policy Specification Language (RPSL) to describe routing policies in the Internet Routing Registry (IRR). This memo provides information for the Internet community.
RFC2649 - An LDAP Control and Schema for Holding Operation Signatures
This document describes an LDAP message control which allows for the retrieval of digitally signed information. This document defines an LDAP v3 based mechanism for signing directory operations in order to create a secure journal of changes that have been made to each directory entry. This memo defines an Experimental Protocol for the Internet community.
RFC2648 - A URN Namespace for IETF Documents
This document proposes the "ietf" namespace, which consists of the RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETF and published by the RFC Editor and the minutes of working groups (WG) and birds of a feather (BOF) meetings that occur during IETF conferences. [STANDARDS-TRACK]
RFC2647 - Benchmarking Terminology for Firewall Performance
This document defines terms used in measuring the performance of firewalls. It extends the terminology already used for benchmarking routers and switches with definitions specific to firewalls. [STANDARDS-TRACK]
RFC2646 - The Text/Plain Format Parameter
This memo proposes a new parameter to be used with Text/Plain, and, in the presence of this parameter, the use of trailing whitespace to indicate flowed lines. This results in an encoding which appears as normal Text/Plain in older implementations, since it is in fact normal Text/Plain. [STANDARDS-TRACK]
RFC2645 - ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP Addresses
This memo proposes a new service, On-Demand Mail Relay (ODMR), which is a profile of SMTP, providing for a secure, extensible, easy to implement approach to the problem. [STANDARDS-TRACK]
RFC2644 - Changing the Default for Directed Broadcasts in Routers
This document discusses and defines a number of tests that may be used to describe the performance characteristics of a network interconnecting device. In addition to defining the tests this document also describes specific formats for reporting the results of the tests. This memo provides information for the Internet community.
RFC2643 - Cabletron's SecureFast VLAN Operational Model
Cabletron's SecureFast VLAN (SFVLAN) product implements a distributed connection-oriented switching protocol that provides fast forwarding of data packets at the MAC layer. The product uses the concept of virtual LANs (VLANs) to determine the validity of call connection requests and to scope the broadcast of certain flooded messages. This memo provides information for the Internet community.
RFC2642 - Cabletron's VLS Protocol Specification
VLSP provides support for equal-cost multipath routing, and recalculates routes quickly in the face of topological changes, utilizing a minimum of routing protocol traffic. This memo provides information for the Internet community.
RFC2641 - Cabletron's VlanHello Protocol Specification Version 4
The VlanHello protocol is part of the InterSwitch Message Protocol (ISMP) which provides interswitch communication between switches running Cabletron's SecureFast VLAN (SFVLAN) product. Switches use the VlanHello protocol to discover their neighboring switches and establish the topology of the switch fabric. This memo provides information for the Internet community.
RFC2640 - Internationalization of the File Transfer Protocol
This document addresses the internationalization (I18n) of FTP, which includes supporting the multiple character sets and languages found throughout the Internet community. This is achieved by extending the FTP specification and giving recommendations for proper internationalization support. [STANDARDS-TRACK]
RFC2639 - Internet Printing Protocol/1.0: Implementer's Guide
This document contains information that supplements the IPP Model and Semantics and the IPP Transport and Encoding documents. It is intended to help implementers understand IPP/1.0 and some of the considerations that may assist them in the design of their client and/or IPP object implementations. This memo provides information for the Internet community.
RFC2638 - A Two-bit Differentiated Services Architecture for the Internet
This document presents a differentiated services architecture for the internet. This memo provides information for the Internet community.
RFC2637 - Point-to-Point Tunneling Protocol (PPTP)
This document specifies a protocol which allows the Point to Point Protocol (PPP) to be tunneled through an IP network. This memo provides information for the Internet community.
RFC2636 - Wireless Device Configuration (OTASP/OTAPA) via ACAP
This paper describes a viable and attractive means to provide OTASP/OTAPA via IS-707, using the ACAP protocol. This memo provides information for the Internet community.
RFC2635 - DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and Postings (spam*)
This document explains why mass unsolicited electronic mail messages are harmful in the Internetworking community. This memo provides information for the Internet community.
RFC2634 - Enhanced Security Services for S/MIME
This document describes four optional security service extensions for S/MIME. [STANDARDS-TRACK]
RFC2633 - S/MIME Version 3 Message Specification
This document describes a protocol for adding cryptographic signature and encryption services to MIME data. [STANDARDS-TRACK]
RFC2632 - S/MIME Version 3 Certificate Handling
S/MIME (Secure/Multipurpose Internet Mail Extensions), provides a method to send and receive secure MIME messages. Before using a public key to provide security services, the S/MIME agent MUST certify that the public key is valid. S/MIME agents MUST use PKIX certificates to validate public keys as described in the Internet X.509 Public Key Infrastructure (PKIX) Certificate and CRL Profile. [STANDARDS-TRACK]
RFC2631 - Diffie-Hellman Key Agreement Method
This document standardizes one particular Diffie-Hellman variant, based on the ANSI X9.42 draft, developed by the ANSI X9F1 working group. [STANDARDS-TRACK]
RFC2630 - Cryptographic Message Syntax
This document describes the Cryptographic Message Syntax. This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary messages. [STANDARDS-TRACK]
RFC2629 - Writing I-Ds and RFCs using XML
This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series. This memo provides information for the Internet community.
RFC2628 - Simple Cryptographic Program Interface (Crypto API)
This document describes a simple Application Program Interface to cryptographic functions. This memo provides information for the Internet community.
RFC2627 - Key Management for Multicast: Issues and Architectures
This report contains a discussion of the difficult problem of key management for multicast communication sessions. It focuses on two main areas of concern with respect to key management, which are, initializing the multicast group with a common net key and rekeying the multicast group. This memo provides information for the Internet community.
RFC2626 - The Internet and the Millennium Problem (Year 2000)
The Year 2000 Working Group (WG) has conducted an investigation into the millennium problem as it regards Internet related protocols. This investigation only targeted the protocols as documented in the Request For Comments Series (RFCs). This investigation discovered little reason for concern with regards to the functionality of the protocols. A few minor cases of older implementations still using two digit years (ala RFC 850) were discovered, but almost all Internet protocols were given a clean bill of health. Several cases of "period" problems were discovered, where a time field would "roll over" as the size of field was reached. In particular, there are several protocols, which have 32 bit, signed integer representations of the number of seconds since January 1, 1970 which will turn negative at Tue Jan 19 03:14:07 GMT 2038. Areas whose protocols will be effected by such problems have been notified so that new revisions will remove this limitation. This memo provides information for the Internet community.
RFC2625 - IP and ARP over Fibre Channel
The purpose of this document is to specify a way of encapsulating IP and Address Resolution Protocol(ARP) over Fibre Channel and also to describe a mechanism(s) for IP address resolution. [STANDARDS-TRACK]
RFC2624 - NFS Version 4 Design Considerations
This design considerations document is meant to present more detail than the working group charter. Specifically, it presents the areas that the working group will investigate and consider while developing a protocol specification for NFS version 4. This memo provides information for the Internet community.
RFC2623 - NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5
This memorandum clarifies various security issues involving the NFS protocol (Version 2 and Version 3 only) and then describes how the Version 2 and Version 3 of the NFS protocol use the RPCSEC_GSS security flavor protocol and Kerberos V5. [STANDARDS-TRACK]
RFC2622 - Routing Policy Specification Language (RPSL)
RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK]
RFC2621 - RADIUS Accounting Server MIB
This memo defines a set of extensions which instrument RADIUS accounting server functions. This memo provides information for the Internet community.
RFC2620 - RADIUS Accounting Client MIB
This memo defines a set of extensions which instrument RADIUS accounting client functions. This memo provides information for the Internet community.
RFC2619 - RADIUS Authentication Server MIB
This memo defines a set of extensions which instrument RADIUS authentication server functions. [STANDARDS-TRACK]
RFC2618 - RADIUS Authentication Client MIB
This memo defines a set of extensions which instrument RADIUS authentication client functions. [STANDARDS-TRACK]
RFC2617 - HTTP Authentication: Basic and Digest Access Authentication
This document provides the specification for HTTP's authentication framework, the original Basic authentication scheme and a scheme based on cryptographic hashes, referred to as "Digest Access Authentication". [STANDARDS-TRACK]
RFC2616 - Hypertext Transfer Protocol -- HTTP/1.1
HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068. [STANDARDS-TRACK]
RFC2615 - PPP over SONET/SDH
This document describes the use of PPP over Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) circuits. [STANDARDS-TRACK]
RFC2614 - An API for Service Location
This document describes standardized APIs for SLP in C and Java. This memo provides information for the Internet community.
RFC2613 - Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices in switched networks environments. [STANDARDS-TRACK]
RFC2612 - The CAST-256 Encryption Algorithm
This document describes an existing algorithm that can be used to satisfy this requirement. Included are a description of the cipher and the key scheduling algorithm, the s-boxes, and a set of test vectors (Appendix A). This memo provides information for the Internet community.
RFC2611 - URN Namespace Definition Mechanisms
This document lays out general definitions of and mechanisms for establishing URN "namespaces". This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2610 - DHCP Options for Service Location Protocol
The Dynamic Host Configuration Protocol provides a framework for passing configuration information to hosts on a TCP/IP network. Entities using the Service Location Protocol need to find out the address of Directory Agents in order to transact messages. Another option provides an assignment of scope for configuration of SLP User and Service Agents. [STANDARDS-TRACK]
RFC2609 - Service Templates and Service: Schemes
This document describes a formal procedure for defining and standardizing new service types and attributes for use with the "service:" scheme. [STANDARDS-TRACK]
RFC2608 - Service Location Protocol, Version 2
The Service Location Protocol provides a scalable framework for the discovery and selection of network services. Using this protocol, computers using the Internet need little or no static configuration of network services for network based applications. This is especially important as computers become more portable, and users less tolerant or able to fulfill the demands of network system administration. [STANDARDS-TRACK]
RFC2607 - Proxy Chaining and Policy Implementation in Roaming
This document describes how proxy chaining and policy implementation can be supported in roaming systems. This memo provides information for the Internet community.
RFC2606 - Reserved Top Level DNS Names
To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.