< draft-ietf-pwe3-tdm-mib-10.txt   draft-ietf-pwe3-tdm-mib-11.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 April 29, 2008 Intended status: Standards Track October 20, 2008
Expires: October 31, 2008 Expires: April 23, 2009
Managed Objects for TDM over Packet Switched Network (PSN) Managed Objects for TDM over Packet Switched Network (PSN)
draft-ietf-pwe3-tdm-mib-10.txt draft-ietf-pwe3-tdm-mib-11.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 34 skipping to change at page 1, line 34
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 23, 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 pseudo wire In particular, it describes managed objects for pseudo wire
encapsulation for structured or unstructured TDM (T1, E1, T3, E3) encapsulation for structured or unstructured TDM (T1, E1, T3, E3)
circuits over a Packet Switch Network (PSN). circuits over a Packet Switch Network (PSN).
Table of Contents Table of Contents
skipping to change at page 2, line 18 skipping to change at page 2, line 18
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. TDM MIB module usage . . . . . . . . . . . . . . . . . . . . . 5 6. TDM MIB module usage . . . . . . . . . . . . . . . . . . . . . 5
6.1. Structure of TDM MIB . . . . . . . . . . . . . . . . . . . 5 6.1. Structure of TDM MIB . . . . . . . . . . . . . . . . . . . 5
6.2. TDM Connection configuration Procedure . . . . . . . . . . 6 6.2. TDM Connection configuration Procedure . . . . . . . . . . 6
6.3. TDM PW Monitoring . . . . . . . . . . . . . . . . . . . . 6 6.3. TDM PW Monitoring . . . . . . . . . . . . . . . . . . . . 6
7. Example of actual TDM PW Setup . . . . . . . . . . . . . . . . 7 7. Example of actual TDM PW Setup . . . . . . . . . . . . . . . . 7
8. Object definition . . . . . . . . . . . . . . . . . . . . . . 9 8. Object definition . . . . . . . . . . . . . . . . . . . . . . 9
9. Security considerations . . . . . . . . . . . . . . . . . . . 37 9. Security considerations . . . . . . . . . . . . . . . . . . . 43
10. IANA considerations . . . . . . . . . . . . . . . . . . . . . 39 10. IANA considerations . . . . . . . . . . . . . . . . . . . . . 44
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 45
11.1. Normative references . . . . . . . . . . . . . . . . . . . 39 11.1. Normative references . . . . . . . . . . . . . . . . . . . 45
11.2. Informative references . . . . . . . . . . . . . . . . . . 41 11.2. Informative references . . . . . . . . . . . . . . . . . . 47
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 41 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 47
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 41 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 47
Intellectual Property and Copyright Statements . . . . . . . . . . 42 Intellectual Property and Copyright Statements . . . . . . . . . . 48
1. Introduction 1. Introduction
This document describes a model for managing TDM pseudo wires, i.e. This document describes a model for managing TDM pseudo wires, i.e.
TDM data encapsulated for transmission over a Packet Switched Network TDM data encapsulated for transmission over a Packet Switched Network
(PSN). The term TDM in this document is limited to the scope of PDH (PSN). The term TDM in this document is limited to the scope of PDH
hierarchy. It is currently specified to carry any TDM Signals in hierarchy. It is currently specified to carry any TDM Signals in
either Structure Agnostic Transport mode (E1, T1, E3 and T3) or in either Structure Agnostic Transport mode (E1, T1, E3 and T3) or in
Structure Aware Transport mode (E1, T1 and NxDS0) as defined in PWE3 Structure Aware Transport mode (E1, T1 and NxDS0) as defined in PWE3
TDM Requirements document [RFC4197]. TDM Requirements document [RFC4197].
skipping to change at page 10, line 9 skipping to change at page 11, line 4
PerfCurrentCount, PerfIntervalCount PerfCurrentCount, PerfIntervalCount
FROM PerfHist-TC-MIB FROM PerfHist-TC-MIB
pwIndex pwIndex
FROM PW-STD-MIB FROM PW-STD-MIB
PwCfgIndexOrzero PwCfgIndexOrzero
FROM PW-TC-STD-MIB; FROM PW-TC-STD-MIB;
-- The TDM MIB -- The TDM MIB
pwTDMMIB MODULE-IDENTITY pwTDMMIB MODULE-IDENTITY
LAST-UPDATED "200804290000Z" LAST-UPDATED "200804290000Z"
ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3) ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" Orly Nicklass " Orly Nicklass
Postal: Nokia Siemens Networks Postal: RADVISION Ltd.
3 Hanagar st. Neve Ne'eman 24Raul Wallenberg St.
Hod-Hasharon, Israel Tel Aviv, Israel
Email: orly.nicklass@nsn.com Email: orlyn@radvision.com
The PWE3 Working Group (email distribution pwe3@ietf.org, The PWE3 Working Group (email distribution pwe3@ietf.org,
http://www.ietf.org/html.charters/pwe3-charter.html) http://www.ietf.org/html.charters/pwe3-charter.html)
" "
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for "This MIB contains managed object definitions for
encapsulating TDM (T1,E1, T3, E3, NxDS0) as encapsulating TDM (T1,E1, T3, E3, NxDS0) as
pseudo-wires over packet-switching networks (PSN). pseudo-wires over packet-switching networks (PSN).
skipping to change at page 38, line 13 skipping to change at page 44, line 4
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
The pwTDMTable and pwTDMCfgTable contain objects of TDM PW parameters The pwTDMTable and pwTDMCfgTable contain objects of TDM PW parameters
on a Provider Edge (PE) device. Unauthorized access to objects in on a Provider Edge (PE) device. Unauthorized access to objects in
these tables could result in disruption of traffic on the network. these tables could result in disruption of 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, pwTDMPerfCurrentTable, pwTDMPerfIntervalTable and The pwTDMTable, pwTDMPerfCurrentTable, pwTDMPerfIntervalTable and
pwTDMPerf1DayIntervalTable collectively show the TDM pseudo wire pwTDMPerf1DayIntervalTable collectively show the TDM 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.
10. IANA considerations 10. 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
---------- ----------------------- ---------- -----------------------
pwTDMMIB { mib-2 XXX } pwTDMMIB { mib-2 XXX }
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 "XXX" under the mib-2 subtree and to requested to assign a value for "XXX" under the mib-2 subtree and to
record the assignment in the SMI Numbers registry. When the record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note. this note.
11. References 11. References
skipping to change at page 41, line 35 skipping to change at page 47, line 35
12. Acknowledgements 12. Acknowledgements
This document was produced by the PWE3 Working Group. Special thanks This document was produced by the PWE3 Working Group. Special thanks
to Yaakov Stein, Doron Tzur, Sasha Vainshtein; and Ron Cohen; for to Yaakov Stein, Doron Tzur, Sasha Vainshtein; and Ron Cohen; for
close review and good suggestions. close review and good suggestions.
Author's Address Author's Address
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
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). 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
skipping to change at page 42, line 44 skipping to change at line 1901
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. 16 change blocks. 
37 lines changed or deleted 32 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/