Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group M. KennedyRequest for Comments: 1599 ISICategory: Informational January 1997Request for Comments Summary RFC Numbers 1500 - 1599Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 1500 through RFCs 1599. 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--- ------ ---- -----1599 Kennedy Jan 96 Requests For Comments SummaryThis memo.1598 Simpson Mar 94 PPP in X.25The Point-to-Point Protocol (PPP) provides a standard method fortransporting multi-protocol datagrams over point-to-point links. Thisdocument describes the use of X.25 for framing PPP encapsulated packets.[STANDARDS-TRACK]Kennedy Informational [Page 1]
RFC 1599 Summary of 1500-1599 January 19971597 Rekhter Mar 94 Address Allocation for Private InternetsThis RFC describes methods to preserve IP address space by notallocating globally unique IP addresses to hosts private to anenterprise while still permitting full network layer connectivitybetween all hosts inside an enterprise as well as between all publichosts of different enterprises. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1296 Brown Mar 94 Definitions of Managed Objects for Frame Relay ServiceThis 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 the Frame Relay Service.[STANDARDS-TRACK]1295 Brown Mar 94 Definitions of Managed Objects for the SONET/SDH Interface TypeThis 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 Synchronous OpticalNetwork/Synchronous Digital Hierarchy (SONET/SDH) objects. Thisdocument is a companion document with Definitions of Managed Objects forthe DS1/E1 and DS3/E3 Interface Types,RFC1406 andRFC1407. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1594 Marine Mar 94 FYI on Questions and Answers Answers to Commonly asked "New Internet User" QuestionsThis FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A).The goal is to document the most commonly asked questions and answers inthe Internet. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind. [FYI 4]Kennedy Informational [Page 2]
RFC 1599 Summary of 1500-1599 January 19971593 McKenzie Mar 94 SNA APPN Node MIBThis RFC describes IBM's SNMP support for SNA Advanced Peer-to-PeerNetworking (APPN) nodes. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1592 Wijnen Mar 94 Simple Network Management ProtocolThis RFC describes version 2.0 of a protocol that International BusinessMachines Corporation (IBM) has been implementing in most of its SNMPagents to allow dynamic extension of supported MIBs. This memo definesan Experimental Protocol for the Internet community. This memo does notspecify an Internet standard of any kind.1591 Postel Mar 94 Domain Name System Structure and DelegationThis memo provides some information on the structure of the names in theDomain Name System (DNS), specifically the top-level domain names; andon the administration of domains. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1590 Postel Mar 94 Media Type Registration ProcedureSeveral questions have been raised about the requirements andadministrative procedure for registering MIME content-type and subtypes,and the use of these Media Types for other applications. This documentaddresses these issues and specifies a procedure for the registration ofnew Media Types (content-type/subtypes). It also generalizes the scopeof use of these Media Types to make it appropriate to use the sameregistrations and specifications with other applications. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1589 Mills Mar 94 A Kernel Model for Precision TimekeepingThis memorandum describes an engineering model which implements aprecision time-of-day function for a generic operating system. The modelis based on the principles of disciplined oscillators and phase-lockloops (PLL) often found in the engineering literature. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.Kennedy Informational [Page 3]
RFC 1599 Summary of 1500-1599 January 19971588 Postel Feb 94 White Pages Meeting ReportThis report describes the results of a meeting held at the November IETF(Internet Engineering Task Force) in Houston, TX, on November 2, 1993,to discuss the future of and approaches to a white pages directoryservices for the Internet. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1587 Coltun Mar 94 The OSPF NSSA OptionThis document describes a new optional type of OSPF area, somewhathumorously referred to as a "not-so-stubby" area (or NSSA). NSSAs aresimilar to the existing OSPF stub area configuration option but have theadditional capability of importing AS external routes in a limitedfashion. [STANDARDS-TRACK]1586 deSouza Mar 94 Guidelines for Running OSPF Over Frame Relay NetworksThis memo specifies guidelines for implementors and users of the OpenShortest Path First (OSPF) routing protocol to bring about improvementsin how the protocol runs over frame relay networks. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1585 Moy Mar 94 MOSPF: Analysis and ExperienceThis memo documents how the MOSPF protocol satisfies the requirementsimposed on Internet routing protocols by "Internet Engineering TaskForce internet routing protocol standardization criteria" ([RFC 1264]).This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1584 Moy Mar 94 Multicast Extensions to OSPFThis memo documents enhancements to the OSPF protocol enabling therouting of IP multicast datagrams. [STANDARDS-TRACK]1583 Moy Mar 94 OSPF Version 2This memo documents version 2 of the OSPF protocol. OSPF is a link-state routing protocol. [STANDARDS-TRACK]Kennedy Informational [Page 4]
RFC 1599 Summary of 1500-1599 January 19971582 Meyer Feb 94 Extensions to RIP to Support Demand CircuitsThis memo defines a generalized modification which can be applied toBellman-Ford (or distance vector) algorithm information broadcastingprotocols. [STANDARDS-TRACK]1581 Meyer Feb 94 Protocol Analysis for Extensions to RIP to Support Demand CircuitsAs required by Routing Protocol Criteria, this report documents the keyfeatures of Routing over Demand Circuits on Wide Area Networks - RIP andthe current implementation experience. This memo provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.1580 EARN Mar 94 Guide to Network Resource ToolsThe purpose of this guide is to supply the basic information that anyoneon the network needs to try out and begin using tools. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind. [FYI 23]1579 BellovinFeb 94 Firewall-Friendly FTPThis memo describes a suggested change to the behavior of FTP clientprograms. This document provides information for the Internet community.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1578 Sellers Feb 94 FYI on Questions and Answers Answers to Commonly Asked "Primary and Secondary School Internet User" QuestionsThe goal of this FYI RFC is to document the questions most commonlyasked about the Internet by those in the primary and secondary schoolcommunity, and to provide pointers to sources which answer thosequestions. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind. [FYI 22]Kennedy Informational [Page 5]
RFC 1599 Summary of 1500-1599 January 19971577 Laubach Jan 94 Classical IP and ARP over ATMThis memo defines an initial application of classical IP and ARP in anAsynchronous Transfer Mode (ATM) network environment configured as aLogical IP Subnetwork (LIS). [STANDARDS-TRACK]1576 Penner Jan 94 TN3270 Current PracticesThis document describes the existing implementation of transferring 3270display terminal data using currently available telnet capabilities.The name traditionally associated with this implementation is TN3270.This memo provides information for the Internet community. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1575 Hares Feb 94 An Echo Function for CLNP (ISO 8473)This memo defines an echo function for the connection-less network layerprotocol. The mechanism that is mandated here is in the final processof being standardized by ISO as "Amendment X: Addition of an Echofunction to ISO 8473" an integral part of Version 2 of ISO 8473.[STANDARDS-TRACK]1574 Hares Feb 94 Essential Tools for the OSI InternetThis document specifies the following three necessary tools to debugproblems in the deployment and maintenance of networks using ISO 8473(CLNP): ping or OSI Echo function, traceroute function which uses theOSI Echo function, and routing table dump function. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1573 McCloghrie Jan 94 Evolution of the Interfaces Group of MIB-IIThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it describes managed objects used for managing NetworkInterfaces. [STANARDS-TRACK]Kennedy Informational [Page 6]
RFC 1599 Summary of 1500-1599 January 19971572 Alexander Jan 94 Telnet Environment OptionThis document specifies a mechanism for passing environment informationbetween a telnet client and server. Use of this mechanism enables atelnet user to propagate configuration information to a remote host whenconnecting. [STANDARDS-TRACK]1571 Borman Jan 94 Telnet Environment Option Interoperability IssuesThis document describes a method for allowing implementors to ensurethat their implementation of the Environment option will beinteroperable with as many other implementations as possible, byproviding a set of heuristics that can be used to help identify whichdefinitions for VAR and VALUE are being used by the other side of theconnection. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1570 Simpson Jan 94 PPP LCP ExtensionsThe Point-to-Point Protocol (PPP) provides a standard method fortransporting multi-protocol datagrams over point-to-point links. PPPdefines an extensible Link Control Protocol (LCP) for establishing,configuring, and testing the data-link connection. This documentdefines several additional LCP features which have been suggested overthe past few years. [STANDARDS-TRACK]1569 Rose Jan 94 Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical ProceduresThis memo describes a technique for radio paging using the Internet mailinfrastructure. In particular, this memo focuses on the case in whichradio pagers are identified via the international telephone network.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1568 Gwinn Jan 94 Simple Network Paging Protocol - Version 1(b)This RFC suggests a simple way for delivering both alphanumeric andnumeric pages (one-way) to radio paging terminals. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.Kennedy Informational [Page 7]
RFC 1599 Summary of 1500-1599 January 19971567 MansfieldJan 94 X.500 Directory Monitoring MIBThis document defines a portion of the Management Information Base(MIB). It defines the MIB for monitoring Directory System Agents (DSA),a component of the OSI Directory. This MIB will be used in conjunctionwith the APPLICATION-MIB for monitoring DSAs. [STANDARDS-TRACK]1566 Kille Jan 94 Mail Monitoring MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, this memo extends the basic Network Services Monitoring MIBto allow monitoring of Message Transfer Agents (MTAs). It may also beused to monitor MTA components within gateways. [STANDARDS-TRACK]1565 Kille Jan 94 Network Services Monitoring MIBThis document defines a MIB which contains the elements common to themonitoring of any network service application. This informationincludes a table of all monitorable network service applications, acount of the associations (connections) to each application, and basicinformation about the parameters and status of each application-relatedassociation. [STANDARDS-TRACK]1564 Barker Jan 94 DSA Metrics (OSI-DS 34 (v3))This document defines a set of criteria by which a DSA implementationmay be judged. Particular issues covered include conformance tostandards; performance; demonstrated interoperability. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1563 BorensteinJan 94 The text/enriched MIME Content-typeMIME [RFC-1341,RFC-1521] defines a format and general framework for therepresentation of a wide variety of data types in Internet mail. Thisdocument defines one particular type of MIME data, the text/enrichedtype, a refinement of the "text/richtext" type defined inRFC 1341. Thetext/enriched MIME type is intended to facilitate the widerinteroperation of simple enriched text across a wide variety of hardwareand software platforms. This memo provides information for the Internetcommunity. This memo does not specify an Internet standard of any kind.Kennedy Informational [Page 8]
RFC 1599 Summary of 1500-1599 January 19971562 MichaelsonDec 93 Naming Guidelines for the AARNet X.500 Directory ServiceThis document is an AARNet (Australian Academic and Research Network)Engineering Note (AEN-001). AARNet Engineering Notes are engineeringdocuments of the AARNet Engineering Working Group, and record current orproposed operational practices related to the provision ofInternetworking services within Australia, and AARNet in particular.This memo provides information for the Internet community. This memodoes not specify an Internet standard of any kind.1561 PiscitelloDec 93 Use of ISO CLNP in TUBA EnvironmentsThis memo specifies a profile of the ISO/IEC 8473 Connectionless-modeNetwork Layer Protocol for use in conjunction withRFC 1347, TCP/UDPover Bigger Addresses. It describes the use of CLNP to provide thelower-level service expected by Transmission Control Protocol and UserDatagram Protocol. This memo defines an Experimental Protocol for theInternet community. This memo does not specify an Internet standard ofany kind.1560 Leiner Dec 93 The MultiProtocol InternetThere has recently been considerable discussion on two topics:MultiProtocol approaches in the Internet and the selection of a nextgeneration Internet Protocol. This document suggests a strawman positionfor goals and approaches for the IETF/IESG/IAB in these areas. It takesthe view that these two topics are related, and proposes directions forthe IETF/IESG/IAB to pursue. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1559 Saperia Dec 93 DECnet Phase IV MIB ExtensionsThis memo defines a set of DECnet Phase IV extensions that have beencreated for the Internet MIB. It reflects changes which are the resultof operational experience based onRFC 1289. [STANDARDS-TRACK]Kennedy Informational [Page 9]
RFC 1599 Summary of 1500-1599 January 19971558 Howes Dec 93 A String Representation of LDAP Search FiltersThe Lightweight Directory Access Protocol (LDAP) defines a networkrepresentation of a search filter transmitted to an LDAP server. Someapplications may find it useful to have a common way of representingthese search filters in a human-readable form. This document defines ahuman-readable string format for representing LDAP search filters. Thismemo provides information for the Internet community. This memo doesnot specify an Internet standard of any kind.1557 Choi Dec 93 Korean Character Encoding for Internet MessagesThis document describes the encoding method being used to representKorean characters in both header and body part of the Internet mailmessages [RFC822]. This encoding method was specified in 1991, and hassince then been used. It has now widely being used in Korean IPnetworks. This memo provides information for the Internet community.This memo does not specify an Internet standard of any kind.1556 NussbacherDec 93 Handling of Bi-directional Texts in MIMEThis document describes the format and syntax of the "direction" keywordto be used with bi-directional texts in MIME. This memo providesinformation for the Internet community. This memo does not specify anInternet standard of any kind.1555 Nussbacher Dec 93 Hebrew Character Encoding for Internet MessagesThis document describes the encoding used in electronic mail [RFC822]for transferring Hebrew. The standard devised makes use of MIME[RFC1521] and ISO-8859-8. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.Kennedy Informational [Page 10]
RFC 1599 Summary of 1500-1599 January 19971554 Ohta Dec 93 ISO-2022-JP-2: Multilingual Extension of ISO-2022-JPThis memo describes a text encoding scheme: "ISO-2022-JP-2", which isused experimentally for electronic mail [RFC822] and network news[RFC1036] messages in several Japanese networks. The encoding is amultilingual extension of "ISO-2022-JP", the existing encoding forJapanese [2022JP]. The encoding is supported by an Emacs basedmultilingual text editor: MULE [MULE]. This memo provides informationfor the Internet community. This memo does not specify an Internetstandard of any kind.1553 Mathur Dec 93 Compressing IPX Headers Over WAN Media (CIPX)This document describes a method for compressing the headers of IPXdatagrams (CIPX). [STANDARDS-TRACK]1552 Simpson Dec 93 The PPP Internetwork Packet Exchange Control Protocol (IPXCP)This document defines the Network Control Protocol for establishing andconfiguring the IPX protocol over PPP. [STANDARDS-TRACK]1551 Allen Dec 93 Novell IPX Over Various WAN Media (IPXWAN)This document describes how Novell IPX operates over various WAN media.Specifically, it describes the common "IPX WAN" protocol Novell uses toexchange necessary router to router information prior to exchangingstandard IPX routing information and traffic over WAN datalinks. Thismemo provides information for the Internet community. This memo doesnot specify an Internet standard of any kind.1550 Bradner Dec 93 IP: Next Generation (IPng) White Paper SolicitationThis memo solicits white papers on topics related to the IPngrequirements and selection criteria. This memo provides information forthe Internet community. This memo does not specify an Internet standardof any kind.Kennedy Informational [Page 11]
RFC 1599 Summary of 1500-1599 January 19971549 Simpson Dec 93 PPP in HDLC FramingThis document describes the use of HDLC for framing PPP encapsulatedpackets. [STANDARDS-TRACK]1548 Simpson Dec 93 The Point-to-Point Protocol (PPP)This document defines the PPP organization and methodology, and the PPPencapsulation, together with an extensible option negotiation mechanismwhich is able to negotiate a rich assortment of configuration parametersand provides additional management functions. [STANDARDS-TRACK]1547 Perkins Dec 93 Requirements for an Internet Standard Point-to-Point ProtocolThis document discusses the evaluation criteria for an Internet StandardData Link Layer protocol to be used with point-to-point links. This memoprovides information for the Internet community. This memo does notspecify an Internet standard of any kind.1546 PartridgeNov 93 Host Anycasting ServiceThis RFC describes an internet anycasting service for IP. The primarypurpose of this memo is to establish the semantics of an anycastingservice within an IP internet. This memo provides information for theInternet community. This memo does not specify an Internet standard ofany kind.1545 PiscitelloNov 93 FTP Operation Over Big Address Records (FOOBAR)This RFC specifies a method for assigning long addresses in the HOST-PORT specification for the data port to be used in establishing a dataconnection for File Transfer Protocol, FTP (STD 9,RFC 959). This is ageneral solution, applicable for all "next generation" IP alternatives,and can also be extended to allow FTP operation over transportinterfaces other than TCP. This memo defines an Experimental Protocolfor the Internet community. This memo does not specify an Internetstandard of any kind.Kennedy Informational [Page 12]
RFC 1599 Summary of 1500-1599 January 19971544 Rose Nov 93 The Content-MD5 Header FieldThis memo defines the use of an optional header field, Content-MD5,which may be used as a message integrity check (MIC), to verify that thedecoded data are the same data that were initially sent. [STANDARDS-TRACK]1543 Postel Oct 93 Instructions to RFC AuthorsThis Request for Comments (RFC) provides information about thepreparation of RFCs, and certain policies relating to the publication ofRFCs. This memo provides information for the Internet community. Thismemo does not specify an Internet standard of any kind.1542 Wimer Oct 93 Clarifications and Extensions for the Bootstrap ProtocolSome aspects of the BOOTP protocol were rather loosely defined in itsoriginal specification. In particular, only a general description wasprovided for the behavior of "BOOTP relay agents" (originally calledBOOTP forwarding agents"). The client behavior description alsosuffered in certain ways. This memo attempts to clarify and strengthenthe specification in these areas. [STANDARDS-TRACK]1541 Droms Oct 93 Dynamic Host Configuration ProtocolThe Dynamic Host Configuration Protocol (DHCP) provides a framework forpassing configuration information to hosts on a TCP/IP network. DHCP isbased on the Bootstrap Protocol (BOOTP) adding the capability ofautomatic allocation of reusable network addresses and additionalconfiguration options. [STANDARDS-TRACK]1540 IAB Oct 93 Internet Official Protocol StandardsThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Activities Board (IAB).[STANDARDS-TRACK]Kennedy Informational [Page 13]
RFC 1599 Summary of 1500-1599 January 19971539 Malkin Oct 93 A Guide for New Attendees of the Internet Engineering Task ForceThe purpose of this For Your Information (FYI) RFC is to explain to thenewcomers how the IETF works. This memo provides information for theInternet community. It does not specify an Internet standard. [FYI 17]1538 Behl Oct 93 Advanced SNA/IP : A Simple SNA Transport ProtocolThis RFC provides information for the Internet community about a methodfor establishing and maintaining SNA sessions over an IP internet. Thismemo provides information for the Internet community. It does notspecify an Internet standard.1537 BeertemaOct 93 Common DNS Data File Configuration ErrorsThis memo describes errors often found in DNS data files. It points outcommon mistakes system administrators tend to make and why they often gounnoticed for long periods of time. This memo provides information forthe Internet community. It does not specify an Internet standard.1536 Kumar Oct 93 Common DNS Implementation Errors and Suggested FixesThis memo describes common errors seen in DNS implementations andsuggests some fixes. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1535 Gavron Oct 93 A Security Problem and Proposed Correction With Widely Deployed DNS SoftwareThis document discusses a flaw in some of the currently distributed nameresolver clients. The flaw exposes a security weakness related to thesearch heuristic invoked by these same resolvers when users provide apartial domain name, and which is easy to exploit. This document pointsout the flaw, a case in point, and a solution. This memo providesinformation for the Internet community. It does not specify an Internetstandard.Kennedy Informational [Page 14]
RFC 1599 Summary of 1500-1599 January 19971534 Droms Oct 93 Interoperation Between DHCP and BOOTPDHCP provides a superset of the functions provided by BOOTP. Thisdocument describes the interactions between DHCP and BOOTP networkparticipants. [STANDARDS-TRACK]1533 Alexander Oct 93DHCP Options and BOOTP Vendor ExtensionsThis document specifies the current set of DHCP options. [STANDARDS-TRACK]1532 Wimer Oct 93 Clarifications and Extensions for the Bootstrap ProtocolSome aspects of the BOOTP protocol were rather loosely defined in itsoriginal specification. In particular, only a general description wasprovided for the behavior of "BOOTP relay agents" (originally calledBOOTP forwarding agents"). The client behavior description alsosuffered in certain ways. This memo attempts to clarify and strengthenthe specification in these areas. [STANDARDS-TRACK]1531 Droms Oct 93 Dynamic Host Configuration ProtocolThe Dynamic Host Configuration Protocol (DHCP) provides a framework forpassing configuration information to hosts on a TCP/IP network.[STANDARDS-TRACK]1530 Malamud Oct 93 Principles of Operation for the TPC.INT Subdomain: General Principles and PolicyThis document defines the initial principles of operation for thetpc.int subdomain, a collection of service listings accessible over theInternet infrastructure through an administered namespace containedwithin the Domain Name System. This memo provides information for theInternet community. It does not specify an Internet standard.Kennedy Informational [Page 15]
RFC 1599 Summary of 1500-1599 January 19971529 Malamud Oct 93 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative PoliciesThis document defines the administrative policies for the operation ofremote printer facilities within the context of the tpc.int subdomain.The document describes different approaches to resource recovery forremote printer server sites and includes discussions of issuespertaining to auditing, security, and denial of access. This memoprovides information for the Internet community. It does not specify anInternet standard.1528 MalamudOct 93 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical ProceduresThis 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.1527 Cook Sep 93 What Should We Plan Given the Dilemma of the Network?The Internet community needs to be asking what the most important policyissues facing the network are. And given agreement on any particularset of policy issues, the next thing we should be asking is, what wouldbe some of the political choices that would follow for Congress to make?This memo is a shortened version of the suggested policy draft. Thismemo provides information for the Internet community. It does notspecify an Internet standard.1526 Piscitello Sep 93 Assignment of System Identifiers for TUBA/CLNP HostsThis document describes conventions whereby the system identifierportion of anRFC 1237 style NSAP address may be guaranteed uniquenesswithin a routing domain for the purpose of autoconfiguration inTUBA/CLNP internets. This memo provides information for the Internetcommunity. It does not specify an Internet standard.Kennedy Informational [Page 16]
RFC 1599 Summary of 1500-1599 January 19971525 Decker Sep 93 Definitions of Managed Objects for Source Routing 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 source routing and sourcerouting transparent bridges. These bridges are also required toimplement relevant groups in the Bridge MIB. [STANDARDS-TRACK]1524 Borenstein Sep 93 A User Agent Configuration Mechanism For Multimedia Mail Format InformationThis memo suggests a file format to be used to inform multiple mailreading user agent programs about the locally-installed facilities forhandling mail in various formats. This memo provides information for theInternet community. It does not specify an Internet standard.1523 Borenstein Sep 93 The text/enriched MIME Content-typeMIME [RFC-1341,RFC-1521] defines a format and general framework for therepresentation of a wide variety of data types in Internet mail. Thisdocument defines one particular type of MIME data, the text/enrichedtype, a refinement of the "text/richtext" type defined inRFC 1341. Thismemo provides information for the Internet community. It does notspecify an Internet standard.1522 Moore Sep 93 MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII TextThis memo describes an extension to the message format defined in RFC1521, to allow the representation of character sets other than ASCII inRFC 822 (STD 11) message headers. The extensions described weredesigned to be highly compatible with existing Internet mail handlingsoftware, and to be easily implemented in mail readers that support RFC1521.Kennedy Informational [Page 17]
RFC 1599 Summary of 1500-1599 January 19971521 Borenstein Sep 93 MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message BodiesThis document redefines the format of message bodies to allow multi-parttextual and non-textual message bodies to be represented and exchangedwithout loss of information. This is based on earlier work documentedinRFC 934 and STD 11,RFC 1049, but extends and revises that work.[STANDARDS-TRACK]1520 Rekhter Sep 93 Exchanging Routing Information Across Provider Boundaries in the CIDR EnvironmentThe purpose of this document is twofold. First, it describes variousalternatives for exchanging inter-domain routing information acrossdomain boundaries, where one of the peering domain is CIDR-capable andanother is not. Second, it addresses the implications of running CIDR-capable inter-domain routing protocols (e.g., BGP-4, IDRP) on intra-domain routing. This memo provides information for the Internetcommunity. It does not specify an Internet standard.1519 Fuller Sep 93 Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation StrategyThis memo discusses strategies for address assignment of the existing IPaddress space with a view to conserve the address space and stem theexplosive growth of routing tables in default-route-free routers.[STANDARDS-TRACK]1518 Rekhter Sep 93 An Architecture for IP Address Allocation with CIDRThis paper provides an architecture and a plan for allocating IPaddresses in the Internet. This architecture and the plan are intendedto play an important role in steering the Internet towards the AddressAssignment and Aggregating Strategy. [STANDARDS-TRACK]Kennedy Informational [Page 18]
RFC 1599 Summary of 1500-1599 January 19971517 IESG Sep 93 Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR)Classless Inter-Domain Routing (CIDR) defines a mechanism to slow thegrowth of routing tables and reduce the need to allocate new IP networknumbers. [STANDARDS-TRACK]1516 McMaster Sep 93 Definitions of Managed Objects for IEEE 802.3 Repeater DevicesThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it defines objects for managing IEEE 802.3 10 Mb/secondbaseband repeaters, sometimes referred to as "hubs." [STANDARDS-TRACK]1515 McMaster Sep 93 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)This document defines a portion of the Management Information Base (MIB)for use with network management protocols in TCP/IP-based internets. Inparticular, it defines objects for managing IEEE 802.3 Medium AttachmentUnits (MAUs). [STANDARDS-TRACK]1514 Grillo Sep 93 Host Resources MIBThis memo defines a MIB for use with managing host systems. [STANDARDS-TRACK]1513 WaldbusserSep 93 Token Ring Extensions to the Remote Network Monitoring MIBThis memo defines extensions to the Remote Network Monitoring MIB formanaging 802.5 Token Ring networks. [STANDARDS-TRACK]1512 Case Sep 93 FDDI Management Information BaseThis 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 devices which implement theFDDI based on the ANSI FDDI SMT 7.3 draft standard, which has beenforwarded for publication by the X3T9.5 committee.Kennedy Informational [Page 19]
RFC 1599 Summary of 1500-1599 January 19971511 Linn Sep 93 Common Authentication Technology OverviewThis memo provides information for the Internet community. It does notspecify an Internet standard.1510 Kohl Sep 93 The Kerberos Network Authentication Service (V5)This document gives an overview and specification of Version 5 of theprotocol for the Kerberos network authentication system. [STANDARDS-TRACK]1509 Wray Sep 93 Generic Security Service API : C-bindingsThis document specifies C language bindings for the Generic SecurityService Application Program Interface (GSS-API), which is described at alanguage-independent conceptual level in other documents. [STANDARDS-TRACK]1508 Linn Sep 93 Generic Security Service Application Program InterfaceThis Generic Security Service Application Program Interface (GSS-API)definition provides security services to callers in a generic fashion,supportable with a range of underlying mechanisms and technologies andhence allowing source-level portability of applications to differentenvironments. [STANDARDS-TRACK]1507 KaufmanSep 93 DASS Distributed Authentication Security ServiceThe goal of DASS is to provide authentication services in a distributedenvironment which are both more secure and easier to use than existingmechanisms. This memo defines an Experimental Protocol for the Internetcommunity. It does not specify an Internet standard.Kennedy Informational [Page 20]
RFC 1599 Summary of 1500-1599 January 19971506 HouttuinSep 93 A Tutorial on Gatewaying between X.400 and Internet MailThis tutorial was produced especially to help new gateway managers findtheir way into the complicated subject of mail gatewaying according toRFC 1327. This memo provides information for the Internet community. Itdoes not specify an Internet standard.1505 Costanzo Aug 93 Encoding Header Field for Internet MessagesThis document expands upon the elective experimental Encoding headerfield which permits the mailing of multi-part, multi-structuredmessages. It replacesRFC 1154. This memo defines an ExperimentalProtocol for the Internet community. It does not specify an Internetstandard.1504 OppenheimerAug 93 Appletalk Update-Based Routing Protocol: Enhanced Appletalk RoutingThis document provides detailed information about the AppleTalk Update-based Routing Protocol (AURP) and wide area routing. AURP provides widearea routing enhancements to the AppleTalk routing protocols and isfully compatible with AppleTalk Phase 2. This memo provides informationfor the Internet community. It does not specify an Internet standard.1503 McCloghrie Aug 93 Algorithms for Automating Administration in SNMPv2 ManagersWhen a user invokes an SNMPv2 management application, it may bedesirable for the user to specify the minimum amount of informationnecessary to establish and maintain SNMPv2 communications. This memosuggests an approach to achieve this goal. This memo providesinformation for the Internet community. It does not specify an Internetstandard.1502 AlvestrandAug 93 X.400 Use of Extended Character SetsThis RFC defines a suggested method of using "GeneralText" in order toharmonize as much as possible the usage of this body part. [STANDARDS-TRACK]Kennedy Informational [Page 21]
RFC 1599 Summary of 1500-1599 January 19971501 Brunsen Aug 93 OS/2 User GroupMemo soliciting reactions to the proposal of a OS/2 User Group. Thismemo provides information for the Internet community. This memo doesnot specify an IAB standard of any kind.1500 IAB Aug 93 Internet Official Protocol StandardsThis memo describes the state of standardization of protocols used inthe Internet as determined by the Internet Activities Board (IAB).[STANDARDS-TRACK]Security Considerations Security issues are not discussed in this memo.Author's Address Mary Kennedy University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: MKENNEDY@ISI.EDUKennedy Informational [Page 22]
[8]ページ先頭