SIPPING WG Config. Framework draft-ietf-sipping-config-framework-04.txt

1
SIPPING WG Config. Frameworkdraft-ietf-sipping-co
nfig-framework-04.txt

• Dan Petrie
• dpetrie_at_pingtel.com

2
Reviewers solicited at last IETF60

• Review team
• Martin Dolly
• John Elwell
• Cullen Jennings
• Hisham Khartabil
• Henry Sinnreich
• Thank you for detailed review!

3
Changes to 04

• Clarification
• How instance-id is used to generate device
  profile URI
• Why each device should use unique device URI as
  opposed to generic for UA type
• Normative vs. informative statements
• Separate subscription needed for each profile
  type
• More examples for discovery, bootstrapping
  scenarios and usage
• More detail on document, app-id and other event
  header parameters
• Specify
• Which event parameters are option or mandatory
• ABNF for all event header parameters
• Removed TFTP from list of referenced profile
  transport protocols due to security issues
• Profile-Name event header parameter changed back
  to Profile-Type

4
Review issue not incorporated

• Generic mechanism to allow UA to specify optional
  capabilities (e.g. model options)

5
Pending changes to 05

• Correct reference to instance-id generation
• Separate normative and informative references
• Clarification of how security is provided for
  content indirection URI
• Vendor, Model, Version parameters SHOULD be used
  to affect the content only (not the event package
  signaling)
• Example or clarification of how content
  indirection URI scheme can be negotiated
• Define hotelling and roaming
• Make HTTP and HTTPS mandatory if content
  indirection is used
• ABNF typos
• Misc. nits