Re: update on draft-meadors-ediint-features-header and IANA review requested
Graham Klyne <GK@ninebynine.org> Mon, 14 June 2010 19:51 UTC
Return-Path: <owner-ietf-ediint@mail.imc.org>
X-Original-To: ietfarch-ediint-archive@core3.amsl.com
Delivered-To: ietfarch-ediint-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B4C53A694E for <ietfarch-ediint-archive@core3.amsl.com>; Mon, 14 Jun 2010 12:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.554
X-Spam-Level:
X-Spam-Status: No, score=0.554 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ajwQrvCfoUm0 for <ietfarch-ediint-archive@core3.amsl.com>; Mon, 14 Jun 2010 12:51:44 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 239D83A6936 for <ediint-archive@ietf.org>; Mon, 14 Jun 2010 12:51:43 -0700 (PDT)
Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5EJk8xr078650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Jun 2010 12:46:08 -0700 (MST) (envelope-from owner-ietf-ediint@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o5EJk8WL078649; Mon, 14 Jun 2010 12:46:08 -0700 (MST) (envelope-from owner-ietf-ediint@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-ediint@mail.imc.org using -f
Received: from relay4.mail.ox.ac.uk (relay4.mail.ox.ac.uk [129.67.1.163]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5EJk6uH078643 for <ietf-ediint@imc.org>; Mon, 14 Jun 2010 12:46:07 -0700 (MST) (envelope-from GK@ninebynine.org)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay4.mail.ox.ac.uk with esmtp (Exim 4.71) (envelope-from <GK@ninebynine.org>) id 1OOFbe-0007Rt-F1; Mon, 14 Jun 2010 20:46:02 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=Eskarina.local) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1OOFbe-0005bs-7N; Mon, 14 Jun 2010 20:46:02 +0100
Message-ID: <4C167A9A.1020903@ninebynine.org>
Date: Mon, 14 Jun 2010 19:53:14 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
CC: Kyle Meadors <kyle@drummondgroup.com>, 'Nevil Brownlee' <n.brownlee@auckland.ac.nz>, ietf-ediint@imc.org
Subject: Re: update on draft-meadors-ediint-features-header and IANA review requested
References: <9825BCA5935346C59E986A2A1C8B5B11@WorkLaptopSonyC> <4C1659DF.2060005@isode.com>
In-Reply-To: <4C1659DF.2060005@isode.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Sender: owner-ietf-ediint@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ediint/mail-archive/>
List-ID: <ietf-ediint.imc.org>
List-Unsubscribe: <mailto:ietf-ediint-request@imc.org?body=unsubscribe>
Alexey Melnikov wrote: > Hi Kyle, > > Kyle Meadors wrote: > >> To confirm, my next step would be to resubmit a new version of this draft >> but include this section below in the IANA consideration section. >> > Yes. > >> Question: >> do I need to specific the protocol as AS2/AS1/AS3 or HTTP/mail? >> >> This is a request for a permanent header registration. If it's a request for permanent registration, I'd be looking for adequate evidence of IETF consensus - a note from you (Alexey) would suffice. (Otherwise, I'd recommend registration as provisional until any applicable last-call process has been completed, with a view to promoting it at that point.) >> Header field name: EDIINT-Features >> Applicable protocol: AS2 (RFC 4130), AS1 (RFC 3335), AS3 (RFC 4823) >> >> > I think this should be one or more of "mail", "http" (per RFC 3864): > > Applicable protocol: > Specify "mail" (RFC 2822), "mime" (RFC 2045), "http" (RFC 2616), > "netnews" (RFC 1036), or cite any other standards-track RFC > defining the protocol with which the header is intended to be > used. Agreed. The comments about use with AS2, etc, would usefully be included in the "Related information" section of the template. >> Status: Informational >> Author/Change controller: IETF If this is "informational", is it properly under IETF change control? Or is there an EDIInt consortium or body that can more usefully be cited? >> Specification document(s): This I-D (will include a URI) As a process detail, I think the actual registration would then have to take place during the IANA considerations processing phase of RFC publication? Thus, I think we need to be clear that there's adequate consensus for a permanent registration before activating the publication process. That's an IESG call to make. >> Related information: None. #g -- >> -----Original Message----- >> From: Graham Klyne [mailto:GK@ninebynine.org] Sent: Saturday, June 12, >> 2010 2:17 AM >> To: Kyle Meadors >> Cc: 'Nevil Brownlee'; ietf-ediint@imc.org; 'Alexey Melnikov' >> Subject: Re: update on draft-meadors-ediint-features-header and IANA >> review >> requested >> >> 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 also note that the registration procedure is not cited, 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@drummondgroup.com <mailto:kyle@drummondgroup.com> >>> >>> >>> >>> 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. >>> >>> * * * * * * * * * * * * * * * * * * * * * * * * >>>
- update on draft-meadors-ediint-features-header an… Kyle Meadors
- Re: update on draft-meadors-ediint-features-heade… Graham Klyne
- Re: update on draft-meadors-ediint-features-heade… Alexey Melnikov
- Re: update on draft-meadors-ediint-features-heade… Alexey Melnikov
- RE: update on draft-meadors-ediint-features-heade… Kyle Meadors
- Re: update on draft-meadors-ediint-features-heade… Graham Klyne
- RE: update on draft-meadors-ediint-features-heade… Kyle Meadors
- Re: update on draft-meadors-ediint-features-heade… Alexey Melnikov
- Re: update on draft-meadors-ediint-features-heade… Graham Klyne
- Re: update on draft-meadors-ediint-features-heade… Alexey Melnikov