rfc9173v4.txt   rfc9173.txt 
Internet Engineering Task Force (IETF) E. Birrane, III Internet Engineering Task Force (IETF) E. Birrane, III
Request for Comments: 9173 A. White Request for Comments: 9173 A. White
Category: Standards Track S. Heiner Category: Standards Track S. Heiner
ISSN: 2070-1721 JHU/APL ISSN: 2070-1721 JHU/APL
December 2021 January 2022
Default Security Contexts for Bundle Protocol Security (BPSec) Default Security Contexts for Bundle Protocol Security (BPSec)
Abstract Abstract
This document defines default integrity and confidentiality security This document defines default integrity and confidentiality security
contexts that can be used with Bundle Protocol Security (BPSec) contexts that can be used with Bundle Protocol Security (BPSec)
implementations. These security contexts are intended to be used implementations. These security contexts are intended to be used
both for testing the interoperability of BPSec implementations and both for testing the interoperability of BPSec implementations and
for providing basic security operations when no other security for providing basic security operations when no other security
skipping to change at line 35 skipping to change at line 35
received public review and has been approved for publication by the received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841. Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9173. https://www.rfc-editor.org/info/rfc9173.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Revised BSD License text as described in Section 4.e of the include Revised BSD License text as described in Section 4.e of the
Trust Legal Provisions and are provided without warranty as described Trust Legal Provisions and are provided without warranty as described
skipping to change at line 1550 skipping to change at line 1550
Sequences", RFC 8742, DOI 10.17487/RFC8742, February 2020, Sequences", RFC 8742, DOI 10.17487/RFC8742, February 2020,
<https://www.rfc-editor.org/info/rfc8742>. <https://www.rfc-editor.org/info/rfc8742>.
[RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object [RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object
Representation (CBOR)", STD 94, RFC 8949, Representation (CBOR)", STD 94, RFC 8949,
DOI 10.17487/RFC8949, December 2020, DOI 10.17487/RFC8949, December 2020,
<https://www.rfc-editor.org/info/rfc8949>. <https://www.rfc-editor.org/info/rfc8949>.
[RFC9171] Burleigh, S., Fall, K., and E. Birrane, III, "Bundle [RFC9171] Burleigh, S., Fall, K., and E. Birrane, III, "Bundle
Protocol Version 7", RFC 9171, DOI 10.17487/RFC9171, Protocol Version 7", RFC 9171, DOI 10.17487/RFC9171,
December 2021, <https://www.rfc-editor.org/rfc/rfc9171>. January 2022, <https://www.rfc-editor.org/rfc/rfc9171>.
[RFC9172] Birrane, III, E. and K. McKeever, "Bundle Protocol [RFC9172] Birrane, III, E. and K. McKeever, "Bundle Protocol
Security (BPSec)", RFC 9172, DOI 10.17487/RFC9172, Security (BPSec)", RFC 9172, DOI 10.17487/RFC9172, January
December 2021, <https://www.rfc-editor.org/rfc/rfc9172>. 2022, <https://www.rfc-editor.org/rfc/rfc9172>.
[SHS] National Institute of Standards and Technology, "Secure [SHS] National Institute of Standards and Technology, "Secure
Hash Standard (SHS)", FIPS PUB 180-4, Hash Standard (SHS)", FIPS PUB 180-4,
DOI 10.6028/NIST.FIPS.180-4, August 2015, DOI 10.6028/NIST.FIPS.180-4, August 2015,
<https://csrc.nist.gov/publications/detail/fips/180/4/ <https://csrc.nist.gov/publications/detail/fips/180/4/
final>. final>.
Appendix A. Examples Appendix A. Examples
This appendix is informative. This appendix is informative.
skipping to change at line 1581 skipping to change at line 1581
of bundles, security blocks, and the encoding of security context of bundles, security blocks, and the encoding of security context
parameters and results. For this reason, they can inform unit test parameters and results. For this reason, they can inform unit test
suites for individual implementations as well as interoperability suites for individual implementations as well as interoperability
test suites amongst implementations. However, these examples do not test suites amongst implementations. However, these examples do not
cover every permutation of security context parameters, security cover every permutation of security context parameters, security
results, or use of security blocks in a bundle. results, or use of security blocks in a bundle.
NOTES: NOTES:
* The bundle diagrams in this appendix are patterned after the * The bundle diagrams in this appendix are patterned after the
bundle diagrams used in Section 3.11 ("BSP Block Examples") of bundle diagrams used in Section 3.11 ("BPSec Block Examples") of
[RFC9172]. [RFC9172].
* Figures in this appendix identified as "(CBOR Diagnostic * Figures in this appendix identified as "(CBOR Diagnostic
Notation)" are represented using the CBOR diagnostic notation Notation)" are represented using the CBOR diagnostic notation
defined in [RFC8949]. This notation is used to express CBOR data defined in [RFC8949]. This notation is used to express CBOR data
structures in a manner that enables visual inspection. The structures in a manner that enables visual inspection. The
bundles, security blocks, and security context contents in these bundles, security blocks, and security context contents in these
figures are represented using CBOR structures. In cases where BP figures are represented using CBOR structures. In cases where BP
blocks (to include BPSec security blocks) are comprised of a blocks (to include BPSec security blocks) are comprised of a
sequence of CBOR objects, these objects are represented as a CBOR sequence of CBOR objects, these objects are represented as a CBOR
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/