cznic-dns-rdata.yinx 26.3 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
<?xml version="1.0" encoding="utf-8"?>
<module name="cznic-dns-rdata"
        xmlns="urn:ietf:params:xml:ns:yang:yin:1"
        xmlns:dnszc="http://www.nic.cz/ns/yang/dns-rdata"
        xmlns:h="http://www.w3.org/1999/xhtml">
  <namespace uri="http://www.nic.cz/ns/yang/dns-rdata"/>
  <prefix value="rdata"/>
  <yang-version value="1.1"/>

  <!-- Imports -->

  <import module="ietf-inet-types">
    <prefix value="inet"/>
  </import>
  <import module="ietf-yang-types">
    <prefix value="yang"/>
  </import>
  <import module="iana-dns-class-rr-type">
    <prefix value="dnsct"/>
  </import>
  <import module="cznic-dns-parameters">
    <prefix value="dnspar"/>
  </import>

  <!-- Metadata -->

  <organization>
    <text>CZ.NIC, z. s. p. o.</text>
  </organization>
  <contact>
    <text>
      <h:p>
        Editor:   Ladislav Lhotka<h:br/>
                  &lt;mailto:lhotka@nic.cz&gt;
      </h:p>
    </text>
  </contact>
  <description>
    <text>
      <h:p>This module contains typedefs and groupings that define the
      RDATA contents for all DNS resource record types.</h:p>
    </text>
  </description>
  <reference>
    <text>
      RFC 1035: Domain Names - Implementation and Specification.
    </text>
  </reference>
  <revision date="2018-10-26">
    <description>
      <text>Initial revision.</text>
    </description>
  </revision>

  <!-- Groupings -->

57
  <grouping name="rrsig">
58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205
    <description>
      <text>
	RDATA for 'RRSIG' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 4034: Resource Records for the DNS Security
	Extensions
      </text>
    </reference>
    <leaf name="algorithm">
      <type name="dnspar:dnssec-algorithm"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field identifies the cryptographic algorithm
	  used to create the signature.
	</text>
      </description>
    </leaf>
    <leaf name="signature-expiration">
      <type name="dnspar:utc-date-time"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field specifies the end of a validity period
	  for the signature as UTC date and time. The RRSIG
	  record MUST NOT be used for authentication after
	  the expiration date and time.
	</text>
      </description>
    </leaf>
    <leaf name="signature-inception">
      <type name="dnspar:utc-date-time"/>
      <mandatory value="true"/>
      <description>
	<text>
	  <h:p>This field specifies the start of a validity
	  period for the signature as UTC date and time. The
	  RRSIG record MUST NOT be used for authentication
	  prior the inception date and time.</h:p>
	  <h:p>This date MUST precede the date specified in
	  'signature-expiration'.</h:p>
	</text>
      </description>
    </leaf>
    <uses name="key-tag-field"/>
    <leaf name="signature">
      <type name="binary">
	<length value="1..max"/>
      </type>
      <mandatory value="true"/>
      <description>
	<text>
	  <h:p>This field contains the cryptographic
	  signature that covers the RRSIG RDATA (excluding
	  the Signature field) and the RRset specified by
	  the RRSIG owner name, RRSIG class, and RRSIG Type
	  Covered field.</h:p>
	  <h:p>The format of this field depends on the algorithm in
	  use.</h:p>
	</text>
      </description>
    </leaf>
  </grouping>

  <grouping name="key-tag-field">
    <description>
      <text>
	This grouping defines the 'key-tag' field that is used in
	RRSIG and DS resource records.
      </text>
    </description>
    <leaf name="key-tag">
      <type name="uint16"/>
      <mandatory value="true"/>
      <description>
	<text>
	  The Key Tag field contains the key tag value of the DNSKEY
	  RR that validates this signature, in network byte order.
	</text>
      </description>
    </leaf>
  </grouping>

  <grouping name="rrset-types">
    <description>
      <text>
	This grouping defines a sequence of RR types, It is used in
	NSEC and NSEC3 resource records.
      </text>
    </description>
    <leaf-list name="rrset-type">
      <type name="dnsct:rr-type"/>
      <min-elements value="1"/>
      <description>
	<text>
	  This leaf-list represents the Type Bit Maps field. Its
	  entries identify the RRset types that exist at the NSEC RR's
	  owner name.
	</text>
      </description>
    </leaf-list>
  </grouping>

  <grouping name="nsec3-common">
    <description>
      <text>
	This grouping defines common field of NSEC3 and NSEC3PARAM
	resource records.
      </text>
    </description>
    <leaf name="hash-algorithm">
      <type name="dnspar:dnssec-nsec3-hash-algorithm"/>
      <default value="SHA-1"/>
      <description>
	<text>
	  This field identifies the cryptographic hash algorithm used
	  to construct the hash-value.
	</text>
      </description>
    </leaf>
    <leaf name="iterations">
      <type name="uint16"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field defines the number of additional times the hash
	  function has been performed.
	</text>
      </description>
    </leaf>
    <leaf name="salt">
      <type name="dnspar:hex-digits">
	<length value="0..510"/>
      </type>
      <mandatory value="true"/>
      <description>
	<text>
	  This field is appended to the original owner name before
	  hashing in order to defend against pre-calculated dictionary
	  attacks.
	</text>
      </description>
    </leaf>
  </grouping>

206
  <grouping name="soa">
207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287
    <description>
      <text>
	RDATA content for 'SOA' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="mname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Name server that was the original or primary source of
	  data for this zone.
	</text>
      </description>
    </leaf>
    <leaf name="rname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Mailbox of the person responsible for this zone.
	</text>
      </description>
    </leaf>
    <leaf name="serial">
      <type name="yang:counter32"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Version number of the original copy of the zone.
	</text>
      </description>
    </leaf>
    <leaf name="refresh">
      <type name="dnspar:time-interval"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Time interval that should elapse before the zone should
	  be refreshed.
	</text>
      </description>
    </leaf>
    <leaf name="retry">
      <type name="dnspar:time-interval"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Time interval that should elapse before a failed refresh
	  should be retried.
	</text>
      </description>
    </leaf>
    <leaf name="expire">
      <type name="dnspar:time-interval"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Upper limit on the time interval that can elapse before
	  the zone is no longer authoritative.
	</text>
      </description>
    </leaf>
    <leaf name="minimum">
      <type name="dnspar:time-interval"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Minimum TTL that should be exported with any RR from
	  this zone.
	</text>
      </description>
    </leaf>
  </grouping>

288
  <grouping name="a">
289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310
    <description>
      <text>
	RDATA content for 'A' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="address">
      <type name="inet:ipv4-address-no-zone"/>
      <mandatory value="true"/>
      <description>
	<text>
	  IPv4 address.
	</text>
      </description>
    </leaf>
  </grouping>

311
  <grouping name="cname">
312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333
    <description>
      <text>
	RDATA content for 'CNAME' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="cname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Canonical or primary name for the owner.
	</text>
      </description>
    </leaf>
  </grouping>

334
  <grouping name="hinfo">
335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365
    <description>
      <text>
	RDATA content for 'HINFO' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="cpu">
      <type name="dnspar:ascii-string"/>
      <mandatory value="true"/>
      <description>
	<text>
	  CPU type.
	</text>
      </description>
    </leaf>
    <leaf name="os">
      <type name="dnspar:ascii-string"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Operating system type.
	</text>
      </description>
    </leaf>
  </grouping>

366
  <grouping name="mb">
367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388
    <description>
      <text>
	RDATA content for 'MB' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="madname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Host which has the specified mailbox.
	</text>
      </description>
    </leaf>
  </grouping>

389
  <grouping name="md">
390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414
    <status value="obsolete"/>
    <description>
      <text>
	RDATA content for 'MD' Resource Record (obsolete,
	use MX).
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="madname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Host which has a mail agent for the domain which
	  should be able to deliver mail for the domain.
	</text>
      </description>
    </leaf>
  </grouping>

415
  <grouping name="mf">
416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440
    <status value="obsolete"/>
    <description>
      <text>
	RDATA content for 'MF' Resource Record (obsolete,
	use MX).
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="madname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Host which has a mail agent for the domain which
	  will accept mail for forwarding to the domain.
	</text>
      </description>
    </leaf>
  </grouping>

441
  <grouping name="mg">
442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464
    <description>
      <text>
	RDATA content for 'MG' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="mgmname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Mailbox which is a member of the mail group
	  specified by the domain name.
	</text>
      </description>
    </leaf>
  </grouping>

465
  <grouping name="minfo">
466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499
    <description>
      <text>
	RDATA content for 'MINFO' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="rmailbx">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Mailbox which is responsible for the mailing list
	  or mailbox.
	</text>
      </description>
    </leaf>
    <leaf name="emailbx">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Mailbox which is to receive error messages related
	  to the mailing list or mailbox specified by the
	  owner of the MINFO RR.
	</text>
      </description>
    </leaf>
  </grouping>

500
  <grouping name="mr">
501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523
    <description>
      <text>
	RDATA content for 'MR' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="newname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Mailbox which is the proper rename of the
	  specified mailbox.
	</text>
      </description>
    </leaf>
  </grouping>

524
  <grouping name="mx">
525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557
    <description>
      <text>
	RDATA content for 'MX' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="preference">
      <type name="uint16"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Preference given to this RR among others at the
	  same owner. Lower values are preferred.
	</text>
      </description>
    </leaf>
    <leaf name="exchange">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Host willing to act as a mail exchange for the
	  owner name.
	</text>
      </description>
    </leaf>
  </grouping>

558
  <grouping name="ns">
559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581
    <description>
      <text>
	RDATA content for 'NS' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="nsdname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Host which should be authoritative for the
	  specified domain.
	</text>
      </description>
    </leaf>
  </grouping>

582
  <grouping name="null">
583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606
    <description>
      <text>
	RDATA content for 'NULL' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="data">
      <type name="binary">
	<length value="0..65535"/>
      </type>
      <mandatory value="true"/>
      <description>
	<text>
	  Arbitrary data.
	</text>
      </description>
    </leaf>
  </grouping>

607
  <grouping name="ptr">
608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630
    <description>
      <text>
	RDATA content for 'PTR' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="ptrdname">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  A pointer to some location in the domain name
	  space.
	</text>
      </description>
    </leaf>
  </grouping>

631
  <grouping name="txt">
632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654
    <description>
      <text>
	RDATA content for 'TXT' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="txt-data">
      <type name="dnspar:ascii-string"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Descriptive text whose semantics depends on the
	  domain where it is found.
	</text>
      </description>
    </leaf>
  </grouping>

655
  <grouping name="wks">
656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696
    <description>
      <text>
	RDATA content for 'WKS' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 1035: Domain Names - Implementation and
	Specification.
      </text>
    </reference>
    <leaf name="address">
      <type name="inet:ipv4-address-no-zone"/>
      <mandatory value="true"/>
      <description>
	<text>
	  IPv4 address.
	</text>
      </description>
    </leaf>
    <leaf name="protocol">
      <type name="uint8"/>
      <mandatory value="true"/>
      <description>
	<text>
	  IP protocol number.
	</text>
      </description>
    </leaf>
    <leaf name="bitmap">
      <type name="binary"/>
      <mandatory value="true"/>
      <description>
	<text>
	  A variable length bitmap that has one bit per port
	  of the specified protocol.
	</text>
      </description>
    </leaf>
  </grouping>

697
  <grouping name="aaaa">
698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718
    <description>
      <text>
	RDATA content for 'AAAA' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 3596: DNS Extensions to Support IP Version 6
      </text>
    </reference>
    <leaf name="address">
      <type name="inet:ipv6-address-no-zone"/>
      <mandatory value="true"/>
      <description>
	<text>
	  IPv6 address.
	</text>
      </description>
    </leaf>
  </grouping>

719
  <grouping name="dnskey">
720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799
    <description>
      <text>
	RDATA content for 'DNSKEY' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 4034: Resource Records for the DNS Security
	Extensions
      </text>
    </reference>
    <leaf name="flags">
      <type name="dnspar:dnskey-flags"/>
      <must condition="not(contains(., 'ZONE')) or
		       ../../../owner = ../../../../name">
		       <description>
			 <text>
			   For a Zone Key, the DNSKEY RR's owner name MUST
			   be the name of a zone.
			 </text>
		       </description>
		       <error-message>
			 <value>
			   For a Zone Key, owner name must be the zone name.
			 </value>
		       </error-message>
      </must>
      <must condition="contains(., 'ZONE') or
		       not(contains(., 'SEP'))">
		       <description>
			 <text>
			   Secure Entry Point flag needs Zone Key flag.
			 </text>
		       </description>
		       <error-message>
			 <value>
			   'secure-entry-point' is set but 'zone-key' isn't
			 </value>
		       </error-message>
      </must>
      <description>
	<text>DNSKEY RR flags.</text>
      </description>
    </leaf>
    <leaf name="protocol">
      <type name="uint8">
	<range value="3"/>
      </type>
      <default value="3"/>
      <description>
	<text>
	  Protocol field. It's value MUST be 3.
	</text>
      </description>
    </leaf>
    <leaf name="algorithm">
      <type name="dnspar:dnssec-algorithm"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field identifies the public key's
	  cryptographic algorithm and determines the format
	  of the 'public-key' field.
	</text>
      </description>
    </leaf>
    <leaf name="public-key">
      <type name="binary">
	<length value="1..max"/>
      </type>
      <mandatory value="true"/>
      <description>
	<text>
	  This field contains public key material. Its
	  format depends on the algorithm.
	</text>
      </description>
    </leaf>
  </grouping>

800
  <grouping name="nsec">
801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826
    <description>
      <text>
	RDATA content for 'NSEC' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 4034: Resource Records for the DNS Security
	Extensions
      </text>
    </reference>
    <leaf name="next-domain-name">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field contains the next owner name (in the
	  canonical ordering of the zone) that has
	  authoritative data or contains a delegation point
	  NS RRset.
	</text>
      </description>
    </leaf>
    <uses name="rrset-types"/>
  </grouping>

827
  <grouping name="ds">
828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873
    <description>
      <text>
	RDATA content for 'DS' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 4034: Resource Records for the DNS Security
	Extensions
      </text>
    </reference>
    <uses name="key-tag-field"/>
    <leaf name="algorithm">
      <type name="dnspar:dnssec-algorithm"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field specifies the algorithm of the DNSKEY
	  RR referred to by the DS record.
	</text>
      </description>
    </leaf>
    <leaf name="digest-type">
      <type name="dnspar:digest-algorithm"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field identifies the algorithm used to
	  construct the digest of the DNSKEY RR.
	</text>
      </description>
    </leaf>
    <leaf name="digest">
      <type name="dnspar:hex-digits">
	<length value="1..max"/>
      </type>
      <mandatory value="true"/>
      <description>
	<text>
	  This field contains a digest of the DNSKEY RR to
	  which the DS RR refers.
	</text>
      </description>
    </leaf>
  </grouping>

874
  <grouping name="nsec3">
875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911
    <description>
      <text>
	RDATA content for 'NSEC3' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 5155: DNS Security (DNSSEC) Hashed Authenticated
	Denial of Existence
      </text>
    </reference>
    <uses name="nsec3-common"/>
    <leaf name="flags">
      <type name="dnspar:dnssec-nsec3-flags"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field contains flags that indicate different
	  processing of the NSEC3 RR data.
	</text>
      </description>
    </leaf>
    <leaf name="next-hashed-owner-name">
      <type name="dnspar:base32hex">
	<length value="8..408"/>
      </type>
      <mandatory value="true"/>
      <description>
	<text>
	  This field contains the next hashed owner name in
	  hash order.
	</text>
      </description>
    </leaf>
    <uses name="rrset-types"/>
  </grouping>

912
  <grouping name="nsec3param">
913 914 915 916 917 918 919 920 921 922 923 924 925 926
    <description>
      <text>
	RDATA content for 'NSEC3PARAM' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 5155: DNS Security (DNSSEC) Hashed Authenticated
	Denial of Existence
      </text>
    </reference>
    <uses name="nsec3-common"/>
  </grouping>

927
  <grouping name="tlsa">
928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993
    <description>
      <text>
	RDATA content for 'TLSA' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 6698: The DNS-Based Authentication of Named
	Entities (DANE) Transport Layer Security (TLS)
	Protocol: TLSA
      </text>
    </reference>
    <leaf name="certificate-usage">
      <type name="dnspar:tlsa-certificate-usages"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field specifies the provided association that
	  will be used to match the certificate presented in
	  the TLS handshake.
	</text>
      </description>
    </leaf>
    <leaf name="selector">
      <type name="dnspar:tlsa-selectors"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field specifies which part of the TLS
	  certificate presented by the server will be
	  matched against the association data.
	</text>
      </description>
    </leaf>
    <leaf name="matching-type">
      <type name="dnspar:tlsa-matching-type"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field specifies how the certificate
	  association is presented.
	</text>
      </description>
    </leaf>
    <leaf name="certificate-association-data">
      <type name="dnspar:hex-digits">
	<length value="1..max"/>
      </type>
      <mandatory value="true"/>
      <description>
	<text>
	  <h:p>This field specifies the "certificate association
	  data" to be matched.</h:p>
	  <h:p>These bytes are either raw data (that is, the
	  full certificate or its SubjectPublicKeyInfo,
	  depending on 'selector') for 'matching-type' 0, or
	  the hash of the raw data for 'matching-type' 1 and
	  2.</h:p>
	  <h:p>The data refers to the certificate in the
	  association, not to the TLS ASN.1 Certificate
	  object.</h:p>
	</text>
      </description>
    </leaf>
  </grouping>

994
  <grouping name="ipseckey">
995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080
    <description>
      <text>
	RDATA content for 'IPSECKEY' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 4025: A Method for Storing IPsec Keying Material
	in DNS
      </text>
    </reference>
    <leaf name="precedence">
      <type name="uint8"/>
      <mandatory value="true"/>
      <description>
	<text>
	  <h:p>Precedence of the resource record.</h:p>
	  <h:p>Gateways listed in IPSECKEY records with
	  lower precedence are to be attempted first.  Where
	  there is a tie in precedence, the order should be
	  non-deterministic.</h:p>
	</text>
      </description>
    </leaf>
    <leaf name="gateway-type">
      <type name="dnspar:ipseckey-gateway-type"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field indicates the format of the information
	  that is stored in the gateway field.
	</text>
      </description>
    </leaf>
    <leaf name="algorithm">
      <type name="dnspar:ipseckey-algorithm-type"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field identifies the public key's
	  cryptographic algorithm and determines the format
	  of the 'public-key' field.
	</text>
      </description>
    </leaf>
    <leaf name="gateway">
      <when condition="../gateway-type != 'no-gateway'">
	<description>
	  <text>
	    This field cannot be present if the value of
	    'gateway-type' is 'no-gateway'.
	  </text>
	</description>
      </when>
      <type name="inet:host"/>
      <mandatory value="true"/>
      <description>
	<text>
	  <h:p>This field indicates a gateway to which an IPsec
	  tunnel may be created in order to reach the entity
	  named by this resource record.</h:p>
	  <h:p>The format of this field MUST correspond to
	  the value set in 'gateway-type'.</h:p>
	</text>
      </description>
    </leaf>
    <leaf name="public-key">
      <when condition="../algorithm != 'no-key'">
	<description>
	  <text>
	    This field cannot be present if the value of
	    'algorithm' is 'no-key'.
	  </text>
	</description>
      </when>
      <type name="binary"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field contains the IPSec public key in a
	  format corresponding to the value of 'algorithm'.
	</text>
      </description>
    </leaf>
  </grouping>

1081
  <grouping name="dname">
1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103
    <description>
      <text>
	RDATA content for 'DNAME' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 2672: Non-Terminal DNS Name Redirection
      </text>
    </reference>
    <leaf name="target">
      <type name="domain-name"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Target domain name that is substituted for 'owner'
	  as a suffix of a domain name.
	</text>
      </description>
    </leaf>
  </grouping>

1104
  <grouping name="sshfp">
1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148
    <description>
      <text>
	RDATA content for 'SSHFP' Resource Record.
      </text>
    </description>
    <reference>
      <text>
	RFC 4255: Using DNS to Securely Publish Secure Shell
	(SSH) Key Fingerprints
      </text>
    </reference>
    <leaf name="algorithm">
      <type name="dnspar:sshfp-algorithm-type"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field specifies the algorithm of the public
	  key.
	</text>
      </description>
    </leaf>
    <leaf name="fingerprint-type">
      <type name="dnspar:sshfp-fingerprint-type"/>
      <mandatory value="true"/>
      <description>
	<text>
	  This field specifies the message-digest algorithm
	  used to calculate teh fingerprint of the public
	  key.
	</text>
      </description>
    </leaf>
    <leaf name="fingerprint">
      <type name="dnspar:hex-digits"/>
      <mandatory value="true"/>
      <description>
	<text>
	  Fingerprint of the public key.
	</text>
      </description>
    </leaf>
  </grouping>

</module>