Himanshu,
I don’t think we should make the Eth-tag a MUST be 24 bit. It should be MAY
but if you decide to use 24 bits, it MUST be right aligned.
Regards,
Patrice Brissette
On 2017-02-21, 2:51 PM, "Shah, Himanshu" wrote:
‘MAY’ does not work.
It has to be ‘MUST’, IMO.
Thank
‘MAY’ does not work.
It has to be ‘MUST’, IMO.
Thanks,
Himanshu
On 2/21/17, 2:22 PM, "BESS on behalf of Patrice Brissette (pbrisset)"
wrote:
Folks,
Why don’t we simply mention that the Eth–Tag is a 32 bit value and MAY be
set to a 24 bits instance
When 24 bits value is used
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-evpn-inter-subnet-
> forward
Folks,
Why don’t we simply mention that the Eth–Tag is a 32 bit value and MAY be set
to a 24 bits instance
When 24 bits value is used is MAY be right aligned.
Regards,
Patrice Brissette
On 2017-02-21, 2:18 PM, "BESS on behalf of Sami Boutros" wrote:
Hi John,
I can add that the va
Hi John,
I can add that the value is from 0 to 0x00ff, will that work?
Thanks,
Sami
On 2/21/17, 10:56 AM, "John E Drake" wrote:
>Sami,
>
>Snipped, comment inline
>
>Yours Irrespectively,
>
>John
>
>> >
>> >> Ethernet Tag ID 32-bit field MUST be set to the 24-bit VPWS service
>> >> instan
Sami,
Snipped, comment inline
Yours Irrespectively,
John
> >
> >> Ethernet Tag ID 32-bit field MUST be set to the 24-bit VPWS service
> >> instance
> identifier value."
> >
> >
> >
> >Ok, but you still didn’t mention how the 24-bit value is to be aligned in
> >the 32-
> bit field. I’m guessi
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS of the IETF.
Title : VPWS support in EVPN
Authors : Sami Boutros
Ali Sajassi
Hi Alvaro,
Please see comments inline. I have submitted 09.
Thanks,
Sami
>
>
>> > M4. Section 1.2 is titled Requirements. However, the list seems to
>> > include a combination of
>
>> > statements of fact (“EPL service access circuit maps to the whole Ethernet
>> > port”: this is pretty
Some nits/questions/comments:
Abstract
EVPN provides a flexible control plane that allows intra-subnet
connectivity in an IP/MPLS and/or an NVO-based network. In NVO
networks, there is also a need for a dynamic and efficient inter-
subnet connectivity across Tenant Systems and End Dev
While I would like to see this document advance eventually, I don't
think it is ready yet.
Main points:
- There is no clear explanation of the key concept of "overlay index".
In particular, there is no real explanation of when to use an overlay
index, or of when to use each kind of overlay i
10 matches
Mail list logo
