%% You should probably cite draft-unify-nfvrg-devops-06 instead of this revision.
@techreport{unify-nfvrg-devops-00,
    number =    {draft-unify-nfvrg-devops-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-unify-nfvrg-devops/00/},
    author =    {Catalin Meirosu and Antonio Manzalini and Juhoon Kim and Rebecca Steinert and Sachin Sharma and Guido Marchetto},
    title =     {{DevOps for Software-Defined Telecom Infrastructures}},
    pagetotal = 14,
    year =      2014,
    month =     oct,
    day =       27,
    abstract =  {The introduction of virtualization technologies, starting from the physical layer and going all the way up to the application plane, is transforming the telecom network infrastructure onto an agile, model- driven production environment for communication services. Carrier- grade network management was optimized for environments built with monolithic physical nodes and involves significant deployment, integration and maintenance efforts from network service providers. The DevOps movement in the data center is a source of inspiration regarding how to simplify and automate management processes for software-defined infrastructure. This first version of this draft identifies three areas that we consider key to applying DevOps principles in a telecom service provider environment, namely for monitoring, verification and troubleshooting processes. Finally, we introduce challenges associated with operationalizing DevOps principles at scale in software-defined telecom networks.},
}