Re: [dhcwg] Follow up from IETF-95 - draft-ietf-dhc-dhcpv6-prefix-length-hint-issue
Ted Lemon <mellon@fugue.com> Thu, 21 April 2016 16:50 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 A2C7312E472 for <dhcwg@ietfa.amsl.com>; Thu, 21 Apr 2016 09:50:02 -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 ai7KbbY5yU4e for <dhcwg@ietfa.amsl.com>; Thu, 21 Apr 2016 09:49:59 -0700 (PDT)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (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 9FD2812E39F for <dhcwg@ietf.org>; Thu, 21 Apr 2016 09:49:56 -0700 (PDT)
Received: by mail-lb0-x229.google.com with SMTP id b1so26807961lbi.1 for <dhcwg@ietf.org>; Thu, 21 Apr 2016 09:49:56 -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=EXR20Bhhj9UPrvJ5/mwfpsVqlPvTTIqxvdb/WJgCgjM=; b=VHDXv1UBMa0vF/S194dlTs/JPlxbOeSs1x9vXPLkcLb60G3Dp68BxqUDLca4qopBbs d0Igru6dIKAvBmx3GZb4BIuCezM+tQedsLJB6uhR+M8gA3UdE3GKoWd8oLV/eNmT290e 6xQYxRw9B6L3Q4SspNo9PXiC+4329euttLpNciYQow3mhJlHCnyaolcZgo5kQHLPsYrg 5CBapnnatp+3gm8EHcgx/IrHK20yTBxgfTW6hIOtezu8S4GaWm63pIFRbJ/ZlvsfVTtN QeTz2H5RrIGQYwu+V/cD2H4DC+Csw53Gf1gMoIMM+uWlX1Jqzj1Fx3BrlrgqIy+uT+op D6oQ==
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=EXR20Bhhj9UPrvJ5/mwfpsVqlPvTTIqxvdb/WJgCgjM=; b=mVox0dN1yOArQ33s6amDakePW4AW63K1dm1DPxIgQPACYcMSozNdrTsB/JvCAat0ww ZVYawWmUXGkXdSEYMDOrdRxTW5KUstsBQlWQmNzRw81/hETOJiMV2QObvFtNPqwfP7eV wCNOciYXF2fCVNo95ZLA5ufK8kKyP5rlxi2+YD8vSdbfukPI0M8miLkf0MLbrs+cp6hI WMWRKKQufMAuctbAd/LadoUHIQcy4PQMxa8xcOC0Dxs1v8x0YRuzW31Fsm1o/Ea5sjZy YnhoGuCSQ8gw3n4Q/5Z0BYA8dA7MJGmfwEoKLEgDS/E5U8+oNq7jBHvsHb3weFwMZD42 tTZA==
X-Gm-Message-State: AOPr4FVcqrYHOdyz5Wi+Vmq81pZHAiuhXk2nvv/6dUN/bGGNpznabqNLhZiXqEp593PwJzNXe1+bXviXcEAgPw==
X-Received: by 10.112.13.8 with SMTP id d8mr6776831lbc.110.1461257394673; Thu, 21 Apr 2016 09:49:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.213.19 with HTTP; Thu, 21 Apr 2016 09:49:15 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <0a8817dba2ea46c88ca67334a11c956d@XCH-ALN-003.cisco.com>
References: <0a8817dba2ea46c88ca67334a11c956d@XCH-ALN-003.cisco.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 21 Apr 2016 12:49:15 -0400
Message-ID: <CAPt1N1=bd8QWBpV7=v74-KV-1LMg-RA4d_UfJJrsPA0048rjsw@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary="001a11c3b44eef76580531017fd3"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/e7AFwHevEN8imsmGtzbr0C6ZC0s>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
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 16:50:02 -0000
I think it's normative. On Thu, Apr 21, 2016 at 12:45 PM, 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] Follow up from IETF-95 - draft-ietf-dhc-d… Bernie Volz (volz)
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Ted Lemon
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Francis Dupont
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Marcin Siodelski
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Francis Dupont
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Ted Lemon
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… otroan
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Ted Lemon
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… otroan
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Bernie Volz (volz)
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Ted Lemon
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Bernie Volz (volz)
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Ted Lemon
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Ian Farrer
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Francis Dupont
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… yogendra pal
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… tianxiang li
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… 神明達哉
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… tianxiang li
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… 神明達哉
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Bernie Volz (volz)
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… 神明達哉
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Bernie Volz (volz)
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… 神明達哉
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… H. Peter Anvin
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… tianxiang li
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Bernie Volz (volz)
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… H. Peter Anvin
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Ted Lemon
- Re: [dhcwg] Follow up from IETF-95 - draft-ietf-d… Bernie Volz (volz)