Fwd:Celebration of 50 years of creation of the CCITT / ITU-T and

OKUBO Sakae okubo at MXZ.MESH.NE.JP
Wed May 31 21:46:46 EDT 2006

Dear experts,



-----Original Message-----
From: rfc-editor at rfc-editor.org [mailto:rfc-editor at rfc-editor.org] 
Sent: 31 May 2006 01:14
To: ietf-announce at ietf.org; rfc-dist at rfc-editor.org
Cc: sip at ietf.org; rfc-editor at rfc-editor.org
Subject: RFC 4485 on Guidelines for Authors of Extensions to the SessionInitiation Protocol (SIP)

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

        RFC 4485

        Title:      Guidelines for Authors of Extensions 
                    to the Session Initiation Protocol (SIP) 
        Author:     J. Rosenberg, H. Schulzrinne
        Status:     Informational
        Date:       May 2006
        Mailbox:    jdrosen at cisco.com, 
                    schulzrinne at cs.columbia.edu
        Pages:      23
        Characters: 57278
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sip-guidelines-09.txt

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

The Session Initiation Protocol (SIP) is a flexible yet simple tool for establishing interactive communications sessions across the Internet. 
Part of this flexibility is the ease with which it can be extended.  In order to facilitate effective and interoperable extensions to SIP, some guidelines need to be followed when developing SIP extensions.
This document outlines a set of such guidelines for authors of SIP extensions.  This memo provides information for the Internet community.

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

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.

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


IETF-Announce mailing list
IETF-Announce at ietf.org

More information about the sg16-avd mailing list