Draft: draft-ietf-sidr-as-migration-03 Status of the draft: Ready for publication   General comment: Thank you for a well-written specification for sidr’s inclusion of the as-migration.   Answers to questions in ops-dir review form are included below, but all the text below can be summarized in one short statement “This document is well-written and does not need any additional changes except to fix the nits for lines over 72 characters).     ·          Deployment discussions o Extensive discussions on deployment and management have been included in the two related specifications (draft-ietf-sidr-as-migration-03 and draft-ietf-idr-as-migration-03). o This specification is written from the viewpoint of operators and provides both a step-by-step deployments, and a consideration of how these solutions are deployed. Scaling issues in a typical migration are discussed. o Configuration parameters are normalized to Juniper and Cisco CLI language.  These two vendors provide two different ends of the spectrum.   Additional references for other vendors could be added to draft-ietf-idr-migration-03, but since these features have been deployed for over 10 years – the features described are references on most vendors CLI-based configuration.   o Co-existence issues within the pre/post SIDR and the pre/post migration are adequately discussed.   o Security issues relating to SIDR architecture, trust models have been discussed along with backward compatibility to Non-SIDR.   ·          Network operation issues      SIDR’s references provide the details on the secure architecture, SIDR operations, and SIDR’s load so needed so no additional details are needed in this draft.   Fault-management and error reporting are also described in SIDR documents.   The SIDR protocol documents provide the description of how to configure, validate correct options, monitor and operate this feature.  This document provides the appropriate level of added description for the SIDR operations.