[e2md] Shall we go this way? (was Re: Problem statement, Requirements and Use Cases (was RFC 5507 & RFC 5395))

Hi E2MD:ers

IMHO something along the lines of what Penn and Dean proposed "agree 
to analyze the problem(s) and solve each appropriately" (see below) 
is a viable strategy to get a E2MD WG approved. This implies a lot of 
wordsmithing to a charter...

We'd need to make a careful selection of initial use cases to be assessed 
in that WG. Furthermore we need a sophisticated strategy to drop certain 
use cases (from the initial list) during the WG forming BoF, if those are 
causing too much harm to the WG approval process. And we need 
Internet-Drafts describing the Use Cases before the WG forming BoF takes 
place.

My questions to all of you:

a) Do you also see this as a viable strategy?

b) Which timeframe do your believe is sensible (Maastricht or Beijing?)

c) Who is willing to actively assist the work on an agreeable charter?

d) Who is willing to write Internet-Drafts describing certain Use Cases?

We'll discuss this as part of tomorrow's conference call. However, 
some initial discussion on this list is most helpful to keep this 
discussion during the call as short as possible. Besides this, your 
opinion will be understood better if it is stated in written.

In case you do not agree with this strategy, please indicate to the list, 
how you believe we should go on with this matter!

cheers,
  Bernie

--

http://ucom.ch/
Tech Consulting for Internet Standardization

On Mon, 17 May 2010, Dean Willis wrote:

> On Mon, 2010-05-17 at 13:31 -0400, PFAUTZ, PENN L (ATTCORP) wrote:
>
>> Please sirs, may we have an e2md WG that will analyze proposed use 
>> cases guided by RFC 5507 & RFC 5395 and propose appropriate 
>> implementations?
>
>
> That probably would work. I think all we need to do is agree to analyze
> the problem(s) and solve each appropriately while respecting the
> "rules", rather than insisting on one-size-fits-all hack/slash on ENUM
> to define a framework for adding arbitrary metadata into NAPTR records.
>
> --
> Dean
>
> _______________________________________________
> e2md mailing list
> e2md@ietf.org
> https://www.ietf.org/mailman/listinfo/e2md
>