RFC Abstracts
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.
RFC2605 - Directory Server Monitoring MIB
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2604 - 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.
RFC2603 - ILMI-Based Server Discovery for NHRP
This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate NHRP servers. [STANDARDS-TRACK]
RFC2602 - ILMI-Based Server Discovery for MARS
This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate MARS servers. [STANDARDS-TRACK]
RFC2601 - ILMI-Based Server Discovery for ATMARP
This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate ATMARP servers. [STANDARDS-TRACK]
RFC2600 - Internet Official Protocol Standards
This memo is published by the RFC Editor in accordance with Section 2.1 of "The Internet Standards Process -- Revision 3", RFC 2026, which specifies the rules and procedures by which all Internet standards are 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]
RFC2598 - An Expedited Forwarding PHB
The definition of PHBs (per-hop forwarding behaviors) is a critical part of the work of the Diffserv Working Group. This document describes a PHB called Expedited Forwarding. [STANDARDS-TRACK]
RFC2597 - Assured Forwarding PHB Group
This document defines a general use Differentiated Services (DS) Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF). [STANDARDS-TRACK]
RFC2596 - Use of Language Codes in LDAP
This document describes how language codes are carried in LDAP and are to be interpreted by LDAP servers. [STANDARDS-TRACK]
RFC2595 - Using TLS with IMAP, POP3 and ACAP
Recognizing that such sites will desire simple password authentication in combination with TLS encryption, this specification defines the PLAIN SASL mechanism for use with protocols which lack a simple password authentication command such as ACAP and SMTP. [STANDARDS-TRACK]
RFC2594 - Definitions of Managed Objects for WWW Services
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet Community. In particular it describes a set of objects for managing World Wide Web (WWW) services. [STANDARDS-TRACK]
RFC2593 - Script MIB Extensibility Protocol Version 1.0
The Script MIB extensibility protocol (SMX) defined in this memo separates language specific runtime systems from language independent Script MIB implementations. This memo defines an Experimental Protocol for the Internet community.
RFC2592 - Definitions of Managed Objects for the Delegation of Management Script
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that allow the delegation of management scripts to distributed managers. [STANDARDS-TRACK]
RFC2591 - Definitions of Managed Objects for Scheduling Management Operations
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2590 - Transmission of IPv6 Packets over Frame Relay Networks Specification
This memo describes mechanisms for the transmission of IPv6 packets over Frame Relay networks. [STANDARDS-TRACK]
RFC2589 - Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services
This document defines the requirements for dynamic directory services and specifies the format of request and response extended operations for supporting client-server interoperation in a dynamic directories environment. [STANDARDS-TRACK]
RFC2588 - IP Multicast and Firewalls
In this document, we discuss the issues surrounding the traversal of IP multicast traffic across a firewall, and describe possible ways in which a firewall can implement and control this traversal. We also explain why some firewall mechanisms - such as SOCKS - that were designed specifically for unicast traffic, are less appropriate for multicast. This memo provides information for the Internet community.
RFC2587 - Internet X.509 Public Key Infrastructure LDAPv2 Schema
The schema defined in this document is a minimal schema to support PKIX in an LDAPv2 environment, as defined in RFC 2559. Only PKIX-specific components are specified here. [STANDARDS-TRACK]
RFC2586 - The Audio/L16 MIME content type
This document defines the audio/L16 MIME type, a reasonable quality audio format for use in Internet applications. This memo provides information for the Internet community.
RFC2585 - Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP
The protocol conventions described in this document satisfy some of the operational requirements of the Internet Public Key Infrastructure (PKI). This document specifies the conventions for using the File Transfer Protocol (FTP) and the Hypertext Transfer Protocol (HTTP) to obtain certificates and certificate revocation lists (CRLs) from PKI repositories. [STANDARDS-TRACK]
RFC2584 - Definitions of Managed Objects for APPN/HPR in IP Networks
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling HPR (High Performance Routing) network devices which have the capability to communicate in IP (Internet Protocol) networks. [STANDARDS-TRACK]
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.
RFC2605 - Directory Server Monitoring MIB
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2604 - 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.
RFC2603 - ILMI-Based Server Discovery for NHRP
This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate NHRP servers. [STANDARDS-TRACK]
RFC2602 - ILMI-Based Server Discovery for MARS
This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate MARS servers. [STANDARDS-TRACK]
RFC2601 - ILMI-Based Server Discovery for ATMARP
This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate ATMARP servers. [STANDARDS-TRACK]
RFC2600 - Internet Official Protocol Standards
This memo is published by the RFC Editor in accordance with Section 2.1 of "The Internet Standards Process -- Revision 3", RFC 2026, which specifies the rules and procedures by which all Internet standards are 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]
RFC2598 - An Expedited Forwarding PHB
The definition of PHBs (per-hop forwarding behaviors) is a critical part of the work of the Diffserv Working Group. This document describes a PHB called Expedited Forwarding. [STANDARDS-TRACK]
RFC2597 - Assured Forwarding PHB Group
This document defines a general use Differentiated Services (DS) Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF). [STANDARDS-TRACK]
RFC2596 - Use of Language Codes in LDAP
This document describes how language codes are carried in LDAP and are to be interpreted by LDAP servers. [STANDARDS-TRACK]
RFC2595 - Using TLS with IMAP, POP3 and ACAP
Recognizing that such sites will desire simple password authentication in combination with TLS encryption, this specification defines the PLAIN SASL mechanism for use with protocols which lack a simple password authentication command such as ACAP and SMTP. [STANDARDS-TRACK]
RFC2594 - Definitions of Managed Objects for WWW Services
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet Community. In particular it describes a set of objects for managing World Wide Web (WWW) services. [STANDARDS-TRACK]
RFC2593 - Script MIB Extensibility Protocol Version 1.0
The Script MIB extensibility protocol (SMX) defined in this memo separates language specific runtime systems from language independent Script MIB implementations. This memo defines an Experimental Protocol for the Internet community.
RFC2592 - Definitions of Managed Objects for the Delegation of Management Script
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that allow the delegation of management scripts to distributed managers. [STANDARDS-TRACK]
RFC2591 - Definitions of Managed Objects for Scheduling Management Operations
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2590 - Transmission of IPv6 Packets over Frame Relay Networks Specification
This memo describes mechanisms for the transmission of IPv6 packets over Frame Relay networks. [STANDARDS-TRACK]
RFC2589 - Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services
This document defines the requirements for dynamic directory services and specifies the format of request and response extended operations for supporting client-server interoperation in a dynamic directories environment. [STANDARDS-TRACK]
RFC2588 - IP Multicast and Firewalls
In this document, we discuss the issues surrounding the traversal of IP multicast traffic across a firewall, and describe possible ways in which a firewall can implement and control this traversal. We also explain why some firewall mechanisms - such as SOCKS - that were designed specifically for unicast traffic, are less appropriate for multicast. This memo provides information for the Internet community.
RFC2587 - Internet X.509 Public Key Infrastructure LDAPv2 Schema
The schema defined in this document is a minimal schema to support PKIX in an LDAPv2 environment, as defined in RFC 2559. Only PKIX-specific components are specified here. [STANDARDS-TRACK]
RFC2586 - The Audio/L16 MIME content type
This document defines the audio/L16 MIME type, a reasonable quality audio format for use in Internet applications. This memo provides information for the Internet community.
RFC2585 - Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP
The protocol conventions described in this document satisfy some of the operational requirements of the Internet Public Key Infrastructure (PKI). This document specifies the conventions for using the File Transfer Protocol (FTP) and the Hypertext Transfer Protocol (HTTP) to obtain certificates and certificate revocation lists (CRLs) from PKI repositories. [STANDARDS-TRACK]
RFC2584 - Definitions of Managed Objects for APPN/HPR in IP Networks
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling HPR (High Performance Routing) network devices which have the capability to communicate in IP (Internet Protocol) networks. [STANDARDS-TRACK]