Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
INFORMATIONAL
Network Working Group S. GinozaRequest for Comments: 2799 ISICategory: Informational September 2000Request for Comments Summary RFC Numbers 2700-2799Status of This Memo This RFC is a slightly annotated list of the 100 RFCs fromRFC 2700 through RFCs 2799. 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.Copyright Notice Copyright (C) The Internet Society (YEAR). All Rights Reserved.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--- ------ ---- -----2799 Ginoza Request for Comments SummaryThis memo.2798 Smith Apr 2000 Definition of the inetOrgPerson LDAP Object ClassWe define a new object class called inetOrgPerson for use in LDAP andX.500 directory services that extends the X.521 standardorganizationalPerson class to meet these needs. This memo providesinformation for the Internet community.Ginoza Informational [Page 1]
RFC 2799 Summary of 2700-2799 September 20002797 Myers Apr 2000 Certificate Management Messages over CMSThis document defines a Certificate Management protocol using CMS (CMC).[STANDARDS TRACK]2796 Bates Apr 2000 BGP Route Reflection - An Alternative to Full Mesh IBGPThis document describes the use and design of a method known as "RouteReflection" to alleviate the the need for "full mesh" IBGP. [STANDARDSTRACK]2795 Christey Mar 2000 The Infinite Monkey Protocol Suite (IMPS)This memo describes a protocol suite which supports an infinite numberof monkeys that sit at an infinite number of typewriters in order todetermine when they have either produced the entire works of WilliamShakespeare or a good television show. This memo provides informationfor the Internet community.2794 Calhoun Mar 2000 Mobile IP Network Access Identifier Extension for IPv4Our proposal defines a way for the mobile node to identify itself, byincluding the NAI along with the Mobile IP Registration Request. Thismemo also updatesRFC 2290 which specifies the Mobile-IPv4 Configurationoption for IPCP, by allowing the Mobile Node's Home Address field ofthis option to be zero. [STANDARDS TRACK]2793 Hellstrom May 2000 RTP Payload for Text ConversationThis memo describes how to carry text conversation session contents inRTP packets. Text conversation session contents are specified in ITU-TRecommendation T.140. [STANDARDS TRACK]Ginoza Informational [Page 2]
RFC 2799 Summary of 2700-2799 September 20002792 Blaze Mar 2000 DSA and RSA Key and Signature Encoding for the KeyNote Trust Management SystemThis memo describes RSA and DSA key and signature encoding, and binarykey encoding for version 2 of the KeyNote trust-management system. Thismemo provides information for the Internet community.2791 Yu Jul 2000 Scalable Routing Design PrinciplesThis document identifies major factors affecting routing scalability aswell as basic principles of designing scalable routing for largenetworks. This memo provides information for the Internet community.2790 Waldbusser Mar 2000 Host Resources MIBThis memo obsoletesRFC 1514, the "Host Resources MIB". This memoextends that specification by clarifying changes based on implementationand deployment experience and documenting the Host Resources MIB inSMIv2 format while remaining semantically identical to the existingSMIv1-based MIB. [STANDARDS TRACK]2789 Freed Mar 2000 Mail Monitoring MIBThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community.Specifically, this memo extends the basic Network Services MonitoringMIB defined inRFC 2788 [16] to allow monitoring of Message TransferAgents (MTAs). It may also be used to monitor MTA components withingateways. [STANDARDS TRACK]2788 Freed Mar 2000 Network Services Monitoring MIBThis document defines a MIB which contains the elements common to themonitoring of any network service application. [STANDARDS TRACK]Ginoza Informational [Page 3]
RFC 2799 Summary of 2700-2799 September 20002787 Jewell Mar 2000 Definitions of Managed Objects for the Virtual Router Redundancy ProtocolThis specification defines an extension to the Management InformationBase (MIB) for use with SNMP-based network management. In particular,it defines objects for configuring, monitoring, and controlling routersthat employ the Virtual Router Redundancy Protocol (VRRP). [STANDARDSTRACK]2786 St. Johns Mar 2000 Diffie-Helman USM Key Management Information Base and Textual ConventionThis memo defines an experimental portion of the Management InformationBase (MIB) for use with network management protocols the Internetcommunity. In particular, it defines a textual convention for doingDiffie-Helman key agreement key exchanges an set of objects which extendthe usmUserTable to permit the use of DH key exchange in addition to thekey change method. This memo defines an Experimental Protocol for theInternet community.2785 Zuccherato Mar 2000 Methods for Avoiding the "Small-Subgroup" Attacks on the Diffie-Hellman Key Agreement Method for S/MIMEThis document will describe the situations relevant to implementationsof S/MIME version 3 in which protection is necessary and the methodsthat can be used to prevent these attacks. This memo providesinformation for the Internet community.2784 Farinacci Mar 2000 Generic Routing Encapsulation (GRE)This document specifies a protocol for encapsulation of an arbitrarynetwork layer protocol over another arbitrary network layer protocol.[STANDARDS TRACK]Ginoza Informational [Page 4]
RFC 2799 Summary of 2700-2799 September 20002783 Mogul Mar 2000 Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0RFC 1589 did not define an API for managing the PPS facility, leavingimplementors without a portable means for using PPS sources. Thisdocument specifies such an API. This memo provides information for theInternet community.2782 Gulbrandsen Feb 2000 A DNS RR for specifying the location of services (DNS SRV)This document describes a DNS RR which specifies the location of theserver(s) for a specific protocol and domain. [STANDARDS TRACK]2781 Hoffman Feb 2000 UTF-16, an encoding of ISO 10646This document describes the UTF-16 encoding of Unicode/ISO-10646,addresses the issues of serializing UTF-16 as an octet stream fortransmission over the Internet, discusses MIME charset naming asdescribed in [CHARSET-REG], and contains the registration for three MIMEcharset parameter values: UTF-16BE (big-endian), UTF-16LE (little-endian), and UTF-16. This memo provides information for the Internetcommunity.2780 Bradner Mar 2000 IANA Allocation Guidelines For Values In the Internet Protocol and Related HeadersThis memo provides guidance for the IANA to use in assigning parametersfor fields in the IPv4, IPv6, ICMP, UDP and TCP protocol headers. Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.2779 Day Feb 2000 Instant Messaging / Presence Protocol RequirementsThis document defines a minimal set of requirements that IMPP must meet.This memo provides information for the Internet community.Ginoza Informational [Page 5]
RFC 2799 Summary of 2700-2799 September 20002778 Day Feb 2000 A Model for Presence and Instant MessagingThis document defines an abstract model for a presence and instantmessaging system. It defines the various entities involved, definesterminology, and outlines the services provided by the system. Thismemo provides information for the Internet community.2777 Eastlake Feb 2000 Publicly Verifiable Nomcom Random SelectionThis document describes a method for making random selections in such away that the unbiased nature of the choice is publicly verifiable. Thismemo provides information for the Internet community.2776 Handley Feb 2000 Multicast-Scope Zone Announcement Protocol (MZAP)This document defines a protocol, the Multicast-Scope Zone AnnouncementProtocol (MZAP), for discovering the multicast administrative scopezones that are relevant at a particular location. [STANDARDS TRACK]2775 Carpenter Feb 2000 Internet TransparencyThis document describes the current state of the Internet from thearchitectural viewpoint, concentrating on issues of end-to-endconnectivity and transparency.2774 Nielsen Feb 2000 An HTTP Extension FrameworkThis document describes a generic extension mechanism for HTTP, which isdesigned to address the tension between private agreement and publicspecification and to accommodate extension of applications using HTTPclients, servers, and proxies. This memo defines an ExperimentalProtocol for the Internet community.Ginoza Informational [Page 6]
RFC 2799 Summary of 2700-2799 September 20002773 Housley Feb 2000 Encryption using KEA and SKIPJACKThis document defines a method to encrypt a file transfer using the FTPspecification STD 9,RFC 959, "File Transfer Protocol (FTP)", (October1985) andRFC 2228, "FTP Security Extensions" (October 1997). This memodefines an Experimental Protocol for the Internet community.2772 Rockell Feb 2000 6Bone Backbone Routing GuidelinesThis document provides a set of guidelines for all 6bone routingequipment operators to use as a reference for efficient and stabledeployment of 6bone routing systems. This memo provides information forthe Internet community.2771 Finlayson Feb 2000 An Abstract API for Multicast Address AllocationThis document describes the "abstract service interface" for the dynamicmulticast address allocation service, as seen by applications. Thismemo provides information for the Internet community.2770 Meyer Feb 2000 GLOP Addressing in 233/8This describes an experimental policy for use of the class D addressspace using 233/8 as the experimental statically assigned subset of theclass D address space. This memo defines an Experimental Protocol forthe Internet community.2769 Villamizar Feb 2000 Routing Policy System ReplicationThis document addresses the need to distribute data over multiplerepositories and delegate authority for data subsets to otherrepositories without compromising the authorization model established inRouting Policy System Security RFC. [STANDARDS TRACK]Ginoza Informational [Page 7]
RFC 2799 Summary of 2700-2799 September 20002768 Aiken Feb 2000 Network Policy and Services: A Report of a Workshop on MiddlewareAn ad hoc middleware workshop was held at the International Center forAdvanced Internet Research in December 1998. The need for a moreorganized framework for middleware R&D was recognized, and a list ofspecific topics needing further work was identified. This memo providesinformation for the Internet community.2767 Tsuchiya Feb 2000 Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)This memo proposes a mechanism of dual stack hosts using the techniquecalled "Bump-in-the-Stack" in the IP security area. This memo providesinformation for the Internet community.2766 Tsirtsis Feb 2000 Network Address Translation - Protocol Translation (NAT-PT)This document specifies an IPv4-to-IPv6 transition mechanism, inaddition to those already specified. [STANDARDS TRACK]2765 Nordmark Feb 2000 Stateless IP/ICMP Translation Algorithm (SIIT)This document specifies a transition mechanism algorithm in addition tothe mechanisms already specified. [STANDARDS TRACK]2764 Gleeson Feb 2000 A Framework for IP Based Virtual Private NetworksThis document describes a framework for Virtual Private Networks (VPNs)running across IP backbones. This memo provides information for theInternet community.Ginoza Informational [Page 8]
RFC 2799 Summary of 2700-2799 September 20002763 Shen Feb 2000 Dynamic Hostname Exchange Mechanism for IS-ISThis document defines a new TLV which allows the IS-IS routers to floodtheir name to system ID mapping information across the IS-IS network.This memo provides information for the Internet community.2762 Rosenberg Feb 2000 Sampling of the Group Membership in RTPThis document discusses mechanisms for sampling of this group membershiptable in order to reduce the memory requirements. This memo defines anExperimental Protocol for the Internet community.2761 Dunn Feb 2000 Terminology for ATM BenchmarkingThis memo discusses and defines terms associated with performancebenchmarking tests and the results of these tests in the context ofAsynchronous Transfer Mode (ATM) based switching devices. This memoprovides information for the Internet community.2760 Allman Feb 2000 Ongoing TCP Research Related to SatellitesThis document outlines possible TCP enhancements that may allow TCP tobetter utilize the available bandwidth provided by networks containingsatellite links. This memo provides information for the Internetcommunity.2759 Zorn Jan 2000 Microsoft PPP CHAP Extensions, Version 2This document describes version two of Microsoft's PPP CHAP dialect(MS-CHAP-V2). MS-CHAP-V2 is similar to, but incompatible with, MS-CHAPversion one (MS-CHAP-V1). This memo provides information for theInternet community.Ginoza Informational [Page 9]
RFC 2799 Summary of 2700-2799 September 20002758 White Feb 2000 Definitions of Managed Objects for Service Level Agreements Performance MonitoringThis memo defines a Management Information Base (MIB) for performancemonitoring of Service Level Agreements (SLAs) defined via policydefinitions. This memo defines an Experimental Protocol for theInternet community.2757 Montenegro Jan 2000 Long Thin NetworksOur goal is to identify a TCP that works for all users, including usersof long thin networks. This memo provides information for the Internetcommunity.2756 Vixie Jan 2000 Hyper Text Caching Protocol (HTCP/0.0)This document describes HTCP, a protocol for discovering HTTP caches andcached data, managing sets of HTTP caches, and monitoring cacheactivity. This is an experimental protocol, one among several proposalsto perform these functions. This memo defines an Experimental Protocolfor the Internet community.2755 Chiu Jan 2000 Security Negotiation for WebNFSThis document describes a protocol for a WebNFS client (RFC2054) tonegotiate the desired security mechanism with a WebNFS server (RFC2055)before the WebNFS client falls back to the MOUNT v3 protocol (RFC1813).This document is provided so that people can write compatibleimplementations. This memo provides information for the Internetcommunity.Ginoza Informational [Page 10]
RFC 2799 Summary of 2700-2799 September 20002754 Alaettinoglu Jan 2000 RPS IANA IssuesRPS Security requires certain RPSL objects in the IRR to behierarchically delegated. The set of objects that are at the root ofthis hierarchy needs to be created and digitally signed by IANA. Thispaper presents these seed objects and lists operations required fromIANA. This memo provides information for the Internet community.2753 Yavatkar Jan 2000 A Framework for Policy-based Admission ControlThis document is concerned with specifying a framework for providingpolicy-based control over admission control decisions. This memoprovides information for the Internet community.2752 Yadav Jan 2000 Identity Representation for RSVPThis document describes the representation of identity information inPOLICY_DATA object for supporting policy based admission control inRSVP. [STANDARDS TRACK]2751 Herzog Jan 2000 Signaled Preemption Priority Policy ElementThis document describes a preemption priority policy element for use bysignaled policy based admission protocols (such as RSVP and COPS).[STANDARDS TRACK]2750 Herzog Jan 2000 RSVP Extensions for Policy ControlThis memo presents a set of extensions for supporting generic policybased admission control in RSVP. [STANDARDS TRACK]Ginoza Informational [Page 11]
RFC 2799 Summary of 2700-2799 September 20002749 Herzog Jan 2000 COPS usage for RSVPThis document describes usage directives for supporting COPS policyservices in RSVP environments. [STANDARDS TRACK]2748 Durham Jan 2000 The COPS (Common Open Policy Service) ProtocolThis document describes a simple client/server model for supportingpolicy control over QoS signaling protocols. [STANDARDS TRACK]2747 Baker Jan 2000 RSVP Cryptographic AuthenticationThis document describes the format and use of RSVP's INTEGRITY object toprovide hop-by-hop integrity and authentication of RSVP messages.[STANDARDS TRACK]2746 Terzis Jan 2000 RSVP Operation Over IP TunnelsThis document describes an approach for providing RSVP protocol servicesover IP tunnels. [STANDARDS TRACK]2745 Terzis Jan 2000 RSVP Diagnostic MessagesThis document specifies the RSVP diagnostic facility, which allows auser to collect information about the RSVP state along a path.[STANDARDS TRACK]2744 Wray Jan 2000 Generic Security Service API Version 2 : C-bindingsThis document specifies C language bindings for Version 2, Update 1 ofthe Generic Security Service Application Program Interface (GSS-API),which is described at a language-independent conceptual level in RFC2743. [STANDARDS TRACK]Ginoza Informational [Page 12]
RFC 2799 Summary of 2700-2799 September 20002743 Linn Jan 2000 Generic Security Service Application Program Interface Version 2, Update 1This memo obsoletes [RFC-2078], making specific, incremental changes inresponse to implementation experience and liaison requests. It isintended, therefore, that this memo or a successor version thereto willbecome the basis for subsequent progression of the GSS-API specificationon the standards track. [STANDARDS TRACK]2742 Heintz Jan 2000 Definitions of Managed Objects for Extensible SNMP AgentsThis memo defines a portion of the Management Information Base (MIB) foruse with network management protocols in the Internet community. Inparticular, it describes objects managing SNMP agents that use the AgentExtensibility (AgentX) Protocol. [STANDARDS TRACK]2741 Daniele Jan 2000 Agent Extensibility (AgentX) Protocol Version 1This memo defines a standardized framework for extensible SNMP agents.[STANDARDS TRACK]2740 Coltun Dec 1999 OSPF for IPv6This document describes the modifications to OSPF to support version 6of the Internet Protocol (IPv6). [STANDARDS TRACK]2739 Small Jan 2000 Calendar Attributes for vCard and LDAPThis memo defines three mechanisms for obtaining a URI to a user'scalendar and free/busy time. [STANDARDS TRACK]Ginoza Informational [Page 13]
RFC 2799 Summary of 2700-2799 September 20002738 Klyne Dec 1999 Corrections to "A Syntax for Describing Media Feature Sets"InRFC 2533, "A Syntax for Describing Media Feature Sets", an expressionformat is presented for describing media feature capabilities usingsimple media feature tags. This memo contains two corrections to thatspecification: one fixes an error in the formal syntax specification,and the other fixes an error in the rules for reducing featurecomparison predicates. [STANDARDS TRACK]2737 McCloghrie Dec 1999 Entity MIB (Version 2)This memo defines a portion of the Management Information Base (M foruse with network management protocols in the Internet communi Inparticular, it describes managed objects used for managing multiplelogical and physical entities managed by a single SNMP agent.[STANDARDS TRACK]2736 Handley Dec 1999 Guidelines for Writers of RTP Payload Format SpecificationsThis document provides general guidelines aimed at assisting the authorsof RTP Payload Format specifications in deciding on good formats. Thisdocument specifies an Internet Best Current Practices for the InternetCommunity, and requests discussion and suggestions for improvements.2735 Fox Dec 1999 NHRP Support for Virtual Private NetworksThe NBMA Next Hop Resolution Protocol (NHRP) is used to determine theNBMA subnetwork addresses of the "NBMA next hop" towards a publicinternetworking layer address. This document describes the enhancementsnecessary to enable NHRP to perform the same function for privateinternetworking layer addresses available within the framework of aVirtual Private Network (VPN) service on a shared NBMA network.[STANDARDS TRACK]2734 Johansson Dec 1999 IPv4 over IEEE 1394This document specifies how to use IEEE Std 1394-1995, Standard for aHigh Performance Serial Bus (and its supplements), for the transport ofInternet Protocol Version 4 (IPv4) datagrams; it defines the necessarymethods, data structures and codes for that purpose. [STANDARDS TRACK]Ginoza Informational [Page 14]
RFC 2799 Summary of 2700-2799 September 20002733 Rosenberg Dec 1999 An RTP Payload Format for Generic Forward Error CorrectionThis document specifies a payload format for generic forward errorcorrection of media encapsulated in RTP. [STANDARDS TRACK]2732 Hinden Dec 1999 Format for Literal IPv6 Addresses in URL'sThis document defines the format for literal IPv6 Addresses in URL's forimplementation in World Wide Web browsers. [STANDARDS TRACK]2731 Kunze Dec 1999 Encoding Dublin Core Metadata in HTMLThe Dublin Core is a small set of metadata elements for describinginformation resources. This document explains how these elements areexpressed using the META and LINK tags of HTML. This memo providesinformation for the Internet community.2730 Hanna Dec 1999 Multicast Address Dynamic Client Allocation Protocol (MADCAP)This document defines a protocol, Multicast Address Dynamic ClientAllocation Protocol (MADCAP), that allows hosts to request multicastaddresses from multicast address allocation servers. [STANDARDS TRACK]2729 Bagnall Dec 1999 Taxonomy of Communication Requirements for Large-scale Multicast ApplicationsThe intention of this memo is to define a classification system for thecommunication requirements of any large-scale multicast application(LSMA). This memo provides information for the Internet community.Ginoza Informational [Page 15]
RFC 2799 Summary of 2700-2799 September 20002728 Panabaker Nov 1999 The Transmission of IP Over the Vertical Blanking Interval of a Television SignalThis document describes a method for broadcasting IP data in aunidirectional manner using the vertical blanking interval of televisionsignals. [STANDARDS TRACK]2727 Galvin Feb 2000 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesThe process by which the members of the IAB and IESG are selected,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]
[8]ページ先頭