1 / 7

RADIUS MIB Updates for IPv6

This document provides updates for RADIUS Management Information Base (MIB) for IPv6, based on discussions and recommendations from the RADEXT working group.

yancym
Download Presentation

RADIUS MIB Updates for IPv6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RADIUS MIB Updates for IPv6 IETF-63 RADEXT WG August 3, 2005 David B. Nelson

  2. Draft Status • -00 drafts were reviewed by Ops Area MIB Doctors • MIB Doctor recommendations discussed on the RADEXT WG list • Consensus obtained to accept the recommendations • -01 drafts incorporated the requested changes

  3. The Drafts • All four drafts contain very similar changes • The drafts now purport to Update their respective predecessor RFCs. • Draft repository locations: • http://www.ietf.org/internet-drafts/draft-nelson-rfc2618bis-01.txt • http://www.ietf.org/internet-drafts/draft-nelson-rfc2619bis-01.txt • http://www.ietf.org/internet-drafts/draft-nelson-rfc2620bis-01.txt • http://www.ietf.org/internet-drafts/draft-nelson-rfc2621bis-01.txt

  4. Summary of changes • Abandoned the method of using table augmentation • Deprecated the table(s) including IPv4 only IP-Address textual convention • Added new tables, mirroring the old ones • Old table(s) can continue to be used for IPv4-only implementations or for backwards compatibility with older SNMP management applications

  5. Specific Usage Guidelines Text • Example: • 6. Deprecated Objects The deprecated table in this MIB is carried forward from RFC 2618 [RFC2618]. There are two conditions under which it MAY be desirable for managed entities to continue to support the deprecated table: 1. The managed entity only supports IPv4 address formats. 2. The managed entity supports both IPv4 and IPv6 address formats, and the deprecated table is supported for backwards compatibility with older management stations. This option SHOULD only be used when the IP addresses in the new table are in IPv4 format and can accurately be represented in both the new table and the deprecated table. Managed entities SHOULD NOT instantiate the deprecated table containing IPv4-only address objects when the RADIUS server address represented in the table row is not an IPv4 address. Managed entities SHOULD NOT return inaccurate values of IP address or SNMP object access errors for IPv4-only address objects in otherwise populated tables.

  6. The New Address Objects • Example: • radiusAuthServerInetAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of address format used for the radiusAuthServerInetAddress object." ::= { radiusAuthServerExtEntry 2 }radiusAuthServerInetAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of the RADIUS authentication server referred to in this table entry, using the IPv6 adddess format." ::= { radiusAuthServerExtEntry 3 }radiusAuthClientServerInetPortNumber OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-only STATUS current DESCRIPTION "The UDP port the client is using to send requests to this server." ::= { radiusAuthServerExtEntry 4 }

  7. Next Steps • Are these documents ready for acceptance as WG work items? • If so, are they ready for WG Last call? • Should the drafts Update or Obsolete their predecessor RFCs?

More Related