Re: Methods to label the passive interfaces within ISIS
Aijun Wang <[email protected]> Tue, 14 Jan 2020 06:36:52 +0800
| Newsgroups | gmane.ietf.isis |
|---|---|
| Message-ID | <DD58CAA4-EB8A-4008-A96C-ED1FFE2FD5A8__49020.2034635999$1578955153$gmane$org@tsinghua.org.cn> |
--===============6724585190556437435== Content-Type: multipart/alternative; boundary=Apple-Mail-4CE1D671-2847-4D3D-B822-CB75024F993F Content-Transfer-Encoding: 7bit --Apple-Mail-4CE1D671-2847-4D3D-B822-CB75024F993F Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, Acee, Les and Jeff: IGP is used to transfer the topology information within the domain, and the s= tub/passive interface is the important part of one network, especially for t= he inter-AS topology. Currently, we have not figured out other use cases to distinguish other inte= rfaces type. But for stub/passive interfaces, it will be useful to flooding s= uch information to other internal routers. OSPF has already the corresponding consideration and specifications, isn=E2=80= =99t it reasonable for ISIS to have such capabilities also? Aijun Wang China Telecom > On Jan 14, 2020, at 02:41, Jeff Tantsura <[email protected]> wrote: >=20 > =EF=BB=BF > Agree with Acee and Les >=20 > Cheers, > Jeff >> On Jan 13, 2020, 9:29 AM -0800, Les Ginsberg (ginsberg) <[email protected]= om>, wrote: >> I agree with Acee that there is no requirement to identify an interface a= s passive =E2=80=93 or (as suggested in this thread) as loopback or tunnel o= r stub=E2=80=A6 >>=20 >> =20 >>=20 >> Before debating the best encoding for information, it would be sensible t= o define the use case/requirements. >>=20 >> Simply having an advertisement that identifies an interface type isn=E2=80= =99t sufficient to do anything useful IMO. >>=20 >> =20 >>=20 >> Les >>=20 >> =20 >>=20 >> From: Acee Lindem (acee) <[email protected]> >> Sent: Monday, January 13, 2020 8:03 AM >> To: [email protected]; Aijun Wang <[email protected]> >> Cc: Les Ginsberg (ginsberg) <[email protected]>; Robert Raszuk <robert@r= aszuk.net>; [email protected] >> Subject: Re: [Lsr] Methods to label the passive interfaces within ISIS >>=20 >> =20 >>=20 >> Hi Aijun, >>=20 >> I guess the external use case for this is advertisement in BGP-LS for Net= work Management purposes?? There really isn=E2=80=99t IS-IS requirement to k= now whether or not an interface is a passive interface. >>=20 >> Thanks, >>=20 >> Acee >>=20 >> =20 >>=20 >> From: Lsr <[email protected]> on behalf of Tony Li <[email protected]> >> Date: Monday, January 13, 2020 at 11:00 AM >> To: Aijun Wang <[email protected]> >> Cc: "Les Ginsberg (ginsberg)" <[email protected]>, Robert Raszuk <robert= @raszuk.net>, "[email protected]" <[email protected]> >> Subject: Re: [Lsr] Methods to label the passive interfaces within ISIS >>=20 >> =20 >>=20 >> =20 >>=20 >> Hi Anjun, >>=20 >> =20 >>=20 >> =20 >>=20 >> Is it reasonable to put the link attribute information into the =E2=80=9C= IP Reachability TLV=E2=80=9D? >>=20 >> IMHO, such stub link is not the normal links within IGP domain. Label th= e related prefix is coming from the passive/stub link seems also acceptable?= >>=20 >> =20 >>=20 >> =20 >>=20 >> Well, a passive interface is really configured so that you advertise the i= nterface=E2=80=99s prefix. Attaching the data that you want to the associat= ed data seems reasonable to me. >>=20 >> =20 >>=20 >> There=E2=80=99s no good IS Neighbor advertisement to attach the sub-TLV t= o because there is no neighbor. >>=20 >> =20 >>=20 >> Tony >>=20 >> =20 >>=20 >> =20 >>=20 >> _______________________________________________ >> Lsr mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/lsr --Apple-Mail-4CE1D671-2847-4D3D-B822-CB75024F993F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D= utf-8"></head><body dir=3D"auto">Hi, Acee, Les and Jeff:<div>IGP is used to t= ransfer the topology information within the domain, and the stub/passive int= erface is the important part of one network, especially for the inter-AS top= ology.</div><div>Currently, we have not figured out other use cases to disti= nguish other interfaces type. But for stub/passive interfaces, it will be us= eful to flooding such information to other internal routers.</div><div>OSPF h= as already the corresponding consideration and specifications, isn=E2=80=99t= it reasonable for ISIS to have such capabilities also?</div><div><br><br><d= iv dir=3D"ltr">Aijun Wang<div>China Telecom</div></div><div dir=3D"ltr"><br>= <blockquote type=3D"cite">On Jan 14, 2020, at 02:41, Jeff Tantsura <jefft= [email protected]> wrote:<br><br></blockquote></div><blockquote type=3D"= cite"><div dir=3D"ltr">=EF=BB=BF <title></title> <div name=3D"messageBodySection"> <div dir=3D"auto">Agree with Acee and Les</div> </div> <div name=3D"messageSignatureSection"><br> <div class=3D"matchFont">Cheers, <div>Jeff</div> </div> </div> <div name=3D"messageReplySection">On Jan 13, 2020, 9:29 AM -0800, Les Ginsbe= rg (ginsberg) <[email protected]>, wrote:<br> <blockquote type=3D"cite" class=3D"spark_quote" style=3D"margin: 5px 5px; pa= dding-left: 10px; border-left: thin solid #1abc9c;"> <div class=3D"WordSection1"> <p class=3D"MsoNormal">I agree with Acee that there is no requirement to ide= ntify an interface as passive =E2=80=93 or (as suggested in this thread) as l= oopback or tunnel or stub=E2=80=A6</p> <p class=3D"MsoNormal"> </p> <p class=3D"MsoNormal">Before debating the best encoding for information, it= would be sensible to define the use case/requirements.</p> <p class=3D"MsoNormal">Simply having an advertisement that identifies an int= erface type isn=E2=80=99t sufficient to do anything useful IMO.</p> <p class=3D"MsoNormal"> </p> <p class=3D"MsoNormal"> Les</p> <p class=3D"MsoNormal"></p> <p class=3D"MsoNormal"> </p> <div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4= ..0pt"> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0= in 0in"> <p class=3D"MsoNormal"><b>From:</b> Acee Lindem (acee) <[email protected]>= ;<br> <b>Sent:</b> Monday, January 13, 2020 8:03 AM<br> <b>To:</b> [email protected]; Aijun Wang <[email protected]><br>= <b>Cc:</b> Les Ginsberg (ginsberg) <[email protected]>; Robert Raszuk= <[email protected]>; [email protected]<br> <b>Subject:</b> Re: [Lsr] Methods to label the passive interfaces within ISI= S</p> </div> </div> <p class=3D"MsoNormal"> </p> <p class=3D"MsoNormal">Hi Aijun,</p> <p class=3D"MsoNormal">I guess the external use case for this is advertiseme= nt in BGP-LS for Network Management purposes?? There really isn=E2=80=99t IS= -IS requirement to know whether or not an interface is a passive interface.<= /p> <p class=3D"MsoNormal">Thanks,</p> <p class=3D"MsoNormal">Acee</p> <p class=3D"MsoNormal"> </p> <div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0= in 0in"> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><b><span style=3D"font-siz= e:12.0pt;color:black">From:</span></b> <span style=3D"font-size:12.0pt;color= :black">Lsr <<a href=3D"mailto:[email protected]">[email protected]= </a>> on behalf of Tony Li <<a href=3D"mailto:[email protected]">tony.li= @tony.li</a>><br> <b>Date:</b> Monday, January 13, 2020 at 11:00 AM<br> <b>To:</b> Aijun Wang <<a href=3D"mailto:[email protected]">wanga= [email protected]</a>><br> <b>Cc:</b> "Les Ginsberg (ginsberg)" <<a href=3D"mailto:[email protected]= m">[email protected]</a>>, Robert Raszuk <<a href=3D"mailto:robert@ra= szuk.net">[email protected]</a>>, "<a href=3D"mailto:[email protected]">lsr@ie= tf.org</a>" <<a href=3D"mailto:[email protected]">[email protected]</a>><br> <b>Subject:</b> Re: [Lsr] Methods to label the passive interfaces within ISI= S</span></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> </p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> </p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">Hi Anjun,</p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> </p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;marg= in-bottom:12.0pt;margin-left:.5in"> </p> <blockquote style=3D"margin: 5px 5px; padding-left: 10px; border-left: thin s= olid #e67e22;" class=3D"spark_quote"> <div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1= 0.5pt;color:#1F497D">Is it reasonable to put the link attribute information i= nto the =E2=80=9CIP Reachability TLV=E2=80=9D?</span><span style=3D"font-siz= e:12.0pt;font-family:SimSun"></span></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1= 0.5pt;color:#1F497D">IMHO, such stub link is not the normal links within IGP= domain. Label the related prefix is coming from the passive/stub link= seems also acceptable?</span><span style=3D"font-size:12.0pt;font-family:Si= mSun"></span></p> </div> </div> </blockquote> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> </p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> </p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">Well, a passive interface i= s really configured so that you advertise the interface=E2=80=99s prefix. &n= bsp;Attaching the data that you want to the associated data seems reasonable= to me.</p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> </p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">There=E2=80=99s no good IS= Neighbor advertisement to attach the sub-TLV to because there is no neighbo= r.</p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> </p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">Tony</p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> </p> </div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;marg= in-bottom:12.0pt;margin-left:.5in"> </p> </div> </div> _______________________________________________<br> Lsr mailing list<br> [email protected]<br> https://www.ietf.org/mailman/listinfo/lsr<br></blockquote> </div> </div></blockquote></div></body></html>= --Apple-Mail-4CE1D671-2847-4D3D-B822-CB75024F993F-- --===============6724585190556437435== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr --===============6724585190556437435==--