High-Level Requirements for Tightly Coupled SIP Conferencing
RFC 4245

Approval announcement
Draft of message to be sent after approval:

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: 'High Level Requirements for Tightly 
         Coupled SIP Conferencing' to Informational RFC 

The IESG has approved the following document:

- 'High Level Requirements for Tightly Coupled SIP Conferencing '
   <draft-ietf-sipping-conferencing-requirements-02.txt> as an Informational RFC

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

The IESG contact persons are Allison Mankin and Jon Peterson.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-conferencing-requirements-02.txt

The WG Chair shepherd for this document was Gonzalo Camarillo.

Notes to the RFC Editor

Add to the end of Section 1 a paragraph that that states
"The terms MAY, SHOULD and MUST are used as defined in [1]."

Section 3.1 Expand AOR to Address of Record

Section 3.1 and Section 3.4, change the phrase 
"we feel" to "there is consensus that".


Section 4
OLD:
   Normal SIP mechanisms including Digest
   authentication and certificates can be used. 
NEW:
  Normal SIP mechanisms including Digest
   authentication and certificates can be used [2].