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

RE: Issue 223: Event-Timestamp and Duplicate Detection

To: "Alan DeKok" <aland@nitros9.org>, "Bernard Aboba" <bernard_aboba@hotmail.com>
Subject: RE: Issue 223: Event-Timestamp and Duplicate Detection
From: "Avi Lior" <avi@bridgewatersystems.com>
Date: Fri, 25 May 2007 11:55:16 -0400
Cc: <radiusext@ops.ietf.org>
In-reply-to: <45FE48AF.6080506@nitros9.org>
References: <BAY117-F27B7344B6808B0B019F0B693760@phx.gbl> <45FE48AF.6080506@nitros9.org>

> RFC 2869 Section 5.3, appears to prohibit inclusion of Event-Timestamp

> except in an Accounting-Request:
...
> RFC 2869 Section 5.19 does not include a table row for the 
> Event-Timestamp attribute, suggesting that Event-Timestamp is 
> prohibited in Access-Request, Accept, Reject and Challenge packets.

  That sounds good.

No. If it was prohibited in an Access-Request, Accept, Reject etc... It
would have specifically stated that. 


--
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:
- Issue 223: Event-Timestamp and Duplicate Detection
  - From: "Bernard Aboba" <bernard_aboba@hotmail.com>
- Re: Issue 223: Event-Timestamp and Duplicate Detection
  - From: Alan DeKok <aland@nitros9.org>

Prev by Date: RE: Issue 226: RFC 3576bis and Renumbering
Next by Date: RE: RFC 3576bis and Session State
Previous by thread: Re: Issue 223: Event-Timestamp and Duplicate Detection
Next by thread: RE: Issue 223: Event-Timestamp and Duplicate Detection
Index(es):
- Date
- Thread