Re: [Pppext] Advancing PPP RFCs to Standard, updating Security

Glen Zorn <glenzorn@gmail.com> Mon, 13 May 2013 05:33 UTC

Return-Path: <glenzorn@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 A9F3F21F8F6E for <pppext@ietfa.amsl.com>; Sun, 12 May 2013 22:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
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 Dun3OAGG4R4o for <pppext@ietfa.amsl.com>; Sun, 12 May 2013 22:33:25 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 1E44421F8F69 for <pppext@ietf.org>; Sun, 12 May 2013 22:33:22 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so896338pbb.20 for <pppext@ietf.org>; Sun, 12 May 2013 22:33:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=b20FDCov7oydceYMSZmMIDjwXvYAGn1NUXpJjFXcfzE=; b=QBbWcmRqMANg+bl/XowBU06QZCfl8Oq+XkFbnHbdoBw5/Vu1jMOX6N+bVZhpQ9ygDp jnRMgfpqESpuZKd4RcTj7UUTQbyKA60e/7k9ZFb48RAWerXjLgbtPzYRu99muuqnCZQa 4HzDBzjLxlrD7r48CXh6uMHccbfzSS3up7HP5ZGCqUnCGKgF7IvvRpHpirDxoLjCZygQ g7XY3UAtVh7OLgMnZfoSQkgLGo+uDU7fBDdSnjH6nR2mSiZG0Vlkq6XVDhdeuvQ3Hpeb 9YfQBLmANU2TYb2Kxkt2ld8GdRrYmZj17IGn1F7xE/6kOp/HOZX8JALY68QorHt+7YHY v+bg==
X-Received: by 10.68.19.103 with SMTP id d7mr27460635pbe.156.1368423201900; Sun, 12 May 2013 22:33:21 -0700 (PDT)
Received: from [192.168.0.104] (ppp-58-11-136-197.revip2.asianet.co.th. [58.11.136.197]) by mx.google.com with ESMTPSA id ih1sm12544411pbb.44.2013.05.12.22.33.18 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 12 May 2013 22:33:20 -0700 (PDT)
Message-ID: <51907B1C.3050300@gmail.com>
Date: Mon, 13 May 2013 12:33:16 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
References: <CAF4+nEFseyZrSivPZ_N-DZVv4uMpeRHiu3iofzgaXpnq3OXe2Q@mail.gmail.com> <BLU404-EAS227A323E2D1BB467B6AB5CE93A70@phx.gbl>
In-Reply-To: <BLU404-EAS227A323E2D1BB467B6AB5CE93A70@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Mon, 13 May 2013 05:33:25 -0000

On 05/13/2013 05:55 AM, Bernard Aboba wrote:

> I see no point in creating new  PPP security standards at this point.
 >
I agree.

>
 >
 > 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 mailing list
 > Pppext@ietf.org https://www.ietf.org/mailman/listinfo/pppext