Hello folks,

I am in the process of reviewing the FPC document. It is an important document and will be foundational for subsequent work in [dmm]. I would like to suggest a change in terminology. I think the way "Port" is currently defined in the document is very confusing, because it is not very intuitively related to the traditional uses of "port" as in TCP, or in switches.

As I understand it, "Policy" lives on the control plane side of the interface, and "Port" is intended to denote a concept that is important on the data plane side of the interface. "Flow" is another word that is closely tied to the data plane, and it seems to me that as currently defined in the document a "Port" is a collection of flows that correspond to a specific Policy or Policy Group.

So, I would like to propose that the word "Port" should be replaced by the term "Flow Group". Another alternative would be "Flow Policy Group", which could then be abbreviated FPG. However, the latter has the perhaps undesirable effect of tying the word "Policy" to a data-plane concept.

Thanks for any comments on this proposal to modify the terminology.

I think it is important to make the terminology as unambiguous and intuitive as we possibly can, especially because the document is necessarily written at a high level of abstraction.

Regards,
Charlie P.


On 10/31/2016 9:54 AM, [email protected] wrote:
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Mobility Management of the IETF.

         Title           : Protocol for Forwarding Policy Configuration (FPC) 
in DMM
         Authors         : Satoru Matsushima
                           Lyle Bertz
                           Marco Liebsch
                           Sri Gundavelli
                           Danny Moses
        Filename        : draft-ietf-dmm-fpc-cpdp-05.txt
        Pages           : 153
        Date            : 2016-10-31

Abstract:
    This document describes the solution of data-plane separation from
    control-plane which enables a flexible mobility management system
    using agent and client functions.  To configure data-plane nodes and
    functions, the data-plane is abstracted by an agent interface to the
    client.  The data-plane abstraction model is extensible in order to
    support many different type of mobility management systems and data-
    plane functions.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-fpc-cpdp/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-fpc-cpdp-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm


_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm

Reply via email to