50 likes | 171 Views
Extensions for Unauthenticated and Unauthorized Devices. draft-ietf-ecrit-unauthenticated-access-01 H. Schulzrinne, S. McCann, G. Bajko, H. Tschofenig, D. Kroeselberg. Document Status. Draft is now WG item, former draft-schulzrinne-ecrit-unauthenticated-access. In the latest update, we
E N D
Extensions for Unauthenticated and Unauthorized Devices draft-ietf-ecrit-unauthenticated-access-01 H. Schulzrinne, S. McCann, G. Bajko, H. Tschofenig, D. Kroeselberg
Document Status • Draft is now WG item, former draft-schulzrinne-ecrit-unauthenticated-access. • In the latest update, we • rearranged/restructured the text and added some clarifications • did numerous editorial updates • slightly reworked the definitions • did not introduce any major technical changes IETF #77, ECRIT WG
A Flow Diagram has been added for clarity Start Credentials available? no yes Waiting for ES callinitiation Lower-layerattach ASP configured? Emergency NW attach possible? yes no no yes PhoneBCP NASP NAA Authorized? no yes ZBP PhoneBCP IETF #77, ECRIT WG
What about ecrit-direct • Relation between this document and ecrit-direct came up at IETF-77(?): • ecrit-unauthenticated covers “unauthenticated” cases in general (see above diagram) • ecrit-direct only covers ASP-less cases (maps to NASP), scope more limited compared to ecrit-unauthenticated. • There should not be any major conflict • Some differences: Ecrit-unauthenticated… • does not assume mandatory LOST support (ESRP discovery via DHCP as fallback) • Does not propose a detailed solution for NASP cases (e.g. no callback considerations) IETF #77, ECRIT WG
Next steps Document considered ready for WG last call. IETF #77, ECRIT WG