Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-05 Thread Fabio Maino
Actually recomposing the VXLAN/LISP splitting was another design goal of VXLAN-GPE. A VXLAN-GPE implementation can share most of its code with a LISP implementation, contributing to the reduction of test and implementation cost. Fabio On 8/5/16 9:21 AM, Jesse Gross wrote: On Aug 5, 2016,

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-05 Thread Jesse Gross
> On Aug 5, 2016, at 8:01 AM, Dino Farinacci wrote: > >> In addition, while you are trying to optimize for one particular >> implementation and architecture, the long term results of these decisions >> tend to impact many more platforms than the original one. For example,

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-05 Thread Tom Herbert
> Tom, > it's more than just infeasibility that should be considered as part of the > technical evaluation, but also the cost/complexity associated with > implementations. > > Encapsulations are not implemented in a vacuum, but compete with other > features for resources available in a given

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-05 Thread Dino Farinacci
> In addition, while you are trying to optimize for one particular > implementation and architecture, the long term results of these decisions > tend to impact many more platforms than the original one. For example, VXLAN > was derived from LISP with the same goals as you are describing here.

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-05 Thread Jesse Gross
> On Aug 4, 2016, at 5:53 PM, Fabio Maino wrote: > Tom, > it's more than just infeasibility that should be considered as part of the > technical evaluation, but also the cost/complexity associated with > implementations. > > Encapsulations are not implemented in a vacuum,

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-04 Thread Fabio Maino
On 8/3/16 4:34 PM, Tom Herbert wrote: On Wed, Aug 3, 2016 at 3:54 PM, Fabio Maino wrote: On 8/3/16 3:38 PM, Tom Herbert wrote: On Wed, Aug 3, 2016 at 2:26 PM, Fabio Maino wrote: On 8/1/16 4:21 PM, Alia Atlas wrote: On Mon, Aug 1, 2016 at 6:35 PM, Tom

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-03 Thread Tom Herbert
On Wed, Aug 3, 2016 at 3:54 PM, Fabio Maino wrote: > On 8/3/16 3:38 PM, Tom Herbert wrote: >> >> On Wed, Aug 3, 2016 at 2:26 PM, Fabio Maino wrote: >>> >>> On 8/1/16 4:21 PM, Alia Atlas wrote: >>> >>> >>> >>> On Mon, Aug 1, 2016 at 6:35 PM, Tom Herbert

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-03 Thread Tom Herbert
On Wed, Aug 3, 2016 at 2:26 PM, Fabio Maino wrote: > On 8/1/16 4:21 PM, Alia Atlas wrote: > > > > On Mon, Aug 1, 2016 at 6:35 PM, Tom Herbert wrote: >> >> On Mon, Aug 1, 2016 at 2:59 PM, Fabio Maino wrote: >> > On 7/29/16 6:38 PM, Jesse

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-03 Thread Fabio Maino
On 8/1/16 4:21 PM, Alia Atlas wrote: On Mon, Aug 1, 2016 at 6:35 PM, Tom Herbert > wrote: On Mon, Aug 1, 2016 at 2:59 PM, Fabio Maino > wrote: > On 7/29/16 6:38 PM, Jesse Gross wrote:

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-01 Thread Alia Atlas
On Mon, Aug 1, 2016 at 6:35 PM, Tom Herbert wrote: > On Mon, Aug 1, 2016 at 2:59 PM, Fabio Maino wrote: > > On 7/29/16 6:38 PM, Jesse Gross wrote: > >>> > >>> On Jul 29, 2016, at 4:39 PM, Fabio Maino wrote: > >>> > >>> On 7/29/16 12:44

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-08-01 Thread Fabio Maino
On 7/29/16 6:38 PM, Jesse Gross wrote: On Jul 29, 2016, at 4:39 PM, Fabio Maino wrote: On 7/29/16 12:44 PM, Jesse Gross wrote: On Jul 29, 2016, at 12:17 PM, Fabio Maino wrote: On 7/29/16 11:45 AM, Tom Herbert wrote: On Jul 29, 2016 11:12 AM, "Fabio

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-07-29 Thread Jesse Gross
> On Jul 29, 2016, at 4:39 PM, Fabio Maino wrote: > > On 7/29/16 12:44 PM, Jesse Gross wrote: >>> On Jul 29, 2016, at 12:17 PM, Fabio Maino wrote: >>> >>> On 7/29/16 11:45 AM, Tom Herbert wrote: On Jul 29, 2016 11:12 AM, "Fabio Maino"

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-07-29 Thread Fabio Maino
On 7/29/16 12:44 PM, Jesse Gross wrote: On Jul 29, 2016, at 12:17 PM, Fabio Maino wrote: On 7/29/16 11:45 AM, Tom Herbert wrote: On Jul 29, 2016 11:12 AM, "Fabio Maino" wrote: On 7/27/16 1:43 PM, Tom Herbert wrote: On Wed, Jul 27, 2016 at 1:15 PM, Fabio

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-07-29 Thread Tom Herbert
On Fri, Jul 29, 2016 at 12:44 PM, Jesse Gross wrote: > >> On Jul 29, 2016, at 12:17 PM, Fabio Maino wrote: >> >> On 7/29/16 11:45 AM, Tom Herbert wrote: >>> On Jul 29, 2016 11:12 AM, "Fabio Maino" wrote: >>> > >>> > On 7/27/16 1:43 PM, Tom

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-07-29 Thread Jesse Gross
> On Jul 29, 2016, at 12:17 PM, Fabio Maino wrote: > > On 7/29/16 11:45 AM, Tom Herbert wrote: >> On Jul 29, 2016 11:12 AM, "Fabio Maino" wrote: >> > >> > On 7/27/16 1:43 PM, Tom Herbert wrote: >> >> >> >> On Wed, Jul 27, 2016 at 1:15 PM, Fabio Maino

Re: [nvo3] Security in VXLAN-GPE (was Re: Consensus call on encap proposals)

2016-07-29 Thread Fabio Maino
On 7/27/16 1:43 PM, Tom Herbert wrote: On Wed, Jul 27, 2016 at 1:15 PM, Fabio Maino wrote: On 7/27/16 12:27 PM, Tom Herbert wrote: On Wed, Jul 27, 2016 at 11:00 AM, Fabio Maino wrote: On 7/27/16 10:53 AM, Tom Herbert wrote: On Wed, Jul 27, 2016 at 10:44