Config Framework pending draftietfsippingconfigframework09 pending draftietfsippingxcapconfig01 Dan Petrie

• Ad hoc meeting at Dallas to discuss – split into draft-ietf-sipping-config-framework-08 &

Changes from 08/00 • Clarifications, edits and nits from reviewers – Thanks Roni, Martin,

Changes from 08/00 Issues and actions from ad hoc in Dallas • Normative text:

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

Normative Issues • The "network-user" parameter SHOULD/MUST be set when subscribing for device and

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

Slides: 9

Download presentation

Config Framework pending: draft-ietf-sipping-config-framework-09 pending: draft-ietf-sipping-xcap-config-01 Dan Petrie SIPez LLC dpetrie@SIPez. com +1 617 273 4000

• 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

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.

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

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 1. when specifying profile-type=application select all auid in home and global directories 2. 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

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

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).

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?

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