Hello,

I have two comments regarding section 4.2


Comment 1:

draft-brissette-bess-evpn-mh-pa-04: “ES-Import RT community inherits from ESI 
only byte 1-7,”

As per RFC 7432, ES-Import RT community inherits from ESI only 6 (not 7, as in 
draft-brissette-bess-evpn-mh-pa-04) octets from ESI


Comment 2:

What is the benefit of restricting Modulo calculation to 5 octets only 
(draft-brissette-bess-evpn-mh-pa-04 specifies here octets 3-7), instead of 
taking all 9 (or even all 10) octets into account. For example, for HRW, RFC 
8584 already describes computing a 32 bit CRC over the concatenation of 
Ethernet Tag and ESI, so *all 10* ESI octets are used for better entropy. What 
is the benefit of restricting here for only subset of ESI octets?



Thanks,
Krzysztof


> On 2020 -Jan-21, at 17:58, Acee Lindem (acee) <a...@cisco.com> wrote:
> 
> Support – though I’ve always thought MC-LAG was a hack, it is part of the 
> landscape.
> Thanks,
> Acee
>  
> From: BESS <bess-boun...@ietf.org <mailto:bess-boun...@ietf.org>> on behalf 
> of "Bocci, Matthew (Nokia - GB)" <matthew.bo...@nokia.com 
> <mailto:matthew.bo...@nokia.com>>
> Date: Tuesday, January 21, 2020 at 9:51 AM
> To: "bess@ietf.org <mailto:bess@ietf.org>" <bess@ietf.org 
> <mailto:bess@ietf.org>>
> Cc: "draft-brissette-bess-evpn-mh...@ietf.org 
> <mailto:draft-brissette-bess-evpn-mh...@ietf.org>" 
> <draft-brissette-bess-evpn-mh...@ietf.org 
> <mailto:draft-brissette-bess-evpn-mh...@ietf.org>>, "bess-cha...@ietf.org 
> <mailto:bess-cha...@ietf.org>" <bess-cha...@ietf.org 
> <mailto:bess-cha...@ietf.org>>
> Subject: [bess] WG Adoption and IPR Poll for 
> draft-brissette-bess-evpn-mh-pa-04
>  
> Hello,
>  
> This email begins a two-weeks WG adoption poll for 
> draft-brissette-bess-evpn-mh-pa-04 [1] .
>  
> Please review the draft and post any comments to the BESS working group list.
>  
> We are also polling for knowledge of any undisclosed IPR that applies to this 
> Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
> rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
>  
> If you are listed as an author or a contributor of this document, please 
> respond to this email and indicate whether or not you are aware of any 
> relevant undisclosed IPR, copying the BESS mailing list. The document won't 
> progress without answers from all the authors and contributors.
>  
> Currently, there are no IPR disclosures against this document.
>  
> If you are not listed as an author or a contributor, then please explicitly 
> respond only if you are aware of any IPR that has not yet been disclosed in 
> conformance with IETF rules.
>  
> This poll for adoption closes on Tuesday 4th February 2020.  
>  
> Regards,
> Matthew and Stephane
>  
> [1] https://datatracker.ietf.org/doc/draft-brissette-bess-evpn-mh-pa/ 
> <https://datatracker.ietf.org/doc/draft-brissette-bess-evpn-mh-pa/>
>  
>  
>  
>  
>  
> _______________________________________________
> BESS mailing list
> BESS@ietf.org <mailto:BESS@ietf.org>
> https://www.ietf.org/mailman/listinfo/bess 
> <https://www.ietf.org/mailman/listinfo/bess>
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Reply via email to