50 likes | 68 Views
draft-rosen-ecrit-phonebcp-01. Brian Rosen. Purpose. Advice to phone and proxy vendors on how to support emergency calls Defines what protocols and mechanisms all phones and emergency call handling proxies must do Does not create any new protocols, extensions or mechanisms
E N D
draft-rosen-ecrit-phonebcp-01 Brian Rosen
Purpose • Advice to phone and proxy vendors on how to support emergency calls • Defines what protocols and mechanisms all phones and emergency call handling proxies must do • Does not create any new protocols, extensions or mechanisms • Currently, some overlap exists between framework and phonebcp, which will be resolved • Generally, phonebcp will be “normative”, framework will be informative
Should there be a protocol list for locat • Draft currently lists DHCP and [L7] as the IETF location acquisition protocols and says phones must implement both and most access networks must implement one or both” • Patty McCalmont suggests “There are many references to DHCP [or L7]. I would suggest changing these to, a mechanism must be supported to provide the Location Indication to the device ” • I think we MUST have a list. I can explicitly create the list and change the text from DHCP [or L7] to “one of the protocols on the list”
Location Issue – Should LLDP-MED be in the list? • LLDP-MED useful primarily in switched Ethernet (and some WiFi environments), almost exclusively enterprise • Pro- easier to deploy than DHCP, fewer elements to work with, no organizational responsibility split • Con- DHCP works wherever LLDP-MED works, if “ease of deployment” is a criteria, lots of protocols should be on the list, list must be short
And… • What is missing? • Send suggestions (I’ll write the text) • Making sure this aligns with 3GPP support of emergency calls • Next rev a WG item?