Closed renghardt closed 2 years ago
I think it should be sufficient to add a few sentences to Section 2.1 to address the issue of contexts for specific technologies. I would not put it in the introduction, since in my opinion it is not necessary to think about different contexts to understand the terminology.
At the IETF 112 PANRG session, Sabine Randriamasy brought up the point that a definition can be relative to different scopes, e.g., an endpoint can mean different things in routing VS transport, or for flows VS applications.
While Section 2.1 of the path properties draft already mentions that the terminology in the document is applicable to different technologies, maybe it should mention the different contexts as well. Or this could be part of the introduction.
Quoting from two emails by @cyrill-k: