idnits 2.17.1 draft-ietf-intserv-v2-mib-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-24) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://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. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 29 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** 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.) ** There are 116 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 3 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 161 has weird spacing: '... Number conve...' == Line 162 has weird spacing: '...numbers ident...' == Line 163 has weird spacing: '...mber in the ...' == Line 164 has weird spacing: '...eturned by a...' == Line 168 has weird spacing: '...nstance or...' == (111 more instances...) -- 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 (July 1997) is 9780 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) -- Missing reference section? '9' on line 127 looks like a reference -- Missing reference section? '1' on line 908 looks like a reference -- Missing reference section? '2' on line 914 looks like a reference -- Missing reference section? '3' on line 920 looks like a reference Summary: 12 errors (**), 0 flaws (~~), 8 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Integrated Services MIB July 1997 4 Integrated Services Management Information Base 5 draft-ietf-intserv-v2-mib-00.txt 7 Thu Oct 2 22:42:04 PDT 1997 9 Fred Baker 11 Cisco Systems 12 519 Lado Drive 13 Santa Barbara, California 93111 15 fred@cisco.com 17 John Krawczyk 19 ArrowPoint Communications 20 235 Littleton Road 21 Westford, Massachusetts 01886 23 jjk@tiac.net 25 1. Status of this Memo 27 This document is an Internet Draft. Internet Drafts are 28 working documents of the Internet Engineering Task Force 29 (IETF), its Areas, and its Working Groups. Note that other 30 groups may also distribute working documents as Internet 31 Drafts. 33 Internet Drafts are draft documents valid for a maximum of six 34 months. Internet Drafts may be updated, replaced, or obsoleted 35 by other documents at any time. It is not appropriate to use 36 Internet Drafts as reference material or to cite them other 37 than as a "working draft" or "work in progress." 39 Please check the I-D abstract listing contained in each 40 Internet Draft directory to learn the current status of this 41 or any other Internet Draft. 43 2. Abstract 45 This memo defines a portion of the Management Information Base 46 (MIB) for use with network management protocols in TCP/IP- 47 based internets. In particular, it defines objects for 48 managing the the interface attributes defined in the 49 Integrated Services Model. Comments should be made to the 50 Integrated Services Working Group, int-serv@isi.edu. 52 This memo does not, in its draft form, specify a standard for 53 the Internet community. 55 3. The SNMPv2 Network Management Framework 57 The SNMPv2 Network Management Framework consists of four major 58 components. They are: 60 o RFC 1441 which defines the SMI, the mechanisms used for 61 describing and naming objects for the purpose of 62 management. 64 o RFC 1213 defines MIB-II, the core set of managed objects 65 for the Internet suite of protocols. 67 o RFC 1445 which defines the administrative and other 68 architectural aspects of the framework. 70 o RFC 1448 which defines the protocol used for network 71 access to managed objects. 73 The Framework permits new objects to be defined for the 74 purpose of experimentation and evaluation. 76 3.1. Object Definitions 78 Managed objects are accessed via a virtual information store, 79 termed the Management Information Base or MIB. Objects in the 80 MIB are defined using the subset of Abstract Syntax Notation 81 One (ASN.1) defined in the SMI. In particular, each object 82 type is named by an OBJECT IDENTIFIER, an administratively 83 assigned name. The object type together with an object 84 instance serves to uniquely identify a specific instantiation 85 of the object. For human convenience, we often use a textual 86 string, termed the descriptor, to refer to the object type. 88 4. Overview 90 4.1. Textual Conventions 92 Several new data types are introduced as a textual convention 93 in this MIB document. These textual conventions enhance the 94 readability of the specification and can ease comparison with 95 other specifications if appropriate. It should be noted that 96 the introduction of the these textual conventions has no 97 effect on either the syntax nor the semantics of any managed 98 objects. The use of these is merely an artifact of the 99 explanatory method used. Objects defined in terms of one of 100 these methods are always encoded by means of the rules that 101 define the primitive type. Hence, no changes to the SMI or 102 the SNMP are necessary to accommodate these textual 103 conventions which are adopted merely for the convenience of 104 readers and writers in pursuit of the elusive goal of clear, 105 concise, and unambiguous MIB documents. 107 4.2. Structure of MIB 109 The MIB is composed of the following sections: 110 Integrated Services 111 Interface Attributes Table 112 Interface Flow Table 114 5. Definitions 116 INTEGRATED-SERVICES-MIB DEFINITIONS ::= BEGIN 118 IMPORTS 119 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 120 Gauge32, Integer32, mib-2 FROM SNMPv2-SMI 121 TEXTUAL-CONVENTION, RowStatus, 122 TruthValue, TestAndIncr FROM SNMPv2-TC 123 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 124 ifIndex, InterfaceIndex FROM IF-MIB; 126 -- This MIB module uses the extended OBJECT-TYPE macro as 127 -- defined in [9]. 129 intSrv MODULE-IDENTITY 130 LAST-UPDATED "9710030642Z" -- Thu Oct 2 22:42:04 PDT 1997 131 ORGANIZATION "IETF Integrated Services Working Group" 132 CONTACT-INFO 133 " Fred Baker 134 Postal: Cisco Systems 135 519 Lado Drive 136 Santa Barbara, California 93111 137 Tel: +1 805 681 0115 138 E-Mail: fred@cisco.com 140 John Krawczyk 141 Postal: ArrowPoint Communications 142 235 Littleton Road 143 Westford, Massachusetts 01886 144 Tel: +1 508 692 5875 145 E-Mail: jjk@tiac.net" 146 DESCRIPTION 147 "The MIB module to describe the Integrated Services 148 Protocol" 149 ::= { mib-2 52 } 151 intSrvObjects OBJECT IDENTIFIER ::= { intSrv 1 } 152 intSrvGenObjects OBJECT IDENTIFIER ::= { intSrv 2 } 153 intSrvNotifications OBJECT IDENTIFIER ::= { intSrv 3 } 154 intSrvConformance OBJECT IDENTIFIER ::= { intSrv 4 } 156 -- Textual Conventions 157 -- 158 SessionNumber ::= TEXTUAL-CONVENTION 159 STATUS current 160 DESCRIPTION 161 "The Session Number convention is used for 162 numbers identifying sessions or saved PATH or 163 RESV information. It is a number in the range 164 returned by a TestAndIncr variable, having no 165 protocol meaning whatsoever but serving instead 166 as simple identifier. 168 The alternative was a very complex instance or 169 instance object that became unwieldy." 170 SYNTAX INTEGER (0..2147483647) 172 Protocol ::= TEXTUAL-CONVENTION 173 DISPLAY-HINT "d" 174 STATUS current 175 DESCRIPTION 176 "The value of the IP Protocol field of an IP 177 Datagram Header. This identifies the protocol 178 layer above IP. For example, the value 6 is 179 used for TCP and the value 17 is used for UDP. 180 The values of this field are defined in the As- 181 signed Numbers RFC." 182 SYNTAX INTEGER (1..255) 184 SessionType ::= TEXTUAL-CONVENTION 185 STATUS current 186 DESCRIPTION 187 "The value of the C-Type field of a Session ob- 188 ject, as defined in the RSVP specification. 189 This value determines the lengths of octet 190 strings and use of certain objects such as the 191 'port' variables. If the C-Type calls for an 192 IP6 address, one would expect all source, des- 193 tination, and next/previous hop addresses to be 194 16 bytes long, and for the ports to be UDP/TCP 195 port numbers, for example." 196 SYNTAX INTEGER (1..255) 198 Port ::= TEXTUAL-CONVENTION 199 DISPLAY-HINT "d" 200 STATUS current 201 DESCRIPTION 202 "The value of the UDP or TCP Source or Destina- 203 tion Port field, a virtual destination port or 204 generalized port identifier used with the IPSEC 205 Authentication Header or Encapsulating Security 206 Payload, or other session discriminator. If it 207 is not used, the value should be of length 0. 208 This pair, when coupled with the IP Addresses 209 of the source and destination system and the IP 210 protocol field, uniquely identifies a data 211 stream." 212 SYNTAX OCTET STRING (SIZE(2..4)) 214 MessageSize ::= TEXTUAL-CONVENTION 215 DISPLAY-HINT "d" 216 STATUS current 217 DESCRIPTION 218 "The size of a message in bytes. This is used 219 to specify the minimum and maximum size of a 220 message along an integrated services route." 221 SYNTAX INTEGER (0..'7FFFFFFF'h) 223 BitRate ::= TEXTUAL-CONVENTION 224 DISPLAY-HINT "d" 225 STATUS current 226 DESCRIPTION 227 "The rate, in bits/second, that data may move 228 in the context. Applicable contexts minimally 229 include the speed of an interface or virtual 230 circuit, the data rate of a (potentially aggre- 231 gated) data flow, or the data rate to be allo- 232 cated for use by a flow." 233 SYNTAX INTEGER (0..'7FFFFFFF'h) 235 BurstSize ::= TEXTUAL-CONVENTION 236 DISPLAY-HINT "d" 237 STATUS current 238 DESCRIPTION 239 "The number of octets of IP Data, including IP 240 Headers, that a stream may send without concern 241 for policing." 242 SYNTAX INTEGER (0..'7FFFFFFF'h) 244 QosService ::= TEXTUAL-CONVENTION 245 STATUS current 246 DESCRIPTION 247 "The class of service in use by a flow." 248 SYNTAX INTEGER { 249 bestEffort (1), -- Best Effort Service 250 guaranteedDelay (2), -- Guaranteed Delay 251 controlledLoad (5) -- Controlled Load 252 } 254 -- The Integrated Services Interface Attributes Database contains 255 -- information about resources allocated by resource reservation 256 -- protocols, such as RSVP and ST-II. 258 intSrvIfAttribTable OBJECT-TYPE 259 SYNTAX SEQUENCE OF IntSrvIfAttribEntry 260 MAX-ACCESS not-accessible 261 STATUS current 262 DESCRIPTION 263 "The reservable attributes of the system's in- 264 terfaces." 265 ::= { intSrvObjects 1 } 267 intSrvIfAttribEntry OBJECT-TYPE 268 SYNTAX IntSrvIfAttribEntry 269 MAX-ACCESS not-accessible 270 STATUS current 271 DESCRIPTION 272 "The reservable attributes of a given inter- 273 face." 274 INDEX { ifIndex } 275 ::= { intSrvIfAttribTable 1 } 277 IntSrvIfAttribEntry ::= 278 SEQUENCE { 279 intSrvIfAttribAllocatedBits BitRate, 280 intSrvIfAttribMaxAllocatedBits BitRate, 281 intSrvIfAttribAllocatedBuffer BurstSize, 282 intSrvIfAttribFlows Gauge32, 283 intSrvIfAttribPropagationDelay Integer32, 284 intSrvIfAttribStatus RowStatus 285 } 287 intSrvIfAttribAllocatedBits OBJECT-TYPE 288 SYNTAX BitRate 289 UNITS "Bits per second" 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "The number of bits/second currently allocated 294 to reserved sessions on the interface." 295 ::= { intSrvIfAttribEntry 1 } 297 intSrvIfAttribMaxAllocatedBits OBJECT-TYPE 298 SYNTAX BitRate 299 UNITS "Bits per second" 300 MAX-ACCESS read-create 301 STATUS current 302 DESCRIPTION 303 "The maximum number of bits/second that may be 304 allocated to reserved sessions on the inter- 305 face." 306 ::= { intSrvIfAttribEntry 2 } 308 intSrvIfAttribAllocatedBuffer OBJECT-TYPE 309 SYNTAX BurstSize 310 UNITS "Bytes" 311 MAX-ACCESS read-only 312 STATUS current 313 DESCRIPTION 314 "The amount of buffer space required to hold 315 the simultaneous burst of all reserved flows on 316 the interface." 317 ::= { intSrvIfAttribEntry 3 } 319 intSrvIfAttribFlows OBJECT-TYPE 320 SYNTAX Gauge32 321 MAX-ACCESS read-only 322 STATUS current 323 DESCRIPTION 324 "The number of reserved flows currently active 325 on this interface. A flow can be created ei- 326 ther from a reservation protocol (such as RSVP 327 or ST-II) or via configuration information." 328 ::= { intSrvIfAttribEntry 4 } 330 intSrvIfAttribPropagationDelay OBJECT-TYPE 331 SYNTAX Integer32 332 UNITS "microseconds" 333 MAX-ACCESS read-create 334 STATUS current 335 DESCRIPTION 336 "The amount of propagation delay that this in- 337 terface introduces in addition to that intro- 338 diced by bit propagation delays." 339 DEFVAL { 0 }-- by default, interfaces are presumed to add no extra delays 340 ::= { intSrvIfAttribEntry 5 } 342 intSrvIfAttribStatus OBJECT-TYPE 343 SYNTAX RowStatus 344 MAX-ACCESS read-create 345 STATUS current 346 DESCRIPTION 347 "'active' on interfaces that are configured for 348 RSVP." 349 ::= { intSrvIfAttribEntry 6 } 351 -- The Integrated Services Active Flows Database 352 -- lists all flows active on an outgoing interface, including 353 -- relevant attributes. 355 intSrvFlowTable OBJECT-TYPE 356 SYNTAX SEQUENCE OF IntSrvFlowEntry 357 MAX-ACCESS not-accessible 358 STATUS current 359 DESCRIPTION 360 "Information describing the reserved flows us- 361 ing the system's interfaces." 362 ::= { intSrvObjects 2 } 364 intSrvFlowEntry OBJECT-TYPE 365 SYNTAX IntSrvFlowEntry 366 MAX-ACCESS not-accessible 367 STATUS current 368 DESCRIPTION 369 "Information describing the use of a given in- 370 terface by a given flow. The counter 371 intSrvFlowPoliced starts counting at the in- 372 stallation of the flow." 373 INDEX { intSrvFlowNumber } 374 ::= { intSrvFlowTable 1 } 376 IntSrvFlowEntry ::= 377 SEQUENCE { 378 intSrvFlowNumber SessionNumber, 379 intSrvFlowType SessionType, 380 intSrvFlowOwner INTEGER, 381 intSrvFlowDestAddr OCTET STRING, 382 intSrvFlowSenderAddr OCTET STRING, 383 intSrvFlowDestAddrLength INTEGER, 384 intSrvFlowSenderAddrLength INTEGER, 385 intSrvFlowProtocol Protocol, 386 intSrvFlowDestPort Port, 387 intSrvFlowPort Port, 388 intSrvFlowFlowId INTEGER, 389 intSrvFlowInterface InterfaceIndex, 390 intSrvFlowIfAddr OCTET STRING, 391 intSrvFlowRate BitRate, 392 intSrvFlowBurst BurstSize, 393 intSrvFlowWeight Integer32, 394 intSrvFlowQueue Integer32, 395 intSrvFlowMinTU MessageSize, 396 intSrvFlowMaxTU MessageSize, 397 intSrvFlowBestEffort Counter32, 398 intSrvFlowPoliced Counter32, 399 intSrvFlowDiscard TruthValue, 400 intSrvFlowService QosService, 401 intSrvFlowOrder INTEGER, 402 intSrvFlowStatus RowStatus 403 } 405 intSrvFlowNumber OBJECT-TYPE 406 SYNTAX SessionNumber 407 MAX-ACCESS not-accessible 408 STATUS current 409 DESCRIPTION 410 "The number of this flow. This is for SNMP In- 411 dexing purposes only and has no relation to any 412 protocol value." 413 ::= { intSrvFlowEntry 1 } 415 intSrvFlowType OBJECT-TYPE 416 SYNTAX SessionType 417 MAX-ACCESS read-create 418 STATUS current 419 DESCRIPTION 420 "The type of session (IP4, IP6, IP6 with flow 421 information, etc)." 422 ::= { intSrvFlowEntry 2 } 424 intSrvFlowOwner OBJECT-TYPE 425 SYNTAX INTEGER { 426 other(1), 427 rsvp(2), 428 management(3) 429 } 430 MAX-ACCESS read-create 431 STATUS current 432 DESCRIPTION 433 "The process that installed this flow in the 434 queue policy database." 435 ::= { intSrvFlowEntry 3 } 437 intSrvFlowDestAddr OBJECT-TYPE 438 SYNTAX OCTET STRING (SIZE(4..16)) 439 MAX-ACCESS read-create 440 STATUS current 441 DESCRIPTION 442 "The destination address used by all senders in 443 this session. This object may not be changed 444 when the value of the RowStatus object is 'ac- 445 tive'." 446 ::= { intSrvFlowEntry 4 } 448 intSrvFlowSenderAddr OBJECT-TYPE 449 SYNTAX OCTET STRING (SIZE(4..16)) 450 MAX-ACCESS read-create 451 STATUS current 452 DESCRIPTION 453 "The source address of the sender selected by 454 this reservation. The value of all zeroes in- 455 dicates 'all senders'. This object may not be 456 changed when the value of the RowStatus object 457 is 'active'." 458 ::= { intSrvFlowEntry 5 } 460 intSrvFlowDestAddrLength OBJECT-TYPE 461 SYNTAX INTEGER(0..128) 462 MAX-ACCESS read-create 463 STATUS current 464 DESCRIPTION 465 "The length of the destination address in bits. 466 This is the CIDR Prefix Length, which for IP4 467 hosts and multicast addresses is 32 bits. This 468 object may not be changed when the value of the 469 RowStatus object is 'active'." 470 ::= { intSrvFlowEntry 6 } 472 intSrvFlowSenderAddrLength OBJECT-TYPE 473 SYNTAX INTEGER(0..128) 474 MAX-ACCESS read-create 475 STATUS current 476 DESCRIPTION 477 "The length of the sender's address in bits. 478 This is the CIDR Prefix Length, which for IP4 479 hosts and multicast addresses is 32 bits. This 480 object may not be changed when the value of the 481 RowStatus object is 'active'." 482 ::= { intSrvFlowEntry 7 } 484 intSrvFlowProtocol OBJECT-TYPE 485 SYNTAX Protocol 486 MAX-ACCESS read-create 487 STATUS current 488 DESCRIPTION 489 "The IP Protocol used by a session. This ob- 490 ject may not be changed when the value of the 491 RowStatus object is 'active'." 492 ::= { intSrvFlowEntry 8 } 494 intSrvFlowDestPort OBJECT-TYPE 495 SYNTAX Port 496 MAX-ACCESS read-create 497 STATUS current 498 DESCRIPTION 499 "The UDP or TCP port number used as a destina- 500 tion port for all senders in this session. If 501 the IP protocol in use, specified by 502 intSrvResvFwdProtocol, is 50 (ESP) or 51 (AH), 503 this represents a virtual destination port 504 number. A value of zero indicates that the IP 505 protocol in use does not have ports. This ob- 506 ject may not be changed when the value of the 507 RowStatus object is 'active'." 508 ::= { intSrvFlowEntry 9 } 510 intSrvFlowPort OBJECT-TYPE 511 SYNTAX Port 512 MAX-ACCESS read-create 513 STATUS current 514 DESCRIPTION 515 "The UDP or TCP port number used as a source 516 port for this sender in this session. If the 517 IP protocol in use, specified by 518 intSrvResvFwdProtocol is 50 (ESP) or 51 (AH), 519 this represents a generalized port identifier 520 (GPI). A value of zero indicates that the IP 521 protocol in use does not have ports. This ob- 522 ject may not be changed when the value of the 523 RowStatus object is 'active'." 524 ::= { intSrvFlowEntry 10 } 526 intSrvFlowFlowId OBJECT-TYPE 527 SYNTAX INTEGER (0..16777215) 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "The flow ID that this sender is using, if 532 this is an IPv6 session." 533 ::= { intSrvFlowEntry 11 } 535 intSrvFlowInterface OBJECT-TYPE 536 SYNTAX InterfaceIndex 537 MAX-ACCESS read-create 538 STATUS current 539 DESCRIPTION 540 "The ifIndex value of the interface on which 541 this reservation exists." 542 ::= { intSrvFlowEntry 12 } 544 intSrvFlowIfAddr OBJECT-TYPE 545 SYNTAX OCTET STRING (SIZE(4..16)) 546 MAX-ACCESS read-create 547 STATUS current 548 DESCRIPTION 549 "The IP Address on the ifEntry on which this 550 reservation exists. This is present primarily 551 to support those interfaces which layer multi- 552 ple IP Addresses on the interface." 553 ::= { intSrvFlowEntry 13 } 555 intSrvFlowRate OBJECT-TYPE 556 SYNTAX BitRate 557 UNITS "bits per second" 558 MAX-ACCESS read-create 559 STATUS current 560 DESCRIPTION 561 "The Reserved Rate of the sender's data stream. 562 If this is a Controlled Load service flow, this 563 rate is derived from the Tspec rate parameter 564 (r). If this is a Guaranteed service flow, 565 this rate is derived from the Rspec clearing 566 rate parameter (R)." 567 ::= { intSrvFlowEntry 14 } 569 intSrvFlowBurst OBJECT-TYPE 570 SYNTAX BurstSize 571 UNITS "bytes" 572 MAX-ACCESS read-create 573 STATUS current 574 DESCRIPTION 575 "The size of the largest burst expected from 576 the sender at a time. 578 If this is less than the sender's advertised 579 burst size, the receiver is asking the network 580 to provide flow pacing beyond what would be 581 provided under normal circumstances. Such pac- 582 ing is at the network's option." 583 ::= { intSrvFlowEntry 15 } 585 intSrvFlowWeight OBJECT-TYPE 586 SYNTAX Integer32 587 MAX-ACCESS read-create 588 STATUS current 589 DESCRIPTION 590 "The weight used to prioritize the traffic. 591 Note that the interpretation of this object is 592 implementation-specific, as implementations 593 vary in their use of weighting procedures." 594 ::= { intSrvFlowEntry 16 } 596 intSrvFlowQueue OBJECT-TYPE 597 SYNTAX Integer32 598 MAX-ACCESS read-create 599 STATUS current 600 DESCRIPTION 601 "The number of the queue used by this traffic. 602 Note that the interpretation of this object is 603 implementation-specific, as implementations 604 vary in their use of queue identifiers." 605 ::= { intSrvFlowEntry 17 } 607 intSrvFlowMinTU OBJECT-TYPE 608 SYNTAX MessageSize 609 MAX-ACCESS read-create 610 STATUS current 611 DESCRIPTION 612 "The minimum message size for this flow. The 613 policing algorithm will treat smaller messages 614 as though they are this size." 615 ::= { intSrvFlowEntry 18 } 617 intSrvFlowMaxTU OBJECT-TYPE 618 SYNTAX MessageSize 619 MAX-ACCESS read-create 620 STATUS current 621 DESCRIPTION 622 "The maximum datagram size for this flow that 623 will conform to the traffic specification. This 624 value cannot exceed the MTU of the interface." 625 ::= { intSrvFlowEntry 19 } 627 intSrvFlowBestEffort OBJECT-TYPE 628 SYNTAX Counter32 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "The number of packets that were remanded to 633 best effort service." 634 ::= { intSrvFlowEntry 20 } 636 intSrvFlowPoliced OBJECT-TYPE 637 SYNTAX Counter32 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "The number of packets policed since the incep- 642 tion of the flow's service." 643 ::= { intSrvFlowEntry 21 } 645 intSrvFlowDiscard OBJECT-TYPE 646 SYNTAX TruthValue 647 MAX-ACCESS read-create 648 STATUS current 649 DESCRIPTION 650 "If 'true', the flow is to incur loss when 651 traffic is policed. If 'false', policed traff- 652 ic is treated as best effort traffic." 653 DEFVAL { false } -- traffic is, by default, treated as best effort 654 ::= { intSrvFlowEntry 22 } 656 intSrvFlowService OBJECT-TYPE 657 SYNTAX QosService 658 MAX-ACCESS read-only 659 STATUS current 660 DESCRIPTION 661 "The QoS service being applied to this flow." 662 ::= { intSrvFlowEntry 23 } 664 intSrvFlowOrder OBJECT-TYPE 665 SYNTAX INTEGER (0..65535) 666 MAX-ACCESS read-create 667 STATUS current 668 DESCRIPTION 669 "In the event of ambiguity, the order in which 670 the classifier should make its comparisons. 671 The row with intSrvFlowOrder=0 is tried first, 672 and comparisons proceed in the order of in- 673 creasing value. Non-serial implementations of 674 the classifier should emulate this behavior." 675 ::= { intSrvFlowEntry 24 } 677 intSrvFlowStatus OBJECT-TYPE 678 SYNTAX RowStatus 679 MAX-ACCESS read-create 680 STATUS current 681 DESCRIPTION 682 "'active' for all active flows. This object 683 may be used to install static classifier infor- 684 mation, delete classifier information, or au- 685 thorize such." 686 ::= { intSrvFlowEntry 25 } 688 intSrvFlowNewIndex OBJECT-TYPE 689 SYNTAX TestAndIncr 690 MAX-ACCESS read-write 691 STATUS current 692 DESCRIPTION 693 "This object is used to assign values to 694 intSrvFlowNumber as described in 'Textual Con- 695 ventions for SNMPv2'. The network manager 696 reads the object, and then writes the value 697 back in the SET that creates a new instance of 698 intSrvFlowEntry. If the SET fails with the 699 code 'inconsistentValue', then the process must 700 be repeated; If the SET succeeds, then the ob- 701 ject is incremented, and the new instance is 702 created according to the manager's directions." 703 ::= { intSrvGenObjects 1 } 705 -- conformance information 707 intSrvGroups OBJECT IDENTIFIER ::= { intSrvConformance 1 } 708 intSrvCompliances OBJECT IDENTIFIER ::= { intSrvConformance 2 } 710 -- compliance statements 711 intSrvCompliance MODULE-COMPLIANCE 712 STATUS current 713 DESCRIPTION 714 "The compliance statement " 715 MODULE -- this module 716 MANDATORY-GROUPS { intSrvIfAttribGroup, intSrvFlowsGroup, 717 intSrvGenObjectsGroup } 719 OBJECT intSrvFlowType 720 MIN-ACCESS read-only 721 DESCRIPTION 722 "read-create access is not required. This may be 723 read-only." 725 OBJECT intSrvFlowOwner 726 MIN-ACCESS read-only 727 DESCRIPTION 728 "read-create access is not required. This may be 729 read-only." 731 OBJECT intSrvFlowDestAddr 732 MIN-ACCESS read-only 733 DESCRIPTION 734 "read-create access is not required. This may be 735 read-only." 737 OBJECT intSrvFlowSenderAddr 738 MIN-ACCESS read-only 739 DESCRIPTION 740 "read-create access is not required. This may be 741 read-only." 743 OBJECT intSrvFlowDestAddrLength 744 MIN-ACCESS read-only 745 DESCRIPTION 746 "read-create access is not required. This may be 747 read-only." 749 OBJECT intSrvFlowSenderAddrLength 750 MIN-ACCESS read-only 751 DESCRIPTION 752 "read-create access is not required. This may be 753 read-only." 755 OBJECT intSrvFlowProtocol 756 MIN-ACCESS read-only 757 DESCRIPTION 758 "read-create access is not required. This may be 759 read-only." 761 OBJECT intSrvFlowDestPort 762 MIN-ACCESS read-only 763 DESCRIPTION 764 "read-create access is not required. This may be 765 read-only." 767 OBJECT intSrvFlowPort 768 MIN-ACCESS read-only 769 DESCRIPTION 770 "read-create access is not required. This may be 771 read-only." 773 OBJECT intSrvFlowFlowId 774 MIN-ACCESS not-accessible 775 DESCRIPTION 776 "This object is needed only in a system that imple- 777 ments IPv6." 779 OBJECT intSrvFlowInterface 780 MIN-ACCESS read-only 781 DESCRIPTION 782 "read-create access is not required. This may be 783 read-only." 785 OBJECT intSrvFlowRate 786 MIN-ACCESS read-only 787 DESCRIPTION 788 "read-create access is not required. This may be 789 read-only." 791 OBJECT intSrvFlowBurst 792 MIN-ACCESS read-only 793 DESCRIPTION 794 "read-create access is not required. This may be 795 read-only." 797 OBJECT intSrvFlowWeight 798 MIN-ACCESS read-only 799 DESCRIPTION 800 "read-create access is not required. This may be 801 read-only." 803 OBJECT intSrvFlowQueue 804 MIN-ACCESS read-only 805 DESCRIPTION 806 "read-create access is not required. This may be 807 read-only." 809 OBJECT intSrvFlowMinTU 810 MIN-ACCESS read-only 811 DESCRIPTION 812 "read-create access is not required. This may be 813 read-only." 815 OBJECT intSrvFlowMaxTU 816 MIN-ACCESS read-only 817 DESCRIPTION 818 "read-create access is not required. This may be 819 read-only." 821 OBJECT intSrvFlowStatus 822 MIN-ACCESS read-only 823 DESCRIPTION 824 "read-create access is not required. This may be 825 read-only." 827 ::= { intSrvCompliances 1 } 829 intSrvIfAttribGroup OBJECT-GROUP 830 OBJECTS { 831 intSrvIfAttribAllocatedBits, intSrvIfAttribMaxAllocatedBits, 832 intSrvIfAttribAllocatedBuffer, intSrvIfAttribFlows, 833 intSrvIfAttribPropagationDelay, intSrvIfAttribStatus 834 } 835 STATUS current 836 DESCRIPTION 837 "These objects are required for Systems sup- 838 porting the Integrated Services Architecture." 839 ::= { intSrvGroups 1 } 841 intSrvFlowsGroup OBJECT-GROUP 842 OBJECTS { 843 intSrvFlowType, intSrvFlowOwner, intSrvFlowDestAddr, 844 intSrvFlowSenderAddr, intSrvFlowDestAddrLength, 845 intSrvFlowSenderAddrLength, intSrvFlowProtocol, 846 intSrvFlowDestPort, intSrvFlowPort, intSrvFlowFlowId, 847 intSrvFlowInterface, intSrvFlowBestEffort, intSrvFlowRate, 848 intSrvFlowBurst, intSrvFlowWeight, intSrvFlowQueue, 849 intSrvFlowMinTU, intSrvFlowMaxTU, intSrvFlowDiscard, 850 intSrvFlowPoliced, intSrvFlowService, intSrvFlowIfAddr, 851 intSrvFlowOrder, intSrvFlowStatus 852 } 853 STATUS current 854 DESCRIPTION 855 "These objects are required for Systems sup- 856 porting the Integrated Services Architecture." 857 ::= { intSrvGroups 2 } 859 intSrvGenObjectsGroup OBJECT-GROUP 860 OBJECTS { 861 intSrvFlowNewIndex 862 } 863 STATUS current 864 DESCRIPTION 865 "These objects are required for Systems sup- 866 porting the Integrated Services Architecture." 867 ::= { intSrvGroups 3 } 869 END 870 6. Security Issues 872 The use of an SNMP SET results in an RSVP or Integrated 873 Services reservation under rules that are different compared 874 to if the reservation was negotiated using RSVP. However, no 875 other security considerations exist other than those imposed 876 by SNMP itself. 878 7. Authors' Addresses 880 Fred Baker 881 Postal: Cisco Systems 882 519 Lado Drive 883 Santa Barbara, California 93111 884 Tel: +1 805 681 0115 885 E-Mail: fred@cisco.com 887 John Krawczyk 888 Postal: ArrowPoint Communications 889 235 Littleton Road 890 Westford, Massachusetts 01886 891 Tel: +1 508 692 5875 892 E-Mail: jjk@tiac.net" 894 8. Acknowledgements 896 This document was produced by the Integrated Services Working 897 Group. 899 The authors would like to thank the following people for 900 providing feedback on this document: 902 Lou Berger, Fore Systems 903 Bob Braden, ISI 904 Viswanatha Rao, Compaq 905 John Wroclawski, MIT 906 9. References 908 [1] M.T. Rose (editor), Management Information Base for 909 Network Management of TCP/IP-based internets, Internet 910 Working Group Request for Comments 1213. Network 911 Information Center, SRI International, Menlo Park, 912 California, (May, 1990). 914 [2] Information processing systems - Open Systems 915 Interconnection - Specification of Abstract Syntax 916 Notation One (ASN.1), International Organization for 917 Standardization. International Standard 8824, (December, 918 1987). 920 [3] Information processing systems - Open Systems 921 Interconnection - Specification of Basic Encoding Rules 922 for Abstract Notation One (ASN.1), International 923 Organization for Standardization. International Standard 924 8825, (December, 1987). 926 Table of Contents 928 1 Status of this Memo ................................... 1 929 2 Abstract .............................................. 2 930 3 The SNMPv2 Network Management Framework ............... 3 931 3.1 Object Definitions .................................. 3 932 4 Overview .............................................. 3 933 4.1 Textual Conventions ................................. 3 934 4.2 Structure of MIB .................................... 4 935 5 Definitions ........................................... 5 936 5.2 Interface Attributes Database ....................... 8 937 5.3 Integrated Services Interface Flows Database ........ 11 938 6 Security Issues ....................................... 27 939 7 Authors' Addresses .................................... 27 940 8 Acknowledgements ...................................... 27 941 9 References ............................................ 28