Dear all:

After receiving a suggestion to make things clearer in the feature 
ikeless-notification description, we have just uploaded a new version -11 with 
a minor change to add the following text:

feature ikeless-notification { 
            description 
                "This feature indicates that the server supports
                generating notifications in the ikeless module.
                
                To ensure broader applicability of this module, 
                the notifications are marked as a feature. 
                For the implementation of ikeless case, 
                the NSF is expected to implement this 
                feature.";
        } 

Best Regards.

> Inicio del mensaje reenviado:
> 
> De: [email protected]
> Asunto: New Version Notification for 
> draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
> Fecha: 22 de octubre de 2020, 15:32:50 CEST
> Para: "Fernando Pereniguez-Garcia" <[email protected]>, "Rafael 
> Lopez" <[email protected]>, "Gabriel Lopez-Millan" <[email protected]>, "Rafa 
> Marin-Lopez" <[email protected]>
> 
> 
> A new version of I-D, draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
> has been successfully submitted by Rafa Marin-Lopez and posted to the
> IETF repository.
> 
> Name:         draft-ietf-i2nsf-sdn-ipsec-flow-protection
> Revision:     11
> Title:                Software-Defined Networking (SDN)-based IPsec Flow 
> Protection
> Document date:        2020-10-22
> Group:                i2nsf
> Pages:                92
> URL:            
> https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
> Status:         
> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/
> Htmlized:       
> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection
> Htmlized:       
> https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
> Diff:           
> https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
> 
> Abstract:
>   This document describes how to provide IPsec-based flow protection
>   (integrity and confidentiality) by means of an Interface to Network
>   Security Function (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 Security Associations (SAs)
>   from a I2NSF Controller to one or several flow-based Network Security
>   Functions (NSFs) that rely on IPsec to protect data traffic.
> 
>   The document focuses on the I2NSF NSF-facing interface by providing
>   YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
>   and IKEv2.  This allows IPsec SA establishment with minimal
>   intervention by the network administrator.  It does not define any
>   new protocol.
> 
> 
> 
> 
> 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.
> 
> 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: [email protected]
-------------------------------------------------------




_______________________________________________
I2nsf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2nsf

Reply via email to