WDIFF

draft-ietf-pwe3-pw-tc-mib-05.txt --> draft-ietf-pwe3-pw-tc-mib-06.txt

view Side-By-Side changes

Expires: December 2004 January 2006 Cisco Systems, Inc.

Dave Danenberg

David Zelig Zelig, Ed.
Corrigent Systems

Andrew G. Malis
Tellabs, Inc.
June 2004

July 2005

Definitions for Textual Conventions and OBJECT-IDENTITIES
for Pseudo-Wires Management

draft-ietf-pwe3-pw-tc-mib-05.txt

draft-ietf-pwe3-pw-tc-mib-06.txt

Status of this Memo

This document

By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is an Internet-Draft
aware have been or will be disclosed, and is any of which he or she
becomes aware will be disclosed, in full conformance accordance with
all provisions of Section 10 6 of RFC2026.
BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-
Drafts. Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
http://www.ietf.org/1id-abstracts.html

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright (C) The Internet Society (2001). All rights reserved.

Abstract

This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
the Internet community. In particular, it describes the textual
conventions to be used in the various Pseudo Wire (PW) Edge-to-Edge
MIB modules.

Nadeau et al. Expires December 2004 [page 1]

PWE3 TC MIB June 2004

Table of Contents

Abstract.......................................................1
2
1 Introduction...................................................2
3
2 Terminology....................................................2
4
3 The Internet-Standard Management Framework.....................2

Nadeau & Zelig, Ed. Expires February 2006 [Page 1]

Internet Draft PW-STD-MIB July 2005

4 PWE3-TC-STD-MIB Module Definitions.............................3
5 Object Definition..............................................3
6 Security Considerations........................................9
7 Considerations.......................................26
6 IANA considerations............................................9
8 References....................................................10
8.1 considerations...........................................27
7 References..................................................27
7.1 Normative References........................................10
8.2 references........................................27
7.2 Informative references......................................11
9 references......................................29
8 Author's Addresses............................................11
10 Addresses..........................................29
9 Full Copyright Statement....................................11
11 Statement....................................29
10 Intellectual Property Notice................................12

2 Notice................................30

1. Introduction

This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet
community. In particular, it defines Textual Conventions used in
IETF PW and PW-related PWE3 MIBs.

This document adopts the definitions, acronyms and mechanisms
described in [RFC3985]. Unless otherwise stated, the mechanisms of
[RFC3985] apply and will not be re-described here.

Comments should be made directly to the MPLS PWE3 mailing list at
pwe3@ietf.org.

For an introduction to the concepts of Pseudo-Wires, see [PWREQ]
and [PWARCH].

Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC-2119
[BCP14].

3
[RFC2119].

2. Terminology

This document uses terminology from the document describing the PW PWE3
architecture [PWARCH].

4 [RFC3985].

3. The Internet-Standard Management Framework

For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].

Nadeau et al Expires December 2004 [page 2]

PWE3 TC MIB June 2004

Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the

Nadeau & Zelig, Ed. Expires February 2006 [Page 2]

Internet Draft PW-STD-MIB July 2005

Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,RFC 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].

5 Object Definition

PW-TC-DRAFT05-MIB

4. PWE3 TC MIB Module Definitions

PW-TC-STD-MIB DEFINITIONS ::= BEGIN

IMPORTS
MODULE-IDENTITY, Unsigned32, Integer32, transmission
FROM SNMPv2-SMI -- [RFC2578]

TEXTUAL-CONVENTION
FROM SNMPv2-TC;

pwTCMIB -- [RFC2579]

pwTcMIB MODULE-IDENTITY
LAST-UPDATED "200406141200Z" "200507121200Z" -- 14 June 2004 12 July 2005 12:00:00 GMT
ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
Group"
CONTACT-INFO
" Thomas D. Nadeau
Postal: Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-497-3051
Email: tnadeau@cisco.com

Dave Danenberg
Email: dave_danenberg@yahoo.com

David Zelig
Postal: Corrigent Systems.
126, Yigal Alon St.
Tel Aviv, ISRAEL
Phone: +972-3-6945273
E-mail: davidz@corrigent.com

Andrew G. Malis
Postal: Tellabs, Inc.
2730 Orchard Parkway
San Jose, CA 95134
Email: Andy.Malis@tellabs.com

The PWE3 Working Group (email distribution pwe3@ietf.org,
http://www.ietf.org/html.charters/pwe3-charter.html)
"

Nadeau et al Expires December 2004 [page 3]

PWE3 TC MIB June 2004

DESCRIPTION
"This MIB Module provides Textual Conventions
and OBJECT-IDENTITY Objects to be used in networks
implementing PW services.

Copyright
"Copyright (C) The Internet Society (date). This (2005). The
initial version of this MIB module is part of was published
in RFC yyyy; 3811. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html

This MIB module defines TEXTUAL-CONVENTIONs
for full legal notices.
-- RFC Ed.: replace yyyy with actual RFC number & remove this note concepts used in Pseudo Wire Edge-to-Edge
networks.
"
-- Revision history.

REVISION "200406141200Z" "200507121200Z" -- 14 June 2004 12 July 2005 12:00:00 GMT
DESCRIPTION " Changes from previous drafts:
- Update PW types based on new IANA draft -04.
- FCS Retention status has been updated to include FCS size
mismatch.
"

REVISION "200402031200Z" -- 3 February 2004 12:00:00 GMT
DESCRIPTION " Changes from previous drafts:
- Change IANA request text.
- Change PwVcRemoteCwStatus to PwVcCwStatus and add two
enum so the textual convention will indicate the full
status of the CW negotiation including the final result.
"
REVISION "200311301200Z" -- 30 November 2003 12:00:00 GMT
DESCRIPTION " Changes from previous drafts:
- Removing non-necessary textual convention.
- Adapt description "Initial version published as part of main clause based on MIB
boilerplate.
"
REVISION "200307281200Z" -- 28 July 2003 12:00:00 GMT
DESCRIPTION "Adding objects to cover new control draft.
Adapt VC types for current values in WG documents."

REVISION "200305011200Z" -- 1 May 2003 12:00:00 GMT
DESCRIPTION "Adding PwVcAttachmentIdentifierType,
Adapt VC types for current values in WG documents."

REVISION "200205281200Z" RFC XXXX."
-- 28 May 2002 12:00:00 GMT
DESCRIPTION "Adding PwVcType, and enhance some descriptions."

REVISION "200201301200Z" RFC Editor: Please replace XXXX with RFC number.
::= { pwMIB XXXX } -- 30 January 2002 12:00:00 GMT
DESCRIPTION "Adding PwVcVlanCfg, PwAddressType and
PwOperStatus."

REVISION "200112201200Z" RFC Editor: please replace
-- 20 Dec 2001 12:00:00 GMT
DESCRIPTION "Remove PwVcInstance" XXXX with IANA assigne value.

Nadeau et al & Zelig, Ed. Expires December 2004 [page 4]

PWE3 TC MIB June 2004

REVISION "200107121200Z" -- 12 February 2006 [Page 3]

Internet Draft PW-STD-MIB July 2001 12:00:00 GMT
DESCRIPTION "Initial version." 2005

-- Please see the See IANA Considerations Section.
-- The requested pwStdMIB subId is 1, e.g.
-- ::= { pwStdMIB 1 }

::= { pwStdMIB x }

pwStdMIB considerations sect.

pwMIB OBJECT IDENTIFIER
-- This object identifier needs to be assigned by IANA.
::= { transmission xxx YYYY }

-- RFC Editor: Please replace YYYY with the IANA-assigned
-- transmission OID.

PwGroupID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An administrative identification mechanism for grouping a
set of service-specific pseudo-wire services. May only
have local significance."
SYNTAX Unsigned32

PwVcIDType

PwIDType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Pseudo-Wire Identifier. Used to identify the PW
(together with some other fields) in the signaling
session. Zero if the PW is set-up manually."
SYNTAX Unsigned32

PwVcIndexType

PwIndexType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Pseudo Wire Index. Locally unique index for indexing
several MIB tables associated with a particular PW."
SYNTAX Unsigned32

PwVcVlanCfg

PwVlanCfg ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"VLAN configuration for Ethernet PW.
Values between 0 to 4095 indicate the actual VLAN field
value.
A value of 4096 indicates that the object refer to
untagged frames, i.e. frames without 802.1Q field.
A value of 4097 indicates that the object is not
relevant."
SYNTAX Integer32 (0..4097)

Nadeau et al Expires December 2004 [page 5]

PWE3 TC MIB June 2004

PwOperStatus

PwOperStatusTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates the operational status of the PW.

Nadeau & Zelig, Ed. Expires February 2006 [Page 4]

Internet Draft PW-STD-MIB July 2005

- up(1): Ready to pass packets.
- down(2): If PW signaling has not yet finished, or
indications available at the service
level indicate that the VC is not
passing packets.
- testing(3): If AdminStatus at the PW level is set to
test.
- dormant(4): The PW is not available because of the
required resources are occupied PW with
higher priority PWs .
- notPresent(5): Some component is missing to accomplish
the set up of the PW.
- lowerLayerDown(6):The underlying PSN or outer tunnel is not
in OperStatus 'up' state.
"
SYNTAX INTEGER {
up(1),
down(2),
testing(3),
unknown(4),
dormant(5),
notPresent(6),
lowerLayerDown(7)
}

PwVcType

PwTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates the PW type (i.e. the carried service).
"
SYNTAX INTEGER {
other(0),
frameRelayDlci(1),
atmAal5SduVcc(2),
atmTransparent(3),
ethernetTagged(4),
ethernet(5),
hdlc(6),
ppp(7),
cem(8), -- old format
atmCellNto1Vcc(9),
atmCellNto1Vpc(10),
ipLayer2Transport(11),
atmCell1to1Vcc(12),
atmCell1to1Vpc(13),
atmAal5PduVcc(14),

Nadeau et al Expires December 2004 [page 6]

PWE3 TC MIB June 2004
frameRelayPortMode(15),
cep(16),

Nadeau & Zelig, Ed. Expires February 2006 [Page 5]

Internet Draft PW-STD-MIB July 2005

e1Satop(17),
t1Satop(18),
e3Satop(19),
t3Satop(20),
basicCesPsn(21),
basicTdmIp(22),
tdmCasCesPsn(23),
tdmCasTdmIp(24)
}

PwVcAttachmentIdentifierType

PwAttachmentIdentifierType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An octet string used in the generalized FEC element for
identifying attachment forwarder and groups. The NULL
identifier is of zero length.
"
SYNTAX OCTET STRING (SIZE (0..255))

PwVcCwStatus

PwCwStatusTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates the status of the control word negotiation based
on the local configuration and the indications received from
the peer node.

waitingForNextMsg(1) indicates that the node is waiting for
another label mapping from the remote.

sentWrongBitErrorCode(2) indicates that the local node has
notified the peer about mismatch in the C bit.

rxWithdrawWithWrongBitErrorCode(3) indicates that a withdraw
message has been received with the wrong C-bit error code.

illegalReceivedBit(4) indicates a C bit configuration with
the remote which is not compatible with the PW type.

cwPresent(5) indicates that the CW is present for this PW:
if signaling is used - C bit is set and agreed between the
peers, and for manual configured PW the local configuration
require the use of the CW.

cwNotPresent(6) indicates that the CW is not present for
this PW: if signaling is used - C bit is reset and agreed
between the peers, and for manual configured PW the local
configuration requires that CW would not be used.

Nadeau et al Expires December 2004 [page 7]

PWE3 TC MIB June 2004
notYetKnown(7) indicate that a label mapping has not yet
received from the peer.

Nadeau & Zelig, Ed. Expires February 2006 [Page 6]

Internet Draft PW-STD-MIB July 2005

"
SYNTAX INTEGER {
waitingForNextMsg (1),
sentWrongBitErrorCode (2),
rxWithdrawWithWrongBitErrorCode (3),
illegalReceivedBit (4),
cwPresent (5),
cwNotPresent (6),
notYetKnown(7)
}

PwVcCapabilities

PwCapabilities ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates the optional capabilities of the control protocol.
A value of zero indicates the basic LDP PW signaling.
Values may be added in the future based on new capabilities
introduced in IETF documents.
"
SYNTAX BITS {
pwStatusIndication (0)
}

PwVcStatus

PwStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The status of the PW and the interfaces affecting this PW.
If none of the bits are set, it indicate no faults are
reported.
"
SYNTAX BITS {
pwNotForwarding (0),
customerFacingPwRxFault (1),
customerFacingPwTxFault (2),
psnFacingPwRxFault (3),
psnFacingPwTxFault (4)
}

PwVcFragSize

PwFragSize ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"If set to value other than zero, it indicates desired
fragmentation to the value set. If set to zero,
fragmentation is not desired for PSN bound packets.
"
SYNTAX Unsigned32

PwVcFragStatus

PwFragStatus ::= TEXTUAL-CONVENTION

Nadeau et al Expires December 2004 [page 8]

PWE3 TC MIB June 2004
STATUS current

Nadeau & Zelig, Ed. Expires February 2006 [Page 7]

Internet Draft PW-STD-MIB July 2005

DESCRIPTION
"The status of the fragmentation process based on local
configuration and the remote capability.

noFrag(0) bit indicates that local configuration is for no
fragmentation.

cfgFragGreaterThanPsnMtu(1) bit indicates the local desire
to fragment, but the fragmentation size desired is greater
than the MTU available at the PSN between peers.
Fragmentation is not done in this case.

cfgFragButRemoteIncapable(2) bit indicates that the local
configuration indicates the desire for fragmentation but
the remote is not capable of fragmentation.

cfgFragFcsLengthMismatch(3) bit indicates that there is a
mismatch between the FCS size between the local
configuration and the remote configuration.

fragEnabled(4) bit indicates that both the local was
configured for fragmentation and the remote has the
cabability to accept fragmented packets, and the FCS size is
equal in both peers.
"
SYNTAX BITS {
noFrag (0),
cfgFragGreaterThanPsnMtu (1),
cfgFragButRemoteIncapable (2),
remoteFragCapable (3),
fragEnabled (4)
}

END

6 Security Considerations

This module does not define any management objects. Instead, it
defines a set

5. Intellectual Property Statement

The IETF takes no position regarding the validity or scope of textual conventions which may be used by any
Intellectual Property Rights or other
MPLS MIB modules to define management objects.

Meaningful security considerations can only rights that might be written in claimed to
pertain to the MIB
modules that define management objects. Therefore, implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has no impact
made any independent effort to identify any such rights. Information
on the security procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the Internet.

7 IANA considerations

IANA is requested IETF Secretariat and any
assurances of licenses to make a MIB OID assignment under be made available, or the
transmission branch, that is, assign result of an
attempt made to obtain a general license or permission for the pwStdMIB under use of

Nadeau et al & Zelig, Ed. Expires December 2004 [page 9]

PWE3 TC MIB June 2004

{ transmission TBD }.

In the future, PWE3 related standards track PW modules should February 2006 [Page 8]

Internet Draft PW-STD-MIB July 2005

such proprietary rights by implementers or users of this
specification can be
rooted under obtained from the pwStdMIB subtree. IETF on-line IPR repository at
http://www.ietf.org/ipr.

The IANA is requested IETF invites any interested party to manage bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that namespace. New assignments can only may cover technology that may be made via a Standards
Action as specified in [RFC2434].

This document also requests IANA required to assign { pwStdMIB 1 } implement
this standard. Please address the information to the PW
MIB specified in this document.

8 IETF at ietf-
ipr@ietf.org.

6. References

8.1

6.1 Normative References

[PWREQ] Xio, X., et al, "Requirements for Pseudo-Wire Emulation
Edge-to-Edge (PWE3)", work-in-progress.

[PWARCH]

[RFC3985] Bryant, S., et al, "PWE3 Architecture", work-in-
progress.

[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC
1700, October 1994. See also: http://www.isi.edu/in-
notes/iana/assignments/smi-numbers

[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS,(http://www.isi.edu/in-
notes/iana/assignements/address-family-numbers), for
MIB see:
ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib

[PWE3IANA] Martini, L., et al., �IANA Allocations for pseudo Wire
Edge to Edge Emulation (PWE3)�, work-in-progress.

[BCP14] Bradner, S., "Key words for use in RFCs to Indicate
requirement Levels", BCP 14, RFC 2119, Architecture",RFC2985,
March 1997. 2005

[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing
an IANA Considerations Section in RFCs", BCP: 26, RFC
2434, October 1998.

[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J.,Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.

[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.

Nadeau et al Expires December 2004 [page 10]

PWE3 TC MIB June 2004

[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999.

8.2

6.2 Informative references

[RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC2119, March 1997.

[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December
2002.

9 Author's Addresses

7. Security Considerations

This module does not define any management objects. Instead, it
defines a set of textual conventions which may be used by other
MPLS MIB modules to define management objects.

Nadeau & Zelig, Ed. Expires February 2006 [Page 9]

Internet Draft PW-STD-MIB July 2005

Meaningful security considerations can only be written in the MIB
modules that define management objects. Therefore, this document
has no impact on the security of the Internet.

8. Editors' Contact Information

Thomas D. Nadeau
Cisco Systems, Inc.
250 Apollo Drive
Chelmsford,
300 Beaver Brook Road
Boxboro, MA 01824 01719
Email: tnadeau@cisco.com

Dave Danenberg
Email: dave_danenberg@yahoo.com

David Zelig
Corrigent Systems
126, Yigal Alon st.
Tel Aviv, ISRAEL
Phone: +972-3-6945273
Email: davidz@corrigent.com

9. Authors' Addresses

Dave Danenberg
Email: dave_danenberg@yahoo.com

Andrew G. Malis
Tellabs, Inc.
2730 Orchard Parkway
San Jose, CA 95134
Email: Andy.Malis@tellabs.com

10. Full Copyright Statement

Copyright (C) The Internet Society (2000). All Rights Reserved. (2005). This document and translations of it may be copied and furnished is
subject to
others, and derivative works that comment on or otherwise explain
it or assist in its implementation may be prepared, copied,
published and distributed, in whole or in part, without restriction
of any kind, provided that the above copyright notice and this
paragraph are included on all such copies rights, licenses and derivative works.
However, this document itself may not be modified restrictions contained in any way, such
as by removing the copyright notice or references to the Internet
Society or other Internet organizations, BCP
78, and except as needed for the
purpose of developing Internet standards in which case the
procedures for copyrights defined in the Internet Standards process

Nadeau et al Expires December 2004 [page 11]

PWE3 TC MIB June 2004

must be followed, or as required to translate it into languages
other than English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. set forth therein, the authors retain all their
rights.

This document and the information contained herein is are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIMS DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.

11 Intellectual Property Notice

The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain

11. IANA Considerations

Nadeau & Zelig, Ed. Expires February 2006 [Page 10]

Internet Draft PW-STD-MIB July 2005

IANA is requested to make a MIB OID assignment under the implementation or use of the technology described in
this document or
transmission branch, that is, assign the extent to which any license pwStdMIB under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information
{ transmission TBD }.
-- RFC Editor: Please assign TBD based on IANA-requested assignment

In the IETF's procedures with respect to rights in standards-track and
standards-related documentation can future, PWE3 related standards track PW modules should be found in BCP-11 [RFC2028].
Copies of claims of rights made available for publication and any
assurances of licenses
rooted under the pwStdMIB subtree. The IANA is requested to manage
that namespace. New assignments can only be made available, or the result of an
attempt made to obtain via a general license or permission Standards
Action as specified in [RFC2434].

11.1 IANA Considerations for the use
of such proprietary rights by implementors or users of this
specification can be obtained from the IETF Secretariat.

The IETF invites any interested party to bring PW-TC-STD-MIB

This document also requests IANA to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required assign { pwStdMIB 1 } to practice the PW
MIB specified in this standard. Please address document.

Acknowledgement

Funding for the information to RFC Editor function is currently provided by the IETF
Executive Director.
Internet Society.

Nadeau et al & Zelig, Ed. Expires December 2004 [page 12] February 2006 [Page 11]
----