I agree with Lionel on the document status, it should be INFO.

In addition, the yang module, "l3-tunnel-service" to be able to configure
UDP src port range, seems very much generic, and not necessarily to be
defined in the draft against the scope of the draft.
If we think that any yang modules which have ietf prefix name should be
STD, this small yang module would be better to get a more appropriate
draft, e.g., an ACasS related draft.

Best regards,
--satoru

On Thu, May 22, 2025 at 9:35 AM Lionel Morand <[email protected]>
wrote:

> Hi John,
>
>
>
> For the question regarding Informational vs Standards, there are two
> aspects:
>
>
>
> A/ there are two requested IANA actions:
>
>
>
>    - IANA is requested to register the following URI in the "ns"
>    subregistry within the "IETF XML Registry" [RFC3688]
>       - Registration Procedure(s): Specification Required
>    - IANA is requested to register the following YANG module in the "YANG
>    Module Names" subregistry [RFC6020] within the "YANG parameters" registry.
>       - Registration Procedure(s): RFC Required
>
>
>
> For both cases, Information RFC is enough.
>
>
>
> B/ Regarding the scope of the document, it is clearly for information.
>
>
>
> Therefore my conclusion is that this draft should be published as
> Informational RFC, as initially intended by the authors.
>
> Hope it clarifies my comment raised at the last IETF meeting.
>
>
>
> Regards,
>
>
>
> Lionel
>
>
>
> *From:* Kaippallimalil John <[email protected]>
> *Sent:* jeudi 22 mai 2025 02:08
> *To:* dmm <[email protected]>; dmm-chairs <[email protected]>; Satoru
> Matsushima <[email protected]>; LUIS MIGUEL CONTRERAS MURILLO <
> [email protected]>; Lionel Morand <
> [email protected]>
> *Subject:* revisions in draft-ietf-dmm-tn-aware-mobility-19
>
>
>
> Hi,
>
> Thanks to Satoru and Lionel for the detailed comments and reviews, and
> Luis for a good proposal to resolve it.
>
>
>
> Posted version 19 with all the updates proposed in the WG mailing list
> (links below for reference).
>
> Perhaps the only issue at this point is clarify the Information/Standards
> status for the draft.
>
> All other comments from the working group have been addressed and this
> draft is ready in our view to progress to the next step.
>
>
>
> Regards,
>
> John
>
>
>
>
>
> Links:
>
> URL:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-dmm-tn-aware-mobility-19.txt&data=05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C292251687851402ef6c008dd98c2c68a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638834684521447573%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=g6wj3OKoZS6cRixZF%2BvIH3OOT6ttRoFG%2FEcWDsBUrWc%3D&reserved=0
> <https://www.ietf.org/archive/id/draft-ietf-dmm-tn-aware-mobility-19.txt>
>
>
>
> Diff:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dmm-tn-aware-mobility-19&data=05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7C292251687851402ef6c008dd98c2c68a%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638834684521499049%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=m1o9sFkIDPH8%2B7%2Bz1bSCRL05lpgWdfUtJT51WQ0HlXg%3D&reserved=0
> <https://author-tools.ietf.org/iddiff?url2=draft-ietf-dmm-tn-aware-mobility-19>
>
>
>
>
>
_______________________________________________
dmm mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to