On 29/04/2010, at 4:46 AM, Sandra Murphy wrote:

> 
> 
> On Wed, 28 Apr 2010, Sandra Murphy wrote:
> 
>> 
>> 
>> On Thu, 29 Apr 2010, Geoff Huston wrote:
>> 
>>> Thank you for this response. As I had noted earlier, if you had made it 
>>> clearer in which role you were posting in these discussions it would be 
>>> easier for others, or at least myself, to understand when you were making 
>>> pronouncements as WG chair and when you were asking questions and airing 
>>> opinions as an individual participant.
>>> If proxy aggregation is "not part of our work" then the outcome of such 
>>> actions, namely AS Sets in the AS_PATH is likewise "not part of our work." 
>>> I will edit the roa validation draft accordingly.
>> 
>> Actually, no, that is not the case.
>> 
>> When I say that proxy aggregation is not part of our work, I mean that sidr 
>> does not promise to protect BGP announcements formed by proxy aggregation.
>> 
>> While it is true that AS_SETS are principally generated in BGP updates by an 
>> AS that is doing proxy aggregation, AS_SETS are still part of the BGP 
>> protocol and might appear in a received AS_PATH.
>> 
>> Until and unless the idr working group decides to eliminate that feature 
>> from the BGP protocol, the sidr route validation must still make a statement 
>> about what happens when the AS_PATH origin is an AS_SET.
>> 
>> That is necessary for completeness.  Furthermore, without such a statement, 
>> implementers could make different decisions as to how to handle such cases 
>> and attack paths could result.
>> 
>> The sidr wg is not now considering anything but origin authorization, so an 
>> AS_PATH segment that is an AS_SET but is not the origin is not of our 
>> concern at all.
>> 
>> 
>> --Sandy
> 
> 
> Whoops!
> 
> I meant:
> 
> --Sandy, still conversing as wg chair
> 

thank you.

So I'm confused with this additional statement of yours in the role of WG chair.

To explain my confusion, when I grep AS_SET in RFC4271 I see it exclusively 
described with reference to aggregation  - for example: "AS_SETs are used in 
the route aggregation algorithm described in Section 9.2.2.2" 

So __with particular reference to the definition of an originating AS__ (which 
is where this particular particular strand started), where and why do AS_SETs 
have any relevance to the WG consideration of Origination Authorization? i.e. 
to phrase it in a more practical manner, what  precisely is the problem with 
applying the edit proposed by John Scudder to the roa validation draft? 

Again, I'm asking the WG chairs here for further clarification because the 
above exchange has managed to confused me.

 Geoff

_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to