[auth48] Re: AUTH48: RFC-to-be 9956 <draft-ietf-tsvwg-nqb-33> for your review

Megan Ferguson <mferguson@staff.rfc-editor.org> Tue, 05 May 2026 17:03 UTC

Return-Path: <mferguson@staff.rfc-editor.org>
X-Original-To: auth48archive@mail2.ietf.org
Delivered-To: auth48archive@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2BBEAE95FF9E for <auth48archive@mail2.ietf.org>; Tue, 5 May 2026 10:03:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778000610; bh=J9ZO7e6BP1WzWSRSzgps5VhZsZgmBap1UWDJd1GR7jM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=Lo9M+3QQYMnORXbt7zpITolTvcbWap7hwf61A9ZMV/GFYPrVhs2FmM2uzd8/kNuD1 A9LYKqHOa0VbO1oIUD3l0D0+ouxBt5nXbFz7oGFVaLPG7IlaV4UtAShK0cDZEebITt TMYeSVGgfMpTwrdzjGJKB/mTa6HZBSh/jFJWVrzg=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=staff-rfc-editor-org.20251104.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L725oz0m7JwN for <auth48archive@mail2.ietf.org>; Tue, 5 May 2026 10:03:24 -0700 (PDT)
Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id EDC80E95FF87 for <auth48archive@rfc-editor.org>; Tue, 5 May 2026 10:03:24 -0700 (PDT)
Received: by mail-oi1-x229.google.com with SMTP id 5614622812f47-47bdee5bfc4so63288b6e.1 for <auth48archive@rfc-editor.org>; Tue, 05 May 2026 10:03:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-rfc-editor-org.20251104.gappssmtp.com; s=20251104; t=1778000604; x=1778605404; darn=rfc-editor.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=DUrsk3dc3K0k/ffssh7T5drnrurDT/Dpq+gmfyg/5f0=; b=tS2efG96ICWue7oTNxPH9WFuCgxwCbbchLkQqHBoMG4JgvTRQABykDm4L2Kb8uJ3jo i+7WFJpqwjqj7bDrsCl0acE7f8MBn2/w7DTYWAyUYgtKvI3/qh0IEEfZeLBabyu1ooBC V4uWnpgXqMqb66m+w4vzJCgElcfR1aoRhFofp+I9wwKsw2vaVTi16uSOkyhflCGvKUkV i800jZNAq/uurnB3MBMg8Tlyws9XaIk1J3AltQI7mlnKEdkhXyrkTwfkzY0pXzfB7nzZ QEyb7yfRKq7sM3v17HoG7p5t7dCNZzmGM22OmqelYmqTNTvdBQJp2OC83Gxn7oYmjSI8 jGCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1778000604; x=1778605404; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-gg:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=DUrsk3dc3K0k/ffssh7T5drnrurDT/Dpq+gmfyg/5f0=; b=sq5XqwHS1PLH7VCKB6OG/8REtezoMGrgVHyyTVlVWy64HgkiElfZB30X7k2bFxxzXV FX7/oid6qhMq4LWPVgwNH8IqXo9Oms0tzwp2KCYPau+5h29FWgQPK4gRU55J+5L2caxl 1y1/Ss3/nzjRI+m+WO/Sd1aD7kEpKgGDhcYXTq11EwmX5jDZZ6czjruLGFno6y0m4PqV yXGLwP7geL/8AvBF2AF2hKjhQNDTEP84umQeQ0yAV1VpzK07AQ4PREexCPCIB+Tyh4Ii +vw8WXN33mZyKUGe419LXPGlmCvXQLdxl60lOxBa8kgsRJMEZI4dBfSkcIDxRfiAJ3Fy XwhA==
X-Forwarded-Encrypted: i=1; AFNElJ+i6Dy5Xn/q/Q37lxRJi3Q1Jd5yq07IdrNhPYqHG+z6wR+t930HyipGiDDtzxZ17D20n5gKyG/aYAOjI7dA@rfc-editor.org
X-Gm-Message-State: AOJu0YxZvHehaWJEn4pCQ6b9/vd3O0WG48aMLTe6AjKh3qT63iqdDpvF 1TL1RhDqJnmRClLwMWXlXtVYSiAfYEDJexK1nYa61IK6QN6ILZV7lIAiYJFcRUmPauRKjQ==
X-Gm-Gg: AeBDieuHzWc7vRFgm8E+NrH2hfIMY6plORzmGbOiKO0HS/gJE64SVgElcc5xc/tx79v JqGDVPD2xuaMxLTOAPnMwh6WE5x6vzQmIIci4RcjPqDOVX69wqCIHwyHA5kldXEzyhWVK1PhBWp eOsi2WJ4L51JFDkHiRKVs3kE1Qr46J7VmKhgv0H9tPuM719z2vSDoXtm3h81P4wgnpNq9PgZgo7 7mmZpi+VqgoRX1XdTeHjVVJosiVyLIkSh8g0KxyEwu3fs65qZ4heYHWf8UAdL4etdEmzIJTikVs ynTTWb/yBeXPQrJHUox4dTrHUzJiH1xrlBxBNTb3FprHAM8Nvk+TrBajogN4cbJMbnKm6Zsa5ql W0AeV56ffSm03GubA492achkJu8dM9XWsnlYg5XShz6Uz4KGtIXv98xfImzTIbHt9eNXNtGsKVB mad92Z0tA8uJpNGMumOu4s/Yj1k3G00U4TW6l6UrR3w9wraFxZoFN+et41iDlDKwV2iM/OiMheF Lx9hhVdXUBM8MI/7pYlWOdM+gN9cA==
X-Received: by 2002:a05:6808:3093:b0:479:ae1d:fff6 with SMTP id 5614622812f47-47d26222169mr2306632b6e.11.1778000603208; Tue, 05 May 2026 10:03:23 -0700 (PDT)
Received: from smtpclient.apple (c-24-9-47-226.hsd1.co.comcast.net. [24.9.47.226]) by smtp.gmail.com with ESMTPSA id 5614622812f47-47c763b33c1sm9001239b6e.1.2026.05.05.10.03.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 May 2026 10:03:22 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
From: Megan Ferguson <mferguson@staff.rfc-editor.org>
In-Reply-To: <BEZP281MB2007693992AE97BC4E2AF9759C3E2@BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM>
Date: Tue, 05 May 2026 11:03:11 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B8AA43D-5D9D-4CC3-915A-A9FD86CF3243@staff.rfc-editor.org>
References: <20260407054522.5DFFB2BBC4E@rfcpa.rfc-editor.org> <1D23105F-4A58-49D5-9304-1F4A5862F52F@CableLabs.com> <BEZP281MB200742A5D792AE99FDB825C89C2A2@BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM> <7EBD5F19-ACD8-407B-A4C1-0DB84B54557F@staff.rfc-editor.org> <A499BDD6-F6D4-462D-8916-EB308687DA0E@CableLabs.com> <BEZP281MB20072C2A6D2A5D3F133EFA239C362@BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM> <5AF957C6-07DE-4648-AFED-0C93B5CA8D67@staff.rfc-editor.org> <15532f7f-0b9f-4943-9a8c-6add42f50826@erg.abdn.ac.uk> <7A67B577-9AF1-4CE4-8FAE-1112B6AAAA88@staff.rfc-editor.org> <CF286B85-957D-4686-8843-B19613B9DE4C@CableLabs.com> <3FEB097F-9421-4BA4-B399-073B4DDE168B@staff.rfc-editor.org> <BEZP281MB2007693992AE97BC4E2AF9759C3E2@BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM>
To: Ruediger.Geib@telekom.de, gorry@erg.abdn.ac.uk, thomas.fossati@linaro.org
X-Mailer: Apple Mail (2.3864.400.21)
Message-ID-Hash: ZJMEKM4WKF6RJT5XHRBWQ5LN5DLV4XTI
X-Message-ID-Hash: ZJMEKM4WKF6RJT5XHRBWQ5LN5DLV4XTI
X-MailFrom: mferguson@staff.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, tsvwg-ads@ietf.org, tsvwg-chairs@ietf.org, zahed.sarker.ietf@gmail.com, auth48archive@rfc-editor.org, "<g.white@cablelabs.com>" <g.white@CableLabs.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [auth48] Re: AUTH48: RFC-to-be 9956 <draft-ietf-tsvwg-nqb-33> for your review
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/vD4VePB4rpTWbmmdP230fvlFeo4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Owner: <mailto:auth48archive-owner@rfc-editor.org>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Subscribe: <mailto:auth48archive-join@rfc-editor.org>
List-Unsubscribe: <mailto:auth48archive-leave@rfc-editor.org>

Ruediger,

Got it!  As all approvals have now been received (see links below), we have updated this document’s status to “AUTH48-DONE”.  We will move it and its companion document (RFC-to-be 9957) forward in the publication process at this time.

The AUTH48 status page is available here:
https://www.rfc-editor.org/auth48/rfc9956

The AUTH48 cluster information is available here:
https://www.rfc-editor.org/auth48/C350

Thank you all for your time and attention during AUTH48!

Megan Feguson
RFC Production Center


> On May 5, 2026, at 12:54 AM, Ruediger.Geib@telekom.de wrote:
> 
> Hi Megan,
> 
> just to make sure I respond to the correct mail: I approve to publication of the document as is.
> 
> Regards, Ruediger
> 
> -----Ursprüngliche Nachricht-----
> Von: Megan Ferguson <mferguson@staff.rfc-editor.org>
> Gesendet: Montag, 4. Mai 2026 20:47
> An: Greg White <g.white@CableLabs.com>; Geib, Rüdiger <Ruediger.Geib@telekom.de>
> Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>; thomas.fossati@linaro.org; rfc-editor@rfc-editor.org; tsvwg-ads@ietf.org; tsvwg-chairs@ietf.org; zahed.sarker.ietf@gmail.com; auth48archive@rfc-editor.org
> Betreff: Re: AUTH48: RFC-to-be 9956 <draft-ietf-tsvwg-nqb-33> for your review
> 
> Hi Greg (and *Ruediger),
> 
> Thanks for the careful review!  We have rolled this small change and updates to the date into the current version of the file.  Please refresh to see at the links below.
> 
> We have also updated your status to “Approved” at the AUTH48 status page (see below).
> 
> Our current files are posted here (please refresh):
> https://www.rfc-editor.org/authors/rfc9956.txt
> https://www.rfc-editor.org/authors/rfc9956.pdf
> https://www.rfc-editor.org/authors/rfc9956.html
> https://www.rfc-editor.org/authors/rfc9956.xml
> 
> The diff files (encompassing changes from both of the above) are posted here (please refresh):
> https://www.rfc-editor.org/authors/rfc9956-diff.html
> https://www.rfc-editor.org/authors/rfc9956-rfcdiff.html (side by side)
> https://www.rfc-editor.org/authors/rfc9956-auth48diff.html
> https://www.rfc-editor.org/authors/rfc9956-auth48rfcdiff.html (side by side)
> 
> Please review the document in its current form carefully as we do not make changes once it is published as an RFC.
> 
> *Ruediger - we see you previously sent:
> 
>> [RG] I agree with all other changes accepted by Greg and Thomas.
> 
> Please reply with an overt approval of the document in its current form (to clarify if you approve it in total or were just approving those specific changes) or with any further updates you may have.  We will await word from you prior to moving this document forward in the publication process.
> 
> Note: Because this document references RFC-to-be 9957, we will await that document’s completion of AUTH48 as well prior to moving to publication.
> 
> The AUTH48 status page is available here:
> https://www.rfc-editor.org/auth48/rfc9956
> 
> The AUTH48 cluster information is available here:
> https://www.rfc-editor.org/auth48/C350
> 
> Thank you.
> 
> Megan Feguson
> RFC Production Center
> 
>> On May 1, 2026, at 4:47 PM, Greg White <g.white@CableLabs.com> wrote:
>> 
>> I did a top-to-bottom review of the current 9956 and found one issue.  In the first sentence of section 6.5, I see one instance of "DS" that was not changed to "Diffserv"
>> 
>> Once that is fixed, I approve moving the document forward.
>> 
>> -Greg
>> 
>> 
>> 
>> On 4/30/26, 2:16 PM, "Megan Ferguson" <mferguson@staff.rfc-editor.org <mailto:mferguson@staff.rfc-editor.org>> wrote:
>> 
>> 
>> Gorry and Thomas,
>> 
>> 
>> Thank you for your replies. We have updated the AUTH48 status page of this document to reflect your approvals. We will await approvals from each listed party prior to moving this document forward in the publication process.
>> 
>> 
>> The AUTH48 status page is available here:
>> https://www.rfc-editor.org/auth48/rfc9956 <https://www.rfc-editor.org/auth48/rfc9956>
>> 
>> 
>> The AUTH48 cluster information is available here:
>> https://www.rfc-editor.org/auth48/C350 <https://www.rfc-editor.org/auth48/C350>
>> 
>> 
>> Thank you.
>> 
>> 
>> Megan Feguson
>> RFC Production Center
>> 
>> 
>>> On Apr 29, 2026, at 1:32 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> wrote:
>>> 
>>> On 27/04/2026 20:00, Megan Ferguson wrote:
>>>> AD/Gorry - Just a reminder to please review/approve the updates to Section 7.2 (described in response to Question #21 below) viewable in the following diff(s):
>>>> https://www.rfc-editor.org/authors/rfc9956-auth48diff.html <https://www.rfc-editor.org/authors/rfc9956-auth48diff.html>
>>>> https://www.rfc-editor.org/authors/rfc9956-auth48rfcdiff.html <https://www.rfc-editor.org/authors/rfc9956-auth48rfcdiff.html> (side by side)
>>>> ---
>>> 
>>> I confirm I have re-read the new Sect 7.2, and this reads OK to me,
>>> 
>>> Gorry
>>> 
>>> 
>> 
>> 
>> 
>> 
>> 
>