The charter as written now aims to develop building blocks which can be applied commonly across a wide range of networks including enterprise, SP, (home?), and IOT, yet the very first use-case listed in order to provide WG focus is restricted to carrier-only? (and, to Lorenzo's point, what does that actually mean with respect to IP address assignment?)
If a carrier-only use-case is doing its job of focusing the WG, it will naturally lead to carrier-centric building blocks, contradictory to the stated goal of the group. - Mark > On Oct 2, 2014, at 8:26 AM, Lorenzo Colitti <lore...@google.com> wrote: > >> On Thu, Oct 2, 2014 at 12:16 PM, Brian E Carpenter >> <brian.e.carpen...@gmail.com> wrote: >> > This use case is precisely what draft-ietf-homenet-prefix-assignment does >> > (which has roots all the way back to >> > draft-arkko-homenet-prefix-assignment-00 in October 2011). So to homenet, >> > this is a solved problem - with an algorithm that has been applied not >> > just to HNCP, but to OSPF and ISIS. >> >> Well, we have a bug in our short description, because the intention is to >> support prefix assignment in a carrier scenario, which is different >> in many ways. > > Really? Which ways?
_______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
