Requirements for Domain Authentication and Validated Location

1
Requirements for Domain Authentication and
Validated Location

• ltdraft-winterbottom-ecrit-location-scope-req-00.tx
  tgt
• J. Winterbottom, M. Dawson, M. Thomson
• IETF62

2
Obvious Thoughts

• ECRITs scope is how to route emergency IP calls
  to the correct destination.
• Making an emergency call, is making a request for
  a specific service in a general way.
• the service identifier does not readily identify
  the destination (there maybe a number).
• additional context information is required to
  determine the final destination.

3
Additional Context Information

• Lots of information form this additional context
  information
• Location of caller
• Time of call
• Application type used
• Draft concentrates on Location as the primary
  context.
• To be useful, context information must be
  dependable

4
Confidence in Location

• High confidence in POTS information, party
  routing the call is the party providing the
  information
• Location, tied to the calling line
• Time of call implicit
• VoIP location needs similar assurances
• Know location of end-point
• Location tied to an end-device (NOT USER)
• Call tied to location, tied to device at specific
  time of call.

5
Location Assurances

• Validation of location relates to whether a
  location is a real place.
• Formatting may be important here, eg Postal vs
  Jurisdicational
• Location authentication relates to the source and
  content of the information.
• Location producer
• Location provider (the calling-device)
• Time, etc.

6
Conclusions

• Reliable routing tied to the dependability of the
  information provided.
• ECRIT may not have this specifically in scope,
  but it should recognize this dependence.
• Adjust scope?
• Capture item in another WG