Hi Roman,

Can you confirm that IANA can move ahead with these changes?

thanks,
Amanda

On Mon May 23 09:04:25 2022, [email protected] wrote:
> Hi Amanda and Roman,
> I have submitted the revised versions of those drafts as follows:
> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-capability-
> data-model-32
> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-nsf-facing-
> interface-dm-28
> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-nsf-monitoring-
> data-model-19
> 
> 
> Amanda,
> Could you reflect the requested changes related to IANA Sections on
> those
> three drafts?
> 
> Thanks.
> 
> Best Regards,
> Paul
> 
> On Mon, May 23, 2022 at 12:01 AM Mr. Jaehoon Paul Jeong <
> [email protected]> wrote:
> 
> > Hi Amanda and Roman,
> > I would like to change the YANG module names for naming consistency
> > for
> > the following three drafts:
> >
> > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-capability-data-
> > model/
> > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-facing-
> > interface-dm/
> >
> > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-monitoring-
> > data-model/
> >
> > -----------------------------------------------------------------------
> > 1. I2NSF Capability YANG Data Model Draft
> >
> > We want to update the YANG module's prefix as follows:
> > // nsfcap => i2nsfcap
> >
> > - OLD
> > ID: yang:ietf-i2nsf-capability
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> > capability.txt
> > Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> >
> > Name: ietf-i2nsf-capability
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> > Prefix: nsfcap
> > Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> > Notes: [RFC-ietf-i2nsf-capability-data-model-31]'s module file will
> > be
> > posted upon the document's publication as an RFC.
> > -----
> >
> > - NEW
> > ID: yang:ietf-i2nsf-capability
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> > capability.txt
> > Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> >
> > Name: ietf-i2nsf-capability
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> > Prefix: i2nsfcap
> > Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> > Notes: [RFC-ietf-i2nsf-capability-data-model-31]'s module file will
> > be
> > posted upon the document's publication as an RFC.
> > -----------------------------------------------------------------------
> >
> > 2. I2NSF NSF-Facing Interface YANG Data Model Draft
> >
> > We want to update the YANG module's name and prefix as follows:
> > // ietf-i2nsf-policy-rule-for-nsf => ietf-i2nsf-nsf-facing-interface
> > // nsfintf => i2nsfnfi
> >
> > - OLD
> > ID: yang:ietf-i2nsf-policy-rule-for-nsf
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-policy-rule-for-nsf
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> > policy-rule-for-nsf.txt
> > Reference: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]
> >
> > Name: ietf-i2nsf-policy-rule-for-nsf
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-policy-rule-for-nsf
> > Prefix: nsfintf
> > Reference: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]
> > Notes: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]'s module file will
> > be
> > posted upon the document's publication as an RFC.
> > -----
> >
> > - NEW
> > ID: yang:ietf-i2nsf-nsf-facing-interface
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-nsf-facing-interface
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-nsf-
> > facing-interface.txt
> > Reference: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]
> >
> > Name: ietf-i2nsf-nsf-facing-interface
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-nsf-facing-
> > interface
> > Prefix: i2nsfnfi
> > Reference: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]
> > Notes: [RFC-ietf-i2nsf-nsf-facing-interface-dm-27]'s module file will
> > be
> > posted upon the document's publication as an RFC.
> >
> > -----------------------------------------------------------------------
> > 3. I2NSF Monitoring Interface YANG Data Model Draft
> >
> > We want to update the YANG module's name and prefix as follows:
> > // ietf-i2nsf-nsf-monitoring => ietf-i2nsf-monitoring-interface
> > // nsfmi => i2nsfmi
> >
> > - OLD
> > ID: yang:ietf-i2nsf-nsf-monitoring
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-nsf-monitoring
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-nsf-
> > monitoring.txt
> > Reference: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]
> >
> > Name: ietf-i2nsf-nsf-monitoring
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:ietf-i2nsf-nsf-monitoring
> > Prefix: nsfmi
> > Reference: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]
> > Notes: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]'s module file
> > will be
> > posted upon the document's publication as an RFC.
> > -----
> >
> > - NEW
> > ID: yang:ietf-i2nsf-monitoring-interface
> > URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-monitoring-interface
> > Filename:
> > https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> > monitoring-interface.txt
> > Reference: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]
> >
> > Name: ietf-i2nsf-monitoring-interface
> > Maintained by IANA: N
> > Namespace: urn:ietf:params:xml:ns:ietf-i2nsf-monitoring-interface
> > Prefix: i2nsfmi
> > Reference: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]
> > Notes: [RFC-ietf-i2nsf-nsf-monitoring-data-model-18]'s module file
> > will be
> > posted upon the document's publication as an RFC.
> > -----------------------------------------------------------------------
> >
> > I attach a PDF file having the updates of the name and prefix of each
> > draft in summary.
> >
> > For these updates, we need to modify the code in the YANG modules in
> > those
> > I2NSF three drafts.
> >
> > I will submit the revised drafts having those updates this Monday
> > (May 24)
> > in Korean time.
> >
> > Thanks.
> >
> > Best Regards,
> > Paul
> >
> >
> > On Tue, May 17, 2022 at 3:16 AM Amanda Baber via RT <
> > [email protected]> wrote:
> >
> >> Dear Authors:
> >>
> >> ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED
> >>
> >> We've completed the registry actions for the following RFC-to-be:
> >>
> >> draft-ietf-i2nsf-capability-data-model-31
> >>
> >> ACTION 1:
> >>
> >> The following entry has been added to the IETF XML ns registry:
> >>
> >> ID: yang:ietf-i2nsf-capability
> >> URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> >> Filename:
> >> https://www.iana.org/assignments/xml-registry/ns/yang/ietf-i2nsf-
> >> capability.txt
> >> Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> >>
> >> Please see
> >> https://www.iana.org/assignments/xml-registry
> >>
> >> ACTION 2:
> >>
> >> The following entry has been added to the YANG Module Names
> >> registry:
> >>
> >> Name: ietf-i2nsf-capability
> >> Maintained by IANA: N
> >> Namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
> >> Prefix: nsfcap
> >> Reference: [RFC-ietf-i2nsf-capability-data-model-31]
> >> Notes: [RFC-ietf-i2nsf-capability-data-model-31]'s module file will
> >> be
> >> posted upon the document's publication as an RFC.
> >>
> >> Please see
> >> https://www.iana.org/assignments/yang-parameters
> >>
> >> Please let us know whether this document's registry actions have
> >> been
> >> completed correctly. Once we receive your confirmation, we'll notify
> >> the
> >> RFC Editor that the actions are complete. If a team of authors is
> >> responsible for the document, and the actions have been performed
> >> correctly, please send a single confirmation message.
> >>
> >> We'll update any references to this document in the registries when
> >> the
> >> RFC Editor notifies us that they've assigned an RFC number.
> >>
> >> Best regards,
> >>
> >> Amanda Baber
> >> IANA Operations Manager
> >>
> >>
> >>
> >>

_______________________________________________
I2nsf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2nsf

Reply via email to