Hi authors, Please make sure to update -05 to drop mention of DF Types 2&3 (these are a Capability) and the pluralisation Nit raised below? Thanks !
Regards, Luc André Luc André Burdet | Cisco | [email protected] | Tel: +1 613 254 4814 From: Luc André Burdet <[email protected]> Date: Friday, December 6, 2019 at 11:49 To: "[email protected]" <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Mail regarding draft-ietf-bess-evpn-per-mcast-flow-df-election Hi authors, Quick note: can you make sure that in the next revision of this draft the DF Election EC section 3 is updated? Fast-DF-recovery is claiming 2 DF Capability bits, not DF-Types * Type 2: Handshake defines in [I-D.ietf-bess-evpn-fast-df-recovery<https://tools.ietf.org/html/draft-ietf-bess-evpn-per-mcast-flow-df-election-02#ref-I-D.ietf-bess-evpn-fast-df-recovery>] * Type 3: Time-Synch defined in [I-D.ietf-bess-evpn-fast-df-recovery<https://tools.ietf.org/html/draft-ietf-bess-evpn-per-mcast-flow-df-election-02#ref-I-D.ietf-bess-evpn-fast-df-recovery>] As a general comment to WG, the DF-Type and DF-Capabilities values are never pre-allocated for WG-adopted documents... making tracking & updating tedious. Can we at/before 107 request pre-allocation of some of these in the WG drafts that have stabilised? Nit: The current proposal extends the existing extended community defined in [I-D.ietf-bess-evpn-df-election-framework<https://tools.ietf.org/html/draft-ietf-bess-evpn-per-mcast-flow-df-election-02#ref-I-D.ietf-bess-evpn-df-election-framework>]. This draft defines new a DF type. -->Defines “two new DF Types” Regards, Luc André Luc André Burdet | Cisco | [email protected] | Tel: +1 613 254 4814
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
