Subject: [Dime] RE : Fwd: Draft minutes available

From: <[email-masked]>
Date: Wed, 27 Mar 2013 08:48:07 +0000

Hi,

Please see below.

-------- Message d'origine --------
Objet : Fwd: [Dime] Draft minutes available
De : Jouni Korhonen <[email-masked]>
A : MORAND Lionel OLNC/OLN <[email-masked]>,Hannes Tschofenig <[email-masked]>
CC :

> I have a few minor comments and corrections for the draft minutes:
>
> -- in the overload-reqs discussion:
>
>> Keith - This is a requirements doc, thus no one will implement this. The MUST constrains the working group on the solution doc. There is no problem with text here. MUST vs SHOULD - we want to say MUST here. If there's problem with the MUST, you should constrain it the following text.
>>
>> Lionel - I don't understand. There's no way to do this without a new application ID. You would need to go through dedicated proxies to do this.
>
> I thought Lionel was commenting that the "new application" approach for moving overload control info around wouldn't be able to solve the Req 35 (crossing non-supporting intermediaries) use case. Did I misunderstand the comment?
>
Ben is right. I said that a new application will only be able to go through existing relay and redirect agent and not through "legacy" proxies i.e. Not supporting/advertising the new application.
So the question is simple: in the requirement elaboration phase, are we sure that a solution based on a new App-id will be rejected? If not, the "Should" is meaningful. If yes, this is a strong requirement draft and this must be stated somewhere in the draft.

Regards,

Lionel

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.