module ietf-tcp-client {

    yang-version 1.1;

    namespace
      "urn:ietf:params:xml:ns:yang:ietf-tcp-client";

    prefix tcpc;

    import ietf-inet-types {
      prefix inet;
      reference
        "RFC 6991: Common YANG Data Types";


    }
    import ietf-crypto-types {
      prefix ct;
      reference
        "RFC 9640: YANG Data Types and Groupings for Cryptography";


    }
    import ietf-tcp-common {
      prefix tcpcmn;
      reference
        "RFC 9643: YANG Groupings for TCP Clients and TCP Servers";


    }

    organization
      "IETF NETCONF (Network Configuration) Working Group and the
     IETF TCP Maintenance and Minor Extensions (TCPM) Working Group";

    contact
      "WG Web:   https://datatracker.ietf.org/wg/netconf
               https://datatracker.ietf.org/wg/tcpm
     WG List:  NETCONF WG list <mailto:netconf@ietf.org>
               TCPM WG list <mailto:tcpm@ietf.org>
     Authors:  Kent Watsen <mailto:kent+ietf@watsen.net>
               Michael Scharf
               <mailto:michael.scharf@hs-esslingen.de>";

    description
      "This module defines reusable groupings for TCP clients that
     can be used as a basis for specific TCP client instances.

     The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
     'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
     'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
     are to be interpreted as described in BCP 14 (RFC 2119)
     (RFC 8174) when, and only when, they appear in all
     capitals, as shown here.

     Copyright (c) 2024 IETF Trust and the persons identified
     as authors of the code.  All rights reserved.

     Redistribution and use in source and binary forms, with
     or without modification, is permitted pursuant to, and
     subject to the license terms contained in, the Revised
     BSD License set forth in Section 4.c of the IETF Trust's
     Legal Provisions Relating to IETF Documents
     (https://trustee.ietf.org/license-info).

     This version of this YANG module is part of RFC 9643
     (https://www.rfc-editor.org/info/rfc9643); see the RFC
     itself for full legal notices.";

    revision "2024-10-10" {
      description "Initial version.";
      reference
        "RFC 9643: YANG Groupings for TCP Clients and TCP Servers";

    }


    feature local-binding-supported {
      description
        "Indicates that the server supports configuring local
       bindings (i.e., the local address and local port) for
       TCP clients.";
    }

    feature tcp-client-keepalives {
      description
        "TCP keepalive parameters are configurable for
       TCP clients on the server implementing this feature.";
      reference
        "RFC 9293: Transmission Control Protocol (TCP)";

    }

    feature proxy-connect {
      description
        "Indicates the TCP client supports connecting through
       TCP proxies.";
    }

    feature socks4-supported {
      if-feature proxy-connect;
      description
        "Indicates the TCP client supports Socks4-based proxies.";
      reference
        "SOCKS Proceedings: 1992 Usenix Security Symposium";

    }

    feature socks4a-supported {
      if-feature proxy-connect;
      description
        "Indicates the TCP client supports Socks4a-based proxies.";
      reference
        "OpenSSH message:
          SOCKS 4A: A Simple Extension to SOCKS 4 Protocol
          <https://www.openssh.com/txt/socks4a.protocol>";

    }

    feature socks5-supported {
      if-feature proxy-connect;
      description
        "Indicates the TCP client supports Socks5-based proxies.";
      reference
        "RFC 1928: SOCKS Protocol Version 5";

    }

    feature socks5-gss-api {
      if-feature socks5-supported;
      description
        "Indicates that the server, when acting as a TCP client,
       supports authenticating to a SOCKS Version 5 proxy server
       using GSS-API credentials.";
      reference
        "RFC 1928: SOCKS Protocol Version 5";

    }

    feature socks5-username-password {
      if-feature socks5-supported;
      description
        "Indicates that the server, when acting as a TCP client,
       supports authenticating to a SOCKS Version 5 proxy server
       using 'username' and 'password' credentials.";
      reference
        "RFC 1928: SOCKS Protocol Version 5";

    }
  }  // module ietf-tcp-client