Re: update on draft-meadors-ediint-features-header and IANA review requested

[Alexey Melnikov <alexey.melnikov@xxxxxxxxx>]

Graham Klyne wrote:

> Dear all,
>
> My apologies for the delay in dealing with this.
>
> My main comment is that there is no registration template per 
> http://tools.ietf.org/html/rfc3864.  Normally, I would expect to see 
> this template included in the IANA considerations section (which, as 
> it stands, isn't really about IANA considerations per se, but a 
> request for expert review - I think there may be a related process 
> issue here which I'll raise separately with Alexey), or submitted 
> separately to IANA per http://tools.ietf.org/html/rfc3864#ref-35
>
> For example, it's not clear to me if this is requesting provisional or 
> permanent registration.

I think after discussing this with you we agreed that the header should 
be registered as "provisional".

> I also note that the registration procedure is not cited,

Right, an Informative reference to RFC 3864 would help.

> which would probably be helpful, though I'm not sure that's a 
> requirement.
>
> As for the header field itself, I see no problem with it.
>
> #g
> --
>
>
> Kyle Meadors wrote:
>
> > Alexey, Nevil,
> >
> >  
> >
> > I have made the changes to the BNF and other comments and re-submit 
> > my I-D.
> >
> >  
> >
> > Graham,
> >
> >  
> >
> > Per conversation with Alexey, I am requesting an IANA expert review 
> > on a registering a new http and email header, EDIINT-Features. The 
> > request is in the I-D listed below.  Thank you.
> >
> >  
> >
> > http://datatracker.ietf.org/doc/draft-meadors-ediint-features-header/
> >
> >  
> >
> > Kyle Meadors
> >
> > Drummond Group Inc.
> >
> > Director of EHR Testing
> >
> > Principal, Test Process
> >
> > 817-709-1627
> >
> > kyle@xxxxxxxxxxxxxxxxx <mailto:kyle@xxxxxxxxxxxxxxxxx>
> >
> >  
> >
> > Calendar: http://tinyurl.com/KyleMeadors-DGI-Calendar
> >
> >  
> >
> > * * * * * * * * * * * * * * * * * * * * * * * *
> >
> > CONFIDENTIALITY DISCLAIMER
> >
> > This email, including attachments, is confidential and proprietary. 
> > It constitutes exclusive communication solely to the addressee. Any 
> > entity other than the intended addressee is prohibited from use of 
> > this communication for any purpose. This email, including 
> > attachments, may not be distributed, whole or in part.
> >
> > * * * * * * * * * * * * * * * * * * * * * * * *
> >
> >  


--
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address