Elia Battiston | 4750d3c | 2022-07-14 13:24:56 +0000 | [diff] [blame] | 1 | module bbf-if-type { |
| 2 | yang-version 1.1; |
| 3 | namespace "urn:bbf:yang:bbf-if-type"; |
| 4 | prefix bbfift; |
| 5 | |
| 6 | import iana-if-type { |
| 7 | prefix ianaift; |
| 8 | } |
| 9 | import ietf-interfaces { |
| 10 | prefix if; |
| 11 | } |
| 12 | |
| 13 | organization |
| 14 | "Broadband Forum <https://www.broadband-forum.org> |
| 15 | Common YANG Work Area"; |
| 16 | contact |
| 17 | "Comments or questions about this Broadband Forum YANG module |
| 18 | should be directed to <mailto:help@broadband-forum.org>. |
| 19 | |
| 20 | Editor: Nick Hancock, ADTRAN |
| 21 | |
| 22 | Editor: Ludwig Pauwels, Nokia |
| 23 | |
| 24 | PS Leader: Joey Boyd, ADTRAN |
| 25 | |
| 26 | PS Leader: Sowrirajan Padmanabhan, Nokia |
| 27 | |
| 28 | WA Director: Joey Boyd, ADTRAN |
| 29 | |
| 30 | WA Director: Sven Ooghe, Nokia"; |
| 31 | description |
| 32 | "This module contains a collection of YANG definitions for |
| 33 | supporting the Broadband Forum requirements on reusable data |
| 34 | types as applicable to access network equipment. As such, this |
| 35 | module is specific to access network equipment (e.g., |
| 36 | BBF-specified Access Nodes and FTTdp DPUs). |
| 37 | |
| 38 | Specifically, this module defines interface types that are needed |
| 39 | for BBF applications but are not defined in iana-if-type. |
| 40 | |
| 41 | Copyright (c) 2017-2020, Broadband Forum |
| 42 | |
| 43 | Redistribution and use in source and binary forms, with or |
| 44 | without modification, are permitted provided that the following |
| 45 | conditions are met: |
| 46 | |
| 47 | 1. Redistributions of source code must retain the above copyright |
| 48 | notice, this list of conditions and the following disclaimer. |
| 49 | |
| 50 | 2. Redistributions in binary form must reproduce the above |
| 51 | copyright notice, this list of conditions and the following |
| 52 | disclaimer in the documentation and/or other materials |
| 53 | provided with the distribution. |
| 54 | |
| 55 | 3. Neither the name of the copyright holder nor the names of its |
| 56 | contributors may be used to endorse or promote products |
| 57 | derived from this software without specific prior written |
| 58 | permission. |
| 59 | |
| 60 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND |
| 61 | CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, |
| 62 | INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF |
| 63 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE |
| 64 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR |
| 65 | CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, |
| 66 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT |
| 67 | NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; |
| 68 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER |
| 69 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, |
| 70 | STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) |
| 71 | ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF |
| 72 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
| 73 | |
| 74 | The above license is used as a license under copyright only. |
| 75 | Please reference the Forum IPR Policy for patent licensing terms |
| 76 | <https://www.broadband-forum.org/ipr-policy>. |
| 77 | |
| 78 | Any moral rights which are necessary to exercise under the above |
| 79 | license grant are also deemed granted under this license. |
| 80 | |
| 81 | This version of this YANG module is part of TR-383a3; see |
| 82 | the TR itself for full legal notices."; |
| 83 | |
| 84 | revision 2020-10-13 { |
| 85 | description |
| 86 | "Amendment 3. |
| 87 | * Approval Date: 2020-10-13. |
| 88 | * Publication Date: 2020-10-13."; |
| 89 | reference |
| 90 | "TR-383a3: Common YANG Modules |
| 91 | <https://www.broadband-forum.org/technical/download/ |
| 92 | TR-383_Amendment-3.pdf>"; |
| 93 | } |
| 94 | revision 2018-12-03 { |
| 95 | description |
| 96 | "Amendment 2. |
| 97 | * Approval Date: 2018-12-03. |
| 98 | * Publication Date: 2018-12-03."; |
| 99 | reference |
| 100 | "TR-383a2: Common YANG Modules |
| 101 | <https://www.broadband-forum.org/technical/download/ |
| 102 | TR-383_Amendment-2.pdf>"; |
| 103 | } |
| 104 | revision 2018-07-13 { |
| 105 | description |
| 106 | "Amendment 1. |
| 107 | * Approval Date: 2018-06-04. |
| 108 | * Publication Date: see revision date above."; |
| 109 | reference |
| 110 | "TR-383: Common YANG Modules |
| 111 | <https://www.broadband-forum.org/technical/download/ |
| 112 | TR-383_Amendment-1.pdf>"; |
| 113 | } |
| 114 | revision 2017-05-08 { |
| 115 | description |
| 116 | "Initial revision. |
| 117 | * Approval Date: see revision date above. |
| 118 | * Publication Date: 2017-06-02."; |
| 119 | reference |
| 120 | "TR-383: Common YANG Modules |
| 121 | <https://www.broadband-forum.org/technical/download/ |
| 122 | TR-383.pdf>"; |
| 123 | } |
| 124 | |
| 125 | identity bbf-interface-type { |
| 126 | base if:interface-type; |
| 127 | description |
| 128 | "This identity is used as a base for all interface types |
| 129 | defined by the BBF that are not in the 'ifType definitions' |
| 130 | registry maintained by IANA."; |
| 131 | } |
| 132 | |
| 133 | identity sub-interface { |
| 134 | base bbf-interface-type; |
| 135 | description |
| 136 | "Base type for generic sub-interfaces. "; |
| 137 | } |
| 138 | |
| 139 | identity vlan-sub-interface { |
| 140 | base ianaift:l2vlan; |
| 141 | base sub-interface; |
| 142 | description |
| 143 | "A sub-interface which carries traffic that is parsed for VLAN |
| 144 | tags. I.e. either the frames carries VLAN tags, or the first |
| 145 | Ethertype differs from one of the VLAN TPIDs defined by IEEE |
| 146 | and then the frame is considered as untagged. "; |
| 147 | } |
| 148 | |
| 149 | identity l2-termination { |
| 150 | base bbf-interface-type; |
| 151 | description |
| 152 | "An interface which terminates layer 2 traffic without the |
| 153 | need to be associated with any Ethernet-like interface."; |
| 154 | } |
| 155 | |
| 156 | identity ethernet-like { |
| 157 | base bbf-interface-type; |
| 158 | description |
| 159 | "An abstract identity defining a class of interfaces which |
| 160 | represents a logical interface transporting Ethernet frames, |
| 161 | i.e. frames with a destination and source MAC address, an |
| 162 | Ethernet type or length field, and a payload. This |
| 163 | 'interface type' is intended only to be used to define |
| 164 | constraints against a class of interfaces each of which have |
| 165 | their 'type' derived from this identity (as well as potentially |
| 166 | others). At no time should this identity be used as the 'type' |
| 167 | for an interface."; |
| 168 | } |
| 169 | } |