[I2nsf] RFC 9061 on A YANG Data Model for IPsec Flow Protection Based on Software-Defined Networking (SDN)

rfc-editor@rfc-editor.org Thu, 15 July 2021 06:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 9C05A3A1E59; Wed, 14 Jul 2021 23:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 qcA6XuOYxVZG; Wed, 14 Jul 2021 23:17:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F0B13A1E57; Wed, 14 Jul 2021 23:17:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5BD56F406F2; Wed, 14 Jul 2021 23:17:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, i2nsf@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210715061735.5BD56F406F2@rfc-editor.org>
Date: Wed, 14 Jul 2021 23:17:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/w0fObsx9eBjfxtOh6UgNQDhHsyA>
Subject: [I2nsf] RFC 9061 on A YANG Data Model for IPsec Flow Protection Based on Software-Defined Networking (SDN)
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: Thu, 15 Jul 2021 06:17:46 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9061

        Title:      A YANG Data Model for IPsec Flow Protection
                    Based on Software-Defined Networking (SDN) 
        Author:     R. Marin-Lopez,
                    G. Lopez-Millan,
                    F. Pereniguez-Garcia
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2021
        Mailbox:    rafa@um.es,
                    gabilm@um.es,
                    fernando.pereniguez@cud.upct.es
        Pages:      90
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-i2nsf-sdn-ipsec-flow-protection-14.txt

        URL:        https://www.rfc-editor.org/info/rfc9061

        DOI:        10.17487/RFC9061

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: gateway-to-gateway and host-to-host.
The service described in this document allows the configuration and
monitoring of IPsec Security Associations (IPsec SAs) from an I2NSF
Controller to one or several flow-based Network Security Functions
(NSFs) that rely on IPsec to protect data traffic. 

This document focuses on the I2NSF NSF-Facing Interface by providing
YANG data models for configuring the IPsec databases, namely Security
Policy Database (SPD), Security Association Database (SAD), Peer
Authorization Database (PAD), and Internet Key Exchange Version 2
(IKEv2). This allows IPsec SA establishment with minimal intervention
by the network administrator. This document defines three YANG
modules, but it does not define any new protocol.

This document is a product of the Interface to Network Security Functions Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC