Re: AAAEXT charter, Take 1

[Greg Weber <gdweber@cisco.com>]

> 
> Why overloading RADIUSext with DIAMETER issues? If discussions
> happen separately, folks who have very little interest in pure 
> RADIUS won't have to deal with volumes of email on RADIUS.

On the contrary, i would imagine that most of the _issues_ are
AAA issues and not specific to the protocol.  Protocol selection
seems to be almost more of a deployment/OPs issue rather than
functional at this point at least.

> Take the example of Mobile IP WG. The WG was split into MIP6 and 
> MIP4 because it became too chaotic to manage and progress work
> on different disjoint threads.

Which contrasts with DHC where DHCPv4 & v6 are both handled by
the same WG....

Greg

> 
> -Kuntal
> 
> >-----Original Message-----
> >From: john.loughney@nokia.com [mailto:john.loughney@nokia.com] 
> >Sent: Wednesday, March 31, 2004 11:51 AM
> >To: avi@bridgewatersystems.com; aboba@internaut.com; 
> >radiusext@ops.ietf.org
> >Subject: RE: AAAEXT charter, Take 1
> >
> >
> >Hi Avi,
> >
> >> Is the scope of work going to remain the same?
> >
> >My feeling is that the scope would basically be the sam.
> > 
> >> If not, how do limited resources get mapped between RADIUS/Diameter?
> >
> >I would have resources if RADIUS and Diameter compatibility is 
> >included. I have less interest in pure RADIUS.
> >
> >John
> >
> >--
> >to unsubscribe send a message to 
> >radiusext-request@ops.ietf.org with the word 'unsubscribe' in 
> >a single line as the message text body.
> >archive: <http://psg.com/lists/radiusext/>
> >
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
> 


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>