Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv6-prefix-length-hint-issue (Ends January 8, 2016)

Marcin Siodelski <msiodelski@gmail.com> Thu, 17 December 2015 12:50 UTC

Return-Path: <msiodelski@gmail.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 817671A1DE1 for <dhcwg@ietfa.amsl.com>; Thu, 17 Dec 2015 04:50:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 drGgPOMHZ4d7 for <dhcwg@ietfa.amsl.com>; Thu, 17 Dec 2015 04:50:51 -0800 (PST)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A660D1A1C02 for <dhcwg@ietf.org>; Thu, 17 Dec 2015 04:50:50 -0800 (PST)
Received: by mail-wm0-x235.google.com with SMTP id l126so20130533wml.1 for <dhcwg@ietf.org>; Thu, 17 Dec 2015 04:50:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=fZkgGQZCwlhGdABnOBa7NtscUyzSxETxELNFGcI5eLU=; b=n+ns8ZBzeguHdEY098U6y0m69h2itHwh6Wxy9hkI9PqveOTWlIsI2z2u+LVTCIje1R MvqJSMeWQIJwYPyY38Ay6+EiraAjP/r4w4WlrJ5PlSVAA2xG4R6YH+USz/fKzm/TDN+O 5/ytZYxf3XgjRM1oJJVWXvPlcaOCz2XrgvlXijbilBAcW1wQLI5bZ0+0YNbV+YuvFBsu vzla54NEcBY/LTN0TDi8pCegJfxgNc+gEVOLBh25cVb0BxjRC//SC3qKEhDn3B4IqSKw tls/QbRbP8Jpi7tPLkAzpIuLrHCs0pICXUQ+xZaGccWY9MN0EBSRHGxAy2dYXsYy6Qxi sdeQ==
X-Received: by 10.28.145.144 with SMTP id t138mr4172840wmd.62.1450356649260; Thu, 17 Dec 2015 04:50:49 -0800 (PST)
Received: from MacBook-Pro-Marcin.local (89-79-26-47.dynamic.chello.pl. [89.79.26.47]) by smtp.googlemail.com with ESMTPSA id wl10sm555857wjb.27.2015.12.17.04.50.48 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Dec 2015 04:50:48 -0800 (PST)
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <ece35e634c91412e86004506b89477c7@XCH-ALN-003.cisco.com>
From: Marcin Siodelski <msiodelski@gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5672AF9E.5060905@gmail.com>
Date: Thu, 17 Dec 2015 13:50:38 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <ece35e634c91412e86004506b89477c7@XCH-ALN-003.cisco.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/FV8s9I3g1FtLX-RtMlksB5uxzho>
Subject: Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv6-prefix-length-hint-issue (Ends January 8, 2016)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 17 Dec 2015 12:50:52 -0000

Hello,

I support adoption of this document. I am iffy whether it should be an
Informational document. It provides pretty consistent description of
requesting/delagating routers' behaviors with respect to prefix length
hint and the motivation was that RFC3633 is "unclear" or "silent" about
it. We also considered integrating it into RFC3315bis, which makes it a
natural candidate for being standards track document. If we don't want
to create an impression that implementations/deployments must
unconditionally follow this behavior we could maybe state something
along the lines: "if the delegating router is configured to honor the
prefix hint..." etc.

Anyway, once again I support adoption of this document. Thanks to the
authors for doing this work.

Marcin

On 16.12.2015 19:45, Bernie Volz (volz) wrote:
> Hello:
> 
>  
> 
> This email initiates a WG call for adoption of the
> draft-cui-dhc-dhcpv6-prefix-length-hint-issue-03
> (http://tools.ietf.org/html/draft-cui-dhc-dhcpv6-prefix-length-hint-issue-03)
> document as a DHC WG work item.
> 
>  
> 
> Please indicate whether you support the adoption or not, and if not, why
> not. See https://tools.ietf.org/html/rfc7221#section-2.2 if you have
> questions about the criteria for adoption. This document falls within
> the WG Charter (https://datatracker.ietf.org/wg/dhc/charter/) under
> items #2, #3, and #4.
> 
>  
> 
> There are currently NO IPR claims against this draft (please see
> http://datatracker.ietf.org/wg/dhc/documents/ as this could change at
> any time).
> 
>  
> 
> The co-chairs will determine the consensus after January 8, 2016. (This
> is a longer period than usual because of the year end Holidays.)
> 
>  
> 
> Happy Holidays & New Year!
> 
>  
> 
> -          Tomek & Bernie
> 
>  
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>