IETF Logo Mail Archive

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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 18 August 2016 22:42 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 EAF0412D639 for <dhcwg@ietfa.amsl.com>; Thu, 18 Aug 2016 15:42:45 -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 NUb1EKaZReio for <dhcwg@ietfa.amsl.com>; Thu, 18 Aug 2016 15:42:44 -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 F047A12D168 for <dhcwg@ietf.org>; Thu, 18 Aug 2016 15:42:43 -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 u7IMggwY060748; Thu, 18 Aug 2016 15:42:43 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (xch15-05-05.nw.nos.boeing.com [137.137.100.80]) by ewa-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u7IMgd0V060721 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 18 Aug 2016 15:42:39 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) by XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 18 Aug 2016 15:42:38 -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; Thu, 18 Aug 2016 15:42:38 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: 神明達哉 <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)
Thread-Index: AdHz4kyO7hzDfzYnSfqWBjHhBsGHFqBFt3GAoEOccRC/eUedAP/8S5WA//aij8CAFPU5gP//AD5Q
Date: Thu, 18 Aug 2016 22:42:38 +0000
Message-ID: <5ec83aaf4e76497aa4b4d465483bdcf5@XCH15-05-05.nw.nos.boeing.com>
References: <92dcf2e0cf08452caa5861f7258ea6c5@XCH15-05-05.nw.nos.boeing.com> <201608121919.u7CJJqcS056876@givry.fdupont.fr> <c5303eef3c124228825f32a40f229107@XCH-ALN-003.cisco.com> <ccaff4d4cb5c4eefb05eee0660c2611c@XCH15-05-05.nw.nos.boeing.com> <f46aa91e4cfb41b29dd2d8186f5959f8@XCH-ALN-003.cisco.com> <ba1c8ff573d7466b8c437373e05f1023@XCH15-05-05.nw.nos.boeing.com> <b65e1dd66b634240b3ca164b2c04c20a@XCH15-05-05.nw.nos.boeing.com> <CAJE_bqfb5sxOpkTEXkwZXckKBWof7U1-W6EFzCHk7ijnMjpMMA@mail.gmail.com>
In-Reply-To: <CAJE_bqfb5sxOpkTEXkwZXckKBWof7U1-W6EFzCHk7ijnMjpMMA@mail.gmail.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/omhjnlu1bfSXmHAtlDdG7YpAvQs>
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>, "Bernie Volz (volz)" <volz@cisco.com>
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: Thu, 18 Aug 2016 22:42:46 -0000

Hi, I already made a stronger case as follows:

> I think what that means in terms of this draft is that for some use cases all
> that is needed is for the client to include a Signature option in its DHCPv6
> messages to the server. The client does not need to include a Certificate
> option nor any encryption options. So, I would like it if the draft could
> include a simple "authentication only" mode of operation.

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

> -----Original Message-----
> From: jinmei.tatuya@gmail.com [mailto:jinmei.tatuya@gmail.com] On Behalf Of ????
> Sent: Wednesday, August 17, 2016 5:26 PM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: Bernie Volz (volz) <volz@cisco.com>; Francis Dupont <Francis.Dupont@fdupont.fr>; <dhcwg@ietf.org> <dhcwg@ietf.org>
> Subject: Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)
> 
> At Tue, 16 Aug 2016 21:35:34 +0000,
> "Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:
> 
> > I glanced through the document, and my first impression is that it has become
> > overkill for what I need. For my needs, there is already link-layer security and
> > so I do not need encryption between the client and server.
> [...]
> > I think what that means in terms of this draft is that for some use cases all
> > that is needed is for the client to include a Signature option in its DHCPv6
> > messages to the server. The client does not need to include a Certificate
> > option nor any encryption options. So, I would like it if the draft could
> > include a simple "authentication only" mode of operation.
> 
> The currently described approach is based on a WG consensus made at
> the Yokohama IETF last November.  So you'll need a stronger argument
> than "it's overkill for me" if you want to change that.
> 
> --
> JINMEI, Tatuya

v2.27.8 | Report a Bug | By Email | System Status