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, 5 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
Message-ID-Hash: ZJMEKM4WKF6RJT5XHRBWQ5LN5DLV4XTI
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>
Precedence: list
Subject: =?utf-8?q?=5Bauth48=5D_Re=3A_AUTH48=3A_RFC-to-be_9956_=3Cdraft-ietf-tsvwg-nq?=
	=?utf-8?q?b-33=3E_for_your_review?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/auth48archive/vD4VePB4rpTWbmmdP230fvlFeo4>

Ruediger,

Got it!  As all approvals have now been received (see links below), we =
have updated this document=E2=80=99s status to =E2=80=9CAUTH48-DONE=E2=80=9D=
.  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=E2=80=AFAM, Ruediger.Geib@telekom.de wrote:
>=20
> Hi Megan,
>=20
> just to make sure I respond to the correct mail: I approve to =
publication of the document as is.
>=20
> Regards, Ruediger
>=20
> -----Urspr=C3=BCngliche 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=C3=BCdiger =
<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
>=20
> Hi Greg (and *Ruediger),
>=20
> 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.
>=20
> We have also updated your status to =E2=80=9CApproved=E2=80=9D at the =
AUTH48 status page (see below).
>=20
> 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
>=20
> 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)
>=20
> Please review the document in its current form carefully as we do not =
make changes once it is published as an RFC.
>=20
> *Ruediger - we see you previously sent:
>=20
>> [RG] I agree with all other changes accepted by Greg and Thomas.
>=20
> 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.
>=20
> Note: Because this document references RFC-to-be 9957, we will await =
that document=E2=80=99s completion of AUTH48 as well prior to moving to =
publication.
>=20
> The AUTH48 status page is available here:
> https://www.rfc-editor.org/auth48/rfc9956
>=20
> The AUTH48 cluster information is available here:
> https://www.rfc-editor.org/auth48/C350
>=20
> Thank you.
>=20
> Megan Feguson
> RFC Production Center
>=20
>> On May 1, 2026, at 4:47=E2=80=AFPM, Greg White =
<g.white@CableLabs.com> wrote:
>>=20
>> 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"
>>=20
>> Once that is fixed, I approve moving the document forward.
>>=20
>> -Greg
>>=20
>>=20
>>=20
>> =EF=BB=BFOn 4/30/26, 2:16 PM, "Megan Ferguson" =
<mferguson@staff.rfc-editor.org <mailto:mferguson@staff.rfc-editor.org>> =
wrote:
>>=20
>>=20
>> Gorry and Thomas,
>>=20
>>=20
>> 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.
>>=20
>>=20
>> The AUTH48 status page is available here:
>> https://www.rfc-editor.org/auth48/rfc9956 =
<https://www.rfc-editor.org/auth48/rfc9956>
>>=20
>>=20
>> The AUTH48 cluster information is available here:
>> https://www.rfc-editor.org/auth48/C350 =
<https://www.rfc-editor.org/auth48/C350>
>>=20
>>=20
>> Thank you.
>>=20
>>=20
>> Megan Feguson
>> RFC Production Center
>>=20
>>=20
>>> On Apr 29, 2026, at 1:32 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk =
<mailto:gorry@erg.abdn.ac.uk>> wrote:
>>>=20
>>> 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)
>>>> ---
>>>=20
>>> I confirm I have re-read the new Sect 7.2, and this reads OK to me,
>>>=20
>>> Gorry
>>>=20
>>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20