Re: [Pppext] Advancing PPP RFCs to Standard, updating Security
Donald Eastlake <d3e3e3@gmail.com> Wed, 15 May 2013 06:59 UTC
Return-Path: <d3e3e3@gmail.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 21DCD21F8FB6 for <pppext@ietfa.amsl.com>; Tue, 14 May 2013 23:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 qF5hZXeVUV9g for <pppext@ietfa.amsl.com>; Tue, 14 May 2013 23:59:41 -0700 (PDT)
Received: from mail-ob0-x241.google.com (mail-ob0-x241.google.com [IPv6:2607:f8b0:4003:c01::241]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6B621F8F9E for <pppext@ietf.org>; Tue, 14 May 2013 23:59:41 -0700 (PDT)
Received: by mail-ob0-f193.google.com with SMTP id v19so393977obq.0 for <pppext@ietf.org>; Tue, 14 May 2013 23:59:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=OXIcdp1NgQqZIwwoEKk/TGbFrlbpETqJWvNPBHAZ350=; b=K8IyEo7iFnqm+g5UTvcydlC6P82ckvYF9wH8wcm6WgTie8G094R34sTqfugF03TNec oN/OyVtFc6he69t4fAmBYmvB4Tn2anueGIS6CrLB+grBQJw5pFbEAB1HMswfP4D8L5JV Sa9Ue7zXFiOtEslwm2DkcIyA98SKsjmwsvep+q5KLdfRZWBR41yjInCVpFi34U4iqA3T jP7vHpblvQ0JBLNOFKaX+QMZUw02Or4oVnGQUTN/r2NMbhrZmg2+V5x4zC3XV9YIM9XH qZvQ6ugdUSiVvyefc272sIrqGmyd2/r5qt5SE72Zimjcj8Vn+MJo0wdaL/cVFVcIE2xm CztA==
X-Received: by 10.60.34.69 with SMTP id x5mr18354324oei.110.1368601181014; Tue, 14 May 2013 23:59:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.162.233 with HTTP; Tue, 14 May 2013 23:59:20 -0700 (PDT)
In-Reply-To: <CAF4+nEFseyZrSivPZ_N-DZVv4uMpeRHiu3iofzgaXpnq3OXe2Q@mail.gmail.com>
References: <CAF4+nEFseyZrSivPZ_N-DZVv4uMpeRHiu3iofzgaXpnq3OXe2Q@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 15 May 2013 02:59:20 -0400
Message-ID: <CAF4+nEHFJwfzRqa8=g3s1FcqvUeBXhgCZcsd7Hw7n5bt6CkEow@mail.gmail.com>
To: IETF PPP Extensions <pppext@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
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: Wed, 15 May 2013 06:59:42 -0000
Hi, Thanks for the feedback thus far on security. Further feedback welcome. I continue to be inclined against having a WG meeting in Berlin. I may have overstated our AD's interest in advancing PPP standards, Brian is perhaps closer to neutral on the idea. Thanks, Donald ============================= Donald E. Eastlake 3rd +1-508-333-2270 (cell) 155 Beaver Street, Milford, MA 01757 USA d3e3e3@gmail.com On Sun, May 12, 2013 at 6: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] 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