Re: [sidr] Stephen Farrell's Discuss on draft-ietf-sidr-bgpsec-protocol-21: (with DISCUSS and COMMENT)

2017-01-09 Thread Randy Bush
i had to do some ascii porn for rob to deal with a secdir reviewer for draft-ietf-sidr-publication. it may help here. i added the routers for this discussion. +--++--++--+ | CA || CA || CA | +--++--++--+ |

Re: [sidr] Review of draft-ietf-sidr-adverse-actions-03

2017-01-09 Thread Steve KENT
Dan, Thanks for the review. Adverse actions include cases where the CA or repository manager is not attacked or did not make an error, as noted in the Introduction: Note that the CA that allocated the affected INRs may be acting in accordance with established policy, and thus the change may

Re: [sidr] AD Review of draft-ietf-sidr-delta-protocol-04

2017-01-09 Thread Alvaro Retana (aretana)
Tim: Congratulations! ☺ I think we’re in sync with everything else, just this last piece is outstanding. Thanks! Alvaro. On 1/9/17, 6:55 AM, "Tim Bruijnzeels" > wrote: Let me try to make the point again – I didn’t do a good job above. In fact,

Re: [sidr] AD Review of draft-ietf-sidr-delta-protocol-04

2017-01-09 Thread Tim Bruijnzeels
Hi Alvaro, in-line > On 07 Jan 2017, at 00:04, Alvaro Retana (aretana) wrote: > > On 12/28/16, 11:43 AM, "Tim Bruijnzeels" > wrote: > > Tim: > > Happy New Year!! Thank you, you (all) too!! > > > | Thank you for your in-depth

[sidr] Review of draft-ietf-sidr-adverse-actions-03

2017-01-09 Thread Dan Romascanu
Reviewer: Dan Romascanu Review result: Ready with Nits 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 treat these comments just like any other last call comments. For