[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I-D Action:draft-ietf-radext-radsec-05.txt

To: radiusext@ops.ietf.org
Subject: Re: I-D Action:draft-ietf-radext-radsec-05.txt
From: Stefan Winter <stefan.winter@restena.lu>
Date: Mon, 13 Jul 2009 16:22:16 +0200
In-reply-to: <20090713141501.5DDC13A6D5B@core3.amsl.com>
References: <20090713141501.5DDC13A6D5B@core3.amsl.com>
User-agent: Thunderbird 2.0.0.19 (X11/20081227)

Hi,

this draft accomodates most of the comments received until now, with two
exceptions

- making the wording TCP-agnostic proved difficult and with the DTLS
content remaining a separate document does not appear to make sense any
more.
- the discussion about profiles for distinguishing clients is still
unresolved (see my earlier message about how to distinguish clients for
an automatic upgrade flagging of RADIUS -> RadSec)

Greetings,

Stefan Winter

-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

References:
- I-D Action:draft-ietf-radext-radsec-05.txt
  - From: Internet-Drafts@ietf.org

Prev by Date: I-D Action:draft-ietf-radext-radsec-05.txt
Next by Date: Re: Crypto-agility requirements: Compromise of Legacy Shared Secret (from Issue 303)
Previous by thread: I-D Action:draft-ietf-radext-radsec-05.txt
Index(es):
- Date
- Thread