Skip to main content

Telechat Review of draft-ietf-regext-bundling-registration-11

Request Review of draft-ietf-regext-bundling-registration
Requested revision No specific revision (document currently at 11)
Type Telechat Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2019-10-15
Requested 2019-10-07
Authors Ning Kong , Jiankang Yao , Linlin Zhou , Wil Tan , Jiagui Xie
I-D last updated 2019-10-10
Completed reviews Secdir Last Call review of -09 by Russ Housley (diff)
Genart Last Call review of -09 by Joel M. Halpern (diff)
Secdir Telechat review of -11 by Russ Housley
Genart Telechat review of -11 by Joel M. Halpern
Assignment Reviewer Joel M. Halpern
State Completed
Request Telechat review on draft-ietf-regext-bundling-registration by General Area Review Team (Gen-ART) Assigned
Posted at
Reviewed revision 11
Result Almost ready
Completed 2019-10-10
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at


Document: draft-ietf-regext-bundling-registration-11
Reviewer: Joel Halpern
Review Date: 2019-10-10
IETF LC End Date: None
IESG Telechat date: 2019-10-17

Summary: This document is almost ready for publication as an RFC.

I have received no response to my earlier review.  Some of the items have been
addressed, but not all of them.

Major issues:
    This document clearly defines normative protocol behavior.  As such, it
    would seem to either be Experimental or Proposed Standard, but not

Minor issues:
    The document incorporates items from a name space
    "urn:ietf:params:xml:ns:epp:b-dn", referred to with the prefix "b-dn:". 
    The only explanation of this meaning is in the terminology section.  
    However, the description does not indicate what document defines this

Nits/editorial comments:
    I note and appreciate that my comments on the SHOULD usage in section 7.2
    has been addressed.