Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER Method
RFC 4508

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

(Allison Mankin; former steering group member) Yes

Yes ()
No email
send info

(Bert Wijnen; former steering group member) No Objection

No Objection ()
No email
send info

(Bill Fenner; former steering group member) (was Discuss) No Objection

No Objection (2006-02-28)
No email
send info
I agree with Ted on the Ampersand-L-T issue (seems the tracker might eat entities).  Was this an I-D editing error, or did the authors really mean to use entities without the trailing semicolons (legal in HTML, not legal in XML)?

(Brian Carpenter; former steering group member) No Objection

No Objection ()
No email
send info

(David Kessens; former steering group member) No Objection

No Objection ()
No email
send info

(Jon Peterson; former steering group member) No Objection

No Objection ()
No email
send info

(Margaret Cullen; former steering group member) No Objection

No Objection ()
No email
send info

(Mark Townsley; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection ()
No email
send info

(Scott Hollenbeck; former steering group member) No Objection

No Objection ()
No email
send info

(Ted Hardie; former steering group member) No Objection

No Objection (2006-02-28)
No email
send info
I assume that this will get worked out with the RFC Editor, but I found the "&lt" and "&gt" 
less effective than simply "<" and ">" would have been:

   Note that if any URI parameters are present, the entire URI must be
   enclosed in "&lt" and "&gt".  If no "&lt" and "&gt" are present, all
   parameters after the URI are header parameters, not URI parameters.