Authors,
there has been a number of comments on this draft during WG LC.
Please make sure you give an answer regarding each, and then update the
draft if needed.
Thank you
M&T
Le 13/02/2017 à 23:07, Martin Vigoureux a écrit :
Hello Working Group,
This email starts a Working Group Last Call
section be moved to the prefix-advertisement draft?
Jeffrey
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
> Sent: Monday, February 13, 2017 5:07 PM
> To: BESS
> Subject: [bess] WG Last Call for
> draft-ietf-bess-evpn
Hi Ali,
Please see below.
> -Original Message-
> From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
> Sent: Tuesday, February 21, 2017 2:12 AM
> To: Jeffrey (Zhaohui) Zhang ; Martin Vigoureux
> ; BESS
> Subject: Re: [bess] WG Last Call for draft-ietf-bess
Hi Jeffrey,
My comments in line ...
On 2/17/17, 9:09 PM, "Jeffrey (Zhaohui) Zhang" wrote:
>Hi Ali,
>
>> >Is it that besides their own default gateway, an additional common
>> >gateway is advertised using that extended community? If so, what's the
>> >purpose to call those different IP addresse
I have a number of comments on this draft. I've attached a copy of the
draft with comments in-line; look for lines beginning with "".
I don't think the document is ready to advance at the present time.
Issues:
- Most of this document is a discussion of various Data Center use
cases, with
Hi Ali,
> >Is it that besides their own default gateway, an additional common
> >gateway is advertised using that extended community? If so, what's the
> >purpose to call those different IP addresses on the IRB interfaces
> >"default gateway"? I assume the hosts will be using the common gateway
>
Support
Regards,
Nabeel
> On Feb 13, 2017, at 5:07 PM, Martin Vigoureux
> wrote:
>
> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] which is considered
> mature and ready for a final working group review.
> Not
o, while each subnet is attached to each NVE, the IP routing process
>> (e.g. TTL decrement) happens twice - first on the source NVE and then on
>> the source GW. That's probably OK, but better point out all these details.
>
> TTL decrement is given when IP lookup is perform
d to forward
> traffic in L2 to a centralized L3GW for a number of reasons: a) they
> don't have IRB capabilities or b) they don't have required policy for
> switching traffic between different tenants or security zones.
>
>For b), do we configure IRB on those non-centr
n different tenants or security zones.
For b), do we configure IRB on those non-centralized gateways at all? I assume
not (even though the NVE could support IRB) - It's better to be clear.
I'll send a follow up email about the symmetric section.
Thanks.
Jeffrey
> -----Original Mes
I support. I’m not aware of any IPR at this point of time.
Regards,
Patrice Brissette
On 2017-02-13, 5:07 PM, "BESS on behalf of Martin Vigoureux"
wrote:
Hello Working Group,
This email starts a Working Group Last Call on
draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] wh
Support and I'm not aware of any IPR
Yours Irrespectively,
John
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
> Sent: Monday, February 13, 2017 5:07 PM
> To: BESS
> Subject: [bess] WG Last Call for
> draft-ietf
Support as co-auhtor. Not aware of any non-disclosed IPR.
Regards,
Ali
On 2/13/17, 2:07 PM, "BESS on behalf of Martin Vigoureux"
wrote:
>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] which is considered
>mature and
Yes/Support
Regards,
Autumn
On 2/13/17, 11:07 PM, "BESS on behalf of Martin Vigoureux"
wrote:
Hello Working Group,
This email starts a Working Group Last Call on
draft-ietf-bess-evpn-inter-subnet-forwarding-03 [
yes/support
Cheers,
Jeff
On 2/13/17, 11:07 PM, "BESS on behalf of Martin Vigoureux"
wrote:
Hello Working Group,
This email starts a Working Group Last Call on
draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] which is considered
mature and
Support doc as co-author for publication as standard RFC
On 14/02/2017, 00:15, "BESS on behalf of Rabadan, Jorge (Nokia - US)"
wrote:
I support this document, as a co-author, for publication as Standard RFC.
Not aware of any IPR.
Thanks.
Jorge
On 2/13/17, 11:07 PM,
Support.
Thanks,
—Satya
>
>On 2/13/17, 11:07 PM, "BESS on behalf of Martin Vigoureux"
> wrote:
>
>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] which is considered
>mature and ready for a final
I support this document, as a co-author, for publication as Standard RFC.
Not aware of any IPR.
Thanks.
Jorge
On 2/13/17, 11:07 PM, "BESS on behalf of Martin Vigoureux"
wrote:
Hello Working Group,
This email starts a Working Group Last Call on
draft-ietf-bess-evpn-inter-subne
Hello Working Group,
This email starts a Working Group Last Call on
draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] which is considered
mature and ready for a final working group review.
Note that this call is longer than usual because we are pushing two
correlated documents together.
Pl
19 matches
Mail list logo
