Re: [Banana] Problem Statement

[Tommy Pauly <[e-mail]>]

Hi Margaret,

This edit seems like a reasonable change to the milestones. The charter text itself does a good job of explaining the problem statement (aggregating links for bandwidth, reduced cost, and reliability), but the initial work of the WG will certainly involve further clarification of this problem statement, so the milestone update makes sense.

Thanks,
Tommy

> On Sep 19, 2017, at 5:22 AM, Margaret Cullen <[e-mail]> wrote:
> 
> Hi All,
> 
> Some people have indicated that they think it would be good to have a better understanding of the problem statement for BANANA.  As Suresh has pointed out, there is a move in the IETF to use informal means to gain WG agreement on support documentation, like problem statements and use cases, and to avoid making those blocking items for WG work.
> 
> In order to make sure that the problem is well-understood by everyone without blocking our other work, perhaps we could make the following change to the WG charter?
> 
> OLD: 
> 
> The BANANA WG is chartered to complete the following  work items:
> 	• Informally document/discuss BANANA usage scenarios in a non-archival document (e.g. Wiki, Google Doc, etc.)
> 
> NEW
> 
> The BANANA WG is chartered to complete the following  work items:
> 	• Informally document/discuss the BANANA problem statement and usage scenarios in non-archival documents (e.g. Wiki, Google Doc, etc.)
> 
> Thoughts?  Would this address the concerns of people who would like more discussion of the problem statement within the WG?
> 
> Thanks,
> Margaret
> 
> 
> 
> _______________________________________________
> Banana mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/banana