Re: Methods to label the passive interfaces within ISIS
Aijun Wang <[email protected]> Tue, 14 Jan 2020 07:34:46 +0800
| Newsgroups | gmane.ietf.isis |
|---|---|
| Message-ID | <71D49830-B207-403E-BAF2-B74A7D4E03EC__2121.03539831645$1578958701$gmane$org@tsinghua.org.cn> |
--===============1156108998154052473== Content-Type: multipart/alternative; boundary=Apple-Mail-E12C2098-FB83-415B-8BC9-A551BB0C0C3A Content-Transfer-Encoding: 7bit --Apple-Mail-E12C2098-FB83-415B-8BC9-A551BB0C0C3A Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, Acee: Actually, currently it arises from the inter-AS topology management needs. I= t is not sufficient for BGP-LS to report only the interior connections infor= mation. To report the edge connection information, the router within the IGP domain t= hat run BGP-LS needs first to distinguish the stub link from the normal link= .. There maybe exists other usages for this information, we will add them if we= get it. Also welcome more examples/solutions from interested LSR experts. Aijun Wang China Telecom > On Jan 14, 2020, at 07:06, Acee Lindem (acee) <[email protected]> wrote: >=20 > =EF=BB=BF > Hi Aijun, > =20 > From: Aijun Wang <[email protected]> > Date: Monday, January 13, 2020 at 5:48 PM > To: Acee Lindem <[email protected]> > Cc: Jeff Tantsura <[email protected]>, "Les Ginsberg (ginsberg)" <gi= [email protected]>, Tony Li <[email protected]>, Robert Raszuk <[email protected]= et>, "[email protected]" <[email protected]> > Subject: Re: [Lsr] Methods to label the passive interfaces within ISIS > =20 > Hi, Acee: > As Tony suggested also before, we can change the description for =E2=80=9C= passive=E2=80=9D to =E2=80=9Cstub=E2=80=9D later. > Is that more acceptable then? > =20 > Yes =E2=80=93 but I=E2=80=99d still like to know why this is needed. > =20 > Thanks, > Acee > =20 >=20 > Aijun Wang > China Telecom >=20 >=20 > On Jan 14, 2020, at 06:40, Acee Lindem (acee) <[email protected]> wrote: >=20 > Hi Aijun, > =20 > From: Aijun Wang <[email protected]> > Date: Monday, January 13, 2020 at 5:37 PM > To: Jeff Tantsura <[email protected]> > Cc: Acee Lindem <[email protected]>, Tony Li <[email protected]>, "Les Ginsberg= (ginsberg)" <[email protected]>, "[email protected]" <[email protected]>, Robert Ras= zuk <[email protected]> > Subject: Re: [Lsr] Methods to label the passive interfaces within ISIS > =20 > Hi, Acee, Les and Jeff: > IGP is used to transfer the topology information within the domain, and th= e stub/passive interface is the important part of one network, especially fo= r the inter-AS topology. > Currently, we have not figured out other use cases to distinguish other in= terfaces type. But for stub/passive interfaces, it will be useful to floodin= g such information to other internal routers. > =20 > A stub interface is not necessarily a passive interace. > =20 > OSPF has already the corresponding consideration and specifications, isn=E2= =80=99t it reasonable for ISIS to have such capabilities also? > =20 > OSPF doesn=E2=80=99t advertise that an interface is a passive interface. O= thers routing can=E2=80=99t distinguish a passive interface from any other s= tub link. > =20 > Thanks, > Acee > =20 >=20 > Aijun Wang > China Telecom >=20 >=20 >=20 > On Jan 14, 2020, at 02:41, Jeff Tantsura <[email protected]> wrote: >=20 > Agree with Acee and Les > =20 > Cheers, > Jeff > On Jan 13, 2020, 9:29 AM -0800, Les Ginsberg (ginsberg) <[email protected]= m>, wrote: >=20 >=20 > I agree with Acee that there is no requirement to identify an interface as= passive =E2=80=93 or (as suggested in this thread) as loopback or tunnel or= stub=E2=80=A6 > =20 > Before debating the best encoding for information, it would be sensible to= define the use case/requirements. > Simply having an advertisement that identifies an interface type isn=E2=80= =99t sufficient to do anything useful IMO. > =20 > Les > =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@ra= szuk.net>; [email protected] > Subject: Re: [Lsr] Methods to label the passive interfaces within ISIS > =20 > Hi Aijun, > I guess the external use case for this is advertisement in BGP-LS for Netw= ork Management purposes?? There really isn=E2=80=99t IS-IS requirement to kn= ow whether or not an interface is a passive interface. > Thanks, > Acee > =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 > Hi Anjun, > =20 > =20 >=20 > Is it reasonable to put the link attribute information into the =E2=80=9CI= P Reachability TLV=E2=80=9D? > 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? > =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 > There=E2=80=99s no good IS Neighbor advertisement to attach the sub-TLV to= because there is no neighbor. > =20 > Tony > =20 > =20 >=20 > _______________________________________________ > Lsr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lsr > _______________________________________________ > Lsr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lsr --Apple-Mail-E12C2098-FB83-415B-8BC9-A551BB0C0C3A 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:<div>Actually, currently it arises= from the inter-AS topology management needs. It is not sufficient for BGP-L= S to report only the interior connections information.</div><div>To report t= he edge connection information, the router within the IGP domain that run BG= P-LS needs first to distinguish the stub link from the normal link.</div><di= v>There maybe exists other usages for this information, we will add them if w= e get it. Also welcome more examples/solutions from interested LSR experts.<= /div><div><br><br><div dir=3D"ltr">Aijun Wang<div>China Telecom</div></div><= div dir=3D"ltr"><br><blockquote type=3D"cite">On Jan 14, 2020, at 07:06, Ace= e Lindem (acee) <[email protected]> wrote:<br><br></blockquote></div><blo= ckquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"> <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} span.EmailStyle19 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} ..MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style> <div class=3D"WordSection1"> <p class=3D"MsoNormal">Hi Aijun, <o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></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">Aijun Wang <wanga= [email protected]><br> <b>Date: </b>Monday, January 13, 2020 at 5:48 PM<br> <b>To: </b>Acee Lindem <[email protected]><br> <b>Cc: </b>Jeff Tantsura <[email protected]>, "Les Ginsberg (gin= sberg)" <[email protected]>, Tony Li <[email protected]>, Robert R= aszuk <[email protected]>, "[email protected]" <[email protected]><br> <b>Subject: </b>Re: [Lsr] Methods to label the passive interfaces within ISI= S<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><o:p> </o:p></p> </div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">Hi, Acee: <o:p></o:p></p> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">As Tony suggested also bef= ore, we can change the description for =E2=80=9Cpassive=E2=80=9D to =E2=80=9C= stub=E2=80=9D later.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">Is that more acceptable th= en?<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Yes =E2=80=93 but I=E2=80=99d still like to know why t= his is needed. <o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Thanks,<o:p></o:p></p> <p class=3D"MsoNormal">Acee<o:p></o:p></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"> <o:p> </o:p></p> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">Aijun Wang <o:p></o:p></p>= <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">China Telecom<o:p></o:p></= p> </div> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;marg= in-bottom:12.0pt;margin-left:.5in"> On Jan 14, 2020, at 06:40, Acee Lindem (acee) <[email protected]> wrote:<= o:p></o:p></p> </blockquote> </div> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">Hi Aijun, <o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> <o:p></o:p></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:1.0in"><b><span style=3D"font-si= ze:12.0pt;color:black">From: </span></b><span style=3D"font-size:12.0pt;color:black">Aijun Wang <wanga= [email protected]><br> <b>Date: </b>Monday, January 13, 2020 at 5:37 PM<br> <b>To: </b>Jeff Tantsura <[email protected]><br> <b>Cc: </b>Acee Lindem <[email protected]>, Tony Li <[email protected]&g= t;, "Les Ginsberg (ginsberg)" <[email protected]>, "[email protected]" <= ;[email protected]>, Robert Raszuk <[email protected]><br> <b>Subject: </b>Re: [Lsr] Methods to label the passive interfaces within ISI= S</span><o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in"> <o:p></o:p></p> </div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">Hi, Acee, Les and Jeff: <= o:p></o:p></p> <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">IGP is used to transfer t= he topology information within the domain, and the stub/passive interface is= the important part of one network, especially for the inter-AS topology.<o:= p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">Currently, we have not fi= gured out other use cases to distinguish other interfaces type. But for stub= /passive interfaces, it will be useful to flooding such information to other= internal routers.<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> <o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in">A stub interface is not ne= cessarily a passive interace.<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">OSPF has already the corr= esponding consideration and specifications, isn=E2=80=99t it reasonable for I= SIS to have such capabilities also?<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> <o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in">OSPF doesn=E2=80=99t adver= tise that an interface is a passive interface. Others routing can=E2=80=99t d= istinguish a passive interface from any other stub link.<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"> <o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in">Thanks,<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in">Acee<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;marg= in-bottom:12.0pt;margin-left:1.0in"> <o:p></o:p></p> <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">Aijun Wang <o:p></o:p></p= > <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">China Telecom<o:p></o:p><= /p> </div> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in"><br> <br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;marg= in-bottom:12.0pt;margin-left:1.0in"> On Jan 14, 2020, at 02:41, Jeff Tantsura <[email protected]> wro= te:<o:p></o:p></p> </blockquote> </div> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <div name=3D"messageBodySection"> <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">Agree with Acee and Les<o= :p></o:p></p> </div> </div> <div name=3D"messageSignatureSection"> <p class=3D"MsoNormal" style=3D"margin-left:1.0in"> <o:p></o:p></p> <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">Cheers, <o:p></o:p></p> <div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">Jeff<o:p></o:p></p> </div> </div> </div> <div name=3D"messageReplySection"> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">On Jan 13, 2020, 9:29 AM -= 0800, Les Ginsberg (ginsberg) <[email protected]>, wrote:<br> <br> <br> <o:p></o:p></p> <blockquote style=3D"border:none;border-left:solid #1ABC9C 1.0pt;padding:0in= 0in 0in 8.0pt;margin-left:3.75pt;margin-top:3.75pt;margin-right:3.75pt;marg= in-bottom:3.75pt"> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> I agree with Acee that there is no requirement to identify an interface as p= assive =E2=80=93 or (as suggested in this thread) as loopback or tunnel or s= tub=E2=80=A6<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> <o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> Before debating the best encoding for information, it would be sensible to d= efine the use case/requirements.<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> Simply having an advertisement that identifies an interface type isn=E2=80=99= t sufficient to do anything useful IMO.<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> <o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> Les<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> <o:p></o:p></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" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> <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<o:p></o:p></p> </div> </div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> <o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> Hi Aijun,<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> I guess the external use case for this is advertisement in BGP-LS for Networ= k Management purposes?? There really isn=E2=80=99t IS-IS requirement to know= whether or not an interface is a passive interface.<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> Thanks,<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> Acee<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.0in"> <o:p></o:p></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"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <b><span style=3D"font-size: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]">[email protected]= </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><o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> Hi Anjun,<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;marg= in-bottom:12.0pt;margin-left:1.5in"> <o:p></o:p></p> <blockquote style=3D"border:none;border-left:solid #E67E22 1.0pt;padding:0in= 0in 0in 8.0pt;margin-left:3.75pt;margin-top:3.75pt;margin-right:3.75pt;marg= in-bottom:3.75pt"> <div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <span style=3D"font-size:10.5pt;color:#1F497D">Is it reasonable to put the l= ink attribute information into the =E2=80=9CIP Reachability TLV=E2=80=9D?</s= pan><o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <span style=3D"font-size:10.5pt;color:#1F497D">IMHO, such stub link is not t= he normal links within IGP domain. Label the related prefix is coming f= rom the passive/stub link seems also acceptable?</span><o:p></o:p></p> </div> </div> </blockquote> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> Well, a passive interface is really configured so that you advertise the int= erface=E2=80=99s prefix. Attaching the data that you want to the assoc= iated data seems reasonable to me.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> There=E2=80=99s no good IS Neighbor advertisement to attach the sub-TLV to b= ecause there is no neighbor.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> Tony<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al= t:auto;margin-left:1.5in"> <o:p></o:p></p> </div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;marg= in-bottom:12.0pt;margin-left:1.5in"> <o:p></o:p></p> </div> </div> <p class=3D"MsoNormal" style=3D"margin-left:1.0in">_________________________= ______________________<br> Lsr mailing list<br> [email protected]<br> https://www.ietf.org/mailman/listinfo/lsr<o:p></o:p></p> </blockquote> </div> </div> </blockquote> </div> <p class=3D"MsoNormal" style=3D"margin-left:.5in">__________________________= _____________________<br> Lsr mailing list<br> [email protected]<br> https://www.ietf.org/mailman/listinfo/lsr<o:p></o:p></p> </div> </blockquote> </div> </div> </div></blockquote></div></body></html>= --Apple-Mail-E12C2098-FB83-415B-8BC9-A551BB0C0C3A-- --===============1156108998154052473== 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 --===============1156108998154052473==--