[Teas] New Liaison Statement, "LS on adding transport information in 3GPP NRM to facilitate Cross-domain OAM coordination"

Liaison Statement Management Tool <statements@ietf.org> Thu, 16 July 2020 15:10 UTC

Return-Path: <statements@ietf.org>
X-Original-To: teas@ietf.org
Delivered-To: teas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE1A33A0AA5; Thu, 16 Jul 2020 08:10:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Liaison Statement Management Tool <statements@ietf.org>
To: "Lou Berger" <lberger@labn.net>, "Vishnu Pavan Beeram" <vbeeram@juniper.net>
Cc: Alvaro Retana <aretana.ietf@gmail.com>, Vishnu Beeram <vbeeram@juniper.net>, Traffic Engineering Architecture and Signaling Discussion List <teas@ietf.org>, jing.ping@nokia-sbell.com, Lou Berger <lberger@labn.net>, Martin Vigoureux <martin.vigoureux@nokia.com>, Deborah Brungard <db3546@att.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159491222615.20854.11934391007140970209@ietfa.amsl.com>
Date: Thu, 16 Jul 2020 08:10:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/8f6cZ6iwBBgk4v5CwFdvA0Evri8>
Subject: [Teas] New Liaison Statement, "LS on adding transport information in 3GPP NRM to facilitate Cross-domain OAM coordination"
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2020 15:10:27 -0000

Title: LS on adding transport information in 3GPP NRM to facilitate Cross-domain OAM coordination
Submission Date: 2020-07-16
URL of the IETF Web page: https://datatracker.ietf.org/liaison/1683/

From: Susanna Kooistra <3GPPLiaison@etsi.org>
To: Vishnu Pavan Beeram <vbeeram@juniper.net>et>, Lou Berger <lberger@labn.net>
Cc: Lou Berger <lberger@labn.net>,Vishnu Beeram <vbeeram@juniper.net>,Alvaro Retana <aretana.ietf@gmail.com>,Traffic Engineering Architecture and Signaling Discussion List <teas@ietf.org>,Deborah Brungard <db3546@att.com>,Martin Vigoureux <martin.vigoureux@nokia.com>
Response Contacts: jing.ping@nokia-sbell.com
Technical Contacts: 
Purpose: For information

Body: 1. Overall Description:

When providing an end to end communication service, the network may use non-3GPP parts (e.g. Data center network (DCN), Transport network (TN)) in addition to the network components defined in 3GPP. Therefore, in order to ensure the performance of a communication service according to the business requirements, the 3GPP management system has to coordinate with the management systems of the non-3GPP parts (e.g., MANO system, IETF defined transport system) when preparing a network slice instance for this service. This coordination may include obtaining capabilities of the non-3GPP parts and providing the slice specific requirements and other requirements on the non-3GPP parts. Figure 4.7.1 illustrates an example for the coordination with management of TN part (e.g., directly or via MANO system).

3GPP management system identifies the requirements on involved network domains, such as RAN, CN and non-3GPP parts of a slice by deriving them from the customer requirements to the services supported by the network slice. The derived requirements are sent to the corresponding management systems. The coordination may also include related management data exchange between those management systems and the 3GPP management system (see clause 4.7 of TS 28.530).

  
Figure 4.7.1: Example of coordination between 3GPP and TN management systems

The 3GPP management system maintains the network topology and the related QOS requirements. (see clause 4.4.1 of 3GPP  TS 28.530).

3GPP SA5 would like to inform you that 3GPP Management System consumes interface(s) produced by TN Domain Manager(s) for the support of network slicing. 
At SA5#117 meeting (Jan. 2018), 3GPP SA5 has sent out an LS (in S5-181456) to BBF, ETSI NFV, ITU-T SG15 and ETSI ZSM to ask for the availability of any TN Domain Manager interface(s) for the support of network slicing. So far SA5 has got a) a reply from ETSI NFV and b) an update from IETF on the network slicing information indicating their ongoing work status in 2018. 
3GPP SA5 has not received further update on the availability of the TN Domain Manager interface(s) for the support of network slicing.

3GPP SA5 would like to inform you that in SA5#131 e-meeting, contributions to add transport endpoint in 3GPP NRM (S5-203419, S5-203420) were agreed, that enables exchanging transport network topology requirements and related QoS requirements between 3GPP and TN management systems.


2. Actions:
To GSMA NEST group.
ACTION: 	3GPP SA5 kindly asks IETF TEAS WG to take the above information into account and update 3GPP with the availability of the TN Domain Manager interface(s) for the support of network slicing, and consider to specify TN Domain Manager interface(s) for the support of network slicing. 

3. Date of Next TSG-SA WG5 Meetings:
SA5#132e	24 – 28 August 2020	e-meeting
SA5#133	12 – 16 October 2020	US
Attachments:

    S5-203420 Rel-16 28.541 CR add transport information and slice mapping on backhaul endpoints
    https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2020-07-16-3gpp-tsg-sa-wg5-teas-ls-on-adding-transport-information-in-3gpp-nrm-to-facilitate-cross-domain-oam-coordination-attachment-1.docx

    S5-203419 TD proposal to add transport endpoint in NRM
    https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2020-07-16-3gpp-tsg-sa-wg5-teas-ls-on-adding-transport-information-in-3gpp-nrm-to-facilitate-cross-domain-oam-coordination-attachment-2.doc

    S5-203262 LS on adding transport information in 3GPP NRM to facilitate Cross-domain OAM coordination
    https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2020-07-16-3gpp-tsg-sa-wg5-teas-ls-on-adding-transport-information-in-3gpp-nrm-to-facilitate-cross-domain-oam-coordination-attachment-3.doc