Re: [Teas] New Version Notification for draft-lee-teas-te-service-mapping-yang-07.txt

"Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com> Wed, 02 May 2018 11:58 UTC

Return-Path: <michael.scharf@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 24352126D3F for <teas@ietfa.amsl.com>; Wed, 2 May 2018 04:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_KAM_HTML_FONT_INVALID=0.01] 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 DTXTafkGW3nn for <teas@ietfa.amsl.com>; Wed, 2 May 2018 04:58:39 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20103.outbound.protection.outlook.com [40.107.2.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05D59120454 for <teas@ietf.org>; Wed, 2 May 2018 04:58:38 -0700 (PDT)
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; bh=V44jVxwMZLPofKulYX4UTws8/Hk4O7VXBayOHpEwOHc=; b=EsKrlFw+Dbaj0J4hvzSpztQvstQKav/OcxG6YLPRsM23dA9I9chVbnzfb0KJVLoXjCSJxh2fOLqmn+JoN1nPPwOZnGGcU8ncPtFQ7iU1KDfMZZbuYYW6eS/ZF5dUKyMxNJmjWCH4IAdrZt/yfhTcavt2sUZf6VOeiY0m3Vy5EL0=
Received: from AM5PR0701MB2547.eurprd07.prod.outlook.com (10.173.92.15) by AM5PR0701MB1810.eurprd07.prod.outlook.com (10.167.216.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.735.6; Wed, 2 May 2018 11:58:35 +0000
Received: from AM5PR0701MB2547.eurprd07.prod.outlook.com ([fe80::a1ee:77c0:a9c5:977e]) by AM5PR0701MB2547.eurprd07.prod.outlook.com ([fe80::a1ee:77c0:a9c5:977e%4]) with mapi id 15.20.0735.006; Wed, 2 May 2018 11:58:35 +0000
From: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>
To: Lou Berger <lberger@labn.net>, Leeyoung <leeyoung@huawei.com>, Vishnu Pavan Beeram <vbeeram@juniper.net>, "teas@ietf.org" <teas@ietf.org>
CC: Dhruv Dhody <dhruv.ietf@gmail.com>, Jeff Tantsura <jefftant@gmail.com>, Giuseppe Fioccola <giuseppe.fioccola@telecomitalia.it>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Thread-Topic: [Teas] New Version Notification for draft-lee-teas-te-service-mapping-yang-07.txt
Thread-Index: AQHTzOx3mRcxMi/fEkChBP4BE+YqfaPyPyUQgCjBAgCAAXmhIA==
Date: Wed, 02 May 2018 11:58:35 +0000
Message-ID: <AM5PR0701MB2547D16FFF442B4472DBAC2093800@AM5PR0701MB2547.eurprd07.prod.outlook.com>
References: <152293940455.26004.8362854609783865293.idtracker@ietfa.amsl.com> <7AEB3D6833318045B4AE71C2C87E8E173CFCD33B@sjceml521-mbs.china.huawei.com> <96bad40b-c6af-c8b5-0340-d14947ba3c86@labn.net>
In-Reply-To: <96bad40b-c6af-c8b5-0340-d14947ba3c86@labn.net>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
x-originating-ip: [135.245.212.158]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB1810; 7:ktvt8BqxIH30+1G1zcSx0NNjbEwfc2HKmyi4J3zxdS40bmAv4ZJ9MBeu8Tz+avQg+77wU/gNRUFFu2Qaw4jFlhV7MP/VkWMRzt+viPPwXJj2FiLzxq1bHhsvPw67eV/reDGiXQlwnjzvKRQBw+1LKgsQIOojpZ1sdCJI8R9LJ0wMy+knan2HFZeaVi5w4AbHTRIB9NEXN2Q5kUPMVEnlr8jUkdBLxY7bJxxdoERlaBD7fB2fRyPvO5TGwv85EDaW
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(48565401081)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7193020); SRVR:AM5PR0701MB1810;
x-ms-traffictypediagnostic: AM5PR0701MB1810:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=michael.scharf@nokia.com;
x-microsoft-antispam-prvs: <AM5PR0701MB18108F87F44E2E31CF1D906693800@AM5PR0701MB1810.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3231254)(11241501184)(806099)(944501410)(52105095)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041310)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123558120)(20161123560045)(6072148)(201708071742011); SRVR:AM5PR0701MB1810; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB1810;
x-forefront-prvs: 06607E485E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(39380400002)(396003)(346002)(39860400002)(199004)(189003)(53936002)(11346002)(6306002)(55016002)(9686003)(54896002)(99286004)(8666007)(14454004)(76176011)(54906003)(478600001)(106356001)(5660300001)(6246003)(25786009)(59450400001)(110136005)(33656002)(102836004)(186003)(7696005)(5250100002)(229853002)(316002)(26005)(68736007)(6506007)(8936002)(81156014)(86362001)(105586002)(3280700002)(2501003)(2906002)(81166006)(7736002)(4326008)(790700001)(1941001)(6116002)(74316002)(8676002)(486006)(97736004)(66066001)(476003)(3846002)(3660700001)(2900100001)(6436002)(39060400002)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:AM5PR0701MB1810; H:AM5PR0701MB2547.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: eCuyOCxMzUxxfZ3pdgkcVIy96SdT9cICctCu0EIBB23sot9Ud2uR1NjX5W96a14u7pbwUuf+0GhMXLXQiFxEHZpAQZJUC4bEiZYoPr0AFIaYuW3ZX0HOOkzUFvLUge7oTYGfTSe8os7kd5xk4djalt07rSjKsoTD3ywt7l6+8jvzWVnJFpl3beUZhksVEtIfk6MWfJC967PKGwE6ghliDBx7cpb47eg9PVhr0JXykEU=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM5PR0701MB2547D16FFF442B4472DBAC2093800AM5PR0701MB2547_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 320cdaee-0ef7-4b5e-43eb-08d5b02408b0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 320cdaee-0ef7-4b5e-43eb-08d5b02408b0
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 May 2018 11:58:35.3092 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB1810
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/TLfk2bWFyJjKdbLOd0saIthCKS0>
Subject: Re: [Teas] New Version Notification for draft-lee-teas-te-service-mapping-yang-07.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 02 May 2018 11:58:42 -0000

I think having a way to map from the LxSMs to  te topology makes a lot of sense.  Although, personally I would have looked at augmenting the existing models with te-topology-ids and te-tp-ids before defining a new module.  This said, what's really important is the opinion of WG contributors.  So I'd be more interested in hearing what others think of the approach.

[Michael] It is somewhat difficult to comment on the variants suggested in different draft versions without realistic examples. Figure 1 is a non-starter as this seems to assume that a single transport network is uses by two AS. This is (1) not the typical scenario in many network operators, (2) it would require a more detailed discussion on how the AS peer which each other (option A, B, C, etc.), and (3), it shows only L3SM, while the document intents to be applicable to L2SMs and L1CSM as well. These are about different technologies. In my opinion, an I-D that proposes a YANG model should at least include some basic explanation how it would be used in an actual network, in particular if the use is not obvious.

Michael