📄 rfc1599.txt
字号:
This 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 Malamud Oct 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 an RFC 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 in RFC 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 documentedin RFC 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 Waldbusser Sep 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 Kaufman Sep 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 Houttuin Sep 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 replaces RFC 1154. This memo defines an ExperimentalProtocol for the Internet community. It does not specify an Internetstandard.1504 Oppenheimer Aug 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 Alvestrand Aug 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]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -