Re: [spring] Proposed policy on reporting implementation and interoperability
Ketan Talaulikar <ketant.ietf@gmail.com> Fri, 19 August 2022 15:56 UTC
Return-Path: <ketant.ietf@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1198EC15948A for <spring@ietfa.amsl.com>; Fri, 19 Aug 2022 08:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 umT-7-79Q1JJ for <spring@ietfa.amsl.com>; Fri, 19 Aug 2022 08:56:56 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (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 82FDAC1527AB for <spring@ietf.org>; Fri, 19 Aug 2022 08:56:56 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id a22so6175551edj.5 for <spring@ietf.org>; Fri, 19 Aug 2022 08:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=Q+uSMDyCwAXkw24BqNz9lNCwaGs19g9m4WCZZNhMh3E=; b=C6ogZv4hIFFV1b+tf64YmlR2cV+dOpvDiGVO7Gdhe+CnBuq2bio6+J2twk6Y8xAdCJ MzGwi/xdqmsAeDogSTzSnwOd9QAmglx32gfpmWfv3ABk0qQl6kUlAc3G7cSFLUWNONrW OopgEsZENqZCih8rcztUjq44qvoWD/HQwwe1KLv8Kd/NLqjz9c8EPgjPG+lUBO21YK3h RP2ByURJwvcIATOGr7sxuKdPjz86Z0uNnbZa/u2W4TUcwHfIUoKuVdLjlA9iKZC+1I7T WyXIXsQ7KPsRa2+lJ04Ukkjjym9+xA5tcFtsm8qJS47ANRvXI7jxG9Xe9v0dTGSwJ1x+ xEiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=Q+uSMDyCwAXkw24BqNz9lNCwaGs19g9m4WCZZNhMh3E=; b=bNZkNvriTy32C0j0fopRVB4ZBRzVx/RuLmln6F1n6NZeh6MwvoXcq+RgqzfOkkvola FB8db8x4A3tsRx8qleBVX2vkW+WN91qG+ZL7JYZVzgiNQRikhXXnvMbJJ6SSjAljKiM6 MyhETk/gzUaOpQMosKmDgMPpHm7WBqXALt8awOPE57yrp7Srr3Jwn+ngWgLFoY1Z7E6T GJ1wPc/euT3x2nCQ5gcPK7z4qvyPpXFOtvkcxP42IMo++ngmH+5xijXo1A//HRZ+X+kr 9hZmwFmK1PKuM6VaInz3jd8WtZwOzIdkhe8p+aDy/OUq7te1MmptyPoeFNBNesE/O47W Kbgg==
X-Gm-Message-State: ACgBeo23z1aCvhnKz8vXQMGBL/g7RLbyw0I8fBt4CQpM8ktkD+D7GrWa qljokCB15g0WeBgfIwg7mY07nsaDWRg9YcGjd7s=
X-Google-Smtp-Source: AA6agR4qvY2VFImoA8MPuQTWu+3DImCpqLZOMgR3B9j7/cwxphCbldOn2SfO+3hQYqM2ZiqS0HXKFqYPjQ6W7Rln+mE=
X-Received: by 2002:a05:6402:5002:b0:444:26fd:d341 with SMTP id p2-20020a056402500200b0044426fdd341mr6746146eda.351.1660924614651; Fri, 19 Aug 2022 08:56:54 -0700 (PDT)
MIME-Version: 1.0
References: <9c7ac280-c1f7-956c-cdbb-2b0745aaf2fa@joelhalpern.com> <CAH6gdPzYmxoVbOaAp3waUWFOCJPVoW1R3iN75SoqimyrkY769w@mail.gmail.com> <fe51b706-dac2-1796-4972-9a561c3bd17a@joelhalpern.com> <CAOj+MMEmXRcESZV5AjJOrgFCEF821CPB0ag7rx3OYz4HSp2gbg@mail.gmail.com> <b17cd0b6-0ac4-e41f-854f-0914c7ac53f7@joelhalpern.com> <CAOj+MMFcaOzUe0CEOjsBr4=S8a6Ku=0qHXvaGw0w+hYZY84A2A@mail.gmail.com> <CAH6gdPwkAsWKFdD47=hrbnuHpAP8Ay_szWEc1AuLsSggnsg5cA@mail.gmail.com> <CAOj+MMHWbamLg_t6fcC-xYY3CUQmEK=ZW_aDBuc1nYh_kATpRw@mail.gmail.com>
In-Reply-To: <CAOj+MMHWbamLg_t6fcC-xYY3CUQmEK=ZW_aDBuc1nYh_kATpRw@mail.gmail.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Fri, 19 Aug 2022 21:26:43 +0530
Message-ID: <CAH6gdPxosfYDxj2hMAMggemPTN+LqFA2giK27T83E-WnUa5F1A@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Joel Halpern <jmh@joelhalpern.com>, SPRING WG <spring@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a7b1ef05e69a25ec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/bWAMRJSnEkQ8bcmXN0Y7aT7nbNA>
Subject: Re: [spring] Proposed policy on reporting implementation and interoperability
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2022 15:56:57 -0000
Hi Robert, Indeed, writing implementation reports for architecture documents (which is what we mostly do in SPRING WG) is more challenging than protocol specs. This was my point as well. For an operator, considering a solution deployment, perhaps the implementation report for the protocol spec is as important (if not more) than the architecture. Coming to your question, we can consider RFC8667 which has several TLVs/sub-TLVs for different segment-type advertisements. For example, features like SRMS or Mirror SID are optional, but should one implement their support, they would need to deal with some MUST clauses specific to those advertisements and their processing. Thanks, Ketan On Fri, Aug 19, 2022 at 9:18 PM Robert Raszuk <robert@raszuk.net> wrote: > Thx Ketan. > > Yes indeed but this is an architecture document ... In such type of > documents it is hard to imagine an implementation report. You implement > protocol specification not an architecture. > > I was more curious how many protocol extension RFCs say from IDR or LSR > WGs have such "issue". > > Thx, > R. > > On Fri, Aug 19, 2022 at 5:43 PM Ketan Talaulikar <ketant.ietf@gmail.com> > wrote: > >> Hi Robert, >> >> Let us consider RFC8402 which has a whole bunch of MUST clauses. An >> implementation may choose not to support IGP Anycast Segment. The spec does >> not say that any of the Segments are mandatory for SR. However, there are >> some MUST clauses to follow should implementation support it. >> >> I hope that clarifies. >> >> Thanks, >> Ketan >> >> >> On Fri, Aug 19, 2022 at 9:01 PM Robert Raszuk <robert@raszuk.net> wrote: >> >>> Hi Joel, >>> >>> Would you mind providing a few such examples of reality in the published >>> standard track RFCs coming via Routing Area ? >>> >>> Many thx, >>> Robert >>> >>> >>> >>> On Fri, Aug 19, 2022 at 5:23 PM Joel Halpern <jmh@joelhalpern.com> >>> wrote: >>> >>>> While what you propose may be cleaner, what Ketan asked about is a >>>> common practice. So it seems useful to recognize that reality. >>>> >>>> Yours, >>>> >>>> Joel >>>> On 8/19/2022 10:58 AM, Robert Raszuk wrote: >>>> >>>> Joel, >>>> >>>>> I would be interested in hearing from the WG on this. My expectations >>>>> is that if someone says they implement optional feature X, and X has MUSTs >>>>> conditioned on it, then they have to explain whether they comply with those >>>>> MUSTs. >>>>> >>>> When I look at BCP-14 or RFC2119 I do not see any distinction for >>>> categorizing MUSTs into main MUSTs or MUSTs under optional features. >>>> >>>> >>>> *1. MUST This word, or the terms "REQUIRED" or "SHALL", mean that the >>>> definition is an absolute requirement of the specification.* >>>> >>>> While technically sound I am not even sure if any optional feature can >>>> have any mandatory MUSTs which apply only when someone chooses to >>>> implement such a feature. >>>> >>>> In such cases IMO it would be much cleaner to just separate those >>>> features into separate documents and still MUST be a top level normative >>>> clause. >>>> >>>> Many thx, >>>> R. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>>
- [spring] Proposed policy on reporting implementat… Joel Halpern
- Re: [spring] Proposed policy on reporting impleme… Dhruv Dhody
- Re: [spring] Proposed policy on reporting impleme… Joel Halpern
- Re: [spring] Proposed policy on reporting impleme… Eric Vyncke (evyncke)
- Re: [spring] Proposed policy on reporting impleme… Joel Halpern
- Re: [spring] Proposed policy on reporting impleme… Tony Przygienda
- Re: [spring] Proposed policy on reporting impleme… Acee Lindem (acee)
- Re: [spring] Proposed policy on reporting impleme… Joel Halpern
- Re: [spring] Proposed policy on reporting impleme… Robert Raszuk
- Re: [spring] Proposed policy on reporting impleme… Joel Halpern
- Re: [spring] Proposed policy on reporting impleme… Robert Raszuk
- Re: [spring] Proposed policy on reporting impleme… Joel Halpern
- Re: [spring] Proposed policy on reporting impleme… Jeff Tantsura
- Re: [spring] Proposed policy on reporting impleme… Robert Raszuk
- Re: [spring] Proposed policy on reporting impleme… Joel Halpern
- Re: [spring] Proposed policy on reporting impleme… Robert Raszuk
- Re: [spring] Proposed policy on reporting impleme… Gyan Mishra
- Re: [spring] Proposed policy on reporting impleme… Ketan Talaulikar
- Re: [spring] Proposed policy on reporting impleme… Joel Halpern
- Re: [spring] Proposed policy on reporting impleme… Robert Raszuk
- Re: [spring] Proposed policy on reporting impleme… Joel Halpern
- Re: [spring] Proposed policy on reporting impleme… Robert Raszuk
- Re: [spring] Proposed policy on reporting impleme… Ketan Talaulikar
- Re: [spring] Proposed policy on reporting impleme… Robert Raszuk
- Re: [spring] Proposed policy on reporting impleme… Ketan Talaulikar
- Re: [spring] Proposed policy on reporting impleme… Robert Raszuk
- Re: [spring] Proposed policy on reporting impleme… Adrian Farrel
- Re: [spring] Proposed policy on reporting impleme… Robert Raszuk
- Re: [spring] Proposed policy on reporting impleme… Chengli (Cheng Li)
- Re: [spring] Proposed policy on reporting impleme… Boris Hassanov
- Re: [spring] Proposed policy on reporting impleme… Suresh Krishnan
- Re: [spring] Proposed policy on reporting impleme… Joel Halpern