[Enum] Regarding brandner-compendium discussion in ATL

Hi all,

Now that the SIP and H323 enumservice drafts are published
<http://www.ietf.org/internet-drafts/draft-peterson-enum-sip-00.txt>
<http://www.ietf.org/internet-drafts/ draft-levin-enum-h323-00.txt>
we need to update the "compendium" draft.

Since both are describing enum services equivalent to the srs 
categorical enumservice, I propose to align the three IDs by changing 
the following sections of the 
<http://www.ietf.org/internet-drafts/draft-brandner-enumservices-compend
ium-00.txt>
as follows:

-begin-
19.  srs categorical enumservice
19.1. Description
This category is used where the Registrant wants to use a specialised 
"Service Resolution Service" above and beyond ENUM. It can be used 
where the services available depend on factors that cannot be covered 
in the global ENUM system; for example, the services "advertised" may 
depend on the person asking, and so requires authentication to be 
performed before any detailed information is returned.

19.2. Comprised Services 
This category comprises THREE main services; dap, H323 and 
sip. Of these, the 'sip' service AND H323 has a rich feature sets and 
will be described in a separate documents.

19.3. Expected Client Behaviour
If the end user has selected this as an "enumservice of interest" then
the client should filter out all NAPTRs but those containing either the
'srs', 'sip', 'H323' or 'dap' tags, together with any NAPTRs showing the
'all'
category and where the processed URIs indicate either "sip:", "H323" 
or "ldap:".

If the Registrant has chosen to include only a NAPTR with either the
'srs'
tag or that of one if its constituent enumservices, then the client can
either initiate the "next stage" of service resolution directly, or
report
that this is required and await the end user's response.
In either case, this is the end of ENUM processing; further evaluation
continues using the features of the constructed URI.

19.4. Associated URIs
At present, there are expected to be THREE URIs that can be associated
with
this category; "sip:", *H323" and "ldap:".
-end-

If there is any additional commments please let me know asap.

In addition, I would like to mention, that the enumservices according 
the the draft-brandner-enumservices-compendium-00.txt
have been implemented sucessfully in the Austrian ENUM Trial and the 
clients provided to the users. The trial is in operation since one 
month.

Interested parties are invited to contact me for a demo in Atlanta and 
also may be provided with links download different available clients.

best regards
Richard Stastny
_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum