Re: A thought... Re: BOF Speakers Needed

["John G. Waclawsky" <jgw@cisco.com>]

This brings me back to my original question. How do we know what has or is
being looked at so we can better "focus" the document. While I agree some of
this can and should be done up front to reduce redundancy... but isn't one of
the purposes of the BOF to better identify overlap with IETF activities and
omissions too. I may be misinterpreting what is expected as input and output
to a BOF. Are there rules and regulations somewhere?  Regards  John

grenville armitage wrote:

> > The
> > idea behind this BOF is to discuss the requirements in
> > draft-reynolds-mobile-isp-requirements-00.txt and present any additional
> > requirements for wireless ISPs.
>
> At the risk of sounding negative, I'd suggest the BOF also
> discuss how to *remove* requirements from the cited draft.
>
> Having looked through the document, it seems that upwards
> of 30% of the listed requirements aren't specific to the
> "wireless Internet" or "Mobile ISP" communities. There is
> a lot of good stuff in there that qualifies as "the functionality
> any good ISP would want to have". But I'd suggest taking scissors
> to anything that isn't specifically a unique requirement to support
> mobility or roaming. (e.g. much of the text relating to security,
> authentication, accounting, etc isn't really unique...)  You'll
> end up with a more focussed document that will make it easier to
> explain to the rest of the IETF what MORE is trying to contribute.
>
> cheers,
> gja
> ____________________________________________________________________
> Grenville Armitage                http://members.home.net/garmitage/