Re: [sidr] Fwd: I-D Action: draft-ietf-sidr-pfx-validate-02.txt

Hi Pradosh, 

I read the document and I think it is in great shape. I found some nits and have some comments.

Roque

General Comment:
  " Depending on the lookup result, we define a property for each route,
   called the "validity state".  It can assume the values "valid", "not
   found", or "invalid"."

You may want to consider calling it "Origin AS validity state" to distinguish it from the validity state in BGPSEC ("valid" and "invalid").

Section 1:
p2: s/verifyable/verifiable

Section 2:
   "An AS can originate more than one
   prefix set.  Thus, multiple prefix sets in the database can contain
   the same origin AS(es)."

I believe you also need to mention that in the table there may be "multi-origin prefixes". Geoff report identifies 2400 but you may find more in local/regional environments (http://bgp.potaroo.net/as6447/report.txt).

Section 5:
p5: 
I believe you should reference draft-ietf-sidr-origin-validation-signaling-00

Security Consideration:
I think you need to consider what you already mentioned in section 4, if the connectivity to the local-caches is lost, invalid routes will be classified as "not-found", which could have a different set of local policies.

> 
> 
> 
> n Jul 11, 2011, at 7:24 PM, Pradosh Mohapatra wrote:
> 
>> FYI... This version addresses comments from Geoff (put a reference to ietf-sidr-origin-ops + some word-smithing). Would appreciate another review.
>> 
>> - Pradosh
>> 
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-sidr-pfx-validate-02.txt
>> 
>> 
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
> 

Re: [sidr] Fwd: I-D Action: draft-ietf-sidr-pfx-validate-02.txt

Attachment: smime.p7s