Re: [dhcwg] Mail regarding draft-ietf-dhc-dhcpv6-prefix-length-hint-issue

tianxiang li <peter416733@gmail.com> Tue, 26 July 2016 07:59 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 0F85812D675 for <dhcwg@ietfa.amsl.com>; Tue, 26 Jul 2016 00:59:59 -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 Y1p4EGJ-4xJr for <dhcwg@ietfa.amsl.com>; Tue, 26 Jul 2016 00:59:57 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 7DFE412D66E for <dhcwg@ietf.org>; Tue, 26 Jul 2016 00:59:57 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id b62so4608614iod.3 for <dhcwg@ietf.org>; Tue, 26 Jul 2016 00:59:57 -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 :cc; bh=aQbucEIsP0VWmIegCFeFZP3X09aJYMt3GpelcxytAQI=; b=V/qwQMC2Hp+K4Y9JaWP0Efm4tkknzedGzaR7354j7NT+jNBno6wYe8IoJ6KwKmP99r 6/i9Npc89fOLOvhAwalbSfiJmMvoRdMnwr905S59c/LFJLK6mElAgK4K5fsz4hXsKQGM jau2PnVlUedM2WBkcB3Pg9kPK7+PzVKXVrjv/gsS40gxpVvwQimvaq+mZOEc/brDUSq2 3RknsHLPry4tnGsJMBUdUZnib26AfGWPGtgvEXjk4Oi1vBiQT5okAHyLZ0p9Y88MtM4n 0d3hu7gV9FGz/1IDOts28tU9+pKIBxpQud0TbgrrvXthnEgmeuhh9KUlxONgJXA/W/qz B75g==
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=aQbucEIsP0VWmIegCFeFZP3X09aJYMt3GpelcxytAQI=; b=TQSRPhQVSMziShq5oRjmabHCMg/0AJPcprBlLl3n4FB53ft10NJaBj+SQIRdYjKS0J dpVYZDWNNUudV0GpaP4WRU3I+umgVQmZk5vt57kakn1IoupZV6e2fYgekFcn2N9z6ChH XlzFDIYYB3+HBlA0MpHrRUorsja/upn9+MWbEadzxPq9vpQDj/HpBwa/kshD5hSYI8vG J0jRA55ILpINf54+xaSyJxpZCBkngpzbv0wa5V4oO8FaG9SGDN6BIiCWChrviyBWkbhE aZ/dg4wrvrl6rC6EVX4ZGyFMYWH4/5qhvLIb6H7l2OezUMM80PBSYfmJVT+sYXfYJBMv PZiA==
X-Gm-Message-State: AEkoouv8xQaTyK3BKmPa7ynkUW9gUCjqlqhK92zxERy0l37WuorE5/ANySjXy5wGfogBbZbHjmIAAxTpg4oofA==
X-Received: by 10.157.39.130 with SMTP id c2mr11024307otb.181.1469519986813; Tue, 26 Jul 2016 00:59:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.108.202 with HTTP; Tue, 26 Jul 2016 00:59:07 -0700 (PDT)
In-Reply-To: <1c1b86809af74a77a1cfb9dffb0bbb5a@XCH-ALN-003.cisco.com>
References: <1c1b86809af74a77a1cfb9dffb0bbb5a@XCH-ALN-003.cisco.com>
From: tianxiang li <peter416733@gmail.com>
Date: Tue, 26 Jul 2016 15:59:07 +0800
Message-ID: <CAFx+hENXhvU8ckZnPZ_yYdjE9DPQsJ7d1AKhvuSERzyeUemC_A@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary=94eb2c04f840cdefb105388548f8
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/v6y6-9dfFtSbkg4tBsHqvccwmiE>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Mail regarding 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: Tue, 26 Jul 2016 07:59:59 -0000

Hi Bernie,

Thank you for the comments, we will update a new version of the draft very
soon.
During the ietf 96 meeting, comments were raised about changing the term
"requesting router / delegating router" to "client / server". Should we
change it in the updated version?

Cheers,
Tianxiang

2016-07-25 20:47 GMT+08:00 Bernie Volz (volz) <volz@cisco.com>om>:

> Hi:
>
>
>
> Here’s some comments related to the
> draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-02 version.
>
>
>
> Section 1:
>
> -          “as it just help a client” -> change help to helps?
>
> -          Same area, perhaps mention that 3315bis is dropping use of the
> lifetime hints?
>
> -          Later – “handle the prefixes which lengths are different” –
> “handle prefixes with lengths different from the prefix-length hint”?
>
>
>
> I wonder whether a “general solution” section should be added which says
> something like:
>
>
>
> “Therefore, the recommendation to address the issues discussed in this
> document, is for a client that wants (at least) to have a delegated prefix
> of a specific prefix length to always include an IAPREFIX option with just
> the prefix length hint in addition to any IAPREFIX options it has included
> for each IA_PD in any Solicit, Request, Renew, and Rebind messages it
> sends. While a server is free to ignore the hint, servers that do not
> choose to ignore the hint should attempt to assign a prefix of at least the
> hint length (or shorter) if one is available. Whether a server favors the
> hint or avoiding a renumbering event is a matter of policy for the server.”
>
>
>
> Note that this could actually be taken as one way to interpret the
> original RFC 3633 text, which said:
>
>
>
>    The requesting router may include prefixes in the IA_PDs as a hint to
>
>    the delegating router about specific prefixes for which the
>
>    requesting router has a preference.
>
>
>
> This text was as part of the Solicit discussion, but perhaps it was
> intended to apply to subsequent transactions as well (Request, Renew,
> Rebind).
>
>
>
> -          Bernie
>
>
>