| Internet-Draft | IP Traffic Flow Security YANG Module | November 2020 |
| Fedyk & Hopps | Expires 19 May 2021 | [Page] |
This document describes a yang module for the management of IP Traffic Flow Security additions to IKEv2 and IPsec.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 19 May 2021.¶
Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
This document defines a YANG module [RFC7950] for the management of the IP Traffic Flow Security (IP-TFS) extensions as defined in [I-D.ietf-ipsecme-iptfs]. IP-TFS provides enhancements to an IPsec tunnel Security Association to provide improved traffic confidentiality. Traffic confidentiality reduces the ability of traffic analysis to determine identity and correlate observable traffic patterns. IP-TFS offers efficiency when aggregating traffic in fixed size IPsec tunnel packets.¶
The YANG data model in this document conforms to the Network Management Datastore Architecture defined in [RFC8342].¶
The only actively published YANG modules for IPsec are found in [I-D.ietf-i2nsf-sdn-ipsec-flow-protection]. This document uses these models as a general IPsec model that can be augmented. The models in [I-D.ietf-i2nsf-sdn-ipsec-flow-protection] provide for an ike and an ikeless model.¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This document defines configuration and operational parameters of IP traffic flow security (IP-TFS). IP-TFS, defined in [I-D.ietf-ipsecme-iptfs], configures a security association for tunnel mode IPsec with characteristics that improve traffic confidentiality and reduce bandwidth efficiency loss. These documents assume familiarity with IP security concepts described in [RFC4301].¶
IP-TFS uses tunnel mode to improve confidentiality by hiding inner packet identifiable information, packet size and packet timing. IP-TFS provides a general capability allowing aggregation of multiple packets and packet size control utilizing padding and additionally utilizing inner packet fragments when a complete inner packet will not fit in the IPsec outer tunnel packet. Zero byte padding is used to fill the packet when no data is available to send.¶
This document specifies an extensible configuration model for IP-TFS. This version utilizes the capabilities of IP-TFS to configure fixed size IP-TFS Packets that are transmitted at a constant rate. This model is structured to allow for different types of operation through future augmentation.¶
IP-TFS YANG augments IPsec YANG model from [I-D.ietf-i2nsf-sdn-ipsec-flow-protection]. IP-TFS makes use of IPsec tunnel mode and adds a small number configuration items to tunnel mode IPsec. As defined in [I-D.ietf-ipsecme-iptfs], any SA configured to use IP-TFS supports only IP-TFS packets i.e. no mixed IPsec modes.¶
The behavior for IP-TFS is controlled by the source. The self-describing format of an IP-TFS packets allows a sending side to adjust the packet-size and timing independently from any receiver. Both directions are also independent, e.g. IP-TFS may be run only in one direction.¶
The data model uses following constructs for configuration and management:¶
o Configuration¶
o Operational State¶
This YANG module supports configuration of fixed size and fixed rate packets, and elements that may be augmented to support future configuration. The protocol specification [I-D.ietf-ipsecme-iptfs], goes beyond this simple fixed mode of operation by defining a general format for any type of scheme. In this document the outer IPsec packets can be sent with fixed or variable size (without padding). The configuration allows the fixed packet size to be determined by the path MTU. The fixed packet size can also be configured if a value lower than the path MTU is desired.¶
Other configuration items include:¶
The YANG operational data allows the readout of the configured parameters as well as the per SA statistics and error counters for IP-TFS. Per SA IPsec packet statistics are provided as a feature and per SA IP-TFS specific statistics as another feature. Both sets of statistics augment the IPsec YANG models with counters that allow observation of IP-TFS packet efficiency.¶
Draft [I-D.ietf-i2nsf-sdn-ipsec-flow-protection] has a mature set of IPsec YANG management objects.¶
IP-TFS YANG augments:¶
The Security Policy database entry and Security Association entry for an IPsec Tunnel can be augmented with IP-TFS.¶
The following is the YANG tree diagram ([RFC8340]) for the IP-TFS extensions.¶
module: ietf-ipsecme-iptfs
augment /nsfike:ipsec-ike/nsfike:conn-entry/nsfike:spd
/nsfike:spd-entry/nsfike:ipsec-policy-config
/nsfike:processing-info/nsfike:ipsec-sa-cfg:
+--rw traffic-flow-security
+--rw congestion-control? boolean
+--rw packet-size
| +--rw use-path-mtu? boolean
| +--rw outer-packet-size? uint16
+--rw (tunnel-rate)?
| +--:(l2-fixed-rate)
| | +--rw l2-fixed-rate? uint64
| +--:(l3-fixed-rate)
| +--rw l3-fixed-rate? uint64
+--rw dont-fragment? boolean
augment /nsfike:ipsec-ike/nsfike:conn-entry/nsfike:child-sa-info:
+--ro traffic-flow-security
+--ro congestion-control? boolean
+--ro packet-size
| +--ro use-path-mtu? boolean
| +--ro outer-packet-size? uint16
+--ro (tunnel-rate)?
| +--:(l2-fixed-rate)
| | +--ro l2-fixed-rate? uint64
| +--:(l3-fixed-rate)
| +--ro l3-fixed-rate? uint64
+--ro dont-fragment? boolean
augment /nsfikels:ipsec-ikeless/nsfikels:spd/nsfikels:spd-entry
/nsfikels:ipsec-policy-config/nsfikels:processing-info
/nsfikels:ipsec-sa-cfg:
+--rw traffic-flow-security
+--rw congestion-control? boolean
+--rw packet-size
| +--rw use-path-mtu? boolean
| +--rw outer-packet-size? uint16
+--rw (tunnel-rate)?
| +--:(l2-fixed-rate)
| | +--rw l2-fixed-rate? uint64
| +--:(l3-fixed-rate)
| +--rw l3-fixed-rate? uint64
+--rw dont-fragment? boolean
augment /nsfikels:ipsec-ikeless/nsfikels:sad/nsfikels:sad-entry:
+--ro traffic-flow-security
+--ro congestion-control? boolean
+--ro packet-size
| +--ro use-path-mtu? boolean
| +--ro outer-packet-size? uint16
+--ro (tunnel-rate)?
| +--:(l2-fixed-rate)
| | +--ro l2-fixed-rate? uint64
| +--:(l3-fixed-rate)
| +--ro l3-fixed-rate? uint64
+--ro dont-fragment? boolean
augment /nsfike:ipsec-ike/nsfike:conn-entry/nsfike:child-sa-info:
+--ro ipsec-stats {ipsec-stats}?
| +--ro tx-packets? uint64
| +--ro tx-octets? uint64
| +--ro tx-drop-packets? uint64
| +--ro rx-packets? uint64
| +--ro rx-octets? uint64
| +--ro rx-drop-packets? uint64
+--ro iptfs-stats {iptfs-stats}?
+--ro tx-inner-packets? uint64
+--ro tx-inner-octets? uint64
+--ro tx-extra-pad-packets? uint64
+--ro tx-extra-pad-octets? uint64
+--ro tx-all-pad-packets? uint64
+--ro tx-all-pad-octets? uint64
+--ro rx-inner-packets? uint64
+--ro rx-inner-octets? uint64
+--ro rx-extra-pad-packets? uint64
+--ro rx-extra-pad-octets? uint64
+--ro rx-all-pad-packets? uint64
+--ro rx-all-pad-octets? uint64
+--ro rx-errored-packets? uint64
+--ro rx-missed-packets? uint64
+--ro rx-incomplete-inner-packets? uint64
augment /nsfikels:ipsec-ikeless/nsfikels:sad/nsfikels:sad-entry:
+--rw ipsec-stats {ipsec-stats}?
| +--ro tx-packets? uint64
| +--ro tx-octets? uint64
| +--ro tx-drop-packets? uint64
| +--ro rx-packets? uint64
| +--ro rx-octets? uint64
| +--ro rx-drop-packets? uint64
+--rw iptfs-stats {iptfs-stats}?
+--ro tx-inner-packets? uint64
+--ro tx-inner-octets? uint64
+--ro tx-extra-pad-packets? uint64
+--ro tx-extra-pad-octets? uint64
+--ro tx-all-pad-packets? uint64
+--ro tx-all-pad-octets? uint64
+--ro rx-inner-packets? uint64
+--ro rx-inner-octets? uint64
+--ro rx-extra-pad-packets? uint64
+--ro rx-extra-pad-octets? uint64
+--ro rx-all-pad-packets? uint64
+--ro rx-all-pad-octets? uint64
+--ro rx-errored-packets? uint64
+--ro rx-missed-packets? uint64
+--ro rx-incomplete-inner-packets? uint64
¶
The following is the YANG module for managing the IP-TFS extensions.¶
<CODE BEGINS> file "ietf-ipsecme-iptfs@2020-11-15.yang"
module ietf-ipsecme-iptfs {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ipsecme-iptfs";
prefix iptfs;
import ietf-i2nsf-ike {
prefix nsfike;
}
import ietf-i2nsf-ikeless {
prefix nsfikels;
}
organization
"IETF IPSECME Working Group (IPSECME)";
contact
"WG Web: <https://tools.ietf.org/wg/ipsecme/>
WG List: <mailto:ipsecme@ietf.org>
Author: Don Fedyk
<mailto:dfedyk@labn.net>
Author: Christian Hopps
<mailto:chopps@chopps.org>";
// RFC Ed.: replace XXXX with actual RFC number and
// remove this note.
description
"This module defines the configuration and operational state for
managing the IP Traffic Flow Security functionality [RFC XXXX].
Copyright (c) 2020 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 Simplified 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 XXXX
(https://tools.ietf.org/html/rfcXXXX); see the RFC itself for
full legal notices.";
revision 2020-11-15 {
description
"Initial Revision";
reference
"RFC XXXX: IP Traffic Flow Security YANG Module";
}
feature ipsec-stats {
description
"This feature indicates the device supports
per SA IPsec statistics";
}
feature iptfs-stats {
description
"This feature indicates the device supports
per SA IP Traffic Flow Security statistics";
}
/*--------------------*/
/* groupings */
/*--------------------*/
grouping ipsec-tx-stat-grouping {
description
"IPsec outbound statistics";
leaf tx-packets {
type uint64;
config false;
description
"Outbound Packet count";
}
leaf tx-octets {
type uint64;
config false;
description
"Outbound Packet bytes";
}
leaf tx-drop-packets {
type uint64;
config false;
description
"Outbound dropped packets count";
}
}
grouping ipsec-rx-stat-grouping {
description
"IPsec inbound statistics";
leaf rx-packets {
type uint64;
config false;
description
"Inbound Packet count";
}
leaf rx-octets {
type uint64;
config false;
description
"Inbound Packet bytes";
}
leaf rx-drop-packets {
type uint64;
config false;
description
"Inbound dropped packets count";
}
}
grouping iptfs-tx-stat-grouping {
description
"IP-TFS outbound statistics";
leaf tx-inner-packets {
type uint64;
config false;
description
"Total number of IP-TFS inner packets sent. This
count is whole packets only. A fragmented packet
counts as one packet";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf tx-inner-octets {
type uint64;
config false;
description
"Total number of IP-TFS inner octets sent. This is
inner packet octets only. Does not count padding.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf tx-extra-pad-packets {
type uint64;
config false;
description
"Total number of transmitted outer IP-TFS packets
that included some padding.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf tx-extra-pad-octets {
type uint64;
config false;
description
"Total number of transmitted octets of padding added
to outer IP-TFS packets with data.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf tx-all-pad-packets {
type uint64;
config false;
description
"Total number of transmitted IP-TFS packets that
were all padding with no inner packet data.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf tx-all-pad-octets {
type uint64;
config false;
description
"Total number transmitted octets of padding added to
IP-TFS packets with no inner packet data.";
reference
"draft-ietf-ipsecme-iptfs";
}
}
grouping iptfs-rx-stat-grouping {
description
"IP-TFS inbound statistics";
leaf rx-inner-packets {
type uint64;
config false;
description
"Total number of IP-TFS inner packets received.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf rx-inner-octets {
type uint64;
config false;
description
"Total number of IP-TFS inner octets received. Does
not include padding or overhead";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf rx-extra-pad-packets {
type uint64;
config false;
description
"Total number of received outer IP-TFS packets that
included some padding.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf rx-extra-pad-octets {
type uint64;
config false;
description
"Total number of received octets of padding added to
outer IP-TFS packets with data.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf rx-all-pad-packets {
type uint64;
config false;
description
"Total number of received IP-TFS packets that were
all padding with no inner packet data.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf rx-all-pad-octets {
type uint64;
config false;
description
"Total number received octets of padding added to
IP-TFS packets with no inner packet data.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf rx-errored-packets {
type uint64;
config false;
description
"Total number of IP-TFS outer packets dropped due to
errors.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf rx-missed-packets {
type uint64;
config false;
description
"Total number of IP-TFS outer packets missing
indicated by missing sequence number.";
reference
"draft-ietf-ipsecme-iptfs";
}
leaf rx-incomplete-inner-packets {
type uint64;
config false;
description
"Total number of IP-TFS inner packets that were
incomplete. Usually this is due to fragments not
received. Also, this may be due to misordering or
errors in received outer packets.";
reference
"draft-ietf-ipsecme-iptfs";
}
}
grouping iptfs-config {
description
"This is the grouping for iptfs configuration";
container traffic-flow-security {
// config true; want this so we can refine?
description
"Configure the IPSec TFS in Security
Association Database (SAD)";
leaf congestion-control {
type boolean;
default "true";
description
"Congestion Control With the congestion controlled
mode, IP-TFS adapts to network congestion by
lowering the packet send rate to accommodate the
congestion, as well as raising the rate when
congestion subsides.";
reference
"draft-ietf-ipsecme-iptfs Section 2.5.2";
}
container packet-size {
description
"Packet size is either auto-discovered or manually
configured.";
leaf use-path-mtu {
type boolean;
default "true";
description
"Utilize path-mtu to determine maximum IP-TFS packet size.
If the packet size is explicitly configured, then it
will only be adjusted downward if use-path-mtu is set.";
reference
"draft-ietf-ipsecme-iptfs Section 4.2";
}
leaf outer-packet-size {
type uint16;
description
"The size of the outer encapsulating tunnel packet (i.e.,
the IP packet containing the ESP payload).";
reference
"draft-ietf-ipsecme-iptfs Section 4.2";
}
}
choice tunnel-rate {
description
"TFS bit rate may be specified at layer 2 wire
rate or layer 3 packet rate";
leaf l2-fixed-rate {
type uint64;
description
"Target bandwidth/bit rate in bps for iptfs tunnel. This
fixed rate is the nominal timing for the fixed size packet.
If congestion control is enabled the rate may be adjusted
down (or up if unset).";
reference
"draft-ietf-ipsecme-iptfs section 4.1";
}
leaf l3-fixed-rate {
type uint64;
description
"Target bandwidth/bit rate in bps for iptfs tunnel. This
fixed rate is the nominal timing for the fixed size packet.
If congestion control is enabled the rate may be adjusted
down (or up if unset).";
reference
"draft-ietf-ipsecme-iptfs section 4.1";
}
}
leaf dont-fragment {
type boolean;
default "false";
description
"Disable packet fragmentation across consecutive iptfs
tunnel packets";
reference
"draft-ietf-ipsecme-iptfs section 2.2.4 and 6.4.1";
}
}
}
/*
* IP-TFS ike configuration
*/
augment "/nsfike:ipsec-ike/nsfike:conn-entry/nsfike:spd/"
+ "nsfike:spd-entry/"
+ "nsfike:ipsec-policy-config/"
+ "nsfike:processing-info/"
+ "nsfike:ipsec-sa-cfg" {
description
"IP-TFS configuration for this policy.";
uses iptfs-config;
}
augment "/nsfike:ipsec-ike/nsfike:conn-entry/"
+ "nsfike:child-sa-info" {
description
"IP-TFS configured on this SA.";
uses iptfs-config {
refine "traffic-flow-security" {
config false;
}
}
}
/*
* IP-TFS ikeless configuration
*/
augment "/nsfikels:ipsec-ikeless/nsfikels:spd/"
+ "nsfikels:spd-entry/"
+ "nsfikels:ipsec-policy-config/"
+ "nsfikels:processing-info/"
+ "nsfikels:ipsec-sa-cfg" {
description
"IP-TFS configuration for this policy.";
uses iptfs-config;
}
augment "/nsfikels:ipsec-ikeless/nsfikels:sad/"
+ "nsfikels:sad-entry" {
description
"IP-TFS configured on this SA.";
uses iptfs-config {
refine "traffic-flow-security" {
config false;
}
}
}
/*
* packet counters
*/
augment "/nsfike:ipsec-ike/nsfike:conn-entry/"
+ "nsfike:child-sa-info" {
description
"Per SA Counters";
container ipsec-stats {
if-feature "ipsec-stats";
config false;
description
"IPsec per SA packet counters.";
uses ipsec-tx-stat-grouping {
//when "direction = 'outbound'";
}
uses ipsec-rx-stat-grouping {
//when "direction = 'inbound'";
}
}
container iptfs-stats {
if-feature "iptfs-stats";
config false;
description
"IPTFS per SA packet counters.";
uses iptfs-tx-stat-grouping {
//when "direction = 'outbound'";
}
uses iptfs-rx-stat-grouping {
//when "direction = 'inbound'";
}
}
}
/*
* packet counters
*/
augment "/nsfikels:ipsec-ikeless/nsfikels:sad/"
+ "nsfikels:sad-entry" {
description
"Per SA Counters";
container ipsec-stats {
if-feature "ipsec-stats";
description
"IPsec per SA packet counters.";
uses ipsec-tx-stat-grouping {
//when "direction = 'outbound'";
}
uses ipsec-rx-stat-grouping {
//when "direction = 'inbound'";
}
}
container iptfs-stats {
if-feature "iptfs-stats";
description
"IPTFS per SA packet counters.";
uses iptfs-tx-stat-grouping {
//when "direction = 'outbound'";
}
uses iptfs-rx-stat-grouping {
//when "direction = 'inbound'";
}
}
}
}
<CODE ENDS>¶
This document registers a URI in the "IETF XML Registry" [RFC3688]. Following the format in [RFC3688], the following registration has been made:¶
This document registers one YANG module in the "YANG Module Names" registry [RFC6020]. Following the format in [RFC6020], the following registration has been made:¶
The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446].¶
The Network Configuration Access Control Model (NACM) [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.¶
The YANG module defined in this document can enable, disable and modify the behavior of IP traffic flow security, for the implications regarding these types of changes consult the [I-D.ietf-ipsecme-iptfs] which defines the functionality.¶
The authors would like to thank Eric Kinzie for his feedback on the YANG model.¶
The following examples show configuration and operational data for the ikeless case in xml and ike case in json. Also, the operational statistics for the ikeless case is shown using xml.¶
<i:ipsec-ikeless
xmlns:i="urn:ietf:params:xml:ns:yang:ietf-i2nsf-ikeless"
xmlns:ic="urn:ietf:params:xml:ns:yang:ietf-i2nsf-ikec"
xmlns:tfs="urn:ietf:params:xml:ns:yang:ietf-ipsecme-iptfs">
<i:spd>
<i:spd-entry>
<i:name>protect-policy-1</i:name>
<i:direction>outbound</i:direction>
<i:ipsec-policy-config>
<i:traffic-selector>
<i:local-subnet>1.1.1.1/32</i:local-subnet>
<i:remote-subnet>2.2.2.2/32</i:remote-subnet>
</i:traffic-selector>
<i:processing-info>
<i:action>protect</i:action>
<i:ipsec-sa-cfg>
<tfs:traffic-flow-security>
<tfs:congestion-control>true</tfs:congestion-control>
<tfs:packet-size>
<tfs:use-path-mtu>true</tfs:use-path-mtu>
</tfs:packet-size>
<tfs:l2-fixed-rate>1000000000</tfs:l2-fixed-rate>
</tfs:traffic-flow-security>
</i:ipsec-sa-cfg>
</i:processing-info>
</i:ipsec-policy-config>
</i:spd-entry>
</i:spd>
</i:ipsec-ikeless>
<i:ipsec-ikeless
xmlns:i="urn:ietf:params:xml:ns:yang:ietf-i2nsf-ikeless"
xmlns:ic="urn:ietf:params:xml:ns:yang:ietf-i2nsf-ikec"
xmlns:tfs="urn:ietf:params:xml:ns:yang:ietf-ipsecme-iptfs">
<i:sad>
<i:sad-entry>
<i:name>sad-1</i:name>
<i:ipsec-sa-config>
<i:spi>1</i:spi>
<i:traffic-selector>
<i:local-subnet>1.1.1.1/32</i:local-subnet>
<i:remote-subnet>2.2.2.2/32</i:remote-subnet>
</i:traffic-selector>
</i:ipsec-sa-config>
<tfs:traffic-flow-security>
<tfs:congestion-control>true</tfs:congestion-control>
<tfs:packet-size>
<tfs:use-path-mtu>true</tfs:use-path-mtu>
</tfs:packet-size>
<tfs:l2-fixed-rate>1000000000</tfs:l2-fixed-rate>
</tfs:traffic-flow-security>
</i:sad-entry>
</i:sad>
</i:ipsec-ikeless>
{
"ietf-i2nsf-ike:ipsec-ike": {
"ietf-i2nsf-ike:conn-entry": [
{
"name": "my-peer-connection",
"encalg": [
{
"id": 1,
"algorithm-type": 12,
"key-length": 128
}
],
"local": {
"local-pad-entry-name": "local-1"
},
"remote": {
"remote-pad-entry-name": "remote-1"
},
"ietf-i2nsf-ike:spd": {
"spd-entry": [
{
"name": "protect-policy-1",
"ipsec-policy-config": {
"traffic-selector": {
"local-subnet": "1.1.1.1/32",
"remote-subnet": "2.2.2.2/32"
},
"processing-info": {
"action": "protect",
"ipsec-sa-cfg": {
"ietf-ipsecme-iptfs:traffic-flow-security": {
"congestion-control": "true",
"l2-fixed-rate": 1000000000,
"packet-size": {
"use-path-mtu": "true"
}
}
}
}
}
}
]
}
}
]
}
}
{
"ietf-i2nsf-ike:ipsec-ike": {
"ietf-i2nsf-ike:conn-entry": [
{
"name": "my-peer-connection",
"encalg": [
{
"id": 1,
"algorithm-type": 12,
"key-length": 128
}
],
"local": {
"local-pad-entry-name": "local-1"
},
"remote": {
"remote-pad-entry-name": "remote-1"
},
"ietf-i2nsf-ike:child-sa-info": {
"ietf-ipsecme-iptfs:traffic-flow-security": {
"congestion-control": "true",
"l2-fixed-rate": 1000000000,
"packet-size": {
"use-path-mtu": "true"
}
}
}
}
]
}
}
<i:ipsec-ikeless
xmlns:i="urn:ietf:params:xml:ns:yang:ietf-i2nsf-ikeless"
xmlns:ic="urn:ietf:params:xml:ns:yang:ietf-i2nsf-ikec"
xmlns:tfs="urn:ietf:params:xml:ns:yang:ietf-ipsecme-iptfs">
<i:sad>
<i:sad-entry>
<i:name>sad-1</i:name>
<i:ipsec-sa-config>
<i:spi>1</i:spi>
<i:traffic-selector>
<i:local-subnet>1.1.1.1/32</i:local-subnet>
<i:remote-subnet>2.2.2.2/32</i:remote-subnet>
</i:traffic-selector>
</i:ipsec-sa-config>
<tfs:ipsec-stats>
<tfs:tx-packets>100</tfs:tx-packets>
<tfs:tx-octets>80000</tfs:tx-octets>
<tfs:tx-drop-packets>2</tfs:tx-drop-packets>
<tfs:rx-packets>50</tfs:rx-packets>
<tfs:rx-octets>50000</tfs:rx-octets>
<tfs:rx-drop-packets>0</tfs:rx-drop-packets>
</tfs:ipsec-stats>
<tfs:iptfs-stats>
<tfs:tx-inner-packets>250</tfs:tx-inner-packets>
<tfs:tx-inner-octets>75000</tfs:tx-inner-octets>
<tfs:tx-extra-pad-packets>200</tfs:tx-extra-pad-packets>
<tfs:tx-extra-pad-octets>30000</tfs:tx-extra-pad-octets>
<tfs:tx-all-pad-packets>40</tfs:tx-all-pad-packets>
<tfs:tx-all-pad-octets>40000</tfs:tx-all-pad-octets>
<tfs:rx-inner-packets>240</tfs:rx-inner-packets>
<tfs:rx-inner-octets>95000</tfs:rx-inner-octets>
<tfs:rx-extra-pad-packets>150</tfs:rx-extra-pad-packets>
<tfs:rx-extra-pad-octets>25000</tfs:rx-extra-pad-octets>
<tfs:rx-all-pad-packets>20</tfs:rx-all-pad-packets>
<tfs:rx-all-pad-octets>20000</tfs:rx-all-pad-octets>
<tfs:rx-errored-packets>0</tfs:rx-errored-packets>
<tfs:rx-missed-packets>0</tfs:rx-missed-packets>
<tfs:rx-incomplete-inner-packets>0</tfs:rx-incomplete-inner-packets>
</tfs:iptfs-stats>
</i:sad-entry>
</i:sad>
</i:ipsec-ikeless>