Re: [Dime] draft-ietf-dime-ovli-01 questions #2

Ben Campbell <ben@nostrum.com> Tue, 03 December 2013 21:51 UTC

Return-Path: <ben@nostrum.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 A28371ADEBF for <dime@ietfa.amsl.com>; Tue, 3 Dec 2013 13:51:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level:
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] 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 YaunBu4Ub5S4 for <dime@ietfa.amsl.com>; Tue, 3 Dec 2013 13:51:32 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4DC1ADE8A for <dime@ietf.org>; Tue, 3 Dec 2013 13:51:32 -0800 (PST)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id rB3LpRlv039041 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 3 Dec 2013 15:51:28 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <529CA996.4020208@usdonovans.com>
Date: Tue, 3 Dec 2013 15:51:27 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A3207D0-BA9B-4659-B975-6D9DD30B85EB@nostrum.com>
References: <2D60D862-45C5-4B13-96E6-F9621AF33759@gmail.com> <19936_1385975192_529C4D98_19936_10950_1_6B7134B31289DC4FAF731D844122B36E30F190@PEXCVZYM13.corporate.adroot.infra.ftgroup> <529CA996.4020208@usdonovans.com>
To: Steve Donovan <srdonovan@usdonovans.com>
X-Mailer: Apple Mail (2.1822)
Received-SPF: pass (shaman.nostrum.com: 173.172.146.58 is authenticated by a trusted mechanism)
Cc: "dime@ietf.org list" <dime@ietf.org>
Subject: Re: [Dime] draft-ietf-dime-ovli-01 questions #2
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: Tue, 03 Dec 2013 21:51:33 -0000

On Dec 2, 2013, at 9:39 AM, Steve Donovan <srdonovan@usdonovans.com>; wrote:

> I would phrase it as application specific.

+1.

>  It is completely possible that the IETF could define an application that used pseudo sessions as well.  
> 

I hope we don't :-) Creating implicit session state while intentionally not using the built in mechanism for session state seems a questionable design choice.

> Steve
> On 12/2/13 3:06 AM, lionel.morand@orange.com wrote:
>> Hi,
>> 
>> Not sure that it is so "SDO" specific. But it is true that we should clarify that this concept is not clearly described in RFC6733 and it is up to the application to define the specific session states when not relying on the session-id and the session state machine defined in RFC6733.
>> 
>> Lionel
>> 
>> -----Message d'origine-----
>> De : DiME [
>> mailto:dime-bounces@ietf.org
>> ] De la part de Jouni
>> Envoyé : lundi 2 décembre 2013 09:25
>> À : 
>> DiME@ietf.org
>> 
>> Objet : [Dime] draft-ietf-dime-ovli-01 questions #2
>> 
>> In Section 3.1.1 where pseudo-session applications are discussed shouldn't
>> we also state that the pseudo-session application is somewhat a SDO specific
>> jewel? IMHO it is not really what RFC6733 session-less application is,
>> although from the base protocol point of view it is compliant.
>> 
>> - 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.
>> 
>> _______________________________________________
>> DiME mailing list
>> 
>> DiME@ietf.org
>> https://www.ietf.org/mailman/listinfo/dime
>> 
>> 
>> 
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime