RE: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt

Vasilenko Eduard <vasilenko.eduard@huawei.com> Tue, 18 May 2021 06:52 UTC

Return-Path: <vasilenko.eduard@huawei.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 E20543A0A73 for <ipv6@ietfa.amsl.com>; Mon, 17 May 2021 23:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 KAx2kdVOxs5W for <ipv6@ietfa.amsl.com>; Mon, 17 May 2021 23:52:30 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC6ED3A0A69 for <ipv6@ietf.org>; Mon, 17 May 2021 23:52:29 -0700 (PDT)
Received: from fraeml705-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FkmgC71rQz6wk3P; Tue, 18 May 2021 14:43:51 +0800 (CST)
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by fraeml705-chm.china.huawei.com (10.206.15.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Tue, 18 May 2021 08:52:22 +0200
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml703-chm.china.huawei.com (10.219.141.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Tue, 18 May 2021 09:52:21 +0300
Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.2176.012; Tue, 18 May 2021 09:52:21 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
Subject: RE: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt
Thread-Topic: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt
Thread-Index: AQHXS2dZ7FnKPTG8CUOTX/wP0AtrIKrox+1Q
Date: Tue, 18 May 2021 06:52:21 +0000
Message-ID: <bb96eda658624724aab6e6308ab9107b@huawei.com>
References: <162126274647.25711.8162789738375511264@ietfa.amsl.com> <32c96d37-a743-f0fa-c858-36333b102d2b@gmail.com>
In-Reply-To: <32c96d37-a743-f0fa-c858-36333b102d2b@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.197.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Kad6sWO6Mgnrt9VHsthGQZ213f4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 18 May 2021 06:52:34 -0000

Hi all,
Sometimes, IPv6 Links are connected into
a "single entity" (except from Proxy-ND RFC 4389) or
a Multi-Link Subnet (from RFC 8929) or
something without a name in the draft-ietf-bess-evpn-proxy-arp-nd-13

And then IP Prefix is attached to this structure.
It is not good that the IP prefix is attached to the structure that does not have the name!

There are 2 options here:
1. call it the "IPv6 link" too. Probably not good, because ND messages are not transparent between L2 domains in all such solutions.
2. give it the name. draft-thubert-6man-ipv6-over-wireless-09 proposes to call it MLSN. Why not?

On the broad scope, the IP prefix is attached not to the link, but to the entity at the next layer of hierarchy. It should be somehow reflected in standards.

PS: This is the biggest thing that I see in draft-thubert-6man-ipv6-over-wireless-09
Eduard
-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Brian E Carpenter
Sent: Tuesday, May 18, 2021 12:55 AM
To: 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-thubert-6man-ipv6-over-wireless-09.txt

Hi,

IMHO this draft now includes some important new material, namely definitions of two terms "IP Link" and "IP Subnet" (at https://www.ietf.org/archive/id/draft-thubert-6man-ipv6-over-wireless-09.html#name-terminology ). While I'm not sure yet that I completely agree with the text, I think the topic is very important, since the previous doctrine has effectively been that all "links" behave like Ethernet. And, by the way, the socket API incorporates that doctrine.

(This is something that gave us quite a lot of angst in ANIMA, especially in clarifying the "link" model in the Autonomic Control Plane, since we depend on link-local multicast.)

Regards
   Brian

On 18-May-21 02:45, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : IPv6 Neighbor Discovery on Wireless Networks
>         Author          : Pascal Thubert
> 	Filename        : draft-thubert-6man-ipv6-over-wireless-09.txt
> 	Pages           : 25
> 	Date            : 2021-05-17
> 
> Abstract:
>    This document describes how the original IPv6 Neighbor Discovery and
>    Wireless ND (WiND) can be applied on various abstractions of wireless
>    media.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-thubert-6man-ipv6-over-wireless
> /
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-thubert-6man-ipv6-over-wireless-
> 09.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-thubert-6man-ipv6-over-wireles
> s-09
> 
> 
> 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.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or 
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

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