1 / 7

draft-ietf-sip-location-conveyance-09

draft-ietf-sip-location-conveyance-09. IETF70 – Vancouver James Polk. Changes since -08 (I). Within the Geolocation header Made the “inserted-by=“ parameter mandatory. Changes since -08 (II). Within the Geolocation-Error header Modified ABNF Made the “inserter=“ parameter mandatory

alec
Download Presentation

draft-ietf-sip-location-conveyance-09

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-ietf-sip-location-conveyance-09 IETF70 – Vancouver James Polk

  2. Changes since -08 (I) Within the Geolocation header • Made the “inserted-by=“ parameter mandatory

  3. Changes since -08 (II) Within the Geolocation-Error header • Modified ABNF • Made the “inserter=“ parameter mandatory • Identifies who a/each locationErrorValue is for • Added ability to list one or more CAtypes considered ‘bad’ by Location Recipient for each locationErrorValue • Changed error codes to be 3-digits

  4. Changes since -08 (III) • Made Presence the event package for dereferencing a location URI • Split out the UAC, UAS and Proxy error text into separate sub-sections • Clarified text and fixed nits

  5. Open Issue remaining #1 Scope of “recipient=“ (endpoint or routing-entity) Geolocation header parameter • Can a cleartext header parameter prohibit viewing a message body? • Is this expecting too much? What to do... can state one of these: • an entity type MUST NOT read what’s to another type • an entity type SHOULD NOT read what’s to another type • That it’s not useful to read what isn’t for an entity type, (can add “and never dereference LbyR URI”) Each would add Security Considerations text stating there are no security properties to any guidance Need to create a new error code indicating location reading was disallowed

  6. Open Issue remaining #2 • Parts of IANA Considerations section are confusing • I know... I’m working on it

  7. What’s next? • Rev to -10 (this week perhaps?) by addressing • comments during preso • Modify text resolving the “recipient=“ parameter discussed here • Resolve IANA section • Other editorial scrubbing

More Related