Dear Scott, As currently defined in draft-boucadair-connectivity-provisioning-profile, IRS level is not in the scope.
IRS does not intervene in the same level as the proposed CPP but some IRS actions (e.g., tweak RIB entries, add a new routing topology (using MT-ISIS or MT-OSPF) or adding a new routing instance (OSPF-MI), etc.) can be used to put into effect a CPP...These actions can be also enforced using COPS or NETCONF or any other provisioning mechanism. Also, note translating a CPP into a network configuration may not be limited to routing actions: forwarding actions and resource control filters may be required too. As I see it, IRS is a tool among others which can be invoked to put into effect a CPP. Cheers, Med >-----Message d'origine----- >De : Scott Brim [mailto:[email protected]] >Envoyé : vendredi 12 octobre 2012 15:33 >À : BOUCADAIR Mohamed OLNC/OLN >Cc : [email protected] >Objet : Re: [Int-area] IP Connectivity Provisioning Profile >(draft-boucadair-connectivity-provisioning-profile) > >Would it be interesting to subsume IRS under this? > >https://datatracker.ietf.org/doc/draft-atlas-irs-problem-statement/ > _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
