< draft-ietf-pwe3-pw-atm-mib-05.txt   draft-ietf-pwe3-pw-atm-mib-06.txt >
Pseudo Wire Edge to Edge Emulation O. Nicklass Pseudo Wire Edge to Edge Emulation O. Nicklass
Internet-Draft Nokia Siemens Networks Internet-Draft RADVISION Ltd.
Intended status: Standards Track S. Sathappan Intended status: Standards Track S. Sathappan
Expires: October 31, 2008 M. Venkatesan Expires: April 15, 2009 M. Venkatesan
Marconi Communications Marconi Communications
T. Nadeau T. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
April 29, 2008 October 12, 2008
Managed Objects for ATM over Packet Switched Network (PSN) Managed Objects for ATM over Packet Switched Network (PSN)
draft-ietf-pwe3-pw-atm-mib-05.txt draft-ietf-pwe3-pw-atm-mib-06.txt
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 38 skipping to change at page 1, line 38
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 October 31, 2008. This Internet-Draft will expire on April 15, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2008).
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 the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling ATM In particular, it describes managed objects for modeling ATM
Pseudowire (PW) carrying ATM cells over Packet Switch Network (PSN). Pseudowire (PW) carrying ATM cells over Packet Switch Network (PSN).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. The Internet-Standard Management Framework . . . . . . . . . . 4 4. The Internet-Standard Management Framework . . . . . . . . . . 4
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Relation to other PW-MIB modules . . . . . . . . . . . . . . . 5 6. Relation to other PW-MIB modules . . . . . . . . . . . . . . . 5
7. ATM-PW MIB Usage . . . . . . . . . . . . . . . . . . . . . . . 6 7. ATM-PW MIB Usage . . . . . . . . . . . . . . . . . . . . . . . 6
8. Structure of the MIB module . . . . . . . . . . . . . . . . . 7 8. Structure of the MIB module . . . . . . . . . . . . . . . . . 7
9. Object definition . . . . . . . . . . . . . . . . . . . . . . 8 9. Object definition . . . . . . . . . . . . . . . . . . . . . . 8
10. Security considerations . . . . . . . . . . . . . . . . . . . 33 10. Security considerations . . . . . . . . . . . . . . . . . . . 36
11. IANA considerations . . . . . . . . . . . . . . . . . . . . . 34 11. IANA considerations . . . . . . . . . . . . . . . . . . . . . 37
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 38
12.1. Normative references . . . . . . . . . . . . . . . . . . 35 12.1. Normative references . . . . . . . . . . . . . . . . . . 38
12.2. Informative references . . . . . . . . . . . . . . . . . 36 12.2. Informative references . . . . . . . . . . . . . . . . . 39
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 36 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39
Intellectual Property and Copyright Statements . . . . . . . . . . 38 Intellectual Property and Copyright Statements . . . . . . . . . . 41
1. Introduction 1. Introduction
This document describes a model for managing "emulated" ATM services This document describes a model for managing "emulated" ATM services
over a Packet Switched Network(PSN). over a Packet Switched Network(PSN).
The document follows the requirements for Pseudo-Wire Emulation Edge- The document follows the requirements for Pseudo-Wire Emulation Edge-
to-Edge [PWREQ], and closely related to [ATMENCAP] and [ATMTRANS] to-Edge [PWREQ], and closely related to [ATMENCAP] and [ATMTRANS]
which describe the encapsulation of ATM signals and provide the which describe the encapsulation of ATM signals and provide the
Emulation Service over a Packet Switched Network. Emulation Service over a Packet Switched Network.
skipping to change at page 9, line 4 skipping to change at page 8, line 47
pwAtmMIB MODULE-IDENTITY pwAtmMIB MODULE-IDENTITY
LAST-UPDATED "200804290000Z" -- 2008 LAST-UPDATED "200804290000Z" -- 2008
ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3) ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Senthilkumar Sathappan "Senthilkumar Sathappan
Postal: 1000 Marconi Drive Postal: 1000 Marconi Drive
Warrendale PA 15086 Warrendale PA 15086
Tel: +1-724-742-6147 Tel: +1-724-742-6147
Email: senthilkumar.sathappan@marconi.com Email: senthilkumar.sathappan@marconi.com
Marichetty Venkatesan Marichetty Venkatesan
Postal: 1000 Marconi Drive Postal: 1000 Marconi Drive
Warrendale PA 15086 Warrendale PA 15086
Tel: +1-724-742-7058 Tel: +1-724-742-7058
Email: venkatesan.marichetty@marconi.com Email: venkatesan.marichetty@marconi.com
Thomas D. Nadeau Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Tel: +1-978-497-3051 Tel: +1-978-497-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Orly Nicklass Orly Nicklass
Postal: Nokia Siemens Networks Postal: RADVISION Ltd.
3 Hanagar st. Neve Ne'eman 24 Raul Wallenberg
Hod-Hasharon, Israel Tel Aviv, Israel
Email: orly.nicklass@nsn.com Email: orlyn@radvision.com
Discussion and general questions should be posed to Discussion and general questions should be posed to
the PWE3 Working Group (pwe3@ietf.org)." the PWE3 Working Group (pwe3@ietf.org)."
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for "This MIB contains managed object definitions for
Pseudo Wire emulation of ATM over Packet Switched Pseudo Wire emulation of ATM over Packet Switched
Networks (PSN). Networks (PSN).
This MIB supplements the PW-STD-MIB module. This MIB supplements the PW-STD-MIB module.
skipping to change at page 14, line 26 skipping to change at page 15, line 4
--Generic ATM PW table for all types of ATM PW connection. --Generic ATM PW table for all types of ATM PW connection.
pwAtmCfgTable OBJECT-TYPE pwAtmCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwAtmCfgEntry SYNTAX SEQUENCE OF PwAtmCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies generic information for an ATM PW "This table specifies generic information for an ATM PW
to be carried over PSN in any mode." to be carried over PSN in any mode."
::= { pwAtmObjects 5 } ::= { pwAtmObjects 5 }
pwAtmCfgEntry OBJECT-TYPE pwAtmCfgEntry OBJECT-TYPE
SYNTAX PwAtmCfgEntry SYNTAX PwAtmCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a set of parameters for "This table contains a set of parameters for
the ATM PW that needs to be adapted and carried the ATM PW that needs to be adapted and carried
over PSN. This table is indexed by pwIndex from over PSN. This table is indexed by pwIndex from
pwTable. An entry is created for every newly pwIndex pwTable. An entry is created for every newly ATM
in the pwTable. Unless otherwise specified, all type associated pwIndex in the pwTable. Unless
read-write objects in this table MAY otherwise specified, all read-write objects in
be changed when the PW is defined as not active this table MAY be changed when the PW is defined
and all RW objects values must persist as not active and all RW objects values must
after reboot" persist after reboot"
REFERENCE REFERENCE
"See [PWMIB] " "See [PWMIB] "
INDEX { pwIndex } INDEX { pwIndex }
::= { pwAtmCfgTable 1 } ::= { pwAtmCfgTable 1 }
PwAtmCfgEntry ::= SEQUENCE { PwAtmCfgEntry ::= SEQUENCE {
pwAtmCfgMaxCellConcatenation Unsigned32, pwAtmCfgMaxCellConcatenation Unsigned32,
pwAtmCfgFarEndMaxCellConcatenation Unsigned32, pwAtmCfgFarEndMaxCellConcatenation Unsigned32,
pwAtmCfgTimeoutMode INTEGER, pwAtmCfgTimeoutMode INTEGER,
skipping to change at page 33, line 39 skipping to change at page 36, line 41
access to objects in these tables could result in disruption of access to objects in these tables could result in disruption of
traffic on the network. traffic on the network.
The use of stronger mechanisms such as SNMPv3 security should be The use of stronger mechanisms such as SNMPv3 security should be
considered where possible. Specifically, SNMPv3 VACM and USM MUST be considered where possible. Specifically, SNMPv3 VACM and USM MUST be
used with any SNMPV3 agent, which implements this MIB module. used with any SNMPV3 agent, which implements this MIB module.
Administrators should consider whether read access to these objects Administrators should consider whether read access to these objects
should be allowed, since read access may be undesirable under certain should be allowed, since read access may be undesirable under certain
circumstances. circumstances.
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:
The pwTDMTable, pwAtmPerfCurrentTable, pwAtmPerfIntervalTable and The pwATMCfgTable, pwAtmPerfCurrentTable, pwAtmPerfIntervalTable and
pwAtmPerf1DayIntervalTable collectively show the ATM pseudo wire pwAtmPerf1DayIntervalTable collectively show the ATM pseudo wire
connectivity topology and its performance characteristics. connectivity topology and its performance characteristics.
If an Administrator does not want to reveal this information, then If an Administrator does not want to reveal this information, then
these tables should be considered sensitive/vulnerable. these tables should be considered sensitive/vulnerable.
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 implementers consider the security features as It is RECOMMENDED that implementers 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.
11. IANA considerations 11. IANA considerations
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
---------- ----------------------- ---------- -----------------------
skipping to change at page 36, line 37 skipping to change at page 39, line 37
December 2002. December 2002.
13. Acknowledgements 13. Acknowledgements
This document was produced by the PWE3 Working Group. Special thanks This document was produced by the PWE3 Working Group. Special thanks
to Bert Wijnen for close review and good suggestions. to Bert Wijnen for close review and good suggestions.
Authors' Addresses Authors' Addresses
Orly Nicklass Orly Nicklass
Nokia Siemens Networks RADVISION Ltd.
3 Hanagar St. 24 Raul Wallenberg St.
Hod Hasharon Tel Aviv
ISRAEL ISRAEL
Phone: +972 9 7751290 Phone: +972 3 7679444
Email: orly.nicklass@nsn.com Email: orlyn@radvision.com
Senthilkumar Sathappan Senthilkumar Sathappan
Marconi Communications Marconi Communications
1000 Marconi Drive 1000 Marconi Drive
Warrendale, PA 15086 Warrendale, PA 15086
USA USA
Phone: +1-724-742-6147 Phone: +1-724-742-6147
Email: senthilkumar.sathappan@marconi.com Email: senthilkumar.sathappan@marconi.com
Marichetty Venkatesan Marichetty Venkatesan
skipping to change at page 38, line 44 skipping to change at line 1698
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. 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 that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 19 change blocks. 
43 lines changed or deleted 39 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/