1 / 9

Config Framework and XCAP Config Updates

This document discusses updates to the config framework and XCAP config, including clarifications, edits, and the addition of a new HTTP header Event statement to the IANA section. It also addresses issues and actions from the ad hoc meeting in Dallas.

kwetzel
Download Presentation

Config Framework and XCAP Config Updates

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. Config Frameworkpending: draft-ietf-sipping-config-framework-09pending: draft-ietf-sipping-xcap-config-01 Dan Petrie SIPez LLC dpetrie@SIPez.com +1 617 273 4000

  2. Ad hoc meeting at Dallas to discuss • split into draft-ietf-sipping-config-framework-08& draft-ietf-sipping-xcap-config-00 • Issue of how device can require XCAP • Reviewers assigned at Dallas

  3. Changes from 08/00 • Clarifications, edits and nits from reviewers • Thanks Roni, Martin, Christian and Adam • Added new HTTP header Event statement to IANA section.

  4. Changes from 08/00 Issues and actions from ad hoc in Dallas • Normative text: "document" parameter MUST refer to a whole document. • Local profile: • URI should be of the form: sip:localdomain (no user part). • From field indicates UUID. • Error should be provided if profile indicated by constraints (profile-type, document, auid) does not exist: 404

  5. Changes from 08/00 • Moved profile-type "application" to draft-ietf-sipping-xcap-config and use as indicate for required support for XCAP • Documented concept of filtering using profile-type, document, auid parameters • when specifying profile-type=application select all auid in home and global directories • if provided, further filter by "auid" and "document" parameters for global and user directories • Error should be provided if there is no support for the XCAP profile type: 489 Bad Event • Fixed certificate validation statements and reference

  6. Issues • Multicast discovery technique proposed • Add to draft-ietf-sipping-config-framework-09 • Make separate draft

  7. Normative Issues • The "network-user" parameter SHOULD/MUST be set when subscribing for device and local network profiles if the user's AOR is known. • The SUBSCRIBE server SHOULD/MUST authenticate the subscriber to verify the resource identifier in the "network-user" parameter if the profile provided is specific to the user (e.g. granting policies or privileges beyond those of an anonymous user).

  8. Issues • Event package provides mechanism to confirm the new profile is received. It does not provide confirmation that a profile was applied. • In scope or out?

  9. Next Steps • Edits for the issues and submit • WG last call? Finally, again

More Related