Re: draft-bourbaki-6man-classless-ipv6-00

"weigengyu" <weigengyu@vip.sina.com> Tue, 13 June 2017 03:38 UTC

Return-Path: <weigengyu@vip.sina.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D834D129B1D for <ipv6@ietfa.amsl.com>; Mon, 12 Jun 2017 20:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.48
X-Spam-Level:
X-Spam-Status: No, score=-1.48 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 YTleR_uebS2V for <ipv6@ietfa.amsl.com>; Mon, 12 Jun 2017 20:38:41 -0700 (PDT)
Received: from smtp-6-48.vip.sina.com.cn (r3-67.sinamail.sina.com.cn [202.108.3.67]) by ietfa.amsl.com (Postfix) with SMTP id 9D0D1129B18 for <ipv6@ietf.org>; Mon, 12 Jun 2017 20:38:39 -0700 (PDT)
Received: from unknown (HELO WeiGengyuPC)([114.255.40.2]) by vip.sina.com with ESMTP 13 Jun 2017 11:38:34 +0800 (CST)
X-Sender: weigengyu@vip.sina.com
X-Auth-ID: weigengyu@vip.sina.com
X-SMAIL-MID: 28117065620
Message-ID: <F0047D8F92074BC181C14E7B91602A70@WeiGengyuPC>
From: weigengyu <weigengyu@vip.sina.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: 6man WG <ipv6@ietf.org>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <91c3c0f4-eb8b-cdf7-b9c9-7d1eecb7fe64@gmail.com> <CAKD1Yr0_WR_TB+OC0U1Qt2h6WzUp9EGvrqC1ZKW2mwFeBd3bCQ@mail.gmail.com> <4021a559-5b6d-b3fb-19cd-afbe9041e8f2@gmail.com> <34A29D4D-3670-40BC-B62E-85C4EABC55D5@employees.org> <6e03e25e-fd6a-6311-390e-4834281a76f7@si6networks.com> <1B580CBB-B29D-4860-9EC8-BECD1D5E0006@employees.org> <4b2f5200-86a1-7711-e5ff-7436572be467@gmail.com> <E02C4C99-155A-4358-A845-F00F8BB071C1@employees.org> <b3ca5271-21b1-ab33-2dff-82735ebe9128@gmail.com> <235143da452c4ff4aec39a26ba918e7e@XCH15-06-11.nw.nos.boeing.com> <1489a50a-2616-f9ac-4109-16c595e15f90@gmail.com> <FA3032F9-F44B-45B4-9AFF-01EBC84F1448@employees.org> <b1c5c13d-ef69-ef30-546c-9178a2655caf@si6networks.com> <391c730c-fa75-7596-bb6b-383ea6583131@gmail.com> <f2ac9e0a467b4015a0a78d549c0fbbf0@XCH15-06-11.nw.nos.boeing.com> <a32c0313eeca44ff97e0c7c8b2daf2b6@XCH15-06-11.nw.nos.boeing.com>
In-Reply-To: <a32c0313eeca44ff97e0c7c8b2daf2b6@XCH15-06-11.nw.nos.boeing.com>
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
Date: Tue, 13 Jun 2017 11:38:34 +0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ccwG7_ajV0dPKcsobjiqYlpnCus>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jun 2017 03:38:44 -0000

Hi,

The flexibility of IID length will bring some benefits.
But, is there any compatible issues to concern?

For example, if two networks are assigned with two length IID in office and 
at home,
the host, such as mobile phone, pad or note PC must adapt to the different 
IID lengths.

Is it practical or available nowadays to have such adaptabilities.
Is it a required to have a default IID length, eg. /64 for the local link?
Should the default length be supported?


Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----原始邮件----- 
From: Manfredi, Albert E
Sent: Tuesday, June 13, 2017 10:30 AM
To: Brian E Carpenter
Cc: 6man WG
Subject: RE: draft-bourbaki-6man-classless-ipv6-00


I should add,

The IID length used by all SLAAC hosts on a link would be the same, because 
presumably, they all receive the same RAs. With the same RAs, their IIDs 
would have to come out to be the same length.

And, most of this change doesn't even apply to RFC 4862. For the most part, 
it applies to RFC 2464-bis. The main points of RFC 4862 remain the same.

Bert


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------