Re: [Pppext] Charter update
William Allen Simpson <william.allen.simpson@gmail.com> Tue, 19 May 2009 21:51 UTC
Return-Path: <william.allen.simpson@gmail.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id 1105D3A6BD0 for <pppext@core3.amsl.com>;
Tue, 19 May 2009 14:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uhqp4wRRNU7n for
<pppext@core3.amsl.com>; Tue, 19 May 2009 14:51:50 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31])
by core3.amsl.com (Postfix) with ESMTP id 0AAE03A6BCD for <pppext@ietf.org>;
Tue, 19 May 2009 14:51:49 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so78382ywj.49 for
<pppext@ietf.org>; Tue, 19 May 2009 14:53:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from
:user-agent:mime-version:to:subject:references:in-reply-to
:content-type:content-transfer-encoding;
bh=Ag2Gd4f6qkDkYm9QUc1fJzB9DW2KEEUYjUfIN49Gk88=;
b=VYF2n1WnlmCCmsN2ACNYkn2ooTPc+dEo7hlTsbrbTaJYSTTQ5Fz1xvC31cfA++rMix
MGSv2aOqJWerFNCOcNSvcy1nCFS54smo/F+D4NGB54dV+u5Yz/UmSjgxJBdiQUbZGFJ4
/8dCLYFEdDDnvD50P5S/bTRYHjwQKjB84+tlc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:user-agent:mime-version:to:subject:references
:in-reply-to:content-type:content-transfer-encoding;
b=XXN+6XbyzhtM9tO3t7TRoAmtsMp4aqMP11vd6Tz6nvA9olmn0w1EdkLETJirSqN3+v
KX58kvbJEtAZRxNL6E9Gfg5rcEE0LrO9Um0y8qllVhDr5Ct/j1FvhLrv09hebVMt1eje
0b3/J8D8i99boKa2VUA/lXUnmHNp1/OCzQvXo=
Received: by 10.100.105.9 with SMTP id d9mr957030anc.142.1242770004798;
Tue, 19 May 2009 14:53:24 -0700 (PDT)
Received: from Wastrel.local (c-68-42-73-61.hsd1.mi.comcast.net [68.42.73.61])
by mx.google.com with ESMTPS id 25sm808124aga.57.2009.05.19.14.53.23
(version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 19 May 2009 14:53:24 -0700 (PDT)
Message-ID: <4A132A52.1040008@gmail.com>
Date: Tue, 19 May 2009 17:53:22 -0400
From: William Allen Simpson <william.allen.simpson@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: pppext@ietf.org
References: <4A11560C.9000806@piuha.net>
In-Reply-To: <4A11560C.9000806@piuha.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Pppext] Charter update
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 19 May 2009 21:51:51 -0000
Jari Arkko wrote: > The Point-to-Point Protocol (PPP, RFC 1661) is a mature protocol with a > large number of subprotocols, encapsulations and other extensions. The > PPPEXT working exists to provide a forum for asking clarifications > about the existing specifications and to defend against enhancements > of questionable value. The group is not expected to create new > specifications, and if a need for such work comes up, a recharter is > required. The group may, however, advance existing specifications > to the next level in the standards track, if a need for that comes up. > Seems OK, other than "not expected to create new specifications". Recent security research has rather obsoleted the ancient authentication and encryption specifications. Every once in awhile, I've been thinking about writing some replacement transforms.... How about changing to: "... new specifications, other than replacing or updating authentication, confidentiality, and improved key management specifications. If a need for other additional work arises, ...." Another thing that group probably ought to discuss is formally retiring some of the ancient Proposed work as Historic. Admittedly, we gave up on advancing things like IPCP, as IPv4 was supposedly ready to be replaced (for the past 15 years). Ha!
- [Pppext] Charter update Jari Arkko
- Re: [Pppext] Charter update William Allen Simpson
- Re: [Pppext] Charter update James Carlson
- Re: [Pppext] Charter update Jari Arkko