HTTP Adaptation with Open Pluggable Edge Services (OPES)
RFC 4236

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

(Ted Hardie) Yes

(Harald Alvestrand) No Objection

(Steven Bellovin) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) (was Discuss) No Objection

(Scott Hollenbeck) No Objection

(Russ Housley) No Objection

(David Kessens) No Objection

(Allison Mankin) (was Discuss) No Objection

Comment (2005-04-20)
No email
send info
The 03 rev addresses both my Discuss and my comments after a lot of useful
discussion with the Editors and Markus Hofmann (and also a useful review of the
document on my behalf by Sam Hartman for the HTTPS concern).


Please change   www.restricted-content.org -> www.restricted-content.example.org

Similarly, change the FQDNs ocp-test.com, example-cdn.com and opes-services-4u.com

This draft cites wiretapping as an application.  What was the resolution of this subject
in the earlier opes document?  My own take is it should not be there, or there should be
a strong caveat that it's a by-product of other application features.

(Thomas Narten) No Objection

(Jon Peterson) No Objection

(Bert Wijnen) No Objection

(Alex Zinin) (was Discuss) No Objection