Re: RADEXT charter for comment...

[stefaan.de_cnodder@alcatel.be]

> 
> - MIB update.  RFC 2618-2621 lack IPv6 compatiblity and modest
>   changes are required to address this issue.
> 

Would it be interesting to extend this item to include MIB updates to
support disconnect and CoA messages as well? 

Another question: Is the draft draft-lior-radius-redirection-00 also in the
scope of the charter? Prepaid services can make use of it, but there are
more applications. Or is this something that can be done after the initial
work on "simple prepaid" has been completed?

> 
> * This WG will not be chartered until sufficient resources can be
>   demonstrated to be available to guarantee a high probability of
>   success.  This includes recruitment of a core of editors and
>   reviewers with significant IETF experience and demonstrated time
>   commitment.
> 

I volunteer to review prepaid, LAN attributes, and MIB.

regards,

Stefaan


> * All drafts will need to undergo review prior to acceptance as WG work
>   items, which includes demonstration that the drafts are backward
>   compatible with RADIUS RFCs and are compatible with equivalent
>   facilities in Diameter.
> 
> * The WG will utilize an issue tracking system.
> 
> * XML to RFC will be used in production of documents.  This enables
>   production of HTML and text files from a single source file as
>   well as automated production of difference files.
> 
> --
> 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/>