On Tuesday, 19 July 2022 at 08:42 Thomas Fossati wrote:
> Hi Rob, Peter,
>
> On Thursday, 14 July 2022 at 16:07, Peter Saint-Andre
> wrote:
> > On 7/14/22 3:37 AM, Robert Wilton via Datatracker wrote:
> > > (4)
> > > When using RSA, servers MUST authenticate using certificates
> > > with
Hi Thomas,
From: iesg On Behalf Of Thomas Fossati
Sent: 18 July 2022 18:42
To: Peter Saint-Andre ; Rob Wilton (rwilton)
; The IESG
Cc: draft-ietf-uta-rfc7525...@ietf.org; uta-cha...@ietf.org; uta@ietf.org;
le...@sunet.se
Subject: Re: [Uta] Robert Wilton's Discuss on draft-ietf-uta-rfc7525bis-0
Hi Peter,
Thanks for the further information. I'm not sure whether we have quite met in
the middle yet, some further comments below.
> -Original Message-
> From: Peter Saint-Andre
> Sent: 18 July 2022 18:56
> To: Rob Wilton (rwilton) ; The IESG
> Cc: draft-ietf-uta-rfc7525...@ietf.or
Hi Rob, more follow-up inline.
On 7/19/22 3:42 AM, Rob Wilton (rwilton) wrote:
Hi Peter,
Thanks for the further information. I'm not sure whether we have quite met in
the middle yet, some further comments below.
-Original Message-
From: Peter Saint-Andre
Sent: 18 July 2022 18:56
T
Hi Peter,
More inline ...
> -Original Message-
> From: Peter Saint-Andre
> Sent: 19 July 2022 14:59
> To: Rob Wilton (rwilton) ; The IESG
> Cc: draft-ietf-uta-rfc7525...@ietf.org; uta-cha...@ietf.org; uta@ietf.org;
> le...@sunet.se
> Subject: Re: Robert Wilton's Discuss on draft-ietf-ut
Hi,
below is a draft charter for UTA WG session at IETF 114
(https://datatracker.ietf.org/meeting/114/materials/agenda-114-uta-00).
We still have some time, so if you want to make a presentation
or discuss some topic - you welcome.
Regards,
Leif & Valery.
Of course it's agenda, not charter :-)
> Hi,
>
> below is a draft charter for UTA WG session at IETF 114
> (https://datatracker.ietf.org/meeting/114/materials/agenda-114-uta-00).
> We still have some time, so if you want to make a presentation
> or discuss some topic - you welcome.
>
> Regards,
We're getting there. :-) See below.
On 7/19/22 9:14 AM, Rob Wilton (rwilton) wrote:
Hi Peter,
More inline ...
-Original Message-
From: Peter Saint-Andre
Sent: 19 July 2022 14:59
To: Rob Wilton (rwilton) ; The IESG
Cc: draft-ietf-uta-rfc7525...@ietf.org; uta-cha...@ietf.org; uta@ietf
>5 min. Administrativia (zulip scribes, note takers), Note Well, Agenda
> bashing
(chairs)
Can you include 6125bis here? A new draft was posted before the deadline
addressing the final WGLC issues.
___
Uta mailing list
Uta@ietf.org
Hi Rich,
> >5 min. Administrativia (zulip scribes, note takers), Note Well, Agenda
> > bashing
> (chairs)
>
> Can you include 6125bis here? A new draft was posted before the deadline
> addressing the final WGLC
> issues.
Sure. I also think that we can discuss an issue of 6125
Robert Wilton has entered the following ballot position for
draft-ietf-uta-rfc7525bis-09: Yes
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.)
Please refer to
https://w
Hi Peter,
> -Original Message-
> From: Peter Saint-Andre
> Sent: 19 July 2022 16:46
> To: Rob Wilton (rwilton) ; The IESG
> Cc: draft-ietf-uta-rfc7525...@ietf.org; uta-cha...@ietf.org; uta@ietf.org;
> le...@sunet.se
> Subject: Re: Robert Wilton's Discuss on draft-ietf-uta-rfc7525bis-09:
One more small note below...
On 7/19/22 10:30 AM, Rob Wilton (rwilton) wrote:
You may want to consider whether it is worth making it clearer, either in the
titles or the first intro paragraph, in section of 3.1.1/3.1.2 that the
protocol version requirements are specifically about implementa
On 7/19/22 10:44 AM, Peter Saint-Andre wrote:
One more small note below...
On 7/19/22 10:30 AM, Rob Wilton (rwilton) wrote:
You may want to consider whether it is worth making it clearer, either
in the titles or the first intro paragraph, in section of 3.1.1/3.1.2
that the protocol version
Peter St. Andre wrote:
> For example, based on knowledge about the deployed
> base for an existing application protocol and a cost-benefit analysis
> regarding cryptographic strength vs. computational load, a given
> service provider might decide to disable TLS 1.2 entirely and offer
> only TLS 1.3
15 matches
Mail list logo
