>1) "Since EAP-TLS deployments may use more than one EAP
server, each with a different certificate, EAP peer implementations
SHOULD allow for the configuration of a unique trusted root (CA
certificate) to authenticate the server certificate and one or more
server names to match
On Jul 8, 2021, at 2:52 AM, tom.ri...@securew2.com wrote:
> Maybe this has been discussed already, but we often see the need for multiple
> root cas when people are migrating the root CA of their RADIUS server. They
> would then configure both the old and new Root CA in the client to allow
>
On Thu, Jul 8, 2021 at 6:11 AM Alan DeKok wrote:
> On Jul 8, 2021, at 2:52 AM, tom.ri...@securew2.com wrote:
> > Maybe this has been discussed already, but we often see the need for
> multiple root cas when people are migrating the root CA of their RADIUS
> server. They would then configure both
On Thu, Jul 8, 2021 at 8:31 AM Mohit Sethi M
wrote:
> Hi Oleg, Joe, all,
> On 7/8/21 8:06 AM, Joseph Salowey wrote:
>
>
>
> On Tue, Jul 6, 2021 at 10:08 PM Joseph Salowey wrote:
>
>>
>>
>> On Mon, Jun 28, 2021 at 8:11 AM Oleg Pekar
>> wrote:
>>
>>> I still see unclearness in Section "2.2.
I created PR that I think captures these suggestions and another editorial
fix - https://github.com/emu-wg/draft-ietf-emu-eap-tls13/pull/87
Cheers,
Joe
On Thu, Jul 8, 2021 at 9:36 AM Oleg Pekar wrote:
>
>
> On Thu, Jul 8, 2021 at 8:31 AM Mohit Sethi M
> wrote:
>
>> Hi Oleg, Joe, all,
>> On
On Jul 8, 2021, at 12:42 PM, Joseph Salowey wrote:
>
> I created PR that I think captures these suggestions and another editorial
> fix - https://github.com/emu-wg/draft-ietf-emu-eap-tls13/pull/87
I think it looks good.
Alan DeKok.
___
Emu