On Thu, 29 Apr 2010, Geoff Huston wrote:


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"

Section 9.2 is describing the "Update-Send Process."

My statements about the AS_SET concern what happens in the Update receipt process, when the route validation is performed.


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?

The algorithm in 9.2.2.2 that is referenced above can result in an AS_SET as the first segment in an AS_PATH. Also, RFC4271 has plenty of references to AS_SETs occurring as the first segment in an AS_PATH (i.e., the originating AS). So an originating AS of type AS_SET is a legal part of BGP and will not be rejected by current implementations.

An originating AS in the AS_PATH of type AS_SET is therefore part of our work because it will occur in inputs that the route validation must judge.

I as wg chair am correcting your statement 'the outcome of such actions, namely AS Sets in the AS_PATH is likewise "not part of our work."'

When you say "what precisely is the problem with applying the edit proposed by John Scudder to the roa validation draft?", I presume that you are referring to John's message of 3 Apr, in which he says:


  Granted this is a corner case, but nonetheless I can't see what the
  reason would be for considering an intermediate AS (albeit the first one
  contained in an AS_SEQUENCE) to be the origin.  I suggest revising as
  follows: Consider the origin AS to be the contents of the AS_SET if it's
  a singleton set.  Otherwise the origin cannot be determined.

  Given that it's a corner case, you could also cut right to the chase and
  just call it undetermined if the path starts (or ends, in your parlance)
  with an AS_SET, period.

I am not saying that there is anything wrong with John's edit.

I am not judging consensus that this would be the best way of dealing with an originating AS of type AS_SET.

I am saying that we must have SOME rule of what happens when validating a route that contains an originating AS of type AS_SET, for document and implementation completeness.

--Sandy, as wg chair


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