Hi Carsten: I'm not buying this.
The way the charter is worded we can do nothing on these issues because we are not chartered to and that would be distraction to the chartered items. If we wish to "fully understand what we want to do on these issues", then we need at least to charter a Problem Statement work. But I'd think that flow control and ECN are known well enough already so we could figure intuitively what they would do for 6LoWPAN; in that case, the question is really whether we think there's a need for those flow control and ECN to cover our own fragmentation, or not. It should not be rocket science for the people in this group to figure that out and I haven't seen disagreement so far. There's advanced work available from quite some time in this group on this issue, and taking that work out now seems a bit arbitrary to me. Pascal >-----Original Message----- >From: Carsten Bormann [mailto:[EMAIL PROTECTED] >Sent: jeudi 19 juin 2008 12:02 >To: Pascal Thubert (pthubert) >Cc: Carsten Bormann; Geoff Mulligan; 6lowpan >Subject: Re: [6lowpan] revised new new charter text > >On Jun 19 2008, at 11:38, Pascal Thubert (pthubert) wrote: > >> The work on fragment recovery and flow control is still missing. I did >> not figure that Carsten's mail meant that e should not do it. Did I >> miss >> something? > >My proposal was to spend some more time shaping these potential work >items instead of including them in this round. >Since we need to finish the charter now; we should not wait until we >fully understand what we want to do on these issues; we can always add >new work items later. > >Gruesse, Carsten _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
