Hello Scott. While doing the shepherd writeup, noted few minor things which may help polish the doc further.
* 5.5: Add “The” to the "Autonomous System Number Object Class” section title to be consistent with others. * 1, 5, 5.4, 5.5, 7, 8: Looks like the [I-D.ietf-regext-rfc7482bis] reference needs the correct link. Additionally, in section 8, [I-D.ietf-regext-rfc7482bis] has no link. * 1.1: Is the trailing period intended for member, object, and object class definitions? * 2.1: Should lunarNic prefix in the fields match the casing of the lunarNIC prefix for the extension in 4.1? I know there was some discussion on this but not sure if they are orthogonal or not. * 4.5: Looks like extraneous trailing period for eventDate description. * 5.3: Does the description of the network member need a trailing period? * 5.5: "high-level structure of the autnum object class consists of information about the network registration” - should “network” be changed to "autonomous system number”? * Should phrase “registry unique” be “registry-unique” to be consistent? * 13.2: [RFC7480] needs a link. * Typo “referencce” in the Changes from RFC 7483 section. Also, “00:” used twice in the list. Thanks, Jasdip
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
