idnits 2.17.1 draft-bolton-edimib-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-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 -- 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 684 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 9 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** There are 304 instances of lines with control characters in the document. 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 (September 27, 1996) is 10071 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: '5' is mentioned on line 105, but not defined ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '4') Summary: 12 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT 2 Expire in six months 3 5 Electronic Data Interchange MIB (EDIMIB) 6 Version 1 8 September 27, 1996 10 John Andrukonis 11 MITRE Corporation 12 jandru@mitre.org 14 Daniel Bolton 15 MITRE Corporation 16 dbolton@mitre.org 18 Status of this Memo 20 This document is an Internet-Draft. Internet-Drafts are working 21 documents of the Internet Engineering Task Force (IETF), its areas, 22 and its working groups. Note that other groups may also distribute 23 working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other documents 27 at any time. It is inappropriate to use Internet-Drafts as 28 reference material or to cite them other than as ``work in 29 progress.'' 31 To learn the current status of any Internet-Draft, please check the 32 ``1id-abstracts.txt'' listing contained in the Internet-Drafts 33 Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net 34 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 35 Rim). 37 Abstract 39 This memo defines a MIB for use with managing EDI systems. The term 40 EDI systems includes large scale systems providing translator functions 41 such as the US federal government's Electronic Commerce Processing Node 42 (ECPN) for which this MIB was specifically designed, as well as smaller 43 Value Added Network (VAN) systems. Because of the desire for scalability 44 variable names are deliberately vague, so that a channel may represent a 45 single user, a group of users that use the same network entry point or 46 that are defined by the implementor as functionally similar, or (as in 47 the case of the ECPN) a connection to a third party network. This MIB 48 does not address management of client systems which connect to the 49 various EDI systems. 51 Table of Contents 53 1 The Network Management Framework 54 2 Objects 55 3 Format of Definitions 56 4 Definitions 57 4.1 The EDI program group 58 4.2 The Site channels group 59 4.3 The Channel Entry group 60 4.4 The Channel Input group 61 4.5 Channel Incoming Throughput group 62 4.6 The Channel Output group 63 4.7 The Outgoing Throughput group 64 4.8 Channel Activity statistics 65 4.9 The Site Connection statistics group 66 5. References 67 6. Security Considerations 68 7. Authors' Addresses 70 1 The Network Management Framework 72 The Internet-standard Network Management Framework consists of three 73 components. They are: 75 RFC 1155 [1] which defines the Structure of Management Information 76 (SMI), the mechanisms for describing and naming objects for the 77 purpose of management. RFC 1212 [2] defines a more concise description 78 mechanism, which is wholly consistent with the SMI. 80 RFC 1213 [3] which defines MIB-II, the core set of managed objects 81 for the Internet suite of protocols. 83 RFC 1157 [4] which defines the Simple Network Management Protocol 84 (SNMP), the protocol used for network access to managed objects. 86 The Network Management Framework permits new objects to be defined 87 for the purpose of experimentation and evaluation. 89 2 Objects 91 Managed objects are accessed via a virtual information store, termed 92 the Management Information Base (MIB). Within a given MIB module, 93 objects are defined using RFC 1212's OBJECT-TYPE macro. At a 94 minimum, each object has a name, a syntax, an access-level, and an 95 implementation status. 97 The name is an object identifier, an administratively assigned name, 98 which specifies an object type. The object type together with an 99 object instance serves to uniquely identify a specific instantiation 100 of the object. For human convenience, we often use a textual string, 101 termed the object descriptor, to also refer to the object type. 103 The syntax of an object type defines the abstract data structure 104 corresponding to that object type. The Abstract Syntax Notation 1 105 (ASN.1)[5] language is used for this purpose. However, RFC 1155 106 purposefully restricts the ASN.1 constructs which may be used. 107 These restrictions are explicitly made for simplicity. 109 The access-level of an object type defines whether it makes 110 "protocol sense" to read and/or write the value of an instance 111 of the object type. (This access-level is independent of any 112 administrative authorization policy.) 114 The implementation-status of an object type indicates whether the 115 object is mandatory, optional, obsolete, or deprecated. 117 The encoding of an object type is simply how that object is 118 represented using the object type's syntax. Implicitly tied to 119 the notion of an object type's syntax and encoding is how the 120 object type is represented when being transmitted on the network. 122 The SMI specifies the use of the basic encoding rules (BER) of 123 ASN.1, subject to the additional requirements imposed by the SNMP. 125 3 Format of Definitions 127 Section 4 contains the specification of all object types contained 128 in this MIB module. These object types are defined using the 129 conventions defined in [1] and [2]. 131 4 Definitions 133 EDI-MIB DEFINITIONS ::= BEGIN 135 -- 136 -- EDI MIB - used for EDI management 137 -- 138 -- Only contains fault and performance monitoring variables at present 140 IMPORTS 141 OBJECT-TYPE FROM RFC-1212 142 DisplayString FROM RFC1213-MIB 143 TimeTicks, Counter 144 Guage FROM RFC1155-SMI; 146 -- At current time the edi tree is placed beneath MITRE's enterprise OID 147 -- this would move beneath MIBII 149 internet OBJECT IDENTIFIER ::= { iso(1) org(3) dod(6) internet(1) } 150 enterprises OBJECT IDENTIFIER ::= { internet private(4) 1 } 151 mitre OBJECT IDENTIFIER ::= { enterprises 115 } 152 edi OBJECT IDENTIFIER ::= { mitre int(1) test(2) 8 } 154 ediProg OBJECT IDENTIFIER ::= { edi 1 } 155 siteInfo OBJECT IDENTIFIER ::= { edi 2 } 157 4.1 The EDI program group 159 ediUptime OBJECT-TYPE 160 SYNTAX TimeTicks 161 ACCESS read-only 162 STATUS mandatory 163 DESCRIPTION 164 "Timestamp to show how long the edi process has been 165 running" 166 ::= { ediProg 1 } 168 ediVersion OBJECT-TYPE 169 SYNTAX DisplayString 170 ACCESS read-only 171 STATUS mandatory 172 DESCRIPTION 173 "Displays the version number of the edi software" 174 ::= { ediProg 2 } 176 ediLastrev OBJECT-TYPE 177 SYNTAX DisplayString 178 ACCESS read-only 179 STATUS mandatory 180 DESCRIPTION 181 "Displays the last time the edi software has been 182 updated" 183 ::= { ediProg 3 } 185 ediAdministrator OBJECT-TYPE 186 SYNTAX DisplayString 187 ACCESS read-write 188 STATUS mandatory 189 DESCRIPTION 190 "Displays information about the edi administrator" 191 ::= { ediProg 4 } 193 4.2 The Site channels group 195 siteChannels OBJECT-TYPE 196 SYNTAX SiteChannels 197 ACCESS not-accessible 198 STATUS mandatory 199 DESCRIPTION 200 "This is the compound data type containing the 201 number of channels and the table containing more 202 detailed info." 203 ::= { siteInfo 1 } 205 SiteChannels ::= 206 SEQUENCE { 207 siteNumChannels INTEGER, 208 siteChanTable SiteChanTable 209 } 211 siteNumChannels OBJECT-TYPE 212 SYNTAX INTEGER 213 ACCESS read-only 214 STATUS mandatory 215 DESCRIPTION 216 "Number of channels configured at current time" 217 ::= { siteChannels 1 } 219 siteErrors OBJECT-TYPE 220 SYNTAX Counter 221 ACCESS read-only 222 STATUS mandatory 223 DESCRIPTION 224 "The total number of errors received relating to 225 all channels on this site." 226 ::= { siteChannels 2 } 228 siteInQueueLen OBJECT-TYPE 229 SYNTAX Counter 230 ACCESS read-only 231 STATUS mandatory 232 DESCRIPTION 233 "The number of messages received that are in the 234 input queue relating to all channels at this site." 235 ::= { siteChannels 3 } 237 siteInKbytes OBJECT-TYPE 238 SYNTAX Counter 239 ACCESS read-only 240 STATUS mandatory 241 DESCRIPTION 242 "The number of kilobytes of messages transmitted 243 on the input queue relating to all channels at 244 this site." 245 ::= { siteChannels 4 } 247 siteOutQueueLen OBJECT-TYPE 248 SYNTAX Counter 249 ACCESS read-only 250 STATUS mandatory 251 DESCRIPTION 252 "The number of messages received that are in 253 the output queue of all channels at this site." 254 ::= { siteChannels 5 } 256 siteOutKbytes OBJECT-TYPE 257 SYNTAX Counter 258 ACCESS read-only 259 STATUS mandatory 260 DESCRIPTION 261 "The number of kilobytes transmitted on the 262 output queue relating to all channels at this 263 site." 264 ::= { siteChannels 6 } 266 SiteChanTable OBJECT-TYPE 267 SYNTAX SEQUENCE OF siteChanEntry 268 ACCESS not-accessible 269 STATUS mandatory 270 DESCRIPTION 271 "List of channels and information associated with 272 them." 273 ::= { siteChannels 7 } 275 siteChanEntry OBJECT-TYPE 276 SYNTAX SiteChanEntry 277 ACCESS not-accessible 278 STATUS mandatory 279 DESCRIPTION 280 "This macro documents the column that uniquely 281 describes each row." 282 INDEX { siteChanIndex } 283 ::= { SiteChanTable 1 } 285 SiteChanEntry ::= 286 SEQUENCE { 287 siteChanIndex INTEGER, 288 siteChanDescription DisplayString, 289 siteChanType INTEGER, 290 siteChanSpeed DisplayString, 291 siteChanErrors Counter, 292 siteChanInQueueLen Counter, 293 siteChanInKbytes Counter, 294 siteChanInThroughTable SiteChanInThroughTable, 295 siteChanOutQueueLen Counter, 296 siteChanOutKbytes Counter, 297 siteChanOutThroughTable SiteChanOutThroughTable, 298 siteChanLastIn TimeTicks, 299 siteChanLastOut TimeTicks, 300 siteChanConnections SiteConnectionTable, 301 siteChanOldestOutMessage TimeTicks 302 } 304 siteChanIndex OBJECT-TYPE 305 SYNTAX INTEGER 306 ACCESS read-only 307 STATUS mandatory 308 DESCRIPTION 309 "The index value which uniquely identifies the 310 channel to which this entry is applicable." 311 ::= { siteChanEntry 1 } 313 4.3 The Channel Entry group 315 siteChanDescription OBJECT-TYPE 316 SYNTAX DisplayString 317 ACCESS read-only 318 STATUS mandatory 319 DESCRIPTION 320 "The textual description of the channel." 321 ::= { siteChanEntry 2 } 323 siteChanType OBJECT-TYPE 324 SYNTAX INTEGER { 325 ftp(1), -- file transfer protocol 326 smtp(2), -- simple mail transfer protocol 327 x.400(3), -- x.400 mail message 328 kermit(4), 329 zmodem(5), 330 cleo(6) 331 } 332 ACCESS read-only 333 STATUS mandatory 334 DESCRIPTION 335 "The protocol that this channel communicates with." 336 ::= { siteChanEntry 3 } 338 siteChanSpeed OBJECT-TYPE 339 SYNTAX DisplayString 340 ACCESS read-only 341 STATUS mandatory 342 DESCRIPTION 343 "A textual description of factors that may affect 344 the speed of transmission through the channel 345 (e.g. baud rate for modem comms)" 346 ::= { siteChanEntry 4 } 348 siteChanErrors OBJECT-TYPE 349 SYNTAX Counter 350 ACCESS read-only 351 STATUS mandatory 352 DESCRIPTION 353 "The total number of errors received relating to 354 this channel." 355 ::= { siteChanEntry 5 } 357 4.4 The Channel Input group 359 siteChanInQueueLen OBJECT-TYPE 360 SYNTAX Counter 361 ACCESS read-only 362 STATUS mandatory 363 DESCRIPTION 364 "The number of messages received that are in the 365 input queue relating to this channel." 366 ::= { siteChanEntry 6 } 368 siteChanInKbytes OBJECT-TYPE 369 SYNTAX Counter 370 ACCESS read-only 371 STATUS mandatory 372 DESCRIPTION 373 "The number of kilobytes of messages transmitted 374 on the input queue relating to this channel." 375 ::= { siteChanEntry 7 } 377 siteChanInThroughTable OBJECT-TYPE 378 SYNTAX SiteChanInThroughTable 379 ACCESS not-accessible 380 STATUS mandatory 381 DESCRIPTION 382 "This macro documents the column that uniquely 383 describes each row." 384 ::= { siteChanEntry 8 } 386 4.5 Channel Incoming Throughput group 388 SiteChanInThroughTable ::= 389 SEQUENCE { 390 siteChanISAIn Counter, 391 siteChanGSIn Counter, 392 siteChanPublicIn Counter, 393 siteChanSTIn Counter, 394 } 396 siteChanISAIn OBJECT-TYPE 397 SYNTAX Counter 398 ACCESS read-only 399 STATUS mandatory 400 DESCRIPTION 401 "The number of ISA messages received that are in the 402 input queue relating to this channel." 403 ::= { siteChanInThroughTable 1 } 405 siteChanGSIn OBJECT-TYPE 406 SYNTAX Counter 407 ACCESS read-only 408 STATUS mandatory 409 DESCRIPTION 410 "The number of GS messages received that are in the 411 input queue relating to this channel." 412 ::= { siteChanInThroughTable 2 } 414 siteChanPublicIn OBJECT-TYPE 415 SYNTAX Counter 416 ACCESS read-only 417 STATUS mandatory 418 DESCRIPTION 419 "The number of public messages received that are 420 in the input queue relating to this channel." 421 ::= { siteChanInThroughTable 3 } 423 siteChanSTIn OBJECT-TYPE 424 SYNTAX Counter 425 ACCESS read-only 426 STATUS mandatory 427 DESCRIPTION 428 "The number of ST messages received that are 429 in the input queue relating to this channel." 430 ::= { siteChanInThroughTable 4 } 432 4.6 The Channel Output group 434 siteChanOutQueueLen OBJECT-TYPE 435 SYNTAX Counter 436 ACCESS read-only 437 STATUS mandatory 438 DESCRIPTION 439 "The number of messages received that are in 440 the output queue relating to this channel." 441 ::= { siteChanEntry 9 } 443 siteChanOutKbytes OBJECT-TYPE 444 SYNTAX Counter 445 ACCESS read-only 446 STATUS mandatory 447 DESCRIPTION 448 "The number of kilobytes transmitted on the 449 output queue relating to this channel." 450 ::= { siteChanEntry 10 } 452 siteChanOutThroughTable OBJECT-TYPE 453 SYNTAX SiteChanOutThroughTable 454 ACCESS not-accessible 455 STATUS mandatory 456 DESCRIPTION 457 "The table that shows the types of outgoing 458 messages for the channel." 459 ::= { siteChanEntry 11 } 461 4.7 The Outgoing Throughput group 463 SiteChanOutThroughTable ::= 464 SEQUENCE { 465 siteChanISAOut Counter, 466 siteChanGSOut Counter, 467 siteChanPublicOut Counter, 468 siteChanSTOut Counter, 469 } 471 siteChanISAOut OBJECT-TYPE 472 SYNTAX Counter 473 ACCESS read-only 474 STATUS mandatory 475 DESCRIPTION 476 "The number of ISA messages received that are 477 in the input queue relating to this channel." 478 ::= { siteChanOutThroughTable 1 } 480 siteChanGSOut OBJECT-TYPE 481 SYNTAX Counter 482 ACCESS read-only 483 STATUS mandatory 484 DESCRIPTION 485 "The number of GS messages received that are 486 in the input queue relating to this channel." 487 ::= { siteChanOutThroughTable 2 } 489 siteChanPublicOut OBJECT-TYPE 490 SYNTAX Counter 491 ACCESS read-only 492 STATUS mandatory 493 DESCRIPTION 494 "The number of public messages received that are 495 in the input queue relating to this channel." 496 ::= { siteChanOutThroughTable 3 } 498 siteChanSTOut OBJECT-TYPE 499 SYNTAX Counter 500 ACCESS read-only 501 STATUS mandatory 502 DESCRIPTION 503 "The number of ST messages received that are 504 in the input queue relating to this channel." 505 ::= { siteChanOutThroughTable 4 } 507 4.8 Channel Activity statistics 509 siteChanLastIn OBJECT-TYPE 510 SYNTAX TimeTicks 511 ACCESS read-only 512 STATUS mandatory 513 DESCRIPTION 514 "The time (in hundredths of a second) since the 515 last message was placed in the input queue." 516 ::= { siteChanEntry 12 } 518 siteChanLastOut OBJECT-TYPE 519 SYNTAX TimeTicks 520 ACCESS read-only 521 STATUS mandatory 522 DESCRIPTION 523 "The time (in hundredths of a second) since the 524 last message was placed in the output queue." 525 ::= { siteChanEntry 13 } 527 siteChanOldestOut OBJECT-TYPE 528 SYNTAX TimeTicks 529 ACCESS read-only 530 STATUS mandatory 531 DESCRIPTION 532 "The time (in hundredths of a second) that the 533 oldest message has resided in the output queue." 534 ::= { siteChanEntry 14 } 536 4.9 The Site Connection statistics group 538 siteConnectionTable OBJECT-TYPE 539 SYNTAX SiteConnectionTable 540 ACCESS not-accessible 541 STATUS mandatory 542 DESCRIPTION 543 "This table describes the connections and connection 544 attempts for this channel." 545 ::= { siteChanEntry 15 } 547 SiteConnectionTable ::= 548 SEQUENCE { 549 siteConnLastIn TimeTicks, 550 siteConnLastOut TimeTicks, 551 siteConnLastFailedIn TimeTicks, 552 siteConnLastFailedOut TimeTicks, 553 siteConnIn Counter, 554 siteConnOut Counter, 555 siteConnFailedIn Counter, 556 siteConnFailedOut Counter, 557 } 559 siteConnLastIn OBJECT-TYPE 560 SYNTAX TimeTicks 561 ACCESS read-only 562 STATUS mandatory 563 DESCRIPTION 564 "The time (in hundredths of a second) since the 565 last successful inbound connection attempt." 566 ::= { siteConnectionTable 1 } 568 siteConnLastOut OBJECT-TYPE 569 SYNTAX TimeTicks 570 ACCESS read-only 571 STATUS mandatory 572 DESCRIPTION 573 "The time (in hundredths of a second) since the 574 last successful outbound connection attempt." 575 ::= { siteConnectionTable 2 } 577 siteConnLastFailedIn OBJECT-TYPE 578 SYNTAX TimeTicks 579 ACCESS read-only 580 STATUS mandatory 581 DESCRIPTION 582 "The time (in hundredths of a second) since the 583 last unsuccessful inbound connection attempt." 584 ::= { siteConnectionTable 3 } 586 siteConnLastFailedOut OBJECT-TYPE 587 SYNTAX TimeTicks 588 ACCESS read-only 589 STATUS mandatory 590 DESCRIPTION 591 "The time (in hundredths of a second) since the 592 last unsuccessful outbound connection attempt." 593 ::= { siteConnectionTable 4 } 595 siteConnIn OBJECT-TYPE 596 SYNTAX Counter 597 ACCESS read-only 598 STATUS mandatory 599 DESCRIPTION 600 "The total number of inbound connections received 601 on this channel." 602 ::= { siteConnectionTable 5 } 604 siteConnOut OBJECT-TYPE 605 SYNTAX Counter 606 ACCESS read-only 607 STATUS mandatory 608 DESCRIPTION 609 "The total number of outbound connections recieved 610 on this channel." 611 ::= { siteConnectionTable 6 } 613 siteConnFailedIn OBJECT-TYPE 614 SYNTAX Counter 615 ACCESS read-only 616 STATUS mandatory 617 DESCRIPTION 618 "The total number of failed inbound connection 619 attempts on this channel." 620 ::= { siteConnectionTable 7 } 622 siteConnFailedOut OBJECT-TYPE 623 SYNTAX Counter 624 ACCESS read-only 625 STATUS mandatory 626 DESCRIPTION 627 "The total number of failed outbound connection 628 attempts on this channel." 629 ::= { siteConnectionTable 8 } 631 END 633 5. References 635 [1] Rose M. and McCloghrie K., "Structure and Identification of 636 Management Information for TCP/IP-based Internets", STD 16, RFC 637 1155, Performance Systems International, Hughes LAN Systems, 638 May 1990. 640 [2] Rose M. and K. McCloghrie, Editors, "Concise MIB Definitions", 641 STD 16, RFC 1212, Performance Systems International, Hughes LAN 642 Systems, March 1991. 644 [3] McCloghrie K. and Rose M., Editors, "Management Information 645 Base for Network Management of TCP/IP-based Internets", STD 17, 646 RFC 1213, Performance Systems International, March 1991. 648 [4] Case J., Fedor M., Schoffstall M., and Davin J., "Simple 649 Network Management Protocol", STD 15, RFC 1157, SNMP Research, 650 Performance Systems International, Performance Systems 651 International, MIT Laboratory for Computer Science, May 1990. 653 6. Security Considerations 655 Security issues are not discussed in this memo. 657 7. Authors' Addresses 659 John Andrukonis 660 The MITRE Corporation 661 Mailstop W658 662 1820 Dolley Madison Blvd. 663 McLean, VA 22102 665 email: jandru@mitre.org 667 Daniel Bolton 668 The MITRE Corporation 669 Mailstop W658 670 1820 Dolley Madison Blvd. 671 McLean, VA 22102 673 email: dbolton@mitre.org 674