idnits 2.17.1 draft-ietf-sipping-config-framework-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1682. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1654. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1661. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1667. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 1688), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 36. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 2 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1579 has weird spacing: '...Changes in XM...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: The "discovered" host for the "local" profile subscription URI is the local IP network domain for the user agent, either provisioned as part of the device's static network configuration or discovered via DHCP. The local network profile subscription URI SHOULD not be cached if the user agent moves from one local network to another other. The user agent should perform the local network discovery every time it starts up or network connectivity is regained. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 19, 2005) is 7006 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2132' is defined on line 1531, but no explicit reference was found in the text == Unused Reference: 'RFC2246' is defined on line 1534, but no explicit reference was found in the text == Unused Reference: 'RFC2617' is defined on line 1541, but no explicit reference was found in the text == Unused Reference: 'RFC2131' is defined on line 1614, but no explicit reference was found in the text == Outdated reference: A later version (-06) exists of draft-ietf-sip-identity-04 ** Obsolete normative reference: RFC 2246 (Obsoleted by RFC 4346) ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Obsolete normative reference: RFC 2617 (Obsoleted by RFC 7235, RFC 7615, RFC 7616, RFC 7617) ** Obsolete normative reference: RFC 2818 (Obsoleted by RFC 9110) ** Obsolete normative reference: RFC 3265 (Obsoleted by RFC 6665) == Outdated reference: A later version (-12) exists of draft-ietf-simple-xcap-06 == Outdated reference: A later version (-15) exists of draft-ietf-sip-gruu-02 == Outdated reference: A later version (-05) exists of draft-petrie-sipping-profile-datasets-00 == Outdated reference: A later version (-08) exists of draft-sinnreich-sipdev-req-05 -- Obsolete informational reference (is this intentional?): RFC 822 (Obsoleted by RFC 2822) -- Obsolete informational reference (is this intentional?): RFC 2141 (Obsoleted by RFC 8141) -- Obsolete informational reference (is this intentional?): RFC 2396 (Obsoleted by RFC 3986) -- Obsolete informational reference (is this intentional?): RFC 3377 (Obsoleted by RFC 4510) Summary: 11 errors (**), 0 flaws (~~), 15 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 SIPPING D. Petrie 2 Internet-Draft Pingtel Corp. 3 Expires: August 20, 2005 February 19, 2005 5 A Framework for Session Initiation Protocol User Agent Profile 6 Delivery 7 draft-ietf-sipping-config-framework-06.txt 9 Status of this Memo 11 By submitting this Internet-Draft, I certify that any applicable 12 patent or other IPR claims of which I am aware have been disclosed, 13 and any of which I become aware will be disclosed, in accordance with 14 RFC 3668. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as 19 Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on August 20, 2005. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). All Rights Reserved. 38 Abstract 40 This document defines the application of a set of protocols for 41 providing profile data to SIP user agents. The objective is to 42 define a means for automatically providing profile data a user agent 43 needs to be functional without user or administrative intervention. 44 The framework for discovery, delivery, notification and updates of 45 user agent profile data is defined here. As part of this framework a 46 new SIP event package is defined here for the notification of profile 47 changes. This framework is also intended to ease ongoing 48 administration and upgrading of large scale deployments of SIP user 49 agents. The contents and format of the profile data to be defined is 50 outside the scope of this document. 52 Table of Contents 54 1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 56 2.1 Requirements Terminology . . . . . . . . . . . . . . . . . 4 57 2.2 Profile Delivery Framework Terminology . . . . . . . . . . 5 58 2.3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 2.4 Data Model . . . . . . . . . . . . . . . . . . . . . . . . 7 60 3. Profile Change Event Notification Package . . . . . . . . . 8 61 3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 9 62 3.2 Event Package Parameters . . . . . . . . . . . . . . . . . 9 63 3.3 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 12 64 3.4 Subscription Duration . . . . . . . . . . . . . . . . . . 13 65 3.5 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 13 66 3.6 Notifier processing of SUBSCRIBE requests . . . . . . . . 14 67 3.7 Notifier generation of NOTIFY requests . . . . . . . . . . 15 68 3.8 Subscriber processing of NOTIFY requests . . . . . . . . . 15 69 3.9 Handling of forked requests . . . . . . . . . . . . . . . 16 70 3.10 Rate of notifications . . . . . . . . . . . . . . . . . 16 71 3.11 State Agents . . . . . . . . . . . . . . . . . . . . . . 16 72 3.12 Examples . . . . . . . . . . . . . . . . . . . . . . . . 16 73 3.13 Use of URIs to Retrieve State . . . . . . . . . . . . . 17 74 3.13.1 Device URIs . . . . . . . . . . . . . . . . . . . . 18 75 3.13.2 User and Application URIs . . . . . . . . . . . . . 19 76 3.13.3 Local Network URIs . . . . . . . . . . . . . . . . . 20 77 4. Profile Delivery Framework Details . . . . . . . . . . . . . 20 78 4.1 Discovery of Subscription URI . . . . . . . . . . . . . . 20 79 4.1.1 Discovery of Local Network URI . . . . . . . . . . . . 21 80 4.1.2 Discovery of Device URI . . . . . . . . . . . . . . . 21 81 4.1.3 Discovery of User and Application URI . . . . . . . . 24 82 4.2 Enrollment with Profile Server . . . . . . . . . . . . . . 24 83 4.3 Notification of Profile Changes . . . . . . . . . . . . . 24 84 4.4 Retrieval of Profile Data . . . . . . . . . . . . . . . . 25 85 4.5 Upload of Profile Changes . . . . . . . . . . . . . . . . 25 86 4.6 Usage of XCAP with the Profile Package . . . . . . . . . . 25 87 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . 28 88 5.1 SIP Event Package . . . . . . . . . . . . . . . . . . . . 28 89 6. Security Considerations . . . . . . . . . . . . . . . . . . 28 90 6.1 Confidential Profile Content in NOTIFY Request . . . . . . 29 91 6.2 Confidential Profile Content via Content Indirection . . . 29 92 6.3 Integrity protection for non-confidential profiles . . . . 30 93 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 94 8. Change History . . . . . . . . . . . . . . . . . . . . . . . 30 95 8.1 Changes from draft-ietf-sipping-config-framework-05.txt . 31 96 8.2 Changes from draft-ietf-sipping-config-framework-04.txt . 31 97 8.3 Changes from draft-ietf-sipping-config-framework-03.txt . 31 98 8.4 Changes from draft-ietf-sipping-config-framework-02.txt . 31 99 8.5 Changes from draft-ietf-sipping-config-framework-01.txt . 32 100 8.6 Changes from draft-ietf-sipping-config-framework-00.txt . 32 101 8.7 Changes from 102 draft-petrie-sipping-config-framework-00.txt . . . . . . . 32 103 8.8 Changes from draft-petrie-sip-config-framework-01.txt . . 33 104 8.9 Changes from draft-petrie-sip-config-framework-00.txt . . 33 105 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 106 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 33 107 9.2 Informative References . . . . . . . . . . . . . . . . . . . 34 108 Author's Address . . . . . . . . . . . . . . . . . . . . . . 36 109 Intellectual Property and Copyright Statements . . . . . . . 37 111 1. Motivation 113 Today all SIP (Session Initiation Protocol) [RFC3261] user agent 114 implementers use proprietary means of delivering user, device, 115 application and local network policy profiles to the user agent. The 116 profile delivery framework defined in this document is intended to 117 enable a first phase migration to a standard means of providing 118 profiles to SIP user agents. It is expected that UA (User Agent) 119 implementers will be able to use this framework as a means of 120 delivering their existing proprietary data profiles (i.e. using 121 their existing proprietary binary or text formats). This in itself 122 is a tremendous advantage in that a SIP environment can use a single 123 profile delivery server for profile data to user agents from multiple 124 implementers. Follow-on standardization activities can: 125 1. define a standard profile content format framework (e.g. XML 126 with namespaces [W3C.REC-xml-names11-20040204] or name-value 127 pairs [RFC0822]). 128 2. specify the content (i.e. name the profile data parameters, xml 129 schema, name spaces) of the data profiles. 131 One of the objectives of the framework described in this document is 132 to provide a start up experience similar to that of users of an 133 analog telephone. When you plug in an analog telephone it just works 134 (assuming the line is live and the switch has been provisioned). 135 There is no end user configuration required to make analog phone 136 work, at least in a basic sense. So the objective here is to be able 137 to take a new SIP user agent out of the box, plug it in or install 138 the software and have it get its profiles without human intervention 139 other than security measures. This is necessary for cost effective 140 deployment of large numbers of user agents. 142 Another objective is to provide a scalable means for ongoing 143 administration of profiles. Administrators and users are likely to 144 want to make changes to profiles. 146 Additional requirements for the framework defined in this document 147 are described in: [I-D.ietf-sipping-ua-prof-framewk-reqs], 148 [I-D.sinnreich-sipdev-req] 150 2. Introduction 152 2.1 Requirements Terminology 154 Keywords "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT" and 155 "MAY" that appear in this document are to be interpreted as described 156 in [RFC2119]. 158 2.2 Profile Delivery Framework Terminology 160 profile - data set specific to a user, device, user's application or 161 the local network. 162 device - software or hardware appliance containing one or more SIP 163 user agent. 164 profile content server - The server that provides the content of the 165 profiles using the protocol specified by the URI scheme. 166 notifier - As defined in [RFC3265] the SIP user agent server which 167 processes SUBSCRIBE requests for events and sends NOTIFY requests 168 with profile data or URIs (Uniform Resource Identifiers) that 169 point to the data. 170 profile delivery server - The logical collection of the notifier and 171 the server which provides the contents of the notification either 172 directly in the NOTIFY requests or indirectly via profile URI(s). 173 hotelling- when a user moves to a new user agent (i.e. that is not 174 already provisioned to know the user's identity, credentials or 175 profile data) and gives the user agent sufficient information to 176 retrieve the user's profile(s). The user agent either permanently 177 or temporarily makes the user's profiles effective on that user 178 agent. 179 roaming- when the user agent moves to a different local network 181 2.3 Overview 183 The profile life cycle can be described by five functional steps. 184 These steps are not necessarily discrete. However it is useful to 185 describe these steps as logically distinct. These steps are named as 186 follows: 188 Discovery - discover a profile delivery server 189 Enrollment - enroll with the profile delivery server 190 Profile Retrieval - retrieve profile data 191 Profile Change Notification - receive notification of profile changes 192 Profile Change Upload - upload profile data changes back to the 193 profile delivery server 195 Discovery is the process by which a UA finds the address and port at 196 which it enrolls with the profile delivery server. As there is no 197 single discovery mechanism which will work in all network 198 environments, a number of discovery mechanisms are defined with a 199 prescribed order in which the UA tries them until one succeeds. 201 Enrollment is the process by which a UA makes itself known to the 202 profile delivery server. In enrolling, the UA provides identity 203 information, requested profile type(s) and supported protocols for 204 profile retrieval. It also subscribes to a mechanism for 205 notification of profile changes. As a result of enrollment, the UA 206 receives the data or the URI for each of the profiles that the 207 profile delivery server is able to provide. Each profile type (set) 208 requires a separate enrollment or SUBSCRIBE session. A profile type 209 may represent one or more data sets (e.g. one profile data set for 210 each of a user's applications). 212 Profile Retrieval is the process of retrieving the content for each 213 of the profiles the UA requested. 215 Profile Change Notification is the process by which the profile 216 delivery server notifies the UA that the content of one or more of 217 the profiles has changed. If the content is provided indirectly the 218 UA MAY retrieve the profile from the specified URI upon receipt of 219 the change notification. 221 Profile Change Upload is the process by which a UA or other entity 222 (e.g. corporate directory or configuration management server) pushes 223 a change to the profile data back up to the profile delivery server. 225 This framework defines a new SIP event package [RFC3265] to solve 226 enrollment and profile change notification steps. This event package 227 defines everything but the mandatory content type. This makes this 228 event package abstract until the content type is bound. The profile 229 content type(s) will be defined outside the scope of this document. 230 It is the author's belief that it would be a huge accomplishment if 231 all SIP user agent used this framework for delivering their existing 232 proprietary profiles. Even though this does not accomplish 233 interoperability of profiles, it is a big first step in easing the 234 administration of SIP user agents. The definition of standard 235 profiles and data sets (see [I-D.petrie-sipping-profile-datasets] ) 236 will enable interoperability as a subsequent step. 238 The question arises as to why SIP should be used for the profile 239 delivery framework. In this document SIP is used for only a small 240 portion of the framework. Other existing protocols are more 241 appropriate for transport of the profile contents (to and from the 242 user agent) and are suggested in this document. The discovery step 243 is simply a specified order and application of existing protocols. 244 SIP is only needed for the enrollment and change notification 245 functionality of the profile delivery framework. In many SIP 246 environments (e.g. carrier/subscriber and multi-site enterprise) 247 firewall, NAT (Network Address Translation) and IP addressing issues 248 make it difficult to get messages between the profile delivery server 249 and the user agent requiring the profiles. 251 With SIP the users and devices already are assigned globally routable 252 addresses. In addition the firewall and NAT problems are already 253 presumably solved in the environments in which SIP user agents are to 254 be used. Therefore SIP is the best solution for allowing the user 255 agent to enroll with the profile delivery server, which may require 256 traversal of multiple firewalls and NATs. For the same reason the 257 notification of profile changes is best solved by SIP. It should be 258 noted that this document is scoped to providing profiles for devices 259 which contain one or more SIP user agents. This framework may be 260 applied to non-SIP devices, however more general requirements for 261 non-SIP devices are beyond the scope of this document. 263 The content delivery server may be either in the public network or 264 accessible through a private network. The user agents requiring 265 profiles may be behind firewalls and NATs and many protocols, such as 266 HTTP, may be used for profile content retrieval without special 267 consideration in the firewalls and NATs (e.g. an HTTP client on the 268 UA can typically pull content from a server outside the NAT/ 269 firewall.). 271 2.4 Data Model 273 A conscious separation of device, user, application and local network 274 profiles is made in this document. This is useful to provide 275 features such as hotelling (described above) as well as securing or 276 restricting user agent functionality. By maintaining this 277 separation, a user may walk up to someone else's user agent and 278 direct that user agent to get the new user's profile data. In doing 279 so the user agent can replace the previous user's profile data while 280 still keeping the device's and the local network's profile data which 281 may be necessary for core functionality and communication described 282 in this document. The local network profiles are relevant to a 283 visiting device which gets plugged in to a foreign network. The 284 concept of the local network providing profile data is useful to 285 provide roaming (described above) as well as local policy data that 286 may constrain the user or device behavior relative to the local 287 network. For example media types and codecs may be constrained to 288 reflect the network's capabilities. 290 The separation of these profiles also enables the separation of the 291 management of the profiles. The user profile may be managed by a 292 profile delivery server operated by the user's ISP. The device 293 profile may be delivered from a profile delivery server operated by 294 the user's employer. The application profile(s) may be delivered 295 from the user's ASP (Application Service Provider). The local 296 network profile may delivered by a WLAN (Wireless LAN) hotspot 297 service provider. Some interesting services and mobility 298 applications are enabled with this separation of profiles. 300 A very high level data model is implied here with the separation of 301 these four profile types. Each profile type instance requires a 302 separate subscription to retrieve the profile. A loose hierarchy 303 exists mostly for the purpose of boot strapping and discovery or 304 formation of the profile URIs. No other meaning is implied by this 305 hierarchy. However the profile format and data sets to be defined 306 outside this document may define additional meaning to this 307 hierarchy. In the boot strapping scenario, a device straight out of 308 the box (software or hardware) does not know anything about it's user 309 or local network. The one thing that is does know is it's instance 310 id. So the hierarchy of the profiles exists as follows. 312 The instance id is used to form the user id part of the URI for 313 subscribing to the device profile. The device profile may contain a 314 default user AOR (Address of Record) for that device. The default 315 user AOR may then be used to retrieve the user profile. Applications 316 to be used on the device may be defined in the device and user 317 profiles. The user's AOR is also used to retrieve any application 318 profiles for that user. The local network profile is not referenced 319 in any way from the device, user, application profiles. It is 320 subscribed to and retrieved based upon a URI formed from the local 321 network domain. 323 3. Profile Change Event Notification Package 325 This section defines a new SIP event package [RFC3265]. The purpose 326 of this event package is to send to subscribers notification of 327 content changes to the profile(s) of interest and to provide the 328 location of the profile(s) via content indirection 329 [I-D.ietf-sip-content-indirect-mech] or directly in the body of the 330 NOTIFY. Frequently the profiles delivered to the user agent are much 331 larger (e.g. several KB or even several MB) than the MTU of the 332 network. These larger profiles will cause larger than normal SIP 333 messages and consequently higher impact on the SIP servers and 334 infrastructure. To avoid the higher impact and load on the SIP 335 infrastructure, content indirection SHOULD be used if the profile is 336 large enough to cause packet fragmentation over the transport 337 protocol. The presence of the MIME type for content indirection 338 [I-D.ietf-sip-content-indirect-mech] in the Accept header indicates 339 that the user agent supports content indirection and that the profile 340 delivery server SHOULD use content indirection. Similarly the 341 content type for the differential notification of profile changes 342 [I-D.ietf-simple-xcap-package] may be used in the Accept header to 343 express support for receiving profile change deltas. 345 The MIME types or formats of profiles to be delivered via this 346 framework are to be defined in the documents that define the profile 347 contents. These profile MIME types specified in the Accept header 348 along with the profile types specified in the Event header parameter 349 "profile-type" MAY be used to specify which profiles get delivered 350 either directly or indirectly in the NOTIFY requests. As this event 351 package does not specify the mandatory content type, this package is 352 abstract. The profile definition documents will specify the 353 mandatory content type to make a concrete event package. 355 3.1 Event Package Name 357 The name of this package is "sip-profile". This value appears in the 358 Event header field present in SUBSCRIBE and NOTIFY requests for this 359 package as defined in [RFC3265]. 361 3.2 Event Package Parameters 363 This package defines the following new parameters for the event 364 header: "profile-type", "vendor", "model", "version", "effective-by", 365 "document", "app-id", "network-user". The "effective-by" parameter 366 is for use in NOTIFY requests only. The "effective-by" parameter is 367 ignored if it appears in a SUBSCRIBE request. The others parameters 368 are for use in the SUBSCRIBE request and are ignored if they appear 369 in NOTIFY requests. 371 The "profile-type" parameter is used to indicate the token name of 372 the profile type the user agent wishes to obtain data or URIs for and 373 to be notified of subsequent changes. Using a token in this 374 parameter allows the URI semantics for retrieving the profiles to be 375 opaque to the subscribing user agent. All it needs to know is the 376 token value for this parameter. This document defines four logical 377 types of profiles and their token names. The contents or format of 378 the profiles is outside the scope of this document. 380 The four types of profiles defined here are "device", "user", 381 "application" and "local". Specifying "device" type profile(s) 382 indicates the desire for the profile data (URI when content 383 indirection is used) and change notification of the contents of the 384 profile that is specific to the device or user agent. Specifying 385 "user" type profile indicates the desire for the profile data (URI 386 when content indirection is used) and change notification of the 387 profile content for the user. Specifying "application" type profile 388 indicates the desire for the profile data (URI when content 389 indirection is used) and change notification of the profile content 390 for the user's applications. Specifying "local" type profile 391 indicates the desire for profiles data (URI when content indirection 392 is used) specific to the local network. The device, user, 393 application or local network is identified in the URI of the 394 SUBSCRIBE request. A separate SUBSCRIBE dialog is used for each 395 profile type. The profile type associated with the dialog can then 396 be used to infer which profile type changed and is contained in the 397 NOTIFY or content indirection URI. The Accept header of the 398 SUBSCRIBE request MUST include the MIME types for all profile content 399 types for which the subscribing user agent wishes to retrieve 400 profiles or receive change notifications. 402 Profile-type = "profile-type" EQUAL profile-value 403 profile-value = profile-types / token 404 profile-types = "device" / "user" / "application" / "local" 406 The "device", "user", "application" or "local" token in the 407 profile-type parameter may represent a class or set of profile 408 properties. As standards are defined for specific profile 409 contents related to the user, device or local network, it may be 410 desirable to define additional tokens for the profile-type 411 parameter. Also additional content types may be defined along 412 with the profile formats that can be used in the Accept header of 413 the SUBSCRIBE to filter or indicate what data sets of the profile 414 are desired. 416 The rational for the separation of user, device, application and 417 local network type profiles is provided in Section 2.3. It should be 418 noted that any of the types may result in zero or more profiles or 419 URIs being provided in the NOTIFY request. As discussed, a default 420 user may be assigned to a device. The default user's AOR, if defined 421 in the device profile, may in turn be used as the URI to SUBSCRIBE to 422 the "user" and "application" profile types. 424 The data provided in the four types of profiles may overlap. As an 425 example the codecs that a user prefers to use, the codecs that the 426 device supports (and the enterprise or device owner wishes to use), 427 the codecs that the local network can support (and the network 428 operator wishes to allow) all may overlap in how they are specified 429 in the three corresponding profiles. This policy of merging the 430 constraints across the multiple profile types can only unambiguously 431 be defined along with the profile format and syntax. This is out of 432 scope for this document. 434 The "vendor", "model" and "version" parameter values are tokens 435 specified by the implementer of the user agent. These parameters 436 MUST be provided in the SUBSCRIBE request for all profile types. The 437 implementer SHOULD use their DNS domain name (e.g. example.com) as 438 the value of the "vendor" parameter so that it is known to be unique. 439 These parameters are useful to the profile delivery server to affect 440 the profiles provided. In some scenarios it is desirable to provide 441 different profiles based upon these parameters. For example feature 442 property X in a profile may work differently on two versions of user 443 agent. This gives the profile delivery server the ability to 444 compensate for or take advantage of the differences. 446 Vendor = "vendor" EQUAL token / quoted-string 447 Model = "model" EQUAL token / quoted-string 448 Version = "version" EQUAL token / quoted-string 450 The "network-user" parameter MAY be used when subscribing for device 451 and local network profiles. When the profile-type is "device" or 452 "local" , the SUBSCRIBE URI addresses the device or local network 453 profile delivery server. It by design cannot indicate the user's 454 identity. The "network-user" parameter is used to indicate the 455 user's AOR. The SUBSCRIBE server may authenticate the subscriber to 456 verify this AOR. If the value of the "profile-type" parameter is not 457 "device" or "local", the "network-user" parameter has no defined 458 meaning and is ignored. 460 Network-User = "network-user" EQUAL name-addr / addr-spec 462 When the profile-type is "device", the user agent MAY set the 463 "network-user" parameter to the user's AOR. This is an indication to 464 the profile delivery server to set or change the association of the 465 default user with the device indicated in the SUBSCRIBE URI. If the 466 profile delivery server implements and allows this policy of setting 467 the default user with a device, the user agent can utilize this 468 mechanism to allow a user to login and make the user agent and user 469 association permanent. 471 In the case where the profile-type is "local", the user agent MAY set 472 the "network-user" parameter. If the user has special privileges 473 beyond that of an anonymous user in the local network, the 474 "network-user" parameter identifies the user to the local network. 475 The value of this parameter is the user's address of record. 477 The "effective-by" parameter in the Event header of the NOTIFY 478 request specifies the maximum number of seconds before the user agent 479 must attempt to make the new profile effective. A value of 0 (zero) 480 indicates that the subscribing user agent must attempt to make the 481 profiles effective immediately (despite possible service 482 interruptions). This gives the profile delivery server the power to 483 control when the profile is effective. This may be important to 484 resolve an emergency problem or disable a user agent immediately. 485 The "effective-by" parameter is ignored in all messages other than 486 the NOTIFY request. 488 Effective-By = "effective-by" EQUAL 1*DIGIT 490 The "document" parameter is used to specify a relative URI for a 491 specific profile document that the user agent wishes to retrieve and 492 to receive change notification. This is particularly useful for 493 profile content like XCAP [I-D.ietf-simple-xcap] where there is a 494 well defined URI schema and the user agent knows the specific content 495 that it wants. This provides a filtering mechanism to restrict the 496 content to be retrieved and for which change notification is to be 497 received. (The size of the content is important in limited bandwidth 498 environments.) The "document" parameter value syntax is a quoted 499 string. The values for the "document" parameter are defined as part 500 of the profile data format, which is out of scope for this document. 501 For more details on the use of this package with XCAP see Section 502 4.6. The "document" parameter MAY be set in SUBSCRIBE requests. It 503 is ignored in all other messages. 505 Document = "document" EQUAL quoted-string 507 The "app-id" parameter MAY be set when the "profile-type" parameter 508 value is "application". The "app-id" indicates that the user agent 509 wishes to retrieve the profile data or URI and change notification 510 for the application profile data for the specific application 511 indicated in the value of the "app-id" parameter. Like the 512 "document" parameter, the "app-id" parameter provides a filtering 513 mechanism on the profile content. The "app-id" parameter value is a 514 token. The values for the app-id parameter are defined as part of 515 the profile data format, which is out of scope for this document. 516 The "app-id" parameter has meaning only in SUBSCRIBE requests when 517 the "profile-type" Event header parameter is set to "application". 518 The "app-id" parameter is ignored in all other messages. 520 App-Id = "app-id" EQUAL token / quoted-string 522 SUBSCRIBE request Event header examples: 523 Event: sip-profile;profile-type=device; 524 vendor=vendor.example.com;model=Z100;version=1.2.3 526 Event: sip-profile;profile-type="user"; 527 document="user-aor/"; 528 vendor=premier;model=trs8000;version=5.5 530 NOTIFY request Event header examples: 531 Event: sip-profile;effective-by=0 533 Event: sip-profile;effective-by=3600 535 3.3 SUBSCRIBE Bodies 537 This package defines no new use of the SUBSCRIBE request body. 538 Future follow on documents may specify a filter-like mechanism using 539 etags to minimize the delivery or notification of profiles where the 540 user agent already has a current version. 542 3.4 Subscription Duration 544 As the presence (or lack of) a device or user agent it not very time 545 critical to the functionality of the profile delivery server, it is 546 recommended that default subscription duration be 86400 seconds (one 547 day). A one time fetch of a profile can be accomplished by setting 548 the Expires parameter to 0 as defined in [RFC3265] resulting in a 549 single NOTIFY with no change notification. 551 3.5 NOTIFY Bodies 553 The size of profile content is likely to be hundreds to several 554 thousand of bytes in size. For this reason if the Accept header of 555 the SUBSCRIBE included the MIME type: message/external-body 556 indicating support for content indirection the profile delivery 557 server SHOULD use content indirection 558 [I-D.ietf-sip-content-indirect-mech] in the NOTIFY body for providing 559 the profiles. 561 When delivering profiles via content indirection the profile delivery 562 server MUST include the Content-ID MIME header described in 563 [I-D.ietf-sip-content-indirect-mech] for each profile URI. This is 564 to avoid unnecessary download of the profiles. Some user agents are 565 not able to make a profile effective without rebooting or restarting. 566 Rebooting is something to be avoided on a user agent performing 567 services such as telephony. In this way the Content-ID allows the 568 user agent to avoid unnecessary interruption of service as well. The 569 Content-Type MUST be specified for each URI. The profile delivery 570 server MUST support the "http:" and "https:" schemes URI for content 571 indirection. Other URI schemes MAY also be provided in the content 572 indirection. 574 Initially user agent implementers may use a proprietary content 575 type for the profiles retrieved from the URI(s). This is a good 576 first step towards easing the management of user agents. Standard 577 profile contents, content type and formats will need to be defined 578 for true interoperability of profile delivery. The specification 579 of the content is out of the scope of this document. 581 The URI scheme [RFC2396] used in content indirection may be dictated 582 by the profile content that is required. It is expected that FTP 583 [RFC0959], HTTP [RFC2616], HTTPS [RFC2818], LDAP [RFC3377], XCAP 584 [I-D.ietf-simple-xcap] and other URI schemes could be used by this 585 package and framework if the subscribing user agent and profile 586 delivery server both support the same scheme. The negotiation of the 587 URI scheme is described in the following sections. 589 3.6 Notifier processing of SUBSCRIBE requests 591 The general rules for processing SUBSCRIBE requests [RFC3265] apply 592 to this package. If content indirection is used for delivering the 593 profiles, the notifier does not need to authenticate the subscription 594 as the profile content is not transported in the SUBSCRIBE or NOTIFY 595 transaction messages. With content indirection only URIs are 596 transported in the NOTIFY request which may be secured using the 597 techniques in Section 6. If content indirection is not used, SIPS 598 with SIP authentication SHOULD be used. The subscriber MUST support 599 the "http:" or "https:" URI scheme for content indirection. If the 600 subscriber wishes to use a URI scheme other than "http:", the 601 subscriber must use the "schemes" Contact header field parameter to 602 indicate the URI scheme as defined in 603 [I-D.ietf-sip-content-indirect-mech]. For example the subscriber may 604 request that content indirection use the "ldaps:" URI scheme by 605 including "ldaps" in the "scheme" Contact header parameter of the 606 SUBSCRIBE request. If the subscriber does not specify the URI 607 scheme, the notifier may use either "http:" or "https:". 609 The profile generation behavior of the profile delivery server is 610 left to the implementer. The profile delivery server may be as 611 simple as a SIP SUBSCRIBE UAS and NOTIFY UAC front end to a simple 612 HTTP server delivering static files that are hand edited. At the 613 other extreme the profile delivery server can be part of a 614 configuration management system that integrates with a corporate 615 directory and IT system or carrier operations support systems, 616 where the profiles are automatically generated. The design of 617 this framework intentionally provides the flexibility of 618 implementation from simple/cheap to complex/expensive. 620 If the user or device is not known to the profile delivery server, 621 the implementer MAY accept the subscription or reject it. It is 622 recommended that the implementer accept the subscription. It is 623 useful for the profile delivery server to maintain the subscription 624 for unprovisioned users or devices as an administrator may add the 625 user or device to the system after the initial subscription, defining 626 the profile contents. This allows the profile delivery server to 627 immediately send a NOTIFY request with the profile URIs. If the 628 profile delivery server does not accept the subscription from an 629 unknown user or device, the administer or user must manually provoke 630 the user agent to resubscribe. This may be difficult if the user 631 agent and administrator are at different locations. 633 A user agent can provide hotelling by collecting a user's AOR and 634 credentials needed to SUBSCRIBE and retrieve the user's profiles. 636 Hotelling functionality is achieved by subscribing to the user's AOR 637 and specifying the "user" profile type. This same mechanism can also 638 be used to secure a user agent, requiring a non-mobile user to login 639 to enable functionality beyond the default user's restricted 640 functionality. 642 When the Event header "profile-type" is "device" and the user agent 643 has provided the user's AOR in the "network-user" parameter, the 644 profile delivery server MAY set or change the default user associated 645 with the device indicated in the SUBSCRIBE URI. This is an 646 implementation or policy decision. The profile delivery server 647 SHOULD authenticate the user for the SUBSCRIBE request before 648 effecting the default user associated with the device as indicated in 649 the "network-user" parameter. 651 3.7 Notifier generation of NOTIFY requests 653 As in [RFC3265], the profile delivery server MUST always send a 654 NOTIFY request upon accepting a subscription. If the device or user 655 is unknown to the profile delivery server and it chooses to accept 656 the subscription, the implementer has two choices. A NOTIFY MAY be 657 sent with no body or content indirection containing the profile 658 URI(s). Alternatively a NOTIFY MAY be sent with a body or content 659 indirection containing URI(s) pointing to a default data set. The 660 data sets provided may allow for only limited functionality of the 661 user agent (e.g. a phone user agent with data to enable calls to 662 help desk and emergency services.). This is an implementation and 663 business policy decision for the profile delivery server. 665 If the URI in the SUBSCRIBE request is a known identity and 666 provisioned with the requested profile type (i.e. as specified in 667 the profile-type parameter of the Event header), the profile delivery 668 server SHOULD send a NOTIFY with profile data or content indirection 669 (if the content indirection mime type was included in the Accept 670 header) containing the URI for the profile. 672 The profile delivery server may specify when the new profiles must be 673 made effective by the user agent. The profile delivery server MAY 674 specify a maximum time in seconds (zero or more), in the 675 "effective-by" event header parameter, by which the user agent is 676 required to make the new profiles effective for all dialogs. 678 3.8 Subscriber processing of NOTIFY requests 680 The user agent subscribing to this event package MUST adhere to the 681 NOTIFY request processing behavior specified in [RFC3265]. The user 682 agent MUST attempt to make the profiles effective within the time in 683 seconds given in the "effective-by" Event header parameter if present 684 in the NOTIFY request (see Section 3.7). By default the user agent 685 makes the profiles effective as soon as it thinks that it is 686 non-obtrusive (e.g. when there are no active calls). Profile 687 changes SHOULD affect behavior on all new dialogs which are created 688 after the notification, but may not be able to affect existing 689 dialogs. The user agent SHOULD use one of the techniques specified 690 in Section 6 to securely retrieve the profiles. If the subscriber 691 included the MIME type: message/external-body for content indirection 692 in the SUBSCRIBE request Accept header, the subscriber MUST support 693 the http: or https: URI schemes for content indirection. If the 694 subscriber indicated alternative URI schemes for content indirection 695 it MUST also indicate support for http: or https:. The subscriber 696 should still be prepared to use http: or https: as the profile 697 delivery server may not support the alternative URI schemes. 699 3.9 Handling of forked requests 701 This event package allows the creation of only one dialog as a result 702 of an initial SUBSCRIBE request. The techniques to achieve this are 703 described in section 4.4.9 of [RFC3265]. 705 3.10 Rate of notifications 707 It is anticipated that the rate of change for user and device 708 profiles will be very infrequent (i.e. days or weeks apart). For 709 this reason no throttling or minimum period between NOTIFY requests 710 is specified for this package. 712 3.11 State Agents 714 State agents are not applicable to this event package. 716 3.12 Examples 718 Example SUBSCRIBE and NOTIFY request using content indirection: 720 SUBSCRIBE sip:MAC%3aFF00000036C5@acme.example.com SIP/2.0 721 Event: sip-profile;profile-type=device;vendor=vendor.example.com; 722 model=Z100;version=1.2.3 723 From: sip:MAC%3aFF00000036C5@acme.example.com;tag=1234 724 To: sip:MAC%3aFF00000036C5@acme.example.com;tag=abcd 725 Call-ID: 3573853342923422@10.1.1.44 726 CSeq: 2131 SUBSCRIBE 727 Contact: sip:MAC%3aFF00000036C5@10.1.1.44 728 Via: SIP/2.0/TCP 10.1.1.41; 729 branch=z9hG4bK6d6d35b6e2a203104d97211a3d18f57a 730 Accept: message/external-body, application/z100-device-profile 731 Content-Length: 0 733 NOTIFY sip:MAC%3aFF00000036C5@10.1.1.44 SIP/2.0 734 Event: sip-profile;effective-by=3600 735 From: sip:MAC%3aFF00000036C5@acme.example.com;tag=abcd 736 To: sip:MAC%3aFF00000036C5@acme.example.com;tag=1234 737 Call-ID: 3573853342923422@10.1.1.44 738 CSeq: 321 NOTIFY 739 Via: SIP/2.0/UDP 192.168.0.3; 740 branch=z9hG4bK1e3effada91dc37fd5a0c95cbf6767d1 741 MIME-Version: 1.0 742 Content-Type: multipart/mixed; boundary=boundary42 743 Content-Length: ... 745 --boundary42 746 Content-Type: message/external-body; 747 access-type="URL"; 748 expiration="Mon, 24 June 2002 09:00:00 GMT"; 749 URL="http://www.example.com/devices/ff00000036c5"; 750 size=1234 752 Content-Type: application/z100-device-profile 753 Content-ID: <39EHF78SA@example.com> 755 --boundary42-- 757 3.13 Use of URIs to Retrieve State 759 The URI for the SUBSCRIBE request is formed differently depending 760 upon which profile type the subscription is for. This allows the 761 different profile types to be potentially managed by different 762 profile delivery servers (perhaps even operated by different 763 entities). 765 3.13.1 Device URIs 767 The URI for the "device" type profile (device URI) is based upon the 768 identity of the device. The device URI MUST be unique across all 769 devices and implementations. If an instance id is used as the user 770 part of the device URI, it SHOULD remain the same for the lifetime of 771 the user agent. The device URI is used to identify which profile is 772 associated with a specific instance of a user agent. 774 If the user agent changed its device URI, the profile delivery 775 server would not know the association between the profile and the 776 device. This would also make it difficult for the profile 777 delivery server to track user agents under profile management. 778 The profile delivery server may decide to provide the same device 779 profile to all devices of the same vendor, model and version. 780 However this is a implementation choice on the profile delivery 781 server. The subscribing device has no way of knowing whether the 782 profiles for each device are different. For this reason the 783 device must always use a unique id in the device SUBSCRIBE request 784 URI. As an example the device profile for similar devices may 785 differ with properties such as the default user. This is how the 786 bootstrapping mechanism works as described in Section 4.1.3. 788 The URI for the device type profile MUST use a unique identifier as 789 the user portion of the URI. The host and port portion of the URI is 790 set to that of the domain or address of the profile deliver server 791 which manages that user agent. A means of discovering the host and 792 port portion is discussed in Section 4.1. There is an administration 793 aspect of the unique identifier, that makes it desirable for the id 794 to be obtainable or predictable prior to installation of the device 795 (hard or soft). Also from a human factors perspective, ids that are 796 easily distinguished and communicated will make the administrators 797 job a little easier. The MAC address or UUID SHOULD be used for 798 constructing a unique identifier to be used in the user portion of 799 the device URI. 801 If the identifier is a MAC address, it MUST be formatted as the 802 letters "MAC:" followed by a 12 digit hexadecimal representation of 803 the MAC address. The address can not include ":", whitespace, or 804 other formatting. 805 The MAC address of the device may be used if there will always be 806 no more than one user agent using that MAC address over time (e.g. 807 a dedicated telephone appliance). The MAC address may not be used 808 if more than one user agent instance exists or use the same MAC 809 address (e.g. multiple instances of a softphone may run on a 810 general purpose computing device). The advantage of the MAC 811 address is that many vendors put bar codes on the device with the 812 actual MAC address on it. A bar code scanner is a convenient 813 means of collecting the instance id for input and provisioning on 814 the profile delivery server. If the MAC address is used, it is 815 recommended that the MAC address is rendered in all upper case 816 with no punctuation for consistency across implementations. A 817 prefix of "MAC:" should be added to the MAC address to form a 818 proper URN [RFC2141]. For example a device managed by 819 sipuaconfig.example.com using its MAC address to form the device 820 URI might look like: 821 sip:MAC%3a00DF1E004CD0@sipuaconfig.example.com. 823 UHEX = DIGIT / %x41-46 ;uppercase A-F 824 MAC = %x4d.41.43 ; MAC in caps 825 RANDID = %x52.41.4e.44.49.44 ; RANDID in caps 826 uniq-ident = ( mac-ident / rand-ident ) 827 mac-ident = MAC "-" 12UHEX 829 When the MAC address is not used in the device URI, UUID SHOULD be 830 used. 832 For devices where there is no MAC address or the MAC address is 833 not unique to an instance of a user agent (e.g. multiple 834 softphones on a computer or a gateway with multiple logical user 835 agents) it is recommended that a UUID is used as the user portion 836 of the device URI. The same approach to defining a user agent 837 instance ID as [I-D.ietf-sip-gruu] should be used. When 838 constructing the instance id the implementer should also consider 839 that a human may need to manually enter the instance id to 840 provision the device in the profile delivery server (i.e. longer 841 strings are more error prone in data entry). When the URN is used 842 as the user part of URI, it MUST be URL escaped. The ":" is not a 843 legal character (without being escaped) in the user part of a 844 name-addr. For example the instance ID: 845 urn:uuid:f81d4fae-7ced-11d0-a765-00a0c91e6bf6 would be escaped to 846 look as follows in a URI: 847 sip:urn%3auuid%3af81d4fae-7ced-11d0-a765-00a0c91e6bf6@example.com. 848 Soft user agents are likely to need to use this approach due to 849 the multi-user nature of general purpose computers. The software 850 installer program might generate the uuid as part of the install 851 process so that it remains persistent for the installation. It 852 may also be desirable that any upgrades of the software maintain 853 the unique id. However these are all implementation choices. 855 3.13.2 User and Application URIs 857 The URI for the "user" and "application" type profiles is based upon 858 the identity of the user. The user's address of record (AOR) is used 859 as the URI in the SUBSCRIBE request. A new user agent or device may 860 not know the user's AOR. The user's AOR may be obtained as part of a 861 default user property in the device profile. Alternatively the user 862 agent may prompt the user for an AOR and credentials to be used to 863 authenticate the request. This can provide a login and/or hotelling 864 feature on the user agent. The user agent may be pre-provisioned 865 with the user's AOR or provided as information on a SIM or flash key. 866 These are only examples not an exhaustive list of sources for the 867 user AOR. 869 3.13.3 Local Network URIs 871 The URI for the "local" type profile is based upon the identity of 872 the local network. When subscribing to the local network profile, 873 the user part of the URI is "anonymous". The host and port part of 874 the URI is the local network name/domain. The discovery of the local 875 network name or domain is discussed in Section 4.1. The user agent 876 may provide the user's AOR as the value to the "network-user" event 877 header parameter. This is useful if the user has privileges in the 878 local network beyond those of the default user. The profile delivery 879 server SHOULD authenticate the user before providing the profile if 880 additional privileges are granted. Example URI: 881 sip:anonymous@example.com 883 4. Profile Delivery Framework Details 885 The following describes how different functional steps of the profile 886 delivery framework work. Also described here is how the event 887 package defined in this document provides the enrollment and 888 notification functions within the framework. 890 4.1 Discovery of Subscription URI 892 The discovery approach varies depending upon which profile type URI 893 is to be discovered. The order of discovery is important in the boot 894 strapping situation as the user agent may not have any information 895 provisioned. The local network profile should be discovered first as 896 it may contain key information such as how to traverse a NAT/firewall 897 to get to outside services (e.g. the user's profile delivery 898 server). The device profile URI should be discovered next. The 899 device profile may contain the default user's AOR or firmware/ 900 software information that should be updated first before proceeding 901 with the discovery process. The user and application profile 902 subscription URIs should be discovered last. The URIs are formed 903 differently for each of the profile types. This is to support the 904 delegation of the profile management to potentially four different 905 entities. However all four profile types may be provided by the same 906 entity. As the user agent has no way of knowing whether the profiles 907 are provide by one or more different profile delivery servers ahead 908 of time, it must subscribe to all four profile types in separate 909 SUBSCRIBE requests to get the profiles. 911 4.1.1 Discovery of Local Network URI 913 The "discovered" host for the "local" profile subscription URI is the 914 local IP network domain for the user agent, either provisioned as 915 part of the device's static network configuration or discovered via 916 DHCP. The local network profile subscription URI SHOULD not be 917 cached if the user agent moves from one local network to another 918 other. The user agent should perform the local network discovery 919 every time it starts up or network connectivity is regained. 921 For example: The user agent requested and received the local 922 domain name via DHCP: airport.example.net. The local network 923 profile SUBSCRIBE request URI would look like: 924 sip:anonymous@airport.example.net. The user agent should send 925 this request using the normal SIP locating mechanisms defined in 926 [RFC3263]. The Event header would look like the following if the 927 user agent decided to provide the user's AOR: 928 sip:alice@example.com as Alice may have a prior arrangement with 929 the local network operator giving her special policy privileges: 931 Event: sip-profile;profile-type=local; 932 network-user="sip:alice@example.com" 934 4.1.2 Discovery of Device URI 936 The discovery function is needed to bootstrap user agents to the 937 point of knowing where to enroll with the profile delivery server. 938 Section 3.13.1 describes how to form the user part of the device 939 profile SUBSCRIBE request URI used for enrollment. However the 940 bootstrapping problem for the user agent (out of the box) is what to 941 use for the host and port in the device URI. Due to the wide 942 variation of environments in which the enrolling user agent may 943 reside (e.g. behind residential router, enterprise LAN, WLAN 944 hotspot, ISP, dialup modem) and the limited control that the 945 administrator of the profile delivery server (e.g. enterprise, 946 service provider) may have over that environment, no single discovery 947 mechanism works everywhere. 949 Therefore a number of mechanisms should be tried in the specified 950 order: SIP DHCP option [RFC3361], SIP DNS SRV [RFC3263], DNS A record 951 and manual. The user agent may be pre-provisioned with the host and 952 port (e.g. service providers may pre-provision a device before 953 sending it to a subscriber, provide a SIM or flash key, etc.) in 954 which case this discovery mechanism is not needed. Before performing 955 the discovery steps, the user agent should provide a means to skip 956 the discovery stage and manually enter the device URI host and port. 957 In addition the user agent should allow the user to accept or reject 958 the discovered host and port, in case an alternate to the discovered 959 host and port are desired. 961 1. The first discovery mechanism that should be tried to construct 962 the device SUBSCRIBE request URI, as described in Section 3.13.1, 963 is to use the host and port of the out bound proxy discovered by 964 the SIP DHCP option as described in [RFC3361]. If the SIP DHCP 965 option is not provided in the DHCP response; or no SIP response 966 is received for the SUBSCRIBE request; or a SIP failure response 967 other than for authorization is received for the SUBSCRIBE 968 request to the sip-profile event, the next discovery mechanism 969 should be tried. 971 For example: Consider a dedicated hardware device with a 972 single user agent having the MAC address: abc123efd456. The 973 user agent sends a DHCP request including the request for the 974 DHCP option for SIP: 120 (see [RFC3361]). If the DHCP 975 response includes an answer for option 120, then the DNS name 976 or IP address included is used in the host part of the device 977 URI. For this example let's assume: example.com. The device 978 URI would look like: sip:MAC%3aABC123EFD456@example.com. The 979 user agent should send this request using the normal SIP 980 locating mechanisms defined in [RFC3263]. If the response 981 fails then, the next discovery mechanism is tried. 983 2. The local IP network domain for the user agent, either configured 984 or discovered via DHCP, should be used with the technique in 985 [RFC3263] to obtain a host and port to use in the SUBSCRIBE URI. 986 If no SIP response or a SIP failure response other than for 987 authorization is received for the SUBSCRIBE request to the 988 sip-profile event, the next discovery mechanism should be tried. 990 For example: The user agent requested and received the local 991 domain name (option 15) in the DHCP response: 992 boston.example.com. The device URI would look like: 993 sip:MAC%3aABC123EFD456@boston.example.com. The user agent 994 should send this request using the normal SIP locating 995 mechanisms defined in [RFC3263]. If the response fails then, 996 the next discovery mechanism is tried. 998 3. The fully qualified host name constructed using the host name 999 "sipuaconfig" and concatenated with the local IP network domain 1000 (as provided via DHCP or provisioned) should be tried next using 1001 the technique in [RFC3263] to obtain a host and port to use in 1002 the SUBSCRIBE URI. If no SIP response or a SIP failure response 1003 other than for authorization is received for the SUBSCRIBE 1004 request to the sip-profile event, the next discovery mechanism 1005 should be tried. 1007 For example: The user agent requested and received the local 1008 domain name via DHCP as in the above example: 1009 boston.example.com. The device URI would look like: 1010 sip:MAC%3aABC123EFD456@sipuaconfig.boston.example.com. The 1011 user agent should send this request using the normal SIP 1012 locating mechanisms defined in [RFC3263]. If the response 1013 fails then, the next discovery mechanism is tried. 1015 4. If all other discovery techniques fail, the user agent MUST 1016 provide a manual means for the user to enter the host and port 1017 used to construct the SUBSCRIBE request URI. 1019 Two approaches to the manual discovery process are suggested. In the 1020 first approach using SIP, the user agent provides a means for 1021 entering the subscription host and port information for the request 1022 URI along with the user id and password to be used for authentication 1023 of the SUBSCRIBE request. With this approach the user agent begins 1024 with the enrollment process followed by the change notification and 1025 profile retrieve steps. 1027 An alternative to the manual discovery using SIP, is to start with 1028 the retrieve process. The user agent provides a means of entering a 1029 HTTPS URI along with the user id and password to be used for 1030 authentication of the retrieval of the profile. The retrieved device 1031 profile may contain the properties for the SUBSCRIBE request URI and 1032 credentials to enroll and get change notification of profile changes. 1033 This approach bootstraps the process in a different step in the 1034 cycle, but uses the same profile framework. 1036 Once a user agent has successfully discovered, enrolled and received 1037 a NOTIFY response with profile data or URI(s), the user agent should 1038 cache the device profile SUBSCRIBE request URI to avoid having to 1039 rediscover the profile delivery server again in the future. Caching 1040 of the device URI is necessary when the user agent is likely to move 1041 to different local network domains as the local network may not be 1042 the provider for the device's profile. The user agent should not 1043 cache the device URI until it receives a NOTIFY with profile data or 1044 URI(s). The reason for this is that a profile delivery server may 1045 send 202 responses to SUBSCRIBE requests and NOTIFY responses to 1046 unknown user agent (see Section 3.6) with no profile data or URIs. 1047 Until the profile delivery server has sent a NOTIFY request with 1048 profile data or URI(s), it has not agreed to provide profiles. 1050 To illustrate why the user agent should not cache the device 1051 profile SUBSCRIBE URI until profile data or URI(s) are provided in 1052 the NOTIFY, consider the following example: a user agent running 1053 on a laptop plugged into a visited LAN in which a foreign profile 1054 delivery server is discovered. The profile delivery server never 1055 provides profile URIs in the NOTIFY request as it is not 1056 provisioned to accept the user agent. The user then takes the 1057 laptop to their enterprise LAN. If the user agent cached the 1058 SUBSCRIBE URI from the visited LAN (which did not provide 1059 profiles), when subsequently placed in the enterprise LAN which is 1060 provisioned to provide profiles to the user agent, the user agent 1061 would not attempt to discover the profile delivery server. 1063 4.1.3 Discovery of User and Application URI 1065 The default user's AOR from the device profile (if provided) may then 1066 be used to subscribe to the "user" and "application" profiles. The 1067 user's AOR may be preprovisioned or provided via SIM or flash key, 1068 etc. Alternatively the user's AOR to be used for the "user" and 1069 "application" subscription URI, may be "discovered" manually by 1070 prompting the user. This "discovered" URI for the user and 1071 application profile subscription may be cached. 1073 4.2 Enrollment with Profile Server 1075 Enrollment is accomplished by subscribing to the event package 1076 described in Section 3. The enrollment process is useful to the 1077 profile delivery server as it makes the server aware of user agents 1078 to which it may deliver profiles (those user agents the profile 1079 delivery server is provisioned to provide profiles to; those present 1080 to which the server may provide profiles in the future; and those 1081 that the server can automatically provide default profiles). It is 1082 an implementation choice and business policy as to whether the 1083 profile delivery server provides profiles to user agents that it is 1084 not explicitly provisioned to do so. However the profile delivery 1085 server SHOULD accept (with 2xx response) SUBSCRIBE requests from any 1086 user agent as explained in Section 3.5. 1088 4.3 Notification of Profile Changes 1090 The NOTIFY request in the sip-profile event package serves two 1091 purposes. First it provides the user agent with a means to obtain 1092 the profile data directly or via URI(s) for desired profiles without 1093 requiring the end user to manually enter them. It also provides the 1094 means for the profile delivery server to notify the user agent that 1095 the content of the profiles has changed and should be made effective. 1096 Optionally the differential changes may be obtained by notification 1097 by including the content-type: "application/xcap-diff+xml" defined in 1099 [I-D.ietf-simple-xcap-package] in the Accept header of the SUBSCRIBE 1100 request. 1102 4.4 Retrieval of Profile Data 1104 The user agent retrieves its needed profile(s) directly or via the 1105 URI(s) provided in the NOTIFY request as specified in Section 3.5. 1106 The profile delivery server SHOULD secure the content of the profiles 1107 using one of the techniques described in Section 6. The user agent 1108 SHOULD make the new profiles effective in the timeframe described in 1109 Section 3.2. 1111 The contents of the profiles SHOULD be cached by the user agent. The 1112 cache should be used if the user agent is unable to successfully 1113 SUBSCRIBE or receive the NOTIFY providing the most recent profile. 1114 This it to avoid the situation where the content delivery server is 1115 not available, leaving the user agent non-functional. The user agent 1116 should verify that it has the latest profile content using the "hash" 1117 parameter defined in [I-D.ietf-sip-content-indirect-mech]. 1119 4.5 Upload of Profile Changes 1121 The user agent or other service MAY push changes up to the profile 1122 delivery server using the technique appropriate to the profile's URL 1123 scheme (e.g. HTTP PUT method, FTP put command). The technique for 1124 pushing incremental or atomic changes MUST be described by the 1125 specific profile data framework. A means for pushing changes up into 1126 the profile delivery server for XCAP is defined in 1127 [I-D.ietf-simple-xcap]. 1129 4.6 Usage of XCAP with the Profile Package 1131 This framework allows for the usage of several different protocols 1132 for the retrieval of profiles. One protocol which is suitable is 1133 XCAP [I-D.ietf-simple-xcap], which allows for HTTP URIs to represent 1134 XML documents, elements and attributes. XCAP defines a specific 1135 hierarchy for how documents are organized. As a result, it is 1136 necessary to discuss how that organization relates to the rough data 1137 model presented here. 1139 When a user or device enrolls with a SUBSCRIBE request, the request 1140 URI will contain some kind of identifying information for that user 1141 or device. This identity is mapped to an XCAP User ID (XUID) based 1142 on an implementation specific mapping. The "profile-type" along with 1143 the "app-id" Event header parameters specify the specific XCAP 1144 application usage. 1146 In particular, when the Event header parameter "profile-type" is 1147 "application", the "app-id" MAY be included to contain the XCAP 1148 Application Unique ID (AUID). When the "profile-type" is 1149 "application", but the "app-id" parameter is absent, this specifies 1150 that the user wishes to SUBSCRIBE to all documents for all 1151 application usages associated with the user in the request-uri. This 1152 provides a convenient way for a single subscription to be used to 1153 obtain all application data. The XCAP root is determined by a local 1154 mapping. 1156 When the "profile-type" is "device", or "user" or "local", this maps 1157 to an AUID and document selector for representing device, user and 1158 local-network data, respectively. The mapping is a matter of local 1159 policy. This allows different providers to use different XCAP 1160 application usages and document schemas for representing these 1161 profiles, without having to configure the device with the specific 1162 AUID which is being used. 1164 Furthermore, when the "document" attribute is present, it identifies 1165 a specific document that is being requested. If the "profile-type" 1166 is "application", the "app-id" MAY be present as well if the 1167 "document" relative path does not indicate the specific application 1168 profile. The "document" attribute then specifies a relative path 1169 reference. Its first path segment is either "global", specifying 1170 global data, or "user", specifying user data for the user in the 1171 request URI. The next path segment identifies the path in the global 1172 directory or the user's home directory. For "profile-type" 1173 "application", if "app-id" is not present the next path segment (i.e. 1174 after "global" or the user's home directory segment) MAY indicate the 1175 XCAP Application Unique ID (AUID) if the user agent wishes to 1176 subscribe to a specific application profile. 1178 For example, consider a phone with an instance ID of 1179 urn:uuid:00000000-0000-0000-0000-0003968cf920. To obtain its device 1180 profile, it would generate a SUBSCRIBE that contain the following 1181 Request-Line and Event header: (Note that line folding of the 1182 Request-URI is illegal in SIP. The Request URI is shown broken 1183 across the first 3-line here only due to formatting limitations of 1184 IETF documents.) 1186 SUBSCRIBE 1187 sip:urn%3auuid%3a00000000-0000-0000-0000-0003968cf920@example.com 1188 SIP/2.0 1189 Event: sip-profile;profile-type=device 1191 If the profile data is stored in an XCAP server, the server would map 1192 the "device" profile to an application usage and document selector 1193 based on local policy. If this mapping specifies the AUID 1194 "vendor2-device-data" and a document called "index" within the user 1195 directory, the corresponding HTTP URI for the document is: (Note that 1196 this URL is only one line; it is split across two lines due to 1197 formatting limitations of IETF documents.) 1199 http://xcap.example.com/root/vendor2-device-data/users/ 1200 urn%3auuid%3a00000000-0000-0000-0000-0003968cf920/index 1202 and indeed, if a content indirection is returned in a NOTIFY, the URL 1203 would equal this. 1205 That user profile might specify the user identity (as a SIP AOR) and 1206 their application-usages. From that, the device can enroll to learn 1207 about its application data. To learn about all of the data: 1209 SUBSCRIBE sip:alice@example.com SIP/2.0 1210 Event: sip-profile;profile-type=application 1212 The server would map the request URI to an XUI (user-aor, for 1213 example) and the xcap root based on local policy. If there are two 1214 AUIDs, "resource-lists" [I-D.ietf-simple-xcap-list-usage] and 1215 "rls-services" [I-D.ietf-simple-xcap-list-usage], this would result 1216 in a subscription to all documents within: 1218 http://xcap.example.com/root/rls-services/users/user-aor 1219 http://xcap.example.com/root/resource-lists/users/user-aor 1221 The user would not be subscribed to the global data for these two 1222 application usages, since that data is not important for users. 1224 However, the user/device could be made aware that it needs to 1225 subscribe to a specific document. In that case, its subscribe would 1226 look like: 1228 SUBSCRIBE sip:user-aor@example.com SIP/2.0 1229 Event: sip-profile;profile-type=application;app-id=resource-lists 1230 ;document="global/index" 1232 this would result in a subscription to the single global document for 1233 resource-lists. 1235 In some cases, these subscriptions are to a multiplicity of 1236 documents. In that case, the notification format will need to be one 1237 which can indicate what document has changed. This includes content 1238 indirection, but also the xcap diff format 1239 [I-D.ietf-simple-xcap-package]. 1241 5. IANA Considerations 1243 There are several IANA considerations associated with this 1244 specification. 1246 5.1 SIP Event Package 1248 This specification registers a new event package as defined in 1249 [RFC3265]. The following information required for this registration: 1250 Package Name: sip-profile 1251 Package or Template-Package: This is a package 1252 Published Document: RFC XXXX (Note to RFC Editor: Please fill in 1253 XXXX with the RFC number of this specification). 1254 Person to Contact: Daniel Petrie dpetrie AT pingtel.com 1255 New event header parameters: profile-type, vendor, model, version, 1256 effective-by, document, app-id, network-user 1258 6. Security Considerations 1260 Profiles may contain sensitive data such as user credentials and 1261 personal information. The protection of this data depends upon how 1262 the data is delivered. Some profiles may be safe to deliver without 1263 the need to protect the content. For example in some environments 1264 the local network profile may contain the list of codecs that are 1265 acceptable for use in the network and information on NAT traversal 1266 such as a STUN server to use. As the information in this example 1267 local network profile does not contain passwords or sensitive 1268 information it may be acceptable to provide it without authentication 1269 or confidentiality (encryption). We refer to these as 1270 non-confidential profiles. Non-confidential profiles require message 1271 integrity and profile server authentication, as described in Section 1272 6.3. However any profiles that contain personal information, 1273 passwords or credentials (confidential profiles) require mutual 1274 authentication, confidentiality, and message integrity, and must 1275 follow the guidance provided in the next two subsections. Profile 1276 specifications that define schemas MUST identify if they contain 1277 confidential data to indicate which of the security approaches 1278 describer here should be used. 1280 The profile data is delivered in either the NOTIFY request or via the 1281 URI scheme indicated in the content indirection in the NOTIFY 1282 request. The security approach is different for these two delivery 1283 mechanisms. 1285 Subscribers implementing this specification MUST implement either 1286 HTTP or HTTPS. Subscribers also MUST implement the hash verification 1287 scheme described in SIP content indirection 1288 [I-D.ietf-sip-content-indirect-mech]. SIP profile delivery servers 1289 MUST implement both HTTP and HTTPS, and SHOULD implement a SIP 1290 Authentication Service as described in the SIP Identity mechanism 1291 [I-D.ietf-sip-identity]. All SIP entities are already required to 1292 implement SIP Digest authentication [RFC3261]. 1294 6.1 Confidential Profile Content in NOTIFY Request 1296 When the profile data is delivered directly in the NOTIFY request, 1297 the SUBSCRIBE request MUST be authenticated (for example, using the 1298 SIP Digest authentication mechanism). As the profile content is 1299 delivered in the resulting NOTIFY request to the subscription, 1300 authenticating the SUBSCRIBE is the only way to prevent unauthorized 1301 access to the profile data. To provide message integrity and 1302 confidentiality over the profile data, a direct TLS connection 1303 established with the SUBSCRIBE request or S/MIME MUST be used for the 1304 NOTIFY request containing the profile data. The profile data in the 1305 S/MIME body should be encrypted using the public key for the user or 1306 device subscribing to the profile data. For user, application and 1307 local network profiles the user public key is used. For device 1308 profiles the device public key is used. 1310 6.2 Confidential Profile Content via Content Indirection 1312 When the profile data is delivered via content indirection, SIP 1313 integrity protection (a direct TLS connection established by the user 1314 agent for the SUBSCRIBE request, S/MIME or [I-D.ietf-sip-identity]) 1315 MUST be used to protect the integrity of any content indirection body 1316 provided in a SIP NOTIFY request. In addition, the indirect profile 1317 transport mechanism also requires security protection. A 1318 non-replayable authentication mechanism such as Digest authentication 1319 MUST be used for the content indirection URI scheme which provides 1320 the profile data (e.g. LDAP, HTTP and HTTPS all support Digest 1321 authentication). URI schemes which provide no authentication or only 1322 clear-text authentication SHOULD NOT be used for profile delivery as 1323 they are vulnerable to replay attacks (e.g. TFTP does not provide 1324 authentication). 1325 Without a suitable authentication mechanism, the content 1326 indirection profile delivery URI scheme is susceptible to replay 1327 attacks. Even if the profile is symmetrically encrypted, if it 1328 can be retrieved through a replay attack, the encrypted profile 1329 can be used for offline attacks to crack the encryption key. 1331 The profile delivery scheme MUST use channel security such as TLS 1332 (e.g. HTTPS) to protect the content from being snooped in transport 1333 to the user agent. Mutual authentication using the client and server 1334 certificates MAY be used to verify the authenticity of the user or 1335 device identity and the profile delivery server identity. The user 1336 agent SHOULD provide a mechanism for the user to approve the profile 1337 delivery server identity or provision the acceptable server 1338 identity(s) through out of band means. Other transport schemes which 1339 do not support TLS MAY be used if communications channel for profile 1340 transport is known to be secured (e.g. VPN or IPsec type 1341 mechanisms). 1343 6.3 Integrity protection for non-confidential profiles 1345 Even for non-confidential profiles, the subscriber MUST verify the 1346 authenticity of the profile delivery server, and MUST verify that the 1347 integrity of the profile data and content indirection URI, if one is 1348 provided. To meet these requirements in the SIP messaging the NOTIFY 1349 request MUST use a SIP Identity header [I-D.ietf-sip-identity], or S/ 1350 MIME. If content is provided via redirection, the content 1351 indirection "hash" parameter MUST be included unless the profile data 1352 is delivered via a protocol which natively provides authentication 1353 and message integrity, such as HTTP or LDAP protected by TLS. The 1354 content retrieved via the content indirection URI MUST be integrity 1355 checked using the "hash" parameter. 1357 For example, Alice subscribes to the local domain profile for 1358 paris.example.com. She receives the following NOTIFY request which 1359 uses content indirection, including a "hash" parameter. Alice uses 1360 the Identity header from the NOTIFY to verify that the request came 1361 from paris.example.com and that the body was not modified. Then she 1362 fetches the content at the provided URI and verifies that the hash 1363 she calculates from the profile matches the hash provided in the SIP 1364 signaling. 1366 7. Acknowledgements 1368 Many thanks to those who contributed and commented on the many 1369 iterations of this document. Detailed input was provided by Jonathan 1370 Rosenberg from Cisco, Henning Schulzrinne from Columbia University, 1371 Cullen Jennings from Cisco, Rohan Mahy from Airespace, Rich Schaaf 1372 from Pingtel, Volker Hilt from Bell Labs, Hisham Khartabil from 1373 Telio, Henry Sinnreich from MCI, Martin Dolly from AT&T Labs, John 1374 Elwell from Siemens, Elliot Eichen and Robert Liao from Verizon. 1376 8. Change History 1378 [[RFC Editor: Please remove this entire section upon publication as 1379 an RFC.]] 1381 8.1 Changes from draft-ietf-sipping-config-framework-05.txt 1383 Made HTTP and HTTPS profile transport schemes mandatory in the 1384 profile delivery server. The subscribing device must implement 1385 HTTP or HTTPS as the profile transport scheme. 1386 Rewrote the security considerations section. 1387 Divided references into Normative and Informative. 1388 Minor edits through out. 1390 8.2 Changes from draft-ietf-sipping-config-framework-04.txt 1392 Clarified usage of instance-id 1393 Specify which event header parameters are mandatory or optional 1394 and in which messages. 1395 Included complete list of event header parameters in parameter 1396 overview and IANA sections. 1397 Removed TFTP reference as protocol for profile transport. 1398 Added examples for discovery. 1399 Added ABNF for all event header parameters. 1400 Changed profile-name parameter back to profile-type. This was 1401 changed profile-name in 02 when the parameter could contain either 1402 a token or a path. Now that the path is contained in the separate 1403 parameter: "document", profile-type make more sense as the 1404 parameter name. 1405 Fixed some statements that should have and should not have been 1406 normative. 1407 Added the ability for the user agent to request that the default 1408 user associated with the device be set/changed using the 1409 "network-user" parameter. 1410 A bunch of editorial nits and fixes. 1412 8.3 Changes from draft-ietf-sipping-config-framework-03.txt 1414 Incorporated changes to better support the requirements for the use 1415 of this event package with XCAP and SIMPLE so that we can have one 1416 package (i.e. simple-xcap-package now defines a content type not a 1417 package). Added an additional profile type: "application". Added 1418 document and app-id Event header parameters in support of the 1419 application profile. Define a loose high level data model or 1420 relationship between the four profile types. Tried to edit and fix 1421 the confusing and ambiguous sections related to URI formation and 1422 discovery for the different profile types. Better describe the 1423 importance of uniqueness for the instance id which is used in the 1424 user part of the device URI. 1426 8.4 Changes from draft-ietf-sipping-config-framework-02.txt 1428 Added the concept of the local network as a source of profile data. 1430 There are now three separate logical sources for profile data: user, 1431 device and local network. Each of these requires a separate 1432 subscription to obtain. 1434 8.5 Changes from draft-ietf-sipping-config-framework-01.txt 1436 Changed the name of the profile-type event parameter to profile-name. 1437 Also allow the profile-name parameter to be either a token or an 1438 explicit URI. 1440 Allow content indirection to be optional. Clarified the use of the 1441 Accept header to indicate how the profile is to be delivered. 1443 Added some content to the Iana section. 1445 8.6 Changes from draft-ietf-sipping-config-framework-00.txt 1447 This version of the document was entirely restructured and re-written 1448 from the previous version as it had been micro edited too much. 1450 All of the aspects of defining the event package are now organized in 1451 one section and is believed to be complete and up to date with 1452 [RFC3265]. 1454 The URI used to subscribe to the event package is now either the user 1455 or device address or record. 1457 The user agent information (vendor, model, MAC and serial number) are 1458 now provided as event header parameters. 1460 Added a mechanism to force profile changes to be make effective by 1461 the user agent in a specified maximum period of time. 1463 Changed the name of the event package from sip-config to sip-profile 1465 Three high level security approaches are now specified. 1467 8.7 Changes from draft-petrie-sipping-config-framework-00.txt 1469 Changed name to reflect SIPPING work group item 1471 Synchronized with changes to SIP DHCP [RFC3361], SIP [RFC3261] and 1472 [RFC3263], SIP Events [RFC3265] and content indirection 1473 [I-D.ietf-sip-content-indirect-mech] 1475 Moved the device identity parameters from the From field parameters 1476 to User-Agent header parameters. 1478 Many thanks to Rich Schaaf of Pingtel, Cullen Jennings of Cisco and 1479 Adam Roach of Dyamicsoft for the great comments and input. 1481 8.8 Changes from draft-petrie-sip-config-framework-01.txt 1483 Changed the name as this belongs in the SIPPING work group. 1485 Minor edits 1487 8.9 Changes from draft-petrie-sip-config-framework-00.txt 1489 Split the enrollment into a single SUBSCRIBE dialog for each profile. 1490 The 00 draft sent a single SUBSCRIBE listing all of the desired. 1491 These have been split so that each enrollment can be routed 1492 differently. As there is a concept of device specific and user 1493 specific profiles, these may also be managed on separate servers. 1494 For instance in a roaming situation the device might get its profile 1495 data from a local server which knows the LAN specific profile data. 1496 At the same time the user specific profiles might come from the 1497 user's home environment profile delivery server. 1499 Removed the Config-Expires header as it is largely superfluous with 1500 the SUBSCRIBE Expires header. 1502 Eliminated some of the complexity in the discovery mechanism. 1504 Suggest caching information discovered about a profile delivery 1505 server to avoid an avalanche problem when a whole building full of 1506 devices powers up. 1508 Added the User-Profile From header field parameter so that the device 1509 can request a user specific profile for a user that is different from 1510 the device's default user. 1512 9. References 1514 9.1 Normative References 1516 [I-D.ietf-sip-content-indirect-mech] 1517 Burger, E., "A Mechanism for Content Indirection in 1518 Session Initiation Protocol (SIP) Messages", 1519 draft-ietf-sip-content-indirect-mech-05 (work in 1520 progress), October 2004. 1522 [I-D.ietf-sip-identity] 1523 Peterson, J., "Enhancements for Authenticated Identity 1524 Management in the Session Initiation Protocol (SIP)", 1525 draft-ietf-sip-identity-04 (work in progress), February 1526 2005. 1528 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1529 Requirement Levels", BCP 14, RFC 2119, March 1997. 1531 [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor 1532 Extensions", RFC 2132, March 1997. 1534 [RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", 1535 RFC 2246, January 1999. 1537 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 1538 Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext 1539 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 1541 [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., 1542 Leach, P., Luotonen, A. and L. Stewart, "HTTP 1543 Authentication: Basic and Digest Access Authentication", 1544 RFC 2617, June 1999. 1546 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. 1548 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 1549 A., Peterson, J., Sparks, R., Handley, M. and E. Schooler, 1550 "SIP: Session Initiation Protocol", RFC 3261, June 2002. 1552 [RFC3263] Rosenberg, J. and H. Schulzrinne, "Session Initiation 1553 Protocol (SIP): Locating SIP Servers", RFC 3263, June 1554 2002. 1556 [RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific 1557 Event Notification", RFC 3265, June 2002. 1559 [RFC3361] Schulzrinne, H., "Dynamic Host Configuration Protocol 1560 (DHCP-for-IPv4) Option for Session Initiation Protocol 1561 (SIP) Servers", RFC 3361, August 2002. 1563 9.2 Informative References 1565 [I-D.ietf-simple-xcap] 1566 Rosenberg, J., "The Extensible Markup Language (XML) 1567 Configuration Access Protocol (XCAP)", 1568 draft-ietf-simple-xcap-06 (work in progress), February 1569 2005. 1571 [I-D.ietf-simple-xcap-list-usage] 1572 Rosenberg, J., "Extensible Markup Language (XML) Formats 1573 for Representing Resource Lists", 1574 draft-ietf-simple-xcap-list-usage-05 (work in progress), 1575 February 2005. 1577 [I-D.ietf-simple-xcap-package] 1578 Rosenberg, J., "An Extensible Markup Language (XML) 1579 Document Format for Indicating Changes in XML 1580 Configuration Access Protocol (XCAP) Resources", 1581 draft-ietf-simple-xcap-package-03 (work in progress), 1582 January 2005. 1584 [I-D.ietf-sip-gruu] 1585 Rosenberg, J., "Obtaining and Using Globally Routable User 1586 Agent (UA) URIs (GRUU) in the Session Initiation Protocol 1587 (SIP)", draft-ietf-sip-gruu-02 (work in progress), July 1588 2004. 1590 [I-D.ietf-sipping-ua-prof-framewk-reqs] 1591 Petrie, D. and C. Jennings, "Requirements for SIP User 1592 Agent Profile Delivery Framework", 1593 draft-ietf-sipping-ua-prof-framewk-reqs-00 (work in 1594 progress), March 2003. 1596 [I-D.petrie-sipping-profile-datasets] 1597 Petrie, D., "A Schema for Session Initiation Protocol User 1598 Agent Profile Data Sets", 1599 draft-petrie-sipping-profile-datasets-00 (work in 1600 progress), July 2004. 1602 [I-D.sinnreich-sipdev-req] 1603 Butcher, I., Lass, S., Petrie, D., Sinnreich, H. and C. 1604 Stredicke, "SIP Telephony Device Requirements and 1605 Configuration", draft-sinnreich-sipdev-req-05 (work in 1606 progress), January 2005. 1608 [RFC0822] Crocker, D., "Standard for the format of ARPA Internet 1609 text messages", STD 11, RFC 822, August 1982. 1611 [RFC0959] Postel, J. and J. Reynolds, "File Transfer Protocol", STD 1612 9, RFC 959, October 1985. 1614 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 1615 2131, March 1997. 1617 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 1619 [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform 1620 Resource Identifiers (URI): Generic Syntax", RFC 2396, 1621 August 1998. 1623 [RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access 1624 Protocol (v3): Technical Specification", RFC 3377, 1625 September 2002. 1627 [W3C.REC-xml-names11-20040204] 1628 Tobin, R., Hollander, D., Layman, A. and T. Bray, 1629 "Namespaces in XML 1.1", W3C REC REC-xml-names11-20040204, 1630 February 2004. 1632 Author's Address 1634 Daniel Petrie 1635 Pingtel Corp. 1636 400 W. Cummings Park 1637 Suite 2200 1638 Woburn, MA 01801 1639 US 1641 Phone: "Dan Petrie (+1 617 835 1379)" 1642 EMail: dpetrie AT pingtel.com 1643 URI: http://www.pingtel.com/ 1645 Intellectual Property Statement 1647 The IETF takes no position regarding the validity or scope of any 1648 Intellectual Property Rights or other rights that might be claimed to 1649 pertain to the implementation or use of the technology described in 1650 this document or the extent to which any license under such rights 1651 might or might not be available; nor does it represent that it has 1652 made any independent effort to identify any such rights. Information 1653 on the procedures with respect to rights in RFC documents can be 1654 found in BCP 78 and BCP 79. 1656 Copies of IPR disclosures made to the IETF Secretariat and any 1657 assurances of licenses to be made available, or the result of an 1658 attempt made to obtain a general license or permission for the use of 1659 such proprietary rights by implementers or users of this 1660 specification can be obtained from the IETF on-line IPR repository at 1661 http://www.ietf.org/ipr. 1663 The IETF invites any interested party to bring to its attention any 1664 copyrights, patents or patent applications, or other proprietary 1665 rights that may cover technology that may be required to implement 1666 this standard. Please address the information to the IETF at 1667 ietf-ipr@ietf.org. 1669 The IETF has been notified of intellectual property rights claimed in 1670 regard to some or all of the specification contained in this 1671 document. For more information consult the online list of claimed 1672 rights. 1674 Disclaimer of Validity 1676 This document and the information contained herein are provided on an 1677 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1678 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1679 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1680 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1681 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1682 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1684 Copyright Statement 1686 Copyright (C) The Internet Society (2005). This document is subject 1687 to the rights, licenses and restrictions contained in BCP 78, and 1688 except as set forth therein, the authors retain all their rights. 1690 Acknowledgment 1692 Funding for the RFC Editor function is currently provided by the 1693 Internet Society.