Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"

"Acee Lindem (acee)" <acee@cisco.com> Thu, 10 June 2021 19:14 UTC

Return-Path: <acee@cisco.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 4124D3A1500 for <lsr@ietfa.amsl.com>; Thu, 10 Jun 2021 12:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.584
X-Spam-Level:
X-Spam-Status: No, score=-9.584 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=P81P0FMc; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=P2XUzyW5
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 g6MLY8fp2c8B for <lsr@ietfa.amsl.com>; Thu, 10 Jun 2021 12:14:36 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB8603A14FE for <lsr@ietf.org>; Thu, 10 Jun 2021 12:14:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26209; q=dns/txt; s=iport; t=1623352475; x=1624562075; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=8j7ivjKUZE0vC7OuEijbDlKQJU+c0uT3U9uYQa0aAds=; b=P81P0FMcudCYYX50Qfnyg6YZCHa39B47uH4tedt6KJoYiaPvbcyqPxLP jBb8dXW0i5mXl1adh4UN8XZ6kxMoxKtC16agvhS2OUZ0F59eelpedZzb8 C952R9euz341CO/n2yAsef0eQDZpTw41zCVNBRJ4CWW14FFWU2FUa/7xx s=;
X-IPAS-Result: A0D3AQA/ZMJgl4sNJK1XAxYGAQEBAQEBBwEBEgEBBAQBAYIXgSMwIwYoflo3MQuEPYNIA4U5iFElA4pLj02BQoERA1QLAQEBDQEBKgEMCAIEAQGEUAIXglECJTgTAgQBAQEBAwIDAQEBAQUBAQUBAQECAQYEFAEBAQEBAQEBaIVoDYZFAQEBAQMBARALBgoTAQEsCwELBAIBBgIHCgMBAQEJHwMCAgIfBQELFAkIAgQBDQQBGweCTwGBflcDLwEOjVCPNAGBOgKKH3qBMoEBggcBAQYEBIE4Ag5Bgw4NC4IxCYE6gnuEDAEBgReFSiccgg2BFQEmDBCCMS8+giBCAQEBAQGBKAELBwEHMQkBDAkICYJQNoIugl1bBmQEUQEBBSogAQsgHUEvXJEWgzuID40ekSRbCoMcig+IAoYMhVkFJoNeiyCWZpNWbgyBAoIYiX+DKJRxAgICAgQFAg4BAQaBayJrcHAVOyoBgj4JRxcCDo4fDAUICRVtAQiCQ4UUhUpzAjYCBgEJAQEDCXyGJoE2AYEQAQE
IronPort-PHdr: A9a23:q+vJwxyLiN9KYrXXCzM5ngc9DxPP8534OwcP4dwmhq5ANKO58MeqM E/e4KBri1nEFcXe5ulfguXb+6bnRSQb4JmHvXxDFf4EVxIMhcgM2QB1BsmDBB73KffwZGo7E dhMElh/8CLzPU1cAs2rYVrUrzW75iITHROqMw1zK6z1F4fegt7x2fq1/sjYYh5Dg3y2ZrYhR Cg=
IronPort-HdrOrdr: A9a23:rGt47a9z9dynrRyNEMFuk+Fldb1zdoMgy1knxilNoENuE/Bwxv rBoB1E73DJYW4qKQ4dcdDpAtjmfZquz+8K3WBxB8bjYOCCgguVxe5ZnPDfKlHbakjDH6tmpN tdmstFeZ7N5DpB/LzHCWCDer5KqrTqgcPY59s2jU0dMD2CAJsQiTuRfzzranGeMzM2fKbReq DsgvZvln6FQzA6f867Dn4KU6zovNvQjq/rZhYAGloO9BSOpSnA0s+5LzGomjMlFx9fy7Yr9m bI1ybj4L+4jv29whjAk0fO8pVtnsf7wNcrPr3ItiFVEESptu+bXvUmZ1SwhkFtnAhp0idzrD D4mWZmAy200QKLQoj6m2q25+Cq6kde15ar8y7pvZKkm72leNr/YPAx2r6wtXDimhYdVZhHod B2NyjyjeslMTrQ2Cv6/NTGTBdsiw69pmcji/caizhFXZIZc6I5l/1SwKp5KuZLIMvB0vFrLA CuNrCU2N9GNVeBK3zJtGhmx9KhGnw1AxedW0AH/siYySJfknx1x1YRgJV3pAZPyLstD51fo+ jUOKVhk79DCscQcKJmHe8EBc+6EHbETx7AOH+bZV7nCKYEMXTQrIOf2sR72AhrQu1C8HIWou WBbLp1jx9ER6veM7zH4HQQyGG4fIyUZ0Wa9ihx3ekNhoHB
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.83,264,1616457600"; d="scan'208,217";a="731994216"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Jun 2021 19:14:31 +0000
Received: from mail.cisco.com (xbe-aln-004.cisco.com [173.36.7.19]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 15AJEV5T027588 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 10 Jun 2021 19:14:31 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xbe-aln-004.cisco.com (173.36.7.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.792.15; Thu, 10 Jun 2021 14:14:31 -0500
Received: from xfe-rcd-003.cisco.com (173.37.227.251) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Thu, 10 Jun 2021 15:14:29 -0400
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xfe-rcd-003.cisco.com (173.37.227.251) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15 via Frontend Transport; Thu, 10 Jun 2021 14:14:30 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=k7Jvf2m413Wk8nENT4cYmTxK3qWS4QXjgAgxKtrPiGDJ2koog3+6ydwoUDOfZQ1Rz1zBAPVbEYc2XP0YI49KpueVdC817YKd/fLJ+3vdyXNk1Uqz7PYqqBbp+eOfcKZ3iAhb6i+XzF2EZJPva3zixMe119pktZe2nhVf8rV0NUy9f9l+Km3yYmBPs6E+tifSTUOHiRLSmobhUowrJD/G7cviYiPnd4e9Vk8GeGieetBixzA47+OebYTxlfJO2L9EphcD1Tzaya6Isva2ayhj+3Fjl60YsGe3XFeSZfeMXL9cTzitQn8Wbr5Ai4qt9ZF0JQp77U7P/doOPEsDAb2GKA==
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=8j7ivjKUZE0vC7OuEijbDlKQJU+c0uT3U9uYQa0aAds=; b=CWzwmDtwMCmJR9Apeq5qS5Uz0FAoyJ9xT4zvsG0kpD87t3mEjM7o8xqy4BJp1WulZcqXy6dz1So8Etz2tyeZhJ13kBZrR53EfG3h9zpFv7SbTKFVOaEDW1ybexG07kEm7gsSYx6/z9DPW/8jECXnXrf/MQPanhAYuhBV3InuU64lJklyxzjqh0GSlWafnQGY98XOXMazTeAcpHfx3weNGEXPLK1R8lVLcjFzy0Tsx0kUhhff0GzmXX0fUcteZfP5QNjJtmxKQAxKi/e3g6Erru/YGmNrJNgpuKlLunuUD+NA8jMSi838QzyadvNttwP3/RLH5DzoCKX0qf/eauYyqw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8j7ivjKUZE0vC7OuEijbDlKQJU+c0uT3U9uYQa0aAds=; b=P2XUzyW57mb/7V6nzsrijTRYGyYgT90e3L3Z+xO2uyzeOyP4Sf8JrDmXgrIaGm372uiogN4owFBFxQ3PJll2pOi3Dd1/PImYFghW42zq9WWXgX4BSqy7m5apX1MQ8EUuzb8vLbi3cWm1dc3HIES/1uMGsXUhjAN7WCia3Zf8hXU=
Received: from BYAPR11MB2887.namprd11.prod.outlook.com (2603:10b6:a03:89::27) by BYAPR11MB3638.namprd11.prod.outlook.com (2603:10b6:a03:f8::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4219.21; Thu, 10 Jun 2021 19:14:28 +0000
Received: from BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::e98f:cd3e:b6d:6f9d]) by BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::e98f:cd3e:b6d:6f9d%7]) with mapi id 15.20.4195.030; Thu, 10 Jun 2021 19:14:28 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>, Gyan Mishra <hayabusagsm@gmail.com>
CC: "lsr@ietf.org" <lsr@ietf.org>, "chopps@chopps.org" <chopps@chopps.org>, "peng.shaofu@zte.com.cn" <peng.shaofu@zte.com.cn>
Thread-Topic: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"
Thread-Index: AQHXXdRNJDgku+gfMkSZTWt+/4yZOqsNPCaAgAAdPwCAAAGMAA==
Date: Thu, 10 Jun 2021 19:14:28 +0000
Message-ID: <AA3138A8-FD09-4164-8241-F79DF7010041@cisco.com>
References: <202106101417420546260@zte.com.cn> <MW3PR11MB457083C01D78F91D5B9A3AE2C1359@MW3PR11MB4570.namprd11.prod.outlook.com> <CABNhwV2rfcRS_+QQRUT5byVsVMdVQbtheMSX4dAUrreac29q3A@mail.gmail.com> <MW3PR11MB4570A81E56F5BC6194C72C05C1359@MW3PR11MB4570.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB4570A81E56F5BC6194C72C05C1359@MW3PR11MB4570.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.49.21050901
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [136.56.133.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 28c4b007-9031-497d-6a60-08d92c43f826
x-ms-traffictypediagnostic: BYAPR11MB3638:
x-microsoft-antispam-prvs: <BYAPR11MB3638B13B4BAD868EF0722F04C2359@BYAPR11MB3638.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:5516;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: wt7aXu9umw5X52u0ir8OjV6JaS8SEmjtmc/GHKaGwRIGcTgjqAaRi0SG110Q4ygtHMgEcwRHVXFP0vgK/RTAA1cutQ4Bh+PJQqC/Ygur13M1kV3SuuHFydZcjaKsUL+1hXOWoifok2g6I7RTR3HwRiHvjhiuzngDPpAfcd4gMEUiGtWnHVz6XUeQKNUrx1dF8lXd5N1/+EMoy7KKrf4bRlpGIrZSPsM05dipkdjeqVt5CxPKdAKDHMns+N9nqGZ7hE+Q3nbGf76M7LX7J3d15dETwLxCu0LheNVe14du5ei1SJAaCbCnriYpOKdU3BGob1lYnlHEUGSXvTPqhKbw+WohuA+pCbWpL9r4M0exZDRelAtF43M70RgalIBIlRCHg4+4FXTD0Ue9/3ax3iXKyuU8BsxChh+ATsvXVB5LUHljsmBPuT60HMOryoEXj1mKUPYiV8qN5pHZzzR16UOD/JXqoFeQIR1axKjYWElu6xg7sX5RwGGLg4mTgWL+a3Dm09PMKaHm4z0xDLDD6Sk4iRthVZKrb3MLI6yM4kCcgD09uDOvZFBxiUoCgMc/Ut8Ds1KCPf4zEZoDBNSAJo2QO98V1rMEcCGYTzqqxk+apjNIIQGEBBDC91RrQmBGhmhypF9oLCQOZDD6Hk2jddDceonb88dJ4AHsX+GmOULnhcGg3ejXltiHRVXrpuTHluqQrzeu5JQJ2zVkmnUH17r/530V3GxJAN11YXBJ592yd9usJ8ZWjE8rIo/BVQVcwED9gj2YIwYKRonMcISVWEk/DEKW6L+6h1yTMY8puCKCf9ZbyIDMo0Pr1X3D97YRkp+g
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB2887.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(136003)(346002)(376002)(396003)(39860400002)(366004)(2616005)(186003)(64756008)(83380400001)(33656002)(2906002)(66556008)(66946007)(6486002)(5660300002)(54906003)(478600001)(6506007)(26005)(66446008)(66476007)(76116006)(966005)(36756003)(86362001)(4326008)(166002)(122000001)(53546011)(110136005)(71200400001)(6512007)(38100700002)(8936002)(316002)(8676002)(45980500001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: tjxOqAV1GOtQ7a5AqS1PZRA57DyoR+iDin5kWeUXhw+WWKHWaNL9NZyQknrKelVqf/0u152SBky4WN6TPVxhF5lvJIhZ7CHGLGyyhAst1Lf/xit1d44HBa3cMd9keJv121+1FhN47H0ttNaV8JlFXdc78lMD3XIWrMdXajcvdek5/lflEJqazhAZJrqZV0l+reIPAW8vGOh/SG9SMRo36L6AzkNBoELa4RlWUs1pY/O8TjkCL0IjBTXWPbMSWEnKep2YeMmyhT+siX10M4x6ZL4c+7QBv+3rw4/wAge6aKjzVU2DdlsG8sJ4DqJCgQxmKOLqrWbnhumUMZN9SQenEKIctB/Uh56AfqdPEO8mAOz4pPgIq/bv2bM0hNf7lzQLPbZ9C46zP0OMWiTAvK56PPqxM8Njc/Xxi+3fkGux825kjRRktO0wlbBrex0POm2qKqiMuXc0ACWjrdlFHBWUIGbtfaq04xxMu0NAaxt+rzQmerqliZ7z0byiC0r1nkdOzOgzINYfM0kr3dSgOZ8LvHSqz/uOLmEO+lpzZ5qDKNYCdf/QD60HQ1UrQyGFm9W+5i+vCF3+w9jdlqL9ql9zQmVQSSQdEkL0nGqq1sUFDI34XbvNSeh7OwhEdEgM9FgMKCcJq6d6MPg+QXLnHH+K5kq/2lA7+PPS81yXo2WXPZU9NSX/yd7GwLsd4LYhCznaxCkDP3lBFI1xzSwEZX21FtHjSTri6Z29nAyy2fSwICNP7QO5ZLSTm7E5x8c8wFb0uNo+ouZ8ByFVchmmuHaoPzYq67xQn9pLYO6H8eJ10kQ63xfbMnHxs8co+en+zqi6sG29syQ8uxvNzrHIdmETiiASfTCV15xcuV+2MpkfyRBoxxtX8sZt2u2MT1f2Kk4zhSlpJBkLZrA/nrbRNYQs4lCcsdiXinu6TYfrgM2ZSyIv73qaWMQNWPPOCboW9gFNYQxB3Uc7KOBq+KAId8Um9u2nEySBEoHiZjBnfzZXiObNPcwc6Jgq9YFquWGGKKdOHtPXSFqny/4sVF7S0kCIyKyjZ6S8k1ExSo5ODRxGCEvuiWxD55dSkGlhlWZs/XytQ/CdHBRl6XePd/NWjK3p/RKc4rlRlMaiQS7wE13kdaTZJwEtjYbJRzTf/FnHrGWZ3ra5nd+WSP6PSO+nMaKpwKP22zts1BEEnEim3l8TeGtlqUjiuucK0Nk9Umn5qpG19+xjdmLBaDWE2ChdIVIkdaVydZemR6dj2/Hhdr6fyPGGdHZn3+C1EkbjosE/liTdAZm9QvwuvAosGawWZSXIO1jLf1END74Grz1RKGsqCLYLLirRq5ELCo/vLtrEYgrCpchdhHx70ZjbluOxkuD5mQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AA3138A8FD0941648241F79DF7010041ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB2887.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 28c4b007-9031-497d-6a60-08d92c43f826
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jun 2021 19:14:28.5545 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Qk8zdmtoGIQ0eO/4mneX+hznSgProkue7HF5lhQVBrsALaAfFlBPRObRPpJVhS1L
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3638
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.19, xbe-aln-004.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/BtyLqoKW2yorBGMiROBJ0B1XOy8>
Subject: Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"
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: Thu, 10 Jun 2021 19:14:41 -0000

I agree with Ketan.
Thanks,
Acee

From: Lsr <lsr-bounces@ietf.org> on behalf of "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>
Date: Thursday, June 10, 2021 at 11:10 AM
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: "lsr@ietf.org" <lsr@ietf.org>, Christian Hopps <chopps@chopps.org>, "peng.shaofu@zte.com.cn" <peng.shaofu@zte.com.cn>
Subject: Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"

Hi Gyan,

This document does not even “update” the LSR Flex-Algo draft since it is introducing something new and on top. It does not change what’s in the LSR Flex-Algo draft.

This document would be pretty much independent and an optional/add-on element on top of the LSR Flex-Algo solution.

Thanks,
Ketan

From: Gyan Mishra <hayabusagsm@gmail.com>
Sent: 10 June 2021 18:54
To: Ketan Talaulikar (ketant) <ketant@cisco.com>
Cc: chopps@chopps.org; lsr@ietf.org; peng.shaofu@zte.com.cn
Subject: Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"


Hi Ketan

See in-line

Thanks

Gyan

On Thu, Jun 10, 2021 at 4:40 AM Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>> wrote:
One quick clarification on the following:

Does this draft update the SR IGP extensions for SR-MPLS RFC 8665 8666 8667.
[PSF] Yes.
KT> This draft proposes something new (an Algo-specific Adj-SID) and their relevant signalling extensions for the IGPs. It does not change anything in the RFCs referred to above. Hence there is no "updates" consideration here.

    Gyan>This is a confusing point and maybe something the authors can clarify in the text.  So this  draft defines a new Adj-Sid that has an Algo identifier specifically for Flex Algo and if that’s the case I agree it does not update the SR-MPLS IGP extensions, but instead should update the Flex Algo extensions.


Thanks,
Ketan

-----Original Message-----
From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> On Behalf Of peng.shaofu@zte.com.cn<mailto:peng.shaofu@zte.com.cn>
Sent: 10 June 2021 11:48
To: hayabusagsm@gmail.com<mailto:hayabusagsm@gmail.com>
Cc: lsr@ietf.org<mailto:lsr@ietf.org>; chopps@chopps.org<mailto:chopps@chopps.org>
Subject: Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"

Hi Gyan,

Thanks for your support.
Please see inline [PSF]

Regards,
PSF


------------------原始邮件------------------
发件人:GyanMishra
收件人:Christian Hopps;
抄送人:lsr@ietf.org<mailto:lsr@ietf.org>;
日 期 :2021年06月10日 13:05
主 题 :Re: [Lsr] LSR WG Adoption Call for "Algorithm Related IGP-Adjacency SID Advertisement"
_______________________________________________
Lsr mailing list
Lsr@ietf.org<mailto:Lsr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsr


I support WG adoption of this draft.

This draft fills the gap where multiple algorithm identifiers are associated with a link applied to prefix sid and to add parity as now this draft provides Algo association with the adjacency SID as well.  At the end of the introduction is stated that the algorithm identifier should be included as part of the adjacency SID advertisement for SR-MPLS.   What about SRv6?

[PSF] For SRv6, tt was born with this ability, since SRv6 END.X SID can be allocated from an algorithm specific Locator.


Does this draft update the SR IGP extensions for SR-MPLS RFC 8665 8666 8667.

[PSF] Yes.


Also does it update the Flex Algo draft?
https://datatracker.ietf.org/doc/html/draft-ietf-lsr-flex-algo-16

[PSF] No.


In section 5 operations describes how flex Algo plane can now be differentiated on the same  adjacency link with the Algo identifier adjacency sid to Algo plane can now have QOS and link resources characteristics defined which maybe beneficial to TEAS network slicing application as well as used in conjunction with a resource sid for underlay resource provisioning for Enhanced VPN overlay.

[PSF] Agree. Flex-algo can be used alone as a network slicing mechanism for some limited scenarios, and adj-sid per algo provide a basis for this purpose. However this is outside the scope of this document, so it is not described in detailed.


Kind Regards

Gyan

On Wed, May 26, 2021 at 5:00 PM Christian Hopps <chopps@chopps.org<mailto:chopps@chopps.org>> wrote:

Hi Folks,

This begins a 2 week WG Adoption Call for the following draft:

https://datatracker.ietf.org/doc/draft-peng-lsr-algorithm-related-adjacency-sid/

Please indicate your support or objections by June 9th, 2021

Authors, please respond to the list indicating whether you are aware of any IPR that applies to this draft.

Thanks,
Acee and Chris.

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

--

Gyan Mishra
Network Solutions Architect
Email gyan.s.mishra@verizon.com<mailto:gyan.s.mishra@verizon.com>
M 301 502-1347
--

[Image removed by sender.]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mishra@verizon.com<mailto:gyan.s.mishra@verizon.com>

M 301 502-1347