[Raw] Magnus Westerlund's Block on charter-ietf-raw-00-00: (with BLOCK)

[Magnus Westerlund via Datatracker <[e-mail]>]

Magnus Westerlund has entered the following ballot position for
charter-ietf-raw-00-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-raw/



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

This is not a particular hard Block. However, I think the sum of the comments
from the IESG recommends substantial rewording on the charter before it going
out for external review. I at least would like to see the reworked charter
before giving it a go-ahead to sending it out for external review. I personally
are especially interested if it can be clarified what the WG actually is
expected to produce.

I also have to ask the question, is Routing the right area? A lot of the text
appears to talk about issues that would be more at home in INT? This appears to
take a more architectural gap analysis. I understand that there is overlap into
both areas. However, if the target is to produce a gap analysis to figure out
where there are short comings in the IETF suit of protocols, are there going to
be any effort into identifying issues using this network for transport
protocols?

The LDACS text appears to implicitly indicate that the WG should consider how
to provide an IP solution for them. If such work is to be done I think that
needs its own home. Can the below part be changed to not imply such work:

" The Aeronautical standards work on a physical layer and data
link layer for data communications is reaching maturity and there is
significant interest in developing an IP connectivity solution."