From: Vipul2 Aggarwal <vipul2.aggarwal@aricent.com>
To: Jouni <jouni.nospam@gmail.com>
Date: Fri, 7 May 2010 11:06:49 +0530
Thread-Topic: [Dime] Origin-State-Id AVP
Thread-Index: AcrtSSHr04+FVwroSNO+vX4fwWJMYAAXHHMg
Message-ID: <082B8F090E42374E91BDB6571C58FF990228B246A9@GUREXMB01.ASIAN.AD.ARICENT.COM>
References: <082B8F090E42374E91BDB6571C58FF990228B245B0@GUREXMB01.ASIAN.AD.ARICENT.COM>
 <167B065D-8FC2-40AE-860B-4A42E8637ABF@gmail.com>
In-Reply-To: <167B065D-8FC2-40AE-860B-4A42E8637ABF@gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] Origin-State-Id AVP
Precedence: list

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.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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 defin=
ed in 29.272. However, there is *[AVP].
So, I now know that Origin-State-Id AVP can theoretically come.
But, I doubt whether it is really required in S6a, as the Auth-Session-Stat=
e AVP for S6a is NO_STATE_MAINTAINED i.e. no state information about a sess=
ion 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 an=
yone have different views?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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] the=
n 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) de=
fines new commands and in those commands' ABNF Origin-State-Id AVP is not p=
resent.
> Then does this imply that Origin-State-Id AVP MUST not be sent in these c=
ommands or it can be sent because RFC 3588 says it can be sent in any diame=
ter message?
>
> Thanks n Regards,
> Vipul Aggarwal
> ARICENT
> Gurgaon
> India
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solel=
y for the use of the individual to whom it is addressed. It may contain pri=
vileged or confidential information and should not be circulated or used fo=
r 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 o=
f 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 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."