Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why limit scope to just IETF-defined modules #7

Open
kwatsen opened this issue Sep 14, 2015 · 4 comments
Open

Why limit scope to just IETF-defined modules #7

kwatsen opened this issue Sep 14, 2015 · 4 comments
Labels

Comments

@kwatsen
Copy link
Contributor

kwatsen commented Sep 14, 2015

Jonathan> Why does 7(A) limit the scope to IETF-defined modules of others are now defining YANG modules?

Benoit> Good point. We need to provide guidance for the other SDOs.

@kwatsen kwatsen changed the title Why does limit scope to just IETF-defined modules Why limit scope to just IETF-defined modules Sep 14, 2015
@kwatsen kwatsen added the NEW label Sep 18, 2015
@bclaise
Copy link

bclaise commented Sep 21, 2015

This issue will be taken care of in the Guidelines document RFC6087bis, for both the IETF and the other SDOs, once we agree on the solution.
It is covered by both:
netmod-wg/rfc6087bis#18
netmod-wg/rfc6087bis#22

I would change the requirement text like this.
OLD:

  7.  Ability for distinct modules to leverage a common model-structure
       A.  Scope is limited to IETF-defined modules
       B.  Multiple domain-specific trees are okay
       C.  Multiple namespaces are okay

NEW:

  7.  Ability for distinct modules to leverage a common model-structure
       A.  Focus on the IETF-defined modules, and ideally provides guidance to other SDOs
       B.  Multiple domain-specific trees are okay
       C.  Multiple namespaces are okay

@kwatsen kwatsen added VERIFY and removed NEW labels Sep 21, 2015
@kwatsen
Copy link
Contributor Author

kwatsen commented Sep 23, 2015

NEW:

   7.  Ability for distinct modules to leverage a common model-structure
        A.  Focus on the IETF-defined modules, and ideally provides guidance to other SDOs
        B.  Multiple domain-specific trees are okay
        C.  Model-structures may be defined in multiple modules with distinct namespaces.

If no one objects within 5 days, we will move forward with the NEW text listed above for requirement #7.

Thanks,
Kent

@kwatsen
Copy link
Contributor Author

kwatsen commented Sep 30, 2015

More than 5 days with no objections, moving to EDIT state.

@kwatsen kwatsen added EDIT and removed VERIFY labels Sep 30, 2015
kwatsen pushed a commit that referenced this issue Oct 5, 2015
@kwatsen kwatsen added REVIEW and removed EDIT labels Oct 5, 2015
@kwatsen kwatsen added DONE and removed REVIEW labels Dec 15, 2015
@kwatsen
Copy link
Contributor Author

kwatsen commented Dec 15, 2015

7-C was accepted in -00 draft (moving to DONE)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants