« Return to Thread: BGPSEC proposal to drop AS_PATH [was: Fwd: [sidr] request for agenda items for interim meeting 6 Jun]

Re: [sidr] BGPSEC proposal to drop AS_PATH [was: Fwd: request for agenda items for interim meeting 6 Jun]

by Jakob Heitz-3 :: Rate this Message:

| View in Thread

On Tuesday, May 29, 2012 5:29 PM, Randy Bush <mailto:randy@...> wrote:

>> AS_PATH is used to specify the path that the payload takes.
>
> really?  i thought it was a routing loop detection mechanism.
> it's been a while since folk wrote research papers describing
> schemes for routing by AS.
>
> i would phrase it as
>
> AS_PATH specifies the ASs through which the routing announcement has
> passed.
>
>> Signed_AS_PATH is to verify the path that the update message takes.
>
> and then this works really nicely.
>
>> There is no reason they can not be different.
>
> and here i thought that detecting that they differ, as an attack, is
> the core goal of as-path validation.

I thought it was to prevent an AS from
announcing an update that it was not authorised  to.

An entirely different thing.

>
> randy

--
Jakob Heitz.
_______________________________________________
Idr mailing list
Idr@...
https://www.ietf.org/mailman/listinfo/idr

 « Return to Thread: BGPSEC proposal to drop AS_PATH [was: Fwd: [sidr] request for agenda items for interim meeting 6 Jun]