Labeled IPsec Traffic Selector support for IKEv2
draft-ietf-ipsecme-labeled-ipsec-04
Network P. Wouters
Internet-Draft S. Prasad
Updates: 7296 (if approved) Red Hat
Intended status: Standards Track October 30, 2020
Expires: May 3, 2021
Labeled IPsec Traffic Selector support for IKEv2
draft-ietf-ipsecme-labeled-ipsec-04
Abstract
This document defines a new Traffic Selector (TS) Type for Internet
Key Exchange version 2 to add support for negotiating Mandatory
Access Control (MAC) security labels as a traffic selector of the
Security Policy Database (SPD). Security Labels for IPsec are also
known as "Labeled IPsec". The new TS type is TS_SECLABEL, which
consists of a variable length opaque field specifying the security
label. This document updates the IKEv2 TS negotiation specified in
RFC 7296 Section 2.9.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 3, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Wouters & Prasad Expires May 3, 2021 [Page 1]
Internet-Draft Labeled IPsec October 2020
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Traffic Selector clarification . . . . . . . . . . . . . 3
1.3. Traffic Selector update . . . . . . . . . . . . . . . . . 4
2. TS_SECLABEL Traffic Selector Type . . . . . . . . . . . . . . 4
2.1. TS_SECLABEL payload format . . . . . . . . . . . . . . . 4
2.2. TS_SECLABEL properties . . . . . . . . . . . . . . . . . 4
3. Traffic Selector negotiation . . . . . . . . . . . . . . . . 5
3.1. Example TS negotiation . . . . . . . . . . . . . . . . . 6
3.2. Considerations for using multiple TS_TYPEs in a TS . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 7
6.1. Libreswan . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
In computer security, Mandatory Access Control usually refers to
systems in which all subjects and objects are assigned a security
label. A security label is comprised of a set of security
attributes. The security labels along with a system authorization
policy determine access. Rules within the system authorization
policy determine whether the access will be granted based on the
security attributes of the subject and object.
Traditionally, security labels used by Multilevel Systems (MLS) are
comprised of a sensitivity level (or classification) field and a
compartment (or category) field, as defined in [FIPS188] and
[RFC5570]. As MAC systems evolved, other MAC models gained in
popularity. For example, SELinux, a Flux Advanced Security Kernel
(FLASK) implementation, has security labels represented as colon-
separated ASCII strings composed of values for identity, role, and
type. The security labels are often referred to as security
contexts.
Wouters & Prasad Expires May 3, 2021 [Page 2]
Show full document text