[I2nsf] Fwd: I-D Action: draft-ietf-i2nsf-sdn-ipsec-flow-protection-05.txt

Rafa Marin-Lopez <rafa@um.es> Tue, 16 July 2019 12:42 UTC

Return-Path: <rafa@um.es>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 833AC120412; Tue, 16 Jul 2019 05:42:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id J8U043Bzk-2j; Tue, 16 Jul 2019 05:42:45 -0700 (PDT)
Received: from xenon42.um.es (xenon42.um.es [IPv6:2001:720:1710:601::42]) by ietfa.amsl.com (Postfix) with ESMTP id 204AB12004F; Tue, 16 Jul 2019 05:42:45 -0700 (PDT)
Received: from localhost (localhost []) by xenon42.um.es (Postfix) with ESMTP id 8D4AE1FF1C; Tue, 16 Jul 2019 14:42:40 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon42.um.es
Received: from xenon42.um.es ([]) by localhost (xenon42.um.es []) (amavisd-new, port 10024) with LMTP id ZX4_1DnDfU3h; Tue, 16 Jul 2019 14:42:40 +0200 (CEST)
Received: from quantum.inf.um.es (quantum.inf.um.es []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon42.um.es (Postfix) with ESMTPSA id 79E3A1FE6A; Tue, 16 Jul 2019 14:42:37 +0200 (CEST)
From: Rafa Marin-Lopez <rafa@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C449926D-3684-4DC9-BC8B-A54674982BAD"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 16 Jul 2019 14:42:35 +0200
References: <156253524318.473.14686910090362577746@ietfa.amsl.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, "ipsec@ietf.org WG" <ipsec@ietf.org>, Gabriel Lopez <gabilm@um.es>, =?utf-8?B?RmVybmFuZG8gUGVyZcOxw61ndWV6IEdhcmPDrWE=?= <fernando.pereniguez@cud.upct.es>, mbj@tail-f.com
To: i2nsf@ietf.org
Message-Id: <4E36A715-3B6C-4BDF-A149-9E10574E3F96@um.es>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/9TEiLwmjQklkbCoppZGTf2Z30As>
Subject: [I2nsf] Fwd: I-D Action: draft-ietf-i2nsf-sdn-ipsec-flow-protection-05.txt
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2019 12:42:49 -0000

Dear all:

We submitted a new version of the I-D (v05) where we have applied several changes. In the following you have a summary of the main changes, which we will expand/explain during our presentation: 

- We have dealt with YANG doctors’ review (Martin's)

- We have dealt with Paul Wouters’ comments and Tero’s comments.

- We have added more specific text in the descriptions.

- Notifications have a simpler format now since most of the information that contained in the past is already handled by the Security Controller.

- State data has been reduced. For example, in IKE case, most of the information is related with IKE and not with the specific details about IPsec SAs that IKE handles (after all, IKE can abstract this information from the Security Controller).

- We have included text in the security section to discuss about the default IPsec policies that should be in the NSF when it starts before contacting with the SC such as the IPsec policies required to allow traffic between the SC and the NSF.

- We have added a subsection 5.3.4 about NSF discovery by the Security Controller.

- In order to specify the crypto-algorithms we have used a simple approach by including an integer and adding a text pointing the IANA in the reference clause. For example:

typedef encryption-algorithm-type {
           type uint32;
               "The encryption algorithm is specified with a 32-bit
               number extracted from IANA Registry. The acceptable
               values MUST follow the requirement levels for
               encryption algorithms for ESP and IKEv2.";
                "IANA Registry- Transform Type 1 - Encryption
                Algorithm Transform IDs. RFC 8221 - Cryptographic
                Algorithm Implementation Requirements and Usage
                Guidance for Encapsulating Security Payload (ESP)
                and Authentication Header (AH) and RFC 8247 -
                Algorithm Implementation Requirements and Usage
                Guidance for the Internet Key Exchange Protocol
                Version 2 (IKEv2).";

- We have included three additional Annexes with examples in about the usage of the YANG model.

- We have performed pyang --lint --lint-ensure-hyphenated-names and pyang -f yang --yang-line-length 69 in our model without warnings.

Best Regards.

> Inicio del mensaje reenviado:
> De: internet-drafts@ietf.org
> Asunto: [I2nsf] I-D Action: draft-ietf-i2nsf-sdn-ipsec-flow-protection-05.txt
> Fecha: 7 de julio de 2019, 23:34:03 CEST
> Para: <i-d-announce@ietf.org>
> Cc: i2nsf@ietf.org
> Responder a: i2nsf@ietf.org
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Interface to Network Security Functions WG of the IETF.
>        Title           : Software-Defined Networking (SDN)-based IPsec Flow Protection
>        Authors         : Rafa Marin-Lopez
>                          Gabriel Lopez-Millan
>                          Fernando Pereniguez-Garcia
> 	Filename        : draft-ietf-i2nsf-sdn-ipsec-flow-protection-05.txt
> 	Pages           : 81
> 	Date            : 2019-07-07
> Abstract:
>   This document describes how providing IPsec-based flow protection by
>   means of a Software-Defined Network (SDN) controller (aka.  Security
>   Controller) and establishes the requirements to support this service.
>   It considers two main well-known scenarios in IPsec: (i) gateway-to-
>   gateway and (ii) host-to-host.  The SDN-based service described in
>   this document allows the distribution and monitoring of IPsec
>   information from a Security Controller to one or several flow-based
>   Network Security Function (NSF).  The NSFs implement IPsec to protect
>   data traffic between network resources.
>   The document focuses on the NSF Facing Interface by providing models
>   for configuration and state data required to allow the Security
>   Controller to configure the IPsec databases (SPD, SAD, PAD) and IKEv2
>   to establish Security Associations with a reduced intervention of the
>   network administrator.
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-05
> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-05
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-05
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf

Rafa Marin-Lopez, PhD
Dept. Information and Communications Engineering (DIIC)
Faculty of Computer Science-University of Murcia
30100 Murcia - Spain
Telf: +34868888501 Fax: +34868884151 e-mail: rafa@um.es