Let me clarify one nit ...
In the other mail you said:
"any announcement of any prefixes in that space, from /16 to /32, from
an AS other than 42 are INVALID."
In the light of the below quote from origin-ops-10 should the above be
reworded as:
"any announcement of any prefixes in that space, from /16 to /32, from
an AS other than 42 are INVALID unless a valid ROA is present in the
RPKI covering such sub-allocation"
Thx,
R.
From a partial deployment perspective, it does mean that once a ROA is
published for an address block (and follows the ops guideline of being
precise), further sub-allocations NEED to have the ROA
published. Otherwise, they would be marked invalid and risk being not
routed.
from draft-ietf-sidr-origin-ops-10
Before issuing a ROA for a super-block, an operator MUST ensure that
any sub-allocations from that block which are announced by other ASs,
e.g. customers, have correct ROAs in the RPKI. Otherwise, issuing a
ROA for the super-block will cause the announcements of sub-
allocations with no ROAs to be viewed as Invalid, see
[I-D.ietf-sidr-pfx-validate].
randy
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
