rfc2499.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 1,236 行 · 第 1/3 页

Network Working Group                                           A. Ramos
Request for Comments: 2499                                           ISI
Category: Informational                                        July 1999


                      Request for Comments Summary

                         RFC Numbers 2400-2499

Status of This Memo

   This RFC is a slightly annotated list of the 100 RFCs from RFC 2400
   through RFCs 2499.  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 (1999).  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
---     ------          ----            -----


2499    Ramos           July 1999       Request for Comments Summary

This memo.


2498    Mahdavi         Jan 1999        IPPM Metrics for Measuring
                                        Connectivity

This memo defines a series of metrics for connectivity between a pair of
Internet hosts.  It builds on notions introduced and discussed in RFC
2330, the IPPM framework document.  This memo defines an Experimental
Protocol for the Internet community.




Ramos                        Informational                      [Page 1]

RFC 2499                  Summary of 2400-2499                 July 1999


2497    Souvatzis       Jan 1999        Transmission of IPv6 Packets
                                        over ARCnet Networks

This memo specifies a frame format for transmission of IPv6 packets and
the method of forming IPv6 link-local and statelessly autoconfigured
addresses on ARCnet networks. It also specifies the content of the
Source/Target Link-layer Address option used by the Router Solicitation,
Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and
Redirect messages described in, when those messages are transmitted on
an ARCnet.  [STANDARDS-TRACK]


2496    Fowler          Jan 1999        Definitions of Managed Objects
                                        for the DS3/E3 Interface Type

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes objects used for managing DS3 and E3
interfaces.  This document is a companion document with Definitions of
Managed Objects for the DS0 (RFC 2494), DS1/E1/DS2/E2 (RFC 2495), and
the work in progress SONET/SDH Interface Types.  [STANDARDS-TRACK]


2495    Fowler          Jan 1999        Definitions of Managed Objects
                                        for the DS1, E1, DS2 and E2
                                        Interface Types

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes objects used for managing DS1, E1, DS2 and E2
interfaces.  This document is a companion document with Definitions of
Managed Objects for the DS0 (RFC 2494), DS3/E3 (RFC 2496), and the work
in progress, SONET/SDH Interface Types.  [STANDARDS-TRACK]


2494    Fowler          Jan 1999        Definitions of Managed Objects
                                        for the DS0 and DS0 Bundle
                                        Interface Type

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes objects used for managing DS0 and DS0 Bundle
interfaces.  This document is a companion document with Definitions of
Managed Objects for the DS1/E1/DS2/E2 (RFC 2495), DS3/E3 (RFC 2496), and
the work in progress, SONET/SDH Interface Types.  [STANDARDS-TRACK]






Ramos                        Informational                      [Page 2]

RFC 2499                  Summary of 2400-2499                 July 1999


2493    Tesink          Jan 1999        Textual Conventions for MIB
                                        Modules Using Performance
                                        History Based on 15 Minute
                                        Intervals

This document defines a set of Textual Conventions for MIB modules which
make use of performance history data based on 15 minute intervals.
[STANDARDS-TRACK]


2492    Armitage        Jan 1999        IPv6 over ATM Networks

This document is a companion to the ION working group's architecture
document, "IPv6 over Non Broadcast Multiple Access (NBMA) networks".  It
provides specific details on how to apply the IPv6 over NBMA
architecture to ATM networks. This architecture allows conventional
host-side operation of the IPv6 Neighbor Discovery protocol, while also
supporting the establishment of 'shortcut' ATM forwarding paths (when
using SVCs).  Operation over administratively configured Point to Point
PVCs is also supported.  [STANDARDS-TRACK]


2491    Armitage        Jan 1999        IPv6 over Non-Broadcast
                                        Multiple Access (NBMA) networks

This document describes a general architecture for IPv6 over NBMA
networks.  [STANDARDS-TRACK]


2490    Pullen          Jan 1999        A Simulation Model for IP
                                        Multicast with RSVP


This document describes a detailed model of IPv4 multicast with RSVP
that has been developed using the OPNET simulation package, with
protocol procedures defined in the C language.  This memo provides
information for the Internet community.


2489    Droms           Jan 1999        Procedure for Defining New
                                        DHCP Options


This document describes the procedure for defining new DHCP options.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.




Ramos                        Informational                      [Page 3]

RFC 2499                  Summary of 2400-2499                 July 1999


2488    Allman          Jan 1999        Enhancing TCP Over Satellite
                                        Channels using Standard
                                        Mechanisms

The Transmission Control Protocol (TCP) provides reliable delivery of
data across any network path, including network paths containing
satellite channels.  While TCP works over satellite channels there are
several IETF standardized mechanisms that enable TCP to more effectively
utilize the available capacity of the network path.  This document
outlines some of these TCP mitigations.  This document specifies an
Internet Best Current Practices for the Internet Community, and requests
discussion and suggestions for improvements.


2487    Hoffman         Jan 1999        SMTP Service Extension for
                                        Secure SMTP over TLS

This document describes an extension to the SMTP service that allows an
SMTP server and client to use transport-layer security to provide
private, authenticated communication over the Internet. This gives SMTP
agents the ability to protect some or all of their communications from
eavesdroppers and attackers.  [STANDARDS-TRACK]


2486    Aboba           Jan 1999        The Network Access Identifier

This document proposes syntax for the Network Access Identifier (NAI),
the userID submitted by the client during PPP authentication.
[STANDARDS-TRACK]


2485    Drach           Jan 1999        DHCP Option for The Open
                                        Group's User Authentication
                                        Protocol

This document defines a DHCP option that contains a list of pointers to
User Authentication Protocol servers that provide user authentication
services for clients that conform to The Open Group Network Computing
Client Technical Standard.  [STANDARDS-TRACK]












Ramos                        Informational                      [Page 4]

RFC 2499                  Summary of 2400-2499                 July 1999


2484    Zorn            Jan 1999        PPP LCP Internationalization
                                        Configuration Option

The Point-to-Point Protocol (PPP) provides a standard method for
transporting multi-protocol datagrams over point-to-point links.  PPP
also defines an extensible Link Control Protocol (LCP), which allows
negotiation of an Authentication Protocol for authenticating its peer
before allowing Network Layer protocols to transmit over the link.
[STANDARDS-TRACK]


2483    Mealling        Jan 1999        URI Resolution Services
                                        Necessary for URN Resolution

Retrieving the resource identified by a Uniform Resource Identifier
(URI) is only one of the operations that can be performed on a URI.  One
might also ask for and get a list of other identifiers that are aliases
for the original URI or a bibliographic description of the resource the
URI denotes, for example. This applies to both Uniform Resource Names
(URNs) and Uniform Resource Locators (URLs). Uniform Resource
Characteristics (URCs) are discussed in this document but only as
descriptions of resources rather than identifiers.  This memo defines an
Experimental Protocol for the Internet community.


2482    Whistler        Jan 1999        Language Tagging in Unicode
                                        Plain Text

This document proposed a mechanism for language tagging in plain text.
This memo provides information for the Internet community.


2481    Ramakrishnan    Jan 1999        A Proposal to add Explicit
                                        Congestion Notification (ECN)
                                        to IP

This note describes a proposed addition of ECN (Explicit Congestion
Notification) to IP.  This memo defines an Experimental Protocol for the
Internet community.


2480    Freed           Jan 1999        Gateways and MIME Security
                                        Multiparts

This document examines the problems associated with use of MIME security
multiparts and gateways to non-MIME environments.  [STANDARDS-TRACK]





Ramos                        Informational                      [Page 5]

RFC 2499                  Summary of 2400-2499                 July 1999


2479    Adams           Dec 1998        Independent Data Unit
                                        Protection Generic Security Service
                                        Application Program Interface
                                        (IDUP-GSS-API)

The IDUP-GSS-API extends the GSS-API for applications requiring
protection of a generic data unit (such as a file or message) in a way
which is independent of the protection of any other data unit and
independent of any concurrent contact with designated "receivers" of the
data unit.  This memo provides information for the Internet community.


2478    Baize           Dec 1998        The Simple and Protected
                                        GSS-API Negotiation Mechanism

This document specifies a Security Negotiation Mechanism for the Generic
Security Service Application Program Interface (GSS-API).  [STANDARDS-
TRACK]


2477    Aboba           Jan 1999        Criteria for Evaluating
                                        Roaming Protocols

This document describes requirements for the provisioning of "roaming
capability" for dialup Internet users.  "Roaming capability" is defined
as the ability to use multiple Internet service providers (ISPs), while
maintaining a formal, customer-vendor relationship with only one.  This
memo provides information for the Internet community.


2476    Gellens         Dec 1998        Message Submission

This memo describes a low cost, deterministic means for messages to be
identified as submissions, and specifies what actions are to be taken by
a submission server.  [STANDARDS-TRACK]


2475    Blake           Dec 1998        An Architecture for
                                        Differentiated Services

This document defines an architecture for implementing scalable service
differentiation in the Internet.  This memo provides information for the
Internet community.








Ramos                        Informational                      [Page 6]

RFC 2499                  Summary of 2400-2499                 July 1999


2474    Nichols         Dec 1998        Definition of the
                                        Differentiated Services Field
                                        (DS Field) in the IPv4 and
                                        IPv6 Headers

This document defines the IP header field, called the DS (for
differentiated services) field.  [STANDARDS-TRACK]


2473    Conta           Dec 1998        Generic Packet Tunneling in
                                        IPv6 Specification

This document defines the model and generic mechanisms for IPv6
encapsulation of Internet packets, such as IPv6 and IPv4.  [STANDARDS-
TRACK]


2472    Haskin          Dec 1998        IP Version 6 over PPP

This document defines the method for transmission of IP Version 6
packets over PPP links as well as the Network Control Protocol (NCP) for
establishing and configuring the IPv6 over PPP. It also specifies the
method of forming IPv6 link-local addresses on PPP links.  [STANDARDS-
TRACK]


2471    Hinden          Dec 1998        IPv6 Testing Address Allocation

This document describes an allocation plan for IPv6 addresses to be used
in testing IPv6 prototype software.  This memo defines an Experimental
Protocol for the Internet community.


2470    Crawford        Dec 1998        Transmission of IPv6 Packets
                                        over Token Ring Networks

This memo specifies the MTU and frame format for transmission of IPv6
packets on Token Ring networks.  [STANDARDS-TRACK]













Ramos                        Informational                      [Page 7]

RFC 2499                  Summary of 2400-2499                 July 1999


2469    Narten          Dec 1998        A Caution On The Canonical
                                        Ordering Of Link-Layer Addresses

Protocols such as ARP and Neighbor Discovery have data fields that
contain link-layer addresses. In order to interoperate properly, a
sender setting such a field must insure that the receiver extracts those
bits and interprets them correctly.  In most cases, such fields must be
in "canonical form".  Unfortunately, not all LAN adaptors are consistent
in their use of canonical form, and implementations may need to
explicitly bit swap individual bytes in order to obtain the correct
format.  This document provides information to implementors to help them
avoid the pitfall of using non-canonical forms when canonical forms are
required.  This memo provides information for the Internet community.