Re: [dhcwg] seDHCPv6 update and next steps ...

"Bernie Volz (volz)" <volz@cisco.com> Wed, 12 July 2017 21:06 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99AD3131788 for <dhcwg@ietfa.amsl.com>; Wed, 12 Jul 2017 14:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 Yb7T4bWTfPxN for <dhcwg@ietfa.amsl.com>; Wed, 12 Jul 2017 14:06:14 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBCED1317BF for <dhcwg@ietf.org>; Wed, 12 Jul 2017 14:06:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22490; q=dns/txt; s=iport; t=1499893573; x=1501103173; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=bZ3pNP7+pnr9ztXjkGq0Wy+6RwjJAQKKjfi2assLVJg=; b=RrI/M7TcPLnkmIdauhiNf1KLMhR5avR58VSjk61uBgrk/ZUQJ7rIXTRS 9nMzUqpFsVYT4omxKGbWwc7/W+6MZMNaOGYCQTi+aTVGAQ3I+KJw06CsT 23sRLYnEftUP+5YHKHnBxH/GMg5C+beB10KU905rqW40LNQk5QAvnyuov k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DMAAD5jWZZ/4ENJK1eGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgm9rZIEUB44CkXGWA4IRhXYCg1E/GAECAQEBAQEBAWsohRgBAQEBAy1?= =?us-ascii?q?BGwIBCBEEAQEhBwcyFAkIAQEEARIIiUNksBqLIgEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAR2DKIFhg02DJIRUTIU+BZc8h2wClASCFZAZiUOMDQEfOIEKdRVJhxZ2AYY?= =?us-ascii?q?bK4EFgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.40,351,1496102400"; d="scan'208,217";a="258856606"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Jul 2017 21:06:12 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v6CL6COO013462 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 12 Jul 2017 21:06:12 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 12 Jul 2017 16:06:11 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Wed, 12 Jul 2017 16:06:11 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "draft-ietf-dhc-sedhcpv6@tools.ietf.org" <draft-ietf-dhc-sedhcpv6@tools.ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: seDHCPv6 update and next steps ...
Thread-Index: AdL7TPjzgLDuRsMjTzK32MYQ2IpqqAAAv6lwAABm4DA=
Date: Wed, 12 Jul 2017 21:06:11 +0000
Message-ID: <e9cbb73ac7164448aa215c5ab3081e18@XCH-ALN-003.cisco.com>
References: <4775705423554cc39360724881251abe@XCH-ALN-003.cisco.com> <a3d7522c763947a2916edfc461bf92af@XCH15-06-08.nw.nos.boeing.com>
In-Reply-To: <a3d7522c763947a2916edfc461bf92af@XCH15-06-08.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.98.1.196]
Content-Type: multipart/alternative; boundary="_000_e9cbb73ac7164448aa215c5ab3081e18XCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/DNgSZsc0IYedT_ORJv83Oa-yOL8>
Subject: Re: [dhcwg] seDHCPv6 update and next steps ...
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2017 21:06:16 -0000

Hi Fred:

Thanks for your interest.

Could you clarify what you mean by authentication-only? As I see if in terms of authentication there is:

1.       Authenticate the server to the client

2.       Authenticate the client to the server

3.       Or both

There are also various degrees of authentication - for example, TOFU (Trust on First Use) to trusted third party (and what that might impose on certificate distribution / validation).

And, if you have a specific use model in mind (for example, if this is for AERO), having a brief summary of this and the authentication requirements would be useful.

I'd also suggest that understanding why other techniques, such as 802.1X, would not be appropriate could provide added value in understanding the requirements.


-          Bernie

From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
Sent: Wednesday, July 12, 2017 4:49 PM
To: Bernie Volz (volz) <volz@cisco.com>om>; draft-ietf-dhc-sedhcpv6@tools.ietf.org; dhcwg@ietf.org
Subject: RE: seDHCPv6 update and next steps ...

Hi Bernie,

Unfortunately, my plane does not arrive until ~16:00 CEST on Sunday. But, if
this work is going back to first principles I would like to express an interest in
an authentication-only mode of operation (i.e., no encryption). It would
avoid a "double-encryption" when encryption is already provided by the
link layer between the client and server (or first-hop relay) and there are
already other securing mechanisms in place between relays and servers.

Thanks - Fred


From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, July 12, 2017 1:30 PM
To: draft-ietf-dhc-sedhcpv6@tools.ietf.org<mailto:draft-ietf-dhc-sedhcpv6@tools.ietf.org>; dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] seDHCPv6 update and next steps ...

Hi:

There has been some discussion (most recently off the dhcwg mailing list) about the sedhcpv6 draft.

Previously, as discussed on the dhcwg mailing list a while back, there are some issues with the current draft (including the encryption issue; the key can't be used to encrypt more data than the size of the key). And, while some of the co-authors have communicated recently, others have been quiet and it is not clear what the level of interest for each is in continuing. This work has sadly had a long road with several turns already.

The discussion raised the question as to what the goals of this work should be. Some feel that we need to step back and first develop a "requirements document" to clearly detail what the goals of a securing DHCPv6 should be (for example, was the fairly recent push to add encryption appropriate?).

Thus, Tomek and I feel that it would be worth having an interested group meet before the IETF-99 DHC WG session (which is on Wednesday, 7/19 afternoon) to discuss this so that we could formulate a strategy. If you have interest, let us know. We propose to meet on Sunday at 14:00 (CEST) in Chez Louis (Hackathon) room - we can find a table there, or look for another place. (If there is remote participation interest, let us know and we'll see what we might be able to accommodate.)

We may also have extra time in the DHC WG session to discuss in detail there, but it could be helpful to have one or more proposals and, if we get the slides out quickly, give people some time to think about it before the WG session.


-          Bernie and Tomek