draft-ietf-anima-stable-connectivity-01.txt   draft-ietf-anima-stable-connectivity-02.txt 
ANIMA T. Eckert ANIMA T. Eckert
Internet-Draft M. Behringer Internet-Draft Huawei
Intended status: Informational Cisco Intended status: Informational M. Behringer
Expires: January 9, 2017 July 8, 2016 Expires: August 11, 2017 Cisco
February 7, 2017
Using Autonomic Control Plane for Stable Connectivity of Network OAM Using Autonomic Control Plane for Stable Connectivity of Network OAM
draft-ietf-anima-stable-connectivity-01 draft-ietf-anima-stable-connectivity-02
Abstract Abstract
OAM (Operations, Administration and Management) processes for data OAM (Operations, Administration and Management) processes for data
networks are often subject to the problem of circular dependencies networks are often subject to the problem of circular dependencies
when relying on network connectivity of the network to be managed for when relying on network connectivity of the network to be managed for
the OAM operations itself. Provisioning during device/network bring the OAM operations itself. Provisioning during device/network bring
up tends to be far less easy to automate than service provisioning up tends to be far less easy to automate than service provisioning
later on, changes in core network functions impacting reachability later on, changes in core network functions impacting reachability
can not be automated either because of ongoing connectivity can not be automated either because of ongoing connectivity
skipping to change at page 1, line 43 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 9, 2017. This Internet-Draft will expire on August 11, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Self dependent OAM connectivity . . . . . . . . . . . . . 2 1.1. Self dependent OAM connectivity . . . . . . . . . . . . . 3
1.2. Data Communication Networks (DCNs) . . . . . . . . . . . 3 1.2. Data Communication Networks (DCNs) . . . . . . . . . . . 3
1.3. Leveraging the ACP . . . . . . . . . . . . . . . . . . . 3 1.3. Leveraging the ACP . . . . . . . . . . . . . . . . . . . 4
2. Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Stable connectivity for centralized OAM operations . . . 4 2.1. Stable connectivity for centralized OAM operations . . . 4
2.1.1. Simple connectivity for non-autonomic NOC application 2.1.1. Simple connectivity for non-autonomic NOC application
devices . . . . . . . . . . . . . . . . . . . . . . . 4 devices . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.2. Limitations and enhancement overview . . . . . . . . 5 2.1.2. Limitations and enhancement overview . . . . . . . . 5
2.1.3. Simultaneous ACP and data plane connectivity . . . . 6 2.1.3. Simultaneous ACP and data plane connectivity . . . . 6
2.1.4. IPv4 only NOC application devices . . . . . . . . . . 7 2.1.4. IPv4 only NOC application devices . . . . . . . . . . 7
2.1.5. Path selection policies . . . . . . . . . . . . . . . 8 2.1.5. Path selection policies . . . . . . . . . . . . . . . 8
2.1.6. Autonomic NOC device/applications . . . . . . . . . . 10 2.1.6. Autonomic NOC device/applications . . . . . . . . . . 10
2.1.7. Encryption of data-plane connections . . . . . . . . 10 2.1.7. Encryption of data-plane connections . . . . . . . . 10
2.1.8. Long term direction of the solution . . . . . . . . . 11 2.1.8. Long term direction of the solution . . . . . . . . . 11
2.2. Stable connectivity for distributed network/OAM functions 12 2.2. Stable connectivity for distributed network/OAM functions 12
3. Security Considerations . . . . . . . . . . . . . . . . . . . 12 3. Security Considerations . . . . . . . . . . . . . . . . . . . 12
4. No IPv4 for ACP . . . . . . . . . . . . . . . . . . . . . . . 14 4. No IPv4 for ACP . . . . . . . . . . . . . . . . . . . . . . . 14
5. Further considerations . . . . . . . . . . . . . . . . . . . 14 5. Further considerations . . . . . . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
8. Change log [RFC Editor: Please remove] . . . . . . . . . . . 15 8. Change log [RFC Editor: Please remove] . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
1.1. Self dependent OAM connectivity 1.1. Self dependent OAM connectivity
OAM (Operations, Administration and Management) processes for data OAM (Operations, Administration and Management) processes for data
networks are often subject to the problem of circular dependencies networks are often subject to the problem of circular dependencies
when relying on network connectivity of the network to be managed for when relying on network connectivity of the network to be managed for
the OAM operations itself: the OAM operations itself:
The ability to perform OAM operations on a network device requires The ability to perform OAM operations on a network device requires
first the execution of OAM procedures necessary to create network first the execution of OAM procedures necessary to create network
connectivity to that device in all intervening devices. This connectivity to that device in all intervening devices. This
skipping to change at page 15, line 7 skipping to change at page 15, line 18
Systems, which started in early 2010 including customers involved in Systems, which started in early 2010 including customers involved in
the design and early testing. Many people contributed to the aspects the design and early testing. Many people contributed to the aspects
described in this document, including in alphabetical order: BL described in this document, including in alphabetical order: BL
Balaji, Steinthor Bjarnason, Yves Herthoghs, Sebastian Meissner, Ravi Balaji, Steinthor Bjarnason, Yves Herthoghs, Sebastian Meissner, Ravi
Kumar Vadapalli. The author would also like to thank Michael Kumar Vadapalli. The author would also like to thank Michael
Richardson, James Woodyatt and Brian Carpenter for their review and Richardson, James Woodyatt and Brian Carpenter for their review and
comments. comments.
8. Change log [RFC Editor: Please remove] 8. Change log [RFC Editor: Please remove]
01: Refresh timeout. Stable document, change in author
association.
01: Refresh timeout. Stable document, no changes. 01: Refresh timeout. Stable document, no changes.
00: Changed title/dates. 00: Changed title/dates.
individual-02: Updated references. individual-02: Updated references.
individual-03: Modified ULA text to not suggest ULA-C as much individual-03: Modified ULA text to not suggest ULA-C as much
better anymore, but still mention it. better anymore, but still mention it.
individual-02: Added explanation why no IPv4 for ACP. individual-02: Added explanation why no IPv4 for ACP.
skipping to change at page 15, line 35 skipping to change at page 15, line 49
[I-D.behringer-anima-reference-model] [I-D.behringer-anima-reference-model]
Behringer, M., Carpenter, B., Eckert, T., Ciavaglia, L., Behringer, M., Carpenter, B., Eckert, T., Ciavaglia, L.,
Liu, B., Jeff, J., and J. Strassner, "A Reference Model Liu, B., Jeff, J., and J. Strassner, "A Reference Model
for Autonomic Networking", draft-behringer-anima- for Autonomic Networking", draft-behringer-anima-
reference-model-04 (work in progress), October 2015. reference-model-04 (work in progress), October 2015.
[I-D.ietf-anima-autonomic-control-plane] [I-D.ietf-anima-autonomic-control-plane]
Behringer, M., Eckert, T., and S. Bjarnason, "An Autonomic Behringer, M., Eckert, T., and S. Bjarnason, "An Autonomic
Control Plane", draft-ietf-anima-autonomic-control- Control Plane", draft-ietf-anima-autonomic-control-
plane-03 (work in progress), July 2016. plane-05 (work in progress), January 2017.
[I-D.ietf-anima-bootstrapping-keyinfra] [I-D.ietf-anima-bootstrapping-keyinfra]
Pritikin, M., Richardson, M., Behringer, M., and S. Pritikin, M., Richardson, M., Behringer, M., Bjarnason,
Bjarnason, "Bootstrapping Remote Secure Key S., and K. Watsen, "Bootstrapping Remote Secure Key
Infrastructures (BRSKI)", draft-ietf-anima-bootstrapping- Infrastructures (BRSKI)", draft-ietf-anima-bootstrapping-
keyinfra-03 (work in progress), June 2016. keyinfra-04 (work in progress), October 2016.
[I-D.irtf-nmrg-an-gap-analysis] [I-D.irtf-nmrg-an-gap-analysis]
Jiang, S., Carpenter, B., and M. Behringer, "General Gap Jiang, S., Carpenter, B., and M. Behringer, "General Gap
Analysis for Autonomic Networking", draft-irtf-nmrg-an- Analysis for Autonomic Networking", draft-irtf-nmrg-an-
gap-analysis-06 (work in progress), April 2015. gap-analysis-06 (work in progress), April 2015.
[I-D.irtf-nmrg-autonomic-network-definitions] [I-D.irtf-nmrg-autonomic-network-definitions]
Behringer, M., Pritikin, M., Bjarnason, S., Clemm, A., Behringer, M., Pritikin, M., Bjarnason, S., Clemm, A.,
Carpenter, B., Jiang, S., and L. Ciavaglia, "Autonomic Carpenter, B., Jiang, S., and L. Ciavaglia, "Autonomic
Networking - Definitions and Design Goals", draft-irtf- Networking - Definitions and Design Goals", draft-irtf-
nmrg-autonomic-network-definitions-07 (work in progress), nmrg-autonomic-network-definitions-07 (work in progress),
March 2015. March 2015.
[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005, Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005,
<http://www.rfc-editor.org/info/rfc4193>. <http://www.rfc-editor.org/info/rfc4193>.
Authors' Addresses Authors' Addresses
Toerless Eckert Toerless Eckert
Cisco Futurewei Technologies Inc.
2330 Central Expy
Santa Clara 95050
USA
Email: eckert@cisco.com Email: tte+ietf@cs.fau.de
Michael H. Behringer Michael H. Behringer
Cisco Cisco
Email: mbehring@cisco.com Email: mbehring@cisco.com
 End of changes. 15 change blocks. 
17 lines changed or deleted 23 lines changed or added

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