Re: [Dime] open issues #1 in DOIC

Jouni Korhonen <jouni.nospam@gmail.com> Fri, 29 November 2013 10:04 UTC

Return-Path: <jouni.nospam@gmail.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D0261A1F55 for <dime@ietfa.amsl.com>; Fri, 29 Nov 2013 02:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6uBM_d20QYH for <dime@ietfa.amsl.com>; Fri, 29 Nov 2013 02:04:51 -0800 (PST)
Received: from mail-bk0-x22d.google.com (mail-bk0-x22d.google.com [IPv6:2a00:1450:4008:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 2FEA51A1F4A for <dime@ietf.org>; Fri, 29 Nov 2013 02:04:50 -0800 (PST)
Received: by mail-bk0-f45.google.com with SMTP id mx13so4157625bkb.4 for <dime@ietf.org>; Fri, 29 Nov 2013 02:04:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bcrgy992bJfujHWQaWnbCSWpLJUMNUSo+4++RXb+xtk=; b=iZuN/QOX0fJjMdM7YIGcTF2JD26nMxDe3euHlWruLSFQUUskfycvgH7/qboIwurg/9 30UasVhluR5rjOQaPOIDuMM23F7Ic4Nhg0Prq/y90XcQ7aaVPYernjsw/ISrALj8C4PJ 5Ii7oh9St4t5Yr0B+saYgM4J4PygEuDe9gLVtGNDtdaXStD6rhR+QO6hBZjkJkREEoRL r/7WG2QQd++pVeLrD+nZtxqhyoIwmQTgWX1xN7ZjNvUM+wCX07DA71C5t8DhIG7wKy9p lTzE3Z3mCModCSIDxQr5fT5ogK2GSh+NTq8roYGkGlXinHSub2W/jYQYv1Ws2LhC7rRw gOcw==
X-Received: by 10.204.166.15 with SMTP id k15mr146107bky.78.1385719489402; Fri, 29 Nov 2013 02:04:49 -0800 (PST)
Received: from ?IPv6:2001:1bc8:101:f101:a031:8d25:ae76:95d8? ([2001:1bc8:101:f101:a031:8d25:ae76:95d8]) by mx.google.com with ESMTPSA id t2sm62786518bkh.3.2013.11.29.02.04.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 29 Nov 2013 02:04:46 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <3468_1385718494_529862DE_3468_4222_1_6B7134B31289DC4FAF731D844122B36E309600@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Date: Fri, 29 Nov 2013 12:04:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDAFA23D-F4BA-42F6-9CC4-10399B905CEA@gmail.com>
References: <5E28C8B7-2E5E-41E8-9592-24A19AD76826@gmail.com> <9889_1385714340_529852A4_9889_16410_1_6B7134B31289DC4FAF731D844122B36E3093B0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <52EDD6D4-71CD-439F-9D2D-439CC656C3CC@gmail.com> <3468_1385718494_529862DE_3468_4222_1_6B7134B31289DC4FAF731D844122B36E309600@PEXCVZYM13.corporate.adroot.infra.ftgroup>
To: lionel.morand@orange.com
X-Mailer: Apple Mail (2.1510)
Cc: "dime@ietf.org list" <dime@ietf.org>
Subject: Re: [Dime] open issues #1 in DOIC
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Nov 2013 10:04:53 -0000

Would work for me.

- Jouni

On Nov 29, 2013, at 11:48 AM, lionel.morand@orange.com wrote:

> Actually, I realized that we are redefining something somehow already in use in RFC 6733:
> 
> 9.6. Correlation of Accounting Records
> 
> 
>   If an application uses accounting messages, it can correlate
>   accounting records with a specific application session by using the
>   Session-Id of the particular application session in the accounting
>   messages.  Accounting messages MAY also use a different Session-Id
>   from that of the application sessions, in which case, other session-
>   related information is needed to perform correlation.
> 
> We could maybe reuse the same type of wording to simplify the definition:
> 
> Pseudo-session applications are applications that
> do not rely on the Session-Id AVP for correlation 
> of application messages related to the same session
> but use another session-related information for this
> purpose. The 3GPP defined Cx application [3GPP.29.229]
> is an example of a pseudo-session application.
> 
> OK?
> 
> Regards,
> 
> Lionel
> 
> -----Message d'origine-----
> De : Jouni Korhonen [mailto:jouni.nospam@gmail.com] 
> Envoyé : vendredi 29 novembre 2013 10:01
> À : MORAND Lionel IMT/OLN
> Cc : dime@ietf.org list
> Objet : Re: [Dime] open issues #1 in DOIC
> 
> 
>   Pseudo-session applications:
> 
>      While this class of application does not use the Diameter
>      Session-ID AVP to correlate requests, there is an implied ordering
>      of transactions defined by the application and except for the
>      Session-ID differences pseudo-session based applications are
>      generally assumed to behave like session-based application.  The
>      3GPP defined Cx application [3GPP.29.229] is an example of a
>      pseudo-session application.
> 
> 
> Would this suffice?
> 
> - Jouni
> 
> 
> 
> On Nov 29, 2013, at 10:38 AM, lionel.morand@orange.com wrote:
> 
>> Hi,
>> 
>> 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.
>> 
>> Regards,
>> 
>> Lionel 
>> 
>> -----Message d'origine-----
>> De : DiME [mailto:dime-bounces@ietf.org] De la part de Jouni Korhonen
>> Envoyé : vendredi 29 novembre 2013 09:30
>> À : dime@ietf.org list
>> Objet : [Dime] open issues #1 in DOIC
>> 
>> Folks,
>> 
>>          [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
>> DiME@ietf.org
>> https://www.ietf.org/mailman/listinfo/dime
>> 
>> _________________________________________________________________________________________________________________________
>> 
>> 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.
>> 
> 
> 
> _________________________________________________________________________________________________________________________
> 
> 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.
>