Re: [Sidrops] Closed -- [WGLC] draft-ietf-sidrops-rpkimaxlen-09 - Ends 2/February/2022

[Christopher Morrow <[e-mail]>]

On Mon, May 2, 2022 at 2:29 PM Sriram, Kotikalapudi (Fed) <
[e-mail]> wrote:

> Hi Chris,
>
> Sorry for the delay in replying.
>
> >  1) use of private address space instead of documentation space
>
> The document provides the rationale for this in Section 1.2.
>
>
ok, I think the tool just sees: "192.168 ... complain!" :)
So, provided we put a rational, it seems fine to ignore this complaint.

1.2.  Documentation Prefixes
>
>    The documentation prefixes recommended in [RFC5737] are insufficient
>    for use as example prefixes in this document.  Therefore, this
>    document uses [RFC1918] address space for constructing example
>    prefixes.
>
> BTW, the same rationale was used in RFC 6907
> https://www.rfc-editor.org/rfc/rfc6907.html
> Also, the same reason prompted the use of private address space in RFC
> 7115.
> Both are SIDR/SIDROPS RFCs.
>
> >  2) 2119 boilerplate missing
> >  3) An extra reference (nist-800-189)
>
> We can fix these two nits and upload a new version as soon as we get your
> OK about #1).
>
>
cool!


> Thank you.
>
> Sriram
>
> ------------------------------------------------------
> From: Christopher Morrow <[e-mail]> Fri, 22 April
> 2022 01:08 UTC
>
> As a note to the authors, could you please take care of these hanging
> chads at the next edit;
>   1) use of private address space instead of documentation space
>   2) 2119 boilerplate missing
>   3) An extra reference (nist-800-189)
>
> thanks!
>
>
> On Thu, Apr 21, 2022 at 1:02 PM Christopher Morrow <
> [e-mail]> wrote:
>
> > howdy folks! I've sent this forward to the IESG for publication.
> > (well, I didn't click 'go-go' yet, but shortly)
> >
> > -chris
> > co-chair-persona
>