Movatterモバイル変換

Network Working Group                                         J. ElliottRequest for Comments: 1499                                           ISICategory: Informational                                     January 1997Request for Comments Summary                         RFC Numbers 1400-1499Status of This Memo   This RFC is a slightly annotated list of the 100 RFCs fromRFC 1400   through RFCs 1499.  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.Note   Many RFCs, but not all, are Proposed Standards, Draft Standards, or   Standards.  Since the status of these RFCs may change during the   standards processing, we note here only that they are on the   standards track.  Please see the latest edition of "Internet Official   Protocol Standards" for the current state and status of these RFCs.   In the following, RFCs on the standards track are marked [STANDARDS-   TRACK].RFC     Author       Date      Title---     ------       ----      -----1499    Elliott    Jan 97   Requests For Comments SummaryThis memo.1498    Saltzer    Aug 93   On the Naming and Binding of Network                              DestinationsThis brief paper offers a perspective on the subject of names ofdestinations in data communication networks. It suggests two ideas:First, it is helpful to distinguish among four different kinds ofobjects that may be named as the destination of a packet in a network.Second, the operating system concept of binding is a useful way todescribe the relations among the four kinds of objects.  This memoprovides information for the Internet community.  It does not specify anInternet standard.Elliott                      Informational                      [Page 1]

RFC 1499                  Summary of 1400-1499              January 19971497    Reynolds   Aug 93   BOOTP Vendor Information ExtensionsThis RFC is a slight revision and extension ofRFC-1048 by PhilipPrindeville, who should be credited with the original work in this memo.This memo is a status report on the vendor information extensions usedin the Bootstrap Protocol (BOOTP).1496    AlverstrandAug 93   Rules for Downgrading Messages from                              X.400/88 to X.400/84 When MIME                              Content-Types are Present in the                              MessagesThis document describes howRFC-1328 must be modified in order toprovide adequate support for the scenarios:                    SMTP(MIME) -> X.400(84)                    X.400(84) -> SMTP(MIME)It replaces chapter 6 ofRFC-1328. The rest ofRFC-1328 is NOTobsoleted.  [STANDARDS-TRACK]1495    AlverstrandAug 93   Mapping between X.400 andRFC-822                              Message BodiesSince the introduction of X.400(84), there has been work ongoing fordefining mappings between MHS andRFC-822.  The most recent work in thisarea isRFC-1327 [3], which focuses primarily on translation of envelopeand headers.  This document is complimentary toRFC-1327 as it focuseson translation of the message body.  [STANDARDS-TRACK]1494    AlverstrandAug 93   Equivalences between 1988 X.400 andRFC-822 Message BodiesThis document describes the content of the "IANA MHS/MIME Equivalencetable", and defines the initial configuration of this table.  Mappingsfor new MIME content-types and/or X.400 body part types should beregistered with the IANA to minimize redundancy and promoteinteroperability. [STANDARDS-TRACK]Elliott                      Informational                      [Page 2]

RFC 1499                  Summary of 1400-1499              January 19971493    Decker     Jul 93   Definitions of Managed Objects                              for BridgesThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP based internets.  Inparticular it defines objects for managing MAC bridges based on the IEEE802.1D-1990 standard between Local Area Network (LAN) segments.[STANDARDS-TRACK]1492    Finseth    Jul 93   An Access Control Protocol, Sometimes                              Called TACACSThis RFC documents the extended TACACS protocol use by the Cisco Systemsterminal servers.  This same protocol is used by the University ofMinnesota's distributed authentication system.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard.1491    Weider     Jul 93   A Survey of Advanced Usages of X.500This document is the result of a survey asking people to detail theiradvanced usages of X.500. It is intended to show how variousorganizations are using X.500 in ways which extend the view of X.500 asa "White Pages" service.  This RFC is a product of the IntegratedDirectory Services Working Group of the Application and User ServicesAreas of the IETF.  This memo provides information for the Internetcommunity.  It does not specify an Internet standard.1490    Bradley    Jul 93   Multiprotocol Interconnect over Frame                              RelayThis memo describes an encapsulation method for carrying networkinterconnect traffic over a Frame Relay backbone.  It covers aspects ofboth Bridging and Routing.  Additionally, it describes a simplefragmentation procedure for carrying large frames over a frame relaynetwork with a smaller MTU.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 3]

RFC 1499                  Summary of 1400-1499              January 19971489    Chernov    Jul 93   Registration of a Cyrillic Character SetThough the proposed character set "koi8-r" is not currently aninternational standard, there is very large user community (includingRelcom Net) supporting it.  Factually, "koi8-r" is de-facto standard forUnix and global network applications in the former Soviet Union.  Thisis the reason the Society of Unix User Groups (SUUG) believes "koi8-r"should be registered.  This memo provides information for the Internetcommunity.  It does not specify an Internet standard.1488    Howes      Jul 93   The X.500 String Representation of                              Standard Attribute SyntaxesThis document defines the requirements that must be satisfied byencoding rules used to render Directory attribute syntaxes into a formsuitable for use in the LDAP, then goes on to define the encoding rulesfor the standard set of attribute syntaxes defined in [1,2] and [3].[STANDARDS-TRACK]1487    Yeong      Jul 93   X.500 Lightweight Directory Access                              ProtocolThe protocol described in this document is designed to provide access tothe Directory while not incurring the resource requirements of theDirectory Access Protocol (DAP).  [STANDARDS-TRACK]1486    Rose       Jul 93   An Experiment in Remote PrintingThis memo describes a technique for "remote printing" using the Internetmail infrastructure.  In particular, this memo focuses on the case inwhich remote printers are connected to the international telephonenetwork.  This memo defines an Experimental Protocol for the Internetcommunity.  It does not specify an Internet standard.1485    Kille      Jul 93   A String Representation of Distinguished                              Names (OSI-DS 23 (v5))When a distinguished name is communicated between to users not using adirectory protocol (e.g., in a mail message), there is a need to have auser-oriented string representation of distinguished name.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 4]

RFC 1499                  Summary of 1400-1499              January 19971484    Kille      Jul 93   Using the OSI Directory to achieve                              User Friendly Naming (OSI-DS 24 (v1.2))This proposal sets out some conventions for representing names in afriendly manner, and shows how this can be used to achieve reallyfriendly naming.  This memo defines an Experimental Protocol for theInternet community.  It does not specify an Internet standard.1483    Heinanen   Jul 93   Multiprotocol Encapsulation over ATM                              Adaptation Layer 5This memo describes two encapsulations methods for carrying networkinterconnect traffic over ATM AAL5.  [STANDARDS-TRACK]1482    Knopper    Jun 93   Aggregation Support in the NSFNET                              Policy-Based Routing DatabaseThis document describes plans for support of route aggregation, asspecified in the descriptions of Classless Inter-Domain Routing (CIDR)[1] and the BGP-4 protocol [2], by the NSFNET Backbone Network Service.This memo provides information for the Internet community.  It does notspecify an Internet standard.1481    Huitema    Jul 93   IAB Recommendation for an Intermediate                              Strategy to Address the Issue of ScalingCIDR is proposed as an immediate term strategy to extend the life of thecurrent 32 bit IP address space.  This memo provides information for theInternet community.  It does not specify an Internet standard.1480    Cooper     Jun 93   The US DomainThis is a description of the US Top Level Domains on the Internet.  Thismemo provides information for the Internet community. It does notspecify an Internet standard.1479    Steenstrup Jul 93   Inter-Domain Policy Routing Protocol                              Specification: Version 1We present the set of protocols and procedures that constitute Inter-Domain Policy Routing (IDPR).  [STANDARDS-TRACK]Elliott                      Informational                      [Page 5]

RFC 1499                  Summary of 1400-1499              January 19971478    Steenstrup Jul 93   An Architecture for Inter-Domain Policy                              RoutingWe present an architecture for inter-domain policy routing (IDPR).[STANDARDS-TRACK]1477    Steenstrup Jul 93   IDPR as a Proposed StandardThis document contains a discussion of inter-domain policy routing(IDPR), including an overview of functionality and a discussion ofexperiments.  This memo provides information for the Internet community.It does not specify an Internet standard.1476    Ullman     Jun 93   RAP: Internet Route Access ProtocolThis RFC describes an open distance vector routing protocol for use atall levels of the internet, from isolated LANs to the major routers ofan international commercial network provider.  This memo defines anExperimental Protocol for the Internet community.  It does not specifyan Internet standard.1475    Ullman     Jun 93   TP/IX: The Next InternetThis memo presents the specification for version 7 of the InternetProtocol, as well as version 7 of the TCP and the user datagramprotocol.  This memo defines an Experimental Protocol for the Internetcommunity.  It does not specify an Internet standard.1474    KastrenholzJun 93   The Definitions of Managed Objects for                              the Bridge Network Control Protocol of                              the Point-to-Point ProtocolThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it describes managed objects used for managing the bridgeNetwork Control Protocol [10] on subnetwork interfaces using the familyof Point-to-Point Protocols.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 6]

RFC 1499                  Summary of 1400-1499              January 19971473    KastrenholzJun 93   The Definitions of Managed Objects for                              the IP Network Control Protocol of                              the Point-to-Point ProtocolThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it describes managed objects used for managing the IPNetwork Control Protocol on subnetwork interfaces using the family ofPoint-to-Point Protocols [8, 9, 10, 11, & 12].  [STANDARDS-TRACK]1472    KastrenholzJun 93   The Definitions of Managed Objects for                              the Security Protocols of                              the Point-to-Point ProtocolThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it describes managed objects used for managing the SecurityProtocols on subnetwork interfaces using the family of Point-to-PointProtocols [8, 9, 10, 11, & 12].  [STANDARDS-TRACK]1471    KastrenholzJun 93   The Definitions of Managed Objects for                              the Link Control Protocol of                              the Point-to-Point ProtocolThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it describes managed objects used for managing the LinkControl Protocol and Link Quality Monitoring on subnetwork interfacesthat use the family of Point-to-Point Protocols [8, 9, 10, 11, & 12].[STANDARDS-TRACK]1470    Enger      Jun 93   FYI on a Network Management Tool                              Catalog: Tools for Monitoring and                              Debugging TCP/IP Internets and                              Interconnected DevicesThe goal of this FYI memo is to provide an update to FYI 2,RFC 1147[1], which provided practical information to site administrators andnetwork managers.  This memo provides information for the Internetcommunity.  It does not specify an Internet standard.Elliott                      Informational                      [Page 7]

RFC 1499                  Summary of 1400-1499              January 19971469    Pusateri   Jun 93   IP Multicast over Token-Ring Local Area                              NetworksThis document specifies a method for the transmission of IP multicastdatagrams over Token-Ring Local Area Networks.  [STANDARDS-TRACK]1468    Murai      Jun 93   Japanese Character Encoding for Internet                              MessagesThis document describes the encoding used in electronic mail [RFC822]and network news [RFC1036] messages in several Japanese networks.  Thismemo provides information for the Internet community.  It does notspecify an Internet standard.1467    Topolcic   Aug 93   Status of CIDR Deployment in the                              InternetThis document describes the current status of the development anddeployment of CIDR technology into the Internet. This document replacesRFC 1367, which was a schedule for the deployment of IP address spacemanagement procedures to support route aggregation.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard.1466    Gerich     May 93   Guidelines for Management of IP Address                              SpaceThis document proposes a plan which will forward the implementation ofRFC 1174 and which defines the allocation and assignment of the networknumber space.  This memo provides information for the Internetcommunity.  It does not specify an Internet standard.1465    EppenbergerMay 93   Routing Coordination for X.400 MHS                              Services Within a Multi Protocol / Multi                              Network Environment Table Format V3 for                              Static RoutingThis document proposes short term solutions for maintaining anddistributing routing information and shows how messages can travel overdifferent networks by using multi stack MTAs as relays.  This memodefines an Experimental Protocol for the Internet community.Elliott                      Informational                      [Page 8]

RFC 1499                  Summary of 1400-1499              January 19971464    Rosenbaum  May 93   Using the Domain Name System                              To Store Arbitrary String AttributesThis paper describes a simple means to associate arbitrary stringinformation (ASCII text) with attributes that have not been defined bythe DNS.  This memo defines an Experimental Protocol for the Internetcommunity.1463    Hoffman    May 93   FYI on Introducing the Internet--                              A Short Bibliography of Introductory                              Internetworking Readings for the Network                              NoviceThis bibliography offers a short list of recent information resourcesthat will help the network novice become familiar with the Internet,including its associated networks, resources, protocols, and history.This memo provides information for the Internet community.  It does notspecify an Internet standard.1462    Krol       May 93   FYI on "What is the Internet?"This FYI RFC answers the question, "What is the Internet?"  and isproduced by the User Services Working Group of the Internet EngineeringTask Force (IETF).  This memo provides information for the Internetcommunity.  It does not specify an Internet standard.1461    Throop     May 93   SNMP MIB extension for Multiprotocol                              Interconnect over X.25This memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it defines objects for managing Multiprotocol Interconnect(including IP) traffic carried over X.25.  [STANDARDS-TRACK]1460    Rose       Jun 93   Post Office Protocol - Version 3This memo is a revision toRFC 1225, a Draft Standard.  [STANDARDS-TRACK]Elliott                      Informational                      [Page 9]

RFC 1499                  Summary of 1400-1499              January 19971459    Oikarinen  May 93   Internet Relay Chat ProtocolThe IRC protocol is a text-based protocol, with the simplest clientbeing any socket program capable of connecting to the server.  This memodefines an Experimental Protocol for the Internet community.1458    Braudes    May 93   Requirements for Multicast ProtocolsThis memo discusses some of these unresolved issues, and provides ahigh-level design for a new multicast transport protocol, group addressand membership authority, and modifications to existing routingprotocols.  This memo provides information for the Internet community.It does not specify an Internet standard.1457    Housley    May 93   Security Label Framework for the                              InternetThis memo presents a security labeling framework for the Internet.  Theframework is intended to help protocol designers determine what, if any,security labeling should be supported by their protocols.  This memoprovides information for the Internet community.  It does not specify anInternet standard.1456    V.S.W.G.   May 93   Conventions for Encoding the Vietnamese                              Language VISCII: VIetnamese Standard                              Code for Information Interchange VIQR:                              Vietnamese Quoted-Readable Specification                              Revision 1.1This document provides information to the Internet community on thecurrently used conventions for encoding Vietnamese characters into 7-bitUS ASCII and in an 8-bit form.  This memo provides information for theInternet community.  It does not specify an Internet standard.1455    Eastlake   May 93   Physical Link Security Type of ServiceThis RFC documents an experimental protocol providing a Type of Service(TOS) to request maximum physical link security.  This is an addition tothe types of service enumerated inRFC 1349: Type of Service in theInternet Protocol Suite.  This memo defines an Experimental Protocol forthe Internet community.Elliott                      Informational                     [Page 10]

RFC 1499                  Summary of 1400-1499              January 19971454    Dixon      May 93   Comparison of Proposals for Next Version                              of IPThis is a slightly edited reprint of RARE Technical Report (RTC(93)004).This memo provides information for the Internet community.  It does notspecify an Internet standard.1453    Chimiak    Apr 93   A Comment on Packet Video Remote                              Conferencing and the Transport/Network                              LayersThis RFC is a vehicle to inform the Internet community about XTP as itbenefits from past Internet activity and targets general-purposeapplications and multimedia applications with the emerging ATM networksin mind.  This memo provides information for the Internet community.  Itdoes not specify an Internet standard.1452    Case       Apr 93   Coexistence between version 1 and                              version 2 of the Internet-standard                              Network Management FrameworkThe purpose of this document is to describe coexistence between version2 of the Internet-standard Network Management Framework, termed the SNMPversion 2 framework (SNMPv2) [1], and the original Internet-standardNetwork Management Framework (SNMPv1).  [STANDARDS-TRACK]1451    Case       Apr 93   Manager-to-Manager                              Management Information BaseIt is the purpose of this document to define managed objects whichdescribe the behavior of a SNMPv2 entity acting in both a manager roleand an agent role.  [STANDARDS-TRACK]1450    Case       Apr 93   Management Information Base for version                              2 of the Simple Network Management                              Protocol (SNMPv2)It is the purpose of this document to define managed objects whichdescribe the behavior of a SNMPv2 entity.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 11]

RFC 1499                  Summary of 1400-1499              January 19971449    Case       Apr 93   Transport Mapplings for version 2 of the                              Simple Network Management Protocol                              (SNMPv2)It is the purpose of this document to define how the SNMPv2 maps onto aninitial set of transport domains.  [STANDARDS-TRACK]1448    Case       Apr 93   Protocol Operations for version 2 of the                              Simple Network Management Protocol                              (SNMPv2)It is the purpose of this document, Protocol Operations for SNMPv2, todefine the operations of the protocol with respect to the sending andreceiving of the PDUs.  [STANDARDS-TRACK]1447    McCloghrie Apr 93   Party MIB for version 2 of the Simple                              Network Management Protocol (SNMPv2)The Administrative Model for SNMPv2 document [3] defines the propertiesassociated with SNMPv2 parties, SNMPv2 contexts, and access controlpolicies.  It is the purpose of this document, the Party MIB for SNMPv2,to define managed objects which correspond to these properties.[STANDARDS-TRACK]1446    Galvin     Apr 93   Security Protocols for version 2 of the                              Simple Network Management Protocol                              (SNMPv2)It is the purpose of this document, Security Protocols for SNMPv2, todefine one such authentication and one such privacy protocol.[STANDARDS-TRACK]1445    Galvin     Apr 93   Administrative Model for version 2 of                              the Simple Network Management Protocol                              (SNMPv2)It is the purpose of this document, the Administrative Model for SNMPv2,to define how the administrative framework is applied to realizeeffective network management in a variety of configurations andenvironments.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 12]

RFC 1499                  Summary of 1400-1499              January 19971444    Case       Apr 93   Conformance Statements for version 2 of                              the Simple Network Management Protocol                              (SNMPv2)It may be useful to define the acceptable lower-bounds ofimplementation, along with the actual level of implementation achieved.It is the purpose of this document to define the notation used for thesepurposes.  [STANDARDS-TRACK]1443    Case       Apr 93   Textual Conventions for version 2 of the                              Simple Network Management Protocol                              (SNMPv2)It is the purpose of this document to define the initial set of textualconventions available to all MIB modules.  [STANDARDS-TRACK]1442    Case       Apr 93   Structure of Management Information for                              version 2 of the Simple Network                              Management Protocol (SNMPv2)Management information is viewed as a collection of managed objects,residing in a virtual information store, termed the ManagementInformation Base (MIB).  Collections of related objects are defined inMIB modules.  These modules are written using a subset of OSI's AbstractSyntax Notation One (ASN.1) [1].  It is the purpose of this document,the Structure of Management Information (SMI), to define that subset.[STANDARDS-TRACK]1441    Case       Apr 93   Introduction to version 2 of the                              Internet-standard Network Management                              FrameworkThe purpose of this document is to provide an overview of version 2 ofthe Internet-standard Network Management Framework, termed the SNMPversion 2 framework (SNMPv2).  [STANDARDS-TRACK]1440    Troth      Jul 93   SIFT/UFT: Sender-Initiated/Unsolicited                              File TransferThis document describes a Sender-Initiated File Transfer (SIFT)protocol, also commonly called Unsolicited File Transfer (UFT) protocol.This memo defines an Experimental Protocol for the Internet community.Elliott                      Informational                     [Page 13]

RFC 1499                  Summary of 1400-1499              January 19971439    Finseth    Mar 93   The Uniqueness of Unique IdentifiersThis RFC provides information that may be useful when selecting a methodto use for assigning unique identifiers to people.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard.1438    Chapin     Apr 93   IETF Statements Of Boredom (SOB)sThis document creates a new subseries of RFCs, entitled, IETF StatementsOf Boredom (SOBs).  This memo provides information for the Internetcommunity.  It does not specify an Internet standard.1437    Borenstein Apr 93   The Extension of MIME Content-Types to a                              New MediumThis document defines one particular type of MIME data, the matter-transport/sentient-life-form type.  This memo provides information forthe Internet community.  It does not specify an Internet standard.1436    Anklesaria Mar 93   The Internet Gopher ProtocolThis document describes the protocol, lists some of the implementationscurrently available, and has an overview of how to implement new clientand server applications.  This memo provides information for theInternet community.  It does not specify an Internet standard.1435    Knowles    Mar 93   IESG Advice from Experience with Path                              MTU DiscoveryIn the course of reviewing the MTU Discovery protocol for possibleelevation to Draft Standard, a specific operational problem wasuncovered.  The problem results from the optional suppression of ICMPmessages implemented in some routers.  This memo outlines a modificationto this practice to allow the correct functioning of MTU Discovery.This memo provides information for the Internet community.  It does notspecify an Internet standard.Elliott                      Informational                     [Page 14]

RFC 1499                  Summary of 1400-1499              January 19971434    Dixon      Mar 93   Data Link Switching: Switch-to-Switch                              ProtocolThis RFC describes IBM's support of Data Link Switching over TCP/IP.This memo provides information for the Internet community.  It does notspecify an Internet standard.1433    Garrett    Mar 93   Directed ARPDirected ARP is a dynamic address resolution procedure that enableshosts and routers to resolve advertised potential next-hop IP addresseson foreign IP networks to their associated link level addresses.  Thismemo defines an Experimental Protocol for the Internet community.1432    Quarterman Mar 93   Recent Internet BooksHere is a list of books related to using the Internet.  This memoprovides information for the Internet community.  It does not specify anInternet standard.1431    Barker     Feb 93   DUA MetricsThis document defines a set of criteria by which a DUA implementation,or more precisely a Directory user interface, may be judged.  This memoprovides information for the Internet community.  It does not specify anInternet standard.1430    Kille      Feb 93   A Strategic Plan for Deploying an                              Internet X.500 Directory ServiceThis document describes an overall strategy for deploying a DirectoryService on the Internet, based on the OSI X.500 Directory Service.  Thismemo provides information for the Internet community.  It does notspecify an Internet standard.1429    Thomas     Feb 93   Listserv Distribute ProtocolThis memo specifies a subset of the distribution protocol used by theBITNET LISTSERV to deliver mail messages to large amounts of recipients.This memo provides information for the Internet community.  It does notspecify an Internet standard.Elliott                      Informational                     [Page 15]

RFC 1499                  Summary of 1400-1499              January 19971428    Vaudreuil  Feb 93   Transition of Internet Mail from                              Just-Send-8 to 8bit-SMTP/MIMEThis document outlines the problems in this environment and an approachto minimizing the cost of transition from current usage of non-MIME 8bitmessages to MIME.  This RFC provides information for the Internetcommunity.  It does not specify an Internet standard.1427    Klensin    Feb 93   SMTP Service Extension                              for Message Size DeclarationThis memo defines an extension to the SMTP service whereby an SMTPclient and server may interact to give the server an opportunity todecline to accept a message (perhaps temporarily) based on the client'sestimate of the message size.  [STANDARDS-TRACK]1426    Klensin    Feb 93   SMTP Service Extension                              for 8bit-MIMEtransportThis memo defines an extension to the SMTP service whereby an SMTPcontent body containing octets outside of the US ASCII octet range (hex00-7F) may be relayed using SMTP.  [STANDARDS-TRACK]1425    Klensin    Feb 93   SMTP Service ExtensionsThis memo defines a framework for extending the SMTP service by defininga means whereby a server SMTP can inform a client SMTP as to the serviceextensions it supports.  [STANDARDS-TRACK]1424    Kaliski     Feb 93   Privacy Enhancement for Internet                               Electronic Mail:  Part IV: Key                               Certification and Related ServicesThis document describes three types of service in support of InternetPrivacy-Enhanced Mail (PEM) [1-3]: key certification, certificate-revocation list (CRL) storage, and CRL retrieval.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 16]

RFC 1499                  Summary of 1400-1499              January 19971423    Balenson    Feb 93   Privacy Enhancement for Internet                               Electronic Mail:  Part III: Algorithms,                               Modes, and IdentifiersThis document provides definitions, formats, references, and citationsfor cryptographic algorithms, usage modes, and associated identifiersand parameters used in support of Privacy Enhanced Mail (PEM) in theInternet community.  [STANDARDS-TRACK]1422    Kent        Feb 93   Privacy Enhancement for Internet                               Electronic Mail:  Part II:                               Certificate-Based Key ManagementThis is one of a series of documents defining privacy enhancementmechanisms for electronic mail transferred using Internet mailprotocols.  [STANDARDS-TRACK]1421    Linn        Feb 93   Privacy Enhancement for Internet                               Electronic Mail:  Part I: Message                               Encryption and Authentication                               ProceduresThis document defines message encryption and authentication procedures,in order to provide privacy-enhanced mail (PEM) services for electronicmail transfer in the Internet.  [STANDARDS-TRACK]1420    Bostock     Mar 93   SNMP over IPXThis document defines a convention for encapsulating Simple NetworkManagement Protocol (SNMP) [1] packets over the transport mechanismprovided via the Internetwork Packet Exchange (IPX) protocol [2].[STANDARDS-TRACK]1419    Minshall    Mar 93   SNMP over AppleTalkThis memo describes the method by which the Simple Network ManagementProtocol (SNMP) as specified in [1] can be used over AppleTalk protocols[2] instead of the Internet UDP/IP protocol stack.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 17]

RFC 1499                  Summary of 1400-1499              January 19971418    Rose        Mar 93   SNMP over OSIThis memo addresses some concerns by defining a framework for runningthe SNMP in an environment which supports the OSI connectionless-modetransport service.  [STANDARDS-TRACK]1417    N.A.D.F.    Feb 93   NADF Standing Documents:                               A Brief OverviewThe purpose of this document is to provide a brief overview of theNADF's Standing Document series.  This memo provides information for theInternet community.  It does not specify an Internet standard.1416    Borman      Feb 93   Telnet Authentication OptionThisRFC 1416 replacesRFC 1409, which has an important typographicalerror in the example on page 6 (one occurance of "REPLY" should be"IS").  This memo defines an Experimental Protocol for the Internetcommunity.1415    Mindel      Jan 93   FTP-FTAM Gateway SpecificationThis memo describes a dual protocol stack application layer gateway thatperforms protocol translation, in an interactive environment, betweenthe FTP and FTAM file transfer protocols.  [STANDARDS-TRACK]1414    St. Johns   Feb 93   Identification MIBThis memo defines a MIB for use with identifying the users associatedwith TCP connections.  It provides functionality approximatelyequivalent to that provided by the protocol defined inRFC 1413 [1].[STANDARDS-TRACK]1413    St. Johns   Feb 93   Identification ProtocolThe Identification Protocol was formerly called the AuthenticationServer Protocol.  It has been renamed to better reflect its function.[STANDARDS-TRACK]Elliott                      Informational                     [Page 18]

RFC 1499                  Summary of 1400-1499              January 19971412    Alagappan   Jan 93   Telnet Authentication: SPXThis memo defines an Experimental Protocol for the Internet community.1411    Borman      Jan 93   Telnet Authentication:                               Kerberos Version 4This memo defines an Experimental Protocol for the Internet community.1410    I.A.B       Mar 93   IAB OFFICIAL PROTOCOL STANDARDSThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Architecture Board (IAB).1409    Borman      Jan 93   Telnet Authentication OptionThis memo defines an Experimental Protocol for the Internet community.1408    Borman      Jan 93   Telnet Environment OptionThis document specifies a mechanism for passing environment informationbetween a telnet client and server.  [STANDARDS-TRACK]1407    Cox         Jan 93   Definitions of Managed Objects for the                               DS3/E3 Interface TypeThis memo defines an extension to the Management Information Base (MIB)for use with network management protocols in TCP/IP-based internets.  Inparticular, it defines objects for managing DS3 and E3 Interfaces.[STANDARDS-TRACK]1406    Basker      Jan 93   Definitions of Managed Objects for the                               DS1 and E1 Interface TypesThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in TCP/IP-based internets.  Inparticular, it defines objects for managing DS1 Interfaces -- includingboth T1 and E1 (a.k.a., CEPT 2 Mbit/s) links.  [STANDARDS-TRACK]Elliott                      Informational                     [Page 19]

RFC 1499                  Summary of 1400-1499              January 19971405    Allocchio   Jan 93   Mapping between X.400(1984/1988) and                               Mail-11 (DECnet mail)This document describes a set of mappings which will enable interworking between systems operating the CCITT X.400 ( 1984 / 1988 )Recommendations on Message Handling Systems, and systems running theMail-11 (also known as DECnet mail) protocol.  This memo defines anExperimental Protocol for the Internet community.1404    Stockman    Jan 93   A Model for Common Operational                               StatisticsThis memo describes a model for operational statistics in the Internet.It gives recommendations for metrics, measurements, polling periods,storage formats and presentation formats.  This memo providesinformation for the Internet community.  It does not specify an Internetstandard.1403    Varadhan    Jan 93   BGP OSPF InteractionThis memo defines the various criteria to be used when designing anAutonomous System Border Routers (ASBR) that will run BGP with otherASBRs external to the AS and OSPF as its IGP.  [STANDARDS-TRACK]1402    Martin      Jan 93   There's Gold in them thar Networks!                               Searching for Treasure in all the Wrong                               PlacesThe ultimate goal is to make the route to these sources of informationinvisible to you.  At present, this is not easy to do.  I will explainsome of the techniques that can be used to make these nuggets easier topick up so that we all can be richer.  This RFC provides information forthe Internet community.  It does not specify an Internet standard.1401    I.A.B.      Jan 93   Correspondence between the IAB and DISA                               on the use of DNS throughout the                               InternetThis memo reproduces three letters exchanged between the InternetActivities Board (IAB) and the Defense Information Systems Agency (DISA)regarding the importance of using the Domain Name System (DNS)throughout the Internet, and phasing out the use of older host name toaddress tables, such as "hosts.txt".  This memo provides information forthe Internet community.  It does not specify an Internet standard.Elliott                      Informational                     [Page 20]

RFC 1499                  Summary of 1400-1499              January 19971400    Williamson  Mar 93   Transition and Modernization                               of the Internet Registration ServiceAs a result of the NREN NIS award by National Science Foundation, non-DDN registration services will soon be transferred from the DDN NIC tothe new Internet Registration Service, which is a part of an entityreferred to as the InterNIC.  This memo provides information for theInternet community.  It does not specify an Internet standard.Security Considerations   Security issues are not discussed in this memo.Author's Address   Josh Elliott   University of Southern California   Information Sciences Institute   4676 Admiralty Way   Marina del Rey, CA 90292   Phone:  (310) 822-1511   EMail: elliott@isi.eduElliott                      Informational                     [Page 21]