RE: on-link and off-link
Vasilenko Eduard <vasilenko.eduard@huawei.com> Mon, 12 July 2021 16:14 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 2D7A33A20A5 for <ipv6@ietfa.amsl.com>; Mon, 12 Jul 2021 09:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, 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 xDSMlFtPntf7 for <ipv6@ietfa.amsl.com>; Mon, 12 Jul 2021 09:14:42 -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 ADC813A20F0 for <ipv6@ietf.org>; Mon, 12 Jul 2021 09:14:39 -0700 (PDT)
Received: from fraeml741-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GNpPm2PRrz6BBD7; Tue, 13 Jul 2021 00:00:12 +0800 (CST)
Received: from msceml702-chm.china.huawei.com (10.219.141.160) by fraeml741-chm.china.huawei.com (10.206.15.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Mon, 12 Jul 2021 18:14:33 +0200
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml702-chm.china.huawei.com (10.219.141.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Mon, 12 Jul 2021 19:14:32 +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; Mon, 12 Jul 2021 19:14:32 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>, "ipv6@ietf.org" <ipv6@ietf.org>
CC: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: RE: on-link and off-link
Thread-Topic: on-link and off-link
Thread-Index: AQHXdyb7YXMuWgk+gkikqI5k+gcOz6s/dH1SgAADpuD//9ZSAIAANLxg
Date: Mon, 12 Jul 2021 16:14:32 +0000
Message-ID: <f4c17849b9b64be8aefba261c86e6d4b@huawei.com>
References: <162512790860.6559.14490468072475126698@ietfa.amsl.com> <CAFU7BAT0O9nsuhs5FyNjvPfRKY+EM1fLYKaMYTwaPg2QjZAEpA@mail.gmail.com> <61e14cd7-ff37-5380-e547-8a9b6d3993da@gmail.com> <CAFU7BASF-vas+PP2dVNXuqScQArC+joB-fwRGzG3UZnsqq1QJg@mail.gmail.com> <6A22DCF6-5132-44D3-AB45-E9C151376D2C@cisco.com> <6f6ab3f9-daa8-a468-1abc-f32a22497af2@gmail.com> <m1m2xiY-0000FNC@stereo.hq.phicoh.net> <3652d4977d7540469730c35c83e20d60@huawei.com> <CO1PR11MB4881F0E86ABF8AF04364D9A9D8159@CO1PR11MB4881.namprd11.prod.outlook.com>
In-Reply-To: <CO1PR11MB4881F0E86ABF8AF04364D9A9D8159@CO1PR11MB4881.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.202.93]
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/iPz4wtHJWMm_vZ6Q61BBaU8Rl5k>
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: Mon, 12 Jul 2021 16:14:47 -0000
By the way, It blocks not just native P2MP technology, It does break any filtering, like "PVLAN" or "WiFi isolation", Because if it is not possible to send a multicast to other hosts to check DAD even for LLA. Ed/ -----Original Message----- From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com] Sent: Monday, July 12, 2021 7:04 PM To: Vasilenko Eduard <vasilenko.eduard@huawei.com>; Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>; ipv6@ietf.org Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com> Subject: RE: on-link and off-link Exactly; the model at the IP layer has to be multilink subnet. Your link local gets you to a router but not to all in the subnet. With IPv6 all is abstracted with multicast operations and link local addresses. So what IP considers a link and who belongs to a subnet (is constrained by but) does not need to match what the L2 sees, e.g., the L2 links (e.g., an ethernet wire or a radio range) and the L2 broadcast domains (e.g., a 802.1 bridged domain or a Wi-Fi ESS). IPv4 gave the wrong habit of thinking they have to be congruent. They don't. Pascal > -----Original Message----- > From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Vasilenko Eduard > Sent: lundi 12 juillet 2021 17:35 > To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>; ipv6@ietf.org > Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com> > Subject: RE: on-link and off-link > > NBMA or P2MP are not supported by IPv6 anyway because it is not > possible to check LLA uniqueness - multicast does not work. > LLA proxy is needed on the hub site. > Ed/ > -----Original Message----- > From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Philip Homburg > Sent: Monday, July 12, 2021 6:20 PM > To: ipv6@ietf.org > Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com> > Subject: Re: on-link and off-link > > > I think one question > > might be: do we agree that each IP address is assigned on an > > interface, and thus is on-link on a particular link? > > This is not correct. On a NBMA link it is possible that all GUA > addresses are not on-link. > > The conceptual model of on-link is that a host can use neighbor > discovery to find an onlink neighbor. If the neighbor is not on-link > then traffic has to go (at least initially) through a default router. > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > --------------------------------------------------------------------
- Robert Wilton's No Objection on draft-ietf-6man-g… Robert Wilton via Datatracker
- Re: Robert Wilton's No Objection on draft-ietf-6m… Jen Linkova
- RE: Robert Wilton's No Objection on draft-ietf-6m… Rob Wilton (rwilton)
- Re: Robert Wilton's No Objection on draft-ietf-6m… Alexandre Petrescu
- Re: Robert Wilton's No Objection on draft-ietf-6m… Jen Linkova
- on-link and off-link addresses, side discussion Alexandre Petrescu
- Re: on-link and off-link addresses, side discussi… Simon Hobson
- Re: on-link and off-link addresses, side discussi… Alexandre Petrescu
- Re: on-link and off-link addresses, side discussi… Philip Homburg
- Re: on-link and off-link addresses, side discussi… Simon Hobson
- Re: Robert Wilton's No Objection on draft-ietf-6m… Wes Beebee (wbeebee)
- Re: why "is /64 [a] "default" prefix length when … Alexandre Petrescu
- Re: on-link and off-link Alexandre Petrescu
- Re: on-link and off-link Philip Homburg
- RE: on-link and off-link Vasilenko Eduard
- RE: on-link and off-link Pascal Thubert (pthubert)
- RE: on-link and off-link Vasilenko Eduard
- RE: on-link and off-link Pascal Thubert (pthubert)
- Re: why "is /64 [a] "default" prefix length when … Wes Beebee (wbeebee)
- Re: on-link and off-link Wes Beebee (wbeebee)
- RE: on-link and off-link Vasilenko Eduard