Re: [dhcwg] Follow up from IETF-95 - draft-ietf-dhc-dhcpv6-prefix-length-hint-issue

Ted Lemon <mellon@fugue.com> Thu, 21 April 2016 18:33 UTC

Return-Path: <mellon@fugue.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 2E96012E578 for <dhcwg@ietfa.amsl.com>; Thu, 21 Apr 2016 11:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 2zWGMjRrBZsm for <dhcwg@ietfa.amsl.com>; Thu, 21 Apr 2016 11:33:33 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 EDD8112E304 for <dhcwg@ietf.org>; Thu, 21 Apr 2016 11:33:28 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id j11so65986743lfb.1 for <dhcwg@ietf.org>; Thu, 21 Apr 2016 11:33:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=oLCiBGKXgJ2e8RbmYM/M2sHb5tWGyCYCm+qWlZXGJrM=; b=jlhmXwbdQBVuVdi0DfvkUVJcT3iWjiA2Brps2LoQk162H4wZy+ihrdu+qmPnXx1F9n H2ty3uOjTaQwXq9hPwVmepJROyjM4ETodD7YD+FxTwgs2CGVrTL67Y3P8Vse1Kyrhfpf E6NFtdZT8mY9hY4z1AGV9dIfMbjiU5NqYT26W8ik4X9byJYlQGjC5BcFkBPBC6u5DIWj HFdaLn6etO1+SSYBeDoMR6kKO9bEye4SrtFdYA6ocI7cmUQv5sgnuvrm9wyDRUkuJj1V cx4Wd4DfbIRkG3GSeKeWWpPvO1n3EqcpQWrT0KV2+AiAJDDsrRB0xbGQ8ojj/ZZ4n8xO T1yw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=oLCiBGKXgJ2e8RbmYM/M2sHb5tWGyCYCm+qWlZXGJrM=; b=drPftZFj77iW3rEk2BFa1rFjPJSMSbBvHvFBdn6Z6uiGQiRbzwAAACtcL7yNY4skpT BS5+EcWgwKQ0TqvWu8xBBO9BEonih93EaJPJx0Y63wWegbzK2WWSU6TQE9CjW/aWR9pH yg5EbXP2b49xcUvDJbHSRZkefvENCG4XJA1Z9Ekilyi7eNUFf70uMQwHGuTUmXUoMlBk Q/qMa9kwiUAMHU6OkFoLBB0C9uMH673gCiI1jyDF51rVxcr42I9KKgMVg5SWTS6acMST qKmbrT/D0blcirB5E2t6AfHIwJaRl4QfwYeEsrgrqFwax+9v2rzIPHqj+xCb+j3lwXNC EkrQ==
X-Gm-Message-State: AOPr4FWHnVxMckAAix6nE60TjJZxWky3XrlCpCee49HS0qou2j75KA4xlc5qrdDLn7LYFefK/r/AxaSwcwrY/Q==
X-Received: by 10.25.85.210 with SMTP id j201mr6062167lfb.132.1461263607111; Thu, 21 Apr 2016 11:33:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.213.19 with HTTP; Thu, 21 Apr 2016 11:32:47 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <DE53D859-B436-4F5B-A475-BA27B9AF8359@employees.org>
References: <0a8817dba2ea46c88ca67334a11c956d@XCH-ALN-003.cisco.com> <DE53D859-B436-4F5B-A475-BA27B9AF8359@employees.org>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 21 Apr 2016 14:32:47 -0400
Message-ID: <CAPt1N1mODQYscemGNoicjiFa6sKdKeYrpBkVNjbHhDERC-7hNA@mail.gmail.com>
To: otroan@employees.org
Content-Type: multipart/alternative; boundary="001a1141d82639cab7053102f283"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/W2iRGULHFxS1DHwoGrX3U6d_oVA>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] Follow up from IETF-95 - draft-ietf-dhc-dhcpv6-prefix-length-hint-issue
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Apr 2016 18:33:38 -0000

Ole, the point is that if the document makes any normative statements, it's
got to be standards-track.   You are quite right that the particular
statements you call out should not be made normatively, though!

On Thu, Apr 21, 2016 at 2:28 PM, <otroan@employees.org> wrote:

> there are some parts that could be made normative, like section 2.5.
> but most of the document appears informational in nature.
> paraphrased example: "the server should delegates a /48 if the client
> requests it".
> that's clearly policy, and a matter of the possible commercial
> arrangement, seems strange if the IETF should try to codify that.
>
> I lean towards informational.
>
> the document also does not say anything about _how_ the client is supposed
> to figure out what sized address block to request.
> if the answer to that is manual configuration, then there are tens of ways
> that could be done differently out of band.
>
> cheers,
> Ole
>
>
>
> > On 21 Apr 2016, at 18:45, Bernie Volz (volz) <volz@cisco.com> wrote:
> >
> > Hi:
> >
> > One item that was raised at the IETF-95 DHC WG session was the recent
> change (suggested by me before
> draft-cui-dhc-dhcpv6-prefix-length-hint-issue-02 was published) to switch
> draft-ietf-dhc-dhcpv6-prefix-length-hint-issue to Informational rather than
> Standards Track. Marcin Siodelski suggested that the document be Standards
> Track:
> >
> > The brief (draft) minutes for this discuss are:
> >
> > ---
> > 5. DHCPv6 Prefix Length Hint Issues, Bernie Volz (for Tianxiang Li) - 10
> minutes, 14:50
> >     draft-ietf-dhc-dhcpv6-prefix-length-hint-issue
> >
> >     The authors believe work is ready for WGLC.
> >
> >     Ian: Is this now informational? "This is the suggested way to do it"?
> >     Bernie: Correct. There were some discussions and the conclusion was
> to not
> >        enforce it.
> >     Marcin (on jabber): I'd suggest this is standards track doc with
> normative language
> >        in. Otherwise implementations will ignore hints.
> > ---
> >
> > Once we resolve this open question (and after a possible update to the
> document), we intend to start a WGLC on the document.
> >
> > Please respond with your comments as to whether this document should be
> Informational or Standards Track by May 5th, 2016. Of course, any other
> comments are welcome as well!
> >
> > Thanks!
> >
> > -          Tomek & Bernie
> > _______________________________________________
> > dhcwg mailing list
> > dhcwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/dhcwg
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>