IETF Logo Mail Archive

Re: [I2nsf] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-08.txt

Rafa Marin-Lopez <rafa@um.es> Wed, 17 June 2020 15:50 UTC

Return-Path: <rafa@um.es>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C12703A0928 for <i2nsf@ietfa.amsl.com>; Wed, 17 Jun 2020 08:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=um.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VEut9GkVLDs for <i2nsf@ietfa.amsl.com>; Wed, 17 Jun 2020 08:50:22 -0700 (PDT)
Received: from mx02.puc.rediris.es (outbound4sev.lav.puc.rediris.es [130.206.19.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C2853A0929 for <i2nsf@ietf.org>; Wed, 17 Jun 2020 08:50:22 -0700 (PDT)
Received: from xenon43.um.es (xenon43.um.es [155.54.212.170]) by mx02.puc.rediris.es with ESMTP id 05HFoAee002821-05HFoAef002821; Wed, 17 Jun 2020 17:50:10 +0200
Received: from localhost (localhost [127.0.0.1]) by xenon43.um.es (Postfix) with ESMTP id A1EC420FBE; Wed, 17 Jun 2020 17:50:10 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon43.um.es
Received: from xenon43.um.es ([127.0.0.1]) by localhost (xenon43.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Z1p7_JC19bFe; Wed, 17 Jun 2020 17:50:10 +0200 (CEST)
Received: from [192.168.1.41] (85.red-88-11-216.dynamicip.rima-tde.net [88.11.216.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon43.um.es (Postfix) with ESMTPSA id 7F9F71FF19; Wed, 17 Jun 2020 17:50:09 +0200 (CEST)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <B382BACC-82DB-4BEF-8E16-059E5B78C8D1@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_170886AF-C2DF-44EB-BA4B-3081CA7B14D6"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Wed, 17 Jun 2020 17:50:08 +0200
In-Reply-To: <159240856978.14608.2680457798997255985@ietfa.amsl.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, Gabriel Lopez-Millan <gabilm@um.es>
To: i2nsf@ietf.org, Roman Danyliw <rdd@cert.org>
References: <159240856978.14608.2680457798997255985@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.104.14)
Authentication-Results: mx02.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.170 as permitted sender) smtp.mailfrom=rafa@um.es
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=um.es; s=DKIM; c=relaxed/relaxed; h=from:message-id:content-type:mime-version:subject:date:cc:to:references; bh=IRNV24ToGb/FeQYahTRwIyAZXGjoZ1Y/Mx31jZ7CXOU=; b=aHjiHeFaQ9ykRWB/xlxyBsxpoFG6Twrpu0cgoV515i2VsCETRXXZdyRLguyhsEt4XO4LD2yv2gWU XGpF+1hVbAxnISH4T2wqEfzN0DnaJOIphOQbbKkpXX2XdqYeF+zp2GTTdXylWKszC1XK5njXDBxA IGUoSklMEpLFp29RVHbGtBVjC9S5G47G3haEbOXHx76QX9dBy2SxihC2HyuEUh5+hZc7PRWU1TBC xxN0FXQyVi5Ovx80uCM1zjUUoYTW+4IUvymEgcUNgATomsMBkJ9T3+tgzT2PgEg/RggxTF1AMe+P fj2QbkrTg+G6hpOvTKI1pexPEXOLzX+PB3YURg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/6ZSTv3y4l2emn2MaBfr1RnSKp9Y>
Subject: Re: [I2nsf] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-08.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: Wed, 17 Jun 2020 15:50:25 -0000

Dear all, Roman:

We have just submitted -08 that tries to address Roman’s comments. 

Roman, thank you very much again for all your comments. Hope we have been able to correctly address them.

Best Regards. 

> El 17 jun 2020, a las 17:42, internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> escribió:
> 
> 
> A new version of I-D, draft-ietf-i2nsf-sdn-ipsec-flow-protection-08.txt
> has been successfully submitted by Rafa Marin-Lopez and posted to the
> IETF repository.
> 
> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
> Revision:	08
> Title:		Software-Defined Networking (SDN)-based IPsec Flow Protection
> Document date:	2020-06-17
> Group:		i2nsf
> Pages:		87
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-i2nsf-sdn-ipsec-flow-protection-08.txt <https://www.ietf.org/internet-drafts/draft-ietf-i2nsf-sdn-ipsec-flow-protection-08.txt>
> Status:         https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/ <https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/>
> Htmlized:       https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-08 <https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-08>
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection <https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection>
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-08 <https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-08>
> 
> Abstract:
>   This document describes how to provide IPsec-based flow protection
>   (integrity and confidentiality) by means of an I2NSF Controller.  It
>   considers two main well-known scenarios in IPsec: (i) gateway-to-
>   gateway and (ii) host-to-host.  The service described in this
>   document allows the configuration and monitoring of IPsec information
>   from a I2NSF Controller to one or several flow-based Network Security
>   Function (NSF) that implement IPsec to protect data traffic.
> 
>   The document focuses on the I2NSF NSF-Facing Interface by providing
>   YANG data models for configuration and state data required to allow
>   the I2NSF Controller to configure the IPsec databases (SPD, SAD, PAD)
>   and IKEv2 to establish IPsec Security Associations with a reduced
>   intervention of the network administrator.
> 
> 
> 
> 
> 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 <http://tools.ietf.org/>.
> 
> The IETF Secretariat
> 
> 

-------------------------------------------------------
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 <mailto:rafa@um.es>
-------------------------------------------------------

v2.23.0 | Report a Bug | By Email