📄 rfc2799.txt
字号:
confirmed, and recalled is specified. This document is a self-consistent, organized compilation of the process as it was known at thetime of publication. This document specifies an Internet Best CurrentPractices for the Internet Community, and requests discussion andsuggestions for improvements.2726 Zsako Dec 1999 PGP Authentication for RIPE Database UpdatesThis document presents the proposal for a stronger authentication methodof the updates of the RIPE database based on digital signatures.[STANDARDS TRACK]2725 Villamizar Dec 1999 Routing Policy System SecurityThe implementation and deployment of a routing policy system mustmaintain some degree of integrity to be of any operational use. Thisdocument addresses the need to assure integrity of the data by providingan authentication and authorization model. [STANDARDS TRACK]2724 Handelman Oct 1999 RTFM: New Attributes for Traffic Flow MeasurementThis document discusses RTFM flows and the attributes which they canhave, so as to provide a logical framework for extending thearchitecture by adding new attributes. This memo defines anExperimental Protocol for the Internet community.Ginoza Informational [Page 16]RFC 2799 Summary of 2700-2799 September 20002723 Brownlee Oct 1999 SRL: A Language for Describing Traffic Flows and Specifying Actions for Flow GroupsThis document describes a language for specifying rulesets, i.e.configuration files which may be loaded into a traffic flow meter so asto specify which traffic flows are measured by the meter, and theinformation it will store for each flow. This memo provides informationfor the Internet community.2722 Brownlee Oct 1999 Traffic Flow Measurement: ArchitectureThis document provides a general framework for describing networktraffic flows, presents an architecture for traffic flow measurement andreporting, discusses how this relates to an overall network traffic flowarchitecture and indicates how it can be used within the Internet. Thismemo provides information for the Internet community.2721 Brownlee Oct 1999 RTFM: Applicability StatementThis document provides an overview covering all aspects of RealtimeTraffic Flow Measurement, including its area of applicability and itslimitations. This memo provides information for the Internet community.2720 Brownlee Oct 1999 Traffic Flow Measurement: Meter MIBThis document defines a Management Information Base (MIB) for use incontrolling an RTFM Traffic Meter, in particular for specifying theflows to be measured. It also provides an efficient mechanism forretrieving flow data from the meter using SNMP. Security issuesconcerning the operation of traffic meters are summarised. [STANDARDSTRACK]2719 Ong Oct 1999 Framework Architecture for Signaling TransportThis document defines an architecture framework and functionalrequirements for transport of signaling information over IP. This memoprovides information for the Internet community.Ginoza Informational [Page 17]RFC 2799 Summary of 2700-2799 September 20002718 Masinter Nov 1999 Guidelines for new URL SchemesThis document provides guidelines for the definition of new URL schemes.This memo provides information for the Internet community.2717 Petke Nov 1999 Registration Procedures for URL Scheme NamesThis document defines the process by which new URL scheme names areregistered. This document specifies an Internet Best Current Practicesfor the Internet Community, and requests discussion and suggestions forimprovements.2716 Aboba Oct 1999 PPP EAP TLS Authentication ProtocolThe Point-to-Point Protocol (PPP) provides a standard method fortransporting multi-protocol datagrams over point-to-point links.TheExtensible Authentication Protocol (EAP) is a PPP extension thatprovides support for additional authentication methods within PPP. Thismemo defines an Experimental Protocol for the Internet community.2715 Thaler Oct 1999 Interoperability Rules for Multicast Routing ProtocolsThe rules described in this document will allow efficient interoperationamong multiple independent multicast routing domains. This memoprovides information for the Internet community.2714 Ryan Oct 1999 Schema for Representing CORBA Object References in an LDAP DirectoryThis document defines the schema for representing CORBA objectreferences in an LDAP directory. This memo provides information for theInternet community.Ginoza Informational [Page 18]RFC 2799 Summary of 2700-2799 September 20002713 Ryan Oct 1999 Schema for Representing Java(tm) Objects in an LDAP DirectoryThis document defines the schema for representing Java(tm) objects in anLDAP directory. This memo provides information for the Internetcommunity.2712 Medvinsky Oct 1999 Addition of Kerberos Cipher Suites to Transport Layer Security (TLS)This document proposes the addition of new cipher suites to the TLSprotocol to support Kerberos-based authentication. [STANDARDS TRACK]2711 Partridge Oct 1999 IPv6 Router Alert OptionThis memo describes a new IPv6 Hop-by-Hop Option type that alertstransit routers to more closely examine the contents of an IP datagram.[STANDARDS TRACK]2710 Deering Oct 1999 Multicast Listener Discovery (MLD) for IPv6This document specifies the protocol used by an IPv6 router to discoverthe presence of multicast listeners (that is, nodes wishing to receivemulticast packets) on its directly attached links, and to discoverspecifically which multicast addresses are of interest to thoseneighboring nodes. [STANDARDS TRACK]2709 Srisuresh Oct 1999 Security Model with Tunnel-mode IPsec for NAT DomainsThis document describes a security model by which tunnel-mode IPsecsecurity can be architected on NAT devices. This memo providesinformation for the Internet community.Ginoza Informational [Page 19]RFC 2799 Summary of 2700-2799 September 20002708 Bergman Nov 1999 Job Submission Protocol Mapping Recommendations for the Job Monitoring MIBThis document defines the recommended mapping for many currently popularJob submission protocols to objects and attributes in the Job MonitoringMIB. This memo provides information for the Internet community.2707 Bergman Nov 1999 Job Monitoring MIB - V1.0This document provides a printer industry standard SNMP MIB for (1)monitoring the status and progress of print jobs (2) obtaining resourcerequirements before a job is processed, (3) monitoring resourceconsumption while a job is being processed and (4) collecting resourceaccounting data after the completion of a job. This memo providesinformation for the Internet community.2706 Eastlake Oct 1999 ECML v1: Field Names for E-CommerceA standard set of information fields is defined as the first version ofan Electronic Commerce Modeling Language (ECML) so that this task can bemore easily automated, for example by wallet software that could fill infields. This memo provides information for the Internet community.2705 Arango Oct 1999 Media Gateway Control Protocol (MGCP) Version 1.0This document describes an application programming interface and acorresponding protocol (MGCP) for controlling Voice over IP (VoIP)Gateways from external call control elements. MGCP assumes a callcontrol architecture where the call control "intelligence" is outsidethe gateways and handled by external call control elements. This memoprovides information for the Internet community.2704 Blaze Sep 1999 The KeyNote Trust-Management System Version 2This memo describes version 2 of the KeyNote trust-management system.Itspecifies the syntax and semantics of KeyNote `assertions', describes`action attribute' processing, and outlines the application architectureinto which a KeyNote implementation can be fit. This memo providesinformation for the Internet community.Ginoza Informational [Page 20]RFC 2799 Summary of 2700-2799 September 20002703 Klyne Sep 1999 Protocol-independent Content Negotiation FrameworkThis memo sets out terminology, an abstract framework and goals forprotocol-independent content negotiation, and identifies some technicalissues which may need to be addressed. This memo provides informationfor the Internet community.2702 Awduche Sep 1999 Requirements for Traffic Engineering Over MPLSThis document presents a set of requirements for Traffic Engineeringover Multiprotocol Label Switching (MPLS). It identifies the functionalcapabilities required to implement policies that facilitate efficientand reliable network operations in an MPLS domain. This memo providesinformation for the Internet community.2701 Malkin Sep 1999 Nortel Networks Multi-link Multi-node PPP Bundle Discovery ProtocolThis document specifies a standard way for Multi-link PPP to operateacross multiple nodes. This memo provides information for the Internetcommunity.2700 Reynolds Aug 2000 Internet Official Protocol StandardsThis memo describes the current state of standardization of protocolsused in the Internet as determined by the Internet Engineering TaskForce (IETF). [STANDARDS TRACK]Security Considerations Security issues are not discussed in this memo.Ginoza Informational [Page 21]RFC 2799 Summary of 2700-2799 September 2000Author's Address Sandy Ginoza University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: (310) 822-1511 EMail: ginoza@isi.eduGinoza Informational [Page 22]RFC 2799 Summary of 2700-2799 September 2000Full Copyright Statement Copyright (C) The Internet Society (YEAR). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.Ginoza Informational [Page 23]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -