draft-ietf-opsawg-rfc5066bis-00.txt   draft-ietf-opsawg-rfc5066bis-01.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Obsoletes: 5066 (if approved) December 25, 2012 Obsoletes: 5066 (if approved) January 07, 2013
Intended status: Standards Track Intended status: Standards Track
Expires: June 28, 2013 Expires: July 11, 2013
Interface Stack Capability MIB Interface Stack Capability MIB
draft-ietf-opsawg-rfc5066bis-00.txt draft-ietf-opsawg-rfc5066bis-01.txt
Abstract Abstract
This document defines Management Information Base (MIB) module for This document defines Management Information Base (MIB) module for
use with network management protocols in TCP/IP-based internets. use with network management protocols in TCP/IP-based internets.
This document defines a set of objects, describing cross-connect This document defines a set of objects, describing cross-connect
capability of a managed device with multi-layer (stacked) interfaces, capability of a managed device with multi-layer (stacked) interfaces,
extending the stack management objects in the Interfaces Group MIB extending the stack management objects in the Interfaces Group MIB
and the Inverted Stack Table MIB modules. This document obsoletes and the Inverted Stack Table MIB modules. This document obsoletes
RFC 5066. It amends that specification by moving the entire EFM-CU- RFC 5066. It amends that specification by taking out the entire EFM-
MIB module along with the relevant descriptive text, to a separate CU-MIB module along with the relevant descriptive text. That MIB
document, maintained by the Institute of Electrical and Electronics module will be part of a separate document, maintained by the
Engineers (IEEE) 802.3.1 working group. Institute of Electrical and Electronics Engineers (IEEE) 802.3
working group.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 28, 2013. This Internet-Draft will expire on July 11, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 24 skipping to change at page 2, line 25
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Relation to Other MIB Modules . . . . . . . . . . . . . . . . 3 3. Relation to Other MIB Modules . . . . . . . . . . . . . . . . 3
3.1. Relation to the EFMCu Interfaces MIB Module . . . . . . . 4 3.1. Relation to the EFMCu Interfaces MIB Module . . . . . . . 4
3.2. Relation to Interfaces Group MIB Module . . . . . . . . . 4 3.2. Relation to Interfaces Group MIB Module . . . . . . . . . 4
3.2.1. ifCapStackTable usage example for bonded xDSL 3.2.1. ifCapStackTable usage example for bonded xDSL
interfaces . . . . . . . . . . . . . . . . . . . . . . 4 interfaces . . . . . . . . . . . . . . . . . . . . . . 4
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 5 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Interface Stack Capability MIB Overview . . . . . . . . . 5 4.1. Interface Stack Capability MIB Overview . . . . . . . . . 5
5. Interface Stack Capability MIB Definitions . . . . . . . . . . 5 5. Interface Stack Capability MIB Definitions . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
This memo defines a Management Information Base (MIB) module for use This memo defines a Management Information Base (MIB) module for use
with network management protocols in the Internet community, with network management protocols in the Internet community,
describing the cross-connect capability of a stacked interface. describing the cross-connect capability of a stacked interface.
2BASE-TL and 10PASS-TS physical interfaces, defined in the IEEE 2BASE-TL and 10PASS-TS physical interfaces, defined in the IEEE
Standard 802.3 [802.3], as well the xDSL Multi-Pair Bonded interfaces Standard 802.3 [802.3], as well the xDSL Multi-Pair Bonded interfaces
defined in ITU-T recommendations G.998.1 [G.998.1], G.998.2 [G.998.2] defined in ITU-T recommendations G.998.1 [G.998.1], G.998.2 [G.998.2]
and G.998.3 [G.998.3] are prime examples of the stacked interfaces, and G.998.3 [G.998.3] are prime examples of the stacked interfaces,
which MAY require the management information about the cross-connect which MAY require the management information about the cross-connect
capability. capability.
The previous version of this document, RFC 5066 [RFC5066], defined The previous version of this document, RFC 5066 [RFC5066], defined
EFM-CU-MIB module along with the relevant descriptive text. This EFM-CU-MIB module along with the relevant descriptive text. This
version moves the entire EFM-CU-MIB module along with the relevant version removes the entire EFM-CU-MIB module along with the relevant
descriptive text, to a separate document, maintained by the Institute descriptive text. That MIB module will be part of a separate
of Electrical and Electronics Engineers (IEEE) 802.3.1 working group. document, maintained by the Institute of Electrical and Electronics
In addition the Security Considerations section was updated to Engineers (IEEE) 802.3 working group. In addition the Security
conform to the latest recommended boilerplate text, along with the Considerations section was updated to conform to the latest
relevant references. recommended boilerplate text, along with the relevant references.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies MIB Structure of Management Information (SMI). This memo specifies MIB
modules that are compliant to the SMIv2, which is described in STD modules that are compliant to the SMIv2, which is described in STD
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580]. 2580 [RFC2580].
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", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119].
3. Relation to Other MIB Modules 3. Relation to Other MIB Modules
This section outlines the relationship of the MIB modules defined in This section outlines the relationship of the MIB modules defined in
this document with other MIB modules described in the relevant RFCs. this document with other MIB modules described in the relevant RFCs.
Specifically, the Ethernet in the First Mile Copper (EFMCu) Specifically, the Ethernet in the First Mile Copper (EFMCu)
Interfaces MIB (EFM-CU-MIB) and the Interfaces Group MIB (IF-MIB) Interfaces MIB (EFM-CU-MIB) and the Interfaces Group MIB (IF-MIB)
module are discussed. module are discussed.
3.1. Relation to the EFMCu Interfaces MIB Module 3.1. Relation to the EFMCu Interfaces MIB Module
The EFM-CU-MIB module defined in the previous version of this The EFM-CU-MIB module defined in [RFC5066], along with the relevant
document, along with the relevant descriptive text, is now moved to a descriptive text, is now moved to a separate, IEEE maintained
separate, IEEE maintained document, IEEE Std 802.3.1-2011 [802.3.1], document, IEEE Std 802.3.1-2011 [802.3.1], which also renamed the
which also renamed the EFM-CU-MIB to IEEE8023-EFM-CU-MIB. EFM-CU-MIB to IEEE8023-EFM-CU-MIB.
3.2. Relation to Interfaces Group MIB Module 3.2. Relation to Interfaces Group MIB Module
Stacked (a.k.a. aggregated or bonded) interfaces are managed using Stacked (a.k.a. aggregated or bonded) interfaces are managed using
generic interface management objects defined in the IF-MIB [RFC2863]. generic interface management objects defined in the IF-MIB [RFC2863].
The stack management (i.e., actual connection of the sub-layers to The stack management (i.e., actual connection of the sub-layers to
the top-layer interface) is done via the ifStackTable, as defined in the top-layer interface) is done via the ifStackTable, as defined in
the IF-MIB [RFC2863], and its inverse ifInvStackTable, as defined in the IF-MIB [RFC2863], and its inverse ifInvStackTable, as defined in
the IF-INVERTED-STACK-MIB [RFC2864]. the IF-INVERTED-STACK-MIB [RFC2864].
skipping to change at page 4, line 38 skipping to change at page 4, line 39
3.2.1. ifCapStackTable usage example for bonded xDSL interfaces 3.2.1. ifCapStackTable usage example for bonded xDSL interfaces
An bonded xDSL interface, for example IEEE 2BASE-TL or 10PASS-TS or An bonded xDSL interface, for example IEEE 2BASE-TL or 10PASS-TS or
ITU-T G.998.2 interface, can aggregate or bond a number of individual ITU-T G.998.2 interface, can aggregate or bond a number of individual
xDSL interfaces, referred to as Physical Medium Entity (PME) sub- xDSL interfaces, referred to as Physical Medium Entity (PME) sub-
layer devices in IEEE 802.3 or Bonding Channel Entity (BCE) in ITU-T layer devices in IEEE 802.3 or Bonding Channel Entity (BCE) in ITU-T
G.998. G.998.
A generic bonded xDSL multiport device can have a number of bonded A generic bonded xDSL multiport device can have a number of bonded
xDSL interfaces, referred to as Physical Coding Sublayer (PCS) in xDSL interfaces, referred to as Physical Coding Sublayer (PCS) in
IEEE 802.3 or Generic Bonding Sublayer (GBS) in ITU-T G.998 cross- IEEE 802.3 or Generic Bonding Sublayer (GBS) in ITU-T G.998, cross-
connected, via a configurable cross-connect fabric, to a number of connected, via a configurable cross-connect fabric, to a number of
underlying PMEs/BCEs, with a single PCS/GBS per PME/GBE relationship. underlying PMEs/BCEs, with a single PCS/GBS per PME/GBE relationship.
The ifStackTable is indexed by the ifIndex values of the bonded PCS/ The ifStackTable is indexed by the ifIndex values of the bonded PCS/
GBS interface and the PMEs/BCEs connected to it. The ifStackTable GBS interface and the PMEs/BCEs connected to it. The ifStackTable
allows a Network Management application to determine which PMEs/BCEs allows a Network Management application to determine which PMEs/BCEs
are connected to a particular PCS/GBS and change connections (if are connected to a particular PCS/GBS and change connections (if
supported by the application). The ifInvStackTable, being an supported by the application). The ifInvStackTable, being an
inverted version of the ifStackTable, provides an efficient means for inverted version of the ifStackTable, provides an efficient means for
a Network Management application to read a subset of the ifStackTable a Network Management application to read a subset of the ifStackTable
skipping to change at page 6, line 18 skipping to change at page 6, line 21
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
ifInvStackGroup ifInvStackGroup
FROM IF-INVERTED-STACK-MIB -- [RFC2864] FROM IF-INVERTED-STACK-MIB -- [RFC2864]
; ;
ifCapStackMIB MODULE-IDENTITY ifCapStackMIB MODULE-IDENTITY
LAST-UPDATED "201212250000Z" -- December 25, 2012 LAST-UPDATED "201301070000Z" -- January 07, 2013
ORGANIZATION "IETF Operations and Management Area Working Group" ORGANIZATION "IETF Operations and Management Area Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://datatracker.ietf.org/wg/opsawg/charter/ http://datatracker.ietf.org/wg/opsawg/charter/
Mailing Lists: Mailing Lists:
General Discussion: opsawg@ietf.org General Discussion: opsawg@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/opsawg To Subscribe: https://www.ietf.org/mailman/listinfo/opsawg
Chair: Scott Bradner Chair: Scott Bradner
skipping to change at page 6, line 49 skipping to change at page 6, line 52
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
EMail: edward.beili@actelis.com" EMail: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to describe "The objects in this MIB module are used to describe
cross-connect capabilities of stacked (layered) interfaces, cross-connect capabilities of stacked (layered) interfaces,
complementing ifStackTable and ifInvStackTable defined in complementing ifStackTable and ifInvStackTable defined in
IF-MIB and IF-INVERTED-STACK-MIB, respectively. IF-MIB and IF-INVERTED-STACK-MIB, respectively.
Copyright (C) The IETF Trust (2012). This version Copyright (C) The IETF Trust (2013). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200711070000Z" -- November 07, 2007 REVISION "200711070000Z" -- November 07, 2007
DESCRIPTION "Initial version, published as RFC 5066." DESCRIPTION "Initial version, published as RFC 5066."
REVISION "201212250000Z" -- December 25, 2012 REVISION "201301070000Z" -- January 07, 2013
DESCRIPTION "Re-published as RFC XXXX. EFM-CU-MIB has been DESCRIPTION "Re-published as RFC XXXX. EFM-CU-MIB has been
relocated to IEEE Std. 802.3.1. Since HUBMIB relocated to IEEE Std. 802.3.1. Since HUBMIB
WG has been concluded, the IF-CAP-STACK-MIB WG has been concluded, the IF-CAP-STACK-MIB
is now maintained by OPSAWG." is now maintained by OPSAWG."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 166 } ::= { mib-2 166 }
skipping to change at page 12, line 51 skipping to change at page 13, line 7
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
Object identifier 166 for the ifCapStackMIB MODULE-IDENTITY have been No action is required from IANA as the OID for ifCapStackMIB MODULE-
allocated by IANA in the MIB-2 sub-tree. IDENTITY was already allocated in [RFC5066].
8. Acknowledgments 8. Acknowledgments
This document was produced by the [OPSAWG] working group. This document was produced by the [OPSAWG] working group, whose
efforts were greatly advanced by the contributions of the following
people (in alphabetical order):
Dan Romascanu (Avaya)
This document is based on the RFC 5066, authored by Edward Beili of This document is based on the RFC 5066, authored by Edward Beili of
Actelis Networks, and produced by the, now concluded, [HUBMIB] Actelis Networks, and produced by the, now concluded, [HUBMIB]
working group. working group.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
 End of changes. 17 change blocks. 
30 lines changed or deleted 36 lines changed or added

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