[Pppext] Advancing PPP RFCs to Standard, updating Security

Donald Eastlake <d3e3e3@gmail.com> Sun, 12 May 2013 10:01 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: pppext@ietfa.amsl.com
Delivered-To: pppext@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 1108821F86CE for <pppext@ietfa.amsl.com>; Sun, 12 May 2013 03:01:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.079
X-Spam-Status: No, score=-102.079 tagged_above=-999 required=5 tests=[AWL=0.521, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 6uj08+UHTfVV for <pppext@ietfa.amsl.com>; Sun, 12 May 2013 03:01:21 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 8FBD221F86BB for <pppext@ietf.org>; Sun, 12 May 2013 03:01:21 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id un3so569937obb.33 for <pppext@ietf.org>; Sun, 12 May 2013 03:01:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=TD0DMfaXYGDmAqfY/sjecYqiFTg7d9UvgQaj6KGPkYo=; b=O/xkeEk3sCo3q5a96lIwuJazTgg4NlHQHAQ+OK6IIXT6fd8uCPQ9nHLYUpGKbiu9Um jkV7iSeWCvP1MO5B0JS7eT7DW9SIBUB6BGlhLkXVOxGlsa4zYmKMBbku5w83SNmwA7WL 23Y00UVzHQwPlS7lci9cXaT7uLutPl75zJx7yaiDS7+WxOTC3uQU7JT2gbycJDHWQRQt w+4/u2HnpyLh7Qs7hdZWztfSvRuRB7ilynKdyOO/ECm2Soaf79BxSfkAUaA3bczy1HMS OWI6zcbBt+2obIXglZ2aLouje/BGLedXmq2PVYKUIbrFd8HZr8nnqc/eGjt8wxHxYGgA M5wA==
X-Received: by with SMTP id b8mr10380203oeq.5.1368352881096; Sun, 12 May 2013 03:01:21 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Sun, 12 May 2013 03:01:00 -0700 (PDT)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 12 May 2013 06:01:00 -0400
Message-ID: <CAF4+nEFseyZrSivPZ_N-DZVv4uMpeRHiu3iofzgaXpnq3OXe2Q@mail.gmail.com>
To: IETF PPP Extensions <pppext@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [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 10:01:22 -0000


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

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...

Donald [PPPEXT Chair]
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA