Presentation is loading. Please wait.

Presentation is loading. Please wait.

NAI (4282bis) RADEXT - IETF 82.

Similar presentations


Presentation on theme: "NAI (4282bis) RADEXT - IETF 82."— Presentation transcript:

1 NAI (4282bis) RADEXT - IETF 82

2 Why? RFC 4282 is referenced in many places EAP, RADIUS, now abfab
NAI is a MUST for abfab 4282 not 8-bit clean. EAP and RADIUS are 8-bit clean

3 Even more why 4282 requires that intermediate nodes (proxies) mangle the NAI Create normal form Perform code point filtering DNS affects EAP and RADIUS? Why? ToAscii is for DNS lookups…

4 No one implements any of the requirements of RFC 4282
The best reason No one implements any of the requirements of RFC 4282

5 4282 is blocking progress

6 The solution: 4282bis The document has one proposal:
Realms MUST be of the form that can be registered as a Fully Qualified Domain Name (FQDN) within the DNS name system. Pretty much everything else from is gone. The rest of the document explains why

7 The results This change allows new documents (abfab) to be compatible with existing practice This change is compatible with precis Has no effect on any other specification Has no new normative requirements on implementations

8 Discussion?


Download ppt "NAI (4282bis) RADEXT - IETF 82."

Similar presentations


Ads by Google