[Pppext] Future of the PPP WG

Donald Eastlake <d3e3e3@gmail.com> Thu, 08 September 2011 22:22 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 D168F21F8BAD for <pppext@ietfa.amsl.com>; Thu, 8 Sep 2011 15:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.143
X-Spam-Status: No, score=-104.143 tagged_above=-999 required=5 tests=[AWL=-0.544, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 2bmERagd4b-H for <pppext@ietfa.amsl.com>; Thu, 8 Sep 2011 15:22:51 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 3CFD121F8BAC for <pppext@ietf.org>; Thu, 8 Sep 2011 15:22:51 -0700 (PDT)
Received: by vxi29 with SMTP id 29so1260129vxi.31 for <pppext@ietf.org>; Thu, 08 Sep 2011 15:24:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=R7YhWAgveVsawYaCIQGSqmgCEwqS+EB/zDhjX7GmiWg=; b=FKBLBhCzeAPocarpG+m1K8Kgg5Vr4L1bQmbGeSeW3YDs+7KZSuwlNhE5sxh9b5C3Dh KQhbymVIcUJVXxueHtGeXW+fsctOvfQypYl/uKrWG8ID99HpNKKG/ZGYdrU4guajh0of ZnE65m8Wu+mg0ufR/doOUXHEb00NedJ1MsBGA=
Received: by with SMTP id bq7mr1232333vdc.526.1315520684071; Thu, 08 Sep 2011 15:24:44 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Thu, 8 Sep 2011 15:24:24 -0700 (PDT)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 8 Sep 2011 18:24:24 -0400
Message-ID: <CAF4+nEF-G1zpRABffyT+fpx=Oc0__u1Yth6oK-1UWLTqEgCRVg@mail.gmail.com>
To: IETF PPP Extensions <pppext@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [Pppext] Future of the PPP WG
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: Thu, 08 Sep 2011 22:22:51 -0000


In case you were unaware, I am now the Chair of PPPEXT.

Generally, there has been little activity in this WG for some years.
Although I believe it serves a useful purpose in examining PPP
proposals, possibly that purpose could be served by just continuing
the mailing list. In any case, it seems likely that, if the situation
continues unchanged, the WG will be dissolved sometime early next

In the process of producing RFC 6361, it became very apparent that the
PPP security RFCs, such as they are, meet few, if any, modern IETF
security guidelines. I believe that there should be an update of PPP
security or, if an effort to update them fails for some reason, then
at least old / inadequate / unimplemented PPP security RFCs should be
declared historic.

My suggestion is that PPPEXT re-Charter to include a goal such as the
above and I'm willing to try drafting a new Charter but welcome
suggestions and comments on all this.

One question is, should PPPEXT have a 1 hour meeting at the November
IETF meeting? I think that would be the best way to come to consensus
on this but obviously only if enough people would plan to actually
attend. So, I'd be interested in who is would attend and any opinions
for or against such a meeting.

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