Benchmarking Methodology for In-Service Software Upgrade (ISSU)
draft-ietf-bmwg-issu-meth-02

[Ballot comment]

- I was a bit surprised there was no reference to software
signing here (only checksums are mentioned).  The
difference is that signature verification can also
sometimes require e.g. an OCSP lookup to check for
revocation and that could I guess impact on benchmarking.
(The secdir reviewer also made this point.)

- Kathleen makes a good point in her comment too.

[Ballot comment]

Section 3:
OLD
Note that, a given vendor implementation may or may not permit the abortion of
  the in-progress ISSU at particular stages.

NEW
Note that, a given vendor implementation may or may not permit halting the in-progress ISSU at particular stages.

OLD
the test
  plan document should reflect these and other relevant details and
  SHOULD be written with close attention

NEW
the test
  plan document should reflect these and other relevant details and
  should be written with close attention

[Ballot comment]
- Some discrepancies regarding MUST, SHOULD, MAY

One one side: The hardware configuration of the DUT SHOULD be identical to the one expected to be or currently deployed in production
One the other side: the feature, protocol timing and other relevant configurations should be matched to the expected production environment.

Note: potentially some other discrepancie with lower/upper case MUST/SHOULD/MAY

- expand "NSR"


nits:
- point missing in the abstract
- section 1 title is wrongly formatted

[Ballot comment]
In section 3, when "other checks" are described, I'd like to see an explicit mention of a check to ensure the device is authorized to install the software/firmware.  There have been numerous attacks against just about every vendor where counterfeit hardware is deployed and runs the firmware, OS, etc. issued.  Fraud can be a big issue and it isn't always talked about, but this should definitely be a security consideration.  I do think it fits in the subsections of section 3.  The statement added can be as simple as, "check performed to ensure the device is authorized to install the firmware".

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-bmwg-issu-meth-01, which is currently in Last Call, and has the following comments:

We understand that, upon approval of this document, there are no IANA Actions that need completion.

While it is helpful for the IANA Considerations section of the document to remain in place upon publication, if the authors prefer to remove it, IANA doesn't object.

If this assessment is not accurate, please respond as soon as possible.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (ISSU Benchmarking Methodology) to Informational RFC


The IESG has received a request from the Benchmarking Methodology WG
(bmwg) to consider the following document:
- 'ISSU Benchmarking Methodology'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-07-02. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bmwg-issu-meth/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-bmwg-issu-meth/ballot/


No IPR declarations have been submitted directly on this I-D.

This is a publication request for:
ISSU Benchmarking Methodology
draft-ietf-bmwg-issu-meth-01


Al Morton is the Document Shepherd, and prepared this form.

(1) What type of RFC is being requested (BCP, Proposed Standard, Internet Standard,
Informational, Experimental, or Historic)?
Why is this the proper type of RFC? Is this type of RFC indicated in the title page header?

Informational, as indicated on the title page.
All BMWG RFCs are traditionally Informational,
in part because they do not define protocols and
the traditional conditions for Stds track advancement
did not apply.  However, they are specifications and
the RFC 2119 terms are applicable to identify the
level of requirements.

(2) The IESG approval announcement includes a Document Announcement Write-Up.
Please provide such a Document Announcement Write-Up. Recent examples can be
found in the "Action" announcements for approved documents.
The approval announcement contains the following sections:

Technical Summary:

Many networking functions require operating software maintenance
during their useful life, and some require update on a frequent-enough
basis that there may be an operational challenge to keep sufficient
service capacity on-line due to the need to schedule upgrades during
quiet periods.  In response, network function developers have devised ways
minimize the operational impact of upgrades.  The methodology of this memo
assesses the affect of a software update on dataplane traffic. 

Working Group Summary:

Since this proposed the assessment of an operational characteristic
rather than measuring the usual benchmarking dimensions (how big? how many?),
there was considerable discussion to frame the problem so that
BMWG could adopt the work and relate it to existing methods.
Once the scope and purpose were clear, inclusion in re-chartering,
adoption and consensus followed very smoothly. The BMWG believes
this draft serves a useful purpose for the industry.

Document Quality:

Some of the major manufacturers whose products will be measured are
represented among the co-authors, and among those who supported the
draft through review.

Personnel:

Who is the Document Shepherd? Who is the Responsible Area Director?
Al Morton is Shepherd, Joel Jaeggli is Responsible AD.

(3) Briefly describe the review of this document that was performed by the
Document Shepherd. If this version of the document is not ready for
publication, please explain why the document is being forwarded to the IESG.

The shepherd has reviewed the drafts several times, and his comments are
in the BMWG list archive.

(4) Does the document Shepherd have any concerns about the depth or breadth
of the reviews that have been performed?
No.

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity,
AAA, DNS, DHCP, XML, or internationalization?
If so, describe the review that took place.

No.


(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the IESG
should be aware of? For example, perhaps he or she is uncomfortable with
certain parts of the document, or has concerns whether there really is a
need for it. In any event, if the WG has discussed those issues and has
indicated that it still wishes to advance the document, detail those
concerns here.

No concerns, this is still a valuable memo, as mentioned above.

(7) Has each author confirmed that any and all appropriate IPR disclosures
required for full conformance with the provisions of BCP 78 and BCP 79 have
already been filed. If not, explain why?

There are No outstanding IPR disclosures, according to the authors.

(8) Has an IPR disclosure been filed that references this document? If so, summarize
any WG discussion and conclusion regarding the IPR disclosures.

No.

(9) How solid is the WG consensus behind this document? Does it represent the strong
concurrence of a few individuals, with others being silent, or does the WG as a whole
understand and agree with it?

Although the comments and review intensity was highly variable,
it now appears that the WG is satisfied. 
The first WGLC was completed on March 2015 with comments.
The second WGLC was completed on April 2015 with minor comments.

(10) Has anyone threatened an appeal or otherwise indicated extreme discontent?
If so, please summarise the areas of conflict in separate email messages to
the Responsible Area Director. (It should be in a separate email because
this questionnaire is publicly available.)

No.

(11) Identify any ID nits the Document Shepherd has found in this document.
(See http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist).
Boilerplate checks are not enough; this check needs to be thorough.

No nits issues.

(12) Describe how the document meets any required formal review criteria,
such as the MIB Doctor, media type, and URI type reviews.

N/A

(13) Have all references within this document been identified as either
normative or informative?

Yes.

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

No.

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in
the Last Call procedure.

No.

(16) Will publication of this document change the status of any existing RFCs?
Are those RFCs listed on the title page header, listed in the abstract,
and discussed in the introduction? If the RFCs are not listed in the Abstract
and Introduction, explain why, and point to the part of the document where
the relationship of this document to the other RFCs is discussed. If this
information is not in the document, explain why the WG considers it unnecessary.

No.

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly identified.
Confirm that newly created IANA registries include a detailed specification
of the initial contents for the registry, that allocations procedures for
future registrations are defined, and a reasonable name for the new
registry has been suggested (see RFC 5226).

No requests of IANA.

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find useful
in selecting the IANA Experts for these new registries.

N/A

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal language,
such as XML code, BNF rules, MIB definitions, etc.

N/A