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

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

Summary: Needs a YES. Has enough positions to pass.

Gonzalo Camarillo

Comment (2010-04-22)

Abstracts should not contain references.

Sean Turner

Comment (2010-04-21)

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) ...."

[Dan Romascanu]

Comment (2010-04-22)

I support Lars' DISCUSS.

[Russ Housley]

Comment (2010-04-21)

  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
  extensions.