| Network Working Group | B. Liu |
| Internet-Draft | S. Jiang |
| Intended status: Standards Track | Huawei Technologies |
| Expires: September 23, 2016 | March 22, 2016 |
Information Distribution over GRASP
draft-liu-anima-grasp-distribution-01
This document discusses the requirement of information distribution capability in autonomic networks. Ideally, the autonomic network should support distributing some information which is generated/injected at an arbitrary autonomic node and be distributed among the whole autonomic domain. This docuemnt specifically proposes to achive this goal based on the GRASP (A Generic Autonomic Signaling Protocol), and specifies additional node behavior.
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 September 23, 2016.
Copyright (c) 2016 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.
In an autonomic network, sometimes the nodes need to share a set of common information. One typical case is the Intent Distribution which is briefly discussed in Section 4.5 of [I-D.behringer-anima-reference-model]. However, the distribution should be a general function that one autonomic node should support, rather than a specific mechanism dedicated for Intent. This document firstly analyzes several basic information distribution scenarios (Section 2), and then discusses the technical requirements (Section 3) that one autonomic node needs to fulfill.
This document proposes to achieve distribution function based on the GRASP (A Generic Autonomic Signaling Protocol) [I-D.ietf-anima-grasp] . GRASP already provides some capability to support part of the distribution function. Along with that, this document also proposes some additional functionality. Detailed design is described in Section 4.
Once the information is input to the autonomic network, the node that firstly handle the information MUST be able to distribute it to all the other nodes in the autonomic domain.
The distributed information might not relevant to every autonomic node, but it is flooded to all the devices.
When one node receive the information, it only replicates it to the neighbors that fit for a certain of conditions. This could reduce some unnecessary signaling amplification.
However, this scenario implies there needs to be corresponding mechanisms to represent the conditions and to judge which neighbors fit for the conditions. Please refer to Section 4.3.2 (selective flooding behavior).
The distribution only goes to the nodes that newly get online. This might mostly happen between neighbors.
The incremental distribution could also be a sub scenario of the whole domain distribution. When one node is doing the whole domain distribution, it is possible that some of its neighbors are sleeping/off-line, so when the neighbors get online again, the node should do incremental distribution of the previous whole domain distributed information.
The domain boundary devices are supposed to know themselves as boundary. When the distribution messages come to the devices, they do not distribute them outside the domain.
The distributed information SHOULD be injected at any autonomic node within the domain (or within a specific set of nodes [TBD]).
There should be a mechanism to prevent the distributed information to travel around the domain again and again, so that there would not be a large amount of redundant packets troubling the network.
When one node receive the information, it only floods it to the neighbors that fit for a certain of rules.
One node only distributes the information to another node. This is for the incremental distribution scenario.
As long as it supports arbitrary point of injecting distribution, there is possibility that two nodes advertise the same information but with conflict attribute(s). Hence, there should be a mechanism to handle the conflict.
This section specifies using certain GRASP messages for distribution, and also specifies the distribution behavior in an autonomic node.
It is natural to use the GRASP Flood Synchronization message for distribution, since the Flood Synchronization behavior specified in GRASP is identical to the the whole domain distribution scenario described in Section 2.1. And the Flood Synchronization naturally fits for "Arbitrary Injection Point" and "Avoiding Loops" requirements.
It is natural to use the GRASP Synchronization message for Point-to-Point distribution. The two behavior is identical.
When doing selective flooding, the distributed information needs to contain the cretiria for nodes to judge which interfaces should be sent the distributed information and which are not. Specifically, the indication information needs to include following attributes/meta-data:
Example:
This example means: only distributing the information to the neighbors who are IPRAN_RSG.
1) The distribution initial node Includes the Selecting Cretiria as attributes/meta-data in the distributed information.
2) The recieving node does the matching indicated by the Selecting Cretiria.
The distribution information needs to include timestamps or version information. When conflict happens, the node only accepts the latest information.
The distribution source authentication could be done at multiple layers:
TBD.
No IANA assignment is needed.
This document is inherited from [I-D.ietf-anima-grasp] and [I-D.behringer-anima-reference-model]. So thanks all the contributors of the two work items.
This document was produced using the xml2rfc tool [RFC2629].
| [I-D.ietf-anima-grasp] | Bormann, C., Carpenter, B. and B. Liu, "A Generic Autonomic Signaling Protocol (GRASP)", Internet-Draft draft-ietf-anima-grasp-04, March 2016. |
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. |
| [RFC2629] | Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, June 1999. |
| [I-D.behringer-anima-autonomic-control-plane] | Behringer, M., Bjarnason, S., BL, B. and T. Eckert, "An Autonomic Control Plane", Internet-Draft draft-behringer-anima-autonomic-control-plane-03, June 2015. |
| [I-D.behringer-anima-reference-model] | Behringer, M., Carpenter, B., Eckert, T., Ciavaglia, L., Liu, B., Jeff, J. and J. Strassner, "A Reference Model for Autonomic Networking", Internet-Draft draft-behringer-anima-reference-model-04, October 2015. |
| [I-D.du-anima-an-intent] | Du, Z., Jiang, S., Jeff, J. and L. Ciavaglia, "ANIMA Intent Policy and Format", Internet-Draft draft-du-anima-an-intent-03, March 2016. |
| [I-D.irtf-nmrg-autonomic-network-definitions] | Behringer, M., Pritikin, M., Bjarnason, S., Clemm, A., Carpenter, B., Jiang, S. and L. Ciavaglia, "Autonomic Networking - Definitions and Design Goals", Internet-Draft draft-irtf-nmrg-autonomic-network-definitions-07, March 2015. |
| [I-D.pritikin-anima-bootstrapping-keyinfra] | Pritikin, M., Richardson, M., Behringer, M. and S. Bjarnason, "Bootstrapping Key Infrastructures", Internet-Draft draft-pritikin-anima-bootstrapping-keyinfra-02, July 2015. |