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:    [email protected],
                    [email protected],
                    [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
IETF-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-announce

Reply via email to