Re: [bess] [Editorial Errata Reported] RFC9252 (7652)

Ketan Talaulikar <ketant.ietf@gmail.com> Mon, 12 February 2024 14:10 UTC

Return-Path: <ketant.ietf@gmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBB52C151527; Mon, 12 Feb 2024 06:10:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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_BLOCKED=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 UmUiq9O4TlN3; Mon, 12 Feb 2024 06:10:19 -0800 (PST)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 98C7BC14F6B6; Mon, 12 Feb 2024 06:10:19 -0800 (PST)
Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-5611e54a92dso3990592a12.2; Mon, 12 Feb 2024 06:10:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707747018; x=1708351818; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=bqYVjYOa7YJ1FBoD6wMdWut4tuJ3xfzt9JtgSGxp73w=; b=C7eKLmjcABkF6umnJAQxvb66VPT6h2JWUXrxL8AoL4Swa5J1RVCIFsIr511KmnuHHd oHjiw+yqPuqHFjo7qavGQzO1Mm4gSV1QzuuAb+9HiCKBwcGR5d78og4cqXD5oxd1Qj5U CSopseKOoDHLXfToiZh6X+e17htx7lwzRkaZOqegYN9Vm5tjdWlkKWMaiCGtSOuhVTJw px9mLjuLeiZ/gu53JMeU/Hy8vZJf41Pki2U1Qnk9FABPOLodmiGp8vOQFnjv5PVumq+b gym18cW008kA/8qz2l42Pzl1qtSfQ9X1bNIfdNL76B9Okx+jHmyuoQPX52wvHf1cCXMZ fHZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707747018; x=1708351818; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=bqYVjYOa7YJ1FBoD6wMdWut4tuJ3xfzt9JtgSGxp73w=; b=olgnIWwTF1MYGgE4QlLQlYw6+0lg3ajfau0/0O/e4KcU7gvooMuMis66b0pdloPNg5 HHdw9luonVqokN507tVF+T97mnq+G04WkzsOr6UZXDOB1DeW/IsNE0fh0hdkvr2Z36Xi pfEk9jXlr7oXm5LsY4poSySVnPYw4c81QeULRAs2zCYr87sfwgHeiy9OHJo74H8jfG2S Xhn1k8UoFApRgD65sd/2/CG+LXc8MweefOuMi6peA704UKHt1WRP6WAjJbRL6Va57ArM cn/8U1QxKFtPvpEEJEHJ43Sbg5d+GzRV2H2WE9pHSdukEaH2XUdzLm7JxKTLfDO32hFw 9oMg==
X-Forwarded-Encrypted: i=1; AJvYcCWkbzhsmzs1zoY3cWO/k6AUEhCCxR45mOsrTL41tqMGbYRzcn+O91hmJlchf01oJXcbmF5psIuFi2VI8XEPmvaF
X-Gm-Message-State: AOJu0YwagVdPsHgLRa9vpO0c3bTvIHpQJRaXCts5+wYXtzPhr5SWvVN2 OqxSh3D+g5bcI6ysPwvvEwsUGyqs7LzAkFRGeXMqey/Uh2oq7WFlyU96xLQFr5T3KieZHwMG9/2 43VktafKyTY4KSjNZdc4FZE6xgopPZoDg
X-Google-Smtp-Source: AGHT+IGEZ/obstejPIAit3c1apJe6TH7t+Vgq1BMdwJUpWasaPYofgZbE4Xo7SIHaYYR11ZlY1gg6vB/oxYC3k1lxlY=
X-Received: by 2002:a17:906:5ad8:b0:a3c:9bc7:7a0e with SMTP id x24-20020a1709065ad800b00a3c9bc77a0emr2000545ejs.9.1707747017876; Mon, 12 Feb 2024 06:10:17 -0800 (PST)
MIME-Version: 1.0
References: <20230922080522.17B21E5F67@rfcpa.amsl.com> <20D18BE5-1BE0-49D0-9626-9483D17893E1@amsl.com>
In-Reply-To: <20D18BE5-1BE0-49D0-9626-9483D17893E1@amsl.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Mon, 12 Feb 2024 19:40:01 +0530
Message-ID: <CAH6gdPyG1YBcgZP5BiQ4yO5=Rf8zJMQZoHQ_RtEQ4hWm37YzKQ@mail.gmail.com>
To: andrew-ietf@liquid.tech, "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>
Cc: bess@ietf.org, Rebecca VanRheenen <rvanrheenen@amsl.com>
Content-Type: multipart/alternative; boundary="0000000000005de61506112fd698"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/R3eQReTmpttirT5VeJirnjoM86w>
Subject: Re: [bess] [Editorial Errata Reported] RFC9252 (7652)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Feb 2024 14:10:24 -0000

Any update on this?


On Thu, Nov 9, 2023 at 12:03 AM Rebecca VanRheenen <rvanrheenen@amsl.com>
wrote:

> HI Andrew,
>
> We are unable to verify this erratum that the submitter marked as
> editorial.
> Please note that we have changed the “Type” of the following errata
> report to “Technical”.  As Stream Approver, please review and set the
> Status and Type accordingly (see the definitions at
> https://www.rfc-editor.org/errata-definitions/).
>
> You may review the report at:
> https://www.rfc-editor.org/errata/eid7652
>
> Please see https://www.rfc-editor.org/how-to-verify/ for further
> information on how to verify errata reports.
>
> Further information on errata can be found at:
> https://www.rfc-editor.org/errata.php.
>
> Thank you.
>
> RFC Editor/rv
>
>
>
> > On Sep 22, 2023, at 1:05 AM, RFC Errata System <
> rfc-editor@rfc-editor.org> wrote:
> >
> > The following errata report has been submitted for RFC9252,
> > "BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)".
> >
> > --------------------------------------
> > You may review the report below and at:
> > https://www.rfc-editor.org/errata/eid7652
> >
> > --------------------------------------
> > Type: Editorial
> > Reported by: Ketan Talaulikar <ketant.ietf@gmail.com>
> >
> > Section: 3.2.1
> >
> > Original Text
> > -------------
> >   Transposition Offset indicates the bit position, and Transposition
> >   Length indicates the number of bits that are being taken out of the
> >   SRv6 SID value and encoded in the MPLS Label field.  The bits that
> >   have been shifted out MUST be set to 0 in the SID value.
> >
> > Corrected Text
> > --------------
> >   Transposition Offset indicates the bit position and Transposition
> >   Length indicates the number of bits that are being taken out of the
> >   SRv6 SID value and put into high order bits of MPLS label field. The
> >   bits that have been shifted out MUST be set to 0 in the SID value.
> >
> > Notes
> > -----
> > This errata reverses an editorial change that was made during the AUTH48
> phase and restores the text that came from the WG and IESG review. Refer
> https://datatracker.ietf.org/doc/html/draft-ietf-bess-srv6-services-15#page-10
> >
> > This change was made during the AUTH48 since the "high order bits" was
> already covered under various subsections of Sec 6. However, readers have
> reported that there are other places in Sec 6 and Sec 5 where transposition
> also occurs and that the original text was still required.
> >
> > Instructions:
> > -------------
> > This erratum is currently posted as "Reported". If necessary, please
> > use "Reply All" to discuss whether it should be verified or
> > rejected. When a decision is reached, the verifying party
> > can log in to change the status and edit the report, if necessary.
> >
> > --------------------------------------
> > RFC9252 (draft-ietf-bess-srv6-services-15)
> > --------------------------------------
> > Title               : BGP Overlay Services Based on Segment Routing over
> IPv6 (SRv6)
> > Publication Date    : July 2022
> > Author(s)           : G. Dawra, Ed., K. Talaulikar, Ed., R. Raszuk, B.
> Decraene, S. Zhuang, J. Rabadan
> > Category            : PROPOSED STANDARD
> > Source              : BGP Enabled ServiceS
> > Area                : Routing
> > Stream              : IETF
> > Verifying Party     : IESG
> >
>
>