Configuration Frameworkdraft-ietf-sipping-config-framework-06 Dan Petrie dgpetrie AT yahoo.com
Changes from 05 • Delivery server MUST support HTTP and HTTPS profile transport schemes • User agent MUST support HTTP or HTTPS profile transport schemes • Rewrote security section • Clarification and separation of Normative and Informative statements and references • Editorial and clarification changes through out
Event package name and parameters issues from the list • Local network subscription URI should be <device-id>@<local-network> (currently anonymous@<local-network>) • Change event type name to “config-profile” or “ua-profile”? (currently “sip-profile”) • Change token for Event parameter “profile-type” to “local-network”? (currently “local”) • Vendor, Model, Version should allow only quoted string values (currently allows token as well)
General comments from the list Henning: • More examples in overview section: • Softphone bootstrapping user experience • Enterprise ATA (i.e. no GUI) bootstrapping user experience • More cross referencing in overview to normative descriptions • Security section too terse Cullen: • Use of term cache of profile needs clarification • Need to provide references with use of name-addr, token
XCAP section issues from list • XCAP section too abstract, options: • Remove XCAP section or • Need to better define use and scheme for “document” and “app-id” header parameters. Need a volunteer to provide text.