: Origin-State-Id AVP limitations
"German Blanco (E2/EEM)" <[email protected]> Mon, 9 Jan 2006 14:55:00 +0100
| Newsgroups | gmane.ietf.aaa |
|---|---|
| Message-ID | <7457D12699374F40BD026D2B1EFFBEC6175BD1@eesmdmw020.eemea.ericsson.se> |
This is a multi-part message in MIME format. ------_=_NextPart_001_01C61524.483AF39B Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hello, It seems to me that using Origin-State-Id AVP to indicate the shutdown of a Diameter client has some limitations that were not there for the Accounting On and Off in RADIUS. On one hand, there is no direct way to indicate an scheduled shutdown before it happens. Also, in order to send this AVP, a message is needed. That is OK for Diameter peers, since they will always send the CER/CEA when starting up, but when there is e.g. a Diameter Proxy between the access device and the Diameter server the information will be delayed without need. Is there a reason for not having a command in the Diameter protocol to do this? Thanks a lot for your help, German Blanco. ------_=_NextPart_001_01C61524.483AF39B Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.5.7232.84"> <TITLE>[AAA-WG]: Origin-State-Id AVP limitations</TITLE> </HEAD> <BODY> <!-- Converted from text/rtf format --> <BR> <P><FONT SIZE=3D2 FACE=3D"Arial">Hello,</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">It seems to me that using = Origin-State-Id AVP to indicate the shutdown of a Diameter client has = some limitations that were not there for the Accounting On and Off in = RADIUS.</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">On one hand, there is no direct way to = indicate an scheduled shutdown before it happens. Also, in order = to send this AVP, a message is needed. That is OK for Diameter = peers, since they will always send the CER/CEA when starting up, but = when there is e.g. a Diameter Proxy between the access device and the = Diameter server the information will be delayed without need.</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Is there a reason for not having a = command in the Diameter protocol to do this?</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Thanks a lot for your help,</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">German Blanco.</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C61524.483AF39B--