draft-ietf-dmm-fpc-cpdp-02.txt   draft-ietf-dmm-fpc-cpdp-03.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
Expires: September 22, 2016 SoftBank Expires: September 22, 2016 SoftBank
S. Gundavelli S. Gundavelli
Cisco Cisco
D. Moses D. Moses
Intel Corporation Intel Corporation
L. Bertz L. Bertz
Sprint Sprint
March 21, 2016 March 21, 2016
Protocol for Forwarding Policy Configuration (FPC) in DMM Protocol for Forwarding Policy Configuration (FPC) in DMM
draft-ietf-dmm-fpc-cpdp-02.txt draft-ietf-dmm-fpc-cpdp-03.txt
Abstract Abstract
This specification supports the separation of the Control-Plane for This specification supports the separation of the Control-Plane for
mobility- and session management from the Data-Plane. The protocol mobility- and session management from the Data-Plane. The protocol
semantics abstract the configuration of Data-Plane nodes and applies semantics abstract the configuration of Data-Plane nodes and applies
it between a Client function, which is used by an application of the it between a Client function, which is used by an application of the
mobility Control-Plane, and an Agent function, which is associated mobility Control-Plane, and an Agent function, which is associated
with the configuration of Data-Plane nodes, according to the Data- with the configuration of Data-Plane nodes, according to the Data-
Plane rules issued by the mobility Control-Plane. The scope of the Plane rules issued by the mobility Control-Plane. The scope of the
skipping to change at page 2, line 41 skipping to change at page 2, line 41
3.3.2. Role of the DMM FPC Agent Function . . . . . . . . . 8 3.3.2. Role of the DMM FPC Agent Function . . . . . . . . . 8
4. Protocol to support Model I . . . . . . . . . . . . . . . . . 9 4. Protocol to support Model I . . . . . . . . . . . . . . . . . 9
4.1. Data Structure . . . . . . . . . . . . . . . . . . . . . 9 4.1. Data Structure . . . . . . . . . . . . . . . . . . . . . 9
4.2. Protocol Attributes . . . . . . . . . . . . . . . . . . . 12 4.2. Protocol Attributes . . . . . . . . . . . . . . . . . . . 12
4.3. Protocol Messages and Semantics . . . . . . . . . . . . . 19 4.3. Protocol Messages and Semantics . . . . . . . . . . . . . 19
4.4. Protocol Operation . . . . . . . . . . . . . . . . . . . 20 4.4. Protocol Operation . . . . . . . . . . . . . . . . . . . 20
5. Protocol to support Model II . . . . . . . . . . . . . . . . 29 5. Protocol to support Model II . . . . . . . . . . . . . . . . 29
5.1. Protocol Attributes . . . . . . . . . . . . . . . . . . . 29 5.1. Protocol Attributes . . . . . . . . . . . . . . . . . . . 29
5.2. Protocol Messages and Semantics . . . . . . . . . . . . . 31 5.2. Protocol Messages and Semantics . . . . . . . . . . . . . 31
5.3. Protocol Operation . . . . . . . . . . . . . . . . . . . 33 5.3. Protocol Operation . . . . . . . . . . . . . . . . . . . 33
6. YANG Data Model for the FPC protocol . . . . . . . . . . . . 34 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34
6.1. FPC Base . . . . . . . . . . . . . . . . . . . . . . . . 34 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
6.1.1. FPC Base YANG Model . . . . . . . . . . . . . . . . . 34 8. Work Team Participants . . . . . . . . . . . . . . . . . . . 34
6.1.2. FPC Base tree . . . . . . . . . . . . . . . . . . . . 51 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.2. FPC PMIP . . . . . . . . . . . . . . . . . . . . . . . . 57 9.1. Normative References . . . . . . . . . . . . . . . . . . 34
6.2.1. FPC PMIP YANG Model . . . . . . . . . . . . . . . . . 57 9.2. Informative References . . . . . . . . . . . . . . . . . 35
6.2.2. FPC PMIP tree . . . . . . . . . . . . . . . . . . . . 60 Appendix A. YANG Data Model for the FPC protocol . . . . . . . . 35
7. Security Considerations . . . . . . . . . . . . . . . . . . . 65 A.1. FPC Base . . . . . . . . . . . . . . . . . . . . . . . . 36
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65 A.1.1. FPC Base YANG Model . . . . . . . . . . . . . . . . . 36
9. Work Team Participants . . . . . . . . . . . . . . . . . . . 66 A.1.2. FPC Base tree . . . . . . . . . . . . . . . . . . . . 52
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 66 A.2. FPC PMIP . . . . . . . . . . . . . . . . . . . . . . . . 58
10.1. Normative References . . . . . . . . . . . . . . . . . . 66 A.2.1. FPC PMIP YANG Model . . . . . . . . . . . . . . . . . 58
10.2. Informative References . . . . . . . . . . . . . . . . . 66 A.2.2. FPC PMIP tree . . . . . . . . . . . . . . . . . . . . 61
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 67
1. Introduction 1. Introduction
One objective of the Distributed Mobility Management (DMM) WG is the One objective of the Distributed Mobility Management (DMM) WG is the
separation of the mobility management Control- and Data-Plane to separation of the mobility management Control- and Data-Plane to
enable flexible deployment, such as decentralized provisioning of enable flexible deployment, such as decentralized provisioning of
Data-Plane nodes (DPN). Data-Plane nodes can be configured to Data-Plane nodes (DPN). Data-Plane nodes can be configured to
function as an anchor for a registered Mobile Node's (MN) traffic, function as an anchor for a registered Mobile Node's (MN) traffic,
others can be configured to function as a Mobile Access Gateway (MAG) others can be configured to function as a Mobile Access Gateway (MAG)
skipping to change at page 34, line 14 skipping to change at page 34, line 14
o DEALLOCATE_QOS_RESOURCES - Message can include Session_ID, o DEALLOCATE_QOS_RESOURCES - Message can include Session_ID,
QOS_SERVICE_ID, CONTEXT_ID. QOS_SERVICE_ID, CONTEXT_ID.
o ADD_NSH_HEADER - Message can include SERVICE_PATH_ID, o ADD_NSH_HEADER - Message can include SERVICE_PATH_ID,
SERVICE_INDEX, TFT SERVICE_INDEX, TFT
o DELETE_NSH_HEADER - Message can include SERVICE_PATH_ID, o DELETE_NSH_HEADER - Message can include SERVICE_PATH_ID,
SERVICE_INDEX, TFT SERVICE_INDEX, TFT
6. YANG Data Model for the FPC protocol 6. Security Considerations
Detailed protocol implementations for DMM Forwarding Policy
Configuration must ensure integrity of the information exchanged
between an FPC Client and an FPC Agent. Required Security
Associations may be derived from co-located functions, which utilize
the FPC Client and FPC Agent respectively.
7. IANA Considerations
This document provides a data model and protocol operation for DMM
Forwarding Policy Configuration. YANG models are currently included
in the Appendix and will be updated per the next revision of this
document to specify the data model as well as to enable an
implementation of the FPC protocol using RPC.
No actions from IANA are required. In case the semantics of this
specification will be mapped to a particular wire protocol, authors
of an associated separate document will approach IANA for the
associated action to create a registry or add registry entries.
8. Work Team Participants
Participants in the FPSM work team discussion include Satoru
Matsushima, Danny Moses, Sri Gundavelli, Marco Liebsch, Pierrick
Seite, Alper Yegin, Carlos Bernardos, Charles Perkins and Fred
Templin.
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC6088] Tsirtsis, G., Giarreta, G., Soliman, H., and N. Montavont,
"Traffic Selectors for Flow Bindings", RFC 6088,
DOI 10.17487/RFC6088, January 2011,
<http://www.rfc-editor.org/info/rfc6088>.
[RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J.
Korhonen, "Requirements for Distributed Mobility
Management", RFC 7333, DOI 10.17487/RFC7333, August 2014,
<http://www.rfc-editor.org/info/rfc7333>.
[RFC7429] Liu, D., Ed., Zuniga, JC., Ed., Seite, P., Chan, H., and
CJ. Bernardos, "Distributed Mobility Management: Current
Practices and Gap Analysis", RFC 7429,
DOI 10.17487/RFC7429, January 2015,
<http://www.rfc-editor.org/info/rfc7429>.
9.2. Informative References
[RFC3344] Perkins, C., Ed., "IP Mobility Support for IPv4",
RFC 3344, DOI 10.17487/RFC3344, August 2002,
<http://www.rfc-editor.org/info/rfc3344>.
[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
RFC 5213, DOI 10.17487/RFC5213, August 2008,
<http://www.rfc-editor.org/info/rfc5213>.
[RFC7222] Liebsch, M., Seite, P., Yokota, H., Korhonen, J., and S.
Gundavelli, "Quality-of-Service Option for Proxy Mobile
IPv6", RFC 7222, DOI 10.17487/RFC7222, May 2014,
<http://www.rfc-editor.org/info/rfc7222>.
Appendix A. YANG Data Model for the FPC protocol
These modules define Model I YANG definitions. Four modules are These modules define Model I YANG definitions. Four modules are
defined: defined:
o ietf-dmm-fpcp-base (fpcp-base) - Defines the base model for Model o ietf-dmm-fpcp-base (fpcp-base) - Defines the base model for Model
I FPC as defined in this document I FPC as defined in this document
o ietf-pmip-qos (pmip-qos) - Defines proxy mobile IPv6 QoS o ietf-pmip-qos (pmip-qos) - Defines proxy mobile IPv6 QoS
parameters per RFC 7222 parameters per RFC 7222
skipping to change at page 34, line 36 skipping to change at page 36, line 13
Selectors per RFC 6088 Selectors per RFC 6088
o ietf-dmm-fpcp-pmip - Augments fpcp-base to include PMIP Traffic o ietf-dmm-fpcp-pmip - Augments fpcp-base to include PMIP Traffic
Selectors as a Traffic Descriptor subtype and pmip-qos QoS Selectors as a Traffic Descriptor subtype and pmip-qos QoS
parameters, where applicable, as properties. parameters, where applicable, as properties.
Note (2016-03-21): The YANG Data Model does not yet adopt all Note (2016-03-21): The YANG Data Model does not yet adopt all
extensions per this version of the draft and will be updated shortly extensions per this version of the draft and will be updated shortly
after the IETF95 meeting. after the IETF95 meeting.
6.1. FPC Base A.1. FPC Base
6.1.1. FPC Base YANG Model A.1.1. FPC Base YANG Model
module ietf-dmm-fpcp-base { module ietf-dmm-fpcp-base {
namespace "urn:ietf:params:xml:ns:yang:ietf-dmm-fpcp-base"; namespace "urn:ietf:params:xml:ns:yang:ietf-dmm-fpcp-base";
prefix fpcp-base; prefix fpcp-base;
import ietf-inet-types { prefix inet; } import ietf-inet-types { prefix inet; }
organization "IETF DMM Working Group"; organization "IETF DMM Working Group";
contact "Satoru Matsushima <satoru.matsushima@g.softbank.co.jp>"; contact "Satoru Matsushima <satoru.matsushima@g.softbank.co.jp>";
skipping to change at page 51, line 20 skipping to change at page 52, line 41
notification notify { notification notify {
description description
"TBD for which status and event are reported to client."; "TBD for which status and event are reported to client.";
} }
} }
Figure 19: FPC YANG base Figure 19: FPC YANG base
6.1.2. FPC Base tree A.1.2. FPC Base tree
module: ietf-dmm-fpcp-base module: ietf-dmm-fpcp-base
+--rw fpcp-carriers +--rw fpcp-carriers
| +--rw carrier* [carrier-id] | +--rw carrier* [carrier-id]
| +--rw name? fpcp-name-type | +--rw name? fpcp-name-type
| +--rw carrier-id fpcp-carrier-id | +--rw carrier-id fpcp-carrier-id
| +--rw agent-id? fpcp-agent-id | +--rw agent-id? fpcp-agent-id
| +--rw client* [client-id] | +--rw client* [client-id]
| | +--rw name? fpcp-name-type | | +--rw name? fpcp-name-type
| | +--rw client-id fpcp-client-id | | +--rw client-id fpcp-client-id
skipping to change at page 57, line 5 skipping to change at page 58, line 22
| +---w network-id? fpcp-network-id | +---w network-id? fpcp-network-id
| +---w target-rule* | +---w target-rule*
| +---w target-rule-id fpcp-rule-id | +---w target-rule-id fpcp-rule-id
+---x event_register +---x event_register
+---x probe +---x probe
notifications: notifications:
+---n notify +---n notify
Figure 20: FPC base tree Figure 20: FPC base tree
6.2. FPC PMIP A.2. FPC PMIP
6.2.1. FPC PMIP YANG Model A.2.1. FPC PMIP YANG Model
module ietf-dmm-fpcp-pmip { module ietf-dmm-fpcp-pmip {
namespace "urn:ietf:params:xml:ns:yang:ietf-dmm-fpcp-pmip"; namespace "urn:ietf:params:xml:ns:yang:ietf-dmm-fpcp-pmip";
prefix fpcp-pmip; prefix fpcp-pmip;
import ietf-inet-types { prefix inet; } import ietf-inet-types { prefix inet; }
import ietf-dmm-fpcp-base { prefix fpcp-base; } import ietf-dmm-fpcp-base { prefix fpcp-base; }
import ietf-pmip-qos { prefix qos-pmip; } import ietf-pmip-qos { prefix qos-pmip; }
import ietf-traffic-selectors { prefix traffic-selectors; } import ietf-traffic-selectors { prefix traffic-selectors; }
skipping to change at page 60, line 28 skipping to change at page 61, line 46
case traffic-selector-mip6 { case traffic-selector-mip6 {
when "/fpcp-base:rule_modify/fpcp-base:input/fpcp-base:modifying-rule/fpcp-base:forwarding-rule/fpcp-base:traffic-descriptor-type = 'traffic-selector-mip6'"; when "/fpcp-base:rule_modify/fpcp-base:input/fpcp-base:modifying-rule/fpcp-base:forwarding-rule/fpcp-base:traffic-descriptor-type = 'traffic-selector-mip6'";
uses traffic-selectors:traffic-selector; uses traffic-selectors:traffic-selector;
} }
} }
} }
Figure 21: caption1 Figure 21: caption1
6.2.2. FPC PMIP tree A.2.2. FPC PMIP tree
module: ietf-dmm-fpcp-pmip module: ietf-dmm-fpcp-pmip
augment /fpcp-base:fpcp-carriers/fpcp-base:carrier/fpcp-base:qos-profile/fpcp-base:index-type: augment /fpcp-base:fpcp-carriers/fpcp-base:carrier/fpcp-base:qos-profile/fpcp-base:index-type:
+--:(pmip) +--:(pmip)
+--rw dscp? inet:dscp +--rw dscp? inet:dscp
+--rw (attribute)? +--rw (attribute)?
+--:(per-mn-agg-max-dl) +--:(per-mn-agg-max-dl)
| +--rw per-mn-agg-max-dl? qos-pmip:Per-MN-Agg-Max-DL-Bit-Rate-Value | +--rw per-mn-agg-max-dl? qos-pmip:Per-MN-Agg-Max-DL-Bit-Rate-Value
+--:(per-mn-agg-max-ul) +--:(per-mn-agg-max-ul)
| +--rw per-mn-agg-max-ul? qos-pmip:Per-MN-Agg-Max-UL-Bit-Rate-Value | +--rw per-mn-agg-max-ul? qos-pmip:Per-MN-Agg-Max-UL-Bit-Rate-Value
skipping to change at page 65, line 28 skipping to change at page 67, line 5
+---- end-destination-address-v6? inet:ipv6-address +---- end-destination-address-v6? inet:ipv6-address
+---- start-flow-label? inet:ipv6-flow-label +---- start-flow-label? inet:ipv6-flow-label
+---- end-flow-label? inet:ipv6-flow-label +---- end-flow-label? inet:ipv6-flow-label
+---- start-traffic-class? inet:dscp +---- start-traffic-class? inet:dscp
+---- end-traffic-class? inet:dscp +---- end-traffic-class? inet:dscp
+---- start-next-header? uint8 +---- start-next-header? uint8
+---- end-next-header? uint8 +---- end-next-header? uint8
Figure 22: FPC PMIP tree Figure 22: FPC PMIP tree
7. Security Considerations
Detailed protocol implementations for DMM Forwarding Policy
Configuration must ensure integrity of the information exchanged
between an FPC Client and an FPC Agent. Required Security
Associations may be derived from co-located functions, which utilize
the FPC Client and FPC Agent respectively.
8. IANA Considerations
This document provides a data model and protocol operation for DMM
Forwarding Policy Configuration. Yang models are included to specify
the data model as well as to enable an implementation of this
protocol using RPC.
No actions from IANA are required. In case the semantics of this
specification will be mapped to a particular wire protocol, authors
of an associated separate document will approach IANA for the
associated action to create a registry or add registry entries.
9. Work Team Participants
Participants in the FPSM work team discussion include Satoru
Matsushima, Danny Moses, Sri Gundavelli, Marco Liebsch, Pierrick
Seite, Alper Yegin, Carlos Bernardos, Charles Perkins and Fred
Templin.
10. References
10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC6088] Tsirtsis, G., Giarreta, G., Soliman, H., and N. Montavont,
"Traffic Selectors for Flow Bindings", RFC 6088,
DOI 10.17487/RFC6088, January 2011,
<http://www.rfc-editor.org/info/rfc6088>.
[RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J.
Korhonen, "Requirements for Distributed Mobility
Management", RFC 7333, DOI 10.17487/RFC7333, August 2014,
<http://www.rfc-editor.org/info/rfc7333>.
[RFC7429] Liu, D., Ed., Zuniga, JC., Ed., Seite, P., Chan, H., and
CJ. Bernardos, "Distributed Mobility Management: Current
Practices and Gap Analysis", RFC 7429,
DOI 10.17487/RFC7429, January 2015,
<http://www.rfc-editor.org/info/rfc7429>.
10.2. Informative References
[RFC3344] Perkins, C., Ed., "IP Mobility Support for IPv4",
RFC 3344, DOI 10.17487/RFC3344, August 2002,
<http://www.rfc-editor.org/info/rfc3344>.
[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
RFC 5213, DOI 10.17487/RFC5213, August 2008,
<http://www.rfc-editor.org/info/rfc5213>.
[RFC7222] Liebsch, M., Seite, P., Yokota, H., Korhonen, J., and S.
Gundavelli, "Quality-of-Service Option for Proxy Mobile
IPv6", RFC 7222, DOI 10.17487/RFC7222, May 2014,
<http://www.rfc-editor.org/info/rfc7222>.
Authors' Addresses Authors' Addresses
Marco Liebsch Marco Liebsch
NEC Laboratories Europe NEC Laboratories Europe
NEC Europe Ltd. NEC Europe Ltd.
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
D-69115 Heidelberg D-69115 Heidelberg
Germany Germany
Phone: +49 6221 4342146 Phone: +49 6221 4342146
 End of changes. 10 change blocks. 
89 lines changed or deleted 90 lines changed or added

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