RE: RADIUS drafts review -- LAN attributes

["Nelson, David" <dnelson@enterasys.com>]

Farid writes...

> I think everyone should participate in scrubbing the LAN attributes,
and
> help finalize their definition, format/syntax ...  Whether or not we
> need a single or multiple drafts to express these attributes, we can
> discuss it in parallel.  I think our primary focus should be to
identify
> a list of LAN attributes that we need to standardize, and work on
their
> definition.  Your comment?

That sounds fine.  If we can organize that effort to occur on the list,
and we have some active participants, then let's start...   Actual
editing of the drafts will still require an individual to act as editor,
of course.

Keep in mind, however, the WG work items and milestones from the draft
charter.

Dec 04  Updated RADIUS MIBs submitted for publication.
Dec 04  RADIUS design guidelines submitted as an Informational RFC.
Dec 04  SIP RADIUS authentication draft submitted as a Proposed Standard
        RFC.
Feb 05  RADIUS implementation issues and fixes submitted as an
        Informational RFC.
Feb 05  WLAN attributes draft submitted as a Proposed Standard RFC.
Feb 05  RFC 2486bis submitted as a Proposed Standard.
Dec 05  LAN attributes draft submitted as a Proposed Standard RFC.
Dec 05  RADIUS Prepaid draft submitted as a Proposed Standard RFC.

Before we can close on the LAN Attributes draft (or others) we need to
complete the design guidelines draft.  Certainly, we can work in
parallel, to the extent that resources permit.  The LAN Attributes draft
is scheduled to be completed in December of 2005.

-- Dave



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