Request for Comments: 3599 ISI
Category: Informational December 2003
Request for Comments Summary
RFC Numbers 3500-3599
Status of This Memo
This RFC is a slightly annotated list of the 100 RFCs from RFC 3500
through RFC 3599. 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 (2003). 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
--- ------ ---- -----
3599 Ginoza Request for Comments Summary
This memo.
3598 Murchison Sep 2003 Sieve Email Filtering --
Subaddress Extension
On email systems that allow for "subaddressing" or "detailed addressing"
(e.g., "ken+sieve@example.org"), it is sometimes desirable to make
comparisons against these sub-parts of addresses. This document defines
an extension to the Sieve mail filtering language that allows users to
compare against the user and detail parts of an address. [STANDARDS
TRACK]
3597 Gustafsson Sep 2003 Handling of Unknown DNS
Resource Record (RR) Types
Extending the Domain Name System (DNS) with new Resource Record (RR)
types currently requires changes to name server software. This document
specifies the changes necessary to allow future DNS implementations to
handle new RR types transparently. [STANDARDS TRACK]
3596 Thomson Oct 2003 DNS Extensions to Support IP
Version 6
This document defines the changes that need to be made to the Domain
Name System (DNS) to support hosts running IP version 6 (IPv6). The
changes include a resource record type to store an IPv6 address, a
domain to support lookups based on an IPv6 address, and updated
definitions of existing query types that return Internet addresses as
part of additional section processing. The extensions are designed to
be compatible with existing applications and, in particular, DNS
implementations themselves. [STANDARDS TRACK]
3595 Wijnen Sep 2003 Textual Conventions for IPv6
Flow Label
This MIB module defines textual conventions to represent the commonly
used IPv6 Flow Label. The intent is that these textual conventions
(TCs) will be imported and used in MIB modules that would otherwise
define their own representations. [STANDARDS TRACK]
3594 Duffy Sep 2003 PacketCable Security Ticket
Control Sub-Option for the
DHCP CableLabs Client
Configuration (CCC) Option
This document defines a new sub-option for the DHCP CableLabs Client
Configuration (CCC) Option. This new sub-option will be used to direct
CableLabs Client Devices (CCDs) to invalidate security tickets stored in
CCD non volatile memory (i.e., locally persisted security tickets).
[STANDARDS TRACK]
3593 Tesink, Ed. Sep 2003 Textual Conventions for MIB
Modules Using Performance
History Based on 15 Minute
Intervals
This document defines a set of Textual Conventions for MIB modules that
make use of performance history data based on 15 minute intervals.
This memo replaces RFC 2493. Changes relative to RFC 2493 are
summarized in the MIB module’s REVISION clause. [STANDARDS TRACK]
3592 Tesink Sep 2003 Definitions of Managed Objects
for the Synchronous Optical
Network/Synchronous Digital
Hierarchy (SONET/SDH)
Interface Type
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in TCP/IP-based internets. In
particular, it defines objects for managing Synchronous Optical
Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This
document is a companion to the documents that define Managed Objects for
the DS1/E1/DS2/E2 and DS3/E3 Interface Types.
This memo replaces RFC 2558. Changes relative to RFC 2558 are
summarized in the MIB module’s REVISION clause. [STANDARDS TRACK]
3591 Lam Sep 2003 Definitions of Managed Objects
for the Optical Interface Type
This memo defines a portion of the Management Information Base (MIB) for
use with Simple Network Management Protocol (SNMP) in TCP/IP-based
internets. In particular, it defines objects for managing Optical
Interfaces associated with WavelengthDivision Multiplexing systems or
characterized by the Optical Transport Network (OTN) in accordance with
the OTN architecture defined in ITU-T Recommendation G.872.
The MIB module defined in this memo can be used for performance
monitoring and/or configuration of such optical interface. [STANDARDS
TRACK]
3590 Haberman Sep 2003 Source Address Selection for
the Multicast Listener
Discovery (MLD) Protocol
It has come to light that there is an issue with the selection of a
suitable IPv6 source address for Multicast Listener Discovery (MLD)
messages when a node is performing stateless address autoconfiguration.
This document is intended to clarify the rules on selecting an IPv6
address to use for MLD messages. [STANDARDS TRACK]
3589 Loughney Sep 2003 Diameter Command Codes for
Third Generation Partnership
Project (3GPP) Release 5
This document describes the IANA’s allocation of a block of Diameter
Command Codes for the Third Generation Partnership Project (3GPP)
Release 5. This document does not pass judgment on the usage of these
command codes. Further more, these command codes are for use for
Release 5. For future releases, these codes cannot be reused, but must
be allocated according to the Diameter Base specification. This memo
provides information for the Internet community.
3588 Calhoun Sep 2003 Diameter Base Protocol
The Diameter base protocol is intended to provide an Authentication,
Authorization and Accounting (AAA) framework for applications such as
network access or IP mobility. Diameter is also intended to work in
both local Authentication, Authorization & Accounting and roaming
situations. This document specifies the message format, transport,
error reporting, accounting and security services to be used by all
Diameter applications. The Diameter base application needs to be
supported by all Diameter implementations. [STANDARDS TRACK]
3587 Hinden Aug 2003 IPv6 Global Unicast Address
Format
This document obsoletes RFC 2374, "An IPv6 Aggregatable Global Unicast
Address Format". It defined an IPv6 address allocation structure that
includes Top Level Aggregator (TLA) and Next Level Aggregator (NLA).
This document makes RFC 2374 and the TLA/NLA structure historic. This
memo provides information for the Internet community.
3586 Blaze Aug 2003 IP Security Policy (IPSP)
Requirements
This document describes the problem space and solution requirements for
developing an IP Security Policy (IPSP) configuration and management
framework. The IPSP architecture provides a scalable, decentralized
framework for managing, discovering and negotiating the host and network
security policies that govern access, authorization, authentication,
confidentiality, data integrity, and other IP Security properties. This
document highlights such architectural components and presents their
functional requirements. [STANDARDS TRACK]
3585 Jason Aug 2003 IPsec Configuration Policy
Information Model
This document presents an object-oriented information model of IP
Security (IPsec) policy designed to facilitate agreement about the
content and semantics of IPsec policy, and enable derivations of task-
specific representations of IPsec policy such as storage schema,
distribution representations, and policy specification languages used to
configure IPsec-enabled endpoints. The information model described in
this document models the configuration parameters defined by IPSec. The
information model also covers the parameters found by the Internet Key
Exchange protocol (IKE). Other key exchange protocols could easily be
added to the information model by a simple extension. Further
extensions can further be added easily due to the object-oriented nature
of the model.
This information model is based upon the core policy classes as defined
in the Policy Core Information Model (PCIM) and in the Policy Core
Information Model Extensions (PCIMe). [STANDARDS TRACK]
3584 Frye Aug 2003 Coexistence between Version 1,
Version 2, and Version 3 of
the Internet-standard Network
Management Framework
The purpose of this document is to describe coexistence between version
3 of the Internet-standard Network Management Framework, (SNMPv3),
version 2 of the Internet-standard Network Management Framework
(SNMPv2), and the original Internet-standard Network Management
Framework (SNMPv1). This document also describes how to convert MIB
modules from SMIv1 format to SMIv2 format. This document obsoletes RFC
2576. This document specifies an Internet Best Current Practices for
the Internet Community, and requests discussion and suggestions for
improvements.
3583 Chaskar, Ed. Sep 2003 Requirements of a Quality of
Service (QoS) Solution for
Mobile IP
Mobile IP ensures correct routing of packets to a mobile node as the
mobile node changes its point of attachment to the Internet. However,
it is also required to provide proper Quality of Service (QoS)
forwarding treatment to the mobile node’s packet stream at the
intermediate nodes in the network, so that QoS-sensitive IP services can
be supported over Mobile IP. This document describes requirements for
an IP QoS mechanism for its satisfactory operation with Mobile IP. This
memo provides information for the Internet community.
3582 Abley Aug 2003 Goals for IPv6
Site-Multihoming Architectures
This document outlines a set of goals for proposed new IPv6 site-
multihoming architectures. It is recognised that this set of goals is
ambitious and that some goals may conflict with others. The solution or
solutions adopted may only be able to satisfy some of the goals
presented here. This memo provides information for the Internet
community.
3581 Rosenberg Aug 2003 An Extension to the Session
Initiation Protocol (SIP) for
Symmetric Response Routing
The Session Initiation Protocol (SIP) operates over UDP and TCP, among
others. When used with UDP, responses to requests are returned to the
source address the request came from, and to the port written into the
topmost Via header field value of the request. This behavior is not
desirable in many cases, most notably, when the client is behind a
Network Address Translator (NAT). This extension defines a new
parameter for the Via header field, called "rport", that allows a client
to request that the server send the response back to the source IP
address and port from which the request originated. [STANDARDS TRACK]
3580 Congdon Sep 2003 IEEE 802.1X Remote
Authentication Dial In User
Service (RADIUS) Usage
Guidelines
This document provides suggestions on Remote Authentication Dial In User
Service (RADIUS) usage by IEEE 802.1X Authenticators. The material in
this document is also included within a non-normative Appendix within
the IEEE 802.1X specification, and is being presented as an IETF RFC for
informational purposes. This memo provides information for the Internet
community.
3579 Aboba Sep 2003 RADIUS (Remote Authentication
Dial In User Service)
Support For Extensible
Authentication Protocol (EAP)
This document defines Remote Authentication Dial In User Service
(RADIUS) support for the Extensible Authentication Protocol (EAP), an
authentication framework which supports multiple authentication
mechanisms. In the proposed scheme, the Network Access Server (NAS)
forwards EAP packets to and from the RADIUS server, encapsulated within
EAP-Message attributes. This has the advantage of allowing the NAS to
support any EAP authentication method, without the need for method-
specific code, which resides on the RADIUS server. While EAP was
originally developed for use with PPP, it is now also in use with IEEE
802. This memo provides information for the Internet community.
3578 Camarillo Aug 2003 Mapping of Integrated Services
Digital Network (ISDN) User
Part (ISUP) Overlap Signalling
to the Session Initiation
Protocol (SIP)
This document describes a way to map Integrated Services Digital Network
User Part (ISUP) overlap signalling to Session Initiation Protocol
(SIP). This mechanism might be implemented when using SIP in an
environment where part of the call involves interworking with the Public
Switched Telephone Network (PSTN). [STANDARDS TRACK]
3577 Waldbusser Aug 2003 Introduction to the Remote
Monitoring (RMON) Family of
MIB Modules
The Remote Monitoring (RMON) Framework consists of a number of
interrelated documents. This memo describes these documents and how
they relate to one another. This memo provides information for the
Internet community.
3576 Chiba Jul 2003 Dynamic Authorization
Extensions to Remote
Authentication Dial In User
Service (RADIUS)
This document describes a currently deployed extension to the Remote
Authentication Dial In User Service (RADIUS) protocol, allowing dynamic
changes to a user session, as implemented by network access server
products. This includes support for disconnecting users and changing
authorizations applicable to a user session. This memo provides
information for the Internet community.
3575 Aboba Jul 2003 IANA Considerations for RADIUS
(Remote Authentication Dial In
User Service)
This document describes the IANA considerations for the Remote
Authentication Dial In User Service (RADIUS). [STANDARDS TRACK]
3574 Soininen, Ed. Aug 2003 Transition Scenarios for 3GPP
Networks
This document describes different scenarios in Third Generation
Partnership Project (3GPP) defined packet network, i.e., General Packet
Radio Service (GPRS) that would need IP version 6 and IP version 4
transition. The focus of this document is on the scenarios where the
User Equipment (UE) connects to nodes in other networks, e.g., in the
Internet. GPRS network internal transition scenarios, i.e., between
different GPRS elements in the network, are out of scope. The purpose
of the document is to list the scenarios for further discussion and
study. This memo provides information for the Internet community.
3573 Goyret Jul 2003 Signaling of Modem-On-Hold
status in Layer 2 Tunneling
Protocol (L2TP)
The Layer 2 Tunneling Protocol (L2TP) defines a mechanism for tunneling
Point-to-Point Protocol (PPP) sessions. It is common for these PPP
sessions to be established using modems connected over the public
switched telephone network.
One of the standards governing modem operation defines procedures that
enable a client modem to put the call on hold and later, re-establish
the modem link with minimal delay and without having to redial. While
the modem call is on hold, the client phone line can be used to place or
receive other calls.
The L2TP base protocol does not provide any means to signal these events
from the L2TP Access Controller (LAC), where the modem is physically
connected, to the L2TP Network Server (LNS), where the PPP session is
handled.
This document describes a method to let the LNS know when a client modem
connected to a LAC has placed the call on hold. [STANDARDS TRACK]
3572 Ogura Jul 2003 Internet Protocol Version 6
over MAPOS (Multiple Access
Protocol Over SONET/SDH)
Multiple Access Protocol over SONET/SDH (MAPOS) is a high-speed link-
layer protocol that provides multiple access capability over a
Synchronous Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH).
This document specifies the frame format for encapsulating an IPv6
datagram in a MAPOS frame. It also specifies the method of forming IPv6
interface identifiers, the method of detecting duplicate addresses, and
the format of the Source/Target Link-layer Addresses option field used
in IPv6 Neighbor Discovery messages. This memo provides information for
the Internet community.
3571 Rawlins Aug 2003 Framework Policy Information
Base for Usage Feedback
This document describes a portion of the Policy Information Base (PIB)
to control policy usage collection and reporting in a device.
The provisioning classes specified here allow a Policy Decision Point
(PDP) to select which policy objects should collect usage information,
what information should be collected and when it should be reported.
This PIB requires the presence of other PIBs (defined elsewhere) that
provide the policy objects from which usage information is collected.
This memo provides information for the Internet community.
3570 Rzewski Jul 2003 Content Internetworking (CDI)
Scenarios
In describing content internetworking as a technology targeted for use
in production networks, it is useful to provide examples of the sequence
of events that may occur when two content networks decide to
interconnect. The scenarios presented here seek to provide some
concrete examples of what content internetworking is, and also to
provide a basis for evaluating content internetworking proposals. This
memo provides information for the Internet community.
3569 Bhattacharyya Jul 2003 An Overview of Source-Specific
Multicast (SSM)
The purpose of this document is to provide an overview of
Source-Specific Multicast (SSM) and issues related to its deployment.
It discusses how the SSM service model addresses the challenges faced in
inter-domain multicast deployment, changes needed to routing protocols
and applications to deploy SSM and interoperability issues with current
multicast service models. This memo provides information for the
Internet community.
3568 Barbir Jul 2003 Known Content Network (CN)
Request-Routing Mechanisms
This document presents a summary of Request-Routing techniques that are
used to direct client requests to surrogates based on various policies
and a possible set of metrics. The document covers techniques that were
commonly used in the industry on or before December 2000. In this memo,
the term Request-Routing represents techniques that is commonly called
content routing or content redirection. In principle, Request-Routing
techniques can be classified under: DNS Request-Routing, Transport-layer
Request-Routing, and Application-layer Request-Routing. This memo
provides information for the Internet community.
3567 Li Jul 2003 Intermediate System to
Intermediate System (IS-IS)