IETF Logo Mail Archive

Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 12 August 2016 23:22 UTC

Return-Path: <Fred.L.Templin@boeing.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 A497412D0AA for <dhcwg@ietfa.amsl.com>; Fri, 12 Aug 2016 16:22:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 qWt6fih9DGWT for <dhcwg@ietfa.amsl.com>; Fri, 12 Aug 2016 16:22:36 -0700 (PDT)
Received: from ewa-mbsout-01.mbs.boeing.net (ewa-mbsout-01.mbs.boeing.net [130.76.20.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F138612D0A1 for <dhcwg@ietf.org>; Fri, 12 Aug 2016 16:22:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u7CNMZGC044196; Fri, 12 Aug 2016 16:22:35 -0700
Received: from XCH15-05-01.nw.nos.boeing.com (xch15-05-01.nw.nos.boeing.com [137.137.100.58]) by ewa-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u7CNMVRd044154 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 12 Aug 2016 16:22:31 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) by XCH15-05-01.nw.nos.boeing.com (2002:8989:643a::8989:643a) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 12 Aug 2016 16:22:30 -0700
Received: from XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) by XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) with mapi id 15.00.1178.000; Fri, 12 Aug 2016 16:22:30 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Francis Dupont <Francis.Dupont@fdupont.fr>
Thread-Topic: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)
Thread-Index: AdHz4kyO7hzDfzYnSfqWBjHhBsGHFqBFt3GAoEOccRA=
Date: Fri, 12 Aug 2016 23:22:30 +0000
Message-ID: <ccaff4d4cb5c4eefb05eee0660c2611c@XCH15-05-05.nw.nos.boeing.com>
References: Your message of Thu, 11 Aug 2016 15:10:10 -0000. <92dcf2e0cf08452caa5861f7258ea6c5@XCH15-05-05.nw.nos.boeing.com> <201608121919.u7CJJqcS056876@givry.fdupont.fr> <c5303eef3c124228825f32a40f229107@XCH-ALN-003.cisco.com>
In-Reply-To: <c5303eef3c124228825f32a40f229107@XCH-ALN-003.cisco.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: [137.137.12.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/BPqkztu1xNgZR3XyC6dfPNcTjws>
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 12 Aug 2016 23:22:37 -0000

Hi, OK to remain silent on this but:

> => IMHO it should not and in particular it should not be referenced as a replacement for authentication according to the new direction
> taken by secdhcpv6 (i.e., encryption vs authentication).

this part has me worried. My use case is a large multi-access link that is secured
via physical and/or link-layer security. But, the link is still vulnerable to "insider
attacks" where a rogue node might try to fool the DHCPv6 server into giving it
configuration information pertaining to a victim node. So, I was counting on
secdhcpv6 to provide a means for the server to authenticate each client.
Has something changed?

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Bernie Volz (volz) [mailto:volz@cisco.com]
> Sent: Friday, August 12, 2016 12:38 PM
> To: Francis Dupont <Francis.Dupont@fdupont.fr>; Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: <dhcwg@ietf.org> <dhcwg@ietf.org>
> Subject: RE: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)
> 
> I second this ... mostly because:
> 
> 1. It is still very much a work in progress.
> 2. Several previous attempts at this had to be rebooted; while we hope that isn't the case this time around ...
> 3. This is the base standard and extensions to it will always exist.
> 
> Note: We only reference two drafts, prefix-length-hints and topo-conf. Topo-conf will be an RFC well before this one (it is at RFC-
> editor). And, we still need to finalize what we do re: prefix-length-hints in this document (see Ticket #114 -
> https://trac.tools.ietf.org/group/dhcpv6bis/ticket/114).
> 
> - Bernie
> 
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Francis Dupont
> Sent: Friday, August 12, 2016 3:20 PM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: <dhcwg@ietf.org> <dhcwg@ietf.org>
> Subject: Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)
> 
>  In your previous mail you wrote:
> 
> >  Should RFC3315(bis) cite 'draft-ietf-dhc-secdhcpv6?
> 
> => IMHO it should not and in particular it should not be referenced as a replacement for authentication according to the new direction
> taken by secdhcpv6 (i.e., encryption vs authentication).
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email