>>>>> "Mark" == Mark Baugher <[email protected]> writes: Mark> IETF Homenet will have a default policy for security and Mark> protocol operation, etc. Future vendors who ship Homenet may Mark> choose to change the default policy, and users who use Homenet Mark> may want to change the policy that the vendors ship. So I Mark> would expect that there may be policies that are required for Mark> compliance and many others that are recommended. Why can't
Assuming that we get over the hurdle of having vendors and ISP implement and deploy homenet, and homenet security, 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. (That you and I can change our policies is great, but doesn't help someone selling a new application to grandma) So, if we recommend something which does not facilitate e2e, including incoming connections, then we have killed e2e. While I'm not happy about Simple Security + PCP, I prefer that to killing e2e. -- ] He who is tired of Weird Al is tired of life! | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] [email protected] http://www.sandelman.ottawa.on.ca/ |device driver[ Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE> then sign the petition.
pgpu2bL73LBJC.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
