25. Ben: Raise the same issue again. It uses RPKI based objects which is similar but not the same. That doesn't exist today. If this is deployed, it will jeopardize the use of RPKI in routing security. This is a big problem but not addressed. We need new signed objects. I'm happy to help but no one proposes it. [during ietf119] #25
Response: The inter-domain SAVNET architecture proposes to use RPKI ROA and ASPA objects as a SAV information source for generating SAV rules, when the SAV-specific information is not available. The new inter-domain SAV mechanism can determine how to use them and should avoid jeopardizing the use of RPKI in routing security. We have added this requirement “when using RPKI ROA objects and ASPA objects as the SAV information source, the new inter-domain SAV mechanism should avoid jeopardizing the use of RPKI in routing security.” in Section 6.
Response: The inter-domain SAVNET architecture proposes to use RPKI ROA and ASPA objects as a SAV information source for generating SAV rules, when the SAV-specific information is not available. The new inter-domain SAV mechanism can determine how to use them and should avoid jeopardizing the use of RPKI in routing security. We have added this requirement “when using RPKI ROA objects and ASPA objects as the SAV information source, the new inter-domain SAV mechanism should avoid jeopardizing the use of RPKI in routing security.” in Section 6.