Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)
RFC 6140

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

(Gonzalo Camarillo) Yes

(Robert Sparks) Yes

Comment (2011-01-19 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
The examples in section 8 have bugs that are important to fix before publication.
The Call-ID changes unintentionally in each example. The messages that have two Via header field values have the values in the wrong order.

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Ralph Droms) No Objection

(Lars Eggert) No Objection

(Adrian Farrel) No Objection

Comment (2011-01-20 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
AOR is used without expansion in the abstract.

(David Harrington) No Objection

(Russ Housley) No Objection

(Alexey Melnikov) No Objection

Comment (2011-01-19 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
In Section 7.1.2:

   All base64 encoding discussed in the following sections MUST use the
   character set and encoding defined in RFC 2045 [1],

RFC 4648 is a better reference here.

   except that any
   trailing "=" characters are discarded on encoding, and added as
   necessary to decode.


In Section 7.1.2.1:

SHA256-80 needs a reference and an explanation (i.e. that the output of the hash function
is truncated to 80 bits).


The first reference to TLS needs an Informative reference.

(Dan Romascanu) No Objection

Comment (2011-01-18 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
The OPS-DIR review by Warren Kumari signalled a number of nits which would be useful to fix: 

Abstract:
In the abstract many acronyms are expanded (SIP, SIP-PBX, UA), but AOR is not. Having them all expanded (or none expanded) would be nice.

Section 4:
Globally Routable UA URI's (GRUU) are first mentioned, but the reference to the RFC is in section 7.1.


Section 5.1:
Acronym "UAC" not expanded / defined.


Section 6:
s/An SSP using this mechanism/A SSP using this mechanism/


Section 7.1.2.1 (indented):
s/The registrar maintains a counter, I. this counter is/The registrar maintains a counter, I. This counter is/ (Capitalization of 't').

(Peter Saint-Andre) No Objection

(Sean Turner) (was Discuss) No Objection

Comment (2011-01-20)
No email
send info
(author adding some text) Section 7.1.2.2: Seems like there should be a pointer to RFC 4086 for the "D" method.