IETF Logo Mail Archive

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

John Kristoff <jtk@depaul.edu> Wed, 18 December 2019 22:04 UTC

Return-Path: <jtk@depaul.edu>
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 E0496120125 for <mboned@ietfa.amsl.com>; Wed, 18 Dec 2019 14:04:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 r05upeo7BPVH for <mboned@ietfa.amsl.com>; Wed, 18 Dec 2019 14:04:18 -0800 (PST)
Received: from aharp.iorc.depaul.edu (aharp.iorc.depaul.edu [140.192.218.132]) by ietfa.amsl.com (Postfix) with ESMTP id 697A5120089 for <mboned@ietf.org>; Wed, 18 Dec 2019 14:04:18 -0800 (PST)
Received: from p50.localdomain (localhost [127.0.0.1]) by aharp.iorc.depaul.edu (Postfix) with ESMTP id 9820118BA; Wed, 18 Dec 2019 22:04:15 +0000 (UTC)
Date: Wed, 18 Dec 2019 16:04:15 -0600
From: John Kristoff <jtk@depaul.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: Leonard Giuliano <lenny@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
Message-ID: <20191218160415.2bb50748@p50.localdomain>
In-Reply-To: <7bc9c8da585544dd8f0cc1384ef5e732@ex16prd04a.dpu.depaul.edu>
References: <CAA93jw6Wy=+cc1kHNm97SMjYW31KNhaEM4KXZo=nFcCkG9UjCQ@mail.gmail.com> <alpine.DEB.2.02.1912181240340.5406@contrail-ubm-wing.svec1.juniper.net> <7bc9c8da585544dd8f0cc1384ef5e732@ex16prd04a.dpu.depaul.edu>
X-Trump: Sucks
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/vN9TX68XqP3JKoCB3RH97wxX1lw>
Subject: Re: [MBONED] 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: Wed, 18 Dec 2019 22:04:20 -0000

On Wed, 18 Dec 2019 21:01:28 +0000
Dave Taht <dave.taht@gmail.com> wrote:

> "to what extent are the various allocations in the 232/8 to 238/8
> range actually used today, and for what?"
> 
> The "for what" portion of the question was: what applications today
> actually use GLOP? or RFC6038? or SSM?

I think IETF RFC 6308 is the correct reference.

I can only tell you that we (DePaul AS 2013) no longer use any
IP multicast addresses outside of the organization local scope block
239.192.0.0/14. We used to have some applications uses our associated
GLOP prefix, but those are long gone and in fact we've ceased all
inter-AS IP multicast connectivity as of a few years ago.

I also happen to know Northwestern (AS 103) no longer distributes C-SPAN
onto the multicast-enabled Internet and hasn't for a long time, that
was using GLOP addressing.  One of the few R&E Internet-wide
applications I even recall hearing of that may have be in one of these
prefixes is some sort of oceanic-related project.

Not a lot of evidence of much, but hopefully small anecdotes are better
than silence.

John

v2.30.2 | Report a Bug | By Email | System Status