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

tianxiang li <peter416733@gmail.com> Tue, 26 July 2016 12:41 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 C428012D7C4 for <dhcwg@ietfa.amsl.com>; Tue, 26 Jul 2016 05:41:23 -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 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 u3CANONQOw0E for <dhcwg@ietfa.amsl.com>; Tue, 26 Jul 2016 05:41:22 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::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 1C50012D0C4 for <dhcwg@ietf.org>; Tue, 26 Jul 2016 05:41:22 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id f6so17505204ith.0 for <dhcwg@ietf.org>; Tue, 26 Jul 2016 05:41:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=A7oA5Xae3c+5+55DiKwvNe9/rZ+i+5EOxkkMpxjA3AM=; b=b3l7sGPp6Q/KpWOHAWmOkspZFTwO4g2bLbK5lcR+fz4gGDWLiVIjrmCsKSIGElQy9W PIEQj9U6Vjrr+V7cHisN0XH+lgT092VZZfJUznGrXkekqVInE3FhV9HOqQXEgZpopT1Z 31yNJts+jDg4PCip734EGwgvINWqta77OLmtE1xKKyUm3FOOSco2A0E3PO8pnxr2dg1J PvkJnXw77SMAs2kIj0zpUXoDGGn72hwuKgpQ9YD4x+fq1oYCOXHF6CmdXNWuSLzCcKn5 K5BpIWttwYMK6PvUq3cF1FvNqo8fH7gYkcxF6DeV8080BBz3y4ZW9GTqlJBeVDGr+i1S jEOw==
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; bh=A7oA5Xae3c+5+55DiKwvNe9/rZ+i+5EOxkkMpxjA3AM=; b=UBQC80FVid5VaXaycYjMuYjnnf+GnJZCdPbOghlRSelenvzaVHWcvVdAlGcwPfr9zL fGZ7vAjctkLVpZ7zZkEG4vNE7sEmJiT6XKDUclm/E6dlc4a3Toh+UiONxw410av350kN 63vlcKbGt5LZgYxaMOTHQfSrb+K46YDthy7VeuJcOISOwAL6XdOJoH3ubNrM5Za4GllM i/A3spxv1KoaAe2lnXtPDJEcLhnw1HUsnaUpr6tYWySLYNgfp0/Jx+HdCGKugOm3zMVb y0brvLPutdNC7b6rX4YZ9MMAThVBXMA2C+sBB4GqNq8cCRgDmEscHYOJn3OCrSf8GWwK u6Vw==
X-Gm-Message-State: AEkooutuuW6Ao4f3X/1Szxj9fqjNZU6KBF3BjL7tgagtLo2wcNl7PAwdabyYqT2haq8/+V3zRLCEz+2ra5D3Og==
X-Received: by 10.202.184.65 with SMTP id i62mr12598169oif.94.1469536881226; Tue, 26 Jul 2016 05:41:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.108.202 with HTTP; Tue, 26 Jul 2016 05:40:41 -0700 (PDT)
In-Reply-To: <20160726123452.8431.81249.idtracker@ietfa.amsl.com>
References: <20160726123452.8431.81249.idtracker@ietfa.amsl.com>
From: tianxiang li <peter416733@gmail.com>
Date: Tue, 26 Jul 2016 20:40:41 +0800
Message-ID: <CAFx+hEMo94Rt3+UfXnTiJRPm4_w80upmf+YrEkxjvfiYmpsHQg@mail.gmail.com>
To: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=001a113cd19aca374f0538893770
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/oHh_qAYAqMmoErTakBU5Qr-j2Vo>
Subject: [dhcwg] Fwd: New Version Notification for draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-03.txt
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: Tue, 26 Jul 2016 12:41:24 -0000

Hi all,

We updated a new version of the prefix-length-hint-issues draft (version
03) according to feedback form the ietf 96 meeting. The main changes are
listed below:

1. Changed sections 3.1 and 3.2 (Creation/ Receipt of Solicit message).
Adding the following actions for client, and the corresponding actions for
server.

-If the client wants a specific prefix, but would also prefer to accept a
prefix of specified length in case the requested prefix is not available,
it should send a Solicit message containing the prefix and a prefix-length
hint.

2. Added "General Recommendation" section (Section 3.6)

3. Removed text in section 1(Introduction) concerning lifetime hints, since
they are obsoleted in 3315bis.

4. Changed terms "requesting router/delegating router" to "client/server"
to be consistent with 3315bis

Best regards,
Tianxiang

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



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

Name:           draft-ietf-dhc-dhcpv6-prefix-length-hint-issue
Revision:       03
Title:          DHCPv6 Prefix Length Hint Issues
Document date:  2016-07-26
Group:          dhc
Pages:          9
URL:
https://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-03.txt
Status:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-prefix-length-hint-issue/
Htmlized:
https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-03
Diff:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-03

Abstract:
   DHCPv6 Prefix Delegation [RFC3633] allows a client to include a
   prefix-length hint value in 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 different situations.




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