< draft-ietf-pwe3-pw-mib-13.txt   draft-ietf-pwe3-pw-mib-14.txt >
Pseudowire Edge-to-Edge Emulation T. Nadeau, Ed. Pseudowire Edge-to-Edge Emulation T. Nadeau, Ed.
Internet-Draft BT Internet-Draft BT
Intended status: Standards Track D. Zelig, Ed. Intended status: Standards Track D. Zelig, Ed.
Expires: May 21, 2008 Corrigent Systems Expires: July 12, 2008 Corrigent Systems
D. Danenberg January 9, 2008
S. Mantin
Corrigent Systems
November 18, 2007
Pseudowire (PW) Management Information Base (MIB) Pseudowire (PW) Management Information Base (MIB)
draft-ietf-pwe3-pw-mib-13 draft-ietf-pwe3-pw-mib-14
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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
skipping to change at page 1, line 39 skipping to change at page 1, line 35
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.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
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.
This Internet-Draft will expire on May 21, 2008. This Internet-Draft will expire on July 12, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base for use with network management protocols in the Information Base for use with network management protocols in the
Internet community. In particular, it describes managed objects for Internet community. In particular, it describes managed objects for
modeling of Pseudowire Edge-to-Edge services carried over a general modeling of Pseudowire Edge-to-Edge services carried over a general
Packet Switched Network. Packet Switched Network.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Co-Authors . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. PW-STD-MIB Module Usage . . . . . . . . . . . . . . . . . . . 5 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
7. Relations to Other PWE3 MIB Modules . . . . . . . . . . . . . 5 7. PW-STD-MIB Module Usage . . . . . . . . . . . . . . . . . . . 5
8. Relations to the IF-MIB . . . . . . . . . . . . . . . . . . . 5 8. Relations to Other PWE3 MIB Modules . . . . . . . . . . . . . 5
9. PW Notifications . . . . . . . . . . . . . . . . . . . . . . . 6 9. Relations to the IF-MIB . . . . . . . . . . . . . . . . . . . 6
10. Example of the PW MIB Modules Usage . . . . . . . . . . . . . 6 10. PW Notifications . . . . . . . . . . . . . . . . . . . . . . . 6
11. IANA PWE3 MIB Module . . . . . . . . . . . . . . . . . . . . . 8 11. Example of the PW MIB Modules Usage . . . . . . . . . . . . . 7
12. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 10 12. IANA PWE3 MIB Module . . . . . . . . . . . . . . . . . . . . . 9
13. Security Considerations . . . . . . . . . . . . . . . . . . . 61 13. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 11
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 14. Security Considerations . . . . . . . . . . . . . . . . . . . 62
14.1. IANA Considerations for PW-STD-MIB . . . . . . . . . . . 62 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63
14.2. IANA Considerations for IANA-PWE3-MIB . . . . . . . . . . 63 15.1. ifType for PW . . . . . . . . . . . . . . . . . . . . . . 63
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 63 15.2. PW MIB Modules OBJECT IDENTIFIER values . . . . . . . . . 64
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63 15.3. IANA Considerations for PW-STD-MIB . . . . . . . . . . . 64
16.1. Normative References . . . . . . . . . . . . . . . . . . 63 15.4. IANA Considerations for IANA-PWE3-MIB . . . . . . . . . . 64
16.2. Informative References . . . . . . . . . . . . . . . . . 65 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 65
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 65 17. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Intellectual Property and Copyright Statements . . . . . . . . . . 67 17.1. Normative References . . . . . . . . . . . . . . . . . . 65
17.2. Informative References . . . . . . . . . . . . . . . . . 66
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 67
Intellectual Property and Copyright Statements . . . . . . . . . . 68
1. Introduction 1. Introduction
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 the Internet community. for use with network management protocols in the Internet community.
In particular, it defines a MIB module that can be used to manage In particular, it defines a MIB module that can be used to manage
pseudowire (PW) services for transmission over a packet Switched pseudowire (PW) services for transmission over a packet Switched
Network (PSN) [RFC3931] [RFC4447]. This MIB module provides generic Network (PSN) [RFC3931] [RFC4447]. This MIB module provides generic
management of PWs which is common to all types of PSN and PW services management of PWs which is common to all types of PSN and PW services
defined by the IETF PWE3 Working Group. defined by the IETF PWE3 Working Group.
skipping to change at page 3, line 43 skipping to change at page 3, line 43
3. Conventions 3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [BCP14]. document are to be interpreted as described in RFC 2119 [BCP14].
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms and mechanisms
described in [RFC3985] and [RFC3916]. Unless otherwise stated, the described in [RFC3985] and [RFC3916]. Unless otherwise stated, the
mechanisms of [RFC3985] apply and will not be re-described here. mechanisms of [RFC3985] apply and will not be re-described here.
4. Overview 4. Co-Authors
The individuals listed below are co-authors of this document.
Dave Danenberg - Litchfield Communications
Sharon Mantin - Corrigent Systems
5. Overview
The PWE3 MIB Modules architecture provides a layered modular model The PWE3 MIB Modules architecture provides a layered modular model
into which any supported emulated service can be connected to any into which any supported emulated service can be connected to any
supported PSN type. This specific MIB module provides the glue for supported PSN type. This specific MIB module provides the glue for
mapping between the emulated service onto the native PSN service. As mapping between the emulated service onto the native PSN service. As
such the defining of a PW emulated service requires the use of at such the defining of a PW emulated service requires the use of at
least three types of MIB modules. least three types of MIB modules.
Starting from the emulated service, the first type is service- Starting from the emulated service, the first type is service-
specific module, which is emulated signal type dependent. These specific module, which is emulated signal type dependent. These
skipping to change at page 4, line 19 skipping to change at page 4, line 28
The second type is this module, the PW-STD-MIB module, which The second type is this module, the PW-STD-MIB module, which
configures general parameters of the PW that are common to all types configures general parameters of the PW that are common to all types
of emulated services and PSN types. of emulated services and PSN types.
The third type of modules is PSN-specific module. There is a The third type of modules is PSN-specific module. There is a
different module for each type of PSN. These modules associate the different module for each type of PSN. These modules associate the
PW with one or more "tunnels" that carry the service over the PSN. PW with one or more "tunnels" that carry the service over the PSN.
These modules are defined in other documents. These modules are defined in other documents.
5. Structure of the MIB Module 6. Structure of the MIB Module
The MIB Module consists of five tables; The MIB Module consists of five tables;
- The generic configuration and status monitoring objects which are - The generic configuration and status monitoring objects which are
common to all service types and PSN types (pwTable). common to all service types and PSN types (pwTable).
- The PW Performance Current Table (pwPerfCurrentTable) contains PW - The PW Performance Current Table (pwPerfCurrentTable) contains PW
statistics for the current 15-minute period. statistics for the current 15-minute period.
- The PW Performance Interval Table (pwPerfIntervalTable) contains PW - The PW Performance Interval Table (pwPerfIntervalTable) contains PW
skipping to change at page 5, line 5 skipping to change at page 5, line 14
- The mapping table (pwGenFecIndexMappingTable) enables the reverse - The mapping table (pwGenFecIndexMappingTable) enables the reverse
mapping of unique PWid parameters used in genFecSignaling mapping of unique PWid parameters used in genFecSignaling
[pwGroupAttachmentID, pwLocalAttachmentID and pwPeerAttachmentID] and [pwGroupAttachmentID, pwLocalAttachmentID and pwPeerAttachmentID] and
the pwIndex. the pwIndex.
This MIB module uses TCs from [RFC2578], [RFC2579], [RFC2580], This MIB module uses TCs from [RFC2578], [RFC2579], [RFC2580],
[RFC2863], [RFC3411], [RFC3593], [RFC3705], [RFC4001] and [PWTC], and [RFC2863], [RFC3411], [RFC3593], [RFC3705], [RFC4001] and [PWTC], and
references [RFC3413], [RFC4623] and [RFC4720]. references [RFC3413], [RFC4623] and [RFC4720].
6. PW-STD-MIB Module Usage 7. PW-STD-MIB Module Usage
An entry in the PW table (pwTable) MUST exist for all PW types (ATM, An entry in the PW table (pwTable) MUST exist for all PW types (ATM,
FR, Ethernet, SONET, etc.). This table holds generic parameters FR, Ethernet, SONET, etc.). This table holds generic parameters
related to the PW creation and monitoring. related to the PW creation and monitoring.
A conceptual row can be created in the pwTable in one of the A conceptual row can be created in the pwTable in one of the
following ways: following ways:
1) The operator creates a row in the PwTable when configuring the 1) The operator creates a row in the PwTable when configuring the
node for a new service. This mode MUST be supported by the agent, node for a new service. This mode MUST be supported by the agent,
skipping to change at page 5, line 30 skipping to change at page 5, line 39
identifications parameters already unknown to the local node. This identifications parameters already unknown to the local node. This
mode is OPTIONAL. mode is OPTIONAL.
3) The agent MAY create a row in the PwTable automatically due to 3) The agent MAY create a row in the PwTable automatically due to
some auto discovery application, or based on configuration that is some auto discovery application, or based on configuration that is
done through non-SNMP applications. This mode is OPTIONAL. done through non-SNMP applications. This mode is OPTIONAL.
- The agent than creates the rows in the (locally supported) - The agent than creates the rows in the (locally supported)
performance tables and reverse mapping tables in PW-STD-MIB module. performance tables and reverse mapping tables in PW-STD-MIB module.
7. Relations to Other PWE3 MIB Modules 8. Relations to Other PWE3 MIB Modules
- Based on the PSN type defined for the PW, a row is created in PSN - Based on the PSN type defined for the PW, a row is created in PSN
specific module (for example [PWMPLSMIB]) and associated to the PW specific module (for example [PWMPLSMIB]) and associated to the PW
table by the common pwIndex. table by the common pwIndex.
- Based on the PW type defined for the PW, a row is created in - Based on the PW type defined for the PW, a row is created in
service-specific module (for example [CEPMIB]) and associated to the service-specific module (for example [CEPMIB]) and associated to the
PW table by the common pwIndex. PW table by the common pwIndex.
- Unless all the necessary entries in the applicable tables have been - Unless all the necessary entries in the applicable tables have been
created and all the parameters have been consistently configured in created and all the parameters have been consistently configured in
those tables, signaling cannot be performed from the local node, and those tables, signaling cannot be performed from the local node, and
the pwVcOperStatus should report 'notPresent'. the pwVcOperStatus should report 'notPresent'.
8. Relations to the IF-MIB 9. Relations to the IF-MIB
The PW in general is not an ifIndex [RFC2863] on its own, from agent The PW in general is not an ifIndex [RFC2863] on its own, for agent
scalability reasons. The PW is typically associated via the PWE3 MIB scalability reasons. The PW is typically associated via the PWE3 MIB
modules to an ifIndex the PW is emulating. This ifIndex may modules to an ifIndex the PW is emulating. This ifIndex may
represent a physical entity - for example a PW emulating a SONET path represent a physical entity - for example a PW emulating a SONET path
as in CEP: The PW itself is not an ifIndex, however the PW-STD-CEP- as in CEP: The PW itself is not an ifIndex, however the PW-STD-CEP-
MIB module associates the PW to the ifIndex of the path to be MIB module associates the PW to the ifIndex of the path to be
emulated. In some cases, the PW will be associated to an ifIndex emulated. In some cases, the PW will be associated to an ifIndex
representing a virtual interface. An example is VPLS service where representing a virtual interface. An example is VPLS service where
the PW emulates a logical interface of a (logical) bridge. The the PW emulates a logical interface of a (logical) bridge. The
physical ports association to the VPLS service instance is defined in physical ports association to the VPLS service instance is defined in
non-PW MIB modules in this case. non-PW MIB modules in this case.
Exception to the above MAY exist in some implementations, where it is Exception to the above MAY exist in some implementations, where it is
convenient to manage the PW as an ifIndex in the ifTable. A special convenient to manage the PW as an ifIndex in the ifTable. A special
ifType to represent a PW virtual interface (exact number to be ifType to represent a PW virtual interface (exact number to be
assigned by IANA) will be used in the ifTable in this case. assigned by IANA) will be used in the ifTable in this case.
When the PW is managed as an ifIndex, there is no requirement that When the PW is managed as an ifIndex, by default it SHOULD NOT be
this ifIndex will be layered above the respective PSN tunnel ifIndex stacked, i.e. this ifIndex SHOULD NOT be layered above the respective
or the attachment circuit ifIndex or the interface carrying the PSN tunnel ifIndex or the attachment circuit ifIndex or the interface
attachment circuit. carrying the attachment circuit.
Note that the ifIndex that carry the PW toward/from the PSN is in Note that the ifIndex that carries the PW toward/from the PSN is in
general not explicitly configured via PWE3 MIB modules except in rare general not explicitly configured via PWE3 MIB modules except in rare
cases. In most cases the PW is carried inside a PSN tunnel, and the cases. In most cases the PW is carried inside a PSN tunnel, and the
interfaces carrying the tunnel are specified in the related MIB interfaces carrying the tunnel are specified in the related MIB
modules that control the PSN tunnels. modules that control the PSN tunnels.
9. PW Notifications 10. PW Notifications
This MIB module includes notifications for PW entering the up or down This MIB module includes notifications for PW entering the up or down
state, in accordance with the guidelines for interface notifications state, in accordance with the guidelines for interface notifications
as described in [RFC2863]. Implementers should be aware that in many as described in [RFC2863]. Implementers should be aware that in many
systems it is desired to correlate notifications, such that systems it is desired to correlate notifications, such that
notifications will not be emitted if higher hierarchy (such as ports notifications will not be emitted if higher hierarchy (such as ports
or tunnels) notifications are already in effect. Specifically for or tunnels) notifications are already in effect. Specifically for
PWs, it is anticipated that most network's equipment failures turn PWs, it is anticipated that most network's equipment failures turn
into lowerLayerDown state at the PW level, where higher hierarchy into lowerLayerDown state at the PW level, where higher hierarchy
level notification has already been emitted. level notification has already been emitted.
10. Example of the PW MIB Modules Usage When a PW is represented as an ifIndex, it is RECOMMENDED that PW
notifications will be turned off, to avoid duplication with the
ifIndex status change notifications.
11. Example of the PW MIB Modules Usage
In this section we provide an example of using the MIB objects In this section we provide an example of using the MIB objects
described in section 7 to set up a CEP PW over MPLS PSN. While this described in section 7 to set up a CEP PW over MPLS PSN. While this
example is not meant to illustrate every permutation of the MIB, it example is not meant to illustrate every permutation of the MIB, it
is intended as an aid to understanding some of the key concepts. It is intended as an aid to understanding some of the key concepts. It
is meant to be read after going through the MIB itself. is meant to be read after going through the MIB itself.
In this example a PW service for CEP is configured over an MPLS PSN In this example a PW service for CEP is configured over an MPLS PSN
(MPLS-TE tunnel). It uses LDP as in [RFC4447] for service set-up. (MPLS-TE tunnel). It uses LDP as in [RFC4447] for service set-up.
skipping to change at page 8, line 4 skipping to change at page 8, line 47
pwOutboundVcLabel 0xFFFF, -- Will be received by pwOutboundVcLabel 0xFFFF, -- Will be received by
-- signaling protocol -- signaling protocol
pwInboundVcLabel 0xFFFF, -- Will be set by signaling pwInboundVcLabel 0xFFFF, -- Will be set by signaling
-- protocol -- protocol
pwName "Example of CEP PW", pwName "Example of CEP PW",
pwDescr "", pwDescr "",
.. ..
pwAdminStatus up, pwAdminStatus up,
.. ..
} }
11. IANA PWE3 MIB Module 12. IANA PWE3 MIB Module
This section contains the initial version of the IANA-PWE3-MIB. IANA This section contains the initial version of the IANA-PWE3-MIB. IANA
is requested to update this MIB module based on expert review as is requested to update this MIB module based on expert review as
defined in [RFC2434]. Each new assignment of PW type or PW PSN type defined in [RFC2434]. Each new assignment of PW type or PW PSN type
made by IANA based on the procedures described in [RFC4446] should be made by IANA based on the procedures described in [RFC4446] should be
documented in the online version of IANA-PWE3-MIB. The current IANA- documented in the online version of IANA-PWE3-MIB. The current IANA-
PWE3-MIB contains PW types as requested in [RFC4446] and [RFC4863]. PWE3-MIB contains PW types as requested in [RFC4446] and [RFC4863].
IANA-PWE3-MIB DEFINITIONS ::= BEGIN IANA-PWE3-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, transmission MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- [RFC2579]
ianaPwe3MIB MODULE-IDENTITY ianaPwe3MIB MODULE-IDENTITY
LAST-UPDATED "200711121200Z" -- 12 November 2007 12:00:00 GMT LAST-UPDATED "200712091200Z" -- 9 December 2007 12:00:00 GMT
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO CONTACT-INFO
"Internet Assigned Numbers Authority "Internet Assigned Numbers Authority
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292-6601 Marina del Rey, CA 90292-6601
Phone: +1 310 823 9358 Phone: +1 310 823 9358
EMail: iana@iana.org" EMail: iana@iana.org"
DESCRIPTION DESCRIPTION
skipping to change at page 8, line 49 skipping to change at page 9, line 47
MIB modules. MIB modules.
Any additions or changes to the contents of this MIB Any additions or changes to the contents of this MIB
module require either publication of an RFC, Designated module require either publication of an RFC, Designated
Expert Review as defined in RFC 2434, Guidelines for Expert Review as defined in RFC 2434, Guidelines for
Writing an IANA Considerations Section in RFCs, and should Writing an IANA Considerations Section in RFCs, and should
be based on the procedures defined in [RFC4446]. The be based on the procedures defined in [RFC4446]. The
Designated Expert will be selected by the IESG Area Designated Expert will be selected by the IESG Area
Director(s) of the internet Area. Director(s) of the internet Area.
Copyright (C) The IETF Trust (2007). The initial Copyright (C) The IETF Trust (2008). The initial
version of this MIB module was published in RFC yyyy; version of this MIB module was published in RFC yyyy;
for full legal notices see the RFC itself. Supplementary for full legal notices see the RFC itself. Supplementary
information may be available at: information may be available at:
http://www.ietf.org/copyrights/ianamib.html." http://www.ietf.org/copyrights/ianamib.html."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200711121200Z" -- 12 November 2007 12:00:00 GMT REVISION "200712091200Z" -- 9 December 2007 12:00:00 GMT
DESCRIPTION "Original version, published as part of RFC yyyy." DESCRIPTION "Original version, published as part of RFC yyyy."
-- RFC Editor: please fill the yyyy and remove this note. -- RFC Editor: please fill the yyyy and remove this note.
::= { transmission XXXX } ::= { mib-2 XXXX }
-- RFC Editor: please fill the XXXX based on the IANA allocation -- RFC Editor: please fill the XXXX based on the IANA allocation
-- and remove this note. -- and remove this note.
IANAPwTypeTC ::= TEXTUAL-CONVENTION IANAPwTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the PW type (i.e. the carried service). " "Indicates the PW type (i.e. the carried service). "
SYNTAX INTEGER { SYNTAX INTEGER {
other(0), other(0),
frameRelayDlciMartiniMode(1), frameRelayDlciMartiniMode(1),
skipping to change at page 10, line 35 skipping to change at page 11, line 31
introduced in IETF documents. introduced in IETF documents.
" "
SYNTAX BITS { SYNTAX BITS {
pwStatusIndication (0), -- Applicable only if maintenance pwStatusIndication (0), -- Applicable only if maintenance
-- protocol is in use. -- protocol is in use.
pwVCCV (1) pwVCCV (1)
} }
END END
12. Object Definitions 13. Object Definitions
PW-STD-MIB DEFINITIONS ::= BEGIN PW-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Integer32, Unsigned32, Counter32, Counter64, TimeTicks, Integer32, Unsigned32, Counter32, Counter64, TimeTicks,
transmission transmission
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
skipping to change at page 12, line 23 skipping to change at page 13, line 21
This MIB module enables the use of any underlying packet This MIB module enables the use of any underlying packet
switched network (PSN). MIB nodules that will support switched network (PSN). MIB nodules that will support
PW operations over specific PSN types are defined in PW operations over specific PSN types are defined in
separate memos. separate memos.
The indexes for this MIB module are also used to index the The indexes for this MIB module are also used to index the
PSN-specific tables and the PW-specific tables. The PW Type PSN-specific tables and the PW-specific tables. The PW Type
dictates which PW-specific MIB module to use. dictates which PW-specific MIB module to use.
Copyright (C) The IETF Trust (2007). This version Copyright (C) The IETF Trust (2008). This version
of this MIB module is part of RFC XXX; of this MIB module is part of RFC XXX;
For full legal notices see the RFC itself or For full legal notices see the RFC itself or
http://www.ietf.org/copyrights/ianamib.html http://www.ietf.org/copyrights/ianamib.html
-- RFC Ed.: replace XXX with actual RFC number & remove this note -- RFC Ed.: replace XXX with actual RFC number & remove this note
" "
-- Revision history. -- Revision history.
REVISION REVISION
"200711121200Z" -- 12 November 2007 12:00:00 GMT "200711121200Z" -- 12 November 2007 12:00:00 GMT
skipping to change at page 61, line 26 skipping to change at page 62, line 26
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects for use in implementations that "Collection of objects for use in implementations that
support the PW signaling." support the PW signaling."
::= { pwGroups 18 } ::= { pwGroups 18 }
END END
13. Security Considerations 14. Security Considerations
It is clear that this MIB module is potentially useful for monitoring It is clear that this MIB module is potentially useful for monitoring
PW capable PEs. This MIB module can also be used for configuration PW capable PEs. This MIB module can also be used for configuration
of certain objects, and anything that can be configured can be of certain objects, and anything that can be configured can be
incorrectly configured, with potentially disastrous results. incorrectly configured, with potentially disastrous results.
There are number of management objects defined in this MIB module There are number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
skipping to change at page 62, line 44 skipping to change at page 63, line 44
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 con8figured to give access instance of this MIB module, is properly con8figured to give access
to the objects only to those principals (users) that have legitimate to 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.
14. IANA Considerations 15. IANA Considerations
14.1. IANA Considerations for PW-STD-MIB 15.1. ifType for PW
IANA has beeen requested to register a value for PW in the
IANAifType-MIB called ifPwType. When the assignment has been made,
the RFC Editor is asked to document the value here.
15.2. PW MIB Modules OBJECT IDENTIFIER values
A PW may appear as ifIndex in the ifTable, and therefore it is
requested below that the pwStdMIB OBJECT IDENTIFIER will be assigned
under the 'transmission' subtree, as the common practice in assigning
OBJECT IDENTIFIERs for MIB modules representing entities in the
ifTable.
All other MIB modules related to PW management SHOULD be assigned
under the 'mib-2' subtree, individual request will appear in the MIB
module memo IANA Considerations section.
15.3. IANA Considerations for PW-STD-MIB
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
pwStdMIB { transmission ZZZZ } pwStdMIB { transmission ZZZZ }
Editor's Note (to be removed prior to publication): The IANA is Editor's Note (to be removed prior to publication): The IANA is
requested to assign a value for "ZZZZ" under the 'transmission' requested to assign a value for "ZZZZ" under the 'transmission'
subtree and to record the assignment in the SMI Numbers registry. subtree and to record the assignment in the SMI Numbers registry.
When the assignment has been made, the RFC Editor is asked to replace This value SHOULD be the same value assigned for the PW ifType for
"ZZZZ" (here and in the MIB module) with the assigned value and to representation of the PW in the ifTable. When the assignment has
remove this note. been made, the RFC Editor is asked to replace "ZZZZ" (here and in the
MIB module) with the assigned value and to remove this note.
IANA is also requested to register a value for a PW type in the
IANAifType-MIB.
14.2. IANA Considerations for IANA-PWE3-MIB 15.4. IANA Considerations for IANA-PWE3-MIB
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
ianaPwe3MIB { transmission XXXX } ianaPwe3MIB { mib-2 XXXX }
Editor's Note (to be removed prior to publication): The IANA is Editor's Note (to be removed prior to publication): The IANA is
requested to assign a value for "XXXX" under the 'transmission' requested to assign a value for "XXXX" under the 'mib-2' subtree and
subtree and to record the assignment in the SMI Numbers registry. to record the assignment in the SMI Numbers registry. When the
When the assignment has been made, the RFC Editor is asked to replace assignment has been made, the RFC Editor is asked to replace "XXXX"
"XXXX" (here and in the MIB module) with the assigned value and to (here and in the MIB module) with the assigned value and to remove
remove this note. this note.
15. Acknowledgements 16. Acknowledgements
We thank Orly Nicklass for her dedicated review and significant edit We thank Orly Nicklass for her dedicated review and significant edit
at various sections of the document, and Kiran Koushik for his at various sections of the document, and Kiran Koushik for his
contribution. contribution.
16. References 17. References
16.1. Normative References 17.1. Normative References
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate [BCP14] Bradner, S., "Key words for use in RFCs to Indicate
requirement Levels", BCP 14, RFC 2119, March 1997. requirement Levels", BCP 14, RFC 2119, March 1997.
[PWTC] Nadeau, T. and D. Zelig, "Definitions for Textual [PWTC] Nadeau, T. and D. Zelig, "Definitions for Textual
Conventions and OBJECT-IDENTITIES for Pseudowires Conventions and OBJECT-IDENTITIES for Pseudowires
Management", work-in-progress . Management", work-in-progress .
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
skipping to change at page 65, line 16 skipping to change at page 66, line 31
Edge (PWE3) Fragmentation and Reassembly", RFC 4623, Edge (PWE3) Fragmentation and Reassembly", RFC 4623,
August 2006. August 2006.
[RFC4720] Malis, A., Allan, D., and N. Del Regno, "Pseudowire [RFC4720] Malis, A., Allan, D., and N. Del Regno, "Pseudowire
Emulation Edge-to-Edge (PWE3) Frame Check Sequence Emulation Edge-to-Edge (PWE3) Frame Check Sequence
Retention", RFC 4720, November 2006. Retention", RFC 4720, November 2006.
[RFC4863] Martini, L. and G. Swallow, "Wildcard Pseudowire Type", [RFC4863] Martini, L. and G. Swallow, "Wildcard Pseudowire Type",
RFC 4863, May 2007. RFC 4863, May 2007.
16.2. Informative References 17.2. Informative References
[CEPMIB] Zelig, D., Nadeau, T., and R. Cohen, "SONET/SDH Circuit [CEPMIB] Zelig, D., Nadeau, T., and R. Cohen, "SONET/SDH Circuit
Emulation Service Over Packet (CEP) Management Information Emulation Service Over Packet (CEP) Management Information
Base Using SMIv2", work-in-progress . Base Using SMIv2", work-in-progress .
[PWMPLSMIB] [PWMPLSMIB]
Zelig, D. and T. Nadeau, "Pseudowire (PW) Over MPLS PSN Zelig, D. and T. Nadeau, "Pseudowire (PW) Over MPLS PSN
Management Information Base", work-in-progress . Management Information Base", work-in-progress .
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
skipping to change at page 66, line 4 skipping to change at page 67, line 18
Authors' Addresses Authors' Addresses
Thomas D. Nadeau (editor) Thomas D. Nadeau (editor)
BT BT
BT Centre BT Centre
81 Newgate Street 81 Newgate Street
London EC1A 7AJ London EC1A 7AJ
United Kingdom United Kingdom
Email: thomas.nadeau@bt.com Email: thomas.nadeau@bt.com
David Zelig (editor) David Zelig (editor)
Corrigent Systems Corrigent Systems
126, Yigal Alon St. 126, Yigal Alon St.
Tel Aviv, Tel Aviv,
Israel Israel
Phone: +972 3 6945 273 Phone: +972 3 6945 273
Email: davidz@corrigent.com Email: davidz@corrigent.com
Dave Danenberg
Email: dave_danenberg@yahoo.com
Sharon Mantin
Corrigent Systems
126, Yigal Alon St.
Tel Aviv,
Israel
Phone: +972 3 6948 615
Email: sharonma@corrigent.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 39 change blocks. 
84 lines changed or deleted 98 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/