IETF Logo Mail Archive

Re: [MBONED] [Ext] Re: ipv4 multicast address ranges, actual usage.

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Fri, 20 December 2019 00:15 UTC

Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37CE012004D for <mboned@ietfa.amsl.com>; Thu, 19 Dec 2019 16:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 5IEo8moGNTKd for <mboned@ietfa.amsl.com>; Thu, 19 Dec 2019 16:15:32 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 782FF120044 for <mboned@ietf.org>; Thu, 19 Dec 2019 16:15:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id xBK0FT1Y005082; Thu, 19 Dec 2019 19:15:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1576800929; bh=tX+zkQVvF13d29VTR89OOwKC9iuefUI0kz0RTRtr0dQ=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=SC/mtIiNGg5DmoMhsXg3gEQbEPPK3x1BllOvxCnJmwPcjvWf68XKD6LiEMpnQ4ZSV w2u7I0Zsj7LlXjE494QxscfMVR879UHHfxsBO8OjPe5k6OWq8cw+zSaVJyaIsPnNws gUn8ge1G1QmhoVUEGK1bXC1N1UaQIWfWwksvO3SF2+HRjpf3OuyQbctyW7jVF20hLd SS33qW+5qn+Wd3+IXhywRuTtR4yiCv7PJl8BQ1t1JrWA+Iv/7Qim98LDLsD9Ls9eUg haibYMoZxrLfF2VzaL47V3veMdgvHk0iIfeonrmd+apwlrfslvFmzjqM9kO0aPkZTh 2ejTXA3l/lDVQ==
Received: from XCH16-01-08.nos.boeing.com (xch16-01-08.nos.boeing.com [144.115.65.218]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id xBK0FL92004512 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Thu, 19 Dec 2019 19:15:22 -0500
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-08.nos.boeing.com (144.115.65.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1779.2; Thu, 19 Dec 2019 16:15:20 -0800
Received: from XCH16-01-11.nos.boeing.com ([fe80::a96c:5d85:1337:4323]) by XCH16-01-11.nos.boeing.com ([fe80::a96c:5d85:1337:4323%4]) with mapi id 15.01.1779.002; Thu, 19 Dec 2019 16:15:20 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Leonard Giuliano <lenny@juniper.net>
CC: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] [Ext] Re: ipv4 multicast address ranges, actual usage.
Thread-Index: AQHVtfZZyiO2saLeJ0uigZnIvFBII6fBCdAAgAACooCAAKtVAIAAic2A//+cJtCAALbRgP//kYFg
Date: Fri, 20 Dec 2019 00:15:20 +0000
Message-ID: <62b1285043f145628752be68adb5a314@boeing.com>
References: <CAA93jw6Wy=+cc1kHNm97SMjYW31KNhaEM4KXZo=nFcCkG9UjCQ@mail.gmail.com> <alpine.DEB.2.02.1912181240340.5406@contrail-ubm-wing.svec1.juniper.net> <CAA93jw7MtXtHVxGnJnZTovSi+o8rtssf2f0uKn-7YNn+YgUg6Q@mail.gmail.com> <5E817666-6988-4A68-8125-F3D3BDB24861@akamai.com> <alpine.DEB.2.02.1912181500530.27773@contrail-ubm-wing.svec1.juniper.net> <CAA93jw6_dSfYZCoGURSqkfdFvdgA+Rxgu63Wdu=73xSsTThuHQ@mail.gmail.com> <BBDA65F0-6D36-443F-8370-62F144139087@icann.org> <CAA93jw6-BJh-GKEHALN+SiKtrroJzNPgodKawevN3puK0BkBJQ@mail.gmail.com> <0c2f76b5431f42f1b9144be1cbc17caa@boeing.com> <alpine.DEB.2.02.1912191428480.32170@contrail-ubm-wing.svec1.juniper.net>
In-Reply-To: <alpine.DEB.2.02.1912191428480.32170@contrail-ubm-wing.svec1.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: 01FEC3E3454A2316BBCCC6AA8CE7548A94E8B78935C09EC9338FDDDD2F5857142000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/_Bb8ucEPA-nmy6Bo_PNIBLqxSMs>
Subject: Re: [MBONED] [Ext] Re: ipv4 multicast address ranges, actual usage.
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Dec 2019 00:15:34 -0000

-----Original Message-----
From: Leonard Giuliano <lenny@juniper.net> 

> Well, 225/8-231/8 and 235/8-238/8 are unassigned/reserved, so there's 
nothing to reclaim since there is no valid use of it in the first place 
(ie, they are squatters).

Granted. Also, by the way, 233/8 and 234/8, squatters *that I know of*.

However, they are harmless squatters, because they use multicast. If we start introducing unicast in those address blocks, when we know these squatters exist, that won’t be harmless anymore.

> That said, I suspect there are much bigger technical issues with 
reassigning chunks of Class D space into unicast (beyond the linux source 
code).  I'm not a hw guy, but I imagine there's a lot of silicon out there 
that will not forward 224/4 packets using the unicast forwarding path.

Was wondering the same thing, but not being a hardware guy myself, I figured someone more personally impacted would pipe up. Splitting up the 1110xxxx prefix into blocks of unicast and blocks of multicast, when now the leading four bits always indicate multicast, might upset some hardware processing.

Bert

v2.23.0 | Report a Bug | By Email