Re: [Dime] Origin-State-Id AVP
jouni korhonen <jouni.nospam@gmail.com> Fri, 07 May 2010 07:25 UTC
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C2933A6AD3 for <dime@core3.amsl.com>; Fri, 7 May 2010 00:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[AWL=0.720, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0JELfpzCXuuw for <dime@core3.amsl.com>; Fri, 7 May 2010 00:25:44 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by core3.amsl.com (Postfix) with ESMTP id 2D10A3A6C84 for <dime@ietf.org>; Fri, 7 May 2010 00:24:59 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id 22so1919840fge.13 for <dime@ietf.org>; Fri, 07 May 2010 00:24:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=CSofHS5nLjFYEyEzQe8MANArh7qaAYrMB4+RvJrpnOY=; b=BrSqxKdiYO2uqgUP5r79x6/miiMidfsFq4fGa1pQYGuYmNFw3bAWOfzdKbevtZabpp qvBiiYAA6bTq+d/abgQhGE40GS6AKXbOJraEInj6JzzB/ms+VBbLAgkgv6aVPehUM0eP UZhfov1Wb1XzlYLif+OOR+umQhXGduLEmqLW4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=B2sU8TKnJyy3DMo2C3eG/8kMostVavFFS2Jjsdme7vMQvFXKTYO/agvhV8W9DLQawU Hfb3RzDTHwd0dvZ7NEqHV/tw1tEIGv4hpzfOPZDq86d2Vc/Mp7nygoXHgs8GVGzBq0FX aVx3ZZB0MImZxXcsoksEArDeSg87bO7jpqJPg=
Received: by 10.87.63.1 with SMTP id q1mr3020832fgk.38.1273217084077; Fri, 07 May 2010 00:24:44 -0700 (PDT)
Received: from a88-114-64-208.elisa-laajakaista.fi (a88-114-64-208.elisa-laajakaista.fi [88.114.64.208]) by mx.google.com with ESMTPS id 1sm3529409fkt.41.2010.05.07.00.24.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 07 May 2010 00:24:42 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <082B8F090E42374E91BDB6571C58FF990228B246A9@GUREXMB01.ASIAN.AD.ARICENT.COM>
Date: Fri, 07 May 2010 10:24:40 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2DF89C0-8006-49A1-A4E7-643BA83DF1D9@gmail.com>
References: <082B8F090E42374E91BDB6571C58FF990228B245B0@GUREXMB01.ASIAN.AD.ARICENT.COM> <167B065D-8FC2-40AE-860B-4A42E8637ABF@gmail.com> <082B8F090E42374E91BDB6571C58FF990228B246A9@GUREXMB01.ASIAN.AD.ARICENT.COM>
To: Vipul2 Aggarwal <vipul2.aggarwal@aricent.com>
X-Mailer: Apple Mail (2.1078)
Cc: "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] Origin-State-Id AVP
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 07 May 2010 07:25:45 -0000
Hi, On May 7, 2010, at 8:36 AM, Vipul2 Aggarwal wrote: > Hi, > > Thanks Jouni for the clarification. > > I think now I need to take my query with 3GPP. > But, in case, anyone can help me here, I am describing my query below. > > ======================================================================== > I am specifically concerned about 3GPP S6a application defined in 29.272. > S6a is the interface between MME and HSS. > The Origin-State-Id AVP is not present in any of the 8 commands' ABNF defined in 29.272. However, there is *[AVP]. > So, I now know that Origin-State-Id AVP can theoretically come. Yes, it can. However, in this particular case my concern would be the content of M-bit. As S6a is based on base protocol, it would sound logical that S6a application should then understand RFC3588 AVPs with M-bit set. Based on the earlier experience on 3GPP interfaces such assumption would be rather risky though ;) > But, I doubt whether it is really required in S6a, as the Auth-Session-State AVP for S6a is NO_STATE_MAINTAINED i.e. no state information about a session is maintained? > Moreover, there is a Reset Request command from HSS to indicate to the MME about the restart of HSS. > So, I think Origin-State-Id AVP is not required in S6a Application. Does anyone have different views? There are people here who are familiar with S6a (and basically the whole plethora of 3GPP Diameter interfaces). However, the question as such is rather specific to 3GPP, especially as the S6a *is* a 3GPP vendor specific application. We really don't have much control over it. So I advice you to bring your question to 3GPP CT4 mailing list (http://list.etsi.org/3gpp_tsg_ct_wg4.html) and ask there. - Jouni > ======================================================================== > > Thanks n Regds, > Vipul > > -----Original Message----- > From: Jouni [mailto:jouni.nospam@gmail.com] > Sent: Thursday, May 06, 2010 11:53 PM > To: Vipul2 Aggarwal > Cc: dime@ietf.org > Subject: Re: [Dime] Origin-State-Id AVP > > Hi, > > Eventually it is up to the command ABNF. If the command ABNF has *[AVP] then including Origin-State-Id AVP is ok. > > - Jouni > > > On May 6, 2010, at 4:03 PM, Vipul2 Aggarwal wrote: > >> Hi, >> >> I have a query regarding usage of Origin-State-Id AVP in Diameter. >> >> The Diameter Base Protocol RFC 3588 says that Origin-State-Id AVP MAY be included in any diameter message. >> >> Now, some diameter based application (like a 3GPP defined application) defines new commands and in those commands' ABNF Origin-State-Id AVP is not present. >> Then does this imply that Origin-State-Id AVP MUST not be sent in these commands or it can be sent because RFC 3588 says it can be sent in any diameter message? >> >> Thanks n Regards, >> Vipul Aggarwal >> ARICENT >> Gurgaon >> India >> >> >> "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." >> _______________________________________________ >> DiME mailing list >> DiME@ietf.org >> https://www.ietf.org/mailman/listinfo/dime > > > "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
- [Dime] Origin-State-Id AVP Vipul2 Aggarwal
- Re: [Dime] Origin-State-Id AVP Jouni
- Re: [Dime] Origin-State-Id AVP Vipul2 Aggarwal
- Re: [Dime] Origin-State-Id AVP jouni korhonen