Re: [Manycouches] Éric Vyncke's No Objection on draft-ietf-shmoo-remote-fee-08: (with COMMENT)

Hi Eric,

thanks for your review!

Please see quickly below, marked with [MK].

On 24.08.23, 11:23, "Eric Vyncke (evyncke)" <evyncke@cisco.com> wrote:

    Hello Rich,

    Thanks for your reply. As you know, my comments are "just" comments, but I appreciate the interaction.

    See below for EV>

    Regards

    -éric

    On 23/08/2023, 23:52, "Salz, Rich" <rsalz@akamai.com <mailto:rsalz@akamai.com>> wrote:

    # COMMENTS

    > Like Paul Wouters, I find that there is some confusions between 'free option'
    and 'fee waiver', e.g., the I-D could clearly mention that "fee waivers" is
    just one way to have a "free option".

    Does this work?
    -there should always be a free option to make the process as open as possible. Having said that,
    +there should always be a free option to make the process as open as possible.
    +(One example of implementing this is to have the ability to request a fee
    +waiver.)
    +Having said that,

    EV> much clearer. Thanks.

    > ## Section 2

    > `must be kept confidential.` is probably underspecified: could it be visible to
    > the IETF secretariat ? to the IETF LLC ?

    As Mirja has said, we want to avoid getting too much into implementation details, so specifying this seems wrong and subject to change if other mechanisms are used.

[MK] I agree with Rich here. The point is this information should not be publicly available. This is also true for some of the other (registration) info the secretariat hold. It's actually covered by e.g. the GDPR if and how such information can be used for monitoring. I don't think we should get further into details here.

    > ## Section 3

    >`If unlimited free remote participation is determined` by who ?

    By those responsible for the financial viability of the meeting and the IETF overall. I hope that is clear from context especially since the tail end of the sentence refers to the LLC.

[MK] I think this would be the LLC but it could also be "the community". However, I think for this sentence it doesn't matter. The sentence is say, if there is a problem, the LLC need to take action. We purposefully do not specify in detail who to detect a problem because it really depends on what the problem is. However, if the problem is, we are running out of money, I'm pretty sure the LLC would be the one bringing it up.

    > `assessment of eligibility` to what ?

[MK] Really? Eligibility on use of the free option... this is what the whole document is about... we could add that but this really seems clear enough to me. But to ensure I understand your concern: can you further explain how this could be interpret in any other way?

    Again, I think context provides enough detail, as seen in the next line of the sentence.

    EV> for the 3 points above, we disagree about the context being enough. My own taste is to be crisp in the statements.

    > ## Authors' Addresses

    > It seems that Rich's address is missing.

    Strange, looks okay locally. Oh well, something the RPC can address if necessary.

    EV> possibly, a rendering issue indeed, RPC will take care of it if the metadata is there.

    _______________________________________________
    Manycouches mailing list
    Manycouches@ietf.org <mailto:Manycouches@ietf.org> <mailto:Manycouches@ietf.org <mailto:Manycouches@ietf.org>>
    https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/manycouches__;!!GjvTz_vk!UXNkEBPTYpxUwEBsWfkgqvKze1LOuxwo-znJYQAO32OGQDJ01910JOEJmBkcBdVbRbsGm3LUmkj6$ <https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/manycouches__;!!GjvTz_vk!UXNkEBPTYpxUwEBsWfkgqvKze1LOuxwo-znJYQAO32OGQDJ01910JOEJmBkcBdVbRbsGm3LUmkj6$> <https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/manycouches__;!!GjvTz_vk!UXNkEBPTYpxUwEBsWfkgqvKze1LOuxwo-znJYQAO32OGQDJ01910JOEJmBkcBdVbRbsGm3LUmkj6$ <https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/manycouches__;!!GjvTz_vk!UXNkEBPTYpxUwEBsWfkgqvKze1LOuxwo-znJYQAO32OGQDJ01910JOEJmBkcBdVbRbsGm3LUmkj6$>> 