Representing Trunk Groups in tel/sip Uniform Resource Identifiers (URIs)
RFC 4904
Note: This ballot was opened for revision 10 and is now closed.
(Jon Peterson) Yes
(Jari Arkko) No Objection
(Ross Callon) No Objection
(Brian Carpenter) No Objection
Comment (2007-01-10 for -)
No email
send info
send info
6. Normative behavior of SIP entities using trunk groups In order to satisfy REQ 3, the placement of the trunk group parameters in a SIP Contact header or a R-URI, respectively, signifies the intent. I had to read that sentence, and REQ 3, and the following sentence, several times before I could understand it. But having understood it, I think it's redundant and confusing.