Skip to main content

Early Review of draft-ietf-teas-te-service-mapping-yang-10

Request Review of draft-ietf-teas-te-service-mapping-yang-09
Requested revision 09 (document currently at 15)
Type Early Review
Team YANG Doctors (yangdoctors)
Deadline 2022-03-11
Requested 2022-02-09
Requested by Vishnu Pavan Beeram
Authors Young Lee , Dhruv Dhody , Giuseppe Fioccola , Qin Wu , Daniele Ceccarelli , Jeff Tantsura
I-D last updated 2022-03-14
Completed reviews Yangdoctors Early review of -10 by Xufeng Liu (diff)
Requesting early Yang Doctors' Review
Assignment Reviewer Xufeng Liu
State Completed
Request Early review on draft-ietf-teas-te-service-mapping-yang by YANG Doctors Assigned
Posted at
Reviewed revision 10 (document currently at 15)
Result Almost ready
Completed 2022-03-14
This is a review of the YANG modules in

1) ietf-te-service-mapping-types@2022-03-07.yang

1.1) In list sr-policy, there is the line: “/*Headend should also be there!*/”.
I would agree with the comment since the color and (tail)-endpoint only
uniquely identify an sr-policy within the headend node. Does this mean that
something still needs to be done here?

1.2) As described in Sec 4.3.1. of RFC8407, child nodes within a container or
list SHOULD NOT replicate the parent identifier. The prefix “policy-” in
“policy-color-ref” and “policy-endpoint-ref” should be dropped.

1.3) Similar to 1.2), “te-mapping-template-ref” can be improved by dropping the
prefix “te-mapping”.

1.4) The leaf color under the container te-policy has no reference. Is this the
same as the “admin-group” defined in RFC 8776,  RFC 7308, RFC 5305, and RFC

1.5) In “map-type”, is the “map” the same as the “te-mapping” and
“te-service-mapping” in the parent containers? If these terms are the same, it
should be considered to drop the prefix “map”. Furthermore, these three terms
should be consistent, or their differences are explained.

1.6) In this YANG module, there are many lines of  “//grouping”. What are they
used for?

1.7) In this YANG module, there are section headers like “Typedef”, and
“Groupings”, etc., but there is no section header for “container
te-mapping-templates”, so it falls into the “Groupings” section, which is

1.8) One identity is named “detnet-hard-isolation”. Does it mean to use
“detnet” architecture and implementation as defined in the DETNET Working
Group? If so, more detailed descriptions on how to use would be good. If not,
it would be better to avoid the same term as used in

2) ietf-l3sm-te-service-mapping@2022-03-07.yang

2.1) This document uses the term “Layer 3 Service Model (L3SM)” which has been
changed to “L3VPN Service Delivery” by RFC 8299. The term “L3SM” is not used in
RFC 8299 any more, but is still used in this document extensively. Some
explanations in the document would be useful to avoid confusion.

2.2) Why is the container te-service-mapping “presence”? What does an empty
container te-service-mapping indicate?

2.3) Why is there container te-mapping under te-service-mapping? Are the two
containers duplicated?

2.4) In the augmentation to site-network-access, why is vn-ap a list, but ltp
single? It is notable that site-network-access is a list by itself, so we can
support multiple parallel access points by using multiple entries of the
site-network-access list.

2.5) In the YANG module, there are a few lines of “//augment”. What do they

2.6) The module l3vpn-svc supports two types of vpn-topology: any-to-any and
hub-spoke. For hub-spoke, there are site-roles of hub-role and spoke-role. It
would be beneficial for this document to describe how each type of vpn-topology
is mapped, and how the site-roles are mapped.

3) All modules

3.1) All leaves are optional. Please double-check and/or add meaningful
explanations. For example, for a template, what does an empty template do? For
a l3-tsm, what does an empty mapping do? Are there any implications when a leaf
is not configured?

3.2) There is no default on any leaf. Please double-check and/or add meaningful
explanations. For example, if availability-type is not configured, what is the
expected behavior?

4) Examples

4.1) Sec 3.12 in RFC 8407 requires that “Example modules MUST be validated”.
This can be done either by a validation tool or on a NETCONF/RESTCONF server.
Some notable issues with the current examples are: 4.1.1) There are no
namespaces on any of the data nodes. 4.1.2) Some leafref values need to appear
in the referenced module.

5) Editorial

5.1) Use of the term “YANG model”. The document mostly uses correct terms of
“YANG data model” and “YANG module”, but there are still occurrences of “YANG
model” that should be changed to “YANG data model”.

5.2) Sec 1.4. “Section 5 of this this document” should be “Section 6 of this

5.3)  “YANG codes” is better changed to “YANG modules”.

5.4) In each subsection of Sec 7, the document text does not have the
references to the RFCs cited in the YANG module. These references also need to
be listed in the document. Sec 5 of RFC7317 provides a good example.

5.5) “Import network model” should be “Import network module”. The "import"
statement makes definitions from one module available inside another module.

- Xufeng