table of contents for security architecture
draft-richardson-6tisch-table-of-contents-00

Abstract

This is a template for a security architecture.

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 December 5, 2014.

Copyright Notice

Copyright (c) 2014 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 (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. security requirements
• 1.1. thread model
• 1.2. implementation cost
• 1.3. denial of service
• 2. protocol requirements/constraints/assumptions
• 2.1. inline/offline
• 3. time sequence diagram
• 3.1. explanation of each step
• 3.2. size of each packet
• 4. resulting security properties obtained from this process
• 5. deployment scenarios underlying protocol requirements
• 6. device identification
• 6.1. PCE/Proxy vs Node identification
• 6.2. Time source authentication / time validation
• 6.3. description of certificate contents
• 6.4. privacy aspects
• 7. slotframes to be used during join
• 8. configuration aspects
• 9. authorization aspects
• 9.1. how to determine a proxy/PCE from a end node
• 9.2. security considerations
• 10. security architecture
• 11. Posture Maintenance
• 12. Security Considerations
• 13. Other Related Protocols
• 14. IANA Considerations
• 15. Acknowledgements
• 16. Normative references
• Author's Address

1. security requirements

1.1. thread model

1.2. implementation cost

(storage of security material, computational cost)

1.3. denial of service

other communication impacts of security protocol mechanics

2. protocol requirements/constraints/assumptions

2.1. inline/offline

dependencies on centralized or external functionality, inline and offline

3. time sequence diagram

3.1. explanation of each step

3.2. size of each packet

and number of frames needed to contain it.

4. resulting security properties obtained from this process

5. deployment scenarios underlying protocol requirements

6. device identification

6.1. PCE/Proxy vs Node identification

6.2. Time source authentication / time validation

Note: RPL Root authentication is a chartered item

6.3. description of certificate contents

6.4. privacy aspects

7. slotframes to be used during join

how is this communicated in the (extended) beacon.

8. configuration aspects

(allocation of slotframes after join, network statistics, neighboetc.)

9. authorization aspects

lifecycle (key management, trust management)

9.1. how to determine a proxy/PCE from a end node

9.2. security considerations

what prevents a node from transmitting when it is not their turn (part one: jamming)

can a node successfully communicate with a peer at a time when not supposed to, may be tied to link layer security, or will it be policed by receiver?

10. security architecture

security architecture and fit of e.g. join protocol and provisioning into this

11. Posture Maintenance

(SACM related work)

12. Security Considerations

13. Other Related Protocols

14. IANA Considerations

15. Acknowledgements

16. Normative references

Author's Address