Hi All, Thanks Jorge for catching & provide feedback . Currently section 9.3 of the draft defines NLRI for Leave Sync Route. Which is defined as
https://tools.ietf.org/html/draft-ietf-bess-evpn-igmp-mld-proxy-04#section-9.3 +--------------------------------------------------+ | RD (8 octets) | +--------------------------------------------------+ | Ethernet Segment Identifier (10 octets) | +--------------------------------------------------+ | Ethernet Tag ID (4 octets) | +--------------------------------------------------+ | Multicast Source Length (1 octet) | +--------------------------------------------------+ | Multicast Source Address (variable) | +--------------------------------------------------+ | Multicast Group Length (1 octet) | +--------------------------------------------------+ | Multicast Group Address (Variable) | +--------------------------------------------------+ | Originator Router Length (1 octet) | +--------------------------------------------------+ | Originator Router Address (variable) | +--------------------------------------------------+ | Leave Group Synchronization # (4 octets) | +--------------------------------------------------+ | Maximum Response Time (1 octet) | +--------------------------------------------------+ | Flags (1 octet) | +--------------------------------------------------+ Currently there is no much detail added about Leave Group Sequence number (4 Octets). After having multiple discussion among authors, we do not think there is real use case for sequence number in this route. And we propose to remove the filed from NLRI. Usual Deployment: This route is limited to multi-home peer who are part of same ES. Most of deployment would have same vendor peers , so we do not see interop issue between different vendor (one with Sequence number and one without sequence number) RR Behavior to accommodate early implementation There may be an implementation which has included Sequence number in implementation. So RR MUST accept both length of NLRI (With sequence number and without sequence number). Change to Draft: * Leave Group Synchronization would be removed from section 9.3 * Text would be added that RR MUST accept & reflect EVPN route type 8 with current length and with current length +4 There is plan to go over this change in room as well in Singapore . Mankamana
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
