[DMM] Re: mobile traffic steering - feeback on clarifying co mments and questions

Hi,

 

In addition, there was another comment Q of the draft from the IETF-121 @ Dublin: 

 

“Is there a relationship to CATS?”

==============

CATS is about compute-aware traffic steering assuming an overlay network in which a network edge node (C-PS) makes decision based on the metrics of interest, and then (C-Forwarder) steers the traffic to a node that serves a service instance (service contact instance + service instance). Similar to MTS, CATS also has 3 deployment models, i.e., distributed, centralized and hybrid. However, the classification of CATS models depends on how *computing metrics’ are distributed and/or collected among the three major networks (client network, transport network and service network). On the other aspect, MTS differentiates the 3 types of models mainly based on the interactions between the MCS domain and the MTS domain, without the requirement of direct involvement of ACS metrics in the DN (service network domain).

 

In our opinion, MTS proposes a more generic framework which CATS could certainly leverage, e.g., the reference points defined in the MTS draft. For example, the dedicated MTS controller may be a good anchor for the CATS control plane (i.e., C-NMA). Further, while the MTS Controller uses the MTS reference point towards the mobile communication system control plane, CATS may define a reference point and semantics between the compute domain (service network) and the MTS controller. This would help complete the end-to-end view of the needed control plane up to the data network/compute domain.

=============

 

Let us know if you may have more comment(s) and/or question(s). 

See you in Bangkok.

 

BR,

 

-Tianji

 

 

From: Marco Liebsch <[email protected]>
Date: Tuesday, March 11, 2025 at 9:08 AM
To: "[email protected]" <[email protected]>
Subject: [DMM] mobile traffic steering - feeback on clarifying comments and questions

 

Folks,

we’d like to address a few received and remaining questions and comments on the discussed mobile traffic steering work and the associated
draft (https://datatracker.ietf.org/doc/draft-liebsch-dmm-mts/) before IETF122. 

 

The question was “Relationship to N6-intf 'router' on traffic steering: how the N6-intf 'router' may interact with the TN ?”

 

The question applies to a 3GPP reference points N6, which is between the User Plane Anchor (UPA) and the Transport Network (TN) towards the
Data Network. The updated draft defines clearly the reference point where it applies, which is between a dedicated controller in the TN and the
mobile communication system (MCS) control plane, as well as between a TN’s Data Plane Node (DPN) such as a router and the
MCS’s UPA. These two associated interfaces can be used to interact between the MCS and the TN. 

 

For details please refer to section 6 of https://datatracker.ietf.org/doc/draft-liebsch-dmm-mts/, where we explain three operational
modes for such interworking based on a dedicated controller in the TN and/or a decentralized control plane, such as BGP.

 

Please let us know in case you have more comments or questions.

 

marco

 

 

 

_______________________________________________ dmm mailing list -- [email protected] To unsubscribe send an email to [email protected]

_______________________________________________
dmm mailing list -- [email protected]
To unsubscribe send an email to [email protected]