IETF Logo Mail Archive

[Teas] Te-topology and te data models questions

Anton Snitser <antons@sedonasys.com> Tue, 22 October 2019 10:54 UTC

Return-Path: <antons@sedonasys.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 B100912022E for <teas@ietfa.amsl.com>; Tue, 22 Oct 2019 03:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.436
X-Spam-Level: *
X-Spam-Status: No, score=1.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sedonasys.onmicrosoft.com
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 Iocv5Ahj5K89 for <teas@ietfa.amsl.com>; Tue, 22 Oct 2019 03:54:56 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60132.outbound.protection.outlook.com [40.107.6.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43C2A12021C for <teas@ietf.org>; Tue, 22 Oct 2019 03:54:56 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hnai2pGrgCEEwvO2mOeaD+Rk10Reifnwg+LeQxpY0/ny++H3rfoUAAws335CeXst3HzQE6QkJCdGbyyWBNDFL1uX60mPt0nKh64Dvx6FrXvd3iZv4Mon1I+HyVEUjFTPV6+W/02x81MgoTqCro7JhXc0z9h61YtZI8km56pzbMdRinVE+5Vmn/nQRn42TuNK5pX6NRhuyX7o4fekWOAEHXGvV6oWpFihi7R7Ty4xDlA94bXSEXFiH5yMLSpmlk7grcg4DQFQsyIKAHg7BSyUlrY1Y2R1xyX8KN32j20zfkWGT3hLZkl6cX8DXizoIdoHQsIWKnxnESinzd8/yRZFNA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=e9ui1r01Xj1XCZk+PJIVJQ9x/uRn6YZi3wd49JLLtEo=; b=YAatfxAQAsp7iTV6GIM4M6VnP1Z20eYhpwaQYxV0STrK1EkbJe5wgg2eLqtnkMo31puF6xzS/YSCENu797AlyvvB0vSaKxCLAIIuIGlRglGCmitdWP7K0M7aUA4V1saAZypFlQBmk+AvVs6lTXlILBjclm7OA3cciJvbqdo1txRHdMJM+a+9GB2fIn0OuKsikjQ3UIW+QpjAdGFAmxa4VpLYG88XQ6PhZAEaRvH05vtGIocl+ePwnrwop0YAA9UE1Lc07UA2DWwaC32cMrk7UVm6gReO/UcBiDJeoEm7I4WIefjF3BODqbT/MPU9fiX1Dfu4EsE5hRybZxpJ78WOuA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sedonasys.com; dmarc=pass action=none header.from=sedonasys.com; dkim=pass header.d=sedonasys.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sedonasys.onmicrosoft.com; s=selector2-sedonasys-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=e9ui1r01Xj1XCZk+PJIVJQ9x/uRn6YZi3wd49JLLtEo=; b=X3ffLa1g0NvW8IDO84m7oZyGxzIZW35Hks+t84bUdwdeD6JzQ7fhbzB+ExgN+lJJaRz/DtsShcgU04xa1u5/NL8Ii2+cDaVy2O/RmTBip259JRtesKXCful6ip+Lxf3xVaJE5z5n+cp+hiJJHGqgg0hTtA2PsoVxUrIEBA3xCak=
Received: from DB8PR10MB3387.EURPRD10.PROD.OUTLOOK.COM (10.255.17.204) by DB8PR10MB2780.EURPRD10.PROD.OUTLOOK.COM (20.179.11.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2367.20; Tue, 22 Oct 2019 10:54:53 +0000
Received: from DB8PR10MB3387.EURPRD10.PROD.OUTLOOK.COM ([fe80::50ed:4f45:c83c:20ce]) by DB8PR10MB3387.EURPRD10.PROD.OUTLOOK.COM ([fe80::50ed:4f45:c83c:20ce%5]) with mapi id 15.20.2367.022; Tue, 22 Oct 2019 10:54:53 +0000
From: Anton Snitser <antons@sedonasys.com>
To: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: Te-topology and te data models questions
Thread-Index: AQHViMcitca1lXHc9k6nIr+9y4jXzQ==
Date: Tue, 22 Oct 2019 10:54:53 +0000
Message-ID: <E317D9F6-D881-4F9B-8640-C3E5F6E25EEC@sedonasys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=antons@sedonasys.com;
x-originating-ip: [37.142.40.85]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a6abbfec-85e0-4d3e-1ab4-08d756de450f
x-ms-traffictypediagnostic: DB8PR10MB2780:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <DB8PR10MB2780CB0A7AAAC9CBA53367FDD7680@DB8PR10MB2780.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01986AE76B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(366004)(396003)(136003)(376002)(39830400003)(53754006)(189003)(199004)(733005)(316002)(256004)(81156014)(8936002)(99286004)(26005)(861006)(1730700003)(81166006)(6506007)(8676002)(102836004)(5660300002)(2906002)(86362001)(99936001)(186003)(66574012)(6436002)(2616005)(476003)(6486002)(486006)(6916009)(6116002)(790700001)(66946007)(606006)(3846002)(66446008)(66556008)(64756008)(66476007)(71190400001)(236005)(66576008)(6512007)(71200400001)(36756003)(45080400002)(7066003)(7736002)(76116006)(14454004)(66066001)(33656002)(91956017)(2351001)(508600001)(2501003)(5640700003)(54896002)(6306002)(25786009); DIR:OUT; SFP:1102; SCL:1; SRVR:DB8PR10MB2780; H:DB8PR10MB3387.EURPRD10.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: sedonasys.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Z1SaMmyfRlUgPVE3utOcIm3VD4a2/zzE/KRA2mROP91TrjX/QL9ihuOvuhgvgrCBFMZAy31BanJpRP0DVphEX2JjQNScnqsiKT1a/4DiSU2F1fe7WbVZ47aLGaN+wLW0RT+REAJodBtLrdmIqInN78oxrmiBrwfn8jtsx91boATv+4KHkmn5DqNDeYu28zpFA13Bewtetdwme3WFTCkV0P6Qa3+fYxps1pH1IojZl+UjRlafL3dUlCkTDIiWSHt2ybcL4sKXHIqoHbhnU5LDJPIm41OR5xR/6f44LjGxkucaTummq6kOkuITlyOgre6e5Mf6SatFMZS2O1QVjUtB7VHfR84R7JeqklWN+YJnIUkYJj3R5t604GBsuCsocHSMrbLcM8DQpQlMiv2MyvVw2t2nLaS1VcdJJywYScCpVy3SYnG2ak1g1kim0C8YLSl14mInoMt0TZ3BGXwocMYnyOB9DY73Xn6DiYFZiMEredo=
x-ms-exchange-transport-forked: True
Content-Type: multipart/related; boundary="_005_E317D9F6D8814F9B8640C3E5F6E25EECsedonasyscom_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: sedonasys.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a6abbfec-85e0-4d3e-1ab4-08d756de450f
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2019 10:54:53.6321 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d7c5624d-c76e-473e-9a79-91d374431ce8
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: p3I3HmorAXj6C66saWl7pyXZaawcscKLYIHJmwCi6dBTbo0X85hawfFY7R7vvn6Y1x61QRxIwtqcDMCgE+MFJA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR10MB2780
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/6OSM44mdnO7q_VtGFlagoofWs6Y>
Subject: [Teas] Te-topology and te data models questions
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Tue, 22 Oct 2019 10:54:59 -0000

Hello everyone,

Name is Anton, am a systems engineer from Sedona systems.

I have been reviewing the ietf-te.yang and ietf-te-topology.yang data models as well as their various augmentations and I had a few questions regarding how they are meant to be used when representing native network state and managed objects. Not sure if this Is the correct email group. Saw it in the drafts, decided to try.


  1.  What is the usage scope of transitional links? – it is meant to represent an inter-layer transition between different layers, but as per the diagrams In the drafts I have only seen it being used in the same node. Can transitional links be used inter layer to describe a cross-layer-link in a technology disaggregated environment? E.g., a router port <-> OTN client-port and subsequently the OTN to WDM cross-layer-links. consider each layer node as a separate physical node e.g., physical router, OTN switch and WDM node

Consider the following.
[cid:image001.png@01D588E0.473D28E0]
Is it possible to describe a link where a source node:tp from the IP topology and a destination node:tp from the OTN/WDM topology create a transitional link


  1.  Are there strict guidelines on how a TTP should be modeled? In the drafts it is mentioned a TTP can be an OCH transponder in the WDM topology. What about OTN and IP? What are the rules used to designate a physical/logical entity as a TTP or non-TTP entity?
     *   Can an IP loopback on routers be considered a TTP? If not then what is a TTP in the IP layer?
     *   What is a TTP in the OTN layer? Is it the framing module in the switch?


  1.  The figures are missing from the tutorial draft<https://tools.ietf.org/html/draft-ietf-teas-te-topo-and-tunnel-modeling-04>. Is there a reference implementation document somewhere?


  1.  I have more questions, but I wanted to start slow.. to see there I get an ACK response.



Thank you very much to whoever answers!
Brgrds

[id:image001.png@01D3D4EC.AFD81260]
Anton Snizar | Systems Engineer

m: +972-504042744
e: antons@sedonasys.com<mailto:antons@sedonasys.com>
w: sedonasys.com<https://sedonasys.com/>
l: Linkedin<http://linkedin.com/in/anton-snizar-4aa57646/>

v2.23.0 | Report a Bug | By Email