idnits 2.17.00 (12 Aug 2021) /tmp/idnits30834/draft-syam-ipv6-state-model-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. 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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 64 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 178 has weird spacing: '...in this state...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2003) is 6793 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: '1' is defined on line 428, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 431, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 434, but no explicit reference was found in the text == Outdated reference: draft-ietf-entmib-state has been published as RFC 4268 Summary: 4 errors (**), 0 flaws (~~), 6 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group S. Madanaplli 2 INTERNET DRAFT S. Kumar 3 O.L.N. Rao 4 Expires: April 2004 S. Park 5 Category:Informational SAMSUNG 6 October 2003 8 State Model for IPv6 Interfaces 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance 13 with all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as 18 Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six 21 months and may be updated, replaced, or obsoleted by other 22 documents at any time. It is inappropriate to use Internet- 23 Drafts as reference material or to cite them other than as 24 "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Abstract 34 This document specifies a generic flexible state model for IPv6 35 Interfaces. 37 Table of Contents 39 1. Introduction ............................................. 3 40 2. Terminology .............................................. 3 41 3. State Model .............................................. 3 42 3.1. Interface States ......................................... 4 43 3.1.1. Primary State ............................................ 4 44 3.1.2. Primary State Qualifier .................................. 4 45 3.1.3. Secondary State .......................................... 5 46 3.1.4. Secondary State Qualifier ................................ 6 47 3.2. Events ................................................... 6 48 3.2.1. Management Events ........................................ 6 49 3.2.2. Lower Layer Events ....................................... 6 50 3.2.3. Autonomous Events ........................................ 7 51 3.3. Dependencies among states ................................ 7 52 3.4. State Transition Diagram ................................. 8 53 3.5. State Transition Table ................................... 9 54 4. Security Considerations .................................. 11 55 5. References ............................................... 11 56 6. Acknowledgements ......................................... 11 57 7. Authors' Addresses ....................................... 12 58 8. Intellectual Property Statement .......................... 12 59 9. Full Copyright Statement ................................. 13 60 1. Introduction 62 This document defines a state model for IPv6 Interfaces. This state 63 model facilitates the administrator to know the current status of 64 the IPv6 interface at any instant and provides information about what 65 actions the administrator may need to take to bring the interface 66 UP, if it is currently unavailable for performing the provisioned 67 services. 69 Any entity in any layered architecture can be DOWN (non-functional) 70 because of the following three reasons: 72 o The management (administrator) explicitly prevented in 73 performing the assigned services. 75 o The lower layer is not providing its assigned services. 77 o There is an internal fault in the entity itself. 79 At any instant, there can be multiple reasons (the combination of 80 the above) because of which the entity may be non-functional. This 81 document captures all the states an IPv6 interface may under go 82 because of the above mentioned reasons. 84 The State Model defined in this document is flexible in the sense 85 that one can define their own reasons/fault conditions for the IPv6 86 interfaces depending on their needs. 88 The State Model described here is based on the Control State 89 Machine that has been implemented in Samsung's IPv6 Protocol Stack. 91 2. Terminology 93 Primary State (PST) 95 Indicates the current overall service condition of an entity. 97 Primary State Qualifier (PSTQ) 99 This gives further information about why the entity is in a 100 particular PST. 102 Secondary State (SST) 104 Provides additional information relevant to state management. 106 3. State Model 108 The State of an entity consists of Operational State and 109 Administrative State. The Operational State indicates whether the 110 entity is capable of providing its provisioned functions. The 111 Administrative State indicates whether it is administratively 112 inhibited from providing its provisioned functions. The Primary 113 State provides the overall service condition of the entity which 114 will be qualified by the Primary State Qualifier. The secondary 115 State and its Qualifiers provide further information why the entity 116 is not able to provide its assigned services. 118 3.1. Interface States 120 3.1.1. Primary State 122 Primary State indicates the overall service condition of the entity, 123 whether it is UP (In-Service), or DOWN (Out-of-Service). 125 UP 126 The entity is partially or fully operable to provide some or all 127 of its assigned services to the users. The entity is 128 operationally capable and at the same time administratively 129 allowed to provide its services. That is, both the operational 130 and administrative states are UP. 132 DOWN 133 The entity is totally inoperable and unable to provide any of its 134 assigned services to the users. The PSTQ value will qualify the 135 unavailability of the entity. For example, whether it is 136 operationally incapable or administratively inhibited from 137 providing its services. 139 3.1.2. Primary State Qualifier 141 The following values of PSTQ qualify the PST value DOWN. 143 AU (Autonomous) 144 Operational State is DOWN. 146 MA (Management) 147 Administrative State is DOWN. 149 AUMA (Autonomous-and-Management) 150 Both Operational and Administrative States are DOWN. 152 Autonomous (AU) 154 The entity is incapable of providing any of its services, and 155 there is no external administrative restriction inhibiting the 156 entity from providing these services. In general, the cause of 157 incapability is an unsolicited event occurrence on the Interface. 158 Examples of such events include, but not limited to a defect 159 developed in the entity, its Lower Layer (Supporting Entity) is 160 DOWN or the Interface ID is duplicate incase of IPv6 Interface 161 etc. 163 Management (MA) 165 The entity is intentionally suspended by the external management 166 command from providing all of its services. In this state the 167 entity itself is still operationally capable of, even though it 168 is currently being suspended from providing service. While 169 resident in this state, updates of providing service, data, and 170 testing and maintenance activities are permitted. Fault detection 171 shall be continued in this state, however no reports will be 172 generated to the management. 174 AUMA (Autonomous-and-Management) 176 The entity is incapable of providing services, and at the same 177 time it has been intentionally suspended from providing all of its 178 services. While resident in this state, updates of provisioning 179 data and Testing and maintenance activities are permitted. Fault 180 detection shall be continued to determine if an operational 181 problem has been corrected or an additional operational problem 182 has occurred. 184 3.1.3. Secondary State 186 The following are the SST values that a stack entity can have: 188 UAS (Unassigned) 189 The IPv6 interface has not been assigned with the necessary 190 provisioning data. That is the IPv6 Interface does not exist. 191 No SSTQs have been defined for this SST. 193 LLD (Lower Layer Down) 194 The associated lower layer entity (Layer 2) is DOWN. 195 No SSTQs have been defined for this SST. 197 LLD (Lower Layer Association Down) 198 The associated lower layer entity (Layer 2) Association is DOWN. 199 No SSTQs have been defined for this SST. 201 FLT (Internal Fault) 202 The stack entity itself has got some fault that inhibited it from 203 providing services. NORS and DIID have been defined as SSTQs for 204 this SST. 206 3.1.4. Secondary State Qualifier 208 Currently the following SSTQs have been defined. Implementers can 209 define their own SSTQs based on their requirements. 211 NORS 212 Stack entity is out of resources. 214 DIID 215 The interface identifier is Duplicate. 217 3.2. Events 219 3.2.1. Management Events 221 ADMIN-LOCK 222 Management inhibited the interface from providing services. 224 ADMIN_UNLOCK 225 Management permitted interface to provide services. 227 CREATE 228 Create an IPv6 Interface. 230 DELETE 231 Remove an IPv6 Interface. 233 3.2.2. Lower Layer Events 235 LLD 236 The Lower Layer is DOWN. 238 LLU 239 The Lower Layer is UP. 241 LLAD 242 The Lower Layer Association is DOWN. 244 LLAU 245 The Lower Layer Association is UP. 247 3.2.3. Autonomous Events 249 RESOURCE REQUEST FAILED 250 The request for a particular of resource that is required for the 251 interface to be functional is FAILED. 253 DAD FAILED 254 Duplicate IID Detection FAILED. 256 DAD FAIL RECOVER 257 Duplicate IID Detection for the new IID is SUCCEEDED after 258 Management intervention or by some other mechanism. 260 3.3. Dependencies among states 262 The following are the possible combination of Operational and 263 Administrative State values. 265 DOWN and Locked (DOWN, AUMA) 266 The resource is totally inoperable, and it is also 267 administratively prohibited from providing service. To make it 268 available for use, both management permission (an unlock 269 operation) and some corrective action are necessary. 271 UP and Locked (DOWN, MA) 272 The resource is partially or fully operable, but is 273 administratively prohibited from providing service. To make it 274 available for use, only management permission (an unlock 275 operation) is required. 277 DOWN and Unlocked (DOWN, AU) 278 The resource is totally inoperable, but it is not administratively 279 prohibited from providing service. To make it available for use, 280 some corrective action is required. 282 UP and Unlocked (UP) 283 The resource is partially or fully operable, and is not 284 administratively prohibited from providing service. 286 3.4. State Transition Diagram 288 The following is the simplified view of the state machine for IPv6 289 Interfaces. The diagram does not take care of all possible state 290 transitions from different states. 292 +---------+ +---------+ 293 | | | | 294 | |---ADMIN_LOCK--->| | 295 |DOWNN,AU,| | DOWN, | 296 | FLT |<--ADMIN_UNLOCK--| AUMA,FLT| 297 | | | | 298 +---------+ +---------+ 299 | ^ ^ ^ 300 | | | | 301 | | | | 302 RECOVER | | RECOVER 303 | | | + 304 | | | | 305 | | | | 306 | FAULT FAULT | 307 | | | | 308 v | | v 309 +---------+ +---------+ +---------+ 310 | | | | | | 311 | |--CREATE-->| |---ADMIN_LOCK--->| | 312 | UAS | | UP | | DOWN,MA | 313 | |<--DELETE--| |<--ADMIN_UNLOCK--| | 314 | | | | | | 315 +---------+ +---------+ +---------+ 316 | ^ | ^ 317 | | | | 318 | | | | 319 LLD | LLD | 320 | | | | 321 | | | | 322 | LLU | LLU 323 | | | | 324 | | | | 325 | | | | 326 V | V | 327 +---------+ +---------+ 328 | | | | 329 | |---ADMIN_LOCK--->| | 330 | DOWNN, | | DOWN, | 331 | AU,LLD |<--ADMIN_UNLOCK--| AUMA,LLD| 332 | | | | 333 +---------+ +---------+ 335 3.5. State Transition Table 337 +---------------+--------------+---------------+-----------------------+ 338 | Current | | Next | Actions | 339 | State | Event | State | to be taken | 340 +---------------+--------------+---------------+-----------------------+ 341 | UAS | CREATE | UP | Create Interface | 342 | | | | and Make it UP | 343 +---------------+--------------+---------------+-----------------------+ 344 | UP | ADMIN_LOCK | DOWN,MA | Set Admin Flag | 345 +---------------+--------------+---------------+-----------------------+ 346 | UP | LLD | DOWN,AU,LLD | Clear Lower Layer flag| 347 +---------------+--------------+---------------+-----------------------+ 348 | UP | LLAD | DOWN,AU,LLAD | Clear Association flag| 349 +---------------+--------------+---------------+-----------------------+ 350 | UP | FAULT | DOWN,AU,FLT | Set Fault flag | 351 +---------------+--------------+---------------+-----------------------+ 352 | DOWN,MA | ADMIN_UNLOCK | UP | Clear Admin Flag | 353 +---------------+--------------+---------------+-----------------------+ 354 | DOWN,MA | LLD | DOWN,AUMA,LLD | Clear Lower Layer flag| 355 +---------------+--------------+---------------+-----------------------+ 356 | DOWN,MA | LLAD | DOWN,AUMA,LLAD| Clear Association flag| 357 +---------------+--------------+---------------+-----------------------+ 358 | DOWN,MA | FAULT | DOWN,AUMA,FLT | Set Fault flag | 359 +---------------+--------------+---------------+-----------------------+ 360 | DOWN,AU,LLD | ADMIN_LOCK | DOWN,AUMA,LLD | Set Admin Flag | 361 +---------------+--------------+---------------+-----------------------+ 362 | DOWN,AU,LLD | LLU | UP | Set Lower Layer Flag | 363 +---------------+--------------+---------------+-----------------------+ 364 | DOWN,AUMA,LLD | ADMIN_UNLOCK | DOWN,AU,LLD | Clear Admin Flag | 365 +---------------+--------------+---------------+-----------------------+ 366 | DOWN,AUMA,LLD | LLU | DOWN,MA | Set Lower Layer Flag | 367 +---------------+--------------+---------------+-----------------------+ 368 | DOWN,AU,LLAD | ADMIN_LOCK | DOWN,AUMA,LLAD| Set Admin Flag | 369 +---------------+--------------+---------------+-----------------------+ 370 | DOWN,AU,LLAD | LLAU | UP | Set Association Flag | 371 +---------------+--------------+---------------+-----------------------+ 372 | DOWN,AUMA,LLAD| ADMIN_UNLOCK | DOWN,AU,LLAD | Clear Admin Flag | 373 +---------------+--------------+---------------+-----------------------+ 374 | DOWN,AUMA,LLAD| LLAU | DOWN,MA | Set Association Flag | 375 +---------------+--------------+---------------+-----------------------+ 376 | DOWN,AU,FLT | ADMIN_LOCK | DOWN,AUMA,FLT | Set Admin Flag | 377 +---------------+--------------+---------------+-----------------------+ 378 | DOWN,AU,FLT | RECOVER(LLU) | UP | Set Lower Layer Flag | 379 +---------------+--------------+---------------+-----------------------+ 380 | DOWN,AU,FLT | RECOVER(LLD) | DOWN,AU,LLD | Clear Lower Layer Flag| 381 +---------------+--------------+---------------+-----------------------+ 382 +---------------+--------------+---------------+-----------------------+ 383 | DOWN,AU,FLT | RECOVER(LLAU)| UP | Set Lower Layer Flag | 384 +---------------+--------------+---------------+-----------------------+ 385 | DOWN,AU,FLT | RECOVER(LLAD)| DOWN,AU,LLAD | Clear Association Flag| 386 +---------------+--------------+---------------+-----------------------+ 387 | DOWN,AUMA,FLT | ADMIN_UNLOCK | DOWN,AU,FLT | Clear Admin Flag | 388 +---------------+--------------+---------------+-----------------------+ 389 | DOWN,AUMA,FLT | RECOVER(LLU) | DOWN,MA | Set Lower Layer Flag | 390 +---------------+--------------+---------------+-----------------------+ 391 | DOWN,AUMA,FLT | RECOVER(LLD) | DOWN,AUMA,LLD | Clear Lower Layer Flag| 392 +---------------+--------------+---------------+-----------------------+ 393 | DOWN,AUMA,FLT | RECOVER(LLAU)| DOWN,MA | Set Lower Layer Flag | 394 +---------------+--------------+---------------+-----------------------+ 395 | DOWN,AUMA,FLT | RECOVER(LLAD)| DOWN,AUMA,LLAD| Clear Association Flag| 396 +---------------+--------------+---------------+-----------------------+ 397 | | DELETE | UAS | Lock and then Shutdown| 398 | | | | the Interface | 399 +---------------+--------------+---------------+-----------------------+ 400 4. Security Considerations 402 CREATE/DELETE and ADMIN_LOCK/ADMIN_UNLOCK operations on an IPv6 403 Interface may be considered sensitive or vulnerable in some network 404 environments. The support for such operations in a non-secure 405 environment without proper protection can have a negative effect 406 on network operations. 408 SNMPv1 by itself is not a secure environment. Even if the network 409 itself is secure (for example by using IPSec), even then, there is 410 no control as to who on the secure network is allowed to access and 411 GET/SET (read/change/create/delete) the state attributes defined in 412 this document. 414 It is recommended that the implementers consider the security 415 features as provided by the SNMPv3 framework when giving access 416 to remote entity using SNMP. Specifically, the use of the User- 417 based Security Model RFC 2574 and the View-based Access Control 418 Model RFC 2575 is recommended. 420 It is then a customer/user responsibility to ensure that the SNMP 421 entity giving access to the state attributes defined in this 422 document, is properly configured to give access to the attributes 423 only to those principals (users) that have legitimate rights to 424 indeed GET or SET (change/create/delete) them. 426 5. References 428 [1] Chisholm, S. and Perkins, D., "Entity State MIB", 429 draft-ietf-entmib-state-00.txt, January 2003. 431 [2] McCloghrie, K. and F. Kastenholz, "The Interface Group MIB", RFC 432 2863, June 2000. 434 [3] ITU Recommendation X.731, "Information Technology - Open Systems 435 Interconnection - System Management: State Management Function", 436 1992 438 6. Acknowledgement 440 The authors would like to thank Margaret Wasserman and Andy Bierman 441 for their comments on this draft. 443 7. Authors' Addresses 445 Syam Madanapalli 446 Network Systems Division, SAMSUNG India Software Operations, INDIA 447 Phone: +91-80-51197777 448 Email:syam@samsung.com 450 O.L.N. Rao 451 Network Systems Division, SAMSUNG India Software Operations, INDIA 452 Phone: +91-80-51197777 453 Email:olnrao@samsung.com 455 Suraj Kumar 456 Network Systems Division, SAMSUNG India Software Operations, INDIA 457 Phone: +91-80-51197777 458 Email:suraj@samsung.com 460 Soohong Daniel Park 461 Mobile Platform Laboratory, SAMSUNG Electronics 462 Phone: +82-31-200-4508 463 Email:soohong.park@samsung.com 465 8. Intellectual Property Statement 467 The IETF takes no position regarding the validity or scope of any 468 intellectual property or other rights that might be claimed to 469 pertain to the implementation or use of the technology described in 470 this document or the extent to which any license under such rights 471 might or might not be available; neither does it represent that it 472 has made any effort to identify any such rights. Information on the 473 IETF's procedures with respect to rights in standards-track and 474 standards-related documentation can be found in BCP-11. Copies of 475 claims of rights made available for publication and any assurances of 476 licenses to be made available, or the result of an attempt made to 477 obtain a general license or permission for the use of such 478 proprietary rights by implementers or users of this specification can 479 be obtained from the IETF Secretariat. 481 The IETF invites any interested party to bring to its attention any 482 copyrights, patents or patent applications, or other proprietary 483 rights which may cover technology that may be required to practice 484 this standard. Please address the information to the IETF Executive 485 Director. 487 9. Full Copyright Statement 489 Copyright (C) The Internet Society (2003). All Rights Reserved. 491 This document and translations of it may be copied and furnished to 492 others, and derivative works that comment on or otherwise explain it 493 or assist in its implementation may be prepared, copied, published and 494 distributed, in whole or in part, without restriction of any kind, 495 provided that the above copyright notice and this paragraph are 496 included on all such copies and derivative works. However, this 497 document itself may not be modified in any way, such as by removing 498 the copyright notice or references to the Internet Society or other 499 Internet organizations, except as needed for the purpose of developing 500 Internet standards in which case the procedures for copyrights defined 501 in the Internet Standards process must be followed, or as required to 502 translate it into languages other than English. 504 The limited permissions granted above are perpetual and will not be 505 revoked by the Internet Society or its successors or assigns. 507 This document and the information contained herein is provided on an 508 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 509 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 510 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 511 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 512 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 514 Funding for the RFC editor function is currently provided by the 515 Internet Society.