Re: [Dime] open issues #1 in DOIC

<> Fri, 29 November 2013 08:39 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 765901AE283 for <>; Fri, 29 Nov 2013 00:39:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4HDDqVJ-Xsbp for <>; Fri, 29 Nov 2013 00:39:02 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 957CB1AC7F0 for <>; Fri, 29 Nov 2013 00:39:02 -0800 (PST)
Received: from (unknown [xx.xx.xx.198]) by (ESMTP service) with ESMTP id C3B4C1901FF; Fri, 29 Nov 2013 09:39:00 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id ABD5918008E; Fri, 29 Nov 2013 09:39:00 +0100 (CET)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0158.001; Fri, 29 Nov 2013 09:39:00 +0100
From: <>
To: Jouni Korhonen <>, " list" <>
Thread-Topic: [Dime] open issues #1 in DOIC
Thread-Index: AQHO7N0388Z4Ak2nq0as3rZt2kE0jJo74RCA
Date: Fri, 29 Nov 2013 08:38:59 +0000
Message-ID: <9889_1385714340_529852A4_9889_16410_1_6B7134B31289DC4FAF731D844122B36E3093B0@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2013.11.29.44815
Subject: Re: [Dime] open issues #1 in DOIC
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 29 Nov 2013 08:39:04 -0000


For me, "pseudo-session" refers to session-based oriented applications that do not rely on the session-id for message correlations but on something else e.g. user-name. So it is implied that the same server is contacted by the client managing the session. In the Cx example, the same origin-host will be used in the client-initiated requests after the initial exchange and the server discovery phase.



-----Message d'origine-----
De : DiME [] De la part de Jouni Korhonen
Envoyé : vendredi 29 novembre 2013 09:30
À : list
Objet : [Dime] open issues #1 in DOIC


           [OpenIssue: Do we assume that all requests in a pseudo-session
           typically need to go to the same server?]

The example here is in context of Cx. Not that I am expert on Cx (or anything)
but based on the CCF the requests _may_ have destination-host. Thus, I assume
that it is an implementation issue whether pseudo-sessions need to go to the
same server.. I guess we cannot have such firm requirement. Correct?

- Jouni
DiME mailing list


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,
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, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.