The global deployment of SIDR, consisting of Resource Public Key Infrastructure (RPKI), Origin Validation of BGP announcements, and BGPSEC, is underway, creating an Internet Routing System consisting of SIDR-aware and non-SIDR-aware networks. This deployment must be properly handled to avoid the division of the Internet into separate networks. SIDR Operations Working Group (SIDROPS) is responsible for encouraging deployment of the SIDR technologies while ensuring as secure of a global routing system, as possible, during the transition.

SIDROPS develops guidelines for the operation of SIDR-aware networks, and provides operational guidance on how to deploy and operate SIDR technologies in existing and new networks. It also develops protocol and protocols extensions that are considered important to improve efficiency and security of SIDR, like for instance Autonomous System Provider Authorization (ASPA). The WG is also responsible for the maintenance of Resource Public Key Infrastructure (RPKI) to Router protocol.

In the space of SIDROPS, the term operators will encompass a range of operational experience: CA Operators, Regional/National and Local Internet Registries, Relying Party software developers as well as the research/measurement community all have relevant operational experience or insight that this WG will consider in its work.

SIDROPS is focused on deployment and operational issues and experiences with SIDR technologies that are part of the global routing system, as well as the repositories and CA systems that
form part of the SIDR architecture.

The goals of SIDROPS are to:

* Solicit input from a range of operators to identify operational issues with a SIDR-aware Internet, and determine solutions or workarounds to those issues.

* Solicit input from all operators to identify issues with interaction with the non-SIDR-aware Internet, and to determine solutions or workarounds to those issues.

* Standardize YANG data models related to the SIDR operations.

* Develop operational solutions for identified issues in SIDROPS and document them in Standard Track, Informational, or BCP documents, depending on the type of solution (e.g., new extensions vs. operational/deployment recommendations).

These documents should document SIDR operational experience, including interactions with non-SIDR-aware networks, the interfaces between SIDR-aware and non-SIDR-aware networks, and the continued operational/security impacts from non-SIDR-aware networks.

SIDR operational and deployment issues with Interdomain Routing Protocols as well as BGPSEC maintenance and extension are the primary responsibility of the IDR Working Group. SIDROPS may provide input to that group, as needed, and cooperate with that group in reviewing solutions to SIDR operational and deployment problems.

Future work items within this scope will be adopted by the WG if there is a substantial expression of interest from the community and if the work (e.g., protocol maintenance) clearly does
not fit elsewhere in the IETF.

There must be a continuous expression of interest for the WG to work on a particular work item. If there is no longer sufficient interest in the WG in a work item, the item may be removed from the list of WG items.