[Dime] Question regarding diameter session

Ajinkya Joshi <ajoshi@definitionnetworks.com> Thu, 29 June 2017 07:45 UTC

Return-Path: <ajoshi@definitionnetworks.com>
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 D413B126DD9 for <dime@ietfa.amsl.com>; Thu, 29 Jun 2017 00:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=definitionnetworks-com.20150623.gappssmtp.com
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 6ns8EZPYlhpy for <dime@ietfa.amsl.com>; Thu, 29 Jun 2017 00:45:06 -0700 (PDT)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49F2E12706D for <dime@ietf.org>; Thu, 29 Jun 2017 00:45:06 -0700 (PDT)
Received: by mail-pf0-x22e.google.com with SMTP id c73so46286225pfk.2 for <dime@ietf.org>; Thu, 29 Jun 2017 00:45:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=definitionnetworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=+zKxUK1yf9E+3XOeA+R+TjEbRPs299bIVVFWWh6tdKE=; b=iFjgn1fBU/Y9tFyYgbAaOYG6hQ1ofEr7RYxTckCZAxGolb5PFmro3t9Mngp+UmG0Tu e+zXV9LNJc/Caf8lKZHquVl+eD9IIViMnVrSJMw+NJI4iVvWLbQlalU7xZperZHwmARt 7ZRi27GgdfZSJtC98iLwgzfN1RjV9xRUFG7tamCcMTlJ3WMGd8OsYg+cSLd9qPXBCUWo 6udFnPLEjZD6a519/srQ8zi6QfP9r+SIlP6aMkSseroRRIEXNG4mBi9onUzGJ1oj4nDa EYM0yO5fr4cX9s0CD3EW899x09alpf6LD+kPXq5ZS2CbRUIObpeQFFXoZscCOOfI/Qdf xZpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+zKxUK1yf9E+3XOeA+R+TjEbRPs299bIVVFWWh6tdKE=; b=NQka/rhlWLWCE/mjFP2Nyn0fh8JJ1qc1askwVeoV2i1Jy8l6JMz+flpBSwpzaRAceu LIHzAfyn/J7wFEJNJnRti/BEf+zU4vAVXp647ykGeEqmcLyKWRG8jwwwe7FcK5M2rj1X putTU2wxqTB4OmdkA9omoMi8iCssUSDjHKTfgLV78vAjFaG44tTKx5Ye+4Co/w82gfWA nEw8x+GSfitX33fmSf2TmEQssVDxVZYRMOyHH2VU9foxiD3L4hZs5BJ+dnQ5ATkvDO5a 71Tu4M3r7TzUbF+/pRy2fGPE8YvVdk1ArN6GgIe0Z8vjkpN6bg/wthcR9IzzvhSBh+Uj aTJA==
X-Gm-Message-State: AKS2vOxTA0r10ukUiyk0TvrNGOnhh7VrsA8VHtMrCszwkAISmEy/KmIp ctNP25BYqAAy2NkgHZv96pNPdpIis860
X-Received: by 10.98.94.134 with SMTP id s128mr14661129pfb.43.1498722305461; Thu, 29 Jun 2017 00:45:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.160.165 with HTTP; Thu, 29 Jun 2017 00:45:05 -0700 (PDT)
From: Ajinkya Joshi <ajoshi@definitionnetworks.com>
Date: Thu, 29 Jun 2017 13:15:05 +0530
Message-ID: <CAFUT_s2os8=BkfGFyBd3W0V+yQ5wiwCibagLxrL8OTKWQ8ZGgA@mail.gmail.com>
To: dime@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c066d1ca2612e0553147a1a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/uiq0LJLZPM8oVVtxsm_TUMVo2og>
Subject: [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 07:45:08 -0000

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?
Does diameter standard allow different requests for the same session to
have different origin-host value?
Is there any possible problem if the value of Diameter Identity (part of
recommended format for session-id) is different from those present in the
request (like origin-host/origin-realm)?

-- 
Regards,
Ajinkya Joshi