A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Layer Security WG of the IETF.
Title : Delegated Credentials for (D)TLS
Authors : Richard Barnes
Subodh Iyengar
Hi Ekr,
On Mon, May 09, 2022 at 08:56:26AM -0700, Eric Rescorla wrote:
> On Mon, May 9, 2022 at 8:43 AM Benjamin Kaduk 40akamai@dmarc.ietf.org> wrote:
>
> > On Mon, May 09, 2022 at 06:10:43PM +0300, Yoav Nir wrote:
> > >
> > >
> > > > On 14 Apr 2022, at 1:51, Benjamin Kaduk >
On Mon, May 9, 2022 at 8:43 AM Benjamin Kaduk wrote:
> On Mon, May 09, 2022 at 06:10:43PM +0300, Yoav Nir wrote:
> >
> >
> > > On 14 Apr 2022, at 1:51, Benjamin Kaduk 40akamai@dmarc.ietf.org> wrote:
> > >
> > > On Wed, Apr 13, 2022 at 10:56:49AM -0700, Eric Rescorla wrote:
> > >> Consider
On Mon, May 09, 2022 at 06:10:43PM +0300, Yoav Nir wrote:
>
>
> > On 14 Apr 2022, at 1:51, Benjamin Kaduk
> > wrote:
> >
> > On Wed, Apr 13, 2022 at 10:56:49AM -0700, Eric Rescorla wrote:
> >> Consider the case where the client wants to offer some capability that
> >> the server then responds
Well, sounds like it's an open issue
My view is that it should be explicitly allowed, but I don't feel that
strongly about it. I do, however, feel strongly that the draft should say
explicitly one way or the other.
On Mon, May 9, 2022 at 8:10 AM Yoav Nir wrote:
>
>
> > On 14 Apr 2022, at 1:51,
> On 14 Apr 2022, at 1:51, Benjamin Kaduk
> wrote:
>
> On Wed, Apr 13, 2022 at 10:56:49AM -0700, Eric Rescorla wrote:
>> Consider the case where the client wants to offer some capability that
>> the server then responds to with real data, rather than just an
>> acknowledgement.
>>
>> For
Hi! We closed the loop on this one, and Roman wanted to make sure this got back.
> On Apr 4, 2021, at 06:57, Francesca Palombini via Datatracker
> wrote:
>
> Francesca Palombini has entered the following ballot position for
> draft-ietf-tls-exported-authenticator-14: No Objection
>
> When
Hi,
Thanks for this draft, which I found interesting and readable. I think it lays
out the problem well and proposes a conceptually straightforward solution that
will hopefully be less prone to implementation errors than more complex
options. However, there are a few points that I think