I believe that it is being discussed in v6ops. However, if you want to tell us how to scalably manage O(10^7) IPv6 PI prefixes without translation, without rearranging all of the operator's transit contracts (which would be one of the side-effects of Metro Addressing), and without aggregation, I guess I'm all ears. The alternative I would come up with is a messaging architecture. *That* would be a discussion for another list, but it's one that I'll probably detail at some point.
On Oct 25, 2010, at 11:28 AM, james woodyatt wrote: > On Oct 25, 2010, at 10:29, Margaret Wasserman wrote: >> >> Wow, I do have to read that. From the name, I thought the document said >> exactly the opposite, although I should have trusted that author list to >> come up with something insightful. Thanks for the pointer! > > Oh, dratz. I made the same mistake. I'm gonna need to read that asap. > > Is that draft an appropriate topic of discussion for this mailing list? > > > -- > james woodyatt <[email protected]> > member of technical staff, communications engineering > > > _______________________________________________ > nat66 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nat66 _______________________________________________ nat66 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nat66
