I don't think this is an all-or-nothing choice. You might want a mesh for VoIP, but a star for HTTP, FTP and mail protocols. Or you may want a mesh within your organization, but to trunk and inspect all traffic going somewhere else.
On Mar 21, 2012, at 3:37 AM, Stephen Hanna wrote: > Please comment. > > Steve > > -----Original Message----- > From: ipsecme issue tracker [mailto:t...@tools.ietf.org] > Sent: Tuesday, March 20, 2012 7:04 PM > To: yaronf.i...@gmail.com; draft-ietf-ipsecme-p2p-vpn-prob...@tools.ietf.org > Subject: [ipsecme] #219: Star topology as an admin choice > > #219: Star topology as an admin choice > > Some admins prefer a star topology so they can inspect traffic. They may > not want to use this technology. > > Suggested Resolution: Mention this in the Security Considerations section. > > -- > -------------------------+------------------------------------------------- > Reporter: | Owner: draft-ietf-ipsecme-p2p-vpn- > yaronf.ietf@… | problem@… > Type: defect | Status: new > Priority: normal | Milestone: > Component: p2p-vpn- | Severity: - > problem | > Keywords: | > -------------------------+------------------------------------------------- > > Ticket URL: <http://trac.tools.ietf.org/wg/ipsecme/trac/ticket/219> > ipsecme <http://tools.ietf.org/ipsecme/> > > _______________________________________________ > IPsec mailing list > IPsec@ietf.org > https://www.ietf.org/mailman/listinfo/ipsec > �jy�u����$>���:-jT�r��!��� _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
