search

haomianzheng / IETF-ACTN-YANG-Model

IETF Optical YANG models in ACTN Architecture
4 stars 4 forks source link

Global text changes in draft-ietf-ccamp-layer1-types-03 after group renaming #44

Closed haomianzheng closed 4 years ago

haomianzheng commented 5 years ago

We have done the following group renaming: otn-label-restriction -> otn-label-range-info; otn-link-label -> otn-label-start-end; otn-path-label -> otn-label-hop

After the other issue is confirmed https://github.com/haomianzheng/IETF-ACTN-YANG-Model/issues/43, a global change would be needed for the whole draft, especially for the text in Section 4.3.

sergiobelotti commented 4 years ago

Reading version 4 of the draft, just uploaded last week, it seems you already provided alignment in the grouping names in seciton 4.3 : otn-label-restriction -> otn-label-range-info; otn-link-label -> otn-label-start-end; otn-path-label -> otn-label-hop The only leaf that is not described is the usage of range-bitmap in the label-restriction list.

italobusi commented 4 years ago

@sergiobelotti : the range-bitmap in the label-restriction list is used as defined in te-types. Should we describe its usage in the layer1-types?

sergiobelotti commented 4 years ago

@italobusi : when I made the comment above I've already checked description of range-bitmap in te-types, for me absolutely insufficent to understand usage in the case of OTN. In the case there is flexible mapping of a LO-ODU into ODUk , the usage of bit-map for any entry is essential to understand which TSs are assigned to any TP realted to the same ODU type. So the answer is yes, we should exploit section 4.3 in the draft to describe range-bitmap usage in OTN.

sergiobelotti commented 4 years ago

Issue closed with reference in the issue below https://github.com/tsaad-dev/te/issues/100