Browse Prior Art Database

Request for Comments Summary RFC Numbers 3500-3599 (RFC3599)

IP.com Disclosure Number: IPCOM000020977D
Original Publication Date: 2003-Dec-01
Included in the Prior Art Database: 2003-Dec-16
Document File: 35 page(s) / 77K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Ginoza: AUTHOR

Abstract

RFC Numbers 3500-3599

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

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) Opti...