[Idr] FW: draft-xie-idr-bgpls-sr-vtn-mt-03.txt - Call for WG adoption: 12/18/2021 to 1/7/2022 - Draft adopted

Susan Hares <shares@ndzh.com> Fri, 04 February 2022 12:18 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7653B3A0C70 for <idr@ietfa.amsl.com>; Fri, 4 Feb 2022 04:18:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.95
X-Spam-Level:
X-Spam-Status: No, score=0.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rz0vogKJAT5i for <idr@ietfa.amsl.com>; Fri, 4 Feb 2022 04:18:07 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70AF43A0C5D for <idr@ietf.org>; Fri, 4 Feb 2022 04:18:07 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=50.107.95.51;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
References: <008701d819bf$9f5315e0$ddf941a0$@ndzh.com>
In-Reply-To: <008701d819bf$9f5315e0$ddf941a0$@ndzh.com>
Date: Fri, 04 Feb 2022 07:18:01 -0500
Message-ID: <00a701d819c1$414baa50$c3e2fef0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_00A8_01D81997.58775000"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK/dDPk9JHL/VWCbqPYhM/WjY1vhaq0mbqg
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/IT_tDVCcBI5DZzCigGxnd7pyb1k>
Subject: [Idr] FW: draft-xie-idr-bgpls-sr-vtn-mt-03.txt - Call for WG adoption: 12/18/2021 to 1/7/2022 - Draft adopted
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2022 12:18:10 -0000

Small correction for text below 

 

old/   2) Definition of TEAS Slide ID and application to BGP/

New/2) Definition of TEAS Slice ID and application to BGP/

 

Sue 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Friday, February 4, 2022 7:06 AM
To: idr@ietf.org
Cc: spring-chairs@ietf.org; bess-chairs@ietf.org; 'TEAS WG Chairs';
lsr-chairs@ietf.org
Subject: Re: [Idr] draft-xie-idr-bgpls-sr-vtn-mt-03.txt - Call for WG
adoption: 12/18/2021 to 1/7/2022 - Draft adopted

 

WG group consensus has been reached on draft-xie-idr-bgpls-sr-vtn-mt-03.txt.


The authors should submit this draft as
draft-ietf-idr-bgpls-sr-vtn-mt-00.txt 

 

The draft has been adopted as an information draft.   

 

I've included a summary of the responses to the 2 consensus call questions. 

 

 

Summary comments on consensus call

(https://mailarchive.ietf.org/arch/msg/idr/GdQyiDN8OL0qR_j4uiHF7MKSzgU/)

 

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

A few summary comments on the consensus in the WG: 

 
Q1:  Does this informational draft aid operation of 5G networks for new
applications?

 

WG has consensus this is a useful information description. 

It is useful for 5G networks. 

The draft is useful even in scenarios were MT-ID 

among multiple domains cannot be expected (section 2.2).

 

Q2: Should IDR recommend the global VTN-ID?

IDR does not need to require a global VTN-ID to be defined for this
document. 

 

IDR should monitor TEAS, MPLS, and SPRINGs work on the following the

need for global identifiers for 5G slices.    

 

This work includes:  (but may not be limited to) 

 

1) MPLS Definition of ADI 

The  MPLS DT is discussing requirements in:

draft-bocci-mpls-miad-adi-requirements-01.txt) 

 

2) Definition of TEAS Slide ID and application to BGP 

 

TEAS WG  does not have a protocol specification for a 

Global ID that can be easily mapped to an MT-ID 

among multiple domains. 

 

TEAS does have  Network Slice framework in
draft-ietf-teas-ietf-network-slices-05.txt. 

This document: 

a) defines a slice service (section 3.2) as a 

set of CEs and a connection matrix.  

 

b) identifies the term network slice endpoints (NSE)

as an connection endpoint for ingress and egress (section 4.2).