Re: [Dime] #51: OC-Supported-Features in requests - conclusions

["TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <[e-mail]>]

Hi Anders

My understanding is that a reacting node puts OC-Supported-feature AVP in requests and reporting node put it in answers.

Then Overload control may also be used in the other way where the role of reacting and reporting node is exchanged. For example HSS can be a reporting node (as we want to address the HSS overload), MME being reacting. We can also have overload control in the other way, where MME is a reporting node (to address MME overload) towards HSS that is then the reacting node .
The two ways can be used simultaneously.
Furthermore, each way can use its own set of features/capabilities.

Best regards

JJacques 

  

-----Message d'origine-----
De : DiME [mailto:[e-mail]] De la part de Askerup, Anders
Envoyé : vendredi 21 février 2014 18:49
À : [e-mail]; Maria Cruz Bartolome; [e-mail]
Objet : Re: [Dime] #51: OC-Supported-Features in requests - conclusions

Lionel,

but issue #30 is about the Answer message isn't? My question is if a Server sending a Request message must it include the OC-Supported-Features AVP or not?

/Anders

-----Original Message-----
From: [e-mail] [mailto:[e-mail]]
Sent: Friday, February 21, 2014 11:30 AM
To: Askerup, Anders; Maria Cruz Bartolome; [e-mail]
Subject: RE: [Dime] #51: OC-Supported-Features in requests - conclusions

Hi Anders,

The clarification on the expected behavior of reporting node is covered in issue #30 :)

Lionel

-----Message d'origine-----
De : DiME [mailto:[e-mail]] De la part de Askerup, Anders Envoyé : vendredi 21 février 2014 18:20 À : Maria Cruz Bartolome; [e-mail] Objet : Re: [Dime] #51: OC-Supported-Features in requests - conclusions

Is the intent that it covers both the reporting nodes and reacting nodes, i.e. both Client and Server supporting DOIC must include the OC-Supported-Features AVP if they support DOIC?

/Anders  

-----Original Message-----
From: DiME [mailto:[e-mail]] On Behalf Of Maria Cruz Bartolome
Sent: Friday, February 21, 2014 3:23 AM
To: [e-mail]
Subject: Re: [Dime] #51: OC-Supported-Features in requests - conclusions

Yes, sorry about this, this was my understanding as well but I provided a wrong rephrasing.
My understanding is the following conclusions is reached:

#51: OC-Supported-Features in requests

 Now:
 The OC-Supported-Features AVP SHOULD be included into every Diameter  message a DOIC  supporting node sends (and intends to use for DOIC purposes).
 
Proposal:
The OC-Supported-Features AVP MUST be included into every Diameter request message a DOIC supporting node sends.


-----Original Message-----
From: Wiehe, Ulrich (NSN - DE/Munich) [mailto:[e-mail]]
Sent: viernes, 21 de febrero de 2014 10:19
To: Maria Cruz Bartolome; [e-mail]
Subject: RE: [Dime] #51: OC-Supported-Features in requests - conclusions

I do not agree
I think the conclusion was to say:
The OC-Supported-Features AVP MUST be included into every Diameter request message a DOIC supporting node sends.

For OC-Supported-Features AVP in answer messages refer to issue #30.

Ulrich  

-----Original Message-----
From: DiME [mailto:[e-mail]] On Behalf Of ext Maria Cruz Bartolome
Sent: Friday, February 21, 2014 9:35 AM
To: [e-mail]
Subject: [Dime] #51: OC-Supported-Features in requests - conclusions

#51: OC-Supported-Features in requests
 
My understanding is the following conclusions is reached:

 Now:
 The OC-Supported-Features AVP SHOULD be included into every Diameter  message a DOIC  supporting node sends (and intends to use for DOIC purposes).
 
Proposal:
replace SHOULD by MUST

_______________________________________________
DiME mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dime

_______________________________________________
DiME mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dime

_______________________________________________
DiME mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dime

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_______________________________________________
DiME mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dime