draft-ietf-ips-auth-mib-05.txt   draft-ietf-ips-auth-mib-06.txt 
Internet Draft Mark Bakke Internet Draft Mark Bakke
<draft-ietf-ips-auth-mib-05.txt> Cisco Systems <draft-ietf-ips-auth-mib-06.txt> Cisco Systems
Expires June 2004 Jim Muchow Expires July 2005
James Muchow
Qlogic Corp.
December 2003 January 2005
Definitions of Managed Objects for User Identity Authorization Definitions of Managed Objects for User Identity Authorization
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, I certify that any applicable
of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.html. http://www.ietf.org/ietf/1id-abstracts.html.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets. for use with network management protocols in TCP/IP based internets.
In particular it defines objects for managing user identities and the In particular it defines objects for managing user identities and the
names, addresses, and credentials required manage access control, for names, addresses, and credentials required manage access control, for
use with various protocols. This draft was motivated by the need for use with various protocols. This draft was motivated by the need for
the configuration of authorized user identities for the iSCSI the configuration of authorized user identities for the iSCSI
protocol, but has been extended to be useful for other protocols that protocol, but has been extended to be useful for other protocols that
have similar requirements. It is important to note that this MIB have similar requirements. It is important to note that this MIB
provides only the set of identities to be used within access lists; module provides only the set of identities to be used within access
it is the responsibility of other MIBs making use of this one to tie lists; it is the responsibility of other MIB modules making use of
them to their own access lists or other authorization control this one to tie them to their own access lists or other authorization
methods. control methods.
Acknowledgments Acknowledgments
In addition to the authors, several people contributed to the In addition to the authors, several people contributed to the
development of this MIB through discussions of authentication, development of this MIB module through discussions of authentication,
authorization, and access within the iSCSI MIB and security teams, authorization, and access within the iSCSI MIB module and security
including John Hufferd, Marjorie Krueger, Keith McCloghrie, Tom teams, including John Hufferd, Marjorie Krueger, Keith McCloghrie,
McSweeney, Steve Senum, and Josh Tseng. Thanks also to Bill Tom McSweeney, Steve Senum, and Josh Tseng. Thanks also to Bill
Studenmund (Wasabi Systems) for adding the Kerberos method, and to Studenmund (Wasabi Systems) for adding the Kerberos method, and to
Ayman Ghanem for finding and suggesting changes to several problems Ayman Ghanem for finding and suggesting changes to several problems
found in the MIB. found in the MIB module.
Thanks especially to Keith McCloghrie for serving as advisor for this Thanks especially to Keith McCloghrie for serving as advisor for this
MIB. MIB module.
Table of Contents Table of Contents
1. Introduction..............................................2 1. Introduction..............................................3
2. The Internet-Standard Management Framework................3 2. The Internet-Standard Management Framework................3
3. Relationship to Other MIBs................................3 3. Relationship to Other MIB Modules.........................3
4. Discussion................................................4 4. Discussion................................................4
4.1. Authorization MIB Object Model..........................4 4.1. Authorization MIB Object Model..........................4
4.2. ipsAuthInstance.........................................5 4.2. ipsAuthInstance.........................................5
4.3. ipsAuthIdentity.........................................5 4.3. ipsAuthIdentity.........................................6
4.4. ipsAuthIdentityName.....................................5 4.4. ipsAuthIdentityName.....................................6
4.5. ipsAuthIdentityAddress..................................6 4.5. ipsAuthIdentityAddress..................................6
4.6. ipsAuthCredential.......................................7 4.6. ipsAuthCredential.......................................7
4.7. IP, Fibre Channel, and Other Addresses..................7 4.7. IP, Fibre Channel, and Other Addresses..................8
4.8. Descriptors: Using OIDs in Place of Enumerated Types....8 4.8. Descriptors: Using OIDs in Place of Enumerated Types....8
4.9. Notifications...........................................8 4.9. Notifications...........................................8
5. MIB Definitions...........................................9 5. MIB Definitions...........................................9
6. Security Considerations..................................27 6. Security Considerations..................................30
7. Normative References.....................................28 7. IANA Considerations......................................31
8. Informative References...................................28 7.1. OID Assignment.........................................31
9. Authors' Addresses.......................................29 8. Normative References.....................................31
10. IPR Notice..............................................29 9. Informative References...................................32
11. Full Copyright Notice...................................30 10. Authors' Addresses......................................32
11. IPR Notice..............................................32
12. Full Copyright Notice...................................33
1. Introduction 1. Introduction
This MIB will be used to configure and/or look at the configuration This MIB module will be used to configure and/or look at the
of user identities and their credential information. For the configuration of user identities and their credential information.
purposes of this MIB, a "user" identity does not need to be an actual For the purposes of this MIB module, a "user" identity does not need
person; a user can also be a host, an application, a cluster of to be an actual person; a user can also be a host, an application, a
hosts, or any other identifiable entity that can be authorized to cluster of hosts, or any other identifiable entity that can be
access a resource. authorized to access a resource.
Most objects in this MIB have a MAX-ACCESS of read-create; the MIB is Most objects in this MIB module have a MAX-ACCESS of read-create;
intended to allow configuration of user identities and their names, this module is intended to allow configuration of user identities and
addresses, and credentials. MIN-ACCESS for all objects is read-only their names, addresses, and credentials. MIN-ACCESS for all objects
for those implementations that configure through other means, but is read-only for those implementations that configure through other
require the ability to monitor user identities. means, but require the ability to monitor user identities.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Relationship to Other MIBs 3. Relationship to Other MIB Modules
The identity authorization MIB does not directly address objects The identity authorization MIB module does not directly address
within other MIBs. The identity address objects contain IPv4, IPv6, objects within other modules. The identity address objects contain
or other address types, and as such may be indirectly related to IPv4, IPv6, or other address types, and as such may be indirectly
objects within the IPv4 MIB [RFC1213] [RFC2011] or IPv6 [RFC2465] related to objects within the IPv4 [RFC1213] [RFC2011] or IPv6
MIB. [RFC2465] MIB modules.
This MIB does not provide actual authorization or access control This MIB module does not provide actual authorization or access
lists; it provides a means to identify entities that can be included control lists; it provides a means to identify entities that can be
in other authorization lists. This should generally be done in MIBs included in other authorization lists. This should generally be done
that reference identities in this one. It also does not cover login in MIB modules that reference identities in this one. It also does
or authentication failure statistics or notifications, as these are not cover login or authentication failure statistics or
all fairly application-specific, and are not generic enough to notifications, as these are all fairly application-specific, and are
include here. not generic enough to include here.
The user identity objects within this MIB are typically referenced The user identity objects within this module are typically referenced
from other MIBs by a RowPointer within that MIB. A MIB containing from other modules by a RowPointer within that module. A module
resources for which it requires a list of authorized user identities containing resources for which it requires a list of authorized user
may create such a list, with a single RowPointer within each list identities may create such a list, with a single RowPointer within
element pointing to a user identity within this MIB. This is neither each list element pointing to a user identity within this module.
required nor restricted by this MIB. This is neither required nor restricted by this MIB module.
4. Discussion 4. Discussion
This MIB structure is intended to allow the configuration of a list This MIB module structure is intended to allow the configuration of a
of user identities, each with a list of names, addresses, list of user identities, each with a list of names, addresses,
credentials, and certificates which when combined will distinguish credentials, and certificates which when combined will distinguish
that identity. that identity.
The authorization MIB is structured around two primary "objects", the The authorization MIB module is structured around two primary
authorization instance, and the identity, which serve as containers "objects", the authorization instance, and the identity, which serve
for the remainder of the objects. This section contains a brief as containers for the remainder of the objects. This section
description of the "object" hierarchy and a description of each contains a brief description of the "object" hierarchy and a
object, followed by a discussion of the actual SNMP table structure description of each object, followed by a discussion of the actual
within the objects. SNMP table structure within the objects.
4.1. Authorization MIB Object Model 4.1. Authorization MIB Object Model
The top-level object in this structure is the authorization instance, The top-level object in this structure is the authorization instance,
which "contains" all of the other objects. The indexing hierarchy of which "contains" all of the other objects. The indexing hierarchy of
this MIB looks like: this module looks like:
ipsAuthInstance ipsAuthInstance
-- A distinct authorization entity within the managed system. -- A distinct authorization entity within the managed system.
-- Most implementations will have just one of these. -- Most implementations will have just one of these.
ipsAuthIdentity ipsAuthIdentity
-- A user identity, consisting of a set of identity names, -- A user identity, consisting of a set of identity names,
-- addresses, and credentials reflected in the following -- addresses, and credentials reflected in the following
-- objects: -- objects:
ipsAuthIdentityName ipsAuthIdentityName
-- A name for a user identity. A name should be globally -- A name for a user identity. A name should be globally
skipping to change at page 5, line 10 skipping to change at page 5, line 17
-- Kerberos-specific attributes -- Kerberos-specific attributes
Each identity contains the information necessary to identify a Each identity contains the information necessary to identify a
particular end-point that wishes to access a service, such as iSCSI. particular end-point that wishes to access a service, such as iSCSI.
An identity can contain multiple names, addresses, and credentials. An identity can contain multiple names, addresses, and credentials.
4.2. ipsAuthInstance 4.2. ipsAuthInstance
The ipsAuthInstanceAttributesTable is the primary table of the The ipsAuthInstanceAttributesTable is the primary table of the
authorization MIB. Every other table entry in this MIB includes the authorization MIB module. Every other table entry in this module
index of an ipsAuthInstanceAttributesEntry as its primary index. An includes the index of an ipsAuthInstanceAttributesEntry as its
authorization instance is basically a managed set of identities. primary index. An authorization instance is basically a managed set
of identities.
Many implementations will include just one authorization instance row Many implementations will include just one authorization instance row
in this table. However, there will be cases where multiple rows in in this table. However, there will be cases where multiple rows in
this table may be used: this table may be used:
- A large system may be "partitioned" into multiple, distinct virtual - A large system may be "partitioned" into multiple, distinct virtual
systems, perhaps sharing the SNMP agent but not their lists of systems, perhaps sharing the SNMP agent but not their lists of
identities. Each virtual system would have its own authorization identities. Each virtual system would have its own authorization
instance. instance.
- A set of stackable systems, each with their own set of identities, - A set of stackable systems, each with their own set of identities,
may be represented by a common SNMP agent. Each individual system may be represented by a common SNMP agent. Each individual system
would have its own authorization instance. would have its own authorization instance.
- Multiple protocols, each with their own set of identities, may - Multiple protocols, each with their own set of identities, may
exist within a single system and be represented by a single SNMP exist within a single system and be represented by a single SNMP
agent. In this case, each protocol may have its own authorization agent. In this case, each protocol may have its own authorization
instance. instance.
An entry in this table is typically referenced by its name
(ipsAuthInstDescr), which should be displayed to the user by the
management station. When an implementation supports only one entry
in this table, the description may be returned as a zero-length
string.
An end user will generally use name and description fields in
identifying rows within this and other tables. Therefore,
persistence of index values across reboots is not required in this
MIB module. However, index values for rows that have been deleted
must not be reused before a reboot.
4.3. ipsAuthIdentity 4.3. ipsAuthIdentity
The ipsAuthIdentAttributesTable contains one entry for each The ipsAuthIdentAttributesTable contains one entry for each
configured user identity. The identity contains only a description configured user identity. The identity contains only a description
of what the identity is used for; its attributes are all contained in of what the identity is used for; its attributes are all contained in
other tables, since they can each have multiple values. other tables, since they can each have multiple values.
Other MIBs containing lists of users authorized to access a Other MIB modules containing lists of users authorized to access a
particular resource should generally contain a RowPointer to the particular resource should generally contain a RowPointer to the
ipsAuthIdentAttributesEntry which will, if authenticated, be allowed ipsAuthIdentAttributesEntry which will, if authenticated, be allowed
access to the resource. access to the resource.
All other table entries make use of the indices to this table as All other table entries make use of the indices to this table as
their primary indices. their primary indices.
4.4. ipsAuthIdentityName 4.4. ipsAuthIdentityName
The ipsAuthIdentNameAttributesTable contains a list of UTF-8 names, The ipsAuthIdentNameAttributesTable contains a list of UTF-8 names,
each of which belong to, and may be used to identify, a particular each of which belong to, and may be used to identify, a particular
identity in the authIdentity table. identity in the authIdentity table.
Implementations making use of the authorization MIB may identify Implementations making use of the authorization MIB module may
their resources by names, addresses, or both. A name is typically a identify their resources by names, addresses, or both. A name is
unique (within the required scope), unchanging identifier for a typically a unique (within the required scope), unchanging identifier
resource. It will normally meet some or all of the requirements for a for a resource. It will normally meet some or all of the requirements
Uniform Resource Name [RFC1737], although a name in the context of for a Uniform Resource Name [RFC1737], although a name in the context
this MIB does not need to be a URN. Identifiers that typically of this MIB module does not need to be a URN. Identifiers that
change over time should generally be placed into the typically change over time should generally be placed into the
ipsAuthIdentityAddress table; names that have no uniqueness ipsAuthIdentityAddress table; names that have no uniqueness
properties should usually be placed into the description attribute properties should usually be placed into the description attribute
for the identity. for the identity.
An example of an identity name is the iSCSI Name, defined in [ISCSI]. An example of an identity name is the iSCSI Name, defined in
[RFC3720].
If this table contains no entries associated with a particular user If this table contains no entries associated with a particular user
identity, the implementation does not need to check any name identity, the implementation does not need to check any name
parameters when verifying that identity. If the table contains parameters when verifying that identity. If the table contains
multiple entries associated with a particular user identity, the multiple entries associated with a particular user identity, the
implementation should consider a match with any one of these entries implementation should consider a match with any one of these entries
to be valid. to be valid.
4.5. ipsAuthIdentityAddress 4.5. ipsAuthIdentityAddress
skipping to change at page 6, line 50 skipping to change at page 7, line 23
makes sense to the application. makes sense to the application.
Matching any address within any range within the list associated with Matching any address within any range within the list associated with
a particular identity is considered to be a valid match. If no a particular identity is considered to be a valid match. If no
entries are present in this list for a given identity, its address is entries are present in this list for a given identity, its address is
automatically assumed to match the identity. automatically assumed to match the identity.
Netmasks are not supported, since an address range can express the Netmasks are not supported, since an address range can express the
same thing with more flexibility. An application specifying same thing with more flexibility. An application specifying
addresses using network masks may do so, and convert to and from addresses using network masks may do so, and convert to and from
address ranges when reading or writing this MIB. address ranges when reading or writing this MIB module.
4.6. ipsAuthCredential 4.6. ipsAuthCredential
The ipsAuthCredentialAttributesTable contains a list of credentials, The ipsAuthCredentialAttributesTable contains a list of credentials,
each of which may be used to verify a particular identity. each of which may be used to verify a particular identity.
Each credential contains an authentication method to be used, such as Each credential contains an authentication method to be used, such as
CHAP [RFC1994], SRP [RFC2945], or Kerberos [RFC1510]. This attribute CHAP [RFC1994], SRP [RFC2945], or Kerberos [RFC1510]. This attribute
contains an object identifier instead of an enumerated type, allowing contains an object identifier instead of an enumerated type, allowing
other MIBs to add their own authentication methods, without modifying other MIB modules to add their own authentication methods, without
this MIB. modifying this MIB module.
For each entry in this table, there will exist an entry in another For each entry in this table, there will exist an entry in another
table containing its attributes. The table in which to place the table containing its attributes. The table in which to place the
entry depends on the AuthMethod attribute: entry depends on the AuthMethod attribute:
CHAP If the AuthMethod is set to the CHAP OID, an entry using the CHAP If the AuthMethod is set to the CHAP OID, an entry using the
same indices as the ipsAuthCredential will exist in the same indices as the ipsAuthCredential will exist in the
ipsAuthCredChap table, which contains the CHAP username. ipsAuthCredChap table, which contains the CHAP username.
SRP If the AuthMethod is set to the SRP OID, an entry using the SRP If the AuthMethod is set to the SRP OID, an entry using the
same indices as the ipsAuthCredential will exist in the same indices as the ipsAuthCredential will exist in the
ipsAuthCredSrp table, which contains the SRP username. ipsAuthCredSrp table, which contains the SRP username.
Kerberos If the AuthMethod is set to the Kerberos OID, an entry using Kerberos If the AuthMethod is set to the Kerberos OID, an entry using
the same indices as the ipsAuthCredential will exist in the the same indices as the ipsAuthCredential will exist in the
ipsAuthCredKerberos table, which contains the Kerberos ipsAuthCredKerberos table, which contains the Kerberos
principal. principal.
Other If the AuthMethod is set to any OID not defined in this MIB, Other If the AuthMethod is set to any OID not defined in this
an entry using the same indices as the ipsAuthCredential module, an entry using the same indices as the
entry should be placed in the other MIB that define whatever ipsAuthCredential entry should be placed in the other module
attributes are needed for that type of credential. that define whatever attributes are needed for that type of
credential.
4.7. IP, Fibre Channel, and Other Addresses 4.7. IP, Fibre Channel, and Other Addresses
The IP addresses in this MIB are represented by two attributes, one The IP addresses in this MIB module are represented by two
of type AddressFamilyNumbers, and the other of type AuthAddress. attributes, one of type AddressFamilyNumbers, and the other of type
Each address can take on any of the types within the list of address AuthAddress. Each address can take on any of the types within the
family numbers; the most likely being IPv4, IPv6, or one of the Fibre list of address family numbers; the most likely being IPv4, IPv6, or
Channel address types. one of the Fibre Channel address types.
The type AuthAddress is an octet string. If the address family is The type AuthAddress is an octet string. If the address family is
IPv4 or IPv6, the format is taken from the InetAddress specified in IPv4 or IPv6, the format is taken from the InetAddress specified in
[RFC3291]. If the address family is one of the Fibre Channel types, [RFC3291]. If the address family is one of the Fibre Channel types,
the format is identical to the FcNameIdOrZero type defined in the format is identical to the FcNameIdOrZero type defined in
[FCMGMT]. [FCMGMT].
4.8. Descriptors: Using OIDs in Place of Enumerated Types 4.8. Descriptors: Using OIDs in Place of Enumerated Types
Some attributes, particularly the authentication method attribute, Some attributes, particularly the authentication method attribute,
would normally require an enumerated type. However, implementations would normally require an enumerated type. However, implementations
will likely need to add new authentication method types of their own, will likely need to add new authentication method types of their own,
without extending this MIB. To make this work, the MIB defines a set without extending this MIB module. To make this work, this module
of object identities within ipsAuthDescriptors. Each of these object defines a set of object identities within ipsAuthDescriptors. Each
identities is basically an enumerated type. of these object identities is basically an enumerated type.
Attributes that make use of these object identities have a value Attributes that make use of these object identities have a value
which is an OID instead of an enumerated type. These OIDs can either which is an OID instead of an enumerated type. These OIDs can either
indicate the object identities defined in this MIB, or object indicate the object identities defined in this module, or object
identities defined elsewhere, such as in an enterprise MIB. Those identities defined elsewhere, such as in an enterprise MIB module.
implementations that add their own authentication methods should also Those implementations that add their own authentication methods
define a corresponding object identity for each of these methods should also define a corresponding object identity for each of these
within their own enterprise MIB, and return its OID whenever one of methods within their own enterprise MIB module, and return its OID
these attributes is using that method. whenever one of these attributes is using that method.
4.9. Notifications 4.9. Notifications
Monitoring of authentication failures and other notification events Monitoring of authentication failures and other notification events
are outside the scope of this MIB, as they are generally application- are outside the scope of this MIB module, as they are generally
specific. No notifications are provided or required. application-specific. No notifications are provided or required.
5. MIB Definitions 5. MIB Definitions
IPS-AUTH-MIB DEFINITIONS ::= BEGIN IPS-AUTH-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Unsigned32, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Unsigned32,
experimental experimental
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, AutonomousType TEXTUAL-CONVENTION, RowStatus, AutonomousType, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 2571 FROM SNMP-FRAMEWORK-MIB -- RFC 2571
AddressFamilyNumbers AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB
; ;
ipsAuthModule MODULE-IDENTITY ipsAuthModule MODULE-IDENTITY
LAST-UPDATED "200312090000Z" -- December 9, 2003 LAST-UPDATED "200501250000Z" -- January 25, 2005
ORGANIZATION "IETF IPS Working Group" ORGANIZATION "IETF IPS Working Group"
CONTACT-INFO CONTACT-INFO
" "
Mark Bakke Mark Bakke
Postal: Cisco Systems, Inc Postal: Cisco Systems, Inc
6450 Wedgwood Road, Suite 130 7900 International Drive, Suite 400
Maple Grove, MN Bloomington, MN
USA 55311 USA 55425
Tel: +1 763-398-1000
Fax: +1 763-398-1001
E-mail: mbakke@cisco.com E-mail: mbakke@cisco.com
Jim Muchow James Muchow
E-mail: jamesdmuchow@yahoo.com" Postal: Qlogic Corp.
6321 Bury Dr.
Eden Prairie, MN
USA 55346
E-Mail: james.muchow@qlogic.com"
DESCRIPTION DESCRIPTION
"The IP Storage Authorization MIB module." "The IP Storage Authorization MIB module.
REVISION "200312090000Z" -- December 9, 2003 Copyright (C) The Internet Society (2005). This version of
this MIB module is part of RFC yyyy; see the RFC itself for
full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200501250000Z" -- January 25, 2005
DESCRIPTION DESCRIPTION
"Initial revision published as RFC xxxx." "Initial version of the IP Storage Authentication MIB module"
::= { mib-2 xx }
-- in case you want to COMPILE -- in case you want to COMPILE
::= { experimental 99999 } --::= { experimental 99999 }
ipsAuthNotifications OBJECT IDENTIFIER ::= { ipsAuthModule 0 }
ipsAuthObjects OBJECT IDENTIFIER ::= { ipsAuthModule 1 } ipsAuthObjects OBJECT IDENTIFIER ::= { ipsAuthModule 1 }
ipsAuthNotifications OBJECT IDENTIFIER ::= { ipsAuthModule 2 } ipsAuthConformance OBJECT IDENTIFIER ::= { ipsAuthModule 2 }
ipsAuthConformance OBJECT IDENTIFIER ::= { ipsAuthModule 3 }
-- Textual Conventions -- Textual Conventions
IpsAuthAddress ::= TEXTUAL-CONVENTION IpsAuthAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IP Storage requires the use of address information "IP Storage requires the use of address information
that uses not only the InetAddress type defined in the that uses not only the InetAddress type defined in the
INET-ADDRESS-MIB, but also Fibre Channel type defined INET-ADDRESS-MIB, but also Fibre Channel type defined
in the Fibre Channel Management MIB. Although these in the Fibre Channel Management MIB. Although these
address types are recognized in the IANA Address Family address types are recognized in the IANA Address Family
Numbers MIB, the addressing mechanisms have not been Numbers MIB, the addressing mechanisms have not been
merged into a well-known, common type. This data type, merged into a well-known, common type. This data type,
the IpsAuthAddress, performs this function for this MIB." the IpsAuthAddress, performs this function for this MIB
module."
REFERENCE REFERENCE
"IANA-ADDRESS-FAMILY-NUMBERS-MIB; "IANA-ADDRESS-FAMILY-NUMBERS-MIB;
INET-ADDRESS-MIB (RFC 2851); INET-ADDRESS-MIB (RFC 2851);
Fibre Channel Management MIB (presently defined in Fibre Channel Management MIB (presently defined in
draft-ietf-ips-fcmgmt-mib-01.txt)." draft-ietf-ips-fcmgmt-mib-01.txt)."
SYNTAX OCTET STRING (SIZE(0..255)) SYNTAX OCTET STRING (SIZE(0..255))
------------------------------------------------------------------------ ------------------------------------------------------------------------
ipsAuthDescriptors OBJECT IDENTIFIER ::= { ipsAuthObjects 1 } ipsAuthDescriptors OBJECT IDENTIFIER ::= { ipsAuthObjects 1 }
skipping to change at page 12, line 9 skipping to change at page 12, line 18
ipsAuthInstIndex Unsigned32, ipsAuthInstIndex Unsigned32,
ipsAuthInstDescr SnmpAdminString ipsAuthInstDescr SnmpAdminString
} }
ipsAuthInstIndex OBJECT-TYPE ipsAuthInstIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer used to uniquely identify a "An arbitrary integer used to uniquely identify a
particular authorization instance." particular authorization instance. This value does
not need to be preserved across reboots, and must
not be reused for a new row before a reboot."
::= { ipsAuthInstanceAttributesEntry 1 } ::= { ipsAuthInstanceAttributesEntry 1 }
ipsAuthInstDescr OBJECT-TYPE ipsAuthInstDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An octet string, determined by the implementation to "An octet string, determined by the implementation to
describe the authorization instance. When only a single describe the authorization instance. When only a single
instance is present, this object may be set to the instance is present, this object may be set to the
zero-length string; with multiple authorization zero-length string; with multiple authorization
instances, it may be used in an implementation-dependent instances, it may be set in an implementation-dependent
manner to describe the purpose of the respective instance." manner to describe the purpose of the respective instance."
::= { ipsAuthInstanceAttributesEntry 2 } ::= { ipsAuthInstanceAttributesEntry 2 }
ipsAuthIdentity OBJECT IDENTIFIER ::= { ipsAuthObjects 3 } ipsAuthIdentity OBJECT IDENTIFIER ::= { ipsAuthObjects 3 }
-- User Identity Attributes Table -- User Identity Attributes Table
ipsAuthIdentAttributesTable OBJECT-TYPE ipsAuthIdentAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpsAuthIdentAttributesEntry SYNTAX SEQUENCE OF IpsAuthIdentAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 13, line 4 skipping to change at page 13, line 14
DESCRIPTION DESCRIPTION
"An entry (row) containing management information "An entry (row) containing management information
describing a user identity within an authorization describing a user identity within an authorization
instance on this node." instance on this node."
INDEX { ipsAuthInstIndex, ipsAuthIdentIndex } INDEX { ipsAuthInstIndex, ipsAuthIdentIndex }
::= { ipsAuthIdentAttributesTable 1 } ::= { ipsAuthIdentAttributesTable 1 }
IpsAuthIdentAttributesEntry ::= SEQUENCE { IpsAuthIdentAttributesEntry ::= SEQUENCE {
ipsAuthIdentIndex Unsigned32, ipsAuthIdentIndex Unsigned32,
ipsAuthIdentDescription SnmpAdminString, ipsAuthIdentDescription SnmpAdminString,
ipsAuthIdentRowStatus RowStatus ipsAuthIdentRowStatus RowStatus,
ipsAuthIdentStorageType StorageType
} }
ipsAuthIdentIndex OBJECT-TYPE ipsAuthIdentIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer used to uniquely identify a "An arbitrary integer used to uniquely identify a
particular identity instance within an authorization particular identity instance within an authorization
instance present on the node." instance present on the node. This value does not
need to be preserved across reboots, and must not
be used for a new row before a reboot."
::= { ipsAuthIdentAttributesEntry 1 } ::= { ipsAuthIdentAttributesEntry 1 }
ipsAuthIdentDescription OBJECT-TYPE ipsAuthIdentDescription OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An octet string describing this particular identity." "An octet string describing this particular identity."
::= { ipsAuthIdentAttributesEntry 2 } ::= { ipsAuthIdentAttributesEntry 2 }
ipsAuthIdentRowStatus OBJECT-TYPE ipsAuthIdentRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This field allows entries to be dynamically added and "This field allows entries to be dynamically added and
removed from this table via SNMP." removed from this table via SNMP. When adding a row to
this table, all non-Index/RowStatus objects must be set.
Rows may be discarded using RowStatus."
::= { ipsAuthIdentAttributesEntry 3 } ::= { ipsAuthIdentAttributesEntry 3 }
ipsAuthIdentStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this row. Rows in this table that were
created through an external process may have a storage type of
readOnly or permanent."
DEFVAL { nonVolatile }
::= { ipsAuthIdentAttributesEntry 4 }
ipsAuthIdentityName OBJECT IDENTIFIER ::= { ipsAuthObjects 4 } ipsAuthIdentityName OBJECT IDENTIFIER ::= { ipsAuthObjects 4 }
-- User Initiator Name Attributes Table -- User Initiator Name Attributes Table
ipsAuthIdentNameAttributesTable OBJECT-TYPE ipsAuthIdentNameAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpsAuthIdentNameAttributesEntry SYNTAX SEQUENCE OF IpsAuthIdentNameAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of unique names that can be used to positively "A list of unique names that can be used to positively
skipping to change at page 14, line 15 skipping to change at page 14, line 41
applicable to a unique identity name which can be used applicable to a unique identity name which can be used
to identify a user identity within a particular to identify a user identity within a particular
authorization instance." authorization instance."
INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, INDEX { ipsAuthInstIndex, ipsAuthIdentIndex,
ipsAuthIdentNameIndex } ipsAuthIdentNameIndex }
::= { ipsAuthIdentNameAttributesTable 1 } ::= { ipsAuthIdentNameAttributesTable 1 }
IpsAuthIdentNameAttributesEntry ::= SEQUENCE { IpsAuthIdentNameAttributesEntry ::= SEQUENCE {
ipsAuthIdentNameIndex Unsigned32, ipsAuthIdentNameIndex Unsigned32,
ipsAuthIdentName SnmpAdminString, ipsAuthIdentName SnmpAdminString,
ipsAuthIdentNameRowStatus RowStatus ipsAuthIdentNameRowStatus RowStatus,
ipsAuthIdentNameStorageType StorageType
} }
ipsAuthIdentNameIndex OBJECT-TYPE ipsAuthIdentNameIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer used to uniquely identify a "An arbitrary integer used to uniquely identify a
particular identity name instance within an particular identity name instance within an
ipsAuthIdentity within an authorization instance." ipsAuthIdentity within an authorization instance. This
value does not need to be preserved across reboots,
and must not be used for a new row before a reboot."
::= { ipsAuthIdentNameAttributesEntry 1 } ::= { ipsAuthIdentNameAttributesEntry 1 }
ipsAuthIdentName OBJECT-TYPE ipsAuthIdentName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A character string which is the unique name of an "A character string which is the unique name of an
identity that may be used to identify this ipsAuthIdent identity that may be used to identify this ipsAuthIdent
entry." entry."
::= { ipsAuthIdentNameAttributesEntry 2 } ::= { ipsAuthIdentNameAttributesEntry 2 }
ipsAuthIdentNameRowStatus OBJECT-TYPE ipsAuthIdentNameRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This field allows entries to be dynamically added and "This field allows entries to be dynamically added and
removed from this table via SNMP." removed from this table via SNMP. When adding a row to
this table, all non-Index/RowStatus objects must be set.
Rows may be discarded using RowStatus."
::= { ipsAuthIdentNameAttributesEntry 3 } ::= { ipsAuthIdentNameAttributesEntry 3 }
ipsAuthIdentNameStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this row. Rows in this table that were
created through an external process may have a storage type of
readOnly or permanent."
DEFVAL { nonVolatile }
::= { ipsAuthIdentNameAttributesEntry 4 }
ipsAuthIdentityAddress OBJECT IDENTIFIER ::= { ipsAuthObjects 5 } ipsAuthIdentityAddress OBJECT IDENTIFIER ::= { ipsAuthObjects 5 }
-- User Initiator Address Attributes Table -- User Initiator Address Attributes Table
ipsAuthIdentAddrAttributesTable OBJECT-TYPE ipsAuthIdentAddrAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpsAuthIdentAddrAttributesEntry SYNTAX SEQUENCE OF IpsAuthIdentAddrAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of address ranges that are allowed to serve "A list of address ranges that are allowed to serve
skipping to change at page 15, line 34 skipping to change at page 16, line 29
within an authorization instance on this node." within an authorization instance on this node."
INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, INDEX { ipsAuthInstIndex, ipsAuthIdentIndex,
ipsAuthIdentAddrIndex } ipsAuthIdentAddrIndex }
::= { ipsAuthIdentAddrAttributesTable 1 } ::= { ipsAuthIdentAddrAttributesTable 1 }
IpsAuthIdentAddrAttributesEntry ::= SEQUENCE { IpsAuthIdentAddrAttributesEntry ::= SEQUENCE {
ipsAuthIdentAddrIndex Unsigned32, ipsAuthIdentAddrIndex Unsigned32,
ipsAuthIdentAddrType AddressFamilyNumbers, ipsAuthIdentAddrType AddressFamilyNumbers,
ipsAuthIdentAddrStart IpsAuthAddress, ipsAuthIdentAddrStart IpsAuthAddress,
ipsAuthIdentAddrEnd IpsAuthAddress, ipsAuthIdentAddrEnd IpsAuthAddress,
ipsAuthIdentAddrRowStatus RowStatus ipsAuthIdentAddrRowStatus RowStatus,
ipsAuthIdentAddrStorageType StorageType
} }
ipsAuthIdentAddrIndex OBJECT-TYPE ipsAuthIdentAddrIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer used to uniquely identify a "An arbitrary integer used to uniquely identify a
particular ipsAuthIdentAddress instance within an particular ipsAuthIdentAddress instance within an
ipsAuthIdentity within an authorization instance ipsAuthIdentity within an authorization instance
present on the node." present on the node. This value does not need to
be preserved across reboots, and must not be used
for a new row before a reboot."
::= { ipsAuthIdentAddrAttributesEntry 1 } ::= { ipsAuthIdentAddrAttributesEntry 1 }
ipsAuthIdentAddrType OBJECT-TYPE ipsAuthIdentAddrType OBJECT-TYPE
SYNTAX AddressFamilyNumbers SYNTAX AddressFamilyNumbers
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of Address in the ipsAuthIdentAddress "The type of Address in the ipsAuthIdentAddress
start, end, and mask fields. This type is taken start, end, and mask fields. This type is taken
from the IANA address family types; more types may from the IANA address family types; more types may
be registered independently of this MIB." be registered independently of this MIB module."
::= { ipsAuthIdentAddrAttributesEntry 2 } ::= { ipsAuthIdentAddrAttributesEntry 2 }
ipsAuthIdentAddrStart OBJECT-TYPE ipsAuthIdentAddrStart OBJECT-TYPE
SYNTAX IpsAuthAddress SYNTAX IpsAuthAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The starting address of the allowed address range." "The starting address of the allowed address range."
::= { ipsAuthIdentAddrAttributesEntry 3 } ::= { ipsAuthIdentAddrAttributesEntry 3 }
skipping to change at page 16, line 35 skipping to change at page 17, line 32
If the ipsAuthIdentAddrEntry specifies a single If the ipsAuthIdentAddrEntry specifies a single
address, this shall match the ipsAuthIdentAddrStart." address, this shall match the ipsAuthIdentAddrStart."
::= { ipsAuthIdentAddrAttributesEntry 4 } ::= { ipsAuthIdentAddrAttributesEntry 4 }
ipsAuthIdentAddrRowStatus OBJECT-TYPE ipsAuthIdentAddrRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This field allows entries to be dynamically added and "This field allows entries to be dynamically added and
removed from this table via SNMP." removed from this table via SNMP. When adding a row to
this table, all non-Index/RowStatus objects must be set.
Rows may be discarded using RowStatus."
::= { ipsAuthIdentAddrAttributesEntry 5 } ::= { ipsAuthIdentAddrAttributesEntry 5 }
ipsAuthIdentAddrStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this row. Rows in this table that were
created through an external process may have a storage type of
readOnly or permanent."
DEFVAL { nonVolatile }
::= { ipsAuthIdentAddrAttributesEntry 6 }
ipsAuthCredential OBJECT IDENTIFIER ::= { ipsAuthObjects 6 } ipsAuthCredential OBJECT IDENTIFIER ::= { ipsAuthObjects 6 }
-- Credential Attributes Table -- Credential Attributes Table
ipsAuthCredentialAttributesTable OBJECT-TYPE ipsAuthCredentialAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpsAuthCredentialAttributesEntry SYNTAX SEQUENCE OF IpsAuthCredentialAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of credentials related to user identities "A list of credentials related to user identities
skipping to change at page 17, line 19 skipping to change at page 18, line 29
DESCRIPTION DESCRIPTION
"An entry (row) containing management information "An entry (row) containing management information
applicable to a credential which verifies a user applicable to a credential which verifies a user
identity within an authorization instance." identity within an authorization instance."
INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, ipsAuthCredIndex } INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, ipsAuthCredIndex }
::= { ipsAuthCredentialAttributesTable 1 } ::= { ipsAuthCredentialAttributesTable 1 }
IpsAuthCredentialAttributesEntry ::= SEQUENCE { IpsAuthCredentialAttributesEntry ::= SEQUENCE {
ipsAuthCredIndex Unsigned32, ipsAuthCredIndex Unsigned32,
ipsAuthCredAuthMethod AutonomousType, ipsAuthCredAuthMethod AutonomousType,
ipsAuthCredRowStatus RowStatus ipsAuthCredRowStatus RowStatus,
ipsAuthCredStorageType StorageType
} }
ipsAuthCredIndex OBJECT-TYPE ipsAuthCredIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer used to uniquely identify a "An arbitrary integer used to uniquely identify a
particular Credential instance within an instance particular Credential instance within an instance
present on the node." present on the node. This value does not need to
be preserved across reboots, and must not be used
for a new row before a reboot."
::= { ipsAuthCredentialAttributesEntry 1 } ::= { ipsAuthCredentialAttributesEntry 1 }
ipsAuthCredAuthMethod OBJECT-TYPE ipsAuthCredAuthMethod OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an OBJECT IDENTIFIER "This object contains an OBJECT IDENTIFIER
which identifies the authentication method which identifies the authentication method
used with this credential. used with this credential.
skipping to change at page 17, line 51 skipping to change at page 19, line 15
Some standardized values for this object are defined Some standardized values for this object are defined
within the ipsAuthMethods subtree." within the ipsAuthMethods subtree."
::= { ipsAuthCredentialAttributesEntry 2 } ::= { ipsAuthCredentialAttributesEntry 2 }
ipsAuthCredRowStatus OBJECT-TYPE ipsAuthCredRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This field allows entries to be dynamically added and "This field allows entries to be dynamically added and
removed from this table via SNMP." removed from this table via SNMP. When adding a row to
this table, all non-Index/RowStatus objects must be set.
Rows may be discarded using RowStatus."
::= { ipsAuthCredentialAttributesEntry 3 } ::= { ipsAuthCredentialAttributesEntry 3 }
ipsAuthCredStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this row. Rows in this table that were
created through an external process may have a storage type of
readOnly or permanent."
DEFVAL { nonVolatile }
::= { ipsAuthCredentialAttributesEntry 4 }
ipsAuthCredChap OBJECT IDENTIFIER ::= { ipsAuthObjects 7 } ipsAuthCredChap OBJECT IDENTIFIER ::= { ipsAuthObjects 7 }
-- Credential Chap-Specific Attributes Table -- Credential Chap-Specific Attributes Table
ipsAuthCredChapAttributesTable OBJECT-TYPE ipsAuthCredChapAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpsAuthCredChapAttributesEntry SYNTAX SEQUENCE OF IpsAuthCredChapAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of CHAP attributes for credentials that "A list of CHAP attributes for credentials that
skipping to change at page 18, line 27 skipping to change at page 20, line 4
ipsAuthCredChapAttributesEntry OBJECT-TYPE ipsAuthCredChapAttributesEntry OBJECT-TYPE
SYNTAX IpsAuthCredChapAttributesEntry SYNTAX IpsAuthCredChapAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing management information "An entry (row) containing management information
applicable to a credential which uses applicable to a credential which uses
ipsAuthMethodChap as their ipsAuthCredAuthMethod." ipsAuthMethodChap as their ipsAuthCredAuthMethod."
INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, ipsAuthCredIndex } INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, ipsAuthCredIndex }
::= { ipsAuthCredChapAttributesTable 1 } ::= { ipsAuthCredChapAttributesTable 1 }
IpsAuthCredChapAttributesEntry ::= SEQUENCE { IpsAuthCredChapAttributesEntry ::= SEQUENCE {
ipsAuthCredChapUserName SnmpAdminString, ipsAuthCredChapUserName SnmpAdminString,
ipsAuthCredChapRowStatus RowStatus ipsAuthCredChapRowStatus RowStatus,
ipsAuthCredChapStorageType StorageType
} }
ipsAuthCredChapUserName OBJECT-TYPE ipsAuthCredChapUserName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An octet string containing the CHAP user name for this "An octet string containing the CHAP user name for this
credential." credential."
REFERENCE
"W. Simpson, RFC 1994: PPP Challenge Handshake
Authentication Protocol (CHAP), August 1996"
::= { ipsAuthCredChapAttributesEntry 1 } ::= { ipsAuthCredChapAttributesEntry 1 }
-- ipsAuthCredChapPassword (2) deleted -- ipsAuthCredChapPassword (2) deleted
ipsAuthCredChapRowStatus OBJECT-TYPE ipsAuthCredChapRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This field allows entries to be dynamically added and "This field allows entries to be dynamically added and
removed from this table via SNMP." removed from this table via SNMP. When adding a row to
this table, all non-Index/RowStatus objects must be set.
Rows may be discarded using RowStatus."
::= { ipsAuthCredChapAttributesEntry 3 } ::= { ipsAuthCredChapAttributesEntry 3 }
ipsAuthCredChapStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this row. Rows in this table that were
created through an external process may have a storage type of
readOnly or permanent."
DEFVAL { nonVolatile }
::= { ipsAuthCredChapAttributesEntry 4 }
ipsAuthCredSrp OBJECT IDENTIFIER ::= { ipsAuthObjects 8 } ipsAuthCredSrp OBJECT IDENTIFIER ::= { ipsAuthObjects 8 }
-- Credential Srp-Specific Attributes Table -- Credential Srp-Specific Attributes Table
ipsAuthCredSrpAttributesTable OBJECT-TYPE ipsAuthCredSrpAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpsAuthCredSrpAttributesEntry SYNTAX SEQUENCE OF IpsAuthCredSrpAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of SRP attributes for credentials that "A list of SRP attributes for credentials that
skipping to change at page 19, line 31 skipping to change at page 21, line 27
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing management information "An entry (row) containing management information
applicable to a credential which uses applicable to a credential which uses
ipsAuthMethodSrp as its ipsAuthCredAuthMethod." ipsAuthMethodSrp as its ipsAuthCredAuthMethod."
INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, ipsAuthCredIndex } INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, ipsAuthCredIndex }
::= { ipsAuthCredSrpAttributesTable 1 } ::= { ipsAuthCredSrpAttributesTable 1 }
IpsAuthCredSrpAttributesEntry ::= SEQUENCE { IpsAuthCredSrpAttributesEntry ::= SEQUENCE {
ipsAuthCredSrpUserName SnmpAdminString, ipsAuthCredSrpUserName SnmpAdminString,
ipsAuthCredSrpRowStatus RowStatus ipsAuthCredSrpRowStatus RowStatus,
ipsAuthCredSrpStorageType StorageType
} }
ipsAuthCredSrpUserName OBJECT-TYPE ipsAuthCredSrpUserName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An octet string containing the CHAP user name for this "An octet string containing the SRP user name for this
credential." credential."
REFERENCE
"T. Wu, RFC 2945: The SRP Authentication and Key
Exchange System, September 2000"
::= { ipsAuthCredSrpAttributesEntry 1 } ::= { ipsAuthCredSrpAttributesEntry 1 }
-- ipsAuthCredSrpPassword (2) deleted -- ipsAuthCredSrpPassword (2) deleted
ipsAuthCredSrpRowStatus OBJECT-TYPE ipsAuthCredSrpRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This field allows entries to be dynamically added and "This field allows entries to be dynamically added and
removed from this table via SNMP." removed from this table via SNMP. When adding a row to
this table, all non-Index/RowStatus objects must be set.
Rows may be discarded using RowStatus."
::= { ipsAuthCredSrpAttributesEntry 3 } ::= { ipsAuthCredSrpAttributesEntry 3 }
ipsAuthCredSrpStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this row. Rows in this table that were
created through an external process may have a storage type of
readOnly or permanent."
DEFVAL { nonVolatile }
::= { ipsAuthCredSrpAttributesEntry 4 }
ipsAuthCredKerberos OBJECT IDENTIFIER ::= { ipsAuthObjects 9 } ipsAuthCredKerberos OBJECT IDENTIFIER ::= { ipsAuthObjects 9 }
-- Credential Kerberos-Specific Attributes Table -- Credential Kerberos-Specific Attributes Table
ipsAuthCredKerbAttributesTable OBJECT-TYPE ipsAuthCredKerbAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpsAuthCredKerbAttributesEntry SYNTAX SEQUENCE OF IpsAuthCredKerbAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of Kerberos attributes for credentials that "A list of Kerberos attributes for credentials that
skipping to change at page 20, line 31 skipping to change at page 22, line 45
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing management information "An entry (row) containing management information
applicable to a credential which uses applicable to a credential which uses
ipsAuthMethodKerberos as its ipsAuthCredAuthMethod." ipsAuthMethodKerberos as its ipsAuthCredAuthMethod."
INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, ipsAuthCredIndex } INDEX { ipsAuthInstIndex, ipsAuthIdentIndex, ipsAuthCredIndex }
::= { ipsAuthCredKerbAttributesTable 1 } ::= { ipsAuthCredKerbAttributesTable 1 }
IpsAuthCredKerbAttributesEntry ::= SEQUENCE { IpsAuthCredKerbAttributesEntry ::= SEQUENCE {
ipsAuthCredKerbPrincipal SnmpAdminString, ipsAuthCredKerbPrincipal SnmpAdminString,
ipsAuthCredKerbRowStatus RowStatus ipsAuthCredKerbRowStatus RowStatus,
ipsAuthCredKerbStorageType StorageType
} }
ipsAuthCredKerbPrincipal OBJECT-TYPE ipsAuthCredKerbPrincipal OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An octet string containing a Kerberos principal "An octet string containing a Kerberos principal
for this credential." for this credential."
REFERENCE
"J. Kohl, C. Neuman, RFC 1510: The Kerberos Network
Authentication Service (V5), September 1993"
::= { ipsAuthCredKerbAttributesEntry 1 } ::= { ipsAuthCredKerbAttributesEntry 1 }
ipsAuthCredKerbRowStatus OBJECT-TYPE ipsAuthCredKerbRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This field allows entries to be dynamically added and "This field allows entries to be dynamically added and
removed from this table via SNMP." removed from this table via SNMP. When adding a row to
this table, all non-Index/RowStatus objects must be set.
Rows may be discarded using RowStatus."
::= { ipsAuthCredKerbAttributesEntry 2 } ::= { ipsAuthCredKerbAttributesEntry 2 }
ipsAuthCredKerbStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this row. Rows in this table that were
created through an external process may have a storage type of
readOnly or permanent."
DEFVAL { nonVolatile }
::= { ipsAuthCredKerbAttributesEntry 3 }
------------------------------------------------------------------------
-- Notifications -- Notifications
-- There are no notifications necessary in this MIB module.
------------------------------------------------------------------------ ------------------------------------------------------------------------
-- Conformance Statements -- Conformance Statements
ipsAuthGroups OBJECT IDENTIFIER ::= { ipsAuthConformance 1 } ipsAuthCompliances OBJECT IDENTIFIER ::= { ipsAuthConformance 1 }
ipsAuthGroups OBJECT IDENTIFIER ::= { ipsAuthConformance 2 }
ipsAuthInstanceAttributesGroup OBJECT-GROUP ipsAuthInstanceAttributesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ipsAuthInstDescr ipsAuthInstDescr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
authorization instances." authorization instances."
::= { ipsAuthGroups 1 } ::= { ipsAuthGroups 1 }
ipsAuthIdentAttributesGroup OBJECT-GROUP ipsAuthIdentAttributesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ipsAuthIdentDescription, ipsAuthIdentDescription,
ipsAuthIdentRowStatus ipsAuthIdentRowStatus,
ipsAuthIdentStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
user identities within an authorization instance." user identities within an authorization instance."
::= { ipsAuthGroups 2 } ::= { ipsAuthGroups 2 }
ipsAuthIdentNameAttributesGroup OBJECT-GROUP ipsAuthIdentNameAttributesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ipsAuthIdentName, ipsAuthIdentName,
ipsAuthIdentNameRowStatus ipsAuthIdentNameRowStatus,
ipsAuthIdentNameStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
user names within user identities within an authorization user names within user identities within an authorization
instance." instance."
::= { ipsAuthGroups 3 } ::= { ipsAuthGroups 3 }
ipsAuthIdentAddrAttributesGroup OBJECT-GROUP ipsAuthIdentAddrAttributesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ipsAuthIdentAddrType, ipsAuthIdentAddrType,
ipsAuthIdentAddrStart, ipsAuthIdentAddrStart,
ipsAuthIdentAddrEnd, ipsAuthIdentAddrEnd,
ipsAuthIdentAddrRowStatus ipsAuthIdentAddrRowStatus,
ipsAuthIdentAddrStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
address ranges within user identities within an address ranges within user identities within an
authorization instance." authorization instance."
::= { ipsAuthGroups 4 } ::= { ipsAuthGroups 4 }
ipsAuthIdentCredAttributesGroup OBJECT-GROUP ipsAuthIdentCredAttributesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ipsAuthCredAuthMethod, ipsAuthCredAuthMethod,
ipsAuthCredRowStatus ipsAuthCredRowStatus,
ipsAuthCredStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
credentials within user identities within an authorization credentials within user identities within an authorization
instance." instance."
::= { ipsAuthGroups 5 } ::= { ipsAuthGroups 5 }
ipsAuthIdentChapAttrGroup OBJECT-GROUP ipsAuthIdentChapAttrGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ipsAuthCredChapUserName, ipsAuthCredChapUserName,
ipsAuthCredChapRowStatus ipsAuthCredChapRowStatus,
ipsAuthCredChapStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
CHAP credentials within user identities within an CHAP credentials within user identities within an
authorization instance." authorization instance."
::= { ipsAuthGroups 6 } ::= { ipsAuthGroups 6 }
ipsAuthIdentSrpAttrGroup OBJECT-GROUP ipsAuthIdentSrpAttrGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ipsAuthCredSrpUserName, ipsAuthCredSrpUserName,
ipsAuthCredSrpRowStatus ipsAuthCredSrpRowStatus,
ipsAuthCredSrpStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
SRP credentials within user identities within an SRP credentials within user identities within an
authorization instance." authorization instance."
::= { ipsAuthGroups 7 } ::= { ipsAuthGroups 7 }
ipsAuthIdentKerberosAttrGroup OBJECT-GROUP ipsAuthIdentKerberosAttrGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ipsAuthCredKerbPrincipal, ipsAuthCredKerbPrincipal,
ipsAuthCredKerbRowStatus ipsAuthCredKerbRowStatus,
ipsAuthCredKerbStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
Kerberos credentials within user identities within an Kerberos credentials within user identities within an
authorization instance." authorization instance."
::= { ipsAuthGroups 8 } ::= { ipsAuthGroups 8 }
------------------------------------------------------------------------ ------------------------------------------------------------------------
ipsAuthCompliances OBJECT IDENTIFIER ::= { ipsAuthConformance 2 }
ipsAuthComplianceV1 MODULE-COMPLIANCE ipsAuthComplianceV1 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Initial version of compliance statement based on "Initial version of compliance statement based on
initial version of MIB. initial version of this MIB module.
The Instance and Identity groups are mandatory; The Instance and Identity groups are mandatory;
at least one of the other groups (Name, Address, at least one of the other groups (Name, Address,
Credential, Certificate) is also mandatory for Credential, Certificate) is also mandatory for
any given implementation." any given implementation."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ipsAuthInstanceAttributesGroup, ipsAuthInstanceAttributesGroup,
ipsAuthIdentAttributesGroup ipsAuthIdentAttributesGroup
} }
skipping to change at page 27, line 22 skipping to change at page 30, line 22
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
All tables provide the ability to set up which credentials may be All tables provide the ability to set up which credentials may be
used to access services on the managed system, to remove used to access services on the managed system, to remove
legitimate credentials (a denial of service), or to remove legitimate credentials (a denial of service), or to remove
individual credentials to weaken the requirements for access of a individual credentials to weaken the requirements for access of a
particular service. Write access must always be tightly particular service. Write access must always be tightly
controlled. Note that some types of credentials, such as CHAP or controlled. Note that some types of credentials, such as CHAP or
SRP, also require passwords or verifiers to be associated with the SRP, also require passwords or verifiers to be associated with the
credential. These are managed outside this MIB. credential. These are managed outside this MIB module.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
All tables provide the ability to find out which names, addresses, All tables provide the ability to find out which names, addresses,
and credentials would be required to access services on the and credentials would be required to access services on the
managed system. If these credentials are easily spoofed managed system. If these credentials are easily spoofed
(particularly the name or address), read access to the MIB must be (particularly the name or address), read access to this MIB module
tightly controlled. must be tightly controlled.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementors consider the security features as It is RECOMMENDED that implementors consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. Normative References 7. IANA Considerations
7.1. OID Assignment
IANA is requested to make a MIB OID assignment under the mib-2
branch.
8. Normative References
[RFC2578] K. McCloghrie, D. Perkins, J. Schoenwaelder, J. Case, M. [RFC2578] K. McCloghrie, D. Perkins, J. Schoenwaelder, J. Case, M.
Rose, and S. Waldbusser, "Structure of Management Rose, and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] K. McCloghrie, D. Perkins, J. Schoenwaelder, J. Case, M. [RFC2579] K. McCloghrie, D. Perkins, J. Schoenwaelder, J. Case, M.
Rose, and S. Waldbusser, "Textual Conventions for SMIv2", Rose, and S. Waldbusser, "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
skipping to change at page 28, line 40 skipping to change at page 31, line 46
Network Management of TCP/IP-based internets:MIB-II", March Network Management of TCP/IP-based internets:MIB-II", March
1991. 1991.
[RFC2011] K. McCloghrie, "SNMPv2 Management Information Base for the [RFC2011] K. McCloghrie, "SNMPv2 Management Information Base for the
Internet Protocol using SMIv2", November 1996. Internet Protocol using SMIv2", November 1996.
[RFC2465] D. Haskin, S. Onishi, "Management Information Base for IP [RFC2465] D. Haskin, S. Onishi, "Management Information Base for IP
Version 6: Textual Conventions and General Group", December Version 6: Textual Conventions and General Group", December
1998. 1998.
8. Informative References
[RFC3410] J. Case, R. Mundy, D. Partain, and B. Stewart, "Introduction
and Applicability Statements for Internet-Standard
Management Framework", RFC 3410, December 2002.
[ISCSI] Satran, J., et. al., "iSCSI", Work in Progress, draft-ietf-
ips-iscsi-20, January 2003.
[RFC1737] K. Sollins, L. Masinter, "Functional Requirements for
Uniform Resource Names", December 1994.
[RFC1994] W. Simpson, "PPP Challenge Handshake Authentication Protocol [RFC1994] W. Simpson, "PPP Challenge Handshake Authentication Protocol
(CHAP)", August 1996. (CHAP)", August 1996.
[RFC1510] J. Kohl, C. Neuman, "The Kerberos Network Authentication [RFC1510] J. Kohl, C. Neuman, "The Kerberos Network Authentication
Service (V5)", September 1993. Service (V5)", September 1993.
[RFC2945] T. Wu, "The SRP Authentication and Key Exchange System", [RFC2945] T. Wu, "The SRP Authentication and Key Exchange System",
September 2000. September 2000.
9. Informative References
[RFC3410] J. Case, R. Mundy, D. Partain, and B. Stewart, "Introduction
and Applicability Statements for Internet-Standard
Management Framework", RFC 3410, December 2002.
[RFC3720] Satran, J., et. al., "Internet Small Computer Systems
Interface (iSCSI)", RFC 3720, April 2004.
[RFC1737] K. Sollins, L. Masinter, "Functional Requirements for
Uniform Resource Names", December 1994.
[FCMGMT] K. McCloghrie, "Fibre Channel Management MIB", Work in [FCMGMT] K. McCloghrie, "Fibre Channel Management MIB", Work in
Progress, draft-ietf-ips-fcmgmt-mib-03, October 2002. Progress, draft-ietf-ips-fcmgmt-mib-06, December 2004.
9. Authors' Addresses 10. Authors' Addresses
Mark Bakke Mark Bakke
Postal: Cisco Systems, Inc Postal: Cisco Systems, Inc
6450 Wedgwood Road, Suite 130 7900 International Drive, Suite 400
Maple Grove, MN Bloomington, MN
USA 55311 USA 55425
Tel: +1 763-398-1000 Email: mbakke@cisco.com
Fax: +1 763-398-1001
E-mail: mbakke@cisco.com James Muchow
Postal: Qlogic Corp.
6321 Bury Drive
Eden Prairie, MN
USA 55346
Jim Muchow Email: james.muchow@qlogic.com
E-mail: jamesdmuchow@yahoo.com" 11. IPR Notice
10. IPR Notice By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made
available for publication and any assurances of licenses to be made Copies of IPR disclosures made to the IETF Secretariat and any
available, or the result of an attempt made to obtain a general assurances of licenses to be made available, or the result of an
license or permission for the use of such proprietary rights by attempt made to obtain a general license or permission for the use of
implementors or users of this specification can be obtained from the such proprietary rights by implementers or users of this
IETF Secretariat. specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf-
Director. ipr@ietf.org.
11. Full Copyright Notice 12. Full Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be This document and the information contained herein are provided on an
revoked by the Internet Society or its successors or assigns. "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
This document and the information contained herein is provided on an ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/