[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RADEXT WG Consensus call on acceptance of RADSEC as a work item



I support taking on RADSEC as a WG work item.

--------------------------------------------------
From: "Clint Chaplin" <clint.chaplin@gmail.com>
Sent: Sunday, March 16, 2008 6:21 PM
To: <Bernard_Aboba@hotmail.com>
Cc: <radiusext@ops.ietf.org>
Subject: Re: RADEXT WG Consensus call on acceptance of RADSEC as a work item

I support this.

--------------------------------------------------------------------------------
From: "Klaas Wierenga" <klaas@wierenga.net>
Sent: Saturday, March 15, 2008 7:55 AM
To: <Bernard_Aboba@hotmail.com>
Cc: <radiusext@ops.ietf.org>
Subject: Re: RADEXT WG Consensus call on acceptance of RADSEC as a work item

 I support having RADSEC as a WG item.

Klaas

--------------------------------------------------------------------------------
From: Stephen Hanna
Sent: Sunday, March 16, 2008 4:35 PM
To: Bernard_Aboba@hotmail.com ; radiusext@ops.ietf.org
Subject: RE: RADEXT WG Consensus call on acceptance of RADSEC as a work item


I am in favor of having RADSEC as a RADEXT WG work item. This specification clearly meets the needs of an important group of RADIUS users.

Thanks,

Steve

--------------------------------------------------------------------------------
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard_Aboba@hotmail.com
Sent: Friday, March 14, 2008 11:10 AM
To: radiusext@ops.ietf.org
Subject: RADEXT WG Consensus call on acceptance of RADSEC as a work item


This is a consensus call for acceptance of RADSEC (and the Status Update draft) as a RADEXT WG work item. The consensus call will last until March 28, 2008. Please send email to the list stating whether you are in favor or opposed to accepting RADSEC as a RADEXT WG work item.

--
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/>