sigh - my mailer (on my phone) seems to have eaten my first response.
[If you have a copy, please send it back to me ;-)]
This response has additional response - so if you did receive the first
message, please use this message in its place.
Thank you,
Lou
PS I see there are other responses (Thank you!) and I'll respond to
those if I have anything to add.
On 11/14/2025 5:16 PM, [email protected] wrote:
Authors and AD*,
*AD, please see #1 below.
Authors, while reviewing this cluster of documents*, please reply to the
questions below regarding consistency across the cluster. These questions are
in addition to the document-specific questions sent for each RFC-to-be. Your
reply will likely impact two or more of the documents in the cluster, so
please discuss off-list as necessary, and then let us know how to
proceed. Note - You have the option of updating the edited XML files yourself,
if you prefer. We will wait to hear from you before continuing with the
publication process.
* Cluster 541 (C541) currently in AUTH48 state:
https://www.rfc-editor.org/authors/rfc9892.html
https://www.rfc-editor.org/authors/rfc9893.html
https://www.rfc-editor.org/authors/rfc9894.html
https://www.rfc-editor.org/authors/rfc9895.html
(In addition, the .pdf, .txt, .xml, and diff files are available.)
You may track the progress of all documents in this cluster through AUTH48 at:
https://www.rfc-editor.org/auth48/C541
1) *AD - We are sorry to hear of the passing of David Wiggins and Stan
Ratliff. David is listed as an author for RFCs-to-be 9892, 9893, 9894, and
9895 (all documents in the cluster). Stan is listed as an author for RFC-to-be
9893.
As AD, please confirm that you will approve the documents on behalf of David
and Stan. (Note: Any of the three options at
https://www.rfc-editor.org/faq/#missingauthor are acceptable.)
2) FYI - We updated "DiffServ" to "Diffserv" throughout the cluster per
https://www.rfc-editor.org/rpc/wiki/doku.php?id=terms. If no objections, we
will ask IANA to update the following descriptions prior to publication.
Link to registry group:https://www.iana.org/assignments/dlep-parameters
"Traffic Classification Sub-Data Item Type Values" registry
(draft-ietf-manet-dlep-traffic-classification):
OLD:
DiffServ Traffic Classification
NEW:
Diffserv Traffic Classification
"Extension Type Values" registry (draft-ietf-manet-dlep-da-credit-extension):
OLD:
DiffServ Aware Credit Window
NEW:
Diffserv Aware Credit Window
looks, right. Thank you.
3) We see "Credit window control" (beginning of sentence, so the "C" is
capitalized) but "credit-window scheme". We suggest updating to "credit window
scheme" (no hyphen).
Sure.
4) Do "credit window control" (approx. 24 instances in cluster) and "credit
window flow control" (3 instances in cluster) mean the same thing? Will the
interchangeable usage of these terms - or the distinction between the two -
be clear to readers?
So the, albeit subtle, distinction between the terms is that "credit
window flow control" is the overall preprocess of using credit-based
flow control, while "credit window control" relates to the
mechanisms/procedures defined to grant and maintain credits. I think the
alternatives are to leave as is or to clarify the distinction.
for the latter, my suggestions are:
OLD
credit/draft-ietf-manet-dlep-da-credit-extension.xml: credit window
control mechanisms defined in <xref
credit/draft-ietf-manet-dlep-da-credit-extension.xml: the credit
window control and flow mechanisms defined in <xref
ether-credit/draft-ietf-manet-dlep-ether-credit-extension.xml:
traffic classification and credit window control mechanisms
ether-credit/draft-ietf-manet-dlep-ether-credit-extension.xml: and
the credit window control and flow mechanisms defined in
tc/draft-ietf-manet-dlep-traffic-classification.xml: with
applications such as credit window control as specified in
tc/draft-ietf-manet-dlep-traffic-classification.xml: The credit
window control document provides an
tc/draft-ietf-manet-dlep-traffic-classification.xml: credit window
control, allows credit windows to be shared
fc/draft-ietf-manet-dlep-credit-flow-control.xml: Credit window
control is used to regulate when data may be sent to
fc/draft-ietf-manet-dlep-credit-flow-control.xml: introduces
support for credit window control by defining two new DLEP
fc/draft-ietf-manet-dlep-credit-flow-control.xml: The use of credit
window control impacts the data plane.
fc/draft-ietf-manet-dlep-credit-flow-control.xml: The credit window
control mechanisms defined in this document
fc/draft-ietf-manet-dlep-credit-flow-control.xml: requiring the use
of credit window control is used.
fc/draft-ietf-manet-dlep-credit-flow-control.xml: The defined
credit window control has similar objectives as the
fc/draft-ietf-manet-dlep-credit-flow-control.xml: Two new messages
are defined in support for credit window control:
fc/draft-ietf-manet-dlep-credit-flow-control.xml: <name>Credit Window
Control Data Items</name>
fc/draft-ietf-manet-dlep-credit-flow-control.xml: Five new Data
Items are defined to support credit window control.
fc/draft-ietf-manet-dlep-credit-flow-control.xml: the credit
window control defined in this document is used. Note
fc/draft-ietf-manet-dlep-credit-flow-control.xml: This document
introduces credit window control and flow mechanisms
NEW
credit/draft-ietf-manet-dlep-da-credit-extension.xml: credit window
*flow *control mechanisms defined in <xref
credit/draft-ietf-manet-dlep-da-credit-extension.xml: the *credit
window flow control *mechanisms defined in <xref
ether-credit/draft-ietf-manet-dlep-ether-credit-extension.xml:
traffic classification and credit window *flow *control mechanisms
ether-credit/draft-ietf-manet-dlep-ether-credit-extension.xml: and
the *credit window flow control* mechanisms defined in
tc/draft-ietf-manet-dlep-traffic-classification.xml: with
applications such as credit window *flow *control as specified in
tc/draft-ietf-manet-dlep-traffic-classification.xml: The credit
window *flow *control document provides an
fc/draft-ietf-manet-dlep-credit-flow-control.xml: introduces
support for credit window *flow *control by defining two new DLEP
tc/draft-ietf-manet-dlep-traffic-classification.xml: credit window
*flow *control, allows credit windows to be shared
fc/draft-ietf-manet-dlep-credit-flow-control.xml: Credit window
*flow *control is used to regulate when data may be sent to
fc/draft-ietf-manet-dlep-credit-flow-control.xml: <name>Credit Window
*Flow *Control</name>
fc/draft-ietf-manet-dlep-credit-flow-control.xml: *REPLACE*: _The use of
credit window control impacts the data plane.
_ *WITH: The additions provide the DLEP mechanisms to control credits.
Routers then use this
information to regulate when
data is sent to a modem.*
fc/draft-ietf-manet-dlep-credit-flow-control.xml: The credit window
flow *control *mechanisms defined in this document
fc/draft-ietf-manet-dlep-credit-flow-control.xml: requiring the use
of credit window *flow *control is used.
fc/draft-ietf-manet-dlep-credit-flow-control.xml: The defined
credit window* flow * control has similar objectives as the
fc/draft-ietf-manet-dlep-credit-flow-control.xml: Two new messages
are defined in support for *control of credit windows*:
fc/draft-ietf-manet-dlep-credit-flow-control.xml: Five new Data
Items are defined to support the *control of credit windows*.
fc/draft-ietf-manet-dlep-credit-flow-control.xml: the credit
window *flow *control defined in this document is used. Note
fc/draft-ietf-manet-dlep-credit-flow-control.xml: This document
introduces credit window *flow *control mechanisms
some of the above could refer to ether the process or the mechanisms ,
in which case I chose process. I think this leaves one instance:
fc/draft-ietf-manet-dlep-credit-flow-control.xml: <name>Credit Window
Control Data Items</name>
I think this is better then "Data Items for the Control of Credit
Windows" -- but this too is acceptable.
5) We see both "Type Value" and "Type value" in running text. Which form is
preferred?
Some examples:
"Message Type value" in draft-ietf-manet-dlep-credit-flow-control
"DLEP Extension Type Value" in draft-ietf-manet-dlep-da-credit-extension and
draft-ietf-manet-dlep-ether-credit-extension
"DiffServ Aware Credit Window Type Value" in
draft-ietf-manet-dlep-da-credit-extension
"IEEE 802.1Q Aware Credit Window Type Value" in
draft-ietf-manet-dlep-ether-credit-extension
lower case. to be consistent with rfc8175.
6) 'Rick Taylor's "Data Item Containers"' is only mentioned in the
Acknowledgments sections of two of the four documents in this group
(draft-ietf-manet-dlep-traffic-classification and
draft-ietf-manet-dlep-da-credit-extension). Would you like to add the
applicable sentence to the Acknowledgments sections of
draft-ietf-manet-dlep-credit-flow-control and
draft-ietf-manet-dlep-ether-credit-extension as well?
I'd leave as is or go with Ronald's proposal.
Thank you!
Lou
Thank you,
Lynne Bartholomew and Rebecca VanRheenen
RFC Production Center
--
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]
