Document: draft-hollenbeck-epp-rfc3730bis-03
Reviewer: Harald Tveit Alvestrand
Review Date: 2006-11-10
IETF LC End Date: 2006-11-11
Summary: One question about a protocol change, otherwise OK

Since this document is going to Draft, I did not review the base 
technology, or the unchanged parts of the documents. I focused on the 
changes from the RFC version and the implementation report.

The "changes from RFC 3730" section seems a clear and complete list of the 
changes found by using a diff tool; this is very good.

The changelist documents one protocol change: the <poll> acknowledgement 
response changed the value of the message ID by 1 - from "the next message 
available" to "the message that has been acknowledged". I would be happier 
about this if two things had been stated:

- The reason for the change (in the draft), and whether or not it affects 
interoperability with old implementations
- That the tested implementations actually implement the changed protocol, 
not the RFC 3730 protocol (in the implementation report).

The last is implicit in the fact that the implementation reports refer to 
the -bis documents, so this may be OK. IESG's call.

There is one feature that has only been tested for one client/server pair: 
<response><extValue>. It seems an easy value to support, so I would not 
think it worrisome - but it's a departure from the formal requirements.

The document seems otherwise fine to me.