Return-Path: 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 F2A9128C17C for ; Thu, 6 May 2010 06:06:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] 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 AdwEZmNF3tu7 for ; Thu, 6 May 2010 06:06:12 -0700 (PDT) Received: from jaguar.aricent.com (jaguar.aricent.com [180.151.2.24]) by core3.amsl.com (Postfix) with ESMTP id 594893A6BC6 for ; Thu, 6 May 2010 06:04:09 -0700 (PDT) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 7BE7636B4C for ; Thu, 6 May 2010 18:29:42 +0530 (IST) Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (Postfix) with ESMTP id 66A3236B24 for ; Thu, 6 May 2010 18:29:42 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.130]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Thu, 6 May 2010 18:33:52 +0530 From: Vipul2 Aggarwal To: "dime@ietf.org" Date: Thu, 6 May 2010 18:33:51 +0530 Thread-Topic: Origin-State-Id AVP Thread-Index: AcrtHJMB/7tXid0FRu+wKP5L3x/O/Q== Message-ID: <082B8F090E42374E91BDB6571C58FF990228B245B0@GUREXMB01.ASIAN.AD.ARICENT.COM> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_082B8F090E42374E91BDB6571C58FF990228B245B0GUREXMB01ASIA_" MIME-Version: 1.0 Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2010 13:06:15 -0000 --_000_082B8F090E42374E91BDB6571C58FF990228B245B0GUREXMB01ASIA_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 in= cluded in any diameter message. Now, some diameter based application (like a 3GPP defined application) defi= nes new commands and in those commands' ABNF Origin-State-Id AVP is not pre= sent. Then does this imply that Origin-State-Id AVP MUST not be sent in these com= mands or it can be sent because RFC 3588 says it can be sent in any diamete= r 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 privi= leged 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 m= essage in error, please notify the originator immediately. If you are not t= he intended recipient, you are notified that you are strictly prohibited fr= om using, copying, altering, or disclosing the contents of this message. Ar= icent accepts no responsibility for loss or damage arising from the use of = the information transmitted by this email including damage from virus." --_000_082B8F090E42374E91BDB6571C58FF990228B245B0GUREXMB01ASIA_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

I have a query regarding usage of Origin-State-Id AVP in= Diameter.

 

The Diameter Base Protocol RFC 3588 says that Origin-Sta= te-Id AVP MAY be included in any diameter message.=

 

Now, some diameter based application (like a 3GPP define= d application) defines new commands and in those commands’ ABNF Origi= n-State-Id AVP is not present.

Then does this imply that Origin-State-Id AVP MUST not b= e 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 messa= ge is proprietary to Aricent and is intended solely for the use of the indi= vidual to whom it is addressed. It may contain privileged or confidential i= nformation and should not be circulated or used for any purpose other than for what it is intended. If you have recei= ved this message in error, please notify the originator immediately. If you= are not the intended recipient, you are notified that you are strictly pro= hibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibil= ity for loss or damage arising from the use of the information transmitted = by this email including damage from virus."
 --_000_082B8F090E42374E91BDB6571C58FF990228B245B0GUREXMB01ASIA_--