How is AS path length calculated? Issue#35
Mahesh Jethanandani <[email protected]> Tue, 10 Dec 2019 15:03:13 -0800
| Newsgroups | gmane.ietf.idr |
|---|---|
| Message-ID | <[email protected]> |
--===============1748328163990477286== Content-Type: multipart/alternative; boundary="Apple-Mail=_1389F78C-BDA4-46B1-96E3-4109BF001BF7" --Apple-Mail=_1389F78C-BDA4-46B1-96E3-4109BF001BF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii This, and series of follow-up e-mail, one each for issues discussed in = IETF 106, will summarize the issues discussed there, w.r.t. to the BGP = YANG model for Service Provider Network = <https://tools.ietf.org/html/draft-ietf-idr-bgp-model-07>. I will also = suggest a solution. Unless an objection is heard, the suggested solution = will be deemed appropriate to implement in the YANG model. The issue is = also documented here = <https://github.com/mjethanandani/ietf-bgp-yang/issues/35>, in case you = want to comment it there. On the question of how is AS path length calculated, we proposed that = calculated AS_PATH length for route SHALL follow RFC 4271 rules. It will = let the user see the number that serves as input to BGP route selection.=20= Unless an objection is received, that is what will be documented in the = model. Thanks. Mahesh Jethanandani [email protected] --Apple-Mail=_1389F78C-BDA4-46B1-96E3-4109BF001BF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">This,= and series of follow-up e-mail, one each for issues discussed in IETF = 106, will summarize the issues discussed there, w.r.t. to the <a = href=3D"https://tools.ietf.org/html/draft-ietf-idr-bgp-model-07" = class=3D"">BGP YANG model for Service Provider Network</a>. I will also = suggest a solution. Unless an objection is heard, the suggested solution = will be deemed appropriate to implement in the YANG model. The issue is = also documented <a = href=3D"https://github.com/mjethanandani/ietf-bgp-yang/issues/35" = class=3D"">here</a>, in case you want to comment it there.<div = class=3D""><br class=3D""></div><div class=3D"">On the question of how = is AS path length calculated, we proposed that calculated AS_PATH length = for route SHALL follow RFC 4271 rules. It will let the user see the = number that serves as input to BGP route selection. </div><div = class=3D""><br class=3D""></div><div class=3D"">Unless an objection is = received, that is what will be documented in the model.</div><div = class=3D""><br class=3D""></div><div class=3D"">Thanks.<br class=3D""><div= class=3D""><br class=3D""><div class=3D""> <div class=3D"">Mahesh Jethanandani</div><div class=3D""><a = href=3D"mailto:[email protected]" = class=3D"">[email protected]</a></div><div class=3D""><br = class=3D""></div><br class=3D"Apple-interchange-newline"> </div> <br class=3D""></div></div></body></html>= --Apple-Mail=_1389F78C-BDA4-46B1-96E3-4109BF001BF7-- --===============1748328163990477286== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list [email protected] https://www.ietf.org/mailman/listinfo/idr --===============1748328163990477286==--