Re: [auth48] [AD] AUTH48: RFC-to-be 9376 <draft-ietf-ccamp-gmpls-otn-b100g-applicability-15> for your review
Rebecca VanRheenen <rvanrheenen@amsl.com> Tue, 28 March 2023 19:47 UTC
Return-Path: <rvanrheenen@amsl.com>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70D5CC151B3B; Tue, 28 Mar 2023 12:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
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 vmlr_ioWHZPR; Tue, 28 Mar 2023 12:47:09 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 439C4C14CE53; Tue, 28 Mar 2023 12:47:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id E9D6C424CD05; Tue, 28 Mar 2023 12:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kEFKaj12Djc8; Tue, 28 Mar 2023 12:47:04 -0700 (PDT)
Received: from [IPv6:2601:641:300:5fb0:ecc6:5fbf:a2a3:6375] (unknown [IPv6:2601:641:300:5fb0:ecc6:5fbf:a2a3:6375]) by c8a.amsl.com (Postfix) with ESMTPSA id 7CDD7424CD01; Tue, 28 Mar 2023 12:47:04 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Rebecca VanRheenen <rvanrheenen@amsl.com>
In-Reply-To: <86162F3D-823F-49A8-BA2F-FE181FC8FBD9@amsl.com>
Date: Tue, 28 Mar 2023 12:47:03 -0700
Cc: RFC Editor <rfc-editor@rfc-editor.org>, ccamp-chairs@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, auth48archive@rfc-editor.org, zhangfatai@huawei.com, andrew-ietf@liquid.tech
Content-Transfer-Encoding: quoted-printable
Message-Id: <65C1FA09-12BB-46BF-A63C-FD9D9888A3E2@amsl.com>
References: <202303200955299067065@zte.com.cn> <1025e2e6-3f9f-3aba-eb3a-4db164bae290@gmail.com> <F0B2AD86-257A-44E2-A48E-AC3FF454D4AB@amsl.com> <86162F3D-823F-49A8-BA2F-FE181FC8FBD9@amsl.com>
To: Huub van Helvoort <huubatwork@gmail.com>, wang.qilei@zte.com.cn, Radhakrishna Valiveti <rvaliveti@infinera.com>, Zhenghaomian <zhenghaomian@huawei.com>, "Sergio Belotti (Nokia)" <sergio.belotti@nokia.com>, John Scudder <jgs@juniper.net>, ccamp-ads@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/b9qaMUAcgdEy1LtLHBnHDRnZs-0>
Subject: Re: [auth48] [AD] AUTH48: RFC-to-be 9376 <draft-ietf-ccamp-gmpls-otn-b100g-applicability-15> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2023 19:47:14 -0000
Hi John, This is a friendly reminder that we await your AD approval of the items listed in the email below. All questions have been addressed, and all author approvals have been received; once we receive your approval, we can move this document forward in the publication process. Thank you, RFC Editor/rv > On Mar 20, 2023, at 1:35 PM, Rebecca VanRheenen <rvanrheenen@amsl.com> wrote: > > Hi John, > > As AD, please review the following changes and let us know if you approve: > > - Changes in first paragraph of Section 4.2 (addition of “client signal”) > - All changes in Section 4.3 > - Change from “G” to "Gbit/s” throughout document, including document title (both units were used in original) > > These changes are best viewed in one of the following diff files: > https://www.rfc-editor.org/authors/rfc9376-alt-diff.html (shows all changes) > https://www.rfc-editor.org/authors/rfc9376-auth48diff.html (shows changes made during AUTH48) > > Thank you, > RFC Editor/rv > > > >> On Mar 20, 2023, at 1:33 PM, Rebecca VanRheenen <rvanrheenen@amsl.com> wrote: >> >> Sergio, Haomian, and Huub, >> >> Thank you for your replies. We have noted your approvals on the AUTH48 status page for this document (see https://www.rfc-editor.org/auth48/rfc9376). >> >> We have all author approvals. We will now ask the AD to approve a few changes that are “above editorial”. Once those changes are approved, we can move forward in the publication process. >> >> Thank you, >> RFC Editor/rv >> >> >> >>> On Mar 20, 2023, at 3:03 AM, Huub van Helvoort <huubatwork@gmail.com> wrote: >>> >>> Dear RFC editor, >>> >>> I do not have any further comments. >>> I support publication of this RFC. >>> >>> Cheers, Huub van Helvoort (co-author) >>> >>> ========= >>> >>> On 20/03/2023 02:55, wang.qilei@zte.com.cn wrote: >>>> Hi RFC editor, >>>> Thanks for your work. I reviewed the draft again and have no more changes. >>>> To the other authors, please let us know whether you have further comments, if no, please let us know whether you support the publication of the draft. >>>> Thanks >>>> Qilei >>> >>> -- >>> ================================================================ >>> Always remember that you are unique...just like everyone else... >>> >> >
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… rfc-editor
- [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-ccamp… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… wang.qilei
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… wang.qilei
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… Rebecca VanRheenen
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… wang.qilei
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… Radhakrishna Valiveti
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… Rebecca VanRheenen
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… Rebecca VanRheenen
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… wang.qilei
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… Rebecca VanRheenen
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… wang.qilei
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… Sergio Belotti (Nokia)
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… Zhenghaomian
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… Huub van Helvoort
- Re: [auth48] AUTH48: RFC-to-be 9376 <draft-ietf-c… Rebecca VanRheenen
- [auth48] [AD] Re: AUTH48: RFC-to-be 9376 <draft-i… Rebecca VanRheenen
- Re: [auth48] [AD] AUTH48: RFC-to-be 9376 <draft-i… Rebecca VanRheenen
- Re: [auth48] [AD] AUTH48: RFC-to-be 9376 <draft-i… John Scudder
- Re: [auth48] [AD] AUTH48: RFC-to-be 9376 <draft-i… Rebecca VanRheenen