[dhcwg] Adding normative text into prefix-length hint issues draft

tianxiang li <peter416733@gmail.com> Mon, 23 May 2016 10:37 UTC

Return-Path: <peter416733@gmail.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 49E9F12D0D1 for <dhcwg@ietfa.amsl.com>; Mon, 23 May 2016 03:37:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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=gmail.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 ybHhYmmWapq2 for <dhcwg@ietfa.amsl.com>; Mon, 23 May 2016 03:37:02 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 28C6D12B022 for <dhcwg@ietf.org>; Mon, 23 May 2016 03:37:02 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id j1so32801455oih.3 for <dhcwg@ietf.org>; Mon, 23 May 2016 03:37:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=AlaxHqADkQz3La9OhirD2rmvnHys1Rjynfj5kKLBOug=; b=HRCjKeAPCupYWvvGvC851spaG+BsHEifHzqlHtsvJboayQxhRhZL1IdrlDPOfYqi3G EvmwHtWSI4pVTiHhoGT7yqXGy3TAkf8b3ij6V+mjjtWTDOmqgyfpfesYhfHXjPwgfcEr aQ4iJ2J8D1JLmm3726EnKdawvBEKiLFFywZMbyQKMni4phu/gg35pcL3k3DX0BLhU3Sf 1IwKkZZtGiTd0nLJNh+C5V6yuF/O1kmmpS0llYB0z4BMe5anFPDnHGmqvKIsg7IvZtHL 7VQdw4WkMZj/8j76qawoE9w/XQO0gAkmxc8KySRvHksajc/cM4QvaUb6NIOQGxloMWQT kPWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=AlaxHqADkQz3La9OhirD2rmvnHys1Rjynfj5kKLBOug=; b=Thn91CiZW46TF7x0/vc6qsD0+uHyujEKoa2G8cruLk5wbY592Mou3JhaoJ7v3a2P4o SD7qR3xCB5nsQ/Td/6gtHag3EFRIUNHCWKZKMjjENJffyr31krMNQMHRLj8eU6GilJVc N6yA8tfYlLPEVOldN80e4StyqOUaD2+K+Eap9WXqZ6RVwa5H+mLD2ISl4QUpv5ayHcVD 7acwKvrgZOQlSfGHiPSUzvnQf3HktCBh53WNGGuDs4J0qInfnsJZe38bGgq+GXvWQqdq UBOInH3RtBPV0caeExGtjFek8qjBzsZsegVy05VmNK99koyzBGo+JQut9CY/Puwxizn1 Ub6Q==
X-Gm-Message-State: ALyK8tKq4hhkMuBk9/8ToRqUhSNVsNRyCGXsq7O3ePNbztnvKFZSb7tpDOPpP4w/kBJr/QxtSJ9NAv/NmtPgNQ==
X-Received: by 10.202.221.214 with SMTP id u205mr1987892oig.94.1463999821560; Mon, 23 May 2016 03:37:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.4.87 with HTTP; Mon, 23 May 2016 03:36:22 -0700 (PDT)
From: tianxiang li <peter416733@gmail.com>
Date: Mon, 23 May 2016 18:36:22 +0800
Message-ID: <CAFx+hEP6Wh8SqERqB0dbnLD3pXSyB=vcwuNvaMbVDZhKc-ydXw@mail.gmail.com>
To: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=001a113d42c250c06d05338005a9
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/lKP5WagAv_Bi5JIyM497XlU6EmA>
Subject: [dhcwg] Adding normative text into prefix-length hint issues draft
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: Mon, 23 May 2016 10:37:03 -0000

Hi all,

We updated a new version of the prefix-length hint issues draft (version
01) with normative text added to the solution sections of the document.

There was a discussion about whether this document should be Informational
or Standards Track, and a temporary conclusion was to first add normative
text in and see how it looks. We appreciate your comments on whether the
normative texts added are suitable, and hope to reach a consensus for its
document type.

Thank you,
Tianxiang