From owner-aaa-bof@merit.edu  Wed Sep  1 12:22:01 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id MAA12203
	for <aaa-wg-archive@nic.merit.edu>; Wed, 1 Sep 1999 12:22:01 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 8B56D44403; Wed,  1 Sep 1999 12:21:40 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 72C3B4441A; Wed,  1 Sep 1999 12:21:40 -0400 (EDT)
Received: from keith.lloyd.com (keith.lloyd.com [158.222.1.2])
	by segue.merit.edu (Postfix) with ESMTP id D4A7C44403
	for <aaa-wg@merit.edu>; Wed,  1 Sep 1999 12:21:38 -0400 (EDT)
Received: from murray (root@keith.lloyd.com [158.222.1.2])
	by keith.lloyd.com (8.9.3/8.9.1) with SMTP id JAA01797
	for <aaa-wg@merit.edu>; Wed, 1 Sep 1999 09:21:37 -0700 (PDT)
Message-Id: <3.0.6.32.19990901091923.0098a100@127.0.0.1>
X-Sender: brian@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Wed, 01 Sep 1999 09:19:23 -0700
To: AAA WG <aaa-wg@merit.edu>
From: Brian Lloyd <brian@lloyd.com>
Subject: AAA WG minutes and presentations
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

(repost of message sent to the secretariat for offical minutes)

This is not complete because I was only at the first session on Wednesday.
I have been unable to locate minutes from the Friday session other than my
co-chaircritter saying that there was general discussion.

---------- meeting minutes for Wednesday ---------------

Open about 5 minutes late

Paul reitterated that this is not a protocol WG and that discussion of
Diameter vs. COPS is not appropriate

Paul spoke about what and why things are behind schedule

John Volbrecht presented the work of the authorization subgroup

Alex Latzko presented the work of the authentication subgroup (himself)

Nevil Brownlee presente the work of the accounting subgroup

Charlie Perkins presented the AAA needs of Mobil IP

Betty de Bruijn preseneted the relationship between AAA and existing
e-commerce systems

Steven Bakker presented AAA considerations for middleware

Leon Gommans presented how Bandwidth Broker fit into the AAA model

The program ran until 1740 (ten minutes over time)



Brian Lloyd                                    Lucent Technologies
brian@lloyd.com                                3461 Robin Lane, Suite 1
http://www.livingston.com                      Cameron Park, CA  95682
+1.530.676.6513 - voice                        +1.530.676.3442 - fax



From owner-aaa-bof@merit.edu  Fri Sep  3 07:03:21 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id HAA21126
	for <aaa-wg-archive@nic.merit.edu>; Fri, 3 Sep 1999 07:03:20 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 972AC44416; Fri,  3 Sep 1999 07:03:04 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 7CB7A44473; Fri,  3 Sep 1999 07:03:04 -0400 (EDT)
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
	by segue.merit.edu (Postfix) with ESMTP id 6056444416
	for <aaa-wg@merit.edu>; Fri,  3 Sep 1999 07:02:45 -0400 (EDT)
Received: from fokus.gmd.de (dhcp009 [195.37.78.137])
	by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id NAA16510
	for <aaa-wg@merit.edu>; Fri, 3 Sep 1999 13:02:42 +0200 (MET DST)
Message-ID: <37CFAA5D.2639DC6F@fokus.gmd.de>
Date: Fri, 03 Sep 1999 13:00:45 +0200
From: Felix Hartanto <hartanto@fokus.gmd.de>
Reply-To: hartanto@fokus.gmd.de
Organization: GMD FOKUS
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en,zh
MIME-Version: 1.0
To: AAA Mailing List <aaa-wg@merit.edu>
Subject: Policy-based Billing Architecture
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Hi,

We think that our recent work, entitled: 
    "Policy-based Billing Architecture for Internet Differentiated 
     Services"
might be of interest to this mailing list. 

Attached below is the abstract for the paper. The complete paper is 
available online at: 
    http://www.fokus.gmd.de/usr/hartanto/pubs/bc99_ext.ps.gz

We welcome any comments that people might have. 

Best regards
Felix Hartanto

-- 
Felix Hartanto		      http://www.fokus.gmd.de/usr/hartanto
GMD FOKUS                     Phone: +49-30-3463-7136
Kaiserin-Augusta-Allee 31     Fax:   +49-30-3463-8136
D-10589 Berlin, Germany       Email: hartanto@fokus.gmd.de

=====================================================================
Title: Policy-based Billing Architecture for Internet Differentiated 
       Services

Author: Felix Hartanto and Georg Carle

Abstract:
The Differentiated Services architecture allows a service provider to 
configure new services dynamically using a policy protocol. This 
benefit, however, may not be fully realized if the service provider 
can not charge for the services, or need a high effort to update 
its billing system to charge for the services. Thus, there is 
a real need for a flexible billing architecture to complement 
the flexibility offered by the differentiated service model. To meet 
this need, a policy-based billing architecture is proposed in 
this paper. This architecture allows a service provider to define 
policies for configuring various processes of a billing system 
based on the charging and pricing schemes used for individual services. 
It is demonstrated how the architecture supports flat-rate, 
duration-based and volume-based charging, and also both static and 
dynamic pricing. Definitions of policies for various charging and 
pricing schemes are discussed and the potential complexity of each of 
them is analyzed. Based on the complexity analysis we recommend 
the least complex charging schemes for four classes of differentiated 
services, which have been proposed for meeting different application 
requirements.


From owner-aaa-bof@merit.edu  Sat Sep  4 10:52:09 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA12147
	for <aaa-wg-archive@nic.merit.edu>; Sat, 4 Sep 1999 10:52:09 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 05FEE44419; Sat,  4 Sep 1999 10:51:53 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E089A44470; Sat,  4 Sep 1999 10:51:52 -0400 (EDT)
Received: from alien.rs.itd.umich.edu (alien.rs.itd.umich.edu [141.211.83.10])
	by segue.merit.edu (Postfix) with ESMTP id E25F044419
	for <aaa-wg@merit.edu>; Sat,  4 Sep 1999 10:51:51 -0400 (EDT)
Received: from umich.edu (pm457-23.dialip.mich.net [198.110.21.129])
	by alien.rs.itd.umich.edu (8.8.8/2.5) with ESMTP id KAA15914
	for <aaa-wg@merit.edu>; Sat, 4 Sep 1999 10:50:06 -0400 (EDT)
Message-ID: <37D1319C.AFC3AFB7@umich.edu>
Date: Sat, 04 Sep 1999 10:50:04 -0400
From: Wei Wang <weiwang@umich.edu>
Organization: University of Michigan
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.8 i586)
X-Accept-Language: en, zh, zh-CN, zh-TW
MIME-Version: 1.0
To: aaa-wg@merit.edu
Subject: Re: draft-ekstein-roamops-protcomp-00.txt
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

On page 6 of the draft at the top, there is this statement:

      Neither  RADIUS  nor  COPS  support  explicitly  vendor  
specific
      extensibility.

Which, I don't think is true for RADIUS, although the attribute space
for each vendor is again limited to 256 by RFC2138.

Regards,
--
Wei Wang               weiwang@ [umich | merit] .edu
Merit Network, Inc.    http://www-personal.umich.edu/~weiwang/
[Tel] 734-764-2874     [Fax] 734-647-3745


From owner-aaa-bof@merit.edu  Mon Sep  6 03:58:32 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id DAA09036
	for <aaa-wg-archive@nic.merit.edu>; Mon, 6 Sep 1999 03:58:32 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 598BF44429; Mon,  6 Sep 1999 03:58:13 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 39A9D4442D; Mon,  6 Sep 1999 03:58:13 -0400 (EDT)
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
	by segue.merit.edu (Postfix) with ESMTP id 00A9D44429
	for <aaa-wg@merit.edu>; Mon,  6 Sep 1999 03:58:10 -0400 (EDT)
Received: from fokus.gmd.de (dhcp009 [195.37.78.137])
	by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id JAA19734
	for <aaa-wg@merit.edu>; Mon, 6 Sep 1999 09:58:05 +0200 (MET DST)
Message-ID: <37D37395.9A050111@fokus.gmd.de>
Date: Mon, 06 Sep 1999 09:56:05 +0200
From: Felix Hartanto <hartanto@fokus.gmd.de>
Reply-To: hartanto@fokus.gmd.de
Organization: GMD FOKUS
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en,zh
MIME-Version: 1.0
To: AAA Mailing List <aaa-wg@merit.edu>
Subject: Re: Policy-based Billing Architecture
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Hi,

You can also find the PDF version of the paper at: 
   http://www.fokus.gmd.de/usr/hartanto/pubs/bc99_ext.pdf

Best regards
Felix Hartanto

-- 
Felix Hartanto                http://www.fokus.gmd.de/usr/hartanto
GMD FOKUS                     Phone: +49-30-3463-7136
Kaiserin-Augusta-Allee 31     Fax:   +49-30-3463-8136
D-10589 Berlin, Germany       Email: hartanto@fokus.gmd.de


From owner-aaa-bof@merit.edu  Wed Sep  8 16:56:30 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id QAA03049
	for <aaa-wg-archive@nic.merit.edu>; Wed, 8 Sep 1999 16:56:30 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id B20355DD9A; Wed,  8 Sep 1999 16:55:40 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id C76155DDA9; Wed,  8 Sep 1999 16:53:21 -0400 (EDT)
Received: from smtp6.jps.net (smtp6.jps.net [209.63.224.103])
	by segue.merit.edu (Postfix) with ESMTP id F1BC15DDAA
	for <aaa-wg@merit.edu>; Wed,  8 Sep 1999 16:48:58 -0400 (EDT)
Received: from tiger (209-239-201-157.oak.jps.net [209.239.201.157])
	by smtp6.jps.net (8.9.3/8.9.0) with SMTP id NAA01650;
	Wed, 8 Sep 1999 13:48:06 -0700 (PDT)
Message-ID: <006d01befa3c$e7f83de0$02c8a8c0@tiger>
Reply-To: "Pankaj Parekh" <pankaj@tunnelnet.com>
From: "Pankaj Parekh" <pankaj@tunnelnet.com>
To: <hartanto@fokus.gmd.de>, "AAA Mailing List" <aaa-wg@merit.edu>
References: <37CFAA5D.2639DC6F@fokus.gmd.de>
Subject: Re: Policy-based Billing Architecture
Date: Wed, 8 Sep 1999 13:27:23 -0700
Organization: PolicyOne, Inc.
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.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Very interesting paper. I have one question related to pricing. Why isn't
the mechanism in place to compensate the customer for not meeting the
service level guarantees? i.e.


Shouldn't there be

UC = SC + p1*D1/Du + p2*D2/Du where
p1 = f(B) = PBu * B/Bu and
p2 = f(SLA, B) i.e. function of guaranteed bandwidht?

Again I just expressed this for the Duration charging but this can and may
apply to other pricing models also. Let me know what do you think about?

Pankaj Parekh

----- Original Message -----
From: Felix Hartanto <hartanto@fokus.gmd.de>
To: AAA Mailing List <aaa-wg@merit.edu>
Sent: Friday, September 03, 1999 4:00 AM
Subject: Policy-based Billing Architecture


> Hi,
>
> We think that our recent work, entitled:
>     "Policy-based Billing Architecture for Internet Differentiated
>      Services"
> might be of interest to this mailing list.
>
> Attached below is the abstract for the paper. The complete paper is
> available online at:
>     http://www.fokus.gmd.de/usr/hartanto/pubs/bc99_ext.ps.gz
>
> We welcome any comments that people might have.
>
> Best regards
> Felix Hartanto
>
> --
> Felix Hartanto       http://www.fokus.gmd.de/usr/hartanto
> GMD FOKUS                     Phone: +49-30-3463-7136
> Kaiserin-Augusta-Allee 31     Fax:   +49-30-3463-8136
> D-10589 Berlin, Germany       Email: hartanto@fokus.gmd.de
>
> =====================================================================
> Title: Policy-based Billing Architecture for Internet Differentiated
>        Services
>
> Author: Felix Hartanto and Georg Carle
>
> Abstract:
> The Differentiated Services architecture allows a service provider to
> configure new services dynamically using a policy protocol. This
> benefit, however, may not be fully realized if the service provider
> can not charge for the services, or need a high effort to update
> its billing system to charge for the services. Thus, there is
> a real need for a flexible billing architecture to complement
> the flexibility offered by the differentiated service model. To meet
> this need, a policy-based billing architecture is proposed in
> this paper. This architecture allows a service provider to define
> policies for configuring various processes of a billing system
> based on the charging and pricing schemes used for individual services.
> It is demonstrated how the architecture supports flat-rate,
> duration-based and volume-based charging, and also both static and
> dynamic pricing. Definitions of policies for various charging and
> pricing schemes are discussed and the potential complexity of each of
> them is analyzed. Based on the complexity analysis we recommend
> the least complex charging schemes for four classes of differentiated
> services, which have been proposed for meeting different application
> requirements.
>
>



From owner-aaa-bof@merit.edu  Thu Sep  9 02:27:41 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id CAA11949
	for <aaa-wg-archive@nic.merit.edu>; Thu, 9 Sep 1999 02:27:41 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 78A435DD9B; Thu,  9 Sep 1999 02:27:21 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 5918D5DD9D; Thu,  9 Sep 1999 02:27:21 -0400 (EDT)
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
	by segue.merit.edu (Postfix) with ESMTP id 88E005DD9B
	for <aaa-wg@merit.edu>; Thu,  9 Sep 1999 02:27:19 -0400 (EDT)
Received: from fokus.gmd.de (dial-29 [193.174.152.226])
	by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id IAA02086;
	Thu, 9 Sep 1999 08:27:13 +0200 (MET DST)
Message-ID: <37D75345.31FF9F4@fokus.gmd.de>
Date: Thu, 09 Sep 1999 08:27:17 +0200
From: Felix Hartanto <hartanto@fokus.gmd.de>
Organization: GMD FOKUS, Kaiserin-Augusta-Allee 31, D-10589 Berlin, Germany
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Pankaj Parekh <pankaj@tunnelnet.com>
Cc: AAA Mailing List <aaa-wg@merit.edu>
Subject: Re: Policy-based Billing Architecture
References: <37CFAA5D.2639DC6F@fokus.gmd.de> <006d01befa3c$e7f83de0$02c8a8c0@tiger>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Hi Pankaj

> Very interesting paper. I have one question related to pricing. Why isn't
> the mechanism in place to compensate the customer for not meeting the
> service level guarantees? i.e.
> 
> Shouldn't there be
> 
> UC = SC + p1*D1/Du + p2*D2/Du where
> p1 = f(B) = PBu * B/Bu and
> p2 = f(SLA, B) i.e. function of guaranteed bandwidht?
> 
> Again I just expressed this for the Duration charging but this can and may
> apply to other pricing models also. Let me know what do you think about?

Agree. 
Pro-actively compensating customers for not meeting SLA is one feature 
being offered by Frame Relay providers at present. So, we can expect 
that it will become the trend in the Internet environment as well.  

There are a number of ways to compensate the customers, such as giving 
credits or discounts on total bill, adjusting the price based on the 
measured SLA, etc. It depends on the SLA definition and the way to 
monitor and measure the SLA. 
Either way, the billing system needs to interact with SLA monitoring 
system. We have been investigating the method to link these two 
systems together and expect to publish our results in the near future.

Regards
Felix

-- 
Felix Hartanto                http://www.fokus.gmd.de/usr/hartanto
GMD FOKUS                     Phone: +49-30-3463-7136
Kaiserin-Augusta-Allee 31     Fax:   +49-30-3463-8136
D-10589 Berlin, Germany       Email: hartanto@fokus.gmd.de


From owner-aaa-bof@merit.edu  Thu Sep  9 02:50:03 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id CAA12144
	for <aaa-wg-archive@nic.merit.edu>; Thu, 9 Sep 1999 02:50:02 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 7B3E45DD94; Thu,  9 Sep 1999 02:49:44 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 614D05DD9D; Thu,  9 Sep 1999 02:49:44 -0400 (EDT)
Received: from fastmail.vertical.net (fastmail.vertical.net [146.145.74.44])
	by segue.merit.edu (Postfix) with ESMTP id 5CE645DD94
	for <aaa-wg@MERIT.EDU>; Thu,  9 Sep 1999 02:49:43 -0400 (EDT)
Received: from fastmail (172.16.0.44) by fastmail.vertical.net (LSMTP for Windows NT v1.1b) with SMTP id <5.0002DCAC@fastmail.vertical.net>; Thu, 9 Sep 1999 2:37:47 -0400
From: Computer OEM Online <newsletter@vertical.net>
Subject: Computer OEM Online Newsletter
To: aaa-wg@merit.edu
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Message-Id: <19990909064943.5CE645DD94@segue.merit.edu>
Date: Thu,  9 Sep 1999 02:49:43 -0400 (EDT)
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

============================================================
Computer OEM Online Newsletter
Volume 2   Issue 46
Wednesday, September 08, 1999
============================================================

Computer OEM Online's System Strategy case study series continues. Frank Carau,
R&D Lab Manager at Hewlett-Packard's Portable Capture and Communications
facility, describes how code coverage and regression test analyses tools helped
his team speed a 500-000-gate ASIC to successful first-pass completion. Read
about it at http://www2.computeroemonline.com/read/nl19990907/10080.


******** NATIONAL SPONSOR ********

The 9.99% fixed Bank One Platinum Business Card Visa. No annual fee and up
to $25,000 line of credit. Track expenses, simplify tax reporting, and
streamline your finances. Apply online by visiting:
http://app1.firstusa.com/card.cfm/XPL6UBC13/6B3Z


******** Computer OEM Online’s Weekly Selection:  ********

Advanced Routing of Electronic Modules A vision of the future in advanced
electronics by Michael Pecht, Yeun Tsun G.Wong
The rapid growth of the electronic products market has created an increasing
need for affordable, reliable, high-speed and high-density multi-layer printed
circuit boards (PCBs).
Our Price: $95.00!  To read more and purchase this book, visit:
http://www2.computeroemonline.com/read/nl19990907/10138


****** FEATURED ARTICLES selected by Alex Mendelsohn ******

1) Digital Car Stereo DSP Chip Samples
2) Multiple Instruction-Set Technology Takes A Bow
3) Analog Devices Implements Intel Mobile Power Management

------------------------------------------------------------

1) Digital Car Stereo DSP Chip Samples
IC house STMicroelectronics starts sampling a 3 V mixed-signal DSP-based
baseband processor chip for all-digital car stereos. ST's programmable approach
lets you add features simply by changing firmware. Try that with your
conventional analog car stereo!

http://www2.computeroemonline.com/read/nl19990907/10003


2) Multiple Instruction-Set Technology Takes A Bow
As part of the Navy's Dual Use Science & Technology program sponsored by the
Office of Naval Research, CPU Technology, Inc. is developing a core processing
architecture it says will make possible upgraded high-end embedded systems. CPU
Tech will supply a system-on-a-chip that will work/run both legacy processors
and software without changes, and new higher-order languages and commercial off-
the-shelf software tools.

http://www2.computeroemonline.com/read/nl19990907/10004


3) Analog Devices Implements Intel Mobile Power Management
Chip makers Analog Devices releases the industry's first DC-to-DC converter to
incorporate Intel's Mobile Voltage Positioning technology.

http://www2.computeroemonline.com/read/nl19990907/10005


******** EDITOR'S CHOICE PRODUCTS ********

1) ZIF BGA Sockets
2) Display Driver ICs
3) LVT Logic

------------------------------------------------------------

1) ZIF BGA Sockets
Zero insertion force BGA sockets permit repeated tool-free removal and
insertion of ball-grid-array-packaged microprocessors.

http://www2.computeroemonline.com/read/nl19990907/10007


2) Display Driver ICs
Type CS1084, '85, and '86 driver ICs contain the circuitry needed to interface
between a system microprocessor and automotive Vacuum Fluorescent Display
instrumentation.

http://www2.computeroemonline.com/read/nl19990907/10008


3) LVT Logic
Designed for 3.3 V applications, logic line includes the 74LVTH273 octal D-type
flip-flop with Clear, the 74LVT373/74LVTH373 octal transparent latch with three-
state outputs, and the 74LVT374/74LVTH374 octal D-type with three-state
outputs. Available with and without Bus-hold, the high speed (less than 4.5
nanosecond) ICs can be used for off-board driving applications such as
backplanes, memory arrays, telecom switches, and in networking applications.
Bus-hold maintains a valid logic state on an unloaded input, eliminating the
need for external pull-up or pull-down resistors to prevent floating inputs.

http://www2.computeroemonline.com/read/nl19990907/10009


******** ADVERTISEMENT ********

The award winning My Lycos is the fast and easy-to-use start page -
providing you with personalized news, weather, stock quotes, horoscopes,
weather, sports scores and more.  Try it now - http://my.lycos.com.


***** FEATURED COMPANIES (information from sponsors): ******

Visit the companies below for more industry news and product information:

Adapter Technologies Inc. was established in 1994 to provide interconnect
solutions to OEMs that required application specific products to produce their
end products. Working with fortune 100, 500 and 1000 companies world wide,
their products consist from small run to large run production quantities,
research and development products and high end electronic assemblies
encompassing surface mount technologies and thru hole technologies.
Visit Adapter Technologies Inc. at:
http://www2.computeroemonline.com/storefronts/adaptertech.html

NKK Switches provides comprehensive manufacturing, warehousing, and other sales
services from its USA headquarters in Scottsdale, Arizona. An extensive staff
of knowledgeable marketing and sales personnel is on call to provide technical
information as well as pricing and delivery schedules.
Visit NKK Switches at:
http://www2.computeroemonline.com/storefronts/nkk.html

Ziatech Corporation is a leading supplier of rugged CompactPCI® and STD 32®
industrial computers. They manufacture board-level, system-level, and fully
integrated microcomputer products for OEMs and end users seeking to automate
their applications quickly and cost effectively.
Visit Ziatech Corporation at:
http://www2.computeroemonline.com/storefronts/ziatech.html


Thanks for subscribing to Computer OEM Online's weekly newsletter. Tell your
friends and associates about it. Have questions, or suggestions? Call Managing
Editor Alex Mendelsohn at (207) 967-8812.

-------------------------------------------------------------------

If you enjoy reading Computer OEM Online's Newsletter, please tell a
friend or colleague about it.  Anyone can sign up for a free
subscription on our Web site at http://www.computeroemonline.com

--------------------------------------------------------------------

If your company wishes to sponsor this newsletter, please
contact Sherylen Yoak at mailto:syoak@verticalnet.com to learn more.

==========================================================

If you wish to unsubscribe, please go to the following web page:
http://www2.computeroemonline.com/content/newsletter/unsubscribe.asp

==========================================================
The Computer OEM Online Homepage: http://www.computeroemonline.com

(c) Copyright 1999 VerticalNet, Inc. All rights reserved. All
product names contained herein are the trademarks of their
respective holders.





From owner-aaa-bof@merit.edu  Thu Sep  9 10:29:58 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA18382
	for <aaa-wg-archive@nic.merit.edu>; Thu, 9 Sep 1999 10:29:58 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 4B48C5DDF6; Thu,  9 Sep 1999 10:23:09 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 5FF9F5EA1F; Thu,  9 Sep 1999 09:43:29 -0400 (EDT)
Received: from ns.bigbear.net (bay1-67.la.ziplink.net [206.15.155.81])
	by segue.merit.edu (Postfix) with SMTP
	id D5FEA5EAD6; Thu,  9 Sep 1999 08:34:13 -0400 (EDT)
From: <stevee@loop.com>
Subject: helllo
Date: Thu, 9 Sep 1999 02:11:33
Message-Id: <751.289553.437287@ns.bigbear.net>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Dear Future Associate,

You Can Work At Home & Set Your Own Hours.  Start earning Big 
Money in a short time
       
                                    NO Newspaper Advertising!

Your job will be to stuff and mail envelopes for our company. You 
will receive $.25 for each and every envelope you stuff and mail 
out.

Just follow our simple instructions and you will be making money 
as easy as
1… 2… 3

For example stuff and mail 200 envelopes and you will receive 
$50.00. Stuff and mail 1000 and you will receive $250.00. Stuff 
and mail 2000 and you will receive $500.00 and more 

Never before has there been an easier way to make money from 
home!

Our Company's Home Mailing Program is designed for people with 
little or no experience and provides simple, step by step 
instructions.  

There is no prior experience or special skills necessary on your 
part, Just stuffing envelopes.

We need the help of honest and reliable home workers like you.  
Because we are overloaded with work and have more than our staff 
can handle. We have now expanded our mailing program and are 
expecting to reach millions more with our offers throughout the 
US and Canada.

Our system of stuffing and mailing envelopes is very simple and 
easy to do!
You will not be required to buy envelopes or postage stamps.

We will gladly furnish all circulars at no cost to you. We assure 
you that as a participant in our program you will never have to 
mail anything objective or offensive. 

There are no quotas to meet, and there no contracts to sign. You 
can work as much, or as little as you want. Payment for each 
envelope you send out is Guaranteed!

Here is what you will receive when you get your first Package.  
Inside you will find 100 envelopes, 100 labels and 100 sales 
letters ready to stuff and mail

As soon as you are done with stuffing and mailing these first 
letters, your payment will arrive shortly, thereafter. All you 
have to do is to order more free supplies and stuff and mail more 
envelopes to make more money.

Our sales literature which you will be stuffing and mailing will 
contain
information outlining our highly informative manuals that we are
advertising nationwide.  As a free gift you will receive a 
special manual valued at  $24.95, absolutely free, just for 
joining our Home Mailers Program.

Plus you will get your own special code number, so that we will 
know how much you are to get paid.  And to make re-ordering of 
more envelopes, that our company supplies very simple for you.

We are giving you this free bonus because we want you to be 
confident in our company and to ensure that we will be doing 
business with you for a long time.

Benefits Of This Job:

1. You do not have to quit your present job, to earn more money 
at home
2. You can make between $2,500 to $4,500 a month depending on the 
amount of time you are willing to spend stuffing and mailing 
envelopes
3. This is a great opportunity for the students, mothers, 
disabled persons or those who are home bodies.

To secure your position and to show us that you are serious about 
earning extra income at home we require a one-time registration 
fee of $35.00.
This fee covers the cost of your initial start up package,  which 
includes 100 envelopes, 100 labels and 100 sales letters and a 
manual, your registration fee will be refunded back to you 
shortly thereafter.

Money Back Guarantee!

We guarantee that as soon as you stuff and mail your first 300 
envelopes You will be paid $75.00 and your registration fee will 
be refunded.

Many of you wonder why it is necessary to pay a deposit to get a 
job. It is because we are looking for people that seriously want 
to work from home.  

*  If 3.000 people told us they wanted to start working from home 
and we sent out 3.000 packages free to every one.  And then half 
of the people decided not to work, this would be a potential loss 
of more than $60,000 in supply's and shipping that we have sent 
out to people that don't want to work

We have instituted this policy to make sure that you really want 
to work and at least finish your first package.

To Get Started Today Please Enclose Your Registration Fee of $35
Check,Cash Or Money Order and fill out the application below and 
mail to:

MOHW Co	
PMB
11054 Ventura Blvd #126	
Studio City, CA 91604

Name_____________________________________________________

Address___________________________________________________

City____________________________________ State______________

Zip Code________________

Telephone Number(s)_________________________________________

E-mail Address______________________________________________



For all orders, please allow seven (7) days for delivery and up 
to 10 days. Cash and Money Orders will result in faster shipping 
of your package.
 
 
 
 
 
 
 
 
 
 
 
 


From owner-aaa-bof@merit.edu  Thu Sep  9 10:35:04 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA18482
	for <aaa-wg-archive@nic.merit.edu>; Thu, 9 Sep 1999 10:35:04 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 9A9285DDB9; Thu,  9 Sep 1999 10:34:29 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E4BAF5DE9D; Thu,  9 Sep 1999 10:31:32 -0400 (EDT)
Received: from gmtsw.com (test.glassey.com [207.126.98.130])
	by segue.merit.edu (Postfix) with SMTP id 3AF105E16D
	for <aaa-wg@merit.edu>; Thu,  9 Sep 1999 10:28:09 -0400 (EDT)
Received: from PC1 by gmtsw.com (SMI-8.6/SMI-SVR4)
	id HAA26306; Thu, 9 Sep 1999 07:28:24 -0700
Message-ID: <04d201befad1$d06dd3c0$0b0aff0c@lab.gmtsw.com>
From: "todd@gmtsw" <todd.glassey@www.gmtsw.com>
To: "Felix Hartanto" <hartanto@fokus.gmd.de>,
        "Pankaj Parekh" <pankaj@tunnelnet.com>
Cc: "AAA Mailing List" <aaa-wg@merit.edu>
References: <37CFAA5D.2639DC6F@fokus.gmd.de> <006d01befa3c$e7f83de0$02c8a8c0@tiger> <37D75345.31FF9F4@fokus.gmd.de>
Subject: Re: Policy-based Billing Architecture
Date: Thu, 9 Sep 1999 07:44:20 -0700
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.00.2918.2701
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Have we considered adding event based billing models as well to the policy
control framework. Seems to me that the real goal could be one of
establishing some event representation services and then a policy control
framework for managing them..


Todd

----- Original Message -----
From: Felix Hartanto <hartanto@fokus.gmd.de>
To: Pankaj Parekh <pankaj@tunnelnet.com>
Cc: AAA Mailing List <aaa-wg@merit.edu>
Sent: Wednesday, September 08, 1999 11:27 PM
Subject: Re: Policy-based Billing Architecture


> Hi Pankaj
>
> > Very interesting paper. I have one question related to pricing. Why
isn't
> > the mechanism in place to compensate the customer for not meeting the
> > service level guarantees? i.e.
> >
> > Shouldn't there be
> >
> > UC = SC + p1*D1/Du + p2*D2/Du where
> > p1 = f(B) = PBu * B/Bu and
> > p2 = f(SLA, B) i.e. function of guaranteed bandwidht?
> >
> > Again I just expressed this for the Duration charging but this can and
may
> > apply to other pricing models also. Let me know what do you think about?
>
> Agree.
> Pro-actively compensating customers for not meeting SLA is one feature
> being offered by Frame Relay providers at present. So, we can expect
> that it will become the trend in the Internet environment as well.
>
> There are a number of ways to compensate the customers, such as giving
> credits or discounts on total bill, adjusting the price based on the
> measured SLA, etc. It depends on the SLA definition and the way to
> monitor and measure the SLA.
> Either way, the billing system needs to interact with SLA monitoring
> system. We have been investigating the method to link these two
> systems together and expect to publish our results in the near future.
>
> Regards
> Felix
>
> --
> Felix Hartanto                http://www.fokus.gmd.de/usr/hartanto
> GMD FOKUS                     Phone: +49-30-3463-7136
> Kaiserin-Augusta-Allee 31     Fax:   +49-30-3463-8136
> D-10589 Berlin, Germany       Email: hartanto@fokus.gmd.de
>
>



From owner-aaa-bof@merit.edu  Thu Sep  9 17:52:47 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA03971
	for <aaa-wg-archive@nic.merit.edu>; Thu, 9 Sep 1999 17:52:46 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A942F5DDA2; Thu,  9 Sep 1999 17:52:27 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8A3D35DDA5; Thu,  9 Sep 1999 17:52:27 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 479665DDA2
	for <AAA-WG@Merit.edu>; Thu,  9 Sep 1999 17:52:26 -0400 (EDT)
Received: from Merit.edu (dwspencepc.merit.edu [198.108.62.224]) by home.merit.edu (8.8.8/merit-2.0) with ESMTP id RAA08421 for <AAA-WG@Merit.edu>; Thu, 9 Sep 1999 17:52:26 -0400 (EDT)
Message-ID: <37D82C19.A9E304B4@Merit.edu>
Date: Thu, 09 Sep 1999 17:52:25 -0400
From: "David W. Spence" <DWSpence@merit.edu>
Organization: Merit Network, Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: AAA WG <AAA-WG@merit.edu>
Subject: September 3 Meeting of Authorization Subgroup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

      The Authorization Subgroup of the AAA WG met on Friday Sept. 3, 
      1999 via telephone conference.
      
      The following people participated in the call:
      
         Leon Gommans
         John Vollbrecht
         Pat Calhoun
         Steve Farrell
         Garrept Hussey
         Brian Lloyd
         David Spence
         
      1. Discussion of IESG Actions
         
         The roamops wg has been directed to finish up their phone-book 
         effort and then close down.  Roamops had considered the need to 
         develop an interim AAA protocol for use until aaa wg considers 
         the broader picture and standardizes a more general AAA 
         protocol.   The aaa wg has been directed to complete its 
         requirements drafts by the internet draft cutoff preceding the 
         Washington DC meeting.  If the aaa wg cannot do this then an 
         interim AAA protocol bof may be convened in Washington.  Part 
         of the rationale for creating a new bof rather than doing the 
         work in roamops is that the roamops wg is in the Operations and 
         Management Area and is not the appropriate place to design a 
         AAA protocol.
         
         The CDMA 3G work was depending on the outcome of the roamops 
         work, so these decisions affect their work as well.
         
         This action increases the pressure on the aaa wg to complete 
         its requirements.  Brian Lloyd reiterated the need for a 
         specification of AAA requirements for a broad spectrum of 
         applications.
         
      2. Work Items
         
         David Spence will continue to act as secretary in compiling the 
         authorization requirements draft.  Draft authors should send 
         material to be included in the draft to DWSpence@Merit.edu.
         
         We continued discussing candidate requirements subheadings from 
         where we left off last week.  Pat Calhoun feels proxy 
         requirements are important.  Steve Farrell volunteered to 
         tackle proxy requirements.  Pat will review Steve's 
         contribution and add roamops requirements.  John Vollbrecht 
         suggested making this heading proxy/broker.
         
         There was a brief discussion of attribute certificates.
         
         We reconfirmed our target date of Oct. 15 for the next version 
         of our draft.  That means we should have all material submitted 
         by Sept. 30 to leave time for final edits and final discussion 
         before draft publication.
         
      3. Next Telephone Conferences
      
         Sept. 10 at 1530 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         Sept. 17 at 1530 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         Sept. 24 at 1530 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         Oct.   1 at 1530 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)

-- 
David W. Spence                                email: DWSpence@Merit.edu
Senior Systems Research Programmer             phone: (734) 615-2630
Merit Network, Inc.                            fax:   (734) 647-3745
4151 Plymouth Road, Suite C
Ann Arbor MI 48105-2785
U.S.A.


From owner-aaa-bof@merit.edu  Fri Sep 10 03:39:45 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id DAA12696
	for <aaa-wg-archive@nic.merit.edu>; Fri, 10 Sep 1999 03:39:44 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id C2EC05DDAE; Fri, 10 Sep 1999 03:39:25 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 96B9D5DDAD; Fri, 10 Sep 1999 03:39:25 -0400 (EDT)
Received: from fastmail.vertical.net (fastmail.vertical.net [146.145.74.44])
	by segue.merit.edu (Postfix) with ESMTP id 1433B5DDAD
	for <aaa-wg@MERIT.EDU>; Fri, 10 Sep 1999 03:39:24 -0400 (EDT)
Received: from fastmail (172.16.0.44) by fastmail.vertical.net (LSMTP for Windows NT v1.1b) with SMTP id <1.000349B9@fastmail.vertical.net>; Fri, 10 Sep 1999 3:27:24 -0400
From: Embedded Technology <newsletter@vertical.net>
Subject: Embedded Technology Newsletter
To: aaa-wg@merit.edu
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Message-Id: <19990910073924.1433B5DDAD@segue.merit.edu>
Date: Fri, 10 Sep 1999 03:39:24 -0400 (EDT)
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

============================================================
Embedded Technology.com Newsletter
Volume 1   Issue 18
Thursday, September 09, 1999
============================================================



******** NATIONAL SPONSOR ********

The 9.99% fixed Bank One Platinum Business Card Visa. No annual fee and up
to $25,000 line of credit. Track expenses, simplify tax reporting, and
streamline your finances. Apply online by visiting:
http://app1.firstusa.com/card.cfm/XPL6UBC13/6B3Z


******** Embedded Technology.com’s Weekly Selection: *******

A Practitioner's Guide to RISC Microprocessor Architecture by Patrick H. Stakem
An introduction to Reduced Instruction Set Microprocessors which is a subfield
of RISC.
Retail Price: $82.95 Our Price: $70.99! You Save: $11.96 (14%)
To read more and purchase this book, visit:
http://www2.embeddedtechnology.com/read/nl19990907/10141


****** FEATURED ARTICLES selected by Bruce Bennett *****

1) Uniform Device Driver Spec Ready for Implementation
2) SBS Develops K2 CPCI Board Targeting Telecom Applications
3) Fujitsu Mikrolektronik Restructures

------------------------------------------------------------

1) Uniform Device Driver Spec Ready for Implementation
Members of Project UDI today announced the release of the UDI (Uniform Driver
Interface) 1.0 Specification. This Specification is the culmination of a multi-
company development effort designed to provide device driver portability for
existing and future system configurations.

http://www2.embeddedtechnology.com/read/nl19990907/10054


2) SBS Develops K2 CPCI Board Targeting Telecom Applications
SBS Technologies, Inc. has announced the availability of K2, a 6U cPCI board
targeting high performance telecommunications applications requiring hot-swap,
system/non-system slot functionality, and versatile I/O with dual PMC slots.

http://www2.embeddedtechnology.com/read/nl19990907/10056


3) Fujitsu Mikrolektronik Restructures
Fujitsu Mikroelektronik GmbH in Dreieich-Buchschlag, Frankfurt, Germany has
announced that as part of a restructuring of its European operations, it will
now function as the European headquarters of Fujitsu Microelectronics Europe
GmbH.  Known as Fujitsu Microelectronics Europe (FME), the company will combine
the activities of Marketing, Design Centres and Sales Offices in the UK,
Germany, France, Italy, Sweden.

http://www2.embeddedtechnology.com/read/nl19990907/10059


******** EDITOR'S CHOICE PRODUCTS ********

1) Multimedia PC
2) Emulator
3) I/O Solutions Guide

------------------------------------------------------------

1) Multimedia PC
The SBC-Media GX is an EBX-compliant board based on the MMX-enhanced 233-MHz
MediaGX processor. -- Arcom Control Systems, Kansas City, MO.

http://www2.embeddedtechnology.com/read/nl19990907/8882


2) Emulator
The USP-51A emulator with a POD32X2-60 fully emulates the TS80C32X2 device in
targets at the maximum clock speed of 64 MHz. -- Signum Systems, Moorpark, CA.

http://www2.embeddedtechnology.com/read/nl19990907/8884


3) I/O Solutions Guide
The company’s catalog features a range of VMEbus boards, PC cards and
IndustryPack mezzanine modules.  The boards perform analog I/O, digital I/O and
serial communication functions. -- Acromag, Wixom, MI.

http://www2.embeddedtechnology.com/read/nl19990907/10050


******** ADVERTISEMENT ********

The award winning My Lycos is the fast and easy-to-use start page -
providing you with personalized news, weather, stock quotes, horoscopes,
weather, sports scores and more.  Try it now - http://my.lycos.com.


****** FEATURED COMPANY (information from sponsors): ******

Visit the company below for more industry news and product information:

The Embedded Initiative is a partner program, created by Annasoft Systems in
1997, focused on providing ready-to-run Windows CE platform solutions. These
solutions consist of embedded PC hardware combined with Annasoft software that
enable OEM manufacturers of embedded and dedicated systems to run Windows CE
off-the-shelf, without adaptation or driver development, on a wide range of
commercially available single board computers and modules.
Visit Annasoft Systems at:
http://www2.embeddedtechnology.com/storefronts/embeddedinitiative.html


The Embedded Systems Conference in San Jose, CA is just two weeks away (Sept.
27 to Sept. 30). Be sure to watch for our extensive coverage of the event on
Embedded Technology.com.

-------------------------------------------------------------------

If you enjoy reading Embedded Technology's Newsletter, please tell a
friend or colleague about it.  Anyone can sign up for a free
subscription on our Web site at http://www.embeddedtechnology.com

--------------------------------------------------------------------

If you're a company that wishes to sponsor this newsletter, please
contact Sherylen Yoak at mailto:syoak@verticalnet.com to learn more.

==========================================================

If you wish to unsubscribe, please go to the following web page:
http://www2.embeddedtechnology.com/content/newsletter/unsubscribe.asp

==========================================================
The Embedded Technology Homepage: http://www.embeddedtechnology.com

(c) Copyright 1999 VerticalNet, Inc. All rights reserved. All
product names contained herein are the trademarks of their
respective holders.





From owner-aaa-bof@merit.edu  Fri Sep 10 15:57:32 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id PAA05657
	for <aaa-wg-archive@nic.merit.edu>; Fri, 10 Sep 1999 15:57:32 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 380615DDC0; Fri, 10 Sep 1999 15:57:12 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E75AB5DDC3; Fri, 10 Sep 1999 15:57:11 -0400 (EDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by segue.merit.edu (Postfix) with ESMTP id 229DF5DDC0
	for <aaa-wg@merit.edu>; Fri, 10 Sep 1999 15:57:10 -0400 (EDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id UAA142424; Fri, 10 Sep 1999 20:57:07 +0100
Received: from hursley.ibm.com (lig32-225-118-114.us.lig-dial.ibm.com [32.225.118.114]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id UAA30256; Fri, 10 Sep 1999 20:57:03 +0100 (BST)
Message-ID: <37D9468E.1F556B4C@hursley.ibm.com>
Date: Fri, 10 Sep 1999 12:57:34 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM Internet Division
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
To: "todd@gmtsw" <todd.glassey@www.gmtsw.com>
Cc: Felix Hartanto <hartanto@fokus.gmd.de>,
        Pankaj Parekh <pankaj@tunnelnet.com>,
        AAA Mailing List <aaa-wg@merit.edu>
Subject: Re: Policy-based Billing Architecture
References: <37CFAA5D.2639DC6F@fokus.gmd.de> <006d01befa3c$e7f83de0$02c8a8c0@tiger> <37D75345.31FF9F4@fokus.gmd.de> <04d201befad1$d06dd3c0$0b0aff0c@lab.gmtsw.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Todd,

We probably don't want to go further than accounting models
in the IETF; billing really isn't our thing. We certainly
don't talk about specific business models here; that's
lawyer bait that the IETF doesn't need.

  Brian

todd@gmtsw wrote:
> 
> Have we considered adding event based billing models as well to the policy
> control framework. Seems to me that the real goal could be one of
> establishing some event representation services and then a policy control
> framework for managing them..
> 
> Todd
> 
> ----- Original Message -----
> From: Felix Hartanto <hartanto@fokus.gmd.de>
> To: Pankaj Parekh <pankaj@tunnelnet.com>
> Cc: AAA Mailing List <aaa-wg@merit.edu>
> Sent: Wednesday, September 08, 1999 11:27 PM
> Subject: Re: Policy-based Billing Architecture
> 
> > Hi Pankaj
> >
> > > Very interesting paper. I have one question related to pricing. Why
> isn't
> > > the mechanism in place to compensate the customer for not meeting the
> > > service level guarantees? i.e.
> > >
> > > Shouldn't there be
> > >
> > > UC = SC + p1*D1/Du + p2*D2/Du where
> > > p1 = f(B) = PBu * B/Bu and
> > > p2 = f(SLA, B) i.e. function of guaranteed bandwidht?
> > >
> > > Again I just expressed this for the Duration charging but this can and
> may
> > > apply to other pricing models also. Let me know what do you think about?
> >
> > Agree.
> > Pro-actively compensating customers for not meeting SLA is one feature
> > being offered by Frame Relay providers at present. So, we can expect
> > that it will become the trend in the Internet environment as well.
> >
> > There are a number of ways to compensate the customers, such as giving
> > credits or discounts on total bill, adjusting the price based on the
> > measured SLA, etc. It depends on the SLA definition and the way to
> > monitor and measure the SLA.
> > Either way, the billing system needs to interact with SLA monitoring
> > system. We have been investigating the method to link these two
> > systems together and expect to publish our results in the near future.
> >
> > Regards
> > Felix
> >
> > --
> > Felix Hartanto                http://www.fokus.gmd.de/usr/hartanto
> > GMD FOKUS                     Phone: +49-30-3463-7136
> > Kaiserin-Augusta-Allee 31     Fax:   +49-30-3463-8136
> > D-10589 Berlin, Germany       Email: hartanto@fokus.gmd.de
> >
> >



From owner-aaa-bof@merit.edu  Tue Sep 14 11:28:52 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA11995
	for <aaa-wg-archive@nic.merit.edu>; Tue, 14 Sep 1999 11:28:51 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 978735DD9C; Tue, 14 Sep 1999 11:28:31 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 7AAE15DD9F; Tue, 14 Sep 1999 11:28:31 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 8D8695DD9C
	for <AAA-WG@Merit.edu>; Tue, 14 Sep 1999 11:28:30 -0400 (EDT)
Received: from Merit.edu (dwspencepc.merit.edu [198.108.62.224]) by home.merit.edu (8.8.8/merit-2.0) with ESMTP id LAA17234 for <AAA-WG@Merit.edu>; Tue, 14 Sep 1999 11:28:30 -0400 (EDT)
Message-ID: <37DE699E.C29A9F12@Merit.edu>
Date: Tue, 14 Sep 1999 11:28:30 -0400
From: "David W. Spence" <DWSpence@merit.edu>
Organization: Merit Network, Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: AAA WG <AAA-WG@merit.edu>
Subject: September 10 Meeting of Authorization Subgroup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

      The Authorization Subgroup of the AAA WG met on Friday Sept. 10, 
      1999, 15:30-16:40 UTC, via telephone conference.
      
      The following people participated in the call:
      
         Matt Holdrege
         George Gross
         Gopal Iyengar
         John Vollbrecht
         Stephen Farrell
         David Spence
         
      1. Data Representation
      
         George Gross discussed the work he is doing on data 
         representation requirements.  He is looking at CORBA.  He 
         explained the approach they take in their General Inter-org 
         Protocols (GIOP) and their Internet Inter-org Protocols (IIOP).
      
      2. Attribute Certificates
         
         George asked Stephen Farrell to explain how attribute 
         certificates are organized and encoded.  Stephen explained that 
         attribute certificates are based on X.509 and use an encoding 
         based on ASN.1.  Work on adapting X.509 for use in the Internet 
         is being carried out in the IETF by the PKIX WG.  Attribute 
         certificates are fairly flexible.  They may contain many 
         attributes.  Attributes can be encrypted independently of each 
         other for different recipients.  Attributes may be ordered as 
         needed, and an attribute value may be structured, permitting 
         arbitrary attribute complexity.  As suggested in our 
         authorization draft, it may be desirable to encapsulate 
         attribute certificates within a AAA protocol.  But beyond the 
         need for encapsulation, the organization and security model 
         behind attribute certificates may provide some guidance for 
         tackling the general authorization data representation problem.  
         Stephen referred us to the Internet Draft 
         
            draft-ietf-pkix-ac509prof-00.txt
            "An Internet AttributeCertificate Profile Authorization"
         
         for more information on attribute certificates.
      
      3. Assignments
         
         George Gross will continue work on data representation.
         
         John Vollbrecht will try to contact Nevil Brownlee regarding 
         requirements for session identifiers.
         
         Stephen Farrell will begin collecting general requirements.
         
         Other people are working on various things as agreed during 
         past phone conferences.
      
      4. Next Telephone Conferences
      
         Sept. 17 at 1530 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         Sept. 24 at 1530 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         Oct.   1 at 1530 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)

-- 
David W. Spence                                email: DWSpence@Merit.edu
Senior Systems Research Programmer             phone: (734) 615-2630
Merit Network, Inc.                            fax:   (734) 647-3745
4151 Plymouth Road, Suite C
Ann Arbor MI 48105-2785
U.S.A.


From owner-aaa-bof@merit.edu  Wed Sep 15 14:04:01 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id OAA06424
	for <aaa-wg-archive@nic.merit.edu>; Wed, 15 Sep 1999 14:04:01 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A76F65DEAF; Wed, 15 Sep 1999 13:38:36 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 29E8C5DDF8; Tue, 14 Sep 1999 16:19:21 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by segue.merit.edu (Postfix) with ESMTP id E4FFB5DDF6
	for <aaa-wg@merit.edu>; Tue, 14 Sep 1999 16:19:19 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id QAA25334
	for <aaa-wg@merit.edu>; Tue, 14 Sep 1999 16:19:19 -0400 (EDT)
Received: from luna3.lc.lucent.com (h192-11-90-7.lucent.com [192.11.90.7])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id QAA25318
	for <aaa-wg@merit.edu>; Tue, 14 Sep 1999 16:19:18 -0400 (EDT)
Received: by luna3.lc.lucent.com (SMI-8.6/EMS-1.3.1 sol2)
	id QAA20591; Tue, 14 Sep 1999 16:19:02 -0400
From: gmgross@lucent.com (luna3!gmg)
Received: by luna3.lc.lucent.com (SMI-8.6/EMS-1.3.1 sol2)
	id QAA20574; Tue, 14 Sep 1999 16:19:01 -0400
Date: Tue, 14 Sep 1999 16:19:01 -0400
Message-Id: <199909142019.QAA20574@luna3.lc.lucent.com>
Original-From: gmg@luna3.lc.lucent.com (luna3!gmg)
To: aaa-wg@merit.edu
Subject: AAA data representation reqs...
Content-Type: text
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Hi,
	This is a re-send, as I suspect that I used the wrong mail list
alias "aaa-bof@merit.edu" for my first try. If you have already received
this E-mail, please delete the extra, my apologies for the wasted bandwidth...

	George
=======
Hi,

	In follow up to an action item that I took at the last Authorization
sub-group conference call that I attended, I'm enumerating below a candidate
list of AAA protocol data representation requirements. The goal is to ferment
discussion on this list, and eventually place text shaped by that discussion
into a AAA working group requirements document. In the short term, that text
will likely get inserted in the Authorization requirements draft (chapter 4).

	This requirements list is only a first pass, a guessimate swipe
to discover what makes sense, and no doubt there are many other additions or
modifications that all of you may wish to contribute. IMHO, these functions
are similar to those one would expect from an OSI presentation layer. To
a large extent, I've borrowed from the object oriented framework of CORBA's
Generic Inter-ORB Protocol (GIOP) Common Data Representation (CDR). The V2
specs can be downloaded from www.omg.org.

	Of course, other approaches are also feasible. For example, I've
skimmed through, but will offer no opinion yet on the following
proposals/schemes:

a. SOAP, Simple Object Access Protocol, a recent XML over HTTP proposal:

   http://www.ietf.org/internet-drafts/draft-box-http-soap-00.txt

b. SPADE, Simple Protocol Application Data Encoding

   http://www.ietf.org/internet-drafts/draft-hudson-spade-03.txt

c. Payload Parameter Packaging Scheme:

   http://www.ietf.org/internet-drafts/draft-saraswat-payload-00.txt

d. XDR, RFC1832

e. IOTP, an XML based E-commerce protocol

  http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-v1.0-protocol-06.txt


	I suspect that only an extremely flexible object oriented data
representation and method invocation scheme, such as that examplified by
GIOP CDR, can straddle the breadth of applications being considered for
inclusion by the AAA working group. The key challenges will be strengthening
the security for cross-domain applications, and making the packaging/unpacking
of the data sufficiently lightweight (i.e. an earlier thread on this list
back around January 1999 had thrashed XML for its performance penalty, please
let's not retread that again).

	George

Requirements list follows:

 1. Definition: An object is a composite data structure, formed by the
    aggregration of primitive data types, arrays, and nested objects
    ordered in a well defined sequence. An object's class will have zero
    or more methods (operators) defined as its externally visible
    interface. Each such method in that interface accepts input object
    parameters, and returns output object parameters and a return value.

 2. The AAA message data representation serialization procedure is required
    to encode one or more objects into an unambiguous sequence of octets that
    can be transmitted to a cooperating peer AAA message receiver.  The
    peer AAA message data representation de-serialization procedure
    is required to decode that same octet sequence into a semantically
    equivalent set of object(s) even if the decoding procedure is being
    executed on a heterogenous operating system or hardware architecture
    than the one that encoded that object.

 3. Objects that are nested (i.e. contained) within an object are encoded
    using one of four techniques:

	a) an object instance encoded directly inline as a sequence of typed
           values nested within the containing object's octet stream,

	b) referenced by a "pointer" to another object instance already encoded
           within the same AAA message octet stream,

	c) encapsulation of an object instance's value, whose type definition
           was previously declared in a data dictionary.  This differs from
           case a) in that this object's type definition had already been
           added to the dictionary by an earlier object instance, and so
           this object instance value can be mapped by refering back to
           that earlier object's type definition.

	d) when an object class is derived from a super-class, then the
           super class object instance is encoded as per case c), but it is
           defined to be at a well known implicit location within the serialized
           octet stream (e.g. leftmost nested object of this object instance)

 4. The process sending an object's value to a peer should be able to
    serialize that object into an octet stream, without having to know
    a priori a statically defined attribute/value pair (AVP) tag type for
    each data element within that object. In other words, the AAA protocol
    data representation is application domain independent, and one should not
    have to extend the AAA protocol handler to introduce a new AVP lexicon for
    every new application domain to which the AAA protocol is being applied.
    Instead, the application layer peers should be able to agree to common
    set of application specific object classes, which are transfered using
    the underlying AAA data representation layer syntax.

 5. The process receiving an object's value from a peer should be able to
    de-serialize that object into its equivalent local representation, and pass
    that resulting object into a target object's method entry point as
    a parameter, without requiring any application domain specific program
    logic.

 6. It should be possible for an object's encoding to reference, using a
    message relative index, other object instances contained within the
    same AAA protocol message.

 7. An array is an aggregration of objects having an identical type. They
    are indexed by an unsigned integer ranging in value from zero to one
    less than the size of the array. Each object element in the array
    occupies a fixed number of octets. The number of array elements is
    variable, and it is encoded within the AAA protocol message.

 8. Each object instance value within an AAA message must be capable of being
    digitally signed.

 9. The serialization procedure should be able to encapsulate X.509
    public key or X.509 attribute certificates as an opaque object within
    the AAA message. The de-serialization procedure must recognize X.509
    certificate objects.

 10. An object having a well known type agreed to by the cooperating peers
     can be encapsulated in an <object type identifier/length/value> message
     element. The object's encoding must specify its object type identifier,
     its length, followed by a sequence of binary octets that form the object's
     value.  Unlike a fixed AVP address space scheme, the cooperating peers
     must dynamically and explicitly define through negotiation
     during their session the data dictionary specifying the lexicon
     of <object type identifier/length/value> message elements that they
     are capable of sending and receiving.

 12. An object type identifier must encode the following information:

      - the object class's hierarchy of object super-class(es) names from which
        this class is derived. Multiple inheritance is not supported.

      - An object class's version number and/or most recent modification
        date and timestamp.

      - the name of the application specific object class hierarchy from
        which this object class is rooted

 13. Primitive data types that must be supported as object data members:

	Boolean
	Unsigned two's complement 16-bit, 32-bit, and 64-bit integer
	Signed two's complement 16-bit, 32-bit, and 64-bit integer
	ANSI IEEE 754-1985 compliant single precision floating point (float)
	ANSI IEEE 754-1985 compliant double precision floating point (double)
	Packed decimal
	UTF-8 string
	wide characters: 1, 2, or 4 bytes wide
	enumeration, an integer value constrained to be a member of a set

 14. other Primitive data type requirements:
	- byte swapping is done by the receiver (if it is nescessary)
	- strings may be up to 65KB long
	- basic types are always aligned within a message on their boundaries

 15. The data representation must support the concept of unions, which
     overlap a single storage region with one or more data mappings;
     one of the union data members is declared to be a discriminator tag.

 16. Each object class method shall declare a symbolic name unique within
     the scope of that object class, which can be declared as a calling sequence
     having a set of input parameters, output parameters, a return value
     type, and contextual information (i.e. environment/globals).
     An AAA message must be able to refer to one of a target object instance's
     methods, that is to be executed with parameter objects supplied in the
     same AAA message. 





From owner-aaa-bof@merit.edu  Wed Sep 15 14:04:10 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id OAA06442
	for <aaa-wg-archive@nic.merit.edu>; Wed, 15 Sep 1999 14:04:10 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id D43DC5DF2C; Wed, 15 Sep 1999 13:39:04 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E3CAD5DE66; Wed, 15 Sep 1999 12:31:37 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by segue.merit.edu (Postfix) with ESMTP id 737125DE65
	for <aaa-wg@merit.edu>; Wed, 15 Sep 1999 12:31:27 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id MAA24902
	for <aaa-wg@merit.edu>; Wed, 15 Sep 1999 12:31:16 -0400 (EDT)
Received: from luna3.lc.lucent.com (h192-11-90-7.lucent.com [192.11.90.7])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id MAA24894
	for <aaa-wg@merit.edu>; Wed, 15 Sep 1999 12:31:16 -0400 (EDT)
Received: by luna3.lc.lucent.com (SMI-8.6/EMS-1.3.1 sol2)
	id MAA27046; Wed, 15 Sep 1999 12:30:57 -0400
From: gmgross@lucent.com (luna3!gmg)
Received: by luna3.lc.lucent.com (SMI-8.6/EMS-1.3.1 sol2)
	id MAA27039; Wed, 15 Sep 1999 12:30:56 -0400
Date: Wed, 15 Sep 1999 12:30:56 -0400
Message-Id: <199909151630.MAA27039@luna3.lc.lucent.com>
Original-From: gmg@luna3.lc.lucent.com (luna3!gmg)
To: aaa-wg@merit.edu
Cc: gmgross@lucent.com
Subject: AAA msg data representation reqs...
Content-Type: text
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Hi,
	I've been having trouble with my attempts earlier this week
to send E-mail to this list, please excuse this extra copy if you'd
already received the previous tries...

	George
=============

	In follow up to an action item that I took at the last Authorization
sub-group conference call that I attended, I'm enumerating below a candidate
list of AAA protocol data representation requirements. The goal is to ferment
discussion on this list, and eventually place text shaped by that discussion
into a AAA working group requirements document. In the short term, that text
will likely get inserted in the Authorization requirements draft (chapter 4).

	This requirements list is only a first pass, a guessimate swipe
to discover what makes sense, and no doubt there are many other additions or
modifications that all of you may wish to contribute. IMHO, these functions
are similar to those one would expect from an OSI presentation layer. To
a large extent, I've borrowed from the object oriented framework of CORBA's
Generic Inter-ORB Protocol (GIOP) Common Data Representation (CDR). The V2
specs can be downloaded from www.omg.org.

	Of course, other approaches are also feasible. For example, I've
skimmed through, but will offer no opinion yet on the following
proposals/schemes:

a. SOAP, Simple Object Access Protocol, a recent XML over HTTP proposal:

   http://www.ietf.org/internet-drafts/draft-box-http-soap-00.txt

b. SPADE, Simple Protocol Application Data Encoding

   http://www.ietf.org/internet-drafts/draft-hudson-spade-03.txt

c. Payload Parameter Packaging Scheme:

   http://www.ietf.org/internet-drafts/draft-saraswat-payload-00.txt

d. XDR, RFC1832

e. IOTP, an XML based E-commerce protocol

  http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-v1.0-protocol-06.txt


	I suspect that only an extremely flexible object oriented data
representation and method invocation scheme, such as that examplified by
GIOP CDR, can straddle the breadth of applications being considered for
inclusion by the AAA working group. The key challenges will be strengthening
the security for cross-domain applications, and making the packaging/unpacking
of the data sufficiently lightweight (i.e. an earlier thread on this list
back around January 1999 had thrashed XML for its performance penalty, please
let's not retread that again).

	George

Requirements list follows:

 1. Definition: An object is a composite data structure, formed by the
    aggregration of primitive data types, arrays, and nested objects
    ordered in a well defined sequence. An object's class will have zero
    or more methods (operators) defined as its externally visible
    interface. Each such method in that interface accepts input object
    parameters, and returns output object parameters and a return value.

 2. The AAA message data representation serialization procedure is required
    to encode one or more objects into an unambiguous sequence of octets that
    can be transmitted to a cooperating peer AAA message receiver.  The
    peer AAA message data representation de-serialization procedure
    is required to decode that same octet sequence into a semantically
    equivalent set of object(s) even if the decoding procedure is being
    executed on a heterogenous operating system or hardware architecture
    than the one that encoded that object.

 3. Objects that are nested (i.e. contained) within an object are encoded
    using one of four techniques:

	a) an object instance encoded directly inline as a sequence of typed
           values nested within the containing object's octet stream,

	b) referenced by a "pointer" to another object instance already encoded
           within the same AAA message octet stream,

	c) encapsulation of an object instance's value, whose type definition
           was previously declared in a data dictionary.  This differs from
           case a) in that this object's type definition had already been
           added to the dictionary by an earlier object instance, and so
           this object instance value can be mapped by refering back to
           that earlier object's type definition.

	d) when an object class is derived from a super-class, then the
           super class object instance is encoded as per case c), but it is
           defined to be at a well known implicit location within the serialized
           octet stream (e.g. leftmost nested object of this object instance)

 4. The process sending an object's value to a peer should be able to
    serialize that object into an octet stream, without having to know
    a priori a statically defined attribute/value pair (AVP) tag type for
    each data element within that object. In other words, the AAA protocol
    data representation is application domain independent, and one should not
    have to extend the AAA protocol handler to introduce a new AVP lexicon for
    every new application domain to which the AAA protocol is being applied.
    Instead, the application layer peers should be able to agree to common
    set of application specific object classes, which are transfered using
    the underlying AAA data representation layer syntax.

 5. The process receiving an object's value from a peer should be able to
    de-serialize that object into its equivalent local representation, and pass
    that resulting object into a target object's method entry point as
    a parameter, without requiring any application domain specific program
    logic.

 6. It should be possible for an object's encoding to reference, using a
    message relative index, other object instances contained within the
    same AAA protocol message.

 7. An array is an aggregration of objects having an identical type. They
    are indexed by an unsigned integer ranging in value from zero to one
    less than the size of the array. Each object element in the array
    occupies a fixed number of octets. The number of array elements is
    variable, and it is encoded within the AAA protocol message.

 8. Each object instance value within an AAA message must be capable of being
    digitally signed.

 9. The serialization procedure should be able to encapsulate X.509
    public key or X.509 attribute certificates as an opaque object within
    the AAA message. The de-serialization procedure must recognize X.509
    certificate objects.

 10. An object having a well known type agreed to by the cooperating peers
     can be encapsulated in an <object type identifier/length/value> message
     element. The object's encoding must specify its object type identifier,
     its length, followed by a sequence of binary octets that form the object's
     value.  Unlike a fixed AVP address space scheme, the cooperating peers
     must dynamically and explicitly define through negotiation
     during their session the data dictionary specifying the lexicon
     of <object type identifier/length/value> message elements that they
     are capable of sending and receiving.

 12. An object type identifier must encode the following information:

      - the object class's hierarchy of object super-class(es) names from which
        this class is derived. Multiple inheritance is not supported.

      - An object class's version number and/or most recent modification
        date and timestamp.

      - the name of the application specific object class hierarchy from
        which this object class is rooted

 13. Primitive data types that must be supported as object data members:

	Boolean
	Unsigned two's complement 16-bit, 32-bit, and 64-bit integer
	Signed two's complement 16-bit, 32-bit, and 64-bit integer
	ANSI IEEE 754-1985 compliant single precision floating point (float)
	ANSI IEEE 754-1985 compliant double precision floating point (double)
	Packed decimal
	UTF-8 string
	wide characters: 1, 2, or 4 bytes wide
	enumeration, an integer value constrained to be a member of a set

 14. other Primitive data type requirements:
	- byte swapping is done by the receiver (if it is nescessary)
	- strings may be up to 65KB long
	- basic types are always aligned within a message on their boundaries

 15. The data representation must support the concept of unions, which
     overlap a single storage region with one or more data mappings;
     one of the union data members is declared to be a discriminator tag.

 16. Each object class method shall declare a symbolic name unique within
     the scope of that object class, which can be declared as a calling sequence
     having a set of input parameters, output parameters, a return value
     type, and contextual information (i.e. environment/globals).
     An AAA message must be able to refer to one of a target object instance's
     methods, that is to be executed with parameter objects supplied in the
     same AAA message. 





From owner-aaa-bof@merit.edu  Thu Sep 16 12:03:49 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id MAA26413
	for <aaa-wg-archive@nic.merit.edu>; Thu, 16 Sep 1999 12:03:49 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 433845DD9A; Thu, 16 Sep 1999 12:01:48 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 297695DDA4; Thu, 16 Sep 1999 12:01:48 -0400 (EDT)
Received: from roam.psg.com (bootp39.sesp.nwu.edu [129.105.107.39])
	by segue.merit.edu (Postfix) with ESMTP id 0E5895DD9A
	for <aaa-wg@merit.edu>; Thu, 16 Sep 1999 12:01:47 -0400 (EDT)
Received: from randy by roam.psg.com with local (Exim 3.03 #1)
	id 11RcJz-0005OP-00
	for aaa-wg@merit.edu; Thu, 16 Sep 1999 07:15:35 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: aaa wg <aaa-wg@merit.edu>
Subject: aaa area and co-chair change
Message-Id: <E11RcJz-0005OP-00@roam.psg.com>
Date: Thu, 16 Sep 1999 07:15:35 -0700
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

AAA folk,

The pressure is on AAA for a number of reasons, but it boils down to urgent
need for results.  The IESG has committed to the roaming and other folk that
the requirements phase of AAA will have first documents finished before the
dreadline for the DC meeting (I append the note to roamops et alia).

To that end, the IESG has moved the AAA WG from the general area to the
operations and management area, has asked Bernard Aboba to co-chair with
Paul Krumviede, and requests that the WG very quickly draft a much more
focused charter.

randy

---

Date: Fri, 13 Aug 1999 16:11:02 -0700 (PDT)
From: Randy Bush <randy@psg.com>
To: Glen Zorn <gwz@acm.org>, 
    Pat Calhoun <pcalhoun@eng.sun.com>,
    Paul Krumviede <paul@mci.net>, 
    Brian Lloyd <brian@lloyd.com>
Cc: iesg <iesg@ietf.org>
Subject: roamops, aaa, the universe, and everything

The IESG discussed the issues of using an interim AAA protocol to
address the authentication issues raised in roaming.  Aside from the
technical issues, which were not inconsiderable, the IESG consensus was
that, considering the importance of AAA work to the IETF community, it
would be quite inappropriate for an AAA protocol, or part thereof, to be
added to the tasks of an existing working group chartered to produce a
specific protocol.

AAA work should be done in a forum that can ensure the widest possible
participation.  And there is already a forum for this type of work, the
AAA WG.

On the other hand, there is FUD about the rate of progress in the AAA
WG.  This FUD is the cause for the mobile folk wanting to move ahead
although it would be out of sync.  The IESG is working seriously with
the AAA WG to rectify this situation.

Therefore, the IESG has decided on the following course of action:

  o ROAMOPS is to complete its current chartered work by finishing the
    phone-book effort.  ROAMOPS will then close.  There will be a last
    meeting in DC if and only if it is needed to complete the phone-book
    work.

  o AAA will have all requirements drafts out by the I-D cutoff for the
    DC meeting.  This will allow the DC AAA meeting to discuss those
    drafts and then start discussion of how to best meet those
    requirements.

  o If perchance the AAA WG does not have all requirements drafts out in
    time for the DC meeting, we hope that folk with specific protocol
    proposals would be prepared to have a BOF in DC.

We believe that this is the best plan to meet the overall needs of the
IETF community.  We look forward to having the mobility folk taking an
active role in the AAA WG's efforts.

Thank you.

randy


From owner-aaa-bof@merit.edu  Fri Sep 17 15:03:57 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id PAA10418
	for <aaa-wg-archive@nic.merit.edu>; Fri, 17 Sep 1999 15:03:57 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 217DE5DDC1; Fri, 17 Sep 1999 15:03:37 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id DCE975DDC0; Fri, 17 Sep 1999 15:03:36 -0400 (EDT)
Received: from monitor.internaut.com (mg-206253200-3.ricochet.net [206.253.200.3])
	by segue.merit.edu (Postfix) with ESMTP id 96EBB5DDC0
	for <aaa-wg@merit.edu>; Fri, 17 Sep 1999 15:03:29 -0400 (EDT)
Received: from vaio (vaiobean.internaut.com [204.57.137.68])
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id MAA31243
	for <aaa-wg@merit.edu>; Fri, 17 Sep 1999 12:01:07 -0700 (PDT)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'aaa wg'" <aaa-wg@merit.edu>
Subject: A message from the co-chair...
Date: Fri, 17 Sep 1999 12:35:10 -0700
Message-ID: <002901bf0143$c1dd36c0$448939cc@vaio>
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 CWS, Build 9.0.2416 (9.0.2910.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.5400
Importance: Normal
In-Reply-To: <E11RcJz-0005OP-00@roam.psg.com>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Thank you, Randy. 

As your new co-chair, I thought I'd provide 
a few words of introduction and provide a
schedule for the work in front of us. 

First, a few words about me. I was born
in Brooklyn, New York 41 years ago, the
son of an Egyptian father and mother
(now deceased) of Russian descent. I 
have relatives scattered all over the 
globe, including UK, France, Italy, US, 
and Israel. My interest in the Internet 
began partly out of a desire to keep in 
touch with them.  

For most of the last seven years, I've 
been involved in building, operating, 
and designing Internet access networks 
and AAA infrastructure. I've been employed by
Microsoft since June 1994, first
leading the development of MSN's
Internet capabilities and later working
in the Windows Networking group,
most recently as Network Architect.

During that time, I've seen Internet 
access grow from an idea to a service 
that is now an integral part of the 
lives of tens of millions of people 
worldwide.

Most of those people have no idea what
AAA is, or what it does, but they typically 
do have strong opinions about the end 
results of that activity, namely the 
ability to access the Internet reliably 
and to receive an accurate bill.

During my career I've spent a good bit of
time talking to those users on the phone
or in person, and tracking down problems
that they have encountered. It's a 
profoundly humbling experience. Building
ultra-reliable AAA infrastructure is
hard.

If at times you are feeling discouraged
and wonder whether the work we do in the 
IETF really matters, I suggest taking a 
few hours off to talk to a grandmother
in Fargo, North Dakota, who uses the
Internet to send email to her 
grandchildren.

To the daily experience of those users, 
AAA is every bit as important as any of 
the other critical protocols that help
the Internet run. 

AAA also matters a great deal to access
providers and the equipment vendors who
supply them. Having a AAA protocol that
they can use to enable new forms of
Internet access, such as wireless, is
of critical importance to them, as well
as to millions of potential customers.

In order to address those critical needs, 
the IESG has committed to the mobile IP, 
roaming and other communities that 
the requirements phase of AAA will have 
first documents finished before the
deadline for the DC meeting.

The IESG has also decided to move the 
AAA WG from the General Area to Operations 
and Management.

As Randy noted, this boils down to an 
urgent need for results. To understand 
just how urgent, let's look at the calendar. 

Today, is Friday, September 17, 1999. 
The deadline for submissions to the DC meeting 
is 1700 EST, Monday, October 25, 1999. 
That means that we have 39 days (counting all 
of today) between now and the submission 
deadline. For those of you that distinguish
between weekdays and weekends (I'm not one of 
them), this translates into 27 week days, and 
12 weekend days. 

Anyway you look at it, there isn't a 
lot of time left. 

In that time, the AAA WG needs to 
"very quickly draft a much more focused 
charter" as well as to finish the
first documents for the requirements phase. 

In this case, "very quickly" translates 
into us having a new charter ready for 
IESG discussion by Tuesday, September 21.

Wow. That's just 4 days away. 

When I was first contacted about
becoming a co-chair, and told about
the deadlines, my first reaction was
one of shock. Many of you in the
may be experiencing that emotion now.

However, another way to look at it
is that we have been given a great
challenge. Our job, simply put, is 
to make the next  39 days some of the 
most productive in IETF history.  

I hope that you, the members of the AAA
WG, are as excited and energized about
that challenge as I am.

Cheers, 

Bernard




From owner-aaa-bof@merit.edu  Fri Sep 17 15:43:32 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id PAA11086
	for <aaa-wg-archive@nic.merit.edu>; Fri, 17 Sep 1999 15:43:32 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BD66B5DDC0; Fri, 17 Sep 1999 15:43:12 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A38B95DDC7; Fri, 17 Sep 1999 15:43:12 -0400 (EDT)
Received: from monitor.internaut.com (mg-206253200-3.ricochet.net [206.253.200.3])
	by segue.merit.edu (Postfix) with ESMTP id 267CB5DDC0
	for <aaa-wg@merit.edu>; Fri, 17 Sep 1999 15:43:07 -0400 (EDT)
Received: from vaio (vaiobean.internaut.com [204.57.137.68])
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id MAA31279
	for <aaa-wg@merit.edu>; Fri, 17 Sep 1999 12:40:46 -0700 (PDT)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'aaa wg'" <aaa-wg@merit.edu>
Subject: Re-chartering discussion
Date: Fri, 17 Sep 1999 13:14:46 -0700
Message-ID: <002b01bf0149$4a8a9620$448939cc@vaio>
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 CWS, Build 9.0.2416 (9.0.2910.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.5400
Importance: Normal
In-Reply-To: <E11RcJz-0005OP-00@roam.psg.com>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Some background
===============

As noted in Randy's message, the AAA WG needs to
"very quickly draft a much more focused
charter." In this case "very quickly" means that
the charter needs to be submitted by
Tuesday, September 21.

Given that the AAA WG has been moved to the
Operations & Management area, the charter
needs to be appropriate for a WG in the
O&M area.

The IESG has committed to the mobile IP,
roaming and other communities that
the requirements phase of AAA will have
first documents finished before the
1700 EST, October 25 deadline for the DC meeting.
This implies that for now we should only
take on milestones that we can complete
by the deadline.

The request that the new charter be "much more
focused" implies that the scope of our
charter, and many of the ensuing
milestones, will need to be cut.

This doesn't imply that the items to
be cut aren't important. There might even be
some other WGs either existing or not yet
existing, which might be interested in the
items that we choose to leave of our plate.
However, in view of the tight deadlines we
face, and the need to move forward in
critical areas such as Mobile IP and roaming,
we are going to have to set some priorities.

As important as deciding what we *are* going
to do, is deciding on what we won't do.
That includes what doesn't have
to be done right now, what can be done
somewhere  else, and what doesn't need
to be done at all.

Over the next four days we're going to
grapple with these questions. In my
experience, tight deadlines have a way
of concentrating the mind, and I look
forward to a frank discussion on this.

Charter strawman
================

To get this discussion started, please find
enclosed below a proposed charter. Due
to the urgent need to provide results for the
roaming and mobile IP communities, this
charter proposal focuses on AAA
requirements relating to Internet access,
including roaming, mobile IP, and NASREQ.

As the AAA WG now lives within the
Operations & Management area, applications
AAA is out of scope. That doesn't mean
that applications AAA isn't important
(indeed, the CAT WG has been doing work
in this area for some time). It just means
that it's not on the charter for this WG
at this time.

The proposed charter also has a goal of
assembling requirements produced by other
working groups.

In many ways, other WGs such as NASREQ, ROAMOPS
and Mobile IP are customers of the AAA
WG, and so those other WGs can play a
part in providing us with requirements
documents. Taking input from other WGs
ensures that we are taking into account
the consensus of other WGs in order to
deliver requirements that fit within the
frameworks defined by those groups.

PROPOSED CHARTER
================

The Authentication, Authorization and Accounting working group
focuses on development of requirements for Authentication,
Authorization and Accounting as applied to Internet Access.

The purpose behind this is to create a base protocol
applicable to a number of specific Internet access models.
These will include Network Access Server AAA, Mobile IP, and
roaming. By creating an architecture and set of base
protocols, the amount of work to create specific Internet
access AAA protocols will be reduced.

The working group will incorporate requirements provided by
the NASREQ, Mobile IP, and ROAMOPS working groups. Once
the requirements documents are completed, the working group
may be re-chartered to include work regarding the base protocol.

Since application-layer authentication, authorization and
accounting presents a fundamentally different set of
issues, work in this area is outside the scope of the
AAA WG.

The immediate goals of the AAA working group are to:

- assemble AAA requirements arising from specific Internet access
applications: Network Access Server AAA, Mobile IP, and roaming.

- document requirements for a base AAA architecture;

- identify the relationship and interaction between Policy and
Authorization;

Goals and Milestones:
Sep 99    Submit Mobile IP requirements initial Internet-Draft
Sep 99    Submit Accounting Requirements initial Internet-Draft(s)
Oct 99    Submit policy/authorization initial Internet-Draft
Nov 99    Revision of charter to include statement of work regarding the
base
          protocols and data formats.

Internet-Drafts:
Requirements for Internet-Scale Accounting Management (34150 bytes)
Introduction to Accounting Management (74305 bytes)
Accounting Attributes and Record Formats,
<draft-brownlee-accounting-attributes-00.txt>
AAA Authorization Architecture and Requirements (159682 bytes)
Mobile IP Authentication, Authorization, and Accounting Requirements (52670
bytes)

Requirements documents incorporated by reference:

>From NASREQ:
Criteria for Evaluating Network Access Server Protocols (27062 bytes)
Network Access Server Requirements Next Generation (NASREQNG) NAS Model
(42672 bytes)
Network Access Servers Requirements: Extended RADIUS Practices (27010 bytes)

>From ROAMOPS:
Criteria for Evaluating Roaming Protocols (RFC 2477) (23530 bytes)







From owner-aaa-bof@merit.edu  Fri Sep 17 15:55:38 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id PAA11437
	for <aaa-wg-archive@nic.merit.edu>; Fri, 17 Sep 1999 15:55:38 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 012805DDC8; Fri, 17 Sep 1999 15:55:19 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id DB31C5DDC9; Fri, 17 Sep 1999 15:55:18 -0400 (EDT)
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
	by segue.merit.edu (Postfix) with ESMTP id A72475DDC8
	for <aaa-wg@merit.edu>; Fri, 17 Sep 1999 15:55:16 -0400 (EDT)
Received: from dumbo.fokus.gmd.de (dumbo [193.175.132.239])
	by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id VAA20698;
	Fri, 17 Sep 1999 21:53:28 +0200 (MET DST)
From: Mikhail Smirnov <smirnow@fokus.gmd.de>
Received: (mis@localhost) by dumbo.fokus.gmd.de  (SMI-8.6/8.6.12) id VAA17192; Fri, 17 Sep 1999 21:53:23 +0200
Date: Fri, 17 Sep 1999 21:53:23 +0200
Message-Id: <199909171953.VAA17192@dumbo.fokus.gmd.de >
To: aaa-wg@merit.edu, aboba@internaut.com
Subject: Re: Re-chartering discussion
Cc: smirnow@fokus.gmd.de
X-Sun-Charset: US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Hi,

bearing in mind what happens to the AAA WG and what
Bernard wrote in last two mails:

isn't better to call the new O&M WG 
"R[oaming]&M[obile] AAA"?

Michael


From owner-aaa-bof@merit.edu  Fri Sep 17 18:07:47 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id SAA18225
	for <aaa-wg-archive@nic.merit.edu>; Fri, 17 Sep 1999 18:07:47 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 462025DDC7; Fri, 17 Sep 1999 18:07:28 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 2D4525DDCE; Fri, 17 Sep 1999 18:07:28 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by segue.merit.edu (Postfix) with ESMTP id E10E75DDC7
	for <aaa-wg@merit.edu>; Fri, 17 Sep 1999 18:07:26 -0400 (EDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id OAA23192;
	Fri, 17 Sep 1999 14:59:08 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 17 Sep 1999 22:04:03 UT
Received: from spud.ascend.com (spud [192.207.23.51])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id PAA15048;
	Fri, 17 Sep 1999 15:04:02 -0700 (PDT)
Received: from MATT.ASCEND.COM (matt-pc.eng.ascend.com [172.20.17.137])
	by spud.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id PAA25854;
	Fri, 17 Sep 1999 15:04:02 -0700 (PDT)
Message-Id: <4.2.0.58.19990917145500.009f83c0@porky.ascend.com>
X-Sender: mhold@porky.ascend.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Fri, 17 Sep 1999 15:03:49 -0700
To: <aboba@internaut.com>
From: Matt Holdrege <matt@ascend.com>
Subject: Re: Re-chartering discussion
Cc: "'aaa wg'" <aaa-wg@merit.edu>
In-Reply-To: <002b01bf0149$4a8a9620$448939cc@vaio>
References: <E11RcJz-0005OP-00@roam.psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

At 01:14 PM 09/17/1999 -0700, Bernard Aboba wrote:

>PROPOSED CHARTER
>================
>
>Goals and Milestones:
>Sep 99    Submit Mobile IP requirements initial Internet-Draft
>Sep 99    Submit Accounting Requirements initial Internet-Draft(s)
>Oct 99    Submit policy/authorization initial Internet-Draft
>Nov 99    Revision of charter to include statement of work regarding the
>base protocols and data formats.

Can't we say something stronger about when we will actually begin working 
on a AAA protocol? A lot of us already know the requirements and the 
industry is demanding a protocol. I agree it is a good thing to finish the 
formal requirements phase, but we also should be able to begin working on 
the protocol itself following the November meeting.

I think your last milestone implies this, but it's pretty weak. How about...

Nov 99   Assign base protocol editor and finalize work plan with target 
date of first draft to meet the deadline of the IETF March 2000 meeting.

Matt Holdrege	     http://www.lucent.com	holdrege@lucent.com


From owner-aaa-bof@merit.edu  Sat Sep 18 09:28:19 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id JAA12446
	for <aaa-wg-archive@nic.merit.edu>; Sat, 18 Sep 1999 09:28:19 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 314FC5DDD9; Sat, 18 Sep 1999 09:28:00 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0BFB15DDDB; Sat, 18 Sep 1999 09:28:00 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by segue.merit.edu (Postfix) with ESMTP id D7AD35DDD9
	for <aaa-wg@merit.edu>; Sat, 18 Sep 1999 09:27:58 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.03 #1)
	id 11SKWr-000DJp-00; Sat, 18 Sep 1999 06:27:49 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Matt Holdrege <matt@ascend.com>
Cc: aaa wg <aaa-wg@merit.edu>
Subject: Re: Re-chartering discussion
References: <E11RcJz-0005OP-00@roam.psg.com>
	<4.2.0.58.19990917145500.009f83c0@porky.ascend.com>
Message-Id: <E11SKWr-000DJp-00@rip.psg.com>
Date: Sat, 18 Sep 1999 06:27:49 -0700
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

> Can't we say something stronger about when we will actually begin working 
> on a AAA protocol?

there are no penalties for coming in ahead of schedule.  there are for
coming in behind.  so far, the former has not been a problem.  we all look
forward to the latter,

> A lot of us already know the requirements

the proof is in a draft which has consensus, is it not?  a lot of folk
eagerly await that.

randy


From owner-aaa-bof@merit.edu  Sat Sep 18 10:22:07 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA13604
	for <aaa-wg-archive@nic.merit.edu>; Sat, 18 Sep 1999 10:22:07 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id B07BD5DDBE; Sat, 18 Sep 1999 10:21:48 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8FF815DDCC; Sat, 18 Sep 1999 10:21:48 -0400 (EDT)
Received: from max.phys.uu.nl (max.phys.uu.nl [131.211.32.73])
	by segue.merit.edu (Postfix) with ESMTP id 0CF325DDBE
	for <aaa-wg@merit.edu>; Sat, 18 Sep 1999 10:21:46 -0400 (EDT)
Received: from [192.168.254.5] (hst36100.phys.uu.nl [131.211.36.100])
	by max.phys.uu.nl (8.9.3/8.9.3/hjm) with ESMTP id QAA00004
	for <aaa-wg@merit.edu>; Sat, 18 Sep 1999 16:21:45 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: delaat@mail.phys.uu.nl
Message-Id: <v04210100b409506bf182@[192.168.254.5]>
Date: Sat, 18 Sep 1999 16:21:42 +0200
To: aaa-wg@merit.edu
From: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Subject: Re: Re-chartering discussion
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

>Hi,
>
>bearing in mind what happens to the AAA WG and what
>Bernard wrote in last two mails:
>
>isn't better to call the new O&M WG
>"R[oaming]&M[obile] AAA"?
>
>Michael

Gives a nice unix command :-) --> rm AAA

I would prefer to see a generic part in the AAA architecture, since 
in the end we need multi-domain authorizations. It must be possible 
to define a protocol, which is not limited to very specific 
applications. If we decouple the protocol in two parts,

  - one about the handling of the rules and the logic of the 
authorisations (the logic formula's), and communication between rule 
evaluation servers
  - one about the handling of the "globs", getting info on structure 
of globs, how to query what question to ask to get certain 
authorization, construction of that question

It should then at least be possible to device a very universal 
protocol for the first part and maby some object broker like model 
for the second part. As asked in the conference I will produce a 
piece of text on the topic "why and how to find out what the 
structure of the question is to ask".

In the student and distant learning example this would be:
Student goes to the server and sends a message: "I want to follow 
truck driver course X", server would hypothetically reply: "I then 
need your student ID and your credit card and either a driver license 
or a certificate of the highway police". In the words of John 
Vollbrecht:
student asks: I want authorization for "GLOB-X", AAA server looks 
into the rules and says: "Then I need a message containing GLOB-A and 
GLOB-B and (GLOB-C or GLOB-D)". Note that the server does not need to 
know what those GLOB's mean. The internal structure of the GLOB's is 
known to the specific applications. I will try to elaborate on this 
beginning next week.

best regards,
Cees.

_________________________________________________________________________
dr.ir. C.Th.A.M. de Laat, Faculty of Physics and Astronomy,
Utrecht University, Princetonplein 5, NL-3584CC Utrecht, The Netherlands.
Tel: (31)30-2534585 , mobile: 06-51566438 , Fax:(31)30-2537555
web: http://www.phys.uu.nl/~delaat , mail: c.t.a.m.delaat@phys.uu.nl


From owner-aaa-bof@merit.edu  Sun Sep 19 12:31:59 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id MAA02597
	for <aaa-wg-archive@nic.merit.edu>; Sun, 19 Sep 1999 12:31:59 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 3B4245DD9C; Sun, 19 Sep 1999 12:30:11 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 1222E5DD98; Sun, 19 Sep 1999 12:30:08 -0400 (EDT)
Received: from fogerty.ericsson.fi (fogerty.ericsson.fi [131.160.11.6])
	by segue.merit.edu (Postfix) with ESMTP id 9E8D05DD99
	for <aaa-wg@merit.edu>; Sun, 19 Sep 1999 12:30:03 -0400 (EDT)
Received: from lmf.lmf.ericsson.se ([131.160.11.2])
	by fogerty.ericsson.fi (8.9.3/8.9.3) with ESMTP id TAA16271;
	Sun, 19 Sep 1999 19:30:20 +0300 (EET DST)
Received: from lmf.ericsson.se by lmf.lmf.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id TAA05538; Sun, 19 Sep 1999 19:30:00 +0300 (EET DST)
Message-ID: <37E50F86.78B84FB6@lmf.ericsson.se>
Date: Sun, 19 Sep 1999 19:29:58 +0300
From: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Organization: Oy L M Ericsson Ab
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: aboba@internaut.com
Cc: aaa-wg@merit.edu
Subject: Re: Re-chartering discussion
References: <002b01bf0149$4a8a9620$448939cc@vaio>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


Bernard wrote:

>The working group will incorporate requirements provided by
>the NASREQ, Mobile IP, and ROAMOPS working groups. Once

I am in favor of this new and smaller focus. It will make
things much easier.

If NASREQ requirements are in, are VoIP requirements in or
out? In a way, they should be in, as NASes are required to
do VoIP as well these days, but on the other hand VoIP has
a lot of momentum, a lot of people focused only on it, and even
the standards on it are partially done outside IETF. Would
that slow things down?

Jari
---- 
Jari Arkko, Oy L M Ericsson Ab, 02420 Jorvas, Finland. Tel +358 9 2992480
Fax +358 9 2993052. GSM +358 40 5079256. E-Mail: Jari.Arkko@ericsson.com
Private WWW: http://www.iki.fi/jar. Standard disclaimers apply.


From owner-aaa-bof@merit.edu  Sun Sep 19 15:55:43 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id PAA04921
	for <aaa-wg-archive@nic.merit.edu>; Sun, 19 Sep 1999 15:55:43 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id C97B05DD98; Sun, 19 Sep 1999 15:55:24 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id ACF295DD99; Sun, 19 Sep 1999 15:55:24 -0400 (EDT)
Received: from smtprtp1.ntcom.nortel.net (smtprtp1.ntcom.nortel.net [137.118.22.14])
	by segue.merit.edu (Postfix) with ESMTP id A146B5DD98
	for <aaa-wg@merit.edu>; Sun, 19 Sep 1999 15:55:23 -0400 (EDT)
Received: from zcard00n.ca.nortel.com (actually zcard00n) 
          by smtprtp1.ntcom.nortel.net; Sun, 19 Sep 1999 15:54:51 -0400
Received: from zbl6c008.corpeast.baynetworks.com ([132.245.205.58]) 
          by zcard00n.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) 
          id SQR85P25; Sun, 19 Sep 1999 15:54:51 -0400
Received: from msquire (extranet-139-113.corpeast.baynetworks.com [132.245.139.113]) 
          by zbl6c008.corpeast.baynetworks.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) 
          id SJDZ691Y; Sun, 19 Sep 1999 15:54:49 -0400
Message-Id: <3.0.32.19990919155048.00a8ac50@zbl6c008.corpeast.baynetworks.com>
X-Sender: msquire@zbl6c008.corpeast.baynetworks.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Sun, 19 Sep 1999 15:50:50 -0400
To: aboba <aboba@internaut.com>, "'aaa wg'" <aaa-wg@merit.edu>
From: "Matt Squire" <msquire@nortelnetworks.com>
Subject: Re: Re-chartering discussion
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>
>PROPOSED CHARTER
>================
>
>The Authentication, Authorization and Accounting working group
>focuses on development of requirements for Authentication,
>Authorization and Accounting as applied to Internet Access.
>
>The purpose behind this is to create a base protocol
>applicable to a number of specific Internet access models.
>These will include Network Access Server AAA, Mobile IP, and
>roaming. By creating an architecture and set of base
>protocols, the amount of work to create specific Internet
>access AAA protocols will be reduced.

I'm all in favor of reducing the scope of this wg.  However, I'm not a big
fan of the way its been reduced.  I would rather reduce the scope of the wg
by reducing the number of A's in the title.  

The authentication & authorization requirements of Internet Access do not
appear to be much different than the authentication and authorization
requirements of, say VoIP, or DiffServ, or any other number of functions.
However, the accounting requirements of Internet Access may be
significantly different than the authentication/authorization requirements,
specifically in the generality of data representation for the accounted
information, in extensibility, and in transport.  

Instead of taking a vertical application slice of AAA, why not just
concentrate on authentication and authorization and split off accounting
into a separate wg.  I don't recall that the group ever reached a consensus
that a single base protocol for all three A's was the way to go.  I thought
this was supposed to be discussed after the requirements were put together.
 The old charter specifically included the possibility of protocolS
(plural) instead of restricting the solution to a single
i-can-do-everything protocol.  

Also, there are a number of consortia/groups that are already working on
accounting/billing standard, and splitting accounting off would be a good
way to focus these outside efforts in an IETF wg with that single purpose.   

So by all means let's reduce the scope of the group, but instead of
restricting the number of applications we'll look at, lets reduce the base
functionality that's within the scope of the WG.  

- Matt



Matt Squire
Nortel Networks
innovations.lab
msquire@nortelnetworks.com
(919)992-9048


From owner-aaa-bof@merit.edu  Sun Sep 19 19:12:54 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id TAA07889
	for <aaa-wg-archive@nic.merit.edu>; Sun, 19 Sep 1999 19:12:54 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 6A7AB5DD99; Sun, 19 Sep 1999 19:12:36 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 4E3B95DDA3; Sun, 19 Sep 1999 19:12:36 -0400 (EDT)
Received: from ctron-dnm.ctron.com (ctron-dnm.cabletron.com [12.25.1.120])
	by segue.merit.edu (Postfix) with ESMTP id 3A2915DD99
	for <aaa-wg@merit.edu>; Sun, 19 Sep 1999 19:12:35 -0400 (EDT)
Received: (from uucp@localhost)
	by ctron-dnm.ctron.com (8.8.7/8.8.7) id TAA23874;
	Sun, 19 Sep 1999 19:11:32 -0400 (EDT)
Received: from roc-mail2.ctron.com(134.141.72.230) by ctron-dnm.ctron.com via smap (4.1)
	id xma023868; Sun, 19 Sep 99 19:10:46 -0400
Received: from new-exc1.ctron.com (NEW-EXC1 [134.141.200.123])
	by roc-mail2.ctron.com (8.8.7/8.8.7) with ESMTP id TAA18734;
	Sun, 19 Sep 1999 19:15:38 -0400 (EDT)
Received: by new-exc1.ctron.com with Internet Mail Service (5.5.2448.0)
	id <SQNZKLLQ>; Mon, 20 Sep 1999 00:08:05 +0100
Message-ID: <29752A74B6C5D211A4920090273CA3DC9053CC@new-exc1.ctron.com>
From: "Gommans, Leon" <Leon.Gommans@cabletron.com>
To: "'aboba@internaut.com'" <aboba@internaut.com>
Cc: "'aaa wg'" <aaa-wg@merit.edu>
Subject: Rechartering the long term requirements
Date: Mon, 20 Sep 1999 00:07:54 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Bernard,

A (highly motivated) group of people have been working on requirements
for authorization which were believed to fit what we like to refer to as
"long term requirements" which I believe discussions during the first WG
meeting in Minneapolis called for. The WG meeting specifically asked for
various area's to be explored including application area's such as
E-commerce.
In the mean time the authorization sub-WG devised a generic model that
proved
to be applicable in various area's including some application area's. Even a
computer based learning environment could be described in Authorization
model terms as a recent contribution learned. 

Turning the charter around for reasons that make sense when trying to
fulfill short term needs, without clearly indicating what will
happen to "the long term requirements", could be harmfull to some of
these initiatives. Could you take away some uncertainties about
its status as some of it seems to dangle now. IMHO it almost seems
that we are asked to disregard the current work and start a new
track as I am a bit concerned that the current authorization
model and its terms might be considered to be a little bit
'overdone' if used with the short term requirements
document only. 

Kind regards .. Leon Gommans








From owner-aaa-bof@merit.edu  Mon Sep 20 00:33:43 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id AAA11540
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 00:33:43 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 9463B5DDCB; Mon, 20 Sep 1999 00:31:47 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 1C4795DDC6; Mon, 20 Sep 1999 00:31:47 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by segue.merit.edu (Postfix) with ESMTP id 148B35DDAB
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 00:31:46 -0400 (EDT)
Received: from adsl-63-193-107-75.dsl.snfc21.pacbell.net ([166.45.3.11])
 by shoe.reston.mci.net (PMDF V5.2-32 #33823)
 with ESMTP id <01JG69YEUHBG91W8P9@shoe.reston.mci.net> for aaa-wg@merit.edu;
 Mon, 20 Sep 1999 00:31:28 EDT
Date: Sun, 19 Sep 1999 21:31:22 -0700
From: Paul Krumviede <paul.krumviede@wcom.com>
Subject: Re: Re-chartering discussion
In-reply-to: <37E50F86.78B84FB6@lmf.ericsson.se>
Originator-info: login-id=krumviede; server=localhost
To: Jari Arkko <Jari.Arkko@lmf.ericsson.se>, aboba@internaut.com
Cc: aaa-wg@merit.edu
Message-id: <1473812092.937776682@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
MIME-version: 1.0
X-Mailer: Mulberry (Win32) [1.4.4, s/n P005-300888-001]
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
Content-transfer-encoding: 7BIT
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

--On Sunday, September 19, 1999, 7:29 PM +0300 Jari Arkko <Jari.Arkko@lmf.ericsson.se> wrote:

> 
> Bernard wrote:
> 
>> The working group will incorporate requirements provided by
>> the NASREQ, Mobile IP, and ROAMOPS working groups. Once
> 
> I am in favor of this new and smaller focus. It will make
> things much easier.
> 
> If NASREQ requirements are in, are VoIP requirements in or
> out? In a way, they should be in, as NASes are required to
> do VoIP as well these days, but on the other hand VoIP has
> a lot of momentum, a lot of people focused only on it, and even
> the standards on it are partially done outside IETF. Would
> that slow things down?

My perception was that we, for some value of we, didn't understand
VoIP requirements well enough at this point in time to consider them
now. I would be willing to learn otherwise.

-paul



From owner-aaa-bof@merit.edu  Mon Sep 20 00:43:42 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id AAA11596
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 00:43:41 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 505555DDAB; Mon, 20 Sep 1999 00:43:23 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 2AEC35DDB0; Mon, 20 Sep 1999 00:43:23 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by segue.merit.edu (Postfix) with ESMTP id 1BC995DDAB
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 00:43:22 -0400 (EDT)
Received: from adsl-63-193-107-75.dsl.snfc21.pacbell.net ([166.45.3.11])
 by shoe.reston.mci.net (PMDF V5.2-32 #33823)
 with ESMTP id <01JG6AE5057G934WK1@shoe.reston.mci.net> for aaa-wg@merit.edu;
 Mon, 20 Sep 1999 00:43:21 EDT
Date: Sun, 19 Sep 1999 21:43:13 -0700
From: Paul Krumviede <paul.krumviede@wcom.com>
Subject: Re: Re-chartering discussion
In-reply-to: <3.0.32.19990919155048.00a8ac50@zbl6c008.corpeast.baynetworks.com>
Originator-info: login-id=krumviede; server=localhost
To: Matt Squire <msquire@nortelnetworks.com>, aboba <aboba@internaut.com>,
        "'aaa wg'" <aaa-wg@merit.edu>
Message-id: <1474523432.937777393@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
MIME-version: 1.0
X-Mailer: Mulberry (Win32) [1.4.4, s/n P005-300888-001]
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
Content-transfer-encoding: 7BIT
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

--On Sunday, September 19, 1999, 3:50 PM -0400 Matt Squire <msquire@nortelnetworks.com> wrote:

> 
>> 
>> PROPOSED CHARTER
>> ================
>> 
>> The Authentication, Authorization and Accounting working group
>> focuses on development of requirements for Authentication,
>> Authorization and Accounting as applied to Internet Access.
>> 
>> The purpose behind this is to create a base protocol
>> applicable to a number of specific Internet access models.
>> These will include Network Access Server AAA, Mobile IP, and
>> roaming. By creating an architecture and set of base
>> protocols, the amount of work to create specific Internet
>> access AAA protocols will be reduced.
> 
> I'm all in favor of reducing the scope of this wg.  However, I'm not a big
> fan of the way its been reduced.  I would rather reduce the scope of the wg
> by reducing the number of A's in the title.  
> 
> The authentication & authorization requirements of Internet Access do not
> appear to be much different than the authentication and authorization
> requirements of, say VoIP, or DiffServ, or any other number of functions.
> However, the accounting requirements of Internet Access may be
> significantly different than the authentication/authorization requirements,
> specifically in the generality of data representation for the accounted
> information, in extensibility, and in transport.  

Very true, although I think there may be another dimension driving some
of these issues: much of the original work seemed to assume a single
administrative domain (look at naming as done by most ISPs and in
early roaming implementations). Extending any of the A's to a more
complex world may introduce similar complications (diffserv isn't
even going there).

> Instead of taking a vertical application slice of AAA, why not just
> concentrate on authentication and authorization and split off accounting
> into a separate wg.  I don't recall that the group ever reached a consensus
> that a single base protocol for all three A's was the way to go.  I thought
> this was supposed to be discussed after the requirements were put together.
>  The old charter specifically included the possibility of protocolS
> (plural) instead of restricting the solution to a single
> i-can-do-everything protocol.  

Correct, and I don't think we are trying to force that decision here.

> Also, there are a number of consortia/groups that are already working on
> accounting/billing standard, and splitting accounting off would be a good
> way to focus these outside efforts in an IETF wg with that single purpose.   
> 
> So by all means let's reduce the scope of the group, but instead of
> restricting the number of applications we'll look at, lets reduce the base
> functionality that's within the scope of the WG.  

As a thought experiment, I see 2 reasons to keep these together.
- we may want some form of correlation tag to allow one to associate
all the relevant authentication and authorization decisions and the
subsequent accounting (if any);
- there may be services or inter-domain cases where authorization
is conditional on accounting capabilities (off-hand, I'm thinking of
some fraud detection capabilities here).

These might be addressed by reasonable coordination between
efforts, but I'd like to get some sense of how others see this.

-paul



From owner-aaa-bof@merit.edu  Mon Sep 20 07:37:33 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id HAA16903
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 07:37:33 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id C010B5DDC5; Mon, 20 Sep 1999 07:37:13 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A05A15DDC6; Mon, 20 Sep 1999 07:37:13 -0400 (EDT)
Received: from smtprtp1.ntcom.nortel.net (smtprtp1.ntcom.nortel.net [137.118.22.14])
	by segue.merit.edu (Postfix) with ESMTP id 8CA3C5DDC5
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 07:37:12 -0400 (EDT)
Received: from zsc4c002.corpwest.baynetworks.com (actually h0295.s86b1.BayNetworks.COM) 
          by smtprtp1.ntcom.nortel.net; Mon, 20 Sep 1999 07:36:51 -0400
Received: from zbl6c008.corpeast.baynetworks.com ([132.245.205.58]) 
          by zsc4c002.corpwest.baynetworks.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) 
          id SFRB90LQ; Mon, 20 Sep 1999 04:36:49 -0700
Received: from msquire (msquire.corpeast.baynetworks.com [132.245.252.103]) 
          by zbl6c008.corpeast.baynetworks.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) 
          id SJDZ69K6; Mon, 20 Sep 1999 07:36:48 -0400
Message-Id: <3.0.32.19990920073542.00a7e6d0@zbl6c008.corpeast.baynetworks.com>
X-Sender: msquire@zbl6c008.corpeast.baynetworks.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Mon, 20 Sep 1999 07:35:43 -0400
To: Paul Krumviede <paul.krumviede@wcom.com>, aboba <aboba@internaut.com>,
        "'aaa wg'" <aaa-wg@merit.edu>
From: "Matt Squire" <msquire@nortelnetworks.com>
Subject: Re: Re-chartering discussion
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>
>> Instead of taking a vertical application slice of AAA, why not just
>> concentrate on authentication and authorization and split off accounting
>> into a separate wg.  I don't recall that the group ever reached a consensus
>> that a single base protocol for all three A's was the way to go.  I thought
>> this was supposed to be discussed after the requirements were put together.
>>  The old charter specifically included the possibility of protocolS
>> (plural) instead of restricting the solution to a single
>> i-can-do-everything protocol.  
>
>Correct, and I don't think we are trying to force that decision here.
>

The charter gives the impression, at least to me, that a single base
protocol is the goal.  Maybe we can soften the wording up a bit? 

>These might be addressed by reasonable coordination between
>efforts, but I'd like to get some sense of how others see this.
>

I agree that the efforts need to be coordinated, it just seems like binding
the A's together at the protocol layer is too restrictive.  I'm interested
to see how others see this as well.  

Thanks.

- Matt



Matt Squire
Nortel Networks
innovations.lab
msquire@nortelnetworks.com
(919)992-9048


From owner-aaa-bof@merit.edu  Mon Sep 20 09:06:52 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id JAA18049
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 09:06:52 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0E5625DDC3; Mon, 20 Sep 1999 09:06:32 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D87645DDA8; Mon, 20 Sep 1999 09:06:31 -0400 (EDT)
Received: from omzrelay02.mcit.com (omzrelay02.mcit.com [199.249.19.244])
	by segue.merit.edu (Postfix) with ESMTP id A9F2D5DD9B
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 09:06:30 -0400 (EDT)
Received: from omzrelay.mcit.com ([166.37.204.49])
 by firewall.mcit.com (PMDF V5.2-32 #38417)
 with ESMTP id <0FID00GUF0EA8A@firewall.mcit.com> for aaa-wg@merit.edu; Mon,
 20 Sep 1999 13:06:11 +0000 (GMT)
Received: from omzmta01.mcit.com (omzmta01.mcit.com [166.37.194.119])
 by omzrelay.mcit.com (8.8.7/) with ESMTP	id NAA25440; Mon,
 20 Sep 1999 13:06:18 +0000 (GMT)
Received: from C25776A ([166.37.186.64])
 by omzmta01.mcit.com (InterMail v03.02.05 118 121 101)
 with SMTP id <19990920130607.WXXE7266@C25776A>; Mon, 20 Sep 1999 13:06:07 +0000
Date: Mon, 20 Sep 1999 08:06:03 -0500
From: Henry Sinnreich <henry.sinnreich@wcom.com>
Subject: RE: Re-chartering discussion
In-reply-to: <1473812092.937776682@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
To: aboba@internaut.com, Jari Arkko <Jari.Arkko@lmf.ericsson.se>,
        Paul Krumviede <paul.krumviede@wcom.com>
Cc: aaa-wg@merit.edu
Message-id: <NBBBIIJFOKPMFOOILMBKOEKKEJAA.henry.sinnreich@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Paul wrote:
> My perception was that we, for some value of we, didn't understand
> VoIP requirements well enough at this point in time to consider them
> now. I would be willing to learn otherwise.

Real time communications like VoIP exercise AAA to the utmost, since they
could make use of most network bandwidth and computing resources. Example:

* Authenticate the phone,
* Authenticate the user,
* Get the call request - "collect digits",
* Price out the request and check if in policy,
* Check if you will get paid from the remote party,
  Will require AAA exchanges via clearing house,
* Check if there is bandwidth, check policy,
* Set up QoS end-to-end,
* Set up IPSEC end-to-end or between VPN edge routers or both. Commit its
computing cycles.
* Collect "QoS minutes" IPSEC usage, etc.
* Send billing data to clearing house,
* Settlement for charges.

A two dimensional diagram would look like this:

IP Phone - Local Network - Backbone - Local Network - IP Tel Gateway - PSTN
Phone.
* Authenticate,
* Payments,
* SIP call flows
* QoS - RSVP/DiffServ "call flows"
* LAN - SBM "call flows".

Some of us may be trying to put this down to paper. Would it make sense keep
the door open for VoIP AAA until you see the paper?

Henry




> -----Original Message-----
> From: owner-aaa-bof@merit.edu [mailto:owner-aaa-bof@merit.edu]On Behalf
> Of Paul Krumviede
> Sent: Sunday, September 19, 1999 11:31 PM
> To: Jari Arkko; aboba@internaut.com
> Cc: aaa-wg@merit.edu
> Subject: Re: Re-chartering discussion
>
>
> --On Sunday, September 19, 1999, 7:29 PM +0300 Jari Arkko
> <Jari.Arkko@lmf.ericsson.se> wrote:
>
> >
> > Bernard wrote:
> >
> >> The working group will incorporate requirements provided by
> >> the NASREQ, Mobile IP, and ROAMOPS working groups. Once
> >
> > I am in favor of this new and smaller focus. It will make
> > things much easier.
> >
> > If NASREQ requirements are in, are VoIP requirements in or
> > out? In a way, they should be in, as NASes are required to
> > do VoIP as well these days, but on the other hand VoIP has
> > a lot of momentum, a lot of people focused only on it, and even
> > the standards on it are partially done outside IETF. Would
> > that slow things down?
>
> My perception was that we, for some value of we, didn't understand
> VoIP requirements well enough at this point in time to consider them
> now. I would be willing to learn otherwise.
>
> -paul
>
>



From owner-aaa-bof@merit.edu  Mon Sep 20 09:42:43 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id JAA18524
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 09:42:43 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id F32E05DD9B; Mon, 20 Sep 1999 09:42:23 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id DB2B45DDC6; Mon, 20 Sep 1999 09:42:23 -0400 (EDT)
Received: from mail.transnexus.com (mail.transnexus.com [209.144.152.22])
	by segue.merit.edu (Postfix) with SMTP id E75405DD9B
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 09:42:17 -0400 (EDT)
Received: (qmail 14996 invoked from network); 20 Sep 1999 13:46:07 -0000
Received: from unknown (HELO stephen) (172.16.3.7)
  by 192.168.1.130 with SMTP; 20 Sep 1999 13:46:07 -0000
Message-ID: <00ac01bf036e$0849bf80$070310ac@int.transnexus.com>
From: "Stephen Thomas" <stephen.thomas@transnexus.com>
To: <aaa-wg@merit.edu>
References: <1473812092.937776682@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
Subject: Re: Re-chartering discussion
Date: Mon, 20 Sep 1999 09:42:27 -0400
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.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

| > If NASREQ requirements are in, are VoIP requirements in or
| > out? In a way, they should be in, as NASes are required to
| > do VoIP as well these days, but on the other hand VoIP has
| > a lot of momentum, a lot of people focused only on it, and even
| > the standards on it are partially done outside IETF. Would
| > that slow things down?
| 
| My perception was that we, for some value of we, didn't understand
| VoIP requirements well enough at this point in time to consider them
| now. I would be willing to learn otherwise.

Just a couple of thoughts (from a value of "we" that likes to think
he understands VoIP fairly well ;)

1) In the VoIP space it's been increasingly difficult to separate
   NAS from IP telephony. The purest in me thinks that such separation
   ought to be a desirable goal, but the pragmatist wonders if
   that's realistic.

2) Considering VoIP requirements early could either be a good thing
   or a bad thing, depending on one's objectives. I believe that
   VoIP may represent one of the more complex AAA scenarios because
   of the potential for some degree of interaction with non-IP 
   networks (i.e. the PSTN). Including VoIP in the initial work
   might slow things down because of the additional complexity
   (bad for meeting schedules) but it could also make sure that all
   real requirements are taken into account (good for higher quality
   product). 

As an additional note, some of us with experience in VoIP are willing 
to participate significantly in this working group, so perhaps the
additional complexity might be somewhat offset by the additional
experience ;^)

Stephen


____________________________________________________________________
Stephen Thomas                                       +1 404 872 4887
TransNexus, Chief Technical Officer    stephen.thomas@transnexus.com



From owner-aaa-bof@merit.edu  Mon Sep 20 11:20:05 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA20779
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 11:20:05 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 473DC5DDE9; Mon, 20 Sep 1999 11:19:46 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 169F75DDE1; Mon, 20 Sep 1999 11:19:46 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by segue.merit.edu (Postfix) with ESMTP id AB43B5DDEE
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 11:19:44 -0400 (EDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id IAA19786;
	Mon, 20 Sep 1999 08:14:35 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 20 Sep 1999 15:19:32 UT
Received: from spud.ascend.com (spud [192.207.23.51])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id IAA24881;
	Mon, 20 Sep 1999 08:19:31 -0700 (PDT)
Received: from MATT.ASCEND.COM ([205.228.251.158])
	by spud.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id IAA13356;
	Mon, 20 Sep 1999 08:19:30 -0700 (PDT)
Message-Id: <4.2.0.58.19990920080355.00995130@porky.ascend.com>
X-Sender: mhold@porky.ascend.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 20 Sep 1999 08:19:23 -0700
To: "Stephen Thomas" <stephen.thomas@transnexus.com>
From: Matt Holdrege <matt@ascend.com>
Subject: Re: Re-chartering discussion
Cc: <aaa-wg@merit.edu>
In-Reply-To: <00ac01bf036e$0849bf80$070310ac@int.transnexus.com>
References: <1473812092.937776682@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

At 09:42 AM 09/20/1999 -0400, Stephen Thomas wrote:
>| > If NASREQ requirements are in, are VoIP requirements in or
>| > out? In a way, they should be in, as NASes are required to
>| > do VoIP as well these days, but on the other hand VoIP has
>| > a lot of momentum, a lot of people focused only on it, and even
>| > the standards on it are partially done outside IETF. Would
>| > that slow things down?
>|
>| My perception was that we, for some value of we, didn't understand
>| VoIP requirements well enough at this point in time to consider them
>| now. I would be willing to learn otherwise.
>
>Just a couple of thoughts (from a value of "we" that likes to think
>he understands VoIP fairly well ;)
>
>1) In the VoIP space it's been increasingly difficult to separate
>    NAS from IP telephony. The purest in me thinks that such separation
>    ought to be a desirable goal, but the pragmatist wonders if
>    that's realistic.
>
>2) Considering VoIP requirements early could either be a good thing
>    or a bad thing, depending on one's objectives. I believe that
>    VoIP may represent one of the more complex AAA scenarios because
>    of the potential for some degree of interaction with non-IP
>    networks (i.e. the PSTN). Including VoIP in the initial work
>    might slow things down because of the additional complexity
>    (bad for meeting schedules) but it could also make sure that all
>    real requirements are taken into account (good for higher quality
>    product).

I agree Steve. As you know, many of us have been pursuing these goals 
outside of the IETF since we had no place to develop these requirements 
within the IETF (til now I hope). But I don't think this will slow anything 
down. The IETF meets every day on email lists so meeting schedules 
shouldn't be a big concern.

I also totally agree with the NAS tie-in. The reality is that they are 
tightly linked.



From owner-aaa-bof@merit.edu  Mon Sep 20 12:03:30 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id MAA21352
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 12:03:30 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 846D65DDBB; Mon, 20 Sep 1999 12:03:09 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 6349A5DDDF; Mon, 20 Sep 1999 12:03:09 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by segue.merit.edu (Postfix) with ESMTP id 1B6CC5DDBB
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 12:03:08 -0400 (EDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id IAA27607;
	Mon, 20 Sep 1999 08:48:02 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 20 Sep 1999 15:53:00 UT
Received: from spud.ascend.com (spud [192.207.23.51])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id IAA05793;
	Mon, 20 Sep 1999 08:52:59 -0700 (PDT)
Received: from MATT.ASCEND.COM ([205.228.251.158])
	by spud.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id IAA13894;
	Mon, 20 Sep 1999 08:52:58 -0700 (PDT)
Message-Id: <4.2.0.58.19990920084730.00996240@porky.ascend.com>
X-Sender: mhold@porky.ascend.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 20 Sep 1999 08:52:44 -0700
To: "Matt Squire" <msquire@nortelnetworks.com>
From: Matt Holdrege <matt@ascend.com>
Subject: Re: Re-chartering discussion
Cc: Paul Krumviede <paul.krumviede@wcom.com>, aboba <aboba@internaut.com>,
        "'aaa wg'" <aaa-wg@merit.edu>
In-Reply-To: <3.0.32.19990920073542.00a7e6d0@zbl6c008.corpeast.baynetwor
 ks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

At 07:35 AM 09/20/1999 -0400, Matt Squire wrote:

>The charter gives the impression, at least to me, that a single base
>protocol is the goal.  Maybe we can soften the wording up a bit?
>
> >These might be addressed by reasonable coordination between
> >efforts, but I'd like to get some sense of how others see this.
> >
>
>I agree that the efforts need to be coordinated, it just seems like binding
>the A's together at the protocol layer is too restrictive.  I'm interested
>to see how others see this as well.

Isn't this an implementation issue? Look at Radius. We have the same 
protocol for the three A's. But we use a separate port for Accounting, 
implemenentations may use separate processes, and certainly will have 
separate flows of data. But the development time is reduced since we have 
the same overall protocol.



From owner-aaa-bof@merit.edu  Mon Sep 20 13:09:46 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id NAA22833
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 13:09:45 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 46D755DDCE; Mon, 20 Sep 1999 13:09:27 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 2E9A45DDDF; Mon, 20 Sep 1999 13:09:27 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by segue.merit.edu (Postfix) with ESMTP id 233F25DDCE
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 13:09:26 -0400 (EDT)
Received: from adsl-63-193-107-75.dsl.snfc21.pacbell.net ([166.45.3.11])
 by shoe.reston.mci.net (PMDF V5.2-32 #33823)
 with ESMTP id <01JG70G54AJ490PTDB@shoe.reston.mci.net> for aaa-wg@merit.edu;
 Mon, 20 Sep 1999 13:09:23 EDT
Date: Mon, 20 Sep 1999 10:09:23 -0700
From: Paul Krumviede <paul.krumviede@wcom.com>
Subject: Re: Re-chartering discussion
In-reply-to: <4.2.0.58.19990920080355.00995130@porky.ascend.com>
Originator-info: login-id=krumviede; server=localhost
To: aaa-wg@merit.edu
Message-id: <1519292822.937822163@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
MIME-version: 1.0
X-Mailer: Mulberry (Win32) [1.4.4, s/n P005-300888-001]
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
Content-transfer-encoding: 7BIT
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

--On Monday, September 20, 1999, 8:19 AM -0700 Matt Holdrege <matt@ascend.com> wrote:

> At 09:42 AM 09/20/1999 -0400, Stephen Thomas wrote:
>> | > If NASREQ requirements are in, are VoIP requirements in or
>> | > out? In a way, they should be in, as NASes are required to
>> | > do VoIP as well these days, but on the other hand VoIP has
>> | > a lot of momentum, a lot of people focused only on it, and even
>> | > the standards on it are partially done outside IETF. Would
>> | > that slow things down?
>> |
>> | My perception was that we, for some value of we, didn't understand
>> | VoIP requirements well enough at this point in time to consider them
>> | now. I would be willing to learn otherwise.
>> 
>> Just a couple of thoughts (from a value of "we" that likes to think
>> he understands VoIP fairly well ;)
>> 
>> 1) In the VoIP space it's been increasingly difficult to separate
>>    NAS from IP telephony. The purest in me thinks that such separation
>>    ought to be a desirable goal, but the pragmatist wonders if
>>    that's realistic.
>> 
>> 2) Considering VoIP requirements early could either be a good thing
>>    or a bad thing, depending on one's objectives. I believe that
>>    VoIP may represent one of the more complex AAA scenarios because
>>    of the potential for some degree of interaction with non-IP
>>    networks (i.e. the PSTN). Including VoIP in the initial work
>>    might slow things down because of the additional complexity
>>    (bad for meeting schedules) but it could also make sure that all
>>    real requirements are taken into account (good for higher quality
>>    product).
> 
> I agree Steve. As you know, many of us have been pursuing these goals 
> outside of the IETF since we had no place to develop these requirements 
> within the IETF (til now I hope). But I don't think this will slow anything 
> down. The IETF meets every day on email lists so meeting schedules 
> shouldn't be a big concern.

The problem has been that we haven't seen anybody step up to this,
although such input was solicited in Minneapolis. Perhaps we weren't
aggressive enough in repeating that solicititation.

> I also totally agree with the NAS tie-in. The reality is that they are 
> tightly linked.

Do the current NASreq outputs encapsulate the VoIP requirements?
That may the underlying question...

-paul



From owner-aaa-bof@merit.edu  Mon Sep 20 13:24:42 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id NAA23031
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 13:24:42 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BA44A5DDDF; Mon, 20 Sep 1999 13:24:23 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 9FD8E5DDE1; Mon, 20 Sep 1999 13:24:23 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by segue.merit.edu (Postfix) with ESMTP id 44A0A5DDDF
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 13:24:22 -0400 (EDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id KAA10353;
	Mon, 20 Sep 1999 10:19:23 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 20 Sep 1999 17:24:21 UT
Received: from spud.ascend.com (spud [192.207.23.51])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id KAA27275;
	Mon, 20 Sep 1999 10:24:20 -0700 (PDT)
Received: from MATT.ASCEND.COM ([205.228.251.158])
	by spud.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id KAA15718;
	Mon, 20 Sep 1999 10:24:18 -0700 (PDT)
Message-Id: <4.2.0.58.19990920102150.00a0f950@porky.ascend.com>
X-Sender: mhold@porky.ascend.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 20 Sep 1999 10:24:12 -0700
To: Paul Krumviede <paul.krumviede@wcom.com>
From: Matt Holdrege <matt@ascend.com>
Subject: Re: Re-chartering discussion
Cc: aaa-wg@merit.edu
In-Reply-To: <1519292822.937822163@adsl-63-193-107-75.dsl.snfc21.pacbell
 .net>
References: <4.2.0.58.19990920080355.00995130@porky.ascend.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

At 10:09 AM 09/20/1999 -0700, Paul Krumviede wrote:
>--On Monday, September 20, 1999, 8:19 AM -0700 Matt Holdrege 
><matt@ascend.com> wrote:
>
> > At 09:42 AM 09/20/1999 -0400, Stephen Thomas wrote:
> >> | > If NASREQ requirements are in, are VoIP requirements in or
> >> | > out? In a way, they should be in, as NASes are required to
> >> | > do VoIP as well these days, but on the other hand VoIP has
> >> | > a lot of momentum, a lot of people focused only on it, and even
> >> | > the standards on it are partially done outside IETF. Would
> >> | > that slow things down?
> >> |
> >> | My perception was that we, for some value of we, didn't understand
> >> | VoIP requirements well enough at this point in time to consider them
> >> | now. I would be willing to learn otherwise.
> >>
> >> Just a couple of thoughts (from a value of "we" that likes to think
> >> he understands VoIP fairly well ;)
> >>
> >> 1) In the VoIP space it's been increasingly difficult to separate
> >>    NAS from IP telephony. The purest in me thinks that such separation
> >>    ought to be a desirable goal, but the pragmatist wonders if
> >>    that's realistic.
> >>
> >> 2) Considering VoIP requirements early could either be a good thing
> >>    or a bad thing, depending on one's objectives. I believe that
> >>    VoIP may represent one of the more complex AAA scenarios because
> >>    of the potential for some degree of interaction with non-IP
> >>    networks (i.e. the PSTN). Including VoIP in the initial work
> >>    might slow things down because of the additional complexity
> >>    (bad for meeting schedules) but it could also make sure that all
> >>    real requirements are taken into account (good for higher quality
> >>    product).
> >
> > I agree Steve. As you know, many of us have been pursuing these goals
> > outside of the IETF since we had no place to develop these requirements
> > within the IETF (til now I hope). But I don't think this will slow 
> anything
> > down. The IETF meets every day on email lists so meeting schedules
> > shouldn't be a big concern.
>
>The problem has been that we haven't seen anybody step up to this,
>although such input was solicited in Minneapolis. Perhaps we weren't
>aggressive enough in repeating that solicititation.

Yes we should be aggressive. Perhaps the TIPHON requirements working group 
has something for us? Or IMTC? Or ITU-T SG16?

> > I also totally agree with the NAS tie-in. The reality is that they are
> > tightly linked.
>
>Do the current NASreq outputs encapsulate the VoIP requirements?
>That may the underlying question...

NASreq definitely has *some* of the VoIP requirements. But certainly not all.

As VoIP is a nascent industry, we won't be able to generate a compleat 
document. But we should be able to put together a pretty good list.



From owner-aaa-bof@merit.edu  Mon Sep 20 16:38:43 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id QAA26255
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 16:38:43 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 178875DDEC; Mon, 20 Sep 1999 16:38:24 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id F29785DDF3; Mon, 20 Sep 1999 16:38:23 -0400 (EDT)
Received: from max.phys.uu.nl (max.phys.uu.nl [131.211.32.73])
	by segue.merit.edu (Postfix) with ESMTP id 8FEE15DDEC
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 16:38:22 -0400 (EDT)
Received: from [192.168.254.5] (hst36100.phys.uu.nl [131.211.36.100])
	by max.phys.uu.nl (8.9.3/8.9.3/hjm) with ESMTP id WAA08828
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 22:38:21 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: delaat@mail.phys.uu.nl
Message-Id: <v04210102b40c45353278@[192.168.254.5]>
Date: Mon, 20 Sep 1999 22:38:06 +0200
To: aaa-wg@merit.edu
From: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Subject: Fwd: AAA and APPS area
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Hi,

Today we (Leon Gommans (Cabletron) and Cees de Laat (Utrecht 
University) had several teleconferences with various people about the 
re-chartering. Among the people spoken with are Bert Wijnen and John 
Vollbrecht.

Obviously we are worried that lots of work done in the authorisation 
workgroup gets unused or less efficiently used. Also for some of us, 
working with and thinking about applications not mentioned in the new 
charter give us an uncertain feeling of what we are doing here given 
the weeks we spend at MERIT recently to really get work done.

It now turns out that there is a lack of information on what is going 
on in the authorisation subgroup chaired by John Vollbrecht. We 
decided to split up the current draft in three smaller drafts 
(applications, model, requirements classification) and this work is 
almost done and will be submitted 15th of october. Also, since we in 
the course of those discussions started to think of generic 
multi-domain and delated authorisation requirements, we developed a 
kind of simple picture of how such an AAA server with some service in 
generic form would look like. It seems to turn out that it is 
feasable with reference to this simple model to device communication 
protocols and management requirements to create such systems. Key 
point for the model is to disentangle the authorisation logic, the 
discovery procedures for authorisation and the service specific 
"globs". This approach will give clear requirements and leads for the 
AAA protocol (not sure about the 3th A) while the actual 
implementations can be differently structured. Retrofitting the 
different (existing) applications in that model would be possible and 
as such serving short and long term goals. To make these ideas clear 
we will also try to produce a draft of a few pages describing those 
working ideas.

Discussion with Bert Wijnen learned that there is much unawareness in 
the IESG about this work as can be seen in the mail below. We need to 
work on our marketing :-)

Best regards,
Cees.



>Date: Mon, 20 Sep 99 17:09:05 DST
>From: "Bert Wijnen" <WIJNEN@vnet.ibm.com>
>To: Leon.Gommans@cabletron.com, C.T.A.M.deLaat@phys.uu.nl
>cc: randy@psg.com
>Subject: AAA and APPS area
>
>Well, here is Randy's answer. Are you ready to roll?
>
>Bert
>---------------- following is a copy ------------------------------
>From: Randy Bush <randy@psg.com>
>MIME-Version: 1.0
>To: "Bert Wijnen" <wijnen@uitvm1>
>Subject: Re: FYI - AAA and applications
>References: <199909201451.IAA214454@westrelay03.boulder.ibm.com>
>Date: Mon, 20 Sep 1999 08:01:10 -0700
>
> > Just got a call from Cees De Laat and Leon Gommans (both in NL, Utrecht)
> > who are part of the subteam that has done a lot for AAA for the
> > apps area. They are pretty dissappointed and would hate to see their
> > efforts go donw the drain. They say they have basically done most
> > of the work and are preparing documents right now.
>
>cool!
>
> > They asked if John Vollbrecht (uni of mich) could call me, but I
> > suggested that maybe John could call you today while you are still
> > in the USA. Till what time can he call?
>
>i am walking on the plane in five minutes.
>
> > In any event, I suggested that they take this positive and that
> > their work might be considered after next IETF if the AAA meets
> > current deadlines.
>
>or, if they really have it cooked, then break the exciting news to the
>chairs, and let's attempt to get in in the process!
>
>randy

_________________________________________________________________________
dr.ir. C.Th.A.M. de Laat, Faculty of Physics and Astronomy,
Utrecht University, Princetonplein 5, NL-3584CC Utrecht, The Netherlands.
Tel: (31)30-2534585 , mobile: 06-51566438 , Fax:(31)30-2537555
web: http://www.phys.uu.nl/~delaat , mail: c.t.a.m.delaat@phys.uu.nl


From owner-aaa-bof@merit.edu  Mon Sep 20 17:04:50 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA26587
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 17:04:50 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 2396F5DDC6; Mon, 20 Sep 1999 17:04:32 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E0A325DDE0; Mon, 20 Sep 1999 17:04:31 -0400 (EDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by segue.merit.edu (Postfix) with ESMTP id 90F4C5DDC6
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 17:04:30 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA12960
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 14:04:29 -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.93.37])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id OAA16507
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 14:04:28 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4)
	id OAA11340; Mon, 20 Sep 1999 14:03:59 -0700
From: Pat.Calhoun@Eng.Sun.COM (Patrice Calhoun)
Message-Id: <199909202103.OAA11340@hsmpka.eng.sun.com>
Date: Mon, 20 Sep 1999 13:56:26 -0700
To: <aaa-wg@merit.edu>
Reply-To: <Pat.Calhoun@Eng.Sun.COM>
Subject: Re: Re-chartering discussion
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>> Can't we say something stronger about when we will actually begin working 
>> on a AAA protocol?
>
>there are no penalties for coming in ahead of schedule.  there are for
>coming in behind.  so far, the former has not been a problem.  we all look
>forward to the latter,

Having a charter that implies work items does not work. I believe that we should know
in advance what is expected to happen once these requirements are complete. There are
many other standards organizations that are looking to the IETF to provide leadership
in this area, and we haven't done a great job at proving it. We need to set the 
expectation in advance, even if some of these do not have as hard dates or timelines as 
we normally have. Remember that some of this work has been going on for at least 3 years, 
and we already have some RFCs with requirements. 

However, I do agree that since we are now adding a new more access technologies, it does 
make sense to document their combined requirements.

>
>> A lot of us already know the requirements
>
>the proof is in a draft which has consensus, is it not?  a lot of folk
>eagerly await that.
>

In all fairness, and at the expense of sounding harsh, I used to think so. I believe that
the process involves much more than rough consensus. Unfortunately, I haven't found what
that is :)

PatC




From owner-aaa-bof@merit.edu  Mon Sep 20 17:12:14 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA26653
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 17:12:14 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id C85F95DDE3; Mon, 20 Sep 1999 17:11:55 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id AEDC85DDF3; Mon, 20 Sep 1999 17:11:55 -0400 (EDT)
Received: from gmtsw.com (test.glassey.com [207.126.98.130])
	by segue.merit.edu (Postfix) with SMTP id 628E55DDE3
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 17:11:54 -0400 (EDT)
Received: from PC1 by gmtsw.com (SMI-8.6/SMI-SVR4)
	id OAA03264; Mon, 20 Sep 1999 14:12:40 -0700
Message-ID: <03cf01bf03af$335127e0$0b0aff0c@lab.gmtsw.com>
From: "todd@gmtsw" <todd.glassey@www.gmtsw.com>
To: <aaa-wg@merit.edu>, "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
References: <v04210102b40c45353278@[192.168.254.5]>
Subject: Re: AAA and APPS area
Date: Mon, 20 Sep 1999 14:29:19 -0700
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.00.2918.2701
Disposition-Notification-To: todd@gmtsw <todd.glassey@gmtsw.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

While I share the concerns that merging and rechartering these groups may
have, I also want to add the concern that Audit Models needs to be a part of
this Policy and Accounting services infrastructure. Also that for these, the
use of Time Stamping Tokens and other evidentiary data structures is a key
piece of the bigger puzzle.

My suggestion is that we focus on two or three tracks of deliverables and
use the merging of these WG's to facilitate a more uniform and robust
services model for commercial and technical applications, and that this is a
win for all concerned and will facilitate spin off efforts as needed for the
deployment of these networking technologies.

Todd Glassey

----- Original Message -----
From: C. de Laat <C.T.A.M.deLaat@phys.uu.nl>
To: <aaa-wg@merit.edu>
Sent: Monday, September 20, 1999 1:38 PM
Subject: Fwd: AAA and APPS area


> Hi,
>
> Today we (Leon Gommans (Cabletron) and Cees de Laat (Utrecht
> University) had several teleconferences with various people about the
> re-chartering. Among the people spoken with are Bert Wijnen and John
> Vollbrecht.
>
> Obviously we are worried that lots of work done in the authorisation
> workgroup gets unused or less efficiently used. Also for some of us,
> working with and thinking about applications not mentioned in the new
> charter give us an uncertain feeling of what we are doing here given
> the weeks we spend at MERIT recently to really get work done.
>
> It now turns out that there is a lack of information on what is going
> on in the authorisation subgroup chaired by John Vollbrecht. We
> decided to split up the current draft in three smaller drafts
> (applications, model, requirements classification) and this work is
> almost done and will be submitted 15th of october. Also, since we in
> the course of those discussions started to think of generic
> multi-domain and delated authorisation requirements, we developed a
> kind of simple picture of how such an AAA server with some service in
> generic form would look like. It seems to turn out that it is
> feasable with reference to this simple model to device communication
> protocols and management requirements to create such systems. Key
> point for the model is to disentangle the authorisation logic, the
> discovery procedures for authorisation and the service specific
> "globs". This approach will give clear requirements and leads for the
> AAA protocol (not sure about the 3th A) while the actual
> implementations can be differently structured. Retrofitting the
> different (existing) applications in that model would be possible and
> as such serving short and long term goals. To make these ideas clear
> we will also try to produce a draft of a few pages describing those
> working ideas.
>
> Discussion with Bert Wijnen learned that there is much unawareness in
> the IESG about this work as can be seen in the mail below. We need to
> work on our marketing :-)
>
> Best regards,
> Cees.
>
>
>
> >Date: Mon, 20 Sep 99 17:09:05 DST
> >From: "Bert Wijnen" <WIJNEN@vnet.ibm.com>
> >To: Leon.Gommans@cabletron.com, C.T.A.M.deLaat@phys.uu.nl
> >cc: randy@psg.com
> >Subject: AAA and APPS area
> >
> >Well, here is Randy's answer. Are you ready to roll?
> >
> >Bert
> >---------------- following is a copy ------------------------------
> >From: Randy Bush <randy@psg.com>
> >MIME-Version: 1.0
> >To: "Bert Wijnen" <wijnen@uitvm1>
> >Subject: Re: FYI - AAA and applications
> >References: <199909201451.IAA214454@westrelay03.boulder.ibm.com>
> >Date: Mon, 20 Sep 1999 08:01:10 -0700
> >
> > > Just got a call from Cees De Laat and Leon Gommans (both in NL,
Utrecht)
> > > who are part of the subteam that has done a lot for AAA for the
> > > apps area. They are pretty dissappointed and would hate to see their
> > > efforts go donw the drain. They say they have basically done most
> > > of the work and are preparing documents right now.
> >
> >cool!
> >
> > > They asked if John Vollbrecht (uni of mich) could call me, but I
> > > suggested that maybe John could call you today while you are still
> > > in the USA. Till what time can he call?
> >
> >i am walking on the plane in five minutes.
> >
> > > In any event, I suggested that they take this positive and that
> > > their work might be considered after next IETF if the AAA meets
> > > current deadlines.
> >
> >or, if they really have it cooked, then break the exciting news to the
> >chairs, and let's attempt to get in in the process!
> >
> >randy
>
> _________________________________________________________________________
> dr.ir. C.Th.A.M. de Laat, Faculty of Physics and Astronomy,
> Utrecht University, Princetonplein 5, NL-3584CC Utrecht, The Netherlands.
> Tel: (31)30-2534585 , mobile: 06-51566438 , Fax:(31)30-2537555
> web: http://www.phys.uu.nl/~delaat , mail: c.t.a.m.delaat@phys.uu.nl
>
>



From owner-aaa-bof@merit.edu  Mon Sep 20 17:13:49 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA26711
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 17:13:49 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A9B805DDF4; Mon, 20 Sep 1999 17:13:26 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 90AA15DDF5; Mon, 20 Sep 1999 17:13:26 -0400 (EDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by segue.merit.edu (Postfix) with ESMTP id 458845DDF4
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 17:13:25 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA17181
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 14:13:24 -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.93.37])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id OAA25442
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 14:13:22 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4)
	id OAA14672; Mon, 20 Sep 1999 14:13:13 -0700
From: Pat.Calhoun@Eng.Sun.COM (Patrice Calhoun)
Message-Id: <199909202113.OAA14672@hsmpka.eng.sun.com>
Date: Mon, 20 Sep 1999 14:05:20 -0700
To: "'aaa wg'" <aaa-wg@merit.edu>
Reply-To: <Pat.Calhoun@Eng.Sun.COM>
Subject: Re: Re-chartering discussion
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Matt,

I, for one, am not in favor of reducing the number of A's in the WG's charter. I
believe that we cannot ignore the amount of hacking that ISPs have done over the years
to combine RADIUS authentication and accounting to provide special features. Having
a single protocol, or at least two protocols developed by a single group, is much
simpler than when two protocols are developed by separate standard bodies. One could state
that a good protocol would not require this, but fraud detection comes to mind and 
I think it would require something along these lines.

That said, I am also a little uncertain about reducing the number of applications down
to a small set within this WG. I would have prefered to see a separate WG work on
the short term access problem, and let AAA investigate the longer term problem. Otherwise,
a few years from now, we will be doing this all over again.

Lastly, I am aware of the work going on outside of the IETF, and although I am
involved in some of it, I still prefer open standards.

PatC
>
>>
>>PROPOSED CHARTER
>>================
>>
>>The Authentication, Authorization and Accounting working group
>>focuses on development of requirements for Authentication,
>>Authorization and Accounting as applied to Internet Access.
>>
>>The purpose behind this is to create a base protocol
>>applicable to a number of specific Internet access models.
>>These will include Network Access Server AAA, Mobile IP, and
>>roaming. By creating an architecture and set of base
>>protocols, the amount of work to create specific Internet
>>access AAA protocols will be reduced.
>
>I'm all in favor of reducing the scope of this wg.  However, I'm not a big
>fan of the way its been reduced.  I would rather reduce the scope of the wg
>by reducing the number of A's in the title.  
>
>The authentication & authorization requirements of Internet Access do not
>appear to be much different than the authentication and authorization
>requirements of, say VoIP, or DiffServ, or any other number of functions.
>However, the accounting requirements of Internet Access may be
>significantly different than the authentication/authorization requirements,
>specifically in the generality of data representation for the accounted
>information, in extensibility, and in transport.  
>
>Instead of taking a vertical application slice of AAA, why not just
>concentrate on authentication and authorization and split off accounting
>into a separate wg.  I don't recall that the group ever reached a consensus
>that a single base protocol for all three A's was the way to go.  I thought
>this was supposed to be discussed after the requirements were put together.
> The old charter specifically included the possibility of protocolS
>(plural) instead of restricting the solution to a single
>i-can-do-everything protocol.  
>
>Also, there are a number of consortia/groups that are already working on
>accounting/billing standard, and splitting accounting off would be a good
>way to focus these outside efforts in an IETF wg with that single purpose.   
>
>So by all means let's reduce the scope of the group, but instead of
>restricting the number of applications we'll look at, lets reduce the base
>functionality that's within the scope of the WG.  
>
>- Matt
>
>
>
>Matt Squire
>Nortel Networks
>innovations.lab
>msquire@nortelnetworks.com
>(919)992-9048
>




From owner-aaa-bof@merit.edu  Mon Sep 20 17:29:12 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA27102
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 17:29:12 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 527A75DD9D; Mon, 20 Sep 1999 17:28:53 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 3826A5DDE0; Mon, 20 Sep 1999 17:28:53 -0400 (EDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by segue.merit.edu (Postfix) with ESMTP id E108F5DD9D
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 17:28:51 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA24210;
	Mon, 20 Sep 1999 14:28:49 -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.93.37])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id OAA29485;
	Mon, 20 Sep 1999 14:28:47 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4)
	id OAA20562; Mon, 20 Sep 1999 14:28:40 -0700
From: Pat.Calhoun@Eng.Sun.COM (Patrice Calhoun)
Message-Id: <199909202128.OAA20562@hsmpka.eng.sun.com>
Date: Mon, 20 Sep 1999 14:20:43 -0700
To: "Paul Krumviede" <paul.krumviede@wcom.com>, <aaa-wg@merit.edu>
Reply-To: <Pat.Calhoun@Eng.Sun.COM>
Subject: Re: Re-chartering discussion
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>--On Monday, September 20, 1999, 8:19 AM -0700 Matt Holdrege <matt@ascend.com>
>wrote:
>
>> At 09:42 AM 09/20/1999 -0400, Stephen Thomas wrote:
>>> | > If NASREQ requirements are in, are VoIP requirements in or
>>> | > out? In a way, they should be in, as NASes are required to
>>> | > do VoIP as well these days, but on the other hand VoIP has
>>> | > a lot of momentum, a lot of people focused only on it, and even
>>> | > the standards on it are partially done outside IETF. Would
>>> | > that slow things down?
>>> |
>>> | My perception was that we, for some value of we, didn't understand
>>> | VoIP requirements well enough at this point in time to consider them
>>> | now. I would be willing to learn otherwise.
>>> 
>>> Just a couple of thoughts (from a value of "we" that likes to think
>>> he understands VoIP fairly well ;)
>>> 
>>> 1) In the VoIP space it's been increasingly difficult to separate
>>>    NAS from IP telephony. The purest in me thinks that such separation
>>>    ought to be a desirable goal, but the pragmatist wonders if
>>>    that's realistic.
>>> 
>>> 2) Considering VoIP requirements early could either be a good thing
>>>    or a bad thing, depending on one's objectives. I believe that
>>>    VoIP may represent one of the more complex AAA scenarios because
>>>    of the potential for some degree of interaction with non-IP
>>>    networks (i.e. the PSTN). Including VoIP in the initial work
>>>    might slow things down because of the additional complexity
>>>    (bad for meeting schedules) but it could also make sure that all
>>>    real requirements are taken into account (good for higher quality
>>>    product).
>> 
>> I agree Steve. As you know, many of us have been pursuing these goals 
>> outside of the IETF since we had no place to develop these requirements 
>> within the IETF (til now I hope). But I don't think this will slow anything 
>> down. The IETF meets every day on email lists so meeting schedules 
>> shouldn't be a big concern.
>
>The problem has been that we haven't seen anybody step up to this,
>although such input was solicited in Minneapolis. Perhaps we weren't
>aggressive enough in repeating that solicititation.
>
>> I also totally agree with the NAS tie-in. The reality is that they are 
>> tightly linked.
>
>Do the current NASreq outputs encapsulate the VoIP requirements?
>That may the underlying question...

If memory serves, NASReq included some megaco work as well as Mobile-IP. However,
I am not sure how much of this has been put down on paper.

>
>-paul
>
>




From owner-aaa-bof@merit.edu  Mon Sep 20 18:22:01 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id SAA27755
	for <aaa-wg-archive@nic.merit.edu>; Mon, 20 Sep 1999 18:22:01 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 6FC005DDEE; Mon, 20 Sep 1999 18:21:42 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 506085DDF3; Mon, 20 Sep 1999 18:21:42 -0400 (EDT)
Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14])
	by segue.merit.edu (Postfix) with ESMTP id 31C195DDEE
	for <aaa-wg@merit.edu>; Mon, 20 Sep 1999 18:21:41 -0400 (EDT)
Received: from zsc4c002.corpwest.baynetworks.com (actually h0295.s86b1.BayNetworks.COM) 
          by smtprch1.nortel.com; Mon, 20 Sep 1999 17:13:02 -0500
Received: from zbl6c008.corpeast.baynetworks.com ([132.245.205.58]) 
          by zsc4c002.corpwest.baynetworks.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) 
          id SFRCAJB7; Mon, 20 Sep 1999 15:21:12 -0700
Received: from msquire (extranet-139-167.corpeast.baynetworks.com [132.245.139.167]) 
          by zbl6c008.corpeast.baynetworks.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) 
          id SJDZ7A62; Mon, 20 Sep 1999 18:21:09 -0400
Message-Id: <3.0.32.19990920181945.00a8e7d0@zbl6c008.corpeast.baynetworks.com>
X-Sender: msquire@zbl6c008.corpeast.baynetworks.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Mon, 20 Sep 1999 18:19:48 -0400
To: "Pat.Calhoun" <Pat.Calhoun@Eng.Sun.COM>
From: "Matt Squire" <msquire@nortelnetworks.com>
Subject: Re: Re-chartering discussion
Cc: aaa-wg@merit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>
>I, for one, am not in favor of reducing the number of A's in the WG's
charter. I
>believe that we cannot ignore the amount of hacking that ISPs have done
over the years
>to combine RADIUS authentication and accounting to provide special
features. Having
>a single protocol, or at least two protocols developed by a single group,
is much
>simpler than when two protocols are developed by separate standard bodies.
One could state
>that a good protocol would not require this, but fraud detection comes to
mind and 
>I think it would require something along these lines.
>

I understand your view and even partially agree.  But vendors/providers
should be able to coordinate multiple protocols as long as they have well
defined interfaces.  If industry can't do this, then we're doing a crappy
job defining our work.  The (potential) two working groups would have to
coordinate requirements and interfaces, but not protocols, formats, etc.  

Look at all of the progress in the web/e-commerce space.  Basically,
coordinating HTTP, CGI, SQL, XML, etc, has become a multi-billion dollar
business for innovation.  We just need to provide the building blocks - let
industry run with it to create the system.   I didn't think the IETF was in
the business of defining systems, just parts, yet this WG appears to be an
exception.   

>Lastly, I am aware of the work going on outside of the IETF, and although
I am
>involved in some of it, I still prefer open standards.
>

I can't think of many people that would disagree with this.  Giving those
outside groups that are focused on different parts of the AAA problem,
whether it be accounting or authentication or authorization, an open place
to focus their efforts, without being drawn into side issues on the other
A's, seems like a good thing.  

As is, the AAA group has a huge focus.  It sticks out in the IETF landscape
because of its large potential scope.  We have to reduce it somehow.  This
is an alternate method to that proposed in the new charter.  

Separating the A's doesn't mandate that AA uses different protocols than A,
only that the groups can investigate protocols, data formats, etc.,
independently.  They could both very well both choose to use DIAMETER,
RADIUS+, or whatever.  It gives the participants the chance to focus on a
smaller problem and develop the right solution for that problem.  

For me, I couldn't tell a CHAP from a IKE from a EAP if it bit me in the
fanny, but I have looked at the accounting stuff a bit.   Its difficult for
me to follow the details of the authorization aspects of the requirements,
but I have to try because we're claiming its all just one big happy
protocol.   

Anyway, I am certainly sympathetic to your view, but I still disagree.  I
just wanted to present to the group an alternate way to gain focus.  If
everyone disagrees, so be it.  

- Matt



From owner-aaa-bof@merit.edu  Tue Sep 21 11:12:14 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA13243
	for <aaa-wg-archive@nic.merit.edu>; Tue, 21 Sep 1999 11:12:14 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 9FF995DDCD; Tue, 21 Sep 1999 11:11:53 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 85DFE5DE04; Tue, 21 Sep 1999 11:11:53 -0400 (EDT)
Received: from ctron-dnm.ctron.com (ctron-dnm.cabletron.com [12.25.1.120])
	by segue.merit.edu (Postfix) with ESMTP id 3B0E35DDCD
	for <aaa-wg@merit.edu>; Tue, 21 Sep 1999 11:11:52 -0400 (EDT)
Received: (from uucp@localhost)
	by ctron-dnm.ctron.com (8.8.7/8.8.7) id LAA16204
	for <aaa-wg@merit.edu>; Tue, 21 Sep 1999 11:13:39 -0400 (EDT)
Received: from roc-mail2.ctron.com(134.141.72.230) by ctron-dnm.ctron.com via smap (4.1)
	id xma016132; Tue, 21 Sep 99 11:12:32 -0400
Received: from ctron-exc1.ctron.com (ctron-exc1 [134.141.34.126])
	by roc-mail2.ctron.com (8.8.7/8.8.7) with ESMTP id LAA26728;
	Tue, 21 Sep 1999 11:17:27 -0400 (EDT)
Received: from cabletron.com (P5-100 [134.141.150.68]) by ctron-exc1.ctron.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id RYLW2J6C; Tue, 21 Sep 1999 11:10:08 -0400
Message-ID: <37E79F88.8ED08E1F@cabletron.com>
Date: Tue, 21 Sep 1999 11:08:56 -0400
From: David Harrington <dbh@cabletron.com>
Organization: Cabletron Systems Inc
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: aaa-wg@merit.edu
Subject: Re: Re-chartering discussion
References: <3.0.32.19990920181945.00a8e7d0@zbl6c008.corpeast.baynetworks.com>
Content-Type: multipart/mixed;
 boundary="------------C08D8BE5E94C35EBDD80EEA6"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

This is a multi-part message in MIME format.
--------------C08D8BE5E94C35EBDD80EEA6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

I would like to see the Accounting piece separated from the Auth/Auth
pieces.

1) The Accounting work is really already being done in other WGs

It is my impression that the accounting work of this WG is being done by
persons who are members of multiple working groups, each of which must
deal with accounting to some degree. The discussions about accounting
appear to occur offline or in other WGs and the AAA only gets the
resulting documents without any discussions of what goes into those
documents. I believe the discussions should be happening in, or at least
mirrored to, a centralized accounting wg.

2) Accounting seems to be largely ignored by the AAA WG because AA are
considered the primary topics of concern by most members.

I have been following the AAA WG only for two months, but I have found
it difficult to follow the accounting portion of the discussion, largely
because there hasn't been such discussion on the AAA WG mailing list. I
and others have had to explciitly request information about the
accounting efforts because they seem to be behind-the-scenes efforts, or
occuring in other WGs. The requests for information include "what
happened re: accounting at the IETF meeting in Oslo?" - the information
had not been forthcoming. 

The discussions are simply happening outside this group and the results
are then posted here, but the discussions are not held here, and that's
not fair to the members of this WG that are not also members of the
other WGs.

I don't have the time to participate in the all the other working groups
involved, since the bulk of the discussions in those other working
groups is NOT about accounting, but about other issues of those WGs.


3) Accouting should be designed independently of the other A's

My primary concern is with accounting. While I recognize the importance
of authentication and authorization when doing accounting, it should not
be the overriding concern. While security can be important to IP or SNMP
etc., these  exist independently of the security. It is possible to do
IP or SNMP without security, and it should be possible to do accounting
without security.

It has been suggested that accounting is dependent on authorization and
that authorization is sometimes dependent on accounting. I believe that
we need to design authorization and accounting as separate pieces, which
can both be used by a third piece (the application). To make integration
by a third piece possible, we need to describe the services provided by
the pieces, and we need to ensure that each piece provides services that
can be used in conjunction with the other pieces, and if possible, the
services should not have an ordering dependency. That is, the accounting
process should not require that authorization has been done, and the
authorization should not require that accounting has been done; the
"application" which binds them can impose that ordering within the
application, as needed.

Two-way dependencies make it close to impossible to solve the problem in
a reasonable time because the side-effects of any change in one piece
can affect the design of the other piece. SNMPv2/3 was held up for years
due to the cross-dependencies between pieces.

I think this WG has not done a good job thus far of separating the
authentication and authorization requirements from the accounting
requirements, and is unlikely to do so if they are considered simply
separate parts of the same problem. Accounting should most definitely
pay attention to the need to secure messages and verify that an
authenticated entity is or is not allow access to peform operations on
data, but that is not accounting's main purpose. So far it appears that
in this working group, authorization and autentication are the primary
issues of accounting. I believe there are other issues that are more
central to accounting.

Summary:

I therefore request that the accounting be separated into another
working group, and that the charter of both the AA and the A WGs require
that the working groups work closely together to ensure that the
services of each are provided in a way that promotes integration of the
output of the WGs.

dbh

Matt Squire wrote:
> 
> >
> >I, for one, am not in favor of reducing the number of A's in the WG's
> charter. I
> >believe that we cannot ignore the amount of hacking that ISPs have done
> over the years
> >to combine RADIUS authentication and accounting to provide special
> features. Having
> >a single protocol, or at least two protocols developed by a single group,
> is much
> >simpler than when two protocols are developed by separate standard bodies.
> One could state
> >that a good protocol would not require this, but fraud detection comes to
> mind and
> >I think it would require something along these lines.
> >
> 
> I understand your view and even partially agree.  But vendors/providers
> should be able to coordinate multiple protocols as long as they have well
> defined interfaces.  If industry can't do this, then we're doing a crappy
> job defining our work.  The (potential) two working groups would have to
> coordinate requirements and interfaces, but not protocols, formats, etc.
> 
> Look at all of the progress in the web/e-commerce space.  Basically,
> coordinating HTTP, CGI, SQL, XML, etc, has become a multi-billion dollar
> business for innovation.  We just need to provide the building blocks - let
> industry run with it to create the system.   I didn't think the IETF was in
> the business of defining systems, just parts, yet this WG appears to be an
> exception.
> 
> >Lastly, I am aware of the work going on outside of the IETF, and although
> I am
> >involved in some of it, I still prefer open standards.
> >
> 
> I can't think of many people that would disagree with this.  Giving those
> outside groups that are focused on different parts of the AAA problem,
> whether it be accounting or authentication or authorization, an open place
> to focus their efforts, without being drawn into side issues on the other
> A's, seems like a good thing.
> 
> As is, the AAA group has a huge focus.  It sticks out in the IETF landscape
> because of its large potential scope.  We have to reduce it somehow.  This
> is an alternate method to that proposed in the new charter.
> 
> Separating the A's doesn't mandate that AA uses different protocols than A,
> only that the groups can investigate protocols, data formats, etc.,
> independently.  They could both very well both choose to use DIAMETER,
> RADIUS+, or whatever.  It gives the participants the chance to focus on a
> smaller problem and develop the right solution for that problem.
> 
> For me, I couldn't tell a CHAP from a IKE from a EAP if it bit me in the
> fanny, but I have looked at the accounting stuff a bit.   Its difficult for
> me to follow the details of the authorization aspects of the requirements,
> but I have to try because we're claiming its all just one big happy
> protocol.
> 
> Anyway, I am certainly sympathetic to your view, but I still disagree.  I
> just wanted to present to the group an alternate way to gain focus.  If
> everyone disagrees, so be it.
> 
> - Matt
--------------C08D8BE5E94C35EBDD80EEA6
Content-Type: text/x-vcard; charset=us-ascii;
 name="dbh.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for David Harrington
Content-Disposition: attachment;
 filename="dbh.vcf"

begin:vcard 
n:Harrington;David
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:dbh@cabletron.com
fn:David Harrington
end:vcard

--------------C08D8BE5E94C35EBDD80EEA6--



From owner-aaa-bof@merit.edu  Tue Sep 21 11:37:25 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA13819
	for <aaa-wg-archive@nic.merit.edu>; Tue, 21 Sep 1999 11:37:24 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A31275DE07; Tue, 21 Sep 1999 11:36:49 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 86AFB5DE0B; Tue, 21 Sep 1999 11:36:49 -0400 (EDT)
Received: from ctron-dnm.ctron.com (ctron-dnm.cabletron.com [12.25.1.120])
	by segue.merit.edu (Postfix) with ESMTP id 26D3E5DE07
	for <aaa-wg@merit.edu>; Tue, 21 Sep 1999 11:36:48 -0400 (EDT)
Received: (from uucp@localhost)
	by ctron-dnm.ctron.com (8.8.7/8.8.7) id LAA19303
	for <aaa-wg@merit.edu>; Tue, 21 Sep 1999 11:39:25 -0400 (EDT)
Received: from roc-mail2.ctron.com(134.141.72.230) by ctron-dnm.ctron.com via smap (4.1)
	id xma019203; Tue, 21 Sep 99 11:38:58 -0400
Received: from ctron-exc1.ctron.com (ctron-exc1 [134.141.34.126])
	by roc-mail2.ctron.com (8.8.7/8.8.7) with ESMTP id LAA20520;
	Tue, 21 Sep 1999 11:43:54 -0400 (EDT)
Received: from cabletron.com (P5-100 [134.141.150.68]) by ctron-exc1.ctron.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id RYLW2K31; Tue, 21 Sep 1999 11:36:37 -0400
Message-ID: <37E7A5BD.73B42034@cabletron.com>
Date: Tue, 21 Sep 1999 11:35:25 -0400
From: David Harrington <dbh@cabletron.com>
Organization: Cabletron Systems Inc
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "'aaa wg'" <aaa-wg@merit.edu>
Subject: Re: Re-chartering discussion
References: <1474523432.937777393@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
Content-Type: multipart/mixed;
 boundary="------------68D0645E8A4D2F04B2F187F9"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

This is a multi-part message in MIME format.
--------------68D0645E8A4D2F04B2F187F9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Paul Krumviede wrote:
> 
> As a thought experiment, I see 2 reasons to keep these together.
> - we may want some form of correlation tag to allow one to associate
> all the relevant authentication and authorization decisions and the
> subsequent accounting (if any);
> - there may be services or inter-domain cases where authorization
> is conditional on accounting capabilities (off-hand, I'm thinking of
> some fraud detection capabilities here).
> 
> These might be addressed by reasonable coordination between
> efforts, but I'd like to get some sense of how others see this.
> 
> -paul

I see these two cases as "application processes"
1) a process outside the accounting process, and outside the
authorization process, and outside the accounting process can monitor
the auth/auth decisions and report them to the accounting process. The
auth/auth processes must have a mechanism by which the application can
extract a "correlation tag" and the acctg process must be able to accept
a "correlation tag", but these processes can be developed independently
and still be able to provide such tags.
2) fraud detection is an application that monitors auth/auth/acctg and
may report its findings back to auth/auth/acctg, but these processes can
be developed independently of the fraud detection application.

dbh
--------------68D0645E8A4D2F04B2F187F9
Content-Type: text/x-vcard; charset=us-ascii;
 name="dbh.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for David Harrington
Content-Disposition: attachment;
 filename="dbh.vcf"

begin:vcard 
n:Harrington;David
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:dbh@cabletron.com
fn:David Harrington
end:vcard

--------------68D0645E8A4D2F04B2F187F9--



From owner-aaa-bof@merit.edu  Tue Sep 21 11:49:25 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA13967
	for <aaa-wg-archive@nic.merit.edu>; Tue, 21 Sep 1999 11:49:24 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 4E7515DE39; Tue, 21 Sep 1999 11:48:32 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 1E0195DE2E; Tue, 21 Sep 1999 11:48:30 -0400 (EDT)
Received: from fogerty.ericsson.fi (fogerty.ericsson.fi [131.160.11.6])
	by segue.merit.edu (Postfix) with ESMTP id 76B345DE0F
	for <aaa-wg@merit.edu>; Tue, 21 Sep 1999 11:46:06 -0400 (EDT)
Received: from lmf.lmf.ericsson.se ([131.160.11.2])
	by fogerty.ericsson.fi (8.9.3/8.9.3) with ESMTP id SAA12317;
	Tue, 21 Sep 1999 18:46:23 +0300 (EET DST)
Received: from lmf.ericsson.se by lmf.lmf.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id SAA13932; Tue, 21 Sep 1999 18:46:03 +0300 (EET DST)
Message-ID: <37E7A83A.6C6E686E@lmf.ericsson.se>
Date: Tue, 21 Sep 1999 18:46:02 +0300
From: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Organization: Oy L M Ericsson Ab
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: David Harrington <dbh@cabletron.com>
Cc: aaa-wg@merit.edu
Subject: Re: Re-chartering discussion
References: <3.0.32.19990920181945.00a8e7d0@zbl6c008.corpeast.baynetworks.com> <37E79F88.8ED08E1F@cabletron.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


David writes:

>I would like to see the Accounting piece separated from the Auth/Auth
>pieces.

Do you mean now or in the protocol design phase? I think a reasonable
case can be made for the separation in the protocol design phase,
mainly because as you mention there is a wealth of work on accounting
(or something that can be turned to accounting) by other working
groups. This may make it possible to take existing protocols and tools
from SNMP/SMTP/ADIF/etc into use, and is indeed quite different situation
from the other As.

However, I feel strongly that we should provide the requirements for
all As in this working group, and now. It is precisely because of
those questions you mentioned, such as interdepency of accounting
from authorization. We need to understand the requirements and the
"division of responsibility" between the As. THEN we can do the
protocol design. Indepedently, if we want to.

By the way, I DO think authorization and accounting can be separated.
What's confusing for the dependency is things like resource management
(which has been partly done by RADIUS *Accounting* by some people in the past),
fraud detection (which may require cutting off somebody when a fraud
is detected), and credit limits. My thinking is that resource management
simply shouldn't be done with accounting, even if it means two separate
messages about the same resource -- one to the authorization server
as a request and one to the accounting server later as a report. Credit limit
checks should be done in authorization phase, if not for other reason
then mainly because we want to avoid unnecessary round-trip times
when somebody logs on to a service. It *can* be done in the authorization
server by having the home servers (author and acct) do some internal
communication. And fraud detection can be performed by having the
accounting server use again an internal interface towards the authorization
server, or simply through a public interface (authorization protocol or
SNMP or ...) towards the box itself.

>2) Accounting seems to be largely ignored by the AAA WG because AA are
>considered the primary topics of concern by most members.

I hope I'm not the only member of this WG interested about accounting.

>I think this WG has not done a good job thus far of separating the
>authentication and authorization requirements from the accounting
>requirements, and is unlikely to do so if they are considered simply

Can you point us to concrete examples where such confusion
exists so that such documents could be fixed?

Jari
---- 
Jari Arkko, Oy L M Ericsson Ab, 02420 Jorvas, Finland. Tel +358 9 2992480
Fax +358 9 2993052. GSM +358 40 5079256. E-Mail: Jari.Arkko@ericsson.com
Private WWW: http://www.iki.fi/jar. Standard disclaimers apply.


From owner-aaa-bof@merit.edu  Tue Sep 21 11:55:07 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA14064
	for <aaa-wg-archive@nic.merit.edu>; Tue, 21 Sep 1999 11:55:07 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 6580A5DDDA; Tue, 21 Sep 1999 11:54:46 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 490E05DDF3; Tue, 21 Sep 1999 11:54:46 -0400 (EDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by segue.merit.edu (Postfix) with ESMTP id 149245DDDA
	for <aaa-wg@merit.edu>; Tue, 21 Sep 1999 11:54:45 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA11990;
	Tue, 21 Sep 1999 08:53:40 -0700 (PDT)
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.105.37])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id IAA05256;
	Tue, 21 Sep 1999 08:53:39 -0700 (PDT)
Received: from hsmpka.Eng.Sun.COM by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4)
	id IAA13561; Tue, 21 Sep 1999 08:53:32 -0700
From: Pat.Calhoun@Eng.Sun.COM (Patrice Calhoun)
Message-Id: <199909211553.IAA13561@hsmpka.eng.sun.com>
Date: Tue, 21 Sep 1999 08:45:26 -0700
To: "David Harrington" <dbh@cabletron.com>, <aaa-wg@merit.edu>
Reply-To: <Pat.Calhoun@Eng.Sun.COM>
Subject: Re: Re-chartering discussion
X-Mailer: Sun NetMail 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>Hi,
>
>I would like to see the Accounting piece separated from the Auth/Auth
>pieces.
>
>1) The Accounting work is really already being done in other WGs
>
>It is my impression that the accounting work of this WG is being done by
>persons who are members of multiple working groups, each of which must
>deal with accounting to some degree. The discussions about accounting
>appear to occur offline or in other WGs and the AAA only gets the
>resulting documents without any discussions of what goes into those
>documents. I believe the discussions should be happening in, or at least
>mirrored to, a centralized accounting wg.

True and most of these are intra-domain accounting protocols. However, one of
the main goals behind the AAA WG is to allow the accounting portion to traverse
domains in a manner similar to authentication and authorization. The ROAMOPS,
Mobile-IP and NASREQng WGs need this, but I agree that some other "simpler"
applications may not.

Furthermore, I am reluctant to accept one accounting protocol per WG. I would
prefer to see one IETF accounting protocol, that solves the intra and inter
domain problem. Of course, whatever we end up with may not be acceptable for
some applications, so we will still be seeing other WG work in this area, but 
at least a common accounting protocol for Access Technology (PPP, Mobile-IP, VoIP)
would benefit the Internet Community.

>
>2) Accounting seems to be largely ignored by the AAA WG because AA are
>considered the primary topics of concern by most members.
>
>I have been following the AAA WG only for two months, but I have found
>it difficult to follow the accounting portion of the discussion, largely
>because there hasn't been such discussion on the AAA WG mailing list. I
>and others have had to explciitly request information about the
>accounting efforts because they seem to be behind-the-scenes efforts, or
>occuring in other WGs. The requests for information include "what
>happened re: accounting at the IETF meeting in Oslo?" - the information
>had not been forthcoming. 
>
>The discussions are simply happening outside this group and the results
>are then posted here, but the discussions are not held here, and that's
>not fair to the members of this WG that are not also members of the
>other WGs.
>
>I don't have the time to participate in the all the other working groups
>involved, since the bulk of the discussions in those other working
>groups is NOT about accounting, but about other issues of those WGs.
>

It is true that there are sub-groups working on the different 'A' pieces, but
these are not closed groups. As far as authorization is concerned, I have added
anyone to the list that has requested it. The reason for keeping it as a separate
list is to focus on authorization. There are similar lists for authentication and
accounting. I would suggest that you request to be on the accounting sub-group list
if you are interested.

Once we get the initial set of requirements out, we would then move back to the main
list.

However, now that the charter's changed and we have application specific focus,
perhaps these points are moot.

>
>3) Accouting should be designed independently of the other A's
>
>My primary concern is with accounting. While I recognize the importance
>of authentication and authorization when doing accounting, it should not
>be the overriding concern. While security can be important to IP or SNMP
>etc., these  exist independently of the security. It is possible to do
>IP or SNMP without security, and it should be possible to do accounting
>without security.

Possible yes, but security has to be designed from the get-go, not an add on
to please the IESG while in last call.

>
>It has been suggested that accounting is dependent on authorization and
>that authorization is sometimes dependent on accounting. I believe that
>we need to design authorization and accounting as separate pieces, which
>can both be used by a third piece (the application). To make integration
>by a third piece possible, we need to describe the services provided by
>the pieces, and we need to ensure that each piece provides services that
>can be used in conjunction with the other pieces, and if possible, the
>services should not have an ordering dependency. That is, the accounting
>process should not require that authorization has been done, and the
>authorization should not require that accounting has been done; the
>"application" which binds them can impose that ordering within the
>application, as needed.
>
>Two-way dependencies make it close to impossible to solve the problem in
>a reasonable time because the side-effects of any change in one piece
>can affect the design of the other piece. SNMPv2/3 was held up for years
>due to the cross-dependencies between pieces.
>
>I think this WG has not done a good job thus far of separating the
>authentication and authorization requirements from the accounting
>requirements, and is unlikely to do so if they are considered simply
>separate parts of the same problem. Accounting should most definitely
>pay attention to the need to secure messages and verify that an
>authenticated entity is or is not allow access to peform operations on
>data, but that is not accounting's main purpose. So far it appears that
>in this working group, authorization and autentication are the primary
>issues of accounting. I believe there are other issues that are more
>central to accounting.

I am not sure that I agree with everything here, but I do agree that we haven't
done a good job at separating them. It isn't clear whether we can, or cannot. What
we are currently focusing on are the individual requirements of each component,
independent of the other A's (at least that's what we've done in authorization).

Dependencies can make things very difficult in the end, but exisiting implementations
and deployment have proven that accounting is very much tied to authentication and
authorization. It would be silly to forget what we've already learned.

>
>Summary:
>
>I therefore request that the accounting be separated into another
>working group, and that the charter of both the AA and the A WGs require
>that the working groups work closely together to ensure that the
>services of each are provided in a way that promotes integration of the
>output of the WGs.

What I do agree with here, is that other working groups have to work closely
together, but a major effort to have all WGs that are interested in accounting
work together would be near to impossible. I think that a single WG needs to focus 
on such an area, and invite as many people from other WGs to cooperate.

PatC



From owner-aaa-bof@merit.edu  Tue Sep 21 14:40:55 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id OAA18481
	for <aaa-wg-archive@nic.merit.edu>; Tue, 21 Sep 1999 14:40:54 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 8C8B05DD96; Tue, 21 Sep 1999 14:40:34 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 726515DDF3; Tue, 21 Sep 1999 14:40:34 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 530D25DD96
	for <AAA-WG@Merit.edu>; Tue, 21 Sep 1999 14:40:33 -0400 (EDT)
Received: from Merit.edu (dwspencepc.merit.edu [198.108.62.224]) by home.merit.edu (8.8.8/merit-2.0) with ESMTP id OAA18922 for <AAA-WG@Merit.edu>; Tue, 21 Sep 1999 14:40:33 -0400 (EDT)
Message-ID: <37E7D120.9478F2E6@Merit.edu>
Date: Tue, 21 Sep 1999 14:40:32 -0400
From: "David W. Spence" <DWSpence@merit.edu>
Organization: Merit Network, Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: AAA WG <AAA-WG@merit.edu>
Subject: September 17 Meeting of Authorization Subgroup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

      The Authorization Subgroup of the AAA WG met on Friday Sept. 17, 
      1999, via telephone conference.  The meeting began at 15:30 UTC.
      
      The following people participated in the call:
      
         Stephen Farrell
         Cees de Laat
         Leon Gommans
         Gopal Iyengar
         John Vollbrecht
         David Spence
      
      1. AAA Working Group Status
      
         At the time of the conference call, we had received Randy 
         Bush's email of Sept. 16, but not Bernard Aboba's emails of 
         Sept. 17.  Therefore, we realized that the AAA charter might 
         narrow in scope, but we didn't know how much or when a change 
         in charter might be attempted.
         
         In our discussion, we decided to maintain our course and stick 
         to our goal of producing a set of general purpose authorization 
         requirements by Oct. 15.
         
      2. Document Organization
         
         We discussed the organization of the authorization draft.  
         Currently, it consists of three main parts, an architecture 
         section, a requirements section (mostly to be supplied as of 
         ver. 00), and an applications appendix.  All three sections are 
         important and are highly interrelated, but they don't 
         necessarily need to stay in the same document.
         
         Dependencies among the sections are as follows.  The 
         requirements depend on the architecture.  Without an explicit 
         architecture, the requirements section would be burdened with 
         long-winded explanations which would make it difficult to read.  
         The requirements section also depends on the applications.  
         Each application section lists requirements of that 
         application.  In order for the working group to review the 
         requirements, it is useful to have examples of specific 
         applications that have the requirements.  The architecture 
         section depends on the application section as well.  The 
         architecture by itself is merely interesting.  To see if it is 
         also useful, one needs to ask if it can support multiple 
         diverse applications.  Therefore, each application subsection 
         demonstrates how that application can be accommodated by the 
         architecture.
         
         Due primarily to the length of the document, we decided to 
         break the applications section out into a separate paper.  
         Depending on how large the requirements section grows, we may 
         then split the requirements section off from the architecture 
         and create two more papers.
         
      3. Meetings
         
         We considered having a face-to-face meeting before the November 
         IETF, but concluded that not enough people would be able to 
         attend.
         
         We then considered whether to have an extended phone conference 
         after we have generated an initial cut on the requirements in 
         order to work through them as a group.  We tentatively decided 
         to hold a 3-4 hour conference call in the middle of the week of 
         Oct. 3.
         
         We then reaffirmed our target dates of producing our first 
         complete cut of the requirements by Sept. 30, and releasing a 
         draft by Oct. 15.
         
      4. John Vollbrecht's Contribution on Message Content
         
         Next we considered John Vollbrecht's contribution on message 
         content.  This contribution grew out of our discussions of data 
         representation and attribute certificates, but the contribution 
         is not concerned with message syntax.  Essentially it attempts 
         to fill in a portion of the architecture that had not been 
         adequately considered.  John went back to the entities defined 
         in the architecture and grappled with the fact that specific 
         entities need to generate data destined to other specific 
         entities.  Each of these "globs" of data may need to be signed 
         by the entity that generated it and may need to be encrypted so 
         that only the intended recipient of the glob can decrypt it.  A 
         AAA message flowing according to any of the sequences described 
         in the architecture may need to carry several of these globs.  
         This leads to a requirement to organize the authorization data 
         into a set of possibly signed, possibly encrypted globs that 
         each identify its sender and intended recipient.
         
         John's contribution needs to be refined and added to the 
         architecture.  The requirements that can be derived from it 
         then need to be enumerated and added to the requirements 
         section.
         
      5. Stephen Farrell's Contribution on Base Requirements
         
         Next we took up Stephen Farrell's contribution.  Stephen took a 
         pass through the entire authorization draft and extracted a 
         list of 46 requirements.  These are intended to provide a base 
         to which other requirements can be added.
         
         In our discussion, we stepped through the first several of his 
         requirements.  There are several issues to be addressed 
         regarding how to organize the requirements, how to relate them 
         to the architecture, how to relate between the specific 
         authorization requirements of each application and the general 
         authorization requirements, etc.  Stephen's document provides a 
         concrete base from which we can understand these issues as well 
         as a basic collection of requirements data.
         
         We need to continue discussion of Stephen's contribution in 
         future phone conferences.  In the meantime, participants in 
         the authorization subgroup will send suggestions to Stephen and 
         he will incorporate them into his next revision.
         
      6. Backlog of Contributions
         
         There are several contributions which we did not have time to 
         consider during Friday's phone conference.
         
         We barely introduced Cees de Laat's contribution on "Computer 
         based education and distance learning".  This is essentially a 
         test case to see if our architecture is broad enough to cover a 
         reasonably complex authorization application.  The intent is 
         that the AAA protocols conforming to our architecture and 
         meeting our requirements should either support future 
         applications directly or be able to be extended to support 
         future applications in a straightforward way.  The applications 
         in the appendix of the authorization draft were described 
         concurrently with the development of the architecture.  This 
         one has been offered since publication of the architecture.  
         
         The application also provides insight for AAA server developers 
         who are trying to design servers that can be readily expanded 
         to support fairly complex authorization applications in the 
         future, or else can offer an interface that will allow 
         application developers to interface application specific 
         modules to a core server.
         
         We did not discuss George Gross's contribution on AAA data 
         representation requirements because George was unfortunately 
         prevented from joining the call.
         
         We also did not discuss Pat Calhoun's contribution on mobile-IP 
         requirements because Pat was also regrettably prevented from 
         joining the call.
         
      7. Next Meetings
         
         Due to the backlog of contributions to consider, we decided to 
         have a mid-week meeting on Wednesday Sept. 22 at 15:30 UTC.
         
         We will continue to meet on Fridays as well.  The next few 
         phone conferences will therefore be:
         
         Sept. 22 at 15:30 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         Sept. 24 at 15:30 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         Oct.   1 at 15:30 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         
      8. Adjournment
         
         The meeting adjourned at 16:40 UTC.
         
         
      Postscript
      ----------
      
      As of the adjournment of the September 17 conference call, the 
      authorization subgroup was essentially on target with respect to 
      an admittedly aggressive plan to develop a first draft of a general 
      authorization requirements document before the November IETF.  The 
      goal is to publish the draft by October 15 so as to give some 
      reasonable time for mailing list discussion prior to the November 
      IETF.  Because of the amount of new ground we are breaking, I 
      would expect numerous revisions to be made to the October draft 
      before it will be ready for protocol designers, but our sincere 
      intent is to provide a sound enough foundation to support a 
      detailed review and discussion by IETF experts at the IETF meeting 
      in November.

-- 
David W. Spence                                email: DWSpence@Merit.edu
Senior Systems Research Programmer             phone: (734) 615-2630
Merit Network, Inc.                            fax:   (734) 647-3745
4151 Plymouth Road, Suite C
Ann Arbor MI 48105-2785
U.S.A.


From owner-aaa-bof@merit.edu  Wed Sep 22 09:48:31 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id JAA07013
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 09:48:31 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 1F54D5DDA2; Wed, 22 Sep 1999 09:48:03 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 06E525DDA8; Wed, 22 Sep 1999 09:48:02 -0400 (EDT)
Received: from survis.surfnet.nl (survis.surfnet.nl [192.87.108.3])
	by segue.merit.edu (Postfix) with SMTP id B051D5DDA2
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 09:48:01 -0400 (EDT)
Received: from [192.87.109.229] (actually host dhcp5.surfnet.nl) 
          by survis.surfnet.nl with SN-SMTP (PP) with ESMTP;
          Wed, 22 Sep 1999 15:47:51 +0200
Mime-Version: 1.0
X-Sender: delaat@mail.phys.uu.nl
Message-Id: <v04210101b40e8e3ed91a@[192.87.109.229]>
Date: Wed, 22 Sep 1999 15:47:46 +0200
To: aaa-wg@merit.edu
From: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Subject: Re-chartering wording
Cc: lgommans@phys.uu.nl
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by nic.merit.edu id JAA07013

Hi, the mail below bounced to the aaa-wg listserver this night??? Now 
once more.

Best regards,
Cees.


Hi,

We understand the goals of the charter rework and support the idea to 
focus the work in the short term to get much needed results. However 
we essentially disagree with the statement that application-layer AAA 
is fundamentally different set of issues and that this should be out 
of the scope of the AAA WG.
These issues may not be fully understood yet but in the long term we 
should start to investigate them. We would like to see less strong 
wording on the
focus on Internet Access. The application layer paragraph should 
reflect that that work may be outside the short term milestones but 
nevertheless essential to the long term goals of the AAA-WG.

Kind regards,

Cees de Laat and Leon Gommans

>PROPOSED CHARTER
>================
>
>The Authentication, Authorization and Accounting working group
>focuses on development of requirements for Authentication,
>Authorization and Accounting as applied to Internet Access.
>
>The purpose behind this is to create a base protocol
>applicable to a number of specific Internet access models.
>These will include Network Access Server AAA, Mobile IP, and
>roaming. By creating an architecture and set of base
>protocols, the amount of work to create specific Internet
>access AAA protocols will be reduced.
>
>The working group will incorporate requirements provided by
>the NASREQ, Mobile IP, and ROAMOPS working groups. Once
>the requirements documents are completed, the working group
>may be re-chartered to include work regarding the base protocol.
>
>Since application-layer authentication, authorization and
>accounting presents a fundamentally different set of
>issues, work in this area is outside the scope of the
>AAA WG.
>
>The immediate goals of the AAA working group are to:
>
>- assemble AAA requirements arising from specific Internet access
>applications: Network Access Server AAA, Mobile IP, and roaming.
>
>- document requirements for a base AAA architecture;
>
>- identify the relationship and interaction between Policy and
>Authorization;
>
>Goals and Milestones:
>Sep 99    Submit Mobile IP requirements initial Internet-Draft
>Sep 99    Submit Accounting Requirements initial Internet-Draft(s)
>Oct 99    Submit policy/authorization initial Internet-Draft
>Nov 99    Revision of charter to include statement of work regarding the
>base
>          protocols and data formats.

_________________________________________________________________________
dr.ir. C.Th.A.M. de Laat
Position work: N 52°05'8.3", E 5°10'1.9", home: N 52°02'14.0" E 005°09'26.7"


From owner-aaa-bof@merit.edu  Wed Sep 22 10:13:28 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA07763
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 10:13:28 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 2F2755DE02; Wed, 22 Sep 1999 10:12:31 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 087E05DDBA; Wed, 22 Sep 1999 10:12:31 -0400 (EDT)
Received: from balinese.baltimore.ie (pc215-8.indigo.ie [194.125.215.8])
	by segue.merit.edu (Postfix) with ESMTP id 13E515DDED
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 10:12:26 -0400 (EDT)
Received: by balinese.baltimore.ie; id PAA00296; Wed, 22 Sep 1999 15:12:23 +0100 (GMT/IST)
Received: from bobcat.baltimore.ie(192.168.20.10) by balinese.baltimore.ie via smap (V4.2)
	id xma000280; Wed, 22 Sep 99 15:12:19 +0100
Received: from baltimore.ie ([192.168.21.167])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id PAA05345;
	Wed, 22 Sep 1999 15:12:14 +0100
Message-ID: <37E8E47D.31CC2BE5@baltimore.ie>
Date: Wed, 22 Sep 1999 15:15:26 +0100
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Cc: aaa-wg@merit.edu, lgommans@phys.uu.nl, xme <stephen.farrell@baltimore.ie>
Subject: Re: Re-chartering wording
References: <v04210101b40e8e3ed91a@[192.87.109.229]>
Content-Type: text/plain; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by bobcat.baltimore.ie id PAA05345
Sender: owner-aaa-bof@merit.edu
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by nic.merit.edu id KAA07763


Cees,

I completely agree that application layer AAA isn't "fundamentally 
different" and would suggest given the short/long term issues
involved we invoke the MUST/SHOULD clause. So how about making 
the following change, from:

> >The working group will incorporate requirements provided by
> >the NASREQ, Mobile IP, and ROAMOPS working groups. Once
> >the requirements documents are completed, the working group
> >may be re-chartered to include work regarding the base protocol.
> >
> >Since application-layer authentication, authorization and
> >accounting presents a fundamentally different set of
> >issues, work in this area is outside the scope of the
> >AAA WG.

...to:

"The working group will incorporate requirements provided by
the NASREQ, Mobile IP, and ROAMOPS working groups. Once
the requirements documents are completed, the working group
may be re-chartered to include work regarding the base protocol

Since application layer authentication, authorization and 
accounting MAY raise issues which cannot be addressed in
the short term, the WG MUST address the AAA requirements
for the WGs specified in the previous paragraph, but SHOULD 
also, where possible, address application layer AAA issues."

Regards,
Stephen.


"C. de Laat" wrote:
> 
> Hi, the mail below bounced to the aaa-wg listserver this night??? Now
> once more.
> 
> Best regards,
> Cees.
> 
> Hi,
> 
> We understand the goals of the charter rework and support the idea to
> focus the work in the short term to get much needed results. However
> we essentially disagree with the statement that application-layer AAA
> is fundamentally different set of issues and that this should be out
> of the scope of the AAA WG.
> These issues may not be fully understood yet but in the long term we
> should start to investigate them. We would like to see less strong
> wording on the
> focus on Internet Access. The application layer paragraph should
> reflect that that work may be outside the short term milestones but
> nevertheless essential to the long term goals of the AAA-WG.
> 
> Kind regards,
> 
> Cees de Laat and Leon Gommans
> 
> >PROPOSED CHARTER
> >================
> >
> >The Authentication, Authorization and Accounting working group
> >focuses on development of requirements for Authentication,
> >Authorization and Accounting as applied to Internet Access.
> >
> >The purpose behind this is to create a base protocol
> >applicable to a number of specific Internet access models.
> >These will include Network Access Server AAA, Mobile IP, and
> >roaming. By creating an architecture and set of base
> >protocols, the amount of work to create specific Internet
> >access AAA protocols will be reduced.
> >
> >The working group will incorporate requirements provided by
> >the NASREQ, Mobile IP, and ROAMOPS working groups. Once
> >the requirements documents are completed, the working group
> >may be re-chartered to include work regarding the base protocol.
> >
> >Since application-layer authentication, authorization and
> >accounting presents a fundamentally different set of
> >issues, work in this area is outside the scope of the
> >AAA WG.
> >
> >The immediate goals of the AAA working group are to:
> >
> >- assemble AAA requirements arising from specific Internet access
> >applications: Network Access Server AAA, Mobile IP, and roaming.
> >
> >- document requirements for a base AAA architecture;
> >
> >- identify the relationship and interaction between Policy and
> >Authorization;
> >
> >Goals and Milestones:
> >Sep 99    Submit Mobile IP requirements initial Internet-Draft
> >Sep 99    Submit Accounting Requirements initial Internet-Draft(s)
> >Oct 99    Submit policy/authorization initial Internet-Draft
> >Nov 99    Revision of charter to include statement of work regarding the
> >base
> >          protocols and data formats.
> 
> _________________________________________________________________________
> dr.ir. C.Th.A.M. de Laat
> Position work: N 52°05'8.3", E 5°10'1.9", home: N 52°02'14.0" E 005°09'26.7"

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 647 7406
61 Fitzwilliam Lane,                    fax: +353 1 647 7499
Dublin 2.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-aaa-bof@merit.edu  Wed Sep 22 10:42:18 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA08634
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 10:42:18 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id C63945DDAC; Wed, 22 Sep 1999 10:41:58 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id AA5CD5DDB4; Wed, 22 Sep 1999 10:41:58 -0400 (EDT)
Received: from idrp.merit.edu (idrp.merit.edu [198.108.60.89])
	by segue.merit.edu (Postfix) with ESMTP id AF3E85DDAC
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 10:41:57 -0400 (EDT)
Received: from localhost (skh@localhost)
	by idrp.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA07900
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 10:41:57 -0400 (EDT)
X-Authentication-Warning: idrp.merit.edu: skh owned process doing -bs
Date: Wed, 22 Sep 1999 10:41:57 -0400 (EDT)
From: Susan Hares <skh@merit.edu>
To: aaa-wg@merit.edu
Subject: Forwarding bounced message.
Message-ID: <Pine.GSO.4.03.9909221041390.7703-210000@idrp.merit.edu>
MIME-Version: 1.0
Content-Type: MULTIPART/REPORT; REPORT-TYPE=delivery-status; BOUNDARY="GAA21175.938008101/venus.Sun.COM"
Content-ID: <Pine.GSO.4.03.9909221041391.7703@idrp.merit.edu>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--GAA21175.938008101/venus.Sun.COM
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.GSO.4.03.9909221041392.7703@idrp.merit.edu>



---------- Forwarded message ----------
Date: Wed, 22 Sep 1999 06:48:21 -0700 (PDT)
From: Mail Delivery Subsystem <MAILER-DAEMON@venus.Sun.COM>
To: owner-aaa-bof@merit.edu
Subject: Returned mail: User unknown

The original message was received at Wed, 22 Sep 1999 06:48:20 -0700 (PDT)
from segue.merit.edu [198.108.1.41]

   ----- The following addresses had permanent fatal errors -----
<cperkins@eng.sun.com>

   ----- Transcript of session follows -----
... while talking to engmail3.eng.sun.com.:
>>> RCPT To:<cperkins@eng.sun.com>
<<< 550 <cperkins@eng.sun.com>... User unknown
550 <cperkins@eng.sun.com>... User unknown

--GAA21175.938008101/venus.Sun.COM
Content-Type: MESSAGE/DELIVERY-STATUS; CHARSET=US-ASCII
Content-ID: <Pine.GSO.4.03.9909221041393.7703@idrp.merit.edu>
Content-Description: 

Reporting-MTA: dns; venus.Sun.COM
Received-From-MTA: DNS; segue.merit.edu
Arrival-Date: Wed, 22 Sep 1999 06:48:20 -0700 (PDT)

Final-Recipient: RFC822; cperkins@eng.sun.com
Action: failed
Status: 5.1.1
Remote-MTA: DNS; engmail3.eng.sun.com
Diagnostic-Code: SMTP; 550 <cperkins@eng.sun.com>... User unknown
Last-Attempt-Date: Wed, 22 Sep 1999 06:48:21 -0700 (PDT)

--GAA21175.938008101/venus.Sun.COM
Content-Type: TEXT/RFC822-HEADERS; CHARSET=US-ASCII
Content-ID: <Pine.GSO.4.03.9909221041394.7703@idrp.merit.edu>
Content-Description: 

Return-Path: <owner-aaa-bof@merit.edu>
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA21168;
	Wed, 22 Sep 1999 06:48:20 -0700 (PDT)
Received: by segue.merit.edu (Postfix)
	id 1F54D5DDA2; Wed, 22 Sep 1999 09:48:03 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 06E525DDA8; Wed, 22 Sep 1999 09:48:02 -0400 (EDT)
Received: from survis.surfnet.nl (survis.surfnet.nl [192.87.108.3])
	by segue.merit.edu (Postfix) with SMTP id B051D5DDA2
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 09:48:01 -0400 (EDT)
Received: from [192.87.109.229] (actually host dhcp5.surfnet.nl) 
          by survis.surfnet.nl with SN-SMTP (PP) with ESMTP;
          Wed, 22 Sep 1999 15:47:51 +0200
Mime-Version: 1.0
X-Sender: delaat@mail.phys.uu.nl
Message-Id: <v04210101b40e8e3ed91a@[192.87.109.229]>
Date: Wed, 22 Sep 1999 15:47:46 +0200
To: aaa-wg@merit.edu
From: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Subject: Re-chartering wording
Cc: lgommans@phys.uu.nl
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

--GAA21175.938008101/venus.Sun.COM--


From owner-aaa-bof@merit.edu  Wed Sep 22 10:55:16 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA08943
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 10:55:16 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 4B7C55DDE8; Wed, 22 Sep 1999 10:54:57 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 32BB55DDED; Wed, 22 Sep 1999 10:54:57 -0400 (EDT)
Received: from ctron-dnm.ctron.com (ctron-dnm.cabletron.com [12.25.1.120])
	by segue.merit.edu (Postfix) with ESMTP id 1629F5DDE8
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 10:54:56 -0400 (EDT)
Received: (from uucp@localhost)
	by ctron-dnm.ctron.com (8.8.7/8.8.7) id KAA28049;
	Wed, 22 Sep 1999 10:57:30 -0400 (EDT)
Received: from roc-mail2.ctron.com(134.141.72.230) by ctron-dnm.ctron.com via smap (4.1)
	id xmaxb6258; Wed, 22 Sep 99 10:48:19 -0400
Received: from new-exc1.ctron.com (NEW-EXC1 [134.141.200.123])
	by roc-mail2.ctron.com (8.8.7/8.8.7) with ESMTP id KAA13955;
	Wed, 22 Sep 1999 10:26:09 -0400 (EDT)
Received: by new-exc1.ctron.com with Internet Mail Service (5.5.2448.0)
	id <SQNZKVZV>; Wed, 22 Sep 1999 15:18:33 +0100
Message-ID: <29752A74B6C5D211A4920090273CA3DC9053DC@new-exc1.ctron.com>
From: "Gommans, Leon" <Leon.Gommans@cabletron.com>
To: "'todd@gmtsw'" <todd.glassey@www.gmtsw.com>, aaa-wg@merit.edu,
        "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Subject: RE: AAA and APPS area
Date: Wed, 22 Sep 1999 15:18:31 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Todd,

I agree with your concern and my personal feeling would be to add another
'A' to the working group's name. Some folks however may assert that once
you log every event it is easy to implement both accounting and auditing.
It might be considered both a different process on top of the same
data. However auditing in my oppinion may require specific attributes
which an authorized person might want only turn on for logging when
you suspect fraud or generate certain test messages as you just want
to verify wether all processes involved do all the things you expect
it to do.

I guess we need to be aware that there might be also requirements in
an AAA protocol specificaly serving auditing. E.g. having the
ability to time-stamp an authorization event seems indeed to be a logical
requirement for both auditing and non-repudiation.

Regards .. Leon.



-----Original Message-----
From: todd@gmtsw [mailto:todd.glassey@www.gmtsw.com]
Sent: Monday, September 20, 1999 11:29 PM
To: aaa-wg@merit.edu; C. de Laat
Subject: Re: AAA and APPS area


While I share the concerns that merging and rechartering these groups may
have, I also want to add the concern that Audit Models needs to be a part of
this Policy and Accounting services infrastructure. Also that for these, the
use of Time Stamping Tokens and other evidentiary data structures is a key
piece of the bigger puzzle.

My suggestion is that we focus on two or three tracks of deliverables and
use the merging of these WG's to facilitate a more uniform and robust
services model for commercial and technical applications, and that this is a
win for all concerned and will facilitate spin off efforts as needed for the
deployment of these networking technologies.

Todd Glassey

----- Original Message -----
From: C. de Laat <C.T.A.M.deLaat@phys.uu.nl>
To: <aaa-wg@merit.edu>
Sent: Monday, September 20, 1999 1:38 PM
Subject: Fwd: AAA and APPS area


> Hi,
>
> Today we (Leon Gommans (Cabletron) and Cees de Laat (Utrecht
> University) had several teleconferences with various people about the
> re-chartering. Among the people spoken with are Bert Wijnen and John
> Vollbrecht.
>
> Obviously we are worried that lots of work done in the authorisation
> workgroup gets unused or less efficiently used. Also for some of us,
> working with and thinking about applications not mentioned in the new
> charter give us an uncertain feeling of what we are doing here given
> the weeks we spend at MERIT recently to really get work done.
>
> It now turns out that there is a lack of information on what is going
> on in the authorisation subgroup chaired by John Vollbrecht. We
> decided to split up the current draft in three smaller drafts
> (applications, model, requirements classification) and this work is
> almost done and will be submitted 15th of october. Also, since we in
> the course of those discussions started to think of generic
> multi-domain and delated authorisation requirements, we developed a
> kind of simple picture of how such an AAA server with some service in
> generic form would look like. It seems to turn out that it is
> feasable with reference to this simple model to device communication
> protocols and management requirements to create such systems. Key
> point for the model is to disentangle the authorisation logic, the
> discovery procedures for authorisation and the service specific
> "globs". This approach will give clear requirements and leads for the
> AAA protocol (not sure about the 3th A) while the actual
> implementations can be differently structured. Retrofitting the
> different (existing) applications in that model would be possible and
> as such serving short and long term goals. To make these ideas clear
> we will also try to produce a draft of a few pages describing those
> working ideas.
>
> Discussion with Bert Wijnen learned that there is much unawareness in
> the IESG about this work as can be seen in the mail below. We need to
> work on our marketing :-)
>
> Best regards,
> Cees.
>
>
>
> >Date: Mon, 20 Sep 99 17:09:05 DST
> >From: "Bert Wijnen" <WIJNEN@vnet.ibm.com>
> >To: Leon.Gommans@cabletron.com, C.T.A.M.deLaat@phys.uu.nl
> >cc: randy@psg.com
> >Subject: AAA and APPS area
> >
> >Well, here is Randy's answer. Are you ready to roll?
> >
> >Bert
> >---------------- following is a copy ------------------------------
> >From: Randy Bush <randy@psg.com>
> >MIME-Version: 1.0
> >To: "Bert Wijnen" <wijnen@uitvm1>
> >Subject: Re: FYI - AAA and applications
> >References: <199909201451.IAA214454@westrelay03.boulder.ibm.com>
> >Date: Mon, 20 Sep 1999 08:01:10 -0700
> >
> > > Just got a call from Cees De Laat and Leon Gommans (both in NL,
Utrecht)
> > > who are part of the subteam that has done a lot for AAA for the
> > > apps area. They are pretty dissappointed and would hate to see their
> > > efforts go donw the drain. They say they have basically done most
> > > of the work and are preparing documents right now.
> >
> >cool!
> >
> > > They asked if John Vollbrecht (uni of mich) could call me, but I
> > > suggested that maybe John could call you today while you are still
> > > in the USA. Till what time can he call?
> >
> >i am walking on the plane in five minutes.
> >
> > > In any event, I suggested that they take this positive and that
> > > their work might be considered after next IETF if the AAA meets
> > > current deadlines.
> >
> >or, if they really have it cooked, then break the exciting news to the
> >chairs, and let's attempt to get in in the process!
> >
> >randy
>
> _________________________________________________________________________
> dr.ir. C.Th.A.M. de Laat, Faculty of Physics and Astronomy,
> Utrecht University, Princetonplein 5, NL-3584CC Utrecht, The Netherlands.
> Tel: (31)30-2534585 , mobile: 06-51566438 , Fax:(31)30-2537555
> web: http://www.phys.uu.nl/~delaat , mail: c.t.a.m.delaat@phys.uu.nl
>
>



From owner-aaa-bof@merit.edu  Wed Sep 22 11:04:59 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA09091
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 11:04:59 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 317D15DDF3; Wed, 22 Sep 1999 11:01:33 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 14ACD5DE0E; Wed, 22 Sep 1999 11:01:33 -0400 (EDT)
Received: from idrp.merit.edu (idrp.merit.edu [198.108.60.89])
	by segue.merit.edu (Postfix) with ESMTP id 180205DDF3
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 11:01:32 -0400 (EDT)
Received: from localhost (skh@localhost)
	by idrp.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA07995
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 11:01:31 -0400 (EDT)
X-Authentication-Warning: idrp.merit.edu: skh owned process doing -bs
Date: Wed, 22 Sep 1999 11:01:31 -0400 (EDT)
From: Susan Hares <skh@merit.edu>
To: aaa-wg@merit.edu
Subject: Undelivered Mail Returned to Sender (fwd)
Message-ID: <Pine.GSO.4.03.9909221100070.7703-110000@idrp.merit.edu>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="2F2755DE02.938010015/segue.merit.edu"
Content-ID: <Pine.GSO.4.03.9909221100071.7703@idrp.merit.edu>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--2F2755DE02.938010015/segue.merit.edu
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.GSO.4.03.9909221100072.7703@idrp.merit.edu>
Content-Description: Notification



---------- Forwarded message ----------
Date: Wed, 22 Sep 1999 10:20:15 -0400 (EDT)
From: Mail Delivery System <MAILER-DAEMON@merit.edu>
To: owner-aaa-bof@merit.edu
Subject: Undelivered Mail Returned to Sender

This is the Postfix program at host segue.merit.edu.

I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.

For further assistance, please contact <postmaster@merit.edu>

If you do so, please include this problem report. You can
delete your own text from the message returned below.

			The Postfix program

<barnabybones@hotmail.com>: host mail8.hotmail.com[216.32.243.135] said: 550
    Requested action not taken: mailbox unavailable

<petrack@vocaltec.com>: host digex.vocaltec.com[207.87.4.238] said: 550
    <petrack@vocaltec.com>... User unknown

<dmitton@baynetworks.com>: host smtp-gw.baynetworks.com[134.177.3.20] said: 550
    <dmitton@baynetworks.com>... User unknown


--2F2755DE02.938010015/segue.merit.edu
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.GSO.4.03.9909221100073.7703@idrp.merit.edu>
Content-Description: Undelivered Message

Received: by segue.merit.edu (Postfix)
	id 2F2755DE02; Wed, 22 Sep 1999 10:12:31 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 087E05DDBA; Wed, 22 Sep 1999 10:12:31 -0400 (EDT)
Received: from balinese.baltimore.ie (pc215-8.indigo.ie [194.125.215.8])
	by segue.merit.edu (Postfix) with ESMTP id 13E515DDED
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 10:12:26 -0400 (EDT)
Received: by balinese.baltimore.ie; id PAA00296; Wed, 22 Sep 1999 15:12:23 +0100 (GMT/IST)
Received: from bobcat.baltimore.ie(192.168.20.10) by balinese.baltimore.ie via smap (V4.2)
	id xma000280; Wed, 22 Sep 99 15:12:19 +0100
Received: from baltimore.ie ([192.168.21.167])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id PAA05345;
	Wed, 22 Sep 1999 15:12:14 +0100
Message-ID: <37E8E47D.31CC2BE5@baltimore.ie>
Date: Wed, 22 Sep 1999 15:15:26 +0100
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Cc: aaa-wg@merit.edu, lgommans@phys.uu.nl,
	xme <stephen.farrell@baltimore.ie>
Subject: Re: Re-chartering wording
References: <v04210101b40e8e3ed91a@[192.87.109.229]>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by bobcat.baltimore.ie id PAA05345
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


Cees,

I completely agree that application layer AAA isn't "fundamentally=20
different" and would suggest given the short/long term issues
involved we invoke the MUST/SHOULD clause. So how about making=20
the following change, from:

> >The working group will incorporate requirements provided by
> >the NASREQ, Mobile IP, and ROAMOPS working groups. Once
> >the requirements documents are completed, the working group
> >may be re-chartered to include work regarding the base protocol.
> >
> >Since application-layer authentication, authorization and
> >accounting presents a fundamentally different set of
> >issues, work in this area is outside the scope of the
> >AAA WG.

...to:

"The working group will incorporate requirements provided by
the NASREQ, Mobile IP, and ROAMOPS working groups. Once
the requirements documents are completed, the working group
may be re-chartered to include work regarding the base protocol

Since application layer authentication, authorization and=20
accounting MAY raise issues which cannot be addressed in
the short term, the WG MUST address the AAA requirements
for the WGs specified in the previous paragraph, but SHOULD=20
also, where possible, address application layer AAA issues."

Regards,
Stephen.


"C. de Laat" wrote:
>=20
> Hi, the mail below bounced to the aaa-wg listserver this night??? Now
> once more.
>=20
> Best regards,
> Cees.
>=20
> Hi,
>=20
> We understand the goals of the charter rework and support the idea to
> focus the work in the short term to get much needed results. However
> we essentially disagree with the statement that application-layer AAA
> is fundamentally different set of issues and that this should be out
> of the scope of the AAA WG.
> These issues may not be fully understood yet but in the long term we
> should start to investigate them. We would like to see less strong
> wording on the
> focus on Internet Access. The application layer paragraph should
> reflect that that work may be outside the short term milestones but
> nevertheless essential to the long term goals of the AAA-WG.
>=20
> Kind regards,
>=20
> Cees de Laat and Leon Gommans
>=20
> >PROPOSED CHARTER
> >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> >The Authentication, Authorization and Accounting working group
> >focuses on development of requirements for Authentication,
> >Authorization and Accounting as applied to Internet Access.
> >
> >The purpose behind this is to create a base protocol
> >applicable to a number of specific Internet access models.
> >These will include Network Access Server AAA, Mobile IP, and
> >roaming. By creating an architecture and set of base
> >protocols, the amount of work to create specific Internet
> >access AAA protocols will be reduced.
> >
> >The working group will incorporate requirements provided by
> >the NASREQ, Mobile IP, and ROAMOPS working groups. Once
> >the requirements documents are completed, the working group
> >may be re-chartered to include work regarding the base protocol.
> >
> >Since application-layer authentication, authorization and
> >accounting presents a fundamentally different set of
> >issues, work in this area is outside the scope of the
> >AAA WG.
> >
> >The immediate goals of the AAA working group are to:
> >
> >- assemble AAA requirements arising from specific Internet access
> >applications: Network Access Server AAA, Mobile IP, and roaming.
> >
> >- document requirements for a base AAA architecture;
> >
> >- identify the relationship and interaction between Policy and
> >Authorization;
> >
> >Goals and Milestones:
> >Sep 99    Submit Mobile IP requirements initial Internet-Draft
> >Sep 99    Submit Accounting Requirements initial Internet-Draft(s)
> >Oct 99    Submit policy/authorization initial Internet-Draft
> >Nov 99    Revision of charter to include statement of work regarding t=
he
> >base
> >          protocols and data formats.
>=20
> _______________________________________________________________________=
__
> dr.ir. C.Th.A.M. de Laat
> Position work: N 52=B005'8.3", E 5=B010'1.9", home: N 52=B002'14.0" E 0=
05=B009'26.7"

--=20
____________________________________________________________
Stephen Farrell         				  =20
Baltimore Technologies,   tel: (direct line) +353 1 647 7406
61 Fitzwilliam Lane,                    fax: +353 1 647 7499
Dublin 2.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


--2F2755DE02.938010015/segue.merit.edu--


From owner-aaa-bof@merit.edu  Wed Sep 22 11:10:32 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA09196
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 11:10:32 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id DCD3E5DDE6; Wed, 22 Sep 1999 11:10:12 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id C2B965DDFF; Wed, 22 Sep 1999 11:10:12 -0400 (EDT)
Received: from idrp.merit.edu (idrp.merit.edu [198.108.60.89])
	by segue.merit.edu (Postfix) with ESMTP
	id 499B65DDE6; Wed, 22 Sep 1999 11:10:11 -0400 (EDT)
Received: (from skh@localhost)
	by idrp.merit.edu (8.9.1a/8.9.1) id LAA08044;
	Wed, 22 Sep 1999 11:10:11 -0400 (EDT)
Date: Wed, 22 Sep 1999 11:10:11 -0400 (EDT)
From: <skh@merit.edu>
Message-Id: <199909221510.LAA08044@idrp.merit.edu>
To: aaa-wg@merit.edu
Subject: Problems with mail for aaa-wg
Cc: dwspence@merit.edu, jrv@merit.edu, skh@merit.edu
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


Hi all:

We lost email from 15:21 EDT 9/21/99 to 6:48 EDT 9/22/99.
We apologize for the inconvience of this in the middle
of this charteing discussion. 

In the process of adding filters trying to protect the
list against some of the spam (we switched over 2 days),
we encountered some mailer problems.  Due to some human 
error (part of it mine), we do not have this lost
email on our archives or in a manner we can quickly
retransmit. 

I have sent the messages we current have at this point.
I would appreciate it if you would resend any post that was sent during
this time.

Again, my apologies for this technical difficulty. 
If you have problems reposting, please send a problem
report to skh@merit.edu and dwspence@merit.edu.  We'll work
with our mail list administrators to make sure your email
comes through.  

Our general Merit number for help is (734)764-9430.
Please ask to leave a message for Dave Spence and Sue Hares or
for the mail list administrator.  


Sue Hares





From owner-aaa-bof@merit.edu  Wed Sep 22 11:18:02 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA09380
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 11:18:02 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id C57AC5DE0B; Wed, 22 Sep 1999 11:17:24 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A97D45DDFF; Wed, 22 Sep 1999 11:17:24 -0400 (EDT)
Received: from idrp.merit.edu (idrp.merit.edu [198.108.60.89])
	by segue.merit.edu (Postfix) with ESMTP
	id 9999F5DDED; Wed, 22 Sep 1999 11:17:23 -0400 (EDT)
Received: from localhost (skh@localhost)
	by idrp.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA08055;
	Wed, 22 Sep 1999 11:17:23 -0400 (EDT)
X-Authentication-Warning: idrp.merit.edu: skh owned process doing -bs
Date: Wed, 22 Sep 1999 11:17:23 -0400 (EDT)
From: Susan Hares <skh@merit.edu>
To: aaa-wg@merit.edu
Cc: paul.krumviede@wcom.com, aboba@internaut.com, C.T.A.M.deLaat@phys.uu.nl
Subject: Forwarding mail lost last night
Message-ID: <Pine.GSO.4.03.9909221114330.7703-100000@idrp.merit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk



paul.krumviede@wcom.comDate: Tue, 21 Sep 1999 15:01:33 -0700
From: Paul Krumviede <paul.krumviede@wcom.com>
Subject: Re: Re-chartering wording
In-reply-to: <v04210106b40da096e2e0@[131.211.36.130]>
Originator-info: login-id=krumviede; server=localhost
To: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>, aboba@internaut.com,
	aaa-wg@merit.edu
Cc: Randy Bush <randy@psg.com>, Bert Wijnen <wijnen@vnet.ibm.com>
Message-id: <1623222842.937926093@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
MIME-version: 1.0
X-Mailer: Mulberry (Win32) [1.4.4, s/n P005-300888-001]
Content-type: text/plain; charset=iso-8859-1
Content-disposition: inline
Content-transfer-encoding: quoted-printable

I'm not sure we (yet?) have any officially accepted long term goals.
Should we interpret this as something that should be considered
as part of the charter revision after we get the initial drafts out?

-paul

--On Tuesday, September 21, 1999, 11:41 PM +0200 "C. de Laat" =
<C.T.A.M.deLaat@phys.uu.nl> wrote:

> Hi,
> 
> We understand the goals of the charter rework and support the idea to 
> focus the work in the short term to get much needed results. However 
> we essentially disagree with the statement that application-layer AAA 
> is fundamentally different set of issues and that this should be out 
> of the scope of the AAA WG.
> These issues may not be fully understood yet but in the long term we 
> should start to investigate them. We would like to see less strong 
> wording on the
> focus on Internet Access. The application layer paragraph should 
> reflect that that work may be outside the short term milestones but 
> nevertheless essential to the long term goals of the AAA-WG.
> 
> Kind regards,
> 
> Cees de Laat and Leon Gommans
> 
>> PROPOSED CHARTER
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> 
>> The Authentication, Authorization and Accounting working group
>> focuses on development of requirements for Authentication,
>> Authorization and Accounting as applied to Internet Access.
>> 
>> The purpose behind this is to create a base protocol
>> applicable to a number of specific Internet access models.
>> These will include Network Access Server AAA, Mobile IP, and
>> roaming. By creating an architecture and set of base
>> protocols, the amount of work to create specific Internet
>> access AAA protocols will be reduced.
>> 
>> The working group will incorporate requirements provided by
>> the NASREQ, Mobile IP, and ROAMOPS working groups. Once
>> the requirements documents are completed, the working group
>> may be re-chartered to include work regarding the base protocol.
>> 
>> Since application-layer authentication, authorization and
>> accounting presents a fundamentally different set of
>> issues, work in this area is outside the scope of the
>> AAA WG.
>> 
>> The immediate goals of the AAA working group are to:
>> 
>> - assemble AAA requirements arising from specific Internet access
>> applications: Network Access Server AAA, Mobile IP, and roaming.
>> 
>> - document requirements for a base AAA architecture;
>> 
>> - identify the relationship and interaction between Policy and
>> Authorization;
>> 
>> Goals and Milestones:
>> Sep 99    Submit Mobile IP requirements initial Internet-Draft
>> Sep 99    Submit Accounting Requirements initial Internet-Draft(s)
>> Oct 99    Submit policy/authorization initial Internet-Draft
>> Nov 99    Revision of charter to include statement of work regarding =
the
>> base
>>          protocols and data formats.
> 
> =
_________________________________________________________________________
> dr.ir. C.Th.A.M. de Laat
> Position work: N 52=B005'8.3", E 5=B010'1.9", home: N 52=B002'14.0" E =
005=B009'26.7"






From owner-aaa-bof@merit.edu  Wed Sep 22 11:18:52 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA09392
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 11:18:51 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 2D5C25DE19; Wed, 22 Sep 1999 11:18:01 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 1154F5DE18; Wed, 22 Sep 1999 11:18:01 -0400 (EDT)
Received: from idrp.merit.edu (idrp.merit.edu [198.108.60.89])
	by segue.merit.edu (Postfix) with ESMTP
	id 064205DE17; Wed, 22 Sep 1999 11:18:00 -0400 (EDT)
Received: from localhost (skh@localhost)
	by idrp.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA08059;
	Wed, 22 Sep 1999 11:17:59 -0400 (EDT)
X-Authentication-Warning: idrp.merit.edu: skh owned process doing -bs
Date: Wed, 22 Sep 1999 11:17:59 -0400 (EDT)
From: Susan Hares <skh@merit.edu>
To: aaa-wg@merit.edu
Cc: C.T.A.M.deLaat@phys.uu.nl
Message-ID: <Pine.GSO.4.03.9909221117331.7703-100000@idrp.merit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk



---------- Forwarded message ----------
Date: Tue, 21 Sep 1999 18:20:45 -0400 (EDT)
From: owner-aaa-bof@merit.edu
To: owner-aaa-bof@merit.edu

>From owner-aaa-wg@merit.edu  Tue Sep 21 18:20:44 1999
Return-Path: <owner-aaa-wg@merit.edu>
Delivered-To: aaa-wg@merit.edu
Received: from max.phys.uu.nl (max.phys.uu.nl [131.211.32.73])
	by segue.merit.edu (Postfix) with ESMTP
	id 783315DDA4; Tue, 21 Sep 1999 18:20:43 -0400 (EDT)
Received: from [131.211.36.130] (hst36130.phys.uu.nl [131.211.36.130])
	by max.phys.uu.nl (8.9.3/8.9.3/hjm) with ESMTP id AAA19099;
	Wed, 22 Sep 1999 00:19:20 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: delaat@mail.phys.uu.nl
Message-Id: <v0421010ab40db3ce6b11@[131.211.36.130]>
In-Reply-To: 
 <1623222842.937926093@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
References: 
 <1623222842.937926093@adsl-63-193-107-75.dsl.snfc21.pacbell.net>
Date: Wed, 22 Sep 1999 00:18:57 +0200
To: Paul Krumviede <paul.krumviede@wcom.com>,
	"C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>, aboba@internaut.com,
	aaa-wg@merit.edu
From: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Subject: Re: Re-chartering wording
Cc: Randy Bush <randy@psg.com>, Bert Wijnen <wijnen@vnet.ibm.com>,
	"John R. Vollbrecht" <jrv@merit.edu>, L.H.M.Gommans@phys.uu.nl
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable

At 15:01 -0700 21/9/99, Paul Krumviede wrote:
>I'm not sure we (yet?) have any officially accepted long term goals.
>Should we interpret this as something that should be considered
>as part of the charter revision after we get the initial drafts out?

I don't think so. The current charter has parts which really send the=20
wrong message. So the feeling of a large part of the authorization=20
group is to have this re-worded now.

Best regards,
Cees.


>-paul
>
>--On Tuesday, September 21, 1999, 11:41 PM +0200 "C. de Laat"=20
><C.T.A.M.deLaat@phys.uu.nl> wrote:
>
> > Hi,
> >
> > We understand the goals of the charter rework and support the idea to
> > focus the work in the short term to get much needed results. However
> > we essentially disagree with the statement that application-layer AAA
> > is fundamentally different set of issues and that this should be out
> > of the scope of the AAA WG.
> > These issues may not be fully understood yet but in the long term we
> > should start to investigate them. We would like to see less strong
> > wording on the
> > focus on Internet Access. The application layer paragraph should
> > reflect that that work may be outside the short term milestones but
> > nevertheless essential to the long term goals of the AAA-WG.
> >
> > Kind regards,
> >
> > Cees de Laat and Leon Gommans
> >
> >> PROPOSED CHARTER
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>
> >> The Authentication, Authorization and Accounting working group
> >> focuses on development of requirements for Authentication,
> >> Authorization and Accounting as applied to Internet Access.
> >>
> >> The purpose behind this is to create a base protocol
> >> applicable to a number of specific Internet access models.
> >> These will include Network Access Server AAA, Mobile IP, and
> >> roaming. By creating an architecture and set of base
> >> protocols, the amount of work to create specific Internet
> >> access AAA protocols will be reduced.
> >>
> >> The working group will incorporate requirements provided by
> >> the NASREQ, Mobile IP, and ROAMOPS working groups. Once
> >> the requirements documents are completed, the working group
> >> may be re-chartered to include work regarding the base protocol.
> >>
> >> Since application-layer authentication, authorization and
> >> accounting presents a fundamentally different set of
> >> issues, work in this area is outside the scope of the
> >> AAA WG.
> >>
> >> The immediate goals of the AAA working group are to:
> >>
> >> - assemble AAA requirements arising from specific Internet access
> >> applications: Network Access Server AAA, Mobile IP, and roaming.
> >>
> >> - document requirements for a base AAA architecture;
> >>
> >> - identify the relationship and interaction between Policy and
> >> Authorization;
> >>
> >> Goals and Milestones:
> >> Sep 99    Submit Mobile IP requirements initial Internet-Draft
> >> Sep 99    Submit Accounting Requirements initial Internet-Draft(s)
> >> Oct 99    Submit policy/authorization initial Internet-Draft
> >> Nov 99    Revision of charter to include statement of work regarding th=
e
> >> base
> >>          protocols and data formats.
> >
> > ________________________________________________________________________=
_
> > dr.ir. C.Th.A.M. de Laat
> > Position work: N 52=B005'8.3", E 5=B010'1.9", home: N 52=B002'14.0" E=20
>005=B009'26.7"

_________________________________________________________________________
dr.ir. C.Th.A.M. de Laat
Position work: N 52=B005'8.3", E 5=B010'1.9", home: N 52=B002'14.0" E 005=B0=
09'26.7"




From owner-aaa-bof@merit.edu  Wed Sep 22 11:34:42 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA09714
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 11:34:42 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 3D8735DDAF; Wed, 22 Sep 1999 11:34:25 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 22BF95DDED; Wed, 22 Sep 1999 11:34:25 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 3F1B55DDAF
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 11:34:24 -0400 (EDT)
Received: from home.merit.edu (localhost [127.0.0.1]) by home.merit.edu (8.8.8/merit-2.0) with ESMTP id LAA15716 for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 11:34:24 -0400 (EDT)
Message-Id: <199909221534.LAA15716@home.merit.edu>
X-Mailer: exmh version 2.0zeta 7/24/97
To: aaa-wg@merit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 22 Sep 1999 11:34:23 -0400
From: "John R. Vollbrecht" <jrv@merit.edu>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

forwarding what mayhave been lost -- John

------- Forwarded Message

Return-Path: jrv@home.merit.edu
Received: from home.merit.edu (localhost [127.0.0.1]) by home.merit.edu 
(8.8.8/merit-2.0) with ESMTP id TAA04772; Tue, 21 Sep 1999 19:32:46 -0400 (EDT)
Message-Id: <199909212332.TAA04772@home.merit.edu>
To: aboba@internaut.com, paul.krumviede@wcom.com
cc: "'aaa wg'" <aaa-wg@merit.edu>, jrv@home.merit.edu
Subject: Re: Re-chartering discussion 
In-reply-to: Your message of "Fri, 17 Sep 1999 13:14:46 PDT."
             <002b01bf0149$4a8a9620$448939cc@vaio> 
Date: Tue, 21 Sep 1999 19:32:45 -0400
From: "John R. Vollbrecht" <jrv@home.merit.edu>


I think it is reasonable to try to push to get a protocol for roaming,
mobileIP, and NASREQ quickly.  These have a clear immediate need.  In
the Authorization  subgroup we have suggested that it might be wise to 
work on an "intermediate" protocol in parallel with working on requirements 
for a more inclusive protocol in the long term. We were told that this
was out of scope, so it was not pursued.  In many ways the proposed
charter seems to be pushing to create the "intermediate" protocol and
ignores the possibility of a more inclusive protocol.

I don't agree, however, that the requirements for Internet Access are
fundamentally different than other AAA requirements, only that the pressure
for a protocol to support them is greater.

I suggest the following changes to the draft charter

change the paragraph 

>Since application-layer authentication, authorization and$
>accounting presents a fundamentally different set of$
>issues, work in this area is outside the scope of the$
>AAA WG.$

to say 

*Satisfying application-layer requirements is outside the scope of this
*working group.  Once the AAA requirements for the initial set of protocols
*is complete, the working group may be rechartered to include global
*AAA requirements similar to what was described in the initial charter.

- -------

In addition to the charter change, I am quite curious about how you plan
to attack this.  In reality, I don't see how limiting it to
Internet Access will significantly reduce the effort required.  Anything
which includes documenting a base architecture will be contentious.  What might
be more likely to reduce the time would be to suggest that the group be
required to evaluate existing protocols that might be extended rather
than try to come up with a new "architecture".   


- -- John

In message <002b01bf0149$4a8a9620$448939cc@vaio>, "Bernard Aboba" writes:
>Some background
>===============
>
>PROPOSED CHARTER
>================
>
>The Authentication, Authorization and Accounting working group
>focuses on development of requirements for Authentication,
>Authorization and Accounting as applied to Internet Access.
>
>The purpose behind this is to create a base protocol
>applicable to a number of specific Internet access models.
>These will include Network Access Server AAA, Mobile IP, and
>roaming. By creating an architecture and set of base
>protocols, the amount of work to create specific Internet
>access AAA protocols will be reduced.
>
>The working group will incorporate requirements provided by
>the NASREQ, Mobile IP, and ROAMOPS working groups. Once
>the requirements documents are completed, the working group
>may be re-chartered to include work regarding the base protocol.
>
>Since application-layer authentication, authorization and
>accounting presents a fundamentally different set of
>issues, work in this area is outside the scope of the
>AAA WG.
>
>The immediate goals of the AAA working group are to:
>
>- assemble AAA requirements arising from specific Internet access
>applications: Network Access Server AAA, Mobile IP, and roaming.
>
>- document requirements for a base AAA architecture;
>
>- identify the relationship and interaction between Policy and
>Authorization;
>
>Goals and Milestones:
>Sep 99    Submit Mobile IP requirements initial Internet-Draft
>Sep 99    Submit Accounting Requirements initial Internet-Draft(s)
>Oct 99    Submit policy/authorization initial Internet-Draft
>Nov 99    Revision of charter to include statement of work regarding the
>base
>          protocols and data formats.
>
>Internet-Drafts:
>Requirements for Internet-Scale Accounting Management (34150 bytes)
>Introduction to Accounting Management (74305 bytes)
>Accounting Attributes and Record Formats,
><draft-brownlee-accounting-attributes-00.txt>
>AAA Authorization Architecture and Requirements (159682 bytes)
>Mobile IP Authentication, Authorization, and Accounting Requirements (52670
>bytes)
>
>Requirements documents incorporated by reference:
>
>>From NASREQ:
>Criteria for Evaluating Network Access Server Protocols (27062 bytes)
>Network Access Server Requirements Next Generation (NASREQNG) NAS Model
>(42672 bytes)
>Network Access Servers Requirements: Extended RADIUS Practices (27010 bytes)
>
>>From ROAMOPS:
>Criteria for Evaluating Roaming Protocols (RFC 2477) (23530 bytes)
>
>
>
>
>
>

------- End of Forwarded Message





From owner-aaa-bof@merit.edu  Wed Sep 22 17:00:25 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA16495
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 17:00:25 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 183395DDCA; Wed, 22 Sep 1999 16:59:54 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id EB3A35DDC8; Wed, 22 Sep 1999 16:59:53 -0400 (EDT)
Received: from omzrelay03.mcit.com (omzrelay03.mcit.com [199.249.19.245])
	by segue.merit.edu (Postfix) with ESMTP id 89C245DDC1
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 16:59:52 -0400 (EDT)
Received: from ndcrelay2.mcit.com ([166.37.172.6])
 by firewall.mcit.com (PMDF V5.2-32 #38418)
 with ESMTP id <0FIH00D34BMMN4@firewall.mcit.com> for aaa-wg@merit.edu; Wed,
 22 Sep 1999 20:59:11 +0000 (GMT)
Received: from omzmta02.mcit.com (omzmta02.mcit.com [166.37.194.120])
 by ndcrelay2.mcit.com (8.8.7/) with ESMTP	id UAA32703; Wed,
 22 Sep 1999 20:54:48 +0000 (GMT)
Received: from C25776A ([166.35.151.22])
 by omzmta02.mcit.com (InterMail v03.02.05 118 120)
 with SMTP id <19990922205909.NASK28646@[166.35.151.22]>; Wed,
 22 Sep 1999 20:59:09 +0000
Date: Wed, 22 Sep 1999 15:59:09 -0500
From: Henry Sinnreich <henry.sinnreich@wcom.com>
Subject: RE: Re-chartering wording
In-reply-to: <v04210101b40e8e3ed91a@[192.87.109.229]>
To: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>, aaa-wg@merit.edu
Cc: lgommans@phys.uu.nl
Message-id: <NBBBIIJFOKPMFOOILMBKCENNEJAA.henry.sinnreich@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

>The application layer paragraph should
> reflect that that work may be outside the short term milestones but
> nevertheless essential to the long term goals of the AAA-WG.

Agree. The present charter is focused on access only, and thus too narrow.
None of the Internet services is taken care of, and sorry to repeat, have to
be given a chance, until and if other AAA WGs will have to chartered. All
AAA's are for example pertinent for telephony, but are not dealt with at all
in the proposed charter.

Henry

> -----Original Message-----
> From: owner-aaa-bof@merit.edu [mailto:owner-aaa-bof@merit.edu]On Behalf
> Of C. de Laat
> Sent: Wednesday, September 22, 1999 8:48 AM
> To: aaa-wg@merit.edu
> Cc: lgommans@phys.uu.nl
> Subject: Re-chartering wording
>
>
> Hi, the mail below bounced to the aaa-wg listserver this night??? Now
> once more.
>
> Best regards,
> Cees.
>
>
> Hi,
>
> We understand the goals of the charter rework and support the idea to
> focus the work in the short term to get much needed results. However
> we essentially disagree with the statement that application-layer AAA
> is fundamentally different set of issues and that this should be out
> of the scope of the AAA WG.
> These issues may not be fully understood yet but in the long term we
> should start to investigate them. We would like to see less strong
> wording on the
> focus on Internet Access. The application layer paragraph should
> reflect that that work may be outside the short term milestones but
> nevertheless essential to the long term goals of the AAA-WG.
>
> Kind regards,
>
> Cees de Laat and Leon Gommans
>
> >PROPOSED CHARTER
> >================
> >
> >The Authentication, Authorization and Accounting working group
> >focuses on development of requirements for Authentication,
> >Authorization and Accounting as applied to Internet Access.
> >
> >The purpose behind this is to create a base protocol
> >applicable to a number of specific Internet access models.
> >These will include Network Access Server AAA, Mobile IP, and
> >roaming. By creating an architecture and set of base
> >protocols, the amount of work to create specific Internet
> >access AAA protocols will be reduced.
> >
> >The working group will incorporate requirements provided by
> >the NASREQ, Mobile IP, and ROAMOPS working groups. Once
> >the requirements documents are completed, the working group
> >may be re-chartered to include work regarding the base protocol.
> >
> >Since application-layer authentication, authorization and
> >accounting presents a fundamentally different set of
> >issues, work in this area is outside the scope of the
> >AAA WG.
> >
> >The immediate goals of the AAA working group are to:
> >
> >- assemble AAA requirements arising from specific Internet access
> >applications: Network Access Server AAA, Mobile IP, and roaming.
> >
> >- document requirements for a base AAA architecture;
> >
> >- identify the relationship and interaction between Policy and
> >Authorization;
> >
> >Goals and Milestones:
> >Sep 99    Submit Mobile IP requirements initial Internet-Draft
> >Sep 99    Submit Accounting Requirements initial Internet-Draft(s)
> >Oct 99    Submit policy/authorization initial Internet-Draft
> >Nov 99    Revision of charter to include statement of work regarding the
> >base
> >          protocols and data formats.
>
> _________________________________________________________________________
> dr.ir. C.Th.A.M. de Laat
> Position work: N 52°05'8.3", E 5°10'1.9", home: N 52°02'14.0" E
> 005°09'26.7"
>



From owner-aaa-bof@merit.edu  Wed Sep 22 23:08:35 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id XAA21238
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 23:08:35 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id E00AB5DFE6; Wed, 22 Sep 1999 23:08:17 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id BC3D65DEC0; Wed, 22 Sep 1999 23:08:17 -0400 (EDT)
Received: from smtpgw02.wanmail.net (smtpgw02.wanmail.net [209.154.194.61])
	by segue.merit.edu (Postfix) with ESMTP id 84B6C5DFE6
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 23:08:16 -0400 (EDT)
Received: from wcomexch1.wcom.net (wcomexch1.wcom.net [209.154.236.12])
	by smtpgw02.wanmail.net (8.9.1/8.9.1) with ESMTP id XAA01000;
	Wed, 22 Sep 1999 23:04:32 -0400 (EDT)
Received: by wcomexch1.wcom.net with Internet Mail Service (5.5.2448.0)
	id <SAX884KH>; Wed, 22 Sep 1999 23:03:48 -0400
Message-ID: <9A74C89D6696D2118E500008C7BA7C560C03B111@wcomexch1.wcom.net>
From: "Beadles, Mark A." <MBeadles@wcom.net>
To: "'Paul Krumviede'" <paul.krumviede@wcom.com>,
        Matt Squire <msquire@nortelnetworks.com>, aboba <aboba@internaut.com>,
        "'aaa wg'" <aaa-wg@merit.edu>
Subject: RE: Re-chartering discussion
Date: Wed, 22 Sep 1999 23:03:48 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

From: Paul Krumviede [mailto:paul.krumviede@wcom.com]:
>> Also, there are a number of consortia/groups that are already working on
>> accounting/billing standard, and splitting accounting off would be a good
>> way to focus these outside efforts in an IETF wg with that single
purpose.   
>> 
>> So by all means let's reduce the scope of the group, but instead of
>> restricting the number of applications we'll look at, lets reduce the
base
>> functionality that's within the scope of the WG.  
>
>As a thought experiment, I see 2 reasons to keep these together.
>- we may want some form of correlation tag to allow one to associate
>all the relevant authentication and authorization decisions and the
>subsequent accounting (if any);

Yes!  One may want to account differently for users who have used different
types of authentication.  Same for authorization.  At a minimum you MUST be
able to correlate accounting with authentication and authorization, and very
likely you want to actually include AA information in the accounting stream.


>- there may be services or inter-domain cases where authorization
>is conditional on accounting capabilities (off-hand, I'm thinking of
>some fraud detection capabilities here).

Fraud detection is certainly one motivator for that capability.  Also, if a
network operator is using accounting for tracking of business agreements [I
am avoiding the B-ll--g word], then the operator may also require that
authorization be conditional on certain accounting capabilities being
present.

It would be possible to do this with two distinct protocols.  But in that
case we need to very explicitly describe their relationship.  Also, as new
capabilities are added to one protocol, we would have to do the equivalent
for the other protocol.  

+ Mark Anthony Beadles +  UUNET Product Development  + 
+  mbeadles@wcom.net   + http://networking.us.uu.net +
+  Voice 614.723.1941  +       Fax 614.723.8407      +



From owner-aaa-bof@merit.edu  Wed Sep 22 23:12:50 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id XAA21301
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 23:12:50 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 36D8C5DEC0; Wed, 22 Sep 1999 23:12:33 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 19C805E00B; Wed, 22 Sep 1999 23:12:33 -0400 (EDT)
Received: from smtpgw02.wanmail.net (smtpgw02.wanmail.net [209.154.194.61])
	by segue.merit.edu (Postfix) with ESMTP id E61F35DEC0
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 23:12:31 -0400 (EDT)
Received: from wcomexch1.wcom.net (wcomexch1.wcom.net [209.154.236.12])
	by smtpgw02.wanmail.net (8.9.1/8.9.1) with ESMTP id XAA01152;
	Wed, 22 Sep 1999 23:12:30 -0400 (EDT)
Received: by wcomexch1.wcom.net with Internet Mail Service (5.5.2448.0)
	id <SAX884MD>; Wed, 22 Sep 1999 23:11:46 -0400
Message-ID: <9A74C89D6696D2118E500008C7BA7C560C03B114@wcomexch1.wcom.net>
From: "Beadles, Mark A." <MBeadles@wcom.net>
To: "'Paul Krumviede'" <paul.krumviede@wcom.com>,
        "'aaa-wg@merit.edu'" <aaa-wg@merit.edu>,
        "'Nasreqng List (E-mail)'" <nasreq@tdmx.rutgers.edu>
Subject: RE: Re-chartering discussion
Date: Wed, 22 Sep 1999 23:11:45 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

From: Paul Krumviede [mailto:paul.krumviede@wcom.com]:
>Do the current NASreq outputs encapsulate the VoIP requirements?

No, not all of them.  Certainly I am willing to accept input from a VoIP
subject matter expert in the NASREQ Criteria document.  I would LOVE to see
from text from somebody on more complete VoIP requirements for NAS'es.

+ Mark Anthony Beadles +  UUNET Product Development  + 
+  mbeadles@wcom.net   + http://networking.us.uu.net +
+  Voice 614.723.1941  +       Fax 614.723.8407      +


From owner-aaa-bof@merit.edu  Wed Sep 22 23:16:59 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id XAA21340
	for <aaa-wg-archive@nic.merit.edu>; Wed, 22 Sep 1999 23:16:58 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id CDF505DDD0; Wed, 22 Sep 1999 23:15:57 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 9C9A75DE14; Wed, 22 Sep 1999 23:15:57 -0400 (EDT)
Received: from smtpgw02.wanmail.net (smtpgw02.wanmail.net [209.154.194.61])
	by segue.merit.edu (Postfix) with ESMTP id 7F4015DDD0
	for <aaa-wg@merit.edu>; Wed, 22 Sep 1999 23:15:56 -0400 (EDT)
Received: from wcomexch1.wcom.net (wcomexch1.wcom.net [209.154.236.12])
	by smtpgw02.wanmail.net (8.9.1/8.9.1) with ESMTP id XAA01145;
	Wed, 22 Sep 1999 23:12:12 -0400 (EDT)
Received: by wcomexch1.wcom.net with Internet Mail Service (5.5.2448.0)
	id <SAX884MA>; Wed, 22 Sep 1999 23:11:28 -0400
Message-ID: <9A74C89D6696D2118E500008C7BA7C560C03B113@wcomexch1.wcom.net>
From: "Beadles, Mark A." <MBeadles@wcom.net>
To: "'Paul Krumviede'" <paul.krumviede@wcom.com>,
        "'Matt Squire'" <msquire@nortelnetworks.com>,
        "'aboba'" <aboba@internaut.com>, "'aaa wg'" <aaa-wg@merit.edu>
Subject: RE: Re-chartering discussion
Date: Wed, 22 Sep 1999 23:11:28 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

From: Paul Krumviede [mailto:paul.krumviede@wcom.com]:

>Very true, although I think there may be another dimension driving some
>of these issues: much of the original work seemed to assume a single
>administrative domain (look at naming as done by most ISPs and in
>early roaming implementations). Extending any of the A's to a more
>complex world may introduce similar complications (diffserv isn't
>even going there).

One of the fundamental reasons, IMHO, that we are doing any of this AAA work
at all is that there currently is no good solution for the cross-domain
case.   

Assuming a single administrative domain is no longer a realistic assumption
in today's Internet.    An end user may traverse a whole series of domains
in order to get service. Think of the not very complex situations where an
end user traverses a POTS network, gets backhauled across a frame relay
network, dumped onto  the internet, tunneled to a gateway, then travels a
corporate LAN to an application - every one of those steps may need AAA, and
every one of those networks may be operated by a different administrative
entity.  

The rise of the service provider has guaranteed that there will never again
be a single administrative domain.

+ Mark Anthony Beadles +  UUNET Product Development  + 
+  mbeadles@wcom.net   + http://networking.us.uu.net +
+  Voice 614.723.1941  +       Fax 614.723.8407      +




From owner-aaa-bof@merit.edu  Thu Sep 23 08:07:49 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id IAA28178
	for <aaa-wg-archive@nic.merit.edu>; Thu, 23 Sep 1999 08:07:48 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 9D62C5DDB7; Thu, 23 Sep 1999 08:07:29 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 7F0E15DDB8; Thu, 23 Sep 1999 08:07:29 -0400 (EDT)
Received: from omzrelay03.mcit.com (omzrelay03.mcit.com [199.249.19.245])
	by segue.merit.edu (Postfix) with ESMTP id ED6CF5DDB7
	for <aaa-wg@merit.edu>; Thu, 23 Sep 1999 08:07:27 -0400 (EDT)
Received: from ndcrelay2.mcit.com ([166.37.172.6])
 by firewall.mcit.com (PMDF V5.2-32 #38418)
 with ESMTP id <0FII0089CHM6WG@firewall.mcit.com> for aaa-wg@merit.edu; Thu,
 23 Sep 1999 12:06:06 +0000 (GMT)
Received: from omzmta02.mcit.com (omzmta02.mcit.com [166.37.194.120])
 by ndcrelay2.mcit.com (8.8.7/) with ESMTP	id MAA19973; Thu,
 23 Sep 1999 12:01:43 +0000 (GMT)
Received: from C25776A ([166.37.187.236])
 by omzmta02.mcit.com (InterMail v03.02.05 118 120)
 with SMTP id <19990923120605.QWKB28646@[166.37.187.236]>; Thu,
 23 Sep 1999 12:06:05 +0000
Date: Thu, 23 Sep 1999 07:06:04 -0500
From: Henry Sinnreich <henry.sinnreich@wcom.com>
Subject: RE: Re-chartering discussion
In-reply-to: <9A74C89D6696D2118E500008C7BA7C560C03B113@wcomexch1.wcom.net>
To: "Beadles, Mark A." <MBeadles@wcom.net>,
        "'Paul Krumviede'" <paul.krumviede@wcom.com>,
        "'Matt Squire'" <msquire@nortelnetworks.com>,
        "'aboba'" <aboba@internaut.com>, "'aaa wg'" <aaa-wg@merit.edu>
Message-id: <NBBBIIJFOKPMFOOILMBKIEOEEJAA.henry.sinnreich@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

We could avoid the dilemma with the charter on hand by naming the WG "AAAA",
stands for "Access only AAA"  :-)

Mark makes here some excellent points: AAA has meaning in a multi-provider
environment that includes ISP's, backbone carriers, clearing houses and
private networks.

Henry

> -----Original Message-----
> From: owner-aaa-bof@merit.edu [mailto:owner-aaa-bof@merit.edu]On Behalf
> Of Beadles, Mark A.
> Sent: Wednesday, September 22, 1999 10:11 PM
> To: 'Paul Krumviede'; 'Matt Squire'; 'aboba'; 'aaa wg'
> Subject: RE: Re-chartering discussion
>
>
> From: Paul Krumviede [mailto:paul.krumviede@wcom.com]:
>
> >Very true, although I think there may be another dimension driving some
> >of these issues: much of the original work seemed to assume a single
> >administrative domain (look at naming as done by most ISPs and in
> >early roaming implementations). Extending any of the A's to a more
> >complex world may introduce similar complications (diffserv isn't
> >even going there).
>
> One of the fundamental reasons, IMHO, that we are doing any of
> this AAA work
> at all is that there currently is no good solution for the cross-domain
> case.
>
> Assuming a single administrative domain is no longer a realistic
> assumption
> in today's Internet.    An end user may traverse a whole series of domains
> in order to get service. Think of the not very complex situations where an
> end user traverses a POTS network, gets backhauled across a frame relay
> network, dumped onto  the internet, tunneled to a gateway, then travels a
> corporate LAN to an application - every one of those steps may
> need AAA, and
> every one of those networks may be operated by a different administrative
> entity.
>
> The rise of the service provider has guaranteed that there will
> never again
> be a single administrative domain.
>
> + Mark Anthony Beadles +  UUNET Product Development  +
> +  mbeadles@wcom.net   + http://networking.us.uu.net +
> +  Voice 614.723.1941  +       Fax 614.723.8407      +
>
>
>



From owner-aaa-bof@merit.edu  Fri Sep 24 11:17:21 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA23579
	for <aaa-wg-archive@nic.merit.edu>; Fri, 24 Sep 1999 11:17:21 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0D0975DDD4; Fri, 24 Sep 1999 11:16:47 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E00E55DDE5; Fri, 24 Sep 1999 11:16:46 -0400 (EDT)
Received: from max.phys.uu.nl (max.phys.uu.nl [131.211.32.73])
	by segue.merit.edu (Postfix) with ESMTP id 72BDD5DDD4
	for <aaa-wg@merit.edu>; Fri, 24 Sep 1999 11:16:45 -0400 (EDT)
Received: from [131.211.36.130] (hst36130.phys.uu.nl [131.211.36.130])
	by max.phys.uu.nl (8.9.3/8.9.3/hjm) with ESMTP id RAA03629
	for <aaa-wg@merit.edu>; Fri, 24 Sep 1999 17:16:44 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: delaat@mail.phys.uu.nl (Unverified)
Message-Id: <v04210100b411460306b6@[131.211.36.130]>
Date: Fri, 24 Sep 1999 17:16:26 +0200
To: aaa-wg@merit.edu
From: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Subject: generic AAA model framework
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by nic.merit.edu id LAA23579

Please find a late contribution to the discussion in 15 minutes on 
the phone :-)

best regards,
Cees.


Generic AAA server and its setup and management requirements.

For the long term we envision a generic AAA server which is capable 
of handling authorization requests. Such a generic AAA server would 
typiccally be interfaced to a service and have some form of a 
database containing rules for authorization and another containing 
time-stamped transaction logs. The aaa server would than be able to 
handle AAA requests by inspecting the contents and choose one of the 
following 3 possibillitys for each of the components of the request:
a) let the component be evaluated by the attached service
b) query the transaction log database for the answer
c) forward the component(s) to another AAA server for evaluation
In picture xx-1 such a generic server is displayed:

                      +-----------------------+
                      |                       |
      request  ------>| Generic AAA Server    |<------- to another AAA server
       auth    <------| Rule based engine     |------->
                      |                       |
                      |                       |\
                      +-----------------------+ \ +-------------------+
                               |   ^             \| transaction DBase |
                               |   |              +-------------------+
                               |   |              | Policy DBase      |
                               |   |              +-------------------+
                               v   |
                      +-----------------------+
                      |                       |
                      | Service               |
                      |                       |
                      |                       |
                      +-----------------------+

   fig xx-1: Generic AAA building block


The key points of the model above are:
1) The Rule based engine does only know how to evaluate logical 
formula and how to disentangle the complicated AAA requests (rules as 
defined by policy wg).
2) The rule based engine either forwards a part to the service, looks 
up in the DB or forwards to another AAA server.
3) The Generic AAA server has no knowledge whatsoever about the 
service and as such the components to pass are just globs (yellyfish 
you can find on the beach)
4) The components need some inherent addressing scheme similar to 
URL's. In fact this is a naming space problem.

It is clear that by using this generic model it is feasable to device 
a "future compatible" AAA protocol because much of what we do not 
think about now can be encapsulated in the globs. As such this model 
is similar to that of WWW servers. From this model some generic 
requirements arise. For example: suppose a new user is told that 
somewhere on a specific AAA server a certain authorization can be 
obtained. The AAA protocol should then support:
1) a quiry protocol to find out which authorizations can be obtained 
from a specific server
2) what components must be put in an AAA request for a specific authorization
3) the authorization request itself.

On top of this model another model is needed to handle the setup of 
the rules. Rules in different AAA servers will depend on each other 
and simple things like loops should be avoided.

Observation: this model is recursive. A requester can be just another 
AAA server. So the client server and server server protocol can 
probably be the same.
_________________________________________________________________________
dr.ir. C.Th.A.M. de Laat
Position work: N 52°05'8.3", E 5°10'1.9", home: N 52°02'14.0" E 005°09'26.7"


From owner-aaa-bof@merit.edu  Fri Sep 24 11:26:19 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA23699
	for <aaa-wg-archive@nic.merit.edu>; Fri, 24 Sep 1999 11:26:19 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 809995DDDE; Fri, 24 Sep 1999 11:26:00 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 621755DDE5; Fri, 24 Sep 1999 11:26:00 -0400 (EDT)
Received: from ctron-dnm.ctron.com (ctron-dnm.cabletron.com [12.25.1.120])
	by segue.merit.edu (Postfix) with ESMTP id 313D05DDDE
	for <aaa-wg@merit.edu>; Fri, 24 Sep 1999 11:25:59 -0400 (EDT)
Received: (from uucp@localhost)
	by ctron-dnm.ctron.com (8.8.7/8.8.7) id LAA27265
	for <aaa-wg@merit.edu>; Fri, 24 Sep 1999 11:27:50 -0400 (EDT)
Received: from roc-mail2.ctron.com(134.141.72.230) by ctron-dnm.ctron.com via smap (4.1)
	id xma027248; Fri, 24 Sep 99 11:26:51 -0400
Received: from new-exc1.ctron.com (NEW-EXC1 [134.141.200.123])
	by roc-mail2.ctron.com (8.8.7/8.8.7) with ESMTP id LAA28319
	for <aaa-wg@merit.edu>; Fri, 24 Sep 1999 11:31:48 -0400 (EDT)
Received: by new-exc1.ctron.com with Internet Mail Service (5.5.2448.0)
	id <SQNZK84C>; Fri, 24 Sep 1999 16:24:08 +0100
Message-ID: <29752A74B6C5D211A4920090273CA3DC9053E7@new-exc1.ctron.com>
From: "Gommans, Leon" <Leon.Gommans@cabletron.com>
To: "'aaa wg'" <aaa-wg@merit.edu>
Subject: Thoughts on including AAA functionality in a 'user' process.
Date: Fri, 24 Sep 1999 16:24:07 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


In our previous model we identified AAA functionality to be present in both
something
we called a 'User Authorization' function/process and 'Service
Authorization' process.

Amongst most likely other people, I have been carrying around the idea
about, what if
we put AAA functions in the User. I believe that there is a clear function
of such AAA
functionality during the registration process when a User wants to obtain
authorization
to obtain a service. Think of it as an electronic registration form which a
service
AAA server could send to a user AAA server. Both user and service (or user
authorization) server 'negotiate' the kind of attributes they need from each
other to
allow access to the service. Many question could already be answered by the
students AAA
server and maybe a few not (like does he have a diving suite if he registers
for this
diving course in Hawai) This would help to avoid that a student has to give
all his credentials over and over again to every Education AAA Server he
goes to and would
also help to avoid denail of service attacks when bogus students want to
service
a million time with the same course.

If this makes sense, I'll try to add a few lines to Stephens' document about
this.

Regards .. Leon.


From owner-aaa-bof@merit.edu  Fri Sep 24 11:57:25 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA24048
	for <aaa-wg-archive@nic.merit.edu>; Fri, 24 Sep 1999 11:57:25 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id E2A655DDF7; Fri, 24 Sep 1999 11:57:02 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id C472D5DDF9; Fri, 24 Sep 1999 11:57:02 -0400 (EDT)
Received: from ihemlsrv.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by segue.merit.edu (Postfix) with ESMTP id 399F45DDF7
	for <aaa-wg@merit.edu>; Fri, 24 Sep 1999 11:57:01 -0400 (EDT)
Received: from ihemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id LAA22028
	for <aaa-wg@merit.edu>; Fri, 24 Sep 1999 11:57:00 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id LAA22006
	for <aaa-wg@merit.edu>; Fri, 24 Sep 1999 11:57:00 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2448.0)
	id <TP1AS5V4>; Fri, 24 Sep 1999 17:56:58 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC03184ED2@nl0006exch003u.nl.lucent.com>
From: "Panken, Frans (Frans)" <frans@lucent.com>
To: aaa-wg@merit.edu, "'C. de Laat'" <C.T.A.M.deLaat@phys.uu.nl>
Subject: RE: generic AAA model framework
Date: Fri, 24 Sep 1999 17:56:54 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Cees,

Interesting framework!
This framework describes the retailer concept, as identified by TINA-C (see
Ret reference point of TINA: www.tinac.com) and adopted to a certain extend
by the ITU-T. A similar approach as you described in your e-mail can be
found in the Parlay framework (www.Parlay.org). Your proposal also reflects
perfectly the work we are working on in the TSAS group of OMG, trying to
conferge Parlay and TINA-C interfaces and other efforts to a general
framework for unified access to information and telecom services.
This framework is defined in OMG IDL, exploiting the recent maturity of
distributed computing environments such as CORBA.

Regards,
Frans Panken, Lucent Technologies, Huizen, the Netherlands.

> ----------
> From: 	C. de Laat[SMTP:C.T.A.M.deLaat@phys.uu.nl]
> Sent: 	Friday, September 24, 1999 5:16 PM
> To: 	aaa-wg@merit.edu
> Subject: 	generic AAA model framework
> 
> Please find a late contribution to the discussion in 15 minutes on 
> the phone :-)
> 
> best regards,
> Cees.
> 
> 
> Generic AAA server and its setup and management requirements.
> 
> For the long term we envision a generic AAA server which is capable 
> of handling authorization requests. Such a generic AAA server would 
> typiccally be interfaced to a service and have some form of a 
> database containing rules for authorization and another containing 
> time-stamped transaction logs. The aaa server would than be able to 
> handle AAA requests by inspecting the contents and choose one of the 
> following 3 possibillitys for each of the components of the request:
> a) let the component be evaluated by the attached service
> b) query the transaction log database for the answer
> c) forward the component(s) to another AAA server for evaluation
> In picture xx-1 such a generic server is displayed:
> 
>                       +-----------------------+
>                       |                       |
>       request  ------>| Generic AAA Server    |<------- to another AAA
> server
>        auth    <------| Rule based engine     |------->
>                       |                       |
>                       |                       |\
>                       +-----------------------+ \ +-------------------+
>                                |   ^             \| transaction DBase |
>                                |   |              +-------------------+
>                                |   |              | Policy DBase      |
>                                |   |              +-------------------+
>                                v   |
>                       +-----------------------+
>                       |                       |
>                       | Service               |
>                       |                       |
>                       |                       |
>                       +-----------------------+
> 
>    fig xx-1: Generic AAA building block
> 
> 
> The key points of the model above are:
> 1) The Rule based engine does only know how to evaluate logical 
> formula and how to disentangle the complicated AAA requests (rules as 
> defined by policy wg).
> 2) The rule based engine either forwards a part to the service, looks 
> up in the DB or forwards to another AAA server.
> 3) The Generic AAA server has no knowledge whatsoever about the 
> service and as such the components to pass are just globs (yellyfish 
> you can find on the beach)
> 4) The components need some inherent addressing scheme similar to 
> URL's. In fact this is a naming space problem.
> 
> It is clear that by using this generic model it is feasable to device 
> a "future compatible" AAA protocol because much of what we do not 
> think about now can be encapsulated in the globs. As such this model 
> is similar to that of WWW servers. From this model some generic 
> requirements arise. For example: suppose a new user is told that 
> somewhere on a specific AAA server a certain authorization can be 
> obtained. The AAA protocol should then support:
> 1) a quiry protocol to find out which authorizations can be obtained 
> from a specific server
> 2) what components must be put in an AAA request for a specific
> authorization
> 3) the authorization request itself.
> 
> On top of this model another model is needed to handle the setup of 
> the rules. Rules in different AAA servers will depend on each other 
> and simple things like loops should be avoided.
> 
> Observation: this model is recursive. A requester can be just another 
> AAA server. So the client server and server server protocol can 
> probably be the same.
> _________________________________________________________________________
> dr.ir. C.Th.A.M. de Laat
> Position work: N 52°05'8.3", E 5°10'1.9", home: N 52°02'14.0" E
> 005°09'26.7"
> 


From owner-aaa-bof@merit.edu  Fri Sep 24 17:08:33 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA28537
	for <aaa-wg-archive@nic.merit.edu>; Fri, 24 Sep 1999 17:08:33 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 680435DE75; Fri, 24 Sep 1999 17:07:39 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 4C0F15DE8D; Fri, 24 Sep 1999 17:07:39 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 11DBA5DE75
	for <AAA-WG@Merit.edu>; Fri, 24 Sep 1999 17:07:38 -0400 (EDT)
Received: from Merit.edu (dwspencepc.merit.edu [198.108.62.224]) by home.merit.edu (8.8.8/merit-2.0) with ESMTP id RAA09147 for <AAA-WG@Merit.edu>; Fri, 24 Sep 1999 17:07:37 -0400 (EDT)
Message-ID: <37EBE819.E86356EC@Merit.edu>
Date: Fri, 24 Sep 1999 17:07:37 -0400
From: "David W. Spence" <DWSpence@merit.edu>
Organization: Merit Network, Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: AAA WG <AAA-WG@merit.edu>
Subject: September 24 Meeting of Authorization Subgroup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

       The Authorization Subgroup of the AAA WG met on Friday Sept. 24,
       1999, via telephone conference.  The meeting began at 15:30 UTC.

       The following people participated in the call:

          Pat Calhoun
          Leon Gommans
          Cees de Laat
          George Gross
          Stephen Farrell
          John Vollbrecht
          David Spence

       1. Stephen Farrell's Contribution on Base Requirements

          We continued discussing Stephen Farrell's contribution on base
          requirements.  We discussed requirements 1-10 in some detail.

       2. Protocol Layering and Message Content

          We discussed architectural issues raised in George Gross'
          contribution, "Authentication, Authorization, and Accounting
          Protocol Stack" along with John Vollbrecht's contribution on
          message content.

       3. Next Meetings

          To make up for time lost during the rechartering discussions,
          we will meet three times next week as follows:

          Sept. 27 at 15:30 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
          Sept. 29 at 15:30 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
          Oct.   1 at 15:30 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)

       8. Adjournment

          The meeting adjourned at 17:03 UTC.

-- 
David W. Spence                                email: DWSpence@Merit.edu
Senior Systems Research Programmer             phone: (734) 615-2630
Merit Network, Inc.                            fax:   (734) 647-3745
4151 Plymouth Road, Suite C
Ann Arbor MI 48105-2785
U.S.A.


From owner-aaa-bof@merit.edu  Mon Sep 27 13:01:18 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id NAA22332
	for <aaa-wg-archive@nic.merit.edu>; Mon, 27 Sep 1999 13:01:18 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 7546C5DDF3; Mon, 27 Sep 1999 13:01:03 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 451415DDA8; Mon, 27 Sep 1999 13:01:03 -0400 (EDT)
Received: from max.phys.uu.nl (max.phys.uu.nl [131.211.32.73])
	by segue.merit.edu (Postfix) with ESMTP id 9EF4E5DDF3
	for <aaa-wg@merit.edu>; Mon, 27 Sep 1999 13:01:01 -0400 (EDT)
Received: from [131.211.36.130] (hst36130.phys.uu.nl [131.211.36.130])
	by max.phys.uu.nl (8.9.3/8.9.3/hjm) with ESMTP id TAA09242
	for <aaa-wg@merit.edu>; Mon, 27 Sep 1999 19:00:55 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: delaat@mail.phys.uu.nl
Message-Id: <v04210100b4155333561a@[131.211.36.130]>
Date: Mon, 27 Sep 1999 19:00:56 +0200
To: aaa-wg@merit.edu
From: "C. de Laat" <C.T.A.M.deLaat@phys.uu.nl>
Subject: link to generic model stuf
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by nic.merit.edu id NAA22332

link to generic model sheets and info:

http://www.phys.uu.nl/~wwwfi/aaa/home.html

Best regards,
Cees.
_________________________________________________________________________
dr.ir. C.Th.A.M. de Laat
Position work: N 52°05'8.3", E 5°10'1.9", home: N 52°02'14.0" E 005°09'26.7"


From owner-aaa-bof@merit.edu  Mon Sep 27 17:13:46 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id RAA25864
	for <aaa-wg-archive@nic.merit.edu>; Mon, 27 Sep 1999 17:13:46 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 74B5E5DDB1; Mon, 27 Sep 1999 17:13:26 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 5AD675DDB4; Mon, 27 Sep 1999 17:13:26 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 47A005DDB1
	for <AAA-WG@Merit.edu>; Mon, 27 Sep 1999 17:13:25 -0400 (EDT)
Received: from Merit.edu (dwspencepc.merit.edu [198.108.62.224]) by home.merit.edu (8.8.8/merit-2.0) with ESMTP id RAA15674 for <AAA-WG@Merit.edu>; Mon, 27 Sep 1999 17:13:24 -0400 (EDT)
Message-ID: <37EFDDF4.6E07482F@Merit.edu>
Date: Mon, 27 Sep 1999 17:13:24 -0400
From: "David W. Spence" <DWSpence@merit.edu>
Organization: Merit Network, Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: AAA WG <AAA-WG@merit.edu>
Subject: September 27 Meeting of Authorization Subgroup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

      The Authorization Subgroup of the AAA WG met on Monday Sept. 27, 
      1999, via telephone conference.  The meeting began at 15:30 UTC.
      
      The following people participated in the call:
         
         Stas Khirman
         Cees de Laat
         John Vollbrecht
         Gopal Iyengar
         George Gross
         David Spence
         
      1. Document Organization
         
         We opened with a discussion of document organization.
         
         We considered grouping requirements by "layer".
         
         We considered whether the requirements section would be long 
         enough that it should really be released as a standalone 
         document.  D. Spence suggested that it might be helpful to add 
         a brief discussion following each succinctly worded requirement 
         to help people understand what each one means.  This would tend 
         to lengthen the requirements section.  We concluded that it 
         probably makes sense to split into three documents now rather 
         than do it later when it will be more work.
         
         D. Spence will produce the applications document first by 
         detaching the appendix from the authorization draft, wrapping 
         draft boiler plate around it, promoting the headings one level, 
         and including Cees de Laat's "Computer based education and 
         distance learning" application.  The resulting paper will then 
         be emailed for discussion within the authorization subgroup.  
         We discussed whether to release it as soon as possible as an 
         Internet Draft or to hold it and release all three documents 
         together.  We considered that we may want to add references to 
         new concepts we are adding to the architecture section, so 
         perhaps we should not release it to I-D until after we complete 
         the additions to the architecture.
         
      2. Cees de Laat's Slides
         
         Next we discussed the Powerpoint slides attached to Cees de 
         Laat's email of 9/24/99 13:16:41 (UTC+0200) entitled "Re: Some 
         thoughts about globs and heaps".  These slides are available on 
         Cees de Laat's web page:
         
            http://www.phys.uu.nl/~wwwfi/aaa/home.html
         
         See also Cees' related memo "generic AAA model framework" of 
         9/24/99 17:16:26 (UTC+0200).
         
         C. de Laat explained the slides.  They present a model for a 
         generic authorization server with an interface to 
         service-specific applications.
         
         We noted similarities to George Gross' layers.  In particular, 
         C. de Laat's distinction between a "generic authorization 
         server" and a "service" is similar to G. Gross' distinction 
         between the "transaction/session management" layer and the 
         higher "application specific" and "presentation" layers.
         
      3. George Gross' Layering Contribution
         
         We next turned our attention to George Gross' contribution, 
         "AAA protocol stack", of 9/22/99 17:23:32 (UTC-0400).
         
         G. Gross introduced the paper and described his breakdown into 
         more or less independent layers of functionality.  After 
         discussing the layers, he noted that our work is mostly 
         concentrated in his "transaction/session management" layer.
         
      4. Work Assignments
         
         D. Spence will write up some ideas on requirements.
         
         C. de Laat will expand on his work in the area of transferring 
         policy rules among authorization entities.
         
         G. Gross will expand on his work on layers.
         
      5. Next Meetings
         
         The next two phone conferences will take place as follows:
         
         Sept. 29 at 15:30 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         Oct.   1 at 15:30 UTC  (8:30 a.m. PDT, 11:30 a.m. EDT)
         
      6. Adjournment
         
         The meeting adjourned at 17:02 UTC.


-- 
David W. Spence                                email: DWSpence@Merit.edu
Senior Systems Research Programmer             phone: (734) 615-2630
Merit Network, Inc.                            fax:   (734) 647-3745
4151 Plymouth Road, Suite C
Ann Arbor MI 48105-2785
U.S.A.


From owner-aaa-bof@merit.edu  Tue Sep 28 04:40:23 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id EAA05012
	for <aaa-wg-archive@nic.merit.edu>; Tue, 28 Sep 1999 04:40:23 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 6CBCD5DD9F; Tue, 28 Sep 1999 04:39:48 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 41B5C5DDC1; Tue, 28 Sep 1999 04:39:48 -0400 (EDT)
Received: from bdr-osl-25-005.oslo.telenor.no (BDR-OSL-25-005.telenor.no [134.47.108.13])
	by segue.merit.edu (Postfix) with SMTP id 3127E5DD9F
	for <AAA-WG@Merit.edu>; Tue, 28 Sep 1999 04:39:46 -0400 (EDT)
Received: by BDR-OSL-24-201.telenor.no with Internet Mail Service (5.5.2232.9)
	id <TRC37C0H>; Tue, 28 Sep 1999 10:42:19 +0200
Message-ID: <7923615E38B1D21187EE0008C70DA9C805B1F2@fou-kj-21-001.nta.no>
From: marius.clemetsen@telenor.com
To: AAA-WG@merit.edu
Subject: Accounting Mailinglist
Date: Tue, 28 Sep 1999 10:38:59 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

I would like to be added to the accounting mailing list.

-Marius Clemetsen

--------------------------------------------------------
Marius Clemetsen, Telenor
Instituttveien 23, N-2007 Kjeller
Phone: (+47) 63 84 86 97
Mobile: (+47) 909 14 606
Email: marius.clemetsen@telenor.com
---------------------------------------------------------



