Re: [Pppext] Advancing PPP RFCs to Standard, updating Security

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 <glenzorn@gmail.com> 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" <d3e3e3@gmail.com>
> > 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 d3e3e3@gmail.com
> >> ______________________________**_________________ Pppext mailing
> >> list Pppext@ietf.org https://www.ietf.org/mailman/**listinfo/pppext<https://www.ietf.org/mailman/listinfo/pppext>
> > ______________________________**_________________ Pppext mailing list
> > Pppext@ietf.org https://www.ietf.org/mailman/**listinfo/pppext<https://www.ietf.org/mailman/listinfo/pppext>
>
> ______________________________**_________________
> Pppext mailing list
> Pppext@ietf.org
> https://www.ietf.org/mailman/**listinfo/pppext<https://www.ietf.org/mailman/listinfo/pppext>
>