[Enum] Trunk group document & Charter

[Lawrence Conroy <lconroy at insensate.co.uk>]

Hi Folks,
 I think we're agreed that the old Enumservice is dead. Richard shot  
it with his pearl-handled revolver.

Looking at the ENUM WG charter, which is what any good WG should do...

-  I note point 4 of the ENUM WG charter:
This document proposes using RFC 3761-like technology to store and  
deliver other
information about services addressed by E.164 numbers. It is certainly  
focussed
on PSTN call routing and signalling data.
=> This document fits right into that point, IMHO.

-  I also note, however, ENUM charter point 6, paragraph 2:
This is no longer about an Enumservice (thank goodness).
=> Have the AD(s) approved this *non-Enumservice* item?

I didn't see any mail to that effect on list. As we haven't HAD a
WG meeting since this change in the document, there has been no
chance for them to mention this agreement there either.

----
Assuming that this agreement does turn up on list, & the ADs don't  
want the ENUM WG to stop working just yet...
Who is willing to work on the problem?

The authors have asked for help (I guess, from domain experts) on the  
new process proposed in the document.

People on this ENUM list SHOULD have the right domain expertise --  
this is all about Naming and addressing.
It also involves routing. That kinda implies to me that there will be  
appropriate domain expertise amongst people on the SPEERMINT list.

So .. regardless of the target document status (it really doesn't  
matter at this point), is anyone going to help?
I'd suggest that assistance is requested via the SPEERMINT list **as  
well**, but focussing on ENUM list members...

I will try to review the document. Anyone else?

all the best,
  Lawrence