Re: [Teas] Types within ietf-te-path-computation and ietf-te-types Modules

"Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com> Tue, 15 January 2019 14:39 UTC

Return-Path: <sergio.belotti@nokia.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 16FFF130E92 for <teas@ietfa.amsl.com>; Tue, 15 Jan 2019 06:39:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.453
X-Spam-Level:
X-Spam-Status: No, score=-6.453 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.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 jxczN7IkBsqF for <teas@ietfa.amsl.com>; Tue, 15 Jan 2019 06:39:45 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-db3eur04on0722.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0c::722]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ACAE129BBF for <teas@ietf.org>; Tue, 15 Jan 2019 06:39:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HMv/7QFnqhNajnrQTkJ+vQh3uiLreimq6He1xf+zTws=; b=OxdoQKDAypzRUR5xxBZ2oFaTNMKoWF3C6Fjibv4pDpDDKsQhRozFCbLYsWuB/vwDpQIGT1GpZKWaND0Muv4p4syLrb58WYD+U5bVZr982QjP8aT391Oc0ewmkiENP77beMypxw5qUln/8AYFYgkwlWktUzwzT8lXWEsJ5P0XJNU=
Received: from AM0PR07MB5921.eurprd07.prod.outlook.com (20.178.83.29) by AM0PR07MB3874.eurprd07.prod.outlook.com (52.134.82.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1537.16; Tue, 15 Jan 2019 14:39:41 +0000
Received: from AM0PR07MB5921.eurprd07.prod.outlook.com ([fe80::d46c:f820:830b:8cc9]) by AM0PR07MB5921.eurprd07.prod.outlook.com ([fe80::d46c:f820:830b:8cc9%6]) with mapi id 15.20.1537.018; Tue, 15 Jan 2019 14:39:41 +0000
From: "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>
To: Igor Bryskin <Igor.Bryskin@huawei.com>, "julien.meuric@orange.com" <julien.meuric@orange.com>, "teas@ietf.org" <teas@ietf.org>
CC: "esther.lerouzic@orange.com" <esther.lerouzic@orange.com>, "ahmed.triki@orange.com" <ahmed.triki@orange.com>
Thread-Topic: [Teas] Types within ietf-te-path-computation and ietf-te-types Modules
Thread-Index: AQHUrLF1Ib2A5vq+vkm4QN/hXN8bcqWwQceAgAAdqYCAAAXs8A==
Date: Tue, 15 Jan 2019 14:39:41 +0000
Message-ID: <AM0PR07MB5921AAF50C5C087F961D745A91810@AM0PR07MB5921.eurprd07.prod.outlook.com>
References: <38a2168c-b23d-0324-c058-72ce000a84b4@orange.com>, <etPan.5c3dd203.5c1b45c5.2232@localhost> <etPan.5c3dead0.76c532e5.48f3@localhost>
In-Reply-To: <etPan.5c3dead0.76c532e5.48f3@localhost>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sergio.belotti@nokia.com;
x-originating-ip: [135.245.212.87]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM0PR07MB3874; 6:mcV4pjjFJRsdN5AoUZ0IXaAaoDekz+z3CxdjvYLtqefc7xa8hkCN5G8VS120tX9P88ocBxHxf/IVKUp2zJIGPVwtZmbw9aZ2ekm9pZU7speU1Ib4uNhLtNeiciA4q9SxQaXT7r6GwA4m262EO2wwCbt6e5vNDxfonnCAtElV6DDhLwxF1wesDEgbU5kYeFuHD0gwX1nqyU7GRH28fo09YmJcukQHe9BDs0Kq26SCvCSiIpmOhfq698Sf2BeS7SqlAu72mgMsKcC5l+MKIXl6nfsbMKxr2d76eLIYQ7/HQhb95mv5oXlHamUrbXlseDvfepW0hNWAgeyprY0ccnq9dIzb4UQkjiZpaWzS9aaFzGkmMGvhOMr40CCGEJSFzrY2uBPjiNDGRblK59V9+O0P2ITcXvcK8ypeFY70YEH2FTShIAiECkRBIMKjtnFMfJHl3no1rsebm26EGMVKpYWy0A==; 5:3HLt28jCTJ8IpdgkYS9luetdhV8Cp5cwFrKMUjxQW1GBxCimN+28JJYVlBPeuucLPd6LsLSI1QPuW7rOhiu5f8/rREYYDcyBVFpLU7HnfuvhdxCG/DMRwOf68fxoryduBo0BFi5LcaR1MrCB0W/J0QsOWombS519i1d2oNq9oXXnfGcJGqfOyd/0+GwclAaI5JAYCv4bLg3AoUNorMF7eA==; 7:iYpt+/gbsf6I9V1WjudnXqYaEfuWToLyAZoc47GiRxpQV/zmqgjQuYcznJNcXTliwFA6/WeWtGsioTDRNnJKXVJ5q1MZnpjQ/+a6SRbRRg5Dy3h/MZTwPnpzqUGzGkB4W0VVjFpkNyuqRaUc88ou/g==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 1eeaca5b-b85a-4caf-19ee-08d67af748ee
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600109)(711020)(4618075)(2017052603328)(7193020); SRVR:AM0PR07MB3874;
x-ms-traffictypediagnostic: AM0PR07MB3874:
x-microsoft-antispam-prvs: <AM0PR07MB3874698A78C56B646919E19691810@AM0PR07MB3874.eurprd07.prod.outlook.com>
x-forefront-prvs: 0918748D70
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(396003)(136003)(366004)(39860400002)(37854004)(53754006)(189003)(199004)(5660300001)(9686003)(236005)(81166006)(25786009)(33656002)(81156014)(54896002)(186003)(26005)(102836004)(76176011)(53546011)(8936002)(256004)(6506007)(7696005)(7736002)(66574012)(53936002)(6306002)(14444005)(106356001)(478600001)(476003)(105586002)(4326008)(486006)(11346002)(446003)(66066001)(966005)(55016002)(8676002)(71200400001)(71190400001)(6246003)(53386004)(6116002)(790700001)(99286004)(2501003)(2906002)(3846002)(86362001)(110136005)(2201001)(74316002)(316002)(54906003)(68736007)(6436002)(229853002)(14454004)(606006)(97736004); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR07MB3874; H:AM0PR07MB5921.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: jG36romDz11hGs8jZ097NlfGphG/P7/LOs30bYJDAui1rmbG9NRf1ntq1C12EQ8okpzaIIu287UQaB3D7jhPOL9piqXA/0sbciZYeEAIyVQBN3T0w6x6mgxuIXlL8L92z632G6t2ON/91zlmJEf5E+y/s6NirUB7xrZ8tE/N5tqsL/Rx7ARTYuezkJZT3w+iP5zy4EC9YbKiAAQle03VI2dAVbDLE9moniOWwKn7AvEfO4tYhS2hRQdl2JEdF78NsHpOR3G/f/JrlUQURRzyOkH3uNt7Ur5JU9CFAaVReQN008YkAtgYkEJ4IMdI9F/yZch+SesjFPC7xdbeOnOsXFD9WVplPc6Tj6Om2/3t+0jRKgILlrzv6w52w1+VmKCNyuGttVHTbPWJemyC56YGI06cg55PQpmrZHiahBNqcYA=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM0PR07MB5921AAF50C5C087F961D745A91810AM0PR07MB5921eurp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1eeaca5b-b85a-4caf-19ee-08d67af748ee
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jan 2019 14:39:41.6947 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB3874
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/S1W_fPUWIwDRFI3Ezw61Vt5i52E>
Subject: Re: [Teas] Types within ietf-te-path-computation and ietf-te-types Modules
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, 15 Jan 2019 14:39:55 -0000

Hi Julien, Igor,

I completely share the idea 1) to share src/dst type with node-id type . As co-author, the alignment in path-computation draft to proposed definitions in te-types is one of the item we need to check carefully for next meeting .


Thanks

Sergio

From: Teas <teas-bounces@ietf.org>; On Behalf Of Igor Bryskin
Sent: Tuesday, January 15, 2019 3:13 PM
To: Igor Bryskin <Igor.Bryskin@huawei.com>;; julien.meuric@orange.com; teas@ietf.org
Cc: esther.lerouzic@orange.com; ahmed.triki@orange.com
Subject: Re: [Teas] Types within ietf-te-path-computation and ietf-te-types Modules

Hi Julien,

Two more comments from me and Italo:
1.To<http://1.To> align src/dst type with the node-id type is a good idea;
2. As widely discussed, TE node id, generally speaking, is not (pingable) IP address, nor it is a routing protocol  router ID , just a number that identifys node uniquely in the TE topology the node belongs to, hence uint32 is sufficient.

Cheers,
Igor
From:Igor Bryskin
To:julien.meuric@orange.com,teas@ietf.org,
Cc:esther.lerouzic@orange.com,ahmed.triki@orange.com,
Date:2019-01-15 07:27:22
Subject:Re: [Teas] Types within ietf-te-path-computation and ietf-te-types Modules

Hi Julien,

2 comments:
1.src (dst)-tp-id below means src/dst tunnel termination point, which is different from flink-tp-id below, which menas link termination point, i.e. place where a numbered/unnumbered link is terminated on a node;
2. We discussed a lot and believe that node-id sub-object should be different from numbered link-id sub-object ( as per current RSVP and PCEP) because there are use cases where one needs to distinguish node from link in ERO without necessarily looking into topology infotmation.

Cheers,
Igor
From:Julien Meuric
To:TEAS WG,
Cc:LE ROUZIC Esther TGI/OLN,ahmed.triki@orange.com,
Date:2019-01-15 04:05:43
Subject:[Teas] Types within ietf-te-path-computation and ietf-te-types Modules

Hi all,

A colleague of mine has started to implement some pieces of the
ietf-te-path-computation Yang module. He has already bumped into a
couple of inconsistencies that are worth sharing.

In this module, we have:

+---- path-request* [request-id]
|  +---- ...
|  +---- source?                   inet:ip-address
|  +---- destination?              inet:ip-address
|  +---- src-tp-id?                binary
|  +---- dst-tp-id?                binary
|  +---- ...
|  +---- explicit-route-objects
|  |  +---- route-object-exclude-always* [index]
|  |  |  +---- index            uint32
|  |  |  +---- (type)?
|  |  |     +--:(num-unnum-hop)
|  |  |     |  +---- num-unnum-hop
|  |  |     |     +---- node-id?      te-types:te-node-id
|  |  |     |     +---- link-tp-id?   te-types:te-tp-id
|  |  |     |     +---- ...

In the above, the types associated to source/destination and x-tp-id are
different between the request level and the RO level. This leads us to 2
fixes to consider on this document:
- src-tp-id/dst-tp-id should mimic link-tp-id and reuse te-tp-id instead
of binary;
- source/destination and node-id should share a common type (any reason
they would not?).

What is more, te-node-id is currently defined in ietf-te-types as 32-bit
only, whereas the references it mentions include 128-bit format; e.g.
RFC 6119 (section 3.2.1.) says: "it is useful to have a stable IPv6
address identifying a TE node. The IPv6 TE Router ID TLV is defined in
Section 4.1."
Fixing te-types:te-node-id is a prerequisite to fully solve the 2nd
issue above.

Thanks,

Julien, et al.

_______________________________________________
Teas mailing list
Teas@ietf.org<mailto:Teas@ietf.org>
https://www.ietf.org/mailman/listinfo/teas