IETF Logo Mail Archive

Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 28 October 2014 14:56 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 333ED1A89E0 for <dhcwg@ietfa.amsl.com>; Tue, 28 Oct 2014 07:56:44 -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 y-ORhO4_9raD for <dhcwg@ietfa.amsl.com>; Tue, 28 Oct 2014 07:56:42 -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 A923C1A8A27 for <dhcwg@ietf.org>; Tue, 28 Oct 2014 07:56:42 -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 s9SEugW5011066; Tue, 28 Oct 2014 07:56:42 -0700
Received: from XCH-BLV-508.nw.nos.boeing.com (xch-blv-508.nw.nos.boeing.com [130.247.25.198]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s9SEuag9010553 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 28 Oct 2014 07:56:37 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.66]) by XCH-BLV-508.nw.nos.boeing.com ([169.254.8.95]) with mapi id 14.03.0210.002; Tue, 28 Oct 2014 07:56:36 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
Thread-Index: AQHP8r9eCYTydk8op0Cn7mdDfCs8pQ==
Date: Tue, 28 Oct 2014 14:56:35 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832D6E707@XCH-BLV-504.nw.nos.boeing.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com> <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com> <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/VuewKYWMND7VJBJT6oYBEEBWTJk
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
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, 28 Oct 2014 14:56:44 -0000


> -----Original Message-----
> From: Sheng Jiang [mailto:jiangsheng@huawei.com]
> Sent: Monday, October 27, 2014 7:45 PM
> To: Templin, Fred L; Bernie Volz (volz); dhcwg@ietf.org
> Cc: Zhangdacheng (Dacheng)
> Subject: RE: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
> 
> >I am quite fine with the Client trusting the Server by leap of faith. In the other
> >direction, I need some way for the Client to prove to the Server that it is the
> >authentic owner of the claimed Client ID.
> >
> >Does this new document version provide that?
> 
> Hi, Fred,
> 
> This version has provided a certificate-based mechanism for the client to authenticated by the server. It is assuming the client has a
> certificate honored by the server.

Right, I saw that but help me out here. If the client claims a DUID is the certificate
proof enough that the client is the authorized owner of the DUID?

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

> Best regards,
> 
> Sheng
> 
> >Thanks - Fred
> >fred.l.templin@boeing.com
> >
> >
> >---
> >From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz
> >(volz)
> >Sent: Sunday, October 26, 2014 3:11 PM
> >To: dhcwg@ietf.org
> >Subject: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3,
> >2014
> >
> >Hi all,
> >
> >This message starts the (short) DHC working group last call to advance
> >"Secure DHCPv6", draft-ietf-dhc-sedhcpv6-04, document as a Standards Track
> >(Proposed Standard) RFC. The authors believe that this version is ready. We
> >had a WGLC earlier (May 2014 for the -02 version) and there were some
> >comments, so this is primarily to assure that those comments were
> >addressed.
> >
> >The draft is available here:
> >http://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-04
> >
> >Please send your comments by November 3rd, 2014. If you do not feel this
> >document should advance, please state your reasons why.
> >
> >There are no IPR claims reported at this time.
> >
> >Tomek is the assigned shepherd for this document.
> >
> >- Tomek & Bernie
> >
> >_______________________________________________
> >dhcwg mailing list
> >dhcwg@ietf.org
> >https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email