[Teas] Relationship between TE topology and SAP topology

Italo Busi <Italo.Busi@huawei.com> Wed, 20 November 2024 11:22 UTC

Return-Path: <Italo.Busi@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A241FC1654EB for <teas@ietfa.amsl.com>; Wed, 20 Nov 2024 03:22:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iTTFatDRbPDx for <teas@ietfa.amsl.com>; Wed, 20 Nov 2024 03:22:26 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F81FC151091 for <teas@ietf.org>; Wed, 20 Nov 2024 03:22:26 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Xtf6G4GZjz6K9BF for <teas@ietf.org>; Wed, 20 Nov 2024 19:20:06 +0800 (CST)
Received: from frapeml100005.china.huawei.com (unknown [7.182.85.132]) by mail.maildlp.com (Postfix) with ESMTPS id 44E46140AB8 for <teas@ietf.org>; Wed, 20 Nov 2024 19:22:23 +0800 (CST)
Received: from frapeml500007.china.huawei.com (7.182.85.172) by frapeml100005.china.huawei.com (7.182.85.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Wed, 20 Nov 2024 12:22:23 +0100
Received: from frapeml500007.china.huawei.com ([7.182.85.172]) by frapeml500007.china.huawei.com ([7.182.85.172]) with mapi id 15.01.2507.039; Wed, 20 Nov 2024 12:22:23 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: Relationship between TE topology and SAP topology
Thread-Index: Ads7PNEaUzhVEbhvRPexe/q9rtSigQ==
Date: Wed, 20 Nov 2024 11:22:22 +0000
Message-ID: <143eea52ca024234b15b44c795678ac4@huawei.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.246.202]
Content-Type: multipart/alternative; boundary="_000_143eea52ca024234b15b44c795678ac4huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: 6R5TBXMSVMNQYJZQBWEDKV5QSGVF67MM
X-Message-ID-Hash: 6R5TBXMSVMNQYJZQBWEDKV5QSGVF67MM
X-MailFrom: Italo.Busi@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Teas] Relationship between TE topology and SAP topology
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/FKjX1Y6ueKNxIkfUtYdE00oM2z4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

Hi Oscar, TEAS WG,

During the TEAS WG session at IETF 121, Oscar offered to provide some text to clarify the relationship between the TE topology and the SAP topology

This is the current text in draft-ietf-teas-actn-poi-applicability-12:

   There are two possible models to report the access links between CEs
   and PEs: the TE Topology Model, defined in [RFC8795], or the Service
   Attachment Points (SAP) Model, defined in [RFC9408].

   Although the discovery of access links is outside the scope of this
   document, clarifying the relationship between these two models has
   been identified as a gap.

Considering that the scope of draft-ietf-teas-actn-poi-applicability is to identify gaps, the authors think that we can add the guidelines on using TE Topology and SAP Topology if the text proposal is available before the document is ready for WG LC. Otherwise, the document can be submitted to WG LC just highlighting the gap and without providing any guidance on how to address it.

It is worth noting that there is a similar issue in the TE topology profile draft and the gap can be addressed in that document.

These are some doubts I am having:

  1.  Are TE topology and the SAP topology intended to be used exclusively on different control interfaces? Or, can they co-exist on the same control interface?
  2.  It they can co-exist on the same interface, how it is possible to associate TE and SAP topological entities? For example, which LTP is associate with which SAP?
  3.  It they can co-exist on the same interface, are the they providing completely different and complimentary information or there is some overlapping of information?
  4.  It they can co-exist on the same interface and provides some overlapping information, how to reconcile any difference/inconsistency between the information reported by the two models?

Thanks, Italo