Subject: RE: [Sipping] Comments on config framework draft- URIs and event package parameters

From: Simonetti Gabrielle <[email-masked]>
Date: Fri, 24 Sep 2004 15:39:32 +0200

> Section 3.13.1
> --------------
> 
> - What if instance does not matter? Example all Nokia phone 
> 6600 model require the same profile, instance does not 
> matter. Vendor and model is the only thing needed to download 
> a profile. There is no need for the service provider to have 
> separate profiles for every device, especially will they are 
> identical.

I agree that the instance-id might not matter in the case of the "device" profile. In fact using the instance-id creates unnecessary subscription targets, as these can be grouped by "model", for example, as you say. 
1/What do you suggest for the format of the subscription URI then, leaving out the instance-id?
2/The question has already been raised whether "vendor", "model" and "version" are sufficient to identify the precise profile to be delivered, e.g. in the case where a particular UA model has different components, each with its own version number. A possible solution would be to define a new parameter "component" for the Event Header to identify the component for which the subscription is made.

> Section 3.13.3
> --------------
> 
> - about placing an "anonymous" user name. Why isn't 
> sip:example.com enough (no user part)? If user part is 
> present, it MUST be ignored.

The instance-id might be useful here in the user part of the "local" profile URI, in the case where the default local parameters delivered by the modem depend on the device.

> Section 4.6
> ------------
>
> - This sentence:
>    "When the "profile-name" is application, but the "app-id" parameter 
> is absent, this specifies that the user wishes to SUBSCRIBE to all 
> documents for all application usages associated with the user in the 
> request-uri."
> 
> contradicts with this one:
> 
> "If the "profile-name" is "application", the "app-id" MUST be present as well."
> 
> The latter says its a MUST, but the former said the "app-id" 
> missing is feature.

Actually, it is not specified in the framework which of the Event Header parameters are obligatory/optional/unnecessary in a subscription. For example, I would imagine that for the "device" profile subscription, the parameter "vendor" is obligatory, while the parameters "model" and  "version" are optional (the parameter "vendor" alone in a subscription would correspond to the profile relative to all devices from one same vendor). On the opposite, for the "application" profile subscription, the "app-id" parameter could be obligatory while "vendor", "model" and "version" are unnecessary.

Regards,
Gabrielle

Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.

====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to 
[email-masked]. Thank you
====================================================================

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP