
|
Technical please… What does “draft-ietf-sipping-config-framework” do? It proposes a framework for propagating profile data to SIP UAs How does it accomplish it? By specifying a new Event Package based on the SUBSCRIBE/NOTIFY mechanism (RFC3265) Does it specify anything else (at a high level)? It specifies a profile life cycle describing how: a device requests profile data using the new event package (enrollment) a device retrieves profiles via content indirection (content retrieval) a device is notified of profile changes (change notification) It specifies three types of profiles, each of which use the profile life cycle local-network, device and user What does it not do? It does not specify any data models |