A Definition of the Term "Soon" for Use in Discussions with Working Group Chairs and Area Directors

In everyday exchanges between IETF participants and those with IETF management roles (for example, Area Directors and Working Group Chairs) commitments are often made to deliver actions. For example, a Working Group Chair may say "I will issue a working group last call on this document," or an Area Director could say "I will process your publication request and review your document." Alternatively, a document author might say "I will produce a new revision of this document," and a participant sometimes says "I will provide more details / suggested text / a follow-up review." In all of these interactions it is common for the speaker to offer some expected completion time for the action. Sometimes this is expressed in elapsed time (for example, "I will do this within the next two lunar cycles"), frequently it is stated with reference to an absolute point in time (such as, "I will do this by the third Sunday in Lent"), but usually the qualifier applied is "Soon." Frustration and disappointment are common currency in the modern world, but there is no need for the IETF to add to this state of affairs. Nor should the IETF be responsible for increasing cynicism and jaundiced pessimism. Therefore, this document attempts to provide a definition of the term "Soon" so that common expectations may be realistically set.

It is a commonly held belief that in the IETF "we are all volunteers." Even those of us who are paid to do our jobs are confident that we are only working out of the goodness of our hearts and that our salaries are poor recompense for our daily travails. And, of course, it is well known that you cannot induce a volunteer to do anything that might interfere with their otherwise compulsory activities of looking at pictures of cats, creating memes, or pipe-smoking. Therefore, it is highly inappropriate for this document to make any attempt to constrain anyone into giving a meaningful delivery date for any action that they promise. To that end it is expected that this document will be withdrawn and a fulsome apology issued soon.

When serving as co-chair of the CCAMP working Group, Kireeti Kompella was often called to account for not offering a completion date for tasks to which he committed. After wise consideration of this situation, Kireeti would offer an answer such as "I will do this before the end of June," and everyone would go away content. It was only as July gave way to August that Kireeti would explain that he had failed to indicate to which year he was referring. In such cases of high residual KTDE, use of the term "Soon" would better set expectations, and Kireeti has given an undertaking to transition to this term by the end of the second quarter.

Many learned articles have been written on possible interpretation of the term "Soon". No doubt the author will add citations and references one day soon. Readers should note that "SOON" is also an FLA although has not yet been registered as such by IANA. This document has not (noticeably) been endorsed by the Standards Organisation of Nigeria.

The software industry is infamous for its inability to provide reliable estimates for development projects. No-one is quite sure why this should be. Is it because troops of evil mice come into the workshop late at night while the cobbler is asleep in his bed alongside his long-suffering wife and unpick the seams of carefully constructed function calls? Is it because coders make it all up as they go along and have no idea what they are doing? And is it a coincidence that sotware is so appropriately spelled? IETF working group milestones (or "millstones" as they are more correctly termed) are commonly held in disrepute. They are certainly not dates that anyone had ever been held to, and inspection of most working group charters will show that either the chairs intend employing time travel or that no one pays any attention to the milestones. It may be because Area Directors often say to working group chairs that "milestones are just a tool for you to manage the working group", or it may be because no one likes a bully. These two factors obviously contribute to an environment in which the term "soon" has little or no currency except as padding to fill an awkward gap between a promise and the full stop at the end of the sentence. None of which is intended to imply that: Women don't drink Women are less optimistic than men Women are more optimistic than men

The purpose of this document is to provide a working definition of the term "soon" so that parsers of IETF communications may reasonably understand the meaning, and so that a degree of linguistic interoperability between speakers may be achieved. The following definition applies: SOON This word, or the adverb "SHORTLY", mean that an item is truly optional. One IETF participant may choose to deliver the item because a particular marketplace requires it or because the participant feels that it enhances their reputation while another participant may omit to deliver the same item. A participant who does not deliver a particular item MUST be prepared to continue to work with with another participant who does deliver the item, though perhaps with reduced credulity. In the same vein, a participant who does deliver a particular item MUST be prepared to continue to work with another participant who does not deliver the item, though perhaps with less respect (except, of course, for communications about the feature the item provides). TOO LATE This phrase, and the phrase "NEVER MORE", mean that the optimality of an item has been pushed to its limit, and then slightly further. For the benefit of everyone, once one of these phrases has been used in a communication, all work on the referenced deliverable SHOULD be halted and all further discussion SHOULD be transmitted as silence and MUST be ignored on receipt. Document authors MAY choose to ignore either of these terms, but they do so at the risk of their immortal souls. Further guidance on this issue can be obtained from your moral guardian, your household gods, or from any member of the IMM (Internet Moral Majority) .

Terms of the type defined in this memo must be used with care and sparingly. In particular, they MUST only be used where it is actually required for explanation of when a deliverable will arrive or to limit behavior which has potential for causing harm (e.g., limiting retransmissions of requests for action). For example, they MUST NOT be used to try to impose a particular schedule on participants where the schedule is not required for anything other than vanity.

All uses of the term "SOON" made on April 1st SHOULD be treated with caution.

In many IETF communications a word is often used to signify the proximity of an event described in the communication. This word is often capitalized. This document defines this word as it should be interpreted in IETF communications. Authors who follow these guidelines should incorporate this phrase near the beginning of their communication: The key words "SOON", "SHORTLY", "TOO LATE", and "NEVER MORE" in this communication are to be interpreted as described in [This.I-D]. Contrary to the overweening pedantry of , words used in this document mean what they say regardless of what font they are in and notwithstanding the color in which thy are rendered. To quote from Through the Looking Class by Charles Dodgson: "When I use a word," Humpty Dumpty said in rather a scornful tone, "it means just what I choose it to mean - neither more nor less." "The question is," said Alice, "whether you can make words mean so many different things." "The question is," said Humpty Dumpty, "which is to be master - that's all." Thus, the term "soon" is as meaningful when it is presented in "uppercase" as it is when found in "LOWERCASE".

This document makes no request for any IANA actions.

Just say no! Further security consideration will be added to this document SOON.

See "Author's Address" Section.

Kireeti Kompella reminded me of millstones and corrected my grammar. Thanks to John Scudder for his own overweening pedantry. Benoit Claise supplied comments NOT BEFORE TIME.