IETF Logo Mail Archive

Re: [saag] New Version Notification for draft-cui-dhc-dhcpv6-encryption-02.txt

Randy Bush <randy@psg.com> Sun, 02 August 2015 08:32 UTC

Return-Path: <randy@psg.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0EDD1A6FEC for <saag@ietfa.amsl.com>; Sun, 2 Aug 2015 01:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6zBtKktfCcJ for <saag@ietfa.amsl.com>; Sun, 2 Aug 2015 01:32:28 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05AC41A6FE9 for <saag@ietf.org>; Sun, 2 Aug 2015 01:32:28 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1ZLogy-0006PO-J8; Sun, 02 Aug 2015 08:32:24 +0000
Date: Sun, 02 Aug 2015 17:32:23 +0900
Message-ID: <m2egjm6qg8.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: DeKok Alan <aland@deployingradius.com>
In-Reply-To: <85F31297-B08F-4A86-B9A0-8004FB78DD01@deployingradius.com>
References: <313da830.6be8.14ed8564467.Coremail.lilishan48@126.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/iggLD3PqQKNj7CKFLSzyK5DF184>
Cc: Security Area Advisory Group <saag@ietf.org>
Subject: Re: [saag] New Version Notification for draft-cui-dhc-dhcpv6-encryption-02.txt
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Aug 2015 08:32:29 -0000

> This is imperfect, of course.  It presumes that 802.1X is used,
> which isn't always the case.  Other methods will be needed in
> other circumstances.

is there any chance we can enumerate the significant scenarios so
that we can start to understand how they might be handled?

randy

v2.23.0 | Report a Bug | By Email