[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Comments on draft-carroll-dynmobileip-cdma-04.txt
- To: "'Avi Lior'" <avi@bridgewatersystems.com>, "'Nelson, David'" <dnelson@enterasys.com>, "'Frank Quick'" <fquick@qualcomm.com>, "'Alan DeKok'" <aland@ox.org>, "'W. Mark Townsley'" <townsley@cisco.com>
- Subject: RE: Comments on draft-carroll-dynmobileip-cdma-04.txt
- From: "Glen Zorn \(gwz\)" <gwz@cisco.com>
- Date: Mon, 14 Mar 2005 11:19:43 -0800
- Cc: "'Jari Arkko'" <jari.arkko@piuha.net>, "'Barney Wolff'" <barney@databus.com>, "'Thomas Narten'" <narten@us.ibm.com>, "'Carroll, Christopher P.'" <Ccarroll@ropesgray.com>, <gerry.flynn@verizonwireless.com>, <radiusext@ops.ietf.org>
- In-reply-to: <F17FB067A86B2D488382C923C532EAA7024A5089@exch01.bridgewatersys.com>
- Reply-to: <gwz@cisco.com>
Avi Lior <> supposedly scribbled:
_This document is practically a textbook example of how _not_ to use
RADIUS. Can the note say that?
> I support David's approach.
>
>> -----Original Message-----
>> From: Nelson, David [mailto:dnelson@enterasys.com]
>> Sent: Monday, March 14, 2005 1:32 PM
>> To: Frank Quick; Alan DeKok; Avi Lior; W. Mark Townsley
>> Cc: Jari Arkko; Barney Wolff; Thomas Narten; Carroll, Christopher
P.;
>> gerry.flynn@verizonwireless.com; radiusext@ops.ietf.org
>> Subject: RE: Comments on draft-carroll-dynmobileip-cdma-04.txt
>>
>>
>> Frank Quick writes...
>>
>>> This sounds very reasonable, but I think it actually goes beyond
the
>>> context of this draft. I believe there is no clear statement of
>>> this policy that the draft can reference, and it is not a good
idea
>>> for a draft of this nature to create new policy. For this draft
>>> maybe it is enough that we state that RFC 2865 forbids VSA in
>>> Access-Reject, and that future work should consider using
>>> Access-Challenge instead. That would avoid having to discuss
the
>>> semantics issue in the draft.
>>
>> It is apparent that there is some disagreement within the RADIUS
>> community within IETF about the usage of Access-Reject. The
areas of
>> disagreement cover whether Access-Reject implies link-layer
>> disconnect and when Access-Reject or Access-Challenge is
appropriate
>> (or permissible). In RADEXT, we have added this set of issues to
be
>> considered in our RADIUS Issues and Fixes I-D. Given this lack
of
>> clear consensus, it might be advisable to craft an IESG note
along
>> the lines that Frank describes. Future RFCs may provide more
>> definitive guidance in this area. Understanding that, it is
>> appropriate to discourage new work using *this* document as a
>> precedent.
Hope this helps,
~gwz
Why is it that most of the world's problems can't be solved by
simply
listening to John Coltrane? -- Henry Gabriel
--
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/>