Identification of Communications Services in the Session Initiation Protocol (SIP)
draft-ietf-sipping-service-identification-04

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    sipping mailing list <sipping@ietf.org>, 
    sipping chair <sipping-chairs@tools.ietf.org>
Subject: Document Action: 'Identification of Communications Services in the Session Initiation Protocol (SIP)' to Informational RFC

The IESG has approved the following document:

- 'Identification of Communications Services in the Session Initiation 
   Protocol (SIP) '
   <draft-ietf-sipping-service-identification-04.txt> as an Informational RFC


This document is the product of the Session Initiation Proposal Investigation Working Group. 

The IESG contact persons are Robert Sparks and Cullen Jennings.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-identification-04.txt

Ballot Text

Technical Summary


This document considers the problem of service identification in the
Session Initiation Protocol (SIP). Service identification is the
process of determining the user-level use case that is driving the
signaling being utilized by the user agent. This document discusses
the uses of service identification, and outlines several
architectural principles behind the process. It identifies perils
when service identification is not done properly - including fraud,
interoperability failures and stifling of innovation.

Working Group Summary

The creation of this document was triggered by discussions with 3GPP in
the area of service identification. After those discussions, most active
participants supported the approach documented in this draft.

Document Quality

This document does not define a protocol. There are existing
architectures using the approach discussed in this document.

Personnel

Gonzalo Camarillo is the document shepherd. 
Robert Sparks is the responsible area director.

RFC Editor Note