Newer
Older
import ietf-yang-types {
prefix yang;
reference
"RFC 6991: Common YANG Data Types.";
}
organization
"European Telecommunications Standards Institute (ETSI)";
"Common data types for ETSI data models.";
Miguel Angel Reina Ortega
committed
revision 2022-03-08 {
description
"Version 3.6.1.
Common data structures to support VNFD and NSD according to:
ETSI GS NFV-IFA 014 Release 3
ETSI GS NFV-IFA 011 Release 3.";
}
revision 2021-07-05 {
description
"Version 3.5.1.
Common data structures to support VNFD and NSD according to:
ETSI GS NFV-IFA 014 Release 3
ETSI GS NFV-IFA 011 Release 3.";
}
revision 2020-06-10 {
"Version 3.3.1.
Common data structures to support VNFD and NSD according to:
ETSI GS NFV-IFA 014 Release 3
ETSI GS NFV-IFA 011 Release 3.";
revision 2020-06-01 {
description
"Version 2.8.1.
Common data structures to support VNFD and NSD according to:
ETSI GS NFV-IFA 014 271
ETSI GS NFV-IFA 011 271.";
}
revision 2019-10-01 {
description
"Version 2.7.1.
Common data structures to support VNFD and NSD according to:
ETSI GS NFV-IFA 014 Ed271v264
ETSI GS NFV-IFA 011 Ed271v264";
}
Common data structures to support VNFD and NSD according to:
ETSI GS NFV-IFA 014 Ed261v252
ETSI GS NFV-IFA 011 Ed261v254";
}
/*
* Identities.
*/
identity layer-protocol {
}
base layer-protocol;
}
identity address-type {
description
"Describes the type of the address to be assigned to the CP
instantiated from the parent CPD.
Value:
• MAC address.
• IP address.
• …
The content type shall be aligned with the address type
supported by the layerProtocol attribute of the parent CPD.";
reference
"GS NFV IFA011: Section 7.1.3.3, AddressData information
element.";
}
identity mac-address {
base address-type;
}
identity ip-address {
base address-type;
}
identity supported-operation {
description
"Indicates which operations are available for this DF via the
VNF LCM interface. Instantiate VNF, Query VNF and Terminate
VNF are supported in all DF and therefore need not be
included in this list.";
reference
"GS NFV IFA011: Section 7.1.8.2 VnfDf information element";
}
identity instantiate-vnf {
base supported-operation;
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
description
"This operation instantiates a particular DF of a VNF based on
the definition in the VNFD.";
reference
"GS NFV IFA007: Section 7.2.3 Instantiate VNF Operation";
}
identity scale-vnf {
base supported-operation;
description
"This operation provides methods to request scaling a VNF in
multiple ways:
• horizontal scaling:
- scale out: adding additional VNFC instances to the VNF to
increase capacity
- scale in: removing VNFC instances from the VNF, in order to
release unused capacity";
reference
"GS NFV IFA007: Section 7.2.4 Scale VNF Operation";
}
identity scale-vnf-to-level {
base supported-operation;
description
"This operation scales an instantiated VNF of a particular DF to
a target size. The target size is either expressed as an
instantiation level of that DF as defined in the VNFD, or given
as a list of scale levels, one per scaling aspect of that DF.
Instantiation levels and scaling aspects are declared in the
VNFD. Typically, the result of this operation is adding and/or
removing Network Functions Virtualization Infrastructure (NFVI)
resources to/from the VNF.";
reference
"GS NFV IFA007: Section 7.2.5 Scale VNF To Level Operation";
}
identity change-vnf-flavour {
base supported-operation;
description
"This operation changes the DF of a VNF instance.";
reference
"GS NFV IFA007: Section 7.2.6 Change VNF Flavour Operation";
}
identity terminate-vnf {
base supported-operation;
description
"This operation terminates a VNF.
A VNF can be terminated gracefully or forcefully. Graceful
termination means that the VNFM arranges to take the
VNF out of service, e.g. by asking the VNF's EM to take the
VNF out of service, and only after that shuts down the
VNF and releases the resources. Forceful termination means that
the VNFM immediately shuts down the VNF and releases the
resources. A time interval can be specified for taking the VNF
out of service, after which the VNF is shut down if taking it
out of service has not completed.";
reference
"GS NFV IFA007: Section 7.2.7 Terminate VNF Operation";
}
identity query-vnf {
base supported-operation;
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
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
description
"This operation provides information about VNF instances. The
applicable VNF instances can be chosen based on
filtering criteria, and the information can be restricted to
selected attributes.";
reference
"GS NFV IFA007: Section 7.2.9 Query VNF Operation";
}
identity heal-vnf {
base supported-operation;
description
"This operation enables the NFVO to request a VNFM to perform a
VNF healing procedure.";
reference
"GS NFV IFA007: Section 7.2.10 Heal VNF Operation";
}
identity operate-vnf {
base supported-operation;
description
"This operation enables requesting to change the state of a VNF
instance, including starting and stopping the VNF instance.";
reference
"GS NFV IFA007: Section 7.2.11 Operate VNF Operation";
}
identity modify-vnf-information {
base supported-operation;
description
"This operation allows updating information about a VNF
instance.";
reference
"GS NFV IFA007: Section 7.2.12 Modify VNF Operation";
}
identity cp-role {
description
"Identifies the role of the port in the context of the traffic
flow patterns in the VNF or parent NS.";
reference
"GS NFV IFA011: Section 7.1.6.3 Cpd information element";
}
identity root {
base cp-role;
}
identity leaf {
base cp-role;
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
identity checksum-algorithm {
description
"Identifies the algorithms supported for the purpose of
calculating the checksum.";
reference
"GS NFV IFA011: Section 7.1.6.10 Checksum information element.";
}
identity sha-224 {
base checksum-algorithm;
description
"SHA-224.";
reference
"GS NFV IFA011: Section 7.1.6.10 Checksum information element.";
}
identity sha-256 {
base checksum-algorithm;
description
"SHA-256.";
reference
"GS NFV IFA011: Section 7.1.6.10 Checksum information element.";
}
identity sha-384 {
base checksum-algorithm;
description
"SHA-384.";
reference
"GS NFV IFA011: Section 7.1.6.10 Checksum information element.";
}
identity sha-512 {
base checksum-algorithm;
description
"SHA-512.";
reference
"GS NFV IFA011: Section 7.1.6.10 Checksum information element.";
identity storage-type {
description
"Base type of storage that identities can derive from.";
}
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
identity forwarding-behaviour {
description
"Base identity for forwarding behaviour.";
}
identity all {
base forwarding-behaviour;
description
"Traffic flows shall be forwarded simultaneously to all CP
or SAP instances created from the referenced CP profile(s).";
}
identity lb {
base forwarding-behaviour;
description
"Traffic flows shall be forwarded to one CP or SAP instance
created from the referenced CP profile(s) selected based on
a load-balancing algorithm.";
}
identity vip-function {
description
"Indicates the function the virtual IP address is used for.";
}
identity high-availability {
base vip-function;
description
"High availability function.";
}
identity load-balancing {
base vip-function;
description
"Load balancing function.";
}
334
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
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
identity vnic-type {
description
"Describes the type of the virtual network interface realizing
the CPs instantiated from this CPD. This is used to determine
which mechanism driver(s) to be used to bind the port. Value:
• NORMAL
• VIRTIO
• DIRECT
• BAREMETAL
• VIRTIO-FORWARDER
• DIRECT-PHYSICAL
• SMART-NIC";
}
identity normal {
base vnic-type;
description
"Normal NIC.";
}
identity virtio {
base vnic-type;
description
"VirtIO NIC.";
}
identity direct {
base vnic-type;
description
"Direct NIC type.";
}
identity bare-metal {
base vnic-type;
description
"Bare metal NIC type.";
}
identity virtio-forwarder {
base vnic-type;
description
"VirtIO Forwarder NIC type.";
}
identity direct-physical {
base vnic-type;
description
"Direct physical NIC type.";
}
identity smart-nic {
base vnic-type;
description
"SmartNIC or Smart NIC type.";
typedef flow-pattern {
type enumeration {
enum line;
enum tree;
enum mesh;
}
}
typedef affinity-type {
type enumeration {
enum "affinity";
enum "anti-affinity";
}
}
typedef affinity-scope {
type enumeration {
enum "nfvi-node";
enum "zone-group";
enum "zone";
enum "nfvi-pop";
typedef internal-lifecycle-management-script-event {
type enumeration {
enum "start-instantiation";
enum "end-instantiation";
enum "start-scaling";
enum "end-scaling";
enum "start-healing";
enum "end-healing";
enum "start-termination";
enum "end-termination";
enum "start-vnf-flavour-change";
enum "end-vnf-flavour-change";
enum "start-vnf-operation-change";
enum "end-vnf-operation-change";
enum "start-vnf-ext-conn-change";
enum "end-vnf-ext-conn-change";
enum "start-vnfinfo-modification";
enum "end-vnfinfo-modification";
enum "start-vnf-snapshot-creation";
enum "end-vnf-snapshot-creation";
enum "start-vnf-snapshot-reverting-to";
enum "end-vnf-snapshot-reverting-to";
enum "start-change-current-vnf-package";
enum "end-change-current-vnf-package";
}
}
typedef external-lifecycle-management-script-event {
type enumeration {
enum "instantiation";
enum "scaling";
enum "healing";
enum "termination";
enum "vnf-flavour-change";
enum "vnf-operation-change";
enum "vnf-ext-conn-change";
enum "vnfinfo-modification";
enum "vnf-snapshot-creation";
enum "vnf-snapshot-reverting-to";
enum "change-current-vnf-package";
grouping nfvi-maintenance-info {
container nfvi-maintenance-info {
leaf impact-notification-lead-time {
type yang:timeticks;
mandatory true;
"The value specifies the minimum notification lead time
requested for upcoming impact of the virtualised resource
or their group (i.e. between the notification and the
action causing the impact).";
"GS NFV-IFA011: Section 7.1.8.17, NfviMaintenanceInfo
information element";
leaf is-impact-mitigation-requested {
type boolean;
"When set to True, it is requested that at the time of the
notification of an upcoming change that is expected to have
an impact on the VNF, virtualised resource(s) of the same
characteristics as the impacted ones is/are provided to
compensate for the impact. Cardinality 0 corresponds to the
value False.";
"GS NFV-IFA011: Section 7.1.8.17, NfviMaintenanceInfo
information element";
}
leaf-list supported-migration-type {
type enumeration {
enum "no-migration";
enum "offline-migration";
enum "live-migration";
}
description
"Applicable to VirtualComputeDesc and VirtualStorageDesc.
When present, specifies the allowed migration types in the
order of preference in case of an impact starting with the
most preferred type.
Values:
• NO_MIGRATION
• OFFLINE_MIGRATION
• LIVE_MIGRATION.";
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
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
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
reference
"GS NFV-IFA011: Section 7.1.8.17, NfviMaintenanceInfo
information element";
}
leaf max-undetectable-interruption-time {
type yang:timeticks;
description
"Applicable to VirtualComputeDesc and VirtualStorageDesc.
When present, it specifies the maximum interruption time
that can go undetected at the VNF level and therefore
which will not trigger VNFinternal recovery during live
migration.";
reference
"GS NFV-IFA011: Section 7.1.8.17, NfviMaintenanceInfo
information element";
}
leaf min-recovery-time-between-impacts {
type yang:timeticks;
description
"When present, it specifies the time required by the group
to recover from an impact, thus, the minimum time
requested between consecutive impacts of the group.";
reference
"GS NFV-IFA011: Section 7.1.8.17, NfviMaintenanceInfo
information element";
}
list max-number-of-impacted-instances {
key "group-size";
ordered-by user;
must "./max-number-of-impacted-instances <= ./group-size";
leaf group-size {
type uint32;
description
"When present, it determines the size of the group for
which the maxNumberOfImpactedInstances is specified.
Otherwise the size is not limited.
Each groupSize value specified for a group of virtual
resources shall be unique, and it shall be possible
to form an ascending ordered list of groupSizes.
The number of instances in the group for which the
maxNumberOfImpactedInstances is specified may be equal
to groupSize or less. When the number of instances is
less than the groupSize, it shall be at least 1 if this
is the first groupSize in the ordered list of groupSizes,
or it shall be greater by at least 1 than the previous
groupSize in the ordered list of groupSizes.";
reference
"GS NFV-IFA011: Section 7.1.8.17, NfviMaintenanceInfo
information element";
}
leaf max-number-of-impacted-instances {
type uint32 {
range "1 .. max";
}
description
"The maximum number of instances that can be impacted
simultaneously within the group of the specified size.";
reference
"GS NFV-IFA011: Section 7.1.8.17, NfviMaintenanceInfo
information element";
}
ppree
committed
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
list min-number-of-preserved-instances {
key "group-size";
ordered-by user;
must "./min-number-of-preserved-instances <= ./group-size";
leaf group-size {
type uint32;
description
"When present, it determines the size of the group for
which the minNumberOfPreservedInstances is specified.
Otherwise the size is not limited.";
reference
"GS NFV-IFA011: Section 7.1.8.21, MinNumberOfPreserved
Instances information element";
}
leaf min-number-of-preserved-instances {
type uint32 {
range "1 .. max";
}
description
"The maximum number of instances that can be impacted
simultaneously within the group of the specified size.";
reference
"GS NFV-IFA011: Section 7.1.8.21, MinNumberOfPreserved
Instances information element";
}
}
}
}
grouping connectivity-type {
container connectivity-type {
leaf-list layer-protocol {
type identityref {
base layer-protocol;
}
min-elements 1;
"Specifies the protocols that the VL uses
Values:
• Ethernet
• MPLS
• ODU2
• IPV4
• IPV6
• Pseudo-Wire
• etc.";
reference
"GS NFV IFA011: Section 7.1.7.3, ConnectivityType
information element.";
}
leaf flow-pattern {
type flow-pattern;
description
"Specifies the flow pattern of the connectivity (Line,
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
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
Tree, Mesh).";
reference
"GS NFV IFA011: Section 7.1.7.3, ConnectivityType
information element.";
}
}
}
grouping link-bitrate-requirements {
leaf root {
type uint64;
units "Mbps";
mandatory true;
description
"Specifies the throughput requirement of
the link (e.g. bitrate of E-Line, root bitrate
of E-Tree, aggregate capacity of E-LAN).";
reference
"GS NFV IFA011: Section 7.1.8.6, LinkBitrateRequirements
information element.";
}
leaf leaf {
type uint64;
units "Mbps";
description
"Specifies the throughput requirement of
leaf connections to the link when
applicable to the connectivity type (e.g. for
E-Tree and E-LAN branches).";
reference
"GS NFV IFA011: Section 7.1.8.6, LinkBitrateRequirements
information element.";
}
}
grouping monitoring-parameter {
leaf name {
type string;
description
"Human readable name of the monitoring parameter.";
reference
"GS NFV IFA011: Section 7.1.11.3, MonitoringParameter
information element.";
}
leaf performance-metric {
type string;
description
"Performance metric that is monitored. This attribute shall
contain the related 'Measurement Name' value as defined in
clause 7.2 of ETSI GS NFV-IFA 027";
reference
"GS NFV IFA011: Section 7.1.11.3, MonitoringParameter
information element and Section 7.2 of ETSI GS NFV-IFA 027.";
}
leaf collection-period {
type uint64;
units "ms";
description
"An attribute that describes the recommended periodicity at
which to collect the performance information. VNFM determines
if this parameter is considered.
The vendor may provide this information as a guidance for
creating PmJobs if needed.";
reference
"GS NFV IFA011: Section 7.1.11.3, MonitoringParameter
information element.";
}
}
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
grouping security-parameters {
leaf signature {
type string;
description
"Provides the signature of the signed part of the
descriptor.";
reference
"GS NFV IFA014: Section 6.2.5, SecurityParameters
information element.";
}
leaf algorithm {
type string;
description
"Identifies the algorithm used to compute the signature.";
reference
"GS NFV IFA014: Section 6.2.5, SecurityParameters
information element.";
}
leaf certificate {
type string;
description
"Provides a certificate or a reference to a certificate to
validate the signature.";
reference
"GS NFV IFA014: Section 6.2.5, SecurityParameters
information element.";
}
}
"A Cpd information element describes network
connectivity to a compute resource or a VL.";
"GS NFV IFA011: Section 7.1.6.3 Cpd information element";
leaf id {
type string;
description
"Identifier of this Cpd information element.";
reference
"GS NFV IFA011: Section 7.1.6.3 Cpd information element";
"Specifies which protocol the CP uses for connectivity purposes
Values:
• Ethernet
• MPLS
• ODU2
• IPV4
• IPV6
• Pseudo-Wire
• etc.";
"GS NFV IFA011: Section 7.1.6.3 Cpd information element";
"Identifies the role of the connection points
corresponding to the CPD in the context of the traffic
flow patterns in the VNF, PNF or NS. For example an NS with
a tree flow pattern within the NS will have legal cpRoles
of ROOT and LEAF.";
"GS NFV IFA011: Section 7.1.6.3 Cpd information element";
leaf description {
type string;
description
"Provides human-readable information on the purpose of the
connection point (e.g. connection point for control plane
traffic).";
"GS NFV IFA011: Section 7.1.6.3 Cpd information element";
list protocol {
key "associated-layer-protocol";
leaf associated-layer-protocol {
type identityref {
base layer-protocol;
}
description
"One of the values of the attribute layerProtocol of the Cpd
IE.
Values:
• Ethernet
• MPLS
• ODU2
• IPV4
• IPV6
• Pseudo-Wire
• etc.";
reference
"GS NFV IFA011: Section 7.1.6.8 CpProtocolData information
element";
}
list address-data {
key "type";
leaf type {
type identityref {
base address-type;
}
description
"Describes the type of the address to be assigned to the
CP instantiated from the parent CPD.
Values:
• MAC address
• IP address
• etc.
The content type shall be aligned with the address type
supported by the layerProtocol attribute of the parent
CPD.";
reference
"GS NFV IFA011: Section 7.1.3.3 AddressData information
element";
}
container l2-address-data {
when "../type='mac-address'";
leaf mac-address-assignment {
type boolean;
"Specify which mode is used for the MAC address
assignment.
If it is set to True, a MAC address is expected to
be provided by a management entity via the NFV-MANO
interfaces towards the VNFM using attributes
standardized for this purpose in the NFV-MANO
information model and is further transferred from the
VNFM to the VIM. A MAC address will be automatically
assigned by the VIM/NFVI as fallback if not provided.
If it is set to False, a MAC address is expected to be
assigned by means specific to the VNF itself (e.g., by
an LCM script, by the EM) and is further transferred
from the VNFM to the VIM. A MAC address will be
automatically assigned by the VIM/NFVI as fallback if
not provided to the VIM.";
reference
"GS NFV IFA011: Section 7.1.3.5 L2AddressData
information element";
}
description
"Provides the information on the MAC addresses to be
assigned to the CP(s) instantiated from the parent CPD.
Shall be present when the addressType is MAC address.";
reference
"GS NFV IFA011: Section 7.1.3.3 AddressData information
element";
}
container l3-address-data {
when "../type='ip-address'";
leaf ip-address-assignment {
type boolean;
description
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
912
913
914
915
916
"Specify which mode is used for the address assignment.
If set to True, IP configuration information shall be
provided for the VNF by a management entity using the
NFV MANO interfaces towards the VNFM.
If it is set to False, the value of the
'ipAddressAssignmentSubtype' attribute defines the
method of IP address assignment.
Shall be present if the 'fixedIpAddress' attribute
is not present and should be absent otherwise.";
reference
"GS NFV IFA011: Section 7.1.3.4, L3AddressData
information element.";
}
leaf ip-address-assignment-subtype {
type enumeration {
enum dynamic;
enum vnf_pkg;
enum external;
}
description
"Method of IP address assignment in case the IP
configuration is not provided using the NFV MANO
interfaces towards the VNFM.
Shall be present in case the 'ipAddressAssignment'
attribute is set to 'False' and shall be absent
otherwise.
Valid values:
DYNAMIC: the VNF gets an IP address dynamically from
the NFVI (e.g., using DHCP)
VNF_PKG: an IP address defined by the VNF provider is
assigned by means included as part of the VNF package
(e.g., LCM script)
EXTERNAL: an IP address is provided by an external
management entity (such as EM) directly towards the
VNF.";
reference
"GS NFV IFA011: Section 7.1.3.4, L3AddressData
information element.";
}
leaf floating-ip-activated {
type boolean;
description
"Specify if the floating IP scheme is activated on the CP
or not.";
reference
"GS NFV IFA011: Section 7.1.3.4, L3AddressData
information element.";
}
leaf ip-address-type {
type enumeration {
enum "ipv4";
enum "ipv6";
}
description
"Define address type.
Values:
• IPV4
• IPV6.";
reference
"GS NFV IFA011: Section 7.1.3.4, L3AddressData
information element.";
}
leaf number-of-ip-addresses {
type uint32;
description
"Minimum number of IP addresses to be assigned based on
this L3AddressData information element.";
reference
"GS NFV IFA011: Section 7.1.3.4, L3AddressData
information element.";
}
leaf fixed-ip-address {
type string;
description
"Fixed IP addresses to be assigned to the internal CP
instance.
This attribute enables the VNF provider to define
fixed IP addresses for internal CP instances to be
assigned by the VNFM or the NFVO.";
reference
"GS NFV IFA011: Section 7.1.3.4, L3AddressData
information element.";
}
}
description
"Provides information on the addresses to be assigned to the
CP(s) instantiated from the CPD.";
reference
"GS NFV IFA011: Section 7.1.6.8 CpProtocolData information
element";
}
description
"Identifies the protocol layering information the CP uses for
connectivity purposes and associated information. There shall
be one cpProtocol for each layer protocol as indicated by the
attribute layerProtocol. When a PnfExtCpd as defined in ETSI
GS NFV-IFA 014 [i.8] is inherited from this Cpd, the
cardinality is set to 0.";
reference
"GS NFV IFA011: Section 7.1.6.3 Cpd information element";
}
leaf trunk-mode {
type boolean;
description
"Information about whether the Cp instantiated from this CPD
is in Trunk mode (802.1Q or other). When operating in
'trunk mode', the Cp is capable of carrying traffic for
several VLANs. A cardinality of 0 implies that trunkMode
is not configured for the Cp i.e. It is equivalent to
Boolean value 'false'.";
"GS NFV IFA011: Section 7.1.6.3 Cpd information element";
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
}
grouping security-group-rule {
list security-group-rule {
key "id";
leaf id {
type string;
description
"Identifier of this SecurityGroupRule information
element.";
reference
"GS NFV IFA011: Section 7.1.6.9, SecurityGroupRule
information element.";
}
leaf description {
type string;
description
"Human readable description of the security group rule.";
reference
"GS NFV IFA011: Section 7.1.6.9, SecurityGroupRule
information element.";
}
leaf direction {
type enumeration {
enum ingress;
enum egress;
}
default "ingress";
description
"The direction in which the security group rule is applied.
Values:
• INGRESS
• EGRESS
Defaults to INGRESS.";
reference
"GS NFV IFA011: Section 7.1.6.9, SecurityGroupRule
information element.";
}
leaf ether-type {
type enumeration {
enum ipv4;
enum ipv6;
}
default "ipv4";
description
"Indicates the protocol carried over the Ethernet layer.
Values:
• IPV4
• IPV6
Defaults to IPV4.";
reference
"GS NFV IFA011: Section 7.1.6.9, SecurityGroupRule
information element.";
}
leaf protocol {
type enumeration {
enum tcp;
enum udp;
enum icmp;
}
default "tcp";
description
"Indicates the protocol carried over the IP layer.
Permitted values: any protocol defined in the IANA
protocol registry.
Values:
• TCP
• UDP
• ICMP
• etc.
Defaults to TCP.";
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
reference
"GS NFV IFA011: Section 7.1.6.9, SecurityGroupRule
information element.";
}
leaf port-range-min {
must ". <= ../port-range-max";
type uint16;
default "0";
description
"Indicates minimum port number in the range that is
matched by the security group rule. Defaults to 0.";
reference
"GS NFV IFA011: Section 7.1.6.9, SecurityGroupRule
information element.";
}
leaf port-range-max {
must ". >= ../port-range-min";
type uint16;
default "65535";
description
"Indicates maximum port number in the range that is
matched by the security group rule. Defaults to 65535.";
reference
"GS NFV IFA011: Section 7.1.6.9, SecurityGroupRule
information element.";
}
description
"Defines security group rules to be used by the VNF.";
reference
"GS NFV IFA011: Section 7.1.2, VNFD information element.";
}