Re: [Dime] Application ID, Session Id and message flows

[Vipul2 Aggarwal <vipul2.aggarwal at aricent.com>]

Hi,

 

As far as I know, there is no RAR message in Sh Interface.

The messages supported in Sh Interface are

UDR/UDA

PUR/PUA

SNR/SNA

PNR/PNA

 

All these messages use the application ID of Sh.

 

Can you please elaborate more on the context of RAR in the Sh interface?

 

Regds,

Vipul Aggarwal

Senior Software Engineer

 

A R I C E N T

 

The Presidency Tower-A

351/2, Sector 14, M.G Road

Gurgaon, 122001,  Haryana, India

 

---

From: dime-bounces at ietf.org [mailto:dime-bounces at ietf.org] On Behalf Of Bartosz Baranowski
Sent: Friday, September 26, 2008 8:45 PM
To: dime at ietf.org
Subject: [Dime] Application ID, Session Id and message flows

 

Hi
Im trying to figure few things out for some time now and up until now I have been hearing contradicting voices wherever I turn myself.
I would like to know what are values of ApplicationID set in messages - Base messages used in context of Sh interface to Authanticate/Authorize user?

Lets consider flow like follows (not sure if its valid or not):




CLIENT                        

       SERVER(HSS ?)
     | -------------    UDR -----------------> |                             SesssionId_1, AppId_1 ==Sh
                           X
     | <-----------    RAR ------------------- |                             SessionId_2, AppId_2= Base
     | -------------    RAA -----------------> |                             SessionId_2, AppId_2= Base
     | -------------    UDR -----------------> |                             SesssionId_1, AppId_1 ==Sh
     | <-----------   UDA -------------------- |                             SesssionId_1, AppId_1 ==Sh


Does X indicates UDA denying access?
Is SessionId_1 equal to SessionId_2?
Is AppId_2== Base or is it equal to AppId_2 ?


Thanks

---

"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 at ietf.org
https://www.ietf.org/mailman/listinfo/dime