From: Craig Dorry (chdorry@yahoo.com)
Date: Fri Apr 02 2004 - 12:53:17 GMT-3
Tyson - I think it is all depending upon how you
define "administratively scoped range". While I
concur that 239.0.0.0/8 is administratively scoped
address range defined by RFC 2365, there is another
way to look at things as well.
In the case of the multicast boundary command I view
the "administratively scoped range" as the range
assigned to different applications by the company
network administrative staff (ie the folks who dole
out the multicast group ranges for that particular
company).
Remember, while the 239.0.0.0/8 is reserved for
private use only, you *could* still use any multicast
ranges you desired as long as you prevented them from
connecting to a public network (ie internet). Just
like you *can* use other company's publicly registered
address space on your company's network as long as you
don't advertise those networks to the internet. (ie
at the end of the day "private" addresses are the ones
that you don't advertise to the public domain)
While I am not saying the above are recommended
practices, it is something that *can* be done if so
desired. And the "not recommended practices" have
been things that seem to be commonplace in lab
scenarios based on my personal studies.
Hope this helps.
--- "Scott, Tyson C" <tyson.scott@hp.com> wrote:
> But Craig you are also stating what my question is.
> The groups you are
> stating are what I understand as administratively
> scoped addresses. In
> some of the practice labs I have done they have used
> the boundary
> command to block addresses in the 224.0.0.0/8 range.
> From what I
> understand this is not in the administratively
> scoped range. So am I
> wrong or is the help topic in IOS wrong?
>
> R4(config-if)#ip multicast ?
>
> Boundary Boundary for administratively scoped
> multicast addresses
>
> Regards,
>
> Tyson Scott
>
> -----Original Message-----
> From: Craig Dorry [mailto:chdorry@yahoo.com]
> Sent: Friday, April 02, 2004 7:33 AM
> To: Scott, Tyson C; ccielab@groupstudy.com
> Subject: Re: Multicast Boundary command
>
> Tyson - I think you are misinterpreting the
> "administratively scoped" addresses. I have used
> the
> boundary command in the following way:
> Multiple campuses running multicast, so we defined 3
> "administrative scopes" (3 different blocks of
> multicast addresses) from the 239.0.0.0/8 block of
> addresses - campus local (never leaves the campus),
> regional (stays within the United States), and
> global.
> The boundary was applied to the "campus local"
> which
> is multicast groups where all sources and receivers
> are at the same physical campus. In this case we
> used
> the same scope for all campus local multicast at
> each
> campus. So on the connections from the Campus to
> the
> MAN we used the ip multicast boundary 1 command, and
> then defined access-list 1 deny 239.1.0.0
> 0.0.255.255
> and permit everything else. (239.1.0.0/16 groups
> were
> to never leave the campus)
>
> Hope this helps.
>
> --- "Scott, Tyson C" <tyson.scott@hp.com> wrote:
> > Group,
> >
> > I am confused as to the topic of the use
> > of Boundary with
> > Multicast. When you use the help from IOS it says
> > it is for
> > administratively scoped Multicast addresses. I
> > thought the
> > administratively scoped addresses where 239.0.0.0
> to
> > 239.255.255.255.
> > So does this command only apply to this range or
> is
> > the help menu
> > misleading?
> >
> >
> >
> > R4(config-if)#ip multicast ?
> >
> > Boundary Boundary for administratively
> scoped
> > multicast addresses
> >
> >
> >
> > Regards,
> >
> > Tyson Scott
> >
> >
>
This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:41 GMT-3