Re: Advancing PPP RFCs to Standard, updating Security
Karl Fox <[email protected]> Mon, 13 May 2013 08:54:02 -0400
| Newsgroups | gmane.ietf.pppext |
|---|---|
| Message-ID | <CAKRY2Yw8kYce-ZgxnT+mrvBp4AqhBZ+WP6+FRQsLpQCGGSoL8Q@mail.gmail.com> |
--===============7201445249258340210== Content-Type: multipart/alternative; boundary=089e0111bb74dc5bc204dc99022a --089e0111bb74dc5bc204dc99022a Content-Type: text/plain; charset=ISO-8859-1 Likewise. If they don't meet current security standards, any changes we make are certainly not going to be widely implemented. Karl On Mon, May 13, 2013 at 1:33 AM, Glen Zorn <[email protected]> wrote: > On 05/13/2013 05:55 AM, Bernard Aboba wrote: > > I see no point in creating new PPP security standards at this point. >> > > > I agree. > > > >> > > > On May 12, 2013, at 3:01 AM, "Donald Eastlake" <[email protected]> > > wrote: > > > >> Hi, > >> > >> Our AD is interested in a plan to upgrade appropriate PPP > >> standards track RFCs to full Standard. A change in state can, under > >> the right circumstances, be done without a new RFC. > >> > >> I think it would be appropriate, as I have suggested before, to > >> review the PPP security RFCs with a view, in each case, to moving > >> to Historic those which don't meet modern security standards or to > >> obsolete them with a new version which does... The later would > >> require a Charter change. > >> > >> To quote from the existing PPPEXT Charter: "The group may, > >> however, advance existing specifications to the next level in the > >> standards track, if a need for that comes up. Similarly, the group > >> may classify existing specifications as Historic where this is > >> appropriate." > >> > >> I'd be interested in any comments. If there is any desire for a > >> brief meeting in Berlin to discuss this sort of thing, this would > >> be a good time to request it. (I just noticed that the session > >> request tool has an option to request a 1/2 hour meeting which I > >> never noticed before. While WGs have had very short meetings, I > >> can't recall one scheduled for less than 1 hour...) I suspect such > >> a meeting at the next IETF Meeting in Berlin is not necessary... > >> > >> Thanks, Donald [PPPEXT Chair] ============================= Donald > >> E. Eastlake 3rd +1-508-333-2270 (cell) 155 Beaver Street, > >> Milford, MA 01757 USA [email protected] > >> ______________________________**_________________ Pppext mailing > >> list [email protected] https://www.ietf.org/mailman/**listinfo/pppext<https://www.ietf.org/mailman/listinfo/pppext> > > ______________________________**_________________ Pppext mailing list > > [email protected] https://www.ietf.org/mailman/**listinfo/pppext<https://www.ietf.org/mailman/listinfo/pppext> > > ______________________________**_________________ > Pppext mailing list > [email protected] > https://www.ietf.org/mailman/**listinfo/pppext<https://www.ietf.org/mailman/listinfo/pppext> > --089e0111bb74dc5bc204dc99022a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Likewise. If they don't meet current security standard= s, any changes we make are certainly not going to be widely implemented.<di= v><br></div><div>Karl</div></div><div class=3D"gmail_extra"><br><br><div cl= ass=3D"gmail_quote"> On Mon, May 13, 2013 at 1:33 AM, Glen Zorn <span dir=3D"ltr"><<a href=3D= "mailto:[email protected]" target=3D"_blank">[email protected]</a>></s= pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex= ;border-left:1px #ccc solid;padding-left:1ex"> <div class=3D"im">On 05/13/2013 05:55 AM, Bernard Aboba wrote:<br> <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> I see no point in creating new =A0PPP security standards at this point.<br> </blockquote> ><br></div> I agree.<div class=3D"HOEnZb"><div class=3D"h5"><br> <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> <br> </blockquote> ><br> > On May 12, 2013, at 3:01 AM, "Donald Eastlake" <<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>><br> > wrote:<br> ><br> >> Hi,<br> >><br> >> Our AD is interested in a plan to upgrade appropriate PPP<br> >> standards track RFCs to full Standard. A change in state can, unde= r<br> >> the right circumstances, be done without a new RFC.<br> >><br> >> I think it would be appropriate, as I have suggested before, to<br= > >> review the PPP security RFCs with a view, in each case, to moving<= br> >> to Historic those which don't meet modern security standards o= r to<br> >> obsolete them with a new version which does... The later would<br> >> require a Charter change.<br> >><br> >> To quote from the existing PPPEXT Charter: "The group may,<br= > >> however, advance existing specifications to the next level in the<= br> >> standards track, if a need for that comes up. Similarly, the group= <br> >> may classify existing specifications as Historic where this is<br> >> appropriate."<br> >><br> >> I'd be interested in any comments. If there is any desire for = a<br> >> brief meeting in Berlin to discuss this sort of thing, this would<= br> >> be a good time to request it. (I just noticed that the session<br> >> request tool has an option to request a 1/2 hour meeting which I<b= r> >> never noticed before. While WGs have had very short meetings, I<br= > >> can't recall one scheduled for less than 1 hour...) I suspect = such<br> >> a meeting at the next IETF Meeting in Berlin is not necessary...<b= r> >><br> >> Thanks, Donald [PPPEXT Chair] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Donald<br> >> E. Eastlake 3rd =A0 <a href=3D"tel:%2B1-508-333-2270" value=3D"+15= 083332270" target=3D"_blank">+1-508-333-2270</a> (cell) 155 Beaver Street,<= br> >> Milford, MA 01757 USA <a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a><br> >> ______________________________<u></u>_________________ Pppext mail= ing<br> >> list <a href=3D"mailto:[email protected]" target=3D"_blank">Pppext@i= etf.org</a> <a href=3D"https://www.ietf.org/mailman/listinfo/pppext" target= =3D"_blank">https://www.ietf.org/mailman/<u></u>listinfo/pppext</a><br> > ______________________________<u></u>_________________ Pppext mailing = list<br> > <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</= a> <a href=3D"https://www.ietf.org/mailman/listinfo/pppext" target=3D"_blan= k">https://www.ietf.org/mailman/<u></u>listinfo/pppext</a><br> <br> ______________________________<u></u>_________________<br> Pppext 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/pppext" target=3D"_blank">= https://www.ietf.org/mailman/<u></u>listinfo/pppext</a><br> </div></div></blockquote></div><br></div> --089e0111bb74dc5bc204dc99022a-- --===============7201445249258340210== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Pppext mailing list [email protected] https://www.ietf.org/mailman/listinfo/pppext --===============7201445249258340210==--