Hi Greg, Menachem: I believe during the Greg’s presentation at the BESS WG (which I was attending remotely), I voiced my concerns regarding mandating control word for all cases. So, let me repeat it in context of your comment:
Why do we need to mandate control word when all nodes in a network use entropy label for ECMP load balancing? Cheers, Ali From: Greg Mirsky <gregimir...@gmail.com> Date: Thursday, May 30, 2024 at 8:20 PM To: Menachem Dodge <mdo...@drivenets.com>, draft-ietf-bess-rfc7432...@ietf.org <draft-ietf-bess-rfc7432...@ietf.org>, bess@ietf.org <bess@ietf.org> Cc: draft-ietf-mpls-1stnib...@ietf.org <draft-ietf-mpls-1stnib...@ietf.org> Subject: Re: [bess] FW: I-D Action: draft-ietf-bess-rfc7432bis-09.txt Dear All, I share Menachem's concerns and welcome feedback from the authors. Regards, Greg On Sun, May 5, 2024 at 12:33 AM Menachem Dodge <mdo...@drivenets.com<mailto:mdo...@drivenets.com>> wrote: Hello Authors, Just wondering why none of the discussion held at Brisbane meeting in March and subsequently on the emailing list regarding the PFN ( see the emails with subject: “Re: [bess] PFN questions in rfc4732bis” ) requesting changes in setion 7.11.1 and section 18 , were not included in the latest draft update. I think the last email on this subject was sent on 15th April 2024. In section 7.11 following the discussions I think that the following sentence should be removed: “It is recommended that the control word be included in the absence of an entropy label [RFC6790].” In section 18 “If a network (inclusive of all PE and P nodes) uses entropy labels per [RFC6790] for ECMP load balancing, then the control word may not be used. Should be changed to: “If a network (inclusive of all PE and P nodes) uses entropy labels per [RFC6790] for ECMP load balancing, then the control word should be used, refer to draft-ietf-mpls-1stnibble Thank you kindly, Best Regards, Menachem Dodge From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> on behalf of internet-dra...@ietf.org<mailto:internet-dra...@ietf.org> <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>> Date: Friday, 3 May 2024 at 7:42 To: i-d-annou...@ietf.org<mailto:i-d-annou...@ietf.org> <i-d-annou...@ietf.org<mailto:i-d-annou...@ietf.org>> Cc: bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>> Subject: [bess] I-D Action: draft-ietf-bess-rfc7432bis-09.txt CAUTION: External E-Mail - Use caution with links and attachments Internet-Draft draft-ietf-bess-rfc7432bis-09.txt is now available. It is a work item of the BGP Enabled ServiceS (BESS) WG of the IETF. Title: BGP MPLS-Based Ethernet VPN Authors: Ali Sajassi Luc Andre Burdet John Drake Jorge Rabadan Name: draft-ietf-bess-rfc7432bis-09.txt Pages: 73 Dates: 2024-05-02 Abstract: This document describes procedures for Ethernet VPN (EVPN), a BGP MPLS-based solution which addresses the requirements specified in the corresponding RFC - "Requirements for Ethernet VPN (EVPN)". This document obsoletes RFC7432 (BGP MPLS-Based Ethernet VPN) and updates RFC8214 (Virtual Private Wire Service Support in Ethernet VPN). The IETF datatracker status page for this Internet-Draft is: https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Drfc7432bis_&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=cezglEhs6Oa_CKN9mhFbT8T8kmWwaNdtBDjE9bvBG_E&m=gDpQwIZuZSEOcOuIUV_9_jeGv5m-aqXgzBMzkuCM8wBeIKaKwaQUthJPFuNNZ9Dh&s=Xt33XJv3urxYTFARXBfpdw-RopowitrC7SWSv-L-QBY&e= There is also an HTMLized version available at: https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dietf-2Dbess-2Drfc7432bis-2D09&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=cezglEhs6Oa_CKN9mhFbT8T8kmWwaNdtBDjE9bvBG_E&m=gDpQwIZuZSEOcOuIUV_9_jeGv5m-aqXgzBMzkuCM8wBeIKaKwaQUthJPFuNNZ9Dh&s=oBT0K_2O-jJC2YfcS2X7Srom1ebB2VtVjfyN0CSBZpw&e= A diff from the previous version is available at: https://urldefense.proofpoint.com/v2/url?u=https-3A__author-2Dtools.ietf.org_iddiff-3Furl2-3Ddraft-2Dietf-2Dbess-2Drfc7432bis-2D09&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=cezglEhs6Oa_CKN9mhFbT8T8kmWwaNdtBDjE9bvBG_E&m=gDpQwIZuZSEOcOuIUV_9_jeGv5m-aqXgzBMzkuCM8wBeIKaKwaQUthJPFuNNZ9Dh&s=qjFH58VBc_cT930wv8yqvpU4plxuyfST4kkQHhRr5q4&e= Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ BESS mailing list BESS@ietf.org<mailto:BESS@ietf.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=cezglEhs6Oa_CKN9mhFbT8T8kmWwaNdtBDjE9bvBG_E&m=gDpQwIZuZSEOcOuIUV_9_jeGv5m-aqXgzBMzkuCM8wBeIKaKwaQUthJPFuNNZ9Dh&s=4yKmOpDzDXQKtaAvqAg7SgerPvw_i4yaPZHnS0nl7vE&e= _______________________________________________ BESS mailing list BESS@ietf.org<mailto:BESS@ietf.org> https://www.ietf.org/mailman/listinfo/bess
_______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org
