Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF)
draft-ietf-simple-prescaps-ext-10

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>, 
    simple mailing list <simple@ietf.org>, 
    simple chair <simple-chairs@tools.ietf.org>
Subject: Protocol Action: 'Session Initiation Protocol (SIP) 
         User Agent Capability Extension to Presence Information Data 
         Format (PIDF)' to Proposed Standard 

The IESG has approved the following document:

- 'Session Initiation Protocol (SIP) User Agent Capability Extension to 
   Presence Information Data Format (PIDF) '
   <draft-ietf-simple-prescaps-ext-11.txt> as a Proposed Standard

This document is the product of the SIP for Instant Messaging and 
Presence Leveraging Extensions Working Group. 

The IESG contact persons are Jon Peterson and Cullen Jennings.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-simple-prescaps-ext-11.txt

Ballot Text

Technical Summary
 
This memo introduces a SIP specific extension mechanism to the
Presence Information Document Format to represent SIP User Agent
capabilities using the SIP feature tags defined in RFC3840. With
this extension, presence applications based on SIP can express richer
and more usable presence data compared to the baseline PIDF.
 
Working Group Summary
 
This document reflects the consensus of the SIMPLE working group.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson. Robert Sparks is
the document shepherd. Gen-ART review was provided by Christian Vogt.

Note to RFC Editor
 
References:

Please change reference [12] to the following:

   [12] Camarillo, G., "Internet Assigned Numbers Authority (IANA)
        Registration of the Message Media Feature Tag", RFC 4569,
        July 2006.

Also, please move reference [12] to the Informational References section
of the document.

RFC Editor Note