draft-ietf-dmm-fpc-cpdp-13.txt   draft-ietf-dmm-fpc-cpdp-14.txt 
DMM Working Group S. Matsushima DMM Working Group S. Matsushima
Internet-Draft SoftBank Internet-Draft SoftBank
Intended status: Standards Track L. Bertz Intended status: Standards Track L. Bertz
Expires: September 10, 2020 Sprint Expires: 27 March 2021 Sprint
M. Liebsch M. Liebsch
NEC NEC
S. Gundavelli S. Gundavelli
Cisco Cisco
D. Moses D. Moses
Intel Corporation Intel Corporation
C. Perkins C.E. Perkins
Futurewei Futurewei
March 9, 2020 23 September 2020
Protocol for Forwarding Policy Configuration (FPC) in DMM Protocol for Forwarding Policy Configuration (FPC) in DMM
draft-ietf-dmm-fpc-cpdp-13 draft-ietf-dmm-fpc-cpdp-14
Abstract Abstract
This document describes a way, called Forwarding Policy Configuration This document describes a way, called Forwarding Policy Configuration
(FPC) to manage the separation of data-plane and control-plane. FPC (FPC) to manage the separation of data-plane and control-plane. FPC
defines a flexible mobility management system using FPC agent and FPC defines a flexible mobility management system using FPC agent and FPC
client functions. A FPC agent provides an abstract interface to the client functions. A FPC agent provides an abstract interface to the
data-plane. The FPC client configures data-plane nodes by using the data-plane. The FPC client configures data-plane nodes by using the
functions and abstractions provided by the FPC agent for the data- functions and abstractions provided by the FPC agent for the data-
plane nodes. The data-plane abstractions presented in this document plane nodes. The data-plane abstractions presented in this document
skipping to change at page 1, line 40 skipping to change at page 1, line 40
management systems and data-plane functions. management systems and data-plane functions.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://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 September 10, 2020. This Internet-Draft will expire on 27 March 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 (https://trustee.ietf.org/
(http://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Simplified BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. FPC Design Objectives and Deployment . . . . . . . . . . . . 6 3. FPC Design Objectives and Deployment . . . . . . . . . . . . 6
4. FPC Mobility Information Model . . . . . . . . . . . . . . . 9 4. FPC Mobility Information Model . . . . . . . . . . . . . . . 9
4.1. Model Notation and Conventions . . . . . . . . . . . . . 9 4.1. Model Notation and Conventions . . . . . . . . . . . . . 10
4.2. Templates and Attributes . . . . . . . . . . . . . . . . 12 4.2. Templates and Attributes . . . . . . . . . . . . . . . . 12
4.3. Attribute-Expressions . . . . . . . . . . . . . . . . . . 13 4.3. Attribute-Expressions . . . . . . . . . . . . . . . . . . 13
4.4. Attribute Value Types . . . . . . . . . . . . . . . . . . 14 4.4. Attribute Value Types . . . . . . . . . . . . . . . . . . 14
4.5. Namespace and Format . . . . . . . . . . . . . . . . . . 14 4.5. Namespace and Format . . . . . . . . . . . . . . . . . . 14
4.6. Configuring Attribute Values . . . . . . . . . . . . . . 15 4.6. Configuring Attribute Values . . . . . . . . . . . . . . 15
4.7. Entity Configuration Blocks . . . . . . . . . . . . . . . 16 4.7. Entity Configuration Blocks . . . . . . . . . . . . . . . 16
4.8. Information Model Checkpoint . . . . . . . . . . . . . . 17 4.8. Information Model Checkpoint . . . . . . . . . . . . . . 17
4.9. Information Model Components . . . . . . . . . . . . . . 18 4.9. Information Model Components . . . . . . . . . . . . . . 18
4.9.1. Topology Information Model . . . . . . . . . . . . . 18 4.9.1. Topology Information Model . . . . . . . . . . . . . 18
4.9.2. Service-Group . . . . . . . . . . . . . . . . . . . . 18 4.9.2. Service-Group . . . . . . . . . . . . . . . . . . . . 18
4.9.3. Domain Information Model . . . . . . . . . . . . . . 20 4.9.3. Domain Information Model . . . . . . . . . . . . . . 20
4.9.4. DPN Information Model . . . . . . . . . . . . . . . . 20 4.9.4. DPN Information Model . . . . . . . . . . . . . . . . 20
4.9.5. Policy Information Model . . . . . . . . . . . . . . 21 4.9.5. Policy Information Model . . . . . . . . . . . . . . 22
4.9.6. Mobility-Context Information Model . . . . . . . . . 24 4.9.6. Mobility-Context Information Model . . . . . . . . . 24
4.9.7. Monitor Information Model . . . . . . . . . . . . . . 26 4.9.7. Monitor Information Model . . . . . . . . . . . . . . 26
5. Security Considerations . . . . . . . . . . . . . . . . . . . 27 5. Security Considerations . . . . . . . . . . . . . . . . . . . 28
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
7. Work Team Participants . . . . . . . . . . . . . . . . . . . 28 7. Work Team Participants . . . . . . . . . . . . . . . . . . . 28
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
8.1. Normative References . . . . . . . . . . . . . . . . . . 28 8.1. Normative References . . . . . . . . . . . . . . . . . . 28
8.2. Informative References . . . . . . . . . . . . . . . . . 28 8.2. Informative References . . . . . . . . . . . . . . . . . 28
Appendix A. Implementation Status . . . . . . . . . . . . . . . 29 Appendix A. Implementation Status . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
This document describes Forwarding Policy Configuration (FPC), a This document describes Forwarding Policy Configuration (FPC), a
system for managing the separation of control-plane and data-plane. system for managing the separation of control-plane and data-plane.
FPC enables flexible mobility management using FPC client and FPC FPC enables flexible mobility management using FPC client and FPC
agent functions. A FPC agent exports an abstract interface agent functions. A FPC agent exports an abstract interface
representing the data-plane. To configure data-plane nodes and representing the data-plane. To configure data-plane nodes and
functions, the FPC client uses the interface to the data-plane functions, the FPC client uses the interface to the data-plane
offered by the FPC agent. offered by the FPC agent.
skipping to change at page 8, line 43 skipping to change at page 9, line 4
| | | |
DPN | DPN | DPN | DPN |
+----------|---------+ +----------|---------+ +----------|---------+ +----------|---------+
|+---------v--------+| |+---------v--------+| |+---------v--------+| |+---------v--------+|
|| Configuration || ||[Data-plane model]|| || Configuration || ||[Data-plane model]||
|| Protocol module || || FPC Agent || || Protocol module || || FPC Agent ||
|+------------------+| |+------------------+| |+------------------+| |+------------------+|
| | | | | | | |
| DPN Configuration | | DPN Configuration | | DPN Configuration | | DPN Configuration |
+--------------------+ +--------------------+ +--------------------+ +--------------------+
Figure 1: Reference Forwarding Policy Configuration (FPC) Figure 1: Reference Forwarding Policy Configuration (FPC)
Architecture Architecture
The FPC architecture supports multi-tenancy; a FPC enabled data-plane The FPC architecture supports multi-tenancy; a FPC enabled data-plane
supports tenants of multiple mobile operator networks and/or supports tenants of multiple mobile operator networks and/or
applications. It means that the FPC Client of each tenant connects applications. It means that the FPC Client of each tenant connects
to the FPC Agent and it MUST partition namespace and data for their to the FPC Agent and it MUST partition namespace and data for their
data-planes. DPNs on the data-plane may fulfill multiple data-plane data-planes. DPNs on the data-plane may fulfill multiple data-plane
roles which are defined per session, domain and tenant. roles which are defined per session, domain and tenant.
Multi-tenancy permits the paritioning of data-plane entities as well Multi-tenancy permits the paritioning of data-plane entities as well
as a common namespace requirement upon FPC Agents and Clients when as a common namespace requirement upon FPC Agents and Clients when
skipping to change at page 11, line 18 skipping to change at page 11, line 30
-- Entity2 is a list -- Entity2 is a list
-- Entity3 is a set and is optional -- Entity3 is a set and is optional
+ +
| |
+-[entity1] <G-Key> (M), <Name> (O) +-[entity1] <G-Key> (M), <Name> (O)
+-[entity2] <List> +-[entity2] <List>
+-[entity3] <Set> (O) +-[entity3] <Set> (O)
| |
+ +
Figure 4 Figure 4
When expanding entity1 into a modeling language such as YANG it would When expanding entity1 into a modeling language such as YANG it would
result in two values: entity1-Key and entity1-Name. result in two values: entity1-Key and entity1-Name.
To encourage re-use, FPC defines indexed sets of various entity To encourage re-use, FPC defines indexed sets of various entity
Templates. Other model elements that need access to an indexed model Templates. Other model elements that need access to an indexed model
entity contain an attribute which is always denoted as "entity-Key". entity contain an attribute which is always denoted as "entity-Key".
When a Key attribute is encountered, the referencing model element When a Key attribute is encountered, the referencing model element
may supply attribute values for use when the referenced entity model may supply attribute values for use when the referenced entity model
is instantiated. For example: Figure 5 shows 2 entities: is instantiated. For example: Figure 5 shows 2 entities:
skipping to change at page 12, line 19 skipping to change at page 12, line 19
| +-[entityB-Key] | +-[entityB-Key]
| +-[entityB-Values] | +-[entityB-Values]
. .
. .
| |
+-[entityB] <L-Key> (M) <Set> +-[entityB] <L-Key> (M) <Set>
| +-[entityB-Type] | +-[entityB-Type]
. .
. .
Figure 5: Indexed sets of entities Figure 5: Indexed sets of entities
Indexed sets are specified for each of the following kinds of Indexed sets are specified for each of the following kinds of
entities: entities:
Domain (See Section 4.9.3) Domain (See Section 4.9.3)
DPN (See Section 4.9.4) DPN (See Section 4.9.4)
Policy (See Section 4.9.5) Policy (See Section 4.9.5)
Rule (See Section 4.9.5) Rule (See Section 4.9.5)
Descriptor (See Figure 12) Descriptor (See Figure 12)
Action (See Figure 12) Action (See Figure 12)
skipping to change at page 17, line 13 skipping to change at page 17, line 16
More generally, an Entity-Configuration can be defined for any More generally, an Entity-Configuration can be defined for any
configurable Indexed Set to be the combination of the Entity-Key configurable Indexed Set to be the combination of the Entity-Key
along with a set of Attribute-Expressions that supply configuration along with a set of Attribute-Expressions that supply configuration
information for the entity's Attributes. Figure 7 shows a schematic information for the entity's Attributes. Figure 7 shows a schematic
representation for such Entity Configuration Blocks. representation for such Entity Configuration Blocks.
[Entity Configuration Block] [Entity Configuration Block]
| +-[Entity-Key] (M) | +-[Entity-Key] (M)
| +-[Attribute-Expression] <Set> (M) | +-[Attribute-Expression] <Set> (M)
Figure 7: Entity Configuration Block Figure 7: Entity Configuration Block
This document makes use of the following kinds of Entity This document makes use of the following kinds of Entity
Configuration Blocks: Configuration Blocks:
Descriptor-Configuration Descriptor-Configuration
Action-Configuration Action-Configuration
Rule-Configuration Rule-Configuration
skipping to change at page 18, line 29 skipping to change at page 18, line 35
The Topology structure is illustrated in Figure 8 (for definitions The Topology structure is illustrated in Figure 8 (for definitions
see Section 2): see Section 2):
| |
+-[Topology Information Model] +-[Topology Information Model]
| +-[Extensible: FALSE] | +-[Extensible: FALSE]
| +-[Service-Group] | +-[Service-Group]
| +-[DPN] <Set> | +-[DPN] <Set>
| +-[Domain] <Set> | +-[Domain] <Set>
Figure 8: Topology Structure Figure 8: Topology Structure
4.9.2. Service-Group 4.9.2. Service-Group
Service-Group-Set is collection of DPN interfaces serving some data- Service-Group-Set is collection of DPN interfaces serving some data-
plane purpose including but not limited to DPN Interface selection to plane purpose including but not limited to DPN Interface selection to
fulfill a Mobility-Context. Each Group contains a list of DPNs fulfill a Mobility-Context. Each Group contains a list of DPNs
(referenced by DPN-Key) and selected interfaces (referenced by (referenced by DPN-Key) and selected interfaces (referenced by
Interface-Key). The Interfaces are listed explicitly (rather than Interface-Key). The Interfaces are listed explicitly (rather than
referred implicitly by its specific DPN) so that every Interface of a referred implicitly by its specific DPN) so that every Interface of a
DPN is not required to be part of a Group. The information provided DPN is not required to be part of a Group. The information provided
skipping to change at page 19, line 48 skipping to change at page 19, line 48
Service-Group-Configuration-Set: An optional set of configurations Service-Group-Configuration-Set: An optional set of configurations
that further determine the suitability of an interface for the that further determine the suitability of an interface for the
specific request. For example: SequenceNumber=ON/OFF. specific request. For example: SequenceNumber=ON/OFF.
DPN-Key-Set: A key used to identify the DPN. DPN-Key-Set: A key used to identify the DPN.
Referenced-Interface-Set: The DPN Interfaces and peer Service-Groups Referenced-Interface-Set: The DPN Interfaces and peer Service-Groups
associated with them. Each entry contains associated with them. Each entry contains
Interface-Key: A key that is used together with the DPN-Key, to Interface-Key: A key that is used together with the DPN-Key, to
create a key that is refers to a specific DPN interface create a key that is refers to a specific DPN interface
definition. definition.
Peer-Service-Group-Key: Enables location of the peer Service- Peer-Service-Group-Key: Enables location of the peer Service-
Group for this Interface. Group for this Interface.
4.9.3. Domain Information Model 4.9.3. Domain Information Model
A Domain-Set represents a group of heterogeneous Topology resources A Domain-Set represents a group of heterogeneous Topology resources
typically sharing a common administrative authority. Other models, typically sharing a common administrative authority. Other models,
outside of the scope of this specification, provide the details for outside of the scope of this specification, provide the details for
the Domain. the Domain.
| |
skipping to change at page 20, line 46 skipping to change at page 20, line 46
| +-[Extensible: FALSE] | +-[Extensible: FALSE]
| +-[Interface] <L-Key> <Set> | +-[Interface] <L-Key> <Set>
| | +-[Role] <U-Key> | | +-[Role] <U-Key>
| | +-[Protocol] <Set> | | +-[Protocol] <Set>
| | +-[Interface-Configuration] <Set> (O) | | +-[Interface-Configuration] <Set> (O)
| +-[Domain-Key] | +-[Domain-Key]
| +-[Service-Group-Key] <Set> (O) | +-[Service-Group-Key] <Set> (O)
| +-[DPN-Policy-Configuration] <List> (M) | +-[DPN-Policy-Configuration] <List> (M)
| +-[DPN-Resource-Mapping-Reference] (O) | +-[DPN-Resource-Mapping-Reference] (O)
Figure 11: DPN Information Model Figure 11: DPN Information Model
Each DPN entry contains the following information: Each DPN entry contains the following information:
DPN-Key: A unique Identifier of the DPN. DPN-Key: A unique Identifier of the DPN.
DPN-Name: A human-readable display string. DPN-Name: A human-readable display string.
Domain-Key: A Key providing access to the Domain information about Domain-Key: A Key providing access to the Domain information about
the Domain in which the DPN resides. the Domain in which the DPN resides.
Interface-Set: The Interface-Set references all interfaces (through Interface-Set: The Interface-Set references all interfaces (through
which data packets are received and transmitted) available on the which data packets are received and transmitted) available on the
DPN. Each Interface makes use of attribute values that are DPN. Each Interface makes use of attribute values that are
specific to that interface, for example, the MTU size. These do specific to that interface, for example, the MTU size. These do
not affect the DPN selection of active or enabled interfaces. not affect the DPN selection of active or enabled interfaces.
Interfaces contain the following information: Interfaces contain the following information:
Role: The role (MAG, LMA, PGW, AMF, etc.) of the DPN. Role: The role (MAG, LMA, PGW, AMF, etc.) of the DPN.
Protocol (Set): The set of protocols supported by this interface Protocol (Set): The set of protocols supported by this interface
(e.g., PMIP, S5-GTP, S5-PMIP etc.). The protocol MAY implement (e.g., PMIP, S5-GTP, S5-PMIP etc.). The protocol MAY implement
specific message sets, e.g. s5-pmip, s8-pmip. When a protocol specific message sets, e.g. s5-pmip, s8-pmip. When a protocol
implements such message sub-subsets the Protocol value MUST implements such message sub-subsets the Protocol value MUST
include this information. include this information.
Interface-Configuration-Set: Configurable settings that further Interface-Configuration-Set: Configurable settings that further
determine the suitability of an interface for the specific determine the suitability of an interface for the specific
request. For example: SequenceNumber=ON/OFF. request. For example: SequenceNumber=ON/OFF.
skipping to change at page 22, line 50 skipping to change at page 23, line 10
Figure 12: Policy Information Model Figure 12: Policy Information Model
The Policy structure defines Policy-Set, Rule-Set, Descriptor-Set, The Policy structure defines Policy-Set, Rule-Set, Descriptor-Set,
and Action-Set, as follows: and Action-Set, as follows:
Policy-Template: <Set> A set of Policy structures, indexed by Policy-Template: <Set> A set of Policy structures, indexed by
Policy-Key, each of which is determined by a list of Rules Policy-Key, each of which is determined by a list of Rules
referenced by their Rule-Key. Each Policy structure contains the referenced by their Rule-Key. Each Policy structure contains the
following: following:
Policy-Key: Identifies and enables reference to this Policy Policy-Key: Identifies and enables reference to this Policy
definition. definition.
Rule-Template-Key: Enables reference to a Rule template Rule-Template-Key: Enables reference to a Rule template
definition. definition.
Rule-Precedence: For each Rule identified by a Rule-Template-Key Rule-Precedence: For each Rule identified by a Rule-Template-Key
in the Policy, specifies the order in which that Rule must be in the Policy, specifies the order in which that Rule must be
applied. The lower the numerical value of Precedence, the applied. The lower the numerical value of Precedence, the
higher the rule precedence. Rules with equal precedence MAY be higher the rule precedence. Rules with equal precedence MAY be
executed in parallel if supported by the DPN. If this value is executed in parallel if supported by the DPN. If this value is
absent, the rules SHOULD be applied in the order in which they absent, the rules SHOULD be applied in the order in which they
appear in the Policy. appear in the Policy.
Rule-Template-Set: A set of Rule Template definitions indexed by Rule-Template-Set: A set of Rule Template definitions indexed by
Rule-Key. Each Rule is defined by a list of Descriptors (located Rule-Key. Each Rule is defined by a list of Descriptors (located
by Descriptor-Key) and a list of Actions (located by Action-Key) by Descriptor-Key) and a list of Actions (located by Action-Key)
as follows: as follows:
Rule-Template-Key: Identifies and enables reference to this Rule Rule-Template-Key: Identifies and enables reference to this Rule
definition. definition.
Descriptor-Match-Type Indicates whether the evaluation of the Descriptor-Match-Type Indicates whether the evaluation of the
Rule proceeds by using conditional-AND, or conditional-OR, on Rule proceeds by using conditional-AND, or conditional-OR, on
the list of Descriptors. the list of Descriptors.
Descriptor-Configuration: References a Descriptor template Descriptor-Configuration: References a Descriptor template
definition, along with an expression which names the Attributes definition, along with an expression which names the Attributes
for this instantiation from the Descriptor-Template and also for this instantiation from the Descriptor-Template and also
specifies whether each Attribute of the Descriptor has a specifies whether each Attribute of the Descriptor has a
default value or a statically configured value, according to default value or a statically configured value, according to
the syntax specified in Section 4.2. the syntax specified in Section 4.2.
Direction: Indicates if a rule applies to uplink traffic, to Direction: Indicates if a rule applies to uplink traffic, to
downlink traffic, or to both uplink and downlink traffic. downlink traffic, or to both uplink and downlink traffic.
Applying a rule to both uplink and downlink traffic, in case of Applying a rule to both uplink and downlink traffic, in case of
symmetric rules, eliminates the requirement for a separate symmetric rules, eliminates the requirement for a separate
entry for each direction. When not present, the direction is entry for each direction. When not present, the direction is
implied by the Descriptor's values. implied by the Descriptor's values.
Action-Configuration: References an Action Template definition, Action-Configuration: References an Action Template definition,
along with an expression which names the Attributes for this along with an expression which names the Attributes for this
instantiation from the Action-Template and also specifies instantiation from the Action-Template and also specifies
whether each Attribute of the Action has a default value or a whether each Attribute of the Action has a default value or a
statically configured value, according to the syntax specified statically configured value, according to the syntax specified
in Section 4.2. in Section 4.2.
Action-Order: Defines the order in which actions are executed Action-Order: Defines the order in which actions are executed
when the associated traffic descriptor selects the packet. when the associated traffic descriptor selects the packet.
Descriptor-Template-Set: A set of traffic Descriptor Templates, Descriptor-Template-Set: A set of traffic Descriptor Templates, each
each of which can be evaluated on the incoming or outgoing packet, of which can be evaluated on the incoming or outgoing packet,
returning a TRUE or FALSE value, defined as follows: returning a TRUE or FALSE value, defined as follows:
Descriptor-Template-Key: Identifies and enables reference to Descriptor-Template-Key: Identifies and enables reference to this
this descriptor template definition. descriptor template definition.
Attribute-Expression: An expression which defines an Attribute in Attribute-Expression: An expression which defines an Attribute in
the Descriptor-Template and also specifies whether the Template the Descriptor-Template and also specifies whether the Template
also defines a default value or a statically configured value also defines a default value or a statically configured value
for the Attribute of the Descriptor has, according to the for the Attribute of the Descriptor has, according to the
syntax specified in Section 4.2. syntax specified in Section 4.2.
Descriptor-Type: Identifies the type of descriptor, e.g. an IPv6 Descriptor-Type: Identifies the type of descriptor, e.g. an IPv6
traffic selector per [RFC6088]. traffic selector per [RFC6088].
Action-Template-Set: A set of Action Templates defined as follows: Action-Template-Set: A set of Action Templates defined as follows:
Action-Template-Key: Identifies and enables reference to this Action-Template-Key: Identifies and enables reference to this
action template definition. action template definition.
Attribute-Expression: An expression which defines an Attribute in Attribute-Expression: An expression which defines an Attribute in
the Action-Template and also specifies whether the Template the Action-Template and also specifies whether the Template
also defines a default value or a statically configured value also defines a default value or a statically configured value
for the Attribute of the Action has, according to the syntax for the Attribute of the Action has, according to the syntax
specified in Section 4.2. specified in Section 4.2.
Action-Type: Identifies the type of an action for unambiguous Action-Type: Identifies the type of an action for unambiguous
interpretation of an Action-Value entry. interpretation of an Action-Value entry.
4.9.6. Mobility-Context Information Model 4.9.6. Mobility-Context Information Model
The Mobility-Context structure holds entries associated with a mobile The Mobility-Context structure holds entries associated with a mobile
node and its mobility sessions (flows). It is created on a DPN node and its mobility sessions (flows). It is created on a DPN
during the mobile node's registration to manage the mobile node's during the mobile node's registration to manage the mobile node's
flows. Flow information is added or deleted from the Mobility- flows. Flow information is added or deleted from the Mobility-
Context as needed to support new flows or to deallocate resources for Context as needed to support new flows or to deallocate resources for
flows that are deactivated. Descriptors are used to characterize the flows that are deactivated. Descriptors are used to characterize the
skipping to change at page 25, line 30 skipping to change at page 25, line 35
| | | +-[Service-Group-Key] (O) | | | +-[Service-Group-Key] (O)
| | | +-[Interface-Key] <Set> | | | +-[Interface-Key] <Set>
| | | +-[ServiceDataFlow-Policy- | | | +-[ServiceDataFlow-Policy-
Configuration] <Set> (O) Configuration] <Set> (O)
| | | | +-[Direction] | | | | +-[Direction]
Figure 13: Mobility-Context Information Model Figure 13: Mobility-Context Information Model
The Mobility-Context Substructure holds the following entries: The Mobility-Context Substructure holds the following entries:
Mobility-Context-Key: Identifies a Mobility-Context Mobility-Context-Key: Identifies a Mobility-Context
Delegating-IP-Prefix-Set: Delegated IP Prefixes assigned to the Delegating-IP-Prefix-Set: Delegated IP Prefixes assigned to the
Mobility-Context Mobility-Context
Parent-Context: If present, a Mobility Context from which the Parent-Context: If present, a Mobility Context from which the
Attributes and Attribute Values of this Mobility Context are Attributes and Attribute Values of this Mobility Context are
inherited. inherited.
Child-Context-Set: A set of Mobility Contexts which inherit the Child-Context-Set: A set of Mobility Contexts which inherit the
Attributes and Attribute Values of this Mobility Context. Attributes and Attribute Values of this Mobility Context.
Service-Group-Key: Service-Group(s) used during DPN assignment and Service-Group-Key: Service-Group(s) used during DPN assignment and
re-assignment. re-assignment.
Mobile-Node: Attributes specific to the Mobile Node. It contains Mobile-Node: Attributes specific to the Mobile Node. It contains
the following the following
IP-Address-Set IP addresses assigned to the Mobile Node. IP-Address-Set IP addresses assigned to the Mobile Node.
MN-Policy-Configuration-Set For each MN-Policy in the set, a key MN-Policy-Configuration-Set For each MN-Policy in the set, a key
and relevant information for the Policy Attributes. and relevant information for the Policy Attributes.
Domain-Key: Enables access to a Domain instance. Domain-Key: Enables access to a Domain instance.
Domain-Policy-Configuration-Set: For each Domain-Policy in the set, Domain-Policy-Configuration-Set: For each Domain-Policy in the set,
a key and relevant information for the Policy Attributes. a key and relevant information for the Policy Attributes.
DPN-Key-Set: Enables access to a DPN instance assigned to a DPN-Key-Set: Enables access to a DPN instance assigned to a specific
specific role, i.e. this is a Set that uses DPN-Key and Role as a role, i.e. this is a Set that uses DPN-Key and Role as a compound
compound key to access specific set instances. key to access specific set instances.
Role: Role this DPN fulfills in the Mobility-Context. Role: Role this DPN fulfills in the Mobility-Context.
DPN-Policy-Configuration-Set: For each DPN-Policy in the set, a key DPN-Policy-Configuration-Set: For each DPN-Policy in the set, a key
and relevant information for the Policy Attributes. and relevant information for the Policy Attributes.
ServiceDataFlow-Key-Set: Characterizes a traffic flow that has been ServiceDataFlow-Key-Set: Characterizes a traffic flow that has been
configured (and provided resources) on the DPN to support data- configured (and provided resources) on the DPN to support data-
plane traffic to and from the mobile device. plane traffic to and from the mobile device.
Service-Group-Key: Enables access to a Service-Group instance. Service-Group-Key: Enables access to a Service-Group instance.
Interface-Key-Set: Assigns the selected interface of the DPN. Interface-Key-Set: Assigns the selected interface of the DPN.
ServiceDataFlow-Policy-Configuration-Set: For each Policy in the ServiceDataFlow-Policy-Configuration-Set: For each Policy in the
set, a key and relevant information for the Policy Attributes. set, a key and relevant information for the Policy Attributes.
Direction: Indicates if the reference Policy applies to Direction: Indicates if the reference Policy applies to uplink
uplink or downlink traffic, or to both, uplink- and downlink or downlink traffic, or to both, uplink- and downlink
traffic. Applying a rule to both, uplink- and downlink traffic. Applying a rule to both, uplink- and downlink
traffic, in case of symmetric rules, allows omitting a traffic, in case of symmetric rules, allows omitting a
separate entry for each direction. When not present the separate entry for each direction. When not present the
value is assumed to apply to both directions. value is assumed to apply to both directions.
4.9.7. Monitor Information Model 4.9.7. Monitor Information Model
Monitors provide a mechanism to produce reports when events occur. A Monitors provide a mechanism to produce reports when events occur. A
Monitor will have a target that specifies what is to be watched. Monitor will have a target that specifies what is to be watched.
skipping to change at page 27, line 22 skipping to change at page 27, line 22
Figure 14: Monitor Substructure Figure 14: Monitor Substructure
Monitor-Key: Identifies the Monitor. Monitor-Key: Identifies the Monitor.
Target: Description of what is to be monitored. This can be a Target: Description of what is to be monitored. This can be a
Service Data Flow, a Policy installed upon a DPN, values of a Service Data Flow, a Policy installed upon a DPN, values of a
Mobility-Context, etc. The target name is the absolute Mobility-Context, etc. The target name is the absolute
information model path (separated by '/') to the attribute / information model path (separated by '/') to the attribute /
entity to be monitored. entity to be monitored.
Deferrable: Indicates that a monitoring report can be delayed up to Deferrable: Indicates that a monitoring report can be delayed up to
a defined maximum delay, set in the Agent, for possible bundling a defined maximum delay, set in the Agent, for possible bundling
with other reports. with other reports.
Configuration: Determined by the Monitor subtype. The monitor Configuration: Determined by the Monitor subtype. The monitor
report is specified by the Configuration. Four report types are report is specified by the Configuration. Four report types are
defined: defined:
* "Periodic" reporting specifies an interval by which a * "Periodic" reporting specifies an interval by which a
notification is sent. notification is sent.
skipping to change at page 28, line 31 skipping to change at page 28, line 39
Matsushima, Danny Moses, Sri Gundavelli, Marco Liebsch, Pierrick Matsushima, Danny Moses, Sri Gundavelli, Marco Liebsch, Pierrick
Seite, Alper Yegin, Carlos Bernardos, Charles Perkins and Fred Seite, Alper Yegin, Carlos Bernardos, Charles Perkins and Fred
Templin. Templin.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997,
editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC6088] Tsirtsis, G., Giarreta, G., Soliman, H., and N. Montavont, [RFC6088] Tsirtsis, G., Giarreta, G., Soliman, H., and N. Montavont,
"Traffic Selectors for Flow Bindings", RFC 6088, "Traffic Selectors for Flow Bindings", RFC 6088,
DOI 10.17487/RFC6088, January 2011, <https://www.rfc- DOI 10.17487/RFC6088, January 2011,
editor.org/info/rfc6088>. <https://www.rfc-editor.org/info/rfc6088>.
8.2. Informative References 8.2. Informative References
[I-D.bertz-dime-policygroups] [I-D.bertz-dime-policygroups]
Bertz, L. and M. Bales, "Diameter Policy Groups and Sets", Bertz, L. and M. Bales, "Diameter Policy Groups and Sets",
draft-bertz-dime-policygroups-06 (work in progress), June Work in Progress, Internet-Draft, draft-bertz-dime-
2018. policygroups-06, 18 June 2018, <http://www.ietf.org/
internet-drafts/draft-bertz-dime-policygroups-06.txt>.
[I-D.ietf-dmm-deployment-models] [I-D.ietf-dmm-deployment-models]
Gundavelli, S. and S. Jeon, "DMM Deployment Models and Gundavelli, S. and S. Jeon, "DMM Deployment Models and
Architectural Considerations", draft-ietf-dmm-deployment- Architectural Considerations", Work in Progress, Internet-
models-04 (work in progress), May 2018. Draft, draft-ietf-dmm-deployment-models-04, 15 May 2018,
<http://www.ietf.org/internet-drafts/draft-ietf-dmm-
deployment-models-04.txt>.
[RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J. [RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J.
Korhonen, "Requirements for Distributed Mobility Korhonen, "Requirements for Distributed Mobility
Management", RFC 7333, DOI 10.17487/RFC7333, August 2014, Management", RFC 7333, DOI 10.17487/RFC7333, August 2014,
<https://www.rfc-editor.org/info/rfc7333>. <https://www.rfc-editor.org/info/rfc7333>.
Appendix A. Implementation Status Appendix A. Implementation Status
Three FPC Agent implementations have been made to date. The first Three FPC Agent implementations have been made to date. The first
was based upon Version 03 of the draft and followed Model 1. The was based upon Version 03 of the draft and followed Model 1. The
skipping to change at page 31, line 46 skipping to change at page 32, line 46
for each Context for each Context
for each DPN / direction in Context for each DPN / direction in Context
perform actions on DPN according to Command Set perform actions on DPN according to Command Set
end for end for
end for end for
end for end for
commit changes to in memory cache commit changes to in memory cache
log transaction for tracking and notification log transaction for tracking and notification
(CONFIG_RESULT_NOTIFY) (CONFIG_RESULT_NOTIFY)
Figure 15: fpc pseudo code Figure 15: fpc pseudo code
For further information please contact Lyle Bertz who is also a co- For further information please contact Lyle Bertz who is also a co-
author of this document. author of this document.
NOTE: Tenant support requires binding a Client ID to a Tenant ID (it NOTE: Tenant support requires binding a Client ID to a Tenant ID (it
is a one to many relation) but that is outside of the scope of this is a one to many relation) but that is outside of the scope of this
specification. Otherwise, the specification is complete in terms of specification. Otherwise, the specification is complete in terms of
providing sufficient information to implement an Agent. providing sufficient information to implement an Agent.
Authors' Addresses Authors' Addresses
Satoru Matsushima Satoru Matsushima
SoftBank SoftBank
1-9-1,Higashi-Shimbashi,Minato-Ku 1-9-1,Higashi-Shimbashi,Minato-Ku,
Tokyo 105-7322
Japan Japan
Email: satoru.matsushima@g.softbank.co.jp Email: satoru.matsushima@g.softbank.co.jp
Lyle Bertz Lyle Bertz
6220 Sprint Parkway 6220 Sprint Parkway
Overland Park KS, 66251 Overland Park KS, 66251,
USA United States of America
Email: lylebe551144@gmail.com Email: lylebe551144@gmail.com
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
Email: liebsch@neclab.eu Email: liebsch@neclab.eu
Sri Gundavelli Sri Gundavelli
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA United States of America
Email: sgundave@cisco.com Email: sgundave@cisco.com
Danny Moses Danny Moses
Email: danny.moses@intel.com Email: danny.moses@intel.com
Charles E. Perkins Charles E. Perkins
Futurewei Inc. Futurewei Inc.
2330 Central Expressway 2330 Central Expressway
Santa Clara, CA 95050 Santa Clara, CA 95050
USA United States of America
Phone: +1-408-330-4586 Phone: +1-408-330-4586
Email: charliep@computer.org Email: charliep@computer.org
 End of changes. 63 change blocks. 
83 lines changed or deleted 82 lines changed or added

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