| Re: Basic facts about EAP | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Mon, 2 May 2005 04:00:11 -0400 (EDT) | |
> I am not sure if using an EAP method to carry the NAS-ID or port-ID > for Channel Bindings is really a good idea as it would actually make > the EAP method media-dependent while it would make EAP media > independent. If the Channel Bindings are treated as opaque blobs, and are represented as media-independent attributes, I don't think this creates a media dependency. For example, NAS-Identifier, Called-Station-Id and Calling-Station-ID are all media independent. At least the way Channel Bindings are described in RFC 3748, Section 7.15, it seems like the idea is to export the Bindings for verification by the lower layer. This seems like something that needs more explanation, though. I will file an issue on it and try to post some text to the list.
- RE: Basic facts about EAP, (continued)
-
RE: Basic facts about EAP Alper Yegin, April 29 2005
-
RE: Basic facts about EAP Bernard Aboba, April 30 2005
- Re: Basic facts about EAP Yoshihiro Ohba, May 1 2005
- Re: Basic facts about EAP Jari Arkko, May 2 2005
- Re: Basic facts about EAP Bernard Aboba, May 2 2005
- Re: Basic facts about EAP Yoshihiro Ohba, May 2 2005
- Re: Basic facts about EAP Yoshihiro Ohba, May 2 2005
- Re: Basic facts about EAP Jari Arkko, May 2 2005
- Re: Basic facts about EAP Yoshihiro Ohba, May 2 2005
-
RE: Basic facts about EAP Bernard Aboba, April 30 2005
-
RE: Basic facts about EAP Alper Yegin, April 29 2005
Results generated by Tiger Technologies using MHonArc.