[DMM] Re: (request to review) FW: New Versions - draft-ietf-dmm-tn-aware-mobility-21 and draft-jlu-dmm-udp-tunnel-acaas-00

[[e-mail]]

Hi John,
(ccing opsawg + dmm)
(without the AD Fez)

Sure. Please find a review of  draft-jlu-dmm-udp-tunnel-acaas at:

  *   pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2025/draft-jlu-dmm-udp-tunnel-acaas-00-rev%20Med.pdf
  *   doc: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2025/draft-jlu-dmm-udp-tunnel-acaas-00-rev%20Med.doc

I didn’t flag any major issue with the spec. I suggest you add some text to the introduction to exemplify cases where the UDP tunnel extension is needed. Also, please consider adding an example to illustrate the use of the extension.

For draft-ietf-dmm-tn-aware-mobility:


  *   I don’t understand the two modules mentioned here. I suggest you simply delete it:

CURRENT:
   The "ietf-ac-udpt" data module and "ietf-ac-udp-tunnel" YANG module
   for UDP tunnel port in this document are specified in
   [I-D.jlu-dmm-udp-tunnel-acaas].


  *   Idem, I don’t this full text is needed. A pointer to [I-D.jlu-dmm-udp-tunnel-acaas] and [I-D.ietf-opsawg-teas-attachment-circuit] would suffice.

CURRENT:
The UDP tunnel source port
   identifier defined in the ietf-ac-udp-tunnel YANG module are
   writable/creatable/deletable (i.e., config true, which is the
   default).  Write operations (e.g., edit-config) and delete operations
   to the 'udp-port' without proper protection or authentication can
   have a negative effect on network operations.  The 'udp-port'
   information may be used to track a customer of the slice service and
   may be considered a violation of the customer-provider trust
   relationship.  The data module and YANG model should conform to
   security constraints described in [I-D.jlu-dmm-udp-tunnel-acaas] and
   [I-D.ietf-opsawg-teas-attachment-circuit].


  *   Delete I-D.ietf-netmod-rfc8407bis, RFC3688, RFC4252, etc. from the ref list (please check of unused ones)

Hope this helps.

Cheers,
Med

De : Kaippallimalil John <[e-mail]>
Envoyé : mercredi 17 septembre 2025 18:50
À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>
Cc : LUIS MIGUEL CONTRERAS MURILLO <[e-mail]>
Objet : (request to review) FW: New Versions - draft-ietf-dmm-tn-aware-mobility-21 and draft-jlu-dmm-udp-tunnel-acaas-00


Hi Med,

Hope you are doing well!

Would you be able to have a quick review?

Thanks &
BR,
John


From: Satoru Matsushima <[e-mail]<mailto:[e-mail]>>
Sent: Friday, September 12, 2025 8:43 PM
To: Kaippallimalil John <[e-mail]<mailto:[e-mail]>>
Cc: Distributed Mobility Management Discussion List <[e-mail]<mailto:[e-mail]>>; dmm-chairs <[e-mail]<mailto:[e-mail]>>
Subject: Re: New Versions - draft-ietf-dmm-tn-aware-mobility-21 and draft-jlu-dmm-udp-tunnel-acaas-00

Thanks John, for all your efforts to proceed this work.

I would add a background on this sprit. During the last meeting an OPSAD who gave us his feedback, like it is ok to include the YANG module in the INFO draft. However another AD gave us opposite feedback. So the chairs and the authors decided to sprit the draft, which looks more likely and safer way.

DMMer, please review these drafts,
draft-ietf-dmm-tn-aware-mobility-21
 and
draft-jlu-dmm-udp-tunnel-acaas-00.

Cheers,
—satoru

2025年9月10日(水) 0:12 Kaippallimalil John <[e-mail]<mailto:[e-mail]>>:

Hi All,



As discussed in IETF-123, the authors split draft-dmm-tn-aware-mobility into two separate I-Ds: one that describes using UDP source port to map 3GPP slice to IP transport slice; and the second STDs track with YANG model for UDP bearer.



draft-ietf-dmm-tn-aware-mobility-21:

  *   No changes to methods/procedures (except removal of YANG model in old section 5)
  *   Security section is revised to focus on details of UDP source-port and otherwise refer to jlu-dmm-udp-tunnel-acaas security section.



draft-jlu-dmm-udp-tunnel-acaas-00

  *   STDs track draft with YANG model of section 5 in tn-aware-mobility-20, section 5. (no changes to data module or YANG model).
  *   Revised to remove all references to GTP-U so that the YANG model can be used for any UDP tunnel/bearer.
  *   Abstract and Introduction sections are new to be general they and align with opsawg-teas-attachment-circuit from which the UDP module inherits.
Security and IANA are practically copied from tn-aware-mobility-20.



As mentioned, these 2 drafts have no new methods or YANG models and have been thoroughly reviewed by dmm and members of teas for slicing and details of YANG model.

draft-jlu-dmm-udp-tunnel-acaas has changes to abstract, introduction (and minor revisions to security section) and should be reviewed by the group.



Diff of dmm-tn-aware-mobility 20 -> 21 shows the changes across these 2 drafts:

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dmm-tn-aware-mobility-21&data=05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C80ef45f3c7dc4bb4765308ddefae0d7a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638930253014015238%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=hLe05S3qKaOCI5xxAekWU8a8H941%2F161whMJMbivT0o%3D&reserved=0<https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-21>



Would appreciate reviews and feedback to progress these drafts as soon as possible.



Best Regards,

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.