[dtn] RFC 9173 on Default Security Contexts for Bundle Protocol Security (BPSec)
rfc-editor@rfc-editor.org Tue, 01 February 2022 07:03 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 741FF3A1952; Mon, 31 Jan 2022 23:03:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 aFrNb9iLHWB1; Mon, 31 Jan 2022 23:03:09 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 270763A18D3; Mon, 31 Jan 2022 23:02:53 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 106E61F8F6F6; Mon, 31 Jan 2022 23:02:53 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dtn@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220201070253.106E61F8F6F6@rfc-editor.org>
Date: Mon, 31 Jan 2022 23:02:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/bBN2nkc8zJJOIFcU_XBh-n9rLsQ>
Subject: [dtn] RFC 9173 on Default Security Contexts for Bundle Protocol Security (BPSec)
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2022 07:03:20 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9173
Title: Default Security Contexts for Bundle
Protocol Security (BPSec)
Author: E. Birrane, III,
A. White,
S. Heiner
Status: Standards Track
Stream: IETF
Date: January 2022
Mailbox: edward.birrane@jhuapl.edu,
alex.white@jhuapl.edu,
sarah.heiner@jhuapl.edu
Pages: 51
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dtn-bpsec-default-sc-11.txt
URL: https://www.rfc-editor.org/info/rfc9173
DOI: 10.17487/RFC9173
This document defines default integrity and confidentiality security
contexts that can be used with Bundle Protocol Security (BPSec)
implementations. These security contexts are intended to be used
both for testing the interoperability of BPSec implementations and
for providing basic security operations when no other security
contexts are defined or otherwise required for a network.
This document is a product of the Delay/Disruption Tolerant Networking 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