On Mon, 16 Aug 2010 18:46:18 +0900 Randy Bush <[email protected]> wrote: > >> I have no plans to ask Cisco and Juniper about this. I want /127 to > >> continue working, and couldn't care less about subnet anycast for my > >> core routers. > > > > I think you miss my point: they might finally comply with the specs one > > day (if you ask or not, others might) and you will have forgotten about > > this little subtle problem and upgrade your routers and voila your > > network is broken. > > then you will join us supporting the /127 document and it won't be a > problem, will it. >
Why won't you and the other authors do a proper job with it then? It doesn't address all the implications that arise. It should, point by point address, all the issues in RFC3627. It should address the points I raised here 2 weeks ago. It doesn't read to me as a proper justification of why the RFCs it contradicts should be contradicted. e.g. Where is the text explaining the implications to bits 70 and 71, if there are any, and do they need to be managed, and if so, how? Saying "it works" is not good enough. A screw driver can be used to open a paint can, so "it works" as a paint can opener, but eventually you ruin it and won't be able to use it to undo screws. /127s break things that are described in existing specifications and have been implemented. I think the /127 draft needs to justify itself against each and every one of them. I personally probably won't use them. But that doesn't mean that I don't want to understand them and that I don't want to know exactly all the implications and tradeoffs involved in using them. The draft as it stands doesn't properly provide that information. > randy > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > [email protected] > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
