Re: [Raw] "leg" vs "lane"

The term leg appears in existing literature (last I saw it getting used was
for SIP Call legs) and hence I too think it might be better to use the term
"lane" in the context of DAO projection. Would like to know if there was a
discussion/background on RAW/elsewhere about how the term lane originated.

After going through ver -29 of DAO projection (simply grepping for "leg"
and checking if "lane" makes more sense), here are some thoughts:
1. Section 2.2 in DAO projection -29 says, "The RAW Architecture also
defines the concepts of subTrack, Segment, leg, East-West, and more." but
I did not find any context of "Leg" or "subTrack" in that draft
<https://datatracker.ietf.org/doc/draft-ietf-raw-architecture/>. Maybe we
should fix this while at it.
2. Section 2.4.5.5 defines "Stand-Alone Track" ... but the remainder of the
text uses the term "Stand-Alone Segment". There is no reference of
"Stand-Alone Track" except in the terms section.
3. In all other contexts, the lane can be a suitable alternative to leg.

Regards,
Rahul

On Tue, 6 Dec 2022 at 12:52, Pascal Thubert (pthubert) <pthubert=
40cisco.com@dmarc.ietf.org> wrote:

> Dear all
>
> RAW has mostly completed its architecture work, for which the DAO
> projection work provides a useful component. We are in the process of
> cleaning up the terminology, juggling with the tension between
> compatibility with the IETF art when fit and avoiding confusion by
> overloading existing terms too much.
>
> As part of the review, we got a comment that the term "lane" could be
> appropriate for east west protection paths.
> The DAO projection draft introduced the term "leg" for this.
>
> I agree with the commenter that "lane" is a good term (probably better
> than "leg") and would like to sync RAW and ROLL on it, using the RAW
> architecture as the defining place for the concept.
>
> Please let me know if that's a bad idea, otherwise it will show in the
> next publication.
>
> All the best,
>
> Pascal
>
> --
> RAW mailing list
> RAW@ietf.org
> https://www.ietf.org/mailman/listinfo/raw
>