RFC 3599 (rfc3599) - Page 2 of 34


Request for Comments Summary RFC Numbers 3500-3599



Alternative Format: Original Text Document



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