Hi Sean,

Thank you for your careful review.


On 11/02/11 11:31 AM, "Sean Turner" <[email protected]> wrote:

> Lots of hats in this WG... With my nit-noid checker hat on ;)
> 
> - Should this be a BCP or standards track?

To me this sits in BCP space, it really describes the best action IANA
should follow for dealing with issuing RPKI objects for the unallocated,
reserved, and special use blocks. It doesn't define or redefine any existing
RPKI structures.

> 
> - Expand RPKI in abstract and introduction
> 
> - Sec 2: r/description od/description of
> 
> - Sec 3: r/, [I-D.ietf-sidr-rpki-manifests]./
>             , and [I-D.ietf-sidr-rpki-manifests].

Thanks, Will fix.

> 
> - Add informative references to IPv4 [RFC793] and IPv6 [RFC2460] either
> in Section 2 or 4.
> 
> [RFC791] Postel, J. (ed.), "Internet Protocol - DARPA Internet
>           Program Protocol Specification", RFC 791, September 1981.
> 
> [RFC2460] Deering, S., and R. Hinden, "Internet Protocol, Version
>            6 (IPv6) Specification," RFC 2460, December 1998.

Thanks, will add.

> 
> - It might be worth noting why this draft uses non-RFC 3849/5735/5771
> compliant addresses.  It'll stop somebody who uses the nit checker from
> asking the question and possibly slowing down publication (think genart,
> secdir, or IESG member).  From the nit checker:
> 
>   == There are 2 instances of lines with non-RFC5735-compliant IPv4
>      addresses in the document.  If these are example addresses, they
>      should be changed.
> 
>   == There are 4 instances of lines with multicast IPv4 addresses in the
>      document.  If these are generic example addresses, they should be
>      changed to use the 233.252.0.x range defined in RFC 5771
> 
>   == There are 1 instance of lines with non-RFC3849-compliant IPv6
>      addresses in the document.  If these are example addresses, they
>      should be changed.

None of the addresses are example addresses. They are specific to the
resources and the expected RPKI objects in question.

> 
> - Sec 5: Missing some periods:
>           r/[RFC5735]/[RFC5735].
>           r/routed/routed.
>           r/[RFC3068]/[RFC3068].

Thanks. Will fix.

> 
> - Sec 5: r/IANA should/IANA SHOULD
> 
> - Sec 6/7/8: Should "IANA MUST refrain" be "IANA MUST NOT"?
> 
> - Sec 7: r/[RFC5180]/[RFC5180].

Thanks. Will fix.

> 
> - Sec 10: If IANA is going to stand up the CA it's going to need to
> write the CPS that says how it does all the things the CP says it needs to.

Correct. Although my take on that is it's an acquired effort of running the
RPKI Unallocated/reserved/special-use CA and need not be specified here. I
also didn't see the need to refer to one of the CPS templates.

Is my thinking misaligned here?

Apart from the last open item, would you be ok if I made the changes prior
to IESG submission instead of cutting another revision.

Cheers
Terry

> 
> spt
> 
> On 2/10/11 6:30 PM, Terry Manderson wrote:
>> with author hat stylishly tilted to one side.
>> 
>> The doc can be found at:
>> 
>> http://tools.ietf.org/html/draft-ietf-sidr-iana-objects-00
>> 
>> Cheers
>> Terry
>> 
>> 
>> On 10/02/11 10:38 AM, "Christopher Morrow"<[email protected]>
>> wrote:
>> 
>>> <wg-co-chair-airplane-seat == on>
>>> Since no one else spoke up, let's make this quick:
>>> 
>>> WGLC, to end Feb 11 2011 23:59 UTC
>>> 
>>> please make your feelings known quickly, this seems like a
>>> non-controversial document, so quick reaction/turn-around would be
>>> helpful.
>>> 
>>> -Chris
>>> </wg-co-chair-airplane-seat == off>
>> 
>> _______________________________________________
>> sidr mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/sidr
>> 

_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to