Request for Comments Summary RFC Numbers 3400-3499
RFC 3499
|
| Document |
Type |
|
RFC - Informational
(December 2003; No errata)
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
Legacy
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
| Stream |
Legacy state
|
|
(None)
|
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
RFC 3499 (Informational)
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group S. Ginoza
Request for Comments: 3499 ISI
Category: Informational December 2003
Request for Comments Summary
RFC Numbers 3400-3499
Status of This Memo
This RFC is a slightly annotated list of the 100 RFCs from RFC 3400
through RFC 3499. 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
--- ------ ---- -----
3499 Ginoza Request for Comments Summary
This memo.
Ginoza Informational [Page 1]
RFC 3499 Summary of 3400-3499 December 2003
3498 Kuhfeld Mar 2003 Definitions of Managed Objects
for Synchronous Optical
Network (SONET) Linear
Automatic Protection Switching
(APS) Architectures
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 networks using Synchronous
Optical Network (SONET) linear Automatic Protection Switching (APS)
architectures. [STANDARDS TRACK]
3497 Gharai Mar 2003 RTP Payload Format for
Society of Motion Picture and
Television Engineers (SMPTE)
292M Video
This memo specifies an RTP payload format for encapsulating uncompressed
High Definition Television (HDTV) as defined by the Society of Motion
Picture and Television Engineers (SMPTE) standard, SMPTE 292M. SMPTE is
the main standardizing body in the motion imaging industry and the SMPTE
292M standard defines a bit-serial digital interface for local area HDTV
transport. [STANDARDS TRACK]
3496 Malis Mar 2003 Protocol Extension for Support
of Asynchronous Transfer Mode
(ATM) Service Class-aware
Multiprotocol Label Switching
(MPLS) Traffic Engineering
This document specifies a Resource ReSerVation Protocol-Traffic
Engineering (RSVP-TE) signaling extension for support of Asynchronous
Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching
(MPLS) Traffic Engineering. This memo provides information for the
Internet community.
Ginoza Informational [Page 2]
RFC 3499 Summary of 3400-3499 December 2003
3495 Beser Mar 2003 Dynamic Host Configuration
Protocol (DHCP) Option
for CableLabs Client
Configuration
This document defines a Dynamic Host Configuration Protocol (DHCP)
option that will be used to configure various devices deployed within
CableLabs architectures. Specifically, the document describes DHCP
option content that will be used to configure one class of CableLabs
client device: a PacketCable Media Terminal Adapter (MTA). The option
content defined within this document will be extended as future
CableLabs client devices are developed. [STANDARDS TRACK]
3494 Zeilenga Mar 2003 Lightweight Directory Access
Protocol version 2 (LDAPv2)
to Historic Status
This document recommends the retirement of version 2 of the Lightweight
Directory Access Protocol (LDAPv2) and other dependent specifications,
and discusses the reasons for doing so. This document recommends RFC
1777, 1778, 1779, 1781, and 2559 (as well as documents they superseded)
be moved to Historic status. This memo provides information for the
Internet community.
3493 Gilligan Mar 2003 Basic Socket Interface
Extensions for IPv6
Show full document text