1 / 4

Schema for SIP Profile Data Sets Draft by Dan Petrie

This draft document outlines use case scenarios for merging and constraint requirements in SIP profile datasets. It covers codec and transport protocol properties, simplifying constraints, default merging algorithm, and examples corresponding to use cases.

marilynb
Download Presentation

Schema for SIP Profile Data Sets Draft by Dan Petrie

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Schema for SIP Profile Data Setsdraft-petrie-sipping-profile-datasets-01.txt Dan Petrie dgpetrie AT yahoo.com

  2. Changes from 00 • Added use case scenarios to illustrate: • Merging and constraint requirements • Codec and transport protocol properties • Removed more complicated constraints elements: “forbid”, “set_any”, “set_all” and “set_one” • Added simpler constraints attributes: "policy" and "visibility" • Defined default merging algorithm and profile source precedence, alternative algorithm may be specified for specific properties • Added some examples correlated to use cases

  3. General Requirements • There are properties that may occur in more than one profile • Need to be able to be able to merge and resolve collisions of the same property across multiple profiles • Merging strategy or algorithm is specific to the property • For some properties aggregation is required • For others a single value exists which may be overridden • Need ability to constrain certain property values from being used or mandate use • Need ability to specify what properties may be changed or not changed • Need to specify property values that should not be shown to user

  4. Hypothesis on solution to constraints and merging • Profile hierarchy of precedence: • Device, User, Application, Local-Network • Merging is algorithm statically specified in property spec: • Aggregate, Override or TBD • Merging is constrained by “policy” attribute: • “allowed “, “disallowed” or “mandatory” • Property values in a profile lower in the hierarch that contradict a property value that is disallowed or mandatory get ignored

More Related