You might want to try the Open Diameter wiki: = http://www.opendiameter.org/&nb= sp;and if=20 you can't find your answers there, you can join the open diameter = mailing=20 list:

= http://lists.sourceforge.net/lists/listinfo/diameter-developers.
<= /DIV>

John

From: owner-aaa-wg@merit.edu=20 [mailto:owner-aaa-wg@merit.edu] On Behalf Of ext=20 darshak
Sent: 17 June, 2006 09:41
To:=20 aaa-wg@merit.edu
Subject: [AAA-WG]: Dimeter=20 installation

Hi

I m new to Diameter.I have installed=20 opendiameter-1.0.7-h

But I dont know how to start/stop = it.How to=20 integrate it with other RADIUS/DIAMTER applications.

when i try to start aaad i got this=20 error

aaad: error while loading shared = libraries:=20 libACE_SSL.so.5

But this file is there in = DIAMETER_HOME folder=20 and /usr/lib.

Can any1 tell me the problem =

Thnxs in=20 advance

------_=_NextPart_001_01C6922F.88AA8C3F-- From owner-aaa-wg@merit.edu Wed Jun 21 11:23:54 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft4Yc-0001IO-Ev for aaa-archive@lists.ietf.org; Wed, 21 Jun 2006 11:23:54 -0400 Received: from trapdoor.merit.edu ([198.108.1.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ft4Yb-0008JH-2J for aaa-archive@lists.ietf.org; Wed, 21 Jun 2006 11:23:54 -0400 Received: by trapdoor.merit.edu (Postfix) id 823FC9123A; Wed, 21 Jun 2006 11:23:44 -0400 (EDT) Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 51F679123F; Wed, 21 Jun 2006 11:23:44 -0400 (EDT) Delivered-To: aaa-wg@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 132AA9123A for ; Wed, 21 Jun 2006 11:23:43 -0400 (EDT) Received: by segue.merit.edu (Postfix) id ED3F558287; Wed, 21 Jun 2006 11:23:42 -0400 (EDT) Delivered-To: aaa-wg@segue.merit.edu Received: from fiji.merit.edu (fiji.merit.edu [198.108.1.12]) by segue.merit.edu (Postfix) with ESMTP id ABFF258280 for ; Wed, 21 Jun 2006 11:23:42 -0400 (EDT) Received: by fiji.merit.edu (Postfix) id AD802C46; Wed, 21 Jun 2006 11:23:42 -0400 (EDT) Delivered-To: aaa-wg@merit.edu Received: from fiji.merit.edu ([127.0.0.1]) by localhost (fiji.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24352-04 for ; Wed, 21 Jun 2006 11:23:42 -0400 (EDT) X-Greylist: delayed 3550 seconds by postgrey-1.21 at fiji.merit.edu; Wed, 21 Jun 2006 11:23:42 EDT Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by fiji.merit.edu (Postfix) with ESMTP id 48CCB698 for ; Wed, 21 Jun 2006 11:23:42 -0400 (EDT) Received: from c-24-16-73-85.hsd1.wa.comcast.net ([24.16.73.85] helo=internaut.com) by outbound.mailhop.org with esmtpa (Exim 4.51) id 1Ft3d3-000Elj-KL; Wed, 21 Jun 2006 10:24:25 -0400 Received: by internaut.com (Postfix, from userid 1000) id 8080D56941; Wed, 21 Jun 2006 07:24:24 -0700 (PDT) X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 24.16.73.85 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: aboba Date: Wed, 21 Jun 2006 07:24:24 -0700 (PDT) From: Bernard Aboba To: "Pat Calhoun (pacalhou)" Cc: MORAND Lionel RD-CORE-ISS , aaa-wg@merit.edu Subject: [AAA-WG]: RE: Conclusions on the draft "Resource Management Extensions" In-Reply-To: <4FF84B0BC277FF45AA27FE969DD956A202108C57@xmb-sjc-235.amer.cisco.com> Message-ID: References: <4FF84B0BC277FF45AA27FE969DD956A202108C57@xmb-sjc-235.amer.cisco.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: amavisd-new at merit.edu Sender: owner-aaa-wg@merit.edu Precedence: bulk X-Spam-Score: 0.1 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 As Pat said, the major priority of the AAA WG was completing work on the Diameter Base protocol and applications. I actually don't recall whether the WG made a judgement on the Resource Management draft; it just wasn't one of the top priorities. I will say that the Diameter architecture provides a much more sound base for resource management than RADIUS does. Most of the resource management implementations I have seen on RADIUS need to incorporate other information sources for validation, in order to deal with potential losses of RADIUS Accounting packets. Since Diameter runs over reliable transport, it should not have to do this. On Wed, 21 Jun 2006, Pat Calhoun (pacalhou) wrote: > I'll let Bernard speak for the WG, but at the time the WG had many other > priorities, and resource management was not one of them. However, I > haven't had the opportunity to participate in the AAA WG for some time, > so I'm not sure if this could be an opportune time to re-introduce it. > > > Pat Calhoun > CTO, Wireless Networking Business Unit > Cisco Systems > > > > > ________________________________ > > From: MORAND Lionel RD-CORE-ISS > [mailto:lionel.morand@orange-ft.com] > Sent: Wednesday, June 21, 2006 7:07 AM > To: Bernard Aboba; Pat Calhoun (pacalhou) > Subject: Conclusions on the draft "Resource Management > Extensions" > > > > Hi, > I would like to know what were the conclusions on the following > draft initiated by Pat: draft-calhoun-diameter-res-mgmt-08.txt. > (http://quimby.gnus.org/internet-drafts/draft-calhoun-diameter-res-mgmt- > 08.txt > 08.txt> ) > > Some folks from TISPAN are initiating a document based on this > draft to perform resource management after failover, proposing to > enhance the Diameter base protocol with dedicated commands. I'm pretty > sure that the previous comments/concerns about such enhancements are > still valid. > > BR, > Lionel > > > From owner-aaa-wg@merit.edu Wed Jun 21 12:11:34 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft5Ik-00088q-8v for aaa-archive@lists.ietf.org; Wed, 21 Jun 2006 12:11:34 -0400 Received: from trapdoor.merit.edu ([198.108.1.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ft5Ii-0004IT-SC for aaa-archive@lists.ietf.org; Wed, 21 Jun 2006 12:11:34 -0400 Received: by trapdoor.merit.edu (Postfix) id F226B91285; Wed, 21 Jun 2006 12:11:26 -0400 (EDT) Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id C172A912A5; Wed, 21 Jun 2006 12:11:25 -0400 (EDT) Delivered-To: aaa-wg@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 3C05B91285 for ; Wed, 21 Jun 2006 12:11:24 -0400 (EDT) Received: by segue.merit.edu (Postfix) id 2A15758287; Wed, 21 Jun 2006 12:11:24 -0400 (EDT) Delivered-To: aaa-wg@segue.merit.edu Received: from fiji.merit.edu (fiji.merit.edu [198.108.1.12]) by segue.merit.edu (Postfix) with ESMTP id DA33B58280 for ; Wed, 21 Jun 2006 12:11:23 -0400 (EDT) Received: by fiji.merit.edu (Postfix) id DE808C46; Wed, 21 Jun 2006 12:11:23 -0400 (EDT) Delivered-To: aaa-wg@merit.edu Received: from fiji.merit.edu ([127.0.0.1]) by localhost (fiji.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25558-05 for ; Wed, 21 Jun 2006 12:11:23 -0400 (EDT) X-Greylist: delayed 1985 seconds by postgrey-1.21 at fiji.merit.edu; Wed, 21 Jun 2006 12:11:23 EDT Received: from lizzard.sbs.de (lizzard.sbs.de [194.138.37.39]) by fiji.merit.edu (Postfix) with ESMTP id 18423B02 for ; Wed, 21 Jun 2006 12:11:22 -0400 (EDT) Received: from mail1.sbs.de (localhost [127.0.0.1]) by lizzard.sbs.de (8.12.6/8.12.6) with ESMTP id k5LFbuPP003720; Wed, 21 Jun 2006 17:37:56 +0200 Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net [157.163.133.222]) by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id k5LFbtge010528; Wed, 21 Jun 2006 17:37:55 +0200 Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.145]) by fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jun 2006 17:37:55 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: AW: [AAA-WG]: RE: Conclusions on the draft "Resource Management Extensions" Date: Wed, 21 Jun 2006 17:32:59 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [AAA-WG]: RE: Conclusions on the draft "Resource Management Extensions" Thread-Index: AcaVRs1ljFlPl29LSB+fntasVgkaCAAAIs9g From: "Tschofenig, Hannes" To: "Bernard Aboba" , "Pat Calhoun (pacalhou)" Cc: "MORAND Lionel RD-CORE-ISS" , , X-OriginalArrivalTime: 21 Jun 2006 15:37:55.0371 (UTC) FILETIME=[AA48A7B0:01C69548] X-Virus-Scanned: amavisd-new at merit.edu Sender: owner-aaa-wg@merit.edu Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Hi all,=20 may I raise your attention to the following draft submitted for this = meeting. Requirement for the addition of Auditing Functionality to Diameter http://psg.com/~avri/dime/draft-bodin-dime-auditing-reqs-00.txt Unfortunately, it did not yet show up.=20 Ciao Hannes > -----Urspr=FCngliche Nachricht----- > Von: owner-aaa-wg@merit.edu [mailto:owner-aaa-wg@merit.edu]=20 > Im Auftrag von Bernard Aboba > Gesendet: Mittwoch, 21. Juni 2006 16:24 > An: Pat Calhoun (pacalhou) > Cc: MORAND Lionel RD-CORE-ISS; aaa-wg@merit.edu > Betreff: [AAA-WG]: RE: Conclusions on the draft "Resource=20 > Management Extensions" >=20 > As Pat said, the major priority of the AAA WG was completing=20 > work on the=20 > Diameter Base protocol and applications. I actually don't=20 > recall whether=20 > the WG made a judgement on the Resource Management draft; it=20 > just wasn't=20 > one of the top priorities.=20 >=20 > I will say that the Diameter architecture provides a much more sound=20 > base for resource management than RADIUS does. Most of the resource=20 > management implementations I have seen on RADIUS need to=20 > incorporate other=20 > information sources for validation, in order to deal with=20 > potential losses=20 > of RADIUS Accounting packets. Since Diameter runs over reliable=20 > transport, it should not have to do this.=20 >=20 > On Wed, 21 Jun 2006, Pat Calhoun (pacalhou) wrote: >=20 > > I'll let Bernard speak for the WG, but at the time the WG=20 > had many other > > priorities, and resource management was not one of them. However, I > > haven't had the opportunity to participate in the AAA WG=20 > for some time, > > so I'm not sure if this could be an opportune time to=20 > re-introduce it. > > =20 > >=20 > > Pat Calhoun > > CTO, Wireless Networking Business Unit > > Cisco Systems > >=20 > > =20 > >=20 > >=20 > > ________________________________ > >=20 > > From: MORAND Lionel RD-CORE-ISS > > [mailto:lionel.morand@orange-ft.com]=20 > > Sent: Wednesday, June 21, 2006 7:07 AM > > To: Bernard Aboba; Pat Calhoun (pacalhou) > > Subject: Conclusions on the draft "Resource Management > > Extensions" > > =09 > > =09 > >=20 > > Hi,=20 > > I would like to know what were the conclusions on the following > > draft initiated by Pat: draft-calhoun-diameter-res-mgmt-08.txt. > >=20 > (http://quimby.gnus.org/internet-drafts/draft-calhoun-diameter > -res-mgmt- > > 08.txt > >=20 > -res-mgmt- > > 08.txt> ) > >=20 > > Some folks from TISPAN are initiating a document based on this > > draft to perform resource management after failover, proposing to > > enhance the Diameter base protocol with dedicated commands.=20 > I'm pretty > > sure that the previous comments/concerns about such enhancements are > > still valid. > >=20 > > BR,=20 > > Lionel=20 > >=20 > >=20 > >=20 >=20 From owner-aaa-wg@merit.edu Wed Jun 21 12:51:01 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft5uv-0000bt-62 for aaa-archive@lists.ietf.org; Wed, 21 Jun 2006 12:51:01 -0400 Received: from trapdoor.merit.edu ([198.108.1.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ft5h9-0006fS-Qm for aaa-archive@lists.ietf.org; Wed, 21 Jun 2006 12:36:49 -0400 Received: by trapdoor.merit.edu (Postfix) id B351F912A5; Wed, 21 Jun 2006 12:36:39 -0400 (EDT) Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 7A84C912A6; Wed, 21 Jun 2006 12:36:39 -0400 (EDT) Delivered-To: aaa-wg@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id ED444912A5 for ; Wed, 21 Jun 2006 12:36:37 -0400 (EDT) Received: by segue.merit.edu (Postfix) id DE03058287; Wed, 21 Jun 2006 12:36:37 -0400 (EDT) Delivered-To: aaa-wg@segue.merit.edu Received: from fiji.merit.edu (fiji.merit.edu [198.108.1.12]) by segue.merit.edu (Postfix) with ESMTP id 9BEE858280 for ; Wed, 21 Jun 2006 12:36:37 -0400 (EDT) Received: by fiji.merit.edu (Postfix) id 7FB50C1B; Wed, 21 Jun 2006 12:36:37 -0400 (EDT) Delivered-To: aaa-wg@merit.edu Received: from fiji.merit.edu ([127.0.0.1]) by localhost (fiji.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26150-08 for ; Wed, 21 Jun 2006 12:36:37 -0400 (EDT) Received: from bw.ulticom.com (bw.ulticom.com [208.255.120.38]) by fiji.merit.edu (Postfix) with ESMTP id EAE57599 for ; Wed, 21 Jun 2006 12:36:36 -0400 (EDT) Received: from colby.ulticom.com (colby.ulticom.com [192.73.206.10]) by bw.ulticom.com (BorderWare MXtreme Mail Firewall) with ESMTP id 99E34D2F3A; Wed, 21 Jun 2006 12:36:35 -0400 (EDT) Received: from pcasveren (pc-asveren.ulticom.com [172.25.33.55]) by colby.ulticom.com (8.13.4/8.12.10) with SMTP id k5LGaYeL016433; Wed, 21 Jun 2006 12:36:34 -0400 (EDT) From: "Tolga Asveren" To: , Subject: RE: [Dime] AW: [AAA-WG]: RE: Conclusions on the draft "ResourceManagement Extensions" Date: Wed, 21 Jun 2006 12:13:15 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 In-reply-to: Importance: Normal Received-SPF: pass X-Virus-Scanned: amavisd-new at merit.edu Sender: owner-aaa-wg@merit.edu Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da A few quick questions/comments about this interesting draft: 1) 2.1 If there is no synchronization on client side, wouldn't using Origin-State-Id AVP (RFC3588 8.16)solve the problem described in this section? After failure/restart/takeover client can populate Origin-state-Id AVP with a value bigger than the one used before the failure and server should clean up previous sessions. 2) 2.1.1 SCTP multi-homing does not provide host redundancy -unless one has a distributed SCTP implementation, which probably is not realistic or something I would recomend to anybody- 3) 2.1.1 Is mentioning about IP address takeover really necessary? IMO, Diameter entities are addressed by Diameter Identities, hence what is important is that a backup assuming the identity of a failed active instance -which doesn't require IP takeover-. 4) As a generic comment, I always thought this type of functionality is to be addressed by specific applications themselves, e.g. DCCA, if there is such a need. Let's consider DCCA: When there is an open session, client will send from time to time CCR(Update) or CCR(Terminate), which would be replied with "DIAMETER UNKNOWN SESSION ID", if server failed/restarted etc... and corresponding state did not survive. Upon receipt of such an error answer, client can clean up its own state for this session. Similarly server can send RAR to client, if CCR(Update) is not received in a timely manner. If state did not survive on client side after a failure, client would reply with "DIAMETER UNKNOWN SESSION ID" and server can clean up session state (Alternatively server may choose not to send RAR and may abort the session) AFAICS, for the above example, all cases are covered. The question is, whose responsibility is that type of fucntionality, base protocol or applications. Thanks, Tolga > -----Original Message----- > From: Tschofenig, Hannes [mailto:hannes.tschofenig@siemens.com] > Sent: Wednesday, June 21, 2006 11:33 AM > To: Bernard Aboba; Pat Calhoun (pacalhou) > Cc: aaa-wg@merit.edu; dime@ietf.org > Subject: [Dime] AW: [AAA-WG]: RE: Conclusions on the draft > "ResourceManagement Extensions" > > > Hi all, > > may I raise your attention to the following draft submitted for > this meeting. > > Requirement for the addition of Auditing Functionality to Diameter > http://psg.com/~avri/dime/draft-bodin-dime-auditing-reqs-00.txt > > Unfortunately, it did not yet show up. > > Ciao > Hannes From owner-aaa-wg@merit.edu Wed Jun 21 23:12:03 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtFbv-0000X7-Oy for aaa-archive@lists.ietf.org; Wed, 21 Jun 2006 23:12:03 -0400 Received: from trapdoor.merit.edu ([198.108.1.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtFbu-0006NM-Do for aaa-archive@lists.ietf.org; Wed, 21 Jun 2006 23:12:03 -0400 Received: by trapdoor.merit.edu (Postfix) id B4D9B912C3; Wed, 21 Jun 2006 23:11:53 -0400 (EDT) Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 84074912C4; Wed, 21 Jun 2006 23:11:53 -0400 (EDT) Delivered-To: aaa-wg@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id C01E7912C3 for ; Wed, 21 Jun 2006 23:11:51 -0400 (EDT) Received: by segue.merit.edu (Postfix) id ADBA558289; Wed, 21 Jun 2006 23:11:51 -0400 (EDT) Delivered-To: aaa-wg@segue.merit.edu Received: from fiji.merit.edu (fiji.merit.edu [198.108.1.12]) by segue.merit.edu (Postfix) with ESMTP id 6DB6F58287 for ; Wed, 21 Jun 2006 23:11:51 -0400 (EDT) Received: by fiji.merit.edu (Postfix) id 510A9599; Wed, 21 Jun 2006 23:11:51 -0400 (EDT) Delivered-To: aaa-wg@merit.edu Received: from fiji.merit.edu ([127.0.0.1]) by localhost (fiji.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07967-06 for ; Wed, 21 Jun 2006 23:11:51 -0400 (EDT) Received: from mgw-ext13.nokia.com (mgw-ext13.nokia.com [131.228.20.172]) by fiji.merit.edu (Postfix) with ESMTP id 9BA0B55F for ; Wed, 21 Jun 2006 23:11:50 -0400 (EDT) Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k5M3Bfn5022452; Thu, 22 Jun 2006 06:11:41 +0300 Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Jun 2006 06:11:40 +0300 Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Jun 2006 06:11:40 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [AAA-WG]: RE: Conclusions on the draft "Resource Management Extensions" Date: Thu, 22 Jun 2006 06:11:40 +0300 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [AAA-WG]: RE: Conclusions on the draft "Resource Management Extensions" Thread-Index: AcaVR7cqZap4AUoPTLWUB+OuD//ieQAYbjyg From: To: , Cc: , , X-OriginalArrivalTime: 22 Jun 2006 03:11:40.0571 (UTC) FILETIME=[94D61EB0:01C695A9] X-Virus-Scanned: amavisd-new at merit.edu Sender: owner-aaa-wg@merit.edu Precedence: bulk X-Spam-Score: 0.2 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Hi all, I think that if there is interest, why not recycle the draft, and we can discuss it on the DiME mailing list. If you are able to rev it before Monday, it can be discussed in Montreal. John =20 >-----Original Message----- >From: owner-aaa-wg@merit.edu [mailto:owner-aaa-wg@merit.edu]=20 >On Behalf Of ext Bernard Aboba >Sent: 21 June, 2006 17:24 >To: Pat Calhoun (pacalhou) >Cc: MORAND Lionel RD-CORE-ISS; aaa-wg@merit.edu >Subject: [AAA-WG]: RE: Conclusions on the draft "Resource=20 >Management Extensions" > >As Pat said, the major priority of the AAA WG was completing=20 >work on the Diameter Base protocol and applications. I=20 >actually don't recall whether the WG made a judgement on the=20 >Resource Management draft; it just wasn't one of the top priorities.=20 > >I will say that the Diameter architecture provides a much more=20 >sound base for resource management than RADIUS does. Most of=20 >the resource management implementations I have seen on RADIUS=20 >need to incorporate other information sources for validation,=20 >in order to deal with potential losses of RADIUS Accounting=20 >packets. Since Diameter runs over reliable transport, it=20 >should not have to do this.=20 > >On Wed, 21 Jun 2006, Pat Calhoun (pacalhou) wrote: > >> I'll let Bernard speak for the WG, but at the time the WG had many=20 >> other priorities, and resource management was not one of them.=20 >> However, I haven't had the opportunity to participate in the AAA WG=20 >> for some time, so I'm not sure if this could be an opportune=20 >time to re-introduce it. >> =20 >>=20 >> Pat Calhoun >> CTO, Wireless Networking Business Unit Cisco Systems >>=20 >> =20 >>=20 >>=20 >> ________________________________ >>=20 >> From: MORAND Lionel RD-CORE-ISS >> [mailto:lionel.morand@orange-ft.com]=20 >> Sent: Wednesday, June 21, 2006 7:07 AM >> To: Bernard Aboba; Pat Calhoun (pacalhou) >> Subject: Conclusions on the draft "Resource Management=20 >Extensions" >> =09 >> =09 >>=20 >> Hi,=20 >> I would like to know what were the conclusions on the=20 >following draft=20 >> initiated by Pat: draft-calhoun-diameter-res-mgmt-08.txt. >>=20 >(http://quimby.gnus.org/internet-drafts/draft-calhoun-diameter-res-mgm >> t- >> 08.txt >>=20 >> t- >> 08.txt> ) >>=20 >> Some folks from TISPAN are initiating a document based=20 >on this draft=20 >> to perform resource management after failover, proposing to enhance=20 >> the Diameter base protocol with dedicated commands. I'm pretty sure=20 >> that the previous comments/concerns about such enhancements=20 >are still=20 >> valid. >>=20 >> BR,=20 >> Lionel >>=20 >>=20 >>=20 > From owner-aaa-wg@merit.edu Fri Jun 23 23:25:56 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtymS-0005p0-5v for aaa-archive@lists.ietf.org; Fri, 23 Jun 2006 23:25:56 -0400 Received: from trapdoor.merit.edu ([198.108.1.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtymP-0004t1-PL for aaa-archive@lists.ietf.org; Fri, 23 Jun 2006 23:25:56 -0400 Received: by trapdoor.merit.edu (Postfix) id 44DA691211; Fri, 23 Jun 2006 23:25:45 -0400 (EDT) Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 10727912E0; Fri, 23 Jun 2006 23:25:44 -0400 (EDT) Delivered-To: aaa-wg@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id A352491211 for ; Fri, 23 Jun 2006 23:25:43 -0400 (EDT) Received: by segue.merit.edu (Postfix) id 8788F5828B; Fri, 23 Jun 2006 23:25:43 -0400 (EDT) Delivered-To: aaa-wg@segue.merit.edu Received: from fiji.merit.edu (fiji.merit.edu [198.108.1.12]) by segue.merit.edu (Postfix) with ESMTP id 737D358283 for ; Fri, 23 Jun 2006 23:25:43 -0400 (EDT) Received: by fiji.merit.edu (Postfix) id 56D9012DC; Fri, 23 Jun 2006 23:25:43 -0400 (EDT) Delivered-To: aaa-wg@merit.edu Received: from fiji.merit.edu ([127.0.0.1]) by localhost (fiji.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19585-07 for ; Fri, 23 Jun 2006 23:25:42 -0400 (EDT) X-Greylist: delayed 606 seconds by postgrey-1.21 at fiji.merit.edu; Fri, 23 Jun 2006 23:25:38 EDT Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [61.144.161.55]) by fiji.merit.edu (Postfix) with ESMTP id 4EE31AEB for ; Fri, 23 Jun 2006 23:25:38 -0400 (EDT) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J1C006C9HH2HF@szxga03-in.huawei.com> for aaa-wg@merit.edu; Sat, 24 Jun 2006 11:24:38 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J1C002YBHH2HJ@szxga03-in.huawei.com> for aaa-wg@merit.edu; Sat, 24 Jun 2006 11:24:38 +0800 (CST) Received: from z26452a ([10.70.145.55]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J1C00HFYH4DN9@szxml03-in.huawei.com> for aaa-wg@merit.edu; Sat, 24 Jun 2006 11:17:02 +0800 (CST) Date: Sat, 24 Jun 2006 11:15:19 +0800 From: Tony Zhang Subject: Re: [Dime] AW: [AAA-WG]: RE: Conclusions on the draft"ResourceManagement Extensions" To: Tolga Asveren , dime@ietf.org, aaa-wg@merit.edu Message-id: <000b01c6973c$6c912000$3791460a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Mailer: Microsoft Outlook Express 6.00.2800.1106 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: X-Virus-Scanned: amavisd-new at merit.edu Sender: owner-aaa-wg@merit.edu Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 HI All: some querys: 1)if Failover,both nodes share same Host name or not.if use different Host name,how to route the message. if share both Host name,maybe establish connects connect two node is ok. 2)after audit,should restore the session state or not,In the case of failover without replication if want restore the sesssion,how long will be permit. a few minustes or hours. 3)should server or client,save some transparent data on each other. 4)session state synchronization maybe is mandatory,but only check the session active or not maybe is simply,if want restore session state then it will complex. Thanks Tony some comments see inline: ----- Original Message ----- From: "Tolga Asveren" To: ; Sent: Thursday, June 22, 2006 12:13 AM Subject: RE: [Dime] AW: [AAA-WG]: RE: Conclusions on the draft"ResourceManagement Extensions" > A few quick questions/comments about this interesting draft: > > 1) 2.1 > If there is no synchronization on client side, wouldn't using > Origin-State-Id AVP (RFC3588 8.16)solve the problem described in this > section? After failure/restart/takeover client can populate Origin-state-Id > AVP with a value bigger than the one used before the failure and server > should clean up previous sessions. [Tony]Origina-State-Id AVP maybe only use for check the session state synchronization or not. cannot use for state recovery > > 2) 2.1.1 > SCTP multi-homing does not provide host redundancy -unless one has a > distributed SCTP implementation, which probably is not realistic or > something I would recomend to anybody- > > 3) 2.1.1 > Is mentioning about IP address takeover really necessary? IMO, Diameter > entities are addressed by Diameter Identities, hence what is important is > that a backup assuming the identity of a failed active instance -which > doesn't require IP takeover-. > > 4) As a generic comment, I always thought this type of functionality is to > be addressed by specific applications themselves, e.g. DCCA, if there is > such a need. > Let's consider DCCA: > When there is an open session, client will send from time to time > CCR(Update) or CCR(Terminate), which would be replied with "DIAMETER UNKNOWN > SESSION ID", if server failed/restarted etc... and corresponding state did > not survive. Upon receipt of such an error answer, client can clean up its > own state for this session. > Similarly server can send RAR to client, if CCR(Update) is not received in a > timely manner. If state did not survive on client side after a failure, > client would reply with "DIAMETER UNKNOWN SESSION ID" and server can clean > up session state (Alternatively server may choose not to send RAR and may > abort the session) > > AFAICS, for the above example, all cases are covered. > > The question is, whose responsibility is that type of fucntionality, base > protocol or applications. > > Thanks, > Tolga > > > -----Original Message----- > > From: Tschofenig, Hannes [mailto:hannes.tschofenig@siemens.com] > > Sent: Wednesday, June 21, 2006 11:33 AM > > To: Bernard Aboba; Pat Calhoun (pacalhou) > > Cc: aaa-wg@merit.edu; dime@ietf.org > > Subject: [Dime] AW: [AAA-WG]: RE: Conclusions on the draft > > "ResourceManagement Extensions" > > > > > > Hi all, > > > > may I raise your attention to the following draft submitted for > > this meeting. > > > > Requirement for the addition of Auditing Functionality to Diameter > > http://psg.com/~avri/dime/draft-bodin-dime-auditing-reqs-00.txt > > > > Unfortunately, it did not yet show up. > > > > Ciao > > Hannes > > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www1.ietf.org/mailman/listinfo/dime > From owner-aaa-wg@merit.edu Sun Jun 25 21:36:41 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fug1p-000778-NT for aaa-archive@lists.ietf.org; Sun, 25 Jun 2006 21:36:41 -0400 Received: from trapdoor.merit.edu ([198.108.1.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fug1o-0001Gk-D3 for aaa-archive@lists.ietf.org; Sun, 25 Jun 2006 21:36:41 -0400 Received: by trapdoor.merit.edu (Postfix) id B51409124A; Sun, 25 Jun 2006 21:35:21 -0400 (EDT) Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 8497091257; Sun, 25 Jun 2006 21:35:21 -0400 (EDT) Delivered-To: aaa-wg@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 59E759124A for ; Sun, 25 Jun 2006 21:35:17 -0400 (EDT) Received: by segue.merit.edu (Postfix) id 3DC7F58293; Sun, 25 Jun 2006 21:35:17 -0400 (EDT) Delivered-To: aaa-wg@segue.merit.edu Received: from fiji.merit.edu (fiji.merit.edu [198.108.1.12]) by segue.merit.edu (Postfix) with ESMTP id 2A2B158282 for ; Sun, 25 Jun 2006 21:35:17 -0400 (EDT) Received: by fiji.merit.edu (Postfix) id 0BDCD17E0; Sun, 25 Jun 2006 21:35:17 -0400 (EDT) Delivered-To: aaa-wg@merit.edu Received: from fiji.merit.edu ([127.0.0.1]) by localhost (fiji.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19405-02 for ; Sun, 25 Jun 2006 21:35:16 -0400 (EDT) Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by fiji.merit.edu (Postfix) with ESMTP id 89C8317D8 for ; Sun, 25 Jun 2006 21:35:16 -0400 (EDT) Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-4.cisco.com with ESMTP; 25 Jun 2006 18:35:16 -0700 X-IronPort-AV: i="4.06,173,1149490800"; d="scan'208"; a="1832360476:sNHT36108862" Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k5Q1ZFuX001141; Sun, 25 Jun 2006 18:35:15 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k5Q1ZFCU011372; Sun, 25 Jun 2006 18:35:15 -0700 (PDT) Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 25 Jun 2006 18:35:15 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: [AAA-WG]: RE: [Dime] RE: Diameter base protocol messages used by DCCA Date: Sun, 25 Jun 2006 18:35:13 -0700 Message-ID: <4C0FAAC489C8B74F96BEAD85EAEB262502376D69@xmb-sjc-215.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dime] RE: Diameter base protocol messages used by DCCA Thread-Index: AcaQvHRLCzEvKzDHRWSkW/O26V/ALwAWLJYwABK/jSAA6/upUADsDA4g From: "Glen Zorn (gwz)" To: "STURA, Marco, VF-IT" , "Tolga Asveren" , "Anders Kristensen" Cc: , X-OriginalArrivalTime: 26 Jun 2006 01:35:15.0266 (UTC) FILETIME=[C62DA220:01C698C0] DKIM-Signature: a=rsa-sha1; q=dns; l=747; t=1151285715; x=1152149715; c=relaxed/simple; s=sjdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=gwz@cisco.com; z=From:=22Glen=20Zorn=20$gwz$=22=20 |Subject:RE=3A=20[Dime]=20RE=3A=20Diameter=20base=20protocol=20messages=20used=20 by=20DCCA; X=v=3Dcisco.com=3B=20h=3DHwsi7c48XQRfyiH8lUrRpE1X9Jg=3D; b=MzJZZkn2pwt0gmIkOPH5DCEuB/Q08EakB4Y2SIw28H32OA1NWhAbjjw1+Dbe7OfS99r2m7S8 MkWjgiMDScJew+E/j/PYKuupMS1WkglyUhz/uCgpdGX7zc4LQwdbXUXQ; Authentication-Results: sj-dkim-2.cisco.com; header.From=gwz@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Virus-Scanned: amavisd-new at merit.edu Sender: owner-aaa-wg@merit.edu Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 STURA, Marco, VF-IT supposedly = scribbled: ... >> So, in other words, in order to implement a e.g., [NASREQ], [DIAMMIP] > peer >intended for general distribution, one must include CCA client >> functionality. >=20 > Not necessarily. One could provide communication means to enable a > CCA functionality module to add relevant AVPs to the initial AA > request and process relevant AVPs from AA answer. =20 Maybe it's just me but that distinction seems to be, at best, = razor-thin. What you are saying is that every peer must make = concessions to CCA. =20 ... ~gwz Why is it that most of the world's problems can't be solved by simply listening to John Coltrane? -- Henry Gabriel From owner-aaa-wg@merit.edu Mon Jun 26 02:28:03 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FukZl-0000M0-PD for aaa-archive@lists.ietf.org; Mon, 26 Jun 2006 02:28:01 -0400 Received: from trapdoor.merit.edu ([198.108.1.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FukRS-00012D-2Y for aaa-archive@lists.ietf.org; Mon, 26 Jun 2006 02:19:27 -0400 Received: by trapdoor.merit.edu (Postfix) id 9CFEE9122C; Mon, 26 Jun 2006 02:19:19 -0400 (EDT) Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 6697291231; Mon, 26 Jun 2006 02:19:19 -0400 (EDT) Delivered-To: aaa-wg@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id EB35C9122C for ; Mon, 26 Jun 2006 02:19:17 -0400 (EDT) Received: by segue.merit.edu (Postfix) id D464158288; Mon, 26 Jun 2006 02:19:17 -0400 (EDT) Delivered-To: aaa-wg@segue.merit.edu Received: from fiji.merit.edu (fiji.merit.edu [198.108.1.12]) by segue.merit.edu (Postfix) with ESMTP id BDD5958282 for ; Mon, 26 Jun 2006 02:19:17 -0400 (EDT) Received: by fiji.merit.edu (Postfix) id A371217D9; Mon, 26 Jun 2006 02:19:17 -0400 (EDT) Delivered-To: aaa-wg@merit.edu Received: from fiji.merit.edu ([127.0.0.1]) by localhost (fiji.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23206-01 for ; Mon, 26 Jun 2006 02:19:17 -0400 (EDT) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by fiji.merit.edu (Postfix) with ESMTP id EBEE517D3 for ; Mon, 26 Jun 2006 02:19:16 -0400 (EDT) Received: by ug-out-1314.google.com with SMTP id a2so1909764ugf for ; Sun, 25 Jun 2006 23:19:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=rWEp6heIvN72YU96MnoHuzqo4flVKC+RjSI76fpGVqWUEim5lmRHWcsR1Iok7WYDF02pIuYkhlLdwwawrNBPO4pcNcHDL8LccXOLl0RWbYA0SeR55CqfkCysHjsVqv6tt94PzJN00lMGd9IPfeZENRxC7s/q1D7KEJ7g/YWAwCI= Received: by 10.67.29.12 with SMTP id g12mr4635954ugj; Sun, 25 Jun 2006 23:19:15 -0700 (PDT) Received: by 10.66.218.14 with HTTP; Sun, 25 Jun 2006 23:19:15 -0700 (PDT) Message-ID: <5be720c40606252319q1bbcff17k182abb9273a16f50@mail.gmail.com> Date: Mon, 26 Jun 2006 11:49:15 +0530 From: "Monal Sengar" To: aaa-wg@merit.edu Subject: [AAA-WG]: Session state machine in DBP MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2864_17389792.1151302755418" X-Virus-Scanned: amavisd-new at merit.edu Sender: owner-aaa-wg@merit.edu Precedence: bulk X-Spam-Score: 1.0 (+) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 ------=_Part_2864_17389792.1151302755418 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I would like to know where should i implement my Session state machine - in Diameter base protocol or in application? ------=_Part_2864_17389792.1151302755418 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

I would like to know where should i implement my Session state machine - in Diameter base protocol or in application?

------=_Part_2864_17389792.1151302755418--