@techreport{sriram-sidrops-drop-invalid-policy-10,
    number =    {draft-sriram-sidrops-drop-invalid-policy-10},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-sriram-sidrops-drop-invalid-policy/10/},
    author =    {Kotikalapudi Sriram and Oliver Borchert and Doug Montgomery},
    title =     {{Origin Validation Policy Considerations for Dropping Invalid Routes}},
    pagetotal = 7,
    year =      2022,
    month =     nov,
    day =       27,
    abstract =  {Deployment of Resource Public Key Infrastructure (RPKI) and Route Origin Authorizations (ROAs) is expected to occur gradually over several or many years. During the incremental deployment period, network operators would wish to have a meaningful policy for dropping Invalid routes. Their goal is to balance (A) dropping Invalid routes so hijacked routes can be eliminated, versus (B) tolerance for missing or erroneously created ROAs for customer prefixes. This document considers a Drop Invalid if Still Routable (DISR) policy that is based on these considerations. The key principle of DISR policy is that an Invalid route can be dropped if a Valid or NotFound route exists for a subsuming less specific prefix.},
}