IETF Logo Mail Archive

Re: [dhcwg] Moving SeDHCPv6 forward

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 17 March 2015 16:54 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45FB11A877F for <dhcwg@ietfa.amsl.com>; Tue, 17 Mar 2015 09:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 6Qc4qh8YmPWU for <dhcwg@ietfa.amsl.com>; Tue, 17 Mar 2015 09:54:43 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCB921A875B for <dhcwg@ietf.org>; Tue, 17 Mar 2015 09:54:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t2HGshli029800; Tue, 17 Mar 2015 09:54:43 -0700
Received: from XCH-PHX-410.sw.nos.boeing.com (xch-phx-410.sw.nos.boeing.com [10.57.37.41]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t2HGsXLu029693 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 17 Mar 2015 09:54:33 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.229]) by XCH-PHX-410.sw.nos.boeing.com ([169.254.10.42]) with mapi id 14.03.0210.002; Tue, 17 Mar 2015 09:54:32 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: 神明達哉 <jinmei@wide.ad.jp>, Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [dhcwg] Moving SeDHCPv6 forward
Thread-Index: AQHQXfcgI7mJnKo7dkmrz3BXUKoeO50g6Zlg
Date: Tue, 17 Mar 2015 16:54:32 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E1F673@XCH-BLV-504.nw.nos.boeing.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923B05E058@nkgeml512-mbx.china.huawei.com> <CAJE_bqdPR-VScm02mx=nRm_j5Bv6+TF6QR=+=YSSrvZ5c9zTJg@mail.gmail.com>
In-Reply-To: <CAJE_bqdPR-VScm02mx=nRm_j5Bv6+TF6QR=+=YSSrvZ5c9zTJg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/6Y78igsi_eA8NY5jzcvjikz2XCw>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Moving SeDHCPv6 forward
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 16:54:45 -0000

Hi,

I want to use SeDHCPv6 to allow servers to authenticate clients. Please
tell me that the document will move ahead with that capability included.

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

> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of ????
> Sent: Friday, March 13, 2015 6:35 PM
> To: Sheng Jiang
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] Moving SeDHCPv6 forward
> 
> At Thu, 12 Mar 2015 04:58:07 +0000,
> Sheng Jiang <jiangsheng@huawei.com> wrote:
> 
> > The intense discussion regarding to the use case of SeDHCPv6 seems settle down for silent now. Do we reach a conclusion on how
> to move the draft forward? We can now work on an update version and submit it when reopen on next Sunday.
> 
> Sorry for the long delay, I've been unexpectedly busy for these
> several days...
> 
> Regarding the discussion, I don't think it settles down, but at least
> I've failed in my attempt of understanding why sedhcpv6-like approach
> is essentially needed for authenticating clients at the server other
> than for preventing a session hijack using a weak form of TOFU.
> 
> At this point I'm not sure if I can contribute to the document in a
> constructive way.  I'd first like to know if the wg in general thinks
> it's okay to ship without clarify the above "why", either because they
> simply don't see the need for it, or because it's only me who can't
> understand it.
> 
> --
> JINMEI, Tatuya
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

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