Re: [auth48] *[AD] Re: [EXTERNAL] AUTH48: RFC-to-be 9406 <draft-ietf-tcpm-hystartplusplus-14> for your review

Martin Duke <martin.h.duke@gmail.com> Tue, 02 May 2023 00:55 UTC

Return-Path: <martin.h.duke@gmail.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 ED098C15C520; Mon, 1 May 2023 17:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 N82486We_SRf; Mon, 1 May 2023 17:55:25 -0700 (PDT)
Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (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 278A7C152575; Mon, 1 May 2023 17:55:25 -0700 (PDT)
Received: by mail-ua1-x92a.google.com with SMTP id a1e0cc1a2514c-76fd0036c7fso962828241.3; Mon, 01 May 2023 17:55:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682988924; x=1685580924; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=1uEbNuk4bkWz7sM4vTXqPxlln+48/yj5bnW+1jhe6fQ=; b=PcaLvd2ctQJ9dJXvCGs4xBi6cwLToXjtINOeUCZ1DhIHzaucRRfujJHtCphqgpfuLq CYoB+aYdIRvz465cY2tnCLu+vRKOl52LnYa5nNxCT2xhFD70rU1m1VzJuwWXwLaqZloT GF8fesXB+bP+ipezpx7h7ExakcP7VccivLDPeXT+eRy8fG2rg1UteL90FVZHWMV3YGJr CFQUMZJCosSMbSznPyGug/qeVUJ1mmC55HRMIb9fFXhE6hQG/rLPmJwO6XSB2IS7rczl +OWCGeY1gnb13XpBCc9XlSFqujzQopPGAi6LQ7C1LWsWVGltWNcHm2O35nRETND52ecB A71g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682988924; x=1685580924; 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=1uEbNuk4bkWz7sM4vTXqPxlln+48/yj5bnW+1jhe6fQ=; b=kSPtikZADAPI3lDpkdmgLo3bNBKjLEM/N1Qzqo6rE0zGhRzhUM8fnyebmONWt8bDAv AAmCq2qEJF6Goty2d+xjBtWJRKSXitZjFkOGwpgpodQw7Sa9pYGDQ7g+QltQiHIB2Ods 5+72v0Pd3DdEbknqx/AcGvY+9+4SE4+KVJwX2PoxRtVhs+4bVF4x8P4tsZj3LWFZQ/yk saJbfx9WHwNYO0Cnvv5W+98oGSt2cG4G0eh7HXU0y0HVD8AVndCifJ4JA0PcT2mRIR2p 36I2h1SqABI4ENB3bwDAeiRCSdxC61HIKmSdZK3HnOZxdjfN77NSzrtpGhrS7+vcMEzC 9q1g==
X-Gm-Message-State: AC+VfDygAm83G6HxlcPYViAogTnr+zbVsva31jeVaFXQEDz4ZZkxSq+5 5+MxPBx91yAkcXtSYuCfHFQ2nRl/28n9qo2nhW8=
X-Google-Smtp-Source: ACHHUZ7ymXCQjF7mFYarU6tmP8o7/CvJfmu2SmX992KSFckQJxvqeZoRtYchiI6WD7EqitcjM1Cbt1/OSDWFHpWFAZk=
X-Received: by 2002:a05:6102:c8:b0:430:1144:20fd with SMTP id u8-20020a05610200c800b00430114420fdmr6050279vsp.8.1682988923800; Mon, 01 May 2023 17:55:23 -0700 (PDT)
MIME-Version: 1.0
References: <20230427221206.E406A563F3@rfcpa.amsl.com> <3CF517BB-7040-4A3D-845E-7F9FCFF987ED@amsl.com> <MN2PR00MB086242D81527119C5A695F14C368A@MN2PR00MB0862.namprd00.prod.outlook.com> <7B8CF13E-053D-44A6-8294-6ABE71DB668C@amsl.com> <BY5PR00MB08510F15C87B36D114B1DEB0C36EA@BY5PR00MB0851.namprd00.prod.outlook.com> <E516034B-7B26-44E9-8A77-47AE108D5900@amsl.com> <BY5PR00MB0851A3587ED0F04A0116AE68C36EA@BY5PR00MB0851.namprd00.prod.outlook.com> <29CE4A98-28FF-4FB7-8CD7-8AD0E1D4C9BA@amsl.com> <BY5PR00MB0851295B1DCDE085C6D778C1C36EA@BY5PR00MB0851.namprd00.prod.outlook.com> <DM5PR00MB03904FAB784D5BA46DCEB320BC6EA@DM5PR00MB0390.namprd00.prod.outlook.com> <CAL=F3yKuLqOzoizFf378YZBY7WoO59Opm4eX3hbMGigzjZiGBA@mail.gmail.com> <DD927491-2BB7-4D36-987C-B0A406F21A8A@amsl.com>
In-Reply-To: <DD927491-2BB7-4D36-987C-B0A406F21A8A@amsl.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Mon, 01 May 2023 17:55:11 -0700
Message-ID: <CAM4esxT8PMvpcG5smBgfZYdqFuZiKK5XBQwT5agPxna3pH8C+w@mail.gmail.com>
To: Lynne Bartholomew <lbartholomew@amsl.com>
Cc: Yi Huang <huanyi@microsoft.com>, Matt Olson <maolson@microsoft.com>, Praveen Balasubramanian <pravb.ietf@gmail.com>, "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, "tcpm-ads@ietf.org" <tcpm-ads@ietf.org>, "tcpm-chairs@ietf.org" <tcpm-chairs@ietf.org>, "tuexen@fh-muenster.de" <tuexen@fh-muenster.de>, "auth48archive@rfc-editor.org" <auth48archive@rfc-editor.org>
Content-Type: multipart/alternative; boundary="000000000000f6cfea05faab64dc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/xoj6GjCJLWyK20i5EeaZUAAw3QQ>
Subject: Re: [auth48] *[AD] Re: [EXTERNAL] AUTH48: RFC-to-be 9406 <draft-ietf-tcpm-hystartplusplus-14> 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, 02 May 2023 00:55:30 -0000

LGTM

On Mon, May 1, 2023 at 5:37 PM Lynne Bartholomew <lbartholomew@amsl.com>
wrote:

> Dear authors and *AD (Martin),
>
> Authors, we have noted your approvals on the AUTH48 status page:
>
>    https://www.rfc-editor.org/auth48/rfc9406
>
> *Martin, we believe that all updates made during AUTH48 are editorial in
> nature (i.e., not considered technical).  Would you please scan <
> https://www.rfc-editor.org/authors/rfc9406-auth48diff.html> and confirm?
>
> Thank you!
>
> RFC Editor/lb
>
> > On May 1, 2023, at 4:52 PM, Praveen Balasubramanian <
> pravb.ietf@gmail.com> wrote:
> >
> > I also approve. All authors have now approved this proposed document.
> >
> > On Mon, May 1, 2023 at 4:33 PM Matt Olson <maolson@microsoft.com> wrote:
> > I also approve
> >
> >   From: Yi Huang <huanyi@microsoft.com>
> > Sent: Monday, May 1, 2023 4:33 PM
> > To: Lynne Bartholomew <lbartholomew@amsl.com>
> > Cc: pravb.ietf@gmail.com; Matt Olson <maolson@microsoft.com>;
> rfc-editor@rfc-editor.org; tcpm-ads@ietf.org; tcpm-chairs@ietf.org;
> tuexen@fh-muenster.de; Martin Duke <martin.h.duke@gmail.com>;
> auth48archive@rfc-editor.org
> > Subject: Re: [EXTERNAL] AUTH48: RFC-to-be 9406
> <draft-ietf-tcpm-hystartplusplus-14> for your review
>
> >   Ah, I stand corrected. I approve the document, thanks!
>
> > From: Lynne Bartholomew <lbartholomew@amsl.com>
> > Sent: Monday, May 1, 2023 4:19 PM
> > To: Yi Huang <huanyi@microsoft.com>
> > Cc: pravb.ietf@gmail.com <pravb.ietf@gmail.com>; Matt Olson <
> maolson@microsoft.com>; rfc-editor@rfc-editor.org <
> rfc-editor@rfc-editor.org>; tcpm-ads@ietf.org <tcpm-ads@ietf.org>;
> tcpm-chairs@ietf.org <tcpm-chairs@ietf.org>; tuexen@fh-muenster.de <
> tuexen@fh-muenster.de>; Martin Duke <martin.h.duke@gmail.com>;
> auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>
> > Subject: Re: [EXTERNAL] AUTH48: RFC-to-be 9406
> <draft-ietf-tcpm-hystartplusplus-14> for your review   Hi, Yi.  This text
> is not a grammatical error; it is referred to as "subjunctive mood".  It is
> often used in RFCs.
> >
> > If you prefer that subjunctive mood not be used in this document*,
> please let us know, and we will remove any instances of subjunctive mood
> that we find.
> >
> > * This phrase itself is an example of subjunctive mood.
> >
> > Thank you.
> >
> > RFC Editor/lb
> >
> > > On May 1, 2023, at 4:02 PM, Yi Huang <huanyi@microsoft.com> wrote:
> > >
> > > Thanks for adding the street full address.
> > >
> > > In section 4.3, there's a grammatical error that needs to be corrected.
> > > Original:
> > > "It is RECOMMENDED that a HyStart++ implementation use the following"
> > >
> > > Proposal:
> > > "It is RECOMMENDED that a HyStart++ implementation uses the following"
> >
> > > From: Lynne Bartholomew <lbartholomew@amsl.com>
> > > Sent: Monday, May 1, 2023 3:49 PM
> > > To: Yi Huang <huanyi@microsoft.com>
> > > Cc: pravb.ietf@gmail.com <pravb.ietf@gmail.com>; Matt Olson <
> maolson@microsoft.com>; rfc-editor@rfc-editor.org <
> rfc-editor@rfc-editor.org>; tcpm-ads@ietf.org <tcpm-ads@ietf.org>;
> tcpm-chairs@ietf.org <tcpm-chairs@ietf.org>; tuexen@fh-muenster.de <
> tuexen@fh-muenster.de>; Martin Duke <martin.h.duke@gmail.com>;
> auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>
> > > Subject: Re: [EXTERNAL] AUTH48: RFC-to-be 9406
> <draft-ietf-tcpm-hystartplusplus-14> for your review
> > >  Hi, Yi.  No worries, and thank you for this prompt reply as well!
> > >
> > > We have made further updates per your notes below.  Per your address
> listing, we also included "One Microsoft Way".  Please let us know if
> Matt's street address should be different.
> > >
> > > The latest files are posted here.  Please refresh your browser:
> > >
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.txt&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943179446%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bIbXnygnzqXP47anKVD%2BDgd%2B3dVUWUCRDt0CqCifNdQ%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.pdf&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943179446%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lqsRuASAMHO0ikPrlAjUfwzJGiIzDPjm0sOGFmn7BPw%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943179446%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AMzQRY1FOWA12v2P%2Fo6m72P3nb3S4J4AMomJwqr6AlY%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.xml&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943179446%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0h7RETI0luc7PYerAwQEhia0D8ueiuN4sqCQalf3BcE%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-diff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943179446%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GnNFFKV9WAZvOYeLtDm7Dadx8CNOsLGza3gv80Im1Ko%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-rfcdiff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943179446%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eTodmt00lBComOEr%2B1cQ2yranO%2BvhNE%2FPgAkQpYqXJc%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-auth48diff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943179446%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbWJhFxzlGLDy775MC%2FQ7iQ6yjVY4m3iFqpoFyz2AmM%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-lastdiff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943179446%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=kFqrbTHtA8Pxx1hhqXnz1STF4gA8OGxTluY28GouHKQ%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-lastrfcdiff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943179446%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ul7Cw%2BKvLeBFWqHZre8QKOPHcZJQkL1CPAc6YlRijpw%3D&reserved=0
> > >
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-xmldiff1.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=i2tw9qhPz7CyYwzxMsTPG4q%2FrLITMsCIHy5mFABSf7E%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-xmldiff2.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EbNmaX1BRdGDW1RtUa0KP%2BDzUhF3BrlkMn3cTgTl78M%3D&reserved=0
> > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-alt-diff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bVEOEDdCDlA4dCqkVS4ePO67sDBnrK8OZ8nu4Ek6w%2BM%3D&reserved=0
> > >
> > > Thanks again!
> > >
> > > RFC Editor/lb
> > >
> > > > On May 1, 2023, at 3:41 PM, Yi Huang <huanyi@microsoft.com> wrote:
> > > >
> > > > Oh, my apologies. I pasted it in the wrong place.
> > > >
> > > >     • "HyStart exit" should be changed to "slow start exit", which
> refers to the pseudocode "exit slow start and enter CSS".
> > > >     • ECN is Explicit Congestion Notification.
> > > > One minor issue in "Authros' Addresses" section, could you please
> add "Redmond, WA 98052" to Matt Olson's address to be consistent with other
> authors' info?
> > > > Original:
> > > >    Matt Olson
> > > >    Microsoft
> > > >    Phone: +1 425 538 8598
> > > >    Email: maolson@microsoft.com
> > > >
> > > > Proposal:
> > > >
> > > >    Matt Olson
> > > >    Microsoft
> > > >    Redmond, WA 98052
> > > >    Phone: +1 425 538 8598
> > > >    Email: maolson@microsoft.com
> > > >
> > > > ---------------------------------------------------
> > > > Thanks,
> > > > Yi
> > > >
> > > > From: Lynne Bartholomew <lbartholomew@amsl.com>
> > > > Sent: Monday, May 1, 2023 3:21 PM
> > > > To: Yi Huang <huanyi@microsoft.com>
> > > > Cc: pravb.ietf@gmail.com <pravb.ietf@gmail.com>; Matt Olson <
> maolson@microsoft.com>; rfc-editor@rfc-editor.org <
> rfc-editor@rfc-editor.org>; tcpm-ads@ietf.org <tcpm-ads@ietf.org>;
> tcpm-chairs@ietf.org <tcpm-chairs@ietf.org>; tuexen@fh-muenster.de <
> tuexen@fh-muenster.de>; Martin Duke <martin.h.duke@gmail.com>;
> auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>
> > > > Subject: Re: [EXTERNAL] AUTH48: RFC-to-be 9406
> <draft-ietf-tcpm-hystartplusplus-14> for your review
> > > >  [You don't often get email from lbartholomew@amsl.com. Learn why
> this is important athttps://aka.ms/LearnAboutSenderIdentification ]
> > > >
> > > > Hi, Yi.  Thank you for your prompt reply!
> > > >
> > > > We have updated this document per your notes below.
> > > >
> > > > A couple quick follow-up items for you:
> > > >
> > > > It appears that our question 4)b) (re. not finding
> "cssBaselineMinRtt" mentioned in any other RFC) was answered by this reply
> to question 5):
> > > >
> > > > >> 5) <!-- [rfced] Section 4.2:  We defined "ECN" as "Explicit
> Congestion
> > > > >> Notification" for ease of the reader.  If this definition is
> > > > >> incorrect, please provide the correct definition of "ECN".
> > > > >>
> > > > >> Original:
> > > > >>  If loss or ECN-marking is observed anytime during standard slow
> start
> > > > >>  or CSS, enter congestion avoidance by setting ssthresh to current
> > > > >>  cwnd.
> > > > >>
> > > > >> Currently:
> > > > >>  If loss or Explicit Congestion Notification (ECN) marking is
> observed
> > > > >>  at any time during standard slow start or CSS, enter congestion
> > > > >>  avoidance by setting the ssthresh to the current cwnd. -->
> > > > >
> > > > > It's referred a few paragraphs below.
> > > > >
> > > > > In "For CSS rounds where at least N_RTT_SAMPLE RTT samples have
> been obtained, check if current round's minRTT drops below baseline
> indicating that HyStart exit was spurious:", the word, "baseline" refers to
> cssBaselineMinRtt. I suggest we change the line to "For CSS rounds where at
> least N_RTT_SAMPLE RTT samples have been obtained, check if current round's
> minRTT drops below the baseline, cssBaselineMinRtt, indicating that HyStart
> exit was spurious:"?
> > > >
> > > > First, apologies for not spotting this earlier and asking about it:
> Should "HyStart exit" be "HyStart++ exit"?
> > > >
> > > > Second, please let us know if our expansion of "ECN" as "Explicit
> Congestion Notification" is correct.  If it's not correct, please let us
> know how it should be defined.
> > > >
> > > > = = = = =
> > > >
> > > > The latest files are posted here (please refresh your browser):
> > > >
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.txt&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WiPoEksrt7XIvspHenFHWC9epCqzdP83PZmh%2BMKaVEo%3D&reserved=0
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.pdf&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CwnZ9%2FuI57KomRwOh7npUioST7PQqhbXVWdjtPQgc%2FE%3D&reserved=0
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FMTAFD%2BFr%2B9sAxf9MIZFp3yXP%2BaA954S5S%2FypmxXuNg%3D&reserved=0
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.xml&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nPZb7EMUPkhSCQR0ZXWhSr6zAatrDE6Fm%2Fk61bD516I%3D&reserved=0
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-diff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oDzh%2FHqQblMe%2Ff6mlC8NU%2F9gEJUx83cB6y1MoMBejXQ%3D&reserved=0
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-rfcdiff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lrQ1cm2lFGb1JM8Iwayr%2BWhE0Tg4FoA7VojhMiCe6z8%3D&reserved=0
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-auth48diff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pX6L8O65mRdrhEV4na2qsURTiDKkTA4ubCjzCRCUnEI%3D&reserved=0
> > > >
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-alt-diff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bVEOEDdCDlA4dCqkVS4ePO67sDBnrK8OZ8nu4Ek6w%2BM%3D&reserved=0
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-xmldiff1.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=i2tw9qhPz7CyYwzxMsTPG4q%2FrLITMsCIHy5mFABSf7E%3D&reserved=0
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-xmldiff2.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EbNmaX1BRdGDW1RtUa0KP%2BDzUhF3BrlkMn3cTgTl78M%3D&reserved=0
> > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-alt-diff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bVEOEDdCDlA4dCqkVS4ePO67sDBnrK8OZ8nu4Ek6w%2BM%3D&reserved=0
> > > >
> > > > Thanks again!
> > > >
> > > > RFC Editor/lb
> > > >
> > > > > On Apr 28, 2023, at 8:54 PM, Yi Huang <huanyi@microsoft.com>
> wrote:
> > > > >
> > > > > Hi Lynne,
> > > > >
> > > > > Thanks a lot for reviewing and editing the doc. I have inlined our
> answers.
> > > > >
> > > > > Thanks,
> > > > > Yi
> > > > >
> > > > >
> > > > > From: Lynne Bartholomew <lbartholomew@amsl.com>
> > > > > Sent: Thursday, April 27, 2023 3:22 PM
> > > > > To: pravb.ietf@gmail.com <pravb.ietf@gmail.com>; Yi Huang <
> huanyi@microsoft.com>; Matt Olson <maolson@microsoft.com>
> > > > > Cc: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>;
> tcpm-ads@ietf.org <tcpm-ads@ietf.org>; tcpm-chairs@ietf.org <
> tcpm-chairs@ietf.org>; tuexen@fh-muenster.de<tuexen@fh-muenster.de>;
> Martin Duke <martin.h.duke@gmail.com>; auth48archive@rfc-editor.org<
> auth48archive@rfc-editor.org>
> > > > > Subject: [EXTERNAL] Re: AUTH48: RFC-to-be 9406
> <draft-ietf-tcpm-hystartplusplus-14> for your review
> > > > >  [Some people who received this message don't often get email from
> lbartholomew@amsl.com. Learn why this is important athttps://
> aka.ms/LearnAboutSenderIdentification ]
> > > > >
> > > > > Authors,
> > > > >
> > > > > While reviewing this document during AUTH48, please resolve (as
> necessary) the following questions, which are also in the XML file.
> > > > >
> > > > > 1) <!-- [rfced] Document title, Abstract, and Introduction:  As
> the term
> > > > > "HyStart" has not been used in any published RFCs to date and the
> > > > > word "hybrid" is not used in this document, would it be helpful to
> > > > > define HyStart++ for readers?
> > > > >
> > > > > Original:
> > > > >  HyStart++: Modified Slow Start for TCP
> > > > > ...
> > > > >  This document describes HyStart++, a simple modification to the
> slow
> > > > >  start phase of congestion control algorithms.
> > > > > ...
> > > > >  HyStart++ uses increase in round-trip delay as a signal to exit
> slow
> > > > >  start before potential packet loss occurs as a result of
> overshoot.
> > > > >  This is one of two algorithms specified in [HyStart].
> > > > >
> > > > > Perhaps:
> > > > >  HyStart++: Modified "Hybrid Start" Slow Start Algorithm for TCP
> > > > > ...
> > > > >  This document describes HyStart++, a simple modification to the
> > > > >  "Hybrid Start" slow start phase of congestion control algorithms.
> > > > > ...
> > > > >  HyStart++, which is a modified "Hybrid Start" slow start
> algorithm,
> > > > >  uses an increase in round-trip delay as a signal to exit slow
> > > > >  start before potential packet loss occurs as a result of
> > > > >  overshoot.  This is one of two algorithms specified in [HyStart].
> -->
> > > > >
> > > > > How about in the introduction we modify seocnd para as:
> > > > > HyStart++ builds upon Hybrid Start (HyStart) originally described
> in [HyStart]. HyStart++ uses increase in round-trip delay as a signal to
> exit slow start before potential packet loss occurs as a result of
> overshoot.
> > > > >
> > > > >
> > > > > 2) <!-- [rfced] Section 1:  In this current text, "This is one of
> two
> > > > > algorithms" appears to refer to HyStart++.  However, we do not see
> > > > > HyStart++ mentioned anywhere in [HyStart].  Also, we only see one
> > > > > algorithm defined in [HyStart]:  "We propose a new slow start
> > > > > algorithm, called Hybrid Start (HyStart) ...").
> > > > >
> > > > > How can this text be clarified for readers?  For example, would
> > > > > "[HyStart] specifies two algorithms (a "Delay Increase" algorithm
> and
> > > > > an "Inter-Packet Arrival" algorithm) to be run in parallel to
> detect
> > > > > that the sending rate has reached capacity" from Section 4.1 also
> > > > > apply to this text here in Section 1?
> > > > >
> > > > > Original (the previous sentence and the next sentence are included
> > > > >    for context):
> > > > >  HyStart++ uses increase in round-trip delay as a signal to exit
> slow
> > > > >  start before potential packet loss occurs as a result of
> overshoot.
> > > > >  This is one of two algorithms specified in [HyStart].  After the
> slow
> > > > >  start exit, a new Conservative Slow Start (CSS) phase is used to
> > > > >  determine whether the slow start exit was premature and to resume
> > > > >  slow start. -->
> > > > >
> > > > > To be clear, Hystart++ itself is not mentioned in [HyStart].
> Hystart++ uses the "delay increase" algorithm in [Hystart] for detecting a
> safe exit point for slow start. Can we just rephrase " This is one of two
> algorithms specified in [HyStart]" to "This is one of two algorithms
> specified in [HyStart] for finding a safe exit point for slow start."?
> > > > >
> > > > > 3) <!-- [rfced] Please review the "type" attribute of each
> sourcecode
> > > > > element in the XML file to ensure correctness.  If you would like
> to
> > > > > make any changes and the current list of preferred values for
> "type"
> > > > > as listed on <
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fmaterials%2Fsourcecode-types.txt&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RKQUNkCMZNprVcoHwY6HQudEdVMLBXZqiQ1fezLvFJU%3D&reserved=0
> >
> > > > > does not contain an applicable type, then feel free to let us know.
> > > > > Also, it is acceptable to leave the "type" attribute not set. -->
> > > > >
> > > > > Can we just not set the "type" attribute? The pseudocode doesn't
> map to a real programming language.
> > > > >
> > > > > 4) <!-- [rfced] Section 4.2:
> > > > >
> > > > > a) The following two lines are too long for the text output.  We
> get
> > > > > the following warning:
> > > > >
> > > > > Warning: Too long line found (L207), 7 characters longer than 72
> characters:
> > > > >      Compute an RTT Threshold clamped between MIN_RTT_THRESH and
> MAX_RTT_THRESH
> > > > > Warning: Too long line found (L208), 20 characters longer than 72
> characters:
> > > > >      RttThresh = max(MIN_RTT_THRESH, min(lastRoundMinRTT /
> MIN_RTT_DIVISOR, MAX_RTT_THRESH))
> > > > >
> > > > > Please let us know where line breaks should be placed.
> > > > >
> > > > > Original (the line break after "DIVISOR," is introduced by
> > > > >   our Terminal-window-line-length constraint):
> > > > >  Compute a RTT Threshold clamped between MIN_RTT_THRESH and
> MAX_RTT_THRESH
> > > > >  RttThresh = max(MIN_RTT_THRESH, min(lastRoundMinRTT /
> MIN_RTT_DIVISOR, MAX_RTT_THRESH))
> > > > >
> > > > > Possibly:
> > > > >  Compute an RTT Threshold clamped between MIN_RTT_THRESH and
> > > > >    MAX_RTT_THRESH
> > > > >  RttThresh = max(MIN_RTT_THRESH,
> > > > >    min(lastRoundMinRTT / MIN_RTT_DIVISOR, MAX_RTT_THRESH))
> > > > >
> > > > > b) We do not see "cssBaselineMinRtt" used in any RFC.  Will this
> > > > > parameter be clear to readers?
> > > > >
> > > > > Original:
> > > > >  cssBaselineMinRtt = currentRoundMinRTT
> > > > > ...
> > > > >  if (currentRoundMinRTT < cssBaselineMinRtt)
> > > > >    cssBaselineMinRtt = infinity -->
> > > > >
> > > > > I think we can remove "Compute an RTT Threshold clamped between
> MIN_RTT_THRESH and MAX_RTT_THRESH" as it's just an explanation of the
> following line, which is clear enough. The suggested line break looks good
> to me.
> > > > >
> > > > > 5) <!-- [rfced] Section 4.2:  We defined "ECN" as "Explicit
> Congestion
> > > > > Notification" for ease of the reader.  If this definition is
> > > > > incorrect, please provide the correct definition of "ECN".
> > > > >
> > > > > Original:
> > > > >  If loss or ECN-marking is observed anytime during standard slow
> start
> > > > >  or CSS, enter congestion avoidance by setting ssthresh to current
> > > > >  cwnd.
> > > > >
> > > > > Currently:
> > > > >  If loss or Explicit Congestion Notification (ECN) marking is
> observed
> > > > >  at any time during standard slow start or CSS, enter congestion
> > > > >  avoidance by setting the ssthresh to the current cwnd. -->
> > > > >
> > > > > It's referred a few paragraphs below.
> > > > >
> > > > > In "For CSS rounds where at least N_RTT_SAMPLE RTT samples have
> been obtained, check if current round's minRTT drops below baseline
> indicating that HyStart exit was spurious:", the word, "baseline" refers to
> cssBaselineMinRtt. I suggest we change the line to "For CSS rounds where at
> least N_RTT_SAMPLE RTT samples have been obtained, check if current round's
> minRTT drops below the baseline, cssBaselineMinRtt, indicating that HyStart
> exit was spurious:"?
> > > > >
> > > > > 6) <!-- [rfced] Section 5:  We changed "As of February 2023" to
> "At the
> > > > > time of this writing".  If this is incorrect, please provide
> > > > > clarifying text.
> > > > >
> > > > > Original:
> > > > >  As of February 2023, HyStart++ as described in this document has
> been
> > > > >  default enabled for all TCP connections in the Windows operating
> > > > >  system for over two years with pacing disabled and an actual L =
> 8.
> > > > >
> > > > > Currently:
> > > > >  At the time of this writing, HyStart++ as described in this
> document
> > > > >  has been default enabled for all TCP connections in the Windows
> > > > >  operating system for over two years with pacing disabled and an
> > > > >  actual L = 8. -->
> > > > > Correct
> > > > >
> > > > >
> > > > > 7) <!-- [rfced] Section 5:  Will the meaning of "HyStart++ draft
> 01" be
> > > > > clear to readers?  If not, please provide clarifying text.
> > > > >
> > > > > Original:
> > > > >  In an A/B test where we compare HyStart++ draft 01 to traditional
> > > > >  slow start across a large Windows device population, out of 52
> > > > >  billion TCP connections, 0.7% of connections move from 1 RTO to 0
> > > > >  RTOs and another 0.7% connections move from 2 RTOs to 1 RTO with
> > > > >  HyStart++. -->
> > > > >
> > > > > I would say we remove draft 01, as its not useful to the reader to
> implement an earlier version of the algorithm:
> > > > >
> > > > > "In an A/B test where we compared an implementation of HyStart++
> (based on an earlier draft of this document) to traditional
> > > > >  slow start across a large Windows device population,"
> > > > >
> > > > > 8) <!-- [rfced] Please review the "Inclusive Language" portion of
> the
> > > > > online Style Guide at
> > > > > <
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BffBQQoCRMttdZUU7TUrwhaABvtPjAblARYCeZud298%3D&reserved=0
> >,
> > > > > and let us know if any changes are needed.
> > > > >
> > > > > In addition, please consider whether "traditional" should be
> updated
> > > > > for clarity.  In this document, could "standard slow start" (as
> seen
> > > > > in Section 4.2) be used instead of "traditional slow start"?
> > > > >
> > > > > While the NIST website
> > > > > (<
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nist.gov%2Fnist-research-library%2Fnist-technical-series-publications-author-instructions%23table1&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wBh7Xie74HQcppP7%2F72rQ03M6cl14Q4tSl1TeOGhA4Q%3D&reserved=0
> >)
> > > > > indicates that this term is potentially biased, it is also
> ambiguous.
> > > > > "Tradition" is a subjective term, as it is not the same for
> everyone. -->
> > > > >
> > > > > Agreed. Standard slow start is better.
> > > > >
> > > > > 9) <!-- [rfced] The following terms were used inconsistently in
> this
> > > > > document.  We chose to use the latter forms.  Please let us know
> any
> > > > > objections.
> > > > >
> > > > >  Hystart++ (6 instances) / HyStart++ (23 instances) (per [HyStart])
> > > > >  INFINITY (1 instance) / infinity (11 instances) -->
> > > > >
> > > > > The latter forms are better, HyStart++ and infinity.
> > > > >
> > > > > Thank you.
> > > > >
> > > > > RFC Editor/lb
> > > > >
> > > > > > On Apr 27, 2023, at 3:12 PM, rfc-editor@rfc-editor.org wrote:
> > > > > >
> > > > > > *****IMPORTANT*****
> > > > > >
> > > > > > Updated 2023/04/27
> > > > > >
> > > > > > RFC Author(s):
> > > > > > --------------
> > > > > >
> > > > > > Instructions for Completing AUTH48
> > > > > >
> > > > > > Your document has now entered AUTH48.  Once it has been reviewed
> and
> > > > > > approved by you and all coauthors, it will be published as an
> RFC.
> > > > > > If an author is no longer available, there are several remedies
> > > > > > available as listed in the FAQ (
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Ffaq%2F&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=N8sMcSfeH42MKADp5a1Aq0hOTu%2F3to%2FnCf5h2EipMaA%3D&reserved=0
> ).
> > > > > >
> > > > > > You and you coauthors are responsible for engaging other parties
> > > > > > (e.g., Contributors or Working Group) as necessary before
> providing
> > > > > > your approval.
> > > > > >
> > > > > > Planning your review
> > > > > > ---------------------
> > > > > >
> > > > > > Please review the following aspects of your document:
> > > > > >
> > > > > > *  RFC Editor questions
> > > > > >
> > > > > >   Please review and resolve any questions raised by the RFC
> Editor
> > > > > >   that have been included in the XML file as comments marked as
> > > > > >   follows:
> > > > > >
> > > > > >   <!-- [rfced] ... -->
> > > > > >
> > > > > >   These questions will also be sent in a subsequent email.
> > > > > >
> > > > > > *  Changes submitted by coauthors
> > > > > >
> > > > > >   Please ensure that you review any changes submitted by your
> > > > > >   coauthors.  We assume that if you do not speak up that you
> > > > > >   agree to changes submitted by your coauthors.
> > > > > >
> > > > > > *  Content
> > > > > >
> > > > > >   Please review the full content of the document, as this cannot
> > > > > >   change once the RFC is published.  Please pay particular
> attention to:
> > > > > >   - IANA considerations updates (if applicable)
> > > > > >   - contact information
> > > > > >   - references
> > > > > >
> > > > > > *  Copyright notices and legends
> > > > > >
> > > > > >   Please review the copyright notice and legends as defined in
> > > > > >   RFC 5378 and the Trust Legal Provisions
> > > > > >   (TLP –
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrustee.ietf.org%2Flicense-info%2F&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ywrMylsbFnJJAZdFJ1Qr9T7sXLfyyCFFbN2KrYujyJM%3D&reserved=0
> ).
> > > > > >
> > > > > > *  Semantic markup
> > > > > >
> > > > > >   Please review the markup in the XML file to ensure that
> elements of
> > > > > >   content are correctly tagged.  For example, ensure that
> <sourcecode>
> > > > > >   and <artwork> are set correctly.  See details at
> > > > > >   <
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthors.ietf.org%2Frfcxml-vocabulary&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iTZmrQmL6D1d1nbtqE1%2FFh3OTftXDXtKrB5xHsmZxC0%3D&reserved=0
> >.
> > > > > >
> > > > > > *  Formatted output
> > > > > >
> > > > > >   Please review the PDF, HTML, and TXT files to ensure that the
> > > > > >   formatted output, as generated from the markup in the XML
> file, is
> > > > > >   reasonable.  Please note that the TXT will have formatting
> > > > > >   limitations compared to the PDF and HTML.
> > > > > >
> > > > > >
> > > > > > Submitting changes
> > > > > > ------------------
> > > > > >
> > > > > > To submit changes, please reply to this email using ‘REPLY ALL’,
> as all
> > > > > > the parties CCed on this message need to see your changes.  The
> parties
> > > > > > include:
> > > > > >
> > > > > >   *  your coauthors
> > > > > >
> > > > > >   *  rfc-editor@rfc-editor.org (the RPC team)
> > > > > >
> > > > > >   *  other document participants, depending on the stream (e.g.,
> > > > > >      IETF Stream participants are your working group chairs, the
> > > > > >      responsible ADs, and the document shepherd)
> > > > > >
> > > > > >   *  auth48archive@rfc-editor.org, which is a new archival
> mailing list
> > > > > >      to preserve AUTH48 conversations; it is not an active
> discussion
> > > > > >      list:
> > > > > >
> > > > > >     *  More info:
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh-4Q9l2USxIAe6P8O4Zc&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uz8F7ELgKKaO7fFUPyt9P3hS%2B1eFSjkzJ0dQeBScl%2FE%3D&reserved=0
> > > > > >
> > > > > >     *  The archive itself:
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=edD%2B8AyRXV3AbVz%2FgHe7dXsRQFASr4T0XXnMjnLlpkw%3D&reserved=0
> > > > > >
> > > > > >     *  Note: If only absolutely necessary, you may temporarily
> opt out
> > > > > >        of the archiving of messages (e.g., to discuss a
> sensitive matter).
> > > > > >        If needed, please add a note at the top of the message
> that you
> > > > > >        have dropped the address.  When the discussion is
> concluded,
> > > > > >        auth48archive@rfc-editor.org will be re-added to the CC
> list and
> > > > > >        its addition will be noted at the top of the message.
> > > > > >
> > > > > > You may submit your changes in one of two ways:
> > > > > >
> > > > > > An update to the provided XML file
> > > > > > — OR —
> > > > > > An explicit list of changes in this format
> > > > > >
> > > > > > Section # (or indicate Global)
> > > > > >
> > > > > > OLD:
> > > > > > old text
> > > > > >
> > > > > > NEW:
> > > > > > new text
> > > > > >
> > > > > > You do not need to reply with both an updated XML file and an
> explicit
> > > > > > list of changes, as either form is sufficient.
> > > > > >
> > > > > > We will ask a stream manager to review and approve any changes
> that seem
> > > > > > beyond editorial in nature, e.g., addition of new text, deletion
> of text,
> > > > > > and technical changes.  Information about stream managers can be
> found in
> > > > > > the FAQ.  Editorial changes do not require approval from a
> stream manager.
> > > > > >
> > > > > >
> > > > > > Approving for publication
> > > > > > --------------------------
> > > > > >
> > > > > > To approve your RFC for publication, please reply to this email
> stating
> > > > > > that you approve this RFC for publication.  Please use ‘REPLY
> ALL’,
> > > > > > as all the parties CCed on this message need to see your
> approval.
> > > > > >
> > > > > >
> > > > > > Files
> > > > > > -----
> > > > > >
> > > > > > The files are available here:
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.xml&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nPZb7EMUPkhSCQR0ZXWhSr6zAatrDE6Fm%2Fk61bD516I%3D&reserved=0
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FMTAFD%2BFr%2B9sAxf9MIZFp3yXP%2BaA954S5S%2FypmxXuNg%3D&reserved=0
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.pdf&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CwnZ9%2FuI57KomRwOh7npUioST7PQqhbXVWdjtPQgc%2FE%3D&reserved=0
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.txt&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WiPoEksrt7XIvspHenFHWC9epCqzdP83PZmh%2BMKaVEo%3D&reserved=0
> > > > > >
> > > > > > Diff files of the text:
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-diff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oDzh%2FHqQblMe%2Ff6mlC8NU%2F9gEJUx83cB6y1MoMBejXQ%3D&reserved=0
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-rfcdiff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943335675%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lrQ1cm2lFGb1JM8Iwayr%2BWhE0Tg4FoA7VojhMiCe6z8%3D&reserved=0
> (side by side)
> > > > > >
> > > > > > For your convenience, we have also created an alt-diff file that
> will allow you to
> > > > > > more easily view changes where text has been deleted or moved:
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-alt-diff.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943491897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Sy1kYKz8HL1ueLYcfeIg7LjATAJepJ8OHREycpc0kBQ%3D&reserved=0
> > > > > >
> > > > > > Diffs of the XML:
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-xmldiff1.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943491897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gFm0L9LuT5PftDfvQ2JWGE6DhC%2BZK8yLfByx8Wl2Pqg%3D&reserved=0
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406-xmldiff2.html&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943491897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=X3aaC4mv2D7LZDaDcWdCIMD746kJOXKvVk5cuSKDzlo%3D&reserved=0
> > > > > >
> > > > > > The following files are provided to facilitate creation of your
> own
> > > > > > diff files of the XML.
> > > > > >
> > > > > > Initial XMLv3 created using XMLv2 as input:
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.original.v2v3.xml&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943491897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5bCk5YFER0E3t8Ovd2%2FQ53O9hE85oLYYD%2Fc8KgPFuwQ%3D&reserved=0
> > > > > >
> > > > > > XMLv3 file that is a best effort to capture v3-related format
> updates
> > > > > > only:
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9406.form.xml&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943491897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Zmbwi1l9HwXRGpsvJ1a7RsRQqxvMaHm9U9QPRFiVjpE%3D&reserved=0
> > > > > >
> > > > > >
> > > > > > Tracking progress
> > > > > > -----------------
> > > > > >
> > > > > > The details of the AUTH48 status of your document are here:
> > > > > >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9406&data=05%7C01%7Chuanyi%40microsoft.com%7C9fa1cceabbbe4109399408db4a9a8777%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638185800943491897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=54PL%2FXuYK38lXIcyVeugJGY1BbXuhaVbJrpvhobJxl4%3D&reserved=0
> > > > > >
> > > > > > Please let us know if you have any questions.
> > > > > >
> > > > > > Thank you for your cooperation.
> > > > > >
> > > > > > RFC Editor
> > > > > >
> > > > > > --------------------------------------
> > > > > > RFC9406 (draft-ietf-tcpm-hystartplusplus-14)
> > > > > >
> > > > > > Title            : HyStart++: Modified Slow Start for TCP
> > > > > > Author(s)        : P. Balasubramanian, Y. Huang, M. Olson
> > > > > > WG Chair(s)      : Yoshifumi Nishida, Michael Tüxen, Ian Swett
> > > > > >
> > > > > > Area Director(s) : Martin Duke, Zaheduzzaman Sarker
> > > > > >
> >
> >
>
>
>