Re: [Idr] Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30) - consensus reached

Susan Hares <shares@ndzh.com> Mon, 04 July 2022 23:26 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 266FEC14F74B for <idr@ietfa.amsl.com>; Mon, 4 Jul 2022 16:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e-ji773wtlcS for <idr@ietfa.amsl.com>; Mon, 4 Jul 2022 16:26:45 -0700 (PDT)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2059.outbound.protection.outlook.com [40.107.244.59]) (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 CD026C14F6EB for <idr@ietf.org>; Mon, 4 Jul 2022 16:26:45 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QQut2cDTtqlAnrRcGNYdG19kznzjE/fQz9mw31oAEv7b/vWMvYxlZBit08OJ/hMvfBhUyOYbec8SfGdgUTAfcFH9AJs2UyrkUidN6wALEw+4WjPczCde5Pw9M0P0wzMRs2xYGXJKQ/xZU4nGXOSl1zcc/uwRGdnOFStB9sp9/DNyxjxXR8BJfLRpSMeTLJZoAilxTPtg8BedpAlHmcRXsNWClhj3pi4WqvH7wVzAF/jJx/as8eCqc3kQ6tBhTV0ITx/owMIkVW3E/q4wHUkSU+zVdvcS3iLGIYLZuIFAhDxNKAUpdxkgxaqSq5DmhmYbh7YiyO53BUONDu0Gn8IaVA==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Ze58jB8NGPg5ABDlkuSLg3hixB8zgk9uaVa2rlQI4N4=; b=JuAz6KxrhuYq2eHm4KWNRf98jI7o3UsXonA9PHszkJWYyLuVyjy9Gm/Ce+iJL/V2n2/fIeVyODaX6nkZUAf8tWlLbb9pfyW0xra+DLvo5zN7/CKF+Bi774FoMLW0ry1j6SSfHten1efOYWGQxaZcLN+u2yZtmu4Stz3TDkETbsq53VG3XyK7iIP4BZhCqsC9lZVKiw+fg3wdm1L62qOmdvAbmFYAT7HqxvKtmEy7LqE14CBcBhPYON+WtGHry0cG+5WZG4ZT9mspGPZ2WXqTAfYTmbSsOrGDXOTe0iqRgAGwWpl/H9CBellUN0H4jh1GJoL5kSel1Bup0CxXRPbkdw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=fail (sender ip is 13.59.96.180) smtp.rcpttodomain=ietf.org smtp.mailfrom=ndzh.com; dmarc=none action=none header.from=ndzh.com; dkim=none (message not signed); arc=none
Received: from CO2PR06CA0066.namprd06.prod.outlook.com (2603:10b6:104:3::24) by CO1PR08MB7047.namprd08.prod.outlook.com (2603:10b6:303:f2::5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5395.14; Mon, 4 Jul 2022 23:26:42 +0000
Received: from MW2NAM12FT013.eop-nam12.prod.protection.outlook.com (2603:10b6:104:3:cafe::c3) by CO2PR06CA0066.outlook.office365.com (2603:10b6:104:3::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5395.14 via Frontend Transport; Mon, 4 Jul 2022 23:26:42 +0000
X-MS-Exchange-Authentication-Results: spf=fail (sender IP is 13.59.96.180) smtp.mailfrom=ndzh.com; dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ndzh.com;
Received-SPF: Fail (protection.outlook.com: domain of ndzh.com does not designate 13.59.96.180 as permitted sender) receiver=protection.outlook.com; client-ip=13.59.96.180; helo=obx.inkyphishfence.com;
Received: from obx.inkyphishfence.com (13.59.96.180) by MW2NAM12FT013.mail.protection.outlook.com (10.13.180.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5417.8 via Frontend Transport; Mon, 4 Jul 2022 23:26:41 +0000
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12lp2040.outbound.protection.outlook.com [104.47.66.40]) by obx-inbound.inkyphishfence.com (Postfix) with ESMTPS id DEAA917D44D for <idr@ietf.org>; Mon, 4 Jul 2022 23:26:39 +0000 (UTC)
Received: from BYAPR08MB4872.namprd08.prod.outlook.com (2603:10b6:a03:70::17) by DM6PR08MB5609.namprd08.prod.outlook.com (2603:10b6:5:109::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5395.15; Mon, 4 Jul 2022 23:26:36 +0000
Received: from BYAPR08MB4872.namprd08.prod.outlook.com ([fe80::de0:4e0d:2268:73c3]) by BYAPR08MB4872.namprd08.prod.outlook.com ([fe80::de0:4e0d:2268:73c3%5]) with mapi id 15.20.5395.020; Mon, 4 Jul 2022 23:26:36 +0000
From: Susan Hares <shares@ndzh.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30) - consensus reached
Thread-Index: AQHYj/2BnYBVsHuzokyFeIkWOwVKTQ==
Date: Mon, 04 Jul 2022 23:26:36 +0000
Message-ID: <BYAPR08MB48720F9F1085F6D878E8E857B3BE9@BYAPR08MB4872.namprd08.prod.outlook.com>
References: <DM6PR08MB4873C34100BDEEB820E92C46B3AF9@DM6PR08MB4873.namprd08.prod.outlook.com> <CAH6gdPyi_gSw551GBz=DJ8OezihmdnhQ+x0im_SCXG2PQpT6HA@mail.gmail.com>
In-Reply-To: <CAH6gdPyi_gSw551GBz=DJ8OezihmdnhQ+x0im_SCXG2PQpT6HA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-MS-Office365-Filtering-Correlation-Id: deedc778-6ea7-4e96-f785-08da5e14a6f2
x-ms-traffictypediagnostic: DM6PR08MB5609:EE_|MW2NAM12FT013:EE_|CO1PR08MB7047:EE_
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: f8AY9ln5AKz2KRhgzY2Ug3QD+BJvhgQ38Nf7G1o5yiAWKhB+jqUjJIaf33pIVlasw0H0i/rzusCS6+U2HFI83cQgbXQqeD4OX6dobN3e/ybZEK9MvW1EiIH/JmGfoRn9qLP7itE0q6KM26ovhODbXTiCjSeoy9w8BoPtUp/WF9nlarsf4uAc/AypEGvxhAIyQRlXZCyhqTT6Fr5o30254JzdCbEEag2S7th9oV3c2WFnCAZIk9R2k+2l2fh13vKnJUq755qOkSQa2zT0zOzMoynUefPbetgz27Q+JhLRAKNmoexZaSFJYbUUa/cyc56YM7JSuU2eiond+W1pGq1953BmYWtJzVKDQyK1XPgk4y3xO/ndKsVLRbxlSdwTfSKHPGKHUDo14iQ9gwWLjpAh5QvbKIG7A7zcG2SQWPcUyfVEg/QI55AN1bevFF0s8trzTsfBo/wgh+CjuqINgoR89OdXw94NMucbjp02TRMpKJX+qZ6nVksYRZX5Pa1xJ1/S4YAdCbRxWsqmKjjT20VAy75vjvRTeiTHILSyDP+m5MUVJmkEsnnpjQZJD/6LJn0XZ895hreU26wrjJ2CpHkdqchLazkZkHYoYyqcTP5YrrNPRQjQt4lEpgZQc2Yr4u+iJqbbmNRA+cDf/DxnYlj0iGdXS5Q/mAgA8GL1d7780rjUDWvNKozHzsJEhSGI71sycEx2xLaWx69RGRTPrwHaPAZJO0POEnFICWlEipHIPLXnk8nNs7n3kwDB8mYECIonB9W90icCJOaNPJU0xoR6Py5JJZtkIZtr20G7s3HuyU88iXkJA7a19jbDTzP+R/71ga6fBBfF/kx4+MtK1skN4A5r7E6/DwoDKRXjKqSaToERPcW+G4Kes8lZGrZSxsDV
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR08MB4872.namprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230016)(366004)(136003)(396003)(376002)(346002)(39830400003)(53546011)(6506007)(66446008)(8676002)(166002)(76116006)(66946007)(7696005)(9686003)(26005)(41300700001)(71200400001)(6916009)(64756008)(966005)(4743002)(66556008)(316002)(66476007)(86362001)(38100700002)(186003)(122000001)(38070700005)(2906002)(478600001)(55016003)(52536014)(8936002)(5660300002)(83380400001)(33656002); DIR:OUT; SFP:1101;
Content-Type: multipart/alternative; boundary="_000_BYAPR08MB48720F9F1085F6D878E8E857B3BE9BYAPR08MB4872namp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR08MB5609
X-Inky-Outbound-Processed: True
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: MW2NAM12FT013.eop-nam12.prod.protection.outlook.com
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id-Prvs: 52e22897-011a-484d-6084-08da5e14a392
X-IPW-GroupMember: False
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: XWkTUUrLxMIfUo55BWWOnmIwj2VDNYlBfqIkTmX/NHqdcBs8POXawVRq3ELjm2/A1QtmeIw9iMXb7g83rM/x0V7GZ3eCBVISYjf3jWe69v67VvD+RTxHKQ0R+L2b0OXV72CCU7i0l0QvuxYlX/nQCRqlykUcTyrzZcD4wvY7qvidTuweM1i7PaRWzHLZntlhCClu1AvXQ9tb+HX8P8S6KR9Jq/5lDVoLHoQhf7lN3hDiG7QsGimbea/ZZfW7Sxyiq4sozJbzVIlQt+j3N5F6ciWImpjvE8Z7gI2wYNjl4GsJmD3IILYd2uQGCUkB/ecPgnJEK3M9jeoR+XtXJFu0wsgX9F5ptXFju34sdNJB7C7Bpa1iFyBFFCCjiWufEXligTjLpf3pbZY41mkuuwRwDDl39ZmJJwyA5x001poF/w6RP/zl6kDTxWIlTDkHi6Co7iGRNkygB2cvkceI82oWH6hBPQsqBvUYyY+Z44HtmOv8sikwvErAmp1yRmAeUu5NlC5TEiso6mRXynyxkH9puOJm7qcBU+luo3y8jmM6WD3kVzypvgrqn5bRt93+uTlCt2jlpy6IODx9XTq48GhtlhFbQPDDTJRuyuicUkudntafig/ayw4NXrmJFM1po0Ophq9i+XP1TsDh/+zV+Ixdk9Mx/W+c2fsTpXM7XG50H9cyq/OgLkwmXLb1OxqVXKr6wX1wSZ/92aJoqN2u5+CQFpAL/R3bnYPv3XQQP11HlbEYZVfNVo6kL3nRJRpVX3H/C3xJoVL5Rj5L1/f6OrY5SbAAuNNWB8huqksm2H0XRhiz8DDSbrokLHG/+76sQ0xzcaKml6DEfllziJCOzTBgKt/7z3eyF2kKwSF+EK/rEHo=
X-Forefront-Antispam-Report: CIP:13.59.96.180; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:obx.inkyphishfence.com; PTR:obx-outbound.inkyphishfence.com; CAT:NONE; SFS:(13230016)(136003)(376002)(396003)(39830400003)(346002)(36840700001)(46966006)(8936002)(52536014)(966005)(478600001)(53546011)(9686003)(6506007)(5660300002)(356005)(36860700001)(2906002)(41300700001)(7696005)(33964004)(166002)(4743002)(33656002)(7636003)(86362001)(26005)(45080400002)(55016003)(47076005)(8676002)(336012)(186003)(83380400001)(6916009)(70586007)(70206006)(40480700001)(316002)(82310400005); DIR:OUT; SFP:1101;
X-OriginatorOrg: ndzh.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Jul 2022 23:26:41.7769 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: deedc778-6ea7-4e96-f785-08da5e14a6f2
X-MS-Exchange-CrossTenant-Id: d6c573f1-34ce-4e5a-8411-94cc752db3e5
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=d6c573f1-34ce-4e5a-8411-94cc752db3e5; Ip=[13.59.96.180]; Helo=[obx.inkyphishfence.com]
X-MS-Exchange-CrossTenant-AuthSource: MW2NAM12FT013.eop-nam12.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR08MB7047
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/xjeZ5KrB0x0utRaWl3TQLSgmt_I>
Subject: Re: [Idr] Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30) - consensus reached
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2022 23:26:50 -0000

Ketan and WG:

The consensus of the WG is that draft-ietf-idr-segment-routing-te-policy-18.txt should be published with its current content.

I will forward this document to the IESG.

Cheers, Sue

From: Ketan Talaulikar <ketant.ietf@gmail.com>
Sent: Friday, July 1, 2022 10:06 AM
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf.org
Subject: Re: [Idr] Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30)

Hi Sue,I believe there is support for this draft in open-source GoBGP: https://github.com/osrg/gobgp/blob/master/docs/sources/lib-srpolicy.md I am not aware of the testing (interoperability and any ot
External (ketant.ietf@gmail.com<mailto:ketant.ietf@gmail.com>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tLzE3OTIwNmY0ODFhZjAwNzRjYWI4NDI3MGU1YTFmOTgyLzE2NTY2ODQzODcuNjM=#key=8e639b702b331afd9f5a7f8ebb174721>  FAQ<https://www.inky.com/banner-faq>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>

Hi Sue,

I believe there is support for this draft in open-source GoBGP: https://github.com/osrg/gobgp/blob/master/docs/sources/lib-srpolicy.md<https://shared.outlook.inky.com/link?domain=github.com&t=h.eJxFzEsOgyAUQNGtNIxbH_gBdORWABGJIIaHg7bp3hs66fTe5LzJlQOZbmQr5cQJwPmyXboxKULC7MAl7U7QIWmICovNsCSDgOnKxiIErx-YzxS8eTZxIfcb2St32JKyY3SQfGQt4KayxflYXtuPZmJsKV97ydRKqeiN0rJvBbWDYusoW2B84Fz2nRQN76pqq7rboo7SeFvW2UXlQ8XqXer9l88X46RDcw.MEUCIDK1kNfSgaq6yyFseRQ4epRSdJZTnJXUqgx20qYPWVRjAiEAqsHeZXrLI3RIuCCJk1WCsPZ0AEosRcOaIYVxfzrpNYc>

I am not aware of the testing (interoperability and any other) done with GoBGP though. A very quick glance at the code seems to suggest a degree of support for some of the TLVs/Sub-TLVs that you refer to in your email. Perhaps someone working on or using GoBGP can clarify.

As authors, we have tried to include the necessary extensions to align with the base SPRING WG specification draft-ietf-spring-segment-routing-policy. I believe support for specific features (i.e., TLVs/Sub-TLVs) gets implemented as required by operators and/or deployment solutions.

I support the publication of this document.

Thanks,
Ketan


On Fri, Jun 17, 2022 at 6:45 PM Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:

IDR:

This is a 2 week call for approval for publication of
draft-ietf-idr-segment-routing-te-policy-18
(https://datatracker.ietf.org/doc/html/draft-ietf-idr-segment-routing-te-policy-18<https://shared.outlook.inky.com/link?domain=datatracker.ietf.org&t=h.eJxFzksOgyAUheGtGMZFwAdiR27lFi5KVGjwOmib7r2lk07_k3w5L3bmjV0rthDdj6sQDggog10x1wHJ1ynPwiUrFto34TJ44qXz4DI_cN4xEs_ppBBnTsjvaQv2wZVhl4qtRY5IX0PJ3uhRNeJYIOMxRfdcapt2oYaxkdp3RoGXcugs3EzXDBJ7UH40jVC619p0rRlq3RYVi7oiQaTfxWneIWwFK6sr67-8PyCIRwo.MEQCIADRLd0XQ8JT0nG8aRLZod-wBAP_TqtR1AAgCbMfYVOKAiA0DhF_VkheZhvvCOyeG63gp7CaxbDZMY0UiApAEMqENA>).

This draft has past WG LC, and it has been implemented by five separate commercial vendors.
(I  do not have any implementation reports from open-source vendors.)

According to the implementation report, not all
features have been implemented.
https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-segment-routing-te-policy%20implementations%20<https://shared.outlook.inky.com/link?domain=trac.ietf.org&t=h.eJxFjs1ugzAQBl8lstRbjX8CxuSUV9nCGlaAjeyNqqTquxfn0uPOSPPtj3jkTdwuYmE-yk0pzjA2hByalOf3pWjK6ptWUlOGwLJKeTJZcN4xsszpwRRnySiPtNH4_LCa9mPDaoEpxXIS8XkRa12KyGfa6M67wVhVFshY7nF6Lc2YdmX6wWoXWm8gaN23I3z51vYaOzBh8FYZ1znn26vvG3etVazVFRkivz-_zzvQVmPVTtX-k98_aKFM4A.MEUCIDPNQRh5jGwEQvZmMj5OP1t02gVcVkW48cdQAteD3f-jAiEAiZLi2iddp0h4rEVsJWGbDqwdRh6o9dCT03x0EIcJOxc>

At this point, it appears we do not have 2 implementations
Supporting the following TLV codes:

-          ENLP sub-TLV (code 14)

-          Priority sub-TLV (code 15)

-          SRv6 Binding SID (code 20)

-          Policy Candidate Path Name sub-TLV (code 129), and

-          Policy Name Sub-TLV (code 130).


And only segment types A and B out of types A-K have been implemented.

Should the IDR WG:
a) publish this draft as is,
b) put it in a “awaiting implementations” hold until more features are implemented,
c) remove unimplemented features and publish?

If you are an implemented (open-source or commercial), please
Update your implementation status on the implementation page
Or send me a note regarding your implementation.

Cheers, Sue


_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr<https://shared.outlook.inky.com/link?domain=www.ietf.org&t=h.eJxFjk0OgyAQha_SsG4YQAR05VWmCkpUbIDGpE3v3k433b6f770Xe-SN9Re21HovPcB5njz6GviRZ9gxbjsm2GKpMYUD4pTZ9cJWaiRfvxkpWmc6qaAsmH0Z0vRc-HjsIG2nhAnaSQxCWD3izWllhW9Rhs4pkKY1xunGWW4aonqirr5iqr8Lw0z7BCN3IvevvD9pTDiE.MEQCIFAXOD18iMdQh_E9shwCDyG6v0UOpcD8A7vb0K-M2bxDAiBbiaRnHH9yA69B41gwAWIPRX0n8RZVaWQ2UxS_SpkRWQ>