On Mar 14, 2012, at 08:16 , Michael Richardson <m...@sandelman.ca> wrote:
> whatever we set as the recommended default will be what is there for 99% of > users, and therefore what anyone writing an application that has to live in > the home is going to have to deal with. A point I have been trying to make for several years now is that we have already set a recommended default in many places for "block all incoming connections" at unmanaged Internet gateways. We probably had a chance to reverse course on this for IPv6 in the middle of the last decade, but not anymore. We now have a strategic direction we have been following for quite some time now, and we have too much invested in it to turn back. I think the credit for preserving the continuity of the IPv4/NAT experience with the transition to IPv6 should go to the IAB and the IESG. The HOMENET architecture should throw in the towel on E2E and go with RFC 6092 on by default at the border gateway. It should be silent about PCP until something can be done about its lack of explicit support for nested security domains. -- james woodyatt <j...@apple.com> member of technical staff, core os networking _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
