Re: Enumservices categories (COMMON, X-, P-, ...)

Hi Duane et al.

On Mon, 3 Mar 2008, lconroy wrote:

> The issue is not confusion with mail headers. There is a difference 
> between email headers (or even old-style proprietary MIME types) and 
> Enumservices inside NAPTRs.

I also do not see any dependency issue between ENUM NAPTR types and other 
codepoints. For example SMTP does not have a too clear concept for mail 
headers (IMHO), i.e. 'X-' is used for different purposes:

1) widely used headers e.g. X-BeenThere, X-Mailer

2) private style headers e.g. X-MyCom-MailScanner-SpamCheck, 
X-Google-Sender-Auth

Should we really blindly take over concepts discovered to be problematic 
elsewhere  just for the sake of consistency? I'd say, Bad Idea!

> The proposal (for P- Enumservices) is quite different. These are 
> Enumservices that should never be on the Internet - no-one outside the 
> walled garden should see them.

I guess it cannot be avoided that P- Enumservices appear outside the 
walled garden. After all, it is in DNS, which normally is public.

Therefore the direction "clients SHOULD ignore them, if not part of to 
walled garden" is rather important.

> If a client DOES encounter one, it should be ignored. The URI may not be 
> interpretable outside the walled garden, so even if you think you know 
> what the Enumservice does, don't try it at home.

cheers,
  Bernie