[Lake] Alissa Cooper's Block on charter-ietf-lake-00-00: (with BLOCK)

[Alissa Cooper via Datatracker <[e-mail]>]

Alissa Cooper has entered the following ballot position for
charter-ietf-lake-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-lake/



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

I have two questions I'd like to discuss before this goes out for external
review:

1. What are "the security properties expected of IETF protocols"? I think it
would be fair to conclude that different protocols have different security
properties. Is there a document to reference or some other way to convey what
is meant by this?

2. I'm a little unclear on the interaction between the "at most one" language
and the text about the TLS WG. If the TLS WG produces a LAKE that satisfies the
requirements that the LAKE WG specifies, would that count as the "one"? Or
might the TLS WG produce one and the LAKE WG produce one? Or is the TLS WG not
expected to work on a LAKE?