From 6213ecaaf5ca733a1c966fc4b9665beee3b21612 Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Thu, 10 Apr 2025 13:24:20 -0700 Subject: [PATCH] -19 pushed with jgs comments and small clean-ups --- draft-ietf-sidrops-8210bis.xml | 45 ++++++++++++++++++++-------------- 1 file changed, 26 insertions(+), 19 deletions(-) diff --git a/draft-ietf-sidrops-8210bis.xml b/draft-ietf-sidrops-8210bis.xml index 939f394..cbcdedd 100644 --- a/draft-ietf-sidrops-8210bis.xml +++ b/draft-ietf-sidrops-8210bis.xml @@ -8,7 +8,7 @@ - @@ -19,7 +19,7 @@ - IIJ Research, Arrcus, & DRL + Arrcus, DRL, & IIJ Research
5147 Crystal Springs @@ -133,6 +133,9 @@ race conditions, Make Before Break and Shorter Prefix First. + + Optional ordering of payload PDUs has been added. + Language was clarified when multiple caches are configured, and an interesting affect is noted. @@ -206,9 +209,9 @@ A payload PDU is a protocol message which contains data for - use by the router, as opposed to a PDU which conveys the control - mechanisms of this protocol. Prefixes and Router Keys are - examples of payload PDUs. + use by the router, as opposed to a PDU which conveys the + control mechanisms of this protocol. IPvX Prefixes, Router + Keys, ASPA are examples of payload PDUs. @@ -1749,7 +1752,7 @@ Cache Router especially an initial full load in response to a Reset Query PDU, undesirable race conditions are possible: - + For some prefix P, an operator may create two or more ROAs with different ASes because they are in the process of changing what provider AS may announce P. This is a case of @@ -1767,7 +1770,7 @@ Cache Router sub-prefix of P0, a router which receives the ROA for P0 before that for P1 is likely to mark a BGP announcement of prefix P1 invalid. Therefore, the cache SHOULD announce the - sub-prefix P1 before the covering prefix P0. Similarly, in + sub-prefix P1 before the covering prefix P0. Conversely, in the case of withdrawals, the cache SHOULD withdraw covering prefixes before their sub-prefixes. @@ -1783,8 +1786,8 @@ Cache Router request until the relevant End of Data PDU is received. - However, a router MAY choose to apply a time limit for how long - it is willing to wait for the End of Data PDU. + However, a router MAY apply a time limit for how long it is + willing to wait for the End of Data PDU. @@ -1792,25 +1795,29 @@ Cache Router
- A Version 2 Cache SHOULD order payload PDUs it sends to routers. - Ascending order is considered somewhat more efficient as routers - are likely building trees. With the exceptions in above, ordering SHOULD be, as follows: + A Version 2 Cache SHOULD, unless it requires major revision of + existing code, order payload PDUs (IPvX, Router Key, ASPA) it + sends to routers. Ascending order is considered somewhat more + efficient as routers are likely building trees. Iff ordering, + with the exceptions in above, ordering MUST + be, as follows: - PDU Type, + PDUs are first ordered by PDU Type, - Within prefix PDUs for the same prefix by Max Length and then - AS, + IPv4 and IPv6 Prefix PDUs are ordered by: first IPvX Prefix, + second Prefix Length, third Max Length, and fourth Autonomous + System Number. Treating AS 0 as sorting last fulfills the "AS 0 + Last" requirement of , - Router Keys ordered by AS Number and then Subject Public Key - Info, and + Router Keys are ordered by AS Number and then Subject Public Key + Info, - ASPA PDUs ordered by Customer AS. + And ASPA PDUs ordered by Customer AS.