idnits 2.17.1 draft-aboba-rpsl-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-25) 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 page length should not exceed 58 lines per page, but there was 15 longer pages, the longest (page 2) being 66 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 15 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 55 instances of too long lines in the document, the longest one being 9 characters in excess of 72. ** 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 68: '... MUST nicHdl...' RFC 2119 keyword, line 77: '... MUST (...' RFC 2119 keyword, line 81: '... MAY (...' RFC 2119 keyword, line 92: '... MUST (...' RFC 2119 keyword, line 95: '... MAY (...' (13 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 14 has weird spacing: '...), its areas...' == Line 15 has weird spacing: '... its worki...' == Line 19 has weird spacing: '... and may ...' == Line 20 has weird spacing: '...afts as refer...' == Line 23 has weird spacing: '... To learn...' == (19 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 (21 November 1997) is 9652 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: '1' is defined on line 675, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 678, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 682, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 686, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 691, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 695, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 699, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 704, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 709, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 714, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 719, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1777 (ref. '1') (Obsoleted by RFC 3494) == Outdated reference: A later version (-07) exists of draft-ietf-asid-ldapv3-attributes-03 -- No information found for draft-ietf-asid-ldapv3ext - is the name correct? == Outdated reference: A later version (-03) exists of draft-ietf-rps-rpsl-00 == Outdated reference: A later version (-06) exists of draft-ietf-rps-appl-rpsl-00 Summary: 13 errors (**), 0 flaws (~~), 22 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Bernard Aboba 3 INTERNET-DRAFT Microsoft 4 Category: Informational 5 6 21 November 1997 8 Lightweight Directory Access Protocol (v3): 9 Schema for the Routing Policy Specification Language (RPSL) 11 1. Status of this Memo 13 This document is an Internet-Draft. Internet-Drafts are working docu- 14 ments of the Internet Engineering Task Force (IETF), its areas, and 15 its working groups. Note that other groups may also distribute work- 16 ing documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference mate- 21 rial or to cite them other than as ``work in progress.'' 23 To learn the current status of any Internet-Draft, please check the 24 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 25 Directories on ds.internic.net (US East Coast), nic.nordu.net 26 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 28 The distribution of this memo is unlimited. It is filed as , and expires June 1, 1998. Please send comments to 30 the authors. 32 2. Abstract 34 This document defines a schema for the Routing Policy Specification 35 Language (RPSL). It is expected that this schema will be useful in 36 providing a standardized format for representation of RPSL within 37 LDAP-based directory services. 39 3. Introduction 41 The Routing Policy Specification Language (RPSL), described in 42 [6]-[8], provides a means for the high-level specification of routing 43 policies. To date, efforts at representing routing policies, as 44 descrbed in [9]-[10], have relied on proprietary schemas. This docu- 45 ment describes how routing policies may be represented in LDAP-based 46 directory services. 48 4. Object definitions 50 The RPSL schema includes definition of the following objects: 52 RPSL Person Class 53 RPSL Entry Class 54 Dictionary object 55 Maintainer object (mntner) 56 Autonomous system number objects (autNum) 57 Route objects (route) 58 Set objects (asSet, routeSet) 59 Router objects (inetRtr) 60 Tunnel objects (inetTunnel) 62 4.1. RPSL Person Class 64 ( rpslPersonClass 1 65 NAME 'rpslOrgPerson' 66 SUP organizationalPerson 67 STRUCTURAL 68 MUST nicHdl 69 ) 71 4.2. RPSL Entry 73 ( rpsl rpslEntry 1 74 NAME 'rpslEntry' 75 SUP top 76 ABSTRACT 77 MUST ( 78 cn $ descr $ techC $ adminC $ mntBy $ 79 changed $ source 80 ) 81 MAY ( 82 remarks $ notify 83 ) 84 ) 86 4.3. Dictionary object 88 ( rpsl rpslDictionary 1 89 NAME 'rpslDictionary' 90 SUP rpslEntry 91 STRUCTURAL 92 MUST ( 93 dictionaryName 94 ) 95 MAY ( 96 rpAttribute $ typeDef $ protocol 97 ) 99 ) 101 4.4. Maintainer Object Class 103 ( rpsl mntner 1 104 NAME 'mntner' 105 SUP rpslEntry 106 STRUCTURAL 107 MUST ( 108 mntnerName $ auth $ updTo 109 ) 110 MAY ( 111 mntNfy 112 ) 113 ) 115 4.5. Autonomous System Number Object Class 117 ( rpsl autNum 1 118 NAME 'autNum' 119 SUP rpslEntry 120 STRUCTURAL 121 MUST ( 122 asNumber $ asName $ autNumGuardian 123 ) 124 MAY ( 125 memberOf $ asIn $ asOut $ default $ igpToEgp $ 126 egpToIgp 127 ) 128 ) 130 4.6. Route Object Class 132 ( rpsl route 1 133 NAME 'route' 134 SUP rpslEntry 135 STRUCTURAL 136 MUST ( 137 addressPrefix $ origin 138 ) 139 MAY ( 140 withdrawn $ memberOf $ injectAt $ aggregateBy $ 141 exportComponents $ holes 142 ) 143 ) 145 4.7. AS-Set Object Class 147 ( rpsl asSet 1 148 NAME 'asSet' 149 SUP rpslEntry 150 STRUCTURAL 151 MUST ( 152 asSetName 153 ) 154 MAY ( 155 asSetMembers $ asSetMembersByReferral 156 ) 157 ) 159 4.8. Route-Set Object Class 161 ( rpsl routeSet 1 162 NAME 'routeSet' 163 SUP rpslEntry 164 STRUCTURAL 165 MUST ( 166 routeSetName 167 ) 168 MAY ( 169 routeSetMembers $ routeSetMembersByReferral 170 ) 171 ) 173 4.9. Router Object Class 175 ( rpsl inetRtr 1 176 NAME 'inetRtr' 177 SUP rpslEntry 178 STRUCTURAL 179 MUST ( 180 rtrName $ localAs $ ifAddr $ 181 inetRtrGuardian 182 ) 183 MAY ( 184 alias $ peer 185 ) 186 ) 188 4.10. Tunnel Object Class 190 ( rpsl inetTunnel 1 191 NAME 'inetTunnel' 192 SUP rpslEntry 193 STRUCTURAL 194 MUST ( 195 TunnelName $ tunnelSource $ tunnelSink $ tunneProtocol $ 196 tunnelIn $ tunnelOut $ inetTunnelGuardian 197 ) 198 ) 200 5. Attribute definitions 202 5.1. New Attribute Types Used in the RPSL Person Class 204 ( rpsl rpslPersonClass 2 205 NAME 'nicHdl' 206 DESC 'the handle by which a person is referred to by the NIC' 207 EQUALITY caseIgnoreMatch 208 SUBSTRINGS caseIgnoreSubstringsMatch 209 SYNTAX 'DirectoryString' 210 SINGLE-VALUE 211 ) 213 5.2. New Attribute Types Used in the RPSL Entry Object Class 215 ( rpsl rpslEntry 2 216 NAME 'descr' 217 DESC 'a description of the object' 218 EQUALITY caseIgnoreMatch 219 SUBSTRINGS caseIgnoreSubstringsMatch 220 SYNTAX 'DirectoryString' 221 SINGLE-VALUE 222 ) 224 ( rpsl rpslEntry 3 225 NAME 'techC' 226 DESC 'the technical contact of the resource' 227 EQUALITY caseIgnoreMatch 228 SUBSTRINGS caseIgnoreSubstringsMatch 229 SYNTAX 'DirectoryString' ) 231 ( rpsl rpslEntry 4 232 NAME 'adminC' 233 DESC 'the administrative contact of the resource' 234 EQUALITY caseIgnoreMatch 235 SUBSTRINGS caseIgnoreSubstringsMatch 236 SYNTAX 'DirectoryString' ) 238 ( rpsl rpslEntry 5 239 NAME 'remarks' 240 DESC 'An explanation or clarification' 241 EQUALITY caseIgnoreMatch 242 SUBSTRINGS caseIgnoreSubstringsMatch 243 SYNTAX 'DirectoryString' ) 245 ( rpsl rpslEntry 6 246 NAME 'notify' 247 DESC 'the email address of the entity to notify in case of 248 Problems with the resource' 250 EQUALITY caseIgnoreMatch 251 SUBSTRINGS caseIgnoreSubstringsMatch 252 SYNTAX 'DirectoryString' ) 254 ( rpsl rpslEntry 7 255 NAME 'mntBy' 256 DESC 'Distinguished Name of maintainer object' 257 EQUALITY distinguishedNameMatch 258 SUBSTRINGS distinguishedNameMatch 259 SYNTAX DN 260 ) 262 ( rpsl rpslEntry 8 263 NAME 'changed' 264 DESC 'the email name of who last changed the resource and 265 the date of when it was changed' 266 EQUALITY caseIgnoreMatch 267 SUBSTRINGS caseIgnoreSubstringsMatch 268 SYNTAX 'DirectoryString' ) 270 ( rpsl rpslEntry 9 271 NAME 'source' 272 DESC 'the registry name from which the information came' 273 EQUALITY caseIgnoreMatch 274 SUBSTRINGS caseIgnoreSubstringsMatch 275 SYNTAX 'DirectoryString' 276 SINGLE-VALUE 277 ) 279 5.3. New Attribute Types Used in the Dictionary Object Class 281 ( rpsl rpslDictionary 2 282 NAME 'dictionaryName' 283 DESC 'the name of the dictionary' 284 EQUALITY caseIgnoreMatch 285 SUBSTRINGS caseIgnoreSubstringsMatch 286 SYNTAX 'DirectoryString' 287 SINGLE-VALUE 288 ) 290 ( rpsl rpslDictionary 3 291 NAME 'rpAttribute' 292 DESC 'routing policy attribute or feature extension' 293 EQUALITY caseIgnoreMatch 294 SUBSTRINGS caseIgnoreSubstringsMatch 295 SYNTAX 'DirectoryString' 296 ) 298 ( rpsl rpslDictionary 4 299 NAME 'typeDef' 300 DESC 'dictionary defined type' 301 EQUALITY caseIgnoreMatch 302 SUBSTRINGS caseIgnoreSubstringsMatch 303 SYNTAX 'DirectoryString' 304 ) 306 ( rpsl rpslDictionary 5 307 NAME 'protocol' 308 DESC 'protocol set and peering options' 309 EQUALITY caseIgnoreMatch 310 SUBSTRINGS caseIgnoreSubstringsMatch 311 SYNTAX 'DirectoryString' 312 ) 314 5.4. New Attribute Types Used in the Maintainer Object Class 316 ( rpsl mntner 2 317 NAME 'mntnerName' 318 DESC 'the name of the maintainer' 319 EQUALITY caseIgnoreMatch 320 SUBSTRINGS caseIgnoreSubstringsMatch 321 SYNTAX 'DirectoryString' 322 SINGLE-VALUE 323 ) 325 ( rpsl mntner 3 326 NAME 'auth' 327 DESC 'The scheme that will be used to identify and authenticate 328 Update requests' 329 EQUALITY caseIgnoreMatch 330 SUBSTRINGS caseIgnoreSubstringsMatch 331 SYNTAX 'DirectoryString' ) 333 ( rpsl mntner 4 334 NAME 'updTo' 335 DESC 'an email address to notify on an unauthorized 336 update of the resource' 337 EQUALITY caseIgnoreMatch 338 SUBSTRINGS caseIgnoreSubstringsMatch 339 SYNTAX 'DirectoryString' ) 341 ( rpsl mntner 5 342 NAME 'mntNfy' 343 DESC 'An email adddress to notify whenever an object is 344 added, changed or deleted' 345 EQUALITY caseIgnoreMatch 346 SUBSTRINGS caseIgnoreSubstringsMatch 347 SYNTAX 'DirectoryString' ) 349 5.5. New Attribute Types Used in the Autonomous System Number Object 350 Class 352 ( rpsl autNum 2 353 NAME 'asNumber' 354 DESC 'the autonomous sytem number' 355 EQUALITY caseIgnoreMatch 356 SUBSTRINGS caseIgnoreSubstringsMatch 357 SYNTAX 'DirectoryString' 358 SINGLE-VALUE 359 ) 361 ( rpsl autNum 3 362 NAME 'asName' 363 DESC 'the autonomous system name' 364 EQUALITY caseIgnoreMatch 365 SUBSTRINGS caseIgnoreSubstringsMatch 366 SYNTAX 'DirectoryString' 367 SINGLE-VALUE 368 ) 370 ( rpsl autNum 4 371 NAME 'memberOf' 372 DESC 'the as-set object name of which this as is a member' 373 EQUALITY caseIgnoreMatch 374 SUBSTRINGS caseIgnoreSubstringsMatch 375 SYNTAX 'DirectoryString' 376 SINGLE-VALUE 377 ) 379 ( rpsl autNum 5 380 NAME 'asIn' 381 DESC 'import policy specification' 382 EQUALITY caseIgnoreMatch 383 SUBSTRINGS caseIgnoreSubstringsMatch 384 SYNTAX 'DirectoryString' ) 386 ( rpsl autNum 6 387 NAME 'asOut' 388 DESC 'export policy specification' 389 EQUALITY caseIgnoreMatch 390 SUBSTRINGS caseIgnoreSubstringsMatch 391 SYNTAX 'DirectoryString' ) 393 ( rpsl autNum 7 394 NAME 'default' 395 DESC 'default policy specification' 396 EQUALITY caseIgnoreMatch 397 SUBSTRINGS caseIgnoreSubstringsMatch 398 SYNTAX 'DirectoryString' ) 400 ( rpsl autNum 8 401 NAME 'igpToEgp' 402 DESC 'specification for how routes from the interAS routing protocol 403 are injected into the IGP protocol' 404 EQUALITY caseIgnoreMatch 405 SUBSTRINGS caseIgnoreSubstringsMatch 406 SYNTAX 'DirectoryString' ) 408 ( rpsl autNum 9 409 NAME 'egpToIgp' 410 DESC 'specification for how routes from the IGP protocol are injected 411 into the interAS routing protocol.' 412 EQUALITY caseIgnoreMatch 413 SUBSTRINGS caseIgnoreSubstringsMatch 414 SYNTAX 'DirectoryString' ) 416 ( rpsl autNum 10 417 NAME 'autNumGuardian' 418 DESC 'the e-mail address of the guardian of the resource' 419 EQUALITY caseIgnoreMatch 420 SUBSTRINGS caseIgnoreSubstringsMatch 421 SYNTAX 'DirectoryString' 422 SINGLE-VALUE 423 ) 425 5.6. New Attribute Types Used in the Route Object Class 427 ( rpsl route 2 428 NAME 'addressPrefix' 429 DESC 'the address prefix for the route' 430 EQUALITY caseIgnoreMatch 431 SUBSTRINGS caseIgnoreSubstringsMatch 432 SYNTAX 'DirectoryString' 433 SINGLE-VALUE 434 ) 436 ( rpsl route 3 437 NAME 'origin' 438 DESC 'the AS number in which the route originates' 439 EQUALITY caseIgnoreMatch 440 SUBSTRINGS caseIgnoreSubstringsMatch 441 SYNTAX 'DirectoryString' 442 SINGLE-VALUE 443 ) 445 ( rpsl route 4 446 NAME 'withdrawn' 447 DESC 'the date at which the route was withdrawn' 448 EQUALITY caseIgnoreMatch 449 SUBSTRINGS caseIgnoreSubstringsMatch 450 SYNTAX 'DirectoryString' 451 SINGLE-VALUE 452 ) 454 ( rpsl route 5 455 NAME 'memberOf' 456 DESC 'the date at which the route was withdrawn' 457 EQUALITY caseIgnoreMatch 458 SUBSTRINGS caseIgnoreSubstringsMatch 459 SYNTAX 'DirectoryString' 460 SINGLE-VALUE 461 ) 462 ( rpsl route 6 463 NAME 'injectAt' 464 DESC 'specifies static routes to inject' 465 EQUALITY caseIgnoreMatch 466 SUBSTRINGS caseIgnoreSubstringsMatch 467 SYNTAX 'DirectoryString' ) 469 ( rpl route 7 470 NAME 'aggregateBy' 471 DESC 'specifies component routes used to form the aggregate' 472 EQUALITY caseIgnoreMatch 473 SUBSTRINGS caseIgnoreSubstringsMatch 474 SYNTAX 'DirectoryString' 475 SINGLE-VALUE 476 ) 478 ( rpsl route 8 479 NAME 'exportComponents' 480 DESC 'a filter matching the routes that need to be exported' 481 EQUALITY caseIgnoreMatch 482 SUBSTRINGS caseIgnoreSubstringsMatch 483 SYNTAX 'DirectoryString' 484 SINGLE-VALUE 485 ) 487 ( rpsl route 9 488 NAME 'holes' 489 DESC 'component address prefixes not reachable through the 490 aggregate route' 491 EQUALITY caseIgnoreMatch 492 SUBSTRINGS caseIgnoreSubstringsMatch 493 SYNTAX 'DirectoryString' 494 SINGLE-VALUE 495 ) 497 5.7. New Attribute Types Used in the AS-Set Object Class 499 ( rpsl asSet 2 500 NAME 'asSetName' 501 DESC 'the AS-SET name' 502 EQUALITY caseIgnoreMatch 503 SUBSTRINGS caseIgnoreSubstringsMatch 504 SYNTAX 'DirectoryString' 505 SINGLE-VALUE 506 ) 508 ( rpsl asSet 3 509 NAME 'asSetMembers' 510 DESC 'list of address prefixes' 511 EQUALITY caseIgnoreMatch 512 SUBSTRINGS caseIgnoreSubstringsMatch 513 SYNTAX 'DirectoryString' 514 SINGLE-VALUE 516 ) 518 ( rpsl asSet 4 519 NAME 'asSetMembersByReferral' 520 DESC 'list of maintainer classes' 521 EQUALITY caseIgnoreMatch 522 SUBSTRINGS caseIgnoreSubstringsMatch 523 SYNTAX 'DirectoryString' 524 SINGLE-VALUE 525 ) 527 5.8. New Attribute Types Used in the Route-Set Object Class 529 ( rpsl routeSet 2 530 NAME 'routeSetName' 531 DESC 'the route set name' 532 EQUALITY caseIgnoreMatch 533 SUBSTRINGS caseIgnoreSubstringsMatch 534 SYNTAX 'DirectoryString' 535 SINGLE-VALUE 536 ) 538 ( rpsl routeSet 3 539 NAME 'routeSetMembers' 540 DESC 'list of address prefixes' 541 EQUALITY caseIgnoreMatch 542 SUBSTRINGS caseIgnoreSubstringsMatch 543 SYNTAX 'DirectoryString' 544 SINGLE-VALUE 545 ) 547 ( rpsl routeSet 4 548 NAME 'routeSetMembersByReferral' 549 DESC 'list of maintainer classes' 550 EQUALITY caseIgnoreMatch 551 SUBSTRINGS caseIgnoreSubstringsMatch 552 SYNTAX 'DirectoryString' 553 SINGLE-VALUE 554 ) 556 5.9. New Attribute Types Used in the Router Object Class 558 ( rpsl inetRtr 2 559 NAME 'rtrName' 560 DESC 'the name of the router' 561 EQUALITY caseIgnoreMatch 562 SUBSTRINGS caseIgnoreSubstringsMatch 563 SYNTAX 'DirectoryString' 564 SINGLE-VALUE 565 ) 567 ( rpsl inetRtr 3 568 NAME 'alias' 569 DESC 'other names by which the router is known' 570 EQUALITY caseIgnoreMatch 571 SUBSTRINGS caseIgnoreSubstringsMatch 572 SYNTAX 'DirectoryString' ) 574 ( rpsl inetRtr 4 575 NAME 'localAs' 576 DESC 'the local AS in which the router resides' 577 EQUALITY caseIgnoreMatch 578 SUBSTRINGS caseIgnoreSubstringsMatch 579 SYNTAX 'DirectoryString' 580 SINGLE-VALUE 581 ) 583 ( rpsl inetRtr 5 584 NAME 'ifAddr' 585 DESC 'a string describing an interface address on the router' 586 EQUALITY caseIgnoreMatch 587 SUBSTRINGS caseIgnoreSubstringsMatch 588 SYNTAX 'DirectoryString' ) 590 ( rpsl inetRtr 6 591 NAME 'peer' 592 DESC 'a string describing relationships with peer routers' 593 EQUALITY caseIgnoreMatch 594 SUBSTRINGS caseIgnoreSubstringsMatch 595 SYNTAX 'DirectoryString' ) 597 ( rpsl inetRtr 7 598 NAME 'inetRtrGuardian' 599 DESC 'the e-mail address of the guardian of the resource' 600 EQUALITY caseIgnoreMatch 601 SUBSTRINGS caseIgnoreSubstringsMatch 602 SYNTAX 'DirectoryString' 603 SINGLE-VALUE 604 ) 606 5.10. New Attribute Types Used in the Tunnel Object Class 608 ( rpsl inetTunnel 2 609 NAME 'tunnelName' 610 DESC 'the name of the tunnel' 611 EQUALITY caseIgnoreMatch 612 SUBSTRINGS caseIgnoreSubstringsMatch 613 SYNTAX 'DirectoryString' 614 SINGLE-VALUE 615 ) 617 ( rpsl inetTunnel 3 618 NAME 'tunnelSource' 619 DESC 'the source of the tunnel' 620 EQUALITY caseIgnoreMatch 621 SUBSTRINGS caseIgnoreSubstringsMatch 622 SYNTAX 'DirectoryString' 623 SINGLE-VALUE 624 ) 626 ( rpsl inetTunnel 4 627 NAME ' tunnelSink' 628 DESC 'the sink of the tunnel' 629 EQUALITY caseIgnoreMatch 630 SUBSTRINGS caseIgnoreSubstringsMatch 631 SYNTAX 'DirectoryString' 632 SINGLE-VALUE 633 ) 635 ( rpsl inetTunnel 5 636 NAME 'tunnelProtocol' 637 DESC 'the protocol to be run inside the tunnel. Values include 638 BGP, RPv6, DVMRP, PIM-DM, and PIM-SM' 639 EQUALITY caseIgnoreMatch 640 SUBSTRINGS caseIgnoreSubstringsMatch 641 SYNTAX 'DirectoryString' 642 SINGLE-VALUE 643 ) 645 ( rpsl inetTunnel 6 646 NAME 'tunnelIn' 647 DESC 'a string describing the inbound routing policy' 648 EQUALITY caseIgnoreMatch 649 SUBSTRINGS caseIgnoreSubstringsMatch 650 SYNTAX 'DirectoryString' ) 652 ( rpsl inetTunnel 7 653 NAME 'tunnelOut' 654 DESC 'a string describing the outbound routing policy' 655 EQUALITY caseIgnoreMatch 656 SUBSTRINGS caseIgnoreSubstringsMatch 657 SYNTAX 'DirectoryString' ) 659 ( rpsl inetTunnel 8 660 NAME 'inetTunnelGuardian' 661 DESC 'the e-mail address of the guardian of the resource' 662 EQUALITY caseIgnoreMatch 663 SUBSTRINGS caseIgnoreSubstringsMatch 664 SYNTAX 'DirectoryString' 665 SINGLE-VALUE 666 ) 668 6. Acknowledgments 670 Thanks to Gurdeep Singh Pall and Narendra Gidwani of Microsoft for 671 useful discussions of this problem space. 673 7. References 675 [1] W. Yeong, T. Howes, S. Kille, "Lightweight Directory Access Pro- 676 tocol." RFC 1777, March, 1995. 678 [2] "Information Processing Systems - Open Systems Interconnection - 679 The Directory: Overview of Concepts, Models and Service." ISO/IEC JTC 680 1/SC21, International Standard 9594-1, 1988. 682 [3] "Information Processing Systems - Open Systems Interconnection - 683 The Directory: Selected Object Classes." Recommendation X.521 ISO/IEC 684 JTC 1/SC21, International Standard 9594-7, 1993. 686 [4] M.Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight Directory 687 Access Protocol: Standard and Pilot Attribute Definitions. " Internet 688 Draft (work in progress), October 1996, draft-ietf-asid- 689 ldapv3-attributes-03.txt. 691 [5] Y. Yaacovi, K. Settle, "Lightweight Directory Access Protocol: 692 Extensions for Dynamic Directory Services. " Internet Draft (work in 693 progress), June 1996, draft-ietf-asid-ldapv3ext-00.txt, Microsoft. 695 [6] D. Meyer, "Representing Tunnels in RPSL." Internet Draft (work in 696 progress), November 1996, draft-ietf-rps-tunnels-00.txt, University of 697 Oregon. 699 [7] C. Allaettinoglu, T. Bates, E. Gerich, D. Karrenberg, M. Terpstra, 700 C. Villamizar, "Routing Policy Specification Language (RPSL)," Inter- 701 net Draft (work in progress), November, 1996, draft-ietf-rps- 702 rpsl-00.txt, USC/ISI, Cisco Systems, @HOME, RIPE, Bay Networks, ANS. 704 [8] C. Allaettinouglu, D. Meyer, J. Schmitz, "Application of Routing 705 Policy Specification Language (RPSL) on the Internet," Internet Draft 706 (work in progress), March, 1997, draft-ietf-rps-appl-rpsl-00.txt, 707 USC/ISI, University of Oregon, DFN-NOC. 709 [9] T. Bates, E. Gerich, L. Joncheray, J-M. Jouanigot, D. Karrenberg, 710 M. Terpstra, and J. Yu, "Representation of IP Routing Policies in a 711 Routing Registry," Technical Report ripe-181, RIPE, RIPE NCC, Amster- 712 dam, Netherlands, October 1994. 714 [10] T. Bates, J-M. Jouanigot, D. Karrenberg, P. Lothberg, and M. 715 Terpstra, "Representation of IP Routing Policies in the RIPE 716 Database," Technical Report ripe-81, RIPE, RIPE NCC, Amsterdam, 717 Netherlands, February, 1993. 719 [11] How to register in RADB. http://www.ra.net/RADB.tools.docs/. 721 8. Authors' Addresses 723 Bernard Aboba 724 Microsoft Corporation 725 One Microsoft Way 726 Redmond, WA 98052 728 Phone: 206-936-6605 729 EMail: bernarda@microsoft.com