RE: Interested in wireless ?

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 02 June 2020 12:04 UTC

Return-Path: <pthubert@cisco.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 DAAA13A03FF for <ipv6@ietfa.amsl.com>; Tue, 2 Jun 2020 05:04:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=N4sRyYaU; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=A7icxWY6
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 NAm02ZRcFgmA for <ipv6@ietfa.amsl.com>; Tue, 2 Jun 2020 05:04:34 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02FD93A03F6 for <ipv6@ietf.org>; Tue, 2 Jun 2020 05:04:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6594; q=dns/txt; s=iport; t=1591099474; x=1592309074; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=lYID1IdcNnaxndDYK7XFRNCRcBKtLjd2BMH8tqpF1C0=; b=N4sRyYaUSY+DekcnUi7tRwcrVhDtKVvgUfFor+9iienaaeND7Gtscxo+ iExbDIkrGpCrfilSVonvoKBv2O83xbPufx8VXVg4bM4806g+Me875YuG8 BTrLSp/GeZs+0feeystIwKFhvz3yiWzm8Xyx4fv3IvvCAqywG7JREpJDG o=;
IronPort-PHdr: 9a23:t6xw3R85XMkf+f9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+7ZRCN6vBkjVuPVoLeuLpIiOvT5qbnX2FIoZOMq2sLf5EEURgZwd4XkAotDI/gawX7IffmYjZ8EJFEU1lorH6+OElRXs35Yg6arni79zVHHBL5OEJ8Lfj0HYiHicOx2qiy9pTfbh8OiiC6ZOZ5LQ69qkPascxFjA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CzCQBUP9Ze/5FdJa1lHgEBCxIMQIMcUgdvWC8shCWDRgONRYl9jlCBQoEQA1ULAQEBDAEBGAsKAgQBAYREAheCAwIkOBMCAwEBCwEBBQEBAQIBBgRthVkMhXIBAQEBAwEBEBERDAEBLAwLBAIBCBEEAQEDAiYCAgIfBgsVCAgCBAESCBqDBYJLAy4BDqMtAoE5iGF2gTKDAQEBBYUwDQuCDgMGgQ4qgmSCS4cYGoFBP4EQRIJNPoIeSQEBA4EoPBUPgm4zgi2Oa4MMoRNMCoJYiDKLX4R9nhqQYIl2gk6NIIQWAgQCBAUCDgEBBYFqIoFWcBU7gmlQFwINkECDcoUUhUJ0NwIGAQcBAQMJfIw/AQE
X-IronPort-AV: E=Sophos;i="5.73,464,1583193600"; d="scan'208";a="489261914"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Jun 2020 12:04:32 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id 052C4VXC028474 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Jun 2020 12:04:31 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 2 Jun 2020 07:04:31 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 2 Jun 2020 07:04:31 -0500
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 2 Jun 2020 07:04:31 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IzNtEWa03GMmddO4F3KvQEXEXRE0AYJmeEKuZWB13K7q1dNFoNkRxDSnHRFBfITgbhKVTzIJcdTxI70HtdzgJAkoNMSEdzhF3oWHHeCTXypV8cyGrmI6HK30C5R9dyksXi5HEhbzJoYCzR7pmlFMnsFM5lvoZOS/wBs1V7ovTpUlsUArdnCw8HmTWvzm30zlQav/8frTa9n5kLlz6rAKa39SPG7+7a42uEluLZFxsTFQ5kw7DnVXuzFEC14gkEnB5JCeSBU5xI3XRiL8tRFll/zJkFednTNBtgyD5diHEZCRUB6O4n3GpOguW0Fz87ODYL6tigvLpB5Ucj4MVblpYA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lYID1IdcNnaxndDYK7XFRNCRcBKtLjd2BMH8tqpF1C0=; b=aI4Kp5PhRnaiONdUNPGV7adx4Q82mwrXmDUFX0u7ckV6Ahz5I5L5k9CbLUfc/ki2j0VXPoRJMeux3s3EVNVwCRbN6UnKV0t1W93Aq1EhnwIoEUcwCWEoXsUC+mgvuaKCkk2f4N2LbbCkHtDYfvzDlVh6xcIX+oB/PG69nBUT1Oci3/OWv2PWDhku29BjIv7ZUByT5wd62BFHdOM7YE+of/q9GH5JCnM2zwuzDPzdVIn/jCdHdvBwBeg0ylf7Y/tp/ZQMlAxk1Ty4PhmOpM7UxHvog5tivIzhzQgVty1hJXyKEldOSNIykaHh5I/Mnei26pZ01gP2h9oM+uYtnfo61w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lYID1IdcNnaxndDYK7XFRNCRcBKtLjd2BMH8tqpF1C0=; b=A7icxWY6SFTa+Yvjsinkszp0pQDILiwblixcfy8u45BIrpUwsXFGLhl4tM60cJvU7y2N6n82lkFzU6ujrC0iBY32U5mSVYxdQS3u9/W95+i61ysqoh29M/i3SA5ZF2O3+cQb8/NkXib7o3CoKaYV7lBcp/Za2Cs9cdRhObhbHJ4=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (2603:10b6:208:ea::31) by MN2PR11MB3872.namprd11.prod.outlook.com (2603:10b6:208:13f::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.19; Tue, 2 Jun 2020 12:04:30 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::55bb:b065:86c1:1108]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::55bb:b065:86c1:1108%6]) with mapi id 15.20.3045.022; Tue, 2 Jun 2020 12:04:30 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Interested in wireless ?
Thread-Topic: Interested in wireless ?
Thread-Index: AQHWNnfqX/nhVMuy1Ea+e7RI89I6LqjEJEEAgAABsICAANGH0IAARIeAgAAAazA=
Date: Tue, 02 Jun 2020 12:04:20 +0000
Deferred-Delivery: Tue, 2 Jun 2020 12:03:31 +0000
Message-ID: <MN2PR11MB3565DB1003B88B0E493DFAFBD88B0@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <A26FA9F8-72B8-4728-B978-6DDD271EC64D@cisco.com> <c0b383ce-9a86-dbe1-30a3-f96e7434c2a6@gmail.com> <ea3dd120-bdad-3ca3-2983-9605324f6e8e@gmail.com> <MN2PR11MB356569D4604334EA732FD796D88B0@MN2PR11MB3565.namprd11.prod.outlook.com> <1c0eb3da-829d-bfc4-00bd-b3f2e9675138@gmail.com>
In-Reply-To: <1c0eb3da-829d-bfc4-00bd-b3f2e9675138@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2a01:cb1d:4ec:2200:9954:9429:7a59:1ac1]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0cd6847e-d4fb-4679-dbb0-08d806ed1b0e
x-ms-traffictypediagnostic: MN2PR11MB3872:
x-microsoft-antispam-prvs: <MN2PR11MB38722B2DE981C0DB3FA923C3D88B0@MN2PR11MB3872.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0422860ED4
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 3JmPE7Eadjmkg7G+AFmXCEYOueK5AVgbDHNZaLt1PI+GEs6VkNmOyhvXKUMaR4c8TilUgypuradOUmCLGEHF4+Zt+KpNZvWOlrhML0N5wMRQ4w5BltD8gOydv5OniToZfQHmYJXCsghGnUdKsuPk6kaKTHbgHwSWTr69ngJzx60NCPWxRDWWnXU3jCByJSXl+4EVVbj69q1SwCotVOhTVMYnAzxfBZ7oQKEv2ls+f+K/OdsD6qBC81WyVuSbRddGU+5HhcgRxP4IoRNxfC1IW7Jp+2ZKGn3EUCGnnaZdIutdSluh8zAMTKHZAxC+0sdyeUcf9mTEzxlSH3VsIpWAv3NsEGHwBzcnhvWYhZczvWDZu1K2v7eXGqR3TbQ97hs/KajtuheCJG4/mXkWwe6dxg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR11MB3565.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(136003)(376002)(346002)(366004)(396003)(39860400002)(66574014)(55016002)(3480700007)(7696005)(6666004)(8936002)(9686003)(52536014)(83380400001)(8676002)(86362001)(7116003)(186003)(71200400001)(5660300002)(66946007)(33656002)(53546011)(6506007)(478600001)(66556008)(66446008)(76116006)(66476007)(64756008)(316002)(966005)(110136005)(2906002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: YGeYycNdDhLN4dOb7lBmloXw4369gMPt5GB97+kjJAkFLeTkuD5rNkdnN0IgLM9GpLeyHtC86ci7LD492FaygA/1Kc7Kc6cbQhCERaFb7PZBBkx/3jrZRwERwb/r0UaX2sZnNIXfQ2yV717f09k9iX4eciaQzPPOdOBY7EhwObAz/DRSaPbJraG/jIGeE0BuQQ0bwZeRWrerVPiJKopQiwY2xAvYEujXb/ccwLg4XxZK/6nsF1ym0SqVBgMB79i8NJV7B6+/8zNfhW/PALNQxtkgMSzCESdyDr+S/Vrys7UDK7CQS6HJYgu70yIcSnQx6xPmmwkUz652RGt7ftGebYPEqJgianmPRIdcExDj4d6dSxYpGDrovPm0KC+EiCDk+jlLMsuOuA1AGSIdIQ4rAmnKVVE2f6hMRK8YgPcMbaL3xc2rE8uMMbwzuKxitgeSRiNTmuJGSmukqJzGYiBFnQZJZDjV9GiRMBfIwTQz1vXlkv1JjGwrR6owez1HzKyfViDO4wOHqhxWc4viNm7jh9S7ksIoFBgvjYJA1sXFagJzPPXzu1dieB1cnE5+LQj3
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0cd6847e-d4fb-4679-dbb0-08d806ed1b0e
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jun 2020 12:04:30.2290 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 3SCzXkXchGfM5uU/Buxjz6J8puhXhgkY54TKjbMGGBwSygbhkusflf9nsg5fbYgjK3rKWftI8CvERgPuQ/YPNg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3872
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/sv60NVA6aS-wEqktSh51u93VWu4>
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, 02 Jun 2020 12:04:36 -0000

Hello Alex

There's a difference between the MAC address used (0x333300-blah) that is multicast and the effective processing by the network. 
For all I know, the IEEE multicast protocols are pretty much never deployed, and only the first bit that says broadcast is of actual interest.
IOW the IETF has thrown the problem of handling multicast for a large number of groups over the fence to IEEE.
The end result is a broadcast to all nodes. True on both IEEE std 802.3 and 802.11.

If you are aware of networks that are operated differently I'm all ears.

Keep safe,

pascal

> -----Original Message-----
> From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
> Sent: mardi 2 juin 2020 13:54
> To: Pascal Thubert (pthubert) <pthubert@cisco.com>; ipv6@ietf.org
> Subject: Re: Interested in wireless ?
> 
> Hello Pascal,
> 
> Le 02/06/2020 à 09:55, Pascal Thubert (pthubert) a écrit :
> > Hello Alex
> >
> >> -----Original Message-----
> >> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Alexandre Petrescu
> >> Sent: lundi 1 juin 2020 21:19
> >> To: ipv6@ietf.org
> >> Subject: Re: Interested in wireless ?
> >>
> >> draft says:
> >>>     To protect their bandwidth, some
> >>>     networks throttle ND-related broadcasts, which reduces the capability
> >>>     for the ND protocol to operate as expected.
> >>
> >> I suspect you mean ND-related multicasts, and not ND-related broadcasts.
> >
> > I meant ND-related MAC-layer broadcasts.
> 
> I think there are no MAC-layer broadcasts used by ND.
> 
> A MAC-layer broadcast is one that sends to ff:ff:ff:ff:ff.  That does not exist for
> ND.
> 
> Or maybe one means a PHY-layer broadcast?
> 
> Broadcast: casting broadly a message, like a fisherman casting a net, like in a
> TV broadcast.
> 
> Alex
> 
> L3 multicast turned in L2 broadcast.
> > But I see that the paragraph needs clarification, will do it for the next
> publication.
> >
> >
> >>
> >> Also, I guess that need to protect (maintain availability) bandwidth
> >> is different when more and more bandwidth is offered by a PHY/MAC in a
> terahertz range.
> >> Maybe these networks will stop throttling(?)
> >
> > I do not have a crystal ball for that. Look at Ethernet, now in the 100s of Gigs
> in the DC.
> > With the overlays and distributed cloud, the desire to eliminate broadcasts is
> more intense than ever.
> >
> > Keep safe,
> >
> > Pascal
> >
> >> Alex
> >>
> >> Le 01/06/2020 à 21:12, Alexandre Petrescu a écrit :
> >>> draft says:
> >>>>     The routers send RAs with a SLLAO at a regular period.  The
> >>>> period
> >>>>     can be indicated in the RA-Interval Option [RFC6275].  If
> >>>> available,
> >>>>     the message can be transported in a compressed form in a
> >>>> beacon,
> >>>>     e.g., in OCB Basic Safety Messages (BSM) that are nominally
> >>>> sent
> >>>>     every 100ms.
> >>>
> >>> I suggest to give CAM as an example as well, not just BSM.
> >>>
> >>> It might be that on some continent CAM is more important than BSM.
> >>>
> >>> It might be, that in an ideal world where all use Internet, there is
> >>> just one CAMBSM message, and maybe we get to that if we put it on IP.
> >>>
> >>> But until then, citing just BSM is not good enough.
> >>>
> >>> Alex
> >>>
> >>>
> >>> Le 30/05/2020 à 13:46, Pascal Thubert (pthubert) a écrit :
> >>>> Dear all
> >>>>
> >>>> Since there’s so much energy on the list these days, could we
> >>>> consider the adoption of
> >>>> https://tools.ietf.org/html/draft-thubert-6man-ipv6-over-wireless-0
> >>>> 5
> >>>> ?
> >>>>
> >>>> I got only positive feedback, there’s no politics, there no label,
> >>>> it’s all about IPv6 models for wireless. This may appear useful in
> >>>> a world where the vast majority of devices are connected that way.
> >>>>
> >>>> Keep safe,
> >>>>
> >>>> Pascal
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> - 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
> >>> --------------------------------------------------------------------
> >>
> >> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> ipv6@ietf.org
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >> --------------------------------------------------------------------