1. Sam hartman Painless Security IETF 80
EAP Channel Binding
Sam hartman
Painless Security
IETF 80

2. Open Issues Diagrams required Confirm 802.11 attributes
What encoding should be used for channel bindings: two options
Diagrams required
Confirm attributes

3. Two encoding options Code: 1 octet Length: 1 octet NSID: 1 octet
| Code | Length | NSID | NS-SPECIFIC ...
| |
| NSID | Length | NS-SPECIFIC...
Encoding option 2
| Code | Length | NSID |
| NS-Specific… |
| Length | NSID | NS-Specific...
Code: 1 octet
Length: 1 octet
NSID: 1 octet
NS-SPECIFIC: =<255 octets
{Length: 1 octet
NS-SPECIFIC: =<255 octets}
Code: 1 octet
Length: 2 octets
NSID: 1 octet
NS-SPECIFIC: all data
{Length: 2 octets
NS-SPECIFIC: all data}
(Any NSID at most once)

4. Two RADIUS AVPs encoded both ways
Encoding option 1
| Code | Length | NSID | Type |
| Value...
| Length | NSID | Type | Value...
| |
Encoding option 2
| Code | Length | NSID |
| Type | Length | Value |