New Prepaid Draf version 3 is now available.

[Avi Lior <avi@bridgewatersystems.com>]

The draft is available
http://www.ietf.org/internet-drafts/draft-lior-radius-prepaid-extensions-03.
txt 

Whats new:

Formalized the required set of attributes -- there are three attributes.
Addes discussion on why the the prepaid approach in this document is more
robust then doing prepaid using existing RADIUS attributes.

There is already a version 4 in the works......

============================================
STATEMENT of Compliance to Proposed Charter
============================================

The draft is 100% compatible with the RADIUS EXT Proposed Charter

Item 1:  All work MUST be backward compatible with exiting RADIUS RFCs.

This draft is 100% backwards compatible with existing RADIUS RFCs.

Item 2: No new RADIUS transports

No new transports were introdcued.

Item 3:  No changes will be considered to the RADIUS attribute format.

No changes were made to any RADIUS attribute format.  The new attriutes are
of type STRING.

Item 4: No new RADIUS data types will be defined.

No new RADIUS  data type was introduced.

Item 5: The RADIUS maximum packet size (4K) will not be increaded.

Packet size remains less the 4K.

Item 6: No RADIUS attribute "sub-types" will be defined.

No new attribute called "sub-types" was defined or introduced.  All
attributes are based on RADIUS type STRING.

Item 7: No new RADIUS secuirty mechanism will be defined.

No new security mechanisms was introduced.

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