SIPPING D. Petrie Internet-Draft SIPez LLC. Intended status: Standards Track S. Channabasappa, Ed. Expires: September2,4, 2007 CableLabs March 3, 2007 A Framework for Session Initiation Protocol User Agent Profile Deliverydraft-ietf-sipping-config-framework-10draft-ietf-sipping-config-framework-11 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on September2,4, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document defines a framework to enable configuration of Session Initiation Protocol (SIP) User Agents in SIP deployments. The framework provides a means to deliver profile data that User Agents need to be functional, automatically and with minimal (preferably none) User and Administrative intervention. The framework describes how SIP User Agents can discover sources, request profiles and receive notifications related to profile modifications. As part of this framework, a new SIP event package is defined for notification of profile changes. The framework provides for multiple data retrieval options, without requiring or defining retrieval protocols. The framework does not include specification of the profile data within its scope. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .65 3.1. Reference Model . . . . . . . . . . . . . . . . . . . . .65 3.2. Data Model and ProfileLife CycleTypes . . . . . . . . . . . . . . 9 3.3. Profile Life Cycle . . . . .9 3.3. Data Model and Profile Types. . . . . . . . . . . . . .109 4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .1110 4.1.Client with different Data and SIP Service ProvidersSimple Deployment Scenario . . . . . . . .11. . . . . . . 10 4.2.ClientsDevices supporting multiple users from different Service Providers . . . . . . . . . . . . . . . . . . . .1312 5. Profile Delivery Framework . . . . . . . . . . . . . . . . . .1514 5.1. ProfileDiscovery .Enrollment . . . . . . . . . . . . . . . . . . .1817 5.1.1.SIP SUBSCRIBE for the Local-Network Profile TypeCreation of Enrollment Subscription . . .19 5.1.2. SIP SUBSCRIBE for the Device Profile Type. . . . . .20 5.1.3. SIP SUBSCRIBE for the User17 5.1.2. ProfileTypeEnrollment Request Transmission . . . . . . . 245.1.4. Caching of SIP Subscription URIs5.1.3. Profile Enrollment Notification . . . . . . . . . . . 24 5.2. ProfileEnrollment . . .Content Retrieval . . . . . . . . . . . . . . . . 25 5.3. ProfileNotification . .Change Operation . . . . . . . . . . . . . . . .2625 5.4. ProfileRetrieval . . . . . . . . . . . . . . . . . . . . 26 5.5. ProfileChangeUpload . . .Notification . . . . . . . . . . . . . . .26 5.6.25 5.5. Additional Considerations . . . . . . . . . . . . . . . .27 5.6.1.25 5.5.1. Manual retrieval of the Device Profile . . . . . . . .27 5.6.2. Client26 5.5.2. Device Types . . . . . . . . . . . . . . . . . . . . .28 5.6.3.26 5.5.3. Profile Data . . . . . . . . . . . . . . . . . . . . .28 5.6.4.27 5.5.4. Profile Data Frameworks . . . . . . . . . . . . . . .28 5.6.5.27 5.5.5. Additional Profile Types . . . . . . . . . . . . . . .2928 5.5.6. Deployment considerations . . . . . . . . . . . . . . 28 6. Event Package Definition . . . . . . . . . . . . . . . . . . .2928 6.1. Event Package Name . . . . . . . . . . . . . . . . . . . 29 6.2. Event Package Parameters . . . . . . . . . . . . . . . . 29 6.3. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . .3332 6.4. Subscription Duration . . . . . . . . . . . . . . . . . . 33 6.5. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . .3433 6.6. Notifier Processing of SUBSCRIBE Requests . . . . . . . .3433 6.7. Notifier Generation of NOTIFY Requests . . . . . . . . .3534 6.8. Subscriber Processing of NOTIFY Requests . . . . . . . . 35 6.9. Handling of Forked Requests . . . . . . . . . . . . . . .3635 6.10. Rate of Notifications . . . . . . . . . . . . . . . . . .3635 6.11. State Agents . . . . . . . . . . . . . . . . . . . . . .3635 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .3635 7.1. Example 1:ClientDevice requesting profile . . . . . . . . . . 36 7.2. Example 2:ClientDevice obtaining change notification . . . . .4039 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . .4443 8.1. SIP Event Package . . . . . . . . . . . . . . . . . . . .4443 8.2. New HTTP Event Header . . . . . . . . . . . . . . . . . .4443 9. Security Considerations . . . . . . . . . . . . . . . . . . .4544 9.1.Event Package .Profile Enrollment and Change Notification . . . . . . . 47 9.2. Profile Content Retrieval . . . . . . . . . . . . . .45 9.2. Profile Life Cycle. . 49 9.3. Profile Change Operation . . . . . . . . . . . . . . . . 50 10. Acknowledgements .46 9.3. Profile Data. . . . . . . . . . . . . . . . . . . . . .46 10. Acknowledgements51 11. Change History . . . . . . . . . . . . . . . . . . . . . . .47 11. Open Items. 51 11.1. Changes from draft-ietf-sipping-config-framework-10.txt . . . . . . . 51 11.2. Changes from draft-ietf-sipping-config-framework-09.txt . . . . . . . 52 11.3. Changes from draft-ietf-sipping-config-framework-08.txt . . . . . . . 52 11.4. Changes from draft-ietf-sipping-config-framework-07.txt . . . .47 12. Change History. . . 53 11.5. Changes from draft-ietf-sipping-config-framework-06.txt . . . . . . . 53 11.6. Changes from draft-ietf-sipping-config-framework-05.txt . . . . . . . 54 11.7. Changes from draft-ietf-sipping-config-framework-04.txt . . . . . . .48 12.1.54 11.8. Changes fromdraft-ietf-sipping-config-framework-09.txtdraft-ietf-sipping-config-framework-03.txt . . . . . . .48 12.2. Changes from draft-ietf-sipping-config-framework-08.txt . . . . . . . 49 12.3. Changes from draft-ietf-sipping-config-framework-07.txt . . . . . . . 49 12.4. Changes from draft-ietf-sipping-config-framework-06.txt . . . . . . . 49 12.5. Changes from draft-ietf-sipping-config-framework-05.txt . . . . . . . 50 12.6. Changes from draft-ietf-sipping-config-framework-04.txt . . . . . . . 50 12.7. Changes from draft-ietf-sipping-config-framework-03.txt . . . . . . . 51 12.8.54 11.9. Changes from draft-ietf-sipping-config-framework-02.txt . . . . . . .51 12.9.55 11.10. Changes from draft-ietf-sipping-config-framework-01.txt . . . . . . .51 12.10.55 11.11. Changes from draft-ietf-sipping-config-framework-00.txt . . . . . . .51 12.11.55 11.12. Changes from draft-petrie-sipping-config-framework-00.txt . . . . . .52 12.12.56 11.13. Changes from draft-petrie-sip-config-framework-01.txt . .52 12.13.56 11.14. Changes from draft-petrie-sip-config-framework-00.txt . .52 13.56 12. References . . . . . . . . . . . . . . . . . . . . . . . . . .53 13.1.57 12.1. Normative References . . . . . . . . . . . . . . . . . .53 13.2.57 12.2. Informative References . . . . . . . . . . . . . . . . .5458 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .5458 Intellectual Property and Copyright Statements . . . . . . . . . .5660 1. Introduction SIP User Agents require configuration data to function properly. Examples include network,Clientdevice and user specific information. Ideally, this configuration process should be automatic and require minimal or no user intervention. Many deployments of SIP User Agents require dynamic configuration and cannot rely on pre-configuration. This framework provides a standard means of providing dynamic configuration which simplifies deployments containing SIP User Agents from multiple vendors. This framework also addresses modifications to profiles and the corresponding change notifications to the SIP User Agents using a new event package. However, the framework does not define the content or format of the actual profile data, leaving that to future standardization activities. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].In addition, thisThis documentintroducesalso reuses the SIP terminology defined in [RFC3261] and [RFC3265], andutilizesspecifies the usage of the followingterms: Client:terms. Device: software or hardware entity containing one or more SIP user agents.Device:It may also contain entities such as a DHCP client. Device Provider: theterms 'Client' and 'Device' are used interchangeably within this framework. Serviceentity responsible for managing a given device Local Network Provider: the entity that controls the local network to which alogicalgiven device is connected SIP Service Provider: the entity providingone or more services.SIP services to users. This can refer to private enterprises or public entities. Profile: configuration data set specific to an entity (for example, user, device, local network or other). Profile Type: a particular category of Profile data (for example, User, Device, Local Network or other). Profile Delivery Server (PDS): the source of a Profile, it is the logical collection of the Profile Notification Component (PNC) and the Profile Content Component(PCC). Profile Notification Component (PNC): the logical component of a Profile Delivery Server that is responsible for enrollingClientsdevices and providing profile notifications. Profile Content Component (PCC): the logical component of a Profile Delivery Server that is responsible for storing, providing access to, and accepting profile content.Profile Discovery: discovery of a Profile Delivery Server (PDS) by the Client. Profile Enrollment: process of enrolling with one or more Profile Delivery Server(s) by a Client. Profile Notification: notification of a requested or changed profile by the PDS. Profile Retrieval: retrieval of Profile data from a PDS by a Client. Profile Change Upload: upload of profile data changes to one or more PDSs by authorized entities such as a Client Notifier: as defined in [RFC3265] the SIP user agent server which processes SUBSCRIBE requests for events and sends NOTIFY requests with profile data or URIs (Uniform Resource Identifiers) that point to the data. Instance ID: text identifier globally unique across all Clients.3. Overview This section provides an overview of the configuration framework. It introduces the reference model and explains key concepts such as the Profile Life Cycle and the Profiletypes. The framework isTypes. It is meant to serve as a reference section for the document, rather than providing a specific logical flow of material, as it may be necessary to revisit these sections for a complete understanding of this document. The detailed framework for the profile delivery, presented in Section5.5, is based on the concepts introduced in this section. 3.1. Reference Model The design of the framework was the result of a careful analysis to identify the configuration needs of a wide range of SIP deployments. As such, the reference model provides for a great deal of flexibility, while breaking down the interactions to their basic forms which can be reused in many different scenarios. In its simplest form, the reference model for the framework defines the interactions between the Profile Delivery Server(PDS) and theClient.device. TheClient is a SIP UA whichdevice needs the profile data to effectively function in the network. The PDS is responsible for responding toClientdevice requests and providing the profile data. The set of interactions between these entities is referred to as the Profile Life Cycle. This reference model is illustrated in the diagram below. +-------------------------++---------++--------+ Interactions | Profile Delivery Server | |ClientDevice |<==========================>| +---+ +---+ || (SIP UA)|+--------+ (Profile Life Cycle) | |PNC| |PCC| |+---------+| +---+ +---+ | +-------------------------+ PNC = Profile Notification Component PCC = Profile Content Component Framework Reference Model The PDS is subdivided into two logical components: o Profile Notification Component (PNC), responsible for enrollingClientsdevices in Profile event subscriptions and providing Profile change notifications; o Profile Content Component (PCC), responsible for storing, providing access to, and acceptingupdatesmodifications related to profile content. SIP deployments vary considerably.To be effective,For theconfiguration framework needs to consider a comprehensive setsake of simplicity, two deployment scenarios representing either end of the SIP deployment spectrum are presented. In the simplest scenario, a device connects through a network that isrepresentative of most deployments. The figure below providescontrolled by asystem level view ofsingle provider who provides thedevice, userlocal-network, manages the devices, andServiceoffers services to the users. The Providerrelationshipspropogates profile data to the device thatmay be involved. --------contains all the necessary information to obtain services in the network (including information related to the local-network and the users). This is illustrated in the following diagram. -------------- / Local-network, \ |Service | | Provider | - > Provides 'Client'(e.g. allowed Users) \ Y /Device &'User'(such as Services) profile -------- | ----- | / Local \ | | Network | | | Provider| - > Provides 'Local Network' profileService | \ZProvider /data (e.g. STUN Server Address) | --------------------- |/|/ =============== ( Local Network ) ===============-------- | Device | -------- |---------|Client X| - > Needs the 'Client' profile (from Y) --------- & 'local network' profile (from Z) / \ / \ ------ ------ |User A| |User B| - > Users need 'User' profile (from Y) ------ ------ Framework---- |User| ---- Simple System Level ModelBased on the system level model, the following considerationsThere arerelevant. Client connectivity: o Clientsalso deployments where the device can connecteither directly to a Service Provider orviaothera localnetworks (fornetwork that is not controlled by the SIP Service Provider, for example,home network, Public Wi-Fi Hotspots, enterprise managed LAN, etc.); o Local networks through which Clientsdevices that connect via available public WiFi hotspots. In such cases, Local Network Providers may wish to providetheir own configurationlocal network informationparticularsuch as bandwidth constraints to the devices. Devices may also be controlled by Device Providers thatspecific network (for example, STUN server information, local Proxy, etc.) which isare independent of the SIP Service Provider(whowho providesservices) or the particular User. Service provider relationships: o The local network provider (the network the Client connects to) and the Service Provider (that hosts the actual voice or other services) can often be different entities, with no administrative or business relationship to each other; o There may be multiple different Service Providers involved, one for each service type a User subscribes to (telephony service, instant messaging, etc); this Framework does not specify explicit behavior in such a scenario, but it does not prohibit its usage either o Each User accessing services via a Client may subscribe to different sets ofuser services,from different Service Providers; User-Client relationship: o The relationship between Clients and Users can be many-to-many (forfor example,a particular UA instance maykiosks that allowfor many Usersusers toobtain subscription services through it, and individual Users may haveaccessto multiple different UA devices); o Each User may have different preferences for use of services, and presentation of thoseservicesinanywhere. In such cases theClient user interface; o Each Userprofile data may havedifferent personal information applicable to use of the Client device, either as relatedtoparticular services, or independent of them. The observations above show a need for a clear distinction betweenbe obtained from differentProfile Types, based on the sourceprofile sources: local network provider, device provider andpurpose of the configuration data contained, and a need for these profiles to be manageable by different PDSs. Accordingly, the framework identifiesSIP service provider. This is indicated in the followingminimal Profile Types. Local-Network Profile: refers todiagram. -------- / SIP \ | Service | -> Provides 'user' profile | Provider | dataas provided by the Local Network to which a Client is directly connected;(e.g., services \ / configuration) -------- -------- | / \ | | DeviceProfile: refers to| -> Provides 'device' profile | | Provider | dataprovided by the Service(e.g., device specifics) | \ / | --------- | / | / ------- | / / Local \ | / | Network | | | | Provideror other entity which is specific to the particular Client; User Profile: refers to| -> Provides 'local-network' profile | | \ / dataprovided by the Service Provider or other entity which is specific to(e.g., bandwidth) | | ------- | | / | | / | | | =================== ( Local Network ) =================== | | -------- | Device | -> Needs theparticular User. The definition of additional Profile Types'local-network' -------- andtheir usage is allowed, but is outside'device' profile / \ / \ ------ ------ |User A| |User B| -> Users need 'user' profiles ------ ------ General System Level Model As illustrated, thescope of this document. The remaindersimplest deployments present a single profile source whereas others may present multiple profile sources. To be effective, a configuration framework needs to address various deployment scenarios. To address a vast majority of deployments thissection provides more information on the two vital componentsframework specifies three distinct profiles, each ofthe framework: Profile Life Cyclewhich can be obtained from a different provider, andProfile Types. 3.2. Profile Life Cycle Automated Profile deliverya profile life cycle common toClients requiresany profile type. The understanding is that deployments in general will support the defined profile types. However, the framework allows for flexibility in specialized cases. The devices are required to support all the three profile types, unless configured otherwise (at a minimum they need to support the device profile). The deployments are required to support the device profile, and user profiles for known users. In the presence of multiple profiles, a retrieval order is specified for the devices. Additional profiles may also be specified outside the scope of this document, but are expected to follow the same profile life cycle. 3.2. Data Model and Profile Types This framework specifies the following three profiles. Additional extended profiles may also be defined. Local Network Profile: contains configuration data related to the local network to which a device is directly connected. It is expected to be provided by the Local Network Provider. Device Profile: cContains configuration data related to a specific device, provided by the Device Provider. User Profile: contains configuration data related to a specific User, as required to reflect that user's preferences and the particular services subscribed to. It is expected to be provided by the SIP Service Provider providing services. 3.3. Profile Life Cycle Automated profile delivery requires proactive behavior on the part of aClient.device. It also requires one or more PDSs which provide the profile data.Profile DeliveryThe set of communications that results in profile delivery is characterized by the profile life cycle. Each profile is propogated using the profile life cycle. The life cycle isusuallyinitiated when theClient discovers PDSs and requestsdevice enrolls for profile data.TheEnrollment either results in profile datacan be modified byor in information referencing content indirection. In theClient (for example, by a User) and subsequently uploadedcase of content indirection, the provided retrieval procedures are used to retrieve thePDS. Alternatively,profile. Additionally, the profiledata can be modifiedlife cycle allows for profile change operations byanauthorizedentity such as an administrative or user interface and the Cliententities. If a profile change operation isnotified through an event notification.successful, it results in profile change notifications to all enrolled devices. The specific functional stepsinvolved in these interactions, collectively termed Profile Life Cycle,are as follows: ProfileDiscovery: TheEnrollment: the process by which aClient finds PDS(s)device requests, and if successful, enrolls with a PDS capable of providingthe Profiles it requires. This Framework defines multiple Profile Types which may be served by one or more PDSs. Profile Enrollment: The process by whichaClient makes itself known toprofile. A successful enrollment is indicated by aPDS. While enrolling, the Client provides identity information and requested Profile Type(s) for profile retrieval. It also subscribes fornotificationof profile changes. As a result of enrollment,containing theClient receivesprofile information (contents or content indirection information).Each Profile Type requiresDepending on the request, this could also result in aseparate enrollment or SUBSCRIBE session.subscription to notification of profile changes. ProfileNotification: TheContent Retrieval: the process by which a device retrieves profile contents, if thePDS notifies the Client that either requested Profile contents are available, or theprofile enrollment resulted in contentof one or more of the Profiles has changed. Ifindirection information. Profile Change Notification: thecontentprocess by which a device isprovided indirectly, the Clientnotified of any changes to an enrolled profile. This mayretrieveprovide the device with modified profilefrom the specified URI upon receipt of the change notification. Profile Retrieval: The process of retrieving thedata or contentfor each of the Profiles requested by the Client.indirection information. Profile ChangeUpload:Operation: The process by whicha Client or otheran authorized entity(for example,- such as a configuration managementserver)server or a device - pushes a profile change toProfile data tothe PDS.3.3. Data Model and Profile Types As outlined previously, this framework defines three specific Profile Types. Additional extended profiles may also be defined. The Profile Types specified in this framework are: Local Network Profile: Contains configuration data related to the Local Network to which a Client is directly connected, as required for the Client to operate effectively in that network. It is expected to be provided by a PDS in the Local Network (or proxied in some way). Device Profile: Contains configuration data related to a specific Client, required for operation in the Service Provider's environment. It is expected to be provided by the Service Provider responsible for configuring the Client. User Profile: Contains configuration data related to the specific User, as required to reflect that User's preferences and the particular services subscribed to. It is expected to be provided by Service Provider(s) responsible for maintaining the User's configuration data. To function effectively, the Client should obtain all of the necessary Profiles. Since each profile may potentially be served by a different source and the Client has no way of ascertaining that in advance, the framework requires the Client to discover the PDS sources independently and request the corresponding Profiles from each individually.4. Use Cases This section provides a small - non-comprehensive - set of representative use cases to further illustrate how this Framework can be utilized in SIP deployments. The first use case is simplistic in nature, where as the second is relatively complex. The use cases illustrate the effectiveness of the framework in either scenario. For Security Considerations please refer to Section 9. 4.1.Client with different Data and SIP Service ProvidersSimple Deployment Scenario Description: Consider auser who obtains data (broadband) and SIP Services from two different Service Providers. Fordeployment scenario (for example, auser obtaining SIP services fromsmall private enterprise) where a single entity enables the local network, manages deployed devices and provides SIPService Provider, via data connectivity provided throughservices. The devices never connect outside the local network and are each pre-configured with aWiFi hotspot or hotel network.single user. The following assumptions apply: oForThe device profile data contains all thesake of simplicity, the Client is assumed to be pre- configured with a) the domain name of the SIP Service Provider, b) the ability to generate a Client identifier (such as, based on MAC address) that can be used to requestinformation necessary for the deviceprofile, and b) a user identity which can be usedtorequestparticipate in theuser profilelocal network and obtain services o TheClientdevice is pre-configured to only requestlocal-network, Client and user profiles - in that order - to obtain information related to the local-network, itself andthepre-configured userdevice profile o Theprofile data provided upon request are based on data models that are comprehenisble by the Client, i.e. the Client understands the data models used for the creation ofenrollment notification contains the profile data (profile content retrieval is not required) The following diagram illustrates this use case and highlights the communications relevant to the framework specified in this document.+-----------------++----------------------+ +--------+ |Data ServiceLocal Network, Device| | Device | |& SIP ServiceProvider | | Client | | Provider | | |Provider| |(SIP UA)| | || SIP PDS PDS |+--------+ | DHCP PDS || PROXY (Client) (User)| +-----------------++----------------------+ | | || | |(A)|<====|<============== DHCP===>| | | | | | | |=============>| | | | | | | || SUBSCRIBE/NOTIFY | | | |(B)|<=== local-network ===>| ||<=========== Profile Enrollment ============>| | | Profile data |profile| is modified |<<Profile Retrieval>>| via "Profile |SUBSCRIBE/NOTIFY| Change Operation" | | (C)|<========= device profile ========>|<=====>| | | | | | | <<Profile Retrieval>> | | | SUBSCRIBE/NOTIFY ||<============ Profile Change ================| |(D) |<========== user profile ========>|<============>|Notification | | | |<<Profile Retrieval>>| The following is an explanation of the interactions in the diagram. (A) Upon initialization, theClientdevice obtains IP configuration parameters(IP address, DNS)using DHCP(as an example)(B) TheClient proceeds to request the 'local-network'device performs ProfileType. The PDS in the local network responds, allowingEnrollment for theClient to retrievedevice profile; thelocal-networkdevice profile data is contained in the enrollment notification (C)The Client then proceedsDue torequesta modification of the'device'device profile, a ProfileType using the pre-configured SIP Service Provider's domain name. This requestChange Notification isreceived by a SIP Proxy insent across to theSIP Service Provider's network. The request is then proxied to a relevant PDS within its network. The PDS responds to the request and provides profile retrieval information. The Client retrieves the Device Profile (this can contain information such as enabling or disabling usage, based on the subscription status) (D) The Client then proceeds to request the 'User' Profile Type for the pre-configured User. This message is proxied to the same or different PDS (diagram assumes the latter) which responds with the profile retrieval information. The Client retrieves the User profile (this can contain information such as service profiles to be retrieved, based on the subscription). The Client then starts providing services. 4.2. Clients supporting multiple users from differentdevice, along with the modified profile 4.2. Devices supporting multiple users from different Service Providers Description: Consider a singleClientdevice (for example, Kiosk at an airport) that allows for multiple users to obtain services from a list of pre-configured SIP Service Providers. The following assumptions apply: oThe Client is provided and managed by SIP ServiceProviderA. ItA isnot pre-configured with any User Identities, but offers an interactive User Interface to enter Service Providerthe Device andUser information o SIP ServiceLocal Network ProviderA providesfor thelocal network connectivity, 'local-network'device, and'device' profiles fortheClient. TheSIP Service Provideralso provides 'user' profilesforexisting subscribers o SIP Serviceuser A; Provider Bprovides SIP services and has pre- existing agreements withis the SIP Service ProviderA. This Service Provider also provides 'user' profilesforexisting subscribersuser B o Profile enrollment always results in content indirection information requiring profile content retrieval The following diagram illustrates the use case and highlights the communications relevant to the framework specified in this document. User User A B +----------------------+ +----------------------+ +--------+ |SIP ServiceProvider | |SIP ServiceProvider | |ClientDevice | | A | | B | |(SIP UA)| | | | | +--------+ | DHCP PROXY PDS | | PROXY PDS | +----------------------+ +----------------------+ | | | | | | (A) |<====DHCP====>| | | | | | | | | | | | | | | |SUBSCRIBE/NOTIFYProfile Enrollment | | | | (B) |<local-network profile>|<====>| | | | | <<ProfileRetrieval>>content retrieval>> | | |SUBSCRIBE/NOTIFYProfile Enrollment | | | | (C) |<== device profile ==> |<====>| | | | | <<ProfileRetrieval>>content retrieval>> | . . . [[User Aattemptsobtains services]] |SUBSCRIBE/NOTIFYProfile Enrollment | | | | (D) |<= user profile (A) => |<====>| | | | | | | | | | <<ProfileRetrieval>>content retrieval>> . . . . [[User Battemptsobtains services]] | |SUBSCRIBE/NOTIFYProfile Enrollment | | (E) |<=========== user profile (B) ==========>|<=========>| | | | | <<ProfileRetrieval>>content retrieval>> | The following is an explanation of the interactions in the diagram. (A) Upon initialization, theClientdevice obtains IP configuration parameters(IP address, DNS)usingDHCP (B) Once local IP connectivity is established and the SIP stack initialized,DHCP. This also provides theClient proceedslocal domain information torequesthelp with local-network profile enrollment (B) The device requests profile enrollment for the'local-network' Profile Type.local network profile. It receivesa responsean enrollment notification containing content indirection information fromthe PDS in ServiceProvider A'snetwork (the local network).PDS. TheClientdevice retrieves the profile (thismay containcontains useful information such as firewall portrestrictions,restrictions and availablebandwidth etc)bandwidth) (C) TheClientdevice thenproceeds to requestrequests profile enrollment for the'device' Profile Type.device profile. It receivesa response containing the profile retrieval from the PDS in Service Provider A's network. The Client retrieves the data providedan enrollment notification resulting inthe Client Profile (this may provide data regarding Users such as the list of SIP Service Providers the Client can communicate with).device profile content retrieval. TheClientdevice initializes the User interface for services. (D) User A with a pre-existing subscription withServiceProvider A attempts communication via theUseruser Interface.This results in a prompt - and responses - for identification and authentication.TheClientdevice uses theprovideduser supplied information (including any credential information) andcommunicates with Service Provider A. Once authenticatedrequests profile enrollment for user A's profile. Successful enrollment andauthorized, it proceeds to request the 'User' Profile Type. The PDS responds with theprofile content retrievalinformation. The Client providesresults in servicesto Userfor user A. (E) At a different point in time,Useruser B with a pre-existing subscription withServiceProvider B attempts communication via theUseruser Interface.This results in a prompt -It enrolls andresponses - for identificationretreives user B's profile andauthentication. Since Service Provider B isthis results inthe list of approved Service Provider, the Client uses the provided information and communicates with Service Provider B. Once authenticated and authorized, it proceeds to request the 'User' Profile Type. The PDS responds with the profile retrieval information. The Client providesservicesto User B. It is to be noted that this Client may allowforexclusive or simultaneous access to both Users.user B. 5. Profile Delivery Framework This section details the framework requirements. The Profile Life Cycle (introduced in Section 3), is examined in further detail, with requirements that apply to theClientdevice and the PDS. Unless explicitly enhanced or indicated by an implementing specification, theClientdevice and the PDS MUST follow the Profile Life Cycle requirements stated in this section for all supportedProfile Types.profile types. A high-level representation of the framework is shown in the following state diagram. Each of the specifiedProfile Typesprofile types is retrieved individually, in the specified order (see below), until all needed Profiles have been received.For each retrieved Profile, the Client then awaits any Change Notifications--------------- /ClientDevice \ \ Initialization/ --------------- | | Completes IP initialization; | Initializes SIP stack | V --------------YES ---------------________\ / Allprofiles?\_____\ | Await Change |profiles?\ | / \ retrieved? // | Notifications || -----------------------------| | | | NO; attempt | | Profile Request | | in specified order | | | V | ------------ ___________/ Profile \ \ Life Cycle / ------------ Framework state diagram The Profile Life Cycle,withinfor eachProfile Type,profile, is illustratedfurther asin thestatediagram below. -------------All methods -------- ________\{ Device enrolls / Profile \............\ / Error \ | /...{ and obtains \DiscoveryEnrollment /exhausted / \Handling/ |{ enrollment ---------------------{ notification | | SUCCESS | | ...PDS... V ...DEVICE... __________________________________ |Try|Send request|alternate|for ProfileActive |method(s)Subscription? |Enrollment(i.e, not a one | time fetch) | | | |VYES |FAILURE ------------ |__________/| | V V -------------- / Profile Change \^__________________\ Content \EnrollmentNotification /^ ------------ | |/ Indirection? -------------- |FAILURE^ | | | YES | SUCCESS | | V| Timeout ------------- _________-------------- ---------------- / Profile\ \ Notification/ ------------- | | |SUCCESS | V ------- Failure ---------Change\ / Profile Content \_________\ / Error\\Retrieval/Operation / \Handling/ ------- --------- . . If allowed . by ProfileRetrieval------ . Framework (Client) -- V ------ \ ------------- /Profile Change\ \ Upload / ----------/------------- {Authorized}-- { Entity } ------------------------- ----------------- The Profile Life Cycle is initiated when theClient starts the 'Profile Discovery' process for a particular Profile Type. Discovery leads to transmission of adevice transmits an enrollment request for'Profile Enrollment'. Successful enrollment leads to 'Profile Notification'. Successful initial notificationa specific profile. If this is accepted, it results in'Profile Retrieval' (either as data within thean enrollment notification that contains the profile data orusingprofile contentindirection). 'Profile Change Upload' can be initiated by any authorized entity (examples include Clients and administrative interfaces). 'Profile Discovery' and 'Profile Enrollment' are closely coupled. Failure to enroll (for example, no response is received forindirection information. Unless theSUBSCRIBE)enrollment request indicates a one-time profile request, it also results inalternate 'Profile Discovery' methods until success is achieved or all the methods are exhausted (resulting in error handling). Simiarly,enrollment for profile change notifications. If theinitial 'Profile Notification'profile isclosely coupled to enrollment. Failure to receivemodified at any point in time, theinitialprofile change notificationalso results in alternate discovery methods. 'Profile Retrieval'isaccomplished using the contents of the Profile Notification. This can either containtransmitted to the device. Notifications due to profiledataenrollment orachange operation may result in content indirectionmethodin which case the device uses profile content retrieval toachieve it.obtain the profile data. The Profile Life Cycle is the same for all theProfile Types,profile types, but there are different requirements in each step based on theProfile Types.profile types. This framework defines threeProfile Typesprofile types and an order that MUST be followed by theClientdevice in requesting them (when it retrieves two or more of the definedProfile Types),profile types), as follows: o local-network o device o user The sub-sections that follow specify the Profile Life Cycle details, with specific requirements based on eachProfile Type.profile type. 5.1. ProfileDiscoveryEnrollment The first step to obtaining a profile is PDSDiscovery.Enrollment. This isaccomplishedinitiated by the device and involves: o creating a profile enrollment subscriptionusingo transmitting a profile enrollment request o receiving a profile enrollment notification The processes are interlinked and retries encompass all three phases. For example, if theEvent Package describedenrollment request does not result inSection 6, and preparing for Profile Enrollment.a profile enrollment notification, the device is required to retry alternate profile enrollment subscription creation options. Only when all the enrollment subscription creation options are exhausted does the device assume that the profile enrollment has failed. The processes themselves are illustrated in the following sub-sections. 5.1.1. Creation of Enrollment Subscription EachProfile Typeprofile type requires its own subscription and based on the entity requesting it, presents certain unique requirements (for example, theClientdevice identifier is provided for theDevice Profile Typedevice profile type where as theUseruser identifier is provided for theUser Profile Type).user profile type). Further, theProfile Typesprofile types are aimed at different PDSs and hence are identified differently (for example, the local-network is identified by the local domain name where as the Service Provider is identified based on the Service Provider's domain name). Some of this information can be obtained in multiple ways (such as local domain information that can be configured statically or dynamically) and theClientdevice may have to try different information sources to obtain the required information (for example, dynamic configuration can override statically configured information). Based on these considerations, the framework defines different rules for obtaining and presenting the information for eachProfile Type.profile type. Additionally, when more than one information source is possible for the information, it is presented as well. This is highlighted in the following sub-sections.5.1.1.5.1.1.1. SIP SUBSCRIBE for the Local-NetworkProfile Typeprofile type Before attempting to create a SIP SUBSCRIBE requesting theLocal- Network Profile,local- network profile, theClientdevice MUST have established local network connectivity. It MUST also have knowledge of the local network domain either via static configuration or dynamic discovery(using DHCP [RFC2131], option 15 [RFC2132]).via DHCPv4 ([RFC2131]) or DHCPv6 ([RFC3315]). The following requirements apply: o the user part of the Request URI MUST NOT be provided. The host and port part of the Request URI MUST be set to thelocal network domain o the user partconcatenation ofthe "From" field MUST be the Identifier that the Client will use to request the 'device' Profile Type o the host"sipuaconfig" andport part of the "From" field MUST be set tothe local network domain o a user AOR, if known to theClientdevice MUST beprovided inused to populate the"network-user" event header parameter,"From" field, unless privacy requirements prohibit its use (this is useful if the user has privileges in the local network beyond those of the default user) o if a user AOR is not known, the user portion of the "From" field MUST be set to "anonymous"; the host and port portion of the Request URI MUST be set to the concatenation of "sipuaconfig" and the local network domain o the "device-id" event header parameter MUST be set to the device identifier that the device will use to request the device profile For example: If theClientdevice requested and received the local domain name via DHCP to be: airport.example.net, then the Local-Network Profile SUBSCRIBE Request URI would look like:sip:airport.example.netsip:sipuaconfig.airport.example.net The Event header would look like the following if theClientdevice decided to providesip:alice@example.comMAC%3a00DF1E004CD0@airport.example.net as theuser's AOR.device identifier. (Alice may have a prior arrangement with the local network operator giving her specialprivileges.):privileges.) Event: ua-profile;profile-type=local-network;network-user="sip:alice@example.com"device-id="sip:MAC%3a00DF1E004CD0@airport.example.net" TheLocal-Network Profilelocal-network profile SUBSCRIBE Request URI does not have a user part so that the URI is distinct between the "local" and "device" URIs when the domain is the same for the two. This provides a means of routing to the appropriate PDS in domains where they are distinct servers. The From fielduses the device ID inis populated with the userpart ofAOR, if available. This allows the local networkRequest URI so that every device inprovider to propagate user-specific profile data, if available. The "device-id" event header parameter is set to thenetwork has a unique and constant From field.device identifier. Even though everyclientdevice may get the same (or similar) Local-Network Profile, the uniqueness of theFrom field"device-id" event header provides an important capability. Having unique From fields allows the management of the local network to trackuser agentsdevices present in the network and consequently also manage resources such as bandwidth and port allocation.For example: If the Client requested and received the local domain name via DHCP to be: airport.example.net and the device ID is: MAC: 00DF1E004CD0, the From field would contain: sip:MAC%3a00DF1E004CD0@airport.example.net 5.1.2.5.1.1.2. SIP SUBSCRIBE for the Device Profile Type TheDevice Profile Typedevice profile type allows the Service Provider managing aClientdevice to provideClient-specificdevice-specific configuration information. To enable this, the Request URI needs to identify theClientdevice and the PDS domain within which it is recognizable. Accordingly, this Framework presents the following requirements for the formation of a Subscription Request URI to request the "device"Profile Typeprofile type o the user portion of the Request URI MUST be set to a uniqueClientdevice Identifier o the host and port portion of the Request URI MUST be set to the PDS domain The following sub-sections explain identification of - and the requirements related to - theClientdevice Identifier and the PDS domain discovery.5.1.2.1. Client5.1.1.2.1. Device Identifier TheClientdevice profile could be specific to eachClientdevice in a SIP deployment (for example, vendor/model) or shared acrossClientdevice types (for example, based on services and service tiers). Further, the sameClientdevice might be provided different configuration profiles based on deployment models.ClientDevice Identifiers play a significant role in ensuring delivery of the correct profile and hence need to be unique within a PDS domain to support the various deployment models. This Framework requires thatClientdevice Identifiers MUST be unique and persistent over the lifetime of aClient. Clientdevice. Device Identifier representations auto-generated byClientsdevices SHOULD be based on MAC address or UUID ([RFC4122]) based representations. AClientdevice may use alternateClientdevice identifiers (for example, SIP URIs) obtained via pre-configuration or dynamic configuration (for example,Clientdevice profile). If a MAC address is used, the following requirements apply: o theClientdevice identifier MUST be formatted as the characters "MAC:" followed by a twelve digit hexadecimal upper case representation of the MAC address to form a proper URN ([RFC2141]). The MAC address representation MUST NOT include visual separators such as colons and whitespaces. The representation is denoted using the following ABNF syntax mac-ident = MAC ":" 12UHEX MAC = %x4d.41.43 ; MAC in caps UHEX = DIGIT / %x41-46 ; uppercase A-F o the MAC address MUST only be used to represent a singleClient.device. It MUST NOT be used if more than oneClientdevice can potentially use the same MAC Address (for example, multiple softwareClientsentities on a single platform). In such cases, the UUID representation SHOULD be used If a UUID is used, the following requirements MUST apply: o the same approach to defining a user agent Instance ID as [RFC4122] MUST be used o when the URN is used as the user part of the URI, it MUST be URL escaped The colon (":") is not a legal character (without being escaped) in the user part of an addr-spec ([RFC4122]). For example the instance ID: urn:uuid:f81d4fae-7ced-11d0-a765-00a0c91e6bf6@example.com would be escaped to look as follows in a URI: sip:urn%3auuid%3af81d4fae-7ced-11d0-a765-00a0c91e6bf6@ example.com The ABNF for the UUID representation is provided in [RFC4122]5.1.2.2.5.1.1.2.2. PDS Domain Discovery AClientdevice needs to identify the PDS domain to form the host and port part of the Request URI. Ideally, this information should be obtained via a single method. However, support for various deployment models implies multipleClientdevice environments (for example, residential routers, enterprise LANs, WLANhotspots,hotspots and dialupmodem etc)modem) and presents hurdles to specifying a single method (for example, if aClientdevice is always in the SIP Service Provider's network one could use DHCP). To accommodate multiple deployment scenarios, the framework specified in this document presents multiple approaches.ClientsDevices MUST follow the procedures specified below in the order presented, unless exceptions are made byClientdevice manufacturers orServiceDevice Providers who may provide an option for the user to choose the order (to suit specific deployment models, for example). 1. Service Provider pre-configuration TheClientdevice MAY be pre-configured with information that can be utilized to identify the host and port of the Request URI. The information can be provided - as examples - when theClientdevice is manufactured, by using Service Provider entities (flash card, SIM card) or via a Service Provider specific method (for example, information or methods that lead to self subscription). If theClientdevice is specified to utilize this approach, it MUST attempt to do so before trying other methods. The details of how this is accomplished are beyond the scope of this document. 2. IP Configuration If pre-configuration is not an option, or not available, IP configuration MUST be utilized to try and obtain information that can help with identification of the host and port for the Request URI. The framework defines the following methods within this procedure to accomplish this.Clientsdevice MUST follow the methods defined, in the order specified, i.e. if the first option cannot be accomplished or results in a failure, then next method is tried. Failure of a specific method is indicated when theClientdevice cannot successfully complete Profile Enrollment. 2a. DHCP option120: Clientsfor SIP server: Devices that support DHCP MUST attempt to obtain the host and port of the outbound proxy during the DHCP process, using theSIPDHCP option120for SIP servers defined in [RFC3361] or [RFC3319] (for IPv4 and IPv6 respectively), and use these as the host and port part of the request URI. For example, a MAC basedClient Identifierdevice identifier with a DHCP SIP servers option120indicating example.com, the Request URI would be constructed as sip:MAC%3aABC123EFD456@example.com 2b. Local IP Network Domain: -Clientsdevices that support DHCP MUST attempt to obtain the local IP network domain during the DHCP process, using DHCP option 15 and use these as the host and port part of the request URI using the technique specificed in [RFC3263] + For example, a MAC basedClient Identifierdevices identifier with a DHCP option 15 indicating local.example.com, the Request URI would be constructed as sip:MAC%3aABC123EFD456@local.example.com - If the local IP network domain is available (previous method), but the usage of the local IP Network domain results in a failure, theClientdevice MUST use the local IP network domain, prefixing it using the label "sipuaconfig." + For example, a MAC basedClientdevice Identifier with a DHCP option 15 indicating local.example.com, the Request URI would be constructed as sip:MAC%3aABC123EFD456@sipuaconfig.local.example.com 3. Manual If pre-configuration and IP Configuration are not options or result in failures, theClientdevice SHOULD provide a means for the user to present information that may help with the retrieval process. Exceptions to this requirement MAY includeClientsdevices with no user interface appropriate for such entry. This framework provides the following alternatives which can be considered individually or together, in any order.ServiceDevice Provider PDS information: The user SHOULD be allowed to present the host and port information which can help with the creation of the Subscription URI to locate a PDS capable of providing the profile.ServiceDevice Provider Configuration Server information The user MAY be allowed to present information pertaining to a configuration server that provides theDevice Profile,device profile, not using a PDS as defined in this framework. This framework specifies one such possible process in Section5.6.1. 5.1.3.5.5.1. 5.1.1.3. SIP SUBSCRIBE for the User Profile Type TheUser Profileuser profile allows the responsible SIP Service Provider to provide user-specific configuration. This is based on theUser's Identityuser's identity that is usually known in the network (for example, associated with a subscription). Similar to the profiles provided toClients,devices, the content and propagation ofUseruser Profiles may partake differently, based on deployment scenarios (for example, users belonging to the same subscription might - or might not - be provided the same profile). However, eachUseruser is uniquely identified in a SIP Service Provider's network using an Address Of Record (AOR).ClientsDevices implementing this framework MUST use theUser'suser's AOR to populate the Request URI. AClientdevice MAY obtain theUser'suser's AOR using various methods such as pre- configuration, via theDevice Profiledevice profile or dynamically via aUseruser Interface.5.1.4.5.1.1.4. Caching of SIP Subscription URIs Creation of Subscription URIs is vital for successful ProfileEnrollment, required for Profile Notification and ultimately Profile Retrieval. Further - unlikeEnrollment. Unlike theUseruser Profile - Local-Network andDevice Profilesdevice profiles are expected to be requested based on discovered information (for example, domain name discovered via DHCP). TheseProfile Typesprofile types have different goals and hence, caching of the Subscription URI should be carefully considered. The Local-NetworkProfile Typeprofile type is aimed at obtaining information from the local network. The local network can change acrossClientdevice initializations (for example,Useruser moves theClientdevice from a home network to a workplace LAN). Thus, theClientdevice SHOULD NOT remember local-network profile subscription URIs across initializations. TheClientdevice SHOULD re-create the Subscription URI every time it moves to a new network or gets re-initialized. Exceptions may be cases where theClientdevice can unambiguously determine changes to the local network. TheDevice Profile Typedevice profile type is aimed at obtaining information from the SIP Service Provider managing theClient.device. Once established, the Service Provider does not change often (an example of an exception would be the re-use ofClientsdevices across Service Providers). However, if the discovery process is used, theClientdevice can only be sure of having reached the Service Provider upon successful Profile Enrollment and Profile Notification. Thus, theClientdevice SHOULD cache the Subscription URI for theDevice Profile.device profile. When cached, theClientdevice should use the cached Subscription URI upon a reset. Exceptions include cases where theClientdevice identifier has changed (for example, new network card with a new MAC address), Service Provider information has changed (for example, user initiates change) or theClientdevice cannot obtain its profile using the Subscription URI.ClientsDevices SHOULD NOT cache the Subscription URI for theDevice Profile Typedevice profile type until successful Profile Notification. The reason for this is that a PDS may send 202 responses to SUBSCRIBE requests and NOTIFY responses to unknownClientsdevices (see Section 6.6) with no profile data or URIs. Thus, successful Profile Notification is the only sure way to know that the Subscription URI is valid.5.2.5.1.2. Profile EnrollmentClients implementing the frameworkRequest Transmission A device requesting a profile type specified in this documentare required to perform Profile Enrollment prior to Profile Retrieval (the only exception- and isnotedsuccessful inSection 5.6.1). Enrollment forforming aspecific profile happens once the specificSubscription URIis formed and is accomplished using the Event Package specified. Thus, a Client requesting a Profile Type specified in this document - and is successful in forming a Subscription URI - MUST enroll- MUST enroll using the event package defined, and as specified, in this framework (see Section 6) . The following requirements apply: o theClientdevice MUST cater to the Event Package requirements specified in Section 6.2 (for example, indicate theProfile Typeprofile type being requested in the profile-type parameter) o theClientdevice MUST use the Subscription URI pertaining to theProfile Typeprofile type being requested, as specified in Section 5.1 The SIP infrastructure receiving such requests is expected to relay and process profile enrollment requests. When a Profile Enrollment request is received by a PDS, it SHOULD accept and respond to any profile requests. Exceptions are when Service Provider policy prevents such a response (for example, requesting entity is unknown). Successful Profile Enrollment involves the following o Acceptance of the SUBSCRIBE request by a PDS (indicated via a 200 response) o Receipt of an initial Profile Notification within the timeouts as specified in [RFC3265] AClientdevice SHOULD follow suitable BackOff and Retry mechanisms if a successful Profile Enrollment does not happen within the expected period.5.3.5.1.3. Profile Enrollment Notification Successful Profile Enrollmentleads to Profile Notification.is indicated by an enrollment notification. Thisserves two purposesprovides either a)initialthe profile contents b) contentfollowing successfulindirection information. If content indirection information is provided, the device retrieves the profile using ProfileEnrollment and b) notification toContent Retrieval. If theClient of modifications toprofilecontent.contents are provided, the following requirements hold good: o the device MUST make the new profiles effective within the specified timeframe, as described in Section 6.2 o the device SHOULD cache (i.e. store persistently) the contents of retrieved profiles, until overridden by subsequent Profile Change Notifications (this avoids situations where a PDS is unavailable, leaving the device without required configuration) Failure to receive the initial NOTIFY following a successful enrollment MUST be treated the same as a failed enrollment.WheneverIn such aprofile is changed,scenario, thePDSdevice MUSTNOTIFYretry using alternate methods for creation of the enrollment subscription and transmit an enrollment request. If allClients currently subscribedthe enrollment subscription creation have been exhausted, the device MUST treat it as a failure to obtain thechanged profile.profile and take appropriate measures. For NOTIFY content please refer to Section 6.5.5.4.5.2. Profile Content Retrieval Upon successful ProfileEnrollment and Profile Notification,Enrollment, theClientdevice can retrieve the documents pertaining to the requested profile directly or via the URI(s) provided in the NOTIFY request as specified in Section 6.5.The following requirements hold good: o the PDS SHOULD secure the content of the profiles using oneProfile Content Retrieval protocols and frameworks are out of scope for this specification. 5.3. Profile Change Operation Configuration Profiles can change over time. Modifications can be initiated by various entities (for example, via thetechniques described in Section 9 o the Client MUST make the new profiles effective within the specified timeframe, as described in Section 6.2 o if content indirection is used, the Client SHOULD verify that it has the latest profile content using the "hash" parameter defined in [RFC4483] o the Client SHOULD cache (i.e. store persistently) the contents of retrieved profiles, until overridden by subsequent Profile Notifications (this avoids situations where a PDS is unavailable, leaving the Client without required configuration) 5.5. Profile Change Upload Configuration Profiles can change over time. This can be initiated by various entities (for example, via the Client, back-office components,device, back- office components and end-user web interfacesintofor configurationservers, etc)servers) and for various reasons (such as, change in user preferences, modifications to services, enterprise-imposed common features or restrictions). This framework allows for such changes to be communicated to the PDS, using the term Profile ChangeUpload.Operation. Any changes to a Profile as a result of Profile ChangeUploadOperation MUST result in a Profile Notification to all enrolledclientsdevices for that Profile, if any. Definition of specific mechanisms for Profile ChangeUploadOperation are out of scope of this document.5.6.5.4. Profile Change Notification Whenever a profile is changed, a PDS compliant with this framework MUST NOTIFY all the devices currently subscribed to the profile under consideration. This process is termed Profile Change Notification. For NOTIFY content please refer to Section 6.5. 5.5. Additional Considerations This section provides a special case for retrieval of theDevice Profiledevice profile and highlights considerations and requirements on external entities such as Profile Data Frameworks.5.6.1.5.5.1. Manual retrieval of the Device Profile At a minimum, aClientdevice requires theDevice Profiledevice profile to be able to function effectively. However, the methods specified in this documentmanymay fail to provide aClientdevice with a profile. To illustrate with an example, consider the case of aClientdevice that finds itself behind a local network which does not provide information about DNS servers in the network (for example, misconfigured home network). In such cases, it would be beneficial to employ an alternative means to obtain the profile information (for example, resolvable DNS Servers could be part of theClientdevice profile). While this specification recommends that such a method be made available, it also specifies one such option using HTTP that is described in this sub-section.Clientsdevices expected to encounter scenarios whereClientpropogation of the device profileretrievalcan be hindered may employ the specified - or any alternative - process. The method being described involves theClientdevice to utilize a HTTPS URI (and any required credentials) based on either pre-configuration or manual entry by theUseruser (in cases where such an interface is possible). This can lead to the retrieval of theDevice Profiledevice profile which may contain the properties for the SUBSCRIBE Request URI and credentials for Profile Enrollment and Profile Notification. This approach bootstraps the process in a different step in the cycle, but uses the same framework. Further, this document defines a new HTTP request header "Event". The syntax of the HTTP Event header is the same as the SIP Event header defined in this document. Similar to the SIP Event header the purpose of the HTTP Event header is to define the content of the state information to be retrieved. In particular, the state information is theDevice, Userdevice, user orLocal-Network Profilelocal-network profile for theClient.device. The SIP Event header parameters for this event package ("profile-type", "vendor", "model", "version") are also mandatory for the HTTP Event header as they are used to provide information as to what profile type is requested along with information about the device which may impact the contents of theprofile.Whenprofile. When theClientdevice starts with retrieval of the profile via HTTPS (instead of a SIP SUBSCRIBE to the event package), the device MUST provide the Event header defined.5.6.2. Client5.5.2. Device Types The examples in this framework tend to associateClientsdevices with entities that are accessible to end-users. However, this is not necessarily the only type ofClientdevice that can utilize the specified Framework.Clientsdevices can be entities such asUseruser Interfaces (that allow forClientdevice Configuration), entities in the network that do not directly communicate with anyUsersusers (for example, Service Provider deployed gateways) or elements in the Service Provider's network (for example, SIP servers).5.6.3.5.5.3. Profile Data This framework does not specify the contents for anyProfile Type.profile type. Follow-on standardization activities can address profile contents. However, it makes the following assumptions and recommendations: o When theClientdevice receives multiple profiles, the contents of eachProfile Typeprofile type will only contain data relevant to the entity it represents. As an example, consider aClientdevice that obtains all the defined profiles. Information pertaining to the local network is contained in the 'local-network' profile and not the'user' profile. This does not preclude relevant data about a different entity from being included in aProfile Type,profile type, for example, the 'device'Profile Typeprofile type may contain information about theUsersusers allowed to access services via theClient.device. A profile may also contain starting information to obtain subsequent Profiles o Data overlap SHOULD be avoided acrossProfile Types,profile types, unless necessary. If data overlap is present, prioritization of the data is left to data definitions. As an example, theDevice Profiledevice profile may contain the list of codecs to be used by theClientdevice and theUseruser Profile (for aUseruser on theClient)device) may contain the codecs preferred by theUser.user. Thus, the same data (usable codecs) is present in two profiles. However, the data definitions may indicate that to function effectively, any codec chosen for communication needs to be present in both the profiles.5.6.4.5.5.4. Profile Data Frameworks This framework specified in this document does not address profile data representation, storage or retrieval protocols. It assumes that the PDS has a PCC based on existing or other Profile Data Frameworks, for example, XCAP ([I-D.ietf-simple-xcap]). While it does not impose vast constraints on any such framework, it does allow for the propagation of profile content to PDS (specifically the PCC). Thus, Profile Data or Retrieval frameworks used in conjunction with this framework MAY consider techniques for propagating incremental, atomic changes to the PDS. For example, a means for propagating changes to a PDS is defined in XCAP ([I-D.ietf-simple-xcap]).5.6.5.5.5.5. Additional Profile Types This document specifies three profile types: local-network, device and user. However, there may be use cases for additional profile types. For example,Profile Typesprofile types for application specific profile data. Definition of such additionalProfile Typesprofile types is not prohibited, but considered out of scope for this document.6. Event Package Definition5.5.6. Deployment considerations The frameworkspecifieddefined in this documentproposeswas designed to address various deployment considerations, some of which are highlighted below. Provider relationships: o The local network provider andspecifies a newthe SIPEvent Package as allowed by [RFC3265]. The purpose is to allow for Clients to subscribe to specific Profile Typesservice provider can often be different entities, with no administrative or business relationship with each other; o There may be multiple SIP service providers involved, one for each service that a user subscribes to (telephony service, instant messaging, etc.); this Framework does not specify explicit behavior in such a scenario, but it does not prohibit its usage either o Each user accessing services via the same device may subscribe to different sets of services, from different Service Providers; User-device relationship: o The relationship between devices and users can be many-to-many (for example, a particular device may allow for many users to obtain subscription services through it, and individual users may have access to multiple devices); o Each user may have different preferences for use of services, and presentation of those services in the device user interface; o Each user may have different personal information applicable to use of the device, either as related to particular services, or independent of them. 6. Event Package Definition The framework specified in this document proposes and specifies a new SIP Event Package as allowed by [RFC3265]. The purpose is to allow for devices to subscribe to specific profile types with PDSs and for the PDSs to notify theClientsdevices with - or pointers to - profile data. The requirements specified in [RFC3265] apply to this package. The following sub-sections specify the Event Package description and the associated requirements. The framework requirements are defined in Section 5. 6.1. Event Package Name The name of this package is "ua-profile". This value appears in the Event header field present in SUBSCRIBE and NOTIFY requests for this package as defined in [RFC3265]. 6.2. Event Package Parameters This package defines the following new parameters for the event header: "profile-type", "vendor", "model", "version","effective-by""effective-by", "device-id" and "network-user". The following rules apply: o All the new parameters, with the exception of the "effective-by" parameter MUST only be used in SUBSCRIBE requests and ignored if they appear in NOTIFY requests o The "effective-by" parameter is for use in NOTIFY requests only and MUST be ignored if it appears in SUBSCRIBE requests The semantics of these new parameters are specified in the following sub-sections. 6.2.1. profile-type The "profile-type" parameter is used to indicate the token name of theProfile Typeprofile type the user agent wishes to obtain data or URIs for and to be notified of subsequent changes. This document defines three logical types of profiles and their token names. They are as follows: local-network Specifying "local-network" type profile indicates the desire for profile data (URI when content indirection is used) specific to the local network. device Specifying "device" type profile(s) indicates the desire for the profile data (URI when content indirection is used) and change notification of the contents of the profile that is specific to the device or user agent. user Specifying "user" type profile indicates the desire for the profile data (URI when content indirection is used) and change notification of the profile content for the user. The "profile-type" is identified is identified in the Event header parameter: profile-type. A separate SUBSCRIBE dialog is used for eachProfile Type.profile type. TheProfile Typeprofile type associated with the dialog can then be used to infer whichProfile Typeprofile type changed and is contained in the NOTIFY or content indirection URI. The Accept header of the SUBSCRIBE request MUST include the MIME types for all profile content types for which the subscribing user agent wishes to retrieve profiles or receive change notifications. In the following syntax definition using ABNF, EQUAL and token are defined in [RFC3261]. It is to be noted that additionalProfile Typesprofile types may be defined in subsequent documents. Profile-type = "profile-type" EQUAL profile-value profile-value = profile-types / token profile-types = "device" / "user" / "local-network" The "device", "user" or "local-network" token in the profile-type parameter may represent a class or set of profile properties. Follow-on standards defining specific profile contents may find it desirable to define additional tokens for the profile-type parameter. Also additional content types may be defined along with the profile formats that can be used in the Accept header of the SUBSCRIBE to filter or indicate what data sets of the profile are desired. 6.2.2. vendor, model and version The "vendor", "model" and "version" parameter values are tokens specified by the implementer of the user agent. These parameters MUST be provided in the SUBSCRIBE request for allProfile Types.profile types. The implementer SHOULD use their DNS domain name (for example, example.com) as the value of the "vendor" parameter so that it is known to be unique. These parameters are useful to the PDS to affect the profiles provided. In some scenarios it is desirable to provide different profiles based upon these parameters. For example, feature property X in a profile may work differently on two versions of the same user agent. This gives the PDS the ability to compensate for or take advantage of the differences. In the following ABNF defining the syntax, EQUAL and quoted-string are defined in [RFC3261]. Vendor = "vendor" EQUAL quoted-string Model = "model" EQUAL quoted-string Version = "version" EQUAL quoted-string 6.2.3.network-userdevice-id The"network-user""device-id" parameter MUST be set when subscribing for "local- network"profiles if it is known, unless the Client is provisioned to preserve privacy within the local network.profiles. Thisallowsidentifies theClient to indicate a user who may have special privileges indevice requesting thelocallocal- networkthat impactprofile. If thecontentsvalue of the"local-network" profile. It"profile-type" parameter is not "local-network", the "device-id" parameter has no defined meaning and is ignored. In the following ABNF, EQUAL, LDQUOT, RDQUOT and addr-spec are defined in [RFC3261]. Device-Id = "device-id" EQUAL LDQUOT addr-spec RDQUOT 6.2.4. network-user The "network-user" parameter MAYalsobe provided in a subscription for a "device" profile. In such cases theClientdevice is requesting the PDS to recognize the indicated user as the default user for itself.The Notifier SHOULD authenticate the subscriber to verify the resource identifier in the "network-user" parameter, if the profile provided is specific to the user (for example, granting policies or privileges beyond those of a default user).If the value of the "profile-type" parameter is not"device" or "local-network","device", the "network-user" parameter has no defined meaning and is ignored. If the "network-user" parameter is provided in the SUBSCRIBE request, it MUST be present in the NOTIFY request as well. In the following ABNF, EQUAL, LDQUOT, RDQUOT and addr-spec are defined in [RFC3261]. Network-User = "network-user" EQUAL LDQUOT addr-spec RDQUOT6.2.4.6.2.5. effective-by parameter The "effective-by" parameter in the Event header of the NOTIFY request specifies the maximum number of seconds before the user agent must attempt to make the new profile effective. The "effective-by" parameter MAY be provided in the NOTIFY request for any of theProfile Types.profile types. A value of 0 (zero) indicates that the subscribing user agent must attempt to make the profiles effective immediately (despite possible service interruptions). This gives the PDS the power to control when the profile is effective. This may be important to resolve an emergency problem or disable a user agent immediately. The "effective-by" parameter is ignored in all messages other than the NOTIFY request. In the following ABNF, EQUAL and DIGIT are defined in [RFC3261]. Effective-By = "effective-by" EQUAL 1*DIGIT6.2.5.6.2.6. Summary of event parameters The following are example Event headers which may occur in SUBSCRIBE requests. These examples are not intended to be complete SUBSCRIBE requests. Event: ua-profile;profile-type=device; vendor="vendor.example.com";model="Z100";version="1.2.3" Event: ua-profile;profile-type="user"; vendor="premier.example.com";model="trs8000";version="5.5" The following are example Event headers which may occur in NOTIFY requests. These example headers are not intended to be complete SUBSCRIBE requests. Event: ua-profile;effective-by=0 Event: ua-profile;effective-by=3600 The following table shows the use of Event header parameters in SUBSCRIBE requests for the threeProfile Types:profile types: profile-type || device | user | local-network ============================================= vendor || m | m | m model || m | m | m version || m | m | m device-id || | | m network-user ||so | |seffective-by || | | m - mandatory s - SHOULD be provided o - optional Non-specified means that the parameter has no meaning and should be ignored. The following table shows the use of Event header parameters in NOTIFY requests for the threeProfile Types:profile types: profile-type || device | user | local-network ============================================= vendor || | | model || | | version || | | device-id || | | o network-user ||so | |seffective-by || o | o | o 6.3. SUBSCRIBE Bodies This package defines no use of the SUBSCRIBE request body. If present, it MUST be ignored. Future enhancements to the framework may specify a use for the SUBSCRIBE request body (for example,, mechanisms using etags to minimize Profile Notifications toClientsdevices with current profile versions). 6.4. Subscription Duration The duration of a subscription is specific to SIP deployments and no specific recommendation is made by this Event Package. If absent, a value of 86400 seconds is RECOMMENDED since the presence (or absence) of aClientdevice subscription is not time critical to the regular functioning of the PDS. It is to be noted that a one-time fetch of a profile can be accomplished by setting the 'Expires' parameter to a value of Zero, as specified in [RFC3265]. 6.5. NOTIFY Bodies The framework specifying the Event Package allows for the NOTIFY body to contain the profile data or a pointer to the profile data using contentdirection.indirection. The framework does not define any profile data and delegates specification of utilized MIME types Profile Data Frameworks. For profile data delivered via content indirection, the following apply: o the Content-ID MIME header, as described in [RFC4483] MUST be used for each Profile document URI o at a minimum, the "http:" and "https:" URI schemes MUST be supported; other URI schemas MAY be supported based on the Profile Data Frameworks (examples include FTP [RFC0959],TFTP [RFC3617],HTTPHTTP [RFC2616], HTTPS [RFC2818], LDAP[RFC3377],[RFC4510], XCAP [I-D.ietf-simple-xcap], XCAP-DIFF [I-D.ietf-simple-xcap-diff]) The NOTIFY body SHOULD include a MIME type specified in the 'Accept' header of the SUBSCRIBE. Further, if the Accept header of the SUBSCRIBE included the MIME type message/external-body (indicating support for content indirection) the content indirection SHOULD be used in the NOTIFY body for providing the profiles. If none are specified, the Profile Data frameworks are responsible for, and MUST specify, the MIME type to be assumed. 6.6. Notifier Processing of SUBSCRIBE Requests A successful SUBSCRIBE request results in a NOTIFY with either profile contents or a pointer to it (via Content Indirection). If the NOTIFY is expected to contain profile contents or the Notifier is unsure, the SUBSCRIBE SHOULD be either authenticated or transmitted over an integrity protected SIP communication channels. Exceptions to authenticating such SUBSCRIBEs include cases where the identity of the Subscriber is unknown and the Notifier is configured to accept such requests. The Notifier MAY also authenticate SUBSCRIBE messages even if the NOTIFY is expected to only contain a pointer to profile data. Securing data sent via Content Indirection is covered in Section 9. If theProfile Typeprofile type indicated in the "profile-type" Event header parameter is unavailable or the Notifier is configured not to provide it, the Notifier SHOULD return a 404 response to the SUBSCRIBE request. If the specific user orClientdevice is unknown, the Notifier MAY either accept or reject the subscription. When the Event header "profile-type" is "device" and the user agent has provided the user's AOR in the "network-user" parameter, the profile delivery server MAY set or change the default user associated with theClientdevice indicated in the Subscription request. However, the Notifier SHOULD authenticate the user indicated before making such a change. 6.7. Notifier Generation of NOTIFY Requests As specified in [RFC3265], the Notifier MUST always send a NOTIFY request upon accepting a subscription. If theClientdevice orUseruser is unknown and the Notifier choose to accept the subscription, the Notifier MAY either respond with profile data (for example, default profile data) or provide no profile information (i.e. no body or content indirection). If the URI in the SUBSCRIBE request is a known identity and the requested profile information is available (i.e. as specified in the profile-type parameter of the Event header), the Notifier SHOULD send a NOTIFY with profile data. Profile data MAY be sent as profile contents or via Content Indirection (if the content indirection MIME type was included in the Accept header). To allow for Content Indirection, the Subscriber MUST support the "http:" or "https:" URI schemas. If the Subscriber wishes to support alternative URI schemas it MUST be indicated in the "schemes" Contact header field parameter as defined in [RFC4483]. If the subscriber does not specify the URI scheme, the Notifier may use either "http:" or "https:". The Notifier MAY specify when the new profiles must be made effective by the Subscriber by specifying a maximum time in seconds (zero or more) in the "effective-by" event header parameter. If the SUBSCRIBE was received over an integrity protected SIP communications channel, the Notifier SHOULD send the NOTIFY over the same channel. 6.8. Subscriber Processing of NOTIFY Requests A Subscriber to this event package MUST adhere to the NOTIFY request processing behavior specified in [RFC3265]. If the Notifier indicated an effective time (using the "effective-by" Event Header parameter), it SHOULD attempt to make the profiles effective within the specified time. Exceptions include deployments that prohibit such behavior in certain cases (for example, emergency sessions are in progress). When profile data cannot be applied within the recommended timeframe and this affectsClientdevice behavior, any actions to be taken SHOULD be defined by the profile data definitions. By default, the Subscriber is RECOMMENDED to make the profiles effective as soon as possible. The Subscriber MUST always support "http:" or "https:" and be prepared to accept NOTIFY messages with those URI schemas.The subscriber MUST also be prepared to receive a NOTIFY request with no body. The subscriber MUST NOT reject the NOTIFY request with no body. The subscription dialog MUST NOT be terminated by a NOTIFY with no body. 6.9. Handling of Forked Requests This Event package allows the creation of only one dialog as a result of an initial SUBSCRIBE request as described in section 4.4.9 of [RFC3265]. It does not support the creation of multiple subscriptions using forked SUBSCRIBE requests. 6.10. Rate of Notifications The rate of notifications for the profiles in this framework is deployment specific, but expected to be infrequent. Hence, the Event Package specification does not specify a throttling or minimum period between NOTIFY requests 6.11. State Agents State agents are not applicable to this Event Package. 7. Examples This section provides examples along with sample SIP message bodies relevant to this framework. Both the examples are derived from a snapshot of Section 4.1, specifically the request for theDevice Profile.device profile. The examples are purely informative and in case of conflicts with the framework or protocols used for illustration, the latter should be deemed normative. 7.1. Example 1:ClientDevice requesting profile This example illustrates the detailed message flows between theClientdevice and the SIP Service Provider's network for requesting and retrieving the profile (the flow uses theDevice Profiledevice profile as an example). The following are assumed for this example: oClientDevice is assumed to have established local network connectivity; NAT and Firewall considerations are assumed to have been addressed by the SIP Service Provider o examples are a snapshot only and do not illustrate all the interactions between theClientdevice and the Service Provider's network (and none between the entities in the SIP Service Provider's network) o All SIP communication with the SIP Service Provider happens via a SIP Proxy o HTTP is assumed to be the Profile Data method used (any suitable alternative can be used as well) o TLS is assumed to be the protocol for securing the Profile Content Retrieval (any other suitable protocol can be employed); authentication and security requirements are not addressed The flow diagram and an explanation of the messages follow. +----------------------+ +--------+ | SIP Service Provider | |ClientDevice | | | |(SIP UA)| | SIP PDS HTTP | +--------+ | PROXY Server | | | +----------------------+ | | | | | | | | | SUBSCRIBE | | | (SReq)|--------device profile--------->| | | | |------>| | | |200 OK | | | 200 OK |<------| | (SRes)|<-------------------------------| | | | | | | | | NOTIFY| | | NOTIFY (Content Indirection)|<------| | (NTFY)|<-------------------------------| | | | 200 OK | | | (NRes)|------------------------------->|200 OK | | | |------>| | | | | | | | |<<<<<<<<<<<<< TLS establishment >>>>>>>>>>>>>| | | | HTTP Request | (XReq)|---------------------------------------------->| | | | HTTP Response | (XRes)|<----------------------------------------------| | | (SReq) theClientdevice transmits a request for the 'device' profile using the SIP SUBSCRIBE utilizing the Event Package specified in this framework. * Note: Some of the header fields (for example, Event, via) are continued on a separate line due to format constraints of this document SUBSCRIBE sip:MAC%3a000000000000@sip.example.net SIP/2.0 Event: ua-profile;profile-type=device;vendor="vendor.example.net"; model="Z100";version="1.2.3";network-user="sip:user@sip.example.net" From: sip:MAC%3A000000000000@sip.example.net;tag=1234 To: sip:MAC%3A000000000000@sip.example.net Call-ID:3573853342923422@10.1.1.443573853342923422@192.0.2.44 CSeq: 2131 SUBSCRIBE Contact: sip:MAC%3A000000000000@sip.example.net Via: SIP/2.0/TCP10.1.1.41;192.0.2.41; branch=z9hG4bK6d6d35b6e2a203104d97211a3d18f57a Accept: message/external-body, application/x-z100-device-profile Content-Length: 0 (SRes) the SUBSCRIBE request is received by a SIP Proxy in the Service Provider's network which transmits it to the PDS. The PDS accepts the response and responds with a 200 OK * Note: TheClientdevice and the SIP proxy may have established a secure communications channel (for example, TLS) (NTFY) subsequently, the PDS transmits a SIP NOTIFY message indicating the profile location * Note: Some of the fields (for example, content-type) are continued on a separate line due to format constraints of this document NOTIFYsip:MAC%3A000000000000@10.1.1.44sip:MAC%3A000000000000@192.0.2.44 SIP/2.0 Event: ua-profile;effective-by=3600 From: sip:MAC%3A000000000000@sip.example.net;tag=abca To: sip:MAC%3A000000000000@sip.example.net;tag=1231 Call-ID:3573853342923422@10.1.1.443573853342923422@192.0.2.44 CSeq: 322 NOTIFY Via: SIP/2.0/UDP192.168.0.3;192.0.2.3; branch=z9hG4bK1e3effada91dc37fd5a0c95cbf6767d0 MIME-Version: 1.0 Content-Type: message/external-body; access-type="URL"; expiration="Mon, 01 Jan 2010 09:00:00 UTC"; URL="http://sip.example.net/z100-000000000000.html";size=9999size=9999; hash=10AB568E91245681AC1B Content-Type: application/x-z100-device-profile Content-ID: <39EHF78SA@sip.example.net> . . . (NRes)ClientDevice accepts the NOTIFY message and responds with a 200 OK (XReq) once the necessary secure communications channel is established, theClientdevice sends an HTTP request to the HTTP server indicated in the NOTIFY (XRes) the HTTP server responds to the request via a HTTP response containing the profile contents 7.2. Example 2:ClientDevice obtaining change notification The following example illustrates the case where aUseruser (X) is simultaneously accessing services via two differentClientsdevices (for example, MultimediaSoft Clientsentities on a PC and PDA) and has access to aUseruser Interface (UI) that allows for changes to theUseruser profile. The following are assumed for this example: o TheClientsdevices (A & B) obtain the necessary profiles from the same SIP Service Provider o The SIP Service Provider also provides aUseruser Interface (UI) that allows theUseruser to change preferences that impact theUseruser profile The flow diagram and an explanation of the messages follow. o Note: The example only shows retrieval ofUseruser X's profile, but it may request and retrieve other profiles (for example, local- network,Client).Device). ----- ----- |User |_________| UI* | * = User Interface | X | | | ----- ----- / \ / \ / \ +----------------------+ +--------+ +--------+ | SIP Service Provider | |ClientDevice | |ClientDevice | | | | A | | B | | SIP PDS HTTP | +--------+ +--------+ | PROXY Server | +----------------------+ | | | | | | | | (A-EX)|<=Enrolls for User X's profile=>|<=====>| | | | | | | | (A-RX)|<===Retrieves User X's profile================>| | | | | | | | | | Enrolls for | | | | (B-EX)|<== User X's ==>|<=====>| | | | profile | | | | | | | | | | | | (B-RX)|<= Retrieves User X's profile=>| | | | | | | (HPut)|---------------------->| | | | | (HRes)|<----------------------| | | | | | | | | NOTIFY| | | NOTIFY |<------| | (A-NT)|<-------------------------------| | | | 200 OK | | | (A-RS)|------------------------------->|200 OK | | | |------>| | | | | | | NOTIFY| | | | NOTIFY |<------| | | (B-NT)|<---------------| | | | | 200 OK | | | | (B-RS)|--------------->|200 OK | | | | |------>| | | | | | (A-RX)|<===Retrieves User X's profile================>| | | | | | | | | | (B-RX)|<= Retrieves User X's profile=>| | | | (A-EX)ClientDevice A discovers, enrolls and obtains notification related toUseruser X's profile (A-RX)ClientDevice A retrievesUseruser X's profile (B-EX)ClientDevice B discovers, enrolls and obtains notification related toUseruser X's profile (B-RX)ClientDevice B retrievesUseruser X's profile (HPut) Changes affected by theUseruser via theUseruser Interface (UI) are uploaded to the HTTP Server * Note: The UI itself can act as aClientdevice and subscribe toUseruser X's profile. This is not the case in the example shown. (HRes) Changes are accepted by the HTTP server (A-NT) PDS transmits a NOTIFY message toClientdevice A indicating the changed profile. A sample message is shown below: Note: Some of the fields (for example, Via) are continued on a separate line due to format constraints of this document NOTIFYsip:userX@10.1.1.44sip:userX@192.0.2.44 SIP/2.0 Event: ua-profile;effective-by=3600 From: sip:userX@sip.example.net;tag=abcd To: sip:userX@sip.example.net.net;tag=1234 Call-ID:3573853342923422@10.1.1.443573853342923422@192.0.2.44 CSeq: 322 NOTIFY Via: SIP/2.0/UDP192.168.0.3;192.0.2.3; branch=z9hG4bK1e3effada91dc37fd5a0c95cbf6767d1 MIME-Version: 1.0 Content-Type: message/external-body; access-type="URL"; expiration="Mon, 01 Jan 2010 09:00:00 UTC"; URL="http://www.example.com/user-x-profile.html";size=9999size=9999; hash=123456789AAABBBCCCDD . . . (A-RS)ClientDevice A accepts the NOTIFY and sends a 200 OK (B-NT) PDS transmits a NOTIFY message toClientdevice B indicating the changed profile. A sample message is shown below: Note: Some of the fields (for example, Via) are continued on a separate line due to format constraints of this document NOTIFYsip:userX@10.1.1.43sip:userX@192.0.2.43 SIP/2.0 Event: ua-profile;effective-by=3600 From: sip:userX@sip.example.net;tag=abce To: sip:userX@sip.example.net.net;tag=1235 Call-ID:3573853342923422@10.1.1.433573853342923422@192.0.2.43 CSeq: 322 NOTIFY Via: SIP/2.0/UDP192.168.0.3;192.0.2.3; branch=z9hG4bK1e3effada91dc37fd5a0c95cbf6767d2 MIME-Version: 1.0 Content-Type: message/external-body; access-type="URL"; expiration="Mon, 01 Jan 2010 09:00:00 UTC"; URL="http://www.example.com/user-x-profile.html";size=9999size=9999; hash=123456789AAABBBCCCDD . . . (B-RS)ClientDevice B accepts the NOTIFY and sends a 200 OK (A-RX)ClientDevice A retrieves the updated profile pertaining toUseruser X (B-RX)ClientDevice B retrieves the updated profile pertaining toUseruser X 8. IANA Considerations There are two IANA considerations associated with this document, SIP Event Package and HTTP header. These are outlined in this section. 8.1. SIP Event Package This specification registers a new event package as defined in [RFC3265]. The following information required for this registration: Package Name: ua-profile Package or Template-Package: This is a package Published Document: RFC XXXX (Note to RFC Editor: Please fill in XXXX with the RFC number of this specification). Persons to Contact: Daniel Petrie dan.ietf AT SIPez DOT com, sumanth@cablelabs.com New event header parameters: profile-type, vendor, model, version, effective-by, device-id, network-user (the profile-type parameter has predefined values. The new event header parameters do not) The following table illustrates the additions to the IANA SIP Header Field Parameters and Parameter Values: (Note to RFC Editor: Please fill in XXXX with the RFC number of this specification) Predefined Header Field Parameter Name Values Reference ---------------------------- --------------- --------- --------- Event profile-type Yes [RFCXXXX] Event vendor No [RFCXXXX] Event model No [RFCXXXX] Event version No [RFCXXXX] Event effective-by No [RFCXXXX] Event device-id No [RFCXXXX] Event network-user No [RFCXXXX] 8.2. New HTTP Event Header This document defines a new permanent HTTP request header field: Event. Header field name: Event Applicable protocol: http Status: standard Author/Change controller: IETF Specification document(s): [RFCXXXX] (Note to RFC Editor: Please fill in XXXX with the RFC number of this specification). 9. Security Considerations The framework specified in this document allowsService Providers to propagatefor the propagation of device profile datato Clients. This is accomplished by requiring deployed Clients to implement the framework. The framework (explained in Section 5)(Section 5.5.3). To accomplish this, it specifies a Profile Life Cyclethat allows Clients to request(Section 3.3) andobtain profile data. The Profile Life Cycle is enabled usingan Event Package(defined in Section 6) as per [RFC3265]. Thus, the primary components requiring security considerations are: Event Package,(Section 6). The Profile Life Cycle consists of three distinct communication channels: Profile Enrollment and Change Notification, ProfileData. The considerations, requirementsContent Retrieval, andrecommendationsProfile Change Operation. +------+ +-----+ | | | | |Device| | PNC | | | | | +------+ +-----+ | | | Profile Enrollment | |---------------------->| | | | Profile Notification | (initial |<----------------------| or upon | | a change) +------+ +-----+ | | | | |Device| | PCC | | | | | +------+ +-----+ | | | Profile Request | (When content |---------------------->| indirection | | is used) | Profile Response | |<----------------------| | | +------------+ +-----+ | Authorized | | PCC | | Entity | | | +------------+ +-----+ | | | | | Profile Change Request | |---------------------------------->| | | | Profile Change Response | |<----------------------------------| | | PNC = Profile Notification Component PCC = Profile Content Component Framework Reference Model Profile enrollment and change notification allows a device to transmit a request for a specific profile - relayed directly, or via one or more SIP proxies - to a PNC. If the PNC accepts the profile request, it transmits a Profile Notification that contains either: profile data or content indirection information. The profile data can contain information specific to an entity (such as the device or a user) and may contain sensitive information (such as service credentials). Compromise of such data can lead to threats such as impersonation attacks (establishing rogue sessions), theft of service (if services are obtainable), and zombie attacks. Even if the profile data is provided using content indirection, PCC information within the notification can lead to threats such as denial of service attacks (rogue devices bombard the PCC with requests for a specific profile) and attempts to modify erroneous data onto the PCC (since the location and format may be known). It is also important for the device to ensure the authenticity of the PNC since impersonation of the Service Provider can lead to Denial of Service, Man-in-the-Middle attacks, etc. Profile Content retrieval allows a device to retrieve profile data from a PCC. This communication is accomplished using one of many profile delivery protocols or frameworks, but is considered to be out of scope within this document. However, since the profile data returned is subject to the same considerations as that sent via profile notification, the same threats exist. Profile Change Operation allows an authorized entity to modify profiles stored on a PCC. The specific entities are based on Service Provider's policy and can include trusted network elements and devices alike. The profile information stored on a PCC can contain information that directs device and user behavior, services offered and may contain sensitive information such as credentials. Thus, allowing entities that are not trusted to perform profile modifications presents threats such as denial-of-service, manipulation of service, impersonation (for example, redirection to rogue networks) and man-in-the-middle attacks. The framework specified in this document accomplishes the propagation of profile data by utilizing the specified "ua-profile" event package which is based on [RFC3265]. Thus, its usage is expected to comply with the security considerations and requirements (access control, Notifier privacy mechanism, Denial-of-Service attacks, replay attacks, and Man-in-the Middle attacks) specified in Section 5 of [RFC3265]. The remainder of this section presents the specific security requirements for the framework. 9.1. Profile Enrollment and Change Notification This framework specifies, and allows for the propagation of, three profile types: local-network, device and user. Enrollment and change notification are expected to be accomplished over integrity-protected SIP communication channels and following requirements are presented: o devices and PNCs complying with this framework MUST implement TLS as specified in [RFC3268], including support for both mutual and one-way authentication (server-side) o devices and PNCs complying with this framework MUST implement the SIP Digest authentication scheme as specified in [RFC3261] o a PNC capable of propagating device and user profiles MUST contain a X.509 certificate. This certificate MUST contain the PNC's Fully Qualified Domain Name in the 'SubjectAltName', establishing the PNC as a host in the Service Provider's domain o a PNC capable of propagating local-network profiles or unauthenticated device profiles MUST support the use of the SIP Identity header as defined in [RFC4474] for inclusion in profile notifications Each profile type serves a different purpose, and is provided under different circumstances and thus presents slightly different requirements for authentication and protection of communication. local-network profile The local-network profile is provided by the local network and usually contains non-sensitive data that is shared among all participants in a local network. However, the framework also allows for the presentation of the user's AOR, if known, for possible privileged user data. This may, or may not, result in user-specific information. The following requirements are presented: * the PNC MUST authenticate the identity of the user (if set to anything other than the default) for local-network profile requests that result in user-specific profile data containing sensitive information; for authentication, unless other mechanisms are employed, SIP Digest is used. If the authentication fails, the PNC MUST not include any user- specific information in the local-network profile * the PNC MAY NOT authenticate requests for the local-network profile that do not result in any user-specific sensitive data (irrespective of the value of the From field) * the PNC MUST include the SIP Identity header as defined in [RFC4474] within profile notifications sent in response to local-network profile enrollment, unless an integrity-protected channel exists (for example, using S/MIME) * a device receiving profile notifications for local-network profiles MUST verify the SIP Identity header, unless transmitted over a previously established authenticated, integrity-protected channel. If the header verification fails, the device MUST not use the provided profile and treat it as a local-network profile enrollment failure and take measures such as enrollment retries device profile The device profile is expected to contain data specific to the device identity (AOR) being presented in the request. The presented identity may be auto-generated (for example, based on its hardware identity as allowed in section Section 5.1.1.2.1) or obtained via configuration. This identity and associated credentials have the following considerations: * credentials can be provided via out-of-band mechanisms such as pre-configuration or user interface * credentials may not be present, but obtained via the initial device profile, if allowed by the Service Provider * device may use the user's AOR and associated credentials for obtaining the device profile If the AOR presented in device profile enrollment is known by the PNC, the following requirements are presented: * the PNC MUST authenticate the AOR presented for enrollment using SIP Digest authentication, unless a previously established mutually authenticated channel exists (for example, using TLS). If the authentication fails, the PNC MUST not provide the requested device-specific profile. In such a scenario, the PNC MAY still provide a generic device profile for minimal services (for example, emergency calls in a telephony deployment, see [I-D.ietf-ecrit-phonebcp]) * if the profile data is provided in the enrollment notificaiton, the PNC MUST transmit it over an integrity-protected, confidential communications channel such as TLS If the AOR presented in device profile enrollment is not known by the PNC, the following requirements are presented: * the PNC MUST not provide any sensitive information in the profile data * the device MUST transmit the request over an integrity- protected SIP communications channel. If none exists, the device MUST establish a TLS connection with the PNC and verify the PNC's certificate. If the PNC authentication fails or a secure communications channel cannot be established, the device MUST treat it as a device profile enrollment failure and take measures such as retry enrollment user profile The user profile is expected to contain data specific to the user identity (AOR) being presented in thefollowing sub-sections. 9.1. Event Package The Event Package usage MUST adhererequest. This identity is expected to be known in thesecurity considerationsnetwork and associated with credentials. Thus, the following requirements(access control, Notifier privacy mechanism, Denial- of-Service attacks, replay attacks,are presented: * the device MUST transmit the request over an integrity- protected SIP communications channel. If none exists, the device MUST establish a TLS connection with the PNC andMan-in-the Middle attacks) specifiedverify the PNC's certificate. If the PNC authentication fails or a secure communications channel cannot be established, the device MUST treat this as a user profile enrollment failure and take measures such as retry enrollment * the PNC MUST authenticate the AOR presented for enrollment using SIP Digest authentication, unless a previously established mutually authenticated channel exists (for example, using TLS). If the user authentication fails, the PNC MUST not provide the requested user-specific information. It MAY provide minimal profile information (such as connection to a customer support webpage) * if the profile data is provided inSection 5 of [RFC3265]. Specificallythe enrollment notificaiton, the PNC MUST transmit it over an integrity-protected, confidential communications channel such as TLS 9.2. Profile Content Retrieval This framework does not mandate specific profile delivery frameworks, but presents security requirements for profile content retrieval using content indirection. Given theEvent Package definednature of the profiles, the requirements are as follows: o devices and PCCs compliant with this framework MUST implement HTTP Digest authentication as specified in [RFC2617]; thisframework,is used whenever an authentication challenge is initiated using HTTP based protocols specified for interoperability o a PCC complying with thissub-section hightlights additional considerations and security requirements. The Notifierframework MUSTauthenticate any SUBSCRIBE requestimplement HTTPS [RFC2818]; this is used when there are no existing integrity- protected communication channels o a PCC complying with this framework MUST contain aknown identity. ItX.509 certificate. This certificate MUSTNOT accept any SUBSCRIBE requests that fail an authentication challenge. Refer to [I-D.ietf-sip-identity] and [RFC3261] for RECOMMENDED SIP authentication methods. Unless configured otherwise,contain theNotifier SHOULD NOT respond to SUBSCRIBEs without an identity that can be authenticated. Exceptions include deployments catering to unknown Clients (for example, for self-subscription) or for troubleshooting (for example, credentials misplaced byPNC's Fully Qualified Domain Name in the 'SubjectAltName', establishing the PNC as auser). Refer to Section 9.3 for Profile Data considerationshost insuch cases.the Service Provider's domain TheNotifierfollowing general requirement applies to all profile types: o a device MUSTtransmit NOTIFY messages with sensitiverequest profiledatacontent retrieval over anauthenticated,integrity protectedchannel. Refer to Section 9.3 for information on profile data classification. It SHOULD transmit Content Indirection information (without profile data) over an integrity-protected channel, unless configured otherwise (for example, if the Service Provider is catering to unknown Clients). For data provided via content indirection, Subscribers MUST implement the hash verification scheme described in [RFC4483]. Subscribers withchannel such as HTTPS. If one does not exist or cannot be established, then theability to authenticate a PDS (for example, Service Provider Certificates, mutual shared secrets)device MUSTemploy such mechanisms prior to retrieving data. This framework RECOMMENDS that Service Providers consider providingtreat thisability to deployed Clients. 9.2. Profile Life Cycle Profile Discovery involves various protocols suchasDHCP and DNS that may provide unauthenticated information. Thus, successful Profile Enrollmenta profile content retrieval failure andsubsequent Profile Notification with an authenticated PDS (for example, via mutual authentication) are required to prevent threatstake measures such asimpersonationprofile content retrieval retries orDenialin the case ofService. Givenretry exhaustion, try enrollment The following profile-specific usage requirements are presented local-network profile * a PCC MUST challenge a profile content retrieval request if thenature of these mechanismsprofile data contains user-specific information; this challenge is against a user's AOR, known by the PCC andto prevent service disruption due to such threats,thespecification recommends caching of retrieved profiles (see Section 5.4) bydevice * a PCC MAY challenge a profile content retrieval request even if theClients. It also provides for multiple Profile Discovery mechanisms (based on Profile Types) which can minimally aid in thwarting security threats from individual mechanisms (for example, impersonated DNS). The specification strongly RECOMMENDS that solutions implementingprofile data contains user-specific information; this challenge is against a user's AOR, if provided device profile * a PCC MUST authenticate a profile content retrieval request if theFramework provideAOR presented is known. If theClients withauthentication fails, theability to recognize, mutually authenticate and establish integrity protected SIP communication channels (for example, mutual TLS using certificates). Clients withoutPCC MUST not provide device-specific information. In suchan ability SHOULD report changes to sensitivea scenario, the PCC MAY still provide a generic device profiledata (refer to Profile Data) using suitable mechanismsfor minimal services (for example,management reporting). Further, Clients with access to credentials (even if obtained viaemergency calls in aUser Interface)telephony deployment, see [I-D.ietf-ecrit-phonebcp]) user profile * a PCC MUSTrespond to authentication challenges. Profile Enrollment and Profile Notification are done viaauthenticate a profile content retrieval request. If theEvent Package definition anduser authentication fails, thesecurity requirements have been presented in Section 9.1. Profile Retrieval and Profile Change Upload are accomplished using Profile Data Frameworks and are addressed in Section 9.3. 9.3. Profile Data Profile data provided using any ofPNC MUST not provide theProfile Types is expected to happen via suitable Profile Data Framework (such as XCAP) or suitable protocolrequested user-specific information. It MAY provide minimal profile information (such asHTTP). Data defined using such frameworks mayconnection to a customer support webpage) 9.3. Profile Change Operation Changes to profiles will only besensitive (for example, user credentials) or non-sensitive (for example, list of DNS servers). Ifmade by authorized entities and requires mutual authentication. The following requirements are presented: o aprofile contains sensitive data, itPCC complying with this framework MUSTbe provided overcontain amutual-authenticated, integrity protected channel. Even ifX.509 certificate. This certificate MUST contain thedata is non-sensitive, it SHOULD still be provided overPNC's Fully Qualified Domain Name in the 'SubjectAltName', establishing the PNC as asecure channel. Exceptions include cases where deployments cater to unknown Clientshost in the Service Provider's domain. This may be the same, or different, from the certificate used fortroubleshooting. Forprofiledata delivered within the framework (i.e. datacontent retrieval o an entity that isprovided inallowed to make updates MUST contain a AOR that is known to theNOTIFY),network and the requirementsspecified in Section 9.1. Whenfor making changes are the same as that for user profiledata is delivered viacontentindirection, authentication, integrity, confidentiality MUST be provided byretrieval, with theProfile Data Frameworks containingauthorized entity playing theretrieval mechanisms. Further,role of anon-replayable authentication mechanism (for example, Digest authentication) MUST be used.user 10. Acknowledgements Many thanks to those who contributed and commented on the many iterations of this document. Detailed comments were provided by the following individuals: Jonathan Rosenberg from Cisco, Henning Schulzrinne from Columbia University, Cullen Jennings from Cisco, Rohan Mahy from Plantronics, Rich Schaaf from Pingtel, Volker Hilt from Bell Labs, Adam Roach of Estacado Systems, Hisham Khartabil from Telio, Henry Sinnreich from MCI, Martin Dolly from AT&T Labs, John Elwell from Siemens, Elliot Eichen and Robert Liao from Verizon, Dale Worley from Pingtel, Francois Audet from Nortel, Roni Even from Polycom, Jason Fischl from Counterpath, Josh Littlefield from Cisco, Nhut Nguyen from Samsung. The editor would like to extend a special thanks to the experts who contributed to the restructuring and revisions as proposed by the SIPPING WG, specifically Keith Drage from Lucent (restructuring proposal), Peter Blatherwick from Mitel (who also contributed to the Overview and Introduction sections), Josh Littlefield from Cisco (examples and diagram suggestions), Alvin Jiang of Engin, Martin Dolly from AT&T,andJason Fischl fromCounterpath.Counterpath, Donald Lukacs from Telcordia and Eugene Nechamkin from Broadcom. Additionally, sincere appreciation is extended to the chairs (Mary Barnes from Nortel and Gonzalo Camarillo from Ericsson) and the Area Directors (Cullen Jennings from Cisco and Jon Peterson and Cisco) for facilitating discussions, and for reviews and contributions. 11.Open Items [[Editor's note: This is being used a place holder only and will be removed once the items listed are addressed]]Change History [[RFC Editor: Please remove this entire section upon publication as an RFC.]] 11.1. Changes from draft-ietf-sipping-config-framework-10.txt The followingcommentsareconsideredthe changes that have been incorporated into this I-D, resulting from the design team discussions based on Working Group feedback. o Modified the "From" header of the local network profile to reflect the user's AOR, if any; delegated the device identifier to a new event header termed "device-id"; removed use for 'network-user' within the local-network profile; if there are objections tobe open (i.e. not addressed) in this version of the I-Dthis, please educate us! o Added text to indicate DHCPv4 or DHCPv6 to accomodate IPv4 and IPv6 environments oReplaceReplaced generic 'Service Provider' witha termterms to betterrepresentative of its definition o Analyze potential unformity in the formation of the Subscription URI across Profile Types. If not, provide a bried explanation of the analysisrepresent scenarios oAnalyzeAnalyzed the current SHOULD v/s MUST requirements for the Profile Frameworkto obtain consensusandfacilitate interoperability o Present an analysis of the Local Network Profile discovery methods in DNS-less environmentsmade modifications oCheck on potentially referencingReferenced RFC4122 instead of OUTBOUND oSecurity Considerations requires further review 12. Change History [[RFC Editor: Please remove this entire section upon publication as an RFC.]] 12.1.Simplified the introductory sections to better illustrate potential deployment possibilities; indicated the minimum profile supported to be 'device' o Revamped the security considerations sections 11.2. Changes from draft-ietf-sipping-config-framework-09.txt Following the ad-hoc SIPPING WG discussions at IETF#67 and as per the email from Gonzalo Camarillo dated 12/07/2006, Sumanth was appointed as the new editor. This sub-section highlights the changes made by the editor (as per expert recommendations from the SIPPING WG folks interested in this effort) and the author. Changes incorporated by the editor: o Document was restructured based on a) Keith's recommendations in the email dated 11/09/2006 and responses (Peter, Sumanth, Josh) b) subsequent discussions by the ad-hoc group consisting of the editor, the author, expert contributors (Peter Blatherwick, Josh Littlefield, Alvin Jiang, Jason Fischl, Martin Dolly, Cullen Jennings) and the co-chairs . Further changes follow. o Use cases were made high-level with detailed examples added later on o Several sections were modified as part of the restructuring (for example, Overview, Introduction, Framework Requirements, Security Sections) o General editorial updates were made Changes incorporated by the author: o Incorporated numerous edits and corrections from CableLabs review. o Used better ascii art picture of overview from Josh Littlefield o Fixed the normative text for network-user so that it is now consistant: MAY provide for device profile, MUST provide for local-network profile.12.2.11.3. Changes from draft-ietf-sipping-config-framework-08.txt The Request URI for profile-type=localnet now SHOULD not have a user part to make routing easier. The From field SHOULD now contain the device id so that device tracking can still be done. Described the concept of profile-type as a filter and added normative text requiring 404 for profile types not provided. Moved "application" profile type to draft-ietf-sipping-xcap-config-01. The "application" value for the profile-type parameter will also be used as a requirement that XCAP be supported. Fixed text on certificate validation. Added new HTTP header: Event to IANA section and clean up the IANA section. Added diagram for Service Provider use case schenario. Added clarification for HTTP Event header. Added clarification of subscriber handling of NOTIFY with no body.12.3.11.4. Changes from draft-ietf-sipping-config-framework-07.txt Made XCAP informative reference. Removed "document" and "auid" event header parameters, and Usage of XCAP section to be put in separate supplementary draft. Fixed ABNF fornetwork-userdevice-id to be addr-spec only (not name-addr) and to be quoted as well. Synchronized with XCAP path terminology. Removed XCAP path definition as it is already defined in XCAP. User agent instance ID is now defined in output (not GRUU). Clarified the rational for thenetwork-userdevice-id parameter. Added text to suggest URIs for To and From fields. Clarified use ofnetwork-userdevice-id parameter. Allow the use of the auid and document parameters per request by the OMA.12.4.11.5. Changes from draft-ietf-sipping-config-framework-06.txt Restructured the introduction and overview section to be more consistent with other Internet-Drafts. Added additional clarification for the Digest Authentication and Certificate based authentication cases in the security section. Added two use case scenarios with cross referencing to better illustrate how the framework works. Added better cross referencing in the overview section to help readers find where concepts and functionality is defined in the document. Clarified the section on the use of XCAP. Changed the Event parameter "App-Id" to "auid". Made "auid" mutually exclusive to "document". "auid" is now only used with XCAP. Local network subscription URI changed to <device-id>@ <local-network> (was anonymous@<local-network>). Having a different Request URI for each device allows the network management to track user agents and potentially manage bandwidth, port allocation, etc. Changed event package name from sip-profile to ua-profile per discussion on the list and last IETF meeting. Changed "local" profile type token to "local-network" per discussion on the list and last IETF meeting. Simplified "Vendor", "Model", "Version" event header parameters to allow only quoted string values (previously allowed token as well). Clarified use of the term cache. Added references for ABNF constructs. Numerous editorial changes. Thanks Dale!12.5.11.6. Changes from draft-ietf-sipping-config-framework-05.txt Made HTTP and HTTPS profile transport schemes mandatory in the profile delivery server. The subscribing device must implement HTTP or HTTPS as the profile transport scheme. Rewrote the security considerations section. Divided references into Normative and Informative. Minor edits throughout.12.6.11.7. Changes from draft-ietf-sipping-config-framework-04.txt Clarified usage of instance-id Specify which event header parameters are mandatory or optional and in which messages. Included complete list of event header parameters in parameter overview and IANA sections. Removed TFTP reference as protocol for profile transport. Added examples for discovery. Added ABNF for all event header parameters. Changed profile-name parameter back to profile-type. This was changed to profile-name in 02 when the parameter could contain either a token or a path. Now that the path is contained in the separate parameter: "document", profile-type make more sense as the parameter name. Fixed some statements that should have and should not have been normative. Added the ability for the user agent to request that the default user associated with the device be set/changed using the"network- user""device-id" parameter. A bunch of editorial nits and fixes.12.7.11.8. Changes from draft-ietf-sipping-config-framework-03.txt Incorporated changes to better support the requirements for the use of this event package with XCAP and SIMPLE so that we can have one package (i.e. simple-xcap-diff now defines a content type not a package). Added an additional profile type: "application". Added document and app-id Event header parameters in support of the application profile. Define a loose high level data model or relationship between the four profile types. Tried to edit and fix the confusing and ambiguous sections related to URI formation and discovery for the different profile types. Better describe the importance of uniqueness for the instance id which is used in the user part of the device URI.12.8.11.9. Changes from draft-ietf-sipping-config-framework-02.txt Added the concept of the local network as a source of profile data. There are now three separate logical sources for profile data: user, device and local network. Each of these requires a separate subscription to obtain.12.9.11.10. Changes from draft-ietf-sipping-config-framework-01.txt Changed the name of the profile-type event parameter to profile-name. Also allow the profile-name parameter to be either a token or an explicit URI. Allow content indirection to be optional. Clarified the use of the Accept header to indicate how the profile is to be delivered. Added some content to the Iana section.12.10.11.11. Changes from draft-ietf-sipping-config-framework-00.txt This version of the document was entirely restructured and re-written from the previous version as it had been micro edited too much. All of the aspects of defining the event package are now organized in one section and is believed to be complete and up to date with [RFC3265]. The URI used to subscribe to the event package is now either the user or device address or record. The user agent information (vendor, model, MAC and serial number) are now provided as event header parameters. Added a mechanism to force profile changes to be make effective by the user agent in a specified maximum period of time. Changed the name of the event package from sip-config to ua-profile Three high level security approaches are now specified.12.11.11.12. Changes from draft-petrie-sipping-config-framework-00.txt Changed name to reflect SIPPING work group item Synchronized with changes to SIP DHCP [RFC3361], SIP [RFC3261] and [RFC3263], SIP Events [RFC3265] and content indirection [RFC4483] Moved the device identity parameters from the From field parameters toUser-Agentuser-agent header parameters. Many thanks to Rich Schaaf of Pingtel, Cullen Jennings of Cisco and Adam Roach of Estacado Systems for the great comments and input.12.12.11.13. Changes from draft-petrie-sip-config-framework-01.txt Changed the name as this belongs in the SIPPING work group. Minor edits12.13.11.14. Changes from draft-petrie-sip-config-framework-00.txt Split the enrollment into a single SUBSCRIBE dialog for each profile. The 00 draft sent a single SUBSCRIBE listing all of the desired. These have been split so that each enrollment can be routed differently. As there is a concept of device specific and user specific profiles, these may also be managed on separate servers. For instance in a nomadic situation the device might get its profile data from a local server which knows the LAN specific profile data. At the same time the user specific profiles might come from the user's home environment profile delivery server. Removed the Config-Expires header as it is largely superfluous with the SUBSCRIBE Expires header. Eliminated some of the complexity in the discovery mechanism. Suggest caching information discovered about a profile delivery server to avoid an avalanche problem when a whole building full of devices powers up. Added theUser-Profileuser-profile From header field parameter so that the device can request a user specific profile for a user that is different from the device's default user.13.12. References13.1.12.1. Normative References[I-D.ietf-sip-identity] Peterson, J. and C. Jennings, "Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)", draft-ietf-sip-identity-06 (work in progress), October 2005.[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.[RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor Extensions", RFC 2132, March 1997.[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, "HTTP Authentication: Basic and Digest Access Authentication", RFC 2617, June 1999. [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002. [RFC3263] Rosenberg, J. and H. Schulzrinne, "Session Initiation Protocol (SIP): Locating SIP Servers", RFC 3263, June 2002. [RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific Event Notification", RFC 3265, June 2002. [RFC3268] Chown, P., "Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)", RFC 3268, June 2002. [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003. [RFC3319] Schulzrinne, H. and B. Volz, "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers", RFC 3319, July 2003. [RFC3361] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers", RFC 3361, August 2002. [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, July 2005. [RFC4474] Peterson, J. and C. Jennings, "Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)", RFC 4474, August 2006. [RFC4483] Burger, E., "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages", RFC 4483, May 2006.13.2.12.2. Informative References [I-D.ietf-ecrit-phonebcp] Rosen, B. and J. Polk, "Best Current Practice for Communications Services in support of Emergency Calling", draft-ietf-ecrit-phonebcp-00 (work in progress), October 2006. [I-D.ietf-simple-xcap] Rosenberg, J., "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)", draft-ietf-simple-xcap-12 (work in progress), October 2006. [I-D.ietf-simple-xcap-diff] Rosenberg, J., "An Extensible Markup Language (XML) Document Format for Indicating A Change in XML Configuration Access Protocol (XCAP) Resources", draft-ietf-simple-xcap-diff-04 (work in progress), October 2006. [RFC0959] Postel, J. and J. Reynolds, "File Transfer Protocol", STD 9, RFC 959, October 1985. [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997. [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.[RFC3377] Hodges, J. and R. Morgan,[RFC4510] Zeilenga, K., "Lightweight Directory Access Protocol(v3):(LDAP): TechnicalSpecification", RFC 3377, September 2002. [RFC3617] Lear, E., "Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol (TFTP)",Specification Road Map", RFC3617, October 2003.4510, June 2006. Authors' Addresses Daniel Petrie SIPez LLC. 34 Robbins Rd Arlington, MA 02476 USA Email: dan.ietf AT SIPez DOT com URI: http://www.SIPez.com/ Sumanth Channabasappa (Editor) CableLabs 858 Coal Creek Circle Louisville, Co 80027 USA Email: sumanth@cablelabs.com URI: http://www.cablelabs.com/ Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).