Re: [Dime] Diameter basics and Apps questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Dime] Diameter basics and Apps questions
Inline...
Bartosz Baranowski wrote:
Hi. I have few questions about diameter base protocol ( and overall
diameter ) , avp values and some app questions ( Sh interface ).
I got through TS's and rfc but thats plain technical knowledge, no
examples, no place to start with.
If someone could enlighten me i would be grateful.
So here it goes.
Is session always estabilished? According to TS's and rfc Session-Id is
required AVP, but for instance Sh messages look a lot like
request-reposnse oriented ( Session-Id is required AVP ) Sh doesnt have
any means to estabilish session. Each time server receives request it
checks if requesting enity has access to requested service/information.
Or maybe session is estabilished only by sending request with session-id ??
The Session-Id is required in the messages but, I believe, is generally
not used for anything. The client should just populate it with some
random but valid value.
what is corellation between header value of application Id and
Auth-Application-Id and Acc-Application-Id ?? And Vendor-Specific-App-Id?
If header value of application_id is Sh# does this imply that
Auth-App-Id or Acc-App-id in Vendor-Spec-app-id will have Sh# value? (
Does it work the same for not grouped Auth-App-Id and Acc-App-id )
This is, in my view, a really sore point for Diameter. Specifically for
Sh it seems pretty clear that the Sh app ID should go into both the
message header and an Auth-Application-Id AVP within a
Vendor-Specific-Application-Id but in general there doesn't seem to be a
satisfying answer to your question.
Anders
Regards
--
Bartosz Baranowski
------------------------------------------------------------------------
_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime
_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.