All things related to multicast

[Gordon Rogier <>]

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Gordon Rogier                        

            
Network Engineer                     785-864-0381wk 785-550-4468 cell
Great Plains Network                 785-864-9330 FAX

On Wed, 30 Jun 1999, David Meyer wrote:
> > I think that 'end' AS entities will ultimately want to use the
> > 239.192.0.0/26 space for AS "organization-scoped" and
> > "organization-site-scoped" applications, eg. local lab file restore
> > applications, local content broadcasting.  Now I know that ttl scoping of
> 
>       Is there an application that is using this now? I ask
>       as /26 is odd for this space.

I have no experience with using mcast routing and apps, but I do have
some local campus (aka. at the University of Kansas) apps that I would
like to assign a mcast address to for only local campus and possibly site
specifice within the campus scoping.  Eg. a lab machine restore app called
LabExpert which comes hard coded to use.

I referenced the /26 from IANA list of mcast addresses, where you have
listed 239.192.0.0/26 as organization-local and site-local scopes by
rfc2365 (and note 239.0.0.0/8 is completely "admin" scoped).  Thusly I do
like using other parts of 239.0.0.0/8 for admin scoping within I2.

> > the source could be used also, but not all apps may behave well on this
> > issue.  Also, many local apps may not participate in sdr, etc. so end AS
> > will have a desire to have a usable preallocated private mcast group
> > space.
> 
>       That's why I suggested glop. We can do it on /10 too,
>       but not as nicely.

I need to go off and read glop, as you have noted it deals with my
concern.  I look forward to reading asap and thank you for the posting on
this detail.

I do not care how we do provide for AS (or the alike of end networks)
private mcast allocations, just that we do it.