[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

No Subject



o A router acting as an RP MUST NOT forward any Register-encapsulated
  packet that has an SSM destination address.


The last two rules are present to deal with "legacy" routers unaware of
SSM that may be sending (*,G) and (S,G,rpt) Join/Prunes, or Register
messages for SSM destination addresses.

Additionally:

o A router MAY be configured to advertise itself as a Candidate RP for
  an SSM address.  If so, it SHOULD respond with a Register-Stop message
  to any Register message containing a packet destined for an SSM
  address.
-----------------
I would say that for the foreseeable future, domains will be BOTH ASM and SSM.
I would also say that these domains will thus have to deal both with RP's and with
cross-domain traffic that potentially has ASM traffic in the ISM space. I
would therefore recommend that the BCP explicitly include these details on what
to do with RP's in the SSM space.

I would also say that the BCP for SSM should be that inter-domain SSM is only done
in the 232/8 address range, and that other SSM uses are restricted to the administratively
scoped domain 239/8. Otherwise, SSM address discovery will rear its ugly head.

--
                                 Regards
                                 Marshall Eubanks



T.M. Eubanks
Multicast Technologies, Inc
10301 Democracy Lane, Suite 410
Fairfax, Virginia 22030
Phone : 703-293-9624
Fax     : 703-293-9609
e-mail : tme@on-the-i.com     tme@multicasttech.com

http://www.on-the-i.com http://www.buzzwaves.com