[rfc-dist] RFC 5079 on Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)

[rfc-editor@rfc-editor.org]

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

        
        RFC 5079

        Title:      Rejecting Anonymous Requests in the 
                    Session Initiation Protocol (SIP) 
        Author:     J. Rosenberg
        Status:     Standards Track
        Date:       December 2007
        Mailbox:    jdrosen at cisco.com
        Pages:      8
        Characters: 15670
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sip-acr-code-05.txt

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

The Session Initiation Protocol (SIP) allows for users to make
anonymous calls.  However, users receiving such calls have the right
to reject them because they are anonymous.  SIP has no way to
indicate to the caller that the reason for call rejection was that
the call was anonymous.  Such an indication is useful to allow the
call to be retried without anonymity.  This specification defines a
new SIP response code for this purpose.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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.

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

...