Hi, On Mon, 22 Feb 2010 16:43:00 -0500, Durand, Alain wrote: > We'd like to announce the softwire WG LC on the 6rd technology. I've > copied both SOFTWIRE and DHC mailing lists and solicit comments from > both groups of experts. The draft is here: > >http://www.ietf.org/internet-drafts/draft-ietf-softwire-ipv6-6rd-07.txt > > Please reply with comments to this thread by 2010.03.08 at 1700 PST
This document truly depict what we are running into production in our backbone here. I strongly support it! I read some post on the ML regarding fragmentation and MTU related. IMHO, section 9.1 is enough explicit, anyone playing around with encapsulation will face at one point MTU issues and fragmentation, it is really common. Any operational networking guy will/have to keep in mind this MTU stuff while designing/setting up its encapsulation architecture. What is important here, 6rd is operating inside a specific routing domain so that if there is MTU/fragmentation issues then it is networking domain designer job/responsibility to fix it ! if networking design has been made into a crappy way then it will transitively operate into a crappy way too. IMHO, it should certainly not be the focus of an operational protocol draft, like 6rd, to provide a networking course. In our production env, MTU is set to 1480 at CPE side. regs, Alexandre _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
