Session Initiation Protocol (SIP) INFO Method and Package Framework
RFC 6086

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

(Robert Sparks) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

Comment (2010-04-22 for -)
Abstracts should not contain references.

(Lars Eggert) (was Discuss) No Objection

(Adrian Farrel) No Objection

(Russ Housley) No Objection

Comment (2010-04-21 for -)
  Please consider the Gen-ART Review comments from Brian Carpenter:

  As a newcomer to the topic, I found the guidance on when to choose the
  Info-Package mechanism and when to choose an alternative (Section 7) a
  little weak. I didn't get a strong sense of when it would be clearly
  idiotic to choose Info-Package (except for bulk data transfer). Maybe
  an Informational document on this would be helpful. Otherwise, the
  mechanism seems at some risk of becoming a catch-all for proprietary

Alexey Melnikov (was Discuss) No Objection

(Tim Polk) No Objection

(Dan Romascanu) No Objection

Comment (2010-04-22 for -)
I support Lars' DISCUSS.

(Peter Saint-Andre) (was Discuss) No Objection

(Sean Turner) No Objection

Comment (2010-04-21 for -)
I support Lars' DISCUSS position.

Sec 6.1: Define "Mandatory".  If its meaning is taken from RFC 3291 add something like "Mandatory (as defined in RFC3261) ...."