Re: [CCAMP] I-D Action: draft-ietf-ccamp-mw-yang-12.txt

[Daniele Ceccarelli <[e-mail]>]

Hi Jonas,

the draft is now in AD followup status, hence managed by Deborah.
You can agree offline with her on how to proceed. Probably a revised id is the best way.

BR
Daniele  

> -----Original Message-----
> From: CCAMP <[e-mail]> On Behalf Of Jonas Ahlberg
> Sent: domenica 11 novembre 2018 11:51
> To: tom petch <[e-mail]>; [e-mail]
> Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-mw-yang-12.txt
> 
> Hi Tom,
> 
> Yes, you are perfectly correct!
> 
> We talked to IANA representatives on Thursday last week at IETF 103 and
> they helped us to apply for two new IANA IfTypes, with the purpose to get
> them registered as ifType definitions in [IANA registry smi-numbers].
> I think we have followed the correct procedure, but I have described it
> incorrectly in the updated draft where I reference RFC7224.
> 
> We also understand that this is a change very late in the process, so before
> going ahead with it we talked to and got an OK from Deborah (responsible
> AD).
> 
> One question is now what to do about the incorrect description of the IANA
> request in the draft. Should I update it right away, reach out to IANA or wait
> for a formal response from them before doing an update.
> 
> Regards
> JonasA
> 
> 
>  -----Original Message-----
> From: tom petch <[e-mail]>
> Sent: den 9 november 2018 18:35
> To: Jonas Ahlberg <[e-mail]>; [e-mail]
> Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-mw-yang-12.txt
> 
> ----- Original Message -----
> From: "Jonas Ahlberg" <[e-mail]>
> To: <[e-mail]>
> Sent: Friday, November 09, 2018 3:37 AM
> 
> > As Amy explained in an earlier mail, this a minor update of
> draft-ietf-ccamp-mw-yang where we have asked IANA to register new
> IANAifTypes for the interface types radio-link-terminal and carrier-
> termination in the "IANA Interface Type YANG Module" [RFC7224], instead
> of defining them locally in the ietf-microwave-types module.
> 
> Jonas
> 
> That is not right - in fact, it is wrong.  RFC7224 provided the initial contents of
> the YANG module and as the IANA website says,
> 
> Interface types must not be directly added to the iana-if-type YANG module.
> They must instead be added to the "ifType definitions" registry at [IANA
> registry smi-numbers].
> 
> after which, IANA updates the IANA-maintained MIB module and the IANA-
> maintained YANG module.
> 
> Your request should be for the registration of an ifType definition (which
> dates back to RFC1213) which, if the Designated Expert approves, will result
> in both IANA-maintained modules being updated.
> 
> And the request for registration can be made in any suitable way to IANA - an
> e-mail does fine - as long as there is a stable definition for the Designated
> Expert to examine.  So, no need to re-issue the I-D.
> 
> However, what is done is done and I trust IANA to read between the lines
> and do what is wanted even if the IANA Considerations in the latest I-D are
> not quite what they might be.  One problem to which I do not know the
> answer:-) is what happens with the I-D changing after the IESG have
> approved it n earlier version  - never a good idea, but more work for the AD
> to sort:-(
> 
> Question is, are we going to go through all this effort all over again for such as
> TEAS and MPLS?  My guess would be yes:-(.
> 
> Tom Petch
> 
> > Regards
> > JonasA
> >
> > -----Original Message-----
> > From: CCAMP <[e-mail]> On Behalf Of
> [e-mail]
> > Sent: den 9 november 2018 10:30
> > To: [e-mail]
> > Cc: [e-mail]
> > Subject: [CCAMP] I-D Action: draft-ietf-ccamp-mw-yang-12.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Common Control and Measurement Plane
> WG of the IETF.
> >
> >         Title           : A YANG Data Model for Microwave Radio Link
> >         Authors         : Jonas Ahlberg
> >                           Ye Min
> >                           Xi Li
> >                           Daniela Spreafico
> >                           Marko Vaupotic
> > Filename        : draft-ietf-ccamp-mw-yang-12.txt
> > Pages           : 51
> > Date            : 2018-11-08
> >
> > Abstract:
> >    This document defines a YANG data model for control and management
> of
> >    the radio link interfaces, and their connectivity to packet
> >    (typically Ethernet) interfaces in a microwave/millimeter wave
> node.
> >    The data nodes for management of the interface protection
> >    functionality is broken out into a separate and generic YANG data
> >    model in order to make it available also for other interface types.
> >
> > RFC Ed.  Note
> >
> >    // RFC Ed.: replace all XXXX throughout the document with actual
> RFC
> >    numbers and remove this note
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-ccamp-mw-yang/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-ccamp-mw-yang-12
> > https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-mw-yang-12
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-mw-yang-12
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > CCAMP mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/ccamp
> >
> > _______________________________________________
> > CCAMP mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/ccamp
> 
> _______________________________________________
> CCAMP mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ccamp