A little. Also like GET-VPN and AC-VPN and Provider-1 (apologies to all the vendors I've missed)
Those are some of the incompatible solutions by individual vendors. Yoav On 10/14/11 8:18 AM, "Dan Harkins" <dhark...@lounge.org> wrote: > > Sounds like TED: > >http://www.cisco.com/en/US/docs/ios/12_0t/12_0t5/feature/guide/ted.html > > Dan. > >On Thu, October 13, 2011 10:23 pm, Yoav Nir wrote: >> Hi all >> >> For years, one of the barriers to the adoption of IPsec was that >> configuration didn't scale. With thousands of peers, the PAD and SPD >>would >> become unwieldy, so even where IPsec was deployed it was often built in >> hub-and-spoke configurations, not because policy demanded this, but >> because it was more convenient to configure. Individual vendors have >> incompatible solutions for this, but they only work with that vendor's >> products, and within the same administrative domain. >> >> In this draft, we are proposing that the IPsecME working group take on a >> working item to first define the problem, and then offer solutions that >> will make IPsec scale better and in an inter-operable way. >> >> We plan to hold a side meeting in Taipei, and we welcome comments both >> before and at that meeting. >> >> Yoav >> >> http://www.ietf.org/id/draft-nir-ipsecme-p2p-00.txt >> http://tools.ietf.org/html/draft-nir-ipsecme-p2p-00 >> >> _______________________________________________ >> IPsec mailing list >> IPsec@ietf.org >> https://www.ietf.org/mailman/listinfo/ipsec >> > > > >Scanned by Check Point Total Security Gateway. _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
