Greg Mirsky <[email protected]> writes: > Thank you for the review and your thoughtful questions. Please find my > notes below, tagged 'GIM>>'. I attached the new working version (it also > includes updates that address comments from RtgDir review).
My apologies for being slow to respond. Though none of my responses require any revisions. > I assume that the term "support XYZ" is understood to mean that the > BIER OAM specification MUST specify particular ways of doing XYZ, ... OK, I was not concerned about *me* knowing the exact meaning of "support" but rather that everybody in the WG had the same understanding of its import. Though I notice now that I didn't say that directly. However, you've made it clear that is the case. >> [...] Although I notice that requirements 2, >> 3, and 6 do not use the word "support"; do they apply to BIER OAM in a >> different way than the others? I take it that the answer is "No, requirements 2, 3, and 6 apply in the same way as the others." >> Is "unidirectional OAM" a known term of art? ... > GIM>> Thank you for this question. In general, some OAM mechanisms and > protocols are unidirectional, e.g., RFC 4656 A One-way Active Measurement > Protocol <https://datatracker.ietf.org/doc/html/rfc4656>. Thinking about a > better term, would "one-way" be clearer? Or, perhaps, replace > unidirectional with downstream? I will leave that to the wisdom of the WG. As long as everybody doing the work understands what the terminology means, whether it is obvious to *me* does not matter. >> 8. BIER OAM MUST support proactive monitoring of BFER availability >> by a BFR in the given BIER domain, e.g., p2mp BFD active tail >> support [RFC9780]. >> >> The phrase "by a BFR" seems ambiguous. ... >> > GIM>> The intention of the requirement is ensuring that any BFR in the BIER > domain may serve as a BFIR for a multicast distribution tree. Thus, the BFR > is required to monitor the leaves of the multicast distribution tree, i.e., > BFERs. I applied the proposed text to get the following: > NEW TEXT: > 8. BIER OAM MUST support the ability of any BFR in the given BIER > domain to proactively monitor BFER availability, e.g., p2mp BFD > active tail support [RFC9780]. Ah, yes, that seems to be completely unambiguous. The remaining queries I made seem to have been resolved in the same way, with full clarification of the ambiguities I was worried about. Dale _______________________________________________ Gen-art mailing list -- [email protected] To unsubscribe send an email to [email protected]
