idnits 2.17.1 draft-bush-rdrn-mib-00.txt: 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-03-28) 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard 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 43 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([3], [8], [9], [5,6], [10], [11], [12], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 279: '...acket radio link MUST have this object...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (January 13, 1997) is 9936 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: '2' is defined on line 1298, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 1306, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1319, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '6') ** Obsolete normative reference: RFC 1229 (ref. '7') (Obsoleted by RFC 1573) -- Possible downref: Non-RFC (?) normative reference: ref. '8' -- Possible downref: Non-RFC (?) normative reference: ref. '9' -- Possible downref: Non-RFC (?) normative reference: ref. '10' -- Possible downref: Non-RFC (?) normative reference: ref. '11' -- Possible downref: Non-RFC (?) normative reference: ref. '12' Summary: 14 errors (**), 0 flaws (~~), 4 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Stephen Bush 2 Expires in June 1997 Sunil Jagannath 3 ITTC 4 January 13, 1997 6 The Definition of Managed Objects for the Configuration of Mobile Wire- 7 less Beamformed GPS-Based Networks 9 Status of this Memo 11 This document is a submission by the Information and Telecommunica- 12 tions Technologies Center (ITTC) at the University of Kansas. Com- 13 ments should be submitted to sbush@tisl.ukans.edu. 15 Distribution of this memo is unlimited. 17 This document is an Internet-Draft. Internet-Drafts are working doc- 18 uments of the Internet Engineering Task Force (IETF), its areas, and 19 its working groups. Note that other groups may also distribute work- 20 ing documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet- Drafts as reference mate- 25 rial or to cite them other than as ``work in progress.'' 27 To learn the current status of any Internet-Draft, please check the 28 ``1id-abstracts.txt'' listing contained in the Internet- Drafts 29 Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 30 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 31 ftp.isi.edu (US West Coast). 33 Abstract 35 This memo defines a portion of the Management Information Base (MIB) 36 for use with network management protocols in TCP/IP-based internets. 37 In particular, it describes managed objects used for managing the 38 Rapidly Deployable Radio Network (RDRN) Network Control Protocol 39 (NCP). 41 The Network Management Framework 43 The Internet-standard Network Management Framework consists of three 44 components. They are: 46 STD 16/RFC 1155 which defines the SMI, the mechanisms used for 47 describing and naming objects for the purpose of management. STD 48 16/RFC 1212 defines a more concise description mechanism, which is 49 wholly consistent with the SMI. 51 STD 17/RFC 1213 which defines MIB-II, the core set of managed 52 objects for the Internet suite of protocols. 54 STD 15/RFC 1157 which defines the SNMP, the protocol used for net- 55 work access to managed objects. 57 The Framework permits new objects to be defined for the purpose of 58 experimentation and evaluation. 60 Objects 62 Managed objects are accessed via a virtual information store, termed 63 the Management Information Base or MIB. Objects in the MIB are 64 defined using the subset of Abstract Syntax Notation One (ASN.1) [3] 65 defined in the SMI. In particular, each object type is named by an 66 OBJECT IDENTIFIER, an administratively assigned name. The object 67 type together with an object instance serves to uniquely identify a 68 specific instantiation of the object. For human convenience, we 69 often use a textual string, termed the descriptor, to refer to the 70 object type. 72 Format of Definitions 74 Section 5 contains the specification of all object types contained in 75 this MIB module. The object types are defined using the conventions 76 defined in the SMI, as amended by the extensions specified in [5,6]. 78 Overview 80 Network Control Protocol Terminology 82 This section defines some of the terminology used in the Description 83 of the NCP operation. 85 o "AX.25" 87 Asynchronous X.25 Protocol (See [1]). 89 o "Callsign" 91 The packet radio callsign is assigned by the FCC and 92 identifies the packet radio operator. 94 o "Edge Switch" (ES) 96 A node which either resides within the wireless 97 network or at the edge of the fixed and 98 wireless network and which serves as a base station. 100 o "Global Positioning System" (GPS) 102 Satellite system which provides location and time. 104 o "Remote Node" (RN) 106 A host with the ability to connect via a beamforming 107 antenna to an edge switch (ES). 109 Rapidly Deployable Radio Network Control Protocol 111 The Rapidly Deployable Radio Network (RDRN) [8] and [9] consists of 112 links formed by beamforming antennas. While beamforming allows 113 improved spectrum usage through spatial reuse, it poses a challenge 114 to configure. Each mobile node and base station contains a GPS 115 receiver and is aware of its current location. This information is 116 shared among nodes and an optimal topology for beamformed links is 117 determined. The protocol which carries this information is known as 118 the network control protocol (NCP) [11]. The NCP is carried over an 119 omni-directional packet radio overlay network. See reference [12] for 120 information about Virtual Network Configuration (VNC) and NCP. 122 MIB Groups 124 The definition of managed objects for the NCP is divided into eleven 125 groups: 127 (1) Initialization Group 128 (2) Configuration Group 129 (3) NCP AX.25 Connection Group 130 (4) Edge Switch Group 131 (5) Remote Node Group 132 (6) GPS Specific Stats Group 133 (7) Packet Radio Specific Stats Group 134 (8) NCP Layer Specific Stats Group 135 (9) ATM Stacks Group 136 (10) Beam Coverage Group 137 (11) NCP Status Group 139 The initialization group objects pertain to the initial startup of 140 the NCP enhanced mobile node. The configuration group objects control 141 timing, encryption, and other configuration information for the NCP. 142 The NCP AX.25 [10] group objects maintains a mapping of packet radio 143 AX.25 streams to callsigns. This is useful for determining which 144 AX.25 packet radio connections are currently established. The Edge 145 Switch (ES) and Remote Node (RN) group objects manage information 146 need by the beamforming algorithm to properly steer beams. The GPS, 147 Packet Radio, and NCP Layer group objects manage GPS, NCP Packet 148 Radio, and NCP information. 150 The ATM Layer configuration objects are described in more detail in 151 the next section. 153 The Beam Coverage group objects provide access to information about 154 the currently active beams. Finally, the NCP Status group objects 155 pertain to timing information of interest to NCP. Virtual Network 156 Configuration (VNC) [11] is managed by a separate MIB. 158 ATM Configuration MIB Objects 160 The ATM Stacks group objects manage the currently active ATM stacks 161 on an ES or RN. As the orderwire network determines the topology of 162 all nodes in the wireless segment (e.g., RNs, ESs) in our architec- 163 ture, and establishes link connectivity among adjacent nodes, setup 164 is still required of the actual ATM circuits on which wireless ATM 165 are carried on the user data overlay network. This is accomplished by 166 providing standard ATM signaling capabilities to RNs and ESs and 167 using Classical IP over ATM to associate ATM VCs to IP addresses. The 168 Classical IP over ATM implementation provided works for PVCs and SVCs 169 (using ATMARP). 171 Since an ES may connect to multiple RNs (wireless connections) or ATM 172 switches (wired connections), it can be thought of as a software- 173 based ATM switch. In this sense, an ES features ATM PNNI signaling 174 while an RN features ATM UNI signaling. By default, an RN creates one 175 wireless-ATM protocol stack and establishes an ATM VC signaling chan- 176 nel on such a stack; however, the stack is initially in an inactive 177 state (i.e., non-operational mode) since there is no link connectiv- 178 ity to another node established yet. Likewise, an ES creates a pre- 179 defined number of wireless-ATM protocol stacks -- acting like ports 180 in an ATM switch -- and establishes ATM VC signaling channels on all 181 configured stacks which are also initialized as inactive. Wireless- 182 ATM protocol stacks are controlled by a daemon, called the adaptation 183 manager, which acts on behalf of the orderwire network. The adapta- 184 tion manager daemon not only controls the stacks by setting their 185 state to either active or inactive (default), but also may modify 186 configuration parameters of the stacks to provide dynamic adaptation 187 to link conditions. 189 Two possible scenarios illustrate the interactions between the order- 190 wire network and the wireless-ATM network. In the first scenario the 191 orderwire detects link connectivity between an adjacent pair of nodes 192 (e.g., RN-ES or ES-ES). In this case, the orderwire network requests 193 an inactive stack from the adaptation manager daemon at each end and 194 associates them with a designated address. Upon establishment of link 195 connectivity, a requested wireless stack has its state set to active 196 and is ready to operate. Note that since the signaling channels are 197 preconfigured on the stacks in question, users on the wireless estab- 198 lish end-to-end connections exactly as if they were connected in a 199 wired ATM network. 201 The other scenario occurs when the orderwire network detects a broken 202 connection, at the link level, between two connected nodes. This case 203 is typical of an RN moving away from the connectivity range of an ES. 204 The orderwire network thus contacts the adaptation manager daemon at 205 each end to set the wireless stacks in question to inactive. Since a 206 wireless stack is never destroyed, it can be reused in a future 207 request from the orderwire to establish connectivity to another pair 208 of nodes. 210 Definitions 211 RDRN-NCP-MIB DEFINITIONS ::= BEGIN 213 IMPORTS 214 MODULE-IDENTITY, OBJECT-TYPE, 215 enterprises, Counter32, Integer32, TimeTicks, Unsigned32 216 FROM SNMPv2-SMI 217 DisplayString, RowStatus, DateAndTime, TruthValue, TimeStamp, 218 TAddress 219 FROM SNMPv2-TC; 221 RdrnNcpMIB MODULE-IDENTITY 222 ORGANIZATION "KU TISL" 223 CONTACT-INFO 224 " Steve Bush 225 sbush@tisl.ukans.edu" 227 DESCRIPTION 228 "Experimental MIB modules for the Rapidly Deployable 229 Radio Networks (RDRN) Project Network Control 230 Protocol (NCP)." 231 ::= { 1 3 6 1 3 ncp(75) 1 } 233 ncp OBJECT IDENTIFIER ::= { ncp(75) 1 } 235 -- 236 -- NCP Initialization Group 237 -- 239 initialization OBJECT IDENTIFIER ::= { ncp 1 } 241 initContact OBJECT-TYPE 242 SYNTAX DisplayString 243 MAX-ACCESS read-only 244 STATUS current 245 DESCRIPTION 246 "NCP Agent Developer, but hopefully NOT maintainer." 247 ::= { initialization 1 } 249 initEntity OBJECT-TYPE 250 SYNTAX INTEGER { 251 edgeSwitch(0), 252 remoteNode(1) 253 } 254 MAX-ACCESS read-only 255 STATUS mandatory 256 DESCRIPTION 257 "Describes the RDRN node component." 259 ::= { initialization 2 } 261 initDebug OBJECT-TYPE 262 SYNTAX INTEGER 263 MAX-ACCESS read-write 264 STATUS mandatory 265 DESCRIPTION 266 "Logging level. Zero is off; the higher the number, the 267 more logging is enabled." 268 ::= { initialization 3 } 270 initEncrypt OBJECT-TYPE 271 SYNTAX INTEGER { 272 clear(0), 273 des(1) 274 } 275 MAX-ACCESS read-write 276 STATUS mandatory 277 DESCRIPTION 278 "Indicates whether data encryption used. Both endpoints 279 of a packet radio link MUST have this object set 280 identically for proper communication." 281 ::= { initialization 4 } 283 initVNC OBJECT-TYPE 284 SYNTAX INTEGER { 285 VNCEnabled(1), 286 Sequentional(0) 287 } 288 MAX-ACCESS read-only 289 STATUS mandatory 290 DESCRIPTION 291 "Indicates whether this system is running using 292 Virtual Network Configuration enhanced mode, 293 or sequential operation." 294 ::= { initialization 5 } 296 initStacks OBJECT-TYPE 297 SYNTAX INTEGER { 298 noStacks(1), 299 useStacks(0) 300 } 301 MAX-ACCESS read-write 302 STATUS mandatory 303 DESCRIPTION 304 "Indicates whether link level stacks will be created. 305 Primarily used for testing purposes." 306 ::= { initialization 6 } 308 initRadioPort OBJECT-TYPE 309 SYNTAX DisplayString 310 MAX-ACCESS read-only 311 STATUS mandatory 312 DESCRIPTION 313 "Indicates the packet radio tty port." 314 ::= { initialization 7 } 316 initGpsPort OBJECT-TYPE 317 SYNTAX DisplayString 318 MAX-ACCESS read-only 319 STATUS mandatory 320 DESCRIPTION 321 "Indicates the GPS tty port." 322 ::= { initialization 8 } 324 initSpeed OBJECT-TYPE 325 SYNTAX DisplayString 326 MAX-ACCESS read-only 327 STATUS mandatory 328 DESCRIPTION 329 "Indicates the assumed initial speed. Primarily used 330 for simulated GPS." 331 ::= { initialization 9 } 333 initDirection OBJECT-TYPE 334 SYNTAX DisplayString 335 MAX-ACCESS read-only 336 STATUS mandatory 337 DESCRIPTION 338 "Indicates the assumed initial direction. Primarily 339 used for simulated GPS." 340 ::= { initialization 10 } 342 initXPos OBJECT-TYPE 343 SYNTAX DisplayString 344 MAX-ACCESS read-only 345 STATUS mandatory 346 DESCRIPTION 347 "Indicates the assumed initial X axis position. 348 Primarily used for simulated GPS." 349 ::= { initialization 11 } 351 initYPos OBJECT-TYPE 352 SYNTAX DisplayString 353 MAX-ACCESS read-only 354 STATUS mandatory 355 DESCRIPTION 356 "Indicates the assumed initial Y axis position. 357 Primarily used for simulated GPS." 358 ::= { initialization 12 } 360 initSimGps OBJECT-TYPE 361 SYNTAX INTEGER { 362 gpsReceiver(0), 363 gpsSimulator(1) 364 } 365 MAX-ACCESS read-write 366 STATUS mandatory 367 DESCRIPTION 368 "Indicates whether the GPS receiver is being read 369 or the GPS simulation code is being used. This 370 value can be set while running without harm. 371 Changing from gpsReceiver to gpsSimulator will 372 cause a smooth transition based on last known 373 direction and speed. Transitioning from gps Simulator 374 to gpsReceiver may cause a large jump in position." 375 ::= { initialization 13 } 377 initTcpEmulation OBJECT-TYPE 378 SYNTAX INTEGER { 379 packetRadio(2), 380 tcpEmulation(1), 381 packetRadio_and_tcpEmulation(3) 382 } 383 MAX-ACCESS read-only 384 STATUS mandatory 385 DESCRIPTION 386 "Indicates whether packet radios or TCP-IP simulation 387 of packet radios is currently in use. This value 388 cannot be set because the tcp emulation requires 389 knowledge of ip addresses of all hosts in the 390 simulated RDRN system and all though this could be 391 set on the fly through a MIB table, I don't feel 392 it's worth the effort to develop at this point." 393 ::= { initialization 14 } 395 -- 396 -- NCP Configuration Group 397 -- 399 configuration OBJECT IDENTIFIER ::= { ncp 2 } 401 configTimeout OBJECT-TYPE 402 SYNTAX INTEGER 403 MAX-ACCESS read-write 404 STATUS mandatory 405 DESCRIPTION 406 "Indicates the timeout during edge switch 407 reconfiguration. Should be set long enough 408 for all edge switches to respond." 409 ::= { configuration 1 } 411 configMaxVel OBJECT-TYPE 412 SYNTAX DisplayString 413 MAX-ACCESS read-write 414 STATUS mandatory 415 DESCRIPTION 416 "Indicates the maximum of a uniformly distributed 417 velocity for simulated GPS operation." 418 ::= { configuration 2 } 420 configSpeed OBJECT-TYPE 421 SYNTAX DisplayString 422 MAX-ACCESS read-write 423 STATUS mandatory 424 DESCRIPTION 425 "Indicates the initial speed for simulated GPS operation. 426 Same as initSpeed for historical reasons, e.g. this one 427 set through a file while the other is set via arguments." 428 ::= { configuration 3 } 430 configDirection OBJECT-TYPE 431 SYNTAX DisplayString 432 MAX-ACCESS read-write 433 STATUS mandatory 434 DESCRIPTION 435 "Indicates the initial direction in degrees for simulated 436 GPS operation. Same as initDirection for historical 437 reasons. This one is read from a file while the other 438 is set as a program argument during startup." 439 ::= { configuration 4 } 441 configUseRealTopology OBJECT-TYPE 442 SYNTAX INTEGER 443 MAX-ACCESS read-write 444 STATUS mandatory 445 DESCRIPTION 446 "Indicates whether edge switch topology code is called. 447 Currently this code uses MatLab and can be quite slow." 448 ::= { configuration 5 } 450 configCallsign OBJECT-TYPE 451 SYNTAX DisplayString 452 MAX-ACCESS read-only 453 STATUS mandatory 454 DESCRIPTION 455 "Indicates this nodes packet radio callsign." 456 ::= { configuration 6 } 458 configKey OBJECT-TYPE 459 SYNTAX DisplayString 460 MAX-ACCESS read-only 461 STATUS mandatory 462 DESCRIPTION 463 "Indicates the current DES key. Probably not secure to 464 put this here, but useful for debugging." 465 ::= { configuration 7 } 467 configUserSwitch OBJECT-TYPE 468 SYNTAX DisplayString 469 MAX-ACCESS read-only 470 STATUS mandatory 471 DESCRIPTION 472 "If this is a remote node, this is the associated edge 473 switch." 474 ::= { configuration 8 } 476 configUpdatePeriod OBJECT-TYPE 477 SYNTAX INTEGER 478 MAX-ACCESS read-write 479 STATUS mandatory 480 DESCRIPTION 481 "Indicates the remote node's user position update rate." 482 ::= { configuration 9 } 484 configDistanceTolerance OBJECT-TYPE 485 SYNTAX INTEGER 486 MAX-ACCESS read-write 487 STATUS mandatory 488 DESCRIPTION 489 "Indicates the amount of movement allowed before 490 beam angles must be recomputed." 491 ::= { configuration 10 } 493 configAntennaAngle OBJECT-TYPE 494 SYNTAX INTEGER 495 MAX-ACCESS read-write 496 STATUS mandatory 497 DESCRIPTION 498 "Indicates the direction of the physical position 499 of the linear array from pointing North." 501 ::= { configuration 11 } 503 -- 504 -- Current NCP AX.25 Connection Group 505 -- 507 radioStreams OBJECT IDENTIFIER ::= { ncp 3 } 509 radioStreamsTable OBJECT-TYPE 510 SYNTAX SEQUENCE OF RadioStreamsEntry 511 ACCESS read-only 512 STATUS mandatory 513 DESCRIPTION 514 "Table of packet currently established packet 515 radio streams and callsigns." 516 ::= { radioStreams 1 } 518 radioStreamsEntry OBJECT-TYPE 519 SYNTAX RadioStreamsEntry 520 ACCESS read-only 521 STATUS mandatory 522 ::= { radioStreamsTable 1 } 524 RadioStreamsEntry ::= SEQUENCE { 525 radioStreamsID 526 DisplayString, 527 radioStreamsCallsign 528 DisplayString 529 } 531 radioStreamsID OBJECT-TYPE 532 SYNTAX DisplayString 533 ACCESS read-only 534 STATUS mandatory 535 DESCRIPTION 536 "The Packet Radio stream identifier for this 537 ARQ AX.25 connection." 538 ::= { radioStreamsEntry 1 } 540 radioStreamsCallsign OBJECT-TYPE 541 SYNTAX DisplayString 542 ACCESS read-only 543 STATUS mandatory 544 DESCRIPTION 545 "This is the callsign of the packet radio with 546 the associated stream identifier." 547 ::= { radioStreamsEntry 2 } 549 -- 550 -- Known Edge Switch Group 551 -- 553 edgeSwitchNetwork OBJECT IDENTIFIER ::= { ncp 4 } 555 edgeSwitchTable OBJECT-TYPE 556 SYNTAX SEQUENCE OF EdgeSwitchEntry 557 ACCESS read-only 558 STATUS mandatory 559 DESCRIPTION 560 "Table of RDRN edge switches known by this edge switch." 561 ::= { edgeSwitchNetwork 1 } 563 edgeSwitchEntry OBJECT-TYPE 564 SYNTAX EdgeSwitchEntry 565 ACCESS read-only 566 STATUS mandatory 567 ::= { edgeSwitchTable 1 } 569 EdgeSwitchEntry ::= SEQUENCE { 570 edgeSwitchCallsign 571 DisplayString, 572 edgeSwitchHostname 573 DisplayString, 574 edgeSwitchATMAddr 575 DisplayString, 576 edgeSwitchLatDeg 577 DisplayString, 578 edgeSwitchLatMin 579 DisplayString, 580 edgeSwitchLatDir 581 DisplayString, 582 edgeSwitchLonDeg 583 DisplayString, 584 edgeSwitchLonMin 585 DisplayString, 586 edgeSwitchLonDir 587 DisplayString, 588 edgeSwitchXPos 589 DisplayString, 590 edgeSwitchYPos 591 DisplayString, 592 edgeSwitchSpeed 593 DisplayString, 594 edgeSwitchDir 595 DisplayString, 596 edgeSwitchAvaliability 597 INTEGER, 598 edgeSwitchNSat 599 INTEGER, 600 edgeSwitchHDop 601 INTEGER, 602 edgeSwitchElevation 603 DisplayString, 604 edgeSwitchHeight 605 DisplayString, 606 edgeSwitchIndex 607 DisplayString, 608 edgeSwitchTime 609 TimeTicks 610 } 612 edgeSwitchCallsign OBJECT-TYPE 613 SYNTAX DisplayString 614 ACCESS read-only 615 STATUS mandatory 616 DESCRIPTION 617 "Edge Switch Callsign." 618 ::= { edgeSwitchEntry 1 } 620 edgeSwitchHostname OBJECT-TYPE 621 SYNTAX DisplayString 622 ACCESS read-only 623 STATUS mandatory 624 DESCRIPTION 625 "Edge Switch IP Hostname." 626 ::= { edgeSwitchEntry 2 } 628 edgeSwitchATMAddr OBJECT-TYPE 629 SYNTAX DisplayString 630 ACCESS read-only 631 STATUS mandatory 632 DESCRIPTION 633 "Edge Switch ATM Address." 634 ::= { edgeSwitchEntry 3 } 636 edgeSwitchLatDeg OBJECT-TYPE 637 SYNTAX DisplayString 638 ACCESS read-only 639 STATUS mandatory 640 DESCRIPTION 641 "Edge Switch Latitude - degrees." 642 ::= { edgeSwitchEntry 4 } 644 edgeSwitchLatMin OBJECT-TYPE 645 SYNTAX DisplayString 646 ACCESS read-only 647 STATUS mandatory 648 DESCRIPTION 649 "Edge Switch Latitude - minutes." 650 ::= { edgeSwitchEntry 5 } 652 edgeSwitchLatDir OBJECT-TYPE 653 SYNTAX DisplayString 654 ACCESS read-only 655 STATUS mandatory 656 DESCRIPTION 657 "Edge Switch Latitude Hemisphere." 658 ::= { edgeSwitchEntry 6 } 660 edgeSwitchLonDeg OBJECT-TYPE 661 SYNTAX DisplayString 662 ACCESS read-only 663 STATUS mandatory 664 DESCRIPTION 665 "Edge Switch Longitude - degrees." 666 ::= { edgeSwitchEntry 7 } 668 edgeSwitchLonMin OBJECT-TYPE 669 SYNTAX DisplayString 670 ACCESS read-only 671 STATUS mandatory 672 DESCRIPTION 673 "Edge Switch Longitude - minutes." 674 ::= { edgeSwitchEntry 8 } 676 edgeSwitchLonDir OBJECT-TYPE 677 SYNTAX DisplayString 678 ACCESS read-only 679 STATUS mandatory 680 DESCRIPTION 681 "Edge Switch Longitude - Hemisphere." 682 ::= { edgeSwitchEntry 9 } 684 edgeSwitchXPos OBJECT-TYPE 685 SYNTAX DisplayString 686 ACCESS read-only 687 STATUS mandatory 688 DESCRIPTION 689 "Edge Switch Cartesian X Coordinate. Units are 690 meters." 691 ::= { edgeSwitchEntry 10 } 693 edgeSwitchYPos OBJECT-TYPE 694 SYNTAX DisplayString 695 ACCESS read-only 696 STATUS mandatory 697 DESCRIPTION 698 "Edge Switch Cartesian Y Coordinate. Units are 699 meters." 700 ::= { edgeSwitchEntry 11 } 702 edgeSwitchSpeed OBJECT-TYPE 703 SYNTAX DisplayString 704 ACCESS read-only 705 STATUS mandatory 706 DESCRIPTION 707 "Edge Switch current speed." 708 ::= { edgeSwitchEntry 12 } 710 edgeSwitchDir OBJECT-TYPE 711 SYNTAX DisplayString 712 ACCESS read-only 713 STATUS mandatory 714 DESCRIPTION 715 "Edge Switch current direction in degrees 716 0 degrees is North." 717 ::= { edgeSwitchEntry 13 } 719 edgeSwitchAvaliability OBJECT-TYPE 720 SYNTAX INTEGER 721 ACCESS read-only 722 STATUS mandatory 723 DESCRIPTION 724 "Edge Switch GPS quality information. 725 0 - fix not available 726 1 - Non differential GPS fix available 727 2 - Differential GPS fix available." 728 ::= { edgeSwitchEntry 14 } 730 edgeSwitchNSat OBJECT-TYPE 731 SYNTAX INTEGER 732 ACCESS read-only 733 STATUS mandatory 734 DESCRIPTION 735 "Edge Switch GPS number of satellites in use. 736 From 0 to 8 satellites." 737 ::= { edgeSwitchEntry 15 } 739 edgeSwitchHDop OBJECT-TYPE 740 SYNTAX INTEGER 741 ACCESS read-only 742 STATUS mandatory 743 DESCRIPTION 744 "Edge Switch GPS horizontal dilution of position. 745 Varies from 1.0 to 99.9." 746 ::= { edgeSwitchEntry 16 } 748 edgeSwitchElevation OBJECT-TYPE 749 SYNTAX DisplayString 750 ACCESS read-only 751 STATUS mandatory 752 DESCRIPTION 753 "Edge Switch current height with respect to sea 754 level in meters." 755 ::= { edgeSwitchEntry 17 } 757 edgeSwitchHeight OBJECT-TYPE 758 SYNTAX DisplayString 759 ACCESS read-only 760 STATUS mandatory 761 DESCRIPTION 762 "Edge Switch current geoidal height in meters." 763 ::= { edgeSwitchEntry 18 } 765 edgeSwitchIndex OBJECT-TYPE 766 SYNTAX DisplayString 767 ACCESS read-only 768 STATUS mandatory 769 DESCRIPTION 770 "Internal index for use in ES/RN associations." 771 ::= { edgeSwitchEntry 19 } 773 edgeSwitchTime OBJECT-TYPE 774 SYNTAX TimeTicks 775 ACCESS read-only 776 STATUS mandatory 777 DESCRIPTION 778 "GPS time at which this information was valid." 779 ::= { edgeSwitchEntry 20 } 781 -- 782 -- Associated Remote Nodes Group 783 -- 785 remoteNodeNetwork OBJECT IDENTIFIER ::= { ncp 5 } 787 remoteNodeTable OBJECT-TYPE 788 SYNTAX SEQUENCE OF RemoteNodeEntry 789 ACCESS read-only 790 STATUS mandatory 791 DESCRIPTION 792 "Table of RDRN remote nodes known by this edge switch." 793 ::= { remoteNodeNetwork 1 } 795 remoteNodeEntry OBJECT-TYPE 796 SYNTAX EdgeSwitchEntry 797 ACCESS read-only 798 STATUS mandatory 799 ::= { remoteNodeTable 1 } 801 RemoteNodeEntry ::= SEQUENCE { 802 remoteNodeCallsign 803 DisplayString, 804 remoteNodeHostname 805 DisplayString, 806 remoteNodeATMAddr 807 DisplayString, 808 remoteNodeLatDeg 809 DisplayString, 810 remoteNodeLatMin 811 DisplayString, 812 remoteNodeLatDir 813 DisplayString, 814 remoteNodeLonDeg 815 DisplayString, 816 remoteNodeLonMin 817 DisplayString, 818 remoteNodeLonDir 819 DisplayString, 820 remoteNodeXPos 821 DisplayString, 822 remoteNodeYPos 823 DisplayString, 824 remoteNodeSpeed 825 DisplayString, 826 remoteNodeDir 827 DisplayString, 828 remoteNodeAvaliability 829 INTEGER, 830 remoteNodeNSat 831 INTEGER, 832 remoteNodeHDop 833 INTEGER, 834 remoteNodeElevation 835 DisplayString, 836 remoteNodeHeight 837 DisplayString, 838 remoteNodeIndex 839 DisplayString, 840 remoteNodeTime 841 TimeTicks, 842 remoteNodeDistance 843 DisplayString 844 } 846 remoteNodeCallsign OBJECT-TYPE 847 SYNTAX DisplayString 848 ACCESS read-only 849 STATUS mandatory 850 DESCRIPTION 851 "Remote Node Callsign." 852 ::= { remoteNodeEntry 1 } 854 remoteNodeHostname OBJECT-TYPE 855 SYNTAX DisplayString 856 ACCESS read-only 857 STATUS mandatory 858 DESCRIPTION 859 "Remote Node IP hostname." 860 ::= { remoteNodeEntry 2 } 862 remoteNodeATMAddr OBJECT-TYPE 863 SYNTAX DisplayString 864 ACCESS read-only 865 STATUS mandatory 866 DESCRIPTION 867 "Remote Node ATM Address." 868 ::= { remoteNodeEntry 3 } 870 remoteNodeLatDeg OBJECT-TYPE 871 SYNTAX DisplayString 872 ACCESS read-only 873 STATUS mandatory 874 DESCRIPTION 875 "Remote Node Latitude - degrees." 876 ::= { remoteNodeEntry 4 } 878 remoteNodeLatMin OBJECT-TYPE 879 SYNTAX DisplayString 880 ACCESS read-only 881 STATUS mandatory 882 DESCRIPTION 883 "Remote Node Latitude - minutes." 884 ::= { remoteNodeEntry 5 } 886 remoteNodeLatDir OBJECT-TYPE 887 SYNTAX DisplayString 888 ACCESS read-only 889 STATUS mandatory 890 DESCRIPTION 891 "Remote Node Latitude Hemisphere." 892 ::= { remoteNodeEntry 6 } 894 remoteNodeLonDeg OBJECT-TYPE 895 SYNTAX DisplayString 896 ACCESS read-only 897 STATUS mandatory 898 DESCRIPTION 899 "Remote Node Longitude - degrees." 900 ::= { remoteNodeEntry 7 } 902 remoteNodeLonMin OBJECT-TYPE 903 SYNTAX DisplayString 904 ACCESS read-only 905 STATUS mandatory 906 DESCRIPTION 907 "Remote Node Longitude - minutes." 908 ::= { remoteNodeEntry 8 } 910 remoteNodeLonDir OBJECT-TYPE 911 SYNTAX DisplayString 912 ACCESS read-only 913 STATUS mandatory 914 DESCRIPTION 915 "Remote Node Longitude - Hemisphere." 916 ::= { remoteNodeEntry 9 } 918 remoteNodeXPos OBJECT-TYPE 919 SYNTAX DisplayString 920 ACCESS read-only 921 STATUS mandatory 922 DESCRIPTION 923 "Remote Node Cartesian X Coordinate. Units are 924 meters." 925 ::= { remoteNodeEntry 10 } 927 remoteNodeYPos OBJECT-TYPE 928 SYNTAX DisplayString 929 ACCESS read-only 930 STATUS mandatory 931 DESCRIPTION 932 "Remote Node Cartesian Y Coordinate. Units are 933 meters." 935 ::= { remoteNodeEntry 11 } 937 remoteNodeSpeed OBJECT-TYPE 938 SYNTAX DisplayString 939 ACCESS read-only 940 STATUS mandatory 941 DESCRIPTION 942 "Remote Node current speed." 943 ::= { remoteNodeEntry 12 } 945 remoteNodeDir OBJECT-TYPE 946 SYNTAX DisplayString 947 ACCESS read-only 948 STATUS mandatory 949 DESCRIPTION 950 "Remote Node current direction in degrees 951 0 degrees is North." 952 ::= { remoteNodeEntry 13 } 954 remoteNodeAvaliability OBJECT-TYPE 955 SYNTAX INTEGER 956 ACCESS read-only 957 STATUS mandatory 958 DESCRIPTION 959 "Remote Node GPS quality information. 960 0 - fix not available 961 1 - Non differential GPS fix available 962 2 - Differential GPS fix available." 963 ::= { remoteNodeEntry 14 } 965 remoteNodeNSat OBJECT-TYPE 966 SYNTAX INTEGER 967 ACCESS read-only 968 STATUS mandatory 969 DESCRIPTION 970 "Remote Node GPS number of satellites in use. 971 From 0 to 8 satellites." 972 ::= { remoteNodeEntry 15 } 974 remoteNodeHDop OBJECT-TYPE 975 SYNTAX INTEGER 976 ACCESS read-only 977 STATUS mandatory 978 DESCRIPTION 979 "Remote Node GPS horizontal dilution of position. 980 Varies from 1.0 to 99.9." 981 ::= { remoteNodeEntry 16 } 983 remoteNodeElevation OBJECT-TYPE 984 SYNTAX DisplayString 985 ACCESS read-only 986 STATUS mandatory 987 DESCRIPTION 988 "Remote Node current height with respect to sea 989 level in meters." 990 ::= { remoteNodeEntry 17 } 992 remoteNodeHeight OBJECT-TYPE 993 SYNTAX DisplayString 994 ACCESS read-only 995 STATUS mandatory 996 DESCRIPTION 997 "Remote Node current geoidal height in meters." 998 ::= { remoteNodeEntry 18 } 1000 remoteNodeIndex OBJECT-TYPE 1001 SYNTAX DisplayString 1002 ACCESS read-only 1003 STATUS mandatory 1004 DESCRIPTION 1005 "Internal index for use in ES/RN associations." 1006 ::= { remoteNodeEntry 19 } 1008 remoteNodeTime OBJECT-TYPE 1009 SYNTAX TimeTicks 1010 ACCESS read-only 1011 STATUS mandatory 1012 DESCRIPTION 1013 "GPS time at which this information was valid." 1014 ::= { remoteNodeEntry 20 } 1016 remoteNodeDistance OBJECT-TYPE 1017 SYNTAX DisplayString 1018 ACCESS read-only 1019 STATUS mandatory 1020 DESCRIPTION 1021 "Distance of this remote node from its associated 1022 base station. A value of 0.0 means that no base 1023 station has been associated yet." 1024 ::= { remoteNodeEntry 21 } 1026 -- 1027 -- GPS Specific Stats Group 1028 -- 1030 gps OBJECT IDENTIFIER ::= { ncp 6 } 1031 gpsPosRead OBJECT-TYPE 1032 SYNTAX Counter 1033 ACCESS read-only 1034 STATUS mandatory 1035 DESCRIPTION 1036 "The total number of GPS position records that have 1037 been read since initialization." 1038 ::= { gps 1 } 1040 -- 1041 -- Packet Radio Specific Stats Group 1042 -- 1044 packetRadio OBJECT IDENTIFIER ::= { ncp 7 } 1046 packetsIn OBJECT-TYPE 1047 SYNTAX Counter 1048 ACCESS read-only 1049 STATUS mandatory 1050 DESCRIPTION 1051 "The total number of NCP packets which have 1052 been read since initialization." 1053 ::= { packetRadio 1 } 1055 packetsOut OBJECT-TYPE 1056 SYNTAX Counter 1057 ACCESS read-only 1058 STATUS mandatory 1059 DESCRIPTION 1060 "The total number of NCP packets which have 1061 been written to the packet radio since initialization." 1062 ::= { packetRadio 2 } 1064 packetsBad OBJECT-TYPE 1065 SYNTAX Counter 1066 ACCESS read-only 1067 STATUS mandatory 1068 DESCRIPTION 1069 "The total number of NCP packets which have 1070 been read and discarded as unreadable or incomplete 1071 since initialization." 1072 ::= { packetRadio 3 } 1074 -- 1075 -- NCP Level Specific Stats Group 1076 -- 1078 ncpLevel OBJECT IDENTIFIER ::= { ncp 8 } 1079 ncpHandoffs OBJECT-TYPE 1080 SYNTAX Counter 1081 ACCESS read-only 1082 STATUS mandatory 1083 DESCRIPTION 1084 "The total number handoffs since since initialization." 1085 ::= { ncpLevel 1 } 1087 -- 1088 -- Existing ATM Stacks Group 1089 -- 1091 atmStacks OBJECT IDENTIFIER ::= { ncp 9 } 1093 atmStacksTable OBJECT-TYPE 1094 SYNTAX SEQUENCE OF AtmStacksEntry 1095 ACCESS read-only 1096 STATUS mandatory 1097 ::= { atmStacks 1 } 1099 atmStacksEntry OBJECT-TYPE 1100 SYNTAX AtmStacksEntry 1101 ACCESS read-only 1102 STATUS mandatory 1103 DESCRIPTION 1104 "Table of currently active AHDLC stacks." 1105 ::= { atmStacksTable 1 } 1107 AtmStacksEntry ::= SEQUENCE { 1108 atmStacksBeam 1109 INTEGER, 1110 atmStacksSlot 1111 INTEGER, 1112 atmStacksATMaddr 1113 DisplayString, 1114 atmStacksAhdlcState 1115 INTEGER 1116 } 1118 atmStacksBeam OBJECT-TYPE 1119 SYNTAX INTEGER 1120 ACCESS read-only 1121 STATUS mandatory 1122 DESCRIPTION 1123 "The beam number for this AHDLC stack." 1124 ::= { atmStacksEntry 1 } 1126 atmStacksSlot OBJECT-TYPE 1127 SYNTAX INTEGER 1128 ACCESS read-only 1129 STATUS mandatory 1130 DESCRIPTION 1131 "The slot number for this AHDLC stack." 1132 ::= { atmStacksEntry 2 } 1134 atmStacksATMaddr OBJECT-TYPE 1135 SYNTAX DisplayString 1136 ACCESS read-only 1137 STATUS mandatory 1138 DESCRIPTION 1139 "The ATM address of the current AHDLC stack." 1140 ::= { atmStacksEntry 3 } 1142 atmStacksAhdlcState OBJECT-TYPE 1143 SYNTAX INTEGER { 1144 down(0), 1145 up(1) 1146 } 1147 MAX-ACCESS read-only 1148 STATUS mandatory 1149 DESCRIPTION 1150 "This is the state of the AHDLC layer." 1151 ::= { atmStacksEntry 4 } 1153 -- 1154 -- The Beam Coverage Group 1155 -- 1157 beamCoverage OBJECT IDENTIFIER ::= { ncp 10 } 1159 beamCovTable OBJECT-TYPE 1160 SYNTAX SEQUENCE OF BeamCovEntry 1161 ACCESS read-only 1162 STATUS mandatory 1163 DESCRIPTION 1164 "Table of beam coverage information." 1165 ::= { beamCoverage 1 } 1167 beamCovEntry OBJECT-TYPE 1168 SYNTAX BeamCovEntry 1169 ACCESS read-only 1170 STATUS mandatory 1171 ::= { beamCovTable 1 } 1173 BeamCovEntry ::= SEQUENCE { 1174 beamCovAngle 1175 DisplayString, 1176 beamCovPower 1177 DisplayString, 1178 beamCovSIR 1179 DisplayString 1180 } 1182 beamCovAngle OBJECT-TYPE 1183 SYNTAX DisplayString 1184 ACCESS read-only 1185 STATUS mandatory 1186 DESCRIPTION 1187 "The beam angle of this beam." 1188 ::= { beamCovEntry 1 } 1190 beamCovPower OBJECT-TYPE 1191 SYNTAX DisplayString 1192 ACCESS read-only 1193 STATUS mandatory 1194 DESCRIPTION 1195 "The power level of this beam." 1196 ::= { beamCovEntry 2 } 1198 beamCovSIR OBJECT-TYPE 1199 SYNTAX DisplayString 1200 ACCESS read-only 1201 STATUS mandatory 1202 DESCRIPTION 1203 "The signal to interference ratio for this beam." 1204 ::= { beamCovEntry 3 } 1206 -- 1207 -- The NCP Status Group 1208 -- 1210 status OBJECT IDENTIFIER ::= { ncp 11 } 1212 statState OBJECT-TYPE 1213 SYNTAX INTEGER { 1214 down(0), 1215 configuring(1), 1216 associating(2), 1217 active(3), 1218 delay(4) 1219 } 1220 MAX-ACCESS read-only 1221 STATUS mandatory 1222 DESCRIPTION 1223 "Describes the NCP state of operation: 1224 down - node administratively idle. 1225 configuring - es-es topology configuration or 1226 initial startup. 1227 associating - handoff in process. 1228 active - other normal operation. 1229 delay - node is in a delay mode, e.g. 1230 remote node waiting between 1231 updates." 1232 ::= { status 1 } 1234 statAdminState OBJECT-TYPE 1235 SYNTAX INTEGER { 1236 idle(0), 1237 active(1) 1238 } 1239 MAX-ACCESS read-write 1240 STATUS mandatory 1241 DESCRIPTION 1242 "Indicates whether the process is in an idle mode 1243 or active. Setting this object to idle causes the 1244 NCP process to remain alive, but stop processing 1245 packets. A transition setting from idle to active 1246 causes the NCP process to re-initialize as though 1247 just started." 1248 ::= { status 2 } 1250 statTopologyTime OBJECT-TYPE 1251 SYNTAX INTEGER 1252 MAX-ACCESS read-only 1253 STATUS mandatory 1254 DESCRIPTION 1255 "The time in micro-seconds to do the last optimal 1256 topology calculation. A zero value means that 1257 the topology calculation has not been performed 1258 yet." 1259 ::= { status 3 } 1261 statBeamformTime OBJECT-TYPE 1262 SYNTAX INTEGER 1263 MAX-ACCESS read-only 1264 STATUS mandatory 1265 DESCRIPTION 1266 "The time in micro-seconds to do the last beamform. 1267 A zero values indicates that beamforming has not 1268 been performed yet." 1269 ::= { status 4 } 1271 statNcpTransferTime OBJECT-TYPE 1272 SYNTAX INTEGER 1273 MAX-ACCESS read-only 1274 STATUS mandatory 1275 DESCRIPTION 1276 "The time in micro-seconds of the last NCP packet 1277 transmission. A zero value means that no packet 1278 measurements are being taken." 1279 ::= { status 5 } 1281 END 1283 Security Considerations 1285 Clearly, the DES encryption key should not be accessible in the MIB, 1286 however, this remains in the MIB for debugging and testing purposes. 1287 Also, critical timing parameters are set-able from this MIB. Again 1288 this is useful for experimental purposes, but may not be desired for 1289 commercial use. 1291 References 1293 [1] Rose M., and K. McCloghrie, "Structure and Identification of 1294 Management Information for TCP/IP-based internets", STD 16, RFC 1295 1155, Performance Systems International, Hughes LAN Systems, May 1296 1990. 1298 [2] McCloghrie K., and M. Rose, Editors, "Management Information Base 1299 for Network Management of TCP/IP-based internets", STD 17, RFC 1300 1213, Performance Systems International, March 1991. 1302 [3] Information processing systems - Open Systems Interconnection - 1303 Specification of Abstract Syntax Notation One (ASN.1), 1304 International Organization for Standardization, International 1306 [4] Information processing systems - Open Systems Interconnection - 1307 Specification of Basic Encoding Rules for Abstract Notation One 1308 (ASN.1), International Organization for Standardization, 1309 International Standard 8825, December 1987. 1311 [5] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", 1312 STD 16, RFC 1212, Performance Systems International, Hughes LAN 1313 Systems, March 1991. 1315 [6] Rose, M., Editor, "A Convention for Defining Traps for use with 1316 the SNMP", RFC 1215, Performance Systems International, March 1317 1991. 1319 [7] McCloghrie, K., "Extensions to the Generic-Interface MIB", RFC 1320 1229, Hughes LAN Systems, Inc., May 1991. 1322 [8] Stephen F. Bush, Sunil Jagannath, Joseph B. Evans, and Victor 1323 Frost, "A Control and Management Network for Wireless ATM 1324 Systems" in Proceedings of the International Communications 1325 Conference '96, p. 459,463 (1996 June). Online version 1326 available at: http://www.tisl.ukans.edu/~sbush/pspapers/icc96.ps 1328 [9] Stephen F. Bush, Sunil Jagannath, Ricardo Sanchez, Joseph B. 1329 Evans, Victor Frost, and K. Sam Shanmugan, Rapidly Deployable 1330 Radio Networks (RDRN) Network Architecture, Telecommunications 1331 Information Sciences Laboratory (1995 July). Online version 1332 available at: 1333 http://www.tisl.ukans.edu/~sbush/pspapers/network_arch.ps 1335 [10] AX.25 Amateur Packet Radio Link-Layer Protocol, IEEE October 1336 (1984). 1338 [11] Network Control Protocol for the Configuration of Mobile 1339 Wireless Beamformed GPS-Based Networks, 1340 , Stephen F. Bush, Sunil 1341 Jagannath. 1343 [12] The Definition of Managed Objects for Virtual Network 1344 Configuration, , Stephen F. Bush, 1345 Sunil Jagannath. 1347 Author's Address 1349 Stephen F. Bush 1350 Sunil Jagannath 1351 Information and Telecommunications Technologies Center (ITTC) 1352 University of Kansas 1353 Lawrence, Kansas 66045 1355 Phone: (913) 864-7761 1357 EMail: sbush@tisl.ukans.edu