Re: [Idr] Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30)
Stefano Previdi IETF <sprevidi4ietf@gmail.com> Thu, 30 June 2022 16:05 UTC
Return-Path: <sprevidi4ietf@gmail.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 10DE5C15C7DE for <idr@ietfa.amsl.com>; Thu, 30 Jun 2022 09:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9NdvgUdvfe7X for <idr@ietfa.amsl.com>; Thu, 30 Jun 2022 09:05:05 -0700 (PDT)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76CE9C14F72F for <idr@ietf.org>; Thu, 30 Jun 2022 09:05:05 -0700 (PDT)
Received: by mail-ej1-x636.google.com with SMTP id fw3so12271553ejc.10 for <idr@ietf.org>; Thu, 30 Jun 2022 09:05:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=DMzktj+d6pZOEq3SieXOjXcLVDW949Ev/+JpdmU0wTE=; b=D9vyJ5dPwSXEbKHvl8+oXWxwBVw9u12OrFnbuRC/dgok/GZeuZ7gFwu+2a9d3TI4WA dVeQ6oKxHaoWrqYHGjPB+iqQE9LrAh9KfS31imdvQCIqjskSt01JN0VFQCL8xz9LTQ9P Z5SWudjHtAkmoGWgRCMmRgNXRFImsX6EgPQacSVpPWVIOab4vT5OHrqFCBOA7uA7cUCH bjireV2HJDxkohNHeigBoTJZNjNB1YMHTQijQ4qdI7gLfZmQfju/unE94PLdbdg9K/U9 CE7a/0JNvdPLApEAKBmJUMsXnAL+3W9O7ymoyCQVHikROxLDXKAPTI4tWoURYlGcxJoR VIYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=DMzktj+d6pZOEq3SieXOjXcLVDW949Ev/+JpdmU0wTE=; b=sE/LuchIVyKudKB/fXUiWdkFvz/AaYuAtGoN2Hg4TA1/4neCwbM4wJutgzeS0S7fEG vO0gclTwaLRKrKKUumUFnv5tk/KcPWbm+6BlCO2K9HLj1k7ReWOsn6XxkFif0zWI3iqf aPQfYm+V8HJ/TeJNdWOV3mWGe3LdHhZAG1TFIeMVUBVPUOKcbWAdbUTn15cMmR7QgoiU gLJEVOBNAjBDWjkmyeQOJe1LynPUN3eslyFKkKnN4yF9HROCp9CfvwVDLCf7ElUyh+4B Q/tXkmylK/j1tmIPzMWltrs/BeAEFajhdMl1SN6bntEuZTqllHzdTsGXXU/ikfyImcev Ci9Q==
X-Gm-Message-State: AJIora8uuOrFY0ZXYnY+5Ii5Mnx6EvFHP4K3JNu199Aocg1yF02A+wjU uoz2GVZ0GCi3YV2AZXDdRXI=
X-Google-Smtp-Source: AGRyM1vzW/bnpIUnpgOqZeJWPjlooZ3ujwdnvqmMXw8Mc7T3QKRAl5Lek8RJpuIvfzsr+xyZfC5ArA==
X-Received: by 2002:a17:906:4fd4:b0:722:f223:8d86 with SMTP id i20-20020a1709064fd400b00722f2238d86mr9658990ejw.558.1656605103495; Thu, 30 Jun 2022 09:05:03 -0700 (PDT)
Received: from pc.home (host-79-42-236-11.retail.telecomitalia.it. [79.42.236.11]) by smtp.gmail.com with ESMTPSA id co6-20020a0564020c0600b0042dd022787esm13504974edb.6.2022.06.30.09.05.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Jun 2022 09:05:02 -0700 (PDT)
From: Stefano Previdi IETF <sprevidi4ietf@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
Date: Thu, 30 Jun 2022 18:05:01 +0200
References: <64C0FBC9-1D78-4098-AF8B-75571D2B6393@cisco.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
In-Reply-To: <64C0FBC9-1D78-4098-AF8B-75571D2B6393@cisco.com>
Message-Id: <18EB54F7-FE4D-46F6-8EEE-FA88FD6C7EF4@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/w0qEiBjPeIR85i6jPSvgeHDD_HI>
Subject: Re: [Idr] Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30)
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: Thu, 30 Jun 2022 16:05:07 -0000
Hi, as co-author, I support the publication of this document. Thanks. s. > On Jun 21, 2022, at 11:14 PM, Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org> wrote: > > Hi Sue, > I support publication. For complicated features such as this SR TE Policy, we rarely have implementations where every line of the specification is supported. It would be a travesty to delay publication for this reason. > Thanks, > Acee > > From: Idr <idr-bounces@ietf.org> on behalf of Susan Hares <shares@ndzh.com> > Date: Friday, June 17, 2022 at 9:15 AM > To: IDR List <idr@ietf.org> > Subject: [Idr] Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30) > > > 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). > > 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 > > 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 > https://www.ietf.org/mailman/listinfo/idr
- [Idr] Call for publication of draft-ietf-idr-segm… Susan Hares
- Re: [Idr] Call for publication of draft-ietf-idr-… Acee Lindem (acee)
- [Idr] FW: Call for publication of draft-ietf-idr-… Susan Hares
- Re: [Idr] Call for publication of draft-ietf-idr-… Stefano Previdi IETF
- Re: [Idr] Call for publication of draft-ietf-idr-… Ketan Talaulikar
- Re: [Idr] [bess] FW: Call for publication of draf… Zafar Ali (zali)
- Re: [Idr] Call for publication of draft-ietf-idr-… Boris Hassanov
- Re: [Idr] Call for publication of draft-ietf-idr-… Susan Hares
- Re: [Idr] Call for publication of draft-ietf-idr-… Susan Hares
- Re: [Idr] Call for publication of draft-ietf-idr-… Boris Hassanov
- Re: [Idr] Call for publication of draft-ietf-idr-… Susan Hares
- Re: [Idr] Call for publication of draft-ietf-idr-… Ketan Talaulikar