Re: ISSU Charter paragraph

Al. et all, 

This looks ok to me

Rgds 

Fernando 





On 1/20/14, 7:56 AM, "MORTON, ALFRED C (AL)" <[email protected]> wrote:

>Good edit Joel. Let's include that point in the last sentence:
>
>Quantification of Upgrade impact will include packet loss measurement,
>and other forms of recovery behavior will be noted accordingly.
>
>> -----Original Message-----
>> From: joel jaeggli [mailto:[email protected]]
>> Sent: Monday, January 20, 2014 1:57 AM
>> To: MORTON, ALFRED C (AL); [email protected]
>> Subject: Re: [bmwg] ISSU Charter paragraph
>> 
>> On 1/19/14, 7:51 PM, MORTON, ALFRED C (AL) wrote:
>> > 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.
>> 
>> Quantification of impact does seem like the key deliverable.
>> 
>> > 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. _______________________________________________ bmwg
>> > mailing list [email protected]
>> > https://www.ietf.org/mailman/listinfo/bmwg
>> >
>> 
>
>_______________________________________________
>bmwg mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/bmwg