IETF Logo Mail Archive

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

Sheng Jiang <jiangsheng@huawei.com> Tue, 28 October 2014 02:45 UTC

Return-Path: <jiangsheng@huawei.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 997F11A1B74 for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 19:45:33 -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 BqzWc-V2WcPP for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 19:45:32 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5AD21A1B60 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 19:45:31 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOC63065; Tue, 28 Oct 2014 02:45:30 +0000 (GMT)
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 28 Oct 2014 02:45:13 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.22]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Tue, 28 Oct 2014 10:45:05 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.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: AQHP8ieJJUcfEK8wIkyxJXJN27K0dpxEsZ9Q
Date: Tue, 28 Oct 2014 02:45:05 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com> <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/t4RXqiuWg9OHaWHpEKBsjn327o0
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 02:45:33 -0000

>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.

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