(AES) Key
This document defines two methods for wrapping an HMAC (Hashed Message
Authentication Code) key. The first method defined uses a Triple DES
(Data Encryption Standard) key to encrypt the HMAC key. The second
method defined uses an AES (Advanced Encryption Standard) key to encrypt
the HMAC key. One place that such an algorithm is used is for the
Authenticated Data type in CMS (Cryptographic Message Syntax).
[PROPOSED STANDARD]
3536 Hoffman May 2003 Terminology Used in
Internationalization in the
IETF
This document provides a glossary of terms used in the IETF when
discussing internationalization. The purpose is to help frame
discussions of internationalization in the various areas of the IETF and
to help introduce the main concepts to IETF participants. This memo
provides information for the Internet community.
3535 Schoenwaelder May 2003 Overview of the 2002 IAB
Network Management
Workshop
This document provides an overview of a workshop held by the Internet
Architecture Board (IAB) on Network Management. The workshop was hosted
by CNRI in Reston, VA, USA on June 4 thru June 6, 2002. The goal of the
workshop was to continue the important dialog started between network
operators and protocol developers, and to guide the IETFs focus on
future work regarding network management. This report summarizes the
discussions and lists the conclusions and recommendations to the
Internet Engineering Task Force (IETF) community. This memo provides
information for the Internet community.
3534 Walleij May 2003 The application/ogg Media
Type
The Ogg Bitstream Format aims at becoming a general, freely-available
standard for transporting multimedia content across computing platforms
and networks. The intention of this document is to define the MIME
media type application/ogg to refer to this kind of content when
transported across the Internet. It is the intention of the Ogg
Bitstream Format developers that it be usable without intellectual
property concerns. [STANDARDS TRACK]
3533 Pfeiffer May 2003 The Ogg Encapsulation
Format Version 0
This document describes the Ogg bitstream format version 0, which is a
general, freely-available encapsulation format for media streams. It is
able to encapsulate any kind and number of video and audio encoding
formats as well as other data streams in a single bitstream. This memo
provides information for the Internet community. This memo provides
information for the Internet community.
3532 Anderson May 2003 Requirements for the Dynamic
Partitioning of Switching
Elements
This document identifies a set of requirements for the mechanisms used
to dynamically reallocate the resources of a switching element (e.g., an
ATM switch) to its partitions. These requirements are particularly
critical in the case of an operator creating a switch partition and then
leasing control of that partition to a third party. This memo provides
information for the Internet community.
3531 Blanchet Apr 2003 A Flexible Method for Managing
the Assignment of Bits of an
IPv6 Address Block
This document proposes a method to manage the assignment of bits of an
IPv6 address block or range. When an organisation needs to make an
address plan for its subnets or when an ISP needs to make an address
plan for its customers, this method enables the organisation to postpone
the final decision on the number of bits to partition in the address
space they have. It does it by keeping the bits around the borders of
the partition to be free as long as possible. This scheme is applicable
to any bits addressing scheme using bits with partitions in the space,
but its first intended use is for IPv6. It is a generalization of RFC
1219 and can be used for IPv6 assignments. This memo provides
information for the Internet community.
3530 Shepler Apr 2003 Network File System (NFS)
version 4 Protocol
The Network File System (NFS) version 4 is a distributed filesystem
protocol which owes heritage to NFS protocol version 2, RFC 1094, and
version 3, RFC 1813. Unlike earlier versions, the NFS version 4
protocol supports traditional file access while integrating support for
file locking and the mount protocol. In addition, support for strong
security (and its negotiation), compound operations, client caching, and
internationalization have been added. Of course, attention has been
applied to making NFS version 4 operate well in an Internet environment.
This document replaces RFC 3010 as the definition of the NFS version 4
protocol. [STANDARDS TRACK]
3529 Harold Apr 2003 XML-RPC is an Extensible
Markup Language-Remote Procedure Calling protocol that works over the
Internet. It defines an XML format for messages that are transfered
between clients and servers using HTTP. An XML-RPC message encodes
either a procedure to be invoked by the server, along with the
parameters to use in the invocation, or the result of an invocation.
Procedure parameters and results can be scalars, numbers, strings,
dates, etc.; they can also be complex record and list structures.
This document specifies a how to use the Blocks Extensible Exchange
Protocol (BEEP) to transfer messages encoded in the XML-RPC format
between clients and servers. This memo defines an Experimental Protocol
for the Internet community.
3528 Zhao Apr 2003 Mesh-enhanced Service Location
Protocol (mSLP)
This document describes the Mesh-enhanced Service Location Protocol
(mSLP). mSLP enhances the Service Location Protocol (SLP) with a
scope-based fully-meshed peering Directory Agent (DA) architecture.
Peer DAs exchange new service registrations in shared scopes via anti-
entropy and direct forwarding. mSLP improves the reliability and
consistency of SLP DA services, and simplifies Service Agent (SA)
registrations in systems with multiple DAs. mSLP is backward compatible
with SLPv2 and can be deployed incrementally. This memo defines an
Experimental Protocol for the Internet community.
3527 Kinnear Apr 2003 Link Selection sub-option
for the Relay Agent
Information Option for DHCPv4
This document describes the link selection sub-option of the relay-
agent-information option for the Dynamic Host Configuration Protocol
(DHCPv4). The giaddr specifies an IP address which determines both a
subnet, and thereby a link on which a Dynamic Host Configuration
Protocol (DHCP) client resides as well as an IP address that can be used
to communicate with the relay agent. The subnet-selection option allows
the functions of the giaddr to be split so that when one entity is
performing as a DHCP proxy, it can specify the subnet/link from which to
allocate an IP address, which is different from the IP address with
which it desires to communicate with the DHCP server. Analogous
situations exist where the relay agent needs to specify the subnet/link
on which a DHCP client resides, which is different from an IP address
that can be used to communicate with the relay agent. [STANDARDS TRACK]
3526 Kivinen May 2003 More Modular Exponential
(MODP) Diffie-Hellman groups
for Internet Key Exchange
(IKE)
This document defines new Modular Exponential (MODP) Groups for the
Internet Key Exchange (IKE) protocol. It documents the well known and
used 1536 bit group 5, and also defines new 2048, 3072, 4096, 6144, and
8192 bit Diffie-Hellman groups numbered starting at 14. The selection
of the primes for theses groups follows the criteria established by
Richard Schroeppel. [STANDARDS TRACK]
3525 Groves Jun 2003 Gateway Control Protocol
Version 1
This document defines the protocol used between elements of a physically
decomposed multimedia gateway, i.e., a Media Gateway and a Media Gateway
Controller. The protocol presented in this document meets the
requirements for a media gateway control protocol as presented in RFC
2805.
This document replaces RFC 3015. It is the result of continued
cooperation between the IETF Megaco Working Group and ITU-T Study Group
16. It incorporates the original text of RFC 3015, modified by
corrections and clarifications discussed on the Megaco
E-mail list and incorporated into the Study Group 16 Implementor’s Guide
for Recommendation H.248. The present version of this document
underwent ITU-T Last Call as Recommendation H.248 Amendment 1. Because
of ITU-T renumbering, it was published by the ITU-T as Recommendation
H.248.1 (03/2002), Gateway Control Protocol Version 1.
Users of this specification are advised to consult the H.248 Sub-series
Implementors’ Guide at http://www.itu.int/itudoc/itu-t/com16/implgd for
additional corrections and clarifications. [STANDARDS TRACK]
3524 Camarillo Apr 2003 Mapping of Media Streams to
Resource Reservation Flows
This document defines an extension to the Session Description Protocol
(SDP) grouping framework. It allows requesting a group of media streams
to be mapped into a single resource reservation flow. The SDP syntax
needed is defined, as well as a new "semantics" attribute called Single
Reservation Flow (SRF). [STANDARDS TRACK]
3523 Polk Apr 2003 Internet Emergency
Preparedness (IEPREP)
Telephony Topology Terminology
This document defines the topology naming conventions that are to be
used in reference to Internet Emergency Preparedness (IEPREP) phone
calls. These naming conventions should be used to focus the IEPREP
Working Group during discussions and when writing requirements, gap
analysis and other solutions documents. This memo provides information
for the Internet community.
3522 Ludwig Apr 2003 The Eifel Detection Algorithm
for TCP
The Eifel detection algorithm allows a TCP sender to detect a posteriori
whether it has entered loss recovery unnecessarily. It requires that
the TCP Timestamps option defined in RFC 1323 be enabled for a
connection. The Eifel detection algorithm makes use of the fact that
the TCP Timestamps option eliminates the retransmission ambiguity in
TCP. Based on the timestamp of the first acceptable ACK that arrives
during loss recovery, it decides whether loss recovery was entered
unnecessarily. The Eifel detection algorithm provides a basis for
future TCP enhancements. This includes response algorithms to back out
of loss recovery by restoring a TCP sender’s congestion control state.
This memo defines an Experimental Protocol for the Internet community.
3521 Hamer Apr 2003 Framework for Session Set-up
with Media Authorization
Establishing multimedia streams must take into account requirements for
end-to-end QoS, authorization of network resource usage and accurate
accounting for resources used. During session set up, policies may be
enforced to ensure that the media streams being requested lie within the
bounds of the service profile established for the requesting host.
Similarly, when a host requests resources to provide a certain QoS for a
packet flow, policies may be enforced to ensure that the required
resources lie within the bounds of the resource profile established for
the requesting host.
To prevent fraud and to ensure accurate billing, this document describes
various scenarios and mechanisms that provide the linkage required to
verify that the resources being used to provide a requested QoS are in-
line with the media streams requested (and authorized) for the session.
This memo provides information for the Internet community.
3520 Hamer Apr 2003 Session Authorization Policy
Element
This document describes the representation of a session authorization
policy element for supporting policy-based per-session authorization and
admission control. The goal of session authorization is to allow the
exchange of information between network elements in order to authorize
the use of resources for a service and to co-ordinate actions between
the signaling and transport planes. This document describes how a
process on a system authorizes the reservation of resources by a host
and then provides that host with a session authorization policy element
which can be inserted into a resource reservation protocol (e.g., the
Resource ReSerVation Protocol (RSVP) PATH message) to facilitate proper
and secure reservation of those resources within the network. We
describe the encoding of session authorization information as a policy
element conforming to the format of a Policy Data object (RFC 2750) and
provide details relating to operations, processing rules and error
scenarios. [STANDARDS TRACK]
3519 Levkowetz May 2003 Mobile IP Traversal of Network
Address Translation (NAT)
Devices
Mobile IP’s datagram tunnelling is incompatible with Network Address
Translation (NAT). This document presents extensions to the Mobile IP
protocol and a tunnelling method which permits mobile nodes using Mobile
IP to operate in private address networks which are separated from the
public internet by NAT devices. The NAT traversal is based on using the
Mobile IP Home Agent UDP port for encapsulated data traffic. [STANDARDS
TRACK]
3518 Higashiyama Apr 2003 Point-to-Point Protocol (PPP)
Bridging Control Protocol
(BCP)
The Point-to-Point Protocol (PPP) provides a standard method for
transporting multi-protocol datagrams over point-to-point links. PPP
defines an extensible Link Control Protocol (LCP) and proposes a family
of Network Control Protocols (NCP) for establishing and configuring
different network-layer protocols.
This document defines the NCP for establishing and configuring Remote
Bridging for PPP links.
This document obsoletes RFC 2878, which was based on the IEEE 802.1D-
1993 MAC Bridge. This document extends that specification by improving
support for bridge control packets. [STANDARDS TRACK]
3517 Blanton Apr 2003 A Conservative Selective
Acknowledgment (SACK)-based
Loss Recovery Algorithm for
TCP
This document presents a conservative loss recovery algorithm for TCP
that is based on the use of the selective acknowledgment (SACK) TCP
option. The algorithm presented in this document conforms to the spirit
of the current congestion control specification (RFC 2581), but allows
TCP senders to recover more effectively when multiple segments are lost
from a single flight of data. [STANDARDS TRACK]
3516 Nerenberg Apr 2003 IMAP4 Binary Content Extension
This memo defines the Binary extension to the Internet Message Access
Protocol (IMAP4). It provides a mechanism for IMAP4 clients and servers
to exchange message body data without using a MIME content-transfer-
encoding. [STANDARDS TRACK]
3515 Sparks Apr 2003 The Session Initiation
Protocol (SIP) Refer Method
This document defines the REFER method. This Session Initiation
Protocol (SIP) extension requests that the recipient REFER to a resource
provided in the request. It provides a mechanism allowing the party
sending the REFER to be notified of the outcome of the referenced
request. This can be used to enable many applications, including call
transfer.
In addition to the REFER method, this document defines the refer event
package and the Refer-To request header. [STANDARDS TRACK]
3514 Bellovin 1 Apr 2003 The Security Flag in the IPv4
Header
Firewalls, packet filters, intrusion detection systems, and the like
often have difficulty distinguishing between packets that have malicious
intent and those that are merely unusual. We define a security flag in
the IPv4 header as a means of distinguishing the two cases. This memo
provides information for the Internet community.
3513 Hinden Apr 2003 Internet Protocol Version 6
(IPv6) Addressing Architecture
This specification defines the addressing architecture of the IP Version
6 (IPv6) protocol. The document includes the IPv6 addressing model,
text representations of IPv6 addresses, definition of IPv6 unicast
addresses, anycast addresses, and multicast addresses, and an IPv6
node’s required addresses. [STANDARDS TRACK]
3512 MacFaden Apr 2003 Configuring Networks and
Devices with Simple Network
Management Protocol (SNMP)
This document is written for readers interested in the Internet Standard
Management Framework and its protocol, the Simple Network Management
Protocol (SNMP). In particular, it offers guidance in the effective use
of SNMP for configuration management. This information is relevant to
vendors that build network elements, management application developers,
and those that acquire and deploy this technology in their networks.
This memo provides information for the Internet community.
3511 Hickman Apr 2003 Benchmarking Methodology for
Firewall Performance
This document discusses and defines a number of tests that may be used
to describe the performance characteristics of firewalls. In addition
to defining the tests, this document also describes specific formats for
reporting the results of the tests.
This document is a product of the Benchmarking Methodology Working Group
(BMWG) of the Internet Engineering Task Force (IETF). This memo
provides information for the Internet community.
3510 Herriot Apr 2003 Internet Printing
Protocol/1.1:
IPP URL Scheme
This memo defines the "ipp" URL (Uniform Resource Locator) scheme. This
memo updates IPP/1.1: Encoding and Transport (RFC 2910), by expanding
and clarifying Section 5, "IPP URL Scheme", of RFC 2910. An "ipp" URL
is used to specify the network location of a print service that supports
the IPP Protocol (RFC 2910), or of a network resource (for example, a
print job) managed by such a print service. [STANDARDS TRACK]
3509 Zinin Apr 2003 Alternative Implementations of
OSPF Area Border Routers
Open Shortest Path First (OSPF) is a link-state intra-domain routing
protocol used for routing in IP networks. Though the definition of the
Area Border Router (ABR) in the OSPF specification does not require a
router with multiple attached areas to have a backbone connection, it is
actually necessary to provide successful routing to the inter-area and
external destinations. If this requirement is not met, all traffic
destined for the areas not connected to such an ABR or out of the OSPF
domain, is dropped. This document describes alternative ABR behaviors
implemented in Cisco and IBM routers. This memo provides information
for the Internet community.
3508 Levin Apr 2003 H.323 Uniform Resource Locator
(URL) Scheme Registration
ITU-T Recommendation H.323 version 4 introduced an H.323-specific
Uniform Resource Locator (URL). This document reproduces the H323-URL
definition found in H.323, and is published as an RFC for ease of access
and registration with the Internet Assigned Numbers Authority (IANA).
This memo provides information for the Internet community.
3507 Elson Apr 2003 Internet Content Adaptation
Protocol (ICAP)
ICAP, the Internet Content Adaption Protocol, is a protocol aimed at
providing simple object-based content vectoring for HTTP services. ICAP
is, in essence, a lightweight protocol for executing a "remote procedure
call" on HTTP messages. It allows ICAP clients to pass HTTP messages to
ICAP servers for some sort of transformation or other processing
("adaptation"). The server executes its transformation service on
messages and sends back responses to the client, usually with modified
messages. Typically, the adapted messages are either HTTP requests or
HTTP responses. This memo provides information for the Internet
community.
3506 Fujimura Mar 2003 Requirements and Design for
Voucher Trading System (VTS)
Crediting loyalty points and collecting digital coupons or gift
certificates are common functions in purchasing and trading
transactions. These activities can be generalized using the concept of
a "voucher", which is a digital representation of the right to claim
goods or services. This document presents a Voucher Trading System
(VTS) that circulates vouchers securely and its terminology; it lists
design principles and requirements for VTS and the Generic Voucher
Language (GVL), with which diverse types of vouchers can be described.
This memo provides information for the Internet community.
3505 Eastlake Mar 2003 Electronic Commerce Modeling
Language (ECML): Version 2
Requirements
This document lists the design principles, scope, and requirements for
the Electronic Commerce Modeling Language (ECML) version 2
specification. It includes requirements as they relate to Extensible
Markup Language (XML) syntax, data model, format, and payment
processing. This memo provides information for the Internet community.
3504 Eastlake Mar 2003 Internet Open Trading Protocol
(IOTP) Version 1, Errata
Since the publication of the RFCs specifying Version 1.0 of the Internet
Open Trading Protocol (IOTP), some errors have been noted. This
informational document lists these errors and provides corrections for