Erik Kline has entered the following ballot position for draft-ietf-bess-mvpn-evpn-sr-p2mp-15: Discuss
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-evpn-sr-p2mp/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- # Internet AD comments for draft-ietf-bess-mvpn-evpn-sr-p2mp-15 CC @ekline * comment syntax: - https://github.com/mnot/ietf-comments/blob/main/format.md * "Handling Ballot Positions": - https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/ ## Discuss ### S3.1.2 * "The advertising ingress PE MAY use a non-routable prefix as LOC of the SRv6 Multicast Service SID to prevent packets being routed to it based on the SID." Can you clarify what is intended here? I'm afraid I couldn't figure out what is meant by a non-routable prefix to prevent packets being routed to the advertising router. Possibly I just don't have the right mental model yet. Is this for some scenario where discarding traffic is desired? _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
