Protocol for Forwarding Policy Configuration (FPC) in DMM
draft-ietf-dmm-fpc-cpdp-00
DMM Working Group M. Liebsch
Internet-Draft NEC
Intended status: Standards Track S. Matsushima
Expires: November 7, 2015 Softbank Telecom
S. Gundavelli
Cisco
D. Moses
Intel Corporation
May 6, 2015
Protocol for Forwarding Policy Configuration (FPC) in DMM
draft-ietf-dmm-fpc-cpdp-00.txt
Abstract
The specification as per this document supports the separation of the
Control-Plane for mobility- and session management from the actual
Data-Plane. The protocol semantics abstract from the actual details
for the configuration of Data-Plane nodes and apply between a Client
function, which is used by an application of the mobility Control-
Plane, and an Agent function, which is associated with the
configuration of Data-Plane nodes according to the policies issued by
the mobility Control-Plane. The scope of the policies comprises
forwarding rules and treatment of packets in terms of encapsulation,
IP address re-writing and QoS. Additional protocol semantics are
described to support the maintenance of the Data-Plane path.
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 November 7, 2015.
Liebsch, et al. Expires November 7, 2015 [Page 1]
Internet-Draft DMM FPC Protocol May 2015
Copyright Notice
Copyright (c) 2015 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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3
3. Model for Policy-based DMM Network Control . . . . . . . . . 3
3.1. Reference Architecture for DMM Forwarding Policy
Configuration . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Generalized Rules on the Client-Agent-Interface . . . . . 6
3.3. Role of the DMM FPC Client Function . . . . . . . . . . . 6
3.4. Role of the DMM FPC Agent Function . . . . . . . . . . . 7
4. Protocol Messages and Semantics . . . . . . . . . . . . . . . 7
4.1. Protocol Messages . . . . . . . . . . . . . . . . . . . . 7
4.2. Protocol Attributes . . . . . . . . . . . . . . . . . . . 8
4.3. Protocol Operation . . . . . . . . . . . . . . . . . . . 10
5. Conceptual Data Structures . . . . . . . . . . . . . . . . . 15
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8. Work Team Participants . . . . . . . . . . . . . . . . . . . 16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
9.1. Normative References . . . . . . . . . . . . . . . . . . 16
9.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. YANG Data Model for the FPC Protocol . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction
One objective of the Distributed Mobility Management (DMM) WG is the
separation of the mobility management Control- and Data-Plane to
enable flexible deployment, such as decentralized provisioning of
Data-Plane nodes (DPN). Data-Plane nodes can be configured to
function as anchor for a registered Mobile Node's (MN) traffic,
Show full document text