Skip to main content

<Green Usage Monitoring Information Base>
draft-suganuma-greenmib-10

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Authors Takuo Suganuma , Naoki Nakamura , Satoru Izumi , Hiroshi Tsunoda , Masahiro Matsuda , Kohei Ohta
Last updated 2017-07-31
RFC stream (None)
Formats
Additional resources
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-suganuma-greenmib-10
Network Working Group                                     Takuo Suganuma
INTERNET-DRAFT                                         Tohoku University
Intended Status: Proposed Standard                        Naoki Nakamura
Expires: February 2, 2018                              Tohoku University
                                                            Satoru Izumi
                                                       Tohoku University
                                                         Hiroshi Tsunoda
                                          Tohoku Institute of Technology
                                                        Masahiro Matsuda
                                          Tohoku Institute of Technology
                                                              Kohei Ohta
                                                         Cyber Solutions
                                                          August 1, 2017

               <Green Usage Monitoring Information Base>
                     draft-suganuma-greenmib-10.txt

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This document is a product of the EMAN Working Group. Comments
   should be addressed to the authors or the mailing list at
   eman@ietf.org

   This Internet-Draft will expire on February 2, 2018.

 

Takuo Suganuma         Expires: February 2, 2018                [Page 1]
Internet Draft                  greenMib                     August 2017

Copyright Notice
   Copyright (c) 2014 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),
   the GreenUsage-MIB, for use with network management protocols
   in the Internet community.  In particular, the GreenUsage-MIB
   can be used to monitor the power-on/power-off status of electrical
   devices.

Table of Contents

   1.  The Internet-Standard Management Framework . . . . . . . . . .  3
   2.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  The GreenUsage monitoring concept  . . . . . . . . . . . .  3
     2.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  GreenUsage Monitoring Requirements . . . . . . . . . . . . . .  4
   4.  MIB Design . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   5.  MIB Definitions  . . . . . . . . . . . . . . . . . . . . . . .  5
     5.1.  The GreenUsage-MIB . . . . . . . . . . . . . . . . . . . .  5
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 13
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 14
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 14
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
   10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 15

 

Takuo Suganuma         Expires: February 2, 2018                [Page 2]
Internet Draft                  greenMib                     August 2017

1.  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].

2.  Overview

2.1.  The GreenUsage monitoring concept

   GreenUsage-MIB is to monitor the power-on/power-off status of 
   electrical devices. If a device is in power-on status beyond business 
   hours, it is wasteful usage of electricity. The GreenUsage-MIB concept 
   aims to monitor and reduce this wastage.

   This document defines a set of managed objects (MOs) of the GreenUsage-MIB 
   that can be used to monitor the power-on/power-off status of electrical 
   devices based on their network activity.

   Target devices of the GreenUsage-MIB is all electrical devices. Also the 
   GreenUsage-Mib cover that of the Energy Management Framework [RFC7326]. 
   Refer to the "Target Devices" section in [RFC7326] for the definition 
   of target devices.

   Since the GreenUsage-MIB has a simple structure, it is easy to use and 
   extend in developing a monitoring system of ALL connected devices including 
   various kinds of devices such as poor resources IoT devices.

2.2.  Terminology

   Electrical device: a device that consumes electricity. Power-
   on/power-off status indicates whether the device is powered on or
   not. Often it is not possible to get a direct indication of whether a
   device is powered on or not. But indirect means may be used to infer
   the power-on/power-off status of a device. For example, if a device
   shows some network activity, it can be inferred that the device is
   powered on. Note that it is difficult to infer that a device is
 

Takuo Suganuma         Expires: February 2, 2018                [Page 3]
Internet Draft                  greenMib                     August 2017

   powered off.  Also, there may be several states between power-on and
   power-off e.g. sleep state, power-saving state, etc.

   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 BCP
   14, RFC 2119 [RFC2119].

3.  GreenUsage Monitoring Requirements

   Multiple mechanisms may be used to determine whether a device is
   powered on or not. The mechanisms will depend on the nature of the
   device. Since the number of devices may be very large, the
   identification, usage type, and location of devices needs to be 
   addressed with care.

4.  MIB Design

   The basic principle has been to keep the MIB as simple as possible
   and at the same time to make it effective enough so that the
   essential needs of monitoring are met.

   The GreenUsage-MIB is composed of the following

       - device Table: a list of the devices that will be monitored
       - deviceStatus Table: the power-on/power-off status of the devices

 

Takuo Suganuma         Expires: February 2, 2018                [Page 4]
Internet Draft                  greenMib                     August 2017

5.  MIB Definitions

5.1.  The GreenUsage-MIB

    GREENUSAGE-MIB DEFINITIONS ::= BEGIN
       IMPORTS
         MODULE-IDENTITY,  mib-2, Unsigned32, OBJECT-TYPE
                    FROM SNMPv2-SMI                   -- RFC 2578
         TimeStamp, MacAddress, TEXTUAL-CONVENTION
                    FROM SNMPv2-TC                    -- RFC 2579
         MODULE-COMPLIANCE, OBJECT-GROUP
                    FROM SNMPv2-CONF                  -- RFC 2580
         SnmpAdminString
                    FROM SNMP-FRAMEWORK-MIB
         ;

     greenUsageMIB  MODULE-IDENTITY
          LAST-UPDATED "201601260000Z"     --  26th January, 2016
          ORGANIZATION "PREDICT Working Group"
          CONTACT-INFO
          "                 Takuo Suganuma
                    Postal: Tohoku University.
                            2-1-1 Katahira
                            Aoba-ku, Sendai, Japan 980-8577.
                       Tel: +81-22-217-5081
                       Fax: +81-22-217-5080
                    E-mail: suganuma@tohoku.ac.jp

                            Naoki Nakamura
                    Postal: Tohoku University.
                            2-1 Seiryo-machi,
                            Aoba-ku, Sendai, Japan 980-8575.
                       Tel: +81-22-717-8024
                       Fax: +81-22-717-8024
                    E-mail: nakamura@med.tohoku.ac.jp

                            Satoru Izumi
                    Postal: Tohoku University.
                            2-1-1 Katahira
                            Aoba-ku, Sendai, Japan 980-8577.
                       Tel: +81-22-217-5080
                       Fax: +81-22-217-5080
                    E-mail: izumi@ci.cc.tohoku.ac.jp

                            Hiroshi Tsunoda
                    Postal: Tohoku Institute of Technology.
                            35-1, Yagiyama Kasumi-cho
 

Takuo Suganuma         Expires: February 2, 2018                [Page 5]
Internet Draft                  greenMib                     August 2017

                            Taihaku-ku, Sendai, Japan 982-8577.
                       Tel: +81-22-305-3411
                    E-mail: tsuno@m.ieice.org

                            Masahiro Matsuda
                    Postal: Tohoku Institute of Technology.
                            35-1, Yagiyama Kasumi-cho
                            Taihaku-ku, Sendai, Japan 982-8577.
                       Tel: +81-22-305-3424
                       E-mail: mmatsuda@tohtech.ac.jp

                            Kohei Ohta
                    Postal: Cyber Solutions Inc.
                            6-6-3, Minami Yoshinari
                            Aoba-ku, Sendai, Japan 989-3204.
                       Tel: +81-22-303-4012
                       Fax: +81-22-303-4015
                    E-mail: kohei@cysols.com

           Support Group E-mail: xxxxxxxxxxxxxx
           "
        DESCRIPTION
            "This MIB module is for monitoring the power-on/power-off
             status of electrical devices.

             Copyright (C) The IETF Trust (2012). This version of
             this MIB module is part of RFC XXXX; see the RFC itself for
             full legal notices.
            "
       -- RFC Ed.: replace XXXX with the actual RFC number & remove this
       -- note

 

Takuo Suganuma         Expires: February 2, 2018                [Page 6]
Internet Draft                  greenMib                     August 2017

        REVISION "201407210000Z"     --  21th July, 2014
        DESCRIPTION
            "added actualMonitoring to GumStatusDetectionMethod"
        REVISION "201401120000Z"     --  11th January, 2014
        DESCRIPTION
            "added deviceMonitoring to GumStatusDetectionMethod"
        REVISION "201301080000Z"     --  8th January, 2013
        DESCRIPTION
            "added gumDevUsageCreatedTimeStamp to usage table"

        REVISION "201207070000Z"     --  7th July, 2012
        DESCRIPTION
            "The initial version, published as draft-suganuma-greenmib-00.txt"

       -- RFC Ed.: replace XXXX with the actual RFC number & remove this
       -- note

        ::= { mib-2 YYY1 }     -- Will be assigned by IANA

       -- IANA Reg.: Please assign a value for "YYY1" under the
       -- 'mib-2' subtree and record the assignment in the SMI
       -- Numbers registry.

       -- RFC Ed.: When the above assignment has been made, please
       --     remove the above note
       --     replace "YYY1" here with the assigned value and
       --     remove this note.

    -- -------------------------------------------------------------
    -- Textual Conventions
    -- -------------------------------------------------------------

       GumStatusDetectionMethod  ::=  TEXTUAL-CONVENTION
           STATUS  current
           DESCRIPTION
               "The object specifies the technology which is used
                to detect the power-on/power-off status of a device.
                The enumerated values and the corresponding
                technology are as follows:
                 reserved                   (0): reserved (Not used)
                 arpSensing                 (1): arp packets from the
                                                 device
                 neighborDiscoverySensing   (2): neighbor discovery
                                                 packets from the device
                 icmpEchoProbing            (3): ICMP echo packets
                 switchMonitoring           (4): switch monitoring
                 deviceMonitoring           (5): the direct monitoring of
 

Takuo Suganuma         Expires: February 2, 2018                [Page 7]
Internet Draft                  greenMib                     August 2017

                                                 device status such as CPU
                                                 load and memory usage
                 actualMonitoring           (6): the actual monitoring of power 
                                                 status of a device by its own 
                                                 functions
               "
           SYNTAX  INTEGER
           {
                 reserved                   (0),
                 arpSensing                 (1),
                 neighborDiscoverySensing   (2),
                 icmpEchoProbing            (3),
                 switchMonitoring           (4),
                 deviceMonitoring           (5),
                 actualMonitoring           (6)
           }

       GumDeviceStatus  ::=  TEXTUAL-CONVENTION
           STATUS  current
           DESCRIPTION
               "The object represents the power-on/power-off
                status of a monitored device.
                 unknown                    (0)
                 powerOn                    (1): device is powered on
                 powerOff                   (2): device is powered off
                 sleepMode                  (3): device is in sleep mode
                 powerSavingMode            (4): device is in
                                                 power saving mode
               "
           SYNTAX  INTEGER
           {
                 unknown                    (0),
                 powerOn                    (1),
                 powerOff                   (2),
                 sleepMode                  (3),
                 powerSavingMode            (4)
           }

       -- The GREENUSAGE-MIB has the following 3 primary groups

       gumNotifications     OBJECT IDENTIFIER ::= { greenUsageMIB 0 }
       gumObjects           OBJECT IDENTIFIER ::= { greenUsageMIB 1 }
       gumConformance       OBJECT IDENTIFIER ::= { greenUsageMIB 2 }

       gumDeviceTable OBJECT-TYPE
           SYNTAX      SEQUENCE OF GumDeviceEntry
           MAX-ACCESS  not-accessible
           STATUS      current
 

Takuo Suganuma         Expires: February 2, 2018                [Page 8]
Internet Draft                  greenMib                     August 2017

           DESCRIPTION
               "This table models the device list

                Entries in this table are required to survive
                a reboot of the managed entity.
               "
           ::= { gumObjects 1 }

       gumDeviceEntry OBJECT-TYPE
           SYNTAX      GumDeviceEntry
           MAX-ACCESS  not-accessible
           STATUS      current
           DESCRIPTION
               "This entry represents a conceptual row in the
                gumDevice table. It represents a device that
                will be monitored for power-on/power-off status.
               "
           INDEX  { gumDeviceID }
           ::= { gumDeviceTable 1 }

       GumDeviceEntry ::=
           SEQUENCE {
            gumDeviceID            Unsigned32,
            gumDeviceName          SnmpAdminString,
            gumDeviceMacAddress    MacAddress,
            gumDeviceType          SnmpAdminString,
            gumDeviceLocation      SnmpAdminString
           }

       gumDeviceID OBJECT-TYPE
           SYNTAX      Unsigned32
           MAX-ACCESS  not-accessible
           STATUS      current
           DESCRIPTION
               "A unique arbitrary identifier for this device."
           ::= { gumDeviceEntry 1 }

       gumDeviceName OBJECT-TYPE
           SYNTAX      SnmpAdminString (SIZE(1..64))
           MAX-ACCESS  read-create
           STATUS      current
           DESCRIPTION
               "Administratively assigned textual name of this
                device."
           ::= { gumDeviceEntry 2 }

       gumDeviceMacAddress OBJECT-TYPE
           SYNTAX      MacAddress
 

Takuo Suganuma         Expires: February 2, 2018                [Page 9]
Internet Draft                  greenMib                     August 2017

           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
               "MAC Address of this device.
                If there is no MAC address, this object will be
                inaccessible."
           ::= { gumDeviceEntry 3 }

       gumDeviceType OBJECT-TYPE
           SYNTAX      SnmpAdminString (SIZE(1..64))
           MAX-ACCESS  read-create
           STATUS      current
           DESCRIPTION
               "Administratively assigned textual description about
                usage type of this device."
           ::= { gumDeviceEntry 4 }

       gumDeviceLocation OBJECT-TYPE
           SYNTAX      SnmpAdminString (SIZE(1..64))
           MAX-ACCESS  read-create
           STATUS      current
           DESCRIPTION
               "Administratively assigned textual location
                name of this device."
           ::= { gumDeviceEntry 5 }

       gumDevUsageTable OBJECT-TYPE
           SYNTAX      SEQUENCE OF GumDevUsageEntry
           MAX-ACCESS  not-accessible
           STATUS      current
           DESCRIPTION
               "This table models the device usage status

                Entries in this table are required to survive
                a reboot of the managed entity.
               "
           ::= { gumObjects 2 }

       gumDevUsageEntry OBJECT-TYPE
           SYNTAX      GumDevUsageEntry
           MAX-ACCESS  not-accessible
           STATUS      current
           DESCRIPTION
               "This entry represents a conceptual row in the
                gumDevUsage table. It represents a power-on/power-off
                status of a monitored device.
               "
           INDEX  { gumDeviceID, gumDevUsageDetID }
 

Takuo Suganuma         Expires: February 2, 2018               [Page 10]
Internet Draft                  greenMib                     August 2017

           ::= { gumDevUsageTable 1 }

       GumDevUsageEntry ::=
           SEQUENCE {
            gumDevUsageDetID            GumStatusDetectionMethod,
            gumDevUsageDetStatus        GumDeviceStatus,
            gumDevUsageDetTimeStamp     TimeStamp,
            gumDevUsageCreatedTimeStamp TimeStamp
           }

       gumDevUsageDetID OBJECT-TYPE
           SYNTAX      GumStatusDetectionMethod
           MAX-ACCESS  not-accessible
           STATUS      current
           DESCRIPTION
               "The detection method by which the usage status is
                computed."
           ::= { gumDevUsageEntry 1 }

       gumDevUsageDetStatus OBJECT-TYPE
           SYNTAX      GumDeviceStatus
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
               "the usage status of the device."
           ::= { gumDevUsageEntry 2 }

       gumDevUsageDetTimeStamp OBJECT-TYPE
           SYNTAX      TimeStamp
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
               "the time at which the usage status of the
                device was computed."
           ::= { gumDevUsageEntry 3 }

       gumDevUsageCreatedTimeStamp OBJECT-TYPE
           SYNTAX      TimeStamp
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
               "the time at which the entry of usage table created."
           ::= { gumDevUsageEntry 4 }   

       -- Units of conformance
       gumGroups       OBJECT IDENTIFIER ::= { gumConformance 1}
       gumCompliances  OBJECT IDENTIFIER ::= { gumConformance 2}

 

Takuo Suganuma         Expires: February 2, 2018               [Page 11]
Internet Draft                  greenMib                     August 2017

       gumObjectsGroup    OBJECT-GROUP
            OBJECTS {
                     gumDeviceName,
                     gumDeviceMacAddress,
                     gumDeviceType,
                     gumDeviceLocation,
                     gumDevUsageDetStatus,
                     gumDevUsageDetTimeStamp,
                     gumDevUsageCreatedTimeStamp
            }
            STATUS  current
            DESCRIPTION
                " A collection of objects for basic GreenUsage
                  monitoring."
            ::= { gumGroups 1 }

       -- Compliance statements
       gumCompliance MODULE-COMPLIANCE
            STATUS  current
            DESCRIPTION
                "The compliance statement for SNMP entities
                 which implement the GREENUSAGE-MIB
                "
            MODULE  -- this module
                MANDATORY-GROUPS { gumObjectsGroup
                                 }
            ::= { gumCompliances 1 }

       END

 

Takuo Suganuma         Expires: February 2, 2018               [Page 12]
Internet Draft                  greenMib                     August 2017

6.  Security Considerations
   There are no management objects defined in this MIB module with a
   MAX-ACCESS clause of read-write.
   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
   vulnerable in some network environments.  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:
                     gumDeviceName,
                     gumDeviceMacAddress,
                     gumDeviceType,
                     gumDeviceLocation,
                     gumDevUsageDetStatus,
                     gumDevUsageDetTimeStamp,
                     gumDevUsageCreatedTimeStamp
         The above objects may be be used to identify users and their
         activities. Thus these objects may be considered to be
         particularly sensitive and/or private.

   SNMP versions prior to SNMPv3 did not include adequate security.
   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
   allowed to access and GET/SET (read/change/create/delete) the objects
   in this MIB module.

   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

   IANA should assign
         1. a base arc in the 'mib-2' (standards track) OID
            tree for the 'greenUsageMIB' MODULE-IDENTITY defined in the
            GREENUSAGE-MIB.

 

Takuo Suganuma         Expires: February 2, 2018               [Page 13]
Internet Draft                  greenMib                     August 2017

8.  References

8.1.  Normative References

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

   [RFC2578]    McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
                J., Rose, M. and S. Waldbusser, Structure of
                Management Information Version 2 (SMIv2), STD 58,
                RFC 2578, April 1999.

   [RFC2579]    McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
                J., Rose, M. and S. Waldbusser, Textual Conventions
                for SMIv2, STD 58, RFC 2579, April 1999.

   [RFC2580]    McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
                J., Rose, M. and S. Waldbusser, Conformance
                Statements for SMIv2, STD 58, RFC 2580, April 1999.

   [RFC4293]    Routhier, S., Management Information Base for the
                Internet Protocol (IP), RFC 4293, April 2006.

   [RFC4001]    Daniele, M., Haberman, B., Routhier, S. and
                Schoenwaelder, J., Textual Conventions for Internet
                Network Addresses, RFC 4001, February 2005.

   [RFC2863]    McCloghrie, K., and Kastenholz., F., The Interfaces
                Group MIB, RFC 2863, June 2000.

8.2.  Informative References

   [RFC3410]    Case, J., Mundy, R., Partain, D. and B. Stewart,
                Introduction and Applicability Statements for
                Internet-Standard Management Framework, RFC 3410,
                December 2002.
   [RFC7326]    Parello, J., Claise, B., Schoening, B. and Quittek, J., 
                Energy Management Framework", RFC 7326, September 2014.

 

Takuo Suganuma         Expires: February 2, 2018               [Page 14]
Internet Draft                  greenMib                     August 2017

9.  Acknowledgements
   The following individuals and groups have contributed to this draft
   with discussions and comments:
        Norio Shiratori
        WIDE Project netman-WG
        EMAN WG of the IETF

  The authors would like to thank Glenn Mansfield Keeni for proposing
  this MIB module and comments for improving this document.

10. Authors' Addresses

    Takuo Suganuma
    Tohoku University.
    2-1-1, Katahira
    Aoba-ku, Sendai, Japan 980-5877.

    Phone: +81-22-217-5081
    E-mail: suganuma@tohoku.ac.jp

    Naoki Nakamura
    Tohoku University.
    2-1 Seiryo-machi,
    Aoba-ku, Sendai, Japan 980-8575.

    Phone: +81-22-717-8024
    E-mail: nakamura@med.tohoku.ac.jp

    Satoru Izumi
    Tohoku University.
    2-1-1 Katahira
    Aoba-ku, Sendai, Japan 980-8577.

    Phone: +81-22-217-5080
    E-mail: izumi@ci.cc.tohoku.ac.jp

    Hiroshi Tsunoda
    Tohoku Institute of Technology.
    35-1, Yagiyama Kasumi-cho
    Taihaku-ku, Sendai, Japan 982-8577.

    Phone: +81-22-305-3411
    E-mail: tsuno@m.ieice.org

    Masahiro Matsuda
    Tohoku Institute of Technology.
    35-1, Yagiyama Kasumi-cho
 

Takuo Suganuma         Expires: February 2, 2018               [Page 15]
Internet Draft                  greenMib                     August 2017

    Taihaku-ku, Sendai, Japan 982-8577.

    Phone: +81-22-305-3424
    E-mail: mmatsuda@tohtech.ac.jp

    Kohei Ohta
    Cyber Solutions Inc.
    6-6-3, Minami Yoshinari
    Aoba-ku, Sendai, Japan 989-3204.

    Phone: +81-22-303-4012
    E-mail: kohei@cysols.com

Takuo Suganuma         Expires: February 2, 2018               [Page 16]