Re: [dhcwg] Fwd: New Version Notification for draft-ietf-dhc-sedhcpv6-20.txt

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 15 February 2017 18:51 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 44A9B1295EE for <dhcwg@ietfa.amsl.com>; Wed, 15 Feb 2017 10:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 dTHj13RkTilQ for <dhcwg@ietfa.amsl.com>; Wed, 15 Feb 2017 10:51:33 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 EB80512954A for <dhcwg@ietf.org>; Wed, 15 Feb 2017 10:51:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v1FIpWoH051000; Wed, 15 Feb 2017 11:51:32 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1FIpQfm050861 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 15 Feb 2017 11:51:27 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 15 Feb 2017 10:51:26 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Wed, 15 Feb 2017 10:51:26 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] Fwd: New Version Notification for draft-ietf-dhc-sedhcpv6-20.txt
Thread-Index: AQHSglOjbTsgor1qYk63PeyrUa0poqFi1e9wgAgT1ID//3y08IAAjtcA//98D6A=
Date: Wed, 15 Feb 2017 18:51:26 +0000
Message-ID: <8549b0b78c2e47e1a1839133dbc5b73a@XCH15-06-08.nw.nos.boeing.com>
References: <148455739520.22478.14651605359463322132.idtracker@ietfa.amsl.com> <CAJ3w4NdCk8CBfNagcXT_VW_50+=xK=N7aB5HHqqn3stMt7Gy-Q@mail.gmail.com> <CAJE_bqf_AP9w1Bh_5kSB4YkLaV9XJ1tngufAiOMxVqQLwMruNA@mail.gmail.com> <aba52c11e462426bb3cbf66fcdca7783@XCH15-06-08.nw.nos.boeing.com> <CAJE_bqcG004FuUkKa0Xk1AiOo-bO4aHweYDpxMeeg+_=dSK6FQ@mail.gmail.com> <5c9ed55cfdc94456baf19740ba62910c@XCH15-06-08.nw.nos.boeing.com> <CAJE_bqeshAHmvGukto+PKs_skVPF5bnukvw8+5_04YEx_6m_sQ@mail.gmail.com>
In-Reply-To: <CAJE_bqeshAHmvGukto+PKs_skVPF5bnukvw8+5_04YEx_6m_sQ@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.136.248.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/VDS6rI58EXXpxiV-eJEJnTi8KLc>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Fwd: New Version Notification for draft-ietf-dhc-sedhcpv6-20.txt
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: Wed, 15 Feb 2017 18:51:34 -0000

Hi Jinmei-san,

> -----Original Message-----
> From: jinmei.tatuya@gmail.com [mailto:jinmei.tatuya@gmail.com] On Behalf Of ????
> Sent: Wednesday, February 15, 2017 10:33 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: dhcwg <dhcwg@ietf.org>
> Subject: Re: [dhcwg] Fwd: New Version Notification for draft-ietf-dhc-sedhcpv6-20.txt
> 
> At Wed, 15 Feb 2017 18:07:29 +0000,
> "Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:
> 
> > > It's probably better to describe the issue in
> > > sedhcpv6 with a reference to the RAAN draft as a possible future
> > > solution to it if and when it's adopted and standardized.
> >
> > If sedhcpv6 will not support an authentication-only mode, then it
> > can' t go forward until RAAN is adopted as a wg item. Otherwise,
> > an encryption-only sedhcpv6 w/o RAAN would break DHCPv6 PD.
> 
> I personally don't think it a blocking issue for sedhcpv6, but, of
> course, the wg should decide it.

Some uses of DHCPv6 PD require a secure exchange between the client and
server supported by an LDRA [RFC6221] that is in the same physical stack as
the server. The LDRA needs to peek into the server's Reply in order to discover
the delegated prefixes for the purpose of configuring routes. This all needs to
work with a standards-compliant DHCPv6 server that implements both
sedhcpv6 and RAAN. Meaning that sedhcpv6 and RAAN would need to be
advanced together as standards.

Maybe better yet would be to bring the RAAN option into the sedhcpv6
spec itself?

Thanks - Fred

> JINMEI, Tatuya