Re: [Idr] 2 week adoption call for - draft-sriram-idr-route-leak-detection-mitigation-00 (6/25 to 7/9/2015)

[Jeffrey Haas <[e-mail]>]

On Thu, Jun 25, 2015 at 01:45:20PM -0400, Susan Hares wrote:
> This begins a 2 week adoption call for  
> 
> draft-sriram-idr-route-leak-detection-mitigation-00

I support adoption of this draft.

> This is an informational draft regarding route-leak mitigation.  For this WG
> adoption call please include in your response: 
> 
>  
> 
> a)      Who will desire to read this informational draft now and in 1 year
> from now>? 

I find it likely that the document will have an extended lifetime in IDR and
SIDR as the mechanism is refined and implemented.

> b)      Is this informational draft's description of route-leak types and
> mitigated by the origin validation [RFC 6811] and BGPSEC path validation  
> 
>           [draft-ietf-sidr-bgpsec-protocol] are correct? 

Better than most.

> c)       It is necessary to solve the route-leak problems not covered by
> origin validation and BGPSEC path validation? 

Yes.

> d)      Do you think the solution suggested for the extension of BGPSEC will
> fix these unsolved route-leak problems?

I believe so, but require more time to re-read the bgpsec protocol and think
about it.

-- Jeff