Sorry, but this has the same problem in figure 11.1 that we've just been
discussing with Ian.
For it to work, (a) the prefix in the alarm-category element MUST be the
same as the namespace prefix for
urn:ietf:params:xml:ns:yang:ietf-i2nsf-nsf-monitoring, which means that XML
software MUST be chosen that makes the namespace prefix information
available. I don't think it's OK for the draft not to say those thigns.
<alarm-category
xmlns:nsfmi="urn:ietf:params:xml:ns:yang:\
ietf-i2nsf-nsf-monitoring">
nsfmi:memory-alarm
</alarm-category>
On Thu, Dec 16, 2021 at 4:25 PM Amanda Baber via RT <
[email protected]> wrote:
> Hi Tim and Martin (cc: i2nsf WG),
>
> Have you had a chance to review the XML registration in this document?
>
>
> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-monitoring-data-model/
>
> thanks,
> Amanda
>
> On Tue Nov 30 21:38:22 2021, michelle.cotton wrote:
> > Dear Tim and Martin,
> > (cc to i2nsf WG)
> >
> > As the designated experts for the ns IETF xml registry, can you review
> > the proposed registration in draft-ietf-i2nsf-nsf-monitoring-data-
> > model-12 for us? Please see
> >
> > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-monitoring-data-
> > model/
> >
> > If this is OK, when the IESG approves the document for publication,
> > we'll make the registration at
> >
> > https://www.iana.org/assignments/xml-registry
> >
> > The IESG has asked us to set a two-week deadline for registration
> > reviews. The due date for this request is 14 December 2021.
> >
> > Thank you,
> >
> > Michelle Cotton
> > IANA Services
>
>
_______________________________________________
I2nsf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2nsf
