SIP Telephony Device Requirements and Configuration
RFC 4504

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

(Harald Alvestrand) Discuss

Discuss (2005-02-17 for -)
Boilerplate shows that the author has scanned, but not parsed, the RFC 3667 requirements on limited rights. We cannot publish this, nor can we derive works from it. I suggest the document be held until we get a normal, unrestricted boilerplate - if the document has value, we'll certainly want to derive work from it.

The points in Mary Barnes' review are pretty significant too, and should be addressed.
Comment (2005-02-17 for -)
No email
send info
Reviewed by Mary Barnes, Gen-ART

Complete review in document comment log.

(Jon Peterson) Yes

(Brian Carpenter) No Objection

Comment (2005-06-03 for -)
No email
send info
I've dropped Harald's DISCUSS as the boilerplate is OK, but it would be good to check that Mary Barnes' comments have been handled:

https://datatracker.ietf.org/cgi-bin/idtracker.cgi?loginid=43&command=view_comment&id=31658

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Russ Housley) (was No Record, Discuss) No Objection

Comment (2005-02-17)
No email
send info
  In section 3.26, please reword to avoid "... RECOMMENDED not ..."
  I think a RF 2119 phrase like "SHOULD NOT" is appropriate.

(David Kessens) (was Discuss) No Objection

(Allison Mankin) No Objection

(Ted Hardie) (was Discuss) Abstain