[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Define some new NAS-Port-Type
- To: "Congdon, Paul T \(ProCurve\)" <paul.congdon@hp.com>
- Subject: RE: Define some new NAS-Port-Type
- From: "Glen Zorn \(gwz\)" <gwz@cisco.com>
- Date: Wed, 16 Aug 2006 11:33:10 -0700
- Authentication-results: sj-dkim-1.cisco.com; header.From=gwz@cisco.com; dkim=pass ( sig from cisco.com verified; );
- Cc: "Bernard Aboba" <Bernard_Aboba@hotmail.com>, "CTO YAN Renxiang" <Renxiang.Yan@alcatel-sbell.com.cn>, <dnelson@enterasys.com>, <radiusext@ops.ietf.org>
- Dkim-signature: a=rsa-sha1; q=dns; l=2899; t=1155753192; x=1156617192; c=relaxed/simple; s=sjdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=gwz@cisco.com; z=From:=22Glen=20Zorn=20\(gwz\)=22=20<gwz@cisco.com> |Subject:RE=3A=20Define=20some=20new=20NAS-Port-Type; X=v=3Dcisco.com=3B=20h=3DEHYHYo3YXUAytdUuU/p5IzHj1PM=3D; b=f6hVauPVZoDiNPWa5FaWH0+yCbIA3V+p4XNoYlBZS7GBQQlL5rRFDkvH7ryWsx257w8oBVIB S7yiDiTzm3fHfUDdgl5DP25ucQBHK4G6ItZ2J3QuDzKG+zw8vnx2g52P;
Congdon, Paul T (ProCurve) <> supposedly scribbled:
> People do use RADIUS to authenticate infrastructure devices as well
True, but the conjunction of the terms "infrastructure" & "Personal Area Network" has me confused. Would you mind elaborating?
>
>> -----Original Message-----
>> From: owner-radiusext@ops.ietf.org
>> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
>> Sent: Tuesday, August 15, 2006 7:30 PM
>> To: 'CTO YAN Renxiang'; dnelson@enterasys.com; radiusext@ops.ietf.org
>> Subject: 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/>
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/>