70 likes | 88 Views
This draft suggests placing device identity parameters in the User-Agent header, explores profile type indication methods, HTTP/HTTPS usage, and security considerations.
E N D
User Profile Frameworkdraft-ietf-sipping-config-framework-00.txt Dan Petrie dpetrie@pingtel.com
Changes fromdraft-petrie-sipping-config-framework-00.txt • Sync’d with RFC 3261, 3265 • Moved the device identity parameters to User-Agent header parameters draft-ietf-sipping-config-framework-00
Content Indirection Protocol • SHOULD use HTTPS • MAY use HTTP draft-ietf-sipping-config-framework-00
Device identity parameters Where should device identity parameter go? e.g. serial num., MAC, model, sw version Currently draft proposes additional syntax to User-Agent header Should it be a new header? draft-ietf-sipping-config-framework-00
How to indicate profile type? Option A: Accept header Create a MIME type for each profile type e.g. application/sip-ua-speedial, application/sip-aor-cred Option B: Event header parameter Token for each profile type Other options? draft-ietf-sipping-config-framework-00
Next steps • Describe security consideration scenario(s) • Make an editing pass • Elaborate change upload process draft-ietf-sipping-config-framework-00
Beyond this draft • Finish requirements drafts draft-ietf-sipping-ua-prof-framewk-reqs-00.txt draft-sinnreich-sipdev-req-00.txt • Draft a profile container syntax/framework • Start defining profiles draft-ietf-sipping-config-framework-00