Re: [Dime] Origin-State-Id AVP

Jouni <jouni.nospam@gmail.com> Thu, 06 May 2010 18: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 2BA0B3A6A36 for <dime@core3.amsl.com>; Thu, 6 May 2010 11:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.733
X-Spam-Level:
X-Spam-Status: No, score=-0.733 tagged_above=-999 required=5 tests=[AWL=-0.548, BAYES_40=-0.185]
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 OEgUK26baIof for <dime@core3.amsl.com>; Thu, 6 May 2010 11:25:46 -0700 (PDT)
Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by core3.amsl.com (Postfix) with ESMTP id 7967528C160 for <dime@ietf.org>; Thu, 6 May 2010 11:22:58 -0700 (PDT)
Received: from a88-114-64-198.elisa-laajakaista.fi (a88-114-64-198.elisa-laajakaista.fi [88.114.64.198]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 7979D13961A; Thu, 6 May 2010 21:22:41 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="windows-1252"
From: Jouni <jouni.nospam@gmail.com>
In-Reply-To: <082B8F090E42374E91BDB6571C58FF990228B245B0@GUREXMB01.ASIAN.AD.ARICENT.COM>
Date: Thu, 06 May 2010 21:22:40 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <167B065D-8FC2-40AE-860B-4A42E8637ABF@gmail.com>
References: <082B8F090E42374E91BDB6571C58FF990228B245B0@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: Thu, 06 May 2010 18:25:48 -0000

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