From owner-aaa-wg@merit.edu  Tue Jan 26 09:40:34 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id JAA13464
	for <aaa-wg-archive@nic.merit.edu>; Tue, 26 Jan 1999 09:40:34 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id JAA18509
	for aaa-wg-outgoing; Tue, 26 Jan 1999 09:38:23 -0500 (EST)
Received: from digdug.cisco.com (digdug.cisco.com [171.69.30.215])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id JAA18505
	for <aaa-wg@merit.edu>; Tue, 26 Jan 1999 09:38:17 -0500 (EST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by digdug.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id GAA05286
	for <extdom.ietf-aaa@domestic.cisco.com>; Tue, 26 Jan 1999 06:37:45 -0800 (PST)
Received: from beasley.cisco.com (beasley.cisco.com [171.69.11.49])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id GAA22143
	for <extdom.ietf-aaa@filter.cisco.com>; Tue, 26 Jan 1999 06:37:52 -0800 (PST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by beasley.cisco.com (8.8.8/2.6/Cisco List Logging/CISCO.GATE.1.1) with ESMTP id GAA21341 for <ietf-aaa@external.cisco.com>; Tue, 26 Jan 1999 06:37:44 -0800 (PST)
Received: from proxy2.cisco.com (proxy2.cisco.com [192.31.7.89])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id GAA22127
	for <ietf-aaa@external.cisco.com>; Tue, 26 Jan 1999 06:37:50 -0800 (PST)
Received: (from smap@localhost)
	by proxy2.cisco.com (8.8.7/8.8.5) id GAA17520
	for <ietf-aaa@external.cisco.com>; Tue, 26 Jan 1999 06:37:41 -0800 (PST)
Received: from ndcrelay2.mcit.com(166.37.172.6) by proxy2.cisco.com via smap (V2.0)
	id xma017508; Tue, 26 Jan 99 14:37:37 GMT
X-SMAP-Received-From: outside
Received: from omta1.mcit.com (omta1.mcit.com [166.37.204.2])
          by ndcrelay2.mcit.com (8.8.7/) with ESMTP
	  id OAA07257; Tue, 26 Jan 1999 14:34:00 GMT
Received: from sinnreich2 ([166.35.227.182]) by omta1.mcit.com
          (InterMail v03.02.05 118 121 101) with SMTP
          id <19990126143642.GTTC8311@sinnreich2>;
          Tue, 26 Jan 1999 08:36:42 -0600
From: "Henry Sinnreich" <henry.sinnreich@mci.com>
To: "pcalhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>,
        "Ping Pan" <pingpan@dnrc.bell-labs.com>, <ietf-aaa@external.cisco.com>
Cc: "Jonathan Rosenberg" <jdrosen@dnrc.bell-labs.com>,
        "Dean Willis" <Dean.Willis@mci.com>,
        "Hoefelmeyer, Ralph (MCI)" <Ralph.Hoefelmeyer@mci.com>,
        <iptel@lists.research.bell-labs.com>
Subject: RE: IP Telphony Gateway metering
Date: Tue, 26 Jan 1999 08:36:15 -0500
Message-ID: <NBBBIIJFOKPMFOOILMBKMEDCDIAA.henry.sinnreich@mci.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
In-Reply-To: <Roam.SIMCSD.2.0.4.917358381.29852.pcalhoun@hsmpka>
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Pat wrote:
>Is it really necessary for the router to spew out XML
> (pages?), as
> opposed to a much simpler (and easier to parse) protocol, and have the AAA
> server simply record the information in an XML format?

I believe you have it right here, since changing the data format in routers
is simply not doable. We also don't yet understand or simply don't know the
computational load required by XML during peak traffic loads. Or the
scalability when handling 100k's of calls in the peak of the busy hour. If
however, XML is delivered by the AAA servers IMHO, we get the best of both
worlds.

>It seems like this
> would be much simpler for the embedded devices, and it would solve your
> real-time usage viewing requirements.

Next generation embedded devices could possibly use a common parser for
HTML, SIP and XML over a very thin operating system.
Would need to involve embedded device and protocol designers to explore the
best web-like approach.

Any other opinions on the list?

> Perhaps this thread really belongs in the AAA list.
>
> PatC

Agree and have addedd <ietf-aaa@external.cisco.com> in the header to see if
of interest.

Thanks, Henry

> -----Original Message-----
> From: pcalhoun@eng.sun.com [mailto:Pat.Calhoun@Eng.Sun.COM]
> Sent: Tuesday, January 26, 1999 8:46 AM
> To: Ping Pan
> Cc: Henry Sinnreich; Jonathan Rosenberg; Dean Willis; Hoefelmeyer, Ralph
> (MCI); iptel@lists.research.bell-labs.com
> Subject: Re: IP Telphony Gateway metering
>
>
> > Henry Sinnreich wrote:
> > >
> > > It appears that for Internet-wide standard AA(A) and metering
> (instead of
> > > the 3rd (A)), there is some work cut out for a possible BOF
> -> WG to agree
> > > on
> > >
> > > * Data excahnge with the AA(A) system,
> > > * Data exchange with the policy server using COPS,
> > > * Gateway metering,
> > > * RSVP and/or DiffServ metering,
> > > * IMHO a data format, why not XML?
>
> Henry,
>
> I know your feelings about XML, and perhaps you are correct, but I have a
> question. Is it really necessary for the router to spew out XML
> (pages?), as
> opposed to a much simpler (and easier to parse) protocol, and have the AAA
> server simply record the information in an XML format? It seems like this
> would be much simpler for the embedded devices, and it would solve your
> real-time usage viewing requirements.
>
> Perhaps this thread really belongs in the AAA list.
>
> PatC
> > >
> >
> > Hentry,
> >
> > More importantly, we need to correlate metering information from
> > different applications. For example, SIP session duration is monitored
> > via some policy servers. However, the actual user data (with RSVP
> > enabled) may take a path that is completely different from what SIP
> > messages are going. The policy servers hence need to collect the data
> > information and map it to the corresponding SIP session to accounting
> > purposes.
> >
> > As for the data format, I have no problem with XML format if all network
> > components are a bunch of Unix/NT servers. For the conventional routers,
> > I doubt that they have spare CPU cycles to process XML messages. In the
> > future, I don't care if all routers run JAVA, but not for now, please.
> > :-) Why cannot we simply send more traditional protocol messages?
> >
> > > Would be nice to agree on a framework and see if there is
> something missing
> > > or has to be written.
> > > Any interest in this?
> > >
> >
> > Isn't AAA group trying to put one together?
> >
> > > Thanks, Henry
> > >
> > >
> >
> > Regards,
> >
> > - Ping
> >
> > ---------
> > This message came from the IETF IPTEL Working Group Mailing List.
>
>


From owner-aaa-wg@merit.edu  Tue Jan 26 15:32:39 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id PAA17565
	for <aaa-wg-archive@nic.merit.edu>; Tue, 26 Jan 1999 15:32:38 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id PAA25973
	for aaa-wg-outgoing; Tue, 26 Jan 1999 15:31:54 -0500 (EST)
Received: from mailer.psc.edu (mailer.psc.edu [128.182.58.100])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id PAA25967
	for <aaa-wg@merit.edu>; Tue, 26 Jan 1999 15:31:48 -0500 (EST)
Received: from psc.edu (haroun.psc.edu [128.182.61.58])
	by mailer.psc.edu (8.8.7/8.8.7/mailer) with ESMTP id PAA31685
	for <aaa-wg@merit.edu>; Tue, 26 Jan 1999 15:31:47 -0500 (EST)
Message-ID: <36AE260C.676E850B@psc.edu>
Date: Tue, 26 Jan 1999 15:31:08 -0500
From: Peter Berger <peterb@psc.edu>
X-Mailer: Mozilla 4.5 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: aaa-wg@merit.edu
Subject: Clarification requested.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


Is the current AAA wg mailing list:

    aaa-wg@merit.edu
        or
    ietf-aaa@external.cisco.com

Thanks.

-Peter


From owner-aaa-wg@merit.edu  Tue Jan 26 16:03:49 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id QAA17977
	for <aaa-wg-archive@nic.merit.edu>; Tue, 26 Jan 1999 16:03:49 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id QAA26783
	for aaa-wg-outgoing; Tue, 26 Jan 1999 16:03:24 -0500 (EST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by merit.edu (8.9.1a/8.9.1) with SMTP id QAA26779
	for <aaa-wg@merit.edu>; Tue, 26 Jan 1999 16:03:19 -0500 (EST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id NAA12746; Tue, 26 Jan 1999 13:02:09 -0800
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.123.37])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id NAA20574;
	Tue, 26 Jan 1999 13:02:04 -0800
Received: from mordor by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4)
	id NAA17529; Tue, 26 Jan 1999 13:02:06 -0800
Date: Tue, 26 Jan 1999 13:02:13 -0800 (PST)
From: "pcalhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>
Reply-To: "pcalhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>
Subject: Re: Clarification requested.
To: Peter Berger <peterb@psc.edu>
Cc: aaa-wg@merit.edu
In-Reply-To: "Your message with ID" <36AE260C.676E850B@psc.edu>
Message-ID: <Roam.SIMCSD.2.0.4.917384533.13549.pcalhoun@hsmpka>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

> 
> Is the current AAA wg mailing list:
> 
>     aaa-wg@merit.edu
I believe this is the correct mailing list.


>         or
>     ietf-aaa@external.cisco.com
Whereas this is the one that was setup for the BOF.

PatC
> 
> Thanks.
> 
> -Peter
> 



From owner-aaa-wg@merit.edu  Tue Jan 26 16:58:03 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id QAA18656
	for <aaa-wg-archive@nic.merit.edu>; Tue, 26 Jan 1999 16:58:03 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id QAA28002
	for aaa-wg-outgoing; Tue, 26 Jan 1999 16:57:18 -0500 (EST)
Received: from ndcrelay.mcit.com (ndcrelay.mcit.com [166.37.172.49])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id QAA27992
	for <aaa-wg@merit.edu>; Tue, 26 Jan 1999 16:57:08 -0500 (EST)
Received: from omta2.mcit.com (omta2.mcit.com [166.37.204.3])
          by ndcrelay.mcit.com (8.8.7/) with ESMTP
	  id VAA30473; Tue, 26 Jan 1999 21:55:21 GMT
Received: from sinnreich2 ([166.35.150.60]) by omta2.mcit.com
          (InterMail v03.02.05 118 121 101) with SMTP
          id <19990126215533.TNGC5654@sinnreich2>;
          Tue, 26 Jan 1999 15:55:33 -0600
From: "Henry Sinnreich" <henry.sinnreich@mci.com>
To: "pcalhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>,
        "Ping Pan" <pingpan@dnrc.bell-labs.com>, <ietf-aaa@external.cisco.com>,
        <aaa-wg@merit.edu>
Cc: "Jonathan Rosenberg" <jdrosen@dnrc.bell-labs.com>,
        "Dean Willis" <Dean.Willis@mci.com>,
        "Hoefelmeyer, Ralph (MCI)" <Ralph.Hoefelmeyer@mci.com>,
        <iptel@lists.research.bell-labs.com>
Subject: RE: IP Telphony Gateway metering
Date: Tue, 26 Jan 1999 15:54:59 -0500
Message-ID: <NBBBIIJFOKPMFOOILMBKCEEFDIAA.henry.sinnreich@mci.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0)
In-reply-to: <Roam.SIMCSD.2.0.4.917358381.29852.pcalhoun@hsmpka>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Pat wrote:
>Is it really necessary for the router to spew out XML
> (pages?), as
> opposed to a much simpler (and easier to parse) protocol, and have the AAA
> server simply record the information in an XML format?

I believe you have it right here, since changing the data format in routers
is simply not doable. We also don't yet understand or simply don't know the
computational load required by XML during peak traffic loads. Or the
scalability when handling 100k's of calls in the peak of the busy hour. If
however, XML is delivered by the AAA servers IMHO, we get the best of both
worlds.

>It seems like this
> would be much simpler for the embedded devices, and it would solve your
> real-time usage viewing requirements.

Next generation embedded devices could possibly use a common parser for
HTML, SIP and XML over a very thin operating system.
Would need to involve embedded device and protocol designers to explore the
best web-like approach.

Any other opinions on the list?

> Perhaps this thread really belongs in the AAA list.
>
> PatC

Agree and have addedd <ietf-aaa@external.cisco.com> and <aaa-wg@merit.edu>
in the header to see if of interest.

Thanks, Henry

> -----Original Message-----
> From: pcalhoun@eng.sun.com [mailto:Pat.Calhoun@Eng.Sun.COM]
> Sent: Tuesday, January 26, 1999 8:46 AM
> To: Ping Pan
> Cc: Henry Sinnreich; Jonathan Rosenberg; Dean Willis; Hoefelmeyer, Ralph
> (MCI); iptel@lists.research.bell-labs.com
> Subject: Re: IP Telphony Gateway metering
>
>
> > Henry Sinnreich wrote:
> > >
> > > It appears that for Internet-wide standard AA(A) and metering
> (instead of
> > > the 3rd (A)), there is some work cut out for a possible BOF
> -> WG to agree
> > > on
> > >
> > > * Data excahnge with the AA(A) system,
> > > * Data exchange with the policy server using COPS,
> > > * Gateway metering,
> > > * RSVP and/or DiffServ metering,
> > > * IMHO a data format, why not XML?
>
> Henry,
>
> I know your feelings about XML, and perhaps you are correct, but I have a
> question. Is it really necessary for the router to spew out XML
> (pages?), as
> opposed to a much simpler (and easier to parse) protocol, and have the AAA
> server simply record the information in an XML format? It seems like this
> would be much simpler for the embedded devices, and it would solve your
> real-time usage viewing requirements.
>
> Perhaps this thread really belongs in the AAA list.
>
> PatC
> > >
> >
> > Hentry,
> >
> > More importantly, we need to correlate metering information from
> > different applications. For example, SIP session duration is monitored
> > via some policy servers. However, the actual user data (with RSVP
> > enabled) may take a path that is completely different from what SIP
> > messages are going. The policy servers hence need to collect the data
> > information and map it to the corresponding SIP session to accounting
> > purposes.
> >
> > As for the data format, I have no problem with XML format if all network
> > components are a bunch of Unix/NT servers. For the conventional routers,
> > I doubt that they have spare CPU cycles to process XML messages. In the
> > future, I don't care if all routers run JAVA, but not for now, please.
> > :-) Why cannot we simply send more traditional protocol messages?
> >
> > > Would be nice to agree on a framework and see if there is
> something missing
> > > or has to be written.
> > > Any interest in this?
> > >
> >
> > Isn't AAA group trying to put one together?
> >
> > > Thanks, Henry
> > >
> > >
> >
> > Regards,
> >
> > - Ping
> >
> > ---------
> > This message came from the IETF IPTEL Working Group Mailing List.
>
>


From owner-aaa-wg@merit.edu  Tue Jan 26 16:58:03 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id QAA18658
	for <aaa-wg-archive@nic.merit.edu>; Tue, 26 Jan 1999 16:58:03 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id QAA28024
	for aaa-wg-outgoing; Tue, 26 Jan 1999 16:57:35 -0500 (EST)
Received: from sj-mailhub-2.cisco.com (sj-mailhub-2.cisco.com [171.69.43.88])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id QAA28003
	for <aaa-wg@merit.edu>; Tue, 26 Jan 1999 16:57:19 -0500 (EST)
Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31])
	by sj-mailhub-2.cisco.com (8.9.1a/8.9.1) with ESMTP id NAA04376
	for <extdom.ietf-aaa@filter.cisco.com>; Tue, 26 Jan 1999 13:56:47 -0800 (PST)
Received: from sj-mailhub-2.cisco.com (sj-mailhub-2.cisco.com [171.69.43.88]) by hubbub.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id NAA06898 for <ietf-aaa@external.cisco.com>; Tue, 26 Jan 1999 13:56:46 -0800 (PST)
Received: from proxy2.cisco.com (proxy2.cisco.com [192.31.7.89])
	by sj-mailhub-2.cisco.com (8.9.1a/8.9.1) with ESMTP id NAA04361
	for <ietf-aaa@external.cisco.com>; Tue, 26 Jan 1999 13:56:45 -0800 (PST)
Received: (from smap@localhost)
	by proxy2.cisco.com (8.8.7/8.8.5) id NAA25036
	for <ietf-aaa@external.cisco.com>; Tue, 26 Jan 1999 13:56:43 -0800 (PST)
Received: from ndcrelay.mcit.com(166.37.172.49) by proxy2.cisco.com via smap (V2.0)
	id xma025006; Tue, 26 Jan 99 21:56:37 GMT
X-SMAP-Received-From: outside
Received: from omta2.mcit.com (omta2.mcit.com [166.37.204.3])
          by ndcrelay.mcit.com (8.8.7/) with ESMTP
	  id VAA30473; Tue, 26 Jan 1999 21:55:21 GMT
Received: from sinnreich2 ([166.35.150.60]) by omta2.mcit.com
          (InterMail v03.02.05 118 121 101) with SMTP
          id <19990126215533.TNGC5654@sinnreich2>;
          Tue, 26 Jan 1999 15:55:33 -0600
From: "Henry Sinnreich" <henry.sinnreich@mci.com>
To: "pcalhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>,
        "Ping Pan" <pingpan@dnrc.bell-labs.com>, <ietf-aaa@external.cisco.com>,
        <aaa-wg@merit.edu>
Cc: "Jonathan Rosenberg" <jdrosen@dnrc.bell-labs.com>,
        "Dean Willis" <Dean.Willis@mci.com>,
        "Hoefelmeyer, Ralph (MCI)" <Ralph.Hoefelmeyer@mci.com>,
        <iptel@lists.research.bell-labs.com>
Subject: RE: IP Telphony Gateway metering
Date: Tue, 26 Jan 1999 15:54:59 -0500
Message-ID: <NBBBIIJFOKPMFOOILMBKCEEFDIAA.henry.sinnreich@mci.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0)
In-reply-to: <Roam.SIMCSD.2.0.4.917358381.29852.pcalhoun@hsmpka>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

Pat wrote:
>Is it really necessary for the router to spew out XML
> (pages?), as
> opposed to a much simpler (and easier to parse) protocol, and have the AAA
> server simply record the information in an XML format?

I believe you have it right here, since changing the data format in routers
is simply not doable. We also don't yet understand or simply don't know the
computational load required by XML during peak traffic loads. Or the
scalability when handling 100k's of calls in the peak of the busy hour. If
however, XML is delivered by the AAA servers IMHO, we get the best of both
worlds.

>It seems like this
> would be much simpler for the embedded devices, and it would solve your
> real-time usage viewing requirements.

Next generation embedded devices could possibly use a common parser for
HTML, SIP and XML over a very thin operating system.
Would need to involve embedded device and protocol designers to explore the
best web-like approach.

Any other opinions on the list?

> Perhaps this thread really belongs in the AAA list.
>
> PatC

Agree and have addedd <ietf-aaa@external.cisco.com> and <aaa-wg@merit.edu>
in the header to see if of interest.

Thanks, Henry

> -----Original Message-----
> From: pcalhoun@eng.sun.com [mailto:Pat.Calhoun@Eng.Sun.COM]
> Sent: Tuesday, January 26, 1999 8:46 AM
> To: Ping Pan
> Cc: Henry Sinnreich; Jonathan Rosenberg; Dean Willis; Hoefelmeyer, Ralph
> (MCI); iptel@lists.research.bell-labs.com
> Subject: Re: IP Telphony Gateway metering
>
>
> > Henry Sinnreich wrote:
> > >
> > > It appears that for Internet-wide standard AA(A) and metering
> (instead of
> > > the 3rd (A)), there is some work cut out for a possible BOF
> -> WG to agree
> > > on
> > >
> > > * Data excahnge with the AA(A) system,
> > > * Data exchange with the policy server using COPS,
> > > * Gateway metering,
> > > * RSVP and/or DiffServ metering,
> > > * IMHO a data format, why not XML?
>
> Henry,
>
> I know your feelings about XML, and perhaps you are correct, but I have a
> question. Is it really necessary for the router to spew out XML
> (pages?), as
> opposed to a much simpler (and easier to parse) protocol, and have the AAA
> server simply record the information in an XML format? It seems like this
> would be much simpler for the embedded devices, and it would solve your
> real-time usage viewing requirements.
>
> Perhaps this thread really belongs in the AAA list.
>
> PatC
> > >
> >
> > Hentry,
> >
> > More importantly, we need to correlate metering information from
> > different applications. For example, SIP session duration is monitored
> > via some policy servers. However, the actual user data (with RSVP
> > enabled) may take a path that is completely different from what SIP
> > messages are going. The policy servers hence need to collect the data
> > information and map it to the corresponding SIP session to accounting
> > purposes.
> >
> > As for the data format, I have no problem with XML format if all network
> > components are a bunch of Unix/NT servers. For the conventional routers,
> > I doubt that they have spare CPU cycles to process XML messages. In the
> > future, I don't care if all routers run JAVA, but not for now, please.
> > :-) Why cannot we simply send more traditional protocol messages?
> >
> > > Would be nice to agree on a framework and see if there is
> something missing
> > > or has to be written.
> > > Any interest in this?
> > >
> >
> > Isn't AAA group trying to put one together?
> >
> > > Thanks, Henry
> > >
> > >
> >
> > Regards,
> >
> > - Ping
> >
> > ---------
> > This message came from the IETF IPTEL Working Group Mailing List.
>
>


From owner-aaa-wg@merit.edu  Wed Jan 27 08:48:01 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id IAA27425
	for <aaa-wg-archive@nic.merit.edu>; Wed, 27 Jan 1999 08:48:01 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id IAA09073
	for aaa-wg-outgoing; Wed, 27 Jan 1999 08:46:30 -0500 (EST)
Received: from quisp.cisco.com (quisp.cisco.com [171.69.95.82])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id IAA09069
	for <aaa-wg@merit.edu>; Wed, 27 Jan 1999 08:46:25 -0500 (EST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by quisp.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id FAA21390 for <extdom.ietf-aaa@domestic.cisco.com>; Wed, 27 Jan 1999 05:45:53 -0800 (PST)
Received: from beasley.cisco.com (beasley.cisco.com [171.69.11.49])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id FAA01688
	for <extdom.ietf-aaa@filter.cisco.com>; Wed, 27 Jan 1999 05:46:00 -0800 (PST)
Received: from sj-mailhub-2.cisco.com (sj-mailhub-2.cisco.com [171.69.43.88]) by beasley.cisco.com (8.8.8/2.6/Cisco List Logging/CISCO.GATE.1.1) with ESMTP id FAA23978 for <ietf-aaa@external.cisco.com>; Wed, 27 Jan 1999 05:45:51 -0800 (PST)
Received: from proxy2.cisco.com (proxy2.cisco.com [192.31.7.89])
	by sj-mailhub-2.cisco.com (8.9.1a/8.9.1) with ESMTP id FAA08247
	for <ietf-aaa@external.cisco.com>; Wed, 27 Jan 1999 05:45:52 -0800 (PST)
Received: (from smap@localhost)
	by proxy2.cisco.com (8.8.7/8.8.5) id FAA19945
	for <ietf-aaa@external.cisco.com>; Wed, 27 Jan 1999 05:45:50 -0800 (PST)
Received: from mail.transnexus.com(209.144.152.22) by proxy2.cisco.com via smap (V2.0)
	id xma019932; Wed, 27 Jan 99 13:45:45 GMT
X-SMAP-Received-From: outside
Received: (qmail 32729 invoked from network); 27 Jan 1999 13:45:04 -0000
Received: from unknown (HELO notebook) (172.16.1.132)
  by 172.16.1.10 with SMTP; 27 Jan 1999 13:45:04 -0000
Message-ID: <017d01be49fa$e14b1b40$840110ac@notebook.int.transnexus.com>
From: "Stephen Thomas" <stephen.thomas@transnexus.com>
To: "Henry Sinnreich" <henry.sinnreich@mci.com>,
        "pcalhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>,
        "Ping Pan" <pingpan@dnrc.bell-labs.com>, <ietf-aaa@external.cisco.com>,
        <aaa-wg@merit.edu>
Cc: "Jonathan Rosenberg" <jdrosen@dnrc.bell-labs.com>,
        "Dean Willis" <Dean.Willis@mci.com>,
        "Hoefelmeyer, Ralph (MCI)" <Ralph.Hoefelmeyer@mci.com>,
        <iptel@lists.research.bell-labs.com>
Subject: Re: IP Telphony Gateway metering
Date: Wed, 27 Jan 1999 08:42:24 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

A couple of observations below.


-----Original Message-----
From: Henry Sinnreich <henry.sinnreich@mci.com>
To: pcalhoun@eng.sun.com <Pat.Calhoun@Eng.Sun.COM>; Ping Pan
<pingpan@dnrc.bell-labs.com>; ietf-aaa@external.cisco.com
<ietf-aaa@external.cisco.com>; aaa-wg@merit.edu <aaa-wg@merit.edu>
Cc: Jonathan Rosenberg <jdrosen@dnrc.bell-labs.com>; Dean Willis
<Dean.Willis@mci.com>; Hoefelmeyer, Ralph (MCI) <Ralph.Hoefelmeyer@mci.com>;
iptel@lists.research.bell-labs.com <iptel@lists.research.bell-labs.com>
Date: Tuesday, 26 January 1999 7:18 PM
Subject: RE: IP Telphony Gateway metering


|Pat wrote:
|>Is it really necessary for the router to spew out XML
|> (pages?), as
|> opposed to a much simpler (and easier to parse) protocol, and have the
AAA
|> server simply record the information in an XML format?

It seems like "simpler" protocols tend to work best when the
information to be parsed has a fairly simple structure. That is
certainly true today for dialup Internet access where the accounting
information is essentially just duration. I'm not certain that new
applications (such as multimedia over IP, to generalize the starting
point of this thread) will meet that same criteria. Considering the
multitude of variables that may be a part of accounting information
(e.g. layered media streams, various QoS attributes, network paths,
measured performance, ...) a way to encode a structure as part the
information might be essential. I suppose I'm suggesting that, in the
future, accounting information might be much more multi-dimensional
than it is today. XML is certainly one way to encode structure, others
exists as well (e.g. ASN.1). I have no credible opinion on whether
the dimensionality is handled by a "router" or an "AAA server,"
partly because I'm not sure the distinction between the two is
necessarily that clear.

[...]

|Next generation embedded devices could possibly use a common parser for
|HTML, SIP and XML over a very thin operating system.
|Would need to involve embedded device and protocol designers to explore the
|best web-like approach.


There is a fair body of work already on embedded device and protocol
support for both ASN.1 and XML (to cite the two examples mentioned
above). Although not necessarily in the IETF (other than SNMP). ISO
and ITU-T have certainly spent a lot of time with ASN.1, and the
Wireless Application Forum (www.wapforum.org) has developed a
considerable body of work on embedded XML support.

Stephen


____________________________________________________________________

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



From owner-aaa-wg@merit.edu  Wed Jan 27 08:48:01 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id IAA27426
	for <aaa-wg-archive@nic.merit.edu>; Wed, 27 Jan 1999 08:48:01 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id IAA09066
	for aaa-wg-outgoing; Wed, 27 Jan 1999 08:45:48 -0500 (EST)
Received: from lists.int.transnexus.com (mail.TRANSNEXUS.com [209.144.152.22])
	by merit.edu (8.9.1a/8.9.1) with SMTP id IAA09062
	for <aaa-wg@merit.edu>; Wed, 27 Jan 1999 08:45:43 -0500 (EST)
Received: (qmail 32729 invoked from network); 27 Jan 1999 13:45:04 -0000
Received: from unknown (HELO notebook) (172.16.1.132)
  by 172.16.1.10 with SMTP; 27 Jan 1999 13:45:04 -0000
Message-ID: <017d01be49fa$e14b1b40$840110ac@notebook.int.transnexus.com>
From: "Stephen Thomas" <stephen.thomas@transnexus.com>
To: "Henry Sinnreich" <henry.sinnreich@mci.com>,
        "pcalhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>,
        "Ping Pan" <pingpan@dnrc.bell-labs.com>, <ietf-aaa@external.cisco.com>,
        <aaa-wg@merit.edu>
Cc: "Jonathan Rosenberg" <jdrosen@dnrc.bell-labs.com>,
        "Dean Willis" <Dean.Willis@mci.com>,
        "Hoefelmeyer, Ralph (MCI)" <Ralph.Hoefelmeyer@mci.com>,
        <iptel@lists.research.bell-labs.com>
Subject: Re: IP Telphony Gateway metering
Date: Wed, 27 Jan 1999 08:42:24 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

A couple of observations below.


-----Original Message-----
From: Henry Sinnreich <henry.sinnreich@mci.com>
To: pcalhoun@eng.sun.com <Pat.Calhoun@Eng.Sun.COM>; Ping Pan
<pingpan@dnrc.bell-labs.com>; ietf-aaa@external.cisco.com
<ietf-aaa@external.cisco.com>; aaa-wg@merit.edu <aaa-wg@merit.edu>
Cc: Jonathan Rosenberg <jdrosen@dnrc.bell-labs.com>; Dean Willis
<Dean.Willis@mci.com>; Hoefelmeyer, Ralph (MCI) <Ralph.Hoefelmeyer@mci.com>;
iptel@lists.research.bell-labs.com <iptel@lists.research.bell-labs.com>
Date: Tuesday, 26 January 1999 7:18 PM
Subject: RE: IP Telphony Gateway metering


|Pat wrote:
|>Is it really necessary for the router to spew out XML
|> (pages?), as
|> opposed to a much simpler (and easier to parse) protocol, and have the
AAA
|> server simply record the information in an XML format?

It seems like "simpler" protocols tend to work best when the
information to be parsed has a fairly simple structure. That is
certainly true today for dialup Internet access where the accounting
information is essentially just duration. I'm not certain that new
applications (such as multimedia over IP, to generalize the starting
point of this thread) will meet that same criteria. Considering the
multitude of variables that may be a part of accounting information
(e.g. layered media streams, various QoS attributes, network paths,
measured performance, ...) a way to encode a structure as part the
information might be essential. I suppose I'm suggesting that, in the
future, accounting information might be much more multi-dimensional
than it is today. XML is certainly one way to encode structure, others
exists as well (e.g. ASN.1). I have no credible opinion on whether
the dimensionality is handled by a "router" or an "AAA server,"
partly because I'm not sure the distinction between the two is
necessarily that clear.

[...]

|Next generation embedded devices could possibly use a common parser for
|HTML, SIP and XML over a very thin operating system.
|Would need to involve embedded device and protocol designers to explore the
|best web-like approach.


There is a fair body of work already on embedded device and protocol
support for both ASN.1 and XML (to cite the two examples mentioned
above). Although not necessarily in the IETF (other than SNMP). ISO
and ITU-T have certainly spent a lot of time with ASN.1, and the
Wireless Application Forum (www.wapforum.org) has developed a
considerable body of work on embedded XML support.

Stephen


____________________________________________________________________

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



From owner-aaa-wg@merit.edu  Wed Jan 27 15:24:02 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id PAA02499
	for <aaa-wg-archive@nic.merit.edu>; Wed, 27 Jan 1999 15:24:02 -0500 (EST)
Received: by merit.edu (8.9.1a/8.9.1) id PAA17681
	for aaa-wg-outgoing; Wed, 27 Jan 1999 15:23:14 -0500 (EST)
Received: from idrp.merit.edu (skh@idrp.merit.edu [198.108.60.89])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id PAA17674;
	Wed, 27 Jan 1999 15:23:07 -0500 (EST)
Received: from localhost by idrp.merit.edu (8.9.1a/8.9.1) with SMTP id PAA02464;
	Wed, 27 Jan 1999 15:23:06 -0500 (EST)
X-Authentication-Warning: idrp.merit.edu: skh owned process doing -bs
Date: Wed, 27 Jan 1999 15:23:06 -0500 (EST)
From: Susan Hares <skh@merit.edu>
To: Peter Berger <peterb@psc.edu>
cc: aaa-wg@merit.edu
Subject: Re: Clarification requested.
In-Reply-To: <36AE260C.676E850B@psc.edu>
Message-ID: <Pine.GSO.3.93.990127152257.1783D-100000@idrp.merit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

aaa-wg@merit.edu.

sue hares


On Tue, 26 Jan 1999, Peter Berger wrote:

> 
> Is the current AAA wg mailing list:
> 
>     aaa-wg@merit.edu
>         or
>     ietf-aaa@external.cisco.com
> 
> Thanks.
> 
> -Peter
> 
> 


From owner-aaa-wg@merit.edu  Thu Jan 28 11:03:48 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA16801
	for <aaa-wg-archive@nic.merit.edu>; Thu, 28 Jan 1999 11:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id LAA18292
	for aaa-wg-outgoing; Thu, 28 Jan 1999 11:01:18 -0500 (EST)
Received: from idrp.merit.edu (skh@idrp.merit.edu [198.108.60.89])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id LAA18284;
	Thu, 28 Jan 1999 11:01:12 -0500 (EST)
Received: from localhost by idrp.merit.edu (8.9.1a/8.9.1) with SMTP id LAA06891;
	Thu, 28 Jan 1999 11:01:11 -0500 (EST)
X-Authentication-Warning: idrp.merit.edu: skh owned process doing -bs
Date: Thu, 28 Jan 1999 11:01:11 -0500 (EST)
From: Susan Hares <skh@merit.edu>
To: Peter Berger <peterb@psc.edu>
cc: aaa-wg@merit.edu
Subject: Re: Clarification requested.
In-Reply-To: <36AE260C.676E850B@psc.edu>
Message-ID: <Pine.GSO.3.93.990128110106.5951l-100000@idrp.merit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk

aaa-wg@merit.edu

On Tue, 26 Jan 1999, Peter Berger wrote:

> 
> Is the current AAA wg mailing list:
> 
>     aaa-wg@merit.edu
>         or
>     ietf-aaa@external.cisco.com
> 
> Thanks.
> 
> -Peter
> 
> 


From owner-aaa-wg@merit.edu  Thu Jan 28 11:42:29 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA17518
	for <aaa-wg-archive@nic.merit.edu>; Thu, 28 Jan 1999 11:42:29 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id LAA19477
	for aaa-wg-outgoing; Thu, 28 Jan 1999 11:42:16 -0500 (EST)
Received: from idrp.merit.edu (skh@idrp.merit.edu [198.108.60.89])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id LAA19472;
	Thu, 28 Jan 1999 11:42:12 -0500 (EST)
From: skh@merit.edu
Received: (from skh@localhost)
	by idrp.merit.edu (8.9.1a/8.9.1) id LAA07036;
	Thu, 28 Jan 1999 11:42:11 -0500 (EST)
Date: Thu, 28 Jan 1999 11:42:11 -0500 (EST)
Message-Id: <199901281642.LAA07036@idrp.merit.edu>
To: aaa-wg@merit.edu
Subject: Straw-person charter
Cc: skh@merit.edu
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


Hi all:

Below is a straw-person charter.  I gave this straw-person charter
to Fred Baker at IETF for review as our area director.  Fred was
going to create a revision for this document prior to me
sending it to all of you.  Fred has been overwhelmed by his numerous
and necessary duties with the IETF and cisco.  I am sending this
"proposed" AAA-charter to all of you to discuss on the mailing list.

Please send comments to either me privately (if you are shy) or to the
list.  For all you who volunteered for areas of work, I will be contacting
you within the week to put you in groupings by your interest.  Please
note that joining one of these sub-group of the Working Group involves:

	1) participating daily on a mail list, and weekly on 
	   a conference call.
	2) volunteering for co-writing a section of the documents

Please contact me privately if you wish to volunteer for 
a subgrouping. 

The current sub-groups (given the current charter), will be by
work area:

   Documents for March presentation (draft finished by February) 
	Document 1 - List of applications that use AAA
	Document 2 - AAA requirments

  Documents for  April documents (drafts finished by April 15th) 
	Document 3 - Transport protocol recommendation/selection
	Document 4 - Base Framework protocol.

   2nd round of Documents subgroups
	Document 5 - Document on Accounting
	Document 6 - Document on Data Format


Sue Hares

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


AAA working group charter 

The Authentication, Authorization and Accounting working group will
focus on the specification of a general Authentication, 
Authorization, and Accounting protocol for the Internet.
The purpose behind creating a general AAA protocol for the Internet is to create
a common base protocol for a number of specific AAA protocols which include
IP Telephony, SS7 AAA, Bandwidth Broker AAA, and Network Access Server AAA.   
By creating a general base Protocol, the amount of work to create a 
specific AAA protocols will be reduced.

The problem space for a general AAA working group contains
work in: 
	- determining the current set of specific applications
	  that the AAA will service, 
	- documenting requirements for a base AAA protocol,  
	- selecting a transport protocol or set of transport protocol to
	  be used by a general AAA protocol based on the requirements,
        - selecting the framework for the AAA protocols, 
	- specifying the base AAA protocol,
	- specifying the data formats for information contained 
	  in the AAA protocol information for authentication,
	  authorization, and accounting.

Since the area of work is broad the working group will need to focus
on subsections of the work.   To aid this effort, the charter of the
working group will be focused on a few sections of the total work.  At the
time period, the working group nears completion of this work the 
charter will be revised to include the next section of the work.

The first step in this working group is to determine the requirements for the
AAA protocol.    To accomplish this, we must document the current set of
applications that we will use to set our requirements.  To set the
requirements, we will collect requirements and then cull out any requirements
which are specific to a particular instantiation of AAA.  These requirements
will be forward to the appropriate working group working on a specific
AAA function such as NASREQ.  The work on the requirements will leverage
the work done on AAA requirements by the two BOF meetings.  

After setting our requirements, we will use the requirements to 
select a transport protocol and set the framework for the AAA protocols.  
After having done all the background work for specifying the base AAA protocol,
The working group will select a base protocol for AAA functions.

At this point, the work will diverge into two paths:

	- specification of data format for AAA functions such as 
	  accounting,
        - the specification of new specific protocols based on
	  the new AAA Base protocol.

The working group should then re-examine the charter to tighten
the focus once again. 

Document Schedule

April '99    AAA Applications (informational RFC) Working Group Draft
	     AAA Requirements to Working Group Draft
	  
May '99      AAA transport selection to Working Group Draft
             AAA Base Protocol Framework Working Group Draft 

July  '99    AAA Base protocol Specification to Working Group Draft 
	     AAA Applications to Informational RFC  
	     AAA Requirements to Informational RFC  
	   
Nov   '99    Revision of charter to include new specific protocols
   	     and data formats.



	
		


From owner-aaa-wg@merit.edu  Fri Jan 29 11:39:31 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id LAA07817
	for <aaa-wg-archive@nic.merit.edu>; Fri, 29 Jan 1999 11:39:31 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id LAA12211
	for aaa-wg-outgoing; Fri, 29 Jan 1999 11:36:11 -0500 (EST)
Received: from smtprich.nortel.com (smtprich.nortel.com [192.135.215.8])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id LAA12207;
	Fri, 29 Jan 1999 11:36:06 -0500 (EST)
Received: from zrtpd004.us.nortel.com (actually nrtpd004) 
          by smtprich.nortel.com; Fri, 29 Jan 1999 10:36:00 -0600
Received: by zrtpd004.us.nortel.com with Internet Mail Service (5.0.1460.8) 
          id <D8AL211A>; Fri, 29 Jan 1999 11:36:00 -0500
Message-ID: <31B1EFDD2CD3D11187710000F805A8D5022D5E39@crchy270.us.nortel.com>
From: "Basavaraj Patil" <bpatil@nortelnetworks.com>
To: "'skh@merit.edu'" <skh@merit.edu>
Cc: "'aaa-wg@merit.edu'" <aaa-wg@merit.edu>
Subject: Re: Straw-person charter
Date: Fri, 29 Jan 1999 11:35:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1460.8)
Content-Type: text/plain
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>
>From:	skh@merit.edu
>Sent:	Thursday, January 28, 1999 10:42 AM
>To:	aaa-wg@merit.edu
>Cc:	skh@merit.edu
>Subject:	Straw-person charter
>

 --- Snip Snip---
>
>--------------
>
>
>AAA working group charter 
>
>The Authentication, Authorization and Accounting working group will
>focus on the specification of a general Authentication, 
>Authorization, and Accounting protocol for the Internet.
>The purpose behind creating a general AAA protocol for the Internet is to
create
>a common base protocol for a number of specific AAA protocols which include
>IP Telephony, SS7 AAA, Bandwidth Broker AAA, and Network Access Server AAA.

>By creating a general base Protocol, the amount of work to create a 
>specific AAA protocols will be reduced.

Mentioning the above applications as examples for supporting the need
for a commmon base AAA protocol is good, but we do not want to
necessarily limit the scope to just a few. Starting with the ones
mentioned above will give a good and common set of requirements for
the WG to focus on. The AAA protocol needs to be generic enough to
support new and future applications. 
It's just a matter of how you say it in the charter and nothing more.

-Basavaraj Patil

>
>The problem space for a general AAA working group contains
>work in: 
>	- determining the current set of specific applications
>	  that the AAA will service, 
>	- documenting requirements for a base AAA protocol,  
>	- selecting a transport protocol or set of transport protocol to
>	  be used by a general AAA protocol based on the requirements,
>        - selecting the framework for the AAA protocols, 
>	- specifying the base AAA protocol,
>	- specifying the data formats for information contained 
>	  in the AAA protocol information for authentication,
>	  authorization, and accounting.
>

Basavaraj Patil
Wireless Technology Labs - Dept IP10
Nortel Networks, Richardson
> *  972-684-1489
> 

From owner-aaa-wg@merit.edu  Fri Jan 29 12:09:34 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id MAA08082
	for <aaa-wg-archive@nic.merit.edu>; Fri, 29 Jan 1999 12:09:34 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id MAA12910
	for aaa-wg-outgoing; Fri, 29 Jan 1999 12:09:19 -0500 (EST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by merit.edu (8.9.1a/8.9.1) with SMTP id MAA12898;
	Fri, 29 Jan 1999 12:09:12 -0500 (EST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id JAA27273; Fri, 29 Jan 1999 09:08:19 -0800
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.105.37])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id JAA03976;
	Fri, 29 Jan 1999 09:08:18 -0800
Received: from hsmpka.eng.sun.com by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4)
	id JAA09816; Fri, 29 Jan 1999 09:08:02 -0800
From: Pat.Calhoun@eng.sun.com (Patrice Calhoun)
Message-Id: <199901291708.JAA09816@hsmpka.eng.sun.com>
Date: Fri, 29 Jan 1999 09:05:39 -0800
To: "Basavaraj Patil" <bpatil@nortelnetworks.com>,
        "'skh@merit.edu'" <skh@merit.edu>
Cc: "'aaa-wg@merit.edu'" <aaa-wg@merit.edu>
Reply-To: <Pat.Calhoun@eng.sun.com>
Subject: Re: Straw-person charter
X-Mailer: Sun NetMail 2.2.5
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


>
>>
>>From:	skh@merit.edu
>>Sent:	Thursday, January 28, 1999 10:42 AM
>>To:	aaa-wg@merit.edu
>>Cc:	skh@merit.edu
>>Subject:	Straw-person charter
>>
>
> --- Snip Snip---
>>
>>--------------
>>
>>
>>AAA working group charter 
>>
>>The Authentication, Authorization and Accounting working group will
>>focus on the specification of a general Authentication, 
>>Authorization, and Accounting protocol for the Internet.
>>The purpose behind creating a general AAA protocol for the Internet is to
>create
>>a common base protocol for a number of specific AAA protocols which include
>>IP Telephony, SS7 AAA, Bandwidth Broker AAA, and Network Access Server AAA.
>
>>By creating a general base Protocol, the amount of work to create a 
>>specific AAA protocols will be reduced.
>
>Mentioning the above applications as examples for supporting the need
>for a commmon base AAA protocol is good, but we do not want to
>necessarily limit the scope to just a few. Starting with the ones
>mentioned above will give a good and common set of requirements for
>the WG to focus on. The AAA protocol needs to be generic enough to
>support new and future applications. 
>It's just a matter of how you say it in the charter and nothing more.
>
>-Basavaraj Patil

Absolutely, and one of the agenda items is to come up with a list of the
current applications that need AAA services. Of course, the intent is to
create the base protocol to be extensible to suit future service requirements.


PatC
>
>>
>>The problem space for a general AAA working group contains
>>work in: 
>>	- determining the current set of specific applications
>>	  that the AAA will service, 
>>	- documenting requirements for a base AAA protocol,  
>>	- selecting a transport protocol or set of transport protocol to
>>	  be used by a general AAA protocol based on the requirements,
>>        - selecting the framework for the AAA protocols, 
>>	- specifying the base AAA protocol,
>>	- specifying the data formats for information contained 
>>	  in the AAA protocol information for authentication,
>>	  authorization, and accounting.
>>
>
>Basavaraj Patil
>Wireless Technology Labs - Dept IP10
>Nortel Networks, Richardson
>> *  972-684-1489
>> 



From owner-aaa-wg@merit.edu  Fri Jan 29 19:02:31 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id TAA12674
	for <aaa-wg-archive@nic.merit.edu>; Fri, 29 Jan 1999 19:02:31 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id SAA21054
	for aaa-wg-outgoing; Fri, 29 Jan 1999 18:59:24 -0500 (EST)
Received: from idrp.merit.edu (skh@idrp.merit.edu [198.108.60.89])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id SAA21050;
	Fri, 29 Jan 1999 18:59:20 -0500 (EST)
Received: from localhost by idrp.merit.edu (8.9.1a/8.9.1) with SMTP id SAA13816;
	Fri, 29 Jan 1999 18:59:19 -0500 (EST)
X-Authentication-Warning: idrp.merit.edu: skh owned process doing -bs
Date: Fri, 29 Jan 1999 18:59:18 -0500 (EST)
From: Susan Hares <skh@merit.edu>
To: Basavaraj Patil <bpatil@nortelnetworks.com>
cc: "'aaa-wg@merit.edu'" <aaa-wg@merit.edu>
Subject: Re: Straw-person charter
In-Reply-To: <31B1EFDD2CD3D11187710000F805A8D5022D5E39@crchy270.us.nortel.com>
Message-ID: <Pine.GSO.3.93.990129185858.13746G-100000@idrp.merit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


Do you have suggestions for rewording that sentence.  Any help
gratefully accepted.

Sue 

On Fri, 29 Jan 1999, Basavaraj Patil wrote:

> 
> >
> >From:	skh@merit.edu
> >Sent:	Thursday, January 28, 1999 10:42 AM
> >To:	aaa-wg@merit.edu
> >Cc:	skh@merit.edu
> >Subject:	Straw-person charter
> >
> 
>  --- Snip Snip---
> >
> >--------------
> >
> >
> >AAA working group charter 
> >
> >The Authentication, Authorization and Accounting working group will
> >focus on the specification of a general Authentication, 
> >Authorization, and Accounting protocol for the Internet.
> >The purpose behind creating a general AAA protocol for the Internet is to
> create
> >a common base protocol for a number of specific AAA protocols which include
> >IP Telephony, SS7 AAA, Bandwidth Broker AAA, and Network Access Server AAA.
> 
> >By creating a general base Protocol, the amount of work to create a 
> >specific AAA protocols will be reduced.
> 
> Mentioning the above applications as examples for supporting the need
> for a commmon base AAA protocol is good, but we do not want to
> necessarily limit the scope to just a few. Starting with the ones
> mentioned above will give a good and common set of requirements for
> the WG to focus on. The AAA protocol needs to be generic enough to
> support new and future applications. 
> It's just a matter of how you say it in the charter and nothing more.
> 
> -Basavaraj Patil
> 
> >
> >The problem space for a general AAA working group contains
> >work in: 
> >	- determining the current set of specific applications
> >	  that the AAA will service, 
> >	- documenting requirements for a base AAA protocol,  
> >	- selecting a transport protocol or set of transport protocol to
> >	  be used by a general AAA protocol based on the requirements,
> >        - selecting the framework for the AAA protocols, 
> >	- specifying the base AAA protocol,
> >	- specifying the data formats for information contained 
> >	  in the AAA protocol information for authentication,
> >	  authorization, and accounting.
> >
> 
> Basavaraj Patil
> Wireless Technology Labs - Dept IP10
> Nortel Networks, Richardson
> > *  972-684-1489
> > 
> 


From owner-aaa-wg@merit.edu  Sat Jan 30 10:12:02 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id KAA19010
	for <aaa-wg-archive@nic.merit.edu>; Sat, 30 Jan 1999 10:12:02 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id KAA28128
	for aaa-wg-outgoing; Sat, 30 Jan 1999 10:09:38 -0500 (EST)
Received: from idrp.merit.edu (skh@idrp.merit.edu [198.108.60.89])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id KAA28122;
	Sat, 30 Jan 1999 10:09:32 -0500 (EST)
From: skh@merit.edu
Received: (from skh@localhost)
	by idrp.merit.edu (8.9.1a/8.9.1) id KAA16542;
	Sat, 30 Jan 1999 10:09:31 -0500 (EST)
Date: Sat, 30 Jan 1999 10:09:31 -0500 (EST)
Message-Id: <199901301509.KAA16542@idrp.merit.edu>
To: aaa-wg@merit.edu
Subject: Charter Discussion ends 2/6/99
Cc: skh@merit.edu
Sender: owner-aaa-bof@merit.edu
Precedence: bulk


Please make your comments on the charter by 2/6/99.
I will post the results and send that charter to  
Fred Baker as the Area Director.

Sue Hares



From owner-aaa-wg@merit.edu  Sun Jan 31 16:44:31 1999
Received: from merit.edu (merit.edu [198.108.1.42])
	by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id QAA05340
	for <aaa-wg-archive@nic.merit.edu>; Sun, 31 Jan 1999 16:44:30 -0500 (EST)
Received: (from majordom@localhost)
	by merit.edu (8.9.1a/8.9.1) id QAA13009
	for aaa-wg-outgoing; Sun, 31 Jan 1999 16:42:31 -0500 (EST)
Received: from calliope1.fm.intel.com (calliope1.fm.intel.com [132.233.247.10])
	by merit.edu (8.9.1a/8.9.1) with ESMTP id QAA13003;
	Sun, 31 Jan 1999 16:42:26 -0500 (EST)
Received: from fmsmsx29.FM.INTEL.COM (fmsmsx29.fm.intel.com [132.233.42.29])
	by calliope1.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id VAA20875;
	Sun, 31 Jan 1999 21:42:22 GMT
Received: by FMSMSX29 with Internet Mail Service (5.5.2232.9)
	id <D6S0Y5FF>; Sun, 31 Jan 1999 13:42:22 -0800
Message-ID: <7DAA70BEB463D211AC3E00A0C96B7AB2A64DDC@ORSMSX41>
From: "Yavatkar, Raj" <raj.yavatkar@intel.com>
To: Susan Hares <skh@merit.edu>, Basavaraj Patil
	 <bpatil@nortelnetworks.com>
Cc: "'aaa-wg@merit.edu'" <aaa-wg@merit.edu>
Subject: RE: Straw-person charter
Date: Sun, 31 Jan 1999 13:42:21 -0800
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

Hi Susan:

Looking at your schedule for documents, I am really surprised. Given that WG
will meet for the first time in March, is it really realistic to have
documents done by April and still ensure a chance for everyone to
participate, contribute, and then reach decisions. I hope we are not coming
in with a pre-conceived notions on any of the documents.

Please clarify

Thanks
Raj

-----Original Message-----
From: Susan Hares [mailto:skh@merit.edu]
Sent: Friday, January 29, 1999 3:59 PM
To: Basavaraj Patil
Cc: 'aaa-wg@merit.edu'
Subject: Re: Straw-person charter



Do you have suggestions for rewording that sentence.  Any help
gratefully accepted.

Sue 

On Fri, 29 Jan 1999, Basavaraj Patil wrote:

> 
> >
> >From:	skh@merit.edu
> >Sent:	Thursday, January 28, 1999 10:42 AM
> >To:	aaa-wg@merit.edu
> >Cc:	skh@merit.edu
> >Subject:	Straw-person charter
> >
> 
>  --- Snip Snip---
> >
> >--------------
> >
> >
> >AAA working group charter 
> >
> >The Authentication, Authorization and Accounting working group will
> >focus on the specification of a general Authentication, 
> >Authorization, and Accounting protocol for the Internet.
> >The purpose behind creating a general AAA protocol for the Internet is to
> create
> >a common base protocol for a number of specific AAA protocols which
include
> >IP Telephony, SS7 AAA, Bandwidth Broker AAA, and Network Access Server
AAA.
> 
> >By creating a general base Protocol, the amount of work to create a 
> >specific AAA protocols will be reduced.
> 
> Mentioning the above applications as examples for supporting the need
> for a commmon base AAA protocol is good, but we do not want to
> necessarily limit the scope to just a few. Starting with the ones
> mentioned above will give a good and common set of requirements for
> the WG to focus on. The AAA protocol needs to be generic enough to
> support new and future applications. 
> It's just a matter of how you say it in the charter and nothing more.
> 
> -Basavaraj Patil
> 
> >
> >The problem space for a general AAA working group contains
> >work in: 
> >	- determining the current set of specific applications
> >	  that the AAA will service, 
> >	- documenting requirements for a base AAA protocol,  
> >	- selecting a transport protocol or set of transport protocol to
> >	  be used by a general AAA protocol based on the requirements,
> >        - selecting the framework for the AAA protocols, 
> >	- specifying the base AAA protocol,
> >	- specifying the data formats for information contained 
> >	  in the AAA protocol information for authentication,
> >	  authorization, and accounting.
> >
> 
> Basavaraj Patil
> Wireless Technology Labs - Dept IP10
> Nortel Networks, Richardson
> > *  972-684-1489
> > 
> 

