ISSU Charter paragraph

BMWG,

As we continue to build our new charter step-by-step, here's
the first draft paragraph Sarah and I put together for your review:

In Service Software Upgrade (ISSU): Develop new methods and benchmarks to characterize the upgrade of network devices while in-service, considering both data and control plane operations and impacts. These devices are generally expected to maintain control plane session integrity, including routing connections. Packet loss should be measured and recovery behavior noted accordingly.

We'd like to have any comments on this proposal in the next 2 weeks.

As a reminder, we have already reviewed the items below,
and we have at least one or more items to sort-out before we
re-charter.

regards,
Sarah and Al


* Traffic Management: Develop the methods to characterize the capacity of
traffic management features in network devices, such as classification, 
policing, shaping, and active queue management. 
Existing terminology will be used where appropriate.
Configured operation will be verified as a part of the methodology.   
The goal is a methodology to assess the maximum forwarding performance that a
network device can sustain without dropping or impairing packets, or
compromising the accuracy of multiple instances of traffic management
functions. This is the benchmark for comparison between devices.
Another goal is to devise methods that utilize flows with congestion-aware 
transport as part of the traffic load and still produce repeatable results in
the isolated test environment.

-=-=-=-=-=-=-=-=-=-

IPv6 Neighbor Discovery-related benchmarking:
Large address space in IPv6 subnets presents several networking 
challenges, as described in RFC 6583. Indexes to describe the 
performance of network devices, such as the number of reachable
devices on a sub-network, are useful benchmarks to the operations
community. The working group will develop the necessary terminology
and methodologies to measure such benchmarks.