A new Request for Comments is now available in online RFC libraries.
RFC 5363
Title: Framework and Security Considerations for
Session Initiation Protocol (SIP) URI-List Services
Author: G. Camarillo, A.B. Roach
Status: Standards Track
Date: October 2008
Mailbox: Gonzalo.Camarillo@xxxxxxxxxxxx,
Adam.Roach@xxxxxxxxxxx
Pages: 10
Characters: 22912
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sipping-uri-services-07.txt
URL: http://www.rfc-editor.org/rfc/rfc5363.txt
This document describes the need for SIP URI-list services and
provides requirements for their invocation. Additionally, it defines
a framework for SIP URI-list services, which includes security
considerations applicable to these services. [STANDARDS TRACK]
This document is a product of the Session Initiation Proposal
Investigation 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@xxxxxxxxxxxxxxx Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
USC/Information Sciences Institute
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
