module bbf-subscriber-profile-common {

    yang-version 1.1;

    namespace
      "urn:bbf:yang:bbf-subscriber-profile-common";

    prefix bbf-subprof-pc;

    import bbf-yang-types {
      prefix bbf-yang;
    }

    organization
      "Broadband Forum <https://www.broadband-forum.org>
Common YANG Work Area";

    contact
      "Comments or questions about this Broadband Forum YANG module
should be directed to <mailto:help@broadband-forum.org>.

Editor:      Nick Hancock, Adtran

Editor:      Ludwig Pauwels, Nokia

PS Leader:   Joey Boyd, Adtran

WA Director: Joey Boyd, Adtran

WA Director: Sven Ooghe, Nokia";

    description
      "This module contains a collection of common YANG definitions for
supporting the Broadband Forum requirements on the management of
subscribers as applicable to access network equipment. As such,
this module is specific to access network equipment (e.g.,
BBF-specified Access Nodes and FTTdp DPUs).

Specifically, this module contains the definition of a profile
for subscriber information used by a L2 DHCP Relay Agent,
Lightweight DHCPv6 Relay Agent, PPPoE Intermediate Agent, or
another Agent in creating an Agent Circuit ID and Remote ID as
described in TR-101i2.

Copyright (c) 2017-2023, Broadband Forum

Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:

1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above
   copyright notice, this list of conditions and the following
   disclaimer in the documentation and/or other materials
   provided with the distribution.

3. Neither the name of the copyright holder nor the names of its
   contributors may be used to endorse or promote products
   derived from this software without specific prior written
   permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The above license is used as a license under copyright only.
Please reference the Forum IPR Policy for patent licensing terms
<https://www.broadband-forum.org/ipr-policy>.

Any moral rights which are necessary to exercise under the above
license grant are also deemed granted under this license.

This version of this YANG module is part of TR-383a7; see
the TR itself for full legal notices.";

    revision "2023-12-15" {
      description
        "Amendment 7.
* Approval Date:    2023-12-15.
* Publication Date: 2023-12-15.";
      reference
        "TR-383a7: Common YANG Modules
        	  <https://www.broadband-forum.org/technical/download/
        		   TR-383_Amendment-7.pdf>";

    }


    grouping subscriber-profiles {
      description
        "Subscriber configuration profiles.";
      container subscriber-profiles {
        description
          "Subscriber configuration profiles.";
        list subscriber-profile {
          key "name";
          description
            "A subscriber configuration profile.

Various protocols need to insert strings in options /
sub-tags. These strings are used to identify the
subscriber.

This insertion can be enabled per protocol per VLAN
sub-interface. Identifying the subscriber is independent of
the protocol and most likely identical for all VLAN
sub-interfaces on top of the same physical line. Therefore
this data is provided in a profile.";
          leaf name {
            type bbf-yang:string-ascii64;
            description
              "Name of the profile.";
          }

          leaf circuit-id {
            type bbf-yang:string-ascii63-or-empty;
            default "";
            description
              "The circuit ID string to be inserted in the subscriber
management protocol packets.";
            reference
              "TR-178 R-117;
              TR-177 R-08";

          }

          leaf remote-id {
            type bbf-yang:string-ascii63-or-empty;
            default "";
            description
              "The remote-id string to be inserted in the subscriber
management protocol packets.";
            reference
              "TR-178 R-120;
              TR-177 R-10";

          }

          leaf subscriber-id {
            type bbf-yang:string-ascii63-or-empty;
            default "";
            description
              "A subscriber-id string to be inserted in the subscriber
management protocol packets.

The subscriber-id carries a value that can be independent
of the physical network configuration through which the
subscriber is connected. This value complements, and
might well be used in addition to the network-based
information.";
            reference
              "RFC 4580 Section 2";

          }
        }  // list subscriber-profile
      }  // container subscriber-profiles
    }  // grouping subscriber-profiles
  }  // module bbf-subscriber-profile-common