Internet DRAFT - draft-pim-mgmd-notif-mib

draft-pim-mgmd-notif-mib




PIM WG                                               Eshna Jain
Internet-Draft                                       C-DOT India
Intended status: Standards Track                     Subhajit Chatterjee
Expires: April 20, 2016                              C-DOT India
                                                     October 18, 2015


         Multicast Group Membership Discovery Notification MIB
                       draft-pim-mgmd-notif-mib-00

Status of This Memo

    This Internet-Draft is submitted in full conformance with the 
    provisions of BCP 78 and BCP 79. Internet-Drafts are working 
    documents of the Internet Engineering Task Force (IETF). Note that
    other groups may also distribute working documents as Internet-
    Drafts. The list of current Internet-Drafts is at 
    http://datatracker.ietf.org/drafts/current.

    Internet-Drafts are draft documents valid for a maximum of six
    months and may be updated, replaced, or obsoleted by other documents
    at any time. It is inappropriate to use Internet-Drafts as 
    reference material or to cite them other than as "work in progress.
    
    This Internet-Draft will expire on April 20,2016.
    
    Comments are solicited and should be addressed to the working
    group's mailing list and/or the author(s).

Copyright Notice

    Copyright (c) 2015 IETF Trust and the persons identified as the 
    document authors.  All rights reserved.

    This document is subject to BCP 78 and the IETF Trust's Legal 
    Provisions Relating to IETF Documents 
    (http://trustee.ietf.org/license-info) in effect on the date of 
    publication of this document.  Please review these documents
    carefully, as they describe your rights and restrictions with
    respect to this document. Code Components extracted from this
    document must include Simplified BSD License text as described in
    Section 4.e of the Trust Legal Provisions and are provided without
    warranty as described in the Simplified BSD License.

Abstract

    This memo defines a portion of the Management Information Base (MIB)
    for use with network management protocols in the Internet community.
    In particular, it describes notification objects used for managing
    notifications of the Internet Group Management Protocol (IGMP) and
    the Multicast Listener Discovery(MLD) protocol.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  
   2.  The Internet-Standard Management Framework . . . . . . . . . .  
   3.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  
   4.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  
   5.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 
   8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . 
     8.2.  Informative References  . . . . . . . . . . . . . . . . . 


1.  Introduction

    This memo defines a portion of the Management Information Base (MIB)
    for use with network management protocols in the Internet community.
    In particular, it describes notification objects used for managing
    notifications of the Internet Group Management Protocol (IGMP),
    version 1 [RFC1112], version 2 [RFC2236] or version 3 [RFC3376] and
    the Multicast Listener Discovery (MLD) protocol version 1 [RFC2710]
    or version 2 [RFC3810].  Both protocols provide multicast membership
    discovery capability.  IGMP pertains to IP version 4 clients, and
    MLD for IP version 6 clients.
 
2.  The Internet-Standard Management Framework

    For a detailed overview of the documents that describe the current
    Internet-Standard Management Framework, please refer to section 7 of
    RFC 3410 [RFC3410].

    Managed objects are accessed via a virtual information store, termed
    the Management Information Base or MIB.  MIB objects are generally
    accessed through the Simple Network Management Protocol (SNMP).
    Objects in the MIB are defined using the mechanisms defined in the
    Structure of Management Information (SMI).  This memo specifies a
    MIB module that is compliant to the SMIv2, which is described in STD
    58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 
    2580 [RFC2580].

3.  Conventions

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
    "OPTIONAL" in this document are to be interpreted as described in
    RFC 2119 [RFC2119].

4.  Overview

    This Multicast Group Membership Discovery (MGMD) Notification MIB
    module contains three notifications that can be generated by the
    MGMD protocols:

    1.  A mgmdWrongVersion trap is sent when a general query whose IGMP
        or MLD version does not match the equivalent
        mgmdRouterInterfaceVersion. 

    2.  A mgmdInterfaceJoins trap is sent when a group membership is
        added on a interface

    3.  A mgmdGroupsExceed trap is sent when the number of groups of
        which the host is a member exceeds threshold value.

    4.  A mgmdInterfaceLastMemberLeave trap is sent when the last member
        of group leaves on interface. 

5.  Definitions

MGMD-STD-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, mib-2, Counter32, Gauge32,
    Unsigned32, TimeTicks            FROM SNMPv2-SMI
    InetAddress, InetAddressType     FROM INET-ADDRESS-MIB
    RowStatus                        FROM SNMPv2-TC
    MODULE-COMPLIANCE, OBJECT-GROUP  FROM SNMPv2-CONF
    InterfaceIndexOrZero,
    InterfaceIndex                   FROM IF-MIB
    mgmdRouterInterfaceIfIndex       FROM MGMD-MIB;

mgmdNotificationMIB MODULE-IDENTITY
    ORGANIZATION "The Protocols for IP Multicast (PIM) working group.
        www:   http://www.ietf.org/html.charters/pim-charter.html"
    CONTACT-INFO
        "Eshna Jain
         C-DOT Campus
         Mehrauli
         Delhi- 110030
         India

         EMail: eshna@cdot.in"
    DESCRIPTION
        "The MIB module for MGMD Protocol Notofication management.
        A new version of MGMD notification.
        Copyright (c) 2015 IETF Trust and the persons identified
        as the document authors.  All rights reserved."

    REVISION "201510180000Z" - October 18, 2015
    DESCRIPTION
        "This MIB introduces a new RFC."

    ::= { mib-2 xxx }


 mgmdNotificationObjects OBJECT IDENTIFIER ::= { mgmdNotificationMIB 1 }
 mgmdNotifications       OBJECT IDENTIFIER ::= { mgmdNotificationMIB 2 }

 mgmdInterfaceVersionReceived       OBJECT-TYPE
     SYNTAX                Unsigned32 (1..3)
     MAX-Access            read-only
     DESCRIPTION           "The MGMD version received on an interface."
    ::=  { mgmdNotificationObjects 1 }

mgmdRouterInterfaceGroupId       OBJECT-TYPE
     SYNTAX                InetAddress (SIZE(4|16))
     MAX-Access            read-only
     DESCRIPTION           "The MGMD group id."
    ::=  { mgmdNotificationObjects 2 }

mgmdHostGroups             OBJECT-TYPE
     SYNTAX                Unsigned32
     MAX-Access            read-only
     DESCRIPTION           
            "The total number of groups of which the host is a member."
    ::=  { mgmdNotificationObjects 3 }

MgmdHostGroupsThreshold    OBJECT-TYPE
     SYNTAX                Unsigned32
     MAX-Access            read-only
     DESCRIPTION           
            "The maximum number of groups of which the host can become a 
            member of."
    ::=  { mgmdNotificationObjects 4 }

 mgmdWrongVersion          NOTIFICATION-TYPE
     OBJECTS               { mgmdRouterInterfaceVersion, 
                             mgmdInterfaceVersionReceived }
     STATUS                Current
     DESCRIPTION
            "A mgmdWrongVersion trap is sent when a general query whose
            IGMP or MLD version does not match the equivalent 
            mgmdRouterInterfaceVersion. Both IGMP and MLD require that
            all routers on a LAN be configured to run the same version.
            Thus, if any general queries are received with the wrong 
            version, this indicates a configuration error."
    ::=  { mgmdNotifications 1 }

mgmdInterfaceJoins         NOTIFICATION-TYPE
    OBJECTS                { mgmdRouterInterfaceIfIndex, 
                             mgmdRouterInterfaceGroupId}
    STATUS                   Current
    DESCRIPTION		
            "A mgmdInterfaceJoins trap is sent when a group membership,
            given by mgmdRouterInterfaceGroupId, is added on a 
            interface, mgmdRouterInterfaceIfIndex."
    ::= { mgmdNotifications 2 }

mgmdGroupsExceed           NOTIFICATION-TYPE
    OBJECTS                {mgmdHostGroups , MgmdHostGroupsThreshold }
    STATUS                  Current
    DESCRIPTION	 
            "A mgmdGroupsExceed trap is sent when the number of groups, 
            mgmdHostGroups ,  of which the host is a member exceeds 
            MgmdHostGroupsThreshold value. When the number exceeds the
            maximum capacity no more groups are learnt and flooding
            becomes the default behavious for such groups."
    ::= { mgmdNotifications 3 }

mgmdInterfaceLastMemberLeave    NOTIFICATION-TYPE
    OBJECTS                     { mgmdRouterInterfaceIfIndex ,
                                  mgmdRouterInterfaceGroupId}
    STATUS                        Current
    DESCRIPTION	
            "A mgmdInterfaceLastMemberLeave trap is sent when the last
            member os group mgmdRouterInterfaceGroupId leaves on 
            interface mgmdRouterInterfaceIfIndex. As a result the
            interface stops being the member of the respective group."
    ::= { mgmdNotifications 4}


6.  Security Considerations

   It is RECOMMENDED that implementers consider the security features as
   provided by the SNMPv3 framework (see [RFC3410], section 8),
   including full support for the SNMPv3 cryptographic mechanisms (for
   authentication and privacy).

   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.

7.  IANA Considerations

   This MIB introduces a new term to refer to the notification provided 
   by two existing multicast protocols, Multicast Group Membership
   Discovery.

   The MIB module in this document uses the following IANA-assigned
   OBJECT IDENTIFIER values recorded in the SMI Numbers registry:

        Descriptor            OBJECT IDENTIFIER value
        ----------            -----------------------
        mgmdNotificationMIB        { mib-2 XXX }

   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 record the assignment in the SMI Numbers registry.  When the
   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
   this note.


8.  References

8.1.  Normative References

    [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
              RFC 1112, August 1989.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2236]  Fenner, W., "Internet Group Management Protocol, Version
              2", RFC 2236, November 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.

   [RFC2710]  Deering, S., Fenner, W., and B. Haberman, "Multicast
              Listener Discovery (MLD) for IPv6", RFC 2710,
              October 1999.

   [RFC3376]  Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
              Thyagarajan, "Internet Group Management Protocol, Version
              3", RFC 3376, October 2002.

   [RFC3810]  Vida, R. and L. Costa, "Multicast Listener Discovery
              Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.

   [RFC5519]  Chesterfield, J., Haberman, B., Ed., "Multicast Group
              Membership Discovery MIB", RFC 5519, April 20019.


10.2.  Informative References

   [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
              June 1999.

   [RFC2933]  McCloghrie, K., Farinacci, D., and D. Thaler, "Internet
              Group Management Protocol MIB", RFC 2933, October 2000.

   [RFC3019]  Haberman, B. and R. Worzella, "IP Version 6 Management
              Information Base for The Multicast Listener Discovery
              Protocol", RFC 3019, January 2001.

   [RFC3410]  Case, J., Mundy, R., Partain, D., and B. Stewart,
              "Introduction and Applicability Statements for Internet-
              Standard Management Framework", RFC 3410, December 2002.

   [RFC4605]  Fenner, B., He, H., Haberman, B., and H. Sandick,
              "Internet Group Management Protocol (IGMP) / Multicast
              Listener Discovery (MLD)-Based Multicast Forwarding
              ("IGMP/MLD Proxying")", RFC 4605, August 2006.

Authors' Addresses

   Eshna Jain
   C-DOT Campus
   Mehrauli
   Delhi - 110030
   India
   Email : eshna@cdot.in

   Subhajit Chatterjee
   C-DOT Campus
   Mehrauli
   Delhi - 110030
   India
   Email : subhajit.chatterjee@cdot.in
   
    This Internet-Draft will expire on April 20,2016.