IETF Logo Mail Archive

Re: [Dime] Question regarding diameter session

Ivan Skytte Jørgensen <isj-dime@i1.dk> Thu, 29 June 2017 09:20 UTC

Return-Path: <isj-dime@i1.dk>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C17E612ECBC for <dime@ietfa.amsl.com>; Thu, 29 Jun 2017 02:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 MI10AS95QaPD for <dime@ietfa.amsl.com>; Thu, 29 Jun 2017 02:20:35 -0700 (PDT)
Received: from i1.dk (55e9f507.rev.dansknet.dk [85.233.245.7]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD0E12EB43 for <dime@ietf.org>; Thu, 29 Jun 2017 02:20:34 -0700 (PDT)
Received: from i1.dk (localhost [127.0.0.1]) by i1.dk (Postfix) with ESMTP id F3C9085571 for <dime@ietf.org>; Thu, 29 Jun 2017 09:20:32 +0000 (UTC)
Received: from isjsys.localnet (isjsys [10.0.0.2]) by i1.dk (Postfix) with ESMTPA for <dime@ietf.org>; Thu, 29 Jun 2017 09:20:32 +0000 (UTC)
From: Ivan Skytte Jørgensen <isj-dime@i1.dk>
To: dime@ietf.org
Date: Thu, 29 Jun 2017 11:20:32 +0200
Message-ID: <4060965.cvG7Lxnu4Z@isjsys>
User-Agent: KMail/4.11.5 (Linux/3.11.10-29-desktop; KDE/4.11.5; x86_64; ; )
In-Reply-To: <CAFUT_s2os8=BkfGFyBd3W0V+yQ5wiwCibagLxrL8OTKWQ8ZGgA@mail.gmail.com>
References: <CAFUT_s2os8=BkfGFyBd3W0V+yQ5wiwCibagLxrL8OTKWQ8ZGgA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/f69uh14pknAutlE7UM-cjEfJq9c>
Subject: Re: [Dime] Question regarding diameter session
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 29 Jun 2017 09:20:37 -0000

On Thursday 29 June 2017 13:15:05 Ajinkya Joshi wrote:
> Hello,
> 
> >From the RFC 6733, it is clear that diameter session is identified bases on
> session-id, which has to be globally unique. Also in section 2.5
> (Connections vs Sessions), it's clearly mentioned that one connection can
> be used to multiplex multiple diameter sessions.
> I have following questions related to diameter session -
> 
> Is there any implicit correlation between diameter session and origin-host?

Only what is spelled out in the RFC "The Session-Id MUST begin with the sender's identity [...]"

A dubious diameter implementation may decode the session-id extracting what the origin-host might be. But that would be silly since it is already present in the origin-host AVP. Well-behaved diameter implementations treat session-id as an opaque string.

> Does diameter standard allow different requests for the same session to
> have different origin-host value?

Yes, eg RAR and ASR requests will have a typically have an origin-host/realm different from where the session-id was created.


/isj

v2.23.0 | Report a Bug | By Email