[IPsec] scalability questions for draft-sathyanarayan-ipsecme-advpn-03

2014-02-06 Thread Timo Teras
Hi, In addition to previous questions, I have few additional scalability concerns regarding draft-sathyanarayan-ipsecme-advpn-03. 1. Scaling hubs, and shortcut creation times If I have so many spokes (>1000) that single gateway node cannot handle feasibly simultaneous connectivity all of them.

Re: [IPsec] Moving prefixes -- clariciations for draft-sathyanarayan-ipsecme-advpn-03

2014-02-06 Thread Praveen Sathyanarayan
Hi Fred, Comments inline. Thanks, Praveen On 2/5/14 8:44 PM, "Frederic Detienne (fdetienn)" wrote: >Hi Praveen, > >I suppose it would be convenient for you to minimize DMVPN to a "routing >solution" however draft-detienne covers more than that. > >The remote access client case is fully covered

Re: [IPsec] clariciations for draft-sathyanarayan-ipsecme-advpn-03

2014-02-06 Thread Timo Teras
On Thu, 6 Feb 2014 09:20:08 +0100 Daniel Migault wrote: > Thanks for the feed back. > > We are happy you provide requirements over "dynamically routing > subnets" as a MUST. ADVPN responds to the requirements listed in > RFC7018. If there is a requirement that does not match you opinion, > can y

Re: [IPsec] clariciations for draft-sathyanarayan-ipsecme-advpn-03

2014-02-06 Thread Daniel Migault
Hi Timo, Thanks for the feed back. We are happy you provide requirements over "dynamically routing subnets" as a MUST. ADVPN responds to the requirements listed in RFC7018. If there is a requirement that does not match you opinion, can you please point it out? Just to make it clear this 1 day ti