Murray Kucherawy has entered the following ballot position for
draft-ietf-rtgwg-net2cloud-problem-statement-41: Abstain

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/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-net2cloud-problem-statement/



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

John's and Paul's primary DISCUSS positions nicely articulate the reason for
this ABSTAIN.  You might be able to make this more palatable by removing the
specific product references and instead find a way to be more generic (some
providers do X, others do X with variant Y, still another does Z), but it's
going to take a bit of work if you want to go that route.  You got all the way
to Section 3.6 without them, for example.

Other comments:

None of the authors claim to represent the cloud operators referenced in the
document, and I'm not familiar with all of the names in Section 10, so I'll
ask: Did this document get feedback or input from any of those operators?

The Abstract says 2023 but at this point we're pretty far into 2024.  Is this
material still timely?

As this document is Informational, I don't think you should use BCP 14.  (It's
barely used anyway.)

Section 2 defines "Heterogeneous Cloud", but this term is not used elsewhere in
the document.

In Section 3.5, I recommend quoting ".internal".  It looks like a syntax error
without the quoting, at least as rendered in HTML.

Shouldn't references like [AWS-NAT] have links or some other actual followable
reference?



_______________________________________________
rtgwg mailing list -- rtgwg@ietf.org
To unsubscribe send an email to rtgwg-le...@ietf.org

Reply via email to