One more point... On 11/7/13 1:05 PM, Brian Haberman wrote: > All, > I seem to be the bane of homenet given my stance on multicast scope > zones. Probably because I am a co-author on RFC 4007. :) > > After some discussions, it seems there is a reasonable way to allow > the homenet arch to use the admin-scope multicast range. My original > concern, as documented in my DISCUSS, is that RFC 4291 requires scope 4 > and larger be administratively configured. I will contend that *if* all > the homenet boundary routers can automatically set a boundary based on > getting a prefix delegation from an ISP, that satisfies the > administratively configured rule 4291. > > If the WG is agreeable with that, there are a few things I would like to > see in the arch doc: > > 1. References to site-local scope need to be changed to admin-scope > > 2. Some guidance on the setting of that boundary triggered by an > administrative function like PD is needed >
This same approach could be used to contain any ULA prefixes generated as well. Regards, Brian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
