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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Sun, 02 November 2014 21:32 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 AD0351ACE10 for <dhcwg@ietfa.amsl.com>; Sun, 2 Nov 2014 13:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.794
X-Spam-Level:
X-Spam-Status: No, score=-4.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] 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 A1V3WYM8-bDi for <dhcwg@ietfa.amsl.com>; Sun, 2 Nov 2014 13:32:51 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 080381ACE14 for <dhcwg@ietf.org>; Sun, 2 Nov 2014 13:32:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sA2LWoAW024562; Sun, 2 Nov 2014 13:32:50 -0800
Received: from XCH-PHX-209.sw.nos.boeing.com (xch-phx-209.sw.nos.boeing.com [130.247.25.29]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sA2LWhPA024095 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Sun, 2 Nov 2014 13:32:44 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.66]) by XCH-PHX-209.sw.nos.boeing.com ([169.254.9.170]) with mapi id 14.03.0210.002; Sun, 2 Nov 2014 13:32:42 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "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: Ac/xaWYb7j/iiP3ISmCf+ekbUUcpTQEojZ3wACXpeVAAFWaIgAAFJ0DQ
Date: Sun, 02 Nov 2014 21:32:42 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832D7700C@XCH-BLV-504.nw.nos.boeing.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B703F70@xmb-rcd-x04.cisco.com> <2134F8430051B64F815C691A62D9831832D76AAE@XCH-BLV-504.nw.nos.boeing.com> <489D13FBFA9B3E41812EA89F188F018E1B704F15@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B704F15@xmb-rcd-x04.cisco.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: multipart/alternative; boundary="_000_2134F8430051B64F815C691A62D9831832D7700CXCHBLV504nwnosb_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/EZfRyRvm_R2D-BbHR2x5z0XEE9k
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: Sun, 02 Nov 2014 21:32:53 -0000

Hi Bernie,

OK, I object to the removal of the client's ability to sign its messages with its own
private key (i.e., so that the server can verify the signature using the client's
public key). Let's talk about it at IETF91.

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

From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Sunday, November 02, 2014 7:58 AM
To: Templin, Fred L; dhcwg@ietf.org
Subject: RE: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014

Fred:

This document (and its predecessor) have had a long and rocky journey. It would be nice to finally wrap this up and move on.

If you have significant concerns or feel that functionality is not there that is needed (and couldn't be added later on by a follow-on document), please raise those issues now and on the WG Mailing List - there's little point in waiting until the WG session.


-          Bernie

From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
Sent: Sunday, November 02, 2014 8:47 AM
To: Bernie Volz (volz); dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: RE: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014

Hi Bernie,

Is there any reason this needs to be finalized before the IETF91 meeting? I am not
100% certain that the document meets my needs in its current form and was hoping
to have discussion on it at the end of my presentation.

Thanks - Fred
fred.l.templin@boeing.com<mailto:fred.l.templin@boeing.com>

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Saturday, November 01, 2014 12:41 PM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014

Just a reminder that this WGLC is in progress and feedback is needed by Nov 3.

Please participate and indicate your support, or lack thereof, for this document.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, October 26, 2014 6:11 PM
To: dhcwg@ietf.org<mailto: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