idnits 2.17.1 draft-kwatsen-netconf-http-client-server-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (April 29, 2019) is 1817 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NETCONF Working Group K. Watsen 3 Internet-Draft Watsen Networks 4 Intended status: Standards Track April 29, 2019 5 Expires: October 31, 2019 7 YANG Groupings for HTTP Clients and HTTP Servers 8 draft-kwatsen-netconf-http-client-server-02 10 Abstract 12 This document defines two YANG modules: the first defines a grouping 13 for configuring a generic HTTP client, and the second defines a 14 grouping for configuring a generic HTTP server. It is intended that 15 these groupings will be used by applications using the HTTP protocol. 17 Editorial Note (To be removed by RFC Editor) 19 This draft contains many placeholder values that need to be replaced 20 with finalized values at the time of publication. This note 21 summarizes all of the substitutions that are needed. No other RFC 22 Editor instructions are specified elsewhere in this document. 24 Artwork in this document contains placeholder values for the date of 25 publication of this draft. Please apply the following replacement: 27 o "2019-04-29" --> the publication date of this draft 29 The following Appendix section is to be removed prior to publication: 31 o Appendix A. Change Log 33 Status of This Memo 35 This Internet-Draft is submitted in full conformance with the 36 provisions of BCP 78 and BCP 79. 38 Internet-Drafts are working documents of the Internet Engineering 39 Task Force (IETF). Note that other groups may also distribute 40 working documents as Internet-Drafts. The list of current Internet- 41 Drafts is at https://datatracker.ietf.org/drafts/current/. 43 Internet-Drafts are draft documents valid for a maximum of six months 44 and may be updated, replaced, or obsoleted by other documents at any 45 time. It is inappropriate to use Internet-Drafts as reference 46 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on October 31, 2019. 50 Copyright Notice 52 Copyright (c) 2019 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (https://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 68 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 3. The HTTP Client Model . . . . . . . . . . . . . . . . . . . . 3 70 3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3 71 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 4 72 3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 5 73 4. The HTTP Server Model . . . . . . . . . . . . . . . . . . . . 12 74 4.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 12 75 4.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 12 76 4.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 12 77 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17 78 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 79 6.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 18 80 6.2. The YANG Module Names Registry . . . . . . . . . . . . . 18 81 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 82 7.1. Normative References . . . . . . . . . . . . . . . . . . 18 83 7.2. Informative References . . . . . . . . . . . . . . . . . 19 84 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19 86 1. Introduction 88 This document defines two YANG 1.1 [RFC7950] modules: the first 89 defines a grouping for configuring a generic HTTP client, and the 90 second defines a grouping for configuring a generic HTTP server. It 91 is intended that these groupings will be used by applications using 92 the HTTP protocol. 94 2. Terminology 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 98 "OPTIONAL" in this document are to be interpreted as described in BCP 99 14 [RFC2119] [RFC8174] when, and only when, they appear in all 100 capitals, as shown here. 102 3. The HTTP Client Model 104 3.1. Tree Diagram 106 This section provides a tree diagram [RFC8340] for the "ietf-http- 107 client" module. 109 module: ietf-http-client 111 grouping http-client-grouping 112 +-- protocol-version? enumeration 113 +-- client-identity 114 | +-- (auth-type)? 115 | +--:(basic) 116 | | +-- basic {basic-auth}? 117 | | +-- user-id? string 118 | | +-- password? string 119 | +--:(bearer) 120 | | +-- bearer {bearer-auth}? 121 | | +-- token? string 122 | +--:(digest) 123 | | +-- digest {digest-auth}? 124 | | +-- username? string 125 | | +-- password? string 126 | +--:(hoba) 127 | | +-- hoba {hoba-auth}? 128 | +--:(mutual) 129 | | +-- mutual {mutual-auth}? 130 | +--:(negotiate) 131 | | +-- negotiate {negotiate-auth}? 132 | +--:(oauth) 133 | | +-- oauth {oauth-auth}? 134 | +--:(scram-sha-1) 135 | | +-- scram-sha-1 {scram-sha-1-auth}? 136 | +--:(scram-sha-256) 137 | | +-- scram-sha-256 {scram-sha-256-auth}? 138 | +--:(vapid) 139 | +-- vapid {vapid-auth}? 140 +-- proxy-server! {proxy-connect}? 141 +-- tcp-client-parameters 142 | +---u tcpc:tcp-client-grouping 143 +-- tls-client-parameters 144 | +---u tlsc:tls-client-grouping 145 +-- proxy-client-identity 146 +-- user-id? string 147 +-- password? string 149 3.2. Example Usage 151 This section presents an example showing the http-client-grouping 152 populated with some data. 154 155 HTTP/1.1 156 157 158 bob 159 secret 160 161 162 164 3.3. YANG Module 166 This YANG module has normative references to [RFC6991]. 168 file "ietf-http-client@2019-04-29.yang" 169 module ietf-http-client { 170 yang-version 1.1; 171 namespace "urn:ietf:params:xml:ns:yang:ietf-http-client"; 172 prefix httpc; 174 import ietf-tcp-client { 175 prefix tcpc; 176 reference 177 "RFC AAAA: YANG Groupings for TCP Clients and TCP Servers"; 178 } 180 import ietf-tls-client { 181 prefix tlsc; 182 reference 183 "RFC BBBB: YANG Groupings for TLS Clients and TLS Servers"; 184 } 186 import ietf-netconf-acm { 187 prefix nacm; 188 reference 189 "RFC 8341: Network Configuration Access Control Model"; 190 } 192 organization 193 "IETF NETCONF (Network Configuration) Working Group"; 195 contact 196 "WG Web: 197 WG List: 198 Author: Kent Watsen "; 200 description 201 "This module defines reusable groupings for HTTP clients that 202 can be used as a basis for specific HTTP client instances. 204 Copyright (c) 2019 IETF Trust and the persons identified 205 as authors of the code. All rights reserved. 207 Redistribution and use in source and binary forms, with 208 or without modification, is permitted pursuant to, and 209 subject to the license terms contained in, the Simplified 210 BSD License set forth in Section 4.c of the IETF Trust's 211 Legal Provisions Relating to IETF Documents 212 (https://trustee.ietf.org/license-info). 214 This version of this YANG module is part of RFC XXXX 215 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 216 itself for full legal notices.; 218 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 219 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 220 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 221 are to be interpreted as described in BCP 14 (RFC 2119) 222 (RFC 8174) when, and only when, they appear in all 223 capitals, as shown here."; 225 revision 2019-04-29 { 226 description 227 "Initial version"; 228 reference 229 "RFC XXXX: YANG Groupings for HTTP Clients and HTTP Servers"; 230 } 232 // Features 234 feature proxy-connect { 235 description 236 "Proxy connection configuration is configurable for 237 HTTP clients on the server implementing this feature."; 238 } 240 feature basic-auth { 241 description 242 "fixme"; 243 } 245 feature bearer-auth { 246 description 247 "fixme"; 248 } 249 feature digest-auth { 250 description 251 "fixme"; 252 } 254 feature hoba-auth { 255 description 256 "fixme"; 257 } 259 feature mutual-auth { 260 description 261 "fixme"; 262 } 264 feature negotiate-auth { 265 description 266 "fixme"; 267 } 269 feature oauth-auth { 270 description 271 "fixme"; 272 } 274 feature scram-sha-1-auth { 275 description 276 "fixme"; 277 } 279 feature scram-sha-256-auth { 280 description 281 "fixme"; 282 } 284 feature vapid-auth { 285 description 286 "fixme"; 287 } 289 // Groupings 291 grouping http-client-grouping { 292 description 293 "A reusable grouping for configuring a HTTP client, 294 including the IP address and port number it initiates 295 a connections to. 297 Note that this grouping uses fairly typical descendent 298 node names such that a stack of 'uses' statements will 299 have name conflicts. It is intended that the consuming 300 data model will resolve the issue (e.g., by wrapping 301 the 'uses' statement in a container called 302 'http-client-parameters'). This model purposely does 303 not do this itself so as to provide maximum flexibility 304 to consuming models."; 306 leaf protocol-version { 307 nacm:default-deny-write; 308 type enumeration { 309 enum HTTP/1.0 { 310 description 311 "The client should use the 'HTTP/1.0' protocol."; 312 } 313 enum HTTP/1.1 { 314 description 315 "The client should use the 'HTTP/1.1' protocol."; 316 } 317 enum HTTP/2.0 { 318 description 319 "The client should use the 'HTTP/2.0' protocol."; 320 } 321 } 322 description 323 "The HTTP protocol version the client should use."; 324 } // leaf protocol-version 326 container client-identity { 327 nacm:default-deny-write; 328 description 329 "The credentials used by the client to authenticate to 330 the HTTP server."; 331 choice auth-type { 332 description 333 "The authentication type."; 334 container basic { 335 if-feature "basic-auth"; 336 leaf user-id { 337 type string; 338 description 339 "The user-id for the authenticating client."; 340 } 341 leaf password { 342 nacm:default-deny-all; 343 type string; 344 description 345 "The password for the authenticating client."; 346 } 347 description 348 "The 'basic' HTTP scheme credentials."; 349 reference 350 "RFC 7617: The 'Basic' HTTP Authentication Scheme"; 351 } 352 container bearer { 353 if-feature "bearer-auth"; 354 leaf token { 355 type string; 356 description 357 "The bearer token for the authenticating client, 358 encoded in base64, as described in RFC 6750, 359 Section 2.1."; 360 } 361 description 362 "The 'bearer' HTTP scheme credentials."; 363 reference 364 "RFC 6750: The OAuth 2.0 Authorization Framework: 365 Bearer Token Usage"; 366 } 367 container digest { 368 if-feature "digest-auth"; 369 leaf username { 370 type string; 371 description 372 "The username for the authenticating client."; 373 } 374 leaf password { 375 nacm:default-deny-all; 376 type string; 377 description 378 "The password for the authenticating client."; 379 } 380 description 381 "The 'digest' HTTP scheme credentials."; 382 reference 383 "RFC 7616: HTTP Digest Access Authentication"; 384 } 385 container hoba { 386 if-feature "hoba-auth"; 387 // FIXME 388 description 389 "The 'hoba' HTTP scheme credentials."; 390 reference 391 "RFC 7486: HTTP Origin-Bound Authentication (HOBA)"; 392 } 393 container mutual { 394 if-feature "mutual-auth"; 395 // FIXME 396 description 397 "The 'mutual' HTTP scheme credentials."; 398 reference 399 "RFC 8120: Mutual Authentication Protocol for HTTP"; 400 } 401 container negotiate { 402 if-feature "negotiate-auth"; 403 // FIXME 404 description 405 "The 'negotiate' HTTP scheme credentials."; 406 reference 407 "RFC 4559: SPNEGO-based Kerberos and NTLM HTTP 408 Authentication in Microsoft Windows"; 409 } 410 container oauth { 411 if-feature "oauth-auth"; 412 // FIXME 413 description 414 "The 'oauth' HTTP scheme credentials."; 415 reference 416 "RFC 6749: The OAuth 2.0 Authorization Framework"; 417 } 418 container scram-sha-1 { 419 if-feature "scram-sha-1-auth"; 420 // FIXME 421 description 422 "The 'scram-sha-1' HTTP scheme credentials."; 423 reference 424 "RFC 7804: Salted Challenge Response HTTP 425 Authentication Mechanism"; 426 } 427 container scram-sha-256 { 428 if-feature "scram-sha-256-auth"; 429 // FIXME 430 description 431 "The 'scram-sha-256' HTTP scheme credentials."; 432 reference 433 "RFC 7804: Salted Challenge Response HTTP 434 Authentication Mechanism"; 435 } 436 container vapid { 437 if-feature "vapid-auth"; 438 // FIXME 439 description 440 "The 'vapid' HTTP scheme credentials."; 442 reference 443 "RFC 8292: Voluntary Application Server 444 Identification (VAPID) for Web Push"; 445 } 446 } 447 } // container client-identity 449 container proxy-server { 450 nacm:default-deny-write; 451 if-feature "proxy-connect"; 452 presence true; // only so ex-http-client can pass validation? 453 container tcp-client-parameters { 454 description 455 "A wrapper around the TCP parameters to avoid 456 name collisions."; 457 uses "tcpc:tcp-client-grouping"; 458 } 459 container tls-client-parameters { 460 description 461 "A wrapper around the TLS parameters to avoid 462 name collisions."; 463 uses "tlsc:tls-client-grouping"; 464 } 465 container proxy-client-identity { 466 leaf user-id { 467 type string; 468 description 469 "The user-id for the authenticating client."; 470 } 471 leaf password { 472 nacm:default-deny-all; 473 type string; 474 description 475 "The password for the authenticating client."; 476 } 477 description 478 "The 'basic' HTTP scheme credentials."; 479 reference 480 "RFC 7617: The 'Basic' HTTP Authentication Scheme"; 481 } 482 description 483 "Proxy server settings."; 484 } // container proxy-server 485 } //grouping http-client-grouping 486 } 487 489 4. The HTTP Server Model 491 4.1. Tree Diagram 493 This section provides a tree diagram [RFC8340] for the "ietf-http- 494 server" module. 496 module: ietf-http-server 498 grouping http-server-grouping 499 +-- server-name? string 500 +-- protocol-versions 501 | +-- protocol-version* enumeration 502 +-- client-authentication! 503 +-- (required-or-optional) 504 | +--:(required) 505 | | +-- required? empty 506 | +--:(optional) 507 | +-- optional? empty 508 +-- (local-or-external) 509 +--:(local) {local-client-auth-supported}? 510 | +-- users 511 | +-- user* [name] 512 | +-- name? string 513 | +-- password? ianach:crypt-hash 514 +--:(external) {external-client-auth-supported}? 515 +-- client-auth-defined-elsewhere? empty 517 4.2. Example Usage 519 This section presents an example showing the http-server-grouping 520 populated with some data. 522 523 foo.example.com 524 525 HTTP/1.1 526 HTTP/2.0 527 528 530 4.3. YANG Module 532 This YANG module has normative references to [RFC6991]. 534 file "ietf-http-server@2019-04-29.yang" 535 module ietf-http-server { 536 yang-version 1.1; 537 namespace "urn:ietf:params:xml:ns:yang:ietf-http-server"; 538 prefix https; 540 import iana-crypt-hash { 541 prefix ianach; 542 reference 543 "RFC 7317: A YANG Data Model for System Management"; 544 } 546 import ietf-netconf-acm { 547 prefix nacm; 548 reference 549 "RFC 8341: Network Configuration Access Control Model"; 550 } 552 organization 553 "IETF NETCONF (Network Configuration) Working Group"; 555 contact 556 "WG Web: 557 WG List: 558 Author: Kent Watsen "; 560 description 561 "This module defines reusable groupings for HTTP servers that 562 can be used as a basis for specific HTTP server instances. 564 Copyright (c) 2019 IETF Trust and the persons identified 565 as authors of the code. All rights reserved. 567 Redistribution and use in source and binary forms, with 568 or without modification, is permitted pursuant to, and 569 subject to the license terms contained in, the Simplified 570 BSD License set forth in Section 4.c of the IETF Trust's 571 Legal Provisions Relating to IETF Documents 572 (https://trustee.ietf.org/license-info). 574 This version of this YANG module is part of RFC XXXX 575 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 576 itself for full legal notices.; 578 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 579 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 580 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 581 are to be interpreted as described in BCP 14 (RFC 2119) 582 (RFC 8174) when, and only when, they appear in all 583 capitals, as shown here."; 585 revision 2019-04-29 { 586 description 587 "Initial version"; 588 reference 589 "RFC XXXX: YANG Groupings for HTTP Clients and HTTP Servers"; 590 } 592 // Features 594 feature local-client-auth-supported { 595 description 596 "Indicates that the HTTP server supports local configuration 597 of client credentials."; 598 } 600 feature external-client-auth-supported { 601 description 602 "Indicates that the HTTP server supports external configuration 603 of client credentials."; 604 } 606 // Groupings 608 grouping http-server-grouping { 609 description 610 "A reusable grouping for configuring an HTTP server. 612 Note that this grouping uses fairly typical descendent 613 node names such that a stack of 'uses' statements will 614 have name conflicts. It is intended that the consuming 615 data model will resolve the issue (e.g., by wrapping 616 the 'uses' statement in a container called 617 'http-server-parameters'). This model purposely does 618 not do this itself so as to provide maximum flexibility 619 to consuming models."; 621 leaf server-name { 622 nacm:default-deny-write; 623 type string; 624 description 625 "The value of the 'Server' header field. If not set, then 626 underlying software's default value is used. Set to the 627 empty string to disable."; 628 } 630 container protocol-versions { 631 nacm:default-deny-write; 632 description 633 "A list of HTTP protocol versions supported by this 634 server."; 635 leaf-list protocol-version { 636 type enumeration { 637 enum "HTTP/1.0" { 638 description 639 "The server supports the 'HTTP/1.0' protocol."; 640 } 641 enum "HTTP/1.1" { 642 description 643 "The server supports the 'HTTP/1.1' protocol."; 644 } 645 enum "HTTP/2.0" { 646 description 647 "The server supports the 'HTTP/2.0' protocol."; 648 } 649 } 650 description 651 "An HTTP protocol version supported by this server."; 652 } 653 } 655 container client-authentication { 656 nacm:default-deny-write; 657 presence 658 "Indicates that HTTP based client authentication is 659 supported (i.e., the server will request that the 660 HTTP client send authenticate when needed). This 661 is needed as some HTTP-based protocols may only 662 support, e.g., TLS-level client authentication."; 663 description 664 "Specifies if HTTP client authentication is required or 665 optional, and specifies if the credentials needed to 666 authenticate the HTTP client are configured locally 667 or externally."; 668 choice required-or-optional { 669 mandatory true; // or default to 'required' ? 670 description 671 "Indicates if HTTP-level client authentication is required 672 or optional. This is necessary for some protocols (e.g., 673 RESTCONF) that may optionally authenticate a client via 674 TLS-level authentication, HTTP-level authentication, or 675 both simultaneously)."; 676 leaf required { 677 type empty; 678 description 679 "Indicates that HTTP-level client authentication is 680 required to access protected resources."; 681 } 682 leaf optional { 683 type empty; 684 description 685 "Indicates that HTTP-level client authentication is 686 optional to access protected resources."; 687 } 688 } 689 choice local-or-external { 690 mandatory true; 691 description 692 "Indicates if the client credentials are configured 693 locally or externally. The need to support external 694 configuration for client authentication stems from 695 the desire to support consuming data models that 696 prefer to place client authentication with client 697 definitions, rather then in a data model principly 698 concerned with configuring the transport."; 699 case local { 700 if-feature "local-client-auth-supported"; 701 description 702 "Client credentials are configured locally."; 703 container users { 704 description 705 "A list of locally configured users."; 706 list user { 707 key name; 708 description 709 "The list of local users configured on this device."; 711 leaf name { 712 type string; 713 description 714 "The user name string identifying this entry."; 715 } 716 leaf password { 717 type ianach:crypt-hash; 718 description 719 "The password for this entry."; 720 } 721 } 722 } 723 } 724 case external { 725 if-feature "external-client-auth-supported"; 726 description 727 "Client credentials are configured externally."; 729 leaf client-auth-defined-elsewhere { 730 type empty; 731 description 732 "Indicates that credentials needed to authenticate 733 clients are configured elsewhere."; 734 } 735 } 736 } // choice local-or-external 737 } // container client-authentication 739 } 740 } 741 743 5. Security Considerations 745 The YANG modules defined in this document are designed to be accessed 746 via YANG based management protocols, such as NETCONF [RFC6241] and 747 RESTCONF [RFC8040]. Both of these protocols have mandatory-to- 748 implement secure transport layers (e.g., SSH, HTTP) with mutual 749 authentication. 751 The NETCONF access control model (NACM) [RFC8341] provides the means 752 to restrict access for particular users to a pre-configured subset of 753 all available protocol operations and content. 755 Since the modules defined in this document only define groupings, 756 these considerations are primarily for the designers of other modules 757 that use these groupings. 759 There are a number of data nodes defined in the YANG modules that are 760 writable/creatable/deletable (i.e., config true, which is the 761 default). These data nodes may be considered sensitive or vulnerable 762 in some network environments. Write operations (e.g., edit-config) 763 to these data nodes without proper protection can have a negative 764 effect on network operations. These are the subtrees and data nodes 765 and their sensitivity/vulnerability: 767 FIXME: (pending - TBD) 769 Some of the readable data nodes in the YANG modules may be considered 770 sensitive or vulnerable in some network environments. It is thus 771 important to control read access (e.g., via get, get-config, or 772 notification) to these data nodes. These are the subtrees and data 773 nodes and their sensitivity/vulnerability: 775 FIXME: (pending client auth params?) 777 Some of the RPC operations in this YANG module may be considered 778 sensitive or vulnerable in some network environments. It is thus 779 important to control access to these operations. These are the 780 operations and their sensitivity/vulnerability: 782 The modules defined in this document do not define any 'RPC' or 783 'action' statements. 785 6. IANA Considerations 787 6.1. The IETF XML Registry 789 This document registers two URIs in the "ns" subregistry of the IETF 790 XML Registry [RFC3688]. Following the format in [RFC3688], the 791 following registrations are requested: 793 URI: urn:ietf:params:xml:ns:yang:ietf-http-client 794 Registrant Contact: The NETCONF WG of the IETF. 795 XML: N/A, the requested URI is an XML namespace. 797 URI: urn:ietf:params:xml:ns:yang:ietf-http-server 798 Registrant Contact: The NETCONF WG of the IETF. 799 XML: N/A, the requested URI is an XML namespace. 801 6.2. The YANG Module Names Registry 803 This document registers two YANG modules in the YANG Module Names 804 registry [RFC6020]. Following the format in [RFC6020], the following 805 registrations are requested: 807 name: ietf-http-client 808 namespace: urn:ietf:params:xml:ns:yang:ietf-http-client 809 prefix: httpc 810 reference: RFC XXXX 812 name: ietf-http-server 813 namespace: urn:ietf:params:xml:ns:yang:ietf-http-server 814 prefix: https 815 reference: RFC XXXX 817 7. References 819 7.1. Normative References 821 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 822 Requirement Levels", BCP 14, RFC 2119, 823 DOI 10.17487/RFC2119, March 1997, 824 . 826 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 827 the Network Configuration Protocol (NETCONF)", RFC 6020, 828 DOI 10.17487/RFC6020, October 2010, 829 . 831 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 832 RFC 6991, DOI 10.17487/RFC6991, July 2013, 833 . 835 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 836 RFC 7950, DOI 10.17487/RFC7950, August 2016, 837 . 839 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 840 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 841 May 2017, . 843 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 844 Access Control Model", STD 91, RFC 8341, 845 DOI 10.17487/RFC8341, March 2018, 846 . 848 7.2. Informative References 850 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 851 DOI 10.17487/RFC3688, January 2004, 852 . 854 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 855 and A. Bierman, Ed., "Network Configuration Protocol 856 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 857 . 859 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 860 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 861 . 863 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 864 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 865 . 867 Author's Address 869 Kent Watsen 870 Watsen Networks 872 EMail: kent+ietf@watsen.net