Request for Comments Summary RFC Numbers 3500-3599
RFC 3599
|
Document |
Type |
|
RFC - Informational
(December 2003; No errata)
|
|
Author |
|
Sandy Ginoza
|
|
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 3599 (Informational)
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group S. Ginoza
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]
Ginoza Informational [Page 1]
RFC 3599 Summary of 3500-3599 December 2003
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]
Ginoza Informational [Page 2]
RFC 3599 Summary of 3500-3599 December 2003
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
Show full document text