[Lsr] draft-xie-lsr-isis-sr-vtn-mt-02
Huaimo Chen <huaimo.chen@futurewei.com> Mon, 19 October 2020 15:09 UTC
Return-Path: <huaimo.chen@futurewei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF6B3A0365 for <lsr@ietfa.amsl.com>; Mon, 19 Oct 2020 08:09:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.189
X-Spam-Level:
X-Spam-Status: No, score=-0.189 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 pL1Ko_iyabug for <lsr@ietfa.amsl.com>; Mon, 19 Oct 2020 08:09:11 -0700 (PDT)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2109.outbound.protection.outlook.com [40.107.243.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F15243A0317 for <lsr@ietf.org>; Mon, 19 Oct 2020 08:09:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=h6e9dAfzD3DuLpH81J7vyN/PT1GHaBvADfnqOOMSyyIzkQzyD2PbVYd4/vWCU1GBdxa3PKbHl7OctnFXuzMPCM5vehWwF56F5AoOvZY+dO1JTxeHdhLy9Lh/t0LdN8IR6h1/sRwP9gAGqI3rwYsewc4fZndH7FkpBM7O2+j1T1KMcdgh+nW5MtKcHr8CjjnEr8eOLFMffSYhSAkIDn36kWlyQnp2Vv1zdkdOb00LqAoN8YKZjLpywYoyizThyo9zIZ9FtOKTA6epGbCcFUJlfAktQgQHRd5j9XT8KJZM+HiuTbA6cJQ0JWc/zuAeMixTeN6vzRBrB/Mg+UaugIaQNw==
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=kj0n0fBYU7USkHOBsmGlu4HHeEkambqGRP+6wztbmp4=; b=eccxagVYDdebAmPKAZZrrKJGuIPy7avjLS34WP4f5v9sBZifkEuT1KfYITU6tTcjscZOvRanfy39bjP+UKCXRENKM/S2FtGEJ0tuFrEfHz5g+qmBnLJRR4vd5/rxDE2rvCp6kpmcJpqCjStVVXkFal7yP0v4b21GuJcOoWXxkFCa1qKGH7JMuvQXwtxoX2Alut4T+3cvme2YJAkyYjBgOUUImZ6z7lnwrrZuWfFO77neYon2qGArzBWLClXq8ah8o+N3DFdjEm7EjIp0duiHniVZZrS3OJlGjjVq+t9dFgKXUiOTF//YpY41S8/1sr9oq2ikoi8B8y8NvqwaB4NYFg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kj0n0fBYU7USkHOBsmGlu4HHeEkambqGRP+6wztbmp4=; b=YTfSug7GMurp0rEoR/HmlzFcLgKjM7koqHCgnb99EbEQ2SkgrjFEzc1sNDTq4csJjPN/CcHcEM97oFNC30XMLkZ1nt4YI81JmrPV9EA9QWkLuUngtGnnH+Qwo30tq01RrsQ/YPa7KvmOXDO98gzLX0yZ7+fg2Euu3Aaha7qsOKk=
Received: from MN2PR13MB4087.namprd13.prod.outlook.com (2603:10b6:208:263::16) by MN2PR13MB3535.namprd13.prod.outlook.com (2603:10b6:208:169::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.11; Mon, 19 Oct 2020 15:09:08 +0000
Received: from MN2PR13MB4087.namprd13.prod.outlook.com ([fe80::a85c:e7b3:4471:18f8]) by MN2PR13MB4087.namprd13.prod.outlook.com ([fe80::a85c:e7b3:4471:18f8%7]) with mapi id 15.20.3499.015; Mon, 19 Oct 2020 15:09:07 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: draft-xie-lsr-isis-sr-vtn-mt-02
Thread-Index: AQHWph98qMRWSMMbYECf37g6lDukqQ==
Date: Mon, 19 Oct 2020 15:09:07 +0000
Message-ID: <MN2PR13MB40878C9C29F8332CA7CD69F1F21E0@MN2PR13MB4087.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [2601:199:4300:8e5a:dfd:1127:ed96:de02]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f15b9218-a8b3-4935-ca71-08d87440ed3e
x-ms-traffictypediagnostic: MN2PR13MB3535:
x-microsoft-antispam-prvs: <MN2PR13MB3535FE04CBC17F586FAF0FD6F21E0@MN2PR13MB3535.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 0AnPSqk6WxbC9aae8Tzt/jozcMrYdwlv7vGxILNmGU9DCeC/44tLr4gSvsgM9eNr9ujU590+agnlL+fzLea1z2Hhgs5A4jAbBGO/ld/Vc3bwdoj1+McPRKeJbuavkJIdh1cq05zePgvweGPJ4krQcjDpQNxpj3c/V/J01uIhjHkt/y8P5yZHV8HFYg4vjKTdC/nES9vEtH07WOQgtyj7RXV0lIaDPYWOVqduMGizDXIJjpsBNQCsxt0aWlXhVxCei/7DCsgXc0GDK6HmSuwEUiQ1xxs/0y+/X8Nc/fErhxJdZtnK5WZEKMIj4xB3iC1rNCm9UdO1eYr6B4IRJOIBCw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR13MB4087.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(396003)(366004)(136003)(39840400004)(376002)(346002)(478600001)(7696005)(19627405001)(83380400001)(8676002)(33656002)(86362001)(6506007)(55016002)(52536014)(8936002)(316002)(5660300002)(71200400001)(6916009)(2906002)(44832011)(64756008)(66446008)(66556008)(66476007)(66946007)(9686003)(76116006)(186003); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: b6ng2a899AYCxRXeDZX9o63tvICVS1boWb7LKDZAVpodA96VK6EvadQsIL3FziRSl+BARGVtbBwomGBul4cDBoGGW6vUqY6TU8451ngIOyBZljBzsmXaiWBFEY6+xuWdRjXL4qrNFkT+asw9Ll/wrUdrYYzjs6XQTjp9Phptxr38SX18UQbCzFfcIRZiew7P+bCP+5FKscvGqvCXJx2Sdixrwvi9GtAznMRbly/v7AgVt5X/JPC4bGULf9bPrea6nQRQaZhgp5YBO6umqWAbxlhoFiLAzBnw9c2FIGCKMKcjxQ3HOz+xjZemXuThzQBa/4cutvNXrQ5f4PKBFG+8eBzixPr2YxIxAol3BCldRO2rRwgq9wPG89gNQayzKzI6OI+1Msc7MRovy6zQMken/LhtTrOEvZ65UARkbaRyS2GO5najTQT3nR5vRzxh5meNm7DC1Zl8m05HpnWR51pBaNydEXf7hO7kOpTVDcuIdjuy2yQe7SBK2P4ibBO9KpOED6MDcAQe30R1kiGaTwUoG3TG9Lw5SxkJf6u3yXxnJhWIG3vKZl4nLFrUOrqf5lAak81pmAaLHnjbyFjHrpltfxlaczIt8IedkCWztw0EI6HuhcswaqinFvy5rm6sH4Uoa1nEmlUSj1g+jPWVM5y3UqUIDEe10/MdL/hpWlODbpf6r3gQugRpHaJqS2PLXLjpapAxFdTAxfW4YF6Hy4dliw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB40878C9C29F8332CA7CD69F1F21E0MN2PR13MB4087namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR13MB4087.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f15b9218-a8b3-4935-ca71-08d87440ed3e
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Oct 2020 15:09:07.8386 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: JXASO5LhK6nXQc2blia2jnZzythi/Dd+aLdKGrbq+sPhtyQH5PufnA0JE60+VFtHsV+a20D0odzD3wQAl+75Nw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3535
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/OjD4pKnnUgowIV6KqJeyxJrFWV0>
Subject: [Lsr] draft-xie-lsr-isis-sr-vtn-mt-02
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2020 15:09:12 -0000
Hi Authors,
I have the following comments/questions:
In a network, can we use other methods to define VTNs while MTs are used as VTNs?
If so, other methods may be used to define VTNs in addition to using MTs as VTNs in the same network. The draft says that MT-ID could be used as VTN-ID. In this case, a block of VTN-IDs must be allocated/reserved specially for using MT-IDs as VTN-IDs. It seems better to state something about this in the draft.
An IS-IS MT has the attributes of a VTN, including the specific topology and resource. An IS-IS MT can be used as a VTN and MT-ID can be used as a VTN ID. Is it possible for an IS-IS MT to be used/shared by two or more VTNs? If so, it seems better to have some details about how the multiple VTNs use/share the resource in the same one MT.
In section 5 "Scalability Considerations", the draft says that while multiple VTNs share the same topology attribute, the same topology is identified by multiple different MT-IDs. This seems giving a way to let two or more VTNs to use/share one MT if IS-IS MT allows multiple MT-IDs to be used for the same one MT. It seems better to move the related text from section 5 to some of the previous sections.
Best Regards,
Huaimo
- [Lsr] draft-xie-lsr-isis-sr-vtn-mt-02 Huaimo Chen
- Re: [Lsr] draft-xie-lsr-isis-sr-vtn-mt-02 Xie Chongfeng