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

RE: [Technical Errata Reported] RFC3162 (1923)

To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
Subject: RE: [Technical Errata Reported] RFC3162 (1923)
From: "Glen Zorn" <glenzorn@comcast.net>
Date: Sun, 25 Oct 2009 21:50:59 +0700
Cc: "'radext mailing list'" <radiusext@ops.ietf.org>
In-reply-to: <EDC652A26FB23C4EB6384A4584434A0401B4C065@307622ANEX5.global.avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A0401B4C065@307622ANEX5.global.avaya.com>

> RADEXT WG,
> 
> Please advise on the Technical Errata below.

The idea that the formal data type (if any) of a field in a RADIUS attribute
can be changed by changing the name of the field is so bizarre as to be
almost unbelievable.  Even if it wasn't so incredibly BASIC, the idea is not
supported by any explicit text in any RADIUS-related RFC.

...


--
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/>

Follow-Ups:
- Re: [Technical Errata Reported] RFC3162 (1923)
  - From: Alan DeKok <aland@deployingradius.com>

References:
- FW: [Technical Errata Reported] RFC3162 (1923)
  - From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>

Prev by Date: RE: Proposed Resolution of Issue #318: REJECT
Next by Date: RE: Proposed Resolution of Issue #318: REJECT
Previous by thread: FW: [Technical Errata Reported] RFC3162 (1923)
Next by thread: Re: [Technical Errata Reported] RFC3162 (1923)
Index(es):
- Date
- Thread