[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: review of draft-ietf-radext-ieee802-01.txt
> -----Original Message-----
> From: owner-radiusext@ops.ietf.org
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Congdon,
> Paul T (ProCurve)
> Sent: Friday, January 27, 2006 5:54 AM
> To: Jari Arkko; radiusext@ops.ietf.org
> Subject: RE: review of draft-ietf-radext-ieee802-01.txt
>
> > Technically, we have two alternatives to get there. The first
> > alternative is to make NAS-Filter-Rule(R) an extension of
> > NAS-Filter-Rule(D). Given the same the same attribute name
> we appear
> > to intend to do this already... The other approach would be
> to define
> > NAS-Filter-Rule-Radius as a new Radius attribute and then allow its
> > use in Diameter as well.
> >
>
> At IETF-64, I believe we agreed to do the latter. I think
> this draft was supposed to rename the attribute to make that
> clear. Looks like we forgot to do that.
Yes, this one fell through the cracks. Are there any suggestions in
terms of names? How about something like NAS-Traffic-Rule or perhaps
to reduce confusion possibility drop the 'NAS-' prefix and just call it
'Traffic-Rule'?
Cheers,
MS
--
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/>