xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIB
RFC 6766
Document | Type | RFC - Proposed Standard (February 2013) Errata | |
---|---|---|---|
Author | Edward Beili | ||
Last updated | 2020-01-21 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
IESG | Responsible AD | Benoît Claise | |
Send notices to | (None) |
RFC 6766
Beili Standards Track [Page 47] RFC 6766 G.Bond/TDIM MIB February 2013 g9983SvcSize, g9983SvcRowStatus, g9983PortStatFltStatus } STATUS current DESCRIPTION "A collection of objects representing management information for G.Bond/TDIM ports." ::= { g9983Groups 1 } g9983FecGroup OBJECT-GROUP OBJECTS { g9983PortCapFecSupported, g9983PortConfFecAdminState, g9983PortStatFecOperState, g9983PortConfFecWordSize, g9983PortConfFecRedundancySize, g9983PortConfFecInterleaverType, g9983PortConfFecInterleaverDepth, g9983PortCapFecMaxWordSize, g9983PortCapFecMaxRedundancySize, g9983PortCapFecInterleaverTypeSupported, g9983PortCapFecMaxInterleaverDepth } STATUS current DESCRIPTION "A collection of objects supporting the OPTIONAL Forward Error Correction (FEC) and Interleaver function in G.Bond/TDIM ports." ::= { g9983Groups 2 } g9983AlarmConfGroup OBJECT-GROUP OBJECTS { g9983PortConfSvcUpDownEnable } STATUS current DESCRIPTION "A collection of objects required for configuration of alarm thresholds and notifications in G.Bond/TDIM ports." ::= { g9983Groups 3 } g9983NotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { g9983SvcUp, g9983SvcDown } STATUS current Beili Standards Track [Page 48] RFC 6766 G.Bond/TDIM MIB February 2013 DESCRIPTION "This group supports notifications of significant conditions associated with G.Bond/TDIM ports." ::= { g9983Groups 4 } g9983PerfCurrGroup OBJECT-GROUP OBJECTS { g9983PortPmCur15MinValidIntervals, g9983PortPmCur15MinInvalidIntervals, g9983PortPmCur15MinTimeElapsed, g9983PortPmCur15MinCrc4s, g9983PortPmCur15MinCrc6s, g9983PortPmCur15MinCrc8s, g9983PortPmCur1DayValidIntervals, g9983PortPmCur1DayInvalidIntervals, g9983PortPmCur1DayTimeElapsed, g9983PortPmCur1DayCrc4s, g9983PortPmCur1DayCrc6s, g9983PortPmCur1DayCrc8s, g9983SvcPmCur15MinValidIntervals, g9983SvcPmCur15MinInvalidIntervals, g9983SvcPmCur15MinTimeElapsed, g9983SvcPmCur15MinDowns, g9983SvcPmCur1DayValidIntervals, g9983SvcPmCur1DayInvalidIntervals, g9983SvcPmCur1DayTimeElapsed, g9983SvcPmCur1DayDowns } STATUS current DESCRIPTION "A collection of objects supporting OPTIONAL current Performance Monitoring information for G.Bond/TDIM ports." ::= { g9983Groups 5 } g9983Perf15MinGroup OBJECT-GROUP OBJECTS { g9983PortPm15MinIntervalMoniTime, g9983PortPm15MinIntervalCrc4s, g9983PortPm15MinIntervalCrc6s, g9983PortPm15MinIntervalCrc8s, g9983PortPm15MinIntervalValid, g9983SvcPm15MinIntervalMoniTime, g9983SvcPm15MinIntervalDowns, g9983SvcPm15MinIntervalValid } STATUS current Beili Standards Track [Page 49] RFC 6766 G.Bond/TDIM MIB February 2013 DESCRIPTION "A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond/TDIM ports, during previous 15-minute intervals." ::= { g9983Groups 6 } g9983Perf1DayGroup OBJECT-GROUP OBJECTS { g9983PortPm1DayIntervalMoniTime, g9983PortPm1DayIntervalCrc4s, g9983PortPm1DayIntervalCrc6s, g9983PortPm1DayIntervalCrc8s, g9983PortPm1DayIntervalValid, g9983SvcPm1DayIntervalMoniTime, g9983SvcPm1DayIntervalDowns, g9983SvcPm1DayIntervalValid } STATUS current DESCRIPTION "A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond/TDIM ports, during previous 1-day intervals." ::= { g9983Groups 7 } -- Compliance Statements g9983Compliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for G.Bond/TDIM interfaces. Compliance with the following external compliance statements is REQUIRED: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 GBOND-MIB gBondCompliance" MODULE -- this module MANDATORY-GROUPS { g9983BasicGroup, g9983AlarmConfGroup, g9983NotificationGroup } GROUP g9983FecGroup Beili Standards Track [Page 50] RFC 6766 G.Bond/TDIM MIB February 2013 DESCRIPTION "Support for this group is only required for implementations supporting the G.Bond/TDIM FEC and Interleaver function." GROUP g9983PerfCurrGroup DESCRIPTION "Support for this group is only required for implementations supporting Performance Monitoring." GROUP g9983Perf15MinGroup DESCRIPTION "Support for this group is only required for implementations supporting historical Performance Monitoring." GROUP g9983Perf1DayGroup DESCRIPTION "Support for this group is only required for implementations supporting historical Performance Monitoring." ::= { g9983Compliances 1 } END 7. Security Considerations There are a number of managed objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability: o Changing of the g9983PortConfAdminServices object may lead to a potential service disruption, by changing a particular service's position (therefore changing its drop priority) or even removing the service from the link altogether. o Changing of g9983SvcTable configuration parameters (e.g., g9983SvcType or g9983SvcSize) may lead to a potential service impairment; for example, a TDM service would be dropped if there is not enough actual bandwidth on the bonded link to support this service. o Changing of g9983PortConfTable configuration parameters (e.g., g9983PortConfFecAdminState) may lead to anything from link quality and rate degradation to a complete link initialization failure. Beili Standards Track [Page 51] RFC 6766 G.Bond/TDIM MIB February 2013 Some of the readable objects in this MIB module (i.e., those with MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments since, collectively, they provide information about the performance of network interfaces and can reveal some aspects of their configuration. In particular, since a bonded xDSL port can be comprised of multiple Unshielded Twisted Pair (UTP) voice-grade copper, located in the same bundle with other pairs belonging to another operator/customer, it is theoretically possible to eavesdrop on a G.Bond transmission, simply by "listening" to cross-talk from the bonded pairs, especially if the operating parameters of the G.Bond link in question are known. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: o g9983PortStatFecOperState in the g9983PortStatTable indicates whether the FEC function is enabled, which may aid in deciphering the G.Bond/TDIM transmissions. o The g9983OperSvcTable provides current operational service configuration, which may aid in deciphering the G.Bond/TDIM transmissions. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. Implementations SHOULD provide the security features described by the SNMPv3 framework (see [RFC3410]), and implementations claiming compliance to the SNMPv3 standard MUST include full support for authentication and privacy via the User-based Security Model (USM) [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations MAY also provide support for the Transport Security Model (TSM) [RFC5591] in combination with a secure transport such as SSH [RFC5592] or TLS/DTLS [RFC6353]. Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. Beili Standards Track [Page 52] RFC 6766 G.Bond/TDIM MIB February 2013 8. IANA Considerations IANA has allocated value 210 as the Object identifier for g9983MIB MODULE-IDENTITY <http://www.iana.org/> in the MIB-2 transmission sub-tree. 9. Acknowledgments This document was produced by the [ADSLMIB] working group. Special thanks to Dan Romascanu for his meticulous review of this text. 10. References 10.1. Normative References [G.998.3] ITU-T, "Multi-pair bonding using time-division inverse multiplexing", ITU-T Recommendation G.998.3, January 2005, <http://www.itu.int/rec/T-REC-G.998.3/en>. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. [RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3705, February 2004. Beili Standards Track [Page 53] RFC 6766 G.Bond/TDIM MIB February 2013 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model", RFC 3826, June 2004. [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", RFC 5591, June 2009. [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, June 2009. [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", RFC 6353, July 2011. [RFC6765] Beili, E. and M. Morgenstern, "xDSL Multi-Pair Bonding (G.Bond) MIB", RFC 6765, February 2013. [TR-159] Beili, E. and M. Morgenstern, "Management Framework for xDSL Bonding", Broadband Forum Technical Report TR-159, December 2008, <http://www.broadband-forum.org/technical/ download/TR-159.pdf>. 10.2. Informative References [ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", <http://datatracker.ietf.org/wg/adslmib/charter/>. [G.704] ITU-T, "Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels", ITU-T Recommendation G.704, October 1998, <http://www.itu.int/rec/T-REC-G.704/en>. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3593, September 2003. [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB Documents", BCP 111, RFC 4181, September 2005. Beili Standards Track [Page 54] RFC 6766 G.Bond/TDIM MIB February 2013 Author's Address Edward Beili Actelis Networks 25 Bazel St. Petach-Tikva 49103 Israel Phone: +972-3-924-3491 EMail: edward.beili@actelis.com Beili Standards Track [Page 55]