[rfc-dist] RFC 3952 on Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) Speech

[rfc-editor at rfc-editor.org ([e-mail])]

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


        RFC 3952

        Title:      Real-time Transport Protocol (RTP) Payload Format
                    for internet Low Bit Rate Codec (iLBC) Speech
        Author(s):  A. Duric, S. Andersen
        Status:     Experimental
        Date:       December 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      13
        Characters: 28655
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-avt-rtp-ilbc-05.txt

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


This document describes the Real-time Transport Protocol (RTP) payload
format for the internet Low Bit Rate Codec (iLBC) Speech developed by
Global IP Sound (GIPS).  Also, within the document there are included
necessary details for the use of iLBC with MIME and Session
Description Protocol (SDP).

This document is a product of the Audio/Video Transport Working Group
of the IETF.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Dec  3 13:25:32 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Dec  3 13:28:10 2004
Subject: [rfc-dist] RFC 3951 on Internet Low Bit Rate Codec (iLBC)
Message-ID: <[e-mail]>


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


        RFC 3951

        Title:      Internet Low Bit Rate Codec (iLBC)
        Author(s):  S. Andersen, A. Duric, H. Astrom, R. Hagen,
                    W. Kleijn, J. Linden
        Status:     Experimental
        Date:       December 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail]
        Pages:      194
        Characters: 373442
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-avt-ilbc-codec-05.txt

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


This document specifies a speech codec suitable for robust voice
communication over IP.  The codec is developed by Global IP Sound
(GIPS).  It is designed for narrow band speech and results in a
payload bit rate of 13.33 kbit/s for 30 ms frames and 15.20 kbit/s
for 20 ms frames.  The codec enables graceful speech quality
degradation in the case of lost frames, which occurs in connection
with lost or delayed IP packets.

This document is a product of the Audio/Video Transport Working Group
of the IETF.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Dec  3 13:29:46 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Dec  3 13:30:00 2004
Subject: [rfc-dist] RFC 3964 on Security Considerations for 6to4
Message-ID: <[e-mail]>


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


        RFC 3964

        Title:      Security Considerations for 6to4
        Author(s):  P. Savola, C. Patel
        Status:     Informational
        Date:       December 2004
        Mailbox:    [e-mail], [e-mail]
        Pages:      41
        Characters: 83360
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-6to4-security-04.txt

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


The IPv6 interim mechanism 6to4 (RFC3056) uses automatic
IPv6-over-IPv4 tunneling to interconnect IPv6 networks.  The
architecture includes 6to4 routers and 6to4 relay routers, which
accept and decapsulate IPv4 protocol-41 ("IPv6-in-IPv4") traffic
from any node in the IPv4 internet.  This characteristic enables a
number of security threats, mainly Denial of Service.  It also makes
it easier for nodes to spoof IPv6 addresses.  This document discusses
these issues in more detail and suggests enhancements to alleviate the
problems. 

This document is a product of the IPv6 Operations Working Group of the
IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Dec  3 13:31:28 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Dec  3 13:32:29 2004
Subject: [rfc-dist] RFC 3966 on The tel URI for Telephone Numbers
Message-ID: <[e-mail]>


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


        RFC 3966

        Title:      The tel URI for Telephone Numbers
        Author(s):  H. Schulzrinne
        Status:     Standards Track
        Date:       December 2004
        Mailbox:    [e-mail]
        Pages:      17
        Characters: 40783
        Obsoletes:  2806

        I-D Tag:    draft-ietf-iptel-rfc2806bis-09.txt

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


This document specifies the URI (Uniform Resource Identifier) scheme
"tel".  The "tel" URI describes resources identified by telephone
numbers.  This document obsoletes RFC 2806.

This document is a product of the IP Telephony 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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Dec 10 16:24:09 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Dec 10 16:25:33 2004
Subject: [rfc-dist] RFC 3944 on H.350 Directory Services
Message-ID: <[e-mail]>


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


        RFC 3944

        Title:      H.350 Directory Services
        Author(s):  T. Johnson, S. Okubo, S. Campos
        Status:     Informational
        Date:       December 2004
        Mailbox:    [e-mail], [e-mail],
                    [e-mail]
        Pages:      30
        Characters: 61160
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-johnson-h350-directory-serv-02.txt

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


The International Telecommunications Union Standardization Sector
(ITU-T) has created the H.350 series of Recommendations that specify
directory services architectures in support of multimedia conferencing
protocols.  The goal of the architecture is to 'directory enable'
multimedia conferencing so that these services can leverage existing
identity management and enterprise directories.  A particular goal is
to enable an enterprise or service provider to maintain a canonical
source of users and their multimedia conferencing systems, so that
multiple call servers from multiple vendors, supporting multiple
protocols, can all access the same data store.

Because SIP is an IETF standard, the contents of H.350 and H.350.4
are made available via this document to the IETF community.  This
document contains the entire normative text of ITU-T Recommendations
H.350 and H.350.4 in sections 4 and 5, respectively.  The remaining
sections are included only in this document, not in the ITU-T
version.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Fri Dec 10 16:27:04 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Fri Dec 10 16:31:06 2004
Subject: [rfc-dist] RFC 3965 on A Simple Mode of Facsimile Using Internet
	Mail
Message-ID: <[e-mail]>


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


        RFC 3965

        Title:      A Simple Mode of Facsimile Using Internet Mail
        Author(s):  K. Toyoda, H. Ohno, J. Murai, D. Wing
        Status:     Standards Track
        Date:       December 2004
        Mailbox:    [e-mail],
                    [e-mail], [e-mail], [e-mail]
        Pages:      14
        Characters: 28157
        Obsoletes:  2305

        I-D Tag:    draft-ietf-fax-service-v2-05.txt

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


This specification provides for "simple mode" carriage of facsimile
data using Internet mail.  Extensions to this document will follow.
The current specification employs standard protocols and file formats
such as TCP/IP, Internet mail protocols, Multipurpose Internet Mail
Extensions (MIME), and Tagged Image File Format (TIFF) for Facsimile.
It can send images not only to other Internet-aware facsimile devices
but also to Internet-native systems, such as PCs with common email
readers which can handle MIME mail and TIFF for Facsimile data.  The
specification facilitates communication among existing facsimile 
devices, Internet mail agents, and the gateways which connect them.

This document is a revision of RFC 2305.  There have been no technical
changes.

This document is a product of the Internet Fax (fax) Working Group of
the IETF.

This is now a Draft 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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Dec 21 15:18:28 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Dec 21 15:21:47 2004
Subject: [rfc-dist] RFC 3939 on Calling Line Identification for Voice Mail
	Messages
Message-ID: <[e-mail]>


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


        RFC 3939

        Title:      Calling Line Identification for Voice Mail
                    Messages
        Author(s):  G. Parsons, J. Maruszak
        Status:     Standards Track
        Date:       December 2004
        Mailbox:    [e-mail],
                    [e-mail]
        Pages:      11
        Characters: 22739
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ema-vpim-clid-09.txt

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


This document describes a method for identifying the originating
calling party in the headers of a stored voice mail message.  Two new
header fields are defined for this purpose: Caller_ID and Called_Name.
Caller_id is used to store sufficient information for the recipient to
callback, or reply to, the sender of the message.  Caller-name
provides the name of the person sending the message.

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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Dec 21 15:20:16 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Dec 21 15:21:51 2004
Subject: [rfc-dist] RFC 3959 on The Early Session Disposition Type for the
	Session Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3959

        Title:      The Early Session Disposition Type for
                    the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo
        Status:     Standards Track
        Date:       December 2004
        Mailbox:    [e-mail]
        Pages:      11
        Characters: 22160
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-early-disposition-03.txt

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


This document defines a new disposition type (early-session) for the
Content-Disposition header field in the Session Initiation Protocol
(SIP).  The treatment of "early-session" bodies is similar to the
treatment of "session" bodies.  That is, they follow the offer/answer
model.  Their only difference is that session descriptions whose
disposition type is "early-session" are used to establish early media
sessions within early dialogs, as opposed to regular sessions within
regular dialogs.

This document is a product of the Session Initiation Proposal
Investigation 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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Dec 21 15:21:52 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Dec 21 15:23:36 2004
Subject: [rfc-dist] RFC 3960 on Early Media and Ringing Tone Generation in
	the Session Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        RFC 3960

        Title:      Early Media and Ringing Tone Generation
                    in the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo, H. Schulzrinne
        Status:     Informational
        Date:       December 2004
        Mailbox:    [e-mail],
                    [e-mail]
        Pages:      13
        Characters: 31692
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-early-media-02.txt

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


This document describes how to manage early media in the Session
Initiation Protocol (SIP) using two models: the gateway model and the
application server model.  It also describes the inputs one needs to
consider in defining local policies for ringing tone generation.

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

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Dec 21 15:23:38 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Dec 21 15:25:54 2004
Subject: [rfc-dist] BCP 98,
	RFC 3968 on The Internet Assigned Number Authority
	(IANA) Header Field Parameter Registry for the Session
	Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        BCP 98
        RFC 3968

        Title:      The Internet Assigned Number Authority (IANA)
                    Header Field Parameter Registry for
                    the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo
        Status:     Best Current Practice
        Date:       December 2004
        Mailbox:    [e-mail]
        Pages:      8
        Characters: 20615
        Updates:    3427
        See Also:   BCP 98

        I-D Tag:    draft-ietf-sip-parameter-registry-02.txt

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


This document creates an Internet Assigned Number Authority (IANA)
registry for the Session Initiation Protocol (SIP) header field
parameters and parameter values.  It also lists the already existing
parameters and parameter values to be used as the initial entries for
this registry.

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

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative
From rfc-editor at rfc-editor.org  Tue Dec 21 15:25:11 2004
From: rfc-editor at rfc-editor.org ([e-mail])
Date: Tue Dec 21 15:30:26 2004
Subject: [rfc-dist] BCP 99,
	RFC 3969 on The Internet Assigned Number Authority
	(IANA) Uniform Resource Identifier (URI) Parameter Registry
	for the Session Initiation Protocol (SIP)
Message-ID: <[e-mail]>


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


        BCP 99
        RFC 3969

        Title:      The Internet Assigned Number Authority (IANA)
                    Uniform Resource Identifier (URI) Parameter
                    Registry for the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo
        Status:     Best Current Practice
        Date:       December 2004
        Mailbox:    [e-mail]
        Pages:      6
        Characters: 12119
        Updates:    3427
        SeeAlso:    BCP 99

        I-D Tag:    draft-ietf-sip-uri-parameter-reg-02.txt

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


This document creates an Internet Assigned Number Authority (IANA)
registry for the Session Initiation Protocol (SIP) and SIPS Uniform
Resource Identifier (URI) parameters, and their values.  It also lists
the already existing parameters to be used as initial values for that
registry.

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

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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.
-------------- next part --------------
Skipped content of type multipart/alternative