From owner-aaa-wg@merit.edu  Tue Dec 11 15:33:33 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24387
	for <aaa-archive@odin.ietf.org>; Tue, 11 Dec 2001 15:33:32 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id C772D9124D; Tue, 11 Dec 2001 15:33:05 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 8F2FD91266; Tue, 11 Dec 2001 15:33:05 -0500 (EST)
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 8503D9124D
	for <aaa-wg@trapdoor.merit.edu>; Tue, 11 Dec 2001 15:33:04 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 608F75DD8F; Tue, 11 Dec 2001 15:33:04 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from ws2.piuha.net (ws2.piuha.net [195.165.196.2])
	by segue.merit.edu (Postfix) with ESMTP id 2D9495DD8D
	for <aaa-wg@merit.edu>; Tue, 11 Dec 2001 15:33:04 -0500 (EST)
Received: from kolumbus.fi (ws4.piuha.net [195.165.196.4])
	by ws2.piuha.net (Postfix) with ESMTP
	id 6B1C26A905; Tue, 11 Dec 2001 22:33:02 +0200 (EET)
Message-ID: <3C166D87.6030607@kolumbus.fi>
Date: Tue, 11 Dec 2001 22:33:11 +0200
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011014
X-Accept-Language: en-us
MIME-Version: 1.0
To: Pat Calhoun <pcalhoun@diameter.org>, jaakko.rajaniemi@nokia.com
Cc: aaa-wg@merit.edu
Subject: [AAA-WG]: Issue 241 and the accounting state table
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-wg@merit.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit


In reading the issue 241, we have noticed that the accounting state machine
in section 8.2 doesn't contain the event record processing. Here's a proposed
fix, three new entries to the state table. Note that I have chosen to
keep similar behaviour to START record handling in that the service isn't
given until the accounting answer is received.

(Question: is this wait really necessary, or even possible? It seems to
prevent non-real-time accounting.)


        State     Event                          Action     New State
        -------------------------------------------------------------
        Idle      Client or device requests      send       Pending
                  a one-time service             accounting
                                                 event req

        Idle      Accounting event request       send       Idle
                  received, and successfully     accounting
                  processed.                     event
                                                 answer

        Pending   Successful accounting          grant      Idle
                  event answer received          service

Jari





From owner-aaa-wg@merit.edu  Wed Dec 12 18:59:56 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21837
	for <aaa-archive@lists.ietf.org>; Wed, 12 Dec 2001 18:59:56 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 8532B91299; Wed, 12 Dec 2001 18:59:44 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 17F4E9129A; Wed, 12 Dec 2001 18:59:44 -0500 (EST)
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 2B60791299
	for <aaa-wg@trapdoor.merit.edu>; Wed, 12 Dec 2001 18:59:43 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 063775DDD1; Wed, 12 Dec 2001 18:59:43 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 41B805DDAD
	for <aaa-wg@merit.edu>; Wed, 12 Dec 2001 18:59:42 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id PAA30772
	for <aaa-wg@merit.edu>; Wed, 12 Dec 2001 15:47:11 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Wed, 12 Dec 2001 15:47:11 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: Slides from IETF 52
Message-ID: <Pine.BSF.4.21.0112121546410.30770-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

If you have slides from your IETF 52 presentatiuons, please send them to
me or Dave. 



From owner-aaa-wg@merit.edu  Thu Dec 20 07:12:12 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06194
	for <aaa-archive@odin.ietf.org>; Thu, 20 Dec 2001 07:12:07 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id BE2E391212; Thu, 20 Dec 2001 07:11:55 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 8E22F9121F; Thu, 20 Dec 2001 07:11:55 -0500 (EST)
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 719A491212
	for <aaa-wg@trapdoor.merit.edu>; Thu, 20 Dec 2001 07:11:54 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 47EB75DD99; Thu, 20 Dec 2001 07:11:54 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by segue.merit.edu (Postfix) with ESMTP id 276645DD8D
	for <aaa-wg@merit.edu>; Thu, 20 Dec 2001 07:10:39 -0500 (EST)
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fBKCAb924335
	for <aaa-wg@merit.edu>; Thu, 20 Dec 2001 14:10:38 +0200 (EET)
Received: from esebh24nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T57f0ff9a17ac158f23148@esvir03nok.nokia.com>;
 Thu, 20 Dec 2001 14:10:37 +0200
Received: by esebh24nok with Internet Mail Service (5.5.2652.78)
	id <ZHDY63G7>; Thu, 20 Dec 2001 14:10:36 +0200
Message-ID: <84230E60BFCF6B4FB0360BAE4C9B3EB526EB56@esebe013.NOE.Nokia.com>
From: jaakko.rajaniemi@nokia.com
To: jari.arkko@kolumbus.fi, pcalhoun@diameter.org
Cc: aaa-wg@merit.edu
Subject: RE: [AAA-WG]: Issue 241 and the accounting state table
Date: Thu, 20 Dec 2001 14:10:28 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

     State     Event                          Action     New State
      -------------------------------------------------------------
      Idle      Client or device requests      send       Pending
                a measurable length service    accounting
                                               start req.


     State     Event                          Action     New State
      -------------------------------------------------------------
      Open      Home server wants to           send ASR   Discon
                terminate the measurable 
                length service

      Open      ASR Received                   send ASA,  Discon
                                               STR

      Open      STR Received                   Send STA   Idle

      Discon    ASA Received                   Cleanup    Idle


      Discon    STR Received                   Send STA   Idle


> -----Original Message-----
> From: ext Jari Arkko [mailto:jari.arkko@kolumbus.fi]
> Sent: 11 December, 2001 22:33
> To: Pat Calhoun; Rajaniemi Jaakko (NET/Espoo)
> Cc: aaa-wg@merit.edu
> Subject: [AAA-WG]: Issue 241 and the accounting state table
> 
> 
> 
> In reading the issue 241, we have noticed that the accounting 
> state machine
> in section 8.2 doesn't contain the event record processing. 
> Here's a proposed
> fix, three new entries to the state table. Note that I have chosen to
> keep similar behaviour to START record handling in that the 
> service isn't
> given until the accounting answer is received.
> 
> (Question: is this wait really necessary, or even possible? 
> It seems to
> prevent non-real-time accounting.)
> 
> 
>         State     Event                          Action     New State
>         -------------------------------------------------------------
>         Idle      Client or device requests      send       Pending
>                   a one-time service             accounting
>                                                  event req
> 
>         Idle      Accounting event request       send       Idle
>                   received, and successfully     accounting
>                   processed.                     event
>                                                  answer
> 
>         Pending   Successful accounting          grant      Idle
>                   event answer received          service
> 
> Jari
> 
> 
> 


From owner-aaa-wg@merit.edu  Thu Dec 20 08:25:49 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06949
	for <aaa-archive@odin.ietf.org>; Thu, 20 Dec 2001 08:25:49 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 3DFAD91263; Thu, 20 Dec 2001 08:25:27 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 0DC0D91264; Thu, 20 Dec 2001 08:25:26 -0500 (EST)
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 DF74191263
	for <aaa-wg@trapdoor.merit.edu>; Thu, 20 Dec 2001 08:25:25 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id B43105DE4D; Thu, 20 Dec 2001 08:25:25 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by segue.merit.edu (Postfix) with ESMTP id A32955DE4C
	for <aaa-wg@merit.edu>; Thu, 20 Dec 2001 08:24:18 -0500 (EST)
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fBKDOHC21028
	for <aaa-wg@merit.edu>; Thu, 20 Dec 2001 15:24:17 +0200 (EET)
Received: from esebh24nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T57f1430a50ac158f21081@esvir01nok.ntc.nokia.com>;
 Thu, 20 Dec 2001 15:24:17 +0200
Received: by esebh24nok with Internet Mail Service (5.5.2652.78)
	id <ZHDY6TG4>; Thu, 20 Dec 2001 15:24:17 +0200
Message-ID: <84230E60BFCF6B4FB0360BAE4C9B3EB526EB5F@esebe013.NOE.Nokia.com>
From: jaakko.rajaniemi@nokia.com
To: jari.arkko@kolumbus.fi, pcalhoun@diameter.org
Cc: aaa-wg@merit.edu
Subject: RE: [AAA-WG]: Issue 241 and the accounting state table
Date: Thu, 20 Dec 2001 15:24:15 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Hello,

(This may be the second time you receive this mail because in the first time
the mail went off too early.)

Also related to the issue 241 and partly related to Jari's proposal, in
order to differentiate the event records from the measurable length service
in the state machine in the section 8.2, a text "measurable length" could be
added when it describes processing of the start/interim/stop records: 

    State     Event                          Action     New State
      -------------------------------------------------------------
      Idle      Client or device requests      send       Pending
                a measurable length service    accounting
                                               start req.

      Open      The measurable length user     send       Discon
                service terminated             accounting
                                               stop req.




The server originated accounting session abortion is missing from the state
machine. It is not clear whether this is missing on purpose. However, I
think that this possibility should be allowed therefore following entries
should be added: 


     State     Event                          Action     New State
      -------------------------------------------------------------
      Open      Home server wants to           send ASR   Discon
                terminate the measurable 
                length service

      Open      ASR Received                   send ASA,  Discon
                                               STR

      Discon    ASA Received                   Cleanup    Idle


      Discon    STR Received                   Send STA   Idle


I think that the last entry (Discon STR Received), which is copied directly
from the section 8.1 Authorization Session State Machine, tries to describe
the server behavior when it receives the STR after it has received the ASA.
However, the server is already in the idle state or in the cleanup process
when it receives the STR and therefore it is not exactly correct entry.
However, this approach was copied to the my proposal.

Best Regards, Jaakko

> -----Original Message-----
> From: ext Jari Arkko [mailto:jari.arkko@kolumbus.fi]
> Sent: 11 December, 2001 22:33
> To: Pat Calhoun; Rajaniemi Jaakko (NET/Espoo)
> Cc: aaa-wg@merit.edu
> Subject: [AAA-WG]: Issue 241 and the accounting state table
> 
> 
> 
> In reading the issue 241, we have noticed that the accounting 
> state machine
> in section 8.2 doesn't contain the event record processing. 
> Here's a proposed
> fix, three new entries to the state table. Note that I have chosen to
> keep similar behaviour to START record handling in that the 
> service isn't
> given until the accounting answer is received.
> 
> (Question: is this wait really necessary, or even possible? 
> It seems to
> prevent non-real-time accounting.)
> 
> 
>         State     Event                          Action     New State
>         -------------------------------------------------------------
>         Idle      Client or device requests      send       Pending
>                   a one-time service             accounting
>                                                  event req
> 
>         Idle      Accounting event request       send       Idle
>                   received, and successfully     accounting
>                   processed.                     event
>                                                  answer
> 
>         Pending   Successful accounting          grant      Idle
>                   event answer received          service
> 
> Jari
> 
> 
> 


From owner-aaa-wg@merit.edu  Thu Dec 20 13:14:17 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15259
	for <aaa-archive@odin.ietf.org>; Thu, 20 Dec 2001 13:14:16 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 6BB0391266; Thu, 20 Dec 2001 13:13:54 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 376E891267; Thu, 20 Dec 2001 13:13:54 -0500 (EST)
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 41A0791266
	for <aaa-wg@trapdoor.merit.edu>; Thu, 20 Dec 2001 13:13:53 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 179545DE29; Thu, 20 Dec 2001 13:13:53 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from frascone.com (adsl-66-137-237-97.dsl.rcsntx.swbell.net [66.137.237.97])
	by segue.merit.edu (Postfix) with SMTP id C409B5DE0E
	for <aaa-wg@merit.edu>; Thu, 20 Dec 2001 13:13:52 -0500 (EST)
Received: (qmail 27246 invoked by uid 507); 20 Dec 2001 18:13:52 -0000
Date: Thu, 20 Dec 2001 12:13:48 -0600
From: David Frascone <dave@frascone.com>
To: diameter@frascone.com, aaa-wg@merit.edu
Subject: [AAA-WG]: Connectathon Interest?
Message-ID: <20011220121348.F1449@newman.frascone.com>
Mail-Followup-To: diameter@frascone.com, aaa-wg@merit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
X-encrypt-payload: no
X-Virus-Scanned: by AMaViS perl-11
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Ok, sorry again for the cross post, but I think this question is relevant to
both lists.

Does *anyone* have a Diameter implementation that they would like to bring
to Connectathon (http://www.connectathon.org)?

I'm trying to get a head count to see if anyone is planning on attending.  If
there is no interest, there will not be any space/resources allocated for
Diameter testing.

Please let me know as soon as possible!


Happy Holidays,


Dave


From owner-aaa-wg@merit.edu  Fri Dec 21 18:43:11 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04138
	for <aaa-archive@odin.ietf.org>; Fri, 21 Dec 2001 18:43:10 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 3724C91207; Fri, 21 Dec 2001 18:43:01 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 0723991290; Fri, 21 Dec 2001 18:43:00 -0500 (EST)
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 0901E91207
	for <aaa-wg@trapdoor.merit.edu>; Fri, 21 Dec 2001 18:42:59 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id D53A55DE02; Fri, 21 Dec 2001 18:42:59 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 1DECF5DDE9
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 18:42:59 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id PAA46740
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 15:29:44 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Fri, 21 Dec 2001 15:29:44 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: Request for slides
Message-ID: <Pine.BSF.4.21.0112211529210.46738-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

If you presented slides at the IETF 52 AAA WG meeting, please submit them
to me or Dave. 

Thanks!



From owner-aaa-wg@merit.edu  Fri Dec 21 18:44:44 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04165
	for <aaa-archive@odin.ietf.org>; Fri, 21 Dec 2001 18:44:44 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 83DF491290; Fri, 21 Dec 2001 18:44:31 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 5995C91291; Fri, 21 Dec 2001 18:44:31 -0500 (EST)
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 701F691290
	for <aaa-wg@trapdoor.merit.edu>; Fri, 21 Dec 2001 18:44:30 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 555015DDA0; Fri, 21 Dec 2001 18:44:30 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 8471A5DDBA
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 18:44:29 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id PAA46751
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 15:31:14 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Fri, 21 Dec 2001 15:31:14 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: Status on Diameter.org?
Message-ID: <Pine.BSF.4.21.0112211529480.46738-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Any update on when Diameter.org will be back online? 

Until it gets back online, would it make sense to rehost the issues list
somewhere else? I have space on my website for it, if that would help. 



From owner-aaa-wg@merit.edu  Fri Dec 21 18:53:20 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04431
	for <aaa-archive@odin.ietf.org>; Fri, 21 Dec 2001 18:53:20 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id ED1AC91292; Fri, 21 Dec 2001 18:53:05 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id B8C3491293; Fri, 21 Dec 2001 18:53:05 -0500 (EST)
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 8E4AE91292
	for <aaa-wg@trapdoor.merit.edu>; Fri, 21 Dec 2001 18:53:04 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 750EE5DDBF; Fri, 21 Dec 2001 18:53:04 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 9E84D5DDA0
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 18:53:03 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id PAA46774
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 15:39:49 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Fri, 21 Dec 2001 15:39:48 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: AAA WG last call on draft-ietf-aaa-transport-05.txt
Message-ID: <Pine.BSF.4.21.0112211531370.46738-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

This is an announcement of AAA WG last call on:

http://www.ietf.org/internet-drafts/draft-ietf-aaa-transport-05.txt

This draft is a Standards Track document. Please send comments on this
document to the AAA WG mailing list, on or before January 15, 2002. 

As with other AAA WG documents, issues are to be submitted using the
following template:

Issue Number: Get_An_Issue_Number_From_Pat
Description of issue:
Submitter name: Your_Name_Here
Date first submitted: Insert_Date_Here
Reference: URL to e-mail describing problem, if available
Document: Document Requiring change [base, nasreq, mobileip, cms,
                                    transport]
Comment type: ['T'echnical | 'E'ditorial ]
Priority: ['S' Must fix | '1' Should fix | '2' May fix ]
Section: Insert_Section_Number_Here
Rationale/Explanation of issues: 

Description_of_Problem_Goes_Here

Requested change: 

Proposal_Goes_Here_With_Specific_Text



From owner-aaa-wg@merit.edu  Fri Dec 21 18:54:49 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04476
	for <aaa-archive@odin.ietf.org>; Fri, 21 Dec 2001 18:54:49 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 33B2291294; Fri, 21 Dec 2001 18:54:35 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id EF75B91295; Fri, 21 Dec 2001 18:54:34 -0500 (EST)
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 058DF91294
	for <aaa-wg@trapdoor.merit.edu>; Fri, 21 Dec 2001 18:54:34 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id E31EA5DDBF; Fri, 21 Dec 2001 18:54:23 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 1814C5DDA0
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 18:54:23 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id PAA46789
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 15:41:03 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Fri, 21 Dec 2001 15:41:03 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: AAA WG last call on draft-ietf-aaa-diameter-08.txt
Message-ID: <Pine.BSF.4.21.0112211540020.46738-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

This is an announcement of AAA WG last call on:

http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-08.txt

This draft is a Standards Track document. Please send comments on this
document to the AAA WG mailing list, on or before January 15, 2002. 

As with other AAA WG documents, issues are to be submitted using the
following template:

Issue Number: Get_An_Issue_Number_From_Pat
Description of issue:
Submitter name: Your_Name_Here
Date first submitted: Insert_Date_Here
Reference: URL to e-mail describing problem, if available
Document: Document Requiring change [base, nasreq, mobileip, cms,
                                    transport]
Comment type: ['T'echnical | 'E'ditorial ]
Priority: ['S' Must fix | '1' Should fix | '2' May fix ]
Section: Insert_Section_Number_Here
Rationale/Explanation of issues: 

Description_of_Problem_Goes_Here

Requested change: 

Proposal_Goes_Here_With_Specific_Text




From owner-aaa-wg@merit.edu  Fri Dec 21 18:56:21 2001
Received: from trapdoor.merit.edu (trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04516
	for <aaa-archive@odin.ietf.org>; Fri, 21 Dec 2001 18:56:21 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id F064C91297; Fri, 21 Dec 2001 18:55:50 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id BC0B59129B; Fri, 21 Dec 2001 18:55:49 -0500 (EST)
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 4670491297
	for <aaa-wg@trapdoor.merit.edu>; Fri, 21 Dec 2001 18:55:47 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 343CD5DE1F; Fri, 21 Dec 2001 18:55:28 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id DB5135DE09
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 18:55:17 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id PAA46797
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 15:41:58 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Fri, 21 Dec 2001 15:41:58 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: AAA WG last call on draft-ietf-aaa-diameter-nasreq-08.txt
Message-ID: <Pine.BSF.4.21.0112211541060.46738-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

This is an announcement of AAA WG last call on:

http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-nasreq-08.txt

This draft is a Standards Track document. Please send comments on this
document to the AAA WG mailing list, on or before January 15, 2002. 

As with other AAA WG documents, issues are to be submitted using the
following template:

Issue Number: Get_An_Issue_Number_From_Pat
Description of issue:
Submitter name: Your_Name_Here
Date first submitted: Insert_Date_Here
Reference: URL to e-mail describing problem, if available
Document: Document Requiring change [base, nasreq, mobileip, cms,
                                    transport]
Comment type: ['T'echnical | 'E'ditorial ]
Priority: ['S' Must fix | '1' Should fix | '2' May fix ]
Section: Insert_Section_Number_Here
Rationale/Explanation of issues: 

Description_of_Problem_Goes_Here

Requested change: 

Proposal_Goes_Here_With_Specific_Text




From owner-aaa-wg@merit.edu  Fri Dec 21 18:56:57 2001
Received: from trapdoor.merit.edu (trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04540
	for <aaa-archive@odin.ietf.org>; Fri, 21 Dec 2001 18:56:57 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 4A7DA9129A; Fri, 21 Dec 2001 18:56:25 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 52BE09129B; Fri, 21 Dec 2001 18:56:21 -0500 (EST)
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 B2B3891298
	for <aaa-wg@trapdoor.merit.edu>; Fri, 21 Dec 2001 18:56:20 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id BA2EA5DDDC; Fri, 21 Dec 2001 18:56:18 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 7BCF75DDEB
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 18:56:04 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id PAA46804
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 15:42:44 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Fri, 21 Dec 2001 15:42:44 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: AAA WG last call on draft-ietf-aaa-diameter-mobileip-08.txt
Message-ID: <Pine.BSF.4.21.0112211541590.46738-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

This is an announcement of AAA WG last call on:

http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-mobileip-08.txt

This draft is a Standards Track document. Please send comments on this
document to the AAA WG mailing list, on or before January 15, 2002. 

As with other AAA WG documents, issues are to be submitted using the
following template:

Issue Number: Get_An_Issue_Number_From_Pat
Description of issue:
Submitter name: Your_Name_Here
Date first submitted: Insert_Date_Here
Reference: URL to e-mail describing problem, if available
Document: Document Requiring change [base, nasreq, mobileip, cms,
                                    transport]
Comment type: ['T'echnical | 'E'ditorial ]
Priority: ['S' Must fix | '1' Should fix | '2' May fix ]
Section: Insert_Section_Number_Here
Rationale/Explanation of issues: 

Description_of_Problem_Goes_Here

Requested change: 

Proposal_Goes_Here_With_Specific_Text




From owner-aaa-wg@merit.edu  Fri Dec 21 18:57:16 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04561
	for <aaa-archive@odin.ietf.org>; Fri, 21 Dec 2001 18:57:16 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 57B5091293; Fri, 21 Dec 2001 18:57:00 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 2364491295; Fri, 21 Dec 2001 18:57:00 -0500 (EST)
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 2FB5791293
	for <aaa-wg@trapdoor.merit.edu>; Fri, 21 Dec 2001 18:56:59 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 11C775DDBF; Fri, 21 Dec 2001 18:56:59 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 38BC55DDA0
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 18:56:58 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id PAA46825
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 15:43:43 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Fri, 21 Dec 2001 15:43:43 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: AAA WG last call on draft-ietf-aaa-diameter-cms-sec-03.txt
Message-ID: <Pine.BSF.4.21.0112211542500.46738-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

This is an announcement of AAA WG last call on:

http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-cms-sec-03.txt

This draft is a Standards Track document. Please send comments on this
document to the AAA WG mailing list, on or before January 15, 2002. 

As with other AAA WG documents, issues are to be submitted using the
following template:

Issue Number: Get_An_Issue_Number_From_Pat
Description of issue:
Submitter name: Your_Name_Here
Date first submitted: Insert_Date_Here
Reference: URL to e-mail describing problem, if available
Document: Document Requiring change [base, nasreq, mobileip, cms,
                                    transport]
Comment type: ['T'echnical | 'E'ditorial ]
Priority: ['S' Must fix | '1' Should fix | '2' May fix ]
Section: Insert_Section_Number_Here
Rationale/Explanation of issues: 

Description_of_Problem_Goes_Here

Requested change: 

Proposal_Goes_Here_With_Specific_Text





From owner-aaa-wg@merit.edu  Fri Dec 21 19:23:54 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05331
	for <aaa-archive@odin.ietf.org>; Fri, 21 Dec 2001 19:23:54 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 1B8E991295; Fri, 21 Dec 2001 19:23:33 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id E158F91296; Fri, 21 Dec 2001 19:23:32 -0500 (EST)
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 DF88E91295
	for <aaa-wg@trapdoor.merit.edu>; Fri, 21 Dec 2001 19:23:31 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id BED6B5DDFB; Fri, 21 Dec 2001 19:23:31 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 02CF75DDEB
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 19:23:30 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id QAA46920
	for <aaa-wg@merit.edu>; Fri, 21 Dec 2001 16:10:16 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Fri, 21 Dec 2001 16:10:16 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: AAA WG Issues list now back online
Message-ID: <Pine.BSF.4.21.0112211608540.46903-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

While Pat is working on getting http://www.diameter.org/ back online,
we've put the AAA WG Issues list back up at the following location:

http://www.drizzle.com/~aboba/AAA/issues.html

Please consult the issues list prior to filing a new issue as part of AAA
WG last call. 



From owner-aaa-wg@merit.edu  Sun Dec 23 22:24:55 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01230
	for <aaa-archive@odin.ietf.org>; Sun, 23 Dec 2001 22:24:55 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 7619A9121D; Sun, 23 Dec 2001 22:24:42 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 4823691221; Sun, 23 Dec 2001 22:24:42 -0500 (EST)
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 41E429121D
	for <aaa-wg@trapdoor.merit.edu>; Sun, 23 Dec 2001 22:24:41 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 099E95DDF3; Sun, 23 Dec 2001 22:24:41 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by segue.merit.edu (Postfix) with ESMTP id 427785DDE5
	for <aaa-wg@merit.edu>; Sun, 23 Dec 2001 22:24:40 -0500 (EST)
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fBO3OZC13594
	for <aaa-wg@merit.edu>; Mon, 24 Dec 2001 05:24:35 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5803b77db5ac158f21082@esvir01nok.ntc.nokia.com> for <aaa-wg@merit.edu>;
 Mon, 24 Dec 2001 05:24:38 +0200
Received: by esebh01nok with Internet Mail Service (5.5.2652.78)
	id <ZHBRWCGR>; Mon, 24 Dec 2001 05:24:35 +0200
Message-ID: <4AE1AC3D692F55488F2D03518907B8AD1820B6@beebe001.NOE.Nokia.com>
From: Yanqun.Le@nokia.com
To: aaa-wg@merit.edu
Subject: [AAA-WG]: failover state machine inconsistent in case of REOPEN
Date: Mon, 24 Dec 2001 05:23:17 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

failover state machine inconsistent in case of REOPEN 
Submitter name: yanqun le 
Submitter email address: yanqun.le@nokia.com 
Date first submitted: Dec 24, 2001 
Reference:  
Document: draft-ietf-aaa-transport-05.txt  
Comment type: E 
Priority: S
Section: Appendix A 
Rationale/Explanation of issue: 
In the state of REOPEN in failover state machine, the action to Event
Send & Pending is inconsistent with that in function OnSendRequest.

Requested change: 
Fix failover state machine to be consistent with function OnSendRequest.



From owner-aaa-wg@merit.edu  Mon Dec 24 11:33:14 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23622
	for <aaa-archive@lists.ietf.org>; Mon, 24 Dec 2001 11:33:13 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id D76E691222; Mon, 24 Dec 2001 11:33:05 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 98D3F91223; Mon, 24 Dec 2001 11:33:05 -0500 (EST)
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 5601391222
	for <aaa-wg@trapdoor.merit.edu>; Mon, 24 Dec 2001 11:33:04 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 2D6355DE00; Mon, 24 Dec 2001 11:33:04 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from web13001.mail.yahoo.com (web13001.mail.yahoo.com [216.136.174.11])
	by segue.merit.edu (Postfix) with SMTP id DEEAA5DDAB
	for <aaa-wg@merit.edu>; Mon, 24 Dec 2001 11:33:03 -0500 (EST)
Message-ID: <20011224163302.66969.qmail@web13001.mail.yahoo.com>
Received: from [207.3.232.118] by web13001.mail.yahoo.com via HTTP; Mon, 24 Dec 2001 08:33:02 PST
Date: Mon, 24 Dec 2001 08:33:02 -0800 (PST)
From: Dilip <dilris@yahoo.com>
Subject: [AAA-WG]: Peer State Machine
To: aaa-wg@merit.edu
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Hi 
In the peer state machine section 5.6.2 Events.
The Rcv-Message Event states
"A message other than CER,CEA,DWR, or DWA was
received"

In THIS definition DPR & DPA is missed out.

suggestion
---------
Sections 5.6.2 Events should have
Rcv-Message " A message other than
CER,CEA,DPR,DPA,DWR, or DWA was received"


Regards
Dilip Patel

=====
Live For Today & not for Tomorrow...
As Tomorrow NEVER COMES..
Do Visit My Site at http://www.angelfire.com/in/dilris

__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com


From owner-aaa-wg@merit.edu  Sat Dec 29 10:44:01 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28087
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 10:44:00 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id B1F8591221; Sat, 29 Dec 2001 10:43:48 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 77C229122B; Sat, 29 Dec 2001 10:43:48 -0500 (EST)
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 7194C91221
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 10:43:47 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 4FB5F5DDA5; Sat, 29 Dec 2001 10:43:47 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 970495DDA2
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 10:43:46 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id HAA62120
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 07:29:53 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 07:29:53 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] Error messages: decimal or hex?
Message-ID: <Pine.BSF.4.21.0112290723461.62077-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter: Bernard Aboba <aboba@internaut.com>
Date: December 28, 2001
Document: Diameter Base -08
Section: 7.1 (page 75)
Rationale: 
  Diameter distinguishes error classes according to the DECIMAL value of
  the Result-Code data field. This is widely used in protocols that 
  utilize ASCII encoding (SMTP, HTTP, etc.). But it doesn't make much
  sense in a binary protocol such as Diameter. Shouldn't the HEX value
  of the Result-Code data field be used instead? 

For example:

Is an Informational error message 1000 - 1999 in DECIMAL? Or is it
10000000 - 1FFFFFFF in HEX? 



From owner-aaa-wg@merit.edu  Sat Dec 29 10:54:23 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28158
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 10:54:23 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 0B7479122B; Sat, 29 Dec 2001 10:54:03 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id C76949122C; Sat, 29 Dec 2001 10:54:02 -0500 (EST)
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 C751A9122B
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 10:54:01 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id A86EF5DDA5; Sat, 29 Dec 2001 10:54:01 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id E7D565DDA2
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 10:54:00 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id HAA62141
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 07:40:07 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 07:40:07 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: Editorial nits in Diameter Base -08
Message-ID: <Pine.BSF.4.21.0112290730400.62077-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter: Bernard Aboba <aboba@internaut.com>
Date: December 28, 2001
Document: Diameter Base -08
Type: Editorial

Page 7, section 1.1, 3rd paragraph, last sentence:
Change
"AVPs are used by base Diameter" to "AVPs are used by the base Diameter"

Page 12, section 3.0-, 3rd paragraph:

"Diameter Servers must support the base protocol"

Shouldn't the must be capitalized? 

Page 14, section 2.1, third and fourth paragraphs:

Change: "ICMP protocol and port unreachable messages" to "ICMP protocol
port unreachable messages". 

"If Diameter receives data to from TCP that" to "If Diameter receives data
from TCP that"

Page 16, Section 2.3.4, first paragraph:
Change "Applications Identifiers is different from the ones" to
"Applications Identifiers are different from the ones"

Page 111, Section 11.1.1, second paragraph
Change:
"is set to a non-zero value, is for Private Use" to 
"is set to a non-zero value, are for Private Use"

Same change in section 11.2.1 on page 111 also. 



From owner-aaa-wg@merit.edu  Sat Dec 29 11:02:20 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28291
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 11:02:20 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id ECC7A9122C; Sat, 29 Dec 2001 11:02:02 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id B69FC9122D; Sat, 29 Dec 2001 11:02:02 -0500 (EST)
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 A23069122C
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 11:02:01 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 831BB5DDA5; Sat, 29 Dec 2001 11:02:01 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id D1AF55DDA2
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 11:02:00 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id HAA62152
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 07:48:07 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 07:48:07 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] Normative versus Informative references
Message-ID: <Pine.BSF.4.21.0112290740100.62077-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter: Bernard Aboba <aboba@internaut.com>
Date: December 28, 2001
Type: Editorial
Drafts: Base, Nasreq, Mobile IP, Transport
Section: References
Rationale:

RFC Editor has indicated that future RFCs will need to separate Normative
versus Informative references. 



From owner-aaa-wg@merit.edu  Sat Dec 29 11:12:18 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28339
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 11:12:18 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 545459122D; Sat, 29 Dec 2001 11:12:06 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 223BD9122E; Sat, 29 Dec 2001 11:12:06 -0500 (EST)
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 305459122D
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 11:12:05 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 04BFE5DDAE; Sat, 29 Dec 2001 11:12:05 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 52F455DDA5
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 11:12:04 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id HAA62166
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 07:58:11 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 07:58:10 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] References to ADIF in NASREQ-08
Message-ID: <Pine.BSF.4.21.0112290748330.62077-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter: Bernard Aboba <aboba@internaut.com>
Date: December 28, 2001
Document: Nasreq-08
Rationale: Support for ADIF was removed a while back
Sections 7.4.3 and 7.4.4

In both sections it is stated "This AVP SHOULD Be included in the ADIF
Record of the corresponding Accounting-Request messages"

Suggestion: strike "the ADIF Record of"



From owner-aaa-wg@merit.edu  Sat Dec 29 11:21:24 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28403
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 11:21:24 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id CCD769122F; Sat, 29 Dec 2001 11:21:06 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 98BCF91230; Sat, 29 Dec 2001 11:21:06 -0500 (EST)
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 3106C9122F
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 11:21:05 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 167F55DDA5; Sat, 29 Dec 2001 11:21:05 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 58FD45DDA2
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 11:21:04 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id IAA62183
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 08:07:11 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 08:07:10 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] Granting Access via Accounting
Message-ID: <Pine.BSF.4.21.0112290803160.62077-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter: Bernard Aboba <aboba@internaut.com>
Date: December 28, 2001
Document: Base-08
Section: 8.2, page 86
Rationale: Access is not granted based on receipt of a successful
accounting start answer

Change:
In the state table on pp. 86, it states that in Pending state, receipt of
a Successful accounting start answer results in "grant access" and
movement to the Open state. Since access is granted within the
authentication/authorization state machine, this appears to be an error. 



From owner-aaa-wg@merit.edu  Sat Dec 29 11:35:46 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28455
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 11:35:46 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 8D3CC91230; Sat, 29 Dec 2001 11:35:34 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 5D3BC91231; Sat, 29 Dec 2001 11:35:34 -0500 (EST)
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 6525691230
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 11:35:33 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 380015DDAE; Sat, 29 Dec 2001 11:35:33 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 7AE8B5DDA2
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 11:35:32 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id IAA62200
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 08:21:39 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 08:21:39 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] Diameter Peer Discovery
Message-ID: <Pine.BSF.4.21.0112290813010.62077-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter: Bernard Aboba <aboba@internaut.com>
Date: December 28, 2001
Type: Technical
Document: Base -08
Section: 5.2, page 49
Rationale: A6 RRs are now deprecated, and the text doesn't mention how to
discover TLS support on the peer

Change:

3. The Diameter implementation uses DNS to request the SRV RR [33] for the
'_diameter._sctp' and/or '_diameter._tcp' server in a particular realm"

To:

3. The Diameter implementation uses DNS to request the SRV RR [33] for the
'_diameter-tls._sctp' and/or '_diameter-tls._tcp' in a particular realm,
as well as the '_diameter._sctp' and/or '_diameter._tcp' servers.  
If records corresponding to the TLS ports are found, the Diameter peer is
assumed to support TLS. 

Change:

"Address records include A RR's, AAAA RR's, A6 RR's or other similar"

To:

"Address records include A RRs, AAAA RRs or other similar"



From owner-aaa-wg@merit.edu  Sat Dec 29 11:50:39 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28545
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 11:50:39 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 4B3E691222; Sat, 29 Dec 2001 11:50:27 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 1B35B91231; Sat, 29 Dec 2001 11:50:27 -0500 (EST)
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 02CB791222
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 11:50:25 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id CC2DA5DDAE; Sat, 29 Dec 2001 11:50:25 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id D58975DDA2
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 11:50:24 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id IAA62219
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 08:36:31 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 08:36:31 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] More details needed on Diameter IPsec usage
Message-ID: <Pine.BSF.4.21.0112290824510.62077-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter: Bernard Aboba <aboba@internaut.com>
Date: December 28, 2001
Type: Technical
Document: Base -08
Section: 2.2
Rationale:
The IPsec mode is not specified. IPsec is also mispelled (do a global
replace of IPSec with IPsec). 

Add:

"
All Diameter implementations MUST support IPsec ESP [RFC2406] in transport
mode with a non-null transform to provide per-packet authentication,
integrity protection and confidentiality, and MUST
support the replay protection mechanisms of IPsec.

Diameter implemenations MUST support IKE
for peer authentication, negotiation of security associations, and
key management, using the IPsec DOI [RFC2407].  Manual keying MUST NOT
be used since it does not provide the necessary rekeying support.
Diameter implementations MUST support peer
authentication using a pre-shared key, and MAY support certificate-based
peer authentication using digital signatures.  Peer authentication using
the public key encryption methods outlined in IKE's sections 5.2 and 5.3
[RFC2409] SHOULD NOT be used.

Conformant  implementations MUST support both
IKE Main Mode and Aggressive Mode.  When pre-shared keys are used for
authentication, IKE Aggressive Mode SHOULD be used, and IKE Main Mode
SHOULD NOT be used.  When digital signatures are used for
authentication, either IKE Main Mode or IKE Aggressive Mode MAY be used.
In all cases, access to  locally stored secret information (pre-shared
key,  or private  key for digital signing) must be suitably restricted,
since compromise of the secret information nullifies the security
properties of the IKE/IPsec protocols.

When digital signatures are used to achieve authentication, an IKE
negotiator SHOULD use IKE Certificate Request Payload(s) to specify the
certificate authority (or authorities) that are trusted in accordance
with its local policy.  IKE negotiators SHOULD check the pertinent
Certificate Revocation List (CRL) before accepting a PKI certificate for
use in IKE's authentication procedures.

The Phase 2 Quick Mode exchanges used to negotiate protection for 
Diameter connections MUST explicitly carry
the Identity Payload fields (IDci and IDcr).  The DOI provides for
several types of identification data.  However, when used in conformant
implementations, each ID Payload MUST carry a
single IP address and a single non-zero port number, and MUST NOT use
the IP Subnet or IP Address Range formats.  This allows the Phase 2
security association to correspond to specific TCP and SCTP
connections.

Since IPsec acceleration hardware may only be able to handle a limited
number of active IKE Phase 2 SAs, Phase 2 delete messages may be sent
for idle SAs, as a means of keeping the number of active Phase 2 SAs to
a minimum. The receipt of an IKE Phase 2 delete message SHOULD NOT be
interpreted as a reason for tearing down a Diameter connection.
Rather, it is preferable to leave the connection up, and if additional
traffic is sent on it, to bring up another IKE Phase 2 SA to protect it.
This avoids the potential for continually bringing connections up and
down.

If an IKE implementation receives a Phase 1 Delete message for a Phase 1
Security Association bound to one or more sessions, then it SHOULD
delete the associated IKE Phase 2 security associations."



From owner-aaa-wg@merit.edu  Sat Dec 29 12:31:44 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28761
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 12:31:39 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 99A3891231; Sat, 29 Dec 2001 12:30:12 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 699AF91232; Sat, 29 Dec 2001 12:30:12 -0500 (EST)
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 5F5A691231
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 12:30:11 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 31BEE5DDCF; Sat, 29 Dec 2001 12:30:11 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 831B25DDA2
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 12:30:10 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id JAA62258
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 09:16:16 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 09:16:16 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] Diameter introduction needs improvement
Message-ID: <Pine.BSF.4.21.0112290914070.62253-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Note: this issue never got entered into the issues list, so it is being
resubmitted. 

Description of issue: Diameter introduction needs improvement

Submitter name: Randy Bush
Submitter email address: randy@psg.com 
Date first submitted: 2001.09.03
Reference: 
Document: base
Comment type: E 
Priority: S 
Section: 1.0, 1.1
Rationale/Explanation of issue: 

The Introduction (section 1.0) talks about the history and motivation for
the development of Diameter. Section 1.1 talks about the basic building
blocks of Diameter. Section 2 provides an overview of protocol
concepts. What would be helpful is if a high-level introduction could be
provided within section 1. The material currently in section 1.1 might be
better moved to section 2.

Requested change: 

To provide context, the following topics would be useful in the
Introduction:
     
     a. An overview of the Diameter approach
            1. Relationship of NASes, Servers and Intermediaries
            2. Message routing concepts
            3. Requests, Responses, Unsolicited messages

     b. Important ways that Diameter differs from RADIUS
        (Idea is to introduce the concepts, not go into
         depth, but make clear what the feature is attempting
         to achieve. Reference where details are provided.)
            1. Peer-to-peer nature
            2. Explicit support for intermediaries
            3. Connection-oriented versus connectionless
            4. Concept of extensions
            5. Built-in failover support
            6. Larger attribute space 
            7. Integrated accounting
            8. Mandatory bit
            9. Application-layer ACKs and error messages
           10. Unsolicited server messages
           11. Peer discovery
           12. Capabilities negotiation (worth explaining why
               this isn't e2e here)

     c. Description of the Diameter document set and relationship
        between the documents.
 
     d. Approach to extensibility (this is in section 2.3, but might
        be better consolidated into the Introduction)



From owner-aaa-wg@merit.edu  Sat Dec 29 12:46:25 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28818
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 12:46:24 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id DD45291232; Sat, 29 Dec 2001 12:45:48 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id AD44391233; Sat, 29 Dec 2001 12:45:48 -0500 (EST)
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 B545F91232
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 12:45:47 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 88ADF5DDB8; Sat, 29 Dec 2001 12:45:47 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id D56925DDA2
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 12:45:46 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id JAA62275
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 09:31:53 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 09:31:53 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] Translation of RADIUS vendor-specific attributes
Message-ID: <Pine.BSF.4.21.0112290920300.62253-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter: Bernard Aboba <aboba@internaut.com>
Date: December 28, 2001
Reference: 
Document: NASREQ -08
Comment type: T
Priority: S 
Section: 9.1
Rationale/Explanation of issue: 
There is no discussion of how RADIUS vendor-specific attributes are to be
translated to Diameter AVPs and vice-versa. 





From owner-aaa-wg@merit.edu  Sat Dec 29 13:37:25 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29315
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 13:37:25 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 495EE91205; Sat, 29 Dec 2001 13:37:10 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 1337591233; Sat, 29 Dec 2001 13:37:09 -0500 (EST)
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 04E3D91205
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 13:37:08 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id CCC7C5DDDD; Sat, 29 Dec 2001 13:37:08 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from fep06-app.kolumbus.fi (fep06-0.kolumbus.fi [193.229.0.57])
	by segue.merit.edu (Postfix) with ESMTP id DFBB85DDA0
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 13:37:07 -0500 (EST)
Received: from jariws1 ([62.248.239.67]) by fep06-app.kolumbus.fi
          (InterMail vM.5.01.03.08 201-253-122-118-108-20010628) with SMTP
          id <20011229183702.EWWY4849.fep06-app.kolumbus.fi@jariws1>;
          Sat, 29 Dec 2001 20:37:02 +0200
Message-ID: <001501c19097$d09e9600$8a1b6e0a@arenanet.fi>
From: "Jari Arkko" <jari.arkko@kolumbus.fi>
To: "Bernard Aboba" <aboba@internaut.com>, <aaa-wg@merit.edu>
References: <Pine.BSF.4.21.0112290803160.62077-100000@internaut.com>
Subject: Re: [AAA-WG]: [Issue] Granting Access via Accounting
Date: Sat, 29 Dec 2001 20:37:05 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-aaa-wg@merit.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Change:
> In the state table on pp. 86, it states that in Pending state, receipt of
> a Successful accounting start answer results in "grant access" and
> movement to the Open state. Since access is granted within the
> authentication/authorization state machine, this appears to be an error. 

Agree. (I also wondered about this some e-mails ago...)
There's been a few suggested changes to the accounting
state machine. I'll try to merge those and post a suggested
final state machine soon.

Jari





From owner-aaa-wg@merit.edu  Sat Dec 29 13:58:10 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29425
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 13:58:10 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 7291291233; Sat, 29 Dec 2001 13:57:58 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 4491891234; Sat, 29 Dec 2001 13:57:58 -0500 (EST)
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 2E1D591233
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 13:57:57 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 0A5655DDE1; Sat, 29 Dec 2001 13:57:57 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by segue.merit.edu (Postfix) with ESMTP id C79715DDA0
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 13:57:56 -0500 (EST)
Received: from randy by rip.psg.com with local (Exim 3.33 #1)
	id 16KOg5-0002Nr-00
	for aaa-wg@merit.edu; Sat, 29 Dec 2001 10:57:53 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: aaa-wg@merit.edu
Subject: [AAA-WG]: Re: Diameter extensibility
Message-Id: <E16KOg5-0002Nr-00@rip.psg.com>
Date: Sat, 29 Dec 2001 10:57:53 -0800
Sender: owner-aaa-wg@merit.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

is eeems that the results of the discussion last may of vendor-specific
commands never made it into the documents.  in specific.

---

25 of the base:

"The Command-Code field is three octets, and is used in order to
communicate the command associated with the message. The 24-bit address
space is managed by IANA (see section 11.2). 

In the event that the Command-Code field contains a vendor specific
command, the four octet Vendor-ID field contains the IANA assigned "SMI
Network Management Private Enterprise Codes" [2] value. If the
Command-Code field contains an IETF standard Command, the Vendor-ID field
MUST be set to zero (0). Any vendor wishing to implement a vendor-specific
Diameter command MUST use their own Vendor-ID along with their privately
managed Command-Code address space, guaranteeing that they will not
collide with any other vnedor's vendor-specific command, nor with future
IETF applications."

---

as i said last april,

> as an engineer, i sympathize with the excitement that the protocol is
> very extensible.  otoh, an architect might view that the protocol is
> merely a list of name/value tuples to indicate a lack of bounding and
> understanding of the problems and/or inability to make a real design for
> it.
> 
> open loop extensibility is really worrying the iesg.

---

and we discussed again in may:

> So, the WG questioned whether the specs could be more relax on the 
> IANA requirements for extensibility. Specifically, could a 
> vendor-specific extension be created without Standards Action.

i can see arguments for relaxing to info but not iana-only.  a
documentation trail is needed.

---

and a number of iesg members made quite clear, or at least tried to, that
any extensions, vendor or otherwise, must require previous documentation
in an rfc.

---

please consider this a bug report.  my apologies for not knowing how to
get a bug number etc.

randy


From owner-aaa-wg@merit.edu  Sat Dec 29 16:14:02 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00475
	for <aaa-archive@odin.ietf.org>; Sat, 29 Dec 2001 16:14:02 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 56A1D91236; Sat, 29 Dec 2001 16:13:50 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 1E7BA91237; Sat, 29 Dec 2001 16:13:50 -0500 (EST)
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 2C8C991236
	for <aaa-wg@trapdoor.merit.edu>; Sat, 29 Dec 2001 16:13:49 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 061DC5DDAB; Sat, 29 Dec 2001 16:13:49 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 46F645DDA2
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 16:13:48 -0500 (EST)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id MAA62497
	for <aaa-wg@merit.edu>; Sat, 29 Dec 2001 12:59:53 -0800 (PST)
	(envelope-from aboba@internaut.com)
Date: Sat, 29 Dec 2001 12:59:53 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] TLS usage issues
Message-ID: <Pine.BSF.4.21.0112291251420.62492-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter: Bernard Aboba <aboba@internaut.com>
Date: December 28, 2001
Reference: 
Document: BASE-08
Comment type: T
Priority: S 
Section: 2.2
Rationale/Explanation of issue: 
There is no discussion of how TLS authentication is used with
Diameter. For example:

 a. Are both peers required to support certificates?
 b. If not, how is it decided which peer authenticates to who?

Proposed change:

Add:

"Diameter clients act as TLS clients according to [RFC2246], and Diameter
servers act as TLS servers. Diameter clients and servers implementing
TLS for security MUST mutually authenticate as part of TLS session
establishment. In order to ensure mutual authentication, Diameter servers
MUST request certificates from Diameter clients, and the client MUST be
prepared to supply a certificate on request."




From owner-aaa-wg@merit.edu  Sun Dec 30 04:40:51 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14714
	for <aaa-archive@lists.ietf.org>; Sun, 30 Dec 2001 04:40:50 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 85B019123A; Sun, 30 Dec 2001 04:40:38 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 579F69123B; Sun, 30 Dec 2001 04:40:38 -0500 (EST)
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 E00CC9123A
	for <aaa-wg@trapdoor.merit.edu>; Sun, 30 Dec 2001 04:40:36 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id B06FD5DDCB; Sun, 30 Dec 2001 04:40:36 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by segue.merit.edu (Postfix) with ESMTP id C4CC25DDBD
	for <aaa-wg@merit.edu>; Sun, 30 Dec 2001 04:40:35 -0500 (EST)
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fBU9eSC11435
	for <aaa-wg@merit.edu>; Sun, 30 Dec 2001 11:40:28 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5823f5d208ac158f250ef@esvir05nok.ntc.nokia.com> for <aaa-wg@merit.edu>;
 Sun, 30 Dec 2001 11:40:34 +0200
Received: by esebh01nok with Internet Mail Service (5.5.2652.78)
	id <ZHBSHDD2>; Sun, 30 Dec 2001 11:40:34 +0200
Message-ID: <4AE1AC3D692F55488F2D03518907B8AD1D3549@beebe001.NOE.Nokia.com>
From: Yanqun.Le@nokia.com
To: aaa-wg@merit.edu
Subject: [AAA-WG]: [Issue] peer connection inconsistent between base08 and
	 transport05
Date: Sun, 30 Dec 2001 11:39:26 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="gb2312"
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

Submitter name: yanqun le 
Submitter email address: yanqun.le@nokia.com 
Date first submitted: Dec 30, 2001 
Reference:  
Document: Diameter Base -08, dratf-ietf-aaa-transport-05
Comment type: T 
Priority: S
Section: Section 5.1 of Base- 08, Section 3.4.1 of Transport -05
Rationale/Explanation of issue: 
The last third paragraphs in Section 5.1 is inconsistent with Section 3.
4.1 of transport-05.

Requested change: 
The last third paragraphs in Section 5.1 should be changed to:

    When a peer is deemed suspect, which could occur for various
reasons, including not receiving a DWA within an alloted timeframe, no
new requests should be forwarded to the peer, and failover procedures
should be invoked. When an active peer is moved to this mode, additional
connections SHOULD be established to ensure that the necessary number of
active connections exists.

   There are two ways that a peer is removed from the suspect peer list:
      1. the peer's watchdog timer has expired without a response,
causing a trasport reset or close to be done on the connection.
      2. a response is received from the peer within the watchdog timer,
and the connection to the peer is considered stabilized.

   In the event the peer being removed is either the primary or
secondary, an alternate peer SHOULD replace the deleted peer, and assume
the role of either primary or secondary.



From owner-aaa-wg@merit.edu  Sun Dec 30 04:53:55 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14778
	for <aaa-archive@lists.ietf.org>; Sun, 30 Dec 2001 04:53:55 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix)
	id 653A89123B; Sun, 30 Dec 2001 04:53:34 -0500 (EST)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 2F0C69123C; Sun, 30 Dec 2001 04:53:34 -0500 (EST)
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 24C8E9123B
	for <aaa-wg@trapdoor.merit.edu>; Sun, 30 Dec 2001 04:53:33 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id DDB365DE03; Sun, 30 Dec 2001 04:53:32 -0500 (EST)
Delivered-To: aaa-wg@merit.edu
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by segue.merit.edu (Postfix) with ESMTP id 2641E5DDF9
	for <aaa-wg@merit.edu>; Sun, 30 Dec 2001 04:53:31 -0500 (EST)
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fBU9rOC12689
	for <aaa-wg@merit.edu>; Sun, 30 Dec 2001 11:53:24 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T582401a9e4ac158f250ef@esvir05nok.ntc.nokia.com> for <aaa-wg@merit.edu>;
 Sun, 30 Dec 2001 11:53:30 +0200
Received: by esebh01nok with Internet Mail Service (5.5.2652.78)
	id <ZHBSHDVN>; Sun, 30 Dec 2001 11:52:41 +0200
Message-ID: <4AE1AC3D692F55488F2D03518907B8AD1D354B@beebe001.NOE.Nokia.com>
From: Yanqun.Le@nokia.com
To: aaa-wg@merit.edu
Subject: [AAA-WG]: CER first or watchdog first when reopening a connection
Date: Sun, 30 Dec 2001 11:51:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="gb2312"
Sender: owner-aaa-wg@merit.edu
Precedence: bulk

In section3.4.1 [5] of draft-ietf-aaa-trasport-05, it said:
If the connection is successfully opened, then the watchdog message is
sent. Once three watchdog messages have been sent and responded to, the
connection is returned to service, and transactions are once again sent
over it.

I wonder:
When a connection to a peer comes up from DOWN status, i.e. reopen a
connction, does it need exchange capabilities again? 
If capabilities exchange is needed, does it send Watchdog first or
exchange CER/CEA first?


