RE: New draft on embedding the RP address in IPv6 multicast address

["Mike O'Connor" <moc@es.net>]

[ post by non-subscriber.  with the massive amount of spam, it is easy to
  miss and therefore delete mis-posts.  so fix subscription addresses! ]

Brian,

Is there an underlying assumption that a given group has all of it's
sources in one PIM domain? 

ASM in V4 doesn't restrict the number of RP's per multicast group. How
does the proposal support an ASM conference where all participants are
in different AS/PIM domains and each is both sender and receiver with
it's own RP?  I'm seeing this as supporting SSM but not ASM.

-Mike 

--
Mike O'Connor,                  E-mail: moc@es.net
Network Engineer                Energy Sciences Network (ESnet)
East coast: +1 631 344-7410     West coast: +1 510 486-7421
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)




-----Original Message-----
From: Brian Haberman [mailto:bkhabs@nc.rr.com] 
Sent: Thursday, October 10, 2002 1:56 PM
To: Mike O'Connor
Cc: Marshall Eubanks; Pekka Savola; mboned@network-services.uoregon.edu;
v6ops@ops.ietf.org; nesg@es.net
Subject: Re: New draft on embedding the RP address in IPv6 multicast
address


Mike O'Connor wrote:
> Hi Brian,
> 
> I don't understand how the reciever's RP receives the "owning RP" 
> address for a given multicast group. How are the "owning RP" addresses

> distributed between domains without PIM flooding?

The RP address is embedded in the multicast address.  The key is in the
assignment of multicast addresses in a domain and the configuration of
RP addresses.

So, if a domain uses prefix 3ffe:1:2::/48.  It places an RP in the
network and gives it an address of 3ffe:1:2:3::5.  Now, this RP can be
the RP for the multicast address range FF7x:0540:3ffe:1:2:3::/96. The
key is that the IID portion of the RP's address is set to a value that
can be encode in the RPad field of the multicast address.  The mcast
groups are distinguished by the lower 32 bits of the address.

Now, a receiver's RP can examine the multicast address when it is
creating state and reconstruct the owning RP's address by extracting the
network prefix value and appending the RPad field.

Brian