[rfc-dist] RFC 5009 on Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue Sep 25 15:32:43 PDT 2007


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

        
        RFC 5009

        Title:      Private Header (P-Header) Extension to 
                    the Session Initiation Protocol (SIP) for 
                    Authorization of Early Media 
        Author:     R. Ejza
        Status:     Informational
        Date:       September 2007
        Mailbox:    ejzak at alcatel-lucent.com
        Pages:      15
        Characters: 36092
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ejzak-sipping-p-em-auth-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5009.txt

This document describes a private Session Initiation Protocol (SIP)
header field (P-header) to be used by the European
Telecommunications Standards Institute (ETSI) Telecommunications and
Internet-converged Services and Protocols for Advanced Networks
(TISPAN) for the purpose of authorizing early media flows in Third
Generation Partnership Project (3GPP) IP Multimedia Subsystems
(IMS).  This header field is useful in any SIP network that is
interconnected with other SIP networks and needs to control the flow
of media in the early dialog state.  This memo provides information for 
the Internet community.


INFORMATIONAL: 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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list