idnits 2.17.1 draft-zhou-softwire-lw4o6-mib-00.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 118 has weird spacing: '...ceIndex lw4o6...' == Line 119 has weird spacing: '...ngIndex lw4...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (July 4, 2012) is 4304 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) ** Obsolete normative reference: RFC 4008 (Obsoleted by RFC 7658) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Schoenwaelder 3 Internet-Draft Jacobs University 4 Intended status: Standards Track C. Zhou 5 Expires: January 5, 2013 Huawei Technologies 6 T. Tsou 7 Huawei Technologies (USA) 8 C. Xie 9 China Telecom 10 July 4, 2012 12 Definition of Managed Objects for Lightweight 4over6 Transition 13 Technology 14 draft-zhou-softwire-lw4o6-mib-00 16 Abstract 18 This memo defines a portion of the Management Information Base (MIB) 19 for use with network management protocols in the Internet community. 20 In particular, it defines objects for managing Lightweight 4over6 21 transition technology. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 5, 2013. 40 Copyright Notice 42 Copyright (c) 2012 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. The Internet-Standard Management Framework . . . . . . . . . . 3 59 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 4 62 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 64 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 65 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 66 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 67 10.1. Normative References . . . . . . . . . . . . . . . . . . 13 68 10.2. Informative References . . . . . . . . . . . . . . . . . 14 70 1. Introduction 72 This memo defines a portion of the Management Information Base (MIB) 73 for use with network management protocols. In particular, it defines 74 objects for managing the Lightweight 4over6 transition technology. 75 The management of the network address translation function of 76 Lightweight 4over6 initiators is expected to be handled by an updated 77 version of the NAT-MIB [RFC4008], perhaps with a small Lightweight 78 4over6 specific addition. 80 2. The Internet-Standard Management Framework 82 For a detailed overview of the documents that describe the current 83 Internet-Standard Management Framework, please refer to section 7 of 84 RFC 3410 [RFC3410]. 86 Managed objects are accessed via a virtual information store, termed 87 the Management Information Base or MIB. MIB objects are generally 88 accessed through the Simple Network Management Protocol (SNMP). 89 Objects in the MIB are defined using the mechanisms defined in the 90 Structure of Management Information (SMI). This memo specifies a MIB 91 module that is compliant to the SMIv2, which is described in STD 58, 92 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 93 [RFC2580]. 95 3. Conventions 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in RFC 2119 [RFC2119]. 101 4. Overview 103 The MIB module is organized into a group of scalars and tables. 104 TODO: Add more details! 106 The OID tree structure of the MIB module is shown below. 108 --lw4o6Mib(1.3.6.1.2.1.XXXX) 109 +--lw4o6Objects(1) 110 +--lw4o6IfTable(1) 111 | +--lw4o6IfEntry(1) [lw4o6IfIndex] 112 | +-- --- InterfaceIndex lw4o6IfIndex(1) 113 | +-- rwn Bits lw4o6IfIcmpControl(2) 114 | +-- r-n Counter32 lw4o6IfBindingMatchFailures(3) 115 | +-- r-n Counter32 lw4o6IfNoBindingFailures(4) 116 +--lw4o6BindTable(2) 117 +--lw4o6BindEntry(1) [lw4o6BindIfIndex,lw4o6BindIndex] 118 +-- --- InterfaceIndex lw4o6BindIfIndex(1) 119 +-- --- BindingIndex lw4o6BindIndex(2) 120 +-- r-n Enumeration lw4o6BindType(3) 121 +-- r-n InetAddressIPv6 lw4o6BindIPv6Address(4) 122 +-- r-n InetAddressIPv4 lw4o6BindIPv4Address(5) 123 +-- r-n Integer32 lw4o6BindPortRangeValue(6) 124 +-- r-n Integer32 lw4o6BindPortRangeMask(7) 125 +-- r-n Integer32 lw4o6BindRandomFunction(8) 126 +-- r-n Integer32 lw4o6BindRandomStartingPoint(9) 127 +-- r-n OctetString lw4o6BindRandomKey(10) 128 +-- r-n Integer32 lw4o6BindNumberOfPorts(11) 129 +-- r-n Gauge32 lw4o6BindNumberOfPortsUsed(12) 130 +-- r-n Counter32 lw4o6BindPortAllocationFailures(13) 132 5. Relationship to Other MIB Modules 134 The MIB module IMPORTS definitions from SNMPv2-SMI [RFC2578], 135 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], SNMP-FRAMEWORK-MIB 136 [RFC3411], IF-MIB [RFC2863], and INET-ADDRESS-MIB [RFC4001]. 138 6. Definitions 140 LW4O6-MIB DEFINITIONS ::= BEGIN 142 IMPORTS 143 MODULE-IDENTITY, OBJECT-TYPE, 144 Integer32, Gauge32, Counter32, mib-2 145 FROM SNMPv2-SMI -- RFC 2578 146 TEXTUAL-CONVENTION 147 FROM SNMPv2-TC -- RFC 2579 148 OBJECT-GROUP, MODULE-COMPLIANCE 149 FROM SNMPv2-CONF -- RFC 2580 150 InterfaceIndex 151 FROM IF-MIB -- RFC 2863 152 InetAddressIPv4, InetAddressIPv6 153 FROM INET-ADDRESS-MIB; -- RFC 4001 155 lw4o6Mib MODULE-IDENTITY 156 LAST-UPDATED "201207040000Z" 158 ORGANIZATION 159 "Huawei Technologies" 160 CONTACT-INFO 161 "Cathy Zhou 162 Huawei Technologies 163 Email: cathyzhou@huawei.com 165 Tina Tsou 166 Huawei Technologies (USA) 167 Email: tina.tsou.zouting@huawei.com" 168 DESCRIPTION 169 "The MIB module for managing the Lightweight 4over6 transition 170 technology. 172 Copyright (c) 2012 IETF Trust and the persons identified as 173 authors of the code. All rights reserved. 175 Redistribution and use in source and binary forms, with or 176 without modification, is permitted pursuant to, and subject 177 to the license terms contained in, the Simplified BSD 178 License set forth in Section 4.c of the IETF Trust's 179 Legal Provisions Relating to IETF Documents 180 (http://trustee.ietf.org/license-info)." 182 REVISION "201207040000Z" 183 DESCRIPTION 184 "Initial version, published as RFC XXXX." 185 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 186 ::= { mib-2 XXXX } 188 lw4o6Notifications OBJECT IDENTIFIER ::= { lw4o6Mib 0 } 189 lw4o6Objects OBJECT IDENTIFIER ::= { lw4o6Mib 1 } 190 lw4o6Conformance OBJECT IDENTIFIER ::= { lw4o6Mib 2 } 192 -- Textual convention definitions: 194 BindingIndex ::= TEXTUAL-CONVENTION 195 DISPLAY-HINT "d" 196 STATUS current 197 DESCRIPTION 198 "A unique value, greater than zero, identifying a Lightweight 199 4over6 binding. The value for each binding must remain 200 constant at least from one re-initialization of the 201 Lightweight 4over6 subsystem to the next re-initialization." 202 SYNTAX Integer32 (1..2147483647) 204 -- Object definitions: 206 -- lw4o6IfTable: 208 lw4o6IfTable OBJECT-TYPE 209 SYNTAX SEQUENCE OF Lw4o6IfEntry 210 MAX-ACCESS not-accessible 211 STATUS current 212 DESCRIPTION 213 "The lw4o6IfTable extends the interface table providing 214 information about Lightweight 4over6 specific error conditions 215 and it controls the interface specific handling of detected 216 error situations." 217 ::= { lw4o6Objects 1 } 219 lw4o6IfEntry OBJECT-TYPE 220 SYNTAX Lw4o6IfEntry 221 MAX-ACCESS not-accessible 222 STATUS current 223 DESCRIPTION 224 "An entry of the lw4o6IfTable providing information about 225 Lightweight 4over6 statistics if an interface." 226 INDEX { lw4o6IfIndex } 227 ::= { lw4o6IfTable 1 } 229 Lw4o6IfEntry ::= SEQUENCE { 230 lw4o6IfIndex InterfaceIndex, 231 lw4o6IfIcmpControl BITS, 232 lw4o6IfBindingMatchFailures Counter32, 233 lw4o6IfNoBindingFailures Counter32 234 } 236 lw4o6IfIndex OBJECT-TYPE 237 SYNTAX InterfaceIndex 238 MAX-ACCESS not-accessible 239 STATUS current 240 DESCRIPTION 241 "The network interface the Lightweight 4over6 statistics are 242 associated with." 243 ::= { lw4o6IfEntry 1 } 245 lw4o6IfIcmpControl OBJECT-TYPE 246 SYNTAX BITS { icmpOnMatchFailure(0), icmpOnBindingFailure(1) } 247 MAX-ACCESS read-write 248 STATUS current 249 DESCRIPTION 250 "This object controls the generation of ICMP messages on certain 251 failures. 253 If the icmpOnMatchFailure(0) bit is set, then an ICMP message 254 is generated when an encapsulated packet is received that does 255 not match a valid binding. 257 If the icmpOnBindingFailure(1) bit is set, then an ICMP 258 message is generated if a packet is received for which there 259 is no valid binding." 260 ::= { lw4o6IfEntry 2 } 262 lw4o6IfBindingMatchFailures OBJECT-TYPE 263 SYNTAX Counter32 264 MAX-ACCESS read-only 265 STATUS current 266 DESCRIPTION 267 "The number of packets received over this interfaces that have 268 been dropped by the concentrator because the IPv6 source 269 address of the outer header or the IPv4 source address or the 270 port number of the inner header did not match a valid binding." 271 ::= { lw4o6IfEntry 3 } 273 lw4o6IfNoBindingFailures OBJECT-TYPE 274 SYNTAX Counter32 275 MAX-ACCESS read-only 276 STATUS current 277 DESCRIPTION 278 "The number of packets received over this interfaces that have 279 been dropped by the concentrator because the IPv4 address and 280 port number of a received IPv4 packet does not match a valid 281 binding." 282 ::= { lw4o6IfEntry 4 } 284 -- lw4o6IfBindTable: 286 lw4o6BindTable OBJECT-TYPE 287 SYNTAX SEQUENCE OF Lw4o6BindEntry 288 MAX-ACCESS not-accessible 289 STATUS current 290 DESCRIPTION 291 "The lw4o6IfBindTable extends the interface table providing 292 information about Lightweight 4over6 bindings." 293 ::= { lw4o6Objects 2 } 295 lw4o6BindEntry OBJECT-TYPE 296 SYNTAX Lw4o6BindEntry 297 MAX-ACCESS not-accessible 298 STATUS current 299 DESCRIPTION 300 "An entry of the lw4o6IfBindTable providing information about 301 Lightweight 4over6 bindings." 302 INDEX { lw4o6BindIfIndex, lw4o6BindIndex } 303 ::= { lw4o6BindTable 1 } 305 -- DISCUSS: Is the binding table a per interface table or a global 306 -- table? 308 Lw4o6BindEntry ::= SEQUENCE { 309 lw4o6BindIfIndex InterfaceIndex, 310 lw4o6BindIndex BindingIndex, 311 lw4o6BindType INTEGER, 312 lw4o6BindIPv6Address InetAddressIPv6, 313 lw4o6BindIPv4Address InetAddressIPv4, 314 lw4o6BindPortRangeValue Integer32, 315 lw4o6BindPortRangeMask Integer32, 316 lw4o6BindRandomFunction Integer32, 317 lw4o6BindRandomStartingPoint Integer32, 318 lw4o6BindRandomKey OCTET STRING, 319 lw4o6BindNumberOfPorts Integer32, 320 lw4o6BindNumberOfPortsUsed Gauge32, 321 lw4o6BindPortAllocationFailures Counter32 322 } 324 lw4o6BindIfIndex OBJECT-TYPE 325 SYNTAX InterfaceIndex 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "The interface the Lightweight 4over6 bindings are 330 associated with." 331 ::= { lw4o6BindEntry 1 } 333 lw4o6BindIndex OBJECT-TYPE 334 SYNTAX BindingIndex 335 MAX-ACCESS not-accessible 336 STATUS current 337 DESCRIPTION 338 "An index uniquely identifying a binding." 339 ::= { lw4o6BindEntry 2 } 341 lw4o6BindType OBJECT-TYPE 342 SYNTAX INTEGER { unknown(0), portrange(1), portrandom(2) } 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The port binding type: 348 portrange(1) The port range is specified using a port 349 range value and a port range mask. 351 portrandom(2) 353 " 354 ::= { lw4o6BindEntry 3 } 356 lw4o6BindIPv6Address OBJECT-TYPE 357 SYNTAX InetAddressIPv6 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "The IPv6 address used with this binding." 362 ::= { lw4o6BindEntry 4 } 364 lw4o6BindIPv4Address OBJECT-TYPE 365 SYNTAX InetAddressIPv4 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION 369 "The IPv4 address used with this binding." 370 ::= { lw4o6BindEntry 5 } 372 lw4o6BindPortRangeValue OBJECT-TYPE 373 SYNTAX Integer32 (0..65535) 374 MAX-ACCESS read-only 375 STATUS current 376 DESCRIPTION 377 "The port value used with this binding if the binding type 378 is portrange." 379 REFERENCE 380 "draft-bajko-pripaddrassign-04" 381 ::= { lw4o6BindEntry 6 } 383 lw4o6BindPortRangeMask OBJECT-TYPE 384 SYNTAX Integer32 (0..65535) 385 MAX-ACCESS read-only 386 STATUS current 387 DESCRIPTION 388 "The port mask used with this binding if the binding type 389 is portrange." 390 REFERENCE 391 "draft-bajko-pripaddrassign-04" 392 ::= { lw4o6BindEntry 7 } 394 lw4o6BindRandomFunction OBJECT-TYPE 395 SYNTAX Integer32 (0..65535) 396 MAX-ACCESS read-only 397 STATUS current 398 DESCRIPTION 399 "The random function used with this binding if the binding type 400 is portrandom." 401 REFERENCE 402 "draft-bajko-pripaddrassign-04" 403 ::= { lw4o6BindEntry 8 } 405 lw4o6BindRandomStartingPoint OBJECT-TYPE 406 SYNTAX Integer32 (0..65535) 407 MAX-ACCESS read-only 408 STATUS current 409 DESCRIPTION 410 "The value used as input to the random function if the 411 binding type is portrandom." 412 REFERENCE 413 "draft-bajko-pripaddrassign-04" 414 ::= { lw4o6BindEntry 9 } 416 lw4o6BindRandomKey OBJECT-TYPE 417 SYNTAX OCTET STRING 418 MAX-ACCESS read-only 419 STATUS current 420 DESCRIPTION 421 "The key used as input to the random function if the 422 binding type is portrandom." 423 REFERENCE 424 "draft-bajko-pripaddrassign-04" 425 ::= { lw4o6BindEntry 10 } 427 lw4o6BindNumberOfPorts OBJECT-TYPE 428 SYNTAX Integer32 (0..65535) 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION 432 "The total number of ports of this binding." 433 ::= { lw4o6BindEntry 11 } 435 lw4o6BindNumberOfPortsUsed OBJECT-TYPE 436 SYNTAX Gauge32 (0..65535) 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "The number of ports of this binding that are currently used." 441 ::= { lw4o6BindEntry 12 } 443 lw4o6BindPortAllocationFailures OBJECT-TYPE 444 SYNTAX Counter32 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "The number of situations where a port could not be allocated 449 because there we no more ports left in the binding." 450 ::= { lw4o6BindEntry 13 } 452 -- Compliance definitions: 454 lw4o6Groups OBJECT IDENTIFIER ::= { lw4o6Conformance 1 } 455 lw4o6Compliances OBJECT IDENTIFIER ::= { lw4o6Conformance 2 } 457 lw4o6FullCompliance MODULE-COMPLIANCE 458 STATUS current 459 DESCRIPTION 460 "Compliance statement for implementations supporting 461 read/write access, according to the object definitions." 462 MODULE -- this module 464 MANDATORY-GROUPS { 465 lw4o6IfGroup, 466 lw4o6BindGroup 467 } 469 ::= { lw4o6Compliances 1 } 471 lw4o6ReadOnlyCompliance MODULE-COMPLIANCE 472 STATUS current 473 DESCRIPTION 474 "Compliance statement for implementations supporting 475 only readonly access." 476 MODULE -- this module 478 MANDATORY-GROUPS { 479 lw4o6IfGroup, 480 lw4o6BindGroup 481 } 483 OBJECT lw4o6IfIcmpControl 484 MIN-ACCESS read-only 485 DESCRIPTION 486 "Write access is not required." 488 ::= { lw4o6Compliances 2 } 490 lw4o6IfGroup OBJECT-GROUP 491 OBJECTS { 492 -- lw4o6IfIndex, 493 lw4o6IfIcmpControl, 494 lw4o6IfBindingMatchFailures, 495 lw4o6IfNoBindingFailures 496 } 497 STATUS current 498 DESCRIPTION 499 "A collection of objects providing insight into the 500 performance of a Lightweight 4over6 interface." 501 ::= { lw4o6Groups 1 } 503 lw4o6BindGroup OBJECT-GROUP 504 OBJECTS { 505 -- lw4o6BindIfIndex, 506 -- lw4o6BindIndex 507 lw4o6BindType, 508 lw4o6BindIPv6Address, 509 lw4o6BindIPv4Address, 510 lw4o6BindPortRangeValue, 511 lw4o6BindPortRangeMask, 512 lw4o6BindRandomFunction, 513 lw4o6BindRandomStartingPoint, 514 lw4o6BindRandomKey, 515 lw4o6BindNumberOfPorts, 516 lw4o6BindNumberOfPortsUsed, 517 lw4o6BindPortAllocationFailures 518 } 519 STATUS current 520 DESCRIPTION 521 "A collection of objects providing insight into the 522 bindings associated with a Lightweight 4over6 interface." 523 ::= { lw4o6Groups 2 } 525 END 527 7. Security Considerations 529 There are a number of management objects defined in this MIB module 530 with a MAX-ACCESS clause of read-write and/or read-create. Such 531 objects may be considered sensitive or vulnerable in some network 532 environments. The support for SET operations in a non-secure 533 environment without proper protection can have a negative effect on 534 network operations. These are the tables and objects and their 535 sensitivity/vulnerability: 537 Some of the readable objects in this MIB module (i.e., objects with a 538 MAX-ACCESS other than not-accessible) may be considered sensitive or 539 vulnerable in some network environments. It is thus important to 540 control even GET and/or NOTIFY access to these objects and possibly 541 to even encrypt the values of these objects when sending them over 542 the network via SNMP. These are the tables and objects and their 543 sensitivity/vulnerability: 545 SNMP versions prior to SNMPv3 did not include adequate security. 546 Even if the network itself is secure (for example by using IPsec), 547 even then, there is no control as to who on the secure network is 548 allowed to access and GET/SET (read/change/create/delete) the objects 549 in this MIB module. 551 It is RECOMMENDED that implementers consider the security features as 552 provided by the SNMPv3 framework (see [RFC3410], section 8), 553 including full support for the SNMPv3 cryptographic mechanisms (for 554 authentication and privacy). 556 Further, deployment of SNMP versions prior to SNMPv3 is NOT 557 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 558 enable cryptographic security. It is then a customer/operator 559 responsibility to ensure that the SNMP entity giving access to an 560 instance of this MIB module is properly configured to give access to 561 the objects only to those principals (users) that have legitimate 562 rights to indeed GET or SET (change/create/delete) them. 564 8. IANA Considerations 566 IANA is requested to assign a value for "XXXX" under the 'mib-2' 567 subtree and to record the assignment in the SMI Numbers registry. 568 When the assignment has been made, the RFC Editor is asked to replace 569 "XXXX" (here and in the MIB module) with the assigned value and to 570 remove this note. 572 9. Acknowledgements 574 TBD 576 10. References 578 10.1. Normative References 580 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 581 Requirement Levels", BCP 14, RFC 2119, March 1997. 583 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 584 Schoenwaelder, Ed., "Structure of Management Information 585 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 587 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 589 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 590 STD 58, RFC 2579, April 1999. 592 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 593 "Conformance Statements for SMIv2", STD 58, RFC 2580, 594 April 1999. 596 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 597 MIB", RFC 2863, June 2000. 599 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 600 Architecture for Describing Simple Network Management 601 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 602 December 2002. 604 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 605 Schoenwaelder, "Textual Conventions for Internet Network 606 Addresses", RFC 4001, February 2005. 608 [RFC4008] Rohit, R., Srisuresh, P., Raghunarayan, R., Pai, N., and 609 C. Wang, "Definitions of Managed Objects for Network 610 Address Translators (NAT)", RFC 4008, March 2005. 612 10.2. Informative References 614 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 615 "Introduction and Applicability Statements for Internet- 616 Standard Management Framework", RFC 3410, December 2002. 618 Authors' Addresses 620 Juergen Schoenwaelder 621 Jacobs University 622 Campus Ring 1 623 Bremen 28759 624 Germany 626 EMail: j.schoenwaelder@jacobs-university.de 628 Cathy Zhou 629 Huawei Technologies 630 Bantian, Longgang District 631 Shenzhen 518129 632 P.R. China 634 EMail: cathy.zhou@huawei.com 635 Tina Tsou 636 Huawei Technologies (USA) 637 2330 Central Expressway 638 Santa Clara CA 95050 639 USA 641 EMail: tina.tsou.zouting@huawei.com 643 Chongfeng Xie 644 China Telecom 645 Room 708 No.118, Xizhimenneidajie 646 Beijing 647 P.R. China 649 EMail: xiechf@ctbri.com.cn