Re: [Pppext] Advancing PPP RFCs to Standard, updating Security
Bernard Aboba <bernard_aboba@hotmail.com> Sun, 12 May 2013 22:55 UTC
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: pppext@ietfa.amsl.com
Delivered-To: pppext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B42DC21F847B for <pppext@ietfa.amsl.com>; Sun, 12 May 2013 15:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level:
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSsXn7gUjeoL for <pppext@ietfa.amsl.com>; Sun, 12 May 2013 15:55:43 -0700 (PDT)
Received: from blu0-omc1-s1.blu0.hotmail.com (blu0-omc1-s1.blu0.hotmail.com [65.55.116.12]) by ietfa.amsl.com (Postfix) with ESMTP id A2DE621F8709 for <pppext@ietf.org>; Sun, 12 May 2013 15:55:43 -0700 (PDT)
Received: from BLU404-EAS227 ([65.55.116.7]) by blu0-omc1-s1.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 12 May 2013 15:55:43 -0700
X-EIP: [eqi6kRBbArJp5Z+4WEijCnM5OsDyG85q]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU404-EAS227A323E2D1BB467B6AB5CE93A70@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
References: <CAF4+nEFseyZrSivPZ_N-DZVv4uMpeRHiu3iofzgaXpnq3OXe2Q@mail.gmail.com>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <CAF4+nEFseyZrSivPZ_N-DZVv4uMpeRHiu3iofzgaXpnq3OXe2Q@mail.gmail.com>
Date: Sun, 12 May 2013 15:55:38 -0700
To: Donald Eastlake <d3e3e3@gmail.com>
X-OriginalArrivalTime: 12 May 2013 22:55:43.0365 (UTC) FILETIME=[D4F73350:01CE4F63]
Cc: IETF PPP Extensions <pppext@ietf.org>
Subject: Re: [Pppext] Advancing PPP RFCs to Standard, updating Security
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 May 2013 22:55:48 -0000
I see no point in creating new PPP security standards at this point. 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
- [Pppext] Advancing PPP RFCs to Standard, updating… Donald Eastlake
- Re: [Pppext] Advancing PPP RFCs to Standard, upda… Bernard Aboba
- Re: [Pppext] Advancing PPP RFCs to Standard, upda… Glen Zorn
- Re: [Pppext] Advancing PPP RFCs to Standard, upda… Karl Fox
- Re: [Pppext] Advancing PPP RFCs to Standard, upda… Donald Eastlake
- Re: [Pppext] Advancing PPP RFCs to Standard, upda… Thomas Narten
- Re: [Pppext] Advancing PPP RFCs to Standard, upda… William Allen Simpson
- Re: [Pppext] Advancing PPP RFCs to Standard, upda… James Carlson
- Re: [Pppext] Advancing PPP RFCs to Standard, upda… William Allen Simpson
- Re: [Pppext] Advancing PPP RFCs to Standard, upda… Brian Haberman