This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 14
Change introductory text to reflect deployment experience #39
Labels
editorial
Editorial change relative to RFC8312 or earlier bis versions
Comments
larseggert
added
editorial
Editorial change relative to RFC8312 or earlier bis versions
help wanted
Looking for someone resolve this issue
labels
Feb 2, 2021
Thanks, Lars. I can help to revise the text later next week, is it ok? |
goelvidhi
added
editorial
Editorial change relative to RFC8312 or earlier bis versions
and removed
editorial
Editorial change relative to RFC8312 or earlier bis versions
help wanted
Looking for someone resolve this issue
labels
Feb 4, 2021
@lisongxu I just wanted to check with you if you'd have time to work on it? :-) |
Mon, Feb 22 is the cutoff date for i-D submissions for IETF-110. If we're not ready to submit by then, we'll have to wait until mid-March. Which isn't a huge issue, but since we're going to ask for WG adoption, it would be nice to have a more up-to-date I-D to discuss. |
I see. I will try my best. Thanks
Lisong
…________________________________
From: Lars Eggert <notifications@github.com>
Sent: Tuesday, February 16, 2021 2:50 AM
To: NTAP/rfc8312bis <rfc8312bis@noreply.github.com>
Cc: Lisong Xu <xu@unl.edu>; Mention <mention@noreply.github.com>
Subject: Re: [NTAP/rfc8312bis] Change introductory text to reflect deployment experience (#39)
Non-NU Email
________________________________
Mon, Feb 22 is the cutoff date for i-D submissions for IETF-110. If we're not ready to submit by then, we'll have to wait until mid-March. Which isn't a huge issue, but since we're going to ask for WG adoption, it would be nice to have a more up-to-date I-D to discuss.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_NTAP_rfc8312bis_issues_39-23issuecomment-2D779682893&d=DwMCaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8Eft-wwo&r=8GgbmpxpPRnPS9z8_jUQhw&m=hSUqqOiPfh2Q1N6MuR2Ij_Ox6ZKD-HzrODl1-Istx0g&s=1lbItThazxoaa6MwBWONmQOg-GF9RhrjJ7vhEK1LWYg&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ACPRVIJ2MY375Q7JVZCWOPDS7IWVLANCNFSM4W6KNQJQ&d=DwMCaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8Eft-wwo&r=8GgbmpxpPRnPS9z8_jUQhw&m=hSUqqOiPfh2Q1N6MuR2Ij_Ox6ZKD-HzrODl1-Istx0g&s=Rb4Gdva2BCz8mFAj60V9sTJh2uHK8qaQPSHjCD-WT5I&e=>.
|
Merged
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The abstract, introduction and other text throughout the document need to be updated to reflect the significantly broader deployment experience CUBIC has seen since RFC8312 was published. At that time, it had been the default for Linux for years, but since then, it's also been the default for Windows and Apple stacks.
The text was updated successfully, but these errors were encountered: