[rfc-dist] RFC 3680 on A Session Initiation Protocol (SIP) Event Package for Registrations

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Wed Mar 31 17:01:53 PST 2004


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


        RFC 3680

        Title:      A Session Initiation Protocol (SIP) Event Package
                    for Registrations
        Author(s):  J. Rosenberg
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    jdrosen at dynamicsoft.com
        Pages:      26
        Characters: 35403
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-reg-event-00.txt

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


This document defines a Session Initiation Protocol (SIP) event
package for registrations.  Through its REGISTER method, SIP allows a
user agent to create, modify, and delete registrations.  Registrations
can also be altered by administrators in order to enforce policy.  As
a result, these registrations represent a piece of state in the
network that can change dynamically.  There are many cases where a
user agent would like to be notified of changes in this state.  This
event package defines a mechanism by which those user agents can
request and obtain such notifications.

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 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.echo 
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

...

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


More information about the rfc-dist mailing list