[Sip] RFC 3608 on Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration

rfc-editor@rfc-editor.org Thu, 09 October 2003 00:01 UTC

Message-Id: <200310090000.h9900qO12690@gamma.isi.edu>
To: IETF-Announce:;
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, 08 Oct 2003 17:00:51 -0700
Subject: [Sip] RFC 3608 on Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
Precedence: bulk

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


        RFC 3608

        Title:      Session Initiation Protocol (SIP) Extension Header
                    Field for Service Route Discovery During
                    Registration
        Author(s):  D. Willis, B. Hoeneisen
        Status:     Standards Track
        Date:       October 2003
        Mailbox:    dean.willis@softarmor.com, hoeneisen@switch.ch
        Pages:      17
        Characters: 35628
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-scvrtdisco-04.txt

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


This document defines a Session Initiation Protocol (SIP) extension
header field used in conjunction with responses to REGISTER requests
to provide a mechanism by which a registrar may inform a registering
user agent (UA) of a service route that the UA may use to request
outbound services from the registrar's domain.

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/rfc3608.txt"><ftp://ftp.isi.edu/in-notes/rfc3608.txt>

[Sip] RFC 3608 on Session Initiation Protocol (SI… rfc-editor
RE: [Sip] RFC 3608 on Session Initiation Protocol… Chris Boulton
RE: [Sip] RFC 3608 on Session Initiation Protocol… Bernie Hoeneisen
Re: [Sip] RFC 3608 on Session Initiation Protocol… Jonathan Rosenberg
Re: [Sip] RFC 3608 on Session Initiation Protocol… Bernie Hoeneisen