Jeff, >> Is such non-standard use objectionable or unadvisable? >Objectionable and unadvisable both.
Thank you. All of your observations very helpful. Yes, it is understood... we must remove the use of 'Segment' to refer to individual ASes in an AS_SEQUENCE. >Within a segment, if it's of type sequence, you can generally talk about an AS >element in an indexed fashion. Yes, good. That is what we will plan to do in the algorithm. >Since there's work to simply make "sets go away" (which I owe you text for), >there are two choices: >1. Make the text correct for as-sets, which will complicate the algorithm (but >perhaps not significantly) >2. Preclude sets as valid matches for aspa purposes and keep the simpler fully >indexed solution. The algorithm currently does #1 (relying on non-standard use of 'Segment'). But we have a way to do #1 even by simply indexing the ASes in the AS_SEQUENCEs. We can accommodate AS_SET at the beginning of the AS_PATH. We will accommodate it. What about AS_SET in the middle is my next question. Please see my other post with the subject: 'Any credence to AS_SET in the *middle* between AS_SEQUENCEs?' >ASPA verification doesn't try to operate on confederation segment types... We are thinking we'll add the following statement in the draft about Confederations: The ASes on the boundary of an AS Confederation MUST register ASPAs using the Confederation’s global ASN and the procedures for ASPA-based AS path validation in this document are NOT RECOMMENDED for use on eBGP links internal to the Confederation. Sriram _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
