Brian, >> requirements from homenet-arch (I might have missed some): >> - must support multi-homing >> - each link should be assigned a stable prefix >> - efficient allocation of prefixes >> - should support both IPv4 and IPv6 > > I think you need to add > - must allow source-address-based next hop routing
care to elaborate why you think so? in my mind addressing != routing > - must support multiple prefixes per subnet yes, multiple "site prefixes", multiple assignments from the same site-prefix should be avoided though. > - must guarantee consistency with routing > > (The last one doesn't mean "must be provided by routing protocol", > but it does mean that whatever box generates the PD message > MUST be configured with the same information as the routers.) absolutely. > And also > - must be zero-conf as far as the end user is concerned yes. in the flow-chart I have that as "auto conf" > I actually don't see how to separate this discussion (PD) > from the discussion about how to announce multiple > first-hop (a.k.a. default) routers. I'm not quite sure what you mean by "announce multiple first-hop routers". is it different than the multihoming support requirement? with regards to terminology. I prefer prefix assignment (PA). and use delegation when the process is between different administrative domains. > I also don't see how to separate it from the discussion > of autonomic networking that is starting in NMRG, because > of the zero-conf requirement. possibly. there are a few autonomic related drafts submitted to homenet already. as far as I can see they are about building trusted adjacencies. (which could be a prerequisite for prefix assignment). cheers, Ole
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
