Re: [Dime] open issues #1 in DOIC
Steve Donovan <srdonovan@usdonovans.com> Mon, 02 December 2013 15:45 UTC
Return-Path: <srdonovan@usdonovans.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 6AB5E1A1F19 for <dime@ietfa.amsl.com>; Mon, 2 Dec 2013 07:45:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level:
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_NEUTRAL=0.779] autolearn=no
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 eZ6FOAKPppsM for <dime@ietfa.amsl.com>; Mon, 2 Dec 2013 07:45:30 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [173.247.247.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6965F1A16F0 for <dime@ietf.org>; Mon, 2 Dec 2013 07:45:30 -0800 (PST)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:64510 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <srdonovan@usdonovans.com>) id 1VnVg4-0003Fd-34 for dime@ietf.org; Mon, 02 Dec 2013 07:45:27 -0800
Message-ID: <529CAAF4.6070708@usdonovans.com>
Date: Mon, 02 Dec 2013 09:44:52 -0600
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: dime@ietf.org
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> <FDAFA23D-F4BA-42F6-9CC4-10399B905CEA@gmail.com>
In-Reply-To: <FDAFA23D-F4BA-42F6-9CC4-10399B905CEA@gmail.com>
Content-Type: multipart/alternative; boundary="------------050001040201080106060308"
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srdonovan@usdonovans.com
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: Mon, 02 Dec 2013 15:45:32 -0000
Agreed, looks good. Steve On 11/29/13 4:04 AM, Jouni Korhonen wrote: > 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. >> > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime >
- [Dime] open issues #1 in DOIC Jouni Korhonen
- Re: [Dime] open issues #1 in DOIC lionel.morand
- Re: [Dime] open issues #1 in DOIC Jouni Korhonen
- Re: [Dime] open issues #1 in DOIC Jouni Korhonen
- Re: [Dime] open issues #1 in DOIC lionel.morand
- Re: [Dime] open issues #1 in DOIC Jouni Korhonen
- Re: [Dime] open issues #1 in DOIC Steve Donovan
- Re: [Dime] open issues #1 in DOIC Maria Cruz Bartolome
- Re: [Dime] open issues #1 in DOIC Ben Campbell
- Re: [Dime] open issues #1 in DOIC Shishufeng (Susan)