[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Define some new NAS-Port-Type
Typically a NAS-Port-Type value is only needed for access technologies that
may need to use RADIUS. I don't think that 802.15 fits into that category
(though lots of other wireless technologies do).
-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of CTO YAN Renxiang
Sent: Tuesday, August 01, 2006 10:13 PM
To: Bernard Aboba; dnelson@enterasys.com; radiusext@ops.ietf.org
Subject: re: Define some new NAS-Port-Type
Hi, David and Bernard,
Thanks for your comments.
I think stating as work in progress in Informative Reference is ok. Many RFC
documents are also written in this way, as follows,
5.2 Informative References
[802.20] Mobile Broadband Wireless Access (MBWA), IEEE Standard, Work
in Progress.
[802.22] Wireless Regional Area Networks (WRAN), IEEE Standard, Work
in Progress.
How do you think about that?
BTW, do you think we need to define a NAS-Port-Type for 802.15 (WPAN) also?
Renxiang
> -----原始邮件-----
> 发件人: Bernard Aboba [mailto:bernard_aboba@hotmail.com]
> 发送时间: 2006年8月2日 9:04
> 收件人: dnelson@enterasys.com; CTO YAN Renxiang; radiusext@ops.ietf.org
> 主题: RE: Define some new NAS-Port-Type
>
>
> >I understand the
> >difficulty of referencing draft IEEE standards, so I'm not
> sure exactly
> >what to suggest as an alternative.
>
> I think they can reference IEEE 802 work-in-progress as an
> Informative
> Reference.
>
>
>
--
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/>
--
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/>