Operations Model for Router Keying
draft-ietf-karp-ops-model-05
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (karp WG)
|
|
Last updated |
|
2013-02-25
|
|
Replaces |
|
draft-hartman-karp-ops-model
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group S. Hartman
Internet-Draft Painless Security
Intended status: Informational D. Zhang
Expires: August 29, 2013 Huawei
February 25, 2013
Operations Model for Router Keying
draft-ietf-karp-ops-model-05.txt
Abstract
Developing an operational and management model for routing protocol
security that works across protocols will be critical to the success
of routing protocol security efforts. This document discusses issues
and begins to consider development of these models.
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 August 29, 2013.
Copyright Notice
Copyright (c) 2013 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.
Hartman & Zhang Expires August 29, 2013 [Page 1]
Internet-Draft Operations Model for Router Keying February 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements notation . . . . . . . . . . . . . . . . . . . . 4
3. Breakdown of KARP configuration . . . . . . . . . . . . . . . 5
3.1. Integrity of the Key Table . . . . . . . . . . . . . . . . 6
3.2. Management of Key Table . . . . . . . . . . . . . . . . . 6
3.3. Interactions with Automated Key Management . . . . . . . . 7
3.4. Virtual Routing and Forwarding Instances (VRFs) . . . . . 7
4. Credentials and Authorization . . . . . . . . . . . . . . . . 8
4.1. Preshared Keys . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1. Sharing Keys and Zones of Trust . . . . . . . . . . . 10
4.1.2. Key Separation and Protocol Design . . . . . . . . . . 10
4.2. Asymmetric Keys . . . . . . . . . . . . . . . . . . . . . 11
4.3. Public Key Infrastructure . . . . . . . . . . . . . . . . 12
4.4. The role of Central Servers . . . . . . . . . . . . . . . 12
5. Grouping Peers Together . . . . . . . . . . . . . . . . . . . 14
6. Administrator Involvement . . . . . . . . . . . . . . . . . . 16
6.1. Enrollment . . . . . . . . . . . . . . . . . . . . . . . . 16
6.2. Handling Faults . . . . . . . . . . . . . . . . . . . . . 16
7. Upgrade Considerations . . . . . . . . . . . . . . . . . . . . 18
8. Security Considerations . . . . . . . . . . . . . . . . . . . 19
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
10.1. Normative References . . . . . . . . . . . . . . . . . . . 21
10.2. Informative References . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
Hartman & Zhang Expires August 29, 2013 [Page 2]
Internet-Draft Operations Model for Router Keying February 2013
1. Introduction
The KARP working group is designing improvements to the cryptographic
authentication of IETF routing protocols. These improvements include
improvements to how integrity functions are handled within each
protocol as well as designing an automated key management solution.
This document discusses issues to consider when thinking about the
operational and management model for KARP. Each implementation will
take its own approach to management; this is one area for vendor
differentiation. However, it is desirable to have a common baseline
for the management objects allowing administrators, security
architects and protocol designers to understand what management
Show full document text