Re: [Privacy-pass] Working group last Call for batched Tokens

RIght now we only have one response to the last call which is not enough to
call consensus on.   It would be good to have a draft that is not expired,
but I also think before we can continue a consensus call we need a draft
with all the outstanding changes as well.

Thanks,

Joe

On Wed, Mar 20, 2024 at 3:37 AM Raphael Robert <ietf@raphaelrobert.com>
wrote:

> As soon as that issue is resolved I’ll make one more editorial pass before
> I cut a new draft. I’ll announce it here.
>
> Raphael
>
> On 20. Mar 2024, at 06:23, Steven Valdez <svaldez=
> 40google.com@dmarc.ietf.org> wrote:
>
> I think this draft looks mostly good and I support it going to the IESG.
> There is one outstanding issue #6
> <https://github.com/ietf-wg-privacypass/ietf-draft-privacypass-batched-tokens/issues/6>
> (I submitted and forgot to follow up on) regarding adding the VOPRF variant
> as a defined type since we're relying on that variant for PST. I can try to
> get a PR for that submitted, though not sure what the ordering between the
> draft being expired, the WGLC and cutting a new draft should look like?
>
> -Steven
>
> On Mon, Mar 11, 2024 at 2:47 PM Joseph Salowey <joe@salowey.net> wrote:
>
>> This is the working group last call for Batched Token Issuance Protocol (
>> https://datatracker.ietf.org/doc/draft-ietf-privacypass-batched-tokens/).
>> Please review the document and indicate if it is ready to forward to the
>> IESG by posting comments to this thread.  The internet draft is about to
>> expire but should still be accessible.  Please send your comments by March
>> 26, 2024.
>>
>> Thanks,
>>
>> Joe and Ben
>> --
>> Privacy-pass mailing list
>> Privacy-pass@ietf.org
>> https://www.ietf.org/mailman/listinfo/privacy-pass
>>
>
>
> --
>
>  Steven Valdez |  Chrome Privacy Sandbox |  svaldez@google.com |  Cambridge,
> MA
> --
> Privacy-pass mailing list
> Privacy-pass@ietf.org
> https://www.ietf.org/mailman/listinfo/privacy-pass
>
>
>