Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-tunnel-01.txt

"Bernie Volz (volz)" <volz@cisco.com> Mon, 13 August 2012 14:35 UTC

Return-Path: <volz@cisco.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 0228721F8683 for <dhcwg@ietfa.amsl.com>; Mon, 13 Aug 2012 07:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.549
X-Spam-Level:
X-Spam-Status: No, score=-10.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nDSLLEW505vk for <dhcwg@ietfa.amsl.com>; Mon, 13 Aug 2012 07:35:54 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 482F621F8611 for <dhcwg@ietf.org>; Mon, 13 Aug 2012 07:35:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=1471; q=dns/txt; s=iport; t=1344868554; x=1346078154; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=8Mp1AVw/S57UKXzyfg7RTW5r8bAbDS3IJFmUiB1v0A0=; b=MWpANXaB5WEOyFcAsjIkmPs/hMhLBZk+upqf25sGwuPf1XOfZLWHwZxu J/HDLdBJGvIldkOASTPi0UG84ED1n+Kr5Yyf212hqpl70VWi4wTqWVUeK h+ISz4pieUkZFWuL4HPBQ+rGgJepr1v06BiGbiRIf9+vJG7oVfSZU86/z 8=;
X-IronPort-AV: E=Sophos;i="4.77,759,1336348800"; d="scan'208";a="111023630"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP; 13 Aug 2012 14:35:52 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id q7DEZqCo018867 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Aug 2012 14:35:52 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.159]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0298.004; Mon, 13 Aug 2012 09:35:52 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, dhc WG <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-tunnel-01.txt
Thread-Index: AQHNdvWqSDMOAnuzpUmlatl1eCUEGJdX0gXA
Date: Mon, 13 Aug 2012 14:35:51 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E0F4EA3B4@xmb-rcd-x04.cisco.com>
References: <4D779082-B182-4728-9534-39456573682E@nominum.com>
In-Reply-To: <4D779082-B182-4728-9534-39456573682E@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.248.186]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19108.006
x-tm-as-result: No--33.190700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ot@cisco.com" <ot@cisco.com>
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-tunnel-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 13 Aug 2012 14:35:55 -0000

I am OK with advancing this.

A few nits:

- In section 1:

  The source tunnel end-point often need more configuration data for

I think need should be needs here.

- In section 3, "CE" and "BR" are not defined and should be the first time used (or perhaps a terminology section is appropriate).

Also, while relaying the packet seems like a fine idea, it might be useful to indicate what the relay should use for a peer-address in the Relay-Forw message. It is all 0's? (Normally the client's link local address would be stored there.)

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Friday, August 10, 2012 8:43 AM
To: dhc WG
Subject: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-tunnel-01.txt

The authors of this draft have requested a working group last call.   The draft explains how DHCP clients operate in an environment where the interface being configured doesn't support multicast (e.g., 6RD).   If this is a matter of interest to you, please review the draft and send comments to the list.

If you are in favor of advancing the draft, please say so on the list; if nobody supports it, it won't advance.   If you oppose advancing it, please also say so.   We will determine consensus on August 24.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg