The IESG has approved the following document: - 'Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP) ' <draft-ietf-sip-uri-list-message-03.txt> as a Proposed Standard This document is the product of the Session Initiation Protocol Working Group. The IESG contact persons are Cullen Jennings and Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-uri-list-message-03.txt Technical Summary This document specifies a mechanism that allows a SIP User Agent Client (UAC) to request a SIP URI-list (Uniform Resource Identifier list) service to send a SIP MESSAGE request to a set of destinations. The client sends a SIP MESSAGE request that includes the payload along with the URI-list to the MESSAGE URI-list service, which sends a similar MESSAGE request to each of the URIs included in the list. Working Group Summary The document was originally produced by the SIPPING working group, but was transferred to the SIP working group due to the need to define a new option tag, in conformance with RFC 3427. There is consensus in the WG to publish this document. Document Quality There is a strong requirement from OMA and 3GPP for a SIP solution in this area. Personnel Keith Drage is the document shepherd for this document. Cullen Jennings is the responsible Area Director. Note to RFC Editor Page 10: OLD: Failing to copy the From header field of the sender would prevent the recipient to get a hint of the sender's identity. NEW: Failure to copy the From header field of the sender results in unacceptable security and privacy failures. Page 11: add reference to RFC 3261 OLD: o A MESSAGE URI-list service SHOULD create a separate count for the CSeq header field of the outgoing MESSAGE request. NEW: o A MESSAGE URI-list service SHOULD create a separate count for the CSeq header field [RFC3261] of the outgoing MESSAGE request. ^^^^^^^^^ _______________________________________________ IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
