RFC 3319 on Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers

rfc-editor@rfc-editor.org Wed, 30 July 2003 23:43 UTC

Message-Id: <200307302338.h6UNcGJ10514@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3319 on Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers
Cc: rfc-editor@rfc-editor.org, sip@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 30 Jul 2003 16:38:16 -0700
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

A new Request for Comments is now available in online RFC libraries.


        RFC 3319

        Title:      Dynamic Host Configuration Protocol (DHCPv6)
                    Options for Session Initiation Protocol (SIP)
                    Servers
        Author(s):  H. Schulzrinne, B. Volz
        Status:     Standards Track
        Date:       July 2003
        Mailbox:    schulzrinne@cs.columbia.edu,
                    volz@metrocast.net
        Pages:      7
        Characters: 14444
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-sip-dhcpv6-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3319.txt


This document defines a Dynamic Host Configuration Protocol version 6
(DHCPv6) option that contains a list of domain names or IPv6 addresses
that can be mapped to one or more Session Initiation Protocol (SIP)
outbound proxy servers.  This is one of the many methods that a SIP
client can use to obtain the addresses of such a local SIP server.

This document is a product of the Session Initiation Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3319.txt"><ftp://ftp.isi.edu/in-notes/rfc3319.txt>

RFC 3319 on Dynamic Host Configuration Protocol (… rfc-editor