[babel] Éric Vyncke's Discuss on draft-ietf-babel-applicability-07: (with DISCUSS and COMMENT)

[Éric Vyncke via Datatracker <[e-mail]>]

Éric Vyncke has entered the following ballot position for
draft-ietf-babel-applicability-07: Discuss

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.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


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



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Julius,

Thank you for the work put into this document. I have one DISCUSS and a couple
of COMMENTs.

One generic comment: is there a need to describe (even in a short format) Babel
again?

Regards,

-éric

== DISCUSS ==

-- Section 2.2 --

The 'bug resistance' property of Babel was perhaps learned during the
implementation, but, I wonder whether the document may simply state 'robust
with respect to bugs', this is quite a strong statement that needs to be backed
by facts or proof.


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

== COMMENTS ==

The title of the document is about 'applicability'; but, should it also include
'use cases' in the title ?

-- Section 3.1 --

The 2nd paragraph is too dense: should explain why Babel is a good fit.

-- Section 5 --

Comparison between HMAC & DTLS variants is probably irrelevant in this
document. Though, a use case with security in mind would be benefitial.

Also, the comparison should include all aspects including confidentiality and
anti-reply for both HMAC & DTLS.

== NITS ==

-- Section 2.2 --

As I am not a native English speaker, I wonder whether 'light' should not be
preferred to 'weak' in "These weak requirements make Babel a robust protocol"

-- Section 3.1 --

Suggest to change the section name into "Diverse networks" or "heterogenous
networks".