IETF Logo Mail Archive

[dhcwg] Fwd: New Version Notification for draft-cui-dhc-dhcpv6-prefix-length-hint-issue-00.txt

tianxiang li <peter416733@gmail.com> Tue, 07 July 2015 13:40 UTC

Return-Path: <peter416733@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 7E0731A036B for <dhcwg@ietfa.amsl.com>; Tue, 7 Jul 2015 06:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 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, SPF_PASS=-0.001] autolearn=no
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 vuNree135j9G for <dhcwg@ietfa.amsl.com>; Tue, 7 Jul 2015 06:40:12 -0700 (PDT)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (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 750FB1A026E for <dhcwg@ietf.org>; Tue, 7 Jul 2015 06:40:11 -0700 (PDT)
Received: by lagx9 with SMTP id x9so195642473lag.1 for <dhcwg@ietf.org>; Tue, 07 Jul 2015 06:40:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=BxDxIO0xh/JvFHXs2qUJZcYad+c1MkySDInuGqAyVSI=; b=vqt1LLLd0/MHmH3qp9TOkNMErBx40yq5MRPql0JbJsIx6IYu1Qav+JINM5j85R9H1I AH9MXEJGxh/UhdR14CaKA5h2ve8/+/a5HlLLIWPE0FnnzeNuoLEw4m9Riy68642trA6R 977+MRJhJFHtaGqVvRt9Lp/6CFgkBVrahrwav66zUj80hZTZKygNPxGXhCKJT0Kr/ofD oHRHk+TVs3CoEhn3TQrhYQhK/vzcpCKGnUgvPj31/2VOv3cs3dhN5Fh5y8Dw1qJvH2Lv tSSmS0eSBhvPFbApRt+DgIkb8tQZlLXvALyX5a7212g1hK95t6QM/e+RAaz+BCNFDXQ5 GVtw==
MIME-Version: 1.0
X-Received: by 10.152.87.97 with SMTP id w1mr4168070laz.124.1436276409791; Tue, 07 Jul 2015 06:40:09 -0700 (PDT)
Received: by 10.25.165.74 with HTTP; Tue, 7 Jul 2015 06:40:09 -0700 (PDT)
In-Reply-To: <20150706121444.25867.9398.idtracker@ietfa.amsl.com>
References: <20150706121444.25867.9398.idtracker@ietfa.amsl.com>
Date: Tue, 07 Jul 2015 21:40:09 +0800
Message-ID: <CAFx+hEPdO98t+PQXD+b5K3FFSd9q_G3J0Ch+eEN1pFEP7eYaww@mail.gmail.com>
From: tianxiang li <peter416733@gmail.com>
To: dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="001a11c33dde347a83051a4929d4"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/bcBhS7Hmq7Dh3QKbG6HshIyJNMo>
Subject: [dhcwg] Fwd: New Version Notification for draft-cui-dhc-dhcpv6-prefix-length-hint-issue-00.txt
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: Tue, 07 Jul 2015 13:40:13 -0000

Hi all,

We have submitted a new draft providing a summary of the existing
problems with the prefix length hint and guidance on what the client
and server could do in the different situation involving the the
prefix length hint.


The document might not cover all of the existing issues with the
prefix length hint, and we hope you can provide your valuable
suggestions to make the document more complete. We proposed some
possible solutions, but they're not perfect, and we'd really
appreciate any comments on how it could be improved.


Comments and reviews are appreciated.


Best Regards,
Tianxiang Li

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: 2015-07-06 20:14 GMT+08:00
Subject: New Version Notification for
draft-cui-dhc-dhcpv6-prefix-length-hint-issue-00.txt
To: Cong Liu <gnocuil@gmail.com>, Yong Cui <yong@csnet1.cs.tsinghua.edu.cn>,
Tianxiang Li <peter416733@gmail.com>



A new version of I-D, draft-cui-dhc-dhcpv6-prefix-length-hint-issue-00.txt
has been successfully submitted by Tianxiang Li and posted to the
IETF repository.

Name:           draft-cui-dhc-dhcpv6-prefix-length-hint-issue
Revision:       00
Title:          DHCPv6 Prefix Length Hint Issues
Document date:  2015-07-06
Group:          Individual Submission
Pages:          9
URL:
https://www.ietf.org/internet-drafts/draft-cui-dhc-dhcpv6-prefix-length-hint-issue-00.txt
Status:
https://datatracker.ietf.org/doc/draft-cui-dhc-dhcpv6-prefix-length-hint-issue/
Htmlized:
https://tools.ietf.org/html/draft-cui-dhc-dhcpv6-prefix-length-hint-issue-00


Abstract:
   DHCPv6 Prefix Delegation [RFC3633] allows a client to set a hint
   value in the prefix-length field of the IA_PD option to indicate a
   preference for the size of the prefix to be delegated, but is unclear
   about how the client and server should act in different situations
   involving the prefix length hint.  This document provides a summary
   of the existing problems with the prefix length hint and guidance on
   what the client and server could do in the different situation
   involving the the prefix length hint.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

v2.23.0 | Report a Bug | By Email