Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-icnrg-pathsteering-07> for your review
rfc-editor@rfc-editor.org Thu, 25 January 2024 22:52 UTC
Return-Path: <wwwrun@rfcpa.amsl.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 874AEC14F6A7; Thu, 25 Jan 2024 14:52:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 nvmFKFW1OnLK; Thu, 25 Jan 2024 14:52:13 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 58EC9C14F61C; Thu, 25 Jan 2024 14:52:13 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 4C46119389B0; Thu, 25 Jan 2024 14:52:13 -0800 (PST)
To: iliamo@mailbox.org, daveoran@orandom.net
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, irsg@irtf.org, ietf@dkutscher.net, auth48archive@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240125225213.4C46119389B0@rfcpa.amsl.com>
Date: Thu, 25 Jan 2024 14:52:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/54J3jRhyNFOEIyCS7_Vci8Rj6o0>
Subject: Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-icnrg-pathsteering-07> 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: Thu, 25 Jan 2024 22:52:17 -0000
Authors,
While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the XML file.
1) <!-- [rfced] Please note that the title of the document has been updated as
follows. Abbreviations have been expanded per Section 3.6 of RFC 7322 ("RFC
Style Guide"). Please review.
Original:
Path Steering in CCNx and NDN
Current:
Path Steering in Content-Centric Networking (CCNx) and Named Data
Networking (NDN)
-->
2) <!-- [rfced] May we make these items parallel by updating the last
item to match the other three that start with a verb ("support",
"perform", and "improve")?
Original:
* Support the discovery, monitoring and troubleshooting of multi-
path network connectivity based on names and name prefixes...
...
* Perform accurate online measurement of network performance, which
generally requires...
...
* Improve the performance and flexibility of multi-path congestion
control algorithms...
...
* A consumer endpoint can mitigate content poisoning attacks by
directing its Interests onto the network paths that bypass
poisoned caches.
Perhaps:
* Support the discovery, monitoring and troubleshooting of multi-
path network connectivity based on names and name prefixes...
...
* Perform accurate online measurement of network performance, which
generally requires...
...
* Improve the performance and flexibility of multi-path congestion
control algorithms...
...
* Provide a consumer endpoint that has the ability to mitigate content
poisoning attacks by directing its Interests onto the network paths
that bypass poisoned caches.
-->
3) <!--[rfced] Is the reference to RFC 8029 correct? This RFC does not contain the
term "tree trace" (but we do see "traceroute and ping" and "MPLS"). Please
review and let us know if an update is needed.
Current:
The canonical tools are the well-known _traceroute_ and _ping_. For
point-to-multipoint MPLS, the more recent tree trace [RFC8029] protocol
is used.
-->
4) <!-- [rfced] In this sentence, is "explicit" referring to A) "advertised" or
B) "property"?
Current:
That makes the question of what properties a consumer uses
to choose a path one of observation or measurement rather than
advance selection based on an explicit advertised property (e.g.,
SCION [SCION]).
Perhaps A:
That makes the question of what properties a consumer uses
to choose a path one of observation or measurement rather than
advance selection based on an explicitly advertised property (e.g.,
SCION [SCION]).
Perhaps B:
That makes the question of what properties a consumer uses
to choose a path one of observation or measurement rather than
advance selection based on an explicit, advertised property (e.g.,
SCION [SCION]).
-->
5) <!-- [rfced] Should “an Interest” be updated to “an Interest message”
and "a Data" be updated to "a Data message” for clarity?
Original:
Path Discovery: The process of sending an Interest requesting
discovery of a path and if successful, receiving a Data containing
a Path Label for the path the corresponding Interest traversed.
Perhaps:
Path Discovery: The process of sending an Interest message requesting
discovery of a path and, if successful, receiving a Data message containing
a Path Label for the path the corresponding Interest traversed.
-->
6) <!--[rfced] Section 3.2 of RFC 8609 does not include the term "Packet Encoding".
Is this reference correct or is an update needed?
Current:
We elucidate the design using CCNx semantics [RFC8569] and extend its
Packet Encoding [RFC8609] as defined in Section 3.2.
-->
7) <!--[rfced] May we update the first occurrence of "MODES" in the sentence
below to "modes" as it appears to be used to refer to modes in a general
sense?
Current:
For example, multiple Interests with different MODES
(e.g., one with DISCOVERY MODE and one without) will get aggregated;
therefore, the behavior of the forwarder might be dependent on
the arrival order of those Interests.-->
8) <!-- [rfced] To avoid non-specific hyphenation ("non-DISCOVERY MODE Path
Label"), would the following update retain the original meaning?
Original:
If that Interest carried no Path Label, its
behavior is essentially unchanged, but if it carried a non
DISCOVERY MODE Path Label, the consumer's intent for the Interest
to traverse the specified path will be ignored and it is
indeterminate if the chosen path will actually be used.
Perhaps:
If that Interest carried no Path Label, its
behavior is essentially unchanged, but if it carried a
Path Label without DISCOVERY MODE, the consumer's intent
for the Interest to traverse the specified path will be ignored,
and it is indeterminate if the chosen path will actually be used.
-->
9) <!-- [rfced] Please review the pointer to Section 2.5, as we did not find
"DISCOVERY MODE" as we expected. Should the pointer be to Section 3.1?
Current:
Multiple Interests intended to discover paths (i.e., by carrying the
DISCOVERY MODE flag defined in Section 2.5) might also be aggregated
by a forwarder.
-->
10) <!-- [rfced] To clarify "a significant a practical problem", may we update
to A) "a significant practical problem" or B) "a significant or practical
problem"? Or is there another way you would like to update?
Current:
While this places a hard upper bound on the
maximum number of network hops that can be represented, this is not a
significant a practical problem in NDN and CCNx, since the size can
be preset during Content (Data) message encoding based on the exact
number of network hops traversed by the Interest message.
Perhaps A:
While this places a hard upper bound on the
maximum number of network hops that can be represented, this is not a
significant practical problem in NDN and CCNx, since the size can
be preset during Content (Data) message encoding based on the exact
number of network hops traversed by the Interest message.
Perhaps B:
While this places a hard upper bound on the
maximum number of network hops that can be represented, this is not a
significant or practical problem in NDN and CCNx, since the size can
be preset during Content (Data) message encoding based on the exact
number of network hops traversed by the Interest message.
-->
11) <!--[rfced] We note that the flag values in Table 1 include underscores,
while they appear without underscores throughout the document. Should
these be made consistent?
DISCOVERY MODE vs. DISCOVERY_MODE
FALLBACK MODE vs. FALLBACK_MODE
STRICT MODE vs. STRICT_MODE
-->
12) <!--[rfced] FYI: For Figure 4, we have realigned the ruler so that "0"
appears in line with the "-" not the "+".
-->
13) <!--[rfced] Does "which is carried..." refer to A) "Path Label" or
B) "NDN Interest and Data packets"? To clarify, how should this
sentence be updated?
Original:
Path Label is an optional TLV for NDN Interest and Data packets,
which is carried in the NDN Link Adaptation Protocol [NDNLPv2] used
to wrap NDN packets for carriage over various link layer protocols.
Perhaps A:
Path Label is an optional TLV for NDN Interest and Data packets.
It is carried in the NDN Link Adaptation Protocol [NDNLPv2], which is
used to wrap NDN packets for carriage over various link layer protocols.
Perhaps B:
Path Label is an optional TLV for NDN Interest and Data packets,
which are carried in the NDN Link Adaptation Protocol [NDNLPv2]; the
protocol is used to wrap NDN packets for carriage over various link
layer protocols.
-->
14) <!--[rfced] It does not appear that "O" is defined for either equation in
the sentences below. How should "O" be defined? Additionally, should a
different letter variable be used, since "O" looks similar to "0" (zero)?
Original:
If nexthop
labels are not allocated in a predictable fashion by the routers,
brute forcing a 32-bit nexthop label requires on average O(2^31)
Interests.
...
The labels that identify each forwarding face is state O(number of
faces) and constitutes a small increase to the existing state
needed to represent a face.
-->
15) <!-- [rfced] How may we rephrase this sentence to avoid the awkward
hyphenation of "anti- label scan heuristics"?
Current:
A relatively short periodic update of nexthop
labels and anti- _label scan_ heuristics implemented in the ICN
forwarder may successfully mitigate this type of attack.
Perhaps:
A relatively short periodic update of nexthop
labels and heuristics, which are not _label scan_ heuristics,
implemented in the ICN forwarder may successfully mitigate
this type of attack.
-->
16) <!-- [rfced] Does the slash between "reads/writes" indicate "or", "and", or
"and/or"? Would you like to update for clarity?
Original:
This
method is viable due to the symmetry of forward and reverse paths in
CCNx and NDN architectures combined with ICN path steering requiring
only reads/writes of the topmost nexthop label (i.e. active nexthop
label) in the path label.
-->
17) <!-- [rfced] Terminology
A) Throughout the text, the following terminology appears to be used
inconsistently. Please review these occurrences and let us know if/how they
may be made consistent.
Content (Data) message vs. Data (Content) message
Data vs. data
Invalid path label vs. invalid path label
Nexthop label vs. nexthop label
Path Discovery vs. path discovery
Path Label vs. path label
Path Label bitmap vs. Path label bitmap vs. path label bitmap
Path Steering vs. path steering
Polynomial encoding vs. polynomial encoding
B) FYI, we have made the following updates to parallel the terminology
in RFCs-to-be 9507 and 9508. Please review and let us know if further
updates are needed.
content object > Content Object
interest > Interest
Interest-Return / Interest Return > InterestReturn
Path label TLV / path label TLV > Path Label TLV
path steering TLV > Path Steering TLV
C) Are the following instances of “nexthop” referring to the “nexthop label”?
If so, should “label" be added to any of these instances? If not, are there any
instances that should perhaps be updated as “next hop” (as in the first sentence
below), or should all of these instances be reflected as “nexthop” for
consistency?
Nexthop Label: One entry in a Path Label representing the next hop
for the corresponding forwarder to use when a path-steered
Interest message arrives at that forwarder. A sequence of Nexthop
Labels constitutes a full Path Label.
which is forwarded to each nexthop through the corresponding egress
through the specified nexthop among
a given nexthop is no longer valid
point to a now-invalid nexthop
This is detected by failure to find
a match between the decoded nexthop ID and the nexthops of the FIB
entry after LNPM FIB lookup.
-->
18) <!-- [rfced] FYI - We have added expansions for abbreviations upon first use
per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each
expansion in the document carefully to ensure correctness.
Content-Centric Networking (CCNx)
Information-Centric Networking (ICN)
Media Access Control Security (MACsec)
Named Data Networking (NDN)
Pending Interest Table (PIT)
-->
19) <!-- [rfced] In the html and pdf outputs, the text enclosed in <tt> is output
in fixed-width font. In the txt output, there are no changes to the font,
and the quotation marks have been removed.
NextHopFaceId
In the html and pdf outputs, the text enclosed in <em> is output in
italics. In the txt output, the text enclosed in <em> appears with an
underscore before and after.
brute force
End-to-end Path Discovery
generator polynomial
Invalid path label (2 instances)
label scan
path label
Path Steering
ping
Polynomial encoding
traceroute
Please review carefully and let us know if the output is acceptable or if any
updates are needed.
-->
20) <!-- [rfced] Please ensure that the guidelines listed in Section 2.1 of RFC 5743
have been adhered to in this document. See
https://www.rfc-editor.org/rfc/rfc5743.html#section-2.1.
-->
21) <!-- [rfced] Some author comments are present in the XML. Please confirm that
no updates related to these comments are outstanding. Note that the
comments will be deleted prior to publication.
-->
22) <!-- [rfced] Please review the "Inclusive Language" portion of the online
Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
and let us know if any changes are needed.
Note that our script did not flag any words in particular, but this should
still be reviewed as a best practice.
-->
Thank you.
RFC Editor/st/ap
On Jan 25, 2024, at 2:50 PM, rfc-editor@rfc-editor.org wrote:
*****IMPORTANT*****
Updated 2024/01/25
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://www.rfc-editor.org/faq/)
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://trustee.ietf.org/license-info/)
* 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://authors.ietf.org/rfcxml-vocabulary>.
* 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://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc
* The archive itself:
https://mailarchive.ietf.org/arch/browse/auth48archive/
* 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://www.rfc-editor.org/authors/rfc9531.xml
https://www.rfc-editor.org/authors/rfc9531.html
https://www.rfc-editor.org/authors/rfc9531.pdf
https://www.rfc-editor.org/authors/rfc9531.txt
Diff file of the text:
https://www.rfc-editor.org/authors/rfc9531-diff.html
https://www.rfc-editor.org/authors/rfc9531-rfcdiff.html (side by side)
Diff of the XML:
https://www.rfc-editor.org/authors/rfc9531-xmldiff1.html
Tracking progress
-----------------
The details of the AUTH48 status of your document are here:
https://www.rfc-editor.org/auth48/rfc9531
Please let us know if you have any questions.
Thank you for your cooperation,
RFC Editor
--------------------------------------
RFC9531 (draft-irtf-icnrg-pathsteering-07)
Title : Path Steering in CCNx and NDN
Author(s) : I. Moiseenko, D. Oran
WG Chair(s) :
Area Director(s) :
- [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-icnrg… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-i… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-i… "David R. Oran"
- Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-i… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-i… "David R. Oran"
- Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-i… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-i… "David R. Oran"
- Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-i… Sarah Tarrant
- Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-i… "David R. Oran"
- Re: [auth48] AUTH48: RFC-to-be 9531 <draft-irtf-i… Sarah Tarrant