RFC 7654 on Benchmarking Methodology for In-Service Software Upgrade (ISSU)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.

        
        RFC 7654

        Title:      Benchmarking Methodology for In-Service Software 
                    Upgrade (ISSU) 
        Author:     S. Banks, F. Calabria,
                    G. Czirjak, R. Machat
        Status:     Informational
        Stream:     IETF
        Date:       October 2015
        Mailbox:    sbanks@encrypted.net, 
                    fcalabri@cisco.com, 
                    gczirjak@juniper.net,
                    rmachat@juniper.net
        Pages:      16
        Characters: 36991
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bmwg-issu-meth-02.txt

        URL:        https://www.rfc-editor.org/info/rfc7654

        DOI:        http://dx.doi.org/10.17487/RFC7654

Modern forwarding devices attempt to minimize any control- and
data-plane disruptions while performing planned software changes by
implementing a technique commonly known as In-Service Software
Upgrade (ISSU).  This document specifies a set of common methodologies
and procedures designed to characterize the overall behavior of a
Device Under Test (DUT), subject to an ISSU event.

This document is a product of the Benchmarking Methodology Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC





[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux