Network Working Group M. Richardson
Internet-Draft SSW
Intended status: Informational December 18, 2013
Expires: June 21, 2014
security architecture for 6top: requirements and structure
draft-richardson-6tisch-security-architecture-00
Abstract
This document details minimal layer-2 requirements for 6top use in
industrial settings, and a few options for accomplishing this. The
layer-2 mechanism is then extended to provide for per-node
authentication and authorization of the node/PCE communications.
This internet-draft is intended for later inclusion into the 6tisch
architecture document.
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 http://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 June 21, 2014.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
Richardson Expires June 21, 2014 [Page 1]
Internet-Draft 6tisch-security December 2013
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://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
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: security bootstrap requirements . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. possible layer-2 mechanism . . . . . . . . . . . . . . . . . 2
4. 6top/PCE security requirements . . . . . . . . . . . . . . . 2
5. leveraging layer-2 identies for layer-4 security . . . . . . 2
6. Security Considerations . . . . . . . . . . . . . . . . . . . 2
7. Other Related Protocols . . . . . . . . . . . . . . . . . . . 3
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
10.1. Informative References . . . . . . . . . . . . . . . . . 3
10.2. Normative References . . . . . . . . . . . . . . . . . . 3
11. Normative references . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction: security bootstrap requirements
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. possible layer-2 mechanism
4. 6top/PCE security requirements
5. leveraging layer-2 identies for layer-4 security
6. Security Considerations
Richardson Expires June 21, 2014 [Page 2]
Internet-Draft 6tisch-security December 2013
7. Other Related Protocols
8. IANA Considerations
9. Acknowledgements
10. References
10.1. Informative References
10.2. Normative References
11. Normative references
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
Author's Address
Michael C. Richardson
Sandelman Software Works
470 Dawson Avenue
Ottawa, ON K1Z 5V7
CA
Email: mcr+ietf@sandelman.ca
URI: http://www.sandelman.ca/
Richardson Expires June 21, 2014 [Page 3]