On Thu, Jul 29, 2010 at 5:41 AM, Sriram, Kotikalapudi <[email protected]> wrote: > Thanks, Jeff. > One more clarification request: > What do you mean when you say "first non-sequence AS"? > Example: > AS path : ASN3 ASN2 ASN1 [ASN25, ASN26] AGGREGATOR: AS1 > Here [ASN25, ASN26] is the AS_SET.
<asking dumb question> so, a the mic I thought Jeff also said that ASN25, ASN26 was explicitly unordered in the spec. If this is the case than the check for the first in the sequence isn't reliable/repeatable. </asking dumb question> -chris <regular-joe-hat> > I this example, what is the first non-sequence AS? > You may use a different example if needed. > > Sriram > ________________________________________ > From: Jeffrey Haas [[email protected]] > Sent: Thursday, July 29, 2010 5:19 AM > To: Sriram, Kotikalapudi > Cc: Randy Bush; Jeffrey Haas; [email protected] > Subject: Re: [sidr] Comment about aggregators and AS_SETs > > Sriram, > > On Thu, Jul 29, 2010 at 04:14:46AM -0400, Sriram, Kotikalapudi wrote: >> We need not look inside the AS_SET, and also we would require no ROAs for >> the AS_SET. >> Simply take the AS to the immediate left of the AS_SET to be the origin. >> The update/RIB data establish clearly that the ASN in that AS position indeed >> matches the AGGREGATOR ASN (wherever it matters for the validation >> algorithm). >> However, the algorithm should not take the AGGREGATOR to be the origin > > Part of my suggestion is that the first non-sequence AS should only be used > *if and only if* the aggregator AS matches. > > This would be in addition to only considering the AS left of an AS_SET when > there are no sequences as the right-most segment type. > > -- Jeff > _______________________________________________ > sidr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/sidr > _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
