Hi all,
I support adopting this document.
Some of the comments raised back in 05/2021 are still pending. I'm reiterating
them here, fwiw:
==
(1)
OLD:
import ietf-inet-types {
prefix inet;
}
NEW
import ietf-inet-types {
prefix inet;
reference
"RFC 6991: Common YANG Data Types, Section 4";
}
(2) Use the prefix as defined in 8520:
OLD:
import ietf-mud {
prefix mud;
}
NEW:
import ietf-mud {
prefix ietf-mud;
reference
"RFC 8520: Manufacturer Usage Description Specification";
}
(3)
You may remove the note about normative language in the description of the
module given that you don't use it.
(4)
OLD:
reference
"RFC XXXX: Extension for ownership and licensing";
NEW:
reference
"RFC XXXX: Ownership and licensing statements in YANG";
(5)
Rather than using "leaf-list owners", I would define this as a list keyed by
owners and which may include a leaf-list of licenses. Rather than defining
license as a choice, I would use a "union".
(6)
OLD:
"ol": {
"owners": [
"Copyright (c) FrobMaster 2021. All Rights Reserved"
],
"spdx-tag": "0BSD"
},
NEW:
"ietf-ol:ol": {
"owners": [
"Copyright (c) FrobMaster 2021. All Rights Reserved"
],
"spdx-tag": "0BSD"
},
(7) Please update the IANA section as follows:
OLD:
The IANA is requested to add "ol" to the MUD extensions registry as
follows:
Extension Name: ol
Standard reference: This document
NEW:
The IANA is requested the following entry to the MUD extensions registry
available at: https://www.iana.org/assignments/mud/mud.xhtml#mud-extensions
Extension Name: ol
Reference: This document
(8) Please update the IANA section with the following:
NEW
This document requests IANA to register the following URI in the "ns"
subregistry within the "IETF XML Registry" [RFC3688]:
URI: urn:ietf:params:xml:ns:yang:ietf-ol
Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace.
This document requests IANA to register the following YANG module in
the "YANG Module Names" subregistry [RFC6020] within the "YANG
Parameters" registry.
name: ietf-ol
namespace: urn:ietf:params:xml:ns:yang:ietf-ol
maintained by IANA: N
prefix: ol
reference: RFC XXXX
===
Cheers,
Med
> -----Message d'origine-----
> DeΒ : OPSAWG <opsawg-boun...@ietf.org> De la part de Henk Birkholz
> Envoyé : lundi 4 octobre 2021 22:00
> ΓΒ : opsawg <opsawg@ietf.org>
> ObjetΒ : [OPSAWG] π WG Adoption Call for draft-lear-opsawg-ol-01
>
> Dear OPSAWG members,
>
> this starts a call for Working Group Adoption of
>
> > https://datatracker.ietf.org/doc/html/draft-lear-opsawg-ol-01
>
> ending on Monday, October 18th.
>
> As a reminder, this I-D describes an extension to MUD that allows MUD file
> authors to specify ownership and licenses in the MUD files themselves. The
> corresponding YANG augment defined can be used outside the scope of MUD as
> well.
>
> Please reply with your support and especially any substantive comments you
> may have.
>
>
> For the OPSAWG co-chairs,
>
> Henk
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
_________________________________________________________________________________________________________________________
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
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
