All things related to multicast

[Gordon Rogier <>]

Hope I am not speaking out of line on this list.

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
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.

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
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:

> 
> 
>       Here's what I propose.
> 
>       (i).    Let's use 239.0.0.0/8 for I2 scoped (non-global)
>               groups 
> 
>       (ii).   Someone run a registry for the assignment
>               of this space (I think that depending on
>               sdr is too hard here, although such groups
>               could be annouced this way). 
> 
>               Alternatively, we could use glop style address 
>               assignment to get started. I'm in favor of this since
>               everyone would know what they have, and there would
>               be no administrative overhead. You would also know
>               immediately which AS was sourcing the
>               group. References for glop style: 
> 
>                 draft-ietf-mboned-static-allocation-00.txt 
>                 http://gigapop.uoregon.edu/glop
> 
>       (iii).  Gigapops/customers leak 239/8 though both admin scope
>               boundaries and SA filters with I2 networks. I2
>               backbones must also forward (leak) packets and SAs
>               from 239/8. 
> 
> 
>       Comments?
> 
>       Dave
> 
>