Presentation on theme: "Extensions for Unauthenticated and Unauthorized Devices draft-ietf-ecrit-unauthenticated-access-01 H. Schulzrinne, S. McCann, G. Bajko, H. Tschofenig,"— Presentation transcript:
Extensions for Unauthenticated and Unauthorized Devices draft-ietf-ecrit-unauthenticated-access-01 H. Schulzrinne, S. McCann, G. Bajko, H. Tschofenig, D. Kroeselberg
2/12/2014 IETF #77, ECRIT WG 2 Reminder Start Lower-layer attach Waiting for ES call initiation NAA NASP PhoneBCP ZBP Credentials for network access available? yes no Emergency NW attach possible? yes no ASP configured? no yes Authorized? no yes
Open Issue In Section 5, step 2, this document says that the ISP informs the calling device about its local ESRP via DHCP. This seems incorrect, not least because there is no DHCP option defined to carry this sort of information. It seems to me that in order to minimize the divergence from the normal procedure, step 2 should have the network providing the client access to location (HELD/DHCP-location) and LoST servers, then connecting to the ESRP. --Richard 2/12/2014 IETF #77, ECRIT WG 3
Next Steps WGLC after updated version. 2/12/2014 IETF #77, ECRIT WG 4
Your consent to our cookies if you continue to use this website.