Tag-rfc-version: 1.0 Introduction:: END_I Generated by index2tag.pl version 4, plus many manual updates See http://www.paladin.demon.co.uk/tag-types/rfc/ END_I Keywords: PPP,Mail,SMTP,IMAP,Kerberos,Lirpa1,SNMP,Security,Web,Standards,DNS,LDAP,IPaddress,DHCP,Calendar End: Rfc: RFC2636 Title: Wireless Device Configuration (OTASP/OTAPA) via ACAP Authors: R. Gellens Status: Informational Date: 1999-07 Mailbox: randy@qualcomm.com Pages: 29 Characters: 65288 Obsoletes: RFC2604 I-D-Tag: draft-gellens-otasp-acap-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2636.txt Description:: END_D This paper describes a viable and attractive means to provide OTASP/OTAPA via IS-707, using the ACAP [ACAP] protocol. END_D End: Rfc: RFC2632 Title: S/MIME Version 3 Certificate Handling Authors: B. Ramsdell, Ed. Status: Proposed_Standard Date: 1999-06 Mailbox: blaker@deming.com Pages: 12 Characters: 27925 I-D-Tag: draft-ietf-smime-cert-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2632.txt Description:: END_D S/MIME agents MUST meet the certificate processing requirements documented in this document in addition to those stated in [KEYM]. END_D Working-Group: S/MIME Mail Security End: Rfc: RFC2629 Title: Writing I-Ds and RFCs using XML Authors: M. Rose Status: Informational Date: 1999-06 Mailbox: mrose@not.invisible.net Pages: 31 Characters: 48677 I-D-Tag: draft-mrose-writing-rfcs-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2629.txt Description:: END_D 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. END_D End: Rfc: RFC2619 Title: RADIUS Authentication Server MIB Authors: G. Zorn, B. Aboba Status: Proposed_Standard Date: 1999-06 Mailbox: glennz@microsoft.com, bernarda@microsoft.com Pages: 16 Characters: 30464 I-D-Tag: draft-ietf-radius-auth-servmib-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2619.txt Keywords: Security Description:: END_D This memo defines a set of extensions which instrument RADIUS authentication server functions. These extensions represent a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Using these extensions IP-based management stations can manage RADIUS authentication servers. END_D Working-Group: Remote Authentication Dial-In User Service End: Rfc: RFC2617 Title: HTTP Authentication: Basic and Digest Access Authentication Authors: J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A. Luotonen, L. Stewart Status: Draft_Standard Date: 1999-06 Mailbox: john@math.nwu.edu, pbaker@verisign.com, jeff@AbiSource.com, lawrence@agranat.com, paulle@microsoft.com, luotonen@netscape.com, stewart@OpenMarket.com Pages: 34 Characters: 77638 Obsoletes: RFC2069 I-D-Tag: draft-ietf-http-authentication-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2617.txt Description:: END_D "HTTP/1.0", includes the specification for a Basic Access Authentication scheme. This scheme is not considered to be a secure method of user authentication (unless used in conjunction with some external secure system such as SSL, as the user name and password are passed over the network as cleartext. END_D Working-Group: HyperText Transfer Protocol End: Rfc: RFC2616 Title: Hypertext Transfer Protocol -- HTTP/1.1 Authors: R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee Status: Draft_Standard Date: 1999-06 Mailbox: fielding@ics.uci.edu, jg@w3.org, mogul@wrl.dec.com, frystyk@w3.org, masinter@parc.xerox.com, paulle@microsoft.com, timbl@w3.org Pages: 176 Characters: 422317 Obsoletes: RFC2068 I-D-Tag: draft-ietf-http-v11-spec-rev-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2616.txt Description:: END_D The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. END_D Working-Group: HyperText Transfer Protocol End: Rfc: RFC2614 Title: An API for Service Location Authors: J. Kempf, E. Guttman Status: Informational Date: 1999-06 Mailbox: james.kempf@sun.com, erik.guttman@sun.com Pages: 91 Characters: 164002 I-D-Tag: draft-ietf-svrloc-api-09.txt Url: ftp://ftp.isi.edu/in-notes/rfc2614.txt Description:: END_D This document describes standardized APIs for SLP in C and Java. The APIs are modular and are designed to allow implementations to offer just the feature set needed. In addition, standardized file formats for configuration and serialized registrations are defined, allowing SLP agents to set network and other parameters in a portable way. END_D Working-Group: Service Location Protocol End: Rfc: RFC2612 Title: The CAST-256 Encryption Algorithm Authors: C. Adams, J. Gilchrist Status: Informational Date: 1999-06 Mailbox: carlisle.adams@entrust.com, jeff.gilchrist@entrust.com Pages: 19 Characters: 37468 I-D-Tag: draft-adams-cast-256-00.txt Url: ftp://ftp.isi.edu/in-notes/rfc2612.txt Description:: END_D There is always a desire in the Internet community for unencumbered encryption algorithms with a range of key sizes that can provide security for a variety of cryptographic applications and protocols. 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. END_D End: Rfc: RFC2611 Title: URN Namespace Definition Mechanisms Authors: L. Daigle, D. van Gulik, R. Iannella, P. Falstrom Status: Best_Current_Practice Date: 1999-06 Mailbox: leslie@thinkingcat.com, Dirk.vanGulik@jrc.it, renato@dstc.edu.au, paf@swip.net Pages: 14 Characters: 26916 I-D-Tag: draft-ietf-urn-nid-req-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2611.txt Description:: END_D The URN WG has defined a syntax for Uniform Resource Names (URNs) [RFC2141], as well as some proposed mechanisms for their resolution and use in Internet applications ([RFC2168, RFC2169]). The whole rests on the concept of individual "namespaces" within the URN structure. Apart from proof-of-concept namespaces, the use of existing identifiers in URNs has been discussed ([RFC2288]), and this document lays out general definitions of and mechanisms for establishing URN "namespaces". END_D Working-Group: Uniform Resource Names End: Rfc: RFC2610 Title: DHCP Options for Service Location Protocol Authors: C. Perkins, E. Guttman Status: Proposed_Standard Date: 1999-06 Mailbox: Charles.Perkins@Sun.Com, Erik.Guttman@Sun.Com Pages: 6 Characters: 10859 I-D-Tag: draft-ietf-dhc-slp-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2610.txt Description:: END_D 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. END_D Working-Group: Dynamic Host Configuration End: Rfc: RFC2609 Title: Service Templates and Service: Schemes Authors: E. Guttman, C. Perkins, J. Kempf Status: Proposed_Standard Date: 1999-06 Mailbox: Erik.Guttman@sun.com, cperkins@sun.com, james.kempf@sun.com Pages: 33 Characters: 72842 Updates: 2165 I-D-Tag: draft-ietf-svrloc-service-scheme-14.txt Url: ftp://ftp.isi.edu/in-notes/rfc2609.txt Description:: END_D This document describes a formal procedure for defining and standardizing new service types and attributes for use with the "service:" scheme. The formal descriptions of service types and attributes are templates that are human and machine understandable. They SHOULD be used by administrative tools to parse service registration information and by client applications to provide localized translations of service attribute strings. END_D Working-Group: Service Location Protocol End: Rfc: RFC2608 Title: Service Location Protocol, Version 2 Authors: E. Guttman, C. Perkins, J. Veizades, M. Day Status: Proposed_Standard Date: 1999-06 Mailbox: Erik.Guttman@sun.com, cperkins@sun.com, veizades@home.net, MDay@vinca.com Pages: 54 Characters: 129475 Updates: 2165 I-D-Tag: draft-ietf-svrloc-protocol-v2-15.txt Url: ftp://ftp.isi.edu/in-notes/rfc2608.txt Description:: END_D 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. END_D Working-Group: Service Location Protocol End: Rfc: RFC2607 Title: Proxy Chaining and Policy Implementation in Roaming Authors: B. Aboba, J. Vollbrecht Status: Informational Date: 1999-06 Mailbox: bernarda@microsoft.com, jrv@merit.edu Pages: 15 Characters: 33271 I-D-Tag: draft-ietf-roamops-auth-10.txt Url: ftp://ftp.isi.edu/in-notes/rfc2607.txt Description:: END_D This document describes how proxy chaining and policy implementation can be supported in roaming systems. The mechanisms described in this document are in current use. END_D Working-Group: Roaming Operations End: Rfc: RFC2606 Title: Reserved Top Level DNS Names Authors: D. Eastlake, A. Panitz Status: Best_Current_Practice Date: 1999-06 Mailbox: dee3@us.ibm.com, buglady@fuschia.net Pages: 5 Characters: 8008 I-D-Tag: draft-ietf-dnsind-test-tlds-13.txt Url: ftp://ftp.isi.edu/in-notes/rfc2606.txt Description:: END_D 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. END_D Working-Group: DNS, IXFR, Notification, and Dynamic Update End: Rfc: RFC2605 Title: Directory Server Monitoring MIB Authors: G. Mansfield, S. Kille Status: Standards Track Date: 1999-06 Mailbox: glenn@cysols.com, Steve.Kille@MessagingDirect.com Pages: 26 Characters: 49166 Obsoletes: RFC1567 I-D-Tag: draft-ietf-madman-dsa-mib-1-10.txt Url: ftp://ftp.isi.edu/in-notes/rfc2605.txt Description:: END_D This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo obsoletes RFC 1567, "X.500 Directory Monitoring MIB". This memo extends that specification to a more generic MIB for monitoring one or more directory servers each of which may support multiple access protocols. The MIB defined in this memo will be used in conjunction with the NETWORK-SERVICES-MIB [19] for monitoring Directory Servers. END_D Working-Group: Mail and Directory Management End: Rfc: RFC2604 Title: Wireless Device Configuration (OTASP/OTAPA) via ACAP Authors: R. Gellens Status: Informational Date: 1999-06 Mailbox: randy@qualcomm.com Pages: 29 Characters: 65329 I-D-Tag: draft-gellens-otasp-acap-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2604.txt Description:: END_D This paper describes a viable and attractive means to provide OTASP/OTAPA via IS-707, using the ACAP [ACAP] protocol. END_D Obsoleted-by: RFC2636 End: Rfc: RFC2603 Title: ILMI-Based Server Discovery for NHRP Authors: M. Davison Status: Proposed_Standard Date: 1999-06 Mailbox: mike.davison@cisco.com Pages: 6 Characters: 11865 I-D-Tag: draft-ietf-ion-discov-nhrp-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2603.txt Description:: END_D 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. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2602 Title: ILMI-Based Server Discovery for MARS Authors: M. Davison Status: Proposed_Standard Date: 1999-06 Mailbox: mike.davison@cisco.com Pages: 6 Characters: 12031 I-D-Tag: draft-ietf-ion-discov-mars-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2602.txt Description:: END_D 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. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2601 Title: ILMI-Based Server Discovery for ATMARP Authors: M. Davison Status: Proposed_Standard Date: 1999-06 Mailbox: mike.davison@cisco.com Pages: 6 Characters: 11820 I-D-Tag: draft-ietf-ion-discov-atmarp-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2601.txt Description:: END_D 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. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2598 Title: An Expedited Forwarding PHB Authors: V. Jacobson, K. Nichols, K. Poduri Status: Proposed_Standard Date: 1999-06 Mailbox: van@cisco.com, kmn@cisco.com, kpoduri@baynetworks.com Pages: 11 Characters: 23656 I-D-Tag: draft-ietf-diffserv-phb-ef-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2598.txt Description:: END_D 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. We show the generality of this PHB by noting that it can be produced by more than one mechanism and give an example of its use to produce at least one service, a Virtual Leased Line. A recommended codepoint for this PHB is given. END_D Working-Group: Differentiated Services End: Rfc: RFC2597 Title: Assured Forwarding PHB Group Authors: J. Heinanen, F. Baker, W. Weiss, J. Wroclawski Status: Proposed_Standard Date: 1999-06 Mailbox: jh@telia.fi, fred@cisco.com, wweiss@lucent.com, jtw@lcs.mit.edu Pages: 11 Characters: 24068 I-D-Tag: draft-ietf-diffserv-af-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2597.txt Description:: END_D This document defines a general use Differentiated Services (DS) Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF). The AF PHB group provides delivery of IP packets in four independently forwarded AF classes. Within each AF class, an IP packet can be assigned one of three different levels of drop precedence. A DS node does not reorder IP packets of the same microflow if they belong to the same AF class. END_D Working-Group: Differentiated Services End: Rfc: RFC2596 Title: Use of Language Codes in LDAP Authors: M. Wahl, T. Howes Status: Proposed_Standard Date: 1999-05 Mailbox: M.Wahl@innosoft.com, howes@netscape.com Pages: 9 Characters: 17413 I-D-Tag: draft-ietf-ldapext-lang-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2596.txt Description:: END_D This document describes how language codes are carried in LDAP and are to be interpreted by LDAP servers. All implementations MUST be prepared to accept language codes in the LDAP protocols. Servers may or may not be capable of storing attributes with language codes in the directory. This document does not specify how to determine whether particular attributes can or cannot have language codes. END_D Working-Group: LDAP Extension End: Rfc: RFC2595 Title: Using TLS with IMAP, POP3 and ACAP Authors: C. Newman Status: Proposed_Standard Date: 1999-06 Mailbox: chris.newman@innosoft.com Pages: 15 Characters: 32440 I-D-Tag: draft-newman-tls-imappop-09.txt Url: ftp://ftp.isi.edu/in-notes/rfc2595.txt Description:: END_D The TLS protocol (formerly known as SSL) provides a way to secure an application protocol from tampering and eavesdropping. The option of using such security is desirable for IMAP, POP and ACAP due to common connection eavesdropping and hijacking attacks. END_D End: Rfc: RFC2594 Title: Definitions of Managed Objects for WWW Services Authors: H. Hazewinkel, C. Kalbfleisch, J. Schoenwaelder Status: Proposed_Standard Date: 1999-05 Mailbox: harrie.hazewinkel@jrc.it, cwk@verio.net, schoenw@ibr.cs.tu-bs.de Pages: 43 Characters: 88876 I-D-Tag: draft-ietf-applmib-wwwmib-11.txt Url: ftp://ftp.isi.edu/in-notes/rfc2594.txt Description:: END_D 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. END_D Working-Group: Application MIB End: Rfc: RFC2593 Title: Script MIB Extensibility Protocol Version 1.0 Authors: J. Schoenwaelder, J. Quittek Status: Experimental Date: 1999-05 Mailbox: schoenw@ibr.cs.tu-bs.de, quittek@ccrle.nec.de Pages: 22 Characters: 49663 I-D-Tag: draft-schoenw-smx-00.txt Url: ftp://ftp.isi.edu/in-notes/rfc2593.txt Keywords: SNMP Description:: END_D The IETF Script MIB defines an interface for the delegation of management functions based on the Internet management framework. A management script is a set of instructions that are executed by a language specific runtime system. The Script MIB extensibility protocol (SMX) defined in this memo separates language specific runtime systems from language independent Script MIB implementations. END_D End: Rfc: RFC2592 Title: Definitions of Managed Objects for the Delegation of Management Scripts Authors: D. Levi, J. Schoenwaelder Status: Proposed_Standard Date: 1999-05 Mailbox: dlevi@nortelnetworks.com, schoenw@ibr.cs.tu-bs.de Pages: 53 Characters: 110629 I-D-Tag: draft-ietf-disman-script-mib-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2592.txt Keywords: SNMP Description:: END_D 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. END_D Working-Group: Distributed Management End: Rfc: RFC2591 Title: Definitions of Managed Objects for Scheduling Management Operations Authors: D. Levi, J. Schoenwaelder Status: Proposed_Standard Date: 1999-05 Mailbox: dlevi@nortelnetworks.com, schoenw@ibr.cs.tu-bs.de Pages: 25 Characters: 53146 Keywords: SNMP I-D-Tag: draft-ietf-disman-schedule-mib-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2591.txt Description:: END_D 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 are used to schedule management operations periodically or at specified dates and times. END_D Working-Group: Distributed Management End: Rfc: RFC2590 Title: Transmission of IPv6 Packets over Frame Relay Networks Specification Authors: A. Conta, A. Malis, M. Mueller Status: Proposed_Standard Date: 1999-05 Mailbox: aconta@lucent.com, malis@ascend.com, memueller@lucent.com Pages: 19 Characters: 41817 I-D-Tag: draft-ietf-ion-ipv6-fr-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2590.txt Description:: END_D This memo describes mechanisms for the transmission of IPv6 packets over Frame Relay networks. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2589 Title: Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services Authors: Y. Yaacovi, M. Wahl, T. Genovese Status: Proposed_Standard Date: 1999-05 Mailbox: yoramy@microsoft.com, Mark.Wahl@INNOSOFT.COM, tonyg@microsoft.com Pages: 12 Characters: 26855 I-D-Tag: draft-ietf-asid-ldapv3-dynamic-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2589.txt Description:: END_D 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. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2588 Title: IP Multicast and Firewalls Authors: R. Finlayson Status: Informational Date: 1999-05 Mailbox: finlayson@live.com Pages: 12 Characters: 28622 I-D-Tag: draft-ietf-mboned-mcast-firewall-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2588.txt Description:: END_D Many organizations use a firewall computer that acts as a security gateway between the public Internet and their private, internal 'intranet'. 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. END_D Working-Group: MBONE Deployment End: Rfc: RFC2587 Title: Internet X.509 Public Key Infrastructure LDAPv2 Schema Authors: S. Boeyen, T. Howes, P. Richard Status: Proposed_Standard Date: 1999-06 Mailbox: sharon.boeyen@entrust.com, howes@netscape.com, patr@xcert.com Pages: 8 Characters: 15102 I-D-Tag: draft-ietf-pkix-ldapv2-schema-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2587.txt Description:: END_D 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. LDAP servers, acting as PKIX repositories should support the auxiliary object classes defined in this specification and integrate this schema specification with the generic and other application-specific schemas as appropriate, depending on the services to be supplied by that server. END_D Working-Group: Public-Key Infrastructure (X.509) End: Rfc: RFC2586 Title: The Audio/L16 MIME content type Authors: J. Salsman, H. Alvestrand Status: Informational Date: 1999-05 Mailbox: James@bovik.org, Harald.T.Alvestrand@uninett.no Pages: 5 Characters: 8694 I-D-Tag: draft-alvestrand-audio-l16-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2586.txt Description:: END_D This document defines the audio/L16 MIME type, a reasonable quality audio format for use in Internet applications. Possible application areas include E-mail, Web served content, file upload in Web forms, and more. END_D End: Rfc: RFC2585 Title: Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP Authors: R. Housley, P. Hoffman Status: Proposed_Standard Date: 1999-05 Mailbox: housley@spyrus.com, phoffman@imc.org Pages: 8 Characters: 14813 I-D-Tag: draft-ietf-pkix-opp-ftp-http-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2585.txt Description:: END_D 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. Additional mechanisms addressing PKIX operational requirements are specified in separate documents. END_D Working-Group: Public-Key Infrastructure (X.509) End: Rfc: RFC2584 Title: Definitions of Managed Objects for APPN/HPR in IP Networks Authors: B. Clouston, B. Moore Status: Proposed_Standard Date: 1999-05 Mailbox: clouston@cisco.com, remoore@us.ibm.com Pages: 21 Characters: 40187 Keywords: SNMP I-D-Tag: draft-ietf-snanau-hpripmib-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2584.txt Description:: END_D 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. This memo identifies managed objects for the HPR in IP network communications. END_D Working-Group: SNA NAU Services MIB End: Rfc: RFC2583 Title: Guidelines for Next Hop Client (NHC) Developers Authors: R. Carlson, L. Winkler Status: Informational Date: 1999-05 Mailbox: RACarlson@anl.gov, lwinkler@anl.gov Pages: 9 Characters: 21338 I-D-Tag: draft-carlson-nhrp-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2583.txt Description:: END_D This document provides guidelines for developers of the Next Hop Resolution Protocol Clients (NHC). It assumes that the clients are directly connected to an ATM based NBMA network. The same principles will apply to clients connected to other types of NBMA networks. The intent is to define the interaction between the NHC code and the TCP/IP protocol stack of the local host operating system. The NHC is capable of sending NHRP requests to a Next Hop Resolution Protocol Server (NHS) to resolve both inter and intra LIS addresses. The NHS reply may be positive (ACK) indicating a short-cut path is available or negative (NAK) indicating that a shortcut is not available and the routed path must be used. The NHC must cache (maintain state) for both the ACK and NAK replies in order to use the correct shortcut or routed path. The NAK reply must be cached to avoid making repeated requests to the NHS when the routed path is being used. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2582 Title: The NewReno Modification to TCP's Fast Recovery Algorithm Authors: S. Floyd, T. Henderson Status: Experimental Date: 1999-04 Mailbox: floyd@acm.org, tomh@cs.berkeley.edu Pages: 12 Characters: 29393 I-D-Tag: draft-ietf-tcpimpl-newreno-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2582.txt Description:: END_D RFC 2001 documents the following four intertwined TCP congestion control algorithms: Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery. RFC 2581 explicitly allows certain modifications of these algorithms, including modifications that use the TCP Selective Acknowledgement (SACK) option, and modifications that respond to "partial acknowledgments" (ACKs which cover new data, but not all the data outstanding when loss was detected) in the absence of SACK. This document describes a specific algorithm for responding to partial acknowledgments, referred to as NewReno. This response to partial acknowledgments was first proposed by Janey Hoe. END_D Working-Group: TCP Implementation End: Rfc: RFC2581 Title: TCP Congestion Control Authors: M. Allman, V. Paxson, W. Stevens Status: Proposed_Standard Date: 1999-04 Mailbox: mallman@grc.nasa.gov, vern@aciri.org, rstevens@kohala.com Pages: 14 Characters: 31351 Obsoletes: RFC2001 I-D-Tag: draft-ietf-tcpimpl-cong-control-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2581.txt Description:: END_D This document defines TCP's four intertwined congestion control algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery. In addition, the document specifies how TCP should begin transmission after a relatively long idle period, as well as discussing various acknowledgment generation methods. END_D Working-Group: TCP Implementation End: Rfc: RFC2580 Title: Conformance Statements for SMIv2 Authors: K. McCloghrie, D. Perkins, J. Schoenwaelder Status: Standards Track Date: 1999-04 Mailbox: kzm@cisco.com, dperkins@snmpinfo.com, schoenw@ibr.cs.tu-bs.de Pages: 29 Characters: 54253 Obsoletes: RFC1904 I-D-Tag: draft-ops-smiv2-conf-01.txt Keywords: SNMP Url: ftp://ftp.isi.edu/in-notes/rfc2580.txt Description:: END_D Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using an adapted subset of OSI's Abstract Syntax Notation One, ASN.1 (1988), termed the Structure of Management Information (SMI). It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. END_D End: Rfc: RFC2579 Title: Textual Conventions for SMIv2 Authors: K. McCloghrie, D. Perkins, J. Schoenwaelder Status: Standards Track Date: 1999-04 Mailbox: kzm@cisco.com, dperkins@snmpinfo.com, schoenw@ibr.cs.tu-bs.de Pages: 26 Characters: 59039 Obsoletes: RFC1903 I-D-Tag: draft-ops-smiv2-tc-01.txt Keywords: SNMP Url: ftp://ftp.isi.edu/in-notes/rfc2579.txt Description:: END_D Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using an adapted subset of OSI's Abstract Syntax Notation One, ASN.1 (1988), termed the Structure of Management Information (SMI). When designing a MIB module, it is often useful to define new types similar to those defined in the SMI. In comparison to a type defined in the SMI, each of these new types has a different name, a similar syntax, but a more precise semantics. These newly defined types are termed textual conventions, and are used for the convenience of humans reading the MIB module. It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. END_D End: Rfc: RFC2578 Title: Structure of Management Information Version 2 (SMIv2) Authors: K. McCloghrie, D. Perkins, J. Schoenwaelder Status: Standards Track Date: 1999-04 Mailbox: kzm@cisco.com, dperkins@snmpinfo.com, schoenw@ibr.cs.tu-bs.de Pages: 43 Characters: 89712 Obsoletes: RFC1902 I-D-Tag: draft-ops-smiv2-smi-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2578.txt Keywords: SNMP Description:: END_D Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using an adapted subset of OSI's Abstract Syntax Notation One, ASN.1 (1988) [1]. It is the purpose of this document, the Structure of Management Information (SMI), to define that adapted subset, and to assign a set of associated administrative values. END_D End: Rfc: RFC2577 Title: FTP Security Considerations Authors: M. Allman, S. Ostermann Status: Informational Date: 1999-05 Mailbox: mallman@grc.nasa.gov, ostermann@cs.ohiou.edu Pages: 8 Characters: 17870 I-D-Tag: draft-ietf-ftpext-sec-consider-02.txt Keywords: Security Url: ftp://ftp.isi.edu/in-notes/rfc2577.txt Description:: END_D The specification for the File Transfer Protocol (FTP) contains a number of mechanisms that can be used to compromise network security. The FTP specification allows a client to instruct a server to transfer files to a third machine. This third-party mechanism, known as proxy FTP, causes a well known security problem. The FTP specification also allows an unlimited number of attempts at entering a user's password. This allows brute force "password guessing" attacks. This document provides suggestions for system administrators and those implementing FTP servers that will decrease the security problems associated with FTP. END_D Working-Group: Extensions to FTP End: Rfc: RFC2575 Title: View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) Authors: B. Wijnen, R. Presuhn, K. McCloghrie Status: Draft_Standard Date: 1999-04 Mailbox: wijnen@vnet.ibm.com, randy_presuhn@bmc.com, kzm@cisco.com Pages: 38 Characters: 79642 Obsoletes: RFC2275 Keywords: SNMP I-D-Tag: draft-ietf-snmpv3-vacm-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2575.txt Description:: END_D This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2571]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. END_D End: Rfc: RFC2574 Title: User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) Authors: U. Blumenthal, B. Wijnen Status: Draft_Standard Date: 1999-04 Mailbox: uri@watson.ibm.com, wijnen@vnet.ibm.com Pages: 86 Characters: 190755 Obsoletes: RFC2274 I-D-Tag: draft-ietf-snmpv3-usm-v2-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2574.txt Keywords: SNMP Description:: END_D This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2571]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. END_D End: Rfc: RFC2573 Title: SNMP Applications Authors: D. Levi, P. Meyer, B. Stewart Status: Draft_Standard Date: 1999-04 Mailbox: levi@snmp.com, paul_meyer@securecomputing.com, bstewart@cisco.com Pages: 72 Characters: 150427 Obsoletes: RFC2273 I-D-Tag: draft-ietf-snmpv3-appl-v2-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2573.txt Keywords: SNMP Description:: END_D This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2571]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. END_D End: Rfc: RFC2572 Title: Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) Authors: J. Case, D. Harrington, R. Presuhn, B. Wijnen Status: Draft_Standard Date: 1999-04 Mailbox: case@snmp.com, dbh@ctron.com, rpresuhn@bmc.com, wijnen@vnet.ibm.com Pages: 44 Characters: 96035 Obsoletes: RFC2272 Keywords: SNMP I-D-Tag: draft-ietf-snmpv3-mpc-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2572.txt Description:: END_D This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2571]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. END_D Working-Group: SNMP Version 3 End: Rfc: RFC2571 Title: An Architecture for Describing SNMP Management Frameworks Authors: B. Wijnen, D. Harrington, R. Presuhn Status: Draft_Standard Date: 1999-04 Mailbox: wijnen@vnet.ibm.com, dbh@ctron.com, randy_presuhn@bmc.com Pages: 62 Characters: 139260 Obsoletes: RFC2271 Keywords: SNMP I-D-Tag: draft-ietf-snmpv3-arch-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2571.txt Description:: END_D This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. The major portions of the architecture are an SNMP engine containing a Message Processing Subsystem, a Security Subsystem and an Access Control Subsystem, and possibly multiple SNMP applications which provide specific functional processing of management data. END_D End: Rfc: RFC2570 Title: Introduction to Version 3 of the Internet-standard Network Management Framework Authors: J. Case, R. Mundy, D. Partain, B. Stewart Status: Informational Date: 1999-04 Mailbox: case@snmp.com, mundy@tis.com, David.Partain@ericsson.com, bstewart@cisco.com Pages: 23 Characters: 50381 I-D-Tag: draft-ietf-snmpv3-intro-04.txt Keywords: SNMP Url: ftp://ftp.isi.edu/in-notes/rfc2570.txt Description:: END_D The purpose of this document is to provide an overview of the third version of the Internet-standard Management Framework, termed the SNMP version 3 Framework (SNMPv3). This Framework is derived from and builds upon both the original Internet-standard Management Framework (SNMPv1) and the second Internet-standard Management Framework (SNMPv2). END_D Working-Group: SNMP Version 3 End: Rfc: RFC2569 Title: Mapping between LPD and IPP Protocols Authors: R. Herriot, Ed., T. Hastings, N. Jacobs, J. Martin Status: Experimental Date: 1999-04 Mailbox: rherriot@pahv.xerox.com, hastings@cp10.es.xerox.com, Norm.Jacobs@Central.sun.com, jkm@underscore.com Pages: 28 Characters: 57886 I-D-Tag: draft-ietf-ipp-lpd-ipp-map-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2569.txt Description:: END_D This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). IPP is an application level protocol that can be used for distributed printing using Internet tools and technologies. This document gives some advice to implementers of gateways between IPP and LPD (Line Printer Daemon). This document describes the mapping between (1) the commands and operands of the 'Line Printer Daemon (LPD) Protocol' specified in RFC 1179 and (2) the operations, operation attributes and job template attributes of the Internet Printing Protocol/1.0 (IPP). One of the purposes of this document is to compare the functionality of the two protocols. Another purpose is to facilitate implementation of gateways between LPD and IPP. END_D Working-Group: Internet Printing Protocol End: Rfc: RFC2568 Title: Rationale for the Structure of the Model and Protocol for the Internet Printing Protocol Authors: S. Zilles Status: Experimental Date: 1999-04 Mailbox: szilles@adobe.com Pages: 10 Characters: 23547 I-D-Tag: draft-ietf-ipp-rat-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2568.txt Description:: END_D This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). IPP is an application level protocol that can be used for distributed printing using Internet tools and technologies. This document describes IPP from a high level view, defines a roadmap for the various documents that form the suite of IPP specifications, and gives background and rationale for the IETF working group's major decisions. END_D Working-Group: Internet Printing Protocol End: Rfc: RFC2567 Title: Design Goals for an Internet Printing Protocol Authors: F. Wright Status: Experimental Date: 1999-04 Mailbox: don@lexmark.com Pages: 43 Characters: 90260 I-D-Tag: draft-ietf-ipp-req-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2567.txt Description:: END_D This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). IPP is an application level protocol that can be used for distributed printing using Internet tools and technologies. This document takes a broad look at distributed printing functionality, and it enumerates real-life scenarios that help to clarify the features that need to be included in a printing protocol for the Internet. It identifies requirements for three types of users: end users, operators, and administrators. The design goals document calls out a subset of end user requirements that are satisfied in IPP/1.0. Operator and administrator requirements are out of scope for version 1.0 END_D Working-Group: Internet Printing Protocol End: Rfc: RFC2566 Title: Internet Printing Protocol/1.0: Model and Semantics Authors: R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell Status: Experimental Date: 1999-04 Mailbox: debry@vnet.ibm.com, hastings@cp10.es.xerox.com, robert.herriot@eng.sun.com, sisaacson@novell.com, papowell@astart.com Pages: 173 Characters: 438887 I-D-Tag: draft-ietf-ipp-model-11.txt Url: ftp://ftp.isi.edu/in-notes/rfc2566.txt Description:: END_D This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). IPP is an application level protocol that can be used for distributed printing using Internet tools and technologies. This document describes a simplified model consisting of abstract objects, their attributes, and their operations that is independent of encoding and transport. The model consists of a Printer and a Job object. A Job optionally supports multiple documents. IPP 1.0 semantics allow end-users and operators to query printer capabilities, submit print jobs, inquire about the status of print jobs and printers, and cancel print jobs. This document also addresses security, internationalization, and directory issues. END_D Working-Group: Internet Printing Protocol End: Rfc: RFC2565 Title: Internet Printing Protocol/1.0: Encoding and Transport Authors: R. Herriot, Ed., S. Butler, P. Moore, R. Turner Status: Experimental Date: 1999-04 Mailbox: rherriot@pahv.xerox.com, sbutler@boi.hp.com, paulmo@microsoft.com, rturner@sharplabs.com Pages: 37 Characters: 80429 I-D-Tag: draft-ietf-ipp-protocol-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2565.txt Description:: END_D This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). IPP is an application level protocol that can be used for distributed printing using Internet tools and technologies. This document defines the rules for encoding IPP operations and IPP attributes into a new Internet mime media type called "application/ipp". This document also defines the rules for transporting over HTTP a message body whose Content-Type is "application/ipp". END_D Working-Group: Internet Printing Protocol End: Rfc: RFC2564 Title: Application Management MIB Authors: C. Kalbfleisch, C. Krupczak, R. Presuhn, J. Saperia Status: Proposed_Standard Date: 1999-05 Mailbox: cwk@verio.net, cheryl@empiretech.com, randy_presuhn@bmc.com, saperia@ironbridgenetworks.com Pages: 86 Characters: 183314 I-D-Tag: draft-ietf-applmib-mib-11.txt Url: ftp://ftp.isi.edu/in-notes/rfc2564.txt Keywords: SNMP Description:: END_D This memo defines a standards track portion of the Management Information Base (MIB) for use with network management protocols in the Internet Community. In particular, it defines objects used for the management of applications. This MIB complements the System Application MIB, providing for the management of applications' common attributes which could not typically be observed without the cooperation of the software being managed. END_D Working-Group: Application MIB End: Rfc: RFC2563 Title: DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients Authors: R. Troll Status: Proposed_Standard Date: 1999-05 Mailbox: ryan@andrew.cmu.edu Pages: 9 Characters: 17838 Keywords: DHCP I-D-Tag: draft-ietf-dhc-autoconfig-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2563.txt Description:: END_D Operating Systems are now attempting to support ad-hoc networks of two or more systems, while keeping user configuration at a minimum. To accommodate this, in the absence of a central configuration mechanism (DHCP), some OS's are automatically choosing a link-local IP address which will allow them to communicate only with other hosts on the same link. This address will not allow the OS to communicate with anything beyond a router. However, some sites depend on the fact that a host with no DHCP response will have no IP address. This document describes a mechanism by which DHCP servers are able to tell clients that they do not have an IP address to offer, and that the client should not generate an IP address it's own. END_D End: Rfc: RFC2562 Title: Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB) Authors: K. White, R. Moore Status: Proposed_Standard Date: 1999-04 Mailbox: kennethw@vnet.ibm.com, remoore@us.ibm.com Pages: 49 Characters: 110633 I-D-Tag: draft-ietf-tn3270e-rt-mib-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2562.txt Description:: END_D This memo defines the protocol and the Management Information Base (MIB) for performing response time data collection on TN3270 and TN3270E sessions by a TN3270E server. The response time data collected by a TN3270E server is structured to support both validation of service level agreements and performance monitoring of TN3270 and TN3270E Sessions. This MIB has as a prerequisite the TN3270E-MIB, reference. END_D Working-Group: Telnet TN3270 Enchancements End: Rfc: RFC2561 Title: Base Definitions of Managed Objects for TN3270E Using SMIv2 Authors: K. White, R. Moore Status: Proposed_Standard Date: 1999-04 Mailbox: kennethw@vnet.ibm.com, remoore@us.ibm.com Pages: 56 Characters: 113705 I-D-Tag: draft-ietf-tn3270e-tn3270-mib-10.txt Url: ftp://ftp.isi.edu/in-notes/rfc2561.txt Description:: END_D The MIB defined by this memo provides generic support for both host and gateway TN3270E server implementations. A TN3270E server connects a Telnet client performing 3270 emulation to a target SNA host over both a client-side network (client to TN3270E server) and an SNA Network (TN3270E server to target SNA host). The client-side network is typically TCP/IP, but it need not be. END_D Working-Group: Telnet TN3270 Enchancements End: Rfc: RFC2560 Title: X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP Authors: M. Myers, R. Ankney, A. Malpani, S. Galperin, C. Adams Status: Proposed_Standard Date: 1999-06 Mailbox: mmyers@verisign.com, rankney@erols.com, ambarish@valicert.com, galperin@mycfo.com, cadams@entrust.com, Pages: 23 Characters: 43243 I-D-Tag: draft-ietf-pkix-ocsp-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2560.txt Description:: END_D This document specifies a protocol useful in determining the current status of a digital certificate without requiring CRLs. Additional mechanisms addressing PKIX operational requirements are specified in separate documents. END_D Working-Group: Public-Key Infrastructure (X.509) End: Rfc: RFC2559 Title: Internet X.509 Public Key Infrastructure Operational Protocols - LDAPv2 Authors: S. Boeyen, T. Howes, P. Richard Status: Standards Track Date: 1999-04 Mailbox: boeyen@entrust.com, howes@netscape.com, patr@xcert.com Pages: 13 Characters: 22889 Updates: 1778 I-D-Tag: draft-ietf-pkix-ipki2opp-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2559.txt Description:: END_D The protocol described in this document is designed to satisfy some of the operational requirements within the Internet X.509 Public Key Infrastructure (IPKI). Specifically, this document addresses requirements to provide access to Public Key Infrastructure (PKI) repositories for the purposes of retrieving PKI information and managing that same information. The mechanism described in this document is based on the Lightweight Directory Access Protocol (LDAP) v2, defined in RFC 1777, defining a profile of that protocol for use within the IPKI and updates encodings for certificates and revocation lists from RFC 1778. Additional mechanisms addressing PKIX operational requirements are specified in separate documents. END_D Working-Group: PKIX End: Rfc: RFC2558 Title: Definitions of Managed Objects for the SONET/SDH Interface Type Authors: K. Tesink Status: Proposed_Standard Date: 1999-03 Mailbox: kaj@research.telcordia.com Pages: 74 Characters: 138550 Obsoletes: RFC1595 I-D-Tag: draft-ietf-atommib-sonetng-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2558.txt Description:: END_D 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 Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This document is a companion to the documents that define Managed Objects for the DS1/E1/DS2/E2 and DS3/E3 Interface Types [24][25]. END_D Working-Group: AToM MIB End: Rfc: RFC2557 Title: MIME Encapsulation of Aggregate Documents, such as HTML (MHTML) Authors: J. Palme, A. Hopmann, N. Shelness Status: Proposed_Standard Date: 1999-03 Mailbox: jpalme@dsv.su.se, alexhop@microsoft.com, Shelness@lotus.com Pages: 28 Characters: 61854 Obsoletes: RFC2110 I-D-Tag: draft-ietf-mhtml-rev-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2557.txt Description:: END_D This document a) defines the use of a MIME multipart/related structure to aggregate a text/html root resource and the subsidiary resources it references, and b) specifies a MIME content-header (Content-Location) that allow URIs in a multipart/related text/html root body part to reference subsidiary resources in other body parts of the same multipart/related structure. END_D Working-Group: MIME Encapsulation of Aggregate HTML Documents End: Rfc: RFC2556 Title: OSI connectionless transport services on top of UDP Applicability Statement for Historic Status Authors: S. Bradner Status: Informational Date: 1999-03 Mailbox: sob@harvard.edu Pages: 4 Characters: 5864 I-D-Tag: draft-bradner-1240.his-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2556.txt Description:: END_D RFC 1240, "OSI connectionless transport services on top of UDP", was published as a Proposed Standard in June 1991 but at this time there do not seem to be any implementations which follow RFC 1240. In addition there is a growing concern over using UDP-based transport protocols in environments where congestion is a possibility. END_D End: Rfc: RFC2555 Title: 30 Years of RFCs Authors: RFC Editor, et al. Status: Informational Date: 1999-04 Mailbox: braden@isi.edu, jkrey@isi.edu, crocker@mbl.edu, vcerf@mci.net, feinler@juno.com, celeste@isi.edu Pages: 18 Characters: 42902 I-D-Tag: none Keywords: Standards Url: ftp://ftp.isi.edu/in-notes/rfc2555.txt Description:: END_D History and reflections on the Request for Comments (RFC) document series, and the people who made it possible, on its 30th anniversary. END_D End: Rfc: RFC2554 Title: SMTP Service Extension for Authentication Authors: J. Myers Status: Proposed_Standard Date: 1999-03 Mailbox: jgmyers@netscape.com Pages: 11 Characters: 20534 I-D-Tag: draft-myers-smtp-auth-12.txt Url: ftp://ftp.isi.edu/in-notes/rfc2554.txt Keywords: SMTP, Mail, Security Description:: END_D This document defines an SMTP service extension [ESMTP] whereby an SMTP client may indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions. This extension is a profile of the Simple Authentication and Security Layer [SASL]. END_D End: Rfc: RFC2553 Title: Basic Socket Interface Extensions for IPv6 Authors: R. Gilligan, S. Thomson, J. Bound, W. Stevens Status: Informational Date: 1999-03 Mailbox: gilligan@freegate.net, set@thumper.bellcore.com, bound@zk3.dec.com, rstevens@kohala.com Pages: 41 Characters: 89215 Obsoletes: RFC2133 I-D-Tag: draft-ietf-ipngwg-bsd-api-new-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2553.txt Description:: END_D The de facto standard application program interface (API) for TCP/IP applications is the "sockets" interface. Although this API wasdeveloped for Unix in the early 1980s it has also been implemented on a wide variety of non-Unix systems. TCP/IP applications written using the sockets API have in the past enjoyed a high degree of portability and we would like the same portability with IPv6 applications. But changes are required to the sockets API to support IPv6 and this memo describes these changes. These include a new socket address structure to carry IPv6 addresses, new address conversion functions, and some new socket options. These extensions are designed to provide access to the basic IPv6 features required by TCP and UDP applications, including multicasting, while introducing a minimum of change into the system and providing complete compatibility for existing IPv4 applications. Additional extensions for advanced IPv6 features (raw sockets and access to the IPv6 extension headers) are defined in another document. END_D Working-Group: IPNG End: Rfc: RFC2552 Title: Architecture for the Information Brokerage in the ACTS Project GAIA Authors: M. Blinov, M. Bessonov, C. Clissmann Status: Informational Date: 1999-04 Mailbox: mch@net-cs.ucd.ie, mikeb@net-cs.ucd.ie, ciaranc@net-cs.ucd.ie Pages: 30 Characters: 65172 I-D-Tag: draft-rfced-info-blinov-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2552.txt Description:: END_D This memo introduces a domain and supplier independent generic architecture for information brokerage, designed as part of the ACTS project GAIA (Generic Architecture for Information Availability). END_D End: Rfc: RFC2551 Title: The Roman Standards Process -- Revision III Authors: S. Bradner Status: Worst Current Practice Date: 1999-04-01 Mailbox: sob@harvard.edu Pages: 14 Characters: 28054 Obsoletes: RFCMMXXVI I-D-Tag: draft-seinfeld-is-over-move-on-01.txt Keywords: Lirpa1 Url: ftp://ftp.isi.edu/in-notes/rfc2551.txt Description:: END_D This memo documents the process used by the Roman community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. It also addresses the intellectual property rights and copyright issues associated with the standards process. This document specifies a Roman Worst Current Practices for the Roman Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. END_D End: Rfc: RFC2550 Title: Y10K and Beyond Authors: S. Glassman, M. Manasse, J. Mogul Status: Stinkards Track Date: 1999-04-01 Mailbox: steveg@pa.dec.com, msm@pa.dec.com, mogul@pa.dec.com Pages: 14 Characters: 28054 Pages: 14 Characters: 28054 I-D-Tag: draft-brrl-of-mnkys-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2550.txt Keywords: Lirpa1 Description:: END_D As we approach the end of the millennium, much attention has been paid to the so-called "Y2K" problem. Nearly everyone now regrets the short-sightedness of the programmers of yore who wrote programs designed to fail in the year 2000. Unfortunately, the current fixes for Y2K lead inevitably to a crisis in the year 10,000 when the programs are again designed to fail. END_D End: Rfc: RFC2549 Title: IP over Avian Carriers with Quality of Servic Authors: D. Waitzman Status: Experimental Date: 1999-04-01 Mailbox: djw@vineyard.net Pages: 6 Characters: 9519 Updates: RFC1149 Keywords: Lirpa1 I-D-Tag: draft-isnt-this-fun-v2-00.txt Url: ftp://ftp.isi.edu/in-notes/rfc2549.txt Description:: END_D This memo amends RFC 1149, "A Standard for the Transmission of IP Datagrams on Avian Carriers", with Quality of Service information. This is an experimental, not recommended standard END_D End: Rfc: RFC2548 Title: Microsoft Vendor-specific RADIUS Attributes Authors: G. Zorn Status: Informational Date: 1999-03 Mailbox: glennz@microsoft.com Pages: 41 Characters: 80763 I-D-Tag: draft-ietf-radius-ms-vsa-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2548.txt Keywords: Security Description:: END_D This document describes the set of Microsoft vendor-specific RADIUS attributes. These attributes are designed to support Microsoft proprietary dial-up protocols and/or provide support for features which is not provided by the standard RADIUS attribute set [3]. It is expected that this memo will be updated whenever Microsoft defines a new vendor-specific attribute, since its primary purpose is to provide an open, easily accessible reference for third-parties wishing to interoperate with Microsoft products. END_D Working-Group: Remote Authentication Dial-In User Service End: Rfc: RFC2547 Title: BGP/MPLS VPNs Authors: E. Rosen, Y. Rekhter Status: Informational Date: 1999-03 Mailbox: erosen@cisco.com, yakov@cisco.com Pages: 25 Characters: 63270 I-D-Tag: draft-rose-vpm-mpls-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2547.txt Description:: END_D This document describes a method by which a Service Provider with an IP backbone may provide VPNs (Virtual Private Networks) for its customers. MPLS (Multiprotocol Label Switching) is used for forwarding packets over the backbone, and BGP (Border Gateway Protocol) is used for distributing routes over the backbone. The primary goal of this method is to support the outsourcing of IP backbone services for enterprise networks. It does so in a manner which is simple for the enterprise, while still scalable and flexible for the Service Provider, and while allowing the Service Provider to add value. These techniques can also be used to provide a VPN which itself provides IP service to customers. END_D End: Rfc: RFC2546 Title: 6Bone Routing Practice Authors: A. Durand, B. Buclin Status: Informational Date: 1999-03 Mailbox: Alain.Durand@imag.fr, Bertrand.Buclin@ch.att.com Pages: 10 Characters: 17844 I-D-Tag: draft-ietf-ngtrans-6bone-routing-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2546.txt Description:: END_D This memo identifies guidelines on how 6Bone sites might operate, so that the 6Bone can remain a quality experimentation environment and to avoid pathological situations that have been encountered in the past. It defines the 'best current practice' acceptable in the 6Bone for the configuration of both Interior Gateway Protocols (such as RIPng [RFC 2080]) and Exterior Gateway Protocols (like BGP4+ [RFC 2283]). END_D Working-Group: Next Generation Transition End: Rfc: RFC2545 Title: Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing Authors: P. Marques, F. Dupont Status: Proposed_Standard Date: 1999-03 Mailbox: roque@cisco.com, Francis.Dupont@inria.fr Pages: 5 Characters: 10209 I-D-Tag: draft-ietf-idr-bgp4-ipv6-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2545.txt Description:: END_D BGP-4 Multiprotocol Extensions [BGP-MP] defines the format of two BGP attributes (MP_REACH_NLRI and MP_UNREACH_NLRI) that can be used to announce and withdraw the announcement of reachability information. This document defines how compliant systems should make use of those attributes for the purpose of conveying IPv6 routing information. END_D Working-Group: Inter-Domain Routing End: Rfc: RFC2544 Title: Benchmarking Methodology for Network Interconnect Devices Authors: S. Bradner, J. McQuaid Status: Informational Date: 1999-03 Mailbox: sob@harvard.edu, mcquaidj@netscout.com Pages: 31 Characters: 66688 Obsoletes: RFC1944 I-D-Tag: NA Url: ftp://ftp.isi.edu/in-notes/rfc2544.txt Description:: END_D This document is a republication of RFC 1944 correcting the values for the IP addresses which were assigned to be used as the default addresses for networking test equipment. (See section C.2.2 ). This RFC replaces and obsoletes RFC 1944. 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. Appendix A lists the tests and conditions that we believe should be included for specific cases and gives additional information about testing practices. Appendix B is a reference listing of maximum frame rates to be used with specific frame sizes on various media and Appendix C gives some examples of frame formats to be used in testing. END_D End: Rfc: RFC2543 Title: SIP: Session Initiation Protocol Authors: M. Handley, H. Schulzrinne, E. Schooler, J. Rosenberg Status: Proposed_Standard Date: 1999-03 Mailbox: mjh@isi.edu, schulzrinne@cs.columbia.edu, schooler@cs.caltech.edu, jdrosen@bell-labs.com Pages: 153 Characters: 338861 I-D-Tag: draft-ietf-mmusic-sip-12.txt Url: ftp://ftp.isi.edu/in-notes/rfc2543.txt Description:: END_D The Session Initiation Protocol (SIP) is an application-layer control (signaling) protocol for creating, modifying and terminating sessions with one or more participants. These sessions include Internet multimedia conferences, Internet telephone calls and multimedia distribution. Members in a session can communicate via multicast or via a mesh of unicast relations, or a combination of these. END_D Working-Group: Multiparty Multimedia Session Control End: Rfc: RFC2542 Title: Terminology and Goals for Internet Fax Authors: L. Masinter Status: Informational Date: 1999-03 Mailbox: masinter@parc.xerox.com Pages: 20 Characters: 46372 I-D-Tag: draft-ietf-fax-goals-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2542.txt Description:: END_D This document defines a number of terms useful for the discussion of Internet Fax. In addition, it describes the goals of the Internet Fax working group and establishes a baseline of desired functionality against which protocols for Internet Fax can be judged. It encompasses the goals for all modes of facsimile delivery, including 'real-time', 'session', and 'store and forward'. Different levels of desirability are indicated throughout the document. END_D Working-Group: Internet Fax End: Rfc: RFC2541 Title: DNS Security Operational Considerations Authors: D. Eastlake Status: Informational Date: 1999-03 Mailbox: dee3@us.ibm.com Pages: 7 Characters: 14498 I-D-Tag: draft-ietf-dnssec-secops-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2541.txt Description:: END_D Secure DNS is based on cryptographic techniques. A necessary part of the strength of these techniques is careful attention to the operational aspects of key and signature generation, lifetime, size, and storage. In addition, special attention must be paid to the security of the high level zones, particularly the root zone. This document discusses these operational aspects for keys and signatures used in connection with the KEY and SIG DNS resource records. END_D Working-Group: Domain Name System Security End: Rfc: RFC2540 Title: Detached Domain Name System (DNS) Information Authors: D. Eastlake Status: Experimental Date: 1999-03 Mailbox: dee3@us.ibm.com Pages: 6 Characters: 12546 Keywords: DNS I-D-Tag: draft-ietf-dnssec-ddi-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2540.txt Description:: END_D A standard format is defined for representing detached DNS information. This is anticipated to be of use for storing information retrieved from the Domain Name System (DNS), including security information, in archival contexts or contexts not connected to the Internet. END_D Working-Group: Domain Name System Security End: Rfc: RFC2539 Title: Storage of Diffie-Hellman Keys in the Domain Name System (DNS) Authors: D. Eastlake Status: Proposed_Standard Date: 1999-03 Mailbox: dee3@us.ibm.com Keywords: DNS Pages: 7 Characters: 21049 I-D-Tag: draft-ietf-dnssec-dhk-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2539.txt Description:: END_D A standard method for storing Diffie-Hellman keys in the Domain Name System is described which utilizes DNS KEY resource records. END_D Working-Group: Domain Name System Security End: Rfc: RFC2538 Title: Storing Certificates in the Domain Name System (DNS) Authors: D. Eastlake, O. Gudmundsson Status: Proposed_Standard Date: 1999-03 Mailbox: dee3@us.ibm.com, ogud@tislabs.com Pages: 10 Keywords: DNS Characters: 19857 I-D-Tag: draft-ietf-dnssec-certs-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2538.txt Description:: END_D Cryptographic public key are frequently published and their authenticity demonstrated by certificates. A CERT resource record (RR) is defined so that such certificates and related certificate revocation lists can be stored in the Domain Name System (DNS). END_D Working-Group: Domain Name System Security End: Rfc: RFC2537 Title: RSA/MD5 KEYs and SIGs in the Domain Name System (DNS) Authors: D. Eastlake Status: Proposed_Standard Date: 1999-03 Mailbox: dee3@us.ibm.com Pages: 6 Characters: 10810 Keywords: DNS I-D-Tag: draft-ietf-dnssec-rsa-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2537.txt Description:: END_D A standard method for storing RSA keys and and RSA/MD5 based signatures in the Domain Name System is described which utilizes DNS KEY and SIG resource records. END_D Working-Group: Domain Name System Security End: Rfc: RFC2536 Title: DSA KEYs and SIGs in the Domain Name System (DNS) Authors: D. Eastlake Status: Proposed_Standard Date: 1999-03 Mailbox: dee3@us.ibm.com Pages: 6 Characters: 11121 Keywords: DNS I-D-Tag: draft-ietf-dnssec-dss-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2536.txt Description:: END_D A standard method for storing US Government Digital Signature Algorithm keys and signatures in the Domain Name System is described which utilizes DNS KEY and SIG resource records. END_D Working-Group: Domain Name System Security End: Rfc: RFC2535 Title: Domain Name System Security Extensions Authors: D. Eastlake Status: Proposed_Standard Date: 1999-03 Mailbox: dee3@us.ibm.com Pages: 47 Characters: 110958 Updates: 2181, 1035, 1034 Obsoletes: RFC2065 Keywords: DNS, Security I-D-Tag: draft-ietf-dnssec-secext2-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2535.txt Description:: END_D Extensions to the Domain Name System (DNS) are described that provide data integrity and authentication to security aware resolvers and applications through the use of cryptographic digital signatures. These digital signatures are included in secured zones as resource records. Security can also be provided through non-security aware DNS servers in some cases. END_D Working-Group: Domain Name System Security End: Rfc: RFC2534 Title: Media Features for Display, Print, and Fax Authors: L. Masinter, D. Wing, A. Mutz, K. Holtman Status: Proposed_Standard Date: 1999-03 Mailbox: masinter@parc.xerox.com, dwing@cisco.com, mutz@alum.mit.edu, koen@win.tue.nl Pages: 9 Characters: 15466 I-D-Tag: draft-ietf-conneg-media-features-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2534.txt Description:: END_D This specification defines some common media features for describing image resolution, size, color, and image representation methods that are common to web browsing, printing, and facsimile applications. END_D Working-Group: Content Negotiation End: Rfc: RFC2533 Title: A Syntax for Describing Media Feature Sets Authors: G. Klyne Status: Proposed_Standard Date: 1999-03 Mailbox: GK@ACM.ORG Pages: 37 Characters: 79057 I-D-Tag: draft-ietf-conneg-feature-syntax-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2533.txt Description:: END_D This document introduces and describes a syntax that can be used to define feature sets which are formed from combinations and relations involving individual media features. Such feature sets are used to describe the media feature handling capabilities of message senders, recipients and file formats. END_D Working-Group: Content Negotiation End: Rfc: RFC2532 Title: Extended Facsimile Using Internet Mail Authors: L. Masinter, D. Wing Status: Proposed_Standard Date: 1999-03 Mailbox: masinter@parc.xerox.com, dwing@cisco.com Pages: 12 Characters: 22717 I-D-Tag: draft-ietf-fax-eifax-12.txt Url: ftp://ftp.isi.edu/in-notes/rfc2532.txt Description:: END_D This document describes extensions to "Simple Mode of Facsimile Using Internet Mail" [RFC2305] and describes additional features, including transmission of enhanced document characteristics (higher resolution, color) and confirmation of delivery and processing. END_D Working-Group: Internet Fax End: Rfc: RFC2531 Title: Content Feature Schema for Internet Fax Authors: G. Klyne, L. McIntyre Status: Proposed_Standard Date: 1999-03 Mailbox: GK@ACM.ORG, Lloyd.McIntyre@pahv.xerox.com Pages: 51 Characters: 88295 I-D-Tag: draft-ietf-fax-feature-schema-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2531.txt Description:: END_D This document defines a content feature schema that is a profile of the media feature registration mechanisms for use in performing capability identification between extended Internet fax systems. END_D Working-Group: Internet Fax End: Rfc: RFC2530 Title: Indicating Supported Media Features Using Extensions to DSN and MDN Authors: D. Wing Status: Proposed_Standard Date: 1999-03 Mailbox: dwing@cisco.com Pages: 5 Characters: 7824 Keywords: SMTP I-D-Tag: draft-ietf-fax-reporting-extensions-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2530.txt Description:: END_D This memo describes a format for generating Message Disposition Notifications [RFC2298] and Delivery Status Notifications [RFC1894] which contain such information. This information can be used by senders to avoid exceeding the recipient's capabilities when sending subsequent messages. END_D Working-Group: Internet Fax End: Rfc: RFC2529 Title: Transmission of IPv6 over IPv4 Domains without Explicit Tunnels Authors: B. Carpenter, C. Jung Status: Proposed_Standard Date: 1999-03 Mailbox: brian@hursley.ibm.com, cmj@3Com.com Pages: 10 Characters: 21049 I-D-Tag: draft-ietf-ipngwg-6over4-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2529.txt Description:: END_D This memo specifies the frame format for transmission of IPv6 [IPV6] packets and the method of forming IPv6 link-local addresses over IPv4 domains. It also specifies the content of the Source/Target Link-layer Address option used in the Router Solicitation, Router Advertisement, Neighbor Solicitation, and Neighbor Advertisement and Redirect messages, when those messages are transmitted on an IPv4 multicast network. END_D Working-Group: IPNG End: Rfc: RFC2528 Title: Internet X.509 Public Key Infrastructure Representation of Key Exchange Algorithm (KEA) Keys in Internet X.509 Public Key Infrastructure Certificates Authors: R. Housley, W. Polk Status: Informational Date: 1999-03 Mailbox: housley@spyrus.com, wpolk@nist.gov Pages: 9 Characters: 18273 I-D-Tag: draft-ietf-pkix-ipki-kea-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2528.txt Description:: END_D The Key Exchange Algorithm (KEA) is a classified algorithm for exchanging keys. This specification profiles the format and semantics of fields in X.509 V3 certificates containing KEA keys. The specification addresses the subjectPublicKeyInfo field and the keyUsage extension. END_D Working-Group: Public-Key Infrastructure (X.509) End: Rfc: RFC2527 Title: Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework Authors: S. Chokhani, W. Ford Status: Informational Date: 1999-03 Mailbox: chokhani@cygnacom.com, wford@verisign.com Pages: 45 Characters: 91860 I-D-Tag: draft-ietf-pkix-ipki-part4-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2527.txt Description:: END_D This document presents a framework to assist the writers of certificate policies or certification practice statements for certification authorities and public key infrastructures. In particular, the framework provides a comprehensive list of topics that potentially (at the writer's discretion) need to be covered in a certificate policy definition or a certification practice statement. END_D Working-Group: Public-Key Infrastructure (X.509) End: Rfc: RFC2526 Title: Reserved IPv6 Subnet Anycast Addresses Authors: D. Johnson, S. Deering Status: Proposed_Standard Date: 1999-03 Mailbox: dbj@cs.cmu.edu, deering@cisco.com Pages: 7 Characters: 14555 I-D-Tag: draft-ietf-ipngwg-resv-anycast-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2526.txt Description:: END_D The IP Version 6 addressing architecture defines an "anycast" address as an IPv6 address that is assigned to one or more network interfaces (typically belonging to different nodes), with the property that a packet sent to an anycast address is routed to the "nearest" interface having that address, according to the routing protocols' measure of distance. This document defines a set of reserved anycast addresses within each subnet prefix, and lists the initial allocation of these reserved subnet anycast addresses. END_D Working-Group: IPNG End: Rfc: RFC2525 Title: Known TCP Implementation Problems Authors: V. Paxson, M Allman, S. Dawson, W. Fenner, J. Griner, I. Heavens, K. Lahey, J. Semke, B. Volz Status: Informational Date: 1999-03 Mailbox: vern@ee.lbl.gov, mallman@lerc.nasa.gov, sdawson@eecs.umich.edu, fenner@parc.xerox.com, jgriner@lerc.nasa.gov, ian@spider.com, kml@nas.nasa.gov, semke@psc.edu, volz@process.com Pages: 61 Characters: 137201 I-D-Tag: draft-ietf-tcpimpl-prob-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2525.txt Description:: END_D This memo catalogs a number of known TCP implementation problems. The goal in doing so is to improve conditions in the existing Internet by enhancing the quality of current TCP/IP implementations. It is hoped that both performance and correctness issues can be resolved by making implementors aware of the problems and their solutions. In the long term, it is hoped that this will provide a reduction in unnecessary traffic on the network, the rate of connection failures due to protocol errors, and load on network servers due to time spent processing both unsuccessful connections and retransmitted data. This will help to ensure the stability of the global Internet. END_D Working-Group: TCP Implementation End: Rfc: RFC2524 Title: Neda's Efficient Mail Submission and Delivery (EMSD) Protocol Specification Version 1.3 Authors: M. Banan Status: Informational Date: 1999-02 Mailbox: mohsen@neda.com Pages: 83 Keywords: Mail Characters: 153171 I-D-Tag: draft-rfced-info-banan-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2524.txt Description:: END_D This document specifies the protocol and format encodings for Efficient Mail Submission and Delivery (EMSD). EMSD is a messaging protocol that is highly optimized for submission and delivery of short Internet mail messages. EMSD is designed to be a companion to existing Internet mail protocols. END_D End: Rfc: RFC2523 Title: Photuris: Extended Schemes and Attributes Authors: P. Karn, W. Simpson Status: Experimental Date: 1999-03 Mailbox: karn@unix.ka9q.ampr.org, wsimpson@GreenDragon.com Pages: 19 Characters: 38166 I-D-Tag: draft-simpson-photouris-schemes-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2523.txt Description:: END_D Photuris is a session-key management protocol. Extensible Exchange-Schemes are provided to enable future implementation changes without affecting the basic protocol. END_D End: Rfc: RFC2522 Title: Photuris: Session-Key Management Protocol Authors: P. Karn, W. Simpson Status: Experimental Date: 1999-03 Mailbox: karn@unix.ka9q.ampr.org, wsimpson@GreenDragon.com Pages: 76 Characters: 157224 I-D-Tag: draft-simpson-photouris-18.txt Url: ftp://ftp.isi.edu/in-notes/rfc2522.txt Description:: END_D Photuris is a session-key management protocol intended for use with the IP Security Protocols (AH and ESP). This document defines the basic protocol mechanisms. END_D End: Rfc: RFC2521 Title: ICMP Security Failures Messages Authors: P. Karn, W. Simpson Status: Experimental Date: 1999-03 Mailbox: karn@unix.ka9q.ampr.org, wsimpson@GreenDragon.com Pages: 7 Characters: 14637 I-D-Tag: draft-simpson-icmp-ipsec-fail-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2521.txt Description:: END_D This mechanism is intended for use with the Internet Security Protocols [RFC-1825 et sequitur] for authentication and privacy. For statically configured Security Associations, these messages indicate that the operator needs to manually reconfigure, or is attempting an unauthorized operation. These messages may also be used to trigger automated session-key management. END_D End: Rfc: RFC2520 Title: NHRP with Mobile NHCs Authors: J. Luciani, H. Suzuki, N. Doraswamy, D. Horton Status: Experimental Date: 1999-02 Mailbox: luciani@baynetworks.com, hsuzuki@cisco.com, naganand@baynetworks.com, d.horton@citr.com.au Pages: 8 Characters: 16763 I-D-Tag: draft-ietf-ion-nhrp-mobile-nhc-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2520.txt Description:: END_D This document describes an extension to NHRP which would allow Mobile NHCs to perform a registration with and attach to an NHS in their home LIS in an authenticated manner. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2519 Title: A Framework for Inter-Domain Route Aggregation Authors: E. Chen, J. Stewart Status: Informational Date: 1999-02 Mailbox: enkechen@cisco.com, jstewart@juniper.net Pages: 13 Characters: 25394 I-D-Tag: draft-ietf-idr-aggregation-framework-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2519.txt Description:: END_D This document presents a framework for inter-domain route aggregation and shows an example router configuration which \'implements' this framework. This framework is flexible and scales well as it emphasizes the philosophy of aggregation by the source, both within routing domains as well as towards upstream providers, and it also strongly encourages the use of the \'no-export' BGP community to balance the provider-subscriber need for more granular routing information with the Internet's need for scalable inter-domain routing. END_D Working-Group: Inter-Domain Routing End: Rfc: RFC2518 Title: HTTP Extensions for Distributed Authoring -- WEBDAV Authors: Y. Goland, E. Whitehead, A. Faizi, S. Carter, D. Jensen Status: Proposed_Standard Date: 1999-02 Mailbox: yarong@microsoft.com, ejw@ics.uci.edu, asad@netscape.com, srcarter@novell.com, dcjensen@novell.com Pages: 94 Characters: 202829 I-D-Tag: draft-ietf-webdav-protocol-10.txt Url: ftp://ftp.isi.edu/in-notes/rfc2518.txt Description:: END_D This document specifies a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, namespace manipulation, and resource locking (collision avoidance). END_D Working-Group: WWW Distributed Authoring and Versioning End: Rfc: RFC2517 Title: Building Directories from DNS: Experiences from WWWSeeker Authors: R. Moats, R. Huber Status: Informational Date: 1999-02 Mailbox: jayhawk@att.com, rvh@att.com Pages: 7 Characters: 14001 I-D-Tag: draft-rfced-info-moats-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2517.txt Description:: END_D There has been much discussion and several documents written about the need for an Internet Directory. Recently, this discussion has focused on ways to discover an organization's domain name without relying on use of DNS as a directory service. This memo discusses lessons that were learned during InterNIC Directory and Database Services' development and operation of WWWSeeker, an application that finds a web site given information about the name and location of an organization. The back end database that drives this application was built from information obtained from domain registries via WHOIS and other protocols. END_D End: Rfc: RFC2516 Title: Method for Transmitting PPP Over Ethernet (PPPoE) Authors: L. Mamakos, K. Lidl, J. Evarts, D. Carrel, D. Simone, R. Wheeler Status: Informational Date: 1999-02 Mailbox: louie@uu.net, lidl@uu.net, jde@uu.net, carrel@RedBack.net, dan@RedBack.net, ross@routerware.com Pages: 17 Characters: 32537 Keywords: PPP I-D-Tag: draft-carrel-info-pppoe-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2516.txt Description:: END_D The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes how to build PPP sessions and encapsulate PPP packets over Ethernet. END_D End: Rfc: RFC2514 Title: Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management Authors: M. Noto, E. Spiegel, K. Tesink Status: Proposed_Standard Date: 1999-02 Mailbox: mike_noto@net.com, mspiegel@cisco.com, kaj@bellcore.com Pages: 20 Characters: 37583 I-D-Tag: draft-ietf-atommib-atm2TC-09.txt Url: ftp://ftp.isi.edu/in-notes/rfc2514.txt Description:: END_D This memo describes Textual Conventions and OBJECT-IDENTITIES used for managing ATM-based interfaces, devices, networks and services. END_D Working-Group: AToM MIB End: Rfc: RFC2511 Title: Internet X.509 Certificate Request Message Format Authors: M. Myers, C. Adams, D. Solo, D. Kemp Status: Proposed_Standard Date: 1999-03 Mailbox: mmyers@verisign.com, cadams@entrust.com, david.solo@citicorp.com, dpkemp@missi.ncsc.mil Pages: 25 Characters: 48278 I-D-Tag: draft-ietf-pkix-crmf-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2511.txt Description:: END_D This document describes the Certificate Request Message Format (CRMF). This syntax is used to convey a request for a certificate to a Certification Authority (CA) (possibly via a Registration Authority (RA)) for the purposes of X.509 certificate production. The request will typically include a public key and associated registration information. END_D Working-Group: Public-Key Infrastructure (X.509) End: Rfc: RFC2510 Title: Internet X.509 Public Key Infrastructure Certificate Management Protocols Authors: C. Adams, S. Farrell Status: Proposed_Standard Date: 1999-03 Mailbox: cadams@entrust.com, stephen.farrell@sse.ie Pages: 72 Characters: 158178 I-D-Tag: draft-ietf-pkix-ipki3cmp-09.txt Url: ftp://ftp.isi.edu/in-notes/rfc2510.txt Description:: END_D This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocols. Protocol messages are defined for all relevant aspects of certificate creation and management. END_D Working-Group: Public-Key Infrastructure (X.509) End: Rfc: RFC2509 Title: IP Header Compression over PPP Authors: M. Engan, S. Casner, C. Bormann Status: Proposed_Standard Date: 1999-02 Mailbox: engan@effnet.com, casner@cisco.com, cabo@tzi.org Pages: 10 Characters: 18676 Keywords: PPP I-D-Tag: draft-engan-ip-compress-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2509.txt Description:: END_D This document describes an option for negotiating the use of header compression on IP datagrams transmitted over the Point-to-Point Protocol [RFC1661]. It defines extensions to the PPP Control Protocols for IPv4 and IPv6 [RFC1332, RFC2023]. Header compression may be applied to IPv4 and IPv6 datagrams in combination with TCP, UDP and for IPv4 and IPv6 [RFC1332, RFC2023]. Header compression may be applied to IPv4 and IPv6 datagrams in combination with TCP, UDP and RTP transport protocols as specified in [IPHC] and [CRTP]. END_D Working-Group: Point-to-Point Protocol Extensions End: Rfc: RFC2508 Title: Compressing IP/UDP/RTP Headers for Low-Speed Serial Links Authors: S. Casner, V. Jacobson Status: Proposed_Standard Date: 1999-02 Mailbox: casner@cisco.com, van@cisco.com Pages: 24 Characters: 60474 I-D-Tag: draft-ietf-avt-crtp-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2508.txt Description:: END_D This document describes a method for compressing the headers of IP/UDP/RTP datagrams to reduce overhead on low-speed serial links. In many cases, all three headers can be compressed to 2-4 bytes. END_D Working-Group: Audio/Video Transport End: Rfc: RFC2507 Title: IP Header Compression Authors: M. Degermark, B. Nordgren, S. Pink Status: Proposed_Standard Date: 1999-02 Mailbox: micke@sm.luth.se, bcn@lulea.trab.se, steve@sm.luth.se Characters: 106292 I-D-Tag: draft-degermark-ipv6-hc-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2507.txt Description:: END_D This document describes how to compress multiple IP headers and TCP and UDP headers per hop over point to point links. The methods can be applied to of IPv6 base and extension headers, IPv4 headers, TCP and UDP headers, and encapsulated IPv6 and IPv4 headers. END_D Working-Group: IPNG End: Rfc: RFC2506 Title: Media Feature Tag Registration Procedure Authors: K. Holtman, A. Mutz, T. Hardie Status: Best_Current_Practice Date: 1999-03 Mailbox: koen@win.tue.nl, andy_mutz@hp.com, hardie@equinix.com Pages: 12 Characters: 24892 I-D-Tag: draft-ietf-conneg-feature-req-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2506.txt Description:: END_D This document defines a registration procedure which uses the Internet Assigned Numbers Authority (IANA) as a central registry for the media feature vocabulary. END_D Working-Group: Content Negotiation End: Rfc: RFC2505 Title: Anti-Spam Recommendations for SMTP MTAs Authors: G. Lindberg Status: Best_Current_Practice Date: 1999-02 Mailbox: lindberg@cdg.chalmers.se Keywords: Mail, SMTP Pages: 24 Characters: 53597 I-D-Tag: draft-lindberg-anti-spam-mta-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2505.txt Description:: END_D This memo gives a number of implementation recommendations for SMTP, MTAs (Mail Transfer Agents, e.g. sendmail) to make them more capable of reducing the impact of spam. END_D End: Rfc: RFC2504 Title: Users' Security Handbook Authors: E. Guttman, L. Leong, G. Malkin Status: Informational Date: 1999-02 Mailbox: erik.guttman@sun.com, lorna@colt.net, gmalkin@baynetworks.com Pages: 33 Characters: 74036 BCP: 34 I-D-Tag: draft-ietf-ssh-users-10.txt Url: ftp://ftp.isi.edu/in-notes/rfc2504.txt Description:: END_D The Users' Security Handbook is the companion to the Site Security Handbook (SSH). It is intended to provide users with the information they need to help keep their networks and systems secure. END_D Working-Group: Site Security Handbook End: Rfc: RFC2503 Title: MIME Types for Use with the ISO ILL Protocol Authors: R. Moulton, M. Needleman Status: Informational Date: 1999-02 Mailbox: ruth@muswell.demon.co.uk, Mark.Needleman@ucop.edu Pages: 6 Characters: 9078 I-D-Tag: draft-needleman-mime-ill-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2503.txt Description:: END_D This memorandum describes a set of MIME types for use with the ISO Interlibrary Loan Protocol (ISO 10160/10161). END_D End: Rfc: RFC2502 Title: Limitations of Internet Protocol Suite for Distributed Simulation the Large Multicast Environment Authors: M. Pullen, M. Myjak, C. Bouwens Status: Informational Date: 1999-02 Mailbox: mpullen@gmu.edu, mmyjak@virtualworkshop.com, christina.bouwens@cpmx.mail.saic.com Pages: 11 Characters: 28190 I-D-Tag: draft-ietf-lsma-limitations-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2502.txt Description:: END_D The Large-Scale Multicast Applications (LSMA) working group was chartered to produce documents aimed at a consensus based development of the Internet protocols to support large scale multicast applications including real-time distributed simulation. This memo defines services that LSMA has found to be required, and aspects of the Internet protocols that LSMA has found to need further development in order to meet these requirements. END_D Working-Group: Large Scale Multicast Applications End: Rfc: RFC2501 Title: Mobile Ad hoc Networking (MANET): Routing Protocol Performance Issues and Evaluation Considerations Authors: S. Corson, J. Macker Status: Informational Date: 1999-01 Mailbox: corson@isr.umd.edu, macker@itd.nrl.navy.mil Pages: 12 Characters: 28912 I-D-Tag: draft-ietf-manet-issues-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2501.txt Description:: END_D This memo first describes the characteristics of Mobile Ad hoc Networks (MANETs), and their idiosyncrasies with respect to traditional, hardwired packet networks. It then discusses the effect these differences have on the design and evaluation of network control protocols with an emphasis on routing performance evaluation considerations. END_D Working-Group: Mobile Ad-hoc Networks End: Rfc: RFC2500 Title: Internet Official Protocol Standards Authors: J. Reynolds, R. Braden, Eds. Status: Standard Date: 1999-06 Mailbox: jkrey@rfc-editor.org, braden@rfc-editor.org Pages: 28 Characters: 78845 Obsoletes: RFC2400, 2300, 2200, 2000, 1920, 1880, 1800, 1780, 1720, 1610, 1600, 1540, 1500, 1410, 1360, 1280, 1250, 1200, 1140, 1130, 1100, 1083 I-D-Tag: None Url: ftp://ftp.isi.edu/in-notes/rfc2500.txt Description:: END_D This memo summarizes the status of Internet protocols and specifications. It 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 stnadards are set. This memo is prepared by the RFC Editor for the IESG and IAB. It is a member of a series of summary memos that are published approximately every one hundred RFCs; please see www.rfc-editor.org. END_D End: Rfc: RFC2498 Title: IPPM Metrics for Measuring Connectivity Authors: J. Mahdavi, V. Paxson Status: Experimental Date: 1999-01 Mailbox: mahdavi@psc.edu, vern@ee.lbl.gov Pages: 10 Characters: 17869 I-D-Tag: draft-ietf-ippm-connectivity-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2498.txt Description:: END_D This memo defines a series of metrics for connectivity between a pair of Internet hosts. It builds on notions introduced and discussed in RFC 2330, the IPPM framework document. The reader is assumed to be familiar with that document. END_D Working-Group: IP Performance Metrics End: Rfc: RFC2497 Title: Transmission of IPv6 Packets over ARCnet Networks Authors: I. Souvatzis Status: Proposed_Standard Date: 1999-01 Mailbox: is@netbsd.org Pages: 6 Characters: 10304 See-Also: RFC1201 I-D-Tag: draft-souvatzis-ipv6-arcnet-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2497.txt Description:: END_D This memo specifies a frame format for transmission of IPv6 [IPV6] packets and the method of forming IPv6 link-local and statelessly autoconfigured addresses on ARCnet networks. It also specifies the content of the Source/Target Link-layer Address option used by the Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and Redirect messages described in [DISC], when those messages are transmitted on an ARCnet. END_D Working-Group: IPNG End: Rfc: RFC2496 Title: Definitions of Managed Objects for the DS3/E3 Interface Type Authors: D. Fowler, Ed. Status: Proposed_Standard Date: 1999-01 Mailbox: davef@newbridge.com Pages: 60 Characters: 124251 Keywords: SNMP I-D-Tag: draft-ietf-trunkmib-ds3-mib-09.txt Url: ftp://ftp.isi.edu/in-notes/rfc2496.txt Description:: END_D 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 objects used for managing DS3 and E3 interfaces. This document is a companion document with Definitions of Managed Objects for the DS0 (RFC 2494 [25]), DS1/E1/DS2/E2 (RFC 2495 [17]), and the work in progress SONET/SDH Interface Types. END_D Working-Group: DS1/DS3 MIB End: Rfc: RFC2495 Title: Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types Authors: D. Fowler, Ed. Status: Proposed_Standard Date: 1999-01 Mailbox: davef@newbridge.com Pages: 75 Characters: 155560 Keywords: SNMP I-D-Tag: draft-ietf-trunkmib-ds1-mib-09.txt Url: ftp://ftp.isi.edu/in-notes/rfc2495.txt Description:: END_D 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 objects used for managing DS1, E1, DS2 and E2 interfaces. This document is a companion document with Definitions of Managed Objects for the DS0 (RFC 2494 [30]), DS3/E3 (RFC 2496 [28]), and the work in progress, SONET/SDH Interface Types. END_D Working-Group: DS1/DS3 MIB End: Rfc: RFC2494 Title: Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type Authors: D. Fowler, Ed. Status: Proposed_Standard Date: 1999-01 Mailbox: davef@newbridge.com Pages: 25 Keywords: SNMP Characters: 47208 I-D-Tag: draft-ietf-trunkmib-ds0-mib-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2494.txt Description:: END_D 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 objects used for managing DS0 and DS0 Bundle interfaces. This document is a companion document with Definitions of Managed Objects for the DS1/E1/DS2/E2 (RFC 2495 [17]), DS3/E3 (RFC 2496 [18]), and the work in progress, SONET/SDH Interface Types. END_D Working-Group: DS1/DS3 MIB End: Rfc: RFC2493 Title: Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals Authors: K. Tesink, Ed. Status: Proposed_Standard Date: 1999-01 Mailbox: kaj@bellcore.com Pages: 9 Keywords: SNMP Characters: 18749 I-D-Tag: draft-ietf-atommib-perfhistTC-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2493.txt Description:: END_D This document defines a set of Textual Conventions for MIB modules which make use of performance history data based on 15 minute intervals. END_D Working-Group: AToM MIB End: Rfc: RFC2492 Title: IPv6 over ATM Networks Authors: G. Armitage, P. Schulter, M. Jork Status: Proposed_Standard Date: 1999-01 Mailbox: gja@lucent.com, paschulter@acm.org, jork@kar.dec.com Pages: 12 Characters: 21199 I-D-Tag: draft-ietf-ion-atm-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2492.txt Description:: END_D This document is a companion to the ION working group's architecture document, "IPv6 over Non Broadcast Multiple Access (NBMA) networks". It provides specific details on how to apply the IPv6 over NBMA architecture to ATM networks. This architecture allows conventional host-side operation of the IPv6 Neighbor Discovery protocol, while also supporting the establishment of \'shortcut' ATM forwarding paths (when using SVCs). Operation over administratively configured Point to Point PVCs is also supported. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2491 Title: IPv6 over Non-Broadcast Multiple Access (NBMA) networks Authors: G. Armitage, P. Schulter, M. Jork, G. Harter Status: Proposed_Standard Date: 1999-01 Mailbox: gja@lucent.com, paschulter@acm.org, jork@kar.dec.com, harter@zk3.dec.com Pages: 44 Characters: 100782 I-D-Tag: draft-ietf-ion-ipv6-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2491.txt Description:: END_D This document describes a general architecture for IPv6 over NBMA networks. It forms the basis for subsidiary companion documents that describe details for various specific NBMA technologies (such as ATM or Frame Relay). The IPv6 over NBMA architecture allows conventional host-side operation of the IPv6 Neighbor Discovery protocol, while also supporting the establishment of \'shortcut' NBMA forwarding paths when dynamically signaled NBMA links are available. Operations over administratively configured Point to Point NBMA links are also described. Dynamic NBMA shortcuts are achieved through the use of IPv6 Neighbor Discovery protocol operation within Logical Links, and inter-router NHRP for the discovery of off-Link NBMA destinations. Both flow-triggered and explicitly source-triggered shortcuts are supported. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2490 Title: A Simulation Model for IP Multicast with RSVP Authors: M. Pullen, R. Malghan, L. Lavu, G. Duan, J. Ma, H. Nah Status: Informational Date: 1999-01 Mailbox: mpullen@gmu.edu, rmalghan@bacon.gmu.edu, llavu@bacon.gmu.edu, gduan@us.oracle.com, jma@newbridge.com, hnah@bacon.gmu.edu Pages: 31 Characters: 74936 I-D-Tag: draft-pullen-ipv4-rsvp-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2490.txt Description:: END_D This document describes a detailed model of IPv4 multicast with RSVP that has been developed using the OPNET simulation package [4], with protocol procedures defined in the C language. The model was developed to allow investigation of performance constraints on routing but should have wide applicability in the Internet multicast/resource reservation community. We are making this model publicly available with the intention that it can be used to provide expanded studies of resource-reserved multicasting. END_D End: Rfc: RFC2489 Title: Procedure for Defining New DHCP Options Authors: R. Droms Status: Best_Current_Practice Date: 1999-01 Mailbox: droms@bucknell.edu Pages: 5 Characters: 10484 Keywords: DHCP I-D-Tag: draft-ietf-dhc-new-options-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2489.txt Description:: END_D The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. Configuration parameters and other control information are carried in tagged data items that are stored in the \'options' field of the DHCP message. The data items themselves are also called "options." New DHCP options may be defined after the publication of the DHCP specification to accommodate requirements for conveyance of new configuration parameters. This document describes the procedure for defining new DHCP options. END_D Working-Group: Dynamic Host Configuration End: Rfc: RFC2488 Title: Enhancing TCP Over Satellite Channels using Standard Mechanisms Authors: M. Allman, D. Glover, L. Sanchez Status: Best_Current_Practice Date: 1999-01 Mailbox: mallman@lerc.nasa.gov, Daniel.R.Glover@lerc.nasa.gov, lsanchez@ir.bbn.com Pages: 19 Characters: 47857 BCP: 28 I-D-Tag: draft-ietf-tcpsat-stand-mech-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2488.txt Description:: END_D The Transmission Control Protocol (TCP) provides reliable delivery of data across any network path, including network paths containing satellite channels. While TCP works over satellite channels there are several IETF standardized mechanisms that enable TCP to more effectively utilize the available capacity of the network path. This document outlines some of these TCP mitigations. At this time, all mitigations discussed in this document are IETF standards track mechanisms (or are compliant with IETF standards). END_D Working-Group: TCP Over Satellite End: Rfc: RFC2487 Title: SMTP Service Extension for Secure SMTP over TLS Authors: P. Hoffman Status: Proposed_Standard Date: 1999-01 Mailbox: phoffman@imc.org Pages: 8 Characters: 15120 Keywords: SMTP, Mail, Security I-D-Tag: draft-hoffman-smtp-ssl-10.txt Url: ftp://ftp.isi.edu/in-notes/rfc2487.txt Description:: END_D This document describes an extension to the SMTP service that allows an SMTP server and client to use transport-layer security to provide private, authenticated communication over the Internet. This gives SMTP agents the ability to protect some or all of their communications from eavesdroppers and attackers. END_D End: Rfc: RFC2486 Title: The Network Access Identifier Authors: B. Aboba, M. Beadles Status: Proposed_Standard Date: 1999-01 Mailbox: bernarda@microsoft.com, mbeadles@wcom.net Pages: 8 Characters: 14261 Keywords: PPP, Security I-D-Tag: draft-ietf-roamops-nai-12.txt Url: ftp://ftp.isi.edu/in-notes/rfc2486.txt Description:: END_D In order to enhance the interoperability of roaming and tunneling services, it is desirable to have a standardized method for identifying users. This document proposes syntax for the Network Access Identifier (NAI), the userID submitted by the client during PPP authentication. It is expected that this will be of interest for support of roaming as well as tunneling. "Roaming capability" may be loosely defined as the ability to use any one of multiple Internet service providers (ISPs), while maintaining a formal, customer-vendor relationship with only one. Examples of where roaming capabilities might be required include ISP "confederations" and ISP-provided corporate network access support. END_D Working-Group: Roaming Operations End: Rfc: RFC2485 Title: DHCP Option for The Open Group's User Authentication Protocol Authors: S. Drach Status: Proposed_Standard Date: 1999-01 Mailbox: drach@sun.com Pages: 4 Keywords: DHCP Characters: 7205 I-D-Tag: draft-ietf-dhc-options-uap-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2485.txt Description:: END_D This document defines a DHCP [1] option that contains a list of pointers to User Authentication Protocol servers that provide user authentication services for clients that conform to The Open Group Network Computing Client Technical Standard [2]. END_D Working-Group: Dynamic Host Configuration End: Rfc: RFC2484 Title: PPP LCP Internationalization Configuration Option Authors: G. Zorn Status: Proposed_Standard Date: 1999-01 Mailbox: glennz@microsoft.com Pages: 5 Characters: 8330 Keywords: PPP Updates: RFC2284, RFC1994, RFC1570 I-D-Tag: draft-ietf-pppext-lcp-charset-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2484.txt Description:: END_D The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP also defines an extensible Link Control Protocol (LCP), which allows negotiation of an Authentication Protocol for authenticating its peer before allowing Network Layer protocols to transmit over the link. Both LCP and Authentication Protocol packets may contain text which is intended to be human-readable [2,3,4]. This document defines an LCP configuration option for the negotiation of character set and language usage, as required by RFC 2277 [5]. END_D Working-Group: Point-to-Point Protocol Extensions End: Rfc: RFC2483 Title: URI Resolution Services Necessary for URN Resolution Authors: M. Mealling, R. Daniel, Jr. Status: Experimental Date: 1999-01 Mailbox: michaelm@rwhois.net, rdaniel@lanl.gov Pages: 16 Characters: 30518 I-D-Tag: draft-ietf-urn-resolution-services-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2483.txt Description:: END_D Retrieving the resource identified by a Uniform Resource Identifier (URI) [1] is only one of the operations that can be performed on a URI. One might also ask for and get a list of other identifiers that are aliases for the original URI or a bibliographic description of the resource the URI denotes, for example. This applies to both Uniform Resource Names (URNs) and Uniform Resource Locators (URLs). Uniform Resource Characteristics (URCs) are discussed in this document but only as descriptions of resources rather than identifiers. END_D Working-Group: Uniform Resource Names End: Rfc: RFC2482 Title: Language Tagging in Unicode Plain Text Authors: K. Whistler, G. Adams Status: Informational Date: 1999-01 Mailbox: kenw@sybase.com, glenn@spyglass.com Pages: 14 Characters: 27800 I-D-Tag: draft-whistler-plane14-00.txt Url: ftp://ftp.isi.edu/in-notes/rfc2482.txt Description:: END_D This document proposed a mechanism for language tagging in [UNICODE] plain text. A set of special-use tag characters on Plane 14 of [ISO10646] (accessible through UTF-8, UTF-16, and UCS-4 encoding forms) are proposed for encoding to enable the spelling out of ASCII-based string tags using characters which can be strictly separated from ordinary text content characters in ISO10646 (or UNICODE). END_D End: Rfc: RFC2481 Title: A Proposal to add Explicit Congestion Notification (ECN) to IP Authors: K. Ramakrishnan, S. Floyd Status: Experimental Date: 1999-01 Mailbox: kkrama@research.att.com, floyd@ee.lbl.gov Pages: 25 Characters: 64559 I-D-Tag: draft-kksjf-ecn-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2481.txt Description:: END_D This note describes a proposed addition of ECN (Explicit Congestion Notification) to IP. TCP is currently the dominant transport protocol used in the Internet. We begin by describing TCP's use of packet drops as an indication of congestion. Next we argue that with the addition of active queue management (e.g., RED) to the Internet infrastructure, where routers detect congestion before the queue overflows, routers are no longer limited to packet drops as an indication of congestion. Routers could instead set a Congestion Experienced (CE) bit in the packet header of packets from ECN-capable transport protocols. We describe when the CE bit would be set in the routers, and describe what modifications would be needed to TCP to make it ECN-capable. Modifications to other transport protocols (e.g., unreliable unicast or multicast, reliable multicast, other reliable unicast transport protocols) could be considered as those protocols are developed and advance through the standards process. END_D End: Rfc: RFC2480 Title: Gateways and MIME Security Multiparts Authors: N. Freed Status: Proposed_Standard Date: 1999-01 Mailbox: ned.freed@innosoft.com Pages: 6 Characters: 11751 Keywords: Mail, Security I-D-Tag: draft-freed-gatesec-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2480.txt Description:: END_D This document examines the problems associated with use of MIME security multiparts and gateways to non-MIME environments. A set of requirements for gateway behavior are defined which provide facilities necessary to properly accomodate the transfer of security multiparts through gateways. END_D End: Rfc: RFC2479 Title: Independent Data Unit Protection Generic Security Service Application Program Interface (IDUP-GSS-API) Authors: C. Adams Status: Informational Date: 1998-12 Mailbox: cadams@entrust.com Pages: 70 Characters: 156070 I-D-Tag: draft-ietf-cat-idup-gss-11.txt Url: ftp://ftp.isi.edu/in-notes/rfc2479.txt Description:: END_D The IDUP-GSS-API extends the GSS-API [RFC-2078] for applications requiring protection of a generic data unit (such as a file or message) in a way which is independent of the protection of any other data unit and independent of any concurrent contact with designated "receivers" of the data unit. Thus, it is suitable for applications such as secure electronic mail where data needs to be protected without any on-line connection with the intended recipient(s) of that data. END_D Working-Group: Common Authentication Technology End: Rfc: RFC2478 Title: The Simple and Protected GSS-API Negotiation Mechanism Authors: E. Baize, D. Pinkas Status: Proposed_Standard Date: 1998-12 Mailbox: E.Baize@bull.com, D.Pinkas@bull.net Pages: 18 Characters: 35581 I-D-Tag: draft-ietf-cat-snego-09.txt Url: ftp://ftp.isi.edu/in-notes/rfc2478.txt Description:: END_D This document specifies a Security Negotiation Mechanism for the Generic Security Service Application Program Interface (GSS-API). END_D Working-Group: Common Authentication Technology End: Rfc: RFC2477 Title: Criteria for Evaluating Roaming Protocols Authors: B. Aboba, G. Zorn Status: Informational Date: 1999-01 Mailbox: bernarda@microsoft.com glennz@microsoft.com Pages: 12 Characters: 23530 I-D-Tag: draft-ietf-roamops-roamreq-10.txt Url: ftp://ftp.isi.edu/in-notes/rfc2477.txt Description:: END_D This document describes requirements for the provisioning of "roaming capability" for dialup Internet users. "Roaming capability" is defined as the ability to use multiple Internet service providers (ISPs), while maintaining a formal, customer-vendor relationship with only one. END_D Working-Group: Roaming Operations End: Rfc: RFC2476 Title: Message Submission Authors: R. Gellens, J. Klensin Status: Proposed_Standard Date: 1998-12 Mailbox: Randy@Qualcomm.Com, klensin@mci.net Pages: 15 Characters: 30050 I-D-Tag: draft-gellens-submit-13.txt Url: ftp://ftp.isi.edu/in-notes/rfc2476.txt Description:: END_D This memo describes a low cost, deterministic means for messages to be identified as submissions, and specifies what actions are to be taken by a submission server. END_D End: Rfc: RFC2475 Title: An Architecture for Differentiated Services Authors: S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. Weiss Status: Informational Date: 1998-12 Mailbox: slblake@torrentnet.com, black_david@emc.com, mark.carlson@sun.com, elwynd@nortel.co.uk, zhwang@bell-labs.com, wweiss@lucent.com Pages: 36 Characters: 94788 I-D-Tag: draft-ietf-diffserv-arch-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2475.txt Description:: END_D This document defines an architecture for implementing scalable service differentiation in the Internet. This architecture achieves scalability by aggregating traffic classification state which is conveyed by means of IP-layer packet marking using the DS field [DSFIELD]. Packets are classified and marked to receive a particular per-hop forwarding behavior on nodes along their path. Sophisticated classification, marking, policing, and shaping operations need only be implemented at network boundaries or hosts. Network resources are allocated to traffic streams by service provisioning policies which govern how traffic is marked and conditioned upon entry to a differentiated services-capable network, and how that traffic is forwarded within that network. A wide variety of services can be implemented on top of these building blocks. END_D Working-Group: Differentiated Services End: Rfc: RFC2474 Title: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers Authors: K. Nichols, S. Blake, F. Baker, D. Black Status: Proposed_Standard Date: 1998-12 Mailbox: kmn@cisco.com, slblake@torrentnet.com, fred@cisco.com, black_david@emc.com Pages: 20 Characters: 50576 Obsoletes: RFC1455, RFC1349 I-D-Tag: draft-ietf-diffserv-header-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2474.txt Description:: END_D This document defines the IP header field, called the DS (for differentiated services) field. In IPv4, it defines the layout of the TOS octet; in IPv6, the Traffic Class octet. In addition, a base set of packet forwarding treatments, or per-hop behaviors, is defined. END_D Working-Group: Differentiated Services End: Rfc: RFC2473 Title: Generic Packet Tunneling in IPv6 Specification Authors: A. Conta, S. Deering Status: Proposed_Standard Date: 1998-12 Mailbox: aconta@lucent.com, deering@cisco.com Pages: 36 Characters: 77956 I-D-Tag: draft-ietf-ipngwg-ipv6-tunnel-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2473.txt Description:: END_D This document defines the model and generic mechanisms for IPv6 encapsulation of Internet packets, such as IPv6 and IPv4. The model and mechanisms can be applied to other protocol packets as well, such as AppleTalk, IPX, CLNP, or others. END_D Working-Group: IPNG End: Rfc: RFC2472 Title: IP Version 6 over PPP Authors: D. Haskin, E. Allen Status: Proposed_Standard Date: 1998-12 Mailbox: dhaskin@baynetworks.com, eallen@baynetworks.com Pages: 14 Characters: 29696 Obsoletes: RFC2023 I-D-Tag: draft-ietf-ipngwg-ipv6-over-ppp-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2472.txt Description:: END_D This document defines the method for transmission of IP Version 6 [2] packets over PPP links as well as the Network Control Protocol (NCP) for establishing and configuring the IPv6 over PPP. It also specifies the method of forming IPv6 link-local addresses on PPP links. END_D Working-Group: IPNG End: Rfc: RFC2471 Title: IPv6 Testing Address Allocation Authors: R. Hinden, R. Fink, J. Postel (deceased) Status: Experimental Date: 1998-12 Mailbox: hinden@ipsilon.com, rlfink@lbl.gov Pages: 5 Characters: 8031 Obsoletes: RFC1897 I-D-Tag: draft-ietf-ipngwg-testv2-addralloc-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2471.txt Description:: END_D This document describes an allocation plan for IPv6 addresses to be used in testing IPv6 prototype software. These addresses are temporary and will be reclaimed in the future. Any IPv6 system using these addresses will have to renumber at some time in the future. These addresses will not to be routable in the Internet other than for IPv6 testing. END_D Working-Group: IPNG End: Rfc: RFC2470 Title: Transmission of IPv6 Packets over Token Ring Networks Authors: M. Crawford, T. Narten, S. Thomas Status: Proposed_Standard Date: 1998-12 Mailbox: crawdad@fnal.gov, narten@raleigh.ibm.com, stephen.thomas@transnexus.com Pages: 11 Characters: 21677 I-D-Tag: draft-ietf-ipngwg-trans-tokenring-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2470.txt Description:: END_D This memo specifies the MTU and frame format for transmission of IPv6 packets on Token Ring networks. It also specifies the method of forming IPv6 link-local addresses on Token Ring networks and the content of the Source/Target Link-layer Address option used the Router Solicitation, Router Advertisement, Redirect, Neighbor Solicitation and Neighbor Advertisement messages when those messages are transmitted on a Token Ring network. END_D Working-Group: IPNG End: Rfc: RFC2469 Title: A Caution On The Canonical Ordering Of Link-Layer Addresses Authors: T. Narten, C. Burton Status: Informational Date: 1998-12 Mailbox: narten@raleigh.ibm.com, burton@rtp.vnet.ibm.com Pages: 5 Characters: 9948 I-D-Tag: draft-narten-canonical-ordering-00.txt Url: ftp://ftp.isi.edu/in-notes/rfc2469.txt Description:: END_D Protocols such as ARP and Neighbor Discovery have data fields that contain link-layer addresses. In order to interoperate properly, a sender setting such a field must insure that the receiver extracts those bits and interprets them correctly. In most cases, such fields must be in "canonical form". Unfortunately, not all LAN adaptors are consistent in their use of canonical form, and implementations may need to explicitly bit swap individual bytes in order to obtain the correct format. This document provides information to implementors to help them avoid the pitfall of using non-canonical forms when canonical forms are required. END_D End: Rfc: RFC2468 Title: I REMEMBER IANA Authors: V. Cerf Status: Informational Date: 1998-10 Mailbox: vcerf@mci.net Pages: 4 Characters: 8543 Url: ftp://ftp.isi.edu/in-notes/rfc2468.txt Description:: END_D Jon, our beloved IANA, is gone. Even as I write these words I cannot quite grasp this stark fact. We had almost lost him once before in 1991. Surely we knew he was at risk as are we all. But he had been our rock, the foundation on which our every web search and email was built, always there to mediate the random dispute, to remind us when our documentation did not do justice to its subject, to make difficult decisions with apparent ease, and to consult when careful consideration was needed. We will survive our loss and we will remember. He has left a monumental legacy for all Internauts to contemplate. Steadfast service for decades, moving when others seemed paralyzed, always finding the right course in a complex minefield of technical and sometimes political obstacles. END_D End: Rfc: RFC2467 Title: Transmission of IPv6 Packets over FDDI Networks Authors: M. Crawford Status: Proposed_Standard Date: 1998-12 Mailbox: crawdad@fnal.gov Pages: 9 Characters: 16028 Obsoletes: RFC2019 I-D-Tag: draft-ietf-ipngwg-trans-fddi-net-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2467.txt Description:: END_D This document specifies the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on FDDI networks. It also specifies the content of the Source/Target Link-layer Address option used in Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and Redirect messages when those messages are transmitted on an FDDI network. END_D Working-Group: IPNG End: Rfc: RFC2466 Title: Management Information Base for IP Version 6: ICMPv6 Group Authors: D. Haskin, S. Onishi Status: Proposed_Standard Date: 1998-12 Mailbox: dhaskin@baynetworks.com, sonishi@baynetworks.com Pages: 16 Characters: 27547 I-D-Tag: draft-ietf-ipngwg-ipv6-icmp-mib-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2466.txt Description:: END_D This document is one in the series of documents that define various MIB object groups for IPv6. Specifically, the ICMPv6 group is defined in this document. END_D Working-Group: IPNG End: Rfc: RFC2465 Title: Management Information Base for IP Version 6: Textual Conventions and General Group Authors: D. Haskin, S. Onishi Status: Proposed_Standard Date: 1998-12 Mailbox: dhaskin@baynetworks.com, sonishi@baynetworks.com Pages: 38 Characters: 77339 I-D-Tag: draft-ietf-ipngwg-ipv6-mib-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2465.txt Description:: END_D This document is one in the series of documents that provide MIB definitions for for IP Version 6. Specifically, the IPv6 MIB textual conventions as well as the IPv6 MIB General group is defined in this document. END_D Working-Group: IPNG End: Rfc: RFC2464 Title: Transmission of IPv6 Packets over Ethernet Networks Authors: M. Crawford Status: Proposed_Standard Date: 1998-12 Mailbox: crawdad@fnal.gov Pages: 7 Characters: 12725 Obsoletes: RFC1972 I-D-Tag: draft-ietf-ipngwg-trans-ethernet-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2464.txt Description:: END_D This document specifies the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on Ethernet networks. It also specifies the content of the Source/Target Link-layer Address option used in Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and Redirect messages when those messages are transmitted on an Ethernet. END_D Working-Group: IPNG End: Rfc: RFC2463 Title: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification Authors: A. Conta, S. Deering Status: Draft_Standard Date: 1998-12 Mailbox: aconta@lucent.com, deering@cisco.com Pages: 18 Characters: 34190 Obsoletes: RFC1885 I-D-Tag: draft-ietf-ipngwg-icmp-v2-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2463.txt Description:: END_D This document specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). END_D Working-Group: IPNG End: Rfc: RFC2462 Title: IPv6 Stateless Address Autoconfiguration Authors: S. Thomson, T. Narten Status: Draft_Standard Date: 1998-12 Mailbox: set@thumper.bellcore.com, narten@raleigh.ibm.com Pages: 25 Characters: 61210 Obsoletes: RFC1971 I-D-Tag: draft-ietf-ipngwg-addrconf-v2-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2462.txt Keywords: IPaddress Description:: END_D This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes creating a link-local address and verifying its uniqueness on a link, determining what information should be autoconfigured (addresses, other information, or both), and in the case of addresses, whether they should be obtained through the stateless mechanism, the stateful mechanism, or both. This document defines the process for generating a link-local address, the process for generating site-local and global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure. The details of autoconfiguration using the stateful protocol are specified elsewhere. END_D Working-Group: IPNG End: Rfc: RFC2461 Title: Neighbor Discovery for IP Version 6 (IPv6) Authors: T. Narten, E. Nordmark, W. Simpson Status: Draft_Standard Date: 1998-12 Mailbox: narten@raleigh.ibm.com, nordmark@sun.com, bsimpson@MorningStar.com Pages: 93 Characters: 222516 Obsoletes: RFC1970 I-D-Tag: draft-ietf-ipngwg-discovery-v2-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2461.txt Description:: END_D This document specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers and to maintain reachability information about the paths to active neighbors. END_D Working-Group: IPNG End: Rfc: RFC2460 Title: Internet Protocol, Version 6 (IPv6) Specification Authors: S. Deering, R. Hinden Status: Draft_Standard Date: 1998-12 Mailbox: deering@cisco.com, hinden@iprg.nokia.com Pages: 37 Characters: 85890 Obsoletes: RFC1883 I-D-Tag: draft-ietf-ipngwg-ipv6-spec-v2-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2460.txt Description:: END_D This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. END_D Working-Group: IPNG End: Rfc: RFC2459 Title: Internet X.509 Public Key Infrastructure Certificate and CRL Profile Authors: R. Housley, W. Ford, W. Polk, D. Solo Status: Proposed_Standard Date: 1999-01 Mailbox: housley@spyrus.co, wford@verisign.com, wpolk@nist.gov, david.solo@citicorp.com Pages: 129 Characters: 278438 I-D-Tag: draft-ietf-pkix-ipki-part1-11.txt Url: ftp://ftp.isi.edu/in-notes/rfc2459.txt Description:: END_D This memo profiles the X.509 v3 certificate and X.509 v2 CRL for use in the Internet. An overview of the approach and model are provided as an introduction. The X.509 v3 certificate format is described in detail, with additional information regarding the format and semantics of Internet name forms (e.g., IP addresses). Standard certificate extensions are described and one new Internet-specific extension is defined. A required set of certificate extensions is specified. The X.509 v2 CRL format is described and a required extension set is defined as well. An algorithm for X.509 certificate path validation is described. Supplemental information is provided describing the format of public keys and digital signatures in X.509 certificates for common Internet public key encryption algorithms (i.e., RSA, DSA, and Diffie-Hellman). ASN.1 modules and examples are provided in the appendices END_D Working-Group: Public-Key Infrastructure (X.509) End: Rfc: RFC2458 Title: Toward the PSTN/Internet Inter-Networking --Pre-PINT Implementations Authors: H. Lu, M. Krishnaswamy, L. Conroy, S. Bellovin, F. Burg, A. DeSimone, K. Tewani, P. Davidson, H. Schulzrinne, K. Vishwanathan Status: Informational Date: 1998-11 Mailbox: hui-lan.lu@bell-labs.com, murali@bell-labs.com, lwc@roke.co.uk, smb@research.att.com, fburg@hogpb.att.com, tds@att.com, tewani@att.com, pauldav@nortel.ca, schulzrinne@cs.columbia.edu, kumar@isochrone.com Pages: 60 Characters: 139100 I-D-Tag: draft-ietf-pint-pre-implement-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2458.txt Description:: END_D This document contains the information relevant to the development of the inter-networking interfaces underway in the Public Switched Telephone Network (PSTN)/Internet Inter-Networking (PINT) Working Group. It addresses technologies, architectures, and several (but by no means all) existing pre-PINT implementations of the arrangements through which Internet applications can request and enrich PSTN telecommunications services. The common denominator of the enriched services (a.k.a. PINT services) is that they combine the Internet and PSTN services in such a way that the Internet is used for non-voice interactions, while the voice (and fax) are carried entirely over the PSTN. One key observation is that the pre-PINT implementations, being developed independently, do not inter-operate. It is a task of the PINT Working Group to define the inter-networking interfaces that will support inter-operation of the future implementations of PINT services. END_D Working-Group: PSTN and Internet Internetworking End: Rfc: RFC2457 Title: Definitions of Managed Objects for Extended Border Node Authors: B. Clouston, B. Moore Status: Proposed_Standard Date: 1998-11 Mailbox: clouston@cisco.com, remoore@us.ibm.com Pages: 28 Characters: 54380 I-D-Tag: draft-ietf-snanau-ebnmib-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2457.txt Description:: END_D 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 network devices with APPN (Advanced Peer-to-Peer Network) EBN (Extended Border Node) capabilities. This memo identifies managed objects for the EBN architecture. END_D Working-Group: SNA NAU Services MIB End: Rfc: RFC2456 Title: Definitions of Managed Objects for APPN TRAPS Authors: B. Clouston, B. Moore Status: Proposed_Standard Date: 1998-11 Mailbox: clouston@cisco.com, remoore@us.ibm.com Pages: 21 Characters: 44023 I-D-Tag: draft-ietf-snanau-appntrapmib-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2456.txt Description:: END_D 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 receiving notifications from network devices with APPN (Advanced Peer-to-Peer Network) and DLUR (Dependent LU Requester) capabilities. This memo identifies notifications for the APPN and DLUR architecture. END_D Working-Group: SNA NAU Services MIB End: Rfc: RFC2455 Title: Definitions of Managed Objects for APPN Authors: B. Clouston, B. Moore Status: Proposed_Standard Date: 1998-11 Mailbox: clouston@cisco.com, remoore@us.ibm.com Pages: 140 Characters: 251061 Obsoletes: RFC2155 I-D-Tag: draft-ietf-snanau-appnmib-v2-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2455.txt Description:: END_D 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 network devices with APPN (Advanced Peer-to-Peer Networking) capabilities. This memo identifies managed objects for the APPN protocol. END_D Working-Group: SNA NAU Services MIB End: Rfc: RFC2454 Title: IP Version 6 Management Information Base for the User Datagram Protocol Authors: M. Daniele Status: Proposed_Standard Date: 1998-12 Mailbox: daniele@zk3.dec.com Pages: 9 Characters: 15862 I-D-Tag: draft-ietf-ipngwg-ipv6-udp-mib-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2454.txt Description:: END_D This document is one in the series of documents that define various MIB objects for IPv6. Specifically, this document is the MIB module which defines managed objects for implementations of the User Datagram Protocol (UDP) over IP Version 6 (IPv6). END_D Working-Group: IPNG End: Rfc: RFC2453 Title: RIP Version 2 Authors: G. Malkin Status: Standard Date: 1998-11 Mailbox: gmalkin@baynetworks.com Pages: 39 Characters: 98462 Obsoletes: RFC1723, RFC1388 I-D-Tag: draft-ietf-ripv2-protocol-v2-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2453.txt Description:: END_D This document specifies an extension of the Routing Information Protocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP messages and to add a measure of security. END_D Working-Group: RIP Version II End: Rfc: RFC2452 Title: IP Version 6 Management Information Base for the Transmission Control Protocol Authors: M. Daniele Status: Proposed_Standard Date: 1998-12 Mailbox: daniele@zk3.dec.com Pages: 10 Characters: 19070 I-D-Tag: draft-ietf-ipngwg-ipv6-tcp-mib-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2452.txt Description:: END_D This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in IPv6-based internets. END_D Working-Group: IPNG End: Rfc: RFC2451 Title: The ESP CBC-Mode Cipher Algorithms Authors: R. Pereira, R. Adams Status: Proposed_Standard Date: 1998-11 Mailbox: 14 Pages: rpereira@timestep.com, adams@cisco.com Characters: 26400 Keywords: Security I-D-Tag: draft-ietf-ipsec-ciph-cbc-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2451.txt Description:: END_D This document describes how to use CBC-mode cipher algorithms with the IPSec ESP (Encapsulating Security Payload) Protocol. It not only clearly states how to use certain cipher algorithms, but also how to use all CBC-mode cipher algorithms. END_D Working-Group: IP Security Protocol End: Rfc: RFC2450 Title: Proposed TLA and NLA Assignment Rules Authors: R. Hinden Status: Informational Date: 1998-12 Mailbox: hinden@iprg.nokia.com Pages: 11 Characters: 24484 I-D-Tag: draft-ietf-ipngwg-tla-assignment-05.txt Url: ftp://ftp.isi.edu/in-notes/rfc2450.txt Description:: END_D This document proposes rules for Top-Level Aggregation Identifiers (TLA ID) and Next-Level Aggregation Identifiers (NLA ID) as defined in [AGGR]. These proposed rules apply to registries allocating TLA ID's and to organizations receiving TLA ID's. END_D Working-Group: IPNG End: Rfc: RFC2449 Title: POP3 Extension Mechanism Authors: R. Gellens, C. Newman, L. Lundblade Status: Proposed_Standard Date: 1998-11 Mailbox: randy@qualcomm.com, chris.newman@innosoft.com, lgl@qualcomm.com Pages: 19 Characters: 36017 Updates: 1939 I-D-Tag: draft-gellens-pop3ext-09.txt Url: ftp://ftp.isi.edu/in-notes/rfc2449.txt Description:: END_D This memo updates RFC 1939 [POP3] to define a mechanism to announce support for optional commands, extensions, and unconditional server behavior. Included is an initial set of currently deployed capabilities which vary between server implementations, and several new capabilities (SASL, RESP-CODES, LOGIN-DELAY, PIPELINING, EXPIRE and IMPLEMENTATION). This document also extends POP3 error messages so that machine parsable codes can be provided to the client. An initial set of response codes is included. In addition, an [ABNF] specification of POP3 commands and responses is defined. END_D End: Rfc: RFC2448 Title: AT&T's Error Resilient Video Transmission Technique Authors: M. Civanlar, G. Cash, B. Haskell Status: Informational Date: 1998-11 Mailbox: civanlar@research.att.com, glenn@research.att.com, bgh@research.att.com Pages: 7 Characters: 14655 I-D-Tag: draft-civanlar-hplp-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2448.txt Description:: END_D This document describes a set of techniques for packet loss resilient transmission of compressed video bitstreams based on reliable delivery of their vital information-carrying segments. The described techniques can be used over packet networks without packet prioritization. These techniques are related to AT&T/Lucent patents [1, 2]. END_D End: Rfc: RFC2447 Title: iCalendar Message-Based Interoperability Protocol (iMIP) Authors: F. Dawson, S. Mansour, S. Silverberg Status: Proposed_Standard Date: 1998-11 Mailbox: Frank_Dawson@Lotus.com, sman@netscape.com, stevesil@Microsoft.com Pages: 18 Keywords: Calendar Characters: 33480 I-D-Tag: draft-ietf-calsch-imip-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2447.txt Description:: END_D This document, [iMIP], specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model [iCAL] are composed using constructs from [RFC-822], [RFC-2045], [RFC-2046], [RFC-2047], [RFC-2048] and [RFC-2049]. END_D Working-Group: Calendaring and Scheduling End: Rfc: RFC2446 Title: iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries Authors: S. Silverberg, S. Mansour, F. Dawson, R. Hopson Status: Proposed_Standard Date: 1998-11 Mailbox: stevesil@Microsoft.com, sman@netscape.com, Frank_Dawson@Lotus.com, rhopson@on.com Pages: 109 Keywords: Calendar Characters: 225964 I-D-Tag: draft-ietf-calsch-itip-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2446.txt Description:: END_D This document specifies how calendaring systems use iCalendar objects to interoperate with other calendar systems. It does so in a general way so as to allow multiple methods of communication between systems. Subsequent documents specify interoperable methods of communications between systems that use this protocol. END_D Working-Group: Calendaring and Scheduling End: Rfc: RFC2445 Title: Internet Calendaring and Scheduling Core Object Specification (iCalendar) Authors: F. Dawson, D. Stenerson Status: Proposed_Standard Date: 1998-11 Mailbox: Frank_Dawson@Lotus.com, deriks@Microsoft.com Pages: 148 Characters: 291838 Keywords: Calendar I-D-Tag: draft-ietf-calsch-ical-12.txt Url: ftp://ftp.isi.edu/in-notes/rfc2445.txt Description:: END_D There is a clear need to provide and deploy interoperable calendaring and scheduling services for the Internet. Current group scheduling and Personal Information Management (PIM) products are being extended for use across the Internet, today, in proprietary ways. This memo has been defined to provide the definition of a common format for openly exchanging calendaring and scheduling information across the Internet. END_D Working-Group: Calendaring and Scheduling End: Rfc: RFC2444 Title: The One-Time-Password SASL Mechanism Authors: C. Newman Status: Proposed_Standard Date: 1998-10 Mailbox: chris.newman@innosoft.com Pages: 7 Characters: 13408 Updates: RFC2222 Keywords: Security I-D-Tag: draft-ietf-otp-sasl-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2444.txt Description:: END_D OTP [OTP] provides a useful authentication mechanism for situations where there is limited client or server trust. Currently, OTP is added to protocols in an ad-hoc fashion with heuristic parsing. This specification defines an OTP SASL [SASL] mechanism so it can be easily and formally integrated into many application protocols. END_D Working-Group: One Time Password Authentication End: Rfc: RFC2443 Title: A Distributed MARS Service Using SCSP Authors: J. Luciani, A. Gallo Status: Experimental Date: 1998-11 Mailbox: luciani@baynetworks.com, gallo@raleigh.ibm.com Pages: 18 Characters: 41451 I-D-Tag: draft-ietf-ion-scsp-mars-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2443.txt Description:: END_D This document describes a method for distributing a MARS service within a LIS[1]. This method uses the Server Cache Synchronization Protocol (SCSP)[2] to synchronize the MARS Server databases within a LIS. When SCSP is used to synchronize the caches of MARS Servers in a LIS, the LIS defines the boundary of an SCSP Server Group (SG). END_D Working-Group: Internetworking over NBMA End: Rfc: RFC2442 Title: The Batch SMTP Media Type Authors: N. Freed, D. Newman, J. Belissen, M. Hoy Status: Informational Date: 1998-11 Mailbox: ned.freed@innosoft.com, dan.newman@innosoft.com, jacques.belissent@eng.sun.com, mark.hoy@mainbrace.com Pages: 9 Characters: 18384 I-D-Tag: draft-freed-bsmtp-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2442.txt Keywords: SMTP, Mail Description:: END_D This document defines a MIME content type suitable for tunneling an ESMTP [RFC-821, RFC-1869] transaction through any MIME-capable transport. This type can be used for a variety of purposes, including: Extending end-to-end MIME-based security services (e.g., [RFC-1847]) to cover message envelope information as well as message content. Making it possible to use specific SMTP extensions such as NOTARY [RFC-1891] over unextended SMTP transport infrastructure. Enabling the transfer of multiple separate messages in a single transactional unit. END_D End: Rfc: RFC2441 Title: Working with Jon, Tribute delivered at UCLA, October 30, 1998 Authors: D. Cohen Status: Informational Date: 1998-11 Mailbox: cohen@myri.com Pages: 6 Characters: 11992 I-D-Tag: None Url: ftp://ftp.isi.edu/in-notes/rfc2441.txt Description:: END_D A tribute by Danny Cohen to long-time friend and peer, Jon Postel. END_D End: Rfc: RFC2440 Title: OpenPGP Message Format Authors: J. Callas, L. Donnerhacke, H. Finney, R. Thayer Status: Proposed_Standard Date: 1998-11 Mailbox: jon@pgp.com, lutz@iks-jena.de, hal@pgp.com, rodney@unitran.com Pages: 65 Keywords: Security,Mail Characters: 141371 I-D-Tag: draft-ietf-openpgp-formats-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2440.txt Description:: END_D This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. It is not a step-by-step cookbook for writing an application. It describes only the format and methods needed to read, check, generate, and write conforming packets crossing any network. It does not deal with storage and implementation questions. It does, however, discuss implementation issues necessary to avoid security flaws. END_D Working-Group: An Open Specification for Pretty Good Privacy End: Rfc: RFC2439 Title: BGP Route Flap Damping Authors: C. Villamizar, R. Chandra, R. Govindan Status: Proposed_Standard Date: 1998-11 Mailbox: curtis@ans.net, rchandra@cisco.com, govindan@isi.edu Pages: 37 Characters: 86376 I-D-Tag: draft-ietf-idr-route-damp-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2439.txt Description:: END_D A usage of the BGP routing protocol is described which is capable of reducing the routing traffic passed on to routing peers and therefore the load on these peers without adversely affecting route convergence time for relatively stable routes. This technique has been implemented in commercial products supporting BGP. The technique is also applicable to IDRP. END_D Working-Group: Inter-Domain Routing End: Rfc: RFC2438 Title: Advancement of MIB specifications on the IETF Standards Track Authors: M. O'Dell, H. Alvestrand, B. Wijnen, S. Bradner Status: Best_Current_Practice Date: 1998-10 Mailbox: mo@uu.net, Harald.Alvestrand@maxware.no, wijnen@vnet.ibm.com, sob@harvard.edu Pages: 7 Characters: 13633 I-D-Tag: draft-iesg-odell-mibtest-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2438.txt Description:: END_D The Internet Standards Process [1] requires that all IETF Standards Track specifications must have "multiple, independent, and interoperable implementations" before they can be advanced beyond Proposed Standard status. This document specifies the process which the IESG will use to determine if a MIB specification document meets these requirements. It also discusses the rationale for this process. END_D End: Rfc: RFC2437 Title: PKCS #1: RSA Cryptography Specifications Version 2.0 Authors: B. Kaliski, J. Staddon Status: Informational Date: 1998-10 Mailbox: burt@rsa.com, jstaddon@rsa.com Pages: 39 Characters: 73529 Obsoletes: RFC2313 I-D-Tag: draft-kaliski-pkcs-pkcs1v2-01.txt Url: ftp://ftp.isi.edu/in-notes/rfc2437.txt Keywords: Security Description:: END_D This document provides recommendations for the implementation of public-key cryptography based on the RSA algorithm. END_D End: Rfc: RFC2436 Title: Collaboration between ISOC/IETF and ITU-T Authors: R. Brett, S. Bradner, G. Parsons Status: Informational Date: 1998-10 Mailbox: rfbrett@nortel.ca, sob@harvard.edu, Glenn.Parsons@Nortel.ca Pages: 14 Characters: 31154 I-D-Tag: draft-itu-isoc-00.txt Url: ftp://ftp.isi.edu/in-notes/rfc2436.This Description:: END_D This document describes the collaboration process between the ITU-T and ISOC/IETF. The process was documented by ITU-T at its TSAG (Telecommunication Standardization Advisory Group) meeting in September 1998. All participants of this meeting (including Study Group chairmen and the ISOC Vice President for Standards) assisted in the creation of this document. Subsequently, it was sent to all ITU-T Study Groups and ISOC/IETF to ensure that everyone was aware of the process. Feedback is requested by the next meeting of TSAG in April 1999. This document is identical to the document produced by TSAG. END_D End: Rfc: RFC2435 Title: RTP Payload Format for JPEG-compressed Video Authors: L. Berc, W. Fenner, R. Frederick, S. McCanne, P. Stewart Status: Proposed_Standard Date: 1998-10 Mailbox: berc@pa.dec.com, fenner@parc.xerox.com, frederick@parc.xerox.com, mccanne@cs.berkeley.edu, stewart@parc.xerox.com Pages: 27 Characters: 54173 Obsoletes: RFC2035 I-D-Tag: draft-ietf-avt-jpeg-new-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2435.txt Description:: END_D This memo describes the RTP payload format for JPEG video streams. The packet format is optimized for real-time video streams where codec parameters change rarely from frame to frame. END_D Working-Group: Audio/Video Transport End: Rfc: RFC2434 Title: Guidelines for Writing an IANA Considerations Section in RFCs Authors: T. Narten, H. Alvestrand Status: Best_Current_Practice Date: 1998-10 Mailbox: narten@raleigh.ibm.com, Harald@Alvestrand.no BCP: 26 Pages: 11 Characters: 25092 I-D-Tag: draft-iesg-iana-considerations-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2434.txt Description:: END_D This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA. END_D Working-Group: Internet Engineering Steering Group End: Rfc: RFC2433 Title: Microsoft PPP CHAP Extensions Authors: G. Zorn, S. Cobb Status: Informational Date: 1998-10 Mailbox: glennz@microsoft.com, stevec@microsoft.com Pages: 20 Characters: 34502 I-D-Tag: draft-ietf-pppext-mschap-00.txt Url: ftp://ftp.isi.edu/in-notes/rfc2433.txt Description:: END_D This document describes Microsoft's PPP CHAP dialect (MS-CHAP), which extends the user authentication functionality provided on Windows networks to remote workstations. MS-CHAP is closely derived from the PPP Challenge Handshake Authentication Protocol described in RFC 1994 [2], which the reader should have at hand. END_D Working-Group: Point-to-Point Protocol Extensions End: Rfc: RFC2432 Title: Terminology for IP Multicast Benchmarking Authors: K. Dubray Status: Informational Date: 1998-10 Mailbox: kdubray@ironbridgenetworks.com Pages: 16 Characters: 29758 Url: ftp://ftp.isi.edu/in-notes/rfc2432.txt Description:: END_D The purpose of this document is to define terminology specific to the benchmarking of multicast IP forwarding devices. It builds upon the tenets set forth in RFC 1242, RFC 2285, and other IETF Benchmarking Methodology Working Group (BMWG) efforts. END_D Working-Group: Benchmarking Methodology End: Rfc: RFC2431 Title: RTP Payload Format for BT.656 Video Encoding Authors: D. Tynan Status: Proposed_Standard Date: 1998-10 Mailbox: dtynan@claddagh.ie Pages: 10 Characters: 22323 Url: ftp://ftp.isi.edu/in-notes/rfc2431.txt Description:: END_D This document specifies the RTP payload format for encapsulating ITU Recommendation BT.656-3 video streams in the Real-Time Transport Protocol (RTP). END_D Working-Group: Audio/Video Transport End: Rfc: RFC2430 Title: A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) Authors: T. Li, Y. Rekhter Status: Informational Date: 1998-10 Mailbox: tli@juniper.net, yakov@cisco.com Pages: 16 Characters: 40148 Url: ftp://ftp.isi.edu/in-notes/rfc2430.txt Description:: END_D This document describes the Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) for Internet Service Providers (ISPs). END_D End: Rfc: RFC2429 Title: RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+) Authors: C. Bormann, L. Cline, G. Deisher, T. Gardos, C. Maciocco, D. Newell, J. Ott, G. Sullivan, S. Wenger, C. Zhu Status: Proposed_Standard Date: 1998-10 Mailbox: cabo@tzi.org, lscline@jf.intel.com, gim.l.deisher@intel.com, thomas.r.gardos@intel.com, christian.maciocco@intel.com, donald.newell@intel.com, jo@tzi.org, garys@pictel.com, stewe@cs.tu-berlin.de, czhu@ix.netcom.com Pages: 17 Characters: 43166 Url: ftp://ftp.isi.edu/in-notes/rfc2429.txt Description:: END_D This document specifies an RTP payload header format applicable to the transmission of video streams generated based on the 1998 version of ITU-T Recommendation H.263. END_D Working-Group: Audio/Video Transport End: Rfc: RFC2428 Title: FTP Extensions for IPv6 and NATs Authors: M. Allman, S. Ostermann, C. Metz Status: Proposed_Standard Date: 1998-09 Mailbox: mallman@lerc.nasa.gov, ostermann@cs.ohiou.edu, cmetz@inner.net Pages: 8 Characters: 16028 Url: ftp://ftp.isi.edu/in-notes/rfc2428.txt Description:: END_D The specification for the File Transfer Protocol assumes that the underlying network protocol uses a 32-bit network address (specifically IP version 4). With the deployment of version 6 of the Internet Protocol, network addresses will no longer be 32-bits. This paper specifies extensions to FTP that will allow the protocol to work over IPv4 and IPv6. In addition, the framework defined can support additional network protocols in the future. END_D Working-Group: Extensions to FTP End: Rfc: RFC2427 Title: Multiprotocol Interconnect over Frame Relay Authors: C. Brown, A. Malis Status: Standard Date: 1998-09 Mailbox: cbrown@juno.com, malis@ascend.com Pages: 34 Characters: 74671 Obsoletes: RFC1490, RFC1294 Url: ftp://ftp.isi.edu/in-notes/rfc2427.txt Description:: END_D This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2426 Title: vCard MIME Directory Profile Authors: F. Dawson, T. Howes Status: Proposed_Standard Date: 1998-09 Mailbox: frank_dawson@lotus.com, howes@netscape.com Pages: 42 Characters: 74646 Url: ftp://ftp.isi.edu/in-notes/rfc2426.txt Description:: END_D This memo defines the profile of the MIME Content-Type [MIME-DIR] for directory information for a white-pages person object, based on a vCard electronic business card. The profile definition is independent of any particular directory service or protocol. The profile is defined for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). The directory information used by this profile is based on the attributes for the person object defined in the X.520 and X.521 directory services recommendations. The profile also provides the method for including a [VCARD] representation of a white-pages directory entry within the MIME Content-Type defined by the [MIME-DIR] document. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2425 Title: A MIME Content-Type for Directory Information Authors: T. Howes, M. Smith, F. Dawson Status: Proposed_Standard Date: 1998-09 Mailbox: howes@netscape.com, mcs@netscape.com, frank_dawson@lotus.com Pages: 33 Characters: 64478 Url: ftp://ftp.isi.edu/in-notes/rfc2425.txt Description:: END_D This document defines a MIME Content-Type for holding directory information. The definition is independent of any particular directory service or protocol. The text/directory Content-Type is defined for holding a variety of directory information, for example, name, or email address, or logo. The text/directory Content-Type can also be used as the root body part in a multipart/related Content-Type for handling more complicated situations, especially those in which non-textual information that already has a natural MIME representation, for example, a photograph or sound, is to be represented. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2424 Title: Content Duration MIME Header Definition Authors: G. Vaudreuil, G. Parsons Status: Proposed_Standard Date: 1998-09 Mailbox: Glenn.Parsons@Nortel.ca, GregV@Lucent.Com Pages: 4 Characters: 7116 Url: ftp://ftp.isi.edu/in-notes/rfc2424.txt Description:: END_D This document describes the MIME header Content-Duration that is intended for use with any timed media content (typically audio/* or video/*). END_D End: Rfc: RFC2423 Title: VPIM Voice Message MIME Sub-type Registration Authors: G. Vaudreuil, G. Parsons Status: Proposed_Standard Date: 1998-09 Mailbox: Glenn.Parsons@Nortel.ca, GregV@Lucent.Com Pages: 6 Characters: 10729 Obsoletes: RFC1911 Url: ftp://ftp.isi.edu/in-notes/rfc2423.txt Description:: END_D This document describes the registration of the MIME sub-type multipart/voice-message for use with the Voice Profile for Internet Mail (VPIM). A full description of usage can be found in the VPIM v2 specification. END_D End: Rfc: RFC2422 Title: Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration Authors: G. Vaudreuil, G. Parsons Status: Proposed_Standard Date: 1998-09 Mailbox: Glenn.Parsons@Nortel.ca, GregV@Lucent.Com Pages: 6 Characters: 10157 Obsoletes: RFC1911 Url: ftp://ftp.isi.edu/in-notes/rfc2422.txt Description:: END_D This document describes the registration of the MIME sub-type audio/32KADPCM for toll quality audio. This audio encoding is defined by the ITU-T in Recommendation G.726. END_D End: Rfc: RFC2421 Title: Voice Profile for Internet Mail - version 2 Authors: G. Vaudreuil, G. Parsons Status: Proposed_Standard Date: 1998-09 Mailbox: Glenn.Parsons@Nortel.ca, GregV@Lucent.Com Pages: 56 Characters: 123663 Obsoletes: RFC1911 Url: ftp://ftp.isi.edu/in-notes/rfc2421.txt Description:: END_D This document profiles Internet mail for voice messaging. END_D End: Rfc: RFC2420 Title: The PPP Triple-DES Encryption Protocol (3DESE) Authors: H. Kummert Status: Proposed_Standard Date: 1998-09 Mailbox: kummert@nentec.de Pages: 8 Keywords: PPP Characters: 16729 Url: ftp://ftp.isi.edu/in-notes/rfc2420.txt Description:: END_D This document provides specific details for the use of the Triple-DES standard (3DES) for encrypting PPP encapsulated packets. END_D Working-Group: Point-to-Point Protocol Extensions End: Rfc: RFC2419 Title: The PPP DES Encryption Protocol, Version 2 (DESE-bis) Authors: K. Sklower, G. Meyer Status: Proposed_Standard Date: 1998-09 Mailbox: sklower@CS.Berkeley.EDU, gemeyer@cisco.com Pages: 12 Characters: 24414 Keywords: PPP Obsoletes: RFC1969 Url: ftp://ftp.isi.edu/in-notes/rfc2419.txt Description:: END_D This document provides specific details for the use of the DES standard for encrypting PPP encapsulated packets. END_D Working-Group: Point-to-Point Protocol Extensions End: Rfc: RFC2418 Title: IETF Working Group Guidelines and Procedures Authors: S. Bradner Status: Best_Current_Practice Date: 1998-09 Mailbox: sob@harvard.edu Pages: 26 Alias: BCP25 Characters: 62857 Obsoletes: RFC1603 Url: ftp://ftp.isi.edu/in-notes/rfc2418.txt Description:: END_D The Internet Engineering Task Force (IETF) has responsibility for developing and reviewing specifications intended as Internet Standards. IETF activities are organized into working groups (WGs). This document describes the guidelines and procedures for formation and operation of IETF working groups. It also describes the formal relationship between IETF participants WG and the Internet Engineering Steering Group (IESG) and the basic duties of IETF participants, including WG Chairs, WG participants, and IETF Area Directors. END_D Working-Group: Process for Organization of Internet Standards ONgoing End: Rfc: RFC2417 Title: Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks Authors: C. Chung, M. Greene Status: Proposed_Standard Date: 1998-09 Mailbox: chihschung@aol.com, maria@xedia.com Characters: 134862 Keywords: SNMP Obsoletes: RFC2366 Url: ftp://ftp.isi.edu/in-notes/rfc2417.txt Description:: END_D 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 managed objects for IP hosts and routers that use a Multicast Address Resolution Server (MARS) to support IP multicast over ATM, as described in 'Support for Multicast over UNI 3.0/3.1 based ATM Networks'. This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. END_D End: Rfc: RFC2416 Title: When TCP Starts Up With Four Packets Into Only Three Buffers Authors: T. Shepard, C. Partridge Status: Informational Date: 1998-09 Mailbox: shep@alum.mit.edu, craig@bbn.com Pages: 7 Characters: 12663 Url: ftp://ftp.isi.edu/in-notes/rfc2416.txt Description:: END_D This memo is to document a simple experiment. The experiment showed that in the case of a TCP receiver behind a 9600 bps modem link at the edge of a fast Internet where there are only 3 buffers before the modem (and the fourth packet of a four-packet start will surely be dropped), no significant degradation in performance is experienced by a TCP sending with a four-packet start when compared with a normal slow start (which starts with just one packet). END_D Working-Group: TCP Implementation End: Rfc: RFC2415 Title: Simulation Studies of Increased Initial TCP Window Size Authors: K. Poduri, K. Nichols Status: Informational Date: 1998-09 Mailbox: kpoduri@Baynetworks.com, knichols@baynetworks.com Pages: 11 Characters: 24205 Url: ftp://ftp.isi.edu/in-notes/rfc2415.txt Description:: END_D An increase in the permissible initial window size of a TCP connection, from one segment to three or four segments, has been under discussion in the tcp-impl working group. This document covers some simulation studies of the effects of increasing the initial window size of TCP. Both long-lived TCP connections (file transfers) and short-lived web-browsing style connections were modeled. The simulations were performed using the publicly available ns-2 simulator and our custom models and files are also available. END_D Working-Group: TCP Implementation End: Rfc: RFC2414 Title: Increasing TCP's Initial Window Authors: M. Allman, S. Floyd, C. Partridge Status: Experimental Date: 1998-09 Mailbox: mallman@lerc.nasa.gov, floyd@ee.lbl.gov, craig@bbn.com Pages: 14 Characters: 32019 Url: ftp://ftp.isi.edu/in-notes/rfc2414.txt Description:: END_D This document specifies an increase in the permitted initial window for TCP from one segment to roughly 4K bytes. This document discusses the advantages and disadvantages of such a change, outlining experimental results that indicate the costs and benefits of such a change to TCP. END_D Working-Group: TCP Implementation End: Rfc: RFC2413 Title: Dublin Core Metadata for Resource Discovery Authors: S. Weibel, J. Kunze, C. Lagoze, M. Wolf Status: Informational Date: 1998-09 Mailbox: weibel@oclc.org, jak@ckm.ucsf.edu, lagoze@cs.cornell.edu, misha.wolf@reuters.com Pages: 8 Characters: 15501 Url: ftp://ftp.isi.edu/in-notes/rfc2413.txt Description:: END_D The Dublin Core Metadata Workshop Series began in 1995 with an invitational workshop which brought together librarians, digital library researchers, content experts, and text-markup experts to promote better discovery standards for electronic resources. The Dublin Core is a 15-element set of descriptors that has emerged from this effort in interdisciplinary and international consensus building. This is the first of a set of Informational RFCs describing the Dublin Core. Its purpose is to introduce the Dublin Core and to describe the consensus reached on the semantics of each of the 15 elements. END_D End: Rfc: RFC2412 Title: The OAKLEY Key Determination Protocol Authors: H. Orman Status: Informational Date: 1998-11 Mailbox: ho@darpa.mil Pages: 55 Characters: 118649 I-D-Tag: draft-ietf-ipsec-oakley-02.txt Keywords: Security Url: ftp://ftp.isi.edu/in-notes/rfc2412.txt Description:: END_D This document describes a protocol, named OAKLEY, by which two authenticated parties can agree on secure and secret keying material. The basic mechanism is the Diffie-Hellman key exchange algorithm. END_D Working-Group: IP Security Protocol End: Rfc: RFC2411 Title: IP Security Document Roadmap Authors: R. Thayer, N. Doraswamy, R. Glenn Status: Informational Date: 1998-11 Mailbox: rodney@sabletech.com, naganand@baynetworks.com, rob.glenn@nist.gov Pages: 11 Characters: 22796 I-D-Tag: draft-ietf-ipsec-doc-roadmap-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2411.txt Keywords: Security Description:: END_D The IPsec protocol suite is used to provide privacy and authentication services at the IP layer. Several documents are used to describe this protocol suite. The interrelationship and organization of the various documents covering the IPsec protocol are discussed here. An explanation of what to find in which document, and what to include in new Encryption Algorithm and Authentication Algorithm documents are described. END_D Working-Group: IP Security Protocol End: Rfc: RFC2410 Title: The NULL Encryption Algorithm and Its Use With IPsec Authors: R. Glenn, S. Kent Status: Proposed_Standard Date: 1998-11 Mailbox: rob.glenn@nist.gov, kent@bbn.com Pages: 6 Characters: 11239 I-D-Tag: draft-ietf-ipsec-ciph-null-01.txt Keywords: Security Url: ftp://ftp.isi.edu/in-notes/rfc2410.txt Description:: END_D This memo defines the NULL encryption algorithm and its use with the IPsec Encapsulating Security Payload (ESP). NULL does nothing to alter plaintext data. In fact, NULL, by itself, does nothing. NULL provides the means for ESP to provide authentication and integrity without confidentiality. END_D Working-Group: IP Security Protocol End: Rfc: RFC2409 Title: The Internet Key Exchange (IKE) Authors: D. Harkins, D. Carrel Status: Proposed_Standard Date: 1998-11 Mailbox: dharkins@cisco.com, carrel@ipsec.org Pages: 41 Characters: 94949 Keywords: Security I-D-Tag: draft-ietf-ipsec-isakmp-oakley-08.txt Url: ftp://ftp.isi.edu/in-notes/rfc2409.txt Description:: END_D This document describes a protocol using part of Oakley and part of SKEME in conjunction with ISAKMP to obtain authenticated keying material for use with ISAKMP, and for other security associations such as AH and ESP for the IETF IPsec DOI. END_D Working-Group: IP Security Protocol End: Rfc: RFC2408 Title: Internet Security Association and Key Management Protocol (ISAKMP) Authors: D. Maughan, M. Schertler, M. Schneider, J. Turner Status: Proposed_Standard Date: 1998-11 Mailbox: wdm@tycho.ncsc.mil, mss@tycho.ncsc.mil, mjs@terisa.com, jeff.turner@raba.com Pages: 86 Keywords: Security Characters: 209175 I-D-Tag: draft-ietf-ipsec-isakmp-10.txt Url: ftp://ftp.isi.edu/in-notes/rfc2408.txt Description:: END_D This memo describes a protocol utilizing security concepts necessary for establishing Security Associations (SA) and cryptographic keys in an Internet environment. END_D Working-Group: IP Security Protocol End: Rfc: RFC2407 Title: The Internet IP Security Domain of Interpretation for ISAKMP Authors: D. Piper Status: Proposed_Standard Date: 1998-11 Mailbox: ddp@network-alchemy.com Pages: 32 Characters: 67878 I-D-Tag: draft-ietf-ipsec-ipsec-doi-10.txt Keywords: Security Url: ftp://ftp.isi.edu/in-notes/rfc2407.txt Description:: END_D The Internet Security Association and Key Management Protocol (ISAKMP) defines a framework for security association management and cryptographic key establishment for the Internet. This framework consists of defined exchanges, payloads, and processing guidelines that occur within a given Domain of Interpretation (DOI). This document defines the Internet IP Security DOI (IPSEC DOI), which instantiates ISAKMP for use with IP when IP uses ISAKMP to negotiate security associations. END_D Working-Group: IP Security Protocol End: Rfc: RFC2406 Title: IP Encapsulating Security Payload (ESP) Authors: S. Kent, R. Atkinson Status: Proposed_Standard Date: 1998-11 Mailbox: kent@bbn.com, rja@corp.home.net Pages: 22 Characters: 54202 Obsoletes: RFC1827 Keywords: Security I-D-Tag: draft-ietf-ipsec-esp-v2-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2406.txt Description:: END_D The Encapsulating Security Payload (ESP) header is designed to provide a mix of security services in IPv4 and IPv6. END_D Working-Group: IP Security Protocol End: Rfc: RFC2405 Title: The ESP DES-CBC Cipher Algorithm With Explicit IV Authors: C. Madson, N. Doraswamy Status: Proposed_Standard Date: 1998-11 Mailbox: cmadson@cisco.com, naganand@baynetworks.com Pages: 10 Characters: 20208 Keywords: Security I-D-Tag: draft-ietf-ipsec-ciph-des-expiv-02.txt Url: ftp://ftp.isi.edu/in-notes/rfc2405.txt Description:: END_D This document describes the use of the DES Cipher algorithm in Cipher Block Chaining Mode, with an explicit IV, as a confidentiality mechanism within the context of the IPSec Encapsulating Security Payload (ESP). END_D Working-Group: IP Security Protocol End: Rfc: RFC2404 Title: The Use of HMAC-SHA-1-96 within ESP and AH Authors: C. Madson, R. Glenn Status: Proposed_Standard Date: 1998-11 Keywords: Security Mailbox: cmadson@cisco.com, rob.glenn@nist.gov Pages: 7 Characters: 13089 I-D-Tag: draft-ietf-ipsec-auth-hmac-sha196-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2404.txt Description:: END_D This memo describes the use of the HMAC algorithm [RFC-2104] in conjunction with the SHA-1 algorithm [FIPS-180-1] as an authentication mechanism within the revised IPSEC Encapsulating Security Payload [ESP] and the revised IPSEC Authentication Header [AH]. HMAC with SHA-1 provides data origin authentication and integrity protection. END_D Working-Group: IP Security Protocol End: Rfc: RFC2403 Title: The Use of HMAC-MD5-96 within ESP and AH Authors: C. Madson, R. Glenn Status: Proposed_Standard Date: 1998-11 Mailbox: cmadson@cisco.com, rob.glenn@nist.gov Pages: 7 Characters: 13578 Keywords: Security I-D-Tag: draft-ietf-ipsec-auth-hmac-md5-96-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2403.txt Description:: END_D This memo describes the use of the HMAC algorithm [RFC-2104] in conjunction with the MD5 algorithm [RFC-1321] as an authentication mechanism within the revised IPSEC Encapsulating Security Payload [ESP] and the revised IPSEC Authentication Header [AH]. HMAC with MD5 provides data origin authentication and integrity protection. END_D Working-Group: IP Security Protocol End: Rfc: RFC2402 Title: IP Authentication Header Authors: S. Kent, R. Atkinson Status: Proposed_Standard Date: 1998-11 Mailbox: kent@bbn.com, rja@corp.home.net Pages: 22 Characters: 52831 Obsoletes: RFC1826 I-D-Tag: draft-ietf-ipsec-auth-header-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2402.txt Keywords: Security Description:: END_D The IP Authentication Header (AH) is used to provide connectionless integrity and data origin authentication for IP datagrams (hereafter referred to as just "authentication"), and to provide protection against replays. END_D Working-Group: IP Security Protocol End: Rfc: RFC2401 Title: Security Architecture for the Internet Protocol Authors: S. Kent, R. Atkinson Status: Proposed_Standard Date: 1998-11 Mailbox: kent@bbn.com, rja@corp.home.net Pages: 66 Characters: 168162 Obsoletes: RFC1825 Keywords: Security I-D-Tag: draft-ietf-ipsec-arch-sec-07.txt Url: ftp://ftp.isi.edu/in-notes/rfc2401.txt Description:: END_D This memo specifies the base architecture for IPsec compliant systems. The goal of the architecture is to provide various security services for traffic at the IP layer, in both the IPv4 and IPv6 environments. This document describes the goals of such systems, their components and how they fit together with each other and into the IP environment. It also describes the security services offered by the IPsec protocols, and how these services can be employed in the IP environment. END_D Working-Group: IP Security Protocol End: Rfc: RFC2400 Title: INTERNET OFFICIAL PROTOCOL STANDARDS Authors: J. Postel, J. Reynolds Status: Standard Date: 1998-09 Mailbox: Postel@ISI.EDU, JKRey@ISI.EDU Pages: 47 Characters: 110969 Obsoletes: RFC2300, RFC2200, RFC2000, RFC1920, RFC1880, RFC1800, RFC1780, RFC1720, RFC1610, RFC1600, RFC1540, RFC1500, RFC1410, RFC1360, RFC1280, RFC1250, RFC1200, RFC1140, RFC1130, RFC1100, RFC1083 Url: ftp://ftp.isi.edu/in-notes/rfc2400.txt Description:: END_D A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally, there are pointers to references and contacts for further information. END_D Obsoleted-by: RFC2500 End: Rfc: RFC2399 Title: Request for Comments Summary Authors: A. Ramos Status: Informational Date: 1999-01 Mailbox: ramos@isi.edu Pages: 23 Characters: 45853 I-D-Tag: None Url: ftp://ftp.isi.edu/in-notes/rfc2399.txt Description:: END_D This RFC is a slightly annotated list of the 100 RFCs from RFC 2300 through RFCs 2399. This is a status report on these RFCs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. END_D End: Rfc: RFC2398 Title: Some Testing Tools for TCP Implementors Authors: S. Parker, C. Schmechel Status: Informational Date: 1998-08 Mailbox: sparker@eng.sun.com, cschmec@eng.sun.com Pages: 15 Alias: FYI33 Characters: 24107 Url: ftp://ftp.isi.edu/in-notes/rfc2398.txt Description:: END_D Available tools for testing TCP implementations are catalogued by this memo. Hopefully disseminating this information will encourage those responsible for building and maintaining TCP to make the best use of available tests. The type of testing the tool provides, the type of tests it is capable of doing, and its availability is enumerated. END_D Working-Group: TCP Implementation End: Rfc: RFC2397 Title: The "data" URL scheme Authors: L. Masinter Status: Proposed_Standard Date: 1998-08 Mailbox: masinter@parc.xerox.com Pages: 5 Characters: 9514 Url: ftp://ftp.isi.edu/in-notes/rfc2397.txt Description:: END_D A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. END_D End: Rfc: RFC2396 Title: Uniform Resource Identifiers (URI): Generic Syntax Authors: T. Berners-Lee, R. Fielding, L. Masinter Status: Draft_Standard Date: 1998-08 Mailbox: timbl@w3.org, fielding@ics.uci.edu, masinter@parc.xerox.com Pages: 39 Characters: 83639 Updates: RFC1808, RFC1738 Url: ftp://ftp.isi.edu/in-notes/rfc2396.txt Description:: END_D This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. This document does not define a generative grammar for URI; that task will be performed by the individual specifications of each URI scheme. END_D End: Rfc: RFC2395 Title: IP Payload Compression Using LZS Authors: R. Friend, R. Monsour Status: Informational Date: 1998-12 Mailbox: rfriend@hifn.com, rmonsour@hifn.com Pages: 9 Characters: 14882 I-D-Tag: draft-ietf-ippcp-lzs-04.txt Url: ftp://ftp.isi.edu/in-notes/rfc2395.txt Description:: END_D This document describes a compression method based on the LZS compression algorithm. This document defines the application of the LZS algorithm to the IP Payload Compression Protocol [IPCOMP]. END_D Working-Group: IP Payload Compression Protocol End: Rfc: RFC2394 Title: IP Payload Compression Using DEFLATE Authors: R. Pereira Status: Informational Date: 1998-12 Mailbox: rpereira@timestep.com Pages: 6 Characters: 11053 I-D-Tag: draft-ietf-ippcp-deflate-03.txt Url: ftp://ftp.isi.edu/in-notes/rfc2394.txt Description:: END_D This document describes a compression method based on the DEFLATE compression algorithm. This document defines the application of the DEFLATE algorithm to the IP Payload Compression Protocol. END_D Working-Group: IP Payload Compression Protocol End: Rfc: RFC2393 Title: IP Payload Compression Protocol (IPComp) Authors: A. Shacham, R. Monsour, R. Pereira, M. Thomas Status: Proposed_Standard Date: 1998-12 Mailbox: shacham@cisco.com, rmonsour@hifn.com, rpereira@timestep.com, matt.thomas@altavista-software.com Pages: 10 Characters: 20762 I-D-Tag: draft-ietf-ippcp-protocol-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2393.txt Description:: END_D This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. END_D Working-Group: IP Payload Compression Protocol End: Rfc: RFC2392 Title: Content-ID and Message-ID Uniform Resource Locators Authors: E. Levinson Status: Proposed_Standard Date: 1998-08 Mailbox: XIson@cnj.digex.net Pages: 6 Characters: 11141 Obsoletes: RFC2111 Url: ftp://ftp.isi.edu/in-notes/rfc2392.txt Description:: END_D The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. END_D Working-Group: MIME Encapsulation of Aggreagate HTML Documents End: Rfc: RFC2391 Title: Load Sharing using IP Network Address Translation (LSNAT) Authors: P. Srisuresh, D. Gan Status: Informationl Date: 1998-08 Mailbox: suresh@ra.lucent.com, dhg@juniper.net Pages: 18 Characters: 44884 Keywords: IPaddress Url: ftp://ftp.isi.edu/in-notes/rfc2391.txt Description:: END_D Network Address Translators (NATs) translate IP addresses in a datagram, transparent to end nodes, while routing the datagram. NATs have traditionally been been used to allow private network domains to connect to Global networks using as few as one globally unique IP address. In this document, we extend the use of NATs to offer Load share feature, where session load can be distributed across a pool of servers, instead of directing to a single server. Load sharing is beneficial to service providers and system administrators alike in grappling with scalability of servers with increasing session load. END_D End: Rfc: RFC2390 Title: Inverse Address Resolution Protocol Authors: T. Bradley, C. Brown, A. Malis Status: Draft_Standard Date: 1998-09 Mailbox: tbradley@avici.com, cbrown@juno.com, malis@ascend.com Pages: 10 Characters: 20849 Obsoletes: RFC1293 Url: ftp://ftp.isi.edu/in-notes/rfc2390.txt Description:: END_D This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. Specifically, this applies to Frame Relay stations that may have a Data Link Connection Identifier (DLCI), the Frame Relay equivalent of a hardware address, associated with an established Permanent Virtual Circuit (PVC), but do not know the protocol address of the station on the other side of this connection. It will also apply to other networks with similar circumstances. END_D Working-Group: Internetworking over NBMA End: Rfc: RFC2389 Title: Feature negotiation mechanism for the File Transfer Protocol Authors: P. Hethmon, R. Elz Status: Proposed_Standard Date: 1998-08 Mailbox: phethmon@hethmon.com, kre@munnari.OZ.AU Pages: 9 Characters: 18536 See-Also: RFC0959 Url: ftp://ftp.isi.edu/in-notes/rfc2389.txt Description:: END_D The File Transfer Protocol is, from time to time, extended with new commands, or facilities. Implementations of the FTP protocol cannot be assumed to all immediately implement all newly defined mechanisms. This document provides a mechanism by which clients of the FTP protocol can discover which new features are supported by a particular FTP server. END_D Working-Group: Extensions to FTP End: Rfc: RFC2388 Title: Returning Values from Forms: multipart/form-data Authors: L. Masinter Status: Proposed_Standard Date: 1998-08 Mailbox: masinter@parc.xerox.com Pages: 9 Characters: 16531 Url: ftp://ftp.isi.edu/in-notes/rfc2388.txt Description:: END_D This specification defines an Internet Media Type, multipart/form-data, which can be used by a wide variety of applications and transported by a wide variety of protocols as a way of returning a set of values as the result of a user filling out a form. END_D End: Rfc: RFC2387 Title: The MIME Multipart/Related Content-type Authors: E. Levinson Status: Proposed_Standard Date: 1998-08 Mailbox: XIson@cnj.digex.com Pages: 10 Characters: 18864 Obsoletes: RFC2112 Url: ftp://ftp.isi.edu/in-notes/rfc2387.txt Description:: END_D The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. END_D Working-Group: MIME Encapsulation of Aggregate HTML Documents End: Rfc: RFC2386 Title: A Framework for QoS-based Routing in the Internet Authors: E. Crawley, R. Nair, B. Rajagopalan, H. Sandick Status: Informational Date: 1998-08 Mailbox: esc@argon.com, nair@arrowpoint.com, braja@ccrl.nj.nec.com, Hsandick@baynetworks.com Pages: 37 Characters: 93459 Url: ftp://ftp.isi.edu/in-notes/rfc2386.txt Description:: END_D QoS-based routing has been recognized as a missing piece in the evolution of QoS-based service offerings in the Internet. This document describes some of the QoS-based routing issues and requirements, and proposes a framework for QoS-based routing in the Internet. This framework is based on extending the current Internet routing model of intra and interdomain routing to support QoS. END_D Working-Group: QoS Routing End: Rfc: RFC2385 Title: Protection of BGP Sessions via the TCP MD5 Signature Option Authors: A. Heffernan Status: Proposed_Standard Date: 1998-08 Mailbox: ahh@cisco.com Pages: 6 Characters: 12315 Url: ftp://ftp.isi.edu/in-notes/rfc2385.txt Description:: END_D This memo describes a TCP extension to enhance security for BGP. It defines a new TCP option for carrying an MD5 [RFC1321] digest in a TCP segment. This digest acts like a signature for that segment, incorporating information known only to the connection end points. Since BGP uses TCP as its transport, using this option in the way described in this paper significantly reduces the danger from certain security attacks on BGP. END_D End: Rfc: RFC2384 Title: POP URL Scheme Authors: R. Gellens Status: Proposed_Standard Date: 1998-08 Mailbox: Randy@Qualcomm.Com Pages: 8 Characters: 13649 Keywords: Mail Url: ftp://ftp.isi.edu/in-notes/rfc2384.txt Description:: END_D This memo defines a URL scheme for referencing a POP mailbox. END_D End: Rfc: RFC2383 Title: ST2+ over ATM Protocol Specification - UNI 3.1 Version Authors: M. Suzuki Status: Informational Date: 1998-08 Mailbox: suzuki@nal.ecl.net Pages: 50 Characters: 99889 Url: ftp://ftp.isi.edu/in-notes/rfc2383.txt Description:: END_D This document specifies an ATM-based protocol for communication between ST2+ agents. The ST2+ over ATM protocol supports the matching of one hop in an ST2+ tree-structure stream with one ATM connection. In this document, ATM is a subnet technology for the ST2+ stream. END_D End: Rfc: RFC2382 Title: A Framework for Integrated Services and RSVP over ATM Authors: E. Crawley, L. Berger, S. Berson, F. Baker, M. Borden, J. Krawczyk Status: Informational Date: 1998-08 Mailbox: esc@argon.com, lberger@fore.com, berson@isi.edu, fred@cisco.com, mborden@baynetworks.com, jj@arrowpoint.com Pages: 30 Characters: 73865 Url: ftp://ftp.isi.edu/in-notes/rfc2382.txt Description:: END_D This document outlines the issues and framework related to providing IP Integrated Services with RSVP over ATM. It provides an overall approach to the problem(s) and related issues. These issues and problems are to be addressed in further documents from the ISATM subgroup of the ISSLL working group. END_D Working-Group: Integrated Services over Specific Link Layers End: Rfc: RFC2381 Title: Interoperation of Controlled-Load Service and Guaranteed Service with ATM Authors: M. Garrett, M. Borden Status: Proposed_Standard Date: 1998-08 Mailbox: mwg@bellcore.com, mborden@baynetworks.com Pages: 43 Characters: 107299 Url: ftp://ftp.isi.edu/in-notes/rfc2381.txt Description:: END_D This document provides guidelines for mapping service classes, and traffic management features and parameters between Internet and ATM technologies. The service mappings are useful for providing effective interoperation and end-to-end Quality of Service for IP Integrated Services networks containing ATM subnetworks. END_D Working-Group: Integrated Services over Specific Link Layers End: Rfc: RFC2380 Title: RSVP over ATM Implementation Requirements Authors: L. Berger Status: Proposed_Standard Date: 1998-08 Mailbox: lberger@fore.com Pages: 14 Characters: 31234 Url: ftp://ftp.isi.edu/in-notes/rfc2380.txt Description:: END_D This memo presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). It presents requirements that ensure interoperability between multiple implementations and conformance to the RSVP and Integrated Services specifications. END_D Working-Group: Integrated Services over Specific Link Layers End: Rfc: RFC2379 Title: RSVP over ATM Implementation Guidelines Authors: L. Berger Status: Best_Current_Practice Date: 1998-08 Mailbox: lberger@fore.com Alias: BCP24 Pages: 8 Characters: 15174 Url: ftp://ftp.isi.edu/in-notes/rfc2379.txt Description:: END_D This memo presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). END_D Working-Group: Integrated Services over Specific Link Layers End: Rfc: RFC2378 Title: The CCSO Nameserver (Ph) Architecture Authors: R. Hedberg, P. Pomes Status: Informational Date: 1998-09 Mailbox: Roland.Hedberg@umdac.umu.se, ppomes@qualcomm.com Pages: 22 Characters: 38960 Url: ftp://ftp.isi.edu/in-notes/rfc2378.txt Description:: END_D This document provides a formal definition of the client-server protocol. The Ph service as specified in this document is built around an information model, a client command language and the server responses. END_D Working-Group: Integrated Directory Services End: Rfc: RFC2377 Title: Naming Plan for Internet Directory-Enabled Applications Authors: A. Grimstad, R. Huber, S. Sataluri, M. Wahl Status: Informational Date: 1998-09 Mailbox: alg@att.com, rvh@att.com, srs@lucent.com, M.Wahl@critical-angle.com Pages: 18 Characters: 38274 Keywords: LDAP Url: ftp://ftp.isi.edu/in-notes/rfc2377.txt Description:: END_D We propose a new directory naming plan that leverages the strengths of the most popular and successful Internet naming schemes for naming objects in a hierarchical directory. This plan can, we believe, by extending the X.500 approach to naming, facilitate the creation of an Internet White Pages Service (IWPS) and other directory-enabled applications by overcoming the problems encountered by those using the conventional X.500 approach. END_D Working-Group: Integrated Directory Services End: Rfc: RFC2376 Title: XML Media Types Authors: E. Whitehead, M. Murata Status: Informational Date: 1998-07 Mailbox: ejw@ics.uci.edu, murata@fxis.fujixerox.co.jp Pages: 15 Characters: 32143 Url: ftp://ftp.isi.edu/in-notes/rfc2376.txt Description:: END_D This document proposes two new media subtypes, text/xml and application/xml, for use in exchanging network entities which are conforming Extensible Markup Language (XML). XML entities are currently exchanged via the HyperText Transfer Protocol on the World Wide Web, are an integral part of the WebDAV protocol for remote web authoring, and are expected to have utility in many domains. END_D End: Rfc: RFC2375 Title: IPv6 Multicast Address Assignments Authors: R. Hinden, S. Deering Status: Informational Date: 1998-07 Mailbox: hinden@iprg.nokia.com, deering@cisco.com Pages: 8 Characters: 14304 Keywords: IPaddress Url: ftp://ftp.isi.edu/in-notes/rfc2375.txt Description:: END_D This document defines the initial assignment of IPv6 multicast addresses. It is based on the "IP Version 6 Addressing Architecture" [ADDARCH] and current IPv4 multicast address assignment found in . It adapts the IPv4 assignments that are relevant to IPv6 assignments. IPv4 assignments that were not relevant were not converted into IPv6 assignments. END_D Working-Group: IPNG End: Rfc: RFC2374 Title: An IPv6 Aggregatable Global Unicast Address Format Authors: R. Hinden, M. O'Dell, S. Deering Status: Proposed_Standard Date: 1998-07 Mailbox: hinden@iprg.nokia.com, mo@uunet.uu.net, deering@cisco.com Pages: 12 Characters: 25068 Obsoletes: RFC2073 Keywords: IPaddress Url: ftp://ftp.isi.edu/in-notes/rfc2374.txt Description:: END_D This document defines an IPv6 aggregatable global unicast address format for use in the Internet. The address format defined in this document is consistent with the IPv6 Protocol [IPV6] and the "IPv6 Addressing Architecture" [ARCH]. It is designed to facilitate scalable Internet routing. END_D Working-Group: IPNG End: Rfc: RFC2373 Title: IP Version 6 Addressing Architecture Authors: R. Hinden, S. Deering Status: Proposed_Standard Date: 1998-07 Mailbox: hinden@iprg.nokia.com, deering@cisco.com Pages: 26 Characters: 52526 Obsoletes: RFC1884 Keywords: IPaddress Url: ftp://ftp.isi.edu/in-notes/rfc2373.txt Description:: END_D This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. END_D Working-Group: IPNG End: Rfc: RFC2372 Title: Transaction Internet Protocol - Requirements and Supplemental Information Authors: K. Evans, J. Klein, J. Lyon Status: Informational Date: 1998-07 Mailbox: Keith.Evans@Tandem.Com, Johannes.Klein@Tandem.Com, JimLyon@Microsoft.Com Pages: 24 Characters: 53699 Url: ftp://ftp.isi.edu/in-notes/rfc2372.txt Description:: END_D This document describes the purpose (usage scenarios), and requirements for the Transaction Internet Protocol [1]. It is intended to help qualify the necessary features and functions of the protocol. It also provides supplemental information to aid understanding and facilitate implementation of the TIP protocol. END_D Working-Group: Transaction Internet Protocol End: Rfc: RFC2371 Title: Transaction Internet Protocol Version 3.0 Authors: J. Lyon, K. Evans, J. Klein Status: Proposed_Standard Date: 1998-07 Mailbox: JimLyon@Microsoft.Com, Keith.Evans@Tandem.Com, Johannes.Klein@Tandem.Com Pages: 31 Characters: 71399 Url: ftp://ftp.isi.edu/in-notes/rfc2371.txt Description:: END_D In many applications where different nodes cooperate on some work, there is a need to guarantee that the work happens atomically. That is, each node must reach the same conclusion as to whether the work is to be completed, even in the face of failures. This document proposes a simple, easily-implemented protocol for achieving this end. END_D Working-Group: Transaction Internet Protocol End: Rfc: RFC2370 Title: The OSPF Opaque LSA Option Authors: R. Coltun Status: Proposed_Standard Date: 1998-07 Mailbox: rcoltun@fore.com Pages: 15 Characters: 33789 See-Also: RFC2328 Url: ftp://ftp.isi.edu/in-notes/rfc2370.txt Description:: END_D This memo defines enhancements to the OSPF protocol to support a new class of link-state advertisements (LSA) called Opaque LSAs. Opaque LSAs provide a generalized mechanism to allow for the future extensibility of OSPF. Opaque LSAs consist of a standard LSA header followed by application-specific information. The information field may be used directly by OSPF or by other applications. Standard OSPF link-state database flooding mechanisms are used to distribute Opaque LSAs to all or some limited portion of the OSPF topology. END_D Working-Group: Open Shortest Path First IGP End: Rfc: RFC2369 Title: The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields Authors: G. Neufeld, J. Baer Status: Proposed_Standard Date: 1998-07 Mailbox: josh@skyweyr.com, grant@acm.org Pages: 15 Characters: 30853 Url: ftp://ftp.isi.edu/in-notes/rfc2369.txt Keywords: Mail Description:: END_D This is a proposal for additional header fields to be added to email messages sent by email distribution lists. The content of each new field is typically a URL - usually mailto [RFC2368] - which locates the relevant information or performs the command directly. MTAs generating the header fields SHOULD usually include a mailto based command, in addition to any other protocols used, in order to support users who do not have access to non-mail-based protocols. END_D End: Rfc: RFC2368 Title: The mailto URL scheme Authors: P. Hoffman, L. Masinter, J. Zawinski Status: Proposed_Standard Date: 1998-07 Mailbox: phoffman@imc.org, masinter@parc.xerox.com, jwz@netscape.com Pages: 10 Characters: 16502 Updates: RFC1738, RFC1808 Url: ftp://ftp.isi.edu/in-notes/rfc2368.txt Description:: END_D This document defines the format of Uniform Resource Locators (URL) for designating electronic mail addresses. It is one of a suite of documents which replace RFC 1738, 'Uniform Resource Locators', and RFC 1808, 'Relative Uniform Resource Locators'. The syntax of 'mailto' URLs from RFC 1738 is extended to allow creation of more RFC 822 messages by allowing the URL to express additional header and body fields. END_D End: Rfc: RFC2367 Title: PF_KEY Key Management API, Version 2 Authors: D. McDonald, C. Metz, B. Phan Status: Informational Date: 1998-07 Mailbox: danmcd@eng.sun.com, cmetz@inner.net, phan@itd.nrl.navy.mil Pages: 68 Characters: 146754 Url: ftp://ftp.isi.edu/in-notes/rfc2367.txt Keywords: Security Description:: END_D A generic key management API that can be used not only for IP Security but also for other network security services is presented in this document. Version 1 of this API was implemented inside 4.4-Lite BSD as part of the U. S. Naval Research Laboratory's freely distributable and usable IPv6 and IPsec implementation. It is documented here for the benefit of others who might also adopt and use the API, thus providing increased portability of key management applications (e.g. a manual keying application, an ISAKMP daemon, a GKMP daemon, a Photuris daemon, or a SKIP certificate discovery protocol daemon). END_D End: Rfc: RFC2366 Title: Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks Authors: C. Chung, M. Greene Status: Proposed_Standard Date: 1998-07 Mailbox: cchung@tieo.saic.com, maria@xedia.com Pages: 76 Characters: 134312 Url: ftp://ftp.isi.edu/in-notes/rfc2366.txt Keywords: SNMP Description:: END_D 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 managed objects for IP hosts and routers that use a Multicast Address Resolution Server (MARS) to support IP multicast over ATM, as described in 'Support for Multicast over UNI 3.0/3.1 based ATM Networks'. END_D Working-Group: Internetworking Over NBMA Obsoleted-by: RFC2417 End: Rfc: RFC2365 Title: Administratively Scoped IP Multicast Authors: D. Meyer Status: Best_Current_Practice Date: 1998-07 Mailbox: dmm@cisco.com Alias: BCP23 Pages: 8 Characters: 17770 Url: ftp://ftp.isi.edu/in-notes/rfc2365.txt Description:: END_D This document defines the "administratively scoped IPv4 multicast space" to be the range 239.0.0.0 to 239.255.255.255. In addition, it describes a simple set of semantics for the implementation of Administratively Scoped IP Multicast. Finally, it provides a mapping between the IPv6 multicast address classes [RFC1884] and IPv4 multicast address classes. END_D Working-Group: MBONE Deployment End: Rfc: RFC2364 Title: PPP Over AAL5 Authors: G. Gross, M. Kaycee, A. Li, A. Malis, J. Stephens Status: Proposed_Standard Date: 1998-07 Mailbox: gmgross@lucent.com, mjk@nj.paradyne.com, alin@shastanets.com, malis@ascend.com, john@cayman.com Pages: 12 Characters: 23539 Url: ftp://ftp.isi.edu/in-notes/rfc2364.txt Keywords: PPP Description:: END_D The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of ATM Adaptation Layer 5 (AAL5) for framing PPP encapsulated packets. END_D Working-Group: Point-to-Point Protocol Extensions End: Rfc: RFC2363 Title: PPP Over FUNI Authors: G. Gross, M. Kaycee, A. Li, A. Malis, J. Stephens Status: Proposed_Standard Date: 1998-07 Mailbox: gmgross@lucent.com, mjk@nj.paradyne.com, alin@shastanets.com, malis@ascend.com, john@cayman.com Pages: 12 Characters: 22576 Url: ftp://ftp.isi.edu/in-notes/rfc2363.txt Keywords: PPP Description:: END_D The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of ATM Frame User Network Interface (FUNI) for framing PPP encapsulated packets. END_D Working-Group: Point-to-Point Protocol Extensions End: Rfc: RFC2362 Title: Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification Authors: D. Estrin, D. Farinacci, A. Helmy, D. Thaler, S. Deering, M. Handley, V. Jacobson, C. Liu, P. Sharma, L. Wei Status: Experimental Date: 1998-06 Mailbox: estrin@usc.edu, dino@cisco.com, ahelmy@catarina.usc.edu, thalerd@eecs.umich.edu, deering@parc.xerox.com, m.handley@cs.ucl.ac.uk, van@ee.lbl.gov, charley@catarina.usc.edu, puneet@catarina.usc.edu, lwei@cisco.com Pages: 66 Characters: 159833 Obsoletes: RFC2117 Url: ftp://ftp.isi.edu/in-notes/rfc2362.txt Description:: END_D This document describes a protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets. We refer to the approach as Protocol Independent Multicast--Sparse Mode (PIM-SM) because it is not dependent on any particular unicast routing protocol, and because it is designed to support sparse groups. END_D Working-Group: Inter-Domain Multicast Routing End: Rfc: RFC2361 Title: WAVE and AVI Codec Registries Authors: E. Fleischman Status: Informational Date: 1998-06 Mailbox: Eric.Fleischman@PSS.Boeing.com Pages: 71 Characters: 97796 Url: ftp://ftp.isi.edu/in-notes/rfc2361.txt Description:: END_D Internet applications may reference specific codecs within the WAVE and AVI registries as follows: * video/vnd.avi; codec=XXX identifies a specific video codec (i.e., XXX) within the AVI Registry. * audio/vnd.wave; codec=YYY identifies a specific audio codec (i.e., YYY) within the WAVE Registry. Appendix A and Appendix B provides an authoritative reference for the interpretation of the required "codec" parameter. That is, the current set of audio codecs that are registered within the WAVE Registry are enumerated in Appendix A. Appendix B enumerates the current set of video codecs that have been registered to date within the AVI Registry. END_D End: Rfc: RFC2360 Title: Guide for Internet Standards Writers Authors: G. Scott, Editor Status: Best_Current_Practice Date: 1998-06 Mailbox: scottg@ftm.disa.mil Pages: 20 Alias: BCP22 Characters: 47280 Url: ftp://ftp.isi.edu/in-notes/rfc2360.txt Description:: END_D This document is a guide for Internet standard writers. It defines those characteristics that make standards coherent, unambiguous, and easy to interpret. In addition, it singles out usage believed to have led to unclear specifications, resulting in non-interoperable interpretations in the past. These guidelines are to be used with RFC 2223, "Instructions to RFC Authors". END_D Working-Group: Guide for Internet Standards Writers End: Rfc: RFC2359 Title: IMAP4 UIDPLUS extension Authors: J. Myers Status: Proposed_Standard Date: 1998-06 Mailbox: jgmyers@netscape.com Pages: 6 Characters: 10862 Url: ftp://ftp.isi.edu/in-notes/rfc2359.txt Keywords: IMAP Description:: END_D The UIDPLUS extension of the Internet Message Access Protocol [IMAP4] provides a set of features intended to reduce the amount of time and resources used by some client operations. The features in UIDPLUS are primarily intended for disconnected-use clients. END_D End: Rfc: RFC2358 Title: Definitions of Managed Objects for the Ethernet-like Interface Types Authors: J. Flick, J. Johnson Status: Proposed_Standard Date: 1998-06 Mailbox: johnf@hprnd.rose.hp.com, jeff@redbacknetworks.com Pages: 39 Characters: 87891 Obsoletes: RFC1650 Url: ftp://ftp.isi.edu/in-notes/rfc2358.txt Description:: END_D This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo obsoletes RFC 1650 "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2". This memo extends that specification by including management information useful for the management of 100 Mb/s Ethernet interfaces. END_D Working-Group: IEEE 802.3 Hub MIB End: Rfc: RFC2357 Title: IETF Criteria for Evaluating Reliable Multicast Transport and Application Protocols Authors: A. Mankin, A. Romanow, S. Bradner, V. Paxson Status: Informational Date: 1998-06 Mailbox: mankin@east.isi.edu, allyn@mci.net, sob@harvard.edu, vern@ee.lbl.gov Pages: 11 Characters: 24130 Url: ftp://ftp.isi.edu/in-notes/rfc2357.txt Description:: END_D This memo describes the procedures and criteria for reviewing reliable multicast protocols within the Transport Area (TSV) of the IETF. END_D End: Rfc: RFC2356 Title: Sun's SKIP Firewall Traversal for Mobile IP Authors: G. Montenegro, V. Gupta Status: Informational Date: 1998-06 Mailbox: gabriel.montenegro@Eng.Sun.COM, vipul.gupta@Eng.Sun.COM Pages: 24 Characters: 53198 Keywords: Security Url: ftp://ftp.isi.edu/in-notes/rfc2356.txt Description:: END_D The Mobile IP specification establishes the mechanisms that enable a mobile host to maintain and use the same IP address as it changes its point of attachment to the network. Mobility implies higher security risks than static operation, because the traffic may at times take unforeseen network paths with unknown or unpredictable security characteristics. The Mobile IP specification makes no provisions for securing data traffic. The mechanisms described in this document allow a mobile node out on a public sector of the internet to negotiate access past a SKIP firewall, and construct a secure channel into its home network. In addition to securing traffic, our mechanisms allow a mobile node to roam into regions that (1) impose ingress filtering, and (2) use a different address space. END_D Working-Group: IP Routing for Wireless/Mobile Hosts End: Rfc: RFC2355 Title: TN3270 Enhancements Authors: B. Kelly Status: Draft_Standard Date: 1998-06 Mailbox: kellywh@mail.auburn.edu Pages: 38 Characters: 89394 Obsoletes: RFC1647 Url: ftp://ftp.isi.edu/in-notes/rfc2355.txt Description:: END_D This document describes a protocol that more fully supports 3270 devices than do traditional tn3270 practices. Specifically, it defines a method of emulating both the terminal and printer members of the 3270 family of devices via Telnet; it provides for the ability of a Telnet client to request that it be assigned a specific device-name (also referred to as "LU name" or "network name"); finally, it adds support for a variety of functions such as the ATTN key, the SYSREQ key, and SNA response handling. This protocol is negotiated under the TN3270E Telnet Option, and is unrelated to the Telnet 3270 Regime Option as defined in RFC 1041. END_D Working-Group: Telnet TN3270 Enhancements End: Rfc: RFC2354 Title: Options for Repair of Streaming Media Authors: C. Perkins, O. Hodson Status: Informational Date: 1998-06 Mailbox: c.perkins@cs.ucl.ac.uk, o.hodson@cs.ucl.ac.uk Pages: 12 Characters: 28876 Url: ftp://ftp.isi.edu/in-notes/rfc2354.txt Description:: END_D This document summarizes a range of possible techniques for the repair of continuous media streams subject to packet loss. The techniques discussed include redundant transmission, retransmission, interleaving and forward error correction. The range of applicability of these techniques is noted, together with the protocol requirements and dependencies. END_D Working-Group: Audio/Video Transport End: Rfc: RFC2353 Title: APPN/HPR in IP Networks APPN Implementers' Workshop Closed Pages Document Authors: G. Dudley Status: Informational Date: 1998-05 Mailbox: dudleyg@us.ibm.com Pages: 48 Characters: 116972 Url: ftp://ftp.isi.edu/in-notes/rfc2353.txt Description:: END_D This memo defines a method with which HPR nodes can use IP networks for communication, and the enhancements to APPN required by this method. This memo also describes an option set that allows the use of the APPN connection network model to allow HPR nodes to use IP networks for communication without having to predefine link connections. END_D End: Rfc: RFC2352 Title: A Convention For Using Legal Names as Domain Names Authors: O. Vaughan Status: Informational Date: 1998-05 Mailbox: owain@vaughan.com Pages: 8 Characters: 16354 Obsoletes: RFC2240 Url: ftp://ftp.isi.edu/in-notes/rfc2352.txt Description:: END_D The purpose of this memo is to focus discussion on the particular problems with the exhaustion of the top level domain space in the Internet and the possible conflicts that can occur when multiple organisations are vying for the same name. The proposed solutions in this document are intended as a framework for development, such that a general consensus will emerge as to the appropriate solution to the problems in each case, leading eventually to the adoption of standards. END_D End: Rfc: RFC2351 Title: Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP Authors: A. Robert Status: Informational Date: 1998-05 Mailbox: arobert@par1.par.sita.int Pages: 23 Characters: 43440 Url: ftp://ftp.isi.edu/in-notes/rfc2351.txt Description:: END_D This memo specifies a protocol for the encapsulation of the airline specific protocol over IP. END_D End: Rfc: RFC2350 Title: Expectations for Computer Security Incident Response Authors: N. Brownlee, E. Guttman Status: Best_Current_Practice Date: 1998-06 Mailbox: n.brownlee@auckland.ac.nz, Erik.Guttman@sun.com Pages: 38 Characters: 86545 Url: ftp://venera.isi.edu/in-notes/rfc2350.txt Keywords: Security Description:: END_D The purpose of this document is to express the general Internet community's expectations of Computer Security Incident Response Teams (CSIRTs). It is not possible to define a set of requirements that would be appropriate for all teams, but it is possible and helpful to list and describe the general set of topics and issues which are of concern and interest to constituent communities. CSIRT constituents have a legitimate need and right to fully understand the policies and procedures of 'their' Computer Security Incident Response Team. One way to support this understanding is to supply detailed information which users may consider, in the form of a formal template completed by the CSIRT. An outline of such a template and a filled in example are provided. END_D Working-Group: Guidelines and Recommendations for Security Incident Processing End: Rfc: RFC2349 Title: TFTP Timeout Interval and Transfer Size Options Authors: G. Malkin, A. Harkin Status: Draft_Standard Date: 1998-05 Mailbox: gmalkin@baynetworks.com, ash@cup.hp.com Pages: 5 Characters: 7848 Updates: RFC1350 Obsoletes: RFC1784 Url: ftp://ftp.isi.edu/in-notes/rfc2349.txt Description:: END_D This document describes two TFTP options. The first allows the client and server to negotiate the Timeout Interval. The second allows the side receiving the file to determine the ultimate size of the transfer before it begins. END_D Working-Group: TFTP Extensions End: Rfc: RFC2348 Title: TFTP Blocksize Option Authors: G. Malkin, A. Harkin Status: Draft_Standard Date: 1998-05 Mailbox: gmalkin@baynetworks.com, ash@cup.hp.com Pages: 5 Characters: 9515 Updates: RFC1350 Obsoletes: RFC1783 Url: ftp://ftp.isi.edu/in-notes/rfc2348.txt Description:: END_D This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. END_D Working-Group: TFTP Extensions End: Rfc: RFC2347 Title: TFTP Option Extension Authors: G. Malkin, A. Harkin Status: Draft_Standard Date: 1998-05 Mailbox: gmalkin@baynetworks.com, ash@cup.hp.com Pages: 7 Characters: 13060 Updates: RFC1350 Obsoletes: RFC1782 Url: ftp://ftp.isi.edu/in-notes/rfc2347.txt Description:: END_D The Trivial File Transfer Protocol [1] is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a simple extension to TFTP to allow option negotiation prior to the file transfer. END_D Working-Group: TFTP Extensions End: Rfc: RFC2346 Title: Making Postscript and PDF International Authors: J. Palme Status: Informational Date: 1998-05 Mailbox: jpalme@dsv.su.se Pages: 6 Characters: 12382 Url: ftp://ftp.isi.edu/in-notes/rfc2346.txt Description:: END_D Certain text formats, for example Postscript (MIME-Type: application/postscript; file extension .ps) and Portable Document Format (MIME-Type: application/pdf; file extension .pdf) specify exactly the page layout of the printed document. The commonly used paper format is different in North America and the rest of the world. North America uses the 'Letter' format, while the rest of the world mostly uses the ISO-standard 'A4' format. This means that documents formatted on one continent may not be easily printable on another continent. This memo gives advice on how to produce documents which are equally well printable with the Letter and the A4 formats. By using the advice in this document, you can put up a document on the Internet, which recipients can print without problem both in and outside North America. END_D End: Rfc: RFC2345 Title: Domain Names and Company Name Retrieval Authors: J. Klensin, T. Wolf, G. Oglesby Status: Experimental Date: 1998-05 Mailbox: klensin@mci.net, ted@usa.net, gary@mci.net Pages: 14 Characters: 29707 Url: ftp://ftp.isi.edu/in-notes/rfc2345.txt Description:: END_D This document proposes a company name to URL mapping service based on the oldest and least complex of Internet directory protocols, whois, in order to explore whether an extremely simple and widely-deployed protocol can succeed where more complex and powerful options have failed or been excessively delayed. END_D End: Rfc: RFC2344 Title: Reverse Tunneling for Mobile IP Authors: G. Montenegro, Editor Status: Proposed_Standard Date: 1998-05 Mailbox: gabriel.montenegro@eng.sun.com Pages: 19 Characters: 39468 Url: ftp://ftp.isi.edu/in-notes/rfc2344.txt Description:: END_D This document proposes backwards-compatible extensions to Mobile IP in order to support topologically correct reverse tunnels. This document does not attempt to solve the problems posed by firewalls located between the home agent and the mobile node's care-of address. END_D Working-Group: IP Routing for Wireless/Mobile Hosts End: Rfc: RFC2343 Title: RTP Payload Format for Bundled MPEG Authors: M. Civanlar, G. Cash, B. Haskell Status: Experimental Date: 1998-05 Mailbox: civanlar@research.att.com, glenn@research.att.com, bgh@research.att.com Pages: 8 Characters: 16557 Url: ftp://ftp.isi.edu/in-notes/rfc2343.txt Description:: END_D This document describes a payload type for bundled, MPEG-2 encoded video and audio data that may be used with RTP, version 2. Bundling has some advantages for this payload type particularly when it is used for video-on-demand applications. This payload type may be used when its advantages are important enough to sacrifice the modularity of having separate audio and video streams. END_D End: Rfc: RFC2342 Title: IMAP4 Namespace Authors: M. Gahrns, C. Newman Status: Proposed_Standard Date: 1998-05 Mailbox: mikega@microsoft.com, chris.newman@innosoft.com Pages: 10 Characters: 19489 Keywords: IMAP Url: ftp://ftp.isi.edu/in-notes/rfc2342.txt Description:: END_D This document defines a NAMESPACE command that allows a client to discover the prefixes of namespaces used by a server for personal mailboxes, other users' mailboxes, and shared mailboxes. This allows a client to avoid much of the manual user configuration that is now necessary when mixing and matching IMAP4 clients and servers. END_D End: Rfc: RFC2341 Title: Cisco Layer Two Forwarding (Protocol) "L2F" Authors: A. Valencia, M. Littlewood, T. Kolar Status: Historic Date: 1998-05 Mailbox: valencia@cisco.com, littlewo@cisco.com, tkolar@cisco.com Pages: 29 Characters: 66592 Url: ftp://ftp.isi.edu/in-notes/rfc2341.txt Description:: END_D This document describes the Layer Two Forwarding protocol (L2F) which permits the tunneling of the link layer (i.e., HDLC, async HDLC, or SLIP frames) of higher level protocols. Using such tunnels, it is possible to divorce the location of the initial dial-up server from the location at which the dial-up protocol connection is terminated and access to the network provided. END_D End: Rfc: RFC2340 Title: Nortel's Virtual Network Switching (VNS) Overview Authors: B. Jamoussi, D. Jamieson, D. Williston, S. Gabe Status: Informational Date: 1998-05 Mailbox: jamoussi@Nortel.ca, djamies@Nortel.ca, danwil@Nortel.ca, spgabe@Nortel.ca Pages: 14 Characters: 30731 Url: ftp://ftp.isi.edu/in-notes/rfc2340.txt Description:: END_D VNS is a multi-protocol switching architecture that provides COS-sensitive packet switching, reduces the complexity of operating protocols like PPP and frame relay, provides logical networks and traffic segregation for Virtual Private Networks (VPNs), security and traffic engineering, enables efficient WAN broadcasting and multicasting, and reduces address space requirements. VNS reduces the number of routing hops over the WAN by switching packets based on labels. END_D End: Rfc: RFC2339 Title: An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 Protocols Authors: The Internet Society, Sun Microsystems Status: Informational Date: 1998-05 Mailbox: sob@harvard.edu Pages: 5 Characters: 10745 Url: ftp://ftp.isi.edu/in-notes/rfc2339.txt Description:: END_D This Request for Comments records an agreement between Sun Microsystems, Inc. and the Internet Society to permit the flow of Sun's Network File System specifications into the Internet Standards process conducted by the Internet Engineering Task Force. END_D End: Rfc: RFC2338 Title: Virtual Router Redundancy Protocol Authors: S. Knight, D. Weaver, D. Whipple, R. Hinden, D. Mitzel, P. Hunt, P. Higginson, M. Shand, A. Lindem Status: Proposed_Standard Date: 1998-04 Mailbox: Steven.Knight@ascend.com, Doug.Weaver@ascend.com, dwhipple@microsoft.com, hinden@iprg.nokia.com, mitzel@iprg.nokia.com, hunt@iprg.nokia.com, higginson@mail.dec.com, shand@mail.dec.com, acee@raleigh.ibm.com Pages: 27 Characters: 59871 Url: ftp://ftp.isi.edu/in-notes/rfc2338.txt Description:: END_D This memo defines the Virtual Router Redundancy Protocol (VRRP). VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IP address(es) associated with a virtual router is called the Master, and forwards packets sent to these IP addresses. The election process provides dynamic fail over in the forwarding responsibility should the Master become unavailable. This allows any of the virtual router IP addresses on the LAN to be used as the default first hop router by end-hosts. The advantage gained from using VRRP is a higher availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. END_D Working-Group: Virtual Router Redundancy Protocol End: Rfc: RFC2337 Title: Intra-LIS IP multicast among routers over ATM using Sparse Mode PIM Authors: D. Farinacci, D. Meyer, Y. Rekhter Status: Experimental Date: 1998-04 Mailbox: dino@cisco.com, dmm@cisco.com, yakov@cisco.com Pages: 8 Characters: 16357 Url: ftp://ftp.isi.edu/in-notes/rfc2337.txt Description:: END_D This document describes how intra-LIS IP multicast can be efficiently supported among routers over ATM without using the Multicast Address Resolution Server (MARS). The method described here is specific to Sparse Mode PIM [PIM-SM], and relies on the explicit join mechanism inherent in PIM-SM to notify routers when they should create group specific point-to-multipoint VCs. END_D Working-Group: Internetworking over NMBA End: Rfc: RFC2336 Title: Classical IP to NHRP Transition Authors: J. Luciani Status: Informational Date: 1998-07 Mailbox: luciani@baynetworks.com Pages: 5 Characters: 10530 Url: ftp://ftp.isi.edu/in-notes/rfc2336.txt Description:: END_D This document describes methods and procedures for the graceful transition from an ATMARP LIS[1] to an NHRP LIS[2] network model over ATM. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2335 Title: A Distributed NHRP Service Using SCSP Authors: J. Luciani Status: Proposed_Standard Date: 1998-04 Mailbox: luciani@baynetworks.com Pages: 7 Characters: 14007 Url: ftp://ftp.isi.edu/in-notes/rfc2335.txt Description:: END_D This document describes a method for distributing an NHRP service within a LIS [1]. This method uses the Server Cache Synchronization Protocol (SCSP) [2] to synchronize the client information databases held by NHRP Servers (NHSs) within a LIS. END_D Working-Group: Internetworking Over NMBA End: Rfc: RFC2334 Title: Server Cache Synchronization Protocol (SCSP) Authors: J. Luciani, G. Armitage, J. Halpern, N. Doraswamy Status: Proposed_Standard Date: 1998-04 Mailbox: luciani@baynetworks.com, gja@lucent.com, jhalpern@Newbridge.COM, naganand@baynetworks.com Pages: 40 Characters: 98161 Url: ftp://ftp.isi.edu/in-notes/rfc2334.txt Description:: END_D As required by the Routing Protocol Criteria [RFC 1264], this memo discusses the applicability of the Next Hop Resolution Protocol (NHRP) in routing of IP datagrams over Non-Broadcast Multiple Access (NBMA) networks, such as ATM, SMDS and X.25. END_D Working-Group: Internetworking Over NMBA End: Rfc: RFC2333 Title: NHRP Protocol Applicability Statement Authors: D. Cansever Status: Proposed_Standard Date: 1998-04 Mailbox: dcansever@gte.com Pages: 9 Characters: 20164 Url: ftp://ftp.isi.edu/in-notes/rfc2333.txt Description:: END_D As required by the Routing Protocol Criteria [RFC 1264], this memo discusses the applicability of the Next Hop Resolution Protocol (NHRP) in routing of IP datagrams over Non-Broadcast Multiple Access (NBMA) networks, such as ATM, SMDS and X.25. END_D Working-Group: Internetworking Over NMBA End: Rfc: RFC2332 Title: NBMA Next Hop Resolution Protocol (NHRP) Authors: J. Luciani, D. Katz, D. Piscitello, B. Cole, N. Doraswamy Status: Proposed_Standard Date: 1998-04 Mailbox: luciani@baynetworks.com, dkatz@cisco.com, dave@corecom.com, bcole@jnx.com, naganand@baynetworks.com Pages: 52 Characters: 126978 Url: ftp://ftp.isi.edu/in-notes/rfc2332.txt Description:: END_D This document describes the NBMA Next Hop Resolution Protocol (NHRP). NHRP can be used by a source station (host or router) connected to a Non-Broadcast, Multi-Access (NBMA) subnetwork to determine the internetworking layer address and NBMA subnetwork addresses of the "NBMA next hop" towards a destination station. END_D Working-Group: Internetworking Over NMBA End: Rfc: RFC2331 Title: ATM Signalling Support for IP over ATM - UNI Signalling 4.0 Update Authors: M. Maher Status: Proposed_Standard Date: 1998-04 Mailbox: maher@isi.edu Pages: 26 Characters: 61119 Url: ftp://ftp.isi.edu/in-notes/rfc2331.txt Description:: END_D This memo describes how to efficiently use the ATM call control signalling procedures defined in UNI Signalling 4.0 to support IP over ATM environments as described in RFC 2225 and in RFC 2332. END_D Working-Group: Internetworking Over NMBA End: Rfc: RFC2330 Title: Framework for IP Performance Metrics Authors: V. Paxson, G. Almes, J. Mahdavi, M. Mathis Status: Informational Date: 1998-05 Mailbox: vern@ee.lbl.gov, almes@advanced.org, mahdavi@psc.edu, mathis@psc.edu Pages: 40 Characters: 94387 Url: ftp://ftp.isi.edu/in-notes/rfc2330.txt Description:: END_D The purpose of this memo is to define a general framework for particular metrics to be developed by the IETF's IP Performance Metrics effort, begun by the Benchmarking Methodology Working Group (BMWG) of the Operational Requirements Area, and being continued by the IP Performance Metrics Working Group (IPPM) of the Transport Area. END_D Working-Group: IP Performance Metrics End: Rfc: RFC2329 Title: OSPF Standardization Report Authors: J. Moy Status: Informational Date: 1998-04 Mailbox: jmoy@casc.com Pages: 9 Characters: 15130 Url: ftp://ftp.isi.edu/in-notes/rfc2329.txt Description:: END_D This memo documents how the requirements for advancing a routing protocol to Full Standard have been met for OSPFv2. END_D Working-Group: Open Shortest Path First IGP End: Rfc: RFC2328 Title: OSPF Version 2 Authors: J. Moy Status: Standard Date: 1998-04 Mailbox: jmoy@casc.com Pages: 244 Characters: 447367 Obsoletes: RFC2178 Url: ftp://ftp.isi.edu/in-notes/rfc2328.txt Description:: END_D This memo documents version 2 of the OSPF protocol. OSPF is a link-state routing protocol. It is designed to be run internal to a single Autonomous System. Each OSPF router maintains an identical database describing the Autonomous System's topology. From this database, a routing table is calculated by constructing a shortest-path tree. END_D Working-Group: Open Shortest Path First End: Rfc: RFC2327 Title: SDP: Session Description Protocol Authors: M. Handley, V. Jacobson Status: Proposed_Standard Date: 1998-04 Mailbox: mjh@isi.edu, van@ee.lbl.gov Pages: 42 Characters: 87096 Url: ftp://ftp.isi.edu/in-notes/rfc2327.txt Description:: END_D This document defines the Session Description Protocol, SDP. SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. END_D Working-Group: Multiparty Multimedia Session Control End: Rfc: RFC2326 Title: Real Time Streaming Protocol (RTSP) Authors: H. Schulzrinne, A. Rao, R. Lanphier Status: Proposed_Standard Date: 1998-04 Mailbox: schulzrinne@cs.columbia.edu, anup@netscape.com, robla@real.com Pages: 92 Characters: 195010 Url: ftp://ftp.isi.edu/in-notes/rfc2326.txt Description:: END_D The Real Time Streaming Protocol, or RTSP, is an application-level protocol for control over the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. Sources of data can include both live data feeds and stored clips. This protocol is intended to control multiple data delivery sessions, provide a means for choosing delivery channels such as UDP, multicast UDP and TCP, and provide a means for choosing delivery mechanisms based upon RTP (RFC 1889). END_D Working-Group: Multiparty Multimedia Session Control End: Rfc: RFC2325 Title: Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2 Authors: M. Slavitch Status: Informational Date: 1998-04-01 Mailbox: slavitch@loran.com Pages: 8 Characters: 12726 Keywords: Lirpa1 Url: ftp://ftp.isi.edu/in-notes/rfc2325.txt Description:: END_D This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of coffee-brewing and maintenance devices. END_D End: Rfc: RFC2324 Title: Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) Authors: L. Masinter Status: Informational Date: 1998-04-01 Mailbox: masinter@parc.xerox.com Pages: 10 Characters: 19610 Keywords: Lirpa1 Url: ftp://ftp.isi.edu/in-notes/rfc2324.txt Description:: END_D This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots. END_D End: Rfc: RFC2323 Title: IETF Identification and Security Guidelines Authors: A. Ramos Status: Informational Date: 1998-04-01 Mailbox: ramos@isi.edu Pages: 5 Characters: 9257 Keywords: Lirpa1 Url: ftp://ftp.isi.edu/in-notes/rfc2323.txt Description:: END_D This RFC is meant to represent a guideline by which the IETF conferences may run more effeciently with regards to identification and security protocols, with specific attention paid to a particular sub-group within the IETF: "facial hairius extremis". END_D End: Rfc: RFC2322 Title: Management of IP numbers by peg-dhcp Authors: K. van den Hout, A. Koopal, R. van Mook Status: Informational Date: 1998-04-01 Mailbox: koos@cetis.hvu.nl, andre@NL.net, remco@sateh.com Pages: 7 Characters: 12665 Url: ftp://ftp.isi.edu/in-notes/rfc2322.txt Description:: END_D This RFC describes a protocol to dynamically hand out ip-numbers on field networks and small events that don't necessarily have a clear organisational body. It can also provide some fixed additional fields global for all clients like netmask and even autoproxyconfigs. It does not depend on a particular ip-stack. END_D End: Rfc: RFC2321 Title: RITA -- The Reliable Internetwork Troubleshooting Agent Authors: A. Bressen Status: Informational Date: 1998-04-01 Mailbox: bressen@leftbank.com, bressen@cohesive.com, bressen@mirror.to Pages: 6 Characters: 12302 Url: ftp://ftp.isi.edu/in-notes/rfc2321.txt Description:: END_D A Description of the usage of Nondeterministic Troubleshooting and Diagnostic Methodologies as applied to today's complex nondeterministic networks and environments. END_D End: Rfc: RFC2320 Title: Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-MIB) Authors: M. Greene, J. Luciani, K. White, T. Kuo Status: Proposed_Standard Date: 1998-04 Mailbox: maria@xedia.com, luciani@baynetworks.com, kennethw@vnet.ibm.com, ted_kuo@Baynetworks.com Pages: 52 Characters: 102116 Keywords: SNMP Url: ftp://ftp.isi.edu/in-notes/rfc2320.txt Description:: END_D The purpose of this memo is to define the Management Information Base (MIB) for supporting Classical IP and ARP over ATM as specified in Classical IP and ARP over ATM. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2319 Title: Ukrainian Character Set KOI8-U Authors: KOI8-U Working Group Status: Informational Date: 1998-04 Mailbox: koi8-u@sita.kiev.ua Pages: 9 Characters: 18042 Url: ftp://ftp.isi.edu/in-notes/rfc2319.txt Description:: END_D This document provides information about character encoding KOI8-U (KOI8 Ukrainian) which is a de-facto standard in Ukrainian Internet community. KOI8-U is compatible with KOI8-R (RFC 1489) in all Russian letters and extends it with four Ukrainian letters which locations are compliant with ISO-IR-111. The official site of KOI8-U Working Group is http://www.net.ua. END_D End: Rfc: RFC2318 Title: The text/css Media Type Authors: H. Lie, B. Bos, C. Lilley Status: Informational Date: 1998-03 Mailbox: howcome@w3.org, bert@w3.org, chris@w3.org Pages: 5 Characters: 7819 Keywords: Web Url: ftp://ftp.isi.edu/in-notes/rfc2318.txt Description:: END_D Cascading Style Sheets (CSS) is a style sheet language for the World Wide Web. CSS style sheets have been in use since October 1995 using the Media Type text/css without registration; this memo seeks to regularize that position. END_D End: Rfc: RFC2317 Title: Classless IN-ADDR.ARPA delegation Authors: H. Eidnes, G. de Groot, P. Vixie Status: Best_Current_Practice Date: 1998-03 Mailbox: Havard.Eidnes@runit.sintef.no, GeertJan.deGroot@bsdi.com, paul@vix.com Pages: 10 Characters: 17744 Keywords: DNS Url: ftp://ftp.isi.edu/in-notes/rfc2317.txt Description:: END_D This document describes a way to do IN-ADDR.ARPA delegation on non-octet boundaries for address spaces covering fewer than 256 addresses. The proposed method should thus remove one of the objections to subnet on non-octet boundaries but perhaps more significantly, make it possible to assign IP address space in smaller chunks than 24-bit prefixes, without losing the ability to delegate authority for the corresponding IN-ADDR.ARPA mappings. The proposed method is fully compatible with the original DNS lookup mechanisms specified in [1], i.e. there is no need to modify the lookup algorithm used, and there should be no need to modify any software which does DNS lookups. END_D Working-Group: DNS IXFR, Notification, and Dynamic Update End: Rfc: RFC2316 Title: Report of the IAB Security Architecture Workshop Authors: S. Bellovin Status: Informational Date: 1998-04 Mailbox: bellovin@acm.org Pages: 9 Characters: 19733 Keywords: Security Url: ftp://ftp.isi.edu/in-notes/rfc2316.txt Description:: END_D On 3-5 March 1997, the IAB held a security architecture workshop at Bell Labs in Murray Hill, NJ. We identified the core security components of the architecture, and specified several documents that need to be written. Most importantly, we agreed that security was not optional, and that it needed to be designed in from the beginning. END_D End: Rfc: RFC2315 Title: PKCS #7: Cryptographic Message Syntax Version 1.5 Authors: B. Kaliski Status: Informational Date: 1998-03 Mailbox: burt@rsa.com Pages: 32 Characters: 69679 Url: ftp://ftp.isi.edu/in-notes/rfc2315.txt Description:: END_D This document describes a general syntax for data that may have cryptography applied to it, such as digital signatures and digital envelopes. The syntax admits recursion, so that, for example, one envelope can be nested inside another, or one party can sign some previously enveloped digital data. It also allows arbitrary attributes, such as signing time, to be authenticated along with the content of a message, and provides for other attributes such as countersignatures to be associated with a signature. A degenerate case of the syntax provides a means for disseminating certificates and certificate-revocation lists. END_D End: Rfc: RFC2314 Title: PKCS #10: Certification Request Syntax Version 1.5 Authors: B. Kaliski Status: Informational Date: 1998-03 Mailbox: burt@rsa.com Pages: 8 Characters: 15814 Keywords: Security Url: ftp://ftp.isi.edu/in-notes/rfc2314.txt Description:: END_D This document describes a syntax for certification requests. END_D End: Rfc: RFC2313 Title: PKCS #1: RSA Encryption Version 1.5 Authors: B. Kaliski Status: Informational Date: 1998-03 Mailbox: burt@rsa.com Pages: 19 Characters: 37777 Keywords: Security Url: ftp://ftp.isi.edu/in-notes/rfc2313.txt Description:: END_D This document describes a method for encrypting data using the RSA public-key cryptosystem. END_D Obsoleted-by: RFC2437 End: Rfc: RFC2312 Title: S/MIME Version 2 Certificate Handling Authors: S. Dusse, P. Hoffman, B. Ramsdell, J. Weinstein Status: Informational Date: 1998-03 Mailbox: spock@rsa.com, phoffman@imc.org, blaker@deming.com, jsw@netscape.com Pages: 20 Characters: 39829 Url: ftp://ftp.isi.edu/in-notes/rfc2312.txt Description:: END_D S/MIME (Secure/Multipurpose Internet Mail Extensions), described in [SMIME-MSG], provides a method to send and receive secure MIME messages. In order to validate the keys of a message sent to it, an S/MIME agent needs to certify that the key is valid. This memo describes the mechanisms S/MIME uses to create and validate keys using certificates. END_D End: Rfc: RFC2311 Title: S/MIME Version 2 Message Specification Authors: S. Dusse, P. Hoffman, B. Ramsdell, L. Lundblade, L. Repka Status: Informational Date: 1998-03 Mailbox: spock@rsa.com, phoffman@imc.org, blaker@deming.com, lgl@qualcomm.com, repka@netscape.com Pages: 37 Characters: 70901 Keywords: Mail, Security Url: ftp://ftp.isi.edu/in-notes/rfc2311.txt Description:: END_D S/MIME (Secure/Multipurpose Internet Mail Extensions) provides a consistent way to send and receive secure MIME data. Based on the popular Internet MIME standard, S/MIME provides the following cryptographic security services for electronic messaging applications: authentication, message integrity and non-repudiation of origin (using digital signatures) and privacy and data security (using encryption). END_D End: Rfc: RFC2310 Title: The Safe Response Header Field Authors: K. Holtman Status: Experimental Date: 1998-04 Mailbox: koen@win.tue.nl Pages: 5 Characters: 8091 Keywords: Web Url: ftp://ftp.isi.edu/in-notes/rfc2310.txt Description:: END_D This document defines a HTTP response header field called Safe, which can be used to indicate that repeating a HTTP request is safe. Such an indication will allow user agents to handle retries of some safe requests, in particular safe POST requests, in a more user-friendly way. END_D Working-Group: HyperText Transfer Protocol End: Rfc: RFC2309 Title: Recommendations on Queue Management and Congestion Avoidance in the Internet Authors: B. Braden, D. Clark, J. Crowcroft, B. Davie, S. Deering, D. Estrin, S. Floyd, V. Jacobson, G. Minshall, C. Partridge, L. Peterson, K. Ramakrishnan, S. Shenker, J. Wroclawski, L. Zhang Status: Informational Date: 1998-04 Mailbox: Braden@@ISI.EDU, DDC@@lcs.mit.edu, Jon.Crowcroft@@cs.ucl.ac.uk, bdavie@@cisco.com, deering@@cisco.com, Estrin@@usc.edu, Floyd@@ee.lbl.gov, Van@@ee.lbl.gov, Minshall@@fiberlane.com, craig@@bbn.com, LLP@@cs.arizona.edu, KKRama@@research.att.com, Shenker@@parc.xerox.com, JTW@@lcs.mit.edu, Lixia@@cs.ucla.edu Pages: 17 Characters: 38079 Url: ftp://ftp.isi.edu/in-notes/rfc2309.txt Description:: END_D This memo presents two recommendations to the Internet community concerning measures to improve and preserve Internet performance. It presents a strong recommendation for testing, standardization, and widespread deployment of active queue management in routers, to improve the performance of today's Internet. It also urges a concerted effort of research, measurement, and ultimate deployment of router mechanisms to protect the Internet from flows that are not sufficiently responsive to congestion notification. END_D End: Rfc: RFC2308 Title: Negative Caching of DNS Queries (DNS NCACHE) Authors: M. Andrews Status: Proposed_Standard Date: 1998-03 Mailbox: Mark.Andrews@cmis.csiro.au Pages: 19 Characters: 41428 Keywords: DNS Updates: RFC1034, RFC1035 Url: ftp://ftp.isi.edu/in-notes/rfc2308.txt Description:: END_D [RFC1034] provided a description of how to cache negative responses. It however had a fundamental flaw in that it did not allow a name server to hand out those cached responses to other resolvers, thereby greatly reducing the effect of the caching. This document addresses issues raise in the light of experience and replaces [RFC1034 Section 4.3.4]. END_D Working-Group: DNS IXFR, Notification and Dynamic Update End: Rfc: RFC2307 Title: An Approach for Using LDAP as a Network Information Service Authors: L. Howard Status: Experimental Date: 1998-03 Mailbox: lukeh@xedoc.com Pages: 21 Characters: 41396 Keywords: LDAP Url: ftp://ftp.isi.edu/in-notes/rfc2307.txt Description:: END_D This document describes an experimental mechanism for mapping entities related to TCP/IP and the UNIX system into X.500 [X500] entries so that they may be resolved with the Lightweight Directory Access Protocol [RFC2251]. A set of attribute types and object classes are proposed, along with specific guidelines for interpreting them. END_D End: Rfc: RFC2305 Title: A Simple Mode of Facsimile Using Internet Mail Authors: K. Toyoda, H. Ohno, J. Murai, D. Wing Status: Proposed_Standard Date: 1998-03 Mailbox: ktoyoda@rdmg.mgcs.mei.co.jp, hohno@is.titech.ac.jp, jun@wide.ad.jp, dwing@cisco.com Pages: 13 Characters: 24624 Url: ftp://ftp.isi.edu/in-notes/rfc2305.txt Description:: END_D This specification provides for "simple mode" carriage of facsimile data over the Internet. It can send images not only to other Internet-aware facsimile devices but also to Internet-native systems, such as PCs with common email readers which can handle MIME mail and TIFF for Facsimile data. The specification facilitates communication among existing facsimile devices, Internet mail agents, and the gateways which connect them. END_D Working-Group: Internet Fax End: Rfc: RFC2304 Title: Minimal FAX address format in Internet Mail Authors: C. Allocchio Status: Proposed_Standard Date: 1998-03 Mailbox: Claudio.Allocchio@elettra.trieste.it Pages: 8 Characters: 13234 Keywords: Mail Url: ftp://ftp.isi.edu/in-notes/rfc2304.txt Description:: END_D This memo describes the MINIMAL addressing method and standard extensions to encode FAX addresses in e-mail addresses, as required in reference [13]. The opposite problem, i.e. to allow a traditional numeric-only fax device user to access the e-mail transport service, is not discussed here. END_D Working-Group: Internet Fax End: Rfc: RFC2303 Title: Minimal PSTN address format in Internet Mail Authors: C. Allocchio Status: Proposed_Standard Date: 1998-03 Mailbox: Claudio.Allocchio@elettra.trieste.it Pages: 8 Characters: 14625 Keywords: Mail Url: ftp://ftp.isi.edu/in-notes/rfc2303.txt Description:: END_D This memo describes the MINIMAL addressing method to encode PSTN addresses into e-mail addresses and the standard extension mechanism to allow definition of further standard elements. The opposite problem, i.e. to allow a traditional numeric-only PSTN device user to access the e-mail transport service, is not discussed here. END_D Working-Group: Internet Fax End: Rfc: RFC2302 Title: Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration Authors: G. Parsons, J. Rafferty, S. Zilles Status: Proposed_Standard Date: 1998-03 Mailbox: Glenn.Parsons@Nortel.ca, Jrafferty@worldnet.att.net, szilles@adobe.com Pages: 8 Characters: 14375 Url: ftp://ftp.isi.edu/in-notes/rfc2302.txt Description:: END_D This document describes the registration of the MIME sub-type image/tiff. The baseline encoding is defined by [TIFF]. END_D Working-Group: Internet Fax End: Rfc: RFC2301 Title: File Format for Internet Fax Authors: L. McIntyre, S. Zilles, R. Buckley, D. Venable, G. Parsons, J. Rafferty Status: Proposed_Standard Date: 1998-03 Mailbox: lmcintyre@adoc.xerox.com, szilles@adobe.com, Rob_Buckley@wb.xerox.com, venable@wrc.xerox.com, Glenn.Parsons@Nortel.ca, Jrafferty@worldnet.att.net Pages: 77 Characters: 200525 Url: ftp://ftp.isi.edu/in-notes/rfc2301.txt Description:: END_D This document describes the TIFF (Tag Image File Format) representation of image data specified by the ITU-T Recommendations for black-and-white and color facsimile. This file format specification is commonly known as TIFF-FX. It formally defines minimal, extended and lossless JBIG modes (Profiles S, F, J) for black-and-white fax, and base JPEG, lossless JBIG and Mixed Raster Content modes (Profiles C, L, M) for color and grayscale fax. These modes or profiles correspond to the content of the applicable ITU-T Recommendations. Files formatted according to this specification use the image/tiff MIME Content Type. END_D Working-Group: Internet Fax End: Rfc: RFC2300 Title: INTERNET OFFICIAL PROTOCOL STANDARDS Authors: Internet Architecture Board, J. Postel Status: Standards_Track Date: 1998-05 Mailbox: Postel@ISI.EDU Pages: 59 Characters: 128322 Obsoletes: RFC2200, RFC2000, RFC1920, RFC1880, RFC1800, RFC1780, RFC1720, RFC1610, RFC1600, RFC1540, RFC1500, RFC1410, RFC1360, RFC1280, RFC1250, RFC1200, RFC1140, RFC1130, RFC1100, RFC1083 Url: ftp://ftp.isi.edu/in-notes/rfc2300.txt Keywords: Standards Description:: END_D A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally are pointers to references and contacts for further information. END_D Obsoleted-by: RFC2400 End: Rfc: RFC2299 Title: Request for Comments Summary Authors: A. Ramos Status: Informational Date: 1999-01 Mailbox: ramos@isi.edu Pages: 24 Characters: 51234 I-D-Tag: None Url: ftp://ftp.isi.edu/in-notes/rfc2299.txt Description:: END_D This RFC is a slightly annotated list of the 100 RFCs from RFC 2200 through RFCs 2299. This is a status report on these RFCs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. END_D End: Rfc: RFC2298 Title: An Extensible Message Format for Message Disposition Notifications Authors: R. Fajman Status: Proposed_Standard Date: 1998-03 Mailbox: raf@cu.nih.gov Pages: 28 Characters: 62059 Keywords: Mail Url: ftp://ftp.isi.edu/in-notes/rfc2298.txt Description:: END_D This memo defines a MIME content-type that may be used by a mail user agent (UA) or electronic mail gateway to report the disposition of a message after it has been sucessfully delivered to a recipient. This content-type is intended to be machine-processable. Additional message headers are also defined to permit Message Disposition Notifications (MDNs) to be requested by the sender of a message. The purpose is to extend Internet Mail to support functionality often found in other messaging systems, such as X.400 and the proprietary "LAN-based" systems, and often referred to as "read receipts," "acknowledgements," or "receipt notifications." The intention is to do this while respecting the privacy concerns that have often been expressed when such functions have been discussed in the past. END_D Working-Group: Receipt Notifications for Internet Mail End: Rfc: RFC2297 Title: Ipsilon's General Switch Management Protocol Specification Version 2.0 Authors: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, G. Minshall Status: Informational Date: 1998-03 Mailbox: pn@ipsilon.com, texas@sprintcorp.com, hinden@ipsilon.com, hoffman@ipsilon.com, fong@coppercom.com, pugs@ipsilon.com, minshall@fiberlane.com Pages: 109 Characters: 280484 Updates: RFC2297 Url: ftp://ftp.isi.edu/in-notes/rfc2297.txt Description:: END_D This memo specifies enhancements to the General Switch Management Protocol (GSMP) [RFC1987]. The major enhancement is the addition of Quality of Service (QoS) messages. Other improvements have been made to the protocol resulting from operational experience. GSMP is a general purpose protocol to control an ATM switch. It allows a controller to establish and release connections across the switch; add and delete leaves on a multicast connection; manage switch ports; request configuration information; and request statistics. END_D End: Rfc: RFC2296 Title: HTTP Remote Variant Selection Algorithm -- RVSA/1.0 Authors: K. Holtman, A. Mutz Status: Experimental Date: 1998-03 Mailbox: koen@win.tue.nl, mutz@hpl.hp.com Pages: 13 Characters: 26932 Url: ftp://ftp.isi.edu/in-notes/rfc2296.txt Description:: END_D HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is a mechanism for automatically selecting the best version when the URL is accessed. A remote variant selection algorithm can be used to speed up the transparent negotiation process. This document defines the remote variant selection algorithm with the version number 1.0. END_D Working-Group: HyperText Transfer Protocol End: Rfc: RFC2295 Title: Transparent Content Negotiation in HTTP Authors: K. Holtman, A. Mutz Status: Experimental Date: 1998-03 Mailbox: koen@win.tue.nl, mutz@hpl.hp.com Pages: 58 Characters: 125130 Keywords: Web Url: ftp://ftp.isi.edu/in-notes/rfc2295.txt Description:: END_D HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is an extensible negotiation mechanism, layered on top of HTTP, for automatically selecting the best version when the URL is accessed. This enables the smooth deployment of new web data formats and markup tags. END_D Working-Group: HyperText Transfer Protocol End: Rfc: RFC2294 Title: Representing the O/R Address hierarchy in the X.500 Directory Information Tree Authors: S. Kille Status: Proposed_Standard Date: 1998-03 Mailbox: S.Kille@ISODE.COM Pages: 13 Characters: 22059 Keywords: LDAP Obsoletes: RFC1836 Url: ftp://ftp.isi.edu/in-notes/rfc2294.txt Description:: END_D This document defines a representation of the O/R Address hierarchy in wthe Directory Information Tree [6, 1]. This is useful for a range of purposes, including: o Support for MHS Routing [4]. o Support for X.400/RFC 822 address mappings [2, 5]. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2293 Title: Representing Tables and Subtrees in the X.500 Directory Authors: S. Kille Status: Proposed_Standard Date: 1998-03 Mailbox: S.Kille@ISODE.COM Pages: 8 Characters: 12539 Keywords: LDAP Obsoletes: RFC1837 Url: ftp://ftp.isi.edu/in-notes/rfc2293.txt Description:: END_D This document defines techniques for representing two types of information mapping in the OSI Directory [1]. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2292 Title: Advanced Sockets API for IPv6 Authors: W. Stevens, M. Thomas Status: Informational Date: 1998-02 Mailbox: rstevens@kohala.com, matt.thomas@altavista-software.com Pages: 67 Characters: 152077 Url: ftp://ds.internic.net/rfc/rfc2292.txt Description:: END_D Specifications are in progress for changes to the sockets API to support IP version 6 [RFC-2133]. These changes are for TCP and UDP- based applications and will support most end-user applications in use today: Telnet and FTP clients and servers, HTTP clients and servers, and the like. END_D Working-Group: IPNG End: Rfc: RFC2291 Title: Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web Authors: J. Slein, F. Vitali, E. Whitehead, D. Durand Status: Informational Date: 1998-02 Mailbox: slein@wrc.xerox.com, fabio@cs.unibo.it, ejw@ics.uci.edu, dgd@cs.bu.edu Pages: 21 Characters: 44036 Url: ftp://ds.internic.net/rfc/rfc2291.txt Description:: END_D Current World Wide Web (WWW or Web) standards provide simple support for applications which allow remote editing of typed data. In practice, the existing capabilities of the WWW have proven inadequate to support efficient, scalable remote editing free of overwriting conflicts. This document presents a list of features in the form of requirements for a Web Distributed Authoring and Versioning protocol which, if implemented, would improve the efficiency of common remote editing operations, provide a locking mechanism to prevent overwrite conflicts, improve link management support between non-HTML data types, provide a simple attribute-value metadata facility, provide for the creation and reading of container data types, and integrate versioning into the WWW. END_D Working-Group: WWW Distributed Authoring and Versioning End: Rfc: RFC2290 Title: Mobile-IPv4 Configuration Option for PPP IPCP Authors: J. Solomon, S. Glass Status: Proposed_Standard Date: 1998-02 Mailbox: solomon@comm.mot.com, glass@ftp.com Pages: 17 Characters: 39421 Updates: RFC2002 Url: ftp://ds.internic.net/rfc/rfc2290.txt Description:: END_D Mobile IP [RFC 2002] defines media-independent procedures by which a Mobile Node can maintain existing transport and application-layer connections despite changing its point-of-attachment to the Internet and without changing its IP address. PPP [RFC 1661] provides a standard method for transporting multi-protocol packets over point-to-point links. As currently specified, Mobile IP Foreign Agents which support Mobile Node connections via PPP can do so only by first assigning unique addresses to those Mobile Nodes, defeating one of the primary advantages of Foreign Agents. This documents corrects this problem by defining the Mobile-IPv4 Configuration Option to the Internet Protocol Control Protocol (IPCP) [RFC 1332]. Using this option, two peers can communicate their support for Mobile IP during the IPCP phase of PPP. Familiarity with Mobile IP [RFC 2002], IPCP [RFC 1332], and PPP [RFC 1661] is assumed. END_D Working-Group: Point-to-Point Protocol Extensions End: Rfc: RFC2288 Title: Using Existing Bibliographic Identifiers as Uniform Resource Names Authors: C. Lynch, C. Preston, R. Daniel Status: Informational Date: 1998-02 Mailbox: cliff@cni.org, cecilia@well.com, rdaniel@acl.lanl.gov Pages: 10 Characters: 21628 Url: ftp://ds.internic.net/rfc/rfc2288.txt Description:: END_D A system for Uniform Resource Names (URNs) must be capable of supporting identifiers from existing widely-used naming systems. This document discusses how three major bibliographic identifiers (the ISBN, ISSN and SICI) can be supported within the URN framework and the currently proposed syntax for URNs. END_D Working-Group: Uniform Resource Names End: Rfc: RFC2287 Title: Definitions of System-Level Managed Objects for Applications Authors: C. Krupczak, J. Saperia Status: Proposed_Standard Date: 1998-02 Mailbox: cheryl@empiretech.com, saperia@networks.bgs.com Pages: 44 Characters: 98210 Url: ftp://ds.internic.net/rfc/rfc2287.txt Description:: END_D 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 basic set of managed objects for fault, configuration and performance management of applications from a systems perspective. More specifically, the managed objects are restricted to information that can be determined from the system itself and which does not require special instrumentation within the applications to make the information available. END_D Working-Group: Application MIB End: Rfc: RFC2286 Title: Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128 Authors: J. Kapp Status: Informational Date: 1998-02 Mailbox: skapp@reapertech.com Pages: 7 Characters: 11849 Url: ftp://ds.internic.net/rfc/rfc2286.txt Description:: END_D This document provides two sets of test cases for HMAC-RIPEMD160 and HMAC-RIPEMD128, respectively. HMAC-RIPEMD160 and HMAC-RIPEMD128 are two constructs of the HMAC [HMAC] message authentication function using the RIPEMD-160 and RIPEMD-128 [RIPE] hash functions. The test cases and results provided in this document are meant to be used as a conformance test for HMAC-RIPEMD160 and HMAC-RIPEMD128 implementations. END_D End: Rfc: RFC2285 Title: Benchmarking Terminology for LAN Switching Devices Authors: R. Mandeville Status: Informational Date: 1998-02 Mailbox: bob.mandeville@eunet.fr Pages: 25 Characters: 43130 Url: ftp://ds.internic.net/rfc/rfc2285.txt Description:: END_D This document is intended to provide terminology for the benchmarking of local area network (LAN) switching devices. It extends the terminology already defined for benchmarking network interconnect devices in RFCs 1242 and 1944 to switching devices. END_D Working-Group: Benchmarking Methodology End: Rfc: RFC2284 Title: PPP Extensible Authentication Protocol (EAP) Authors: L. Blunk, J. Vollbrecht Status: Proposed_Standard Date: 1998-03 Mailbox: ljb@merit.edu, jrv@merit.edu Pages: 15 Characters: 29452 Keywords: PPP Url: ftp://ftp.isi.edu/rfc/rfc2284.txt Description:: END_D This document defines the PPP Extensible Authentication Protocol (EAP). The Link Establishment and Authentication phases, and the Authentication-Protocol Configuration Option, are defined in The Point-to-Point Protocol (PPP). END_D Working-Group: Point-to-Point Protocol Extensions End: Rfc: RFC2283 Title: Multiprotocol Extensions for BGP-4 Authors: T. Bates, R. Chandra, D. Katz, Y. Rekhter Status: Proposed_Standard Date: 1998-02 Mailbox: tbates@cisco.com, rchandra@cisco.com, dkatz@jnx.com, yakov@cisco.com Pages: 9 Characters: 18946 Url: ftp://ds.internic.net/rfc/rfc2283.txt Description:: END_D Currently BGP-4 [BGP-4] is capable of carrying routing information only for IPv4 [IPv4]. This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. END_D Working-Group: Inter-Domain Routing End: Rfc: RFC2282 Title: IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees Alias: BCP10 Authors: J. Galvin Status: Best_Current_Practice Date: 1998-02 Mailbox: galvin@elistx.com Pages: 14 Characters: 29852 Obsoletes: RFC2027 Url: ftp://ds.internic.net/rfc/rfc2282.txt Description:: END_D The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. The evolution of the process has relied principally on oral tradition as a means by which the lessons learned could be passed on to successive committees. This document is a self-consistent, organized compilation of the process as it is known today. END_D Working-Group: Process for Organization of Internet Standards ONg End: Rfc: RFC2281 Title: Cisco Hot Standby Router Protocol (HSRP) Authors: T. Li, B. Cole, P. Morton, D. Li Status: Informational Date: 1998-03 Mailbox: tli@juniper.net, cole@juniper.net, pmorton@cisco.com, dawnli@cisco.com Pages: 17 Characters: 35161 Url: ftp://ftp.isi.edu/in-notes/rfc2281.txt Description:: END_D The memo specifies the Hot Standby Router Protocol (HSRP). The goal of the protocol is to allow hosts to appear to use a single router and to maintain connectivity even if the actual first hop router they are using fails. Multiple routers participate in this protocol and in concert create the illusion of a single virtual router. The protocol insures that one and only one of the routers is forwarding packets on behalf of the virtual router. End hosts forward their packets to the virtual router. END_D End: Rfc: RFC2280 Title: Routing Policy Specification Language (RPSL) Authors: C. Alaettinoglu, T. Bates, E. Gerich, D. Karrenberg, D. Meyer, M. Terpstra, C. Villamizar Status: Proposed_Standard Date: 1998-01 Mailbox: cengiz@isi.edu, tbates@cisco.com, epg@home.net, dfk@ripe.net, meyer@antc.uoregon.edu, marten@BayNetworks.com, curtis@ans.net Pages: 53 Characters: 114985 Url: ftp://ds.internic.net/rfc/rfc2280.txt Description:: END_D This memo is the reference document for the 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. END_D Working-Group: Routing Policy System End: Rfc: RFC2279 Title: UTF-8, a transformation format of ISO 10646 Authors: F. Yergeau Status: Proposed_Standard Date: 1998-01 Mailbox: fyergeau@alis.com Pages: 10 Characters: 21634 Keywords: LDAP Obsoletes: RFC2044 Url: ftp://ds.internic.net/rfc/rfc2279.txt Description:: END_D ISO/IEC 10646-1 defines a multi-octet character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. Multi-octet characters, however, are not compatible with many current applications and protocols, and this has led to the development of a few so-called UCS transformation formats (UTF), each with different characteristics. UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo updates and replaces RFC 2044, in particular addressing the question of versions of the relevant standards. END_D End: Rfc: RFC2278 Title: IANA Charset Registration Procedures Alias: BCP19 Authors: N. Freed, J. Postel Status: Best_Current_Practice Date: 1998-01 Mailbox: ned.freed@innosoft.com, Postel@ISI.EDU Pages: 10 Characters: 18881 Url: ftp://ds.internic.net/rfc/rfc2278.txt Description:: END_D MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. In particular, the general applicability and appropriateness of a given registered charset is a protocol issue, not a registration issue, and is not dealt with by this registration procedure. END_D End: Rfc: RFC2277 Title: IETF Policy on Character Sets and Languages Alias: BCP18 Authors: H. Alvestrand Status: Best_Current_Practice Date: 1998-01 Mailbox: Harald.T.Alvestrand@uninett.no Pages: 9 Characters: 16622 Url: ftp://ds.internic.net/rfc/rfc2277.txt Description:: END_D This document is the current policies being applied by the Internet Engineering Steering Group (IESG) towards the standardization efforts in the Internet Engineering Task Force (IETF) in order to help Internet protocols fulfill these requirements. END_D End: Rfc: RFC2276 Title: Architectural Principles of Uniform Resource Name Resolution Authors: K. Sollins Status: Informational Date: 1998-01 Mailbox: sollins@lcs.mit.edu Pages: 24 Characters: 64811 Url: ftp://ds.internic.net/rfc/rfc2276.txt Description:: END_D This document addresses the issues of the discovery of URN (Uniform Resource Name) resolver services that in turn will directly translate URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource Characteristics). The document falls into three major parts, the assumptions underlying the work, the guidelines in order to be a viable Resolver Discovery Service or RDS, and a framework for designing RDSs. The guidelines fall into three principle areas: evolvability, usability, and security and privacy. An RDS that is compliant with the framework will not necessarily be compliant with the guidelines. Compliance with the guidelines will need to be validated separately. END_D Working-Group: Uniform Resource Names End: Rfc: RFC2275 Title: View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) Authors: B. Wijnen, R. Presuhn, K. McCloghrie Status: Proposed_Standard Date: 1998-01 Mailbox: wijnen@vnet.ibm.com, rpresuhn@bmc.com, kzm@cisco.com Pages: 36 Characters: 77998 Obsoletes: RFC2265 Url: ftp://ds.internic.net/rfc/rfc2275.txt Description:: END_D This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2271]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. END_D Working-Group: SNMPv 3 Obsoleted-by: RFC2575 End: Rfc: RFC2274 Title: User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) Authors: U. Blumenthal, B. Wijnen Status: Proposed_Standard Date: 1998-01 Mailbox: uri@watson.ibm.com, wijnen@vnet.ibm.com Pages: 76 Characters: 168950 Obsoletes: RFC2264 Url: ftp://ds.internic.net/rfc/rfc2274.txt Description:: END_D This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2271]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. END_D Working-Group: SNMPv 3 Obsoleted-by: RFC2574 End: Rfc: RFC2273 Title: SNMPv3 Applications Authors: D. Levi, P. Meyer, B. Stewart Status: Proposed_Standard Date: 1998-01 Mailbox: levi@snmp.com, paul_meyer@securecomputing.com, bstewart@cisco.com Pages: 70 Characters: 143754 Obsoletes: RFC2263 Url: ftp://ds.internic.net/rfc/rfc2273.txt Description:: END_D This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2271]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. END_D Working-Group: SNMPv 3 Obsoleted-by: RFC2573 End: Rfc: RFC2272 Title: Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) Authors: J. Case, D. Harrington, R. Presuhn, B. Wijnen Status: Proposed_Standard Date: 1998-01 Mailbox: case@snmp.com, dbh@ctron.com, rpresuhn@bmc.com, wijnen@vnet.ibm.com Pages: 39 Characters: 88445 Obsoletes: RFC2262 Url: ftp://ds.internic.net/rfc/rfc2272.txt Description:: END_D This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2271]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. END_D Working-Group: SNMPv 3 Obsoleted-by: RFC2572 End: Rfc: RFC2271 Title: An Architecture for Describing SNMP Management Frameworks Authors: D. Harrington, R. Presuhn, B. Wijnen Status: Proposed_Standard Date: 1998-01 Mailbox: dbh@ctron.com, rpresuhn@bmc.com, wijnen@vnet.ibm.com Pages: 56 Characters: 128227 Obsoletes: RFC2261 Url: ftp://ds.internic.net/rfc/rfc2271.txt Description:: END_D This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. The major portions of the architecture are an SNMP engine containing a Message Processing Subsystem, a Security Subsystem and an Access Control Subsystem, and possibly multiple SNMP applications which provide specific functional processing of management data. END_D Working-Group: SNMPv 3 Obsoleted-by: RFC2571 End: Rfc: RFC2270 Title: Using a Dedicated AS for Sites Homed to a Single Provider Authors: J. Stewart, T. Bates, R. Chandra, E. Chen Status: Informational Date: 1998-01 Mailbox: jstewart@isi.edu, tbates@cisco.com, rchandra@cisco.com, enkechen@cisco.com Pages: 6 Characters: 12063 Url: ftp://ds.internic.net/rfc/rfc2270.txt Description:: END_D With the increased growth of the Internet, the number of customers using BGP4 has grown significantly. RFC1930 outlines a set of guidelines for when one needs and should use an AS. However, the customer and service provider (ISP) are left with a problem as a result of this in that while there is no need for an allocated AS under the guidelines, certain conditions make the use of BGP4 a very pragmatic and perhaps only way to connect a customer homed to a single ISP. This paper proposes a solution to this problem in line with recommendations set forth in RFC1930. END_D Working-Group: Inter-Domain Routing End: Rfc: RFC2269 Title: Using the MARS Model in non-ATM NBMA Networks Authors: G. Armitage Status: Informational Date: 1998-01 Mailbox: gja@lucent.com Pages: 6 Characters: 12094 Url: ftp://ds.internic.net/rfc/rfc2269.txt Description:: END_D Initially developed for IP over ATM, the RFC 2022 (MARS) model is also applicable to other NBMA networks that provide the equivalent of switched, point to multipoint connections. This short document is intended to state the obvious equivalences, and explain the less obvious implications. No changes to the MARS model per se are suggested or required. RFC 2022 is not required over NBMA networks that offer Ethernet-like group addressing functionality. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2268 Title: A Description of the RC2(r) Encryption Algorithm Authors: R. Rivest Status: Informational Date: 1998-03 Mailbox: rsa-labs@rsa.com Pages: 11 Characters: 19048 Url: ftp://ftp.isi.edu/rfc/rfc2268.txt Keywords: Security Description:: END_D This memo describes a conventional (secret-key) block encryption algorithm, called RC2, which may be considered as a proposal for a DES replacement. The input and output block sizes are 64 bits each. The key size is variable, from one byte up to 128 bytes, although the current implementation uses eight bytes. The algorithm is designed to be easy to implement on 16-bit microprocessors. On an IBM AT, the encryption runs about twice as fast as DES (assuming that key expansion has been done). END_D End: Rfc: RFC2267 Title: Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing Authors: P. Ferguson, D. Senie Status: Informational Date: 1998-01 Mailbox: ferguson@cisco.com, dts@senie.com Pages: 10 Characters: 21032 Url: ftp://ds.internic.net/rfc/rfc2267.txt Description:: END_D Recent occurrences of various Denial of Service (DoS) attacks which have employed forged source addresses have proven to be a troublesome issue for Internet Service Providers and the Internet community overall. This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS attacks which use forged IP addresses to be propagated from 'behind' an Internet Service Provider's (ISP) aggregation point. END_D End: Rfc: RFC2266 Title: Definitions of Managed Objects for IEEE 802.12 Repeater Devices Authors: J. Flick Status: Proposed_Standard Date: 1998-01 Mailbox: johnf@hprnd.rose.hp.com Pages: 56 Characters: 134027 Url: ftp://ds.internic.net/rfc/rfc2266.txt Description:: END_D 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 network repeaters based on IEEE 802.12. END_D Working-Group: 100VG-AnyLAN MIB End: Rfc: RFC2265 Title: View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) Authors: B. Wijnen, R. Presuhn, K. McCloghrie Status: Proposed_Standard Date: 1998-01 Mailbox: wijnen@vnet.ibm.com, rpresuhn@bmc.com, kzm@cisco.com Pages: 36 Characters: 77807 Url: ftp://ds.internic.net/rfc/rfc2265.txt Description:: END_D This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. END_D Working-Group: SNMPv 3 Obsoleted-by: RFC2275 End: Rfc: RFC2264 Title: User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) Authors: U. Blumenthal, B. Wijnen Status: Proposed_Standard Date: 1998-01 Mailbox: uri@watson.ibm.com, wijnen@vnet.ibm.com Pages: 76 Characters: 168759 Url: ftp://ds.internic.net/rfc/rfc2264.txt Description:: END_D This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. END_D Working-Group: SNMPv 3 Obsoleted-by: RFC2274 End: Rfc: RFC2263 Title: SNMPv3 Applications Authors: D. Levi, P. Meyer, B. Stewart Status: Proposed_Standard Date: 1998-01 Mailbox: levi@snmp.com, paul_meyer@securecomputing.com, bstewart@cisco.com Pages: 70 Characters: 143493 Url: ftp://ds.internic.net/rfc/rfc2263.txt Description:: END_D This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2261]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. END_D Working-Group: SNMPv 3 Obsoleted-by: RFC2273 End: Rfc: RFC2262 Title: Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) Authors: J. Case, D. Harrington, R. Presuhn, B. Wijnen Status: Proposed_Standard Date: 1998-01 Mailbox: case@snmp.com, dbh@ctron.com, rpresuhn@bmc.com, wijnen@vnet.ibm.com Pages: 39 Characters: 88254 Url: ftp://ds.internic.net/rfc/rfc2262.txt Description:: END_D This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2261]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. END_D Working-Group: SNMPv 3 Obsoleted-by: RFC2272 End: Rfc: RFC2261 Title: An Architecture for Describing SNMP Management Frameworks Authors: D. Harrington, R. Presuhn, B. Wijnen Status: Proposed_Standard Date: 1998-01 Mailbox: dbh@ctron.com, rpresuhn@bmc.com, wijnen@vnet.ibm.com Pages: 56 Characters: 128036 Url: ftp://ds.internic.net/rfc/rfc2261.txt Description:: END_D This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. The major portions of the architecture are an SNMP engine containing a Message Processing Subsystem, a Security Subsystem and an Access Control Subsystem, and possibly multiple SNMP applications which provide specific functional processing of management data. END_D Working-Group: SNMPv 3 Working Obsoleted-by: RFC2271 End: Rfc: RFC2260 Title: Scalable Support for Multi-homed Multi-provider Connectivity Authors: T. Bates, Y. Rekhter Status: Informational Date: 1998-01 Mailbox: tbates@cisco.com, yakov@cisco.com Pages: 12 Characters: 28085 Url: ftp://ds.internic.net/rfc/rfc2260.txt Description:: END_D This document describes addressing and routing strategies for multi-homed enterprises attached to multiple Internet Service Providers (ISPs) that are intended to reduce the routing overhead due to these enterprises in the global Internet routing system. END_D End: Rfc: RFC2259 Title: Simple Nomenclator Query Protocol (SNQP) Authors: J. Elliott, J. Ordille Status: Informational Date: 1998-01 Mailbox: jim@apocalypse.org, joann@bell-labs.com Pages: 30 Characters: 58508 Url: ftp://ds.internic.net/rfc/rfc2259.txt Description:: END_D The Simple Nomenclator Query Protocol (SNQP) allows a client to communicate with a descriptive name service or other relational-style query service. The protocol is useful to services that search many data repositories for query responses. SNQP is an ASCII protocol in the request-reply style of SMTP. It was specifically designed for use with the Nomenclator name and information service, and has been useful elsewhere. END_D Working-Group: Integrated Directory Services End: Rfc: RFC2258 Title: Internet Nomenclator Project Authors: J. Ordille Status: Informational Date: 1998-01 Mailbox: joann@bell-labs.com Pages: 15 Characters: 34871 Url: ftp://ds.internic.net/rfc/rfc2258.txt Description:: END_D This document provides an overview of the Nomenclator system, describes how to register a CCSO server in the Internet Nomenclator Project, and how to use the Nomenclator search engine to find people on the Internet. END_D Working-Group: Integrated Directory Services End: Rfc: RFC2257 Title: Agent Extensibility (AgentX) Protocol Version 1 Authors: M. Daniele, B. Wijnen, D. Francisco, Ed. Status: Proposed_Standard Date: 1998-01 Mailbox: daniele@zk3.dec.com, wijnen@vnet.ibm.com, dfrancis@cisco.com Pages: 80 Characters: 177452 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2257.txt Description:: END_D This memo defines a standardized framework for extensible SNMP agents. It defines processing entities called master agents and subagents, a protocol (AgentX) used to communicate between them, and the elements of procedure by which the extensible agent processes SNMP protocol messages. END_D Working-Group: SNMP Agent Extensibility End: Rfc: RFC2256 Title: A Summary of the X.500(96) User Schema for use with LDAPv3 Authors: M. Wahl Status: Proposed_Standard Date: 1997-12 Mailbox: M.Wahl@critical-angle.com Pages: 20 Characters: 32377 Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc2256.txt Description:: END_D This document provides an overview of the attribute types and object classes defined by the ISO and ITU-T committees in the X.500 documents, in particular those intended for use by directory clients. This is the most widely used schema for LDAP/X.500 directories, and many other schema definitions for white pages objects use it as a basis. This document does not cover attributes used for the administration of X.500 directory servers, nor does it include attributes defined by other ISO/ITU-T documents. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2255 Title: The LDAP URL Format Authors: T. Howes, M. Smith Status: Proposed_Standard Date: 1997-12 Mailbox: howes@netscape.com, mcs@netscape.com Pages: 10 Characters: 20685 Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc2255.txt Description:: END_D LDAP is the Lightweight Directory Access Protocol, defined in [1], [2] and [3]. This document describes a format for an LDAP Uniform Resource Locator. The format describes an LDAP search operation to perform to retrieve information from an LDAP directory. This document replaces RFC 1959. It updates the LDAP URL format for version 3 of LDAP and clarifies how LDAP URLs are resolved. This document also defines an extension mechanism for LDAP URLs, so that future documents can extend their functionality, for example, to provide access to new LDAPv3 extensions as they are defined. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2254 Title: The String Representation of LDAP Search Filters, Authors: T. Howes Status: Proposed_Standard Date: 1997-12 Mailbox: howes@netscape.com Pages: 8 Characters: 13511 Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc2254.txt Description:: END_D The Lightweight Directory Access Protocol (LDAP) [1] defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2253 Title: Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names Authors: M. Wahl, S. Kille, T. Howes Status: Proposed_Standard Date: 1997-12 Mailbox: M.Wahl@critical-angle.com, S.Kille@isode.com, howes@netscape.com Pages: 10 Characters: 18226 Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc2253.txt Description:: END_D The X.500 Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1 in the X.500 Directory protocols. In the Lightweight Directory Access Protocol, a string representation of distinguished names is transferred. This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2252 Title: Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions Authors: M. Wahl, A. Coulbeck, T. Howes, S. Kille Status: Proposed_Standard Date: 1997-12 Mailbox: M.Wahl@critical-angle.com, A.Coulbeck@isode.com, howes@netscape.com, S.Kille@isode.com Pages: 32 Characters: 60204 Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc2252.txt Description:: END_D The Lightweight Directory Access Protocol (LDAP) [1] requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines a set of syntaxes for LDAPv3, and the rules by which attribute values of these syntaxes are represented as octet strings for transmission in the LDAP protocol. The syntaxes defined in this document are referenced by this and other documents that define attribute types. This document also defines the set of attribute types which LDAP servers should support. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2251 Title: Lightweight Directory Access Protocol (v3) Authors: M. Wahl, T. Howes, S. Kille Status: Proposed_Standard Date: 1997-12 Mailbox: M.Wahl@critical-angle.com, howes@netscape.com, S.Kille@isode.com Pages: 50 Characters: 114488 Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc2251.txt Description:: END_D The protocol described in this document is designed to provide access to directories supporting the X.500 models, while not incurring theresource requirements of the X.500 Directory Access Protocol (DAP). This protocol is specifically targeted at management applications and browser applications that provide read/write interactive access to directories. When used with a directory supporting the X.500 protocols, it is intended to be a complement to the X.500 DAP. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2250 Title: RTP Payload Format for MPEG1/MPEG2 Video Authors: D. Hoffman, G. Fernando, V. Goyal, M. Civanlar Status: Proposed_Standard Date: 1998-01 Mailbox: don.hoffman@eng.sun.com, gerard.fernando@eng.sun.com, goyal@precept.com, civanlar@research.att.com Pages: 16 Characters: 34293 Obsoletes: RFC2038 Url: ftp://ds.internic.net/rfc/rfc2250.txt Description:: END_D This memo describes a packetization scheme for MPEG video and audio streams. The scheme proposed can be used to transport such a video or audio flow over the transport protocols supported by RTP. Two approaches are described. The first is designed to support maximum interoperability with MPEG System environments. The second is designed to provide maximum compatibility with other RTP-encapsulated media streams and future conference control work of the IETF. END_D Working-Group: Audio/Video Transport End: Rfc: RFC2249 Title: Mail Monitoring MIB Authors: N. Freed, S. Kille Status: Proposed_Standard Date: 1998-01 Mailbox: ned.freed@innosoft.com, S.Kille@isode.com Pages: 28 Characters: 52334 Obsoletes: RFC1566 Keywords: SNMP, Mail Url: ftp://ds.internic.net/rfc/rfc2249.txt Description:: END_D This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Specifically, this memo extends the basic Network Services Monitoring MIB [8] to allow monitoring of Message Transfer Agents (MTAs). It may also be used to monitor MTA components within gateways. END_D Working-Group: Mail and Directory Management End: Rfc: RFC2248 Title: Network Services Monitoring MIB Authors: N. Freed, S. Kille Status: Proposed_Standard Date: 1998-01 Mailbox: ned.freed@innosoft.com, S.Kille@isode.com Pages: 19 Characters: 34107 Obsoletes: RFC1565 Url: ftp://ds.internic.net/rfc/rfc2248.txt Description:: END_D This MIB may be used on its own for any application, and for most simple applications this will suffice. This MIB is also designed to serve as a building block which can be used in conjunction with application-specific monitoring and management. END_D Working-Group: Mail and Directory Management End: Rfc: RFC2247 Title: Using Domains in LDAP/X.500 Distinguished Names Authors: S. Kille, M. Wahl, A. Grimstad, R. Huber, S. Sataluri Status: Proposed_Standard Date: 1998-01 Mailbox: S.Kille@ISODE.COM, M.Wahl@critical-angle.com, alg@att.com, rvh@att.com, sri@att.com Pages: 7 Characters: 12411 Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc2247.txt Description:: END_D This document defines an algorithm by which a name registered with the Internet Domain Name Service [2] can be represented as an LDAP distinguished name. END_D Working-Group: Access, Searching and Indexing of Directories End: Rfc: RFC2246 Title: The TLS Protocol Version 1.0 Authors: T. Dierks, C. Allen Status: Proposed_Standard Date: 1999-01 Mailbox: tdierks@certicom.com, callen@certicom.com Pages: 79 Characters: 170401 Keywords: Security I-D-Tag: draft-ietf-tls-protocol-06.txt Url: ftp://ftp.isi.edu/in-notes/rfc2246.txt Description:: END_D This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. END_D Working-Group: Transport Layer Security End: Rfc: RFC2245 Title: Anonymous SASL Mechanism Authors: C. Newman Status: Proposed_Standard Date: 1997-11 Mailbox: chris.newman@innosoft.com Pages: 5 Characters: 9974 Url: ftp://ds.internic.net/rfc/rfc2245.txt Description:: END_D It is common practice on the Internet to permit anonymous access to various services. Traditionally, this has been done with a plain text password mechanism using "anonymous" as the user name and optional trace information, such as an email address, as the password. As plaintext login commands are not permitted in new IETF protocols, a new way to provide anonymous login is needed within the context of the SASL [SASL] framework. END_D Working-Group: Application Configuration Access Protocol End: Rfc: RFC2244 Title: ACAP -- Application Configuration Access Protocol Authors: C. Newman, J. G. Myers Status: Proposed_Standard Date: 1997-11 Mailbox: chris.newman@innosoft.com, jgmyers@netscape.com Pages: 68 Characters: 154610 Url: ftp://ds.internic.net/rfc/rfc2244.txt Description:: END_D The Application Configuration Access Protocol (ACAP) is designed to support remote storage and access of program option, configuration and preference information. The data store model is designed to allow a client relatively simple access to interesting data, to allow new information to be easily added without server re-configuration, and to promote the use of both standardized data and custom or proprietary data. Key features include "inheritance" which can be used to manage default values for configuration settings and access control lists which allow interesting personal information to be shared and group information to be restricted. END_D Working-Group: Application Configuration Access Protocol End: Rfc: RFC2243 Title: OTP Extended Responses Authors: C. Metz Status: Proposed_Standard Date: 1997-11 Mailbox: cmetz@inner.net Pages: 10 Characters: 19730 Url: ftp://ds.internic.net/rfc/rfc2243.txt Description:: END_D This document provides a specification for a type of response to an OTP [RFC 1938] challenge that carries explicit indication of the response's encoding. Codings for the two mandatory OTP data formats using this new type of response are presented. This document also provides a specification for a response that allows an OTP generator to request that a server re-initialize a sequence and change parameters such as the secret pass phrase. END_D Working-Group: One Time Password End: Rfc: RFC2242 Title: NetWare/IP Domain Name and Information Authors: R. Droms, K. Fong Status: Proposed_Standard Date: 1997-11 Mailbox: droms@bucknell.edu, kfong@novell.com Pages: 6 Characters: 10653 Keywords: DHCP Url: ftp://ds.internic.net/rfc/rfc2242.txt Description:: END_D The Dynamic Host Configuration Protocol (DHCP) [RFC 2131] provides a framework for passing configuration information to hosts on a TCP/IP network. DHCP includes options for specific configuration parameters [RFC 2132]. This document defines options that carry NetWare/IP domain name and NetWare/IP sub-options to DHCP clients. END_D Working-Group: Dynamic Host Configuration (dhc) End: Rfc: RFC2241 Title: DHCP Options for Novell Directory Services Authors: D. Provan Status: Proposed_Standard Date: 1997-11 Mailbox: donp@Novell.Com Pages: 5 Characters: 8419 Keywords: DHCP Url: ftp://ds.internic.net/rfc/rfc2241.txt Description:: END_D This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. The first option carries a list of NDS servers. The second option carries the name of the client's NDS tree. The third carries the initial NDS context. These three options provide an NDS client with enough information to connect to an NDS tree without manual configuration of the client. END_D Working-Group: Dynamic Hosts Configuration (dhc) End: Rfc: RFC2240 Title: A Legal Basis for Domain Name Allocation Authors: O. Vaughan Status: Informational Date: 1997-11 Mailbox: owain@vaughan.com Pages: 7 Characters: 13602 Url: ftp://ds.internic.net/rfc/rfc2240.txt Description:: END_D The purpose of this memo is to focus discussion on the particular problems with the exhaustion of the top level domain space in the Internet and the possible conflicts that can occur when multiple organisations are vying for the same name. No proposed solutions in this document are intended as standards for the Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to such problems, leading eventually to the adoption of standards. END_D Obsoleted-by: RFC2352 End: Rfc: RFC2239 Title: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 Authors: K. de Graaf, D. Romascanu, D. McMaster, K. McCloghrie, S. Roberts Status: Proposed_Standard Date: 1997-11 Mailbox: kdegraaf@isd.3com.com, dromasca@madge.com,mcmaster@cisco.com, kzm@cisco.com, sroberts@farallon.com Pages: 43 Characters: 80651 Url: ftp://ds.internic.net/rfc/rfc2239.txt Description:: END_D This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing 10 and 100 Mb/second Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, "10 & 100 Mb/s Management," October 26, 1995. END_D Working-Group: IEEE 802.3 Hub MIB End: Rfc: RFC2238 Title: Definitions of Managed Objects for HPR using SMIv2 Authors: B. Clouston, B. Moore (Editors) Status: Proposed_Standard Date: 1997-11 Mailbox: clouston@cisco.com, remoore@ralvm6.vnet.ibm.com Pages: 35 Characters: 65498 Url: ftp://ds.internic.net/rfc/rfc2238.txt Description:: END_D 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 network devices with HPR (High Performance Routing) capabilities. This memo identifies managed objects for the HPR protocol. END_D Working-Group: SNA NAU Services MIB End: Rfc: RFC2237 Title: Japanese Character Encoding for Internet Messages Authors: K. Tamaru Status: Informational Date: 1997-11 Mailbox: kenzat@microsoft.com Pages: 6 Characters: 11628 Url: ftp://ds.internic.net/rfc/rfc2237.txt Description:: END_D This memo defines an encoding scheme for the Japanese Characters, describes "ISO-2022-JP-1", which is used in electronic mail [RFC-822], and network news [RFC 1036]. Also this memo provides a listing of the Japanese Character Set that can be used in this encoding scheme. END_D End: Rfc: RFC2236 Title: Internet Group Management Protocol, Version 2 Authors: W. Fenner Status: Proposed_Standard Date: 1997-11 Mailbox: fenner@parc.xerox.com Pages: 24 Characters: 51048 Updates: RFC1112 Url: ftp://ds.internic.net/rfc/rfc2236.txt Description:: END_D This memo documents IGMPv2, used by IP hosts to report their multicast group memberships to routers. It updates STD 5, RFC 1112. IGMPv2 allows group membership termination to be quickly reported to the routing protocol, which is important for high-bandwidth multicast groups and/or subnets with highly volatile group membership. END_D Working-Group: Inter-Domain Multicast Routing End: Rfc: RFC2235 Title: Hobbes' Internet Timeline Authors: R. Zakon Status: Informational Date: 1997-11 Mailbox: zakon@info.isoc.org Pages: 22 Characters: 43060 Alias: FYI32 Url: ftp://ds.internic.net/rfc/rfc2235.txt Description:: END_D This document presents a history of the Internet in timeline fashion, highlighting some of the key events and technologies which helped shape the Internet as we know it today. A growth summary of the Internet and some associated technologies is also included. END_D End: Rfc: RFC2234 Title: Augmented BNF for Syntax Specifications: ABNF Authors: D. Crocker, Ed., P. Overell Status: Proposed_Standard Date: 1997-11 Mailbox: dcrocker@imc.org, paulo@turnpike.com Pages: 14 Characters: 24265 Url: ftp://ds.internic.net/rfc/rfc2234.txt Description:: END_D Internet technical specifications often need to define a format syntax and are free to employ whatever notation their authors deem useful. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. It balances compactness and simplicity, with reasonable representational power. In the early days of the Arpanet, each specification contained its own definition of ABNF. This included the email specifications, RFC733 and then RFC822 which have come to be the common citations for defining ABNF. The current document separates out that definition, to permit selective reference. END_D Working-Group: Detailed Revision/Update of Message Standards End: Rfc: RFC2233 Title: The Interfaces Group MIB using SMIv2 Authors: K. McCloghrie, F. Kastenholz Status: Proposed_Standard Date: 1997-11 Mailbox: kzm@cisco.com, kasten@ftp.com Pages: 66 Characters: 148033 Url: ftp://ds.internic.net/rfc/rfc2233.txt Description:: END_D 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 managed objects used for managing Network Interfaces. END_D Working-Group: Interfaces MIB End: Rfc: RFC2232 Title: Definitions of Managed Objects for DLUR using SMIv2 Authors: B. Clouston, B. Moore, Editors Status: Proposed_Standard Date: 1997-11 Mailbox: clouston@cisco.com, remoore@ralvm6.vnet.ibm.com Pages: 21 Characters: 37955 Url: ftp://ds.internic.net/rfc/rfc2232.txt Description:: END_D 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 network devices with DLUR (Dependent LU Requester) capabilities. This memo identifies managed objects for the DLUR protocol. END_D Working-Group: SNA NAU Services MIB End: Rfc: RFC2231 Title: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations Authors: N. Freed, K. Moore Status: Proposed_Standard Date: 1997-11 Mailbox: ned.freed@innosoft.com, moore@cs.utk.edu Pages: 10 Characters: 19280 Updates: RFC2045, RFC2047, RFC2183 Obsoletes: RFC2184 Url: ftp://ds.internic.net/rfc/rfc2231.txt Description:: END_D This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. This memo also defines an extension to the encoded words defined in RFC 2047 to allow the specification of the language to be used for display as well as the character set. END_D End: Rfc: RFC2230 Title: Key Exchange Delegation Record for the DNS Authors: R. Atkinson Status: Informational Date: 1997-11 Mailbox: atkinson@itd.nrl.navy.mil Pages: 11 Characters: 25563 Url: ftp://ds.internic.net/rfc/rfc2230.txt Description:: END_D This note describes a mechanism whereby authorisation for one node to act as key exchanger for a second node is delegated and made available via the Secure DNS. This mechanism is intended to be used only with the Secure DNS. It can be used with several security services. For example, a system seeking to use IP Security [RFC-1825, RFC-1826, RFC-1827] to protect IP packets for a given destination can use this mechanism to determine the set of authorised remote key exchanger systems for that destination. END_D End: Rfc: RFC2229 Title: A Dictionary Server Protocol Authors: R. Faith, B. Martin Status: Informational Date: 1997-10 Mailbox: faith@cs.unc.edu, bamartin@miranda.org Pages: 30 Characters: 59551 Url: ftp://ds.internic.net/rfc/rfc2229.txt Description:: END_D The Dictionary Server Protocol (DICT) is a TCP transaction based query/response protocol that allows a client to access dictionary definitions from a set of natural language dictionary databases. END_D End: Rfc: RFC2228 Authors: M. Horowitz, S. Lunt. Title: FTP Security Extensions Date: 1997-10 Format: TXT=85127 bytes Status: Proposed_Standard Keywords: Security Url: ftp://ds.internic.net/rfc/rfc2228.txt End: Rfc: RFC2227 Authors: J. Mogul, P. Leach. Title: Simple Hit-Metering and Usage-Limiting for HTTP Mailbox: mogul@wrl.dec.com, paulle@microsoft.com Pages: 37 Date: 1997-10 Format: TXT=85127 bytes Keywords: Web Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2227.txt Description:: END_D This document proposes a simple extension to HTTP, using a new "Meter" header, which permits a limited form of demographic information (colloquially called "hit-counts") to be reported by caches to origin servers, in a more efficient manner than the "cache-busting" techniques currently used. It also permits an origin server to control the number of times a cache uses a cached response, and outlines a technique that origin servers can use to capture referral information without "cache-busting." END_D Working-Group: HyperText Transfer Protocol End: Rfc: RFC2226 Authors: T. Smith, G. Armitage Title: IP Broadcast over ATM Networks Date: 1997-10 Format: TXT=30661 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2226.txt Description:: END_D This memo describes how the IP multicast service being developed by the IP over ATM working group may be used to support IP broadcast transmission. The solution revolves around treating the broadcast problem as a special case of multicast, where every host in the subnet or cluster is a member of the group. END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2225 Title: Classical IP and ARP over ATM Authors: M. Laubach, J. Halpern Status: Proposed_Standard Date: 1998-04 Mailbox: laubach@com21.com, jhalpern@Newbridge.com Pages: 28 Characters: 65779 Obsoletes: RFC1626, RFC1577 Url: ftp://ftp.isi.edu/in-notes/rfc2225.txt Description:: END_D This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS). END_D Working-Group: Internetworking Over NBMA End: Rfc: RFC2224 Authors: B. Callaghan Title: NFS URL Scheme Date: 1997-10 Format: TXT=22726 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2224.txt End: Rfc: RFC2223 Authors: J. Postel, J. Reynolds Title: Instructions to RFC Authors Date: 1997-10 Format: TXT=37948 bytes Obsoletes: RFC1543, RFC1111, RFC825 Keywords: Standards Status: Informational Url: ftp://ds.internic.net/rfc/rfc2223.txt End: Rfc: RFC2222 Title: Simple Authentication and Security Layer (SASL) Authors: J. Myers Status: Proposed_Standard Date: 1997-10 Mailbox: jgmyers@netscape.com Pages: 16 Characters: 35010 Url: ftp://ds.internic.net/rfc/rfc2222.txt Description:: END_D This document describes a method for adding authentication support to connection-based protocols. To use this specification, a protocol includes a command for identifying and authenticating a user to a server and for optionally negotiating protection of subsequent protocol interactions. If its use is negotiated, a security layer is inserted between the protocol and the connection. This document describes how a protocol specifies such a command, defines several mechanisms for use by the command, and defines the protocol used for carrying a negotiated security layer over the connection. END_D End: Rfc: RFC2221 Authors: M. Gahrns Title: IMAP4 Login Referrals Date: 1997-10 Format: TXT=9251 bytes Keywords: IMAP Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2221.txt End: Rfc: RFC2220 Authors: R. Guenther Mailbox: rgue@loc.gov Title: The Application/MARC Content-type Date: 1997-10 Format: TXT Characters: 7075 Pages: 4 Status: Informational Description:: END_D This memorandum provides a mechanism for representing objects which are files of Machine-Readable Cataloging records (MARC). The MARC formats are standards for the representation and communication of bibliographic and related information. A MARC record contains metadata for an information resource following MARC format specifications. END_D Url: ftp://ds.internic.net/rfc/rfc2220.txt End: Rfc: RFC2219 Authors: M. Hamilton, R. Wright Title: Use of DNS Aliases for Network Services Date: 1997-10 Format: TXT=17858 bytes Keywords: DNS Status: Best_Current_Practice Url: ftp://ds.internic.net/rfc/rfc2219.txt End: Rfc: RFC2218 Authors: T. Genovese, B. Jennings Title: A Common Schema for the Internet White Pages Service Date: 1997-10 Format: TXT=16258 bytes Status: Proposed_Standard Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc2218.txt End: Rfc: RFC2217 Authors: G. Clark Title: Telnet Com Port Control Option Date: 1997-10 Format: TXT=31664 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2217.txt End: Rfc: RFC2216 Authors: S. Shenker, J. Wroclawski Title: Network Element Service Specification Template Date: 1997-09 Format: TXT=53655 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2216.txt End: Rfc: RFC2215 Authors: S. Shenker, J. Wroclawski Title: General Characterization Parameters for Integrated Service Network Elements Date: 1997-09 Format: TXT=39552 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2215.txt End: Rfc: RFC2214 Authors: F. Baker, J. Krawczyk, A. Sastry Title: Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2 Date: 1997-09 Format: TXT=15971 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2214.txt End: Rfc: RFC2213 Authors: F. Baker, J. Krawczyk, A. Sastry Title: Integrated Services Management Information Base using SMIv2 Date: 1997-09 Format: TXT=36147 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2213.txt End: Rfc: RFC2212 Authors: S. Shenker, C. Partridge, R. Guerin Title: Specification of Guaranteed Quality of Service Date: 1997-09 Format: TXT=52330 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2212.txt End: Rfc: RFC2211 Authors: J. Wroclawski Title: Specification of the Controlled-Load Network Element Service Date: 1997-09 Format: TXT=46523 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2211.txt End: Rfc: RFC2210 Authors: J. Wroclawski Title: The Use of RSVP with IETF Integrated Services Date: 1997-09 Format: TXT=77613 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2210.txt End: Rfc: RFC2209 Authors: R. Braden, L. Zhang Title: Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules Date: 1997-09 Format: TXT=51690 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2209.txt End: Rfc: RFC2208 Authors: A. Mankin, Ed., F. Baker, B. Braden, S. Bradner, M. O`Dell, A. Romanow, A. Weinrib, L. Zhang Title: Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on Deployment Date: 1997-09 Format: TXT=14289 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2208.txt End: Rfc: RFC2207 Authors: L. Berger, T. O'Malley Title: RSVP Extensions for IPSEC Data Flows Date: 1997-09 Format: TXT=30473 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2207.txt End: Rfc: RFC2206 Authors: F. Baker, J. Krawczyk, A. Sastry Title: RSVP Management Information Base using SMIv2 Date: 1997-09 Format: TXT=112937 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2206.txt End: Rfc: RFC2205 Authors: R. Braden, Ed., L. Zhang, S. Berson, S. Herzog, S. Jamin Title: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification Date: 1997-09 Format: TXT=223974 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2205.txt End: Rfc: RFC2204 Authors: D. Nash Title: ODETTE File Transfer Protocol Date: 1997-09 Format: TXT=151857 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2204.txt End: Rfc: RFC2203 Authors: M. Eisler, A. Chiu, L. Ling Title: RPCSEC_GSS Protocol Specification Date: 1997-09 Format: TXT=50937 bytes Keywords: Security Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2203.txt End: Rfc: RFC2202 Authors: P. Cheng, R. Glenn Title: Test Cases for HMAC-MD5 and HMAC-SHA-1 Date: 1997-09 Format: TXT=11945 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2202.txt End: Rfc: RFC2201 Authors: A. Ballardie Title: Core Based Trees (CBT) Multicast Routing Architecture Date: 1997-09 Format: TXT=38040 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2201.txt End: Rfc: RFC2200 Authors: J. Postel Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1997-06 Format: TXT=94506 bytes Obsoletes: RFC2000, RFC1920, RFC1880, RFC1800 Status: Standard Url: ftp://ds.internic.net/rfc/rfc2200.txt Obsoleted-by: RFC2300,RFC2400 End: Rfc: RFC2199 Title: Request for Comments Summary RFC Numbers 2100-2199 Authors: A. Ramos Status: Informational Date: 1998-01 Mailbox: ramos@isi.edu Pages: 23 Characters: 47664 Url: ftp://ds.internic.net/rfc/rfc2199.txt Description:: END_D This RFC is a slightly annotated list of the 100 RFCs from RFC 2100 through RFCs 2199. This is a status report on these RFCs. END_D End: Rfc: RFC2198 Authors: C. Perkins, I. Kouvelas, O. Hodson, V. Hardman, M. Handley, J.C. Bolot, A. Vega-Garcia, S. Fosse-Parisis Title: RTP Payload for Redundant Audio Data Date: 1997-09 Format: TXT=25166 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2198.txt End: Rfc: RFC2197 Authors: N. Freed Title: SMTP Service Extension for Command Pipelining Date: 1997-09 Format: TXT=15003 bytes Keywords: Mail,SMTP Obsoletes: RFC1854 Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2197.txt End: Rfc: RFC2196 Authors: B. Fraser Title: Site Security Handbook Date: 1997-09 Keywords: Security Format: TXT=191772 bytes Obsoletes: RFC1244 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2196.txt End: Rfc: RFC2195 Authors: J. Klensin, R. Catoe, P. Krumviede Title: IMAP/POP AUTHorize Extension for Simple Challenge/Response Date: 1997-09 Format: TXT=10468 bytes Obsoletes: RFC2095 Keywords: IMAP Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2195.txt End: Rfc: RFC2194 Authors: B. Aboba, J. Lu, J. Alsop, J., Ding, W. Wang Title: Review of Roaming Implementations Date: 1997-09 Format: TXT=81533 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2194.txt End: Rfc: RFC2193 Authors: M. Gahrns Title: IMAP4 Mailbox Referrals Date: 1997-09 Format: TXT=16248 bytes Keywords: IMAP Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2193.txt End: Rfc: RFC2192 Authors: C. Newman Title: IMAP URL Scheme Date: 1997-09 Format: TXT=31426 bytes Keywords: IMAP Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2192.txt End: Rfc: RFC2191 Authors: G. Armitage Title: VENUS - Very Extensive Non-Unicast Service Date: 1997-09 Format: TXT=31316 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2191.txt End: Rfc: RFC2190 Authors: 263 Video Streams. C. Zhu Title: RTP Payload Format for H Date: 1997-09 Format: TXT=26409 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2190.txt End: Rfc: RFC2189 Authors: A. Ballardie Title: Core Based Trees (CBT version 2) Multicast Routing Date: 1997-09 Format: TXT=52043 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2189.txt End: Rfc: RFC2188 Authors: 2. M. Banan, M. Taylor, and J. Cheng Title: AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1 Date: 1997-09 Format: TXT=118374 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2188.txt End: Rfc: RFC2187 Authors: D. Wessels, K. Claffy Title: Application of Internet Cache Protocol (ICP), version 2 Date: 1997-09 Format: TXT=51662 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2187.txt End: Rfc: RFC2186 Authors: D. Wessels, K. Claffy Title: Internet Cache Protocol (ICP), version 2 Date: 1997-09 Format: TXT=18808 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2186.txt End: Rfc: RFC2185 Authors: R. Callon, D. Haskin Title: Routing Aspects of IPv6 Transition Date: 1997-09 Format: TXT=31281 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2185.txt End: Rfc: RFC2184 Authors: N. Freed, K. Moore Title: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations Date: 1997-08 Format: TXT=17635 bytes Keywords: Mail Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2184.txt Obsoleted-by: RFC2231 End: Rfc: RFC2183 Authors: R. Troost, S. Dorner, K. Moore Title: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field Date: 1997-08 Format: TXT=23150 bytes Keywords: Mail Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2183.txt End: Rfc: RFC2182 Authors: R. Elz, R. Bush, S. Bradner, M. Patton Title: Selection and Operation of Secondary DNS Servers Date: 1997-07 Format: TXT=27456 bytes Keywords: DNS Status: Best_Current_Practice Url: ftp://ds.internic.net/rfc/rfc2182.txt End: Rfc: RFC2181 Authors: R. Elz, R. Bush Title: Clarifications to the DNS Specification Date: 1997-07 Format: TXT=36989 bytes Keywords: DNS Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2181.txt End: Rfc: RFC2180 Authors: M. Gahrns Title: IMAP4 Multi-Accessed Mailbox Practice Date: 1997-07 Format: TXT=24750 bytes Keywords: IMAP Status: Informational Url: ftp://ds.internic.net/rfc/rfc2180.txt End: Rfc: RFC2179 Authors: A. Gwinn Title: Network Security For Trade Shows Date: 1997-07 Format: TXT=20690 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2179.txt End: Rfc: RFC2178 Authors: J. Moy Title: OSPF Version 2 Date: 1997-07 Format: TXT=495866 bytes Obsoletes: RFC1583 Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2178.txt Obsoleted-by: RFC2328 End: Rfc: RFC2177 Authors: B. Leiba Title: IMAP4 IDLE command Date: 1997-06 Format: TXT=6770 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2177.txt End: Rfc: RFC2176 Authors: K. Murakami, M. Maruyama Title: IPv4 over MAPOS Version 1 Date: 1997-06 Format: TXT=12305 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2176.txt End: Rfc: RFC2175 Authors: K. Murakami, M. Maruyama Title: MAPOS 16 - Multiple Access Protocol over SONET/SDH with 16 Bit Addressing Date: 1997-06 Format: TXT=11677 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2175.txt End: Rfc: RFC2174 Authors: K. Murakami, M. Maruyama Title: A MAPOS version 1 Extension - Switch-Switch Protocol Date: 1997-06 Format: TXT=47967 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2174.txt End: Rfc: RFC2173 Authors: K. Murakami, M. Maruyama Title: A MAPOS version 1 Extension - Node Switch Protocol Date: 1997-06 Format: TXT=12251 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2173.txt End: Rfc: RFC2172 Authors: M. Maruyama, K. Murakami Title: MAPOS Version 1 Assigned Numbers Date: 1997-06 Format: TXT=4857 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2172.txt End: Rfc: RFC2171 Authors: K. Murakami, M. Maruyama Title: MAPOS - Multiple Access Protocol over SONET/SDH Version 1 Date: 1997-06 Format: TXT=17480 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2171.txt End: Rfc: RFC2170 Authors: W. Almesberger, J. Le Boudec, P. Oechslin Title: Application REQuested IP over ATM (AREQUIPA) Date: 1997-06 Format: TXT=22874 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2170.txt End: Rfc: RFC2169 Authors: R. Danie1 Title: A Trivial Convention for using HTTP in URN Resolution Date: 1997-06 Format: TXT=17763 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2169.txt End: Rfc: RFC2168 Authors: R. Danie1, M. Mealling Title: Resolution of Uniform Resource Identifiers using the Domain Name System Date: 1997-06 Format: TXT=46528 bytes Status: Experimental Keywords: DNS Url: ftp://ds.internic.net/rfc/rfc2168.txt End: Rfc: RFC2167 Authors: S. Williamson, M. Kosters, D. Blacka, J. Singh, K. Zeilstra Title: Referral Whois (RWhois) Protocol V1.5 Date: 1997-06 Format: TXT=136355 bytes Obsoletes: RFC1714 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2167.txt End: Rfc: RFC2166 Authors: 0 Enhancements. D. Bryant, P. Brittain Title: APPN Implementer's Workshop Closed Pages Document DLSw v2 Date: 1997-06 Format: TXT=75527 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2166.txt End: Rfc: RFC2165 Authors: J. Veizades, E. Guttman, C. Perkins, S. Kaplan Title: Service Location Protocol Date: 1997-06 Format: TXT=169889 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2165.txt End: Rfc: RFC2164 Title: Use of an X.500/LDAP directory to support MIXER address mapping Authors: S. Kille Status: Proposed_Standard Date: 1998-01 Mailbox: S.Kille@ISODE.COM Pages: 10 Characters: 16701 Keywords: LDAP Obsoletes: RFC1838 Url: ftp://ds.internic.net/rfc/rfc2164.txt Description:: END_D This specification defines how to represent and maintain these mappings (MIXER Conformant Global Address Mappings of MCGAMs) in an X.500 or LDAP directory. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2163 Title: Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM) Authors: C. Allocchio Status: Proposed_Standard Date: 1998-01 Mailbox: Claudio.Allocchio@elettra.trieste.it Pages: 26 Characters: 58789 Obsoletes: RFC1664 Url: ftp://ds.internic.net/rfc/rfc2163.txt Description:: END_D This memo is the complete technical specification to store in the Internet Domain Name System (DNS) the mapping information (MCGAM) needed by MIXER conformant e-mail gateways and other tools to map RFC822 domain names into X.400 O/R names and vice versa. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2162 Title: MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mail Authors: C. Allocchio Status: Experimental Date: 1998-01 Mailbox: Claudio.Allocchio@elettra.Trieste.it Pages: 34 Characters: 58553 Obsoletes: RFC1405 Url: ftp://ds.internic.net/rfc/rfc2162.txt Description:: END_D This document describes a set of mappings which will enable inter working between systems operating the ISO/IEC 10021 - CCITT (now ITU) X.400 Recommendations on Message Handling Systems, and systems running the Mail-11 (also known as DECnet mail or VMSmail) protocol. The specifications are valid both within DECnet Phase IV and DECnet/OSI addressing and routing scheme. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2161 Title: A MIME Body Part for ODA Authors: H. Alvestrand Status: Experimental Date: 1998-01 Mailbox: Harald.T.Alvestrand@uninett.no Pages: 5 Characters: 8009 Url: ftp://ds.internic.net/rfc/rfc2161.txt Description:: END_D This document contains the definitions, originally contained in RFC 1495 and RFC 1341, on how to carry ODA in MIME, and how to translate it to its X.400 representation. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2160 Title: Carrying PostScript in X.400 and MIME Authors: H. Alvestrand Status: Proposed_Standard Date: 1998-01 Mailbox: Harald.T.Alvestrand@uninett.no Pages: 5 Characters: 7059 Url: ftp://ds.internic.net/rfc/rfc2160.txt Description:: END_D This document describes methods for carrying PostScript information in the two standard mail systems MIME and X.400, and the conversion between them. It uses the notational conventions of [BODYMAP], and the conversion is further described in [MIXER]. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2159 Title: A MIME Body Part for FAX Authors: H. Alvestrand Status: Proposed_Standard Date: 1998-01 Mailbox: Harald.T.Alvestrand@uninett.no Pages: 7 Characters: 11471 Url: ftp://ds.internic.net/rfc/rfc2159.txt Description:: END_D This document contains the definitions, originally contained in RFC 1494, on how to carry CCITT G3Fax in MIME, and how to translate it to its X.400 representation. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2158 Title: X.400 Image Body Parts Authors: H. Alvestrand Status: Proposed_Standard Date: 1998-01 Mailbox: Harald.T.Alvestrand@uninett.no Pages: 4 Characters: 5547 Url: ftp://ds.internic.net/rfc/rfc2158.txt Description:: END_D This document contains the body parts defined in RFC 1495 for carrying image formats that were originally defined in MIME through an X.400 system. It also documents the OIDs assigned to these data formats as FTAM body parts, which allow the MIME types to be converted to FTAM body parts; this will probably be more useful than the new body parts defined here. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2157 Title: Mapping between X.400 and RFC-822/MIME Message Bodies Authors: H. Alvestrand Status: Proposed_Standard Date: 1998-01 Mailbox: Harald.T.Alvestrand@uninett.no Pages: 49 Characters: 92554 Url: ftp://ds.internic.net/rfc/rfc2157.txt Description:: END_D This document defines how to map body parts of X.400 messages into MIME entities and vice versa, including the handling of multipart messages and forwarded messages. END_D Working-Group: MIME - X.400 Gateway End: Rfc: RFC2156 Authors: S. Kille Title: MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME Status: Proposed_Standard Date: 1998-01 Mailbox: S.Kille@ISODE.COM Pages: 144 Characters: 280385 Obsoletes: RFC0987,RFC1026,RFC1138,RFC1148,RFC1327,RFC1945 Updates: RFC0822 Url: ftp://ds.internic.net/rfc/rfc2156.txt Description:: END_D This document relates primarily to the ITU-T 1988 and 1992 X.400 Series Recommendations / ISO IEC 10021 International Standard. This ISO/ITU-T standard is referred to in this document as "X.400", which is a convenient shorthand. Any reference to the 1984 Recommendations will be explicit. Any mappings relating to elements which are in the 1992 version and not in the 1988 version will be noted explicitly. X.400 defines an Interpersonal Messaging System (IPMS), making use of a store and forward Message Transfer System. This document relates to the IPMS, and not to wider application of X.400, such as EDI as defined in X.435. END_D End: Rfc: RFC2155 Authors: B. Clouston, B. Moore Title: Definitions of Managed Objects for APPN using SMIv2 Date: 1997-06 Format: TXT=213809 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2155.txt Obsoleted-by: RFC2455 End: Rfc: RFC2154 Authors: S. Murphy, M. Badger, B. Wellington Title: OSPF with Digital Signatures Date: 1997-06 Format: TXT=72701 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2154.txt End: Rfc: RFC2153 Authors: W. Simpson Title: PPP Vendor Extensions Date: 1997-05 Format: TXT=10780 bytes Status: Informational Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc2153.txt End: Rfc: RFC2152 Authors: D. Goldsmith, M. Davis Title: UTF-7 A Mail-Safe Transformation Format of Unicode Date: 1997-05 Format: TXT=28065 bytes Obsoletes: RFC1642 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2152.txt End: Rfc: RFC2151 Authors: G. Kessler, S. Shepard Title: A Primer On Internet and TCP/IP Tools and Utilities Date: 1997-06 Format: TXT=114130 bytes Obsoletes: RFC1739 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2151.txt End: Rfc: RFC2150 Authors: J. Max, W. Stickle Title: Humanities and Arts: Sharing Center Stage on the Internet Date: 1997-10 Format: TXT=154037 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2150.txt End: Rfc: RFC2149 Authors: R. Talpade, M. Ammar Title: Multicast Server Architectures for MARS-based ATM multicasting Date: 1997-05 Format: TXT=42007 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2149.txt End: Rfc: RFC2148 Authors: H. Alvestrand, P. Jurg Title: Deployment of the Internet White Pages Service Date: 1997-09 Format: TXT=31539 bytes Status: Best_Current_Practice Url: ftp://ds.internic.net/rfc/rfc2148.txt End: Rfc: RFC2147 Authors: D. Borman Title: TCP and UDP over IPv6 Jumbograms Date: 1997-05 Format: TXT=1883 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2147.txt End: Rfc: RFC2146 Authors: Federal Networking Council Title: U.S. Government Internet Domain Names Date: 1997-05 Format: TXT=26564 bytes Keywords: DNS Obsoletes: RFC1816 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2146.txt End: Rfc: RFC2145 Authors: J. C. Mogul, R. Fielding, J. Gettys, H. Frystyk Title: Use and Interpretation of HTTP Version Numbers Date: 1997-05 Format: TXT=13659 bytes Status: Informational Keywords: Web Url: ftp://ds.internic.net/rfc/rfc2145.txt End: Rfc: RFC2143 Authors: B. Elliston Title: Encapsulating IP with the Small Computer System Interface Date: 1997-05 Format: TXT=10749 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2143.txt End: Rfc: RFC2142 Authors: D. Crocker Title: Mailbox Names for Common Services, Roles and Functions Date: 1997-05 Format: TXT=12195 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2142.txt End: Rfc: RFC2141 Authors: R. Moats Title: URN Syntax Date: 1997-05 Format: TXT=14077 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2141.txt End: Rfc: RFC2140 Authors: J. Touch Title: TCP Control Block Interdependence Date: 1997-04 Format: TXT=26032 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2140.txt End: Rfc: RFC2139 Authors: C. Rigney Title: RADIUS Accounting Date: 1997-04 Format: TXT=44919 bytes Obsoletes: RFC2059 Status: Informational Keywords: Security Url: ftp://ds.internic.net/rfc/rfc2139.txt End: Rfc: RFC2138 Authors: C. Rigney, A. Rubens, W. Simpson, S. Willens Title: Remote Authentication Dial In User Service (RADIUS) Date: 1997-04 Format: TXT=120407 bytes Obsoletes: RFC2058 Status: Proposed_Standard Keywords: Security Url: ftp://ds.internic.net/rfc/rfc2138.txt End: Rfc: RFC2137 Authors: D. Eastlake Title: Secure Domain Name System Dynamic Update Date: 1997-04 Format: TXT=24824 bytes Status: Proposed_Standard Keywords: DNS,Security Url: ftp://ds.internic.net/rfc/rfc2137.txt End: Rfc: RFC2136 Authors: P. Vixie, Ed., S. Thomson, Y. Rekhter, J. Bound Title: Dynamic Updates in the Domain Name System (DNS UPDATE) Date: 1997-04 Format: TXT=56354 bytes Keywords: DNS Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2136.txt End: Rfc: RFC2135 Authors: ISOC Board of Trustees Title: Internet Society By-Laws Date: 1997-04 Format: TXT=20467 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2135.txt End: Rfc: RFC2134 Authors: ISOC Board of Trustees Title: Articles of Incorporation of Internet Society Date: 1997-04 Format: TXT=9131 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2134.txt End: Rfc: RFC2133 Authors: R. Gilligan, S. Thomson, J. Bound, W. Stevens Title: Basic Socket Interface Extensions for IPv6 Date: 1997-04 Format: TXT=69737 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2133.txt Obsoleted-by: RFC2553 End: Rfc: RFC2132 Authors: S. Alexander, R. Droms Title: DHCP Options and BOOTP Vendor Extensions Date: 1997-03 Format: TXT=63670 bytes Keywords: DHCP Obsoletes: RFC1533 Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2132.txt End: Rfc: RFC2131 Authors: R. Droms Title: Dynamic Host Configuration Protocol Date: 1997-03 Format: TXT=113738 bytes Keywords: DHCP Obsoletes: RFC1541 Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2131.txt End: Rfc: RFC2130 Authors: C. Weider, C. Preston, K. Simonsen, H. Alvestrand, R. Atkinson, M. Crispin, P. Svanberg Title: The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996 Date: 1997-04 Format: TXT=63443 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2130.txt End: Rfc: RFC2129 Authors: K. Nagami, Y. Katsube, Y. Shobatake, A. Mogi, S. Matsuzawa, T. Jinmei, H. Esaki Title: Toshiba's Flow Attribute Notification Protocol (FANP) Specification Date: 1997-04 Format: TXT=41137 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2129.txt End: Rfc: RFC2128 Authors: G. Roeck Title: Dial Control Management Information Base using SMIv2 Date: 1997-03 Format: TXT=66153 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2128.txt End: Rfc: RFC2127 Authors: G. Roeck Title: ISDN Management Information Base using SMIv2 Date: 1997-03 Format: TXT=95994 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2127.txt End: Rfc: RFC2126 Authors: Y. Pouffary, A. Young Title: ISO Transport Service on top of TCP (ITOT) Date: 1997-03 Format: TXT=51032 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2126.txt End: Rfc: RFC2125 Authors: C. Richards, K. Smith Title: The PPP Bandwidth Allocation Protocol (BAP) / The PPP Bandwidth Allocation Control Protocol (BACP) Date: 1997-03 Format: TXT=49213 bytes Status: Proposed_Standard Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc2125.txt End: Rfc: RFC2124 Authors: 0. P. Amsden, J. Amweg, P. Calato, S. Bensley, G. Lyons Title: Cabletron's Light-weight Flow Admission Protocol Specification Version 1 Date: 1997-03 Format: TXT=47912 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2124.txt End: Rfc: RFC2123 Authors: N. Brownlee Title: Traffic Flow Measurement: Experiences with NeTraMet Date: 1997-03 Format: TXT=81874 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2123.txt End: Rfc: RFC2122 Authors: D. Mavrakis, H. Layec, K. Kartmann Title: VEMMI URL Specification Date: 1997-03 Format: TXT=25043 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2122.txt End: Rfc: RFC2121 Authors: G. Armitage Title: Issues affecting MARS Cluster Size Date: 1997-03 Format: TXT=26781 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2121.txt End: Rfc: RFC2120 Authors: 500 Root Naming Context. D. Chadwick Title: Managing the X Date: 1997-03 Format: TXT=30773 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2120.txt End: Rfc: RFC2119 Authors: S. Bradner Title: Key words for use in RFCs to Indicate Requirement Level Date: 1997-03 Format: TXT=4723 bytes Status: Best_Current_Practice Url: ftp://ds.internic.net/rfc/rfc2119.txt End: Rfc: RFC2118 Authors: G. Pall Title: Microsoft Point-To-Point Compression (MPPC) Protocol Date: 1997-03 Format: TXT=17443 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2118.txt End: Rfc: RFC2117 Authors: D. Estrin, D. Farinacci, A. Helmy, D. Thaler, S. Deering, M. Handley, V. Jacobson, C. Liu, P. Sharma, L. Wei Title: Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification Date: 1997-06 Format: TXT=151886 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2117.txt Obsoleted-by: RFC2362 End: Rfc: RFC2116 Authors: C. Apple, K. Rossen Title: X.500 Implementations Catalog-96 Date: 1997-04 Format: TXT=243994 bytes Obsoletes: RFC1632 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2116.txt End: Rfc: RFC2115 Authors: C. Brown, F. Baker Title: Management Information Base for Frame Relay DTEs Using SMIv2 Date: 1997-09 Format: TXT=59950 bytes Obsoletes: RFC1315 Keywords: SNMP Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2115.txt End: Rfc: RFC2114 Authors: S. Chiang, J. Lee, H. Yasuda Title: Data Link Switching Client Access Protocol Date: 1997-02 Format: TXT=50872 bytes Obsoletes: RFC2106 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2114.txt End: Rfc: RFC2113 Authors: D. Katz Title: IP Router Alert Option Date: 1997-02 Format: TXT=7924 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2113.txt End: Rfc: RFC2112 Authors: E. Levinson Title: The MIME Multipart/Related Content-type Date: 1997-02 Format: TXT=17052 bytes Obsoletes: RFC1872 Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2112.txt Obsoleted-by: RFC2387 End: Rfc: RFC2111 Authors: E. Levinson Title: Content-ID and Message-ID Uniform Resource Locators Date: 1997-02 Format: TXT=9099 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2111.txt Obsoleted-by: RFC2392 End: Rfc: RFC2110 Authors: J. Palme, A. Hopmann Title: MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML) Date: 1997-03 Format: TXT=41961 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2110.txt Obsoleted-by: RFC2557 End: Rfc: RFC2109 Authors: D. Kristol, L. Montulli Title: HTTP State Management Mechanism Date: 1997-02 Format: TXT=43469 bytes Obsoletes: RFC1920 Status: Proposed_Standard Keywords: Web Url: ftp://ds.internic.net/rfc/rfc2109.txt End: Rfc: RFC2108 Authors: K. de Graaf, D. Romascanu, D. McMaster, K. McCloghrie Title: Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2 Date: 1997-02 Format: TXT=166336 bytes Obsoletes: RFC1516 Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2108.txt End: Rfc: RFC2107 Authors: K. Hamzeh Title: Ascend Tunnel Management Protocol - ATMP Date: 1997-02 Format: TXT=44300 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2107.txt End: Rfc: RFC2106 Authors: S. Chiang, J. Lee, H. Yasuda Title: Data Link Switching Remote Access Protocol Date: 1997-02 Format: TXT=40819 bytes Obsoleted-by: RFC2114 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2106.txt End: Rfc: RFC2105 Authors: Y. Rekhter, B. Davie, D. Katz, E. Rosen, G. Swallow Title: Cisco Systems' Tag Switching Architecture Overview Date: 1997-02 Format: TXT=33013 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2105.txt End: Rfc: RFC2104 Authors: H. Krawczyk, M. Bellare, R. Canetti Title: HMAC: Keyed-Hashing for Message Authentication Date: 1997-02 Format: TXT=22297 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2104.txt End: Rfc: RFC2103 Authors: R. Ramanathan Title: Mobility Support for Nimrod : Challenges and Solution Approaches Date: 1997-02 Format: TXT=41352 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2103.txt End: Rfc: RFC2102 Authors: R. Ramanathan Title: Multicast Support for Nimrod : Requirements and Solution Approaches Date: 1997-02 Format: TXT=50963 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2102.txt End: Rfc: RFC2101 Authors: B. Carpenter, J. Crowcroft, Y. Rekhter Title: IPv4 Address Behaviour Today Date: 1997-02 Format: TXT=31407 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2101.txt End: Rfc: RFC2100 Authors: J. Ashworth Title: The Naming of Hosts Date: 1997-04 Format: TXT=4077 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2100.txt End: Rfc: RFC2099 Authors: J. Elliott Title: Request for Comments Summary RFC Numbers 2000-2099 Date: 1997-03 Format: TXT=40763 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2099.txt End: Rfc: RFC2098 Authors: Y. Katsube, K. Nagami, H. Esaki Title: Toshiba's Router Architecture Extensions for ATM : Overview Date: 1997-02 Format: TXT=43622 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2098.txt End: Rfc: RFC2097 Authors: G. Pall Title: The PPP NetBIOS Frames Control Protocol (NBFCP) Date: 1997-01 Format: TXT=27104 bytes Status: Proposed_Standard Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc2097.txt End: Rfc: RFC2096 Authors: F. Baker Title: IP Forwarding Table MIB Date: 1997-01 Format: TXT=1354 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2096.txt End: Rfc: RFC2095 Authors: J. Klensin, R. Catoe, P. Krumviede Title: IMAP/POP AUTHorize Extension for Simple Challenge/Response Date: 1997-01 Format: TXT=10446 bytes Obsoleted-by: RFC2195 Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2095.txt End: Rfc: RFC2094 Authors: H. Harney, C. Muckenhirn Title: Group Key Management Protocol (GKMP) Architecture Date: 1997-07 Format: TXT=53097 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2094.txt End: Rfc: RFC2093 Authors: H. Harney, C. Muckenhirn Title: Group Key Management Protocol (GKMP) Specification Date: 1997-07 Format: TXT=48678 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2093.txt End: Rfc: RFC2092 Authors: S. Sherry, G. Meyer Title: Protocol Analysis for Triggered RIP Date: 1997-01 Format: TXT=10865 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2092.txt End: Rfc: RFC2091 Authors: G. Meyer, S. Sherry Title: Triggered Extensions to RIP to Support Demand Circuits Date: 1997-01 Format: TXT=44835 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2091.txt End: Rfc: RFC2090 Authors: A. Emberson Title: TFTP Multicast Option Date: 1997-02 Format: TXT=11857 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2090.txt End: Rfc: RFC2089 Authors: B. Wijnen, D. Levi Title: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent Date: 1997-01 Format: TXT=23814 bytes Status: Informational Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2089.txt End: Rfc: RFC2088 Authors: J. Myers Title: IMAP4 non-synchronizing literals Date: 1997-01 Format: TXT=4052 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2088.txt End: Rfc: RFC2087 Authors: J. Myers Title: IMAP4 QUOTA extension Date: 1997-01 Format: TXT=8542 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2087.txt End: Rfc: RFC2086 Authors: J. Myers Title: IMAP4 ACL extension Date: 1997-01 Format: TXT=13925 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2086.txt End: Rfc: RFC2085 Authors: M. Oehler, R. Glenn Title: HMAC-MD5 IP Authentication with Replay Prevention Date: 1997-02 Format: TXT=13399 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2085.txt End: Rfc: RFC2084 Authors: G. Bossert, S. Cooper, W. Drummond Title: Considerations for Web Transaction Security Date: 1997-01 Format: TXT=9022 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2084.txt End: Rfc: RFC2083 Authors: T. Boutell Title: PNG (Portable Network Graphics) Specification Date: 1997-01 Format: TXT=242528 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2083.txt End: Rfc: RFC2082 Authors: F. Baker, R. Atkinson Title: RIP-2 MD5 Authentication Date: 1997-01 Format: TXT=25436 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2082.txt End: Rfc: RFC2081 Authors: G. Malkin Title: RIPng Protocol Applicability Statement Date: 1997-01 Format: TXT=6821 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2081.txt End: Rfc: RFC2080 Authors: G. Malkin, R. Minnear Title: RIPng for IPv6 Date: 1997-01 Format: TXT=47534 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2080.txt End: Rfc: RFC2079 Authors: M. Smith Title: Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs) Date: 1997-01 Format: TXT=8757 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2079.txt End: Rfc: RFC2078 Authors: J. Linn Title: Generic Security Service Application Program Interface, Version 2 Date: 1997-01 Format: TXT=185990 bytes Obsoletes: RFC1508 Keywords: Security Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2078.txt End: Rfc: RFC2077 Authors: S. Nelson, C. Parks, Mitra Title: The Model Primary Content Type for Multipurpose Internet Mail Extensions Date: 1997-01 Format: TXT=30158 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2077.txt End: Rfc: RFC2076 Authors: J. Palme Title: Common Internet Message Headers Date: 1997-02 Format: TXT=47639 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2076.txt End: Rfc: RFC2075 Authors: C. Partridge Title: IP Echo Host Service Date: 1997-01 Format: TXT=12536 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2075.txt End: Rfc: RFC2074 Authors: A. Bierman, R. Iddon Title: Remote Network Monitoring MIB Protocol Identifiers Date: 1997-01 Format: TXT=81262 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2074.txt End: Rfc: RFC2073 Authors: Y. Rekhter, P. Lothberg, R. Hinden, S. Deering, J. Postel Title: An IPv6 Provider-Based Unicast Address Format Date: 1997-01 Format: TXT=15549 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2073.txt Obsoleted-by: RFC2374 End: Rfc: RFC2072 Authors: H. Berkowitz Title: Router Renumbering Guide Date: 1997-01 Format: TXT=110591 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2072.txt End: Rfc: RFC2071 Authors: P. Ferguson, H. Berkowitz Title: Network Renumbering Overview: Why would I want it and what is it anyway? Date: 1997-01 Format: TXT=33218 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2071.txt End: Rfc: RFC2070 Authors: F. Yergeau, G. Nicol, G. Adams, M. Duerst Title: Internationalization of the Hypertext Markup Language Date: 1997-01 Format: TXT=91887 bytes Status: Proposed_Standard Keywords: Web Url: ftp://ds.internic.net/rfc/rfc2070.txt End: Rfc: RFC2069 Authors: J. Franks, P. Hallam-Baker, J. Hostetler, P. Leach, A. Luotonen, E. Sink, L. Stewart Title: An Extension to HTTP : Digest Access Authentication Date: 1997-01 Format: TXT=41733 bytes Status: Proposed_Standard Keywords: Web Url: ftp://ds.internic.net/rfc/rfc2069.txt Obsoleted-by: RFC2617 End: Rfc: RFC2068 Authors: 1. R. Fielding, J. Gettys, J. Mogul, H. Frystyk, T. Berners-Lee Title: Hypertext Transfer Protocol -- HTTP/1 Date: 1997-01 Format: TXT=378114 bytes Status: Proposed_Standard Keywords: Web Url: ftp://ds.internic.net/rfc/rfc2068.txt Obsoleted-by: RFC2616 End: Rfc: RFC2067 Authors: J. Renwick Title: IP over HIPPI Date: 1997-01 Format: TXT=66702 bytes Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2067.txt End: Rfc: RFC2066 Authors: R. Gellens Title: TELNET CHARSET Option Date: 1997-01 Format: TXT=26088 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2066.txt End: Rfc: RFC2065 Authors: D. Eastlake, 3rd, C. Kaufman Title: Domain Name System Security Extensions Date: 1997-01 Format: TXT=97718 bytes Keywords: DNS Obsoletes: RFC1034,RFC1035 Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2065.txt Obsoleted-by: RFC2535 End: Rfc: RFC2064 Authors: N. Brownlee Title: Traffic Flow Measurement: Meter MIB Date: 1997-01 Format: TXT=67520 bytes Status: Experimental Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2064.txt End: Rfc: RFC2063 Authors: N. Brownlee, C. Mills, G. Ruth Title: Traffic Flow Measurement: Architecture Date: 1997-01 Format: TXT=89092 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2063.txt End: Rfc: RFC2062 Authors: M. Crispin Title: Internet Message Access Protocol - Obsolete Syntax Date: 1996-12 Format: TXT=14222 bytes Status: Proposed_Standard Keywords: IMAP Url: ftp://ds.internic.net/rfc/rfc2062.txt End: Rfc: RFC2061 Authors: M. Crispin Title: IMAP4 COMPATIBILITY WITH IMAP2BIS Date: 1996-12 Format: TXT=5867 bytes Obsoletes: RFC1730 Status: Informational Keywords: IMAP Url: ftp://ds.internic.net/rfc/rfc2061.txt End: Rfc: RFC2060 Authors: M. Crispin Title: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 Date: 1996-12 Format: TXT=166513 bytes Obsoletes: RFC1730 Status: Proposed_Standard Keywords: IMAP Url: ftp://ds.internic.net/rfc/rfc2060.txt End: Rfc: RFC2059 Authors: C. Rigney Title: RADIUS Accounting Date: 1997-01 Format: TXT=44237 bytes Obsoleted-by: RFC2139 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2059.txt End: Rfc: RFC2058 Authors: C. Rigney, A. Rubens, W. Simpson, S. Willens Title: Remote Authentication Dial In User Service (RADIUS) Date: 1997-01 Format: TXT=118880 bytes Obsoleted-by: RFC2138 Status: Proposed_Standard Keywords: Security Url: ftp://ds.internic.net/rfc/rfc2058.txt End: Rfc: RFC2057 Authors: S. Bradner Title: Source Directed Access Control on the Internet Date: 1996-11 Format: TXT=56664 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2057.txt End: Rfc: RFC2056 Authors: 50. R. Denenberg, J. Kunze, D. Lynch Title: Uniform Resource Locators for Z39 Date: 1996-11 Format: TXT=14204 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2056.txt End: Rfc: RFC2055 Authors: B. Callaghan Title: WebNFS Server Specification Date: 1996-10 Format: TXT=20498 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2055.txt End: Rfc: RFC2054 Authors: B. Callaghan Title: WebNFS Client Specification Date: 1996-10 Format: TXT=36354 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2054.txt End: Rfc: RFC2053 Authors: E. Der-Danieliantz Title: The AM (Armenia) Domain Date: 1996-10 Format: TXT=4128 bytes Status: Informational Keywords: DNS Url: ftp://ds.internic.net/rfc/rfc2053.txt End: Rfc: RFC2052 Authors: A. Gulbrandsen, P. Vixie Title: A DNS RR for specifying the location of services (DNS SRV) Date: 1996-10 Format: TXT=19257 bytes Keywords: DNS Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2052.txt End: Rfc: RFC2051 Authors: M. Allen, B. Clouston, Z. Kielczewski, W. Kwan, B. Moore Title: Definitions of Managed Objects for APPC using SMIv2 Date: 1996-10 Format: TXT=239359 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2051.txt End: Rfc: RFC2050 Authors: K. Hubbard, M. Kosters, D. Conrad, D. Karrenberg, J. Postel Title: INTERNET REGISTRY IP ALLOCATION GUIDELINES Date: 1996-11 Format: TXT=28975 bytes Status: Best_Current_Practice Url: ftp://ds.internic.net/rfc/rfc2050.txt End: Rfc: RFC2049 Authors: N. Freed & N. Borenstein Title: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples Date: 1996-11 Format: TXT=51207 bytes Obsoletes: RFC1521,RFC1522,RFC1590 Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2049.txt End: Rfc: RFC2048 Authors: N. Freed, J. Klensin & J. Postel Title: Multipurpose Internet Mail Extension (MIME) Part Four: Registration Procedures Date: 1996-11 Format: TXT=45033 bytes Obsoletes: RFC1521,RFC1522,RFC1590 Status: Best_Current_Practice Url: ftp://ds.internic.net/rfc/rfc2048.txt End: Rfc: RFC2047 Authors: K. Moore Title: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text Date: 1996-11 Format: TXT=33262 bytes Obsoletes: RFC1521, RFC1522, RFC1590 Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2047.txt End: Rfc: RFC2046 Authors: N. Freed & N. Borenstein Title: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types Date: 1996-11 Format: TXT=105854 bytes Obsoletes: RFC1521,RFC1522,RFC1590 Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2046.txt End: Rfc: RFC2045 Authors: N. Freed & N. Borenstein Title: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies Date: 1996-11 Format: TXT=72932 bytes Obsoletes: RFC1521,RFC1522,RFC1590 Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc2045.txt End: Rfc: RFC2044 Authors: F. Yergeau Title: UTF-8, a transformation format of Unicode and ISO 10646 Date: 1996-10 Format: TXT=11932 bytes Status: Informational Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc2044.txt Obsoleted-by: RFC2279 End: Rfc: RFC2043 Authors: A. Fuqua Title: The PPP SNA Control Protocol (SNACP) Date: 1996-10 Format: TXT=13719 bytes Status: Proposed_Standard Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc2043.txt End: Rfc: RFC2042 Authors: B. Manning Title: Registering New BGP Attribute Types Date: 1997-01 Format: TXT=4001 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2042.txt End: Rfc: RFC2041 Authors: B. Noble, G. Nguyen, M. Satyanarayanan, R. Katz Title: Mobile Network Tracing Date: 1996-12 Format: TXT=64688 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2041.txt End: Rfc: RFC2040 Authors: R. Baldwin, R. Rivest Title: The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms Date: 1996-10 Format: TXT=54598 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2040.txt End: Rfc: RFC2039 Authors: C. Kalbfleisch Title: Applicablity of Standards Track MIBs to Management of World Wide Web Servers Date: 1996-11 Format: TXT=31966 bytes Status: Informational Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2039.txt End: Rfc: RFC2038 Authors: D. Hoffman, G. Fernando, V. Goyal Title: RTP Payload Format for MPEG1/MPEG2 Video Date: 1996-10 Format: TXT=23266 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2038.txt End: Rfc: RFC2037 Authors: K. McCloghrie, A. Bierman Title: Entity MIB using SMIv2 Date: 1996-10 Format: TXT=74362 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2037.txt End: Rfc: RFC2036 Authors: G. Huston Title: Observations on the use of Components of the Class A Address Space within the Internet Date: 1996-10 Format: TXT=20743 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2036.txt End: Rfc: RFC2035 Authors: L. Berc, W. Fenner, R. Frederick, S. McCanne Title: RTP Payload Format for JPEG-compressed Video Date: 1996-10 Format: TXT=30079 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2035.txt Obsoleted-by: RFC2435 End: Rfc: RFC2034 Authors: N. Freed Title: SMTP Service Extension for Returning Enhanced Error Codes Date: 1996-10 Format: TXT=10460 bytes Status: Proposed_Standard Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc2034.txt End: Rfc: RFC2033 Authors: J. Myers Title: Local Mail Transfer Protocol Date: 1996-10 Format: TXT=14711 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2033.txt End: Rfc: RFC2032 Authors: 261 Video Streams. T. Turletti, C. Huitema Title: RTP Payload Format for H Date: 1996-10 Format: TXT=27488 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2032.txt End: Rfc: RFC2031 Authors: E. Huizer Title: IETF-ISOC relationship Date: 1996-10 Format: TXT=8816 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2031.txt End: Rfc: RFC2030 Authors: D. Mills Title: Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI Date: 1996-10 Format: TXT=48620 bytes Obsoletes: RFC1769 Status: Informational Url: ftp://ds.internic.net/rfc/rfc2030.txt End: Rfc: RFC2029 Authors: M. Speer, D. Hoffman Title: RTP Payload Format of Sun's CellB Video Encoding Date: 1996-10 Format: TXT=11216 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2029.txt End: Rfc: RFC2028 Authors: R. Hovey, S. Bradner Title: The Organizations Involved in the IETF Standards Process Date: 1996-10 Format: TXT=13865 bytes Status: Best_Current_Practice Keywords: Standards Url: ftp://ds.internic.net/rfc/rfc2028.txt End: Rfc: RFC2027 Authors: J. Galvin Title: IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees Date: 1996-10 Format: TXT=24207 bytes Status: Best_Current_Practice Url: ftp://ds.internic.net/rfc/rfc2027.txt Obsoleted-by: RFC2282 End: Rfc: RFC2026 Authors: S. Bradner Title: The Internet Standards Process -- Revision 3 Date: 1996-10 Format: TXT=86731 bytes Obsoletes: RFC1602 Status: Best_Current_Practice Keywords: Standards Url: ftp://ds.internic.net/rfc/rfc2026.txt End: Rfc: RFC2025 Authors: C. Adams Title: The Simple Public-Key GSS-API Mechanism (SPKM) Date: 1996-10 Format: TXT=101692 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2025.txt End: Rfc: RFC2024 Authors: D. Chen, P. Gayek, S. Nix Title: Definitions of Managed Objects for Data Link Switching using SMIv2 Date: 1996-10 Format: TXT=173952 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2024.txt End: Rfc: RFC2023 Authors: D. Haskin, E. Allen Title: IP Version 6 over PPP Date: 1996-10 Format: TXT=20275 bytes Status: Proposed_Standard Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc2023.txt Obsoleted-by: RFC2472 End: Rfc: RFC2022 Authors: 0/3.1 based ATM Networks. G. Armitage Title: Support for Multicast over UNI 3 Date: 1996-11 Format: TXT=189219 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2022.txt End: Rfc: RFC2021 Authors: S. Waldbusser Title: Remote Network Monitoring Management Information Base Version 2 using SMIv2 Date: 1997-01 Format: TXT=262223 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2021.txt End: Rfc: RFC2020 Authors: J. Flick Title: IEEE 802.12 Interface MIB Date: 1996-10 Format: TXT=72135 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2020.txt End: Rfc: RFC2019 Authors: M. Crawford Title: Transmission of IPv6 Packets Over FDDI Date: 1996-10 Format: TXT=12344 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2019.txt Obsoleted-by: RFC2467 End: Rfc: RFC2018 Authors: M. Mathis, J. Mahdavi, S. Floyd, A. Romanow Title: TCP Selective Acknowledgement Options Date: 1996-10 Format: TXT=25671 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2018.txt End: Rfc: RFC2017 Authors: N. Freed, K. Moore, A. Cargille Title: Definition of the URL MIME External-Body Access-Type Date: 1996-10 Format: TXT=9000 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2017.txt End: Rfc: RFC2016 Authors: L. Daigle, P. Deutsch, B. Heelan, C. Alpaugh, M. Maclachlan Title: Uniform Resource Agents (URAs) Date: 1996-10 Format: TXT=38355 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2016.txt End: Rfc: RFC2015 Authors: M. Elkins Title: MIME Security with Pretty Good Privacy (PGP) Date: 1996-10 Format: TXT=14223 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2015.txt End: Rfc: RFC2014 Authors: A. Weinrib, J. Postel Title: IRTF Research Group Guidelines and Procedures Date: 1996-10 Format: TXT=27507 bytes Status: Best_Current_Practice Url: ftp://ds.internic.net/rfc/rfc2014.txt End: Rfc: RFC2013 Authors: K. McCloghrie Title: SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2 Date: 1996-11 Format: TXT=9333 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2013.txt End: Rfc: RFC2012 Authors: K. McCloghrie Title: SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2 Date: 1996-11 Format: TXT=16792 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2012.txt End: Rfc: RFC2011 Authors: K. McCloghrie Title: SNMPv2 Management Information Base for the Internet Protocol using SMIv2 Date: 1996-11 Format: TXT=31168 bytes Status: Proposed_Standard Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc2011.txt End: Rfc: RFC2010 Authors: B. Manning, P. Vixie Title: Operational Criteria for Root Name Servers Date: 1996-10 Format: TXT=14870 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2010.txt End: Rfc: RFC2009 Authors: T. Imielinski, J. Navas Title: GPS-Based Addressing and Routing Date: 1996-11 Format: TXT=66229 bytes Status: Experimental Url: ftp://ds.internic.net/rfc/rfc2009.txt End: Rfc: RFC2008 Authors: Y. Rekhter, T. Li Title: Implications of Various Address Allocation Policies for Internet Routing Date: 1996-10 Format: TXT=34717 bytes Status: Best_Current_Practice Url: ftp://ds.internic.net/rfc/rfc2008.txt End: Rfc: RFC2007 Authors: J. Foster, M. Isaacs & M. Prior Title: Catalogue of Network Training Materials Date: 1996-10 Format: TXT=78941 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc2007.txt End: Rfc: RFC2006 Authors: D. Cong, M. Hamlen, C. Perkins Title: The Definitions of Managed Objects for IP Mobility Support using SMIv2 Date: 1996-10 Format: TXT=95030 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2006.txt End: Rfc: RFC2005 Authors: J. Solomon Title: Applicability Statement for IP Mobility Support Date: 1996-10 Format: TXT=10509 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2005.txt End: Rfc: RFC2004 Authors: C. Perkins Title: Minimal Encapsulation within IP Date: 1996-10 Format: TXT=12202 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2004.txt End: Rfc: RFC2003 Authors: C. Perkins Title: IP Encapsulation within IP Date: 1996-10 Format: TXT=30291 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2003.txt End: Rfc: RFC2002 Authors: C. Perkins Title: IP Mobility Support Date: 1996-10 Format: TXT=193103 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2002.txt End: Rfc: RFC2001 Authors: W. Stevens Title: TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms Date: 1997-01 Format: TXT=12981 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc2001.txt Obsoleted-by: RFC2581 End: Rfc: RFC2000 Authors: J. Postel, Editor Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1997-02 Format: TXT=121356 bytes Obsoletes: RFC1920 Obsoleted-by: RFC2200,RFC2300,RFC2400 Status: Historic Url: ftp://ds.internic.net/rfc/rfc2000.txt End: Rfc: RFC1999 Authors: J. Elliott Title: Request for Comments Summary RFC Numbers 1900-1999 Date: 1997-01 Format: TXT=39819 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc1999.txt End: Rfc: RFC1998 Authors: E. Chen & T. Bates Title: An Application of the BGP Community Attribute in Multi-home Routing Date: 1996-08 Format: TXT=16953 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc1998.txt End: Rfc: RFC1997 Authors: R. Chandra, P. Traina & T. Li Title: BGP Communities Attribute Date: 1996-08 Format: TXT=8275 bytes Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc1997.txt End: Rfc: RFC1996 Authors: P. Vixie Title: A Mechanism for Prompt Notification of Zone Changes (DNS Date: 1996-08 Format: TXT=15247 bytes Keywords: DNS Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc1996.txt End: Rfc: RFC1995 Authors: M. Ohta Title: Incremental Zone Transfer in DNS Date: 1996-08 Format: TXT=16810 bytes Keywords: DNS Status: Proposed_Standard Url: ftp://ds.internic.net/rfc/rfc1995.txt End: Rfc: RFC1994 Authors: W. Simpson Title: PPP Challenge Handshake Authentication Protocol (CHAP) Date: 1996-08 Format: TXT=24094 bytes Obsoletes: RFC1334 Keywords: PPP Status: Draft_Standard Url: ftp://ds.internic.net/rfc/rfc1994.txt End: Rfc: RFC1993 Authors: A. Barbir, D. Carr & W. Simpson Title: PPP Gandalf FZA Compression Protocol Date: 1996-08 Format: TXT=9811 bytes Status: Informational Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1993.txt End: Rfc: RFC1992 Authors: I. Castineyra, N. Chiappa, M. Steenstrup Title: The Nimrod Routing Architecture Date: 1996-08 Format: TXT=59848 bytes Status: Informational Url: ftp://ds.internic.net/rfc/rfc1992.txt End: Rfc: RFC1991 Status: Informational Authors: D. Atkins, W. Stallings, P. Zimmermann, Title: PGP Message Exchange Formats Date: 1996-08-16 Pages: 21 Format: .txt Keywords: Mail Url: ftp://ds.internic.net/rfc/rfc1991.txt End: Rfc: RFC1990 Status: Draft_Standard Authors: K. Sklower, B. Lloyd, G. McGregor, D. Carr, T. Coradetti, Title: The PPP Multilink Protocol (MP) Date: 1996-08-16 Pages: 24 Format: .txt Obsoletes: RFC1717 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1990.txt End: Rfc: RFC1989 Status: Draft_Standard Authors: W. Simpson, Title: PPP Link Quality Monitoring Date: 1996-08-16 Pages: 16 Format: .txt Obsoletes: RFC1333 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1989.txt End: Rfc: RFC1988 Status: Informational Authors: G. McAnally, D. Gilbert, J. Flick, Title: Conditional Grant of Rights to Specific Hewlett-Packard Patents In Conjunction With the Internet Engineering Task Force's Internet-Standard Network Management Framework Date: 1996-08-16 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1988.txt End: Rfc: RFC1987 Status: Informational Authors: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Liaw, T. G. Minshall, Title: Ipsilon's General Switch Management Protocol Specification Version 1.1 Date: 1996-08-16 Pages: 44 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1987.txt End: Rfc: RFC1986 Status: Experimental Authors: W. Polites, W. Wollman, D. Woo, R. Langan, Title: Experiments with a Simple File Transfer Protocol for Radio Links using Enhanced Trivial File Transfer Protocol (ETFTP) Date: 1996-08-16 Pages: 21 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1986.txt End: Rfc: RFC1985 Status: Proposed_Standard Authors: J. De Winter, Title: SMTP Service Extension for Remote Message Queue Starting Date: 1996-08-14 Pages: 7 Format: .txt Keywords: Mail,SMTP Url: ftp://ds.internic.net/rfc/rfc1985.txt End: Rfc: RFC1984 Status: Informational Authors: IAB & IESG Title: IAB and IESG Statement on Cryptographic Technology and the Internet Date: 1996-08 Format: .txt Keywords: Security Url: ftp://ds.internic.net/rfc/rfc1984.txt End: Rfc: RFC1983 Status: Informational Authors: G. Malkin, Title: Internet Users' Glossary Date: 1996-08-16 Pages: 62 Format: .txt Obsoletes: RFC1392 Url: ftp://ds.internic.net/rfc/rfc1983.txt End: Rfc: RFC1982 Status: Proposed_Standard Authors: R. Elz & R. Bush Title: Serial Number Arithmetic Date: 1996-08 Format: .txt Updates: RFC1034, RFC1035 Keywords: DNS Url: ftp://ds.internic.net/rfc/rfc1982.txt End: Rfc: RFC1981 Status: Proposed_Standard Authors: J. McCann, S. Deering, J. Mogul, Title: Path MTU Discovery for IP version 6 Date: 1996-08-14 Pages: 15 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1981.txt End: Rfc: RFC1980 Status: Informational Authors: J. Seidman, Title: A Proposed Extension to HTML: Client-Side Image Maps Date: 1996-08-14 Pages: 7 Format: .txt Keywords: Web Url: ftp://ds.internic.net/rfc/rfc1980.txt End: Rfc: RFC1979 Status: Informational Authors: J. Woods, Title: PPP Deflate Protocol Date: 1996-08-09 Pages: 10 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1979.txt End: Rfc: RFC1978 Status: Informational Authors: D. Rand Title: PPP Predictor Compression Protocol Date: 1996-08 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1978.txt End: Rfc: RFC1977 Status: Informational Authors: V. Schryver, Title: PPP BSD Compression Protocol Date: 1996-08-09 Pages: 27 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1977.txt End: Rfc: RFC1976 Status: Informational Authors: K. Schneider, S. Venters, Title: PPP for Data Compression in Data Circuit-Terminating Equipment (DCE) Date: 1996-08-14 Pages: 10 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1976.txt End: Rfc: RFC1975 Status: Informational Authors: D. Schremp, J. Black, J. Weiss, Title: PPP Magnalink Variable Resource Compression Date: 1996-08-09 Pages: 6 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1975.txt End: Rfc: RFC1974 Status: Informational Authors: R. Friend, W. Simpson, Title: PPP Stac LZS Compression Protocol Date: 1996-08-13 Pages: 20 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1974.txt End: Rfc: RFC1973 Status: Proposed_Standard Authors: W. Simpson, Title: PPP in Frame Relay Date: 1996-06-19 Pages: 8 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1973.txt End: Rfc: RFC1972 Status: Proposed_Standard Authors: M. Crawford, Title: A Method for the Transmission of IPv6 Packets over Ethernet Networks Date: 1996-08-16 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1972.txt Obsoleted-by: RFC2464 End: Rfc: RFC1971 Status: Proposed_Standard Authors: S. Thomson, T. Narten, Title: IPv6 Stateless Address Autoconfiguration Date: 1996-08-16 Pages: 23 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1971.txt Obsoleted-by: RFC2462 End: Rfc: RFC1970 Status: Proposed_Standard Authors: T. Narten, E. Nordmark, W. Simpson, Title: Neighbor Discovery for IP Version 6 (IPv6) Date: 1996-08-16 Pages: 82 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1970.txt Obsoleted-by: RFC2461 End: Rfc: RFC1969 Status: Informational Authors: K. Sklower, G. Meyer, Title: The PPP DES Encryption Protocol (DESE) Date: 1996-06-19 Pages: 10 Format: .txt Keywords: PPP,Security Url: ftp://ds.internic.net/rfc/rfc1969.txt Obsoleted-by: RFC2419 End: Rfc: RFC1968 Status: Proposed_Standard Authors: G. Meyer, Title: The PPP Encryption Control Protocol (ECP) Date: 1996-06-19 Pages: 11 Format: .txt Keywords: PPP,Security Url: ftp://ds.internic.net/rfc/rfc1968.txt End: Rfc: RFC1967 Status: Informational Authors: K. Schneider, R. Friend, Title: PPP LZS-DCP Compression Protocol (LZS-DCP) Date: 1996-08-13 Pages: 18 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1967.txt End: Rfc: RFC1966 Status: Experimental Authors: T. Bates, R. Chandra, Title: BGP Route Reflection An alternative to full mesh IBGP Date: 1996-06-19 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1966.txt End: Rfc: RFC1965 Status: Experimental Authors: P. Traina, Title: Autonomous System Confederations for BGP Date: 1996-06-19 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1965.txt End: Rfc: RFC1964 Status: Proposed_Standard Authors: J. Linn, Title: The Kerberos Version 5 GSS-API Mechanism Date: 1996-06-19 Pages: 20 Format: .txt Keywords: Kerberos Url: ftp://ds.internic.net/rfc/rfc1964.txt End: Rfc: RFC1963 Status: Informational Authors: K. Schneider, S. Venters, Title: PPP Serial Data Transport Protocol (SDTP) Date: 1996-08-14 Pages: 20 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1963.txt End: Rfc: RFC1962 Status: Proposed_Standard Authors: D. Rand, Title: The PPP Compression Control Protocol (CCP) Date: 1996-06-19 Pages: 9 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1962.txt End: Rfc: RFC1961 Status: Proposed_Standard Authors: P. McMahon, Title: GSS-API Authentication Method for SOCKS Version 5 Date: 1996-06-19 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1961.txt End: Rfc: RFC1960 Status: Proposed_Standard Authors: T. Howes, Title: A String Representation of LDAP Search Filters Keywords: LDAP Date: 1996-06-19 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1960.txt End: Rfc: RFC1959 Status: Proposed_Standard Authors: T. Howes, M. Smith, Title: An LDAP URL Format Date: 1996-06-19 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1959.txt End: Rfc: RFC1958 Status: Informational Authors: B. Carpenter, Title: Architectural Principles of the Internet Date: 1996-06-06 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1958.txt End: Rfc: RFC1957 Status: Informational Authors: R. Nelson, Title: Some Observations on Implementations of the Post Office Protocol (POP3) Date: 1996-06-06 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1957.txt End: Rfc: RFC1956 Status: Informational Authors: D. Engebretson, R. Plzak, Title: Registration in the MIL Domain Date: 1996-06-06 Pages: 2 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1956.txt End: Rfc: RFC1955 Status: Informational Authors: R. Hinden, Title: New Scheme for Internet Routing and Addressing (ENCAPS) for IPN Date: 1996-06-06 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1955.txt End: Rfc: RFC1954 Status: Informational Authors: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Liaw, T. G. Minshall, Title: Transmission of Flow Labelled IPv4 on ATM Data Links Ipsilon Version 1.0 Date: 1996-05-22 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1954.txt End: Rfc: RFC1953 Status: Informational Authors: P. W. Edwards, R. E. Hoffman, F. Liaw, T. Lyon, G. Minshall, , Title: Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0 Date: 1996-05-23 Pages: 20 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1953.txt End: Rfc: RFC1952 Status: Informational Authors: L. Deutsch, Title: GZIP file format specification version 4.3 Date: 1996-05-23 Pages: 12 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1952.txt End: Rfc: RFC1951 Status: Informational Authors: L. Deutsch, Title: DEFLATE Compressed Data Format Specification version 1.3 Date: 1996-05-23 Pages: 17 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1951.txt End: Rfc: RFC1950 Status: Informational Authors: L. Deutsch, J. Gailly, Title: ZLIB Compressed Data Format Specification version 3.3 Date: 1996-05-23 Pages: 11 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1950.txt End: Rfc: RFC1949 Status: Experimental Authors: A. Ballardie, Title: Scalable Multicast Key Distribution Date: 1996-05-17 Pages: 18 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1949.txt End: Rfc: RFC1948 Status: Informational Authors: S. Bellovin, Title: Defending Against Sequence Number Attacks Date: 1996-05-17 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1948.txt End: Rfc: RFC1947 Status: Informational Authors: D. Spinellis, Title: Greek Character Encoding for Electronic Mail Messages Date: 1996-05-17 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1947.txt End: Rfc: RFC1946 Status: Informational Authors: S. Jackowski, Title: Native ATM Support for ST2+ Date: 1996-05-17 Pages: 21 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1946.txt End: Rfc: RFC1945 Status: Informational Authors: T. Berners-Lee, R. Fielding, H. Nielsen, Title: Hypertext Transfer Protocol -- HTTP/1.0 Date: 1996-05-17 Pages: 60 Format: .txt Keywords: Web Url: ftp://ds.internic.net/rfc/rfc1945.txt End: Rfc: RFC1944 Status: Informational Authors: S. Bradner, J. McQuaid, Title: Benchmarking Methodology for Network Interconnect Devices Date: 1996-05-17 Pages: 30 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1944.txt Obsoleted-by: RFC2544 End: Rfc: RFC1943 Status: Informational Authors: B. Jennings, Title: Building an X.500 Directory Service in the US Date: 1996-05-15 Pages: 22 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1943.txt End: Rfc: RFC1942 Status: Experimental Authors: D. Raggett, Title: HTML Tables Date: 1996-05-15 Pages: 30 Format: .txt Keywords: Web Url: ftp://ds.internic.net/rfc/rfc1942.txt End: Rfc: RFC1941 Status: Informational Authors: J. Sellers, J. Robichaux, Title: Frequently Asked Questions for Schools Date: 1996-05-15 Pages: 70 Format: .txt Obsoletes: RFC1578 Url: ftp://ds.internic.net/rfc/rfc1941.txt End: Rfc: RFC1940 Status: Informational Authors: D. Estrin, T. Li, Y. Rekhter, K. Varadhan, D. Zappala, Title: Source Demand Routing: Packet Format and Forwarding Specification (Version 1). Date: 1996-05-14 Pages: 27 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1940.txt End: Rfc: RFC1939 Status: Standard Authors: J. Myers, M. Rose, Title: Post Office Protocol - Version 3 Date: 1996-05-14 Pages: 23 Format: .txt Obsoletes: RFC1725 Url: ftp://ds.internic.net/rfc/rfc1939.txt End: Rfc: RFC1938 Status: Proposed_Standard Authors: N. Haller, C. Metz, Title: A One-Time Password System Date: 1996-05-14 Pages: 18 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1938.txt End: Rfc: RFC1937 Status: Informational Authors: Y. Rekhter, D. Kandlur, Title: "Local/Remote" Forwarding Decision in Switched Data Link Subnetworks Date: 1996-05-08 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1937.txt End: Rfc: RFC1936 Status: Informational Authors: J. Touch, B. Parham, Title: Implementing the Internet Checksum in Hardware Date: 1996-04-10 Pages: 21 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1936.txt End: Rfc: RFC1935 Status: Informational Authors: J. Quarterman, S. Carl-Mitchell, Title: What is the Internet, Anyway? Date: 1996-04-10 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1935.txt End: Rfc: RFC1934 Status: Informational Authors: K. Smith, Title: Ascend's Multilink Protocol Plus (MP+) Date: 1996-04-08 Pages: 47 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1934.txt End: Rfc: RFC1933 Status: Proposed_Standard Authors: R. Gilligan, E. Nordmark, Title: Transition Mechanisms for IPv6 Hosts and Routers Date: 1996-04-08 Pages: 22 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1933.txt End: Rfc: RFC1932 Status: Informational Authors: R. Cole, D. Shur, C. Villamizar, Title: IP over ATM: A Framework Document Date: 1996-04-08 Pages: 31 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1932.txt End: Rfc: RFC1931 Status: Informational Authors: D. Brownell, Title: Dynamic RARP Extensions and Administrative Support for Automatic Network Address Allocation Date: 1996-04-03 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1931.txt End: Rfc: RFC1930 Authors: J. Hawkinson, T. Bates, Title: Guidelines for creation, selection, and registration of an Autonomous System (AS) Date: 1996-04-03 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1930.txt End: Rfc: RFC1929 Status: Proposed_Standard Authors: M. Leech, Title: Username/Password Authentication for SOCKS V5 Date: 1996-04-03 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1929.txt End: Rfc: RFC1928 Status: Proposed_Standard Authors: M. Leech, M. Ganis, Y. Lee, R. Kuris, D. Koblas, L. Jones, Title: SOCKS Protocol Version 5 Date: 1996-04-03 Pages: 9 Format: .txt Keywords: Security Url: ftp://ds.internic.net/rfc/rfc1928.txt End: Rfc: RFC1927 Status: Informational Authors: C. Rogers, Title: Suggested Additional MIME Types for Associating Documents Date: 1996-04-01 Pages: 3 Format: .txt Keywords: Lirpa1 Url: ftp://ds.internic.net/rfc/rfc1927.txt End: Rfc: RFC1926 Status: Informational Authors: J. Eriksson, Title: An Experimental Encapsulation of IP Datagrams on Top of ATM Date: 1996-04-01 Pages: 2 Format: .txt Keywords: Lirpa1 Url: ftp://ds.internic.net/rfc/rfc1926.txt End: Rfc: RFC1925 Status: Informational Authors: R. Callon, Title: The Twelve Networking Truths Date: 1996-04-01 Pages: 3 Format: .txt Keywords: Lirpa1 Url: ftp://ds.internic.net/rfc/rfc1925.txt End: Rfc: RFC1924 Status: Informational Authors: R. Elz, Title: A Compact Representation of IPv6 Addresses Date: 1996-04-01 Pages: 6 Format: .txt Keywords: Lirpa1 Url: ftp://ds.internic.net/rfc/rfc1924.txt End: Rfc: RFC1923 Status: Informational Authors: J. Halpern, S. Bradner, Title: RIPv1 Applicability Statement for Historic Status Date: 1996-03-25 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1923.txt End: Rfc: RFC1922 Status: Informational Authors: H. Zhu, D. Hu, Z. Wang, T. Kao, W. Chang, M. Crispin, Title: Chinese Character Encoding for Internet Messages Date: 1996-03-26 Pages: 27 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1922.txt End: Rfc: RFC1921 Status: Informational Authors: J. Dujonc, Title: TNVIP protocol Date: 1996-03-25 Pages: 30 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1921.txt End: Rfc: RFC1920 Status: Standard Authors: J. Postel, Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1996-03-22 Pages: 40 Format: .txt Obsoletes: RFC1880 Url: ftp://ds.internic.net/rfc/rfc1920.txt Obsoleted-by: RFC2300,RFC2400 End: Rfc: RFC1919 Status: Informational Authors: M. Chatel, Title: Classical versus Transparent IP Proxies Date: 1996-03-28 Pages: 35 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1919.txt End: Rfc: RFC1918 Authors: Y. Rekhter, R. Moskowitz, D. Karrenberg, G. de Groot, E. Lear, , Title: Address Allocation for Private Internets Date: 1996-02-29 Pages: 9 Format: .txt Keywords: IPaddress Obsoletes: RFC1627 Url: ftp://ds.internic.net/rfc/rfc1918.txt End: Rfc: RFC1917 Authors: P. Nesser, Title: An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA Date: 1996-02-29 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1917.txt End: Rfc: RFC1916 Status: Informational Authors: H. Berkowitz, P. Ferguson, W. Leland, P. Nesser, Title: Enterprise Renumbering: Experience and Information Solicitation Date: 1996-02-28 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1916.txt End: Rfc: RFC1915 Authors: F. Kastenholz, Title: Variance for The PPP Connection Control Protocol and The PPP Encryption Control Protocol Date: 1996-02-28 Pages: 7 Format: .txt Keywords: PPP,Security Url: ftp://ds.internic.net/rfc/rfc1915.txt End: Rfc: RFC1914 Status: Proposed_Standard Authors: P. Faltstrom, R. Schoultz, C. Weider, Title: How to interact with a Whois++ mesh Date: 1996-02-28 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1914.txt End: Rfc: RFC1913 Status: Proposed_Standard Authors: C. Weider, J. Fullton, S. Spero, Title: Architecture of the Whois++ Index Service Date: 1996-02-28 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1913.txt End: Rfc: RFC1912 Status: Informational Authors: D. Barr, Title: Common DNS Operational and Configuration Errors Date: 1996-02-28 Pages: 16 Format: .txt Keywords: DNS Url: ftp://ds.internic.net/rfc/rfc1912.txt End: Rfc: RFC1911 Status: Experimental Authors: G. Vaudreuil, Title: Voice Profile for Internet Mail Date: 1996-02-19 Pages: 22 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1911.txt Obsoleted-by: RFC2421,RFC2422,RFC2423 End: Rfc: RFC1910 Status: Experimental Authors: G. Waters, Title: User-based Security Model for SNMPv2 Date: 1996-02-28 Pages: 44 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1910.txt End: Rfc: RFC1909 Status: Experimental Authors: K. McCloghrie, Title: An Administrative Infrastructure for SNMPv2 Date: 1996-02-28 Pages: 19 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1909.txt End: Rfc: RFC1908 Status: Draft_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework Date: 1996-01-22 Pages: 10 Format: .txt Obsoletes: RFC1452 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1908.txt End: Rfc: RFC1907 Status: Draft_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1996-01-22 Pages: 20 Format: .txt Keywords: SNMP Obsoletes: RFC1450 Url: ftp://ds.internic.net/rfc/rfc1907.txt End: Rfc: RFC1906 Status: Draft_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1996-01-22 Pages: 13 Format: .txt Obsoletes: RFC1449 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1906.txt End: Rfc: RFC1905 Status: Draft_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1996-01-22 Pages: 24 Format: .txt Obsoletes: RFC1448 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1905.txt End: Rfc: RFC1904 Status: Draft_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1996-01-22 Pages: 24 Format: .txt Obsoletes: RFC1444 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1904.txt Obsoleted-by: RFC2580 End: Rfc: RFC1903 Status: Draft_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1996-01-22 Pages: 23 Format: .txt Obsoletes: RFC1443 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1903.txt Obsoleted-by: RFC2579 End: Rfc: RFC1902 Status: Draft_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1996-01-22 Pages: 40 Format: .txt Obsoletes: RFC1442 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1902.txt Obsoleted-by: RFC2578 End: Rfc: RFC1901 Status: Experimental Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Introduction to Community-based SNMPv2 Date: 1996-01-22 Pages: 8 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1901.txt End: Rfc: RFC1900 Status: Informational Authors: B. Carpenter, Y. Rekhter, Title: Renumbering Needs Work Date: 1996-02-28 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1900.txt End: Rfc: RFC1898 Status: Informational Authors: D. Eastlake, B. Boesch, S. Crocker, M. Yesil, Title: CyberCash Credit Card Protocol Version 0.8 Date: 1996-02-19 Pages: 52 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1898.txt End: Rfc: RFC1897 Status: Experimental Authors: R. Hinden, J. Postel, Title: IPv6 Testing Address Allocation Date: 1996-01-25 Pages: 4 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1897.txt Obsoleted-by: RFC2471 End: Rfc: RFC1896 Status: Informational Authors: P. Resnick, A. Walker, Title: The text/enriched MIME Content-type Date: 1996-02-19 Pages: 21 Format: .txt Obsoletes: RFC1563 Url: ftp://ds.internic.net/rfc/rfc1896.txt End: Rfc: RFC1895 Status: Informational Authors: E. Levinson, Title: The Application/CALS-1840 Content-type Date: 1996-02-15 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1895.txt End: Rfc: RFC1894 Status: Proposed_Standard Authors: K. Moore, G. Vaudreuil, Title: An Extensible Message Format for Delivery Status Notifications Date: 1996-01-15 Pages: 31 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1894.txt End: Rfc: RFC1893 Status: Proposed_Standard Authors: G. Vaudreuil, Title: Enhanced Mail System Status Codes Date: 1996-01-15 Pages: 15 Format: .txt Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1893.txt End: Rfc: RFC1892 Status: Proposed_Standard Authors: G. Vaudreuil, Title: The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages Date: 1996-01-15 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1892.txt End: Rfc: RFC1891 Status: Proposed_Standard Authors: K. Moore, Title: SMTP Service Extension for Delivery Status Notifications Date: 1996-01-15 Pages: 31 Format: .txt Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1891.txt End: Rfc: RFC1890 Status: Proposed_Standard Authors: H. Schulzrinne, Title: RTP Profile for Audio and Video Conferences with Minimal Control Date: 1996-01-25 Pages: 18 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1890.txt End: Rfc: RFC1889 Status: Proposed_Standard Authors: H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson, Title: RTP: A Transport Protocol for Real-Time Applications Date: 1996-01-25 Pages: 75 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1889.txt End: Rfc: RFC1888 Status: Experimental Authors: J. Bound, B. Carpenter, D. Harrington, J. Houldsworth, A. Lloyd, , Title: OSI NSAPs and IPv6 Date: 1996-08-16 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1888.txt End: Rfc: RFC1887 Status: Informational Authors: Y. Rekhter, T. Li, Title: An Architecture for IPv6 Unicast Address Allocation Date: 1996-01-04 Pages: 25 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1887.txt End: Rfc: RFC1886 Status: Proposed_Standard Authors: S. Thomson, C. Huitema, Title: DNS Extensions to support IP version 6 Date: 1996-01-04 Pages: 5 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1886.txt End: Rfc: RFC1885 Status: Proposed_Standard Authors: A. Conta, S. Deering, Title: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Date: 1996-01-04 Pages: 20 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1885.txt Obsoleted-by: RFC2463 End: Rfc: RFC1884 Status: Proposed_Standard Authors: R. Hinden, S. Deering, Title: IP Version 6 Addressing Architecture Date: 1996-01-04 Pages: 18 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1884.txt Obsoleted-by: RFC2373 End: Rfc: RFC1883 Status: Proposed_Standard Authors: S. Deering, R. Hinden, Title: Internet Protocol, Version 6 (IPv6) Specification Date: 1996-01-04 Pages: 37 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1883.txt Obsoleted-by: RFC2460 End: Rfc: RFC1882 Status: Informational Authors: B. Hancock, Title: The 12-Days of Technology Before Christmas Date: 1995-12-26 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1882.txt End: Rfc: RFC1881 Status: Informational Authors: I. IESG, Title: IPv6 Address Allocation Management Date: 1995-12-26 Pages: 2 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1881.txt End: Rfc: RFC1880 Status: Standard Authors: J. Postel, Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1995-11-29 Pages: 38 Format: .txt Obsoletes: RFC1800 Obsoleted-by: RFC1920,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1880.txt End: Rfc: RFC1879 Status: Informational Authors: B. Manning, Title: Class A Subnet Experiment Results and Recommendations Date: 1996-01-15 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1879.txt End: Rfc: RFC1878 Status: Informational Authors: T. Pummill, B. Manning, Title: Variable Length Subnet Table For IPv4 Date: 1995-12-26 Pages: 8 Format: .txt Obsoletes: RFC1860 Url: ftp://ds.internic.net/rfc/rfc1878.txt End: Rfc: RFC1877 Status: Informational Authors: S. Cobb, Title: PPP Internet Protocol Control Protocol Extensions for Name Server Addresses Date: 1995-12-26 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1877.txt End: Rfc: RFC1876 Status: Experimental Authors: C. Davis, P. Vixie, T. Goodwin, I. Dickinson, Title: A Means for Expressing Location Information in the Domain Name System Date: 1996-01-15 Pages: 18 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1876.txt End: Rfc: RFC1875 Status: Informational Authors: N. Berge, Title: UNINETT PCA Policy Statements Date: 1995-12-26 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1875.txt End: Rfc: RFC1874 Status: Experimental Authors: E. Levinson, Title: SGML Media Types Date: 1995-12-26 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1874.txt End: Rfc: RFC1873 Status: Experimental Authors: E. Levinson, J. Clark, Title: Message/External-Body Content-ID Access Type Date: 1995-12-26 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1873.txt End: Rfc: RFC1872 Status: Experimental Authors: E. Levinson, Title: The MIME Multipart/Related Content-type Date: 1995-12-26 Pages: 8 Format: .txt Obsoleted-by: RFC2112 Url: ftp://ds.internic.net/rfc/rfc1872.txt End: Rfc: RFC1871 Authors: J. Postel, Title: Addendum to RFC 1602 -- Variance Procedure Date: 1995-11-29 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1871.txt End: Rfc: RFC1870 Status: Standard Authors: J. Klensin, N. Freed, K. Moore, Title: SMTP Service Extension for Message Size Declaration Date: 1995-11-06 Pages: 9 Format: .txt Obsoletes: RFC1653 Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1870.txt End: Rfc: RFC1869 Status: Standard Authors: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker, Title: SMTP Service Extensions Date: 1995-11-06 Pages: 11 Format: .txt Obsoletes: RFC1651 Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1869.txt End: Rfc: RFC1868 Status: Experimental Authors: G. Malkin, Title: ARP Extension - UNARP Date: 1995-11-06 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1868.txt End: Rfc: RFC1867 Status: Experimental Authors: E. Nebel, L. Masinter, Title: Form-based File Upload in HTML Date: 1995-11-07 Pages: 13 Format: .txt Keywords: Web Url: ftp://ds.internic.net/rfc/rfc1867.txt End: Rfc: RFC1866 Status: Proposed_Standard Authors: T. Berners-Lee, D. Connolly, Title: Hypertext Markup Language - 2.0 Date: 1995-11-03 Pages: 77 Format: .txt Keywords: Web Url: ftp://ds.internic.net/rfc/rfc1866.txt End: Rfc: RFC1865 Status: Informational Authors: W. Houser, J. Griffin, C. Hage, Title: EDI Meets the Internet: Frequently Asked Questions about Electronic Data Interchange (EDI) on the Internet Date: 1996-01-04 Pages: 42 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1865.txt End: Rfc: RFC1864 Status: Draft_Standard Authors: J. Myers, M. Rose, Title: The Content-MD5 Header Field Date: 1995-10-24 Pages: 4 Format: .txt Obsoletes: RFC1544 Url: ftp://ds.internic.net/rfc/rfc1864.txt End: Rfc: RFC1863 Status: Experimental Authors: D. Haskin, Title: A BGP/IDRP Route Server alternative to a full mesh routing Date: 1995-10-20 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1863.txt End: Rfc: RFC1862 Status: Informational Authors: M. McCahill, J. , M. Schwartz, K. Sollins, T. Verschuren, C. Weider, Title: Report of the IAB Workshop on Internet Information Infrastructure, October 12-14, 1994 Date: 1995-11-03 Pages: 27 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1862.txt End: Rfc: RFC1861 Status: Informational Authors: A. Gwinn, Title: Simple Network Paging Protocol - Version 3 - Two-Way Enhanced Date: 1995-10-19 Pages: 23 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1861.txt End: Rfc: RFC1860 Status: Informational Authors: T. Pummill, B. Manning, Title: Variable Length Subnet Table For IPv4 Date: 1995-10-20 Pages: 3 Format: .txt Obsoleted-by: RFC1878 Url: ftp://ds.internic.net/rfc/rfc1860.txt End: Rfc: RFC1859 Status: Informational Authors: Y. Pouffary, Title: ISO Transport Class 2 Non-use of Explicit Flow Control over TCP RFC1006 extension Date: 1995-10-20 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1859.txt End: Rfc: RFC1858 Status: Informational Authors: P. Ziemba, D. Reed, P. Traina, Title: Security Considerations for IP Fragment Filtering Date: 1995-10-25 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1858.txt End: Rfc: RFC1857 Status: Informational Authors: , Title: A Model for Common Operational Statistics Date: 1995-10-20 Pages: 27 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1857.txt End: Rfc: RFC1856 Status: Informational Authors: H. Clark, Title: The Opstat Client-Server Model for Statistics Retrieval Date: 1995-10-20 Pages: 21 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1856.txt End: Rfc: RFC1855 Status: Informational Authors: S. Hambridge, Title: Netiquette Guidelines Date: 1995-10-20 Pages: 21 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1855.txt End: Rfc: RFC1854 Status: Proposed_Standard Authors: N. Freed, A. Cargille, Title: SMTP Service Extension for Command Pipelining Date: 1995-10-04 Pages: 7 Format: .txt Keywords: SMTP Obsoleted-by: RFC2197 Url: ftp://ds.internic.net/rfc/rfc1854.txt End: Rfc: RFC1853 Status: Informational Authors: W. Simpson, Title: IP in IP Tunneling Date: 1995-10-04 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1853.txt End: Rfc: RFC1852 Status: Experimental Authors: P. Metzger, W. Simpson, Title: IP Authentication using Keyed SHA Date: 1995-10-02 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1852.txt End: Rfc: RFC1851 Status: Experimental Authors: P. Metzger, P. Karn, W. Simpson, Title: The ESP Triple DES-CBC Transform Date: 1995-10-02 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1851.txt End: Rfc: RFC1850 Status: Draft_Standard Authors: F. Baker, R. Coltun, Title: OSPF Version 2 Management Information Base Date: 1995-11-03 Pages: 80 Format: .txt Obsoletes: RFC1253 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1850.txt End: Rfc: RFC1848 Status: Proposed_Standard Authors: S. Crocker, N. Freed, J. Galvin, S. Murphy, Title: MIME Object Security Services Date: 1995-10-03 Pages: 48 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1848.txt End: Rfc: RFC1847 Status: Proposed_Standard Authors: J. Galvin, S. Murphy, S. Crocker, N. Freed, Title: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted Date: 1995-10-03 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1847.txt End: Rfc: RFC1846 Status: Experimental Authors: A. Durand, F. Dupont, Title: SMTP 521 reply code Date: 1995-10-02 Pages: 4 Format: .txt Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1846.txt End: Rfc: RFC1845 Status: Experimental Authors: D. Crocker, N. Freed, A. Cargille, Title: SMTP Service Extension for Checkpoint/Restart Date: 1995-10-02 Pages: 8 Format: .txt Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1845.txt End: Rfc: RFC1844 Status: Informational Authors: E. Huizer, Title: Multimedia E-mail (MIME) User Agent checklist Date: 1995-08-24 Pages: 8 Format: .txt Obsoletes: RFC1820 Url: ftp://ds.internic.net/rfc/rfc1844.txt End: Rfc: RFC1843 Status: Informational Authors: F. Lee, Title: HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII characters Date: 1995-08-24 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1843.txt End: Rfc: RFC1842 Status: Informational Authors: Y. Wei, Y. Zhang, J. Li, J. Ding, Y. Jiang, Title: ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages Date: 1995-08-24 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1842.txt End: Rfc: RFC1841 Status: Informational Authors: J. Chapman, D. Coli, A. Harvey, B. Jensen, K. Rowett, Title: PPP Network Control Protocol for LAN Extension Date: 1995-09-29 Pages: 66 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1841.txt End: Rfc: RFC1838 Status: Experimental Authors: S. Kille, Title: Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses Date: 1995-08-22 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1838.txt Obsoleted-by: RFC2164 End: Rfc: RFC1837 Status: Experimental Authors: S. Kille, Title: Representing Tables and Subtrees in the X.500 Directory Date: 1995-08-22 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1837.txt Obsoleted-by: RFC2293 End: Rfc: RFC1836 Status: Experimental Authors: S. Kille, Title: Representing the O/R Address hierarchy in the X.500 Directory Information Tree Date: 1995-08-22 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1836.txt Obsoleted-by: RFC2294 End: Rfc: RFC1835 Status: Proposed_Standard Authors: P. Deutsch, R. Schoultz, P. Faltstrom, C. Weider, Title: Architecture of the WHOIS++ service Date: 1995-08-16 Pages: 41 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1835.txt End: Rfc: RFC1834 Status: Informational Authors: J. Gargano, K. Weiss, Title: Whois and Network Information Lookup Service Whois++ Date: 1995-08-16 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1834.txt End: Rfc: RFC1833 Status: Proposed_Standard Authors: R. Srinivasan, Title: Binding Protocols for ONC RPC Version 2 Date: 1995-08-09 Pages: 14 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1833.txt End: Rfc: RFC1832 Status: Proposed_Standard Authors: R. Srinivasan, Title: XDR: External Data Representation Standard Date: 1995-08-09 Pages: 24 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1832.txt End: Rfc: RFC1831 Status: Proposed_Standard Authors: R. Srinivasan, Title: RPC: Remote Procedure Call Protocol Specification Version 2 Date: 1995-08-09 Pages: 18 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1831.txt End: Rfc: RFC1830 Status: Experimental Authors: G. Vaudreuil, Title: SMTP Service Extensions for Transmission of Large and Binary MIME Messages Date: 1995-08-16 Pages: 8 Format: .txt Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1830.txt End: Rfc: RFC1829 Status: Proposed_Standard Authors: P. Metzger, P. Karn, W. Simpson, Title: The ESP DES-CBC Transform Date: 1995-08-09 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1829.txt End: Rfc: RFC1828 Status: Proposed_Standard Authors: P. Metzger, W. Simpson, Title: IP Authentication using Keyed MD5 Date: 1995-08-09 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1828.txt End: Rfc: RFC1827 Status: Proposed_Standard Authors: R. Atkinson, Title: IP Encapsulating Security Payload (ESP) Date: 1995-08-09 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1827.txt Obsoleted-by: RFC2406 End: Rfc: RFC1826 Status: Proposed_Standard Authors: R. Atkinson, Title: IP Authentication Header Date: 1995-08-09 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1826.txt Obsoleted-by: RFC2402 End: Rfc: RFC1825 Status: Proposed_Standard Authors: R. Atkinson, Title: Security Architecture for the Internet Protocol Date: 1995-08-09 Pages: 22 Format: .txt Keywords: Kerberos Url: ftp://ds.internic.net/rfc/rfc1825.txt Obsoleted-by: RFC2401 End: Rfc: RFC1824 Status: Informational Authors: H. Danisch, Title: The Exponential Security System TESS: An Identity-Based Cryptographic Protocol for Authenticated Key-Exchange (E.I.S.S.-Report 1995/4) Date: 1995-08-11 Pages: 21 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1824.txt End: Rfc: RFC1823 Status: Informational Authors: T. Howes, M. Smith, Title: The LDAP Application Program Interface Date: 1995-08-09 Pages: 22 Format: .txt Keywords: Kerberos,LDAP Url: ftp://ds.internic.net/rfc/rfc1823.txt End: Rfc: RFC1822 Status: Informational Authors: J. Lowe, Title: A Grant of Rights to Use a Specific IBM patent with Photuris Date: 1995-08-14 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1822.txt End: Rfc: RFC1821 Status: Informational Authors: M. Borden, E. Crawley, B. Davie, S. Batsell, Title: Integration of Real-time Services in an IP-ATM Network Architecture Date: 1995-08-11 Pages: 24 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1821.txt End: Rfc: RFC1820 Status: Informational Authors: E. Huizer, Title: Multimedia E-mail (MIME) User Agent Checklist Date: 1995-08-22 Pages: 8 Format: .txt Obsoleted-by: RFC1844 Url: ftp://ds.internic.net/rfc/rfc1820.txt End: Rfc: RFC1819 Status: Experimental Authors: L. Delgrossi, L. Berger, Title: Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+ Date: 1995-08-11 Pages: 109 Format: .txt Obsoletes: RFC1190 Url: ftp://ds.internic.net/rfc/rfc1819.txt End: Rfc: RFC1818 Status: Standard Authors: J. Postel, T. Li, Y. Rekhter, Title: Best Current Practices Date: 1995-08-04 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1818.txt End: Rfc: RFC1817 Status: Informational Authors: Y. Rekhter, Title: CIDR and Classful Routing Date: 1995-08-04 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1817.txt End: Rfc: RFC1816 Status: Informational Authors: F. Networking Council (FNC), Title: U.S. Government Internet Domain Names Date: 1995-08-03 Pages: 8 Format: .txt Keywords: DNS Obsoletes: RFC1811 Obsoleted-by: RFC2146 Url: ftp://ds.internic.net/rfc/rfc1816.txt End: Rfc: RFC1815 Status: Informational Authors: M. Ohta, Title: Character Sets ISO-10646 and ISO-10646-J-1 Date: 1995-08-01 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1815.txt End: Rfc: RFC1814 Status: Informational Authors: E. Gerich, Title: Unique Addresses are Good Date: 1995-06-22 Pages: 3 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1814.txt End: Rfc: RFC1813 Status: Informational Authors: B. Callaghan, B. Pawlowski, P. Staubach, Title: NFS Version 3 Protocol Specification Date: 1995-06-21 Pages: 126 Format: .txt Keywords: Kerberos Url: ftp://ds.internic.net/rfc/rfc1813.txt End: Rfc: RFC1812 Status: Proposed_Standard Authors: F. Baker, Title: Requirements for IP Version 4 Routers Date: 1995-06-22 Pages: 175 Format: .txt Obsoletes: RFC1716 Url: ftp://ds.internic.net/rfc/rfc1812.txt End: Rfc: RFC1811 Status: Informational Authors: F. Networking Council, Title: U.S. Government Internet Domain Names Date: 1995-06-21 Pages: 3 Format: .txt Obsoleted-by: RFC1816 Keywords: DNS Url: ftp://ds.internic.net/rfc/rfc1811.txt End: Rfc: RFC1810 Status: Informational Authors: J. Touch, Title: Report on MD5 Performance Date: 1995-06-21 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1810.txt End: Rfc: RFC1809 Status: Informational Authors: C. Partridge, Title: Using the Flow Label Field in IPv6 Date: 1995-06-14 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1809.txt End: Rfc: RFC1808 Status: Proposed_Standard Authors: R. Fielding, Title: Relative Uniform Resource Locators Date: 1995-06-14 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1808.txt End: Rfc: RFC1807 Status: Informational Authors: R. Lasher, D. Cohen, Title: A Format for Bibliographic Records Date: 1995-06-21 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1807.txt End: Rfc: RFC1806 Status: Experimental Authors: R. Troost, S. Dorner, Title: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Date: 1995-06-07 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1806.txt End: Rfc: RFC1805 Status: Informational Authors: A. Rubin, Title: Location-Independent Data/Software Integrity Protocol Date: 1995-06-07 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1805.txt End: Rfc: RFC1804 Status: Experimental Authors: G. Mansfield, P. Rajeev, S. Raghavan, T. Howes, Title: Schema Publishing in X.500 Directory Date: 1995-06-09 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1804.txt End: Rfc: RFC1803 Status: Informational Authors: R. Wright, A. Getchell, T. Howes, S. Sataluri, P. Yee, W. Yeong, , Title: Recommendations for an X.500 Production Directory Service Date: 1995-06-07 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1803.txt End: Rfc: RFC1802 Status: Informational Authors: H. Alvestrand, K. Jordan, S. Langlois, J. Romaguera, Title: Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing Date: 1995-06-12 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1802.txt End: Rfc: RFC1801 Status: Experimental Authors: S. Kille, Title: MHS use of the X.500 Directory to support MHS Routing Date: 1995-06-09 Pages: 73 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1801.txt End: Rfc: RFC1800 Status: Standard Authors: J. Postel, Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1995-07-11 Pages: 36 Format: .txt Obsoletes: RFC1780 Obsoleted-by: RFC1880,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1800.txt End: Rfc: RFC1798 Status: Proposed_Standard Authors: A. Young, Title: Connection-less Lightweight Directory Access Protocol Date: 1995-06-07 Pages: 9 Format: .txt Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc1798.txt End: Rfc: RFC1797 Status: Experimental Authors: I. Assigned Numbers Authority, (IANA), Title: Class A Subnet Experiment Date: 1995-04-25 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1797.txt End: Rfc: RFC1796 Status: Informational Authors: C. Huitema, J. Postel, S. Crocker, Title: Not All RFCs are Standards Date: 1995-04-25 Pages: 4 Format: .txt Keywords: Standards Url: ftp://ds.internic.net/rfc/rfc1796.txt End: Rfc: RFC1795 Status: Informational Authors: L. Wells, A. Bartky, Title: Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1.0 Date: 1995-04-25 Pages: 91 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1795.txt End: Rfc: RFC1794 Status: Informational Authors: T. Brisco, Title: DNS Support for Load Balancing Date: 1995-04-20 Pages: 7 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1794.txt End: Rfc: RFC1793 Status: Proposed_Standard Authors: J. Moy, Title: Extending OSPF to Support Demand Circuits Date: 1995-04-19 Pages: 31 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1793.txt End: Rfc: RFC1792 Status: Experimental Authors: T. Sung, Title: TCP/IPX Connection Mib Specification Date: 1995-04-18 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1792.txt End: Rfc: RFC1791 Status: Experimental Authors: T. Sung, Title: TCP And UDP Over IPX Networks With Fixed Path MTU Date: 1995-04-18 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1791.txt End: Rfc: RFC1790 Status: Informational Authors: V. Cerf, Title: An Agreement between the Internet Society and Sun Microsystems, Inc. in the Matter of ONC RPC and XDR Protocols Date: 1995-04-17 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1790.txt End: Rfc: RFC1789 Status: Informational Authors: C. Yang, Title: INETPhone: Telephone Services and Servers on Internet Date: 1995-04-17 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1789.txt End: Rfc: RFC1788 Status: Experimental Authors: W. Simpson, Title: ICMP Domain Name Messages Date: 1995-04-14 Pages: 7 Format: .txt Keywords: DNS Url: ftp://ds.internic.net/rfc/rfc1788.txt End: Rfc: RFC1787 Status: Informational Authors: Y. Rekhter, Title: Routing in a Multi-provider Internet Date: 1995-04-14 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1787.txt End: Rfc: RFC1786 Status: Informational Authors: T. Bates, E. Gerich, L. Joncheray, J. Jouanigot, and others, , Title: Representation of IP Routing Policies in a Routing Registry (ripe-81++) Date: 1995-03-28 Pages: 83 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1786.txt End: Rfc: RFC1785 Status: Informational Authors: G. Malkin, A. Harkin, Title: TFTP Option Negotiation Analysis Date: 1995-03-28 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1785.txt End: Rfc: RFC1784 Status: Proposed_Standard Authors: G. Malkin, A. Harkin, Title: TFTP Timeout Interval and Transfer Size Options Date: 1995-03-28 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1784.txt Obsoleted-by: RFC2349 End: Rfc: RFC1783 Status: Proposed_Standard Authors: G. Malkin, A. Harkin, Title: TFTP Blocksize Option Date: 1995-03-28 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1783.txt Obsoleted-by: RFC2348 End: Rfc: RFC1782 Status: Proposed_Standard Authors: G. Malkin, A. Harkin, Title: TFTP Option Extension Date: 1995-03-28 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1782.txt Obsoleted-by: RFC2347 End: Rfc: RFC1781 Status: Proposed_Standard Authors: S. Kille, Title: Using the OSI Directory to Achieve User Friendly Naming Date: 1995-03-28 Pages: 26 Format: .txt Keywords: LDAP Obsoletes: RFC1484 Url: ftp://ds.internic.net/rfc/rfc1781.txt End: Rfc: RFC1780 Status: Standard Authors: J. Postel, Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1995-03-28 Pages: 39 Format: .txt Obsoletes: RFC1720 Obsoleted-by: RFC1800,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1780.txt End: Rfc: RFC1779 Status: Draft_Standard Authors: S. Kille, Title: A String Representation of Distinguished Names Date: 1995-03-28 Pages: 8 Format: .txt Keywords: LDAP Obsoletes: RFC1485 Url: ftp://ds.internic.net/rfc/rfc1779.txt End: Rfc: RFC1778 Status: Draft_Standard Authors: T. Howes, S. Kille, W. Yeong, C. Robbins, Title: The String Representation of Standard Attribute Syntaxes Date: 1995-03-28 Pages: 12 Format: .txt Keywords: LDAP Obsoletes: RFC1488 Url: ftp://ds.internic.net/rfc/rfc1778.txt End: Rfc: RFC1777 Status: Draft_Standard Authors: W. Yeong, T. Howes, S. Kille, Title: Lightweight Directory Access Protocol Date: 1995-03-28 Pages: 22 Format: .txt Keywords: Kerberos,LDAP Obsoletes: RFC1487 Url: ftp://ds.internic.net/rfc/rfc1777.txt End: Rfc: RFC1776 Status: Informational Authors: S. Crocker, Title: The Address is the Message Date: 1995-04-01 Pages: 2 Format: .txt Keywords: Lirpa1 Url: ftp://ds.internic.net/rfc/rfc1776.txt End: Rfc: RFC1775 Status: Informational Authors: D. Crocker, Title: To Be "On" the Internet Date: 1995-03-17 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1775.txt End: Rfc: RFC1774 Status: Informational Authors: P. Traina, Title: BGP-4 Protocol Analysis Date: 1995-03-21 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1774.txt End: Rfc: RFC1773 Status: Informational Authors: P. Traina, Title: Experience with the BGP-4 protocol Date: 1995-03-21 Pages: 9 Format: .txt Obsoletes: RFC1656 Url: ftp://ds.internic.net/rfc/rfc1773.txt End: Rfc: RFC1772 Status: Draft_Standard Authors: Y. Rekhter, P. Gross, Title: Application of the Border Gateway Protocol in the Internet Date: 1995-03-21 Pages: 19 Format: .txt Obsoletes: RFC1655 Url: ftp://ds.internic.net/rfc/rfc1772.txt End: Rfc: RFC1771 Status: Draft_Standard Authors: Y. Rekhter, T. Li, Title: A Border Gateway Protocol 4 (BGP-4) Date: 1995-03-21 Pages: 57 Format: .txt Obsoletes: RFC1654 Url: ftp://ds.internic.net/rfc/rfc1771.txt End: Rfc: RFC1770 Status: Informational Authors: C. Graff, Title: IPv4 Option for Sender Directed Multi-Destination Delivery Date: 1995-03-28 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1770.txt End: Rfc: RFC1769 Status: Informational Authors: D. Mills, Title: Simple Network Time Protocol (SNTP) Date: 1995-03-17 Pages: 14 Format: .txt Obsoleted-by: RFC2030 Url: ftp://ds.internic.net/rfc/rfc1769.txt End: Rfc: RFC1768 Status: Experimental Authors: D. Marlow, Title: Host Group Extensions for CLNP Multicasting Date: 1995-03-03 Pages: 42 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1768.txt End: Rfc: RFC1767 Status: Proposed_Standard Authors: D. Crocker, Title: MIME Encapsulation of EDI Objects Date: 1995-03-02 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1767.txt End: Rfc: RFC1766 Status: Proposed_Standard Authors: H. Alvestrand, Title: Tags for the Identification of Languages Date: 1995-03-02 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1766.txt End: Rfc: RFC1765 Status: Experimental Authors: J. Moy, Title: OSPF Database Overflow Date: 1995-03-02 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1765.txt End: Rfc: RFC1764 Status: Proposed_Standard Authors: S. Senum, Title: The PPP XNS IDP Control Protocol (XNSCP) Date: 1995-03-01 Pages: 5 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1764.txt End: Rfc: RFC1763 Status: Proposed_Standard Authors: S. Senum, Title: The PPP Banyan Vines Control Protocol (BVCP) Date: 1995-03-01 Pages: 10 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1763.txt End: Rfc: RFC1762 Status: Draft_Standard Authors: S. Senum, Title: The PPP DECnet Phase IV Control Protocol (DNCP) Date: 1995-03-01 Pages: 7 Format: .txt Obsoletes: RFC1376 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1762.txt End: Rfc: RFC1761 Status: Informational Authors: B. Callaghan, R. Gilligan, Title: Snoop Version 2 Packet Capture File Format Date: 1995-02-09 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1761.txt End: Rfc: RFC1760 Status: Informational Authors: N. Haller, Title: The S/KEY One-Time Password System Date: 1995-02-15 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1760.txt End: Rfc: RFC1759 Status: Proposed_Standard Authors: R. Smith, F. Wright, T. Hastings, S. Zilles, J. Gyllenskog, , Title: Printer MIB Date: 1995-03-28 Pages: 113 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1759.txt End: Rfc: RFC1758 Status: Informational Authors: T. American Directory Forum, Title: NADF Standing Documents: A Brief Overview Date: 1995-02-09 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1758.txt End: Rfc: RFC1757 Status: Draft_Standard Authors: S. Waldbusser, Title: Remote Network Monitoring Management Information Base Date: 1995-02-10 Pages: 91 Format: .txt Obsoletes: RFC1271 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1757.txt End: Rfc: RFC1756 Status: Experimental Authors: T. Rinne, Title: REMOTE WRITE PROTOCOL - VERSION 1.0 Date: 1995-01-19 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1756.txt End: Rfc: RFC1755 Status: Proposed_Standard Authors: M. Perez, F. A. Mankin, E. Hoffman, G. Grossman, A. Malis, Title: ATM Signaling Support for IP over ATM Date: 1995-02-17 Pages: 32 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1755.txt End: Rfc: RFC1754 Status: Informational Authors: M. Laubach, Title: IP over ATM Working Group's Recommendations for the ATM Forum's Multiprotocol BOF Version 1 Date: 1995-01-19 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1754.txt End: Rfc: RFC1753 Status: Informational Authors: J. Chiappa, Title: IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture Date: 1995-01-05 Keywords: IPaddress Pages: 18 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1753.txt End: Rfc: RFC1752 Status: Proposed_Standard Authors: S. Bradner, A. Mankin, Title: The Recommendation for the IP Next Generation Protocol Date: 1995-01-18 Pages: 52 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1752.txt End: Rfc: RFC1751 Status: Informational Authors: D. McDonald, Title: A Convention for Human-Readable 128-bit Keys Date: 1994-12-29 Pages: 15 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1751.txt End: Rfc: RFC1750 Status: Informational Authors: D. Eastlake, S. Crocker, J. Schiller, Title: Randomness Recommendations for Security Date: 1994-12-29 Pages: 25 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1750.txt End: Rfc: RFC1749 Status: Proposed_Standard Authors: K. McCloghrie, F. Baker, E. Decker, Title: IEEE 802.5 Station Source Routing MIB using SMIv2 Date: 1994-12-29 Pages: 10 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1749.txt End: Rfc: RFC1748 Status: Draft_Standard Authors: K. McCloghrie, E. Decker, Title: IEEE 802.5 MIB using SMIv2 Date: 1994-12-29 Pages: 25 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1748.txt End: Rfc: RFC1747 Status: Proposed_Standard Authors: J. Hilgeman, S. Nix, A. Bartky, W. Clark, Title: Definitions of Managed Objects for SNA Data Link Control: SDLC Date: 1995-01-11 Pages: 67 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1747.txt End: Rfc: RFC1746 Status: Informational Authors: B. Manning, D. Perkins, Title: Ways to Define User Expectations Date: 1994-12-30 Pages: 18 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1746.txt End: Rfc: RFC1745 Status: Proposed_Standard Authors: K. Varadhan, S. Hares, Y. Rekhter, Title: BGP4/IDRP for IP---OSPF Interaction Date: 1994-12-27 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1745.txt End: Rfc: RFC1744 Status: Informational Authors: G. Huston, Title: Observations on the Management of the Internet Address Space Date: 1994-12-23 Pages: 12 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1744.txt End: Rfc: RFC1743 Status: Draft_Standard Authors: K. McCloghrie, E. Decker, Title: IEEE 802.5 MIB using SMIv2 Date: 1994-12-27 Pages: 25 Format: .txt Keywords: SNMP Obsoletes: RFC1231 Url: ftp://ds.internic.net/rfc/rfc1743.txt End: Rfc: RFC1742 Status: Proposed_Standard Authors: S. Waldbusser, K. Frisa, Title: AppleTalk Management Information Base II Date: 1995-01-05 Pages: 84 Format: .txt Obsoletes: RFC1243 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1742.txt End: Rfc: RFC1741 Status: Informational Authors: P. Faltstrom, D. Crocker, E. Fair, Title: MIME Content Type for BinHex Encoded Files Date: 1994-12-22 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1741.txt End: Rfc: RFC1740 Status: Proposed_Standard Authors: P. Faltstrom, D. Crocker, E. Fair, Title: MIME Encapsulation of Macintosh files - MacMIME Date: 1994-12-22 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1740.txt End: Rfc: RFC1739 Status: Informational Authors: G. Kessler, S. Shepard, Title: A Primer On Internet and TCP/IP Tools Date: 1994-12-22 Pages: 32 Format: .txt Obsoleted-by: RFC2151 Url: ftp://ds.internic.net/rfc/rfc1739.txt End: Rfc: RFC1738 Status: Proposed_Standard Authors: T. Berners-Lee, L. Masinter, M. McCahill, Title: Uniform Resource Locators (URL) Date: 1994-12-20 Pages: 25 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1738.txt End: Rfc: RFC1737 Status: Informational Authors: K. Sollins, L. Masinter, Title: Functional Requirements for Uniform Resource Names Date: 1994-12-20 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1737.txt End: Rfc: RFC1736 Status: Informational Authors: J. Kunze, Title: Functional Requirements for Internet Resource Locators Date: 1995-02-09 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1736.txt End: Rfc: RFC1735 Status: Experimental Authors: J. Heinanen, R. Govindan, Title: NBMA Address Resolution Protocol (NARP) Date: 1994-12-15 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1735.txt End: Rfc: RFC1734 Status: Proposed_Standard Authors: J. Myers, Title: POP3 AUTHentication command Date: 1994-12-20 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1734.txt End: Rfc: RFC1733 Status: Informational Authors: M. Crispin, Title: DISTRIBUTED ELECTRONIC MAIL MODELS IN IMAP4 Date: 1994-12-20 Pages: 3 Format: .txt Keywords: IMAP Url: ftp://ds.internic.net/rfc/rfc1733.txt End: Rfc: RFC1732 Status: Informational Authors: M. Crispin, Title: IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS Date: 1994-12-20 Pages: 5 Format: .txt Keywords: IMAP Url: ftp://ds.internic.net/rfc/rfc1732.txt End: Rfc: RFC1731 Status: Proposed_Standard Authors: J. Myers, Title: IMAP4 Authentication mechanisms Date: 1994-12-20 Pages: 6 Format: .txt Keywords: IMAP Url: ftp://ds.internic.net/rfc/rfc1731.txt End: Rfc: RFC1730 Status: Proposed_Standard Authors: M. Crispin, Title: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4 Date: 1994-12-20 Pages: 77 Format: .txt Obsoleted-by: RFC2061 Url: ftp://ds.internic.net/rfc/rfc1730.txt End: Rfc: RFC1729 Status: Informational Authors: C. Lynch, Title: Using the Z39.50 Information Retrieval Protocol in the Internet Environment Date: 1994-12-16 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1729.txt End: Rfc: RFC1728 Status: Informational Authors: C. Weider, Title: Resource Transponders Date: 1994-12-16 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1728.txt End: Rfc: RFC1727 Status: Informational Authors: C. Weider, P. Deutsch, Title: A Vision of an Integrated Internet Information Service Date: 1994-12-16 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1727.txt End: Rfc: RFC1726 Status: Informational Authors: F. Kastenholz, C. Partridge, Title: Technical Criteria for Choosing IP:The Next Generation (IPng) Date: 1994-12-20 Pages: 31 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1726.txt End: Rfc: RFC1725 Status: Draft_Standard Authors: J. Myers, M. Rose, Title: Post Office Protocol - Version 3 Date: 1994-11-23 Pages: 18 Format: .txt Obsoletes: RFC1460 Obsoleted-by: RFC1939 Url: ftp://ds.internic.net/rfc/rfc1725.txt End: Rfc: RFC1724 Status: Draft_Standard Authors: G. Malkin, F. Baker, Title: RIP Version 2 MIB Extension Date: 1994-11-15 Pages: 18 Format: .txt Obsoletes: RFC1389 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1724.txt End: Rfc: RFC1723 Status: Draft_Standard Authors: G. Malkin, Title: RIP Version 2 Carrying Additional Information Date: 1994-11-15 Pages: 9 Format: .txt Obsoletes: RFC1388 Url: ftp://ds.internic.net/rfc/rfc1723.txt Obsoleted-by: RFC2453 End: Rfc: RFC1722 Status: Draft_Standard Authors: G. Malkin, Title: RIP Version 2 Protocol Applicability Statement Date: 1994-11-15 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1722.txt End: Rfc: RFC1721 Status: Informational Authors: G. Malkin, Title: RIP Version 2 Protocol Analysis Date: 1994-11-15 Pages: 4 Format: .txt Obsoletes: RFC1387 Url: ftp://ds.internic.net/rfc/rfc1721.txt End: Rfc: RFC1720 Status: Standard Authors: J. Postel, I. Architecture Board (IAB), Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1994-11-23 Pages: 41 Format: .txt Obsoletes: RFC1610 Obsoleted-by: RFC1780,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1720.txt End: Rfc: RFC1719 Status: Informational Authors: P. Gross, Title: A Direction for IPng Date: 1994-12-16 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1719.txt End: Rfc: RFC1718 Status: Informational Authors: T. IETF Secretariat, G. Malkin, Title: The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force Date: 1994-11-23 Pages: 23 Format: .txt Obsoletes: RFC1539 Url: ftp://ds.internic.net/rfc/rfc1718.txt End: Rfc: RFC1717 Status: Proposed_Standard Authors: K. Sklower, B. Lloyd, G. McGregor, D. Carr, Title: The PPP Multilink Protocol (MP) Date: 1994-11-21 Pages: 21 Format: .txt Obsoleted-by: RFC1990 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1717.txt End: Rfc: RFC1716 Status: Informational Authors: P. Almquist, F. Kastenholz, Title: Towards Requirements for IP Routers Date: 1994-11-04 Pages: 186 Format: .txt Obsoletes: RFC1009 Obsoleted-by: RFC1812 Url: ftp://ds.internic.net/rfc/rfc1716.txt End: Rfc: RFC1715 Status: Informational Authors: C. Huitema, Title: The H Ratio for Address Assignment Efficiency Date: 1994-11-03 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1715.txt End: Rfc: RFC1714 Status: Informational Authors: S. Williamson, M. Kosters, Title: Referral Whois Protocol (RWhois) Date: 1994-12-15 Pages: 46 Format: .txt, .ps Obsoleted-by: RFC2167 Url: ftp://ds.internic.net/rfc/rfc1714.txt End: Rfc: RFC1713 Status: Informational Authors: A. Romao, Title: Tools for DNS debugging Date: 1994-11-03 Pages: 13 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1713.txt End: Rfc: RFC1712 Status: Experimental Authors: C. Farrell, M. Schulze, S. Pleitner, D. Baldoni, Title: DNS Encoding of Geographical Location Date: 1994-11-01 Pages: 7 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1712.txt End: Rfc: RFC1711 Status: Informational Authors: J. Houttuin, Title: Classifications in E-mail Routing Date: 1994-10-26 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1711.txt End: Rfc: RFC1710 Status: Informational Authors: R. Hinden, Title: Simple Internet Protocol Plus White Paper Date: 1994-10-26 Pages: 23 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1710.txt End: Rfc: RFC1709 Status: Informational Authors: J. Gargano, D. Wasley, Title: K-12 Internetworking Guidelines Date: 1994-12-23 Pages: 26 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1709.txt End: Rfc: RFC1708 Status: Informational Authors: D. Gowin, Title: NTP PICS PROFORMA For the Network Time Protocol Version 3 Date: 1994-10-26 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1708.txt End: Rfc: RFC1707 Status: Informational Authors: M. McGovern, R. Ullmann, Title: CATNIP: Common Architecture for the Internet Date: 1994-11-02 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1707.txt End: Rfc: RFC1706 Status: Informational Authors: B. Manning, R. Colella, Title: DNS NSAP Resource Records Date: 1994-10-26 Pages: 10 Format: .txt Keywords: DNS Obsoletes: RFC1637 Url: ftp://ds.internic.net/rfc/rfc1706.txt End: Rfc: RFC1705 Status: Informational Authors: R. Carlson, D. Ficarella, Title: Six Virtual Inches to the Left: The Problem with IPng Date: 1994-10-26 Pages: 23 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1705.txt End: Rfc: RFC1704 Status: Informational Authors: N. Haller, R. Atkinson, Title: On Internet Authentication Date: 1994-10-26 Pages: 17 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1704.txt End: Rfc: RFC1703 Status: Informational Authors: M. Rose, Title: Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures Date: 1994-10-26 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1703.txt End: Rfc: RFC1702 Status: Informational Authors: S. Hanks, T. Li, D. Farinacci, P. Traina, Title: Generic Routing Encapsulation over IPv4 networks Date: 1994-10-21 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1702.txt End: Rfc: RFC1701 Status: Informational Authors: S. Hanks, T. Li, D. Farinacci, P. Traina, Title: Generic Routing Encapsulation (GRE) Date: 1994-10-21 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1701.txt End: Rfc: RFC1700 Status: Standard Authors: J. Reynolds, J. Postel, Title: ASSIGNED NUMBERS Date: 1994-10-20 Pages: 230 Format: .txt Obsoletes: RFC1340 Url: ftp://ds.internic.net/rfc/rfc1700.txt End: Rfc: RFC1698 Status: Informational Authors: P. Furniss, Title: Octet Sequences for Upper-Layer OSI to Support Basic Communications Applications Date: 1994-10-26 Pages: 29 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1698.txt End: Rfc: RFC1697 Status: Proposed_Standard Authors: D. Brower, R. Purvy, A. Daniel, M. Sinykin, J. Smith, Title: Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2 Date: 1994-08-23 Pages: 38 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1697.txt End: Rfc: RFC1696 Status: Proposed_Standard Authors: J. Barnes, L. Brown, R. Royston, S. Waldbusser, Title: Modem Management Information Base (MIB) using SMIv2 Date: 1994-08-25 Pages: 31 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1696.txt End: Rfc: RFC1695 Status: Proposed_Standard Authors: M. Ahmed, K. Tesink, Title: Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2 Date: 1994-08-25 Pages: 73 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1695.txt End: Rfc: RFC1694 Status: Draft_Standard Authors: T. Brown, K. Tesink, Title: Definitions of Managed Objects for SMDS Interfaces using SMIv2 Date: 1994-08-23 Pages: 35 Format: .txt Obsoletes: RFC1304 Url: ftp://ds.internic.net/rfc/rfc1694.txt End: Rfc: RFC1693 Status: Experimental Authors: T. Connolly, P. Amer, P. Conrad, Title: An Extension to TCP : Partial Order Service Date: 1994-11-01 Pages: 36 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1693.txt End: Rfc: RFC1692 Status: Proposed_Standard Authors: P. Cameron, D. Crocker, D. Cohen, J. Postel, Title: Transport Multiplexing Protocol (TMux) Date: 1994-08-17 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1692.txt End: Rfc: RFC1691 Status: Informational Authors: W. Turner, Title: The Document Architecture for the Cornell Digital Library Date: 1994-08-17 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1691.txt End: Rfc: RFC1690 Status: Informational Authors: G. Huston, Title: Introducing the Internet Engineering and Planning Group (IEPG) Date: 1994-08-17 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1690.txt End: Rfc: RFC1689 Status: Informational Authors: J. Foster, Title: A Status Report on Networked Information Retrieval: Tools and Groups Date: 1994-08-17 Pages: 204 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1689.txt End: Rfc: RFC1688 Status: Informational Authors: W. Simpson, Title: IPng Mobility Considerations Date: 1994-08-11 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1688.txt End: Rfc: RFC1687 Status: Informational Authors: E. Fleischman, Title: A Large Corporate User's View of IPng Date: 1994-08-11 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1687.txt End: Rfc: RFC1686 Status: Informational Authors: M. Vecchi, Title: IPng Requirements: A Cable Television Industry Viewpoint Date: 1994-08-11 Pages: 14 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1686.txt End: Rfc: RFC1685 Status: Informational Authors: H. Alvestrand, Title: Writing X.400 O/R Names Date: 1994-08-11 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1685.txt End: Rfc: RFC1684 Status: Informational Authors: P. Jurg, Title: Introduction to White Pages services based on X.500 Date: 1994-08-11 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1684.txt End: Rfc: RFC1683 Status: Informational Authors: R. Clark, M. Ammar, K. Calvert, Title: Multiprotocol Interoperability In IPng Date: 1994-08-11 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1683.txt End: Rfc: RFC1682 Status: Informational Authors: J. Bound, Title: IPng BSD Host Implementation Analysis Date: 1994-08-11 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1682.txt End: Rfc: RFC1681 Status: Informational Authors: S. Bellovin, Title: On Many Addresses per Host Date: 1994-08-08 Keywords: IPaddress Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1681.txt End: Rfc: RFC1680 Status: Informational Authors: C. Brazdziunas, Title: IPng Support for ATM Services Date: 1994-08-08 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1680.txt End: Rfc: RFC1679 Status: Informational Authors: D. Green, P. Irey, D. Marlow, K. O'Donoghue, Title: HPN Working Group Input to the IPng Requirements Solicitation Date: 1994-08-08 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1679.txt End: Rfc: RFC1678 Status: Informational Authors: E. Britton, J. Tavs, Title: IPng Requirements of Large Corporate Networks Date: 1994-08-08 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1678.txt End: Rfc: RFC1677 Status: Informational Authors: B. Adamson, Title: Tactical Radio Frequency Communication Requirements for IPng Date: 1994-08-08 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1677.txt End: Rfc: RFC1676 Status: Informational Authors: A. Ghiselli, D. Salomoni, C. Vistoli, Title: INFN Requirements for an IPng Date: 1994-08-11 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1676.txt End: Rfc: RFC1675 Status: Informational Authors: S. Bellovin, Title: Security Concerns for IPng Date: 1994-08-08 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1675.txt End: Rfc: RFC1674 Status: Informational Authors: M. Taylor, Title: A Cellular Industry View of IPng Date: 1994-08-08 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1674.txt End: Rfc: RFC1673 Status: Informational Authors: R. Skelton, Title: Electric Power Research Institute Comments on IPng Date: 1994-08-08 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1673.txt End: Rfc: RFC1672 Status: Informational Authors: J. Brownlee, Title: Accounting Requirements for IPng Date: 1994-08-08 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1672.txt End: Rfc: RFC1671 Status: Informational Authors: B. Carpenter, Title: IPng White Paper on Transition and Other Considerations Date: 1994-08-08 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1671.txt End: Rfc: RFC1670 Status: Informational Authors: D. Heagerty, Title: Input to IPng Engineering Considerations Date: 1994-08-08 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1670.txt End: Rfc: RFC1669 Status: Informational Authors: J. Curran, Title: Market Viability as a IPng Criteria Date: 1994-08-08 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1669.txt End: Rfc: RFC1668 Status: Informational Authors: D. Estrin, T. Li, Y. Rekhter, Title: Unified Routing Requirements for IPng Date: 1994-08-08 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1668.txt End: Rfc: RFC1667 Status: Informational Authors: S. Symington, D. Wood, J. Pullen, Title: Modeling and Simulation Requirements for IPng Date: 1994-08-08 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1667.txt End: Rfc: RFC1666 Status: Proposed_Standard Authors: Z. Kielczewski, D. Kostick, K. Shih, Title: Definitions of Managed Objects for SNA NAUs using SMIv2 Date: 1994-08-11 Pages: 68 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1666.txt End: Rfc: RFC1665 Status: Proposed_Standard Authors: Z. Kielczewski, D. Kostick, K. Shih, Title: Definitions of Managed Objects for SNA NAUs using SMIv2 Date: 1994-07-22 Pages: 67 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1665.txt End: Rfc: RFC1664 Status: Experimental Authors: C. Allocchio, A. Bonito, B. Cole, S. Giordano, R. Hagens, Title: Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables Date: 1994-08-11 Keywords: DNS,Mail Pages: 23 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1664.txt Obsoleted-by: RFC2163 End: Rfc: RFC1663 Status: Proposed_Standard Authors: D. Rand, Title: PPP Reliable Transmission Date: 1994-07-21 Pages: 7 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1663.txt End: Rfc: RFC1662 Status: Standard Authors: W. Simpson, Title: PPP in HDLC-like Framing Date: 1994-07-21 Pages: 27 Format: .txt Obsoletes: RFC1549 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1662.txt End: Rfc: RFC1661 Status: Standard Authors: W. Simpson, Title: The Point-to-Point Protocol (PPP) Date: 1994-07-21 Pages: 54 Format: .txt Obsoletes: RFC1548 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1661.txt End: Rfc: RFC1660 Status: Draft_Standard Authors: B. Stewart, Title: Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2 Date: 1994-07-20 Pages: 10 Format: .txt Obsoletes: RFC1318 Url: ftp://ds.internic.net/rfc/rfc1660.txt End: Rfc: RFC1659 Status: Draft_Standard Authors: B. Stewart, Title: Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2 Date: 1994-07-20 Pages: 21 Format: .txt Obsoletes: RFC1317 Url: ftp://ds.internic.net/rfc/rfc1659.txt End: Rfc: RFC1658 Status: Draft_Standard Authors: B. Stewart, Title: Definitions of Managed Objects for Character Stream Devices using SMIv2 Date: 1994-07-20 Pages: 18 Format: .txt Obsoletes: RFC1316 Url: ftp://ds.internic.net/rfc/rfc1658.txt End: Rfc: RFC1657 Status: Proposed_Standard Authors: S. Willis, J. Burruss, J. Chu, Title: Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 Date: 1994-07-21 Pages: 21 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1657.txt End: Rfc: RFC1656 Status: Informational Authors: P. Traina, Title: BGP-4 Protocol Document Roadmap and Implementation Experience Date: 1994-07-21 Pages: 4 Format: .txt Obsoleted-by: RFC1773 Url: ftp://ds.internic.net/rfc/rfc1656.txt End: Rfc: RFC1655 Status: Proposed_Standard Authors: Y. Rekhter, P. Gross, Title: Application of the Border Gateway Protocol in the Internet Date: 1994-07-21 Pages: 19 Format: .txt Obsoletes: RFC1268 Obsoleted-by: RFC1772 Url: ftp://ds.internic.net/rfc/rfc1655.txt End: Rfc: RFC1654 Status: Proposed_Standard Authors: Y. Rekhter, T. Li, Title: A Border Gateway Protocol 4 (BGP-4) Date: 1994-07-21 Pages: 56 Format: .txt Obsoleted-by: RFC1771 Url: ftp://ds.internic.net/rfc/rfc1654.txt End: Rfc: RFC1653 Status: Draft_Standard Authors: J. Klensin, N. Freed, K. Moore, Title: SMTP Service Extension for Message Size Declaration Date: 1994-07-18 Pages: 8 Format: .txt Obsoletes: RFC1427 Obsoleted-by: RFC1870 Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1653.txt End: Rfc: RFC1652 Status: Draft_Standard Authors: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker, Title: SMTP Service Extension for 8bit-MIMEtransport Date: 1994-07-18 Pages: 6 Format: .txt Obsoletes: RFC1426 Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1652.txt End: Rfc: RFC1651 Status: Draft_Standard Authors: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker, Title: SMTP Service Extensions Date: 1994-07-18 Pages: 11 Format: .txt Obsoletes: RFC1425 Obsoleted-by: RFC1869 Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1651.txt End: Rfc: RFC1650 Status: Proposed_Standard Authors: F. Kastenholz, Title: Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2 Date: 1994-08-23 Pages: 20 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1650.txt Obsoleted-by: RFC2358 End: Rfc: RFC1649 Status: Informational Authors: R. Hagens, A. Hansen, Title: Operational Requirements for X.400 Management Domains in the GO-MHS Community Date: 1994-07-18 Pages: 14 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1649.txt End: Rfc: RFC1648 Status: Proposed_Standard Authors: C. Cargille, Title: Postmaster Convention for X.400 Operations Date: 1994-07-18 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1648.txt End: Rfc: RFC1647 Status: Proposed_Standard Authors: B. Kelly, Title: TN3270 Enhancements Date: 1994-07-15 Pages: 33 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1647.txt Obsoleted-by: RFC2355 End: Rfc: RFC1646 Status: Informational Authors: C. Graves, T. Butts, M. Angel, Title: TN3270 Extensions for LUname and Printer Selection Date: 1994-07-14 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1646.txt End: Rfc: RFC1645 Status: Informational Authors: A. Gwinn, Title: Simple Network Paging Protocol - Version 2 Date: 1994-07-14 Pages: 15 Format: .txt Obsoletes: RFC1568 Url: ftp://ds.internic.net/rfc/rfc1645.txt End: Rfc: RFC1644 Status: Experimental Authors: R. Braden, Title: T/TCP -- TCP Extensions for Transactions Functional Specification Date: 1994-07-13 Pages: 38 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1644.txt End: Rfc: RFC1643 Status: Standard Authors: F. Kastenholz, Title: Definitions of Managed Objects for the Ethernet-like Interface Types Date: 1994-07-13 Pages: 19 Format: .txt Obsoletes: RFC1623 Url: ftp://ds.internic.net/rfc/rfc1643.txt End: Rfc: RFC1642 Status: Experimental Authors: D. Goldsmith, M. Davis, Title: UTF-7 - A Mail-Safe Transformation Format of Unicode Date: 1994-07-13 Pages: 14 Format: .txt, .ps Obsoleted-by: RFC2152 Url: ftp://ds.internic.net/rfc/rfc1642.txt End: Rfc: RFC1641 Status: Experimental Authors: D. Goldsmith, M. Davis, Title: Using Unicode with MIME Date: 1994-07-13 Pages: 6 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1641.txt End: Rfc: RFC1640 Status: Informational Authors: S. Crocker, Title: The Process for Organization of Internet Standards Working Group (POISED) Date: 1994-06-09 Pages: 10 Format: .txt Keywords: Standards Url: ftp://ds.internic.net/rfc/rfc1640.txt End: Rfc: RFC1639 Status: Experimental Authors: D. Piscitello, Title: FTP Operation Over Big Address Records (FOOBAR) Date: 1994-06-09 Pages: 5 Format: .txt Obsoletes: RFC1545 Url: ftp://ds.internic.net/rfc/rfc1639.txt End: Rfc: RFC1638 Status: Proposed_Standard Authors: F. Baker, R. Bowen, Title: PPP Bridging Control Protocol (BCP) Date: 1994-06-09 Pages: 28 Format: .txt Obsoletes: RFC1220 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1638.txt End: Rfc: RFC1637 Status: Experimental Authors: B. Manning, R. Colella, Title: DNS NSAP Resource Records Date: 1994-06-09 Pages: 11 Format: .txt Keywords: DNS Obsoletes: RFC1348 Obsoleted-by: RFC1706 Url: ftp://ds.internic.net/rfc/rfc1637.txt End: Rfc: RFC1636 Status: Informational Authors: I. Architecture Board, R. Braden, D. Clark, S. Crocker, C. Huitema, Title: Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994 Date: 1994-06-09 Pages: 52 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1636.txt End: Rfc: RFC1635 Status: Informational Authors: P. Deutsch, A. Emtage, A. Marine, Title: How to Use Anonymous FTP Date: 1994-05-25 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1635.txt End: Rfc: RFC1634 Status: Informational Authors: M. Allen, Title: Novell IPX Over Various WAN Media (IPXWAN) Date: 1994-05-24 Pages: 23 Format: .txt Obsoletes: RFC1551 Url: ftp://ds.internic.net/rfc/rfc1634.txt End: Rfc: RFC1633 Status: Informational Authors: R. Braden, D. Clark, S. Shenker, Title: Integrated Services in the Internet Architecture: an Overview. Date: 1994-06-09 Pages: 33 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1633.txt End: Rfc: RFC1632 Status: Informational Authors: A. Getchell, S. Sataluri, Title: A Revised Catalog of Available X.500 Implementations Date: 1994-05-20 Pages: 94 Format: .txt Obsoletes: RFC1292 Obsoleted-by: RFC2116 Url: ftp://ds.internic.net/rfc/rfc1632.txt End: Rfc: RFC1631 Status: Informational Authors: P. Francis, K. Egevang, Title: The IP Network Address Translator (Nat) Date: 1994-05-20 Pages: 10 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1631.txt End: Rfc: RFC1630 Status: Informational Authors: T. Berners-Lee, Title: Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web Date: 1994-06-09 Pages: 28 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1630.txt End: Rfc: RFC1629 Status: Draft_Standard Authors: R. Colella, R. Callon, E. Gardner, Y. Rekhter, Title: Guidelines for OSI NSAP Allocation in the Internet Date: 1994-05-19 Pages: 52 Format: .txt Obsoletes: RFC1237 Url: ftp://ds.internic.net/rfc/rfc1629.txt End: Rfc: RFC1628 Status: Proposed_Standard Authors: J. Case, Title: UPS Management Information Base Date: 1994-05-19 Pages: 45 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1628.txt End: Rfc: RFC1627 Status: Informational Authors: E. Lear, E. Fair, D. Crocker, T. Kessler, Title: Network 10 Considered Harmful (Some Practices Shouldn't be Codified) Date: 1994-07-01 Pages: 8 Format: .txt Keywords: IPaddress Obsoleted-by: RFC1918 Url: ftp://ds.internic.net/rfc/rfc1627.txt End: Rfc: RFC1626 Status: Proposed_Standard Authors: R. Atkinson, Title: Default IP MTU for use over ATM AAL5 Date: 1994-05-19 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1626.txt Obsoleted-by: RFC2225 End: Rfc: RFC1625 Status: Informational Authors: M. J. Fullton, K. J. Goldman, B. J. Kunze, H. Morris, F. Schiettecatte, Title: WAIS over Z39.50-1988 Date: 1994-06-09 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1625.txt End: Rfc: RFC1624 Status: Informational Authors: A. Rijsinghani, Title: Computation of the Internet Checksum via Incremental Update Date: 1994-05-20 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1624.txt End: Rfc: RFC1623 Status: Standard Authors: F. Kastenholz, Title: Definitions of Managed Objects for the Ethernet-like Interface Types Date: 1994-05-24 Pages: 23 Format: .txt Obsoletes: RFC1398 Obsoleted-by: RFC1643 Url: ftp://ds.internic.net/rfc/rfc1623.txt End: Rfc: RFC1622 Status: Informational Authors: P. Francis, Title: Pip Header Processing Date: 1994-05-20 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1622.txt End: Rfc: RFC1621 Status: Informational Authors: P. Francis, Title: Pip Near-term Architecture Date: 1994-05-20 Pages: 51 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1621.txt End: Rfc: RFC1620 Status: Informational Authors: R. Braden, J. Postel, Y. Rekhter, Title: Internet Architecture Extensions for Shared Media Date: 1994-05-20 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1620.txt End: Rfc: RFC1619 Status: Proposed_Standard Authors: W. Simpson, Title: PPP over SONET/SDH Date: 1994-05-13 Pages: 5 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1619.txt End: Rfc: RFC1618 Status: Proposed_Standard Authors: W. Simpson, Title: PPP over ISDN Date: 1994-05-13 Pages: 7 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1618.txt End: Rfc: RFC1617 Status: Informational Authors: P. Barker, S. Kille, T. Lenggenhager, Title: Naming and Structuring Guidelines for X.500 Directory Pilots Date: 1994-05-20 Pages: 28 Format: .txt Keywords: LDAP Obsoletes: RFC1384 Url: ftp://ds.internic.net/rfc/rfc1617.txt End: Rfc: RFC1616 Status: Informational Authors: E. Huizer, J. Romaguera, RARE WG-MSG Task Force 88, Title: X.400(1988) for the Academic and Research Community in Europe Date: 1994-05-19 Pages: 44 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1616.txt End: Rfc: RFC1615 Status: Informational Authors: J. Houttuin, J. Craigie, Title: Migrating from X.400(84) to X.400(88) Date: 1994-05-19 Pages: 17 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1615.txt End: Rfc: RFC1614 Status: Informational Authors: C. Adie, Title: Network Access to Multimedia Information Date: 1994-05-20 Pages: 79 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1614.txt End: Rfc: RFC1613 Status: Informational Authors: J. Forster, G. Satz, G. Glick, R. Day, Title: cisco Systems X.25 over TCP (XOT) Date: 1994-05-13 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1613.txt End: Rfc: RFC1612 Status: Proposed_Standard Authors: R. Austein, J. Saperia, Title: DNS Resolver MIB Extensions Date: 1994-05-17 Pages: 36 Format: .txt Keywords: SNMP,DNS Url: ftp://ds.internic.net/rfc/rfc1612.txt End: Rfc: RFC1611 Status: Proposed_Standard Authors: R. Austein, J. Saperia, Title: DNS Server MIB Extensions Date: 1994-05-17 Pages: 32 Format: .txt Keywords: SNMP,DNS Url: ftp://ds.internic.net/rfc/rfc1611.txt End: Rfc: RFC1610 Status: Standard Authors: J. Postel, I. Architecture Board (IAB), Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1994-07-08 Pages: 37 Format: .txt Obsoletes: RFC1600 Obsoleted-by: RFC1720,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1610.txt End: Rfc: RFC1609 Status: Experimental Authors: G. Mansfield, T. Johannsen, M. Knopper, Title: Charting Networks in the X.500 Directory Date: 1994-03-25 Pages: 15 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1609.txt End: Rfc: RFC1608 Status: Experimental Authors: T. Johannsen, G. Mansfield, M. Kosters, S. Sataluri, Title: Representing IP Information in the X.500 Directory Date: 1994-03-25 Pages: 20 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1608.txt End: Rfc: RFC1607 Status: Informational Authors: V. Cerf, Title: A VIEW FROM THE 21ST CENTURY Date: 1994-04-01 Pages: 13 Keywords: Lirpa1 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1607.txt End: Rfc: RFC1606 Status: Informational Authors: J. Onions, Title: A Historical Perspective On The Usage Of IP Version 9 Date: 1994-04-01 Pages: 4 Format: .txt Keywords: Lirpa1 Url: ftp://ds.internic.net/rfc/rfc1606.txt End: Rfc: RFC1605 Status: Informational Authors: W. Shakespeare, Title: SONET to Sonnet Translation Date: 1994-04-01 Pages: 3 Format: .txt Keywords: Lirpa1 Url: ftp://ds.internic.net/rfc/rfc1605.txt End: Rfc: RFC1604 Status: Proposed_Standard Authors: T. Brown, Title: Definitions of Managed Objects for Frame Relay Service Date: 1994-03-25 Pages: 46 Format: .txt Obsoletes: RFC1596 Url: ftp://ds.internic.net/rfc/rfc1604.txt End: Rfc: RFC1603 Status: Informational Authors: E. Huizer, D. Crocker, Title: IETF Working Group Guidelines and Procedures Date: 1994-03-24 Pages: 29 Format: .txt Keywords: Standards Url: ftp://ds.internic.net/rfc/rfc1603.txt Obsoleted-by: RFC2418 End: Rfc: RFC1602 Status: Informational Authors: I. Architecture Board, I. Engineering Steer, C. Huitema, P. Gross, , Title: The Internet Standards Process -- Revision 2 Date: 1994-03-24 Pages: 37 Format: .txt Obsoletes: RFC1310 Obsoleted-by: RFC2026 Keywords: Standards Url: ftp://ds.internic.net/rfc/rfc1602.txt End: Rfc: RFC1601 Status: Informational Authors: C. Huitema, I. Architecture Board (IAB), Title: Charter of the Internet Architecture Board (IAB) Date: 1994-03-22 Pages: 6 Format: .txt Obsoletes: RFC1358 Url: ftp://ds.internic.net/rfc/rfc1601.txt End: Rfc: RFC1600 Status: Standard Authors: J. Postel, Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1994-03-14 Pages: 36 Format: .txt Obsoletes: RFC1540 Obsoleted-by: RFC1610,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1600.txt End: Rfc: RFC1598 Status: Proposed_Standard Authors: W. Simpson, Title: PPP in X.25 Date: 1994-03-17 Pages: 8 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1598.txt End: Rfc: RFC1597 Status: Informational Authors: Y. Rekhter, R. Moskowitz, D. Karrenberg, G. de Groot, Title: Address Allocation for Private Internets Date: 1994-03-17 Pages: 8 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1597.txt End: Rfc: RFC1596 Status: Proposed_Standard Authors: T. Brown, Title: Definitions of Managed Objects for Frame Relay Service Date: 1994-03-17 Pages: 46 Format: .txt Obsoleted-by: RFC1604 Url: ftp://ds.internic.net/rfc/rfc1596.txt End: Rfc: RFC1595 Status: Proposed_Standard Authors: T. Brown, K. Tesink, Title: Definitions of Managed Objects for the SONET/SDH Interface Type Date: 1994-03-11 Pages: 59 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1595.txt Obsoleted-by: RFC2558 End: Rfc: RFC1594 Status: Informational Authors: A. Marine, J. Reynolds, G. Malkin, Title: FYI on Questions and Answer Answers to Commonly asked ``New Internet User'' Questions Date: 1994-03-11 Pages: 44 Format: .txt Obsoletes: RFC1325 Url: ftp://ds.internic.net/rfc/rfc1594.txt End: Rfc: RFC1593 Status: Informational Authors: W. McKenzie, J. Cheng, Title: SNA APPN Node MIB Date: 1994-03-10 Pages: 120 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1593.txt End: Rfc: RFC1592 Status: Experimental Authors: B. Wijnen, G. Carpenter, K. Curran, A. Sehgal, G. Waters, Title: Simple Network Management Protocol Distributed Protocol Interface Version 2.0 Date: 1994-03-03 Pages: 54 Format: .txt Obsoletes: RFC1228 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1592.txt End: Rfc: RFC1591 Status: Informational Authors: J. Postel, Title: Domain Name System Structure and Delegation Date: 1994-03-03 Pages: 7 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1591.txt End: Rfc: RFC1590 Status: Informational Authors: J. Postel, Title: Media Type Registration Procedure Date: 1994-03-02 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1590.txt End: Rfc: RFC1589 Status: Informational Authors: D. Mills, Title: A Kernel Model for Precision Timekeeping Date: 1994-03-03 Pages: 37 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1589.txt End: Rfc: RFC1588 Status: Informational Authors: J. Postel, C. Anderson, Title: WHITE PAGES MEETING REPORT Date: 1994-02-25 Pages: 35 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1588.txt End: Rfc: RFC1587 Status: Proposed_Standard Authors: R. Coltun, V. Fuller, Title: The OSPF NSSA Option Date: 1994-03-24 Pages: 17 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1587.txt End: Rfc: RFC1586 Status: Informational Authors: O. deSouza, M. Rodrigues, Title: Guidelines for Running OSPF Over Frame Relay Networks Date: 1994-03-24 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1586.txt End: Rfc: RFC1585 Status: Informational Authors: J. Moy, Title: MOSPF: Analysis and Experience Date: 1994-03-24 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1585.txt End: Rfc: RFC1584 Status: Proposed_Standard Authors: J. Moy, Title: Multicast Extensions to OSPF Date: 1994-03-24 Pages: 102 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1584.txt End: Rfc: RFC1583 Status: Draft_Standard Authors: J. Moy, Title: OSPF Version 2 Date: 1994-03-23 Pages: 212 Format: .txt, .ps Obsoletes: RFC1247 Obsoleted-by: RFC2178 Url: ftp://ds.internic.net/rfc/rfc1583.txt End: Rfc: RFC1582 Status: Proposed_Standard Authors: G. Meyer, Title: Extensions to RIP to Support Demand Circuits Date: 1994-02-18 Pages: 32 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1582.txt End: Rfc: RFC1581 Status: Informational Authors: G. Meyer, Title: Protocol Analysis for Extensions to RIP to Support Demand Circuits Date: 1994-02-18 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1581.txt End: Rfc: RFC1580 Status: Informational Authors: E. EARN Staff, Title: Guide to Network Resource Tools Date: 1994-03-22 Pages: 107 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1580.txt End: Rfc: RFC1579 Status: Informational Authors: S. Bellovin, Title: Firewall-Friendly FTP Date: 1994-02-18 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1579.txt End: Rfc: RFC1578 Status: Informational Authors: J. Sellers, Title: FYI on Questions and Answers: Answers to Commonly Asked ``Primary and Secondary School Internet User'' Questions Date: 1994-02-18 Pages: 53 Format: .txt Obsoleted-by: RFC1941 Url: ftp://ds.internic.net/rfc/rfc1578.txt End: Rfc: RFC1577 Status: Proposed_Standard Authors: M. Laubach, Title: Classical IP and ARP over ATM Date: 1994-01-20 Pages: 17 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1577.txt Obsoleted-by: RFC2225 End: Rfc: RFC1576 Status: Informational Authors: J. Penner, Title: TN3270 Current Practices Date: 1994-01-20 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1576.txt End: Rfc: RFC1575 Status: Draft_Standard Authors: S. Hares, C. Wittbrodt, Title: An Echo Function for CLNP (ISO 8473) Date: 1994-02-18 Pages: 10 Format: .txt Obsoletes: RFC1139 Url: ftp://ds.internic.net/rfc/rfc1575.txt End: Rfc: RFC1574 Status: Informational Authors: S. Hares, C. Wittbrodt, Title: Essential Tools for the OSI Internet Date: 1994-02-18 Pages: 14 Format: .txt Obsoletes: RFC1139 Url: ftp://ds.internic.net/rfc/rfc1574.txt End: Rfc: RFC1573 Status: Proposed_Standard Authors: K. McCloghrie, F. Kastenholz, Title: Evolution of the Interfaces Group of MIB-II Date: 1994-01-20 Pages: 55 Format: .txt Obsoletes: RFC1229 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1573.txt End: Rfc: RFC1572 Status: Proposed_Standard Authors: S. Alexander, Title: Telnet Environment Option Date: 1994-01-14 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1572.txt End: Rfc: RFC1571 Status: Informational Authors: D. Borman, Title: Telnet Environment Option Interoperability Issues Date: 1994-01-14 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1571.txt End: Rfc: RFC1570 Status: Proposed_Standard Authors: W. Simpson, Title: PPP LCP Extensions Date: 1994-01-11 Pages: 22 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1570.txt End: Rfc: RFC1569 Status: Informational Authors: M. Rose, Title: Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures Date: 1994-01-07 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1569.txt End: Rfc: RFC1568 Status: Informational Authors: A. Gwinn, Title: Simple Network Paging Protocol - Version 1(b) Date: 1994-01-07 Pages: 4 Format: .txt Obsoleted-by: RFC1645 Url: ftp://ds.internic.net/rfc/rfc1568.txt End: Rfc: RFC1567 Status: Proposed_Standard Authors: G. Mansfield, S. Kille, Title: X.500 Directory Monitoring MIB Date: 1994-01-11 Pages: 19 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1567.txt Obsoleted-by: RFC2605 End: Rfc: RFC1566 Status: Proposed_Standard Authors: N. Freed, S. Kille, Title: Mail Monitoring MIB Date: 1994-01-11 Pages: 21 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1566.txt Obsoleted-by: RFC2249 End: Rfc: RFC1565 Status: Proposed_Standard Authors: N. Freed, S. Kille, Title: Network Services Monitoring MIB Date: 1994-01-11 Pages: 18 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1565.txt Obsoleted-by: RFC2248 End: Rfc: RFC1564 Status: Informational Authors: P. Barker, R. Hedberg, Title: DSA Metrics (OSI-DS 34 (v3)) Date: 1994-01-14 Pages: 20 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1564.txt End: Rfc: RFC1563 Status: Informational Authors: N. Borenstein, Title: The text/enriched MIME Content-type Date: 1994-01-10 Pages: 16 Format: .txt, .ps Obsoletes: RFC1523 Obsoleted-by: RFC1896 Url: ftp://ds.internic.net/rfc/rfc1563.txt End: Rfc: RFC1562 Status: Informational Authors: G. Michaelson, M. Prior, Title: Naming Guidelines for the AARNet X.500 Directory Service Date: 1993-12-29 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1562.txt End: Rfc: RFC1561 Status: Experimental Authors: D. Piscitello, Title: Use of ISO CLNP in TUBA Environments Date: 1993-12-23 Pages: 25 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1561.txt End: Rfc: RFC1560 Status: Informational Authors: B. Leiner, Y. Rekhter, Title: The MultiProtocol Internet Date: 1993-12-23 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1560.txt End: Rfc: RFC1559 Status: Draft_Standard Authors: J. Saperia, Title: DECnet Phase IV MIB Extensions Date: 1993-12-27 Pages: 69 Format: .txt Obsoletes: RFC1289 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1559.txt End: Rfc: RFC1558 Status: Informational Authors: T. Howes, Title: A String Representation of LDAP Search Filters Date: 1993-12-23 Pages: 3 Format: .txt Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc1558.txt End: Rfc: RFC1557 Status: Informational Authors: K. Chon, H. Je Park, U. Choi, Title: Korean Character Encoding for Internet Messages Date: 1993-12-27 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1557.txt End: Rfc: RFC1556 Status: Informational Authors: H. Nussbacher, Title: Handling of Bi-directional Texts in MIME Date: 1993-12-23 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1556.txt End: Rfc: RFC1555 Status: Informational Authors: H. Nussbacher, Y. Bourvine, Title: Hebrew Character Encoding for Internet Messages Date: 1993-12-23 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1555.txt End: Rfc: RFC1554 Status: Informational Authors: M. Ohta, K. Handa, Title: ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP Date: 1993-12-23 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1554.txt End: Rfc: RFC1553 Status: Proposed_Standard Authors: S. Mathur, M. Lewis, Title: Compressing IPX Headers Over WAN Media (CIPX) Date: 1993-12-09 Pages: 27 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1553.txt End: Rfc: RFC1552 Status: Proposed_Standard Authors: W. Simpson, Title: The PPP Internetwork Packet Exchange Control Protocol (IPXCP) Date: 1993-12-09 Pages: 19 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1552.txt End: Rfc: RFC1551 Status: Informational Authors: M. Allen, Title: Novell IPX Over Various WAN Media (IPXWAN) Date: 1993-12-09 Pages: 22 Format: .txt Obsoletes: RFC1362 Obsoleted-by: RFC1634 Url: ftp://ds.internic.net/rfc/rfc1551.txt End: Rfc: RFC1550 Status: Informational Authors: S. Bradner, A. Mankin, Title: IP: Next Generation (IPng) White Paper Solicitation Date: 1993-12-16 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1550.txt End: Rfc: RFC1549 Status: Draft_Standard Authors: W. Simpson, Title: PPP in HDLC Framing Date: 1993-12-09 Pages: 20 Format: .txt Obsoleted-by: RFC1662 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1549.txt End: Rfc: RFC1548 Status: Draft_Standard Authors: W. Simpson, Title: The Point-to-Point Protocol (PPP) Date: 1993-12-09 Pages: 62 Format: .txt Obsoletes: RFC1331 Obsoleted-by: RFC1661 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1548.txt End: Rfc: RFC1547 Status: Informational Authors: D. Perkins, Title: Requirements for an Internet Standard Point-to-Point Protocol Date: 1993-12-09 Pages: 21 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1547.txt End: Rfc: RFC1546 Status: Informational Authors: C. Partridge, T. Mendez, W. Milliken, Title: Host Anycasting Service Date: 1993-11-16 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1546.txt End: Rfc: RFC1545 Status: Experimental Authors: D. Piscitello, Title: FTP Operation Over Big Address Records (FOOBAR) Date: 1993-11-16 Pages: 5 Format: .txt Obsoleted-by: RFC1639 Url: ftp://ds.internic.net/rfc/rfc1545.txt End: Rfc: RFC1544 Status: Proposed_Standard Authors: M. Rose, Title: The Content-MD5 Header Field Date: 1993-11-16 Pages: 3 Format: .txt Obsoleted-by: RFC1864 Url: ftp://ds.internic.net/rfc/rfc1544.txt End: Rfc: RFC1543 Status: Informational Authors: J. Postel, Title: Instructions to RFC Authors Date: 1993-10-28 Pages: 16 Format: .txt Obsoletes: RFC1111 Obsoleted-by: RFC2223 Keywords: Standards Url: ftp://ds.internic.net/rfc/rfc1543.txt End: Rfc: RFC1542 Status: Proposed_Standard Authors: W. Wimer, Title: Clarifications and Extensions for the Bootstrap Protocol Date: 1993-10-27 Pages: 23 Format: .txt Obsoletes: RFC1532 Url: ftp://ds.internic.net/rfc/rfc1542.txt End: Rfc: RFC1541 Status: Proposed_Standard Authors: R. Droms, Title: Dynamic Host Configuration Protocol Date: 1993-10-27 Pages: 39 Format: .txt Keywords: DHCP Obsoletes: RFC1531 Obsoleted-by: RFC2131 Url: ftp://ds.internic.net/rfc/rfc1541.txt End: Rfc: RFC1540 Status: Standard Authors: J. Postel, Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1993-10-22 Pages: 34 Format: .txt Obsoletes: RFC1500 Obsoleted-by: RFC1600,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1540.txt End: Rfc: RFC1539 Status: Informational Authors: G. Malkin, Title: The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force Date: 1993-10-07 Pages: 22 Format: .txt Obsoletes: RFC1391 Obsoleted-by: RFC1718 Url: ftp://ds.internic.net/rfc/rfc1539.txt End: Rfc: RFC1538 Status: Informational Authors: W. Behl, B. Sterling, W. Teskey, Title: Advanced SNA/IP : A Simple SNA Transport Protocol Date: 1993-10-06 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1538.txt End: Rfc: RFC1537 Status: Informational Authors: P. Beertema, Title: Common DNS Data File Configuration Error Date: 1993-10-06 Pages: 9 Format: .txt Keywords: DNS Url: ftp://ds.internic.net/rfc/rfc1537.txt End: Rfc: RFC1536 Status: Informational Authors: A. Kumar, J. Postel, C. Neuman, P. Danzig, S. Miller, Title: Common DNS Implementation Errors and Suggested Fixes. Date: 1993-10-06 Pages: 12 Format: .txt Keywords: DNS Url: ftp://ds.internic.net/rfc/rfc1536.txt End: Rfc: RFC1535 Status: Informational Authors: E. Gavron, Title: A Security Problem and Proposed Correction With Widely Deployed DNS Software Date: 1993-10-06 Pages: 5 Format: .txt Keywords: DNS Url: ftp://ds.internic.net/rfc/rfc1535.txt End: Rfc: RFC1534 Status: Proposed_Standard Authors: R. Droms, Title: Interoperation Between DHCP and BOOTP Date: 1993-10-08 Pages: 4 Keywords: DHCP Format: .txt Url: ftp://ds.internic.net/rfc/rfc1534.txt End: Rfc: RFC1533 Status: Proposed_Standard Authors: S. Alexander, R. Droms, Title: DHCP Options and BOOTP Vendor Extensions Date: 1993-10-08 Pages: 30 Format: .txt Keywords: DHCP Obsoletes: RFC1497 Obsoleted-by: RFC2132 Url: ftp://ds.internic.net/rfc/rfc1533.txt End: Rfc: RFC1532 Status: Proposed_Standard Authors: W. Wimer, Title: Clarifications and Extensions for the Bootstrap Protocol Date: 1993-10-08 Pages: 22 Format: .txt Obsoleted-by: RFC1542 Url: ftp://ds.internic.net/rfc/rfc1532.txt End: Rfc: RFC1531 Status: Proposed_Standard Authors: R. Droms, Title: Dynamic Host Configuration Protocol Date: 1993-10-07 Pages: 39 Format: .txt Keywords: DHCP Obsoleted-by: RFC1541 Url: ftp://ds.internic.net/rfc/rfc1531.txt End: Rfc: RFC1530 Status: Informational Authors: C. Malamud, M. Rose, Title: Principles of Operation for the TPC.INT Subdomain: General Principles and Policy Date: 1993-10-06 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1530.txt End: Rfc: RFC1529 Status: Informational Authors: C. Malamud, M. Rose, Title: Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies Date: 1993-10-06 Pages: 5 Format: .txt Obsoletes: RFC1486 Url: ftp://ds.internic.net/rfc/rfc1529.txt End: Rfc: RFC1528 Status: Experimental Authors: C. Malamud, M. Rose, Title: Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures Date: 1993-10-06 Pages: 12 Format: .txt Obsoletes: RFC1486 Url: ftp://ds.internic.net/rfc/rfc1528.txt End: Rfc: RFC1527 Status: Informational Authors: G. Cook, Title: What Should We Plan Given the Dilemma of the Network? Date: 1993-09-30 Pages: 17 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1527.txt End: Rfc: RFC1526 Status: Informational Authors: D. Piscitello, Title: Assignment of System Identifiers for TUBA/CLNP Hosts Date: 1993-09-30 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1526.txt End: Rfc: RFC1525 Status: Proposed_Standard Authors: E. Decker, K. McCloghrie, P. Langille, A. Rijsinghani, Title: Definitions of Managed Objects for Source Routing Bridges Date: 1993-09-30 Pages: 18 Format: .txt Obsoletes: RFC1286 Url: ftp://ds.internic.net/rfc/rfc1525.txt End: Rfc: RFC1524 Status: Informational Authors: N. Borenstein, Title: A User Agent Configuration Mechanism For Multimedia Mail Format Information Date: 1993-09-23 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1524.txt End: Rfc: RFC1523 Status: Informational Authors: N. Borenstein, Title: The text/enriched MIME Content-type Date: 1993-09-23 Pages: 15 Format: .txt Obsoleted-by: RFC1563 Url: ftp://ds.internic.net/rfc/rfc1523.txt End: Rfc: RFC1522 Status: Draft_Standard Authors: K. Moore, Title: MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text Date: 1993-09-23 Pages: 10 Format: .txt Obsoletes: RFC1342 Obsoleted-by: RFC2045,RFC2046,RFC2047,RFC2048,RFC2049 Url: ftp://ds.internic.net/rfc/rfc1522.txt End: Rfc: RFC1521 Status: Draft_Standard Authors: N. Borenstein, N. Freed, Title: MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies Date: 1993-09-23 Pages: 81 Format: .txt, .ps Obsoletes: RFC1341 Obsoleted-by: RFC2045,RFC2046,RFC2047,RFC2048,RFC2049 Url: ftp://ds.internic.net/rfc/rfc1521.txt End: Rfc: RFC1520 Status: Informational Authors: Y. Rekhter, C. Topolcic, Title: Exchanging Routing Information Across Provider Boundaries in the CIDR Environment Date: 1993-09-24 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1520.txt End: Rfc: RFC1519 Status: Proposed_Standard Authors: V. Fuller, T. Li, J. Yu, K. Varadhan, Title: Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy Date: 1993-09-24 Pages: 24 Keywords: IPaddress Format: .txt Obsoletes: RFC1338 Url: ftp://ds.internic.net/rfc/rfc1519.txt End: Rfc: RFC1518 Status: Proposed_Standard Authors: Y. Rekhter, T. Li, Title: An Architecture for IP Address Allocation with CIDR Date: 1993-09-24 Pages: 27 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1518.txt End: Rfc: RFC1517 Status: Proposed_Standard Authors: R. Hinden, Title: Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR) Date: 1993-09-24 Pages: 4 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1517.txt End: Rfc: RFC1516 Status: Draft_Standard Authors: D. McMaster, K. McCloghrie, Title: Definitions of Managed Objects for IEEE 802.3 Repeater Devices Date: 1993-09-10 Pages: 40 Format: .txt Obsoletes: RFC1368 Obsoleted-by: RFC2108 Url: ftp://ds.internic.net/rfc/rfc1516.txt End: Rfc: RFC1515 Status: Proposed_Standard Authors: D. McMaster, K. McCloghrie, S. Roberts, Title: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Date: 1993-09-10 Pages: 25 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1515.txt End: Rfc: RFC1514 Status: Proposed_Standard Authors: P. Grillo, S. Waldbusser, Title: Host Resources MIB Date: 1993-09-23 Pages: 33 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1514.txt End: Rfc: RFC1513 Status: Proposed_Standard Authors: S. Waldbusser, Title: Token Ring Extensions to the Remote Network Monitoring MIB Date: 1993-09-23 Pages: 55 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1513.txt End: Rfc: RFC1512 Status: Proposed_Standard Authors: J. Case, A. Rijsinghani, Title: FDDI Management Information Base Date: 1993-09-10 Pages: 51 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1512.txt End: Rfc: RFC1511 Status: Informational Authors: J. Linn, Title: Common Authentication Technology Overview Date: 1993-09-10 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1511.txt End: Rfc: RFC1510 Status: Proposed_Standard Authors: J. Kohl, B. Neuman, Title: The Kerberos Network Authentication Service (V5) Date: 1993-09-10 Pages: 112 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1510.txt End: Rfc: RFC1509 Status: Proposed_Standard Authors: J. Wray, Title: Generic Security Service API : C-bindings Date: 1993-09-10 Pages: 48 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1509.txt End: Rfc: RFC1508 Status: Proposed_Standard Authors: J. Linn, Title: Generic Security Service Application Program Interface Date: 1993-09-10 Pages: 49 Obsoleted-by: RFC2078 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1508.txt End: Rfc: RFC1507 Status: Experimental Authors: C. Kaufman, Title: DASS - Distributed Authentication Security Service Date: 1993-09-10 Pages: 119 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1507.txt End: Rfc: RFC1506 Status: Informational Authors: J. Houttuin, Title: A tutorial on gatewaying between X.400 and Internet mail Date: 1993-09-23 Pages: 39 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1506.txt End: Rfc: RFC1505 Status: Experimental Authors: A. Costanzo, D. Robinson, R. Ullmann, Title: Encoding Header Field for Internet Messages Date: 1993-08-27 Pages: 36 Format: .txt Obsoletes: RFC1154 Url: ftp://ds.internic.net/rfc/rfc1505.txt End: Rfc: RFC1504 Status: Informational Authors: A. Oppenheimer, Title: Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing Date: 1993-08-27 Pages: 82 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1504.txt End: Rfc: RFC1503 Status: Informational Authors: K. McCloghrie, M. Rose, Title: Algorithms for Automating Administration in SNMPv2 Managers Date: 1993-08-26 Pages: 19 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1503.txt End: Rfc: RFC1502 Status: Proposed_Standard Authors: H. Alvestrand, Title: X.400 Use of Extended Character Sets Date: 1993-08-26 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1502.txt End: Rfc: RFC1501 Status: Informational Authors: E. Brunsen, Title: OS/2 User Group Date: 1993-08-06 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1501.txt End: Rfc: RFC1500 Status: Standard Authors: J. Postel, Title: INTERNET OFFICIAL PROTOCOL STANDARDS Date: 1993-08-30 Pages: 36 Format: .txt Obsoletes: RFC1410 Obsoleted-by: RFC1540,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1500.txt End: Rfc: RFC1498 Status: Informational Authors: J. Saltzer, Title: On the Naming and Binding of Network Destinations Date: 1993-08-04 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1498.txt End: Rfc: RFC1497 Status: Draft_Standard Authors: J. Reynolds, Title: BOOTP Vendor Information Extensions Date: 1993-08-04 Pages: 8 Format: .txt Obsoletes: RFC1395 Obsoleted-by: RFC1533 Url: ftp://ds.internic.net/rfc/rfc1497.txt End: Rfc: RFC1496 Status: Proposed_Standard Authors: H. Alvestrand, J. Romaguera, K. Jordan, Title: Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages Date: 1993-08-26 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1496.txt End: Rfc: RFC1495 Status: Proposed_Standard Authors: H. Alvestrand, S. Kille, R. Miles, M. Rose, S. Thompson, Title: Mapping between X.400 and RFC-822 Message Bodies Date: 1993-08-26 Pages: 15 Format: .txt Obsoleted-by: RFC2156 Url: ftp://ds.internic.net/rfc/rfc1495.txt End: Rfc: RFC1494 Status: Proposed_Standard Authors: H. Alvestrand, S. Thompson, Title: Equivalences between 1988 X.400 and RFC-822 Message Bodies Date: 1993-08-26 Pages: 26 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1494.txt End: Rfc: RFC1493 Status: Draft_Standard Authors: E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie, Title: Definitions of Managed Objects for Bridges Date: 1993-07-28 Pages: 34 Format: .txt Obsoletes: RFC1286 Url: ftp://ds.internic.net/rfc/rfc1493.txt End: Rfc: RFC1492 Status: Informational Authors: C. Finseth, Title: An Access Control Protocol, Sometimes Called TACACS Date: 1993-07-23 Pages: 21 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1492.txt End: Rfc: RFC1491 Status: Informational Authors: C. Weider, R. Wright, Title: A Survey of Advanced Usages of X.500 Date: 1993-07-26 Pages: 18 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1491.txt End: Rfc: RFC1490 Status: Draft_Standard Authors: T. Bradley, C. Brown, A. Malis, Title: Multiprotocol Interconnect over Frame Relay Date: 1993-07-26 Pages: 35 Format: .txt Obsoletes: RFC1294 Url: ftp://ds.internic.net/rfc/rfc1490.txt Obsoleted-by: RFC2427 End: Rfc: RFC1489 Status: Informational Authors: A. Chernov, Title: Registration of a Cyrillic Character Set Date: 1993-07-23 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1489.txt End: Rfc: RFC1488 Status: Proposed_Standard Authors: T. Howes, S. Hardcastle-Kille, W. Yeong, C. Robbins, Title: The X.500 String Representation of Standard Attribute Syntaxes Date: 1993-07-29 Pages: 11 Format: .txt Obsoleted-by: RFC1778 Url: ftp://ds.internic.net/rfc/rfc1488.txt End: Rfc: RFC1487 Status: Proposed_Standard Authors: W. Yeong, T. Howes, S. Hardcastle-Kille, Title: X.500 Lightweight Directory Access Protocol Date: 1993-07-29 Pages: 21 Format: .txt Obsoleted-by: RFC1777 Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc1487.txt End: Rfc: RFC1486 Status: Experimental Authors: M. Rose, C. Malamud, Title: An Experiment in Remote Printing Date: 1993-07-30 Pages: 14 Format: .txt Obsoleted-by: RFC1528, Url: ftp://ds.internic.net/rfc/rfc1486.txt End: Rfc: RFC1485 Status: Proposed_Standard Authors: S. Hardcastle-Kille, Title: A String Representation of Distinguished Names (OSI-DS 23 (v5)) Date: 1993-07-28 Pages: 7 Format: .txt Obsoleted-by: RFC1779 Url: ftp://ds.internic.net/rfc/rfc1485.txt End: Rfc: RFC1484 Status: Experimental Authors: S. Hardcastle-Kille, Title: Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2)) Date: 1993-07-28 Pages: 25 Format: .txt Obsoleted-by: RFC1781 Url: ftp://ds.internic.net/rfc/rfc1484.txt End: Rfc: RFC1483 Status: Proposed_Standard Authors: J. Heinanen, Title: Multiprotocol Encapsulation over ATM Adaptation Layer 5 Date: 1993-07-20 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1483.txt End: Rfc: RFC1482 Status: Informational Authors: M. Knopper, S. Richardson, Title: Aggregation Support in the NSFNET Policy Routing Database Date: 1993-07-20 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1482.txt End: Rfc: RFC1481 Status: Informational Authors: C. Huitema, I. Architecture Board, Title: IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling Date: 1993-07-02 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1481.txt End: Rfc: RFC1480 Status: Informational Authors: A. Cooper, J. Postel, Title: The US Domain Date: 1993-06-28 Pages: 47 Format: .txt Keywords: DNS Obsoletes: RFC1386 Url: ftp://ds.internic.net/rfc/rfc1480.txt End: Rfc: RFC1479 Status: Proposed_Standard Authors: M. Steenstrup, Title: Inter-Domain Policy Routing Protocol Specification: Version 1 Date: 1993-07-26 Pages: 108 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1479.txt End: Rfc: RFC1478 Status: Proposed_Standard Authors: M. Lepp, M. Steenstrup, Title: An Architecture for Inter-Domain Policy Routing Date: 1993-07-26 Pages: 35 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1478.txt End: Rfc: RFC1477 Status: Informational Authors: M. Steenstrup, Title: IDPR as a Proposed Standard Date: 1993-07-26 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1477.txt End: Rfc: RFC1476 Status: Experimental Authors: R. Ullmann, Title: RAP: Internet Route Access Protocol Date: 1993-06-17 Pages: 20 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1476.txt End: Rfc: RFC1475 Status: Experimental Authors: R. Ullmann, Title: TP/IX: The Next Internet Date: 1993-06-17 Pages: 35 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1475.txt End: Rfc: RFC1474 Status: Proposed_Standard Authors: F. Kastenholz, Title: The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol Date: 1993-06-08 Pages: 15 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1474.txt End: Rfc: RFC1473 Status: Proposed_Standard Authors: F. Kastenholz, Title: The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol Date: 1993-06-08 Pages: 9 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1473.txt End: Rfc: RFC1472 Status: Proposed_Standard Authors: F. Kastenholz, Title: The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol Date: 1993-06-08 Pages: 11 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1472.txt End: Rfc: RFC1471 Status: Proposed_Standard Authors: F. Kastenholz, Title: The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol Date: 1993-06-08 Pages: 25 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1471.txt End: Rfc: RFC1470 Status: Informational Authors: R. Enger, J. Reynolds, Title: FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices Date: 1993-06-25 Pages: 216 Format: .txt Obsoletes: RFC1147 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1470.txt End: Rfc: RFC1469 Status: Proposed_Standard Authors: T. Pusateri, Title: IP Multicast over Token-Ring Local Area Networks Date: 1993-06-17 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1469.txt End: Rfc: RFC1468 Status: Informational Authors: J. Murai, M. Crispin, E. van der Poel, Title: Japanese Character Encoding for Internet Messages Date: 1993-06-04 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1468.txt End: Rfc: RFC1467 Status: Informational Authors: C. Topolcic, Title: Status of CIDR Deployment in the Internet Date: 1993-08-06 Pages: 9 Format: .txt Obsoletes: RFC1367 Url: ftp://ds.internic.net/rfc/rfc1467.txt End: Rfc: RFC1466 Status: Informational Authors: E. Gerich, Title: Guidelines for Management of IP Address Space Date: 1993-05-26 Pages: 10 Format: .txt Keywords: IPaddress Obsoletes: RFC1366 Url: ftp://ds.internic.net/rfc/rfc1466.txt End: Rfc: RFC1465 Status: Experimental Authors: D. Eppenberger, Title: Routing coordination for X.400 MHS services within a multi protocol / multi network environment Table Format V3 for static routing Date: 1993-05-26 Pages: 31 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1465.txt End: Rfc: RFC1464 Status: Experimental Authors: R. Rosenbaum, Title: Using the Domain Name System To Store Arbitrary String Attributes Date: 1993-05-27 Pages: 4 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1464.txt End: Rfc: RFC1463 Status: Informational Authors: E. Hoffman, L. Jackson, Title: FYI on Introducing the Internet--A Short Bibliography of Introductory Internetworking Readings for the Network Novice Date: 1993-05-27 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1463.txt End: Rfc: RFC1462 Status: Informational Authors: E. Krol, E. Hoffman, Title: FYI on ``What is the Internet?'' Date: 1993-05-27 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1462.txt End: Rfc: RFC1461 Status: Proposed_Standard Authors: D. Throop, Title: SNMP MIB extension for MultiProtocol Interconnect over X.25 Date: 1993-05-27 Pages: 30 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1461.txt End: Rfc: RFC1460 Status: Draft_Standard Authors: M. Rose, Title: Post Office Protocol - Version 3 Date: 1993-06-16 Pages: 19 Format: .txt Obsoletes: RFC1225 Obsoleted-by: RFC1725 Url: ftp://ds.internic.net/rfc/rfc1460.txt End: Rfc: RFC1459 Status: Experimental Authors: J. Oikarinen, D. Reed, Title: Internet Relay Chat Protocol Date: 1993-05-26 Pages: 65 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1459.txt End: Rfc: RFC1458 Status: Informational Authors: R. Braudes, S. Zabele, Title: Requirements for Multicast Protocols Date: 1993-05-26 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1458.txt End: Rfc: RFC1457 Status: Informational Authors: R. Housley, Title: Security Label Framework for the Internet Date: 1993-05-26 Pages: 14 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1457.txt End: Rfc: RFC1456 Status: Informational Authors: C. Nguyen, H. Ngo, C. Bui, T. van Nguyen, Title: Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification Date: 1993-05-08 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1456.txt End: Rfc: RFC1455 Status: Experimental Authors: D. Eastlake, III, Title: Physical Link Security Type of Service Date: 1993-05-26 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1455.txt Obsoleted-by: RFC2474 End: Rfc: RFC1454 Status: Informational Authors: T. Dixon, Title: Comparison of Proposals for Next Version of IP Date: 1993-05-08 Pages: 15 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1454.txt End: Rfc: RFC1453 Status: Informational Authors: W. Chimiak, Title: A Comment on Packet Video Remote Conferencing and the Transport/Network Layers Date: 1993-04-15 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1453.txt End: Rfc: RFC1452 Status: Proposed_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework Date: 1993-05-03 Pages: 17 Format: .txt Obsoleted-by: RFC1908 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1452.txt End: Rfc: RFC1451 Status: Proposed_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Manager to Manager Management Information Base Date: 1993-05-03 Pages: 36 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1451.txt End: Rfc: RFC1450 Status: Proposed_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1993-05-03 Pages: 27 Format: .txt Keywords: SNMP Obsoleted-by: RFC1907 Url: ftp://ds.internic.net/rfc/rfc1450.txt End: Rfc: RFC1449 Status: Proposed_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1993-05-03 Pages: 24 Format: .txt Obsoleted-by: RFC1906 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1449.txt End: Rfc: RFC1448 Status: Proposed_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1993-05-03 Pages: 36 Format: .txt Obsoleted-by: RFC1905 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1448.txt End: Rfc: RFC1447 Status: Proposed_Standard Authors: K. McCloghrie, J. Galvin, Title: Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1993-05-03 Pages: 50 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1447.txt End: Rfc: RFC1446 Status: Proposed_Standard Authors: J. Galvin, K. McCloghrie, Title: Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1993-05-03 Pages: 51 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1446.txt End: Rfc: RFC1445 Status: Proposed_Standard Authors: J. Davin, K. McCloghie, Title: Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1993-05-03 Pages: 47 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1445.txt End: Rfc: RFC1444 Status: Proposed_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1993-05-03 Pages: 33 Format: .txt Keywords: SNMP Obsoleted-by: RFC1904 Url: ftp://ds.internic.net/rfc/rfc1444.txt End: Rfc: RFC1443 Status: Proposed_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1993-05-03 Pages: 31 Format: .txt Obsoleted-by: RFC1903 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1443.txt End: Rfc: RFC1442 Status: Proposed_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2) Date: 1993-05-03 Pages: 55 Format: .txt Obsoleted-by: RFC1902 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1442.txt End: Rfc: RFC1441 Status: Proposed_Standard Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser, Title: Introduction to version 2 of the Internet-standard Network Management Framework Date: 1993-05-03 Pages: 13 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1441.txt End: Rfc: RFC1440 Status: Experimental Authors: R. Troth, Title: SIFT/UFT: Sender-Initiated/Unsolicited File Transfer Date: 1993-07-23 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1440.txt End: Rfc: RFC1439 Status: Informational Authors: C. Finseth, Title: The Uniqueness of Unique Identifiers Date: 1993-03-25 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1439.txt End: Rfc: RFC1438 Status: Informational Authors: A. Chapin, C. Huitema, Title: Internet Engineering Task Force Statements Of Boredom (SOBs) Date: 1993-03-31 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1438.txt End: Rfc: RFC1437 Status: Informational Authors: N. Borenstein, M. Linimon, Title: The Extension of MIME Content-Types to a New Medium Date: 1993-04-01 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1437.txt End: Rfc: RFC1436 Status: Informational Authors: F. Anklesaria, M. McCahill, P. Lindner, D. Johnson, D. John, D. Torrey, B. Alberti, Title: The Internet Gopher Protocol (a distributed document search and retrieval protocol) Date: 1993-03-18 Pages: 16 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1436.txt End: Rfc: RFC1435 Status: Informational Authors: S. Knowles, Title: IESG Advice from Experience with Path MTU Discovery Date: 1993-03-17 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1435.txt End: Rfc: RFC1434 Status: Informational Authors: R. Dixon, D. Kushi, Title: Data Link Switching: Switch-to-Switch Protocol Date: 1993-03-17 Pages: 33 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1434.txt End: Rfc: RFC1433 Status: Experimental Authors: J. Garrett, J. Hagan, J. Wong, Title: Directed ARP Date: 1993-03-05 Pages: 17 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1433.txt End: Rfc: RFC1432 Status: Informational Authors: J. Quarterman, Title: Recent Internet Books Date: 1993-03-03 Pages: 15 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1432.txt End: Rfc: RFC1431 Status: Informational Authors: P. Barker, Title: DUA Metrics Date: 1993-02-26 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1431.txt End: Rfc: RFC1430 Status: Informational Authors: S. Kille, E. Huizer, V. Cerf, R. Hobby, S. Kent, Title: A Strategic Plan for Deploying an Internet X.500 Directory Service Date: 1993-02-26 Pages: 20 Keywords: LDAP Format: .txt Url: ftp://ds.internic.net/rfc/rfc1430.txt End: Rfc: RFC1429 Status: Informational Authors: E. Thomas, Title: Listserv Distribute Protocol Date: 1993-02-24 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1429.txt End: Rfc: RFC1428 Status: Informational Authors: G. Vaudreuil, Title: Transition of Internet Mail from Just-Send-8 to 8Bit-SMTP/MIME Date: 1993-02-10 Pages: 6 Format: .txt Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1428.txt End: Rfc: RFC1427 Status: Proposed_Standard Authors: K. Moore, N. Freed, J. Klensin, Title: SMTP Service Extension for Message Size Declaration Date: 1993-02-10 Pages: 8 Format: .txt Obsoleted-by: RFC1653 Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1427.txt End: Rfc: RFC1426 Status: Proposed_Standard Authors: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker, Title: SMTP Service Extension for 8bit-MIMEtransport Date: 1993-02-10 Pages: 6 Format: .txt Obsoleted-by: RFC1652 Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1426.txt End: Rfc: RFC1425 Status: Proposed_Standard Authors: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker, Title: SMTP Service Extensions Date: 1993-02-10 Pages: 10 Format: .txt Obsoleted-by: RFC1651 Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1425.txt End: Rfc: RFC1424 Status: Proposed_Standard Authors: B. Kaliski, Title: Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services Date: 1993-02-10 Pages: 9 Format: .txt Keywords: Mail,Security Url: ftp://ds.internic.net/rfc/rfc1424.txt End: Rfc: RFC1423 Status: Proposed_Standard Authors: D. Balenson, Title: Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers Date: 1993-02-10 Pages: 14 Format: .txt Obsoletes: RFC1115 Keywords: Mail,Security Url: ftp://ds.internic.net/rfc/rfc1423.txt End: Rfc: RFC1422 Status: Proposed_Standard Authors: S. Kent, Title: Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management Date: 1993-02-10 Pages: 32 Format: .txt Obsoletes: RFC1114 Keywords: Mail,Security Url: ftp://ds.internic.net/rfc/rfc1422.txt End: Rfc: RFC1421 Status: Proposed_Standard Authors: J. Linn, Title: Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures Date: 1993-02-10 Pages: 42 Format: .txt Obsoletes: RFC1113 Keywords: Mail,Security Url: ftp://ds.internic.net/rfc/rfc1421.txt End: Rfc: RFC1420 Status: Proposed_Standard Authors: S. Bostock, Title: SNMP over IPX Date: 1993-03-03 Pages: 4 Format: .txt Obsoletes: RFC1298 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1420.txt End: Rfc: RFC1419 Status: Proposed_Standard Authors: G. Minshall, M. Ritter, Title: SNMP over AppleTalk Date: 1993-03-03 Pages: 7 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1419.txt End: Rfc: RFC1418 Status: Proposed_Standard Authors: M. Rose, Title: SNMP over OSI Date: 1993-03-03 Pages: 4 Format: .txt Obsoletes: RFC1283 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1418.txt End: Rfc: RFC1417 Status: Informational Authors: T. Myer, NADF, Title: NADF Standing Documents: A Brief Overview Date: 1993-02-04 Pages: 4 Format: .txt Obsoletes: RFC1295 Url: ftp://ds.internic.net/rfc/rfc1417.txt End: Rfc: RFC1416 Status: Experimental Authors: D. Borman, Title: Telnet Authentication Option Date: 1993-02-01 Pages: 7 Format: .txt Obsoletes: RFC1409 Url: ftp://ds.internic.net/rfc/rfc1416.txt End: Rfc: RFC1415 Status: Proposed_Standard Authors: J. Mindel, R. Slaski, Title: FTP-FTAM Gateway Specification Date: 1993-01-27 Pages: 58 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1415.txt End: Rfc: RFC1414 Status: Proposed_Standard Authors: M. St. Johns, M. Rose, Title: Ident MIB Date: 1993-02-04 Pages: 13 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1414.txt End: Rfc: RFC1413 Status: Proposed_Standard Authors: M. St. Johns, Title: Identification Protocol Date: 1993-02-04 Pages: 10 Format: .txt Obsoletes: RFC0931 Url: ftp://ds.internic.net/rfc/rfc1413.txt End: Rfc: RFC1412 Status: Experimental Authors: K. Alagappan, Title: Telnet Authentication : SPX Date: 1993-01-27 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1412.txt End: Rfc: RFC1411 Status: Experimental Authors: D. Borman, Title: Telnet Authentication: Kerberos Version 4 Date: 1993-01-26 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1411.txt End: Rfc: RFC1410 Status: Standard Authors: Internet Architecture Board, L. Chapin, Title: IAB OFFICIAL PROTOCOL STANDARDS Date: 1993-03-24 Pages: 35 Format: .txt Obsoletes: RFC1360 Obsoleted-by: RFC1500,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1410.txt End: Rfc: RFC1409 Status: Experimental Authors: D. Borman, Title: Telnet Authentication Option Date: 1993-01-26 Pages: 7 Format: .txt Obsoleted-by: RFC1416 Url: ftp://ds.internic.net/rfc/rfc1409.txt End: Rfc: RFC1408 Status: Historic Authors: D. Borman, Title: Telnet Environment Option Date: 1993-01-26 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1408.txt End: Rfc: RFC1407 Status: Proposed_Standard Authors: T. Cox, K. Tesink, Title: Definitions of Managed Objects for the DS3/E3 Interface Type Date: 1993-01-26 Pages: 55 Format: .txt Obsoletes: RFC1233 Url: ftp://ds.internic.net/rfc/rfc1407.txt End: Rfc: RFC1406 Status: Proposed_Standard Authors: F. Baker, J. Watt, Title: Definitions of Managed Objects for the DS1 and E1 Interface Types Date: 1993-01-26 Pages: 50 Format: .txt Obsoletes: RFC1232 Url: ftp://ds.internic.net/rfc/rfc1406.txt End: Rfc: RFC1405 Status: Experimental Authors: C. Allocchio, Title: Mapping between X.400(1984/1988) and Mail-11 (DECnet mail) Date: 1993-01-20 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1405.txt Obsoleted-by: RFC2162 End: Rfc: RFC1404 Status: Informational Authors: B. Stockman, Title: A Model for Common Operational Statistics Date: 1993-01-20 Pages: 27 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1404.txt End: Rfc: RFC1403 Status: Proposed_Standard Authors: K. Varadhan, Title: BGP OSPF Interaction Date: 1993-01-14 Pages: 17 Format: .txt Obsoletes: RFC1364 Url: ftp://ds.internic.net/rfc/rfc1403.txt End: Rfc: RFC1402 Status: Informational Authors: J. Martin, Title: There's Gold in them thar Networks! Searching for Treasure in all the Wrong Places Date: 1993-01-14 Pages: 39 Format: .txt Obsoletes: RFC1290 Url: ftp://ds.internic.net/rfc/rfc1402.txt End: Rfc: RFC1401 Status: Informational Authors: Internet Architecture Board, L. Chapin, Title: Correspondence between the IAB and DISA on the use of DNS throughout the Internet Date: 1993-01-13 Pages: 8 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1401.txt End: Rfc: RFC1400 Status: Informational Authors: A. Williamson, Title: Transition and Modernization of the Internet Registration Service Date: 1993-03-25 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1400.txt End: Rfc: RFC1398 Status: Draft_Standard Authors: F. Kastenholz, Title: Definitions of Managed Objects for the Ethernet-like Interface Types Date: 1993-01-14 Pages: 24 Format: .txt Obsoletes: RFC1284 Obsoleted-by: RFC1623 Url: ftp://ds.internic.net/rfc/rfc1398.txt End: Rfc: RFC1397 Status: Proposed_Standard Authors: D. Haskin, Title: Default Route Advertisement In BGP2 And BGP3 Versions Of The Border Gateway Protocol Date: 1993-01-13 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1397.txt End: Rfc: RFC1396 Status: Informational Authors: S. Crocker, Title: The Process for Organization of Internet Standards Working Group (POISED) Date: 1993-01-11 Pages: 10 Format: .txt Keywords: Standards Url: ftp://ds.internic.net/rfc/rfc1396.txt End: Rfc: RFC1395 Status: Draft_Standard Authors: J. Reynolds, Title: BOOTP Vendor Information Extensions Date: 1993-01-11 Pages: 8 Format: .txt Obsoletes: RFC1084 Obsoleted-by: RFC1497 Url: ftp://ds.internic.net/rfc/rfc1395.txt End: Rfc: RFC1394 Status: Informational Authors: P. Robinson, Title: Relationship of Telex Answerback Codes to Internet Domains Date: 1993-01-08 Pages: 15 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1394.txt End: Rfc: RFC1393 Status: Experimental Authors: G. Malkin, Title: Traceroute Using an IP Option Date: 1993-01-11 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1393.txt End: Rfc: RFC1392 Status: Informational Authors: G. Malkin, T. Parker, Title: Internet Users' Glossary Date: 1993-01-12 Pages: 53 Format: .txt Obsoleted-by: RFC1983 Url: ftp://ds.internic.net/rfc/rfc1392.txt End: Rfc: RFC1391 Status: Informational Authors: G. Malkin, Title: The Tao of IETF: A Guide for New Attendees of the Internet Engineering Task Force Date: 1993-01-06 Pages: 19 Format: .txt Obsoleted-by: RFC1539 Url: ftp://ds.internic.net/rfc/rfc1391.txt End: Rfc: RFC1390 Status: Standard Authors: D. Katz, Title: Transmission of IP and ARP over FDDI Networks Date: 1993-01-05 Pages: 12 Format: .txt Obsoletes: RFC1188 Url: ftp://ds.internic.net/rfc/rfc1390.txt End: Rfc: RFC1389 Status: Proposed_Standard Authors: G. Malkin, F. Baker, Title: RIP Version 2 MIB Extension Date: 1993-01-06 Pages: 13 Format: .txt Obsoleted-by: RFC1724 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1389.txt End: Rfc: RFC1388 Status: Proposed_Standard Authors: G. Malkin, Title: RIP Version 2 Carrying Additional Information Date: 1993-01-06 Pages: 7 Format: .txt Obsoleted-by: RFC1723,RFC2453 Url: ftp://ds.internic.net/rfc/rfc1388.txt End: Rfc: RFC1387 Status: Informational Authors: G. Malkin, Title: RIP Version 2 Protocol Analysis Date: 1993-01-06 Pages: 3 Format: .txt Obsoleted-by: RFC1721 Url: ftp://ds.internic.net/rfc/rfc1387.txt End: Rfc: RFC1386 Status: Informational Authors: A. Cooper, J. Postel, Title: The US Domain Date: 1992-12-28 Pages: 31 Format: .txt Keywords: DNS Obsoleted-by: RFC1480 Url: ftp://ds.internic.net/rfc/rfc1386.txt End: Rfc: RFC1385 Status: Informational Authors: Z. Wang, Title: EIP: The Extended Internet Protocol A Framework for Maintaining Backward Compatibility Date: 1992-11-13 Pages: 17 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1385.txt End: Rfc: RFC1384 Status: Informational Authors: P. Barker, S. Hardcastle-Kille, Title: Naming Guidelines for Directory Pilots Date: 1993-02-11 Pages: 12 Format: .txt, .ps Obsoleted-by: RFC1617 Url: ftp://ds.internic.net/rfc/rfc1384.txt End: Rfc: RFC1383 Status: Informational Authors: C. Huitema, Title: An Experiment in DNS Based IP Routing Date: 1992-12-28 Pages: 14 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1383.txt End: Rfc: RFC1382 Status: Proposed_Standard Authors: D. Throop, Title: SNMP MIB Extension for the X.25 Packet Layer Date: 1992-11-10 Pages: 69 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1382.txt End: Rfc: RFC1381 Status: Proposed_Standard Authors: D. Throop, F. Baker, Title: SNMP MIB Extension for X.25 LAPB Date: 1992-11-10 Pages: 33 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1381.txt End: Rfc: RFC1380 Status: Informational Authors: P. Gross, P. Almquist, Title: IESG Deliberations on Routing and Addressing Date: 1992-11-09 Pages: 22 Format: .txt Keywords: IPaddress Url: ftp://ds.internic.net/rfc/rfc1380.txt End: Rfc: RFC1379 Status: Informational Authors: R. Braden, Title: Extending TCP for Transactions -- Concepts Date: 1992-11-05 Pages: 38 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1379.txt End: Rfc: RFC1378 Status: Proposed_Standard Authors: B. Parker, Title: The PPP AppleTalk Control Protocol (ATCP) Date: 1992-11-05 Pages: 16 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1378.txt End: Rfc: RFC1377 Status: Proposed_Standard Authors: D. Katz, Title: The PPP OSI Network Layer Control Protocol (OSINLCP) Date: 1992-11-05 Pages: 10 Format: .txt Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1377.txt End: Rfc: RFC1376 Status: Proposed_Standard Authors: S. Senum, Title: The PPP DECnet Phase IV Control Protocol (DNCP) Date: 1992-11-05 Pages: 6 Format: .txt Obsoleted-by: RFC1762 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1376.txt End: Rfc: RFC1375 Status: Informational Authors: P. Robinson, Title: Suggestion for New Classes of IP Addresses Date: 1992-11-03 Pages: 7 Format: .txt Keywords: IPaddress Url: ftp://ds.internic.net/rfc/rfc1375.txt End: Rfc: RFC1374 Status: Proposed_Standard Authors: J. Renwick, A. Nicholson, Title: IP and ARP on HIPPI Date: 1992-11-02 Pages: 43 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1374.txt End: Rfc: RFC1373 Status: Informational Authors: T. Tignor, Title: PORTABLE DUAs Date: 1992-10-27 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1373.txt End: Rfc: RFC1372 Status: Proposed_Standard Authors: D. Borman, C. Hedrick, Title: Telnet Remote Flow Control Option Date: 1992-10-23 Pages: 6 Format: .txt Obsoletes: RFC1080 Url: ftp://ds.internic.net/rfc/rfc1372.txt End: Rfc: RFC1371 Status: Informational Authors: P. Gross, Title: Choosing a "Common IGP" for the IP Internet (The IESG's Recommendation to the IAB) Date: 1992-10-23 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1371.txt End: Rfc: RFC1370 Status: Proposed_Standard Authors: Internet Architecture Board, Title: Applicability Statement for OSPF Date: 1992-10-23 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1370.txt End: Rfc: RFC1369 Status: Informational Authors: F. Kastenholz, Title: Implementation Notes and Experience for The Internet Ethernet MIB Date: 1992-10-23 Pages: 7 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1369.txt End: Rfc: RFC1368 Status: Proposed_Standard Authors: D. McMaster, K. McCloghrie, Title: Definitions of Managed Objects for IEEE 802.3 Repeater Devices Date: 1992-10-26 Pages: 40 Format: .txt Keywords: SNMP Obsoleted-by: RFC1516 Url: ftp://ds.internic.net/rfc/rfc1368.txt End: Rfc: RFC1367 Status: Informational Authors: C. Topolcic, Title: Schedule for IP Address Space Management Guidelines Date: 1992-10-22 Pages: 3 Format: .txt Keywords: IPaddress Obsoleted-by: RFC1467 Url: ftp://ds.internic.net/rfc/rfc1367.txt End: Rfc: RFC1366 Status: Informational Authors: E. Gerich, Title: Guidelines for Management of IP Address Space Date: 1992-10-22 Pages: 8 Format: .txt Keywords: IPaddress Obsoleted-by: RFC1466 Url: ftp://ds.internic.net/rfc/rfc1366.txt End: Rfc: RFC1365 Status: Informational Authors: K. Siyan, Title: An IP Address Extension Proposal Date: 1992-09-10 Pages: 6 Format: .txt Keywords: IPaddress Url: ftp://ds.internic.net/rfc/rfc1365.txt End: Rfc: RFC1364 Status: Proposed_Standard Authors: K. Varadhan, Title: BGP OSPF Interaction Date: 1992-09-11 Pages: 14 Format: .txt Obsoleted-by: RFC1403 Url: ftp://ds.internic.net/rfc/rfc1364.txt End: Rfc: RFC1363 Status: Experimental Authors: C. Partridge, Title: A Proposed Flow Specification Date: 1992-09-10 Pages: 20 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1363.txt End: Rfc: RFC1362 Status: Informational Authors: M. Allen, Title: Novell IPX Over Various WAN Media (IPXWAN) Date: 1992-09-10 Pages: 13 Format: .txt Obsoleted-by: RFC1551 Url: ftp://ds.internic.net/rfc/rfc1362.txt End: Rfc: RFC1361 Status: Informational Authors: D. Mills, Title: Simple Network Time Protocol (SNTP) Date: 1992-08-10 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1361.txt End: Rfc: RFC1360 Status: Standard Authors: Internet Architecture Board, A. Chapin, Title: IAB OFFICIAL PROTOCOL STANDARDS Date: 1992-09-09 Pages: 33 Format: .txt Obsoletes: RFC1280 Obsoleted-by: RFC1410,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1360.txt End: Rfc: RFC1359 Status: Informational Authors: ACM SIGUCCS, Title: Connecting to the Internet What Connecting Institutions Should Anticipate Date: 1992-08-14 Pages: 25 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1359.txt End: Rfc: RFC1358 Status: Informational Authors: L. Chapin, Title: Charter of the Internet Architecture Board (IAB) Date: 1992-08-07 Pages: 5 Format: .txt Obsoleted-by: RFC1601 Url: ftp://ds.internic.net/rfc/rfc1358.txt End: Rfc: RFC1357 Status: Informational Authors: D. Cohen, Title: A Format for E-mailing Bibliographic Records Date: 1992-07-10 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1357.txt End: Rfc: RFC1356 Status: Proposed_Standard Authors: A. Malis, D. Robinson, R. Ullmann, Title: Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode Date: 1992-08-06 Pages: 14 Format: .txt Obsoletes: RFC0877 Url: ftp://ds.internic.net/rfc/rfc1356.txt End: Rfc: RFC1355 Status: Informational Authors: J. Curran, A. Marine, Title: Privacy and Accuracy Issues in Network Information Center Databases Date: 1992-08-04 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1355.txt End: Rfc: RFC1354 Status: Proposed_Standard Authors: F. Baker, Title: IP Forwarding Table MIB Date: 1992-07-06 Pages: 12 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1354.txt End: Rfc: RFC1353 Status: Historic Authors: K. McCloghrie, J. Davin, J. Galvin, Title: Definitions of Managed Objects for Administration of SNMP Parties Date: 1992-07-06 Pages: 26 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1353.txt End: Rfc: RFC1352 Status: Historic Authors: J. Davin, J. Galvin, K. McCloghrie, Title: SNMP Security Protocols Date: 1992-07-06 Pages: 41 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1352.txt End: Rfc: RFC1351 Status: Historic Authors: J. Davin, J. Galvin, K. McCloghrie, Title: SNMP Administrative Model Date: 1992-07-06 Pages: 35 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1351.txt End: Rfc: RFC1350 Status: Standard Authors: K. Sollins, Title: THE TFTP PROTOCOL (REVISION 2) Date: 1992-07-10 Pages: 11 Format: .txt Obsoletes: RFC0783 Url: ftp://ds.internic.net/rfc/rfc1350.txt End: Rfc: RFC1349 Status: Proposed_Standard Authors: P. Almquist, Title: Type of Service in the Internet Protocol Suite Date: 1992-07-06 Pages: 28 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1349.txt Obsoleted-by: RFC2474 End: Rfc: RFC1348 Status: Experimental Authors: B. Manning, Title: DNS NSAP RRs Date: 1992-07-01 Pages: 4 Format: .txt Keywords: DNS Obsoleted-by: RFC1637 Url: ftp://ds.internic.net/rfc/rfc1348.txt End: Rfc: RFC1347 Status: Informational Authors: R. Callon, Title: TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing Date: 1992-06-19 Pages: 9 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1347.txt End: Rfc: RFC1346 Status: Informational Authors: P. Jones, Title: Resource Allocation, Control, and Accounting for the Use of Network Resources Date: 1992-06-19 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1346.txt End: Rfc: RFC1345 Status: Informational Authors: K. Simonsen, Title: Character Mnemonics & Character Sets Date: 1992-06-11 Pages: 103 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1345.txt End: Rfc: RFC1344 Status: Informational Authors: N. Borenstein, Title: Implications of MIME for Internet Mail Gateways Date: 1992-06-11 Pages: 9 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1344.txt End: Rfc: RFC1343 Status: Informational Authors: N. Borenstein, Title: A User Agent Configuration Mechanism For Multimedia Mail Format Information Date: 1992-06-11 Pages: 10 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1343.txt End: Rfc: RFC1342 Status: Proposed_Standard Authors: K. Moore, Title: Representation of Non-ASCII Text in Internet Message Headers Date: 1992-06-11 Pages: 7 Format: .txt Obsoleted-by: RFC1522 Url: ftp://ds.internic.net/rfc/rfc1342.txt End: Rfc: RFC1341 Status: Proposed_Standard Authors: N. Borenstein, N. Freed, Title: MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies Date: 1992-06-11 Pages: 80 Format: .txt, .ps Obsoleted-by: RFC1521 Url: ftp://ds.internic.net/rfc/rfc1341.txt End: Rfc: RFC1340 Status: Standard Authors: J. Reynolds, J. Postel, Title: ASSIGNED NUMBERS Date: 1992-07-10 Pages: 139 Format: .txt Obsoletes: RFC1060 Obsoleted-by: RFC1700 Url: ftp://ds.internic.net/rfc/rfc1340.txt End: Rfc: RFC1339 Status: Experimental Authors: S. Dorner, P. Resnick, Title: Remote Mail Checking Protocol Date: 1992-06-29 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1339.txt End: Rfc: RFC1338 Status: Informational Authors: V. Fuller, T. Li, K. Varadhan, J. Yu, Title: Supernetting: an Address Assignment and Aggregation Strategy Date: 1992-06-26 Pages: 20 Format: .txt Keywords: IPaddress Obsoleted-by: RFC1519 Url: ftp://ds.internic.net/rfc/rfc1338.txt End: Rfc: RFC1337 Status: Informational Authors: R. Braden, Title: TIME-WAIT Assassination Hazards in TCP Date: 1992-05-27 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1337.txt End: Rfc: RFC1336 Status: Informational Authors: G. Malkin, Title: Who's Who in the Internet Biographies of IAB, IESG and IRSG Members Date: 1992-05-27 Pages: 33 Format: .txt Obsoletes: RFC1251 Url: ftp://ds.internic.net/rfc/rfc1336.txt End: Rfc: RFC1335 Authors: Z. Wang, J. Crowcroft, Title: A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion Date: 1992-05-26 Pages: 7 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1335.txt End: Rfc: RFC1334 Status: Proposed_Standard Authors: B. Lloyd, W. Simpson, Title: PPP Authentication Protocols Date: 1992-10-20 Pages: 16 Format: .txt Keywords: PPP Obsoleted-by: RFC1334 Url: ftp://ds.internic.net/rfc/rfc1334.txt End: Rfc: RFC1333 Status: Proposed_Standard Authors: W. Simpson, Title: PPP Link Quality Monitoring Date: 1992-05-26 Pages: 17 Format: .txt Keywords: PPP Obsoleted-by: RFC1989 Url: ftp://ds.internic.net/rfc/rfc1333.txt End: Rfc: RFC1332 Status: Proposed_Standard Authors: G. McGregor, Title: The PPP Internet Protocol Control Protocol (IPCP) Date: 1992-05-26 Pages: 14 Format: .txt Keywords: PPP Obsoletes: RFC1172 Url: ftp://ds.internic.net/rfc/rfc1332.txt End: Rfc: RFC1331 Status: Proposed_Standard Authors: W. Simpson, Title: The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links Date: 1992-05-26 Pages: 69 Format: .txt Obsoletes: RFC1171 Obsoleted-by: RFC1548 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1331.txt End: Rfc: RFC1330 Status: Informational Authors: ESCC X.500/X.400 Task Force, Title: Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESnet Community Date: 1992-05-22 Pages: 87 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1330.txt End: Rfc: RFC1329 Status: Informational Authors: P. Kuehn, Title: Thoughts on Address Resolution for Dual MAC FDDI Networks Date: 1992-05-19 Pages: 28 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1329.txt End: Rfc: RFC1328 Status: Proposed_Standard Authors: S. Hardcastle-Kille, Title: X.400 1988 to 1984 downgrading Date: 1992-05-18 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1328.txt End: Rfc: RFC1327 Status: Proposed_Standard Authors: S. Hardcastle-Kille, Title: Mapping between X.400(1988) / ISO 10021 and RFC 822 Date: 1992-05-18 Pages: 113 Format: .txt Obsoletes: RFC1148 Keywords: SMTP Url: ftp://ds.internic.net/rfc/rfc1327.txt Obsoleted-by: RFC2156 End: Rfc: RFC1326 Status: Informational Authors: P. Tsuchiya, Title: Mutual Encapsulation Considered Dangerous Date: 1992-05-15 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1326.txt End: Rfc: RFC1325 Status: Informational Authors: G. Malkin, A. Marine, Title: FYI on Questions and Answers Answers to Commonly asked ``New Internet User'' Questions Date: 1992-05-15 Pages: 42 Format: .txt Obsoletes: RFC1206 Obsoleted-by: RFC1594 Url: ftp://ds.internic.net/rfc/rfc1325.txt End: Rfc: RFC1324 Status: Informational Authors: D. Reed, Title: A Discussion on Computer Network Conferencing Date: 1992-05-13 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1324.txt End: Rfc: RFC1323 Status: Proposed_Standard Authors: D. Borman, R. Braden, V. Jacobson, Title: TCP Extensions for High Performance Date: 1992-05-13 Pages: 37 Format: .txt Obsoletes: RFC1185 Url: ftp://ds.internic.net/rfc/rfc1323.txt End: Rfc: RFC1322 Status: Informational Authors: D. Estrin, S. Hotz, Y. Rekhter, Title: A Unified Approach to Inter-Domain Routing Date: 1992-05-11 Pages: 38 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1322.txt End: Rfc: RFC1321 Status: Informational Authors: R. Rivest, Title: The MD5 Message-Digest Algorithm Date: 1992-04-16 Pages: 21 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1321.txt End: Rfc: RFC1320 Status: Informational Authors: R. Rivest, Title: The MD4 Message-Digest Algorithm Date: 1992-04-16 Pages: 20 Format: .txt Obsoletes: RFC1186 Url: ftp://ds.internic.net/rfc/rfc1320.txt End: Rfc: RFC1319 Status: Informational Authors: B. Kaliski, Title: The MD2 Message-Digest Algorithm Date: 1992-04-16 Pages: 17 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1319.txt End: Rfc: RFC1318 Status: Proposed_Standard Authors: B. Stewart, Title: Definitions of Managed Objects for Parallel-printer-like Hardware Devices Date: 1992-04-16 Pages: 11 Format: .txt Obsoleted-by: RFC1660 Url: ftp://ds.internic.net/rfc/rfc1318.txt End: Rfc: RFC1317 Status: Proposed_Standard Authors: B. Stewart, Title: Definitions of Managed Objects for RS-232-like Hardware Devices Date: 1992-04-16 Pages: 17 Format: .txt Obsoleted-by: RFC1659 Url: ftp://ds.internic.net/rfc/rfc1317.txt End: Rfc: RFC1316 Status: Proposed_Standard Authors: B. Stewart, Title: Definitions of Managed Objects for Character Stream Devices Date: 1992-04-16 Pages: 17 Format: .txt Obsoleted-by: RFC1658 Url: ftp://ds.internic.net/rfc/rfc1316.txt End: Rfc: RFC1315 Status: Proposed_Standard Authors: C. Brown, F. Baker, C. Carvalho, Title: Management Information Base for Frame Relay DTEs Date: 1992-04-09 Pages: 19 Format: .txt Keywords: SNMP Obsoleted-by: RFC2115 Url: ftp://ds.internic.net/rfc/rfc1315.txt End: Rfc: RFC1314 Status: Proposed_Standard Authors: D. Cohen, A. Katz, Title: A File Format for the Exchange of Images in the Internet Date: 1992-04-10 Pages: 23 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1314.txt End: Rfc: RFC1313 Status: Informational Authors: C. Partridge, Title: Today's Programming for KRFC AM 1313 Internet Talk Radio Date: 1992-04-01 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1313.txt End: Rfc: RFC1312 Status: Experimental Authors: R. Nelson, G. Arnold, Title: Message Send Protocol Date: 1992-04-01 Pages: 8 Format: .txt Obsoletes: RFC1159 Url: ftp://ds.internic.net/rfc/rfc1312.txt End: Rfc: RFC1311 Status: Informational Authors: Internet Activities Board, A. Chapin, Title: Introduction to the STD Notes Date: 1992-03-14 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1311.txt End: Rfc: RFC1310 Status: Informational Authors: Internet Activities Board, A. Chapin, Title: The Internet Standards Process Date: 1992-03-14 Pages: 23 Format: .txt Obsoleted-by: RFC1602 Keywords: Standards Url: ftp://ds.internic.net/rfc/rfc1310.txt End: Rfc: RFC1309 Status: Informational Authors: S. Heker, J. Reynolds, C. Weider, Title: Technical Overview of Directory Services Using the X.500 Protocol Date: 1992-03-12 Pages: 16 Keywords: LDAP Format: .txt Url: ftp://ds.internic.net/rfc/rfc1309.txt End: Rfc: RFC1308 Status: Informational Authors: J. Reynolds, C. Weider, Title: Executive Introduction to Directory Services Using the X.500 Protocol Date: 1992-03-12 Pages: 4 Keywords: LDAP Format: .txt Url: ftp://ds.internic.net/rfc/rfc1308.txt End: Rfc: RFC1307 Status: Experimental Authors: A. Nicholson, J. Young, Title: Dynamically Switched Link Control Protocol Date: 1992-03-12 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1307.txt End: Rfc: RFC1306 Status: Informational Authors: A. Nicholson, J. Young, Title: Experiences Supporting By-Request Circuit-Switched T3 Networks Date: 1992-03-12 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1306.txt End: Rfc: RFC1305 Status: Proposed_Standard Authors: D. Mills, Title: Network Time Protocol (v3) Date: 1992-04-09 Pages: 120 Format: .txt Obsoletes: RFC1119 Url: ftp://ds.internic.net/rfc/rfc1305.txt End: Rfc: RFC1304 Status: Proposed_Standard Authors: T. Cox, K. Tesink, Title: Definitions of Managed Objects for the SIP Interface Type Date: 1992-02-28 Pages: 25 Format: .txt Obsoleted-by: RFC1694 Url: ftp://ds.internic.net/rfc/rfc1304.txt End: Rfc: RFC1303 Status: Informational Authors: K. McCloghrie, M. Rose, Title: A Convention for Describing SNMP-based Agents Date: 1992-02-26 Pages: 12 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1303.txt End: Rfc: RFC1302 Status: Informational Authors: D. Sitzler, P. Smith, A. Marine, Title: Building a Network Information Services Infrastructure Date: 1992-02-25 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1302.txt End: Rfc: RFC1301 Status: Informational Authors: S. Armstrong, A. Freier, K. Marzullo, Title: Multicast Transport Protocol Date: 1992-02-19 Pages: 38 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1301.txt End: Rfc: RFC1300 Status: Informational Authors: S. Greenfield, Title: Remembrances of Things Past Date: 1992-02-07 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1300.txt End: Rfc: RFC1298 Status: Informational Authors: R. Wormley, S. Bostock, Title: SNMP over IPX Date: 1992-02-07 Pages: 5 Format: .txt Obsoleted-by: RFC1420 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1298.txt End: Rfc: RFC1297 Status: Informational Authors: D. Johnson, Title: NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist (``NOC TT REQUIREMENTS'') Date: 1992-01-31 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1297.txt End: Rfc: RFC1296 Status: Informational Authors: M. Lottor, Title: Internet Growth (1981-1991) Date: 1992-01-29 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1296.txt End: Rfc: RFC1295 Status: Informational Authors: NADF, Title: User Bill of Rights for entries and listings in the Public Directory Date: 1992-01-29 Pages: 2 Format: .txt Obsoleted-by: RFC1417 Url: ftp://ds.internic.net/rfc/rfc1295.txt End: Rfc: RFC1294 Status: Proposed_Standard Authors: T. Bradley, C. Brown, A. Malis, Title: Multiprotocol Interconnect over Frame Relay Date: 1992-01-17 Pages: 28 Format: .txt Obsoleted-by: RFC1490,RFC2427 Url: ftp://ds.internic.net/rfc/rfc1294.txt End: Rfc: RFC1293 Status: Proposed_Standard Authors: T. Bradley, C. Brown, Title: Inverse Address Resolution Protocol Date: 1992-01-17 Pages: 6 Keywords: IPaddress Format: .txt Url: ftp://ds.internic.net/rfc/rfc1293.txt Obsoleted-by: RFC2390 End: Rfc: RFC1292 Status: Informational Authors: R. Lang, R. Wright, Title: A Catalog of Available X.500 Implementations Date: 1992-01-03 Pages: 103 Format: .txt Obsoleted-by: RFC1632 Url: ftp://ds.internic.net/rfc/rfc1292.txt End: Rfc: RFC1291 Status: Informational Authors: V. Aggarwal, Title: Mid-Level Networks: Potential Technical Services Date: 1991-12-30 Pages: 10 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1291.txt End: Rfc: RFC1290 Status: Informational Authors: J. Martin, Title: There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places Date: 1991-12-31 Pages: 27 Format: .txt Obsoleted-by: RFC1402 Url: ftp://ds.internic.net/rfc/rfc1290.txt End: Rfc: RFC1289 Status: Proposed_Standard Authors: J. Saperia, Title: DECnet Phase IV MIB Extensions Date: 1991-12-20 Pages: 64 Format: .txt Keywords: SNMP Obsoleted-by: RFC1559 Url: ftp://ds.internic.net/rfc/rfc1289.txt End: Rfc: RFC1288 Status: Draft_Standard Authors: D. Zimmerman, Title: The Finger User Information Protocol Date: 1991-12-19 Pages: 12 Format: .txt Obsoletes: RFC1196 Url: ftp://ds.internic.net/rfc/rfc1288.txt End: Rfc: RFC1287 Status: Informational Authors: R. Braden, V. Cerf, L. Chapin, D. Clark, R. Hobby, Title: Towards the Future Internet Architecture Date: 1991-12-12 Pages: 29 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1287.txt End: Rfc: RFC1286 Status: Proposed_Standard Authors: K. McCloghrie, E. Decker, P. Langille, A. Rijsinghani, Title: Definitions of Managed Objects for Bridges Date: 1991-12-11 Pages: 40 Format: .txt Obsoleted-by: RFC1525, Url: ftp://ds.internic.net/rfc/rfc1286.txt End: Rfc: RFC1285 Status: Proposed_Standard Authors: J. Case, Title: FDDI Management Information Base Date: 1992-01-24 Pages: 46 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1285.txt End: Rfc: RFC1284 Status: Proposed_Standard Authors: J. Cook, Title: Definitions of Managed Objects for the Ethernet-like Interface Types Date: 1991-12-04 Pages: 21 Format: .txt Obsoleted-by: RFC1398 Url: ftp://ds.internic.net/rfc/rfc1284.txt End: Rfc: RFC1283 Status: Experimental Authors: M. Rose, Title: SNMP over OSI Date: 1991-12-06 Pages: 8 Format: .txt Obsoletes: RFC1161 Obsoleted-by: RFC1418 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1283.txt End: Rfc: RFC1282 Status: Informational Authors: B. Kantor, Title: BSD Rlogin Date: 1991-12-04 Pages: 5 Format: .txt Obsoletes: RFC1258 Url: ftp://ds.internic.net/rfc/rfc1282.txt End: Rfc: RFC1281 Status: Informational Authors: S. Crocker, B. Fraser, R. Pethia, Title: Guidelines for the Secure Operation of the Internet Date: 1991-11-27 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1281.txt End: Rfc: RFC1280 Status: Standard Authors: Internet Activities Board, A. Chapin, Title: IAB OFFICIAL PROTOCOL STANDARDS Date: 1992-03-14 Pages: 32 Format: .txt Obsoletes: RFC1250 Obsoleted-by: RFC1360,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1280.txt End: Rfc: RFC1279 Authors: S. Kille, Title: X.500 and Domains Date: 1991-11-27 Pages: 13 Format: .txt, .ps Keywords: LDAP Url: ftp://ds.internic.net/rfc/rfc1279.txt End: Rfc: RFC1278 Status: Informational Authors: S. Hardcastle-Kille, Title: A String Encoding of Presentation Address Date: 1991-11-27 Pages: 5 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1278.txt End: Rfc: RFC1277 Status: Proposed_Standard Authors: S. Kille, Title: Encoding Network Addresses to Support Operation Over Non-OSI Lower Layers Date: 1991-11-27 Pages: 10 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1277.txt End: Rfc: RFC1276 Status: Proposed_Standard Authors: S. Kille, Title: Replication and Distributed Operations extensions to provide an Internet Directory using X.500 Date: 1991-11-27 Pages: 17 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1276.txt End: Rfc: RFC1275 Status: Informational Authors: S. Kille, Title: Replication Requirements to provide an Internet Directory using X.500 Date: 1991-11-27 Pages: 17 Keywords: LDAP Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1275.txt End: Rfc: RFC1274 Status: Proposed_Standard Authors: P. Barker, S. Kille, Title: The COSINE and Internet X.500 Schema Date: 1991-11-27 Pages: 60 Keywords: LDAP Format: .txt Url: ftp://ds.internic.net/rfc/rfc1274.txt End: Rfc: RFC1273 Status: Informational Authors: M. Schwartz, Title: A Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations Date: 1991-11-14 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1273.txt End: Rfc: RFC1272 Status: Informational Authors: D. Hirsh, C. Mills, G. Ruth, Title: Internet Accounting: Background Date: 1991-11-11 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1272.txt End: Rfc: RFC1271 Status: Proposed_Standard Authors: S. Waldbusser, Title: Remote Network Monitoring Management Information Base Date: 1991-11-12 Pages: 81 Format: .txt Obsoleted-by: RFC1757 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1271.txt End: Rfc: RFC1270 Status: Informational Authors: F. Kastenholz, Title: SNMP Communications Services Date: 1991-10-30 Pages: 11 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1270.txt End: Rfc: RFC1269 Status: Proposed_Standard Authors: J. Burruss, S. Willis, Title: Definitions of Managed Objects for the Border Gateway Protocol (Version 3) Date: 1991-10-26 Pages: 13 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1269.txt End: Rfc: RFC1268 Status: Draft_Standard Authors: P. Gross, Y. Rekhter, Title: Application of the Border Gateway Protocol in the Internet Date: 1991-10-25 Pages: 13 Format: .txt Obsoletes: RFC1164 Obsoleted-by: RFC1655 Url: ftp://ds.internic.net/rfc/rfc1268.txt End: Rfc: RFC1267 Status: Draft_Standard Authors: K. Lougheed, Y. Rekhter, Title: A Border Gateway Protocol 3 (BGP-3) Date: 1991-10-25 Pages: 35 Format: .txt Obsoletes: RFC1163 Url: ftp://ds.internic.net/rfc/rfc1267.txt End: Rfc: RFC1266 Status: Informational Authors: Y. Rekhter, Title: Experience with the BGP Protocol Date: 1991-10-28 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1266.txt End: Rfc: RFC1265 Status: Informational Authors: Y. Rekhter, Title: BGP Protocol Analysis Date: 1991-10-28 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1265.txt End: Rfc: RFC1264 Status: Informational Authors: B. Hinden, Title: Internet Routing Protocol Standardization Criteria Date: 1991-10-25 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1264.txt End: Rfc: RFC1263 Status: Informational Authors: L. Peterson, S. O'Malley, Title: TCP Extensions Considered Harmful Date: 1991-10-22 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1263.txt End: Rfc: RFC1262 Status: Internet Authors: Activities Board, Title: Guidelines for Internet Measurement Activities Date: 1991-10-15 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1262.txt End: Rfc: RFC1261 Status: Informational Authors: S. Williamson, L. Nobile, Title: Transition of NIC Services Date: 1991-09-19 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1261.txt End: Rfc: RFC1259 Status: Informational Authors: M. Kapor, Title: Building The Open Road: The NREN As Test-Bed For The National Public Network Date: 1991-09-17 Pages: 23 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1259.txt End: Rfc: RFC1258 Status: Informational Authors: B. Kantor, Title: BSD Rlogin Date: 1991-09-11 Pages: 5 Format: .txt Obsoleted-by: RFC1282 Url: ftp://ds.internic.net/rfc/rfc1258.txt End: Rfc: RFC1257 Status: Informational Authors: C. Partridge, Title: Isochronous Applications Do Not Require Jitter-Controlled Networks Date: 1991-09-09 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1257.txt End: Rfc: RFC1256 Status: Proposed_Standard Authors: S. Deering, Title: ICMP Router Discovery Messages Date: 1991-09-05 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1256.txt End: Rfc: RFC1255 Status: Informational Authors: T. Directory Forum, Title: A Naming Scheme for c=US Date: 1991-09-05 Pages: 25 Format: .txt Obsoletes: RFC1218 Url: ftp://ds.internic.net/rfc/rfc1255.txt End: Rfc: RFC1254 Status: Informational Authors: A. Mankin, K. Ramakrishnan, Title: Gateway Congestion Control Survey Date: 1991-08-30 Pages: 25 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1254.txt End: Rfc: RFC1253 Status: Proposed_Standard Authors: F. Baker, R. Coltun, Title: OSPF Version 2 Management Information Base Date: 1991-08-30 Pages: 42 Format: .txt Obsoletes: RFC1252 Obsoleted-by: RFC1850 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1253.txt End: Rfc: RFC1252 Status: Proposed_Standard Authors: F. Baker, R. Coltun, Title: OSPF Version 2 Management Information Base Date: 1991-08-21 Pages: 42 Format: .txt Obsoletes: RFC1248 Obsoleted-by: RFC1253 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1252.txt End: Rfc: RFC1251 Authors: G. Malkin, Title: Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members Date: 1991-08-19 Pages: 26 Format: .txt Obsoleted-by: RFC1336 Url: ftp://ds.internic.net/rfc/rfc1251.txt End: Rfc: RFC1250 Status: Standard Authors: J. Postel, Title: IAB Official Protocol Standards Date: 1991-08-26 Pages: 28 Format: .txt Obsoletes: RFC1200 Obsoleted-by: RFC1280,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1250.txt End: Rfc: RFC1249 Status: Informational Authors: T. Howes, M. Smith, B. Beecher, Title: DIXIE Protocol Specification Date: 1991-08-09 Pages: 10 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1249.txt End: Rfc: RFC1248 Status: Proposed_Standard Authors: F. Baker, R. Coltun, Title: OSPF Version 2 Management Information Base Date: 1991-08-08 Pages: 42 Format: .txt Obsoleted-by: RFC1252 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1248.txt End: Rfc: RFC1247 Status: Draft_Standard Authors: J. Moy, Title: OSPF Version 2 Date: 1991-08-08 Pages: 189 Format: .txt, .ps Obsoletes: RFC1131 Obsoleted-by: RFC1583 Url: ftp://ds.internic.net/rfc/rfc1247.txt End: Rfc: RFC1246 Status: Informational Authors: J. Moy, Title: Experience with the OSPF Protocol Date: 1991-08-08 Pages: 31 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1246.txt End: Rfc: RFC1245 Status: Informational Authors: J. Moy, Title: OSPF Protocol Analysis Date: 1991-08-08 Pages: 12 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1245.txt End: Rfc: RFC1244 Status: Informational Authors: P. Holbrook, J. Reynolds, Title: Site Security Handbook Date: 1991-07-23 Pages: 101 Format: .txt Obsoleted-by: RFC2196 Url: ftp://ds.internic.net/rfc/rfc1244.txt End: Rfc: RFC1243 Status: Proposed_Standard Authors: S. Waldbusser, Title: AppleTalk Management Information Base Date: 1991-07-08 Pages: 29 Format: .txt Obsoleted-by: RFC1742 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1243.txt End: Rfc: RFC1242 Authors: S. Bradner, Title: Benchmarking Terminology for Network Interconnection Devices Date: 1991-07-02 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1242.txt End: Rfc: RFC1241 Status: Experimental Authors: D. Mills, R. Woodburn, Title: A Scheme for an Internet Encapsulation Protocol: Version 1 Date: 1991-07-02 Pages: 15 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1241.txt End: Rfc: RFC1240 Status: Proposed_Standard Authors: K. Dobbins, W. Haggerty, C. Shue, Title: OSI Connectionless Transport Services on top of UDP - Version: 1 Date: 1991-06-26 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1240.txt End: Rfc: RFC1239 Status: Proposed_Standard Authors: J. Reynolds, Title: Reassignment of Experimental MIBs to Standard MIBs Date: 1991-06-25 Pages: 2 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1239.txt End: Rfc: RFC1238 Status: Experimental Authors: G. Satz, Title: CLNS MIB - for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Date: 1991-06-25 Pages: 32 Format: .txt Obsoletes: RFC1162 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1238.txt End: Rfc: RFC1237 Status: Proposed_Standard Authors: R. Colella, E. Gardner, R. Callon, Title: Guidelines for OSI NSAP Allocation in the Internet Date: 1991-07-23 Pages: 49 Format: .txt, .ps Obsoleted-by: RFC1629 Url: ftp://ds.internic.net/rfc/rfc1237.txt End: Rfc: RFC1236 Authors: L. Morales, P. Hasse, Title: IP to X.121 Address Mapping for DDN Date: 1991-06-25 Pages: 7 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1236.txt End: Rfc: RFC1235 Status: Experimental Authors: J. Ioannidis, G. Maguire, Jr., Title: The Coherent File Distribution Protocol Date: 1991-06-20 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1235.txt End: Rfc: RFC1234 Status: Proposed_Standard Authors: D. Provan, Title: Tunneling IPX Traffic through IP Networks Date: 1991-06-20 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1234.txt End: Rfc: RFC1233 Status: Historic Authors: T. Cox, K. Tesink, Title: Definitions of Managed Objects for the DS3 Interface Type Date: 1991-05-23 Pages: 23 Format: .txt Obsoleted-by: RFC1407 Url: ftp://ds.internic.net/rfc/rfc1233.txt End: Rfc: RFC1232 Status: Historic Authors: F. Baker, C. Kolb, Title: Definitions of Managed Objects for the DS1 Interface Type Date: 1991-05-23 Pages: 28 Format: .txt Obsoleted-by: RFC1406 Url: ftp://ds.internic.net/rfc/rfc1232.txt End: Rfc: RFC1231 Status: Draft_Standard Authors: E. Decker, R. Fox, K. McCloghrie, Title: IEEE 802.5 Token Ring MIB Date: 1993-02-11 Pages: 23 Format: .txt Obsoleted-by: RFC1743 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1231.txt End: Rfc: RFC1230 Status: Historic Authors: R. Fox, K. McCloghrie, Title: IEEE 802.4 Token Bus MIB Date: 1991-05-23 Pages: 23 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1230.txt End: Rfc: RFC1229 Status: Draft_Standard Authors: K. McCloghrie, Title: Extensions to the Generic-Interface MIB Date: 1992-08-03 Pages: 16 Format: .txt Obsoleted-by: RFC1573 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1229.txt End: Rfc: RFC1228 Status: Experimental Authors: G. Carpenter, B. Wijnen, Title: SNMP-DPI - Simple Network Management Protocol Distributed Program Interface Date: 1991-05-23 Pages: 50 Format: .txt Obsoleted-by: RFC1592 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1228.txt End: Rfc: RFC1227 Status: Experimental Authors: M. Rose, Title: SNMP MUX Protocol and MIB Date: 1991-05-23 Pages: 13 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1227.txt End: Rfc: RFC1226 Status: Experimental Authors: B. Kantor, Title: Internet Protocol Encapsulation of AX.25 Frames Date: 1991-05-13 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1226.txt End: Rfc: RFC1225 Status: Draft_Standard Authors: M. Rose, Title: Post Office Protocol - Version 3 Date: 1991-05-14 Pages: 16 Format: .txt Obsoletes: RFC1081 Obsoleted-by: RFC1460 Url: ftp://ds.internic.net/rfc/rfc1225.txt End: Rfc: RFC1224 Status: Experimental Authors: L. Steinberg, Title: Techniques for Managing Asynchronously Generated Alerts Date: 1991-05-10 Pages: 22 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1224.txt End: Rfc: RFC1223 Authors: J. Halpern, Title: OSI CLNS and LLC1 Protocols on Network Systems HYPERchannel Date: 1991-05-09 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1223.txt End: Rfc: RFC1222 Authors: H. Braun, Y. Rekhter, Title: Advancing the NSFNET Routing Architecture Date: 1991-05-08 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1222.txt End: Rfc: RFC1221 Authors: W. Edmond, Title: Host Access Protocol (HAP) Specification - Version 2 Date: 1991-04-16 Pages: 68 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1221.txt End: Rfc: RFC1220 Status: Proposed_Standard Authors: F. Baker, Title: Point-to-Point Protocol Extensions for Bridging Date: 1991-04-17 Pages: 18 Format: .txt Keywords: PPP Obsoleted-by: RFC1638 Url: ftp://ds.internic.net/rfc/rfc1220.txt End: Rfc: RFC1219 Authors: P. Tsuchiya, Title: On the Assignment of Subnet Numbers Date: 1991-04-16 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1219.txt End: Rfc: RFC1218 Status: Informational Authors: North American Directory Forum, Title: A Naming Scheme for c=US Date: 1991-04-03 Pages: 23 Format: .txt Obsoleted-by: RFC1255 Url: ftp://ds.internic.net/rfc/rfc1218.txt End: Rfc: RFC1217 Status: Informational Authors: V. Cerf, Title: Memo from the Consortium for Slow Commotion Research (CSCR) Date: 1991-04-01 Pages: 5 Format: .txt Keywords: Lirpa1 Url: ftp://ds.internic.net/rfc/rfc1217.txt End: Rfc: RFC1216 Authors: P. Kunikos, P. Richard, Title: Gigabit Network Economics and Paradigm Shifts Date: 1991-03-30 Pages: 4 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1216.txt End: Rfc: RFC1215 Status: Informational Authors: M. Rose, Title: A Convention for Defining Traps for use with the SNMP Date: 1991-03-27 Pages: 9 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1215.txt End: Rfc: RFC1214 Status: Historic Authors: L. Labarre, Title: OSI Internet Management: Management Information Base Date: 1991-04-05 Keywords: SNMP Pages: 83 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1214.txt End: Rfc: RFC1213 Status: Standard Authors: K. McCloghrie, M. Rose, Title: Management Information Base for Network Management of TCP/IP-based internets: MIB-II Date: 1991-03-26 Pages: 70 Format: .txt Obsoletes: RFC1158 Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1213.txt End: Rfc: RFC1212 Status: Standard Authors: K. McCloghrie, M. Rose, Title: Concise MIB Definitions Date: 1991-03-26 Pages: 19 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1212.txt End: Rfc: RFC1211 Authors: A. Westine, J. Postel, Title: Problems with the Maintenance of Large Mailing Lists Date: 1991-03-22 Pages: 54 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1211.txt End: Rfc: RFC1210 Authors: V. Cerf, P. Kirstein, B. Randell, Title: Network and Infrastructure User Requirements for Transatlantic Research Collaboration - Brussels, July 16-18, and Washington July 24-25, 1990 Date: 1991-03-21 Pages: 36 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1210.txt End: Rfc: RFC1209 Status: Draft_Standard Authors: J. Lawrence, D. Piscitello, Title: The Transmission of IP Datagrams over the SMDS Service Date: 1991-03-06 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1209.txt End: Rfc: RFC1208 Authors: O. Jacobsen, D. Lynch, Title: A Glossary of Networking Terms Date: 1991-03-04 Pages: 18 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1208.txt End: Rfc: RFC1207 Authors: G. Malkin, A. Marine, J. Reynolds, Title: Answers to Commonly asked ``Experienced Internet User'' Questions Date: 1991-02-28 Pages: 15 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1207.txt End: Rfc: RFC1206 Authors: G. Malkin, A. Marine, Title: FYI on Questions and Answers - Answers to Commonly asked ``New Internet User'' Questions Date: 1991-02-26 Pages: 32 Format: .txt Obsoletes: RFC1177 Obsoleted-by: RFC1325 Url: ftp://ds.internic.net/rfc/rfc1206.txt End: Rfc: RFC1205 Authors: P. Chmielewski, Title: 5250 Telnet Interface Date: 1991-02-21 Pages: 12 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1205.txt End: Rfc: RFC1204 Status: Experimental Authors: D. Lee, S. Yeh, Title: Message Posting Protocol (MPP) Date: 1991-02-15 Pages: 6 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1204.txt End: Rfc: RFC1203 Status: Historic Authors: J. Rice, Title: Interactive Mail Access Protocol - Version 3 Date: 1991-02-08 Pages: 49 Format: .txt Obsoletes: RFC1064 Keywords: IMAP Url: ftp://ds.internic.net/rfc/rfc1203.txt End: Rfc: RFC1202 Status: Informational Authors: M. Rose, Title: Directory Assistance Service Date: 1991-02-07 Pages: 11 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1202.txt End: Rfc: RFC1201 Status: Historic Authors: D. Provan, Title: Transmitting IP Traffic over ARCNET Networks Date: 1991-02-01 Pages: 7 Format: .txt Obsoletes: RFC1051 Url: ftp://ds.internic.net/rfc/rfc1201.txt End: Rfc: RFC1200 Status: Standard Authors: J. Postel, Title: IAB Official Protocol Standards Date: 1991-04-01 Pages: 31 Format: .txt Obsoletes: RFC1140 Obsoleted-by: RFC1250,RFC2300,RFC2400 Url: ftp://ds.internic.net/rfc/rfc1200.txt End: Rfc: RFC1199 Status: Informational Authors: J. Reynolds, Title: Request for Comments Summary RFC Numbers 1100-1199 Date: 1991-12-31 Pages: 22 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1199.txt End: Rfc: RFC1198 Status: Informational Authors: B. Scheifler, Title: FYI on the X Window System Date: 1991-01-01 Pages: 3 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1198.txt End: Rfc: RFC1197 Status: Informational Authors: M. Sherman, Title: Using ODA for Translating Multimedia Information Date: 1990-12-31 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1197.txt End: Rfc: RFC1196 Status: Draft_Standard Authors: D. Zimmerman, Title: The Finger User Information Protocol Date: 1990-12-26 Pages: 12 Format: .txt Obsoletes: RFC1194 Obsoleted-by: RFC1288 Url: ftp://ds.internic.net/rfc/rfc1196.txt End: Rfc: RFC1195 Status: Proposed_Standard Authors: R. Callon, Title: Use of OSI IS-IS for Routing in TCP/IP and Dual Environments Date: 1990-12-19 Pages: 68 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1195.txt End: Rfc: RFC1194 Status: Draft_Standard Authors: D. Zimmerman, Title: The Finger User Information Protocol Date: 1990-11-21 Pages: 12 Format: .txt Obsoletes: RFC0742 Obsoleted-by: RFC1196 Url: ftp://ds.internic.net/rfc/rfc1194.txt End: Rfc: RFC1193 Authors: D.Ferrari, Title: Client Requirements for Real-Time Communication Services Date: 1990-11-15 Pages: 24 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1193.txt End: Rfc: RFC1192 Authors: B. Kahin, Title: Commercialization of the Internet Summary Report Date: 1990-11-12 Pages: 13 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1192.txt End: Rfc: RFC1191 Status: Draft_Standard Authors: J. Mogul, S. Deering, Title: Path MTU Discovery Date: 1990-11-16 Pages: 19 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1191.txt End: Rfc: RFC1190 Status: Experimental Authors: C. Topolcic, Title: Experimental Internet Stream Protocol, Version 2 (ST-II) Date: 1990-10-30 Pages: 148 Format: .txt Obsoleted-by: RFC1819 Url: ftp://ds.internic.net/rfc/rfc1190.txt End: Rfc: RFC1189 Status: Historic Authors: L. Besaw, B. Handspicker, L. LaBarre, U. Warrier, Title: The Common Management Information Services and Protocols for the Internet Date: 1990-10-26 Pages: 15 Format: .txt Obsoletes: RFC1095 Url: ftp://ds.internic.net/rfc/rfc1189.txt End: Rfc: RFC1188 Status: Draft_Standard Authors: D. Katz, Title: A Proposed Standard for the Transmission of IP Datagrams over FDDI Networks Date: 1990-10-30 Pages: 10 Format: .txt Obsoletes: RFC1103 Obsoleted-by: RFC1390 Url: ftp://ds.internic.net/rfc/rfc1188.txt End: Rfc: RFC1187 Status: Experimental Authors: J. Davin, K. McCloghrie, M. Rose, Title: Bulk Table Retrieval with the SNMP Date: 1990-10-18 Pages: 12 Format: .txt Keywords: SNMP Url: ftp://ds.internic.net/rfc/rfc1187.txt End: Rfc: RFC1186 Status: Informational Authors: R. Rivest, Title: The MD4 Message Digest Algorithm Date: 1990-10-18 Pages: 18 Format: .txt Obsoleted-by: RFC1320 Url: ftp://ds.internic.net/rfc/rfc1186.txt End: Rfc: RFC1185 Status: Experimental Authors: R. Braden, V. Jacobson, L. Zhang, Title: TCP Extension for High-Speed Paths Date: 1990-10-15 Pages: 21 Format: .txt Obsoleted-by: RFC1323 Url: ftp://ds.internic.net/rfc/rfc1185.txt End: Rfc: RFC1184 Status: Draft_Standard Authors: D. Borman, Title: Telnet Linemode Option Date: 1990-10-15 Pages: 23 Format: .txt Obsoletes: RFC1116 Url: ftp://ds.internic.net/rfc/rfc1184.txt End: Rfc: RFC1183 Status: Experimental Authors: R. Ullman, P. Mockapetris, L. Mamakos, C. Everhart, Title: New DNS RR Definitions Date: 1990-10-08 Pages: 11 Keywords: DNS Format: .txt Url: ftp://ds.internic.net/rfc/rfc1183.txt End: Rfc: RFC1181 Authors: R. Blokzijl, Title: RIPE Terms of Reference Date: 1990-09-26 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1181.txt End: Rfc: RFC1180 Authors: T. Socolofsky, C. Kale, Title: A TCP/IP Tutorial Date: 1991-01-15 Pages: 28 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1180.txt End: Rfc: RFC1179 Status: Informational Authors: L. McLaughlin, III, Title: Line Printer Daemon Protocol Date: 1990-09-04 Pages: 14 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1179.txt End: Rfc: RFC1178 Authors: D. Libes, Title: Choosing a Name for Your Computer Date: 1990-09-04 Pages: 8 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1178.txt End: Rfc: RFC1177 Authors: G. Malkin, A. Marine, J. Reynolds, Title: FYI on Questions and Answers - Answers to Commonly Asked ``New Internet User'' Questions Date: 1990-09-04 Pages: 24 Format: .txt Obsoleted-by: RFC1206 Url: ftp://ds.internic.net/rfc/rfc1177.txt End: Rfc: RFC1176 Status: Experimental Authors: M. Crispin, Title: Interactive Mail Access Protocol - Version 2 Date: 1990-08-20 Pages: 30 Format: .txt Obsoletes: RFC1064 Url: ftp://ds.internic.net/rfc/rfc1176.txt End: Rfc: RFC1175 Authors: M. A. Yuan, J. K. Roubicek, K. T. LaQuey, Title: FYI on Where to Start - A Bibliography of Internetworking Information Date: 1990-08-16 Pages: 43 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1175.txt End: Rfc: RFC1174 Status: Informational Authors: V. Cerf, Title: IAB Recommended Policy on Distributing Internet Identifier Assignment and IAB Recommended Policy Change to Internet "Connected" Status Date: 1990-08-09 Pages: 9 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1174.txt End: Rfc: RFC1173 Authors: J. Van Bokkelen, Title: Responsibilities of Host and Network Managers A Summary of the "Oral Tradition" of the Internet Date: 1990-08-07 Pages: 5 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1173.txt End: Rfc: RFC1172 Status: Proposed_Standard Authors: R. Hobby, D. Perkins, Title: The Point-to-Point Protocol (PPP) Initial Configuration Options Date: 1990-07-24 Pages: 40 Format: .txt Obsoleted-by: RFC1332 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1172.txt End: Rfc: RFC1171 Status: Draft_Standard Authors: D. Perkins, Title: The Point-to-Point Protocol for the Transmission of Multi-Protocol Datagrams Over Point-to-Point Links Date: 1990-07-24 Pages: 48 Format: .txt Obsoletes: RFC1134 Obsoleted-by: RFC1331 Keywords: PPP Url: ftp://ds.internic.net/rfc/rfc1171.txt End: Rfc: RFC1170 Status: Informational Authors: R. Fougner, Title: Public Key Standards and Licenses Date: 1991-01-11 Pages: 2 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1170.txt End: Rfc: RFC1169 Authors: K. Mills, V. Cerf, Title: Explaining the Role of GOSIP Date: 1990-08-09 Pages: 15 Format: .txt Url: ftp://ds.internic.net/rfc/rfc1169.txt End: Rfc: RFC1168 Status: Ward, Authors: J. Postel, DeSchon, A. Westine, Title: Intermail and Commercial Mail Relay Services Date: 1990-07-17 Pages: 23 Format: .txt, .ps Url: ftp://ds.internic.net/rfc/rfc1168.txt E