The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)
draft-ietf-sip-sctp-06

IANA Comments:
Upon approval of this document the IANA will add a reference to
the transport parameter and will register a new NAPTR service field value (SIPS+D2S).

In the IANA Considerations section it says that "this document defines a new value (tls-sctp) for the SIP and SIPS URI transport parameter".  Is there anything to do here or is the only IANA Action to add the reference to the transport document?

Review by Mary Barnes, Gen-ART
My "No objection" stands.

Summary:
--------
Draft is ready for publication as Proposed Standard with the correction of the following editorial nits.

Editorial nits:
---------------
- General: choose one form of spelling "signaling"/"signalling"

- Page 4, section 3.1, Transport-Layer Fragmentation bullet, 4th sentence: Propose to reword from:
" IP fragmentation increases the likelihood
  of having packet losses and makes it difficult (when not
  impossible) NAT and firewall traversal."
to:
" IP fragmentation increases the likelihood
  of having packet losses and makes NAT and firewall traversal difficult, if not
  impossible."

- Page 5, section 3.2, Easier parsing bullet, 2nd sentence: change "There is not need..." to
"There is no need...".

- Page 5, section 4, 1st sentence: expand this first usage of URI.

Discussed questions about the multi-transport complexities of SIP with the SIP chairs in early Feb, and still not sure if the spec should go forward, since the WG does not feel strongly about it.