Representing Trunk Groups in tel/sip Uniform Resource Identifiers (URIs)
RFC 4904
Yes
(Jon Peterson)
No Objection
Lars Eggert
(Bill Fenner)
(Dan Romascanu)
(David Kessens)
(Jari Arkko)
(Lisa Dusseault)
(Mark Townsley)
(Ross Callon)
(Russ Housley)
(Sam Hartman)
(Ted Hardie)
Recuse
(Cullen Jennings)
Note: This ballot was opened for revision 10 and is now closed.
Lars Eggert
No Objection
Jon Peterson Former IESG member
Yes
Yes
()
Unknown
Bill Fenner Former IESG member
No Objection
No Objection
()
Unknown
Brian Carpenter Former IESG member
No Objection
No Objection
(2007-01-10)
Unknown
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.
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Lisa Dusseault Former IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Sam Hartman Former IESG member
(was Discuss, Abstain)
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Cullen Jennings Former IESG member
Recuse
Recuse
()
Unknown