Re: [Idr] draft-ietf-sidr-bgpsec-protocol-05 being WGLC'd in sidr

[Christopher Morrow <[e-mail]>]

On Fri, Sep 21, 2012 at 1:59 AM, Robert Raszuk <[e-mail]> wrote:
> Hi John,
>
> The proposal of dropping AS_PATH and the intention to completely replace it
> with AS_SEC_PATH attribute has been negatively commented so many times in
> the past both on idr and sidr that by bringing just one thread below seems
> like erasing all other comments.
>
> The issues are not only related to routing .. they are also related to
> number of BGP monitoring stations deployed today which use AS_PATH attribute
> for real time BGP analysis. Do you expect all of those tools to change/be
> updated when IETF will publish path validation RFC ?

only if they are going to participate in the bgpsec specific parts...
but then they'd already be set using just as_sec_path, right?

we had this discussion (we == sidr-wg and I think idr?) several times
already, essentially the as_sec_path only matters in the bubble that
is 'bgpsec'. outside that bubble as_path still remains, and is
re-manufactured as you cross the border by the exit-router at the
bubble edge.

The idea behind as_sec_path is really just a convenience of
implementations so we don't have to maintain 2 identical (mostly) data
structures in a device. Use as_path where you are not in the bubble,
convert to as_sec_path at the bubble ingress, convert back to as_path
at bubble exit.

I don't see why this is as much of an issue, particularly for any
monitoring code/station/system... if they don't do bgpsec, they just
see the same data as they do today. no changes are required,
operations continue, people stay happy... win?

-chris

> To only bring few past comments:
>
> http://www.ietf.org/mail-archive/web/sidr/current/msg04693.html
> http://www.ietf.org/mail-archive/web/sidr/current/msg04695.html
> http://www.ietf.org/mail-archive/web/sidr/current/msg04701.html
> http://www.ietf.org/mail-archive/web/sidr/current/msg04721.html
> http://www.ietf.org/mail-archive/web/sidr/current/msg04722.html
>
> Regards,
> R.
>
>
>> Folks,
>>
>> FYI draft-ietf-sidr-bgpsec-protocol-05 being WGLC'd in sidr. This
>> draft, assuming it progresses, represents a significant update to the
>> BGP protocol, notably in terms of AS_PATH handling. If you haven't
>> looked at it already, please consider taking the time to do so.
>>
>> Comments should go to both the [e-mail] and [e-mail] mailing
>> lists.
>>
>> There has already been some discussion of the draft on the sidr
>> mailing list. Archives are here
>> http://www.ietf.org/mail-archive/web/sidr/current/msg05062.html
>>
>> --John
>>
>> P.S.: If you intend to review it but need more time, please speak up,
>> and say how much more time you will need.
>>
>> Begin forwarded message:
>>
>>> From: "Murphy, Sandra" <[e-mail]> Subject: [sidr]
>>> WGLC for draft-ietf-sidr-bgpsec-protocol-05 Date: September 15,
>>> 2012 7:45:13 AM EDT To: "[e-mail]" <[e-mail]>
>>>
>>> This starts a working group last call for
>>> draft-ietf-sidr-bgpsec-protocol-05.  The draft is available at
>>> http://tools.ietf.org/html/draft-ietf-sidr-bgpsec-protocol-05 and
>>> https://datatracker.ietf.org/doc/draft-ietf-sidr-bgpsec-protocol/
>>>
>>> Please review this draft to see if you think it is ready for
>>> publication.  Send end comments to the list.
>>>
>>> The WGLC will end on 29 September 2012.
>>>
>>> --Sandy, speaking as wg co-chair
>>> _______________________________________________ sidr mailing list
>>> [e-mail] https://www.ietf.org/mailman/listinfo/sidr
>>
>>
>> _______________________________________________ Idr mailing list
>> [e-mail] https://www.ietf.org/mailman/listinfo/idr
>>
>>
>
> _______________________________________________
> Idr mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/idr