Re: BGP autodiscovery design team
Warren Kumari <[email protected]> Thu, 5 Dec 2019 21:11:01 -0500
| Newsgroups | gmane.ietf.idr |
|---|---|
| Message-ID | <CAHw9_iJc-WsA7SoStS4jLnrLhideXUiuqJdyZYjgaDobKB4j+g@mail.gmail.com> |
--===============0562135451490932227== Content-Type: multipart/alternative; boundary="00000000000057a6310598ff8f42" --00000000000057a6310598ff8f42 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Dec 5, 2019 at 5:15 PM Jeffrey Haas <[email protected]> wrote: > Publicly echoing my private responses, I'm willing to be on the design > team. > As am I (if the chairs will have me!) W > -- Jeff > > > On Dec 4, 2019, at 2:33 PM, John Scudder <jgs=3D > [email protected]> wrote: > > > > Hi All, > > > > I realized this morning that although we announced in the last meeting > that we=E2=80=99re forming this design team, we never announced it on the= list. > This is to correct that mistake. Here=E2=80=99s the text of the slide we = presented > at the meeting ( > https://datatracker.ietf.org/meeting/106/materials/slides-106-idr-sessa-a= uto-discovery-design-team-chairs-00 > ): > > > > --- > > Autodiscovery > > > > =E2=80=A2 Clear interest in WG to work on this topic. > > =E2=80=A2 No clear consensus on a specific approach. > > =E2=80=A2 Proposals (four of them) progressively closer semantically, s= eems > likely convergence can happen. > > =E2=80=A2 But, important differences remain. > > =E2=80=A2 At least: transport (L2, L3), liveness, security, maybe= multihop. > > =E2=80=A2 Chairs propose to charter a design team to close on a single = proposal, > by next meeting. > > =E2=80=A2 Might build on one of the existing drafts, might be a n= ew draft, > up to the design team. > > =E2=80=A2 Emphasis on pragmatism, OK to limit applicability (for = example, > to a single administrative domain). > > =E2=80=A2 Questions? Comments? Volunteers? > > =E2=80=94 > > > > We are in the process of forming the team and hope to announce it soon. > We have many good volunteers already but if you didn=E2=80=99t know and d= o want to > volunteer, please contact Sue and me. > > > > Note that the design team will not make any binding decisions: as with > all WG work, the WG has the final word, so any output of the DT will serv= e > as input to the WG as a whole. (So even if you aren=E2=80=99t part of the= DT, that > doesn=E2=80=99t mean you won=E2=80=99t have a chance to be part of the pr= ocess.) > > > > Thanks, > > > > =E2=80=94John > > _______________________________________________ > > Idr mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/idr > > _______________________________________________ > Idr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/idr > --=20 I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf --00000000000057a6310598ff8f42 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class= =3D"gmail_attr">On Thu, Dec 5, 2019 at 5:15 PM Jeffrey Haas <<a href=3D"= mailto:[email protected]">[email protected]</a>> wrote:<br></div><blockquote c= lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;= padding-left:1ex">Publicly echoing my private responses, I'm willing to= be on the design team.<br> </blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">As am I (if the = chairs will have me!)</div><div dir=3D"auto"><br></div><div dir=3D"auto">W<= /div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><blockquote cl= ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p= adding-left:1ex"><br> -- Jeff<br> <br> > On Dec 4, 2019, at 2:33 PM, John Scudder <jgs=3D<a href=3D"mailto:4= [email protected]" target=3D"_blank">[email protected]= </a>> wrote:<br> > <br> > Hi All,<br> > <br> > I realized this morning that although we announced in the last meeting= that we=E2=80=99re forming this design team, we never announced it on the = list. This is to correct that mistake. Here=E2=80=99s the text of the slide= we presented at the meeting (<a href=3D"https://datatracker.ietf.org/meeti= ng/106/materials/slides-106-idr-sessa-auto-discovery-design-team-chairs-00"= rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/meeting/= 106/materials/slides-106-idr-sessa-auto-discovery-design-team-chairs-00</a>= ):<br> > <br> > ---<br> > Autodiscovery<br> > <br> > =E2=80=A2 Clear interest in WG to work on this topic.<br> > =E2=80=A2 No clear consensus on a specific approach.<br> > =E2=80=A2 Proposals (four of them) progressively closer semantically, = seems likely convergence can happen. <br> > =E2=80=A2 But, important differences remain.<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 At least: transport (L2, L3), live= ness, security, maybe multihop.<br> > =E2=80=A2 Chairs propose to charter a design team to close on a single= proposal, by next meeting.<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Might build on one of the existing= drafts, might be a new draft, up to the design team.<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Emphasis on pragmatism, OK to limi= t applicability (for example, to a single administrative domain). <br> > =E2=80=A2 Questions? Comments? Volunteers?<br> > =E2=80=94<br> > <br> > We are in the process of forming the team and hope to announce it soon= .. We have many good volunteers already but if you didn=E2=80=99t know and d= o want to volunteer, please contact Sue and me. <br> > <br> > Note that the design team will not make any binding decisions: as with= all WG work, the WG has the final word, so any output of the DT will serve= as input to the WG as a whole. (So even if you aren=E2=80=99t part of the = DT, that doesn=E2=80=99t mean you won=E2=80=99t have a chance to be part of= the process.)<br> > <br> > Thanks,<br> > <br> > =E2=80=94John<br> > _______________________________________________<br> > Idr mailing list<br> > <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><br> > <a href=3D"https://www.ietf.org/mailman/listinfo/idr" rel=3D"noreferre= r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/idr</a><br> <br> _______________________________________________<br> Idr mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><br> <a href=3D"https://www.ietf.org/mailman/listinfo/idr" rel=3D"noreferrer" ta= rget=3D"_blank">https://www.ietf.org/mailman/listinfo/idr</a><br> </blockquote></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" = data-smartmail=3D"gmail_signature">I don't think the execution is relev= ant when it was obviously a bad idea in the first place.<br>This is like pu= tting rabid weasels in your pants, and later expressing regret at having ch= osen those particular rabid weasels and that pair of pants.<br>=C2=A0 =C2= =A0---maf</div> --00000000000057a6310598ff8f42-- --===============0562135451490932227== 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 --===============0562135451490932227==--