Ho John, all,
Please find below some few (minor) comments about this version:
(1) Fix a validation warning
The datatracker shows this warning: "libyang warn: Schema node "type" for
parent
"/ietf-ac-svc:attachment-circuits/ac/ip-connection/l3-service/l3-tunnel-service/l3-tunnel-service"
not found; in expr "derived-from-or-self(./type" with context node
"/ietf-ac-svc:attachment-circuits/ac/ip-connection/l3-service/l3-tunnel-service/l3-tunnel-service"."
You can fix that as follows:
OLD:
augment "/ac-svc:attachment-circuits/ac-svc:ac"
+ "/ac-svc:ip-connection/ac-svc:l3-service"
+ "/ac-svc:l3-tunnel-service/ac-svc:l3-tunnel-service" {
when "derived-from-or-self(./type, 'ac-udpt:udp')" {
^^^^^^^^
NEW:
augment "/ac-svc:attachment-circuits/ac-svc:ac"
+ "/ac-svc:ip-connection/ac-svc:l3-service"
+ "/ac-svc:l3-tunnel-service/ac-svc:l3-tunnel-service" {
when "derived-from-or-self(./ac-svc:type, 'ac-udpt:udp')" {
(2) Update all AC I-D references to point the published RFCs.
(3) Although this is an example, consider adding a reference for GTP-U for
readers convenience
CURRENT:
An example of Layer 3 UDP
tunnel as a bearer is in 5G networks where a GTP-U (UDP) bearer is
used to transport datagrams of a mobile end-user between 3GPP user
plane functions.
(4) Better description
OLD:
Section 2 describes the "ietf-ac-udpt" YANG module
for Layer 3 UDP tunnel service. Section 3 describes the UDP tunnel
YANG data model.
NEW:
Section 2 describes the "ietf-ac-udpt" YANG module
for Layer 3 UDP tunnel service defined in Section 3.
(5) Bearers
OLD:
[I-D.ietf-opsawg-teas-attachment-circuit] defines a YANG service
model for AC based on layer 2 bearers.
NEW:
[I-D.ietf-opsawg-teas-attachment-circuit] defines a YANG service
model for AC based on underlying bearers.
A bearer is a defined as a logical link. Better to add restrictions on what is
a bearer in this doc.
# Add 8085 to the informative references
CURRENT:
reference
"RFC 8085: UDP Usage Guidelines, Section 3.1.11";
# Update the second par of Section 5 to follow the template in 8407bis
# Normative references
The following should be listed as normative:
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
# Unused reference
This one is not used:
[RFC8972] Mirsky, G., Min, X., Nydell, H., Foote, R., Masputra, A.,
and E. Ruffini, "Simple Two-Way Active Measurement
Protocol Optional Extensions", RFC 8972,
DOI 10.17487/RFC8972, January 2021,
<https://www.rfc-editor.org/info/rfc8972>.
# RFC 8792 needs to be cited as reference as this is needed for unfolding
CURRENT:
=============== NOTE: '\' line wrapping per RFC 8792 ================
# Move " Appendix A. Abbreviations" to be listed in the main document. You can
put it right under a terminology section.
Hope this helps.
Cheers,
Med
> -----Message d'origine-----
> De : Kaippallimalil John <[email protected]>
> Envoyé : jeudi 6 novembre 2025 16:46
> À : opsawg <[email protected]>; [email protected]; Mahesh Jethanandani
> <[email protected]>; BOUCADAIR Mohamed INNOV/NET
> <[email protected]>
> Cc : Satoru Matsushima <[email protected]>; Sri
> Gundavelli (sgundave) <[email protected]>
> Objet : Request for OPSAWG review of draft-jlu-dmm-udp-tunnel-
> acaas-01
>
>
> Hi,
>
> In the DMM session on Monday (11/03) the draft-jlu-dmm-udp-tunnel-
> acaas-01 was discussed and the chairs (copied here) plan to issue
> a WG adoption call in the next couple of weeks.
>
> We would like to request reviews from OPSAWG as this draft has
> YANG model for Layer 3 (UDP) ACaaS.
>
> Link to the draft:
> [draft-jlu-dmm-udp-tunnel-acaas-01]:
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> author-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-jlu-dmm-udp-tunnel-
> acaas-
> 01&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cc6092ec0a098474
> 72b4b08de1d4b9d62%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638
> 980407777425213%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIl
> YiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D
> %7C0%7C%7C%7C&sdata=4TyCfTJ3cI%2BaqUvbYrYabSH4JghmWFVwZ1OzikdxzgU%
> 3D&reserved=0
>
> Thanks,
> John
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
