idnits 2.17.1 draft-suganuma-greenmib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 13 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 29, 2017) is 2615 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC4293' is defined on line 573, but no explicit reference was found in the text == Unused Reference: 'RFC4001' is defined on line 576, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 580, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Takuo Suganuma 3 INTERNET-DRAFT Tohoku University 4 Intended Status: Proposed Standard Naoki Nakamura 5 Expires: August 2, 2017 Tohoku University 6 Satoru Izumi 7 Tohoku University 8 Hiroshi Tsunoda 9 Tohoku Institute of Technology 10 Masahiro Matsuda 11 Tohoku Institute of Technology 12 Kohei Ohta 13 Cyber Solutions 14 January 29, 2017 16 17 draft-suganuma-greenmib-09.txt 19 Status of this Memo 21 This Internet-Draft is submitted to IETF in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 This document is a product of the EMAN Working Group. Comments 41 should be addressed to the authors or the mailing list at 42 eman@ietf.org 44 This Internet-Draft will expire on August 2, 2017. 46 Copyright Notice 47 Copyright (c) 2014 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with 55 respect to this document. Code Components extracted from this 56 document must include Simplified BSD License text as described 57 in Section 4.e of the Trust Legal Provisions and are provided 58 without warranty as described in the Simplified BSD License. 60 Abstract 62 This memo defines a portion of the Management Information Base (MIB), 63 the GreenUsage-MIB, for use with network management protocols 64 in the Internet community. In particular, the GreenUsage-MIB 65 can be used to monitor the power-on/power-off status of electrical 66 devices. 68 Table of Contents 70 1. The Internet-Standard Management Framework . . . . . . . . . . 3 71 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 72 2.1. The GreenUsage monitoring concept . . . . . . . . . . . . 3 73 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 74 3. GreenUsage Monitoring Requirements . . . . . . . . . . . . . . 4 75 4. MIB Design . . . . . . . . . . . . . . . . . . . . . . . . . . 4 76 5. MIB Definitions . . . . . . . . . . . . . . . . . . . . . . . 5 77 5.1. The GreenUsage-MIB . . . . . . . . . . . . . . . . . . . . 5 78 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 79 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 80 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 81 8.1. Normative References . . . . . . . . . . . . . . . . . . . 14 82 8.2. Informative References . . . . . . . . . . . . . . . . . . 14 83 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 84 10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 15 86 1. The Internet-Standard Management Framework 88 For a detailed overview of the documents that describe the current 89 Internet-Standard Management Framework, please refer to section 7 of 90 RFC 3410 [RFC3410]. 92 Managed objects are accessed via a virtual information store, termed 93 the Management Information Base or MIB. MIB objects are generally 94 accessed through the Simple Network Management Protocol (SNMP). 96 Objects in the MIB are defined using the mechanisms defined in the 97 Structure of Management Information (SMI). This memo specifies a MIB 98 module that is compliant to the SMIv2, which is described in STD 58, 99 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 100 [RFC2580]. 102 2. Overview 104 2.1. The GreenUsage monitoring concept 106 GreenUsage-MIB is to monitor the power-on/power-off status of 107 electrical devices. If a device is in power-on status beyond business 108 hours, it is wasteful usage of electricity. The GreenUsage-MIB concept 109 aims to monitor and reduce this wastage. 111 This document defines a set of managed objects (MOs) of the GreenUsage-MIB 112 that can be used to monitor the power-on/power-off status of electrical 113 devices based on their network activity. 115 Target devices of the GreenUsage-MIB is all electrical devices. Also the 116 GreenUsage-Mib cover that of the Energy Management Framework [RFC7326]. 117 Refer to the "Target Devices" section in [RFC7326] for the definition 118 of target devices. 120 Since the GreenUsage-MIB has a simple structure, it is easy to use and 121 extend in developing a monitoring system of ALL connected devices including 122 poor resources IoT devices. 124 2.2. Terminology 126 Electrical device: a device that consumes electricity. Power- 127 on/power-off status indicates whether the device is powered on or 128 not. Often it is not possible to get a direct indication of whether a 129 device is powered on or not. But indirect means may be used to infer 130 the power-on/power-off status of a device. For example, if a device 131 shows some network activity, it can be inferred that the device is 132 powered on. Note that it is difficult to infer that a device is 133 powered off. Also, there may be several states between power-on and 134 power-off e.g. sleep state, power-saving state, etc. 136 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 137 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 138 "OPTIONAL" in this document are to be interpreted as described in BCP 139 14, RFC 2119 [RFC2119]. 141 3. GreenUsage Monitoring Requirements 143 Multiple mechanisms may be used to determine whether a device is 144 powered on or not. The mechanisms will depend on the nature of the 145 device. Since the number of devices may be very large, the 146 identification, usage type, and location of devices needs to be 147 addressed with care. 149 4. MIB Design 151 The basic principle has been to keep the MIB as simple as possible 152 and at the same time to make it effective enough so that the 153 essential needs of monitoring are met. 155 The GreenUsage-MIB is composed of the following 157 - device Table: a list of the devices that will be monitored 158 - deviceStatus Table: the power-on/power-off status of the devices 160 5. MIB Definitions 162 5.1. The GreenUsage-MIB 164 GREENUSAGE-MIB DEFINITIONS ::= BEGIN 165 IMPORTS 166 MODULE-IDENTITY, mib-2, Unsigned32, OBJECT-TYPE 167 FROM SNMPv2-SMI -- RFC 2578 168 TimeStamp, MacAddress, TEXTUAL-CONVENTION 169 FROM SNMPv2-TC -- RFC 2579 170 MODULE-COMPLIANCE, OBJECT-GROUP 171 FROM SNMPv2-CONF -- RFC 2580 172 SnmpAdminString 173 FROM SNMP-FRAMEWORK-MIB 174 ; 176 greenUsageMIB MODULE-IDENTITY 177 LAST-UPDATED "201601260000Z" -- 26th January, 2016 178 ORGANIZATION "PREDICT Working Group" 179 CONTACT-INFO 180 " Takuo Suganuma 181 Postal: Tohoku University. 182 2-1-1 Katahira 183 Aoba-ku, Sendai, Japan 980-8577. 184 Tel: +81-22-217-5081 185 Fax: +81-22-217-5080 186 E-mail: suganuma@tohoku.ac.jp 188 Naoki Nakamura 189 Postal: Tohoku University. 190 2-1 Seiryo-machi, 191 Aoba-ku, Sendai, Japan 980-8575. 192 Tel: +81-22-717-8024 193 Fax: +81-22-717-8024 194 E-mail: nakamura@med.tohoku.ac.jp 196 Satoru Izumi 197 Postal: Tohoku University. 198 2-1-1 Katahira 199 Aoba-ku, Sendai, Japan 980-8577. 200 Tel: +81-22-217-5080 201 Fax: +81-22-217-5080 202 E-mail: izumi@ci.cc.tohoku.ac.jp 204 Hiroshi Tsunoda 205 Postal: Tohoku Institute of Technology. 206 35-1, Yagiyama Kasumi-cho 207 Taihaku-ku, Sendai, Japan 982-8577. 208 Tel: +81-22-305-3411 209 E-mail: tsuno@m.ieice.org 211 Masahiro Matsuda 212 Postal: Tohoku Institute of Technology. 213 35-1, Yagiyama Kasumi-cho 214 Taihaku-ku, Sendai, Japan 982-8577. 215 Tel: +81-22-305-3424 216 E-mail: mmatsuda@tohtech.ac.jp 218 Kohei Ohta 219 Postal: Cyber Solutions Inc. 220 6-6-3, Minami Yoshinari 221 Aoba-ku, Sendai, Japan 989-3204. 222 Tel: +81-22-303-4012 223 Fax: +81-22-303-4015 224 E-mail: kohei@cysols.com 226 Support Group E-mail: xxxxxxxxxxxxxx 227 " 228 DESCRIPTION 229 "This MIB module is for monitoring the power-on/power-off 230 status of electrical devices. 232 Copyright (C) The IETF Trust (2012). This version of 233 this MIB module is part of RFC XXXX; see the RFC itself for 234 full legal notices. 235 " 236 -- RFC Ed.: replace XXXX with the actual RFC number & remove this 237 -- note 238 REVISION "201407210000Z" -- 21th July, 2014 239 DESCRIPTION 240 "added actualMonitoring to GumStatusDetectionMethod" 241 REVISION "201401120000Z" -- 11th January, 2014 242 DESCRIPTION 243 "added deviceMonitoring to GumStatusDetectionMethod" 244 REVISION "201301080000Z" -- 8th January, 2013 245 DESCRIPTION 246 "added gumDevUsageCreatedTimeStamp to usage table" 248 REVISION "201207070000Z" -- 7th July, 2012 249 DESCRIPTION 250 "The initial version, published as draft-suganuma-greenmib-00.txt" 252 -- RFC Ed.: replace XXXX with the actual RFC number & remove this 253 -- note 255 ::= { mib-2 YYY1 } -- Will be assigned by IANA 257 -- IANA Reg.: Please assign a value for "YYY1" under the 258 -- 'mib-2' subtree and record the assignment in the SMI 259 -- Numbers registry. 261 -- RFC Ed.: When the above assignment has been made, please 262 -- remove the above note 263 -- replace "YYY1" here with the assigned value and 264 -- remove this note. 266 -- ------------------------------------------------------------- 267 -- Textual Conventions 268 -- ------------------------------------------------------------- 270 GumStatusDetectionMethod ::= TEXTUAL-CONVENTION 271 STATUS current 272 DESCRIPTION 273 "The object specifies the technology which is used 274 to detect the power-on/power-off status of a device. 275 The enumerated values and the corresponding 276 technology are as follows: 277 reserved (0): reserved (Not used) 278 arpSensing (1): arp packets from the 279 device 280 neighborDiscoverySensing (2): neighbor discovery 281 packets from the device 282 icmpEchoProbing (3): ICMP echo packets 283 switchMonitoring (4): switch monitoring 284 deviceMonitoring (5): the direct monitoring of 285 device status such as CPU 286 load and memory usage 287 actualMonitoring (6): the actual monitoring of power 288 status of a device by its own 289 functions 290 " 291 SYNTAX INTEGER 292 { 293 reserved (0), 294 arpSensing (1), 295 neighborDiscoverySensing (2), 296 icmpEchoProbing (3), 297 switchMonitoring (4), 298 deviceMonitoring (5), 299 actualMonitoring (6) 300 } 302 GumDeviceStatus ::= TEXTUAL-CONVENTION 303 STATUS current 304 DESCRIPTION 305 "The object represents the power-on/power-off 306 status of a monitored device. 307 unknown (0) 308 powerOn (1): device is powered on 309 powerOff (2): device is powered off 310 sleepMode (3): device is in sleep mode 311 powerSavingMode (4): device is in 312 power saving mode 313 " 314 SYNTAX INTEGER 315 { 316 unknown (0), 317 powerOn (1), 318 powerOff (2), 319 sleepMode (3), 320 powerSavingMode (4) 321 } 323 -- The GREENUSAGE-MIB has the following 3 primary groups 325 gumNotifications OBJECT IDENTIFIER ::= { greenUsageMIB 0 } 326 gumObjects OBJECT IDENTIFIER ::= { greenUsageMIB 1 } 327 gumConformance OBJECT IDENTIFIER ::= { greenUsageMIB 2 } 329 gumDeviceTable OBJECT-TYPE 330 SYNTAX SEQUENCE OF GumDeviceEntry 331 MAX-ACCESS not-accessible 332 STATUS current 333 DESCRIPTION 334 "This table models the device list 336 Entries in this table are required to survive 337 a reboot of the managed entity. 338 " 339 ::= { gumObjects 1 } 341 gumDeviceEntry OBJECT-TYPE 342 SYNTAX GumDeviceEntry 343 MAX-ACCESS not-accessible 344 STATUS current 345 DESCRIPTION 346 "This entry represents a conceptual row in the 347 gumDevice table. It represents a device that 348 will be monitored for power-on/power-off status. 349 " 350 INDEX { gumDeviceID } 351 ::= { gumDeviceTable 1 } 353 GumDeviceEntry ::= 354 SEQUENCE { 355 gumDeviceID Unsigned32, 356 gumDeviceName SnmpAdminString, 357 gumDeviceMacAddress MacAddress, 358 gumDeviceType SnmpAdminString, 359 gumDeviceLocation SnmpAdminString 360 } 362 gumDeviceID OBJECT-TYPE 363 SYNTAX Unsigned32 364 MAX-ACCESS not-accessible 365 STATUS current 366 DESCRIPTION 367 "A unique arbitrary identifier for this device." 368 ::= { gumDeviceEntry 1 } 370 gumDeviceName OBJECT-TYPE 371 SYNTAX SnmpAdminString (SIZE(1..64)) 372 MAX-ACCESS read-create 373 STATUS current 374 DESCRIPTION 375 "Administratively assigned textual name of this 376 device." 377 ::= { gumDeviceEntry 2 } 379 gumDeviceMacAddress OBJECT-TYPE 380 SYNTAX MacAddress 381 MAX-ACCESS read-only 382 STATUS current 383 DESCRIPTION 384 "MAC Address of this device. 385 If there is no MAC address, this object will be 386 inaccessible." 387 ::= { gumDeviceEntry 3 } 389 gumDeviceType OBJECT-TYPE 390 SYNTAX SnmpAdminString (SIZE(1..64)) 391 MAX-ACCESS read-create 392 STATUS current 393 DESCRIPTION 394 "Administratively assigned textual description about 395 usage type of this device." 396 ::= { gumDeviceEntry 4 } 398 gumDeviceLocation OBJECT-TYPE 399 SYNTAX SnmpAdminString (SIZE(1..64)) 400 MAX-ACCESS read-create 401 STATUS current 402 DESCRIPTION 403 "Administratively assigned textual location 404 name of this device." 405 ::= { gumDeviceEntry 5 } 407 gumDevUsageTable OBJECT-TYPE 408 SYNTAX SEQUENCE OF GumDevUsageEntry 409 MAX-ACCESS not-accessible 410 STATUS current 411 DESCRIPTION 412 "This table models the device usage status 414 Entries in this table are required to survive 415 a reboot of the managed entity. 416 " 417 ::= { gumObjects 2 } 419 gumDevUsageEntry OBJECT-TYPE 420 SYNTAX GumDevUsageEntry 421 MAX-ACCESS not-accessible 422 STATUS current 423 DESCRIPTION 424 "This entry represents a conceptual row in the 425 gumDevUsage table. It represents a power-on/power-off 426 status of a monitored device. 427 " 428 INDEX { gumDeviceID, gumDevUsageDetID } 429 ::= { gumDevUsageTable 1 } 431 GumDevUsageEntry ::= 432 SEQUENCE { 433 gumDevUsageDetID GumStatusDetectionMethod, 434 gumDevUsageDetStatus GumDeviceStatus, 435 gumDevUsageDetTimeStamp TimeStamp, 436 gumDevUsageCreatedTimeStamp TimeStamp 437 } 439 gumDevUsageDetID OBJECT-TYPE 440 SYNTAX GumStatusDetectionMethod 441 MAX-ACCESS not-accessible 442 STATUS current 443 DESCRIPTION 444 "The detection method by which the usage status is 445 computed." 446 ::= { gumDevUsageEntry 1 } 448 gumDevUsageDetStatus OBJECT-TYPE 449 SYNTAX GumDeviceStatus 450 MAX-ACCESS read-only 451 STATUS current 452 DESCRIPTION 453 "the usage status of the device." 454 ::= { gumDevUsageEntry 2 } 456 gumDevUsageDetTimeStamp OBJECT-TYPE 457 SYNTAX TimeStamp 458 MAX-ACCESS read-only 459 STATUS current 460 DESCRIPTION 461 "the time at which the usage status of the 462 device was computed." 463 ::= { gumDevUsageEntry 3 } 465 gumDevUsageCreatedTimeStamp OBJECT-TYPE 466 SYNTAX TimeStamp 467 MAX-ACCESS read-only 468 STATUS current 469 DESCRIPTION 470 "the time at which the entry of usage table created." 471 ::= { gumDevUsageEntry 4 } 473 -- Units of conformance 474 gumGroups OBJECT IDENTIFIER ::= { gumConformance 1} 475 gumCompliances OBJECT IDENTIFIER ::= { gumConformance 2} 476 gumObjectsGroup OBJECT-GROUP 477 OBJECTS { 478 gumDeviceName, 479 gumDeviceMacAddress, 480 gumDeviceType, 481 gumDeviceLocation, 482 gumDevUsageDetStatus, 483 gumDevUsageDetTimeStamp, 484 gumDevUsageCreatedTimeStamp 485 } 486 STATUS current 487 DESCRIPTION 488 " A collection of objects for basic GreenUsage 489 monitoring." 490 ::= { gumGroups 1 } 492 -- Compliance statements 493 gumCompliance MODULE-COMPLIANCE 494 STATUS current 495 DESCRIPTION 496 "The compliance statement for SNMP entities 497 which implement the GREENUSAGE-MIB 498 " 499 MODULE -- this module 500 MANDATORY-GROUPS { gumObjectsGroup 501 } 502 ::= { gumCompliances 1 } 504 END 506 6. Security Considerations 507 There are no management objects defined in this MIB module with a 508 MAX-ACCESS clause of read-write. 509 Some of the readable objects in this MIB module (i.e., objects with a 510 MAX-ACCESS other than not-accessible) may be considered sensitive or 511 vulnerable in some network environments. It is thus important to 512 control even GET and/or NOTIFY access to these objects and possibly 513 to even encrypt the values of these objects when sending them over 514 the network via SNMP. These are the tables and objects and their 515 sensitivity/vulnerability: 516 gumDeviceName, 517 gumDeviceMacAddress, 518 gumDeviceType, 519 gumDeviceLocation, 520 gumDevUsageDetStatus, 521 gumDevUsageDetTimeStamp, 522 gumDevUsageCreatedTimeStamp 523 The above objects may be be used to identify users and their 524 activities. Thus these objects may be considered to be 525 particularly sensitive and/or private. 527 SNMP versions prior to SNMPv3 did not include adequate security. 528 Even if the network itself is secure (for example by using IPsec), 529 even then, there is no control as to who on the secure network is 530 allowed to access and GET/SET (read/change/create/delete) the objects 531 in this MIB module. 533 It is RECOMMENDED that implementers consider the security features as 534 provided by the SNMPv3 framework (see [RFC3410], section 8), 535 including full support for the SNMPv3 cryptographic mechanisms (for 536 authentication and privacy). 538 Further, deployment of SNMP versions prior to SNMPv3 is NOT 539 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 540 enable cryptographic security. It is then a customer/operator 541 responsibility to ensure that the SNMP entity giving access to an 542 instance of this MIB module is properly configured to give access to 543 the objects only to those principals (users) that have legitimate 544 rights to indeed GET or SET (change/create/delete) them. 546 7. IANA Considerations 548 IANA should assign 549 1. a base arc in the 'mib-2' (standards track) OID 550 tree for the 'greenUsageMIB' MODULE-IDENTITY defined in the 551 GREENUSAGE-MIB. 553 8. References 555 8.1. Normative References 557 [RFC2119] Bradner, S., Key words for use in RFCs to Indicate 558 Requirements Levels, BCP 14, RFC 2119, March 1997. 560 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 561 J., Rose, M. and S. Waldbusser, Structure of 562 Management Information Version 2 (SMIv2), STD 58, 563 RFC 2578, April 1999. 565 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 566 J., Rose, M. and S. Waldbusser, Textual Conventions 567 for SMIv2, STD 58, RFC 2579, April 1999. 569 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 570 J., Rose, M. and S. Waldbusser, Conformance 571 Statements for SMIv2, STD 58, RFC 2580, April 1999. 573 [RFC4293] Routhier, S., Management Information Base for the 574 Internet Protocol (IP), RFC 4293, April 2006. 576 [RFC4001] Daniele, M., Haberman, B., Routhier, S. and 577 Schoenwaelder, J., Textual Conventions for Internet 578 Network Addresses, RFC 4001, February 2005. 580 [RFC2863] McCloghrie, K., and Kastenholz., F., The Interfaces 581 Group MIB, RFC 2863, June 2000. 583 8.2. Informative References 585 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 586 Introduction and Applicability Statements for 587 Internet-Standard Management Framework, RFC 3410, 588 December 2002. 589 [RFC7326] Parello, J., Claise, B., Schoening, B. and Quittek, J., 590 Energy Management Framework", RFC 7326, September 2014. 592 9. Acknowledgements 593 The following individuals and groups have contributed to this draft 594 with discussions and comments: 595 Norio Shiratori 596 WIDE Project netman-WG 597 EMAN WG of the IETF 599 The authors would like to thank Glenn Mansfield Keeni for proposing 600 this MIB module and comments for improving this document. 602 10. Authors' Addresses 604 Takuo Suganuma 605 Tohoku University. 606 2-1-1, Katahira 607 Aoba-ku, Sendai, Japan 980-5877. 609 Phone: +81-22-217-5081 610 E-mail: suganuma@tohoku.ac.jp 612 Naoki Nakamura 613 Tohoku University. 614 2-1 Seiryo-machi, 615 Aoba-ku, Sendai, Japan 980-8575. 617 Phone: +81-22-717-8024 618 E-mail: nakamura@med.tohoku.ac.jp 620 Satoru Izumi 621 Tohoku University. 622 2-1-1 Katahira 623 Aoba-ku, Sendai, Japan 980-8577. 625 Phone: +81-22-217-5080 626 E-mail: izumi@ci.cc.tohoku.ac.jp 628 Hiroshi Tsunoda 629 Tohoku Institute of Technology. 630 35-1, Yagiyama Kasumi-cho 631 Taihaku-ku, Sendai, Japan 982-8577. 633 Phone: +81-22-305-3411 634 E-mail: tsuno@m.ieice.org 636 Masahiro Matsuda 637 Tohoku Institute of Technology. 638 35-1, Yagiyama Kasumi-cho 639 Taihaku-ku, Sendai, Japan 982-8577. 641 Phone: +81-22-305-3424 642 E-mail: mmatsuda@tohtech.ac.jp 644 Kohei Ohta 645 Cyber Solutions Inc. 646 6-6-3, Minami Yoshinari 647 Aoba-ku, Sendai, Japan 989-3204. 649 Phone: +81-22-303-4012 650 E-mail: kohei@cysols.com