draft-ietf-ecrit- additional-data-04 brian rosen hannes tschofening roger marshall

4
draft-ietf-ecrit- additional-data-04 Brian Rosen Hannes Tschofening Roger Marshall

Upload: mercy-elliott

Post on 19-Jan-2016

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Draft-ietf-ecrit- additional-data-04 Brian Rosen Hannes Tschofening Roger Marshall

draft-ietf-ecrit-additional-data-04

Brian RosenHannes Tschofening

Roger Marshall

Page 2: Draft-ietf-ecrit- additional-data-04 Brian Rosen Hannes Tschofening Roger Marshall

Reminder of what this isWay to get data from service providers and devices

into a PSAP (and then to responders)

Contains SP ID, contact and “class of service” data Subscriber data Device data Hook for device/service specific data

Comes in Call Info header in SIP (or cid, with data in body) for

device or origination SP data Provided-by element of PIDF for access SPdata

Page 3: Draft-ietf-ecrit- additional-data-04 Brian Rosen Hannes Tschofening Roger Marshall

Changes from prior version

Updates due to suggestions from NENAMain Telephone Number property in vCardAdd way to have a data provider who is a

contractor to a service providerAllow multiple Services Delivered by ProviderAdd text on privacy flags in identity headers

Links between MIME blocks

Page 4: Draft-ietf-ecrit- additional-data-04 Brian Rosen Hannes Tschofening Roger Marshall

What’s nextNew version this week with a couple more

comments (including Randy’s)

Are we happy with MIME block links or should we just have one MIME with multiple XML blocks?