Section 4 appears to state the same requirement at two different strengths. The bullets say the VPN-specific IE "SHOULD be preferred", that it is "RECOMMENDED not to use the generic" IE for VPN flows, and that collectors "SHOULD prioritize" the VPN-specific IE; but a later bullet says the Exporting Process "MUST export the bgpVpnNextHopIPv4Address or bgpVpnNextHopIPv6Address IE instead of the generic ... IE for VPN flows". Is exporting the VPN-specific IE for VPN flows a MUST or a SHOULD? As written the SHOULD/RECOMMENDED bullets and the MUST bullet seem to overlap, and it would help interoperability to state the single intended normative level (and, if it is SHOULD, to note the valid exceptions).
On reference classification: the Terminology section says the document uses terms defined in RFC 7011, RFC 8402, and RFC 9252, and terms such as SRv6, Segment List, SID, and Segment Routing from RFC 8402 are used throughout the prose. RFC 9252 is listed as Normative but RFC 8402 is listed as Informative. Since a reader needs the RFC 8402 definitions to understand the document, should RFC 8402 be a Normative reference? On Security Considerations (Section 5): the reconnaissance/privacy discussion of exposing egress-PE next-hop addresses, SRv6 service SIDs, and locator lengths is a good addition, and the pointer to the RFC 7011/7012 considerations is appropriate. Since those IEs are sensitive, would it be worth stating explicitly (rather than only by reference) that the exporter-to-collector path should use the confidentiality and integrity protection described in RFC 7011 (e.g., TLS/DTLS), in addition to the at-rest access-control guidance already given? A few editorial nits. Missing spaces: "data plane[RFC8402]" (Sec 1), "best-effort(SRv6-BE)" (Sec 1), "new IEs(bgpVpnNextHopIPv4Address..." (Sec 4), and "Section 4 of [RFC9252]is used" (Sec 4). Grammar: "there's no other information that be related with the egress PE" (Sec 1) reads as if a word is missing - perhaps "that can be related to" or "that is related to"? P.
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
