rickx, Wim (Wim); bess@ietf.org
> Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
>
> Hi Jim & John,
> Firstly i think option-C interconnection between cloud data center and MPLS
> VPN network exists. Secondly, i think for different encapsulations, different
> intercon
[bess-boun...@ietf.org] on behalf of Rabadan, Jorge (Jorge)
>[jorge.raba...@alcatel-lucent.com]
>Sent: Saturday, November 21, 2015 3:31
>To: UTTARO, JAMES; John E Drake; EXT - thomas.mo...@orange.com; Lucy yong;
>Henderickx, Wim (Wim); bess@ietf.org
>Subject: Re: [bess] draft-hao-bess-inter-nv
>>>
>>>> Hi Diego,
>>>>
>>>> Thanks for your comments. Pls see inline with [Vincent].
>>>>
>>>> Vincent
>>>>
>>>> *发件人:*BESS [mailto:bess-boun...@ietf.org] *代表 *Diego Garcia del
>>>> Rio *发送时间:*2015年
.
>> The other options requires baggage forever on the ASBR elements that does
>> not bring value and it is better to avoid this and build an architecture
>> which is future proof and more cost effective. My 2 cents
>>>
>>> -Thomas
>>
>>>
>>&g
-Thomas
-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Lucy yong
Sent: Friday, November 20, 2015 11:49 AM
To: EXT - thomas.mo...@orange.com; Henderickx, Wim (Wim);
bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Share my 2 ce
To: Henderickx, Wim (Wim); bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
2015-11-19, Henderickx, Wim (Wim):
> WH> I vote for a an evolution of switches/TORs that have proper
> support for this. I hope some HW vendors of TOR chips shime in, but I
> am told the MPLS solution
11:49 AM
> To: EXT - thomas.mo...@orange.com; Henderickx, Wim (Wim);
> bess@ietf.org
> Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
>
> Share my 2 cent.
>
> Cloud providers want to tunnel its customer traffic through DC (AS)BR.
> Option C is a way to realize it. Bo
+1
-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of John E Drake
Sent: Friday, November 20, 2015 12:19 PM
To: EXT - thomas.mo...@orange.com; Lucy yong; Henderickx, Wim (Wim);
bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Lucy,
My
> wrote:
>+1
>
>-Original Message-
>From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of John E Drake
>Sent: Friday, November 20, 2015 12:19 PM
>To: EXT - thomas.mo...@orange.com; Lucy yong; Henderickx, Wim (Wim);
>bess@ietf.org
>Subject: Re: [bess] draft
; Lucy yong;
Henderickx, Wim (Wim); bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
IMHO if TOR chip vendors can confirm they are seriously looking at
MPLS/MPLS/UDP, Wim’s suggestion makes all the sense since we know it works and
scales.
My 2 cents.
Jorge
On 11/20/15
Message-
From: Rabadan, Jorge (Jorge) [mailto:jorge.raba...@alcatel-lucent.com]
Sent: Friday, November 20, 2015 1:32 PM
To: UTTARO, JAMES; John E Drake; EXT - thomas.mo...@orange.com; Lucy yong;
Henderickx, Wim (Wim); bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
IMHO
Vigoureux
Sent: Friday, November 20, 2015 2:13 PM
To: bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Lucy,
there is no such thing as voting in IETF WGs And I haven't seen anything like
voting as part of this discussion.
Thank you
Martin
Le 20/11/2015 20:57, Lucy yong
tt.com> wrote:
+1
-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of John E Drake
Sent: Friday, November 20, 2015 12:19 PM
To: EXT - thomas.mo...@orange.com; Lucy yong; Henderickx, Wim (Wim);
bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-op
@ietf.org] *代表 *Diego Garcia del Rio
*发送时间:*2015年11月18日14:25
*收件人:*bess@ietf.org
*主题:*Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Some comments from my side,
I think the draft makes quite a few assumptions on specific
implementation details that are way too general to be considered
widely
.
Vincent
From: Haoweiguo
Sent: Saturday, November 21, 2015 14:21
To: Rabadan, Jorge (Jorge); UTTARO, JAMES; John E Drake; EXT -
thomas.mo...@orange.com; Lucy yong; Henderickx, Wim (Wim); bess@ietf.org
Subject: RE: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Comments In-Line..
Jim Uttaro
From: Osama Zia [mailto:osa...@microsoft.com]
Sent: Thursday, November 19, 2015 2:06 PM
To: UTTARO, JAMES; Haoweiguo; John E Drake; Henderickx, Wim (Wim); EXT -
thomas.mo...@orange.com; BESS
Subject: RE: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
CIL
From
..@alcatel-lucent.com>; EXT - thomas.mo...@orange.com
<thomas.mo...@orange.com>; BESS <bess@ietf.org>
Subject: RE: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The assumption being based on one's view of what a DC is ;) Yes when an SP and
a Cloud Provider connect an inter-AS mode
is possible in the next generation chips they are working on.
>
> The other options requires baggage forever on the ASBR elements that does
> not bring value and it is better to avoid this and build an architecture
> which is future proof and more cost effective. My 2 cents
> >
<haowei...@huawei.com>; John E Drake <jdr...@juniper.net>;
Henderickx, Wim (Wim) <wim.henderi...@alcatel-lucent.com>; EXT -
thomas.mo...@orange.com <thomas.mo...@orange.com>; BESS <bess@ietf.org>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
A
Zia [mailto:osa...@microsoft.com]
Sent: Thursday, November 19, 2015 2:38 PM
To: UTTARO, JAMES; Haoweiguo; John E Drake; Henderickx, Wim (Wim); EXT -
thomas.mo...@orange.com; BESS
Subject: RE: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
CIL
From: UTTARO, JAMES [mailto:ju1...@att.com]
Sent
which is
future proof and more cost effective. My 2 cents
>
>-Thomas
>
>
>Zhuangshunwan :
>>
>> Hi Diego,
>>
>> Thanks for your comments. Pls see inline with [Vincent].
>>
>> Vincent
>>
>> *发件人:*BESS [mailto:bess-boun...@ietf.org]
, November 17, 2015 11:24 PM
To: John E Drake; Henderickx, Wim (Wim); EXT - thomas.mo...@orange.com; BESS
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Hi,
The problem we are trying to solve is to reduce data center GW/ASBR-d's
forwarding table size, the motivation is same
g mpls label for the packets at DC ASBR when it receives
packets from NVEs.
Lucy
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim)
Sent: Tuesday, November 17, 2015 11:49 AM
To: thomas.mo...@orange.com; BESS
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
"thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>"
<thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>>, BESS
<bess@ietf.org<mailto:bess@ietf.org>>
Subject: RE: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
For this to work every tenant ne
.
Thanks,
weiguo
From: BESS [bess-boun...@ietf.org] on behalf of John E Drake
[jdr...@juniper.net]
Sent: Wednesday, November 18, 2015 2:49
To: Henderickx, Wim (Wim); EXT - thomas.mo...@orange.com; BESS
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Hi
alf of Henderickx, Wim (Wim)
[wim.henderi...@alcatel-lucent.com]
Sent: Tuesday, November 17, 2015 0:52
To: Thomas Morin; bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
In-line
From: Wim Henderickx
<wim.henderi...@alcatel-lucent.com<mailto:wim.henderi...@alcatel-lucent.c
to implement what the draft proposes.
-Thomas
From: Thomas Morin <thomas.mo...@orange.com>
Organization: Orange
Date: Friday 13 November 2015 at 09:57
To: Wim Henderickx <wim.henderi...@alcatel-lucent.com>
Cc: "bess@ietf.org" <bess@ietf.org>
Subject: R
.@alcatel-lucent.com>>,
Linda Dunbar <linda.dun...@huawei.com<mailto:linda.dun...@huawei.com>>,
"bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Hi Wim,
Thanks for you
*Henderickx,
Wim (Wim)
*Sent:* Thursday, November 12, 2015 11:00 PM
*To:* Haoweiguo
*Cc:* bess@ietf.org <mailto:bess@ietf.org>
*Subject:* Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The whole draft complicates any data plane we defined so far and since
there is simpler solutions I d
-
*From:*BESS [bess-boun...@ietf.org <mailto:bess-boun...@ietf.org>] on
behalf of Henderickx, Wim (Wim) [wim.henderi...@alcatel-lucent.com
<mailto:wim.henderi...@alcatel-lucent.com>]
*Sent:* Thursday, November 12, 2015 22:33
*To:* bess@ietf.org <mailto:bess@i
uot; <bess@ietf.org<mailto:bess@ietf.org>>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> on behalf of
Thomas Morin <thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>>
Or
uot; <bess@ietf.org<mailto:bess@ietf.org>>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
In-line
From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> on behalf of
Thomas Morin <thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>>
Or
From: BESS [bess-boun...@ietf.org] on behalf of Henderickx, Wim (Wim)
[wim.henderi...@alcatel-lucent.com]
Sent: Saturday, November 14, 2015 15:12
To: Linda Dunbar; bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Linda, first of all the draft does not say anything
Hi Wim,
I agree on the analysis that this proposal is restricted to
implementations that supports the chosen encap with non-IANA ports
(which may be hard to achieve for instance on hardware implementations,
as you suggest), or to context where managing multiple IPs would be
operationally
] On Behalf Of Henderickx, Wim (Wim)
Sent: Thursday, November 12, 2015 11:00 PM
To: Haoweiguo
Cc: bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The whole draft complicates any data plane we defined so far and since there is
simpler solutions I don’t support this proposal
Fully agree Tomas’s points (below).
Lucy
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of thomas.mo...@orange.com
Sent: Friday, November 13, 2015 10:37 AM
To: Henderickx, Wim (Wim)
Cc: bess@ietf.org
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Hi Wim,
2015-11-13, Henderickx
<wim.henderi...@alcatel-lucent.com
<mailto:wim.henderi...@alcatel-lucent.com>>
Cc: "bess@ietf.org <mailto:bess@ietf.org>" <bess@ietf.org
<mailto:bess@ietf.org>>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
Hi Wim,
I agree on the analysis
Regards,
Lucy
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim)
Sent: Thursday, November 12, 2015 11:00 PM
To: Haoweiguo
Cc: bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The whole draft complicates any data plane we
s,
Lucy
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim)
Sent: Thursday, November 12, 2015 11:00 PM
To: Haoweiguo
Cc: bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The whole draft complicates any data plane w
SS [mailto:bess-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim)
Sent: Thursday, November 12, 2015 11:00 PM
To: Haoweiguo
Cc: bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The whole draft complicates any data plane we defined so far and
nge.com>>
Organization: Orange
Date: Friday 13 November 2015 at 17:36
To: Wim Henderickx
<wim.henderi...@alcatel-lucent.com<mailto:wim.henderi...@alcatel-lucent.com>>
Cc: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Subject
November 12, 2015 11:00 PM
To: Haoweiguo
Cc: bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The whole draft complicates any data plane we defined so far and since there is
simpler solutions I don’t support this proposal.
Arguments have been given a
ore sending toward WAN.
Hope we together work out the solution for this valid use case and like to hear
any better alternative.
Regards,
Lucy
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim)
Sent: Thursday, November 12, 2015 11:00 PM
To: Haoweiguo
Cc: bess@ietf
etter alternative.
Regards,
Lucy
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim)
Sent: Thursday, November 12, 2015 11:00 PM
To: Haoweiguo
Cc: bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The whole draft complicates
@ietf.org] On Behalf Of Henderickx, Wim (Wim)
Sent: Thursday, November 12, 2015 11:00 PM
To: Haoweiguo
Cc: bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The whole draft complicates any data plane we defined so far and since there is
simpler solution
, Wim (Wim)
Sent: Thursday, November 12, 2015 8:34 AM
To: bess@ietf.org
Subject: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
I don’t support the adoption of this draft as a WG. There is a major flaw in
this proposal:
Basically the encapsulation of VXLAN/NVGRE is incompatible with MPLS IP-VPNs
e, it gets the label for the packet, push the label
on the packet before sending toward WAN.
Hope we together work out the solution for this valid use case and like to hear
any better alternative.
Regards,
Lucy
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim)
Se
ilto:bess-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim)
Sent: Thursday, November 12, 2015 11:00 PM
To: Haoweiguo
Cc: bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
The whole draft complicates any data plane we defined so far and since there
2015 8:34 AM
To: bess@ietf.org<mailto:bess@ietf.org>
Subject: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
I don’t support the adoption of this draft as a WG. There is a major flaw in
this proposal:
Basically the encapsulation of VXLAN/NVGRE is incompatible with MPLS IP-VPNs.
VXLAN/NVGRE contain
]
Sent: Thursday, November 12, 2015 22:33
To: bess@ietf.org
Subject: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
I don’t support the adoption of this draft as a WG. There is a major flaw in
this proposal:
Basically the encapsulation of VXLAN/NVGRE is incompatible with MPLS IP-VPNs.
VXLAN/NVGRE
I don’t support the adoption of this draft as a WG. There is a major flaw in
this proposal:
Basically the encapsulation of VXLAN/NVGRE is incompatible with MPLS IP-VPNs.
VXLAN/NVGRE contains a MAC address and IP-VPNs don’t. The draft does not talk
about any of this and introduces a lot of
<mailto:wim.henderi...@alcatel-lucent.com>]
Sent: Thursday, November 12, 2015 22:33
To: bess@ietf.org<mailto:bess@ietf.org>
Subject: [bess] draft-hao-bess-inter-nvo3-vpn-optionc
I don’t support the adoption of this draft as a WG. There is a major flaw in
this proposal:
Basically the encaps
Hi Wim,
Thanks for your feedback.
With my co-chair hat, let met ask a few questions for the sake of well
understanding the issue you raise.
Henderickx, Wim (Wim):
I don’t support the adoption of this draft as a WG. There is a major
flaw in this proposal:
Basically the encapsulation of
53 matches
Mail list logo
