[ippm] [IANA #1223871] IANA-related errata

Amanda Baber via RT <iana-matrix@iana.org> Tue, 01 March 2022 17:46 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 137F43A07CF for <ippm@ietfa.amsl.com>; Tue, 1 Mar 2022 09:46:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level:
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 9hlcY17DFYyn for <ippm@ietfa.amsl.com>; Tue, 1 Mar 2022 09:46:06 -0800 (PST)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (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 836DB3A03F5 for <ippm@ietf.org>; Tue, 1 Mar 2022 09:46:06 -0800 (PST)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id CAF29E0E9F; Tue, 1 Mar 2022 17:46:04 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id B4AD4207A6; Tue, 1 Mar 2022 17:46:04 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-matrix@iana.org>
Reply-To: iana-matrix@iana.org
In-Reply-To: <rt-4.4.3-3812-1645801106-242.1223871-37-0@icann.org>
References: <RT-Ticket-1223871@icann.org> <B86BE79E-3003-4D83-BA13-A5AECF6F579A@amsl.com> <rt-4.4.3-4441-1643754335-1360.1223871-9-0@icann.org> <CH0PR02MB79804F23B2B5B75583124A21D32F9@CH0PR02MB7980.namprd02.prod.outlook.com> <rt-4.4.3-10076-1644506726-1305.1223871-37-0@icann.org> <rt-4.4.3-9065-1645753424-1824.1223871-37-0@icann.org> <CH0PR02MB7980BA786C7295A29BAAFC5AD33E9@CH0PR02MB7980.namprd02.prod.outlook.com> <rt-4.4.3-3812-1645801106-242.1223871-37-0@icann.org>
Message-ID: <rt-4.4.3-10732-1646156764-1407.1223871-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1223871
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
To: sginoza@amsl.com
CC: zaheduzzaman.sarker@ericsson.com, rfc-editor@rfc-editor.org, philip.eardley@bt.com, nmalykh@ieee.org, martin.h.duke@gmail.com, marcelo@it.uc3m.es, kd6913@att.com, ippm@ietf.org, csmiley@amsl.com, acmorton@att.com
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Tue, 01 Mar 2022 17:46:04 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/6zEgyDbVupCw2T5lEINJ_CS-5t8>
X-Mailman-Approved-At: Wed, 02 Mar 2022 08:26:11 -0800
Subject: [ippm] [IANA #1223871] IANA-related errata
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2022 17:46:14 -0000

Hi Al,

This works for us. We'll make these changes (with the appropriate revision date) once the errata report has been verified.

thanks,
Amanda

On Fri Feb 25 14:58:26 2022, acmorton@att.com wrote:
> Hi Amanda,
> please see below,
> Al
> 
> > -----Original Message-----
> > From: Amanda Baber via RT <iana-matrix@iana.org>
> > Sent: Thursday, February 24, 2022 8:44 PM
> > Cc: zaheduzzaman.sarker@ericsson.com; philip.eardley@bt.com;
> > nmalykh@ieee.org;
> > martin.h.duke@gmail.com; marcelo@it.uc3m.es; D'SOUZA, KEVIN L
> > <kd6913@att.com>; csmiley@amsl.com; MORTON JR., AL <acmorton@att.com>
> > Subject: [IANA #1223871] IANA-related errata
> >
> > Hi Al,
> >
> > Sorry for the late reply to this one.
> >
> > If that small piece of text would have been part of the registration,
> > we'll go
> > ahead and add it (once it's been verified) unless you have a
> > preference for
> > not doing so.
> [acm]
> I think we can add the text in the affected registration.
> 
> >
> > Adding it to the registration would mean that we would also add a
> > link to the
> > errata report to that registration's reference field at
> > https://urldefense.com/v3/__https://www.iana.org/assignments/performance-
> > metrics__;!!BhdT!jpiKwWtU-yAuVZPnHKVrDSwrGt-X17FpNNK2LGBfQGlT-
> > PSu2kNrWxpPpx4hV3xh5BgZF87IPtLKz9Zs$ . (I understand that the version
> > number
> > would not be changed.)
> [acm]
> Yes, adding a link to the errata is a good thing.
> Yes, the Version number would not change (this is the version of the
> registry structure).
> 
> In addition to including the small piece of text in the registration,
> I think we would also update:
> 
> OLD
> 5.5.3. Revision
> 
> 1.0
> 
> 5.5.4. Revision Date
> 
> 2021-11-17
> NEW
> 5.5.3. Revision
> 
> 1.1
> 
> 5.5.4. Revision Date
> 
> 2021-02-25  (or date when final)
> 
> Let me know if this sounds right to you.
> 
> >
> > Given the update to the reference field, do you prefer that we *not*
> > update
> > the registration?
> [acm]
> I'm ok with the update(s), it's a good test of the process...
> 
> >
> > thanks,
> > Amanda
> >
> > On Thu Feb 10 15:25:26 2022, acmorton@att.com wrote:
> > > Hi Amanda,
> > >
> > > We could certainly add the paragraph in the registry entry, but it
> > > doesn't add any requirements: it's simply a description of the
> > > category/section.
> > >
> > > Despite the Errata type "Technical", adding the 1 sentence
> > > paragraph
> > > doesn't resolve anything more than an editorial concern.
> > >
> > > I think we can leave it alone for now, unless you want to test the
> > > registration update process...
> > >
> > > Al
> > >
> > > > -----Original Message-----
> > > > From: Amanda Baber via RT <iana-matrix-comment@iana.org>
> > > > Sent: Tuesday, February 1, 2022 5:26 PM
> > > > Cc: zaheduzzaman.sarker@ericsson.com; philip.eardley@bt.com;
> > > > nmalykh@ieee.org;
> > > > martin.h.duke@gmail.com; marcelo@it.uc3m.es; D'SOUZA, KEVIN L
> > > > <kd6913@att.com>; csmiley@amsl.com; MORTON JR., AL
> > > > <acmorton@att.com>
> > > > Subject: [IANA #1223871] IANA-related errata
> > > >
> > > > Dear RFC 8912 authors,
> > > >
> > > > The following errata report states that a paragraph is missing
> > > > from
> > > > Section
> > > > 5.3.5:
> > > >
> > > > https://urldefense.com/v3/__https://www.rfc-
> > > > editor.org/errata/eid6755__;!!BhdT!1DyZFgC9t5y8WjaYLR3tZejTFJGb-
> > > > yAT8sfRMoGV_lUuv-mlAc_mgwlDQb0c$
> > > >
> > > > If this report is verified, will the paragraph need to be added
> > > > to
> > > > Section
> > > > 5.3.5 in this registration?
> > > >
> > > > https://urldefense.com/v3/__https://www.iana.org/assignments/performance-
> > > > metrics/OWPDV_Active_IP-UDP-
> > > >
> > Periodic_RFC8912sec5_Seconds_95Percentile__;!!BhdT!1DyZFgC9t5y8WjaYLR3tZejTFJG
> > > > b-yAT8sfRMoGV_lUuv-mlAc_mg_D6C4QD$
> > > >
> > > > thanks,
> > > >
> > > > Amanda Baber
> > > > IANA Operations Manager
>