Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)
RFC 5365

Note: This ballot was opened for revision 03 and is now closed.

(Cullen Jennings) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Lisa Dusseault) (was Discuss) No Objection

Comment (2008-06-17)
No email
send info
COMMENTS

1. Page 10, grammar nit:  please fix the sentence that reads

   Failing to copy the From header field of the sender would
   prevent the recipient to get a hint of the sender's identity.

Along with the grammar fix, I'd like a stronger term than "hint".  How about

   Failure to copy the From header field of the sender results
   in unacceptable security and privacy failures.

Still vague but maybe there's something better.

2. The requirement related to CSeq should reference RFC3261?

3. The VIA header field that the URI-list service adds should distinguish what it did from pure forwarding.  Is there room in SIP Via headers to indicate the function that was performed?

(Lars Eggert) No Objection

(Russ Housley) No Objection

(Jon Peterson) No Objection

(Tim Polk) No Objection

(Dan Romascanu) No Objection

(Mark Townsley) No Objection

(David Ward) No Objection