Re: [pim] [MBONED] Unambiguous IPv4 Multicast to Ethernet Address mapping?

Joe Touch <touch@strayalpha.com> Mon, 27 July 2020 06:31 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26BFB3A1704; Sun, 26 Jul 2020 23:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.316
X-Spam-Level:
X-Spam-Status: No, score=-1.316 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, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 T6H7wtyMSTdm; Sun, 26 Jul 2020 23:31:00 -0700 (PDT)
Received: from server217-4.web-hosting.com (server217-4.web-hosting.com [198.54.116.98]) (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 44E803A170B; Sun, 26 Jul 2020 23:31:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Transfer-Encoding:Content-Type:Sender: Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender :Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=EcukM3orYEzvLeCrgIID3QAsxmBIvCfa/Q8/rl3NrRU=; b=CsyoH5HcGp5P2GONdy8VSGoc/0 ZHgzTW7AuZVLppJKu+aMiwUBwj3iGLcanZwVxZyxX+d/mdPKxRCg99zIycWMdb3QPKJ3Jg79BaJ3D Qn1VhJpDa3kQAfBtTF7vbyrGxKatZGUk+G2Qx1mmuAyFBvlpsMc+n9UktcdE6ov5dmWxEOkPMRwtG yyn/R0etpPifEdldKdJVs0fNN0APAPAEpsUQBiBn+v4tgXAdDxHPimoDqMbA7SKkS21Yj4Au9i32j J+REuO/iHyBqm4sN96BwfGkrsUxMA83AmpskWWKY5lgbX8i9Utaly0qQs1SZjSx8j08wZSdqR90Mt /cPts9+Q==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:61642 helo=[192.168.1.6]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <touch@strayalpha.com>) id 1jzwf1-002joa-Ax; Mon, 27 Jul 2020 02:30:59 -0400
Content-Type: multipart/alternative; boundary=Apple-Mail-EF5693C9-D5A9-4269-8182-8DCE86283159
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <CAH8Jh6BsVgLW5rV00Ugp9CCwKcDaBvsWCRtc_o83ks83PxGz_w@mail.gmail.com>
Date: Sun, 26 Jul 2020 23:30:54 -0700
Cc: mboned@ietf.org, pim@ietf.org, bier@ietf.org
Message-Id: <2446466B-4F73-421F-AC68-38AAE64E3C3C@strayalpha.com>
References: <CAH8Jh6BsVgLW5rV00Ugp9CCwKcDaBvsWCRtc_o83ks83PxGz_w@mail.gmail.com>
To: "James A. (Jim) Stevens" <james.a.stevens=40collins.com@dmarc.ietf.org>
X-Mailer: iPad Mail (17G68)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/QR6VCl8AxvMUERuQR0S_nCo_4a4>
Subject: Re: [pim] [MBONED] Unambiguous IPv4 Multicast to Ethernet Address mapping?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2020 06:31:02 -0000

First question - why?

As in, what problem has been observed that this would solve?

Note that the IPv6 is a locally administered Ethernet address, not one registered by the IEEE for the IETF.

Joe

> On Jul 26, 2020, at 10:44 PM, James A. (Jim) Stevens <james.a.stevens=40collins.com@dmarc.ietf.org> wrote:
> 
> 
> RFC 1112 maps the 28 unique IPv4 multicast address bits to 23 bits within the Ethernet address so that there is not a unique one to one mapping.
> 
> According to https://networklessons.com/multicast/multicast-ip-address-to-mac-address-mapping, this was because it would have cost $16,000 in 1990 to have reserved 16 OUIs (Organizational Unique Identifiers) to IP multicast MAC addresses so that the IPv4 multicast to Ethernet multicast addressing would be unique.
> 
> IPv6 in RFC 2464, maps the lower 32 bits of the IPv6 multicast addresses into the lower 32 bits of the Ethernet Address - so it looks like IEEE supports other IP address to ethernet multicast address mappings.
> 
> Question - Is any interest within IETF about working with IEEE to come up with an IPv4 to Ethernet multicast address mapping so that the 28 unique IPv4 addresses map uniquely to Ethernet Addresses?
> 
> For example, this could be a new Proposed Standard RFC that also allows the existing RFC 1112 to continue to be used for backwards compatibility?
> 
> Jim Stevens
> 
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned