Embed Size (px)
Citation preview
ECRIT - Getting Certain URIs, and Alternatives to Getting Emergency Dialstring(s)
draft-polk-ecrit-lost-server-uri-00draft-polk-dhc-ecrit-uri-psap-esrp-00
draft-polk-dhc-ecrit-uri-lost-00draft-polk-ecrit-dhc-emergency-dialstring-option-00
draft-polk-ecrit-mapping-during-registration-00draft-polk-ecrit-emergency-dialstring-00
James PolkJuly 11, 2006
OK, let’s get this over with, eh?
What are these 6 IDs discussing?
• How to get a (sometimes preferred) LoST Server, and/or PSAP/ESRP, URI(s) into an endsystem
• How to get a (sometimes preferred) emergency dialstring(s) into an endsystem
• No one ID discusses both
Where are these mechanisms used?
• Access Providers and Enterprises (of all sizes) *can* use DHCP for users to request and/or deliver URIs and Emergency Dialstrings
• VSPs (which could be from a local network or Call processing on the other side of planet) will have SIP communications with endpoints, thus SIP UAs *can* request and/or deliver URIs and Emergency Dialstrings
How are these Mechanisms used?
• During Network Attachment time and/or periodic refresh, specific info *can* be requested for download, or just downloaded to endsystem
• Instead of new protocols, all 6 IDs propose extensions to either DHCP or SIP, which are already a given in most, if not all endsystems
Attachment Time configuration
• Alice sends DISCOVER message
Domain A
Domain C
Domain D
Domain BDomain E
Domain FDHCPServer
Alice
LISServer
DHCPServer
• DHCP Server may interact with LIS
• Alice receives (URI(s), and/or Dialstring(s)
draft-polk-dhc-ecrit-uri-lost-00draft-polk-dhc-ecrit-uri-psap-esrp-00draft-polk-ecrit-dhc-emergency-dialstring-option-00
alsoDomain A
Contacting a specific Server
• Alice may attach here...
Domain A
Domain C
Domain D
Domain BDomain E
Domain FRegistrarServer
Alice
LISServer also
Domain A
• ...or here
• Either way, she may want – or need – to communicate here
Domain A
Domain C
Domain D
Domain BDomain E
Domain F
LISServer
Alice
Contacting a specific Server
RegistrarServer
LISServer also
Domain AThese may be access/core providers only, and not trusted by Alice or her org
Contacting a specific Server
Domain A
Domain C
Domain D
Domain BDomain E
Domain FRegistrarServer
Alice
LISServer also
Domain Adraft-polk-ecrit-lost-server-uri-00draft-polk-ecrit-mapping-during-registration-00draft-polk-ecrit-emergency-dialstring-00
• Alice sends SIP REGISTER with Location
• Registrar Server may interact with LIS
• Alice receives 200 OK w/ URI(s), and/or Dialstring(s)
Domain A
Domain C
Domain D
Domain BDomain E
Domain F
LISServer
Alice
Contacting a specific Server
RegistrarServer
LISServer also
Domain Adraft-polk-ecrit-lost-server-uri-00draft-polk-ecrit-mapping-during-registration-00draft-polk-ecrit-emergency-dialstring-00
• Alice sends SIP REGISTER with Location
• Registrar Server may interact with LIS
• Alice receives 200 OK w/ URI(s), and/or Dialstring(s)
DHCP Messaging 101
• DHCP Clients query for configuration information
DHCPDISCOVER (Options listed)
DHCPOFFER (Options answered)
Alice DHCP Server LIS Server
DHCPREQUEST (Options listed)
DHCPACK (Options answered)
• DHCP Clients update configuration information
DHCP Messaging including LIS
DHCPDISCOVER (Options listed)LoST Query
DHCPOFFER (Options answered)
Alice DHCP Server
LoST Response
LIS Server
DHCPREQUEST (Options listed)
DHCPACK (Options answered)
• DHCP Clients query for configuration information– Could include Location or Location specific information
• DHCP Clients update configuration information
LoST transaction
DHCP Messaging including LIS
DHCPDISCOVER (Options listed)LoST Query
DHCPOFFER (Options answered)
Alice DHCP Server
LoST Response
LIS Server
DHCPREQUEST (Options listed)
DHCPACK (Options answered)
• DHCP Clients query for configuration information– Could include Location or Location specific information
• DHCP Clients update configuration information
LoST transaction
draft-polk-dhc-ecrit-uri-lost-00
• Specifies how an Access Network (SP, Enterprise, SMB, home) provides a LoST Server URI– By creating a new DHCP Option for the LoST server– May or may not involve a location resolution to return
URI
• Motivation: This is the easiest means of getting a LoST URI into a client
• Open Issues – change filename to -ecrit-
draft-polk-ecrit-dhc-emergency-dialstring-option-00
• Specifies how an Access Network (SP, Enterprise, SMB, home) provides a local or visited emergency dialstring– By creating a new DHCP Option for what is important,
or required to be understood, on that network– May or may not involve a location resolution to return
URI
• Motivation: This is the easiest means of getting a LoST URI into a client
• Open Issues – keep ISO country code?
draft-polk-dhc-ecrit-uri-psap-esrp-00
• Specifies how an Access Network (SP, Enterprise, SMB, home) provides a PSAP/ESRP URI– By creating a new DHCP Option for the appropriate
PSAP/ESRP– Means DHCP Server will have to implement LoST
• Unless there is only one answer ever
• Motivation: Local network may be in best position to provide this easy to deliver URI
• Open Issues – change filename to -ecrit-
SIP Registration 101
• SIP UAs Register within a Domain for a certain amount of time– Generally advisable to use TLS, thus this is secure communications anyway
SIP REGISTER
200 OK
Alice SIP Registrar LIS Server
• UAs refresh registration periodically
SIP REGISTER (refresh)
200 OK
SIP Registration including LIS
SIP REGISTER (w/ PIDF-LO)
200 OK (with unique Loc parameters)
Alice SIP Registrar LIS Server
SIP REGISTER (refresh)
200 OK (refreshed parameters)
LoST Query
LoST Response
LoST transaction
• SIP UAs Register within a Domain for a certain amount of time– Can include Location by-value or by-reference for unique parameters– Can include an option-tag requesting additional info sent back
• UAs refresh registration periodically
SIP Registration including LIS
SIP REGISTER (w/ PIDF-LO)
200 OK (with unique Loc parameters)
Alice SIP Registrar LIS Server
SIP REGISTER (refresh)
200 OK (refreshed parameters)
LoST Query
LoST Response
LoST transaction
• SIP UAs Register within a Domain for a certain amount of time– Can include Location by-value or by-reference for unique parameters– Can include an option-tag requesting additional info sent back
• UAs refresh registration periodically
draft-polk-ecrit-lost-server-uri-00
• Specifies how an Application Provider (SP, Enterprise, SMB, home) provides a LoST Server URI– By creating a new SIP option-tag and header for the
LoST server
• Motivation: Application provider is the one often responsible for emergency calling results, but can’t be if it doesn’t give this answer
• Open Issues – none
draft-polk-ecrit-emergency-dialstring-00
• Specifies how an Application Provider (SP, Enterprise, SMB, home) provides a local or visited emergency dialstring– By creating a new SIP option-tag and header for what
is important, or required to be understood, on that network when a user enters a locally significant dialstring
• Motivation: SIP solution within existing TLS secure registration from a trusted server
• Open Issues – change filename to -ecrit-– BNF needs to be corrected
draft-polk-ecrit-mapping-during-registration-00
• Specifies how an Application Provider (SP, Enterprise, SMB, home) provides a PSAP/ESRP URI– By creating a new SIP option-tag and header for the
appropriate PSAP/ESRP– Means SIP Registrar will have to implement LoST
• Unless there is only one answer ever
• Motivation: Application Provider has trusted servers (by contract), and may be bound to provide this URI
• Open Issues – change filename to -ecrit-
Open issues here
• Listed under each ID’s slide
• Asked by DHC chairs to move all related IDs over to ECRIT, resulting in two of these IDs getting new filenames very soon
What’s Next?
• Take comments how to improve each ID
• Want several to become WG items– draft-polk-ecrit-lost-server-uri-00– draft-polk-dhc-ecrit-uri-lost-00– draft-polk-ecrit-dhc-emergency-dialstring-option-00– draft-polk-ecrit-emergency-dialstring-00
• Willing to keep PSAP URI IDs individual for now, unless WG thinks otherwise is best
