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

RE: [Issue 7] Message Authenticator

To: Avi Lior <avi@bridgewatersystems.com>
Subject: RE: [Issue 7] Message Authenticator
From: Bernard Aboba <aboba@internaut.com>
Date: Thu, 4 Nov 2004 08:56:15 -0800 (PST)
Cc: radiusext@ops.ietf.org
In-reply-to: <F17FB067A86B2D488382C923C532EAA7024A4D58@exch01.bridgewatersys.com>
References: <F17FB067A86B2D488382C923C532EAA7024A4D58@exch01.bridgewatersys.com>

> In this email you say: "Message-Authenticator was not required in RFC 2865,
>  so that it was not sent by legacy RADIUS-clients."
>
> On the issues list you say:
> [Bernard Aboba] Use of Message Authenticator is required by RFC 2865.

The issues list has a typo.  It was required by RFC 2869 only for messages
with EAP-Message attributes.

--
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:
- RE: [Issue 7] Message Authenticator
  - From: Avi Lior <avi@bridgewatersystems.com>

Prev by Date: RE: [Issue 7] Message Authenticator
Next by Date: Re: [Issue 7] Message Authenticator
Previous by thread: RE: [Issue 7] Message Authenticator
Next by thread: Re: [Issue 7] Message Authenticator
Index(es):
- Date
- Thread