[ianabis] Mohamed Boucadair's Block on charter-ietf-ianabis-01-00: (with BLOCK and COMMENT)

[Mohamed Boucadair via Datatracker <[e-mail]>]

Mohamed Boucadair has entered the following ballot position for
charter-ietf-ianabis-01-00: Block

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-ianabis/



----------------------------------------------------------------------
BLOCK:
----------------------------------------------------------------------

# Implications

CURRENT:
   Lastly, the working group may consider combining the two documents into a
   single BCP.

We would break all https://datatracker.ietf.org/doc/bcp26/referencedby/ if we
change BCP 26 with a new umbrella. Given
https://datatracker.ietf.org/doc/bcp100/, I would be more explicit here and say
that revision of 7210 may be considered to be under BCP26.

NEW:
   Lastly, the working group may consider combining the two documents into BCP
   26.

# Plan for other specs that update 8126

I’m aware at least about draft-ietf-netmod-rfc8407bis which is tagged as
updating 8126. Do we plan to re-include such considerations as part of 8126bis
or this can be handled by external reference for specific IANA actions.

I think that we need a provision for such checks in the candidate revision work.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

# nit

OLD: These form a critical function in many protocol frameworks
NEW: These BCPs form a critical function in many protocol frameworks

# nit

OLD: The current version of BCP 26 was published in 2017
NEW: The latest version of BCP 26 was published in 2017

# nit

Be consistent through the charter:  IANABIS Working Group vs. IANABIS working group

# nit

Bullet lists: s/;/, or  simply s/;/. and s/; and/.