RFC 9348 on A YANG Data Model for IP Traffic Flow Security
rfc-editor@rfc-editor.org Wed, 01 February 2023 05:35 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9192C169501; Tue, 31 Jan 2023 21:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id poj_LtT1kG82; Tue, 31 Jan 2023 21:35:05 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6248FC16951B; Tue, 31 Jan 2023 21:34:56 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 457FEA4C9; Tue, 31 Jan 2023 21:34:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9348 on A YANG Data Model for IP Traffic Flow Security
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipsec@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230201053456.457FEA4C9@rfcpa.amsl.com>
Date: Tue, 31 Jan 2023 21:34:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/rmXI0rnadsmEvwatgVi3GCkla18>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2023 05:35:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9348
Title: A YANG Data Model for IP Traffic Flow Security
Author: D. Fedyk,
C. Hopps
Status: Standards Track
Stream: IETF
Date: January 2023
Mailbox: dfedyk@labn.net,
chopps@chopps.org
Pages: 25
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipsecme-yang-iptfs-11.txt
URL: https://www.rfc-editor.org/info/rfc9348
DOI: 10.17487/RFC9348
This document describes a YANG module for the management of IP
Traffic Flow Security (IP-TFS) additions to Internet Key Exchange
Protocol version 2 (IKEv2) and IPsec.
This document is a product of the IP Security Maintenance and Extensions 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