Branch: refs/heads/RPC-edits
Home: https://github.com/rfc-editor/AUTH48-rfc9971
Commit: 2dd2b641165b12225a42732256c8c9ee2eade201
https://github.com/rfc-editor/AUTH48-rfc9971/commit/2dd2b641165b12225a42732256c8c9ee2eade201
Author: Vratko Polak <[email protected]>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Fixes #26
+ Minor edits as noticed.
+ Verified capitalization of Binary Search:
++ Most occurences are capitalized to point to the section.
++ Only within that section the generic (lower case) meaning is used.
+ Verified capitalization of the rest of Search instances:
++ Capitalized when related to MLRsearch:
+++ Goal/Duration/Result.
+++ When referring to the active place of MLRsearch procedure.
++ Lowercase when referring to non-MLRsearch procedures:
+++
throughput/precision/procedure/load/algorithm/single/mechanics/implementation.
+++ When used as a verb.
+ Verified capitalization of Result:
++ Capitalize when referring to Trial/Goal/Search result.
++ Except in introductory text to Regular/Irregular when attributes are not
defined yet.
++ Results of test/benchmark/search/throughput/goal/classification remain lower
case.
++ Exception: "results of those Trials".
+ Verified capitalization of Bound:
++ Upper and Lower (Relevant or not) capitalized iff referring to MLRsearch
specification.
++ Lowercase when referring to general searches (usually binary).
+- Next time I will give up and create a section for "Relevant Bounds".
+ Partially verified capitalization of Load:
++ Lowercase when related to:
+++ search, non-constant, average load (within trial), largest/different,
uni-/bi-directional.
++ Capitalized when related to MLRsearch specification:
+++ Trial Load, Load, Load selection, Load Classification, Load terms,
per-interface Load, Max Load, Min Load.
+- Capitalized also for some external definitions:
+-- Intended Load, Offered Load, Constant Load, Data Rate.
+- Load (as not tied to a single Trial yet) does not have its own section.
+- Not reviewed for subtle differences between:
+-- Load / Trial Load / Load value / Trial Load value.
+-- Trial / Trial Result / Trial Output / Trial Loss Ratio.
+-- loss / Trial Loss Ratio.
Signed-off-by: Vratko Polak <[email protected]>
Commit: da7221bc3984792a7297c77bf0ee8a38a24d2ca9
https://github.com/rfc-editor/AUTH48-rfc9971/commit/da7221bc3984792a7297c77bf0ee8a38a24d2ca9
Author: Vratko Polak <[email protected]>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Fix the rest of #26 items
This addresses "minus lines" from the previous commit.
> - Capitalized also for some external definitions:
> -- Intended Load, Offered Load, Constant Load, Data Rate.
+ Will keep capitalization. Verified:
+ Not capitalizing where quoting verbatim from older documents.
+ Data Rate. Maximum Frame Rate, MOL, FRMOL.
+ Allowed "per-interface Forwarding Rate" to better distinguish from Trial
Forwarding Rate.
+ Offered Load, offered quantities.
+ Constant Load, non-constant load.
+ Intended Load.
+ Every word in such "external section" phrase is capitalized even if the
original document did not.
+ Applied small edit in the paragraph summarizing what is capitalized, how and
why.
> - Load (as not tied to a single Trial yet) does not have its own section.
+ New section Load added under Existing Terms.
+ Divided discussion sections so now the length is not as bad.
+ "bidirectional load" and "unidirectional load" are lowercase (values, not
quantities).
+ Needs verification on generic quantity introduction.
+ Mentioned "magnitude".
+ Mentioned integers and rounding.
> - Not reviewed for subtle differences between:
> --Load / Trial Load / Load value / Trial Load value.
+ No “value” except right after definition.
+ Left some occurrences when two values of similar quantities are in context.
+ Additional text in quantity section now explains the usage.
+ Edited and verified.
+ Also minimize occurences of:
+ "instance" verified
+ "quantity" verified
+ Prefer Load unless the Trial part is really needed.
+ Done, verified.
+ Renamed the Loss Inversion defining section to be eponymous.
> -- Trial / Trial Result / Trial Output / Trial Loss Ratio.
+ Trial Output mosly eliminated and verified.
+ Trial Loss Ratio turned out to be the correct form in most occurrences,
verified.
+ result in progress:
+ Lowercase result mostly outside specification, referring to non-MLR search
results.
+ Specification uses either Trial Loss Ratio or Trial Results when duration is
important.
+ Trial Output occurences are minimal, usually when Trial Result is not
defined yet.
+ Lowercase "result" as a verb is allowed.
+ Trial occurences verified.
> -- loss / Trial Loss Ratio.
+ Trial Loss Ratio within specification, lowercase only when referring also to
non-MLR searches.
+ Verified distinction of Trial and Goal.
+ Some forms allowed to remain lowercase when universal orslear from context:
+ "zero loss" or "loss spike".
+ "current loss ratio" or "1% loss Trial".
+ Loss-related adjectives verified:
+ Two are always capitalized (unless in Python): High-Loss and Low-Loss.
+ Exceed Ratio variants verified:
+ Goal Exceed Ratio is capitalized.
+ Temporary variables are not, for example "Optimistic exceed ratio".
+ Verified other Ratio quantities.
- Newly added paragraphs might have caused regression in the usage of quotes
(#24).
- Explicit references not unified yet, opened #38 for that.
- Em dashes not removed yet, opened #39 for that.
- Second-order typos are possible, especially in newly added paragraphs,
I will do one more revew (resulting in a separate PR) once current big PRs
are merged.
Will probably be tracked under #28.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 05fc9aff0bdeb14e27543cd8bdbf4f6ce24f9edf
https://github.com/rfc-editor/AUTH48-rfc9971/commit/05fc9aff0bdeb14e27543cd8bdbf4f6ce24f9edf
Author: Vratko Polak <[email protected]>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Stop using long dashes
Signed-off-by: Vratko Polak <[email protected]>
Commit: 248744a754968c71073bf70e36af0c5bee33293c
https://github.com/rfc-editor/AUTH48-rfc9971/commit/248744a754968c71073bf70e36af0c5bee33293c
Author: Vratko Polak <[email protected]>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Downgrade some quotes to emphasis
Emphasis (enclosing in markdown single asterisks)
is to be used when introducing a new term in its usual meaning.
Quotes remain for section/document names,
substrings, short quotes or paraphrases,
and phrases used exceptionaly outside their usual meaning.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 0a8567c8bd596324e7bc2acbae8b8b28ee54ce69
https://github.com/rfc-editor/AUTH48-rfc9971/commit/0a8567c8bd596324e7bc2acbae8b8b28ee54ce69
Author: Vratko Polak <[email protected]>
Date: 2026-07-01 (Wed, 01 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Edit sentences
- Only reviewed MLRsearch Specification so far,
the rest is to be addressed in a separate commit.
+ Turned verbs ALL CAPS where appropriate there.
- Search and Search Duration could have their own section,
to be fixed in a separate commit.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 982fdb911acbe59fe80d66f9400852279ff63fb9
https://github.com/rfc-editor/AUTH48-rfc9971/commit/982fdb911acbe59fe80d66f9400852279ff63fb9
Author: Vratko Polak <[email protected]>
Date: 2026-07-02 (Thu, 02 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Add Search Duration section
+ Separate existing paragraphs into a Search section.
Signed-off-by: Vratko Polak <[email protected]>
Commit: ee16c603da193f3bf00b868bccd02ce05ca70d61
https://github.com/rfc-editor/AUTH48-rfc9971/commit/ee16c603da193f3bf00b868bccd02ce05ca70d61
Author: Vratko Polak <[email protected]>
Date: 2026-07-03 (Fri, 03 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Turn frequent existing terms into sections for #38
This way external references can become always long,
while frequent internal references marked only bu capitalizaton.
Importantly, externally defined terms are no longer capitalized,
such capitalization always means there is an internal section
with full definition and longe external reference
+ Throughput section.
+ Intended Load section.
+ Offered Load section.
+ Forwarding Rate section.
+ "Search algorithm" -> "search algorithm"
- The througput section does not mention
the difference between conditional and unconditional compliance
with RFC2544, as it is discussed elsewhere and soed not affect
the definition of Througput
Signed-off-by: Vratko Polak <[email protected]>
Commit: 4096506fb303b4182e90d3eb299ca82f73324905
https://github.com/rfc-editor/AUTH48-rfc9971/commit/4096506fb303b4182e90d3eb299ca82f73324905
Author: Vratko Polak <[email protected]>
Date: 2026-07-03 (Fri, 03 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Unify internal references for #38
- Some external references might remain inconsistent,
especially variations of "RFC2544 Throughput" phrase.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 64dc30b450619672dcb06e8236d5abfb52a7e631
https://github.com/rfc-editor/AUTH48-rfc9971/commit/64dc30b450619672dcb06e8236d5abfb52a7e631
Author: Vratko Polak <[email protected]>
Date: 2026-07-03 (Fri, 03 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Update previously external references
Rules for throughput capitalization:
+ Upper case: Conditional Throughput, Throughput, RFC2544 Throughput.
+ Lower case: generalized, TCP, idea (enough when present in context).
Signed-off-by: Vratko Polak <[email protected]>
Commit: 1ea95b62de26b27811e0deb49f0bc733f8128121
https://github.com/rfc-editor/AUTH48-rfc9971/commit/1ea95b62de26b27811e0deb49f0bc733f8128121
Author: Vratko Polak <[email protected]>
Date: 2026-07-03 (Fri, 03 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Prefer computing over calculating
Signed-off-by: Vratko Polak <[email protected]>
Commit: 316a7f9b46fdda4a52a98ed5109d36e4f7e03f57
https://github.com/rfc-editor/AUTH48-rfc9971/commit/316a7f9b46fdda4a52a98ed5109d36e4f7e03f57
Author: Vratko Polak <[email protected]>
Date: 2026-07-06 (Mon, 06 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Fix trailing typos.
Signed-off-by: Vratko Polak <[email protected]>
Commit: ad529871ba251a40ba7b256e49457cbd13c9f149
https://github.com/rfc-editor/AUTH48-rfc9971/commit/ad529871ba251a40ba7b256e49457cbd13c9f149
Author: Vratko Polak <[email protected]>
Date: 2026-07-10 (Fri, 10 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Fix typos and style
- Not fixing expanded sentences around quantities yet.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 065067282bd7f3b3a9c1a3bd4dd666736ec4c764
https://github.com/rfc-editor/AUTH48-rfc9971/commit/065067282bd7f3b3a9c1a3bd4dd666736ec4c764
Author: Vratko Polak <[email protected]>
Date: 2026-07-10 (Fri, 10 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Downgrade some verbs
The all-caps verbs should be used for MLRsearch specification compliance.
+ Including explicit confirmations of non-obvious implementation freedoms.
+ Including conditional rules.
+ Including explicitly marking some examples as optional features.
+ Especially for specific but common examples, such as "bidirectional load".
But not for:
- Compliance with TST009.
- Repeating RFC 5180 guidelines aroung jumbo frames.
- Additional rules some implementations might require for their own reasons.
- Common consequences implicitly following from earlier explicit rules.
- Implementation details without functional effects do not need formal
approval.
- Informal recommendations implementations are unlikely to violate anyway.
+ Added a comment about Measurer technically not performing
a direct measurement of Forwarding Rate,
as an explanation of why Offered Load is not required.
- Weakened the requirement of Manager and Measurer knowledge of common
capabilities.
If such knowledge is missing and the test happens to work,
Test Report is already required to describe Measurer and Traffic Profile,
so in practice the traffic is specified uniquely,
even though it could differ from the intention of the user.
Comparability when traffic is geenrated by different Measurers
is a hard problem, not in scope of this document.
+ Made the requirement for evaluation of goal result regularity more general.
+ Added explanation of how Goal Final Trial Duration may never be reached.
+ Clarified the conditional recommendations related to passing optional
Trail Output attributes to Manager.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 62f20d3cabc17417029687f262c851c6ef721cd6
https://github.com/rfc-editor/AUTH48-rfc9971/commit/62f20d3cabc17417029687f262c851c6ef721cd6
Author: Vratko Polak <[email protected]>
Date: 2026-07-13 (Mon, 13 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Fix more typos and style
Signed-off-by: Vratko Polak <[email protected]>
Commit: 3f03864520b0ae0850442a37fe830ab8f5e2e5b1
https://github.com/rfc-editor/AUTH48-rfc9971/commit/3f03864520b0ae0850442a37fe830ab8f5e2e5b1
Author: Vratko Polak <[email protected]>
Date: 2026-07-13 (Mon, 13 Jul 2026)
Changed paths:
A track.txt
Log Message:
-----------
Track fine-grained items from review
Signed-off-by: Vratko Polak <[email protected]>
Commit: c61a6da10925ebd5a878272788b2983472bcc3dd
https://github.com/rfc-editor/AUTH48-rfc9971/commit/c61a6da10925ebd5a878272788b2983472bcc3dd
Author: Vratko Polak <[email protected]>
Date: 2026-07-13 (Mon, 13 Jul 2026)
Changed paths:
M track.txt
Log Message:
-----------
Reorder review items
Signed-off-by: Vratko Polak <[email protected]>
Commit: c75cb335838cbe9f6df36aaf311e479f67522584
https://github.com/rfc-editor/AUTH48-rfc9971/commit/c75cb335838cbe9f6df36aaf311e479f67522584
Author: Vratko Polak <[email protected]>
Date: 2026-07-13 (Mon, 13 Jul 2026)
Changed paths:
M rfc9971.md
M track.txt
Log Message:
-----------
Standardize primary unit
It is only used for unidirectional load,
but I think it is still a useful concept.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 1f440f392db02f8977afb09b7daba8eeefb4cec8
https://github.com/rfc-editor/AUTH48-rfc9971/commit/1f440f392db02f8977afb09b7daba8eeefb4cec8
Author: Vratko Polak <[email protected]>
Date: 2026-07-13 (Mon, 13 Jul 2026)
Changed paths:
M rfc9971.md
M track.txt
Log Message:
-----------
Simplify the introduction of a magnitude
The shorter sentece still mentions magnitude, but focuses on units.
The word magnitude is still used to undtoduce unidirectional load.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 756b9caea24d4b98c1708f413d24868cecbd134b
https://github.com/rfc-editor/AUTH48-rfc9971/commit/756b9caea24d4b98c1708f413d24868cecbd134b
Author: Vratko Polak <[email protected]>
Date: 2026-07-14 (Tue, 14 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Remove unneeded definitions
While this keeps the new subsections to simplify referencing of external terms,
the subseqtions are minimalistic to signal no real content is added there
since the working group approved this document.
Also discussions of existing terms were reduced,
as the distinctions were already discussed within new term sections.
The concept of base quantity and narrower quantity is made explicit,
as it explains gruoping of similar but strictly speaking not identical
quantities.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 649492446385354a0474d53dd2a0a9d5de923936
https://github.com/rfc-editor/AUTH48-rfc9971/commit/649492446385354a0474d53dd2a0a9d5de923936
Author: Vratko Polak <[email protected]>
Date: 2026-07-14 (Tue, 14 Jul 2026)
Changed paths:
M rfc9971.md
R track.txt
Log Message:
-----------
Do not introduce base and narrower quantities
Older versions were fine with using
"quantity A is based on quantity B"
as a commonly used English phrasing that doues not need introduction.
+ Remove the rewiew items tracking file.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 94b7e122c2d5db20b8dec2fcbf6ba80b5d06007d
https://github.com/rfc-editor/AUTH48-rfc9971/commit/94b7e122c2d5db20b8dec2fcbf6ba80b5d06007d
Author: Vratko Polak <[email protected]>
Date: 2026-07-16 (Thu, 16 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Improve punctuation
Mostly involving "for example" phrase.
+ Outstanding issues are all related to normative language.
Added TODO items, to be fixed in next commit.
Signed-off-by: Vratko Polak <[email protected]>
Commit: ad62779b4e3ab6e9109f88ff193cfa6345a241ba
https://github.com/rfc-editor/AUTH48-rfc9971/commit/ad62779b4e3ab6e9109f88ff193cfa6345a241ba
Author: Vratko Polak <[email protected]>
Date: 2026-07-17 (Fri, 17 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Address comments about normative language
- Leaving COMMENT blocks for items that I think do not need edits,
just more context for the reviewer.
To be removed in nect commit.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 05bc154aed9f129d5ef32de4b678319b0882e310
https://github.com/rfc-editor/AUTH48-rfc9971/commit/05bc154aed9f129d5ef32de4b678319b0882e310
Author: Vratko Polak <[email protected]>
Date: 2026-07-17 (Fri, 17 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Improve explanation blocks
Signed-off-by: Vratko Polak <[email protected]>
Commit: b7a90c0c313b7f1e9375a00febf15b962e2b39d4
https://github.com/rfc-editor/AUTH48-rfc9971/commit/b7a90c0c313b7f1e9375a00febf15b962e2b39d4
Author: Vratko Polak <[email protected]>
Date: 2026-07-17 (Fri, 17 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Remove comment blocks
Signed-off-by: Vratko Polak <[email protected]>
Commit: 4ee0608540aeb0594c89a702a67acb2fdb40b380
https://github.com/rfc-editor/AUTH48-rfc9971/commit/4ee0608540aeb0594c89a702a67acb2fdb40b380
Author: Vratko Polak <[email protected]>
Date: 2026-07-20 (Mon, 20 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Describe typical exceptions to some rules
When a rule is a SHOULD instead of a MUST,
a reader might wonder what exception is allowed.
This adds some explanations related to that.
For DUT as the intended bottleneck of a SUT,
the exception is suprisingly good DUT performance.
I decided not to refer to Max Load there yet.
For compatible goals, I highlighted compatibility itself
is determined by external documents, the soft rules
in MLRsearch Specification are there just to improve comparability.
Impact of alternalive attribute values is now described more broadly,
copying in the case of duration sum smaller than final duration.
It is not clear why would anybody want to measure such alternative goals,
but now it should be clearer only comparability, not compliance is at stake.
Also made the TST009 goal an explicit recommendation for comparability.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 4efb1f66a1e131174678addc734cb03ea3632ebb
https://github.com/rfc-editor/AUTH48-rfc9971/commit/4efb1f66a1e131174678addc734cb03ea3632ebb
Author: Vratko Polak <[email protected]>
Date: 2026-07-21 (Tue, 21 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Admit some recommendations on search goals
+ Reorder the out of scope items.
- Sections after specification are not reviewed yet.
Signed-off-by: Vratko Polak <[email protected]>
Commit: 2a00319cf9f6a5d30637b7561f1482e99b637ab3
https://github.com/rfc-editor/AUTH48-rfc9971/commit/2a00319cf9f6a5d30637b7561f1482e99b637ab3
Author: Vratko Polak <[email protected]>
Date: 2026-07-21 (Tue, 21 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Tweak normative language for search goals
+ Normative verbs in definitions of attributes.
+ Lowercase verbs in discussion paragraphs when summarizing definitions.
Signed-off-by: Vratko Polak <[email protected]>
Commit: d1d71131dcb771adb42149a22ac0d2c04ab9e120
https://github.com/rfc-editor/AUTH48-rfc9971/commit/d1d71131dcb771adb42149a22ac0d2c04ab9e120
Author: apaloma-rpc <[email protected]>
Date: 2026-07-29 (Wed, 29 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Editorial nits
Commit: 12208655d8ecaab1eb6df5fef736a9a93687e0f9
https://github.com/rfc-editor/AUTH48-rfc9971/commit/12208655d8ecaab1eb6df5fef736a9a93687e0f9
Author: apaloma-rpc <[email protected]>
Date: 2026-07-29 (Wed, 29 Jul 2026)
Changed paths:
M rfc9971.md
Log Message:
-----------
Merge pull request #49 from vrpolakatcisco/i43j
Close issues and two rounds of comments
Compare:
https://github.com/rfc-editor/AUTH48-rfc9971/compare/857c03827c25...12208655d8ec
To unsubscribe from these emails, change your notification settings at
https://github.com/rfc-editor/AUTH48-rfc9971/settings/notifications
--
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]
