Re: [Masque] Adoption call for "Requirements for a MASQUE Protocol to Proxy IP Traffic"

[Spencer Dawkins at IETF <[e-mail]>]

Hi, Chris,

On Wed, Sep 9, 2020 at 7:31 AM Christopher Wood <[e-mail]> wrote:

> One of the goals on our charter is producing a requirements document for
> IP proxying. draft-cms-masque-ip-proxy-reqs is one attempt at accomplishing
> this goal. Based on feedback received during the last meeting and the
> document revision since, we'd like to start an adoption call for this
> document in its current form as a starting point.
>
> The document may be found here:
>
>    https://datatracker.ietf.org/doc/draft-cms-masque-ip-proxy-reqs/


I'd like to see this document adopted (as the basis for future work).

I am sympathetic to Mirja's comment that we are still talking about use
cases. My suggestion would be adding tags to each requirement pointing to
the corresponding use case(s) with this requirement so that any use case we
punt that had unique requirements can be easily identified.

I don't have an opinion about whether this is adopted for WG usage or for
publication at this time. I do note that the working group can have that
conversation with the IESG at any time (including during IESG evaluation),
so my suggestion would be to take your best guess and know that your best
guess isn't locking anything in forever.

I do expect that this document will be of use within 3GPP (at least in SA2,
and perhaps other 3GPP working groups), but I don't know if they'll need a
normative dependency on something that gets published in the RFC series, so
don't worry about that as part of the publish/don't publish discussion.

One point that's worth mentioning is that some of our least helpful
documents were written as working group supporting documents, not
maintained while the target protocol was being specified, and then either
publication-requested in a form that was outdated or publication-requested
after a fire drill to do last minute cleanup. If the working group wants to
publish this as an RFC, please keep it updated on along the way!

Best,

Spencer