Re: editorial comment to 2009-07 idnabis draft
Vint Cerf <vint@google.com> Thu, 16 July 2009 20:50 UTC
Return-Path: <vint@google.com>
X-Original-To: idna-update@alvestrand.no
Delivered-To: idna-update@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 05D7539E25B for <idna-update@alvestrand.no>; Thu, 16 Jul 2009 22:50:48 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hg2F0ataJlFv for <idna-update@alvestrand.no>; Thu, 16 Jul 2009 22:50:44 +0200 (CEST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.6.8
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 677C539E12B for <idna-update@alvestrand.no>; Thu, 16 Jul 2009 22:50:43 +0200 (CEST)
Received: from spaceape14.eur.corp.google.com (spaceape14.eur.corp.google.com [172.28.16.148]) by smtp-out.google.com with ESMTP id n6GKog4D015565 for <idna-update@alvestrand.no>; Thu, 16 Jul 2009 21:50:42 +0100
Received: from fg-out-1718.google.com (fge13.prod.google.com [10.86.5.13]) by spaceape14.eur.corp.google.com with ESMTP id n6GKoYAv011548 for <idna-update@alvestrand.no>; Thu, 16 Jul 2009 13:50:34 -0700
Received: by fg-out-1718.google.com with SMTP id 13so117756fge.12 for <idna-update@alvestrand.no>; Thu, 16 Jul 2009 13:50:34 -0700 (PDT)
From: Vint Cerf <vint@google.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcoGVSsvLFZeH9seTfmEgzIA/YKjcAAAeUOY
Date: Thu, 16 Jul 2009 21:50:33 +0100
Received: by 10.86.31.17 with SMTP id e17mr241494fge.47.1247777434062; Thu, 16 Jul 2009 13:50:34 -0700 (PDT)
Message-ID: <0ad001ca0657$104c07a0$30e416e0$@com>
Subject: Re: editorial comment to 2009-07 idnabis draft
To: klensin@jck.com, nicolas1.krebs3@netcourrier.com, idna-update@alvestrand.no
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-System-Of-Record: true
X-BeenThere: idna-update@alvestrand.no
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IDNA update work <idna-update.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=unsubscribe>
List-Archive: <http://www.alvestrand.no/pipermail/idna-update>
List-Post: <mailto:idna-update@alvestrand.no>
List-Help: <mailto:idna-update-request@alvestrand.no?subject=help>
List-Subscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2009 20:50:48 -0000
I think the conflict with editor's standards dictates no change. Perhaps the point might be made to the rfc editor as a matter of common interest? V ----- Original Message ----- From: idna-update-bounces@alvestrand.no <idna-update-bounces@alvestrand.no> To: Nicolas Krebs <nicolas1.krebs3@netcourrier.com>; idna-update@alvestrand.no <idna-update@alvestrand.no> Sent: Thu Jul 16 21:36:37 2009 Subject: Re: editorial comment to 2009-07 idnabis draft These suggestions increase work to stay synchronized with other document and are inconsistent with the RFC Editor's standards. Unless there is considerable belief on the part of the WG that making them would improve efficiency, I'm disinclined to make them. It would be less effort (although definitely not zero) to generate HTML versions of the documents along with the text ones; I'm more inclined to do that if there is really a requirement of this type. john --On Tuesday, July 14, 2009 00:18 +0200 Nicolas Krebs <nicolas1.krebs3@netcourrier.com> wrote: > Below is an editorial comment to three 2009-07 idnabis draft. > > The http://tools.ietf.org/html/ rfc to html conversion tool > can interpret text like "RFC 1034" and "RFC1034" as internal > html link, see by example > http://tools.ietf.org/html/draft-ietf-idnabis-protocol-13#sect > ion-2 . > > This conversion tool can also interpret references to I-D > (IETF internet draft), see by example links to > draft-ietf-idnabis-bidi-03 and draft-ietf-idnabis-defs-07 in > http://tools.ietf.org/html/draft-jet-idnabis-cjk-localmapping- > 01#section-10 and link to draft-ietf-idnabis-protocol-12 > ('<a > href="./draft-ietf-idnabis-protocol-12">draft-ietf-idnabis-pro > tocol-12</a>') in > http://tools.ietf.org/html/draft-ietf-idnabis-mappings-01#sect > ion-6 . > > So I suggest the idnabis WG to add plain text mention of > "draft-ietf-idnabis*-XX" after > "<https://datatracker.ietf.org/drafts/draft-ietf-idnabis-*-XX> > " in the "References" section of > - draft-ietf-idnabis-protocol-13 > http://tools.ietf.org/html/draft-ietf-idnabis-protocol-13#sect > ion-10 - draft-ietf-idnabis-rationale-10 > http://tools.ietf.org/html/draft-ietf-idnabis-rationale-10#sec > tion-14 - draft-ietf-idnabis-tables-05 > http://tools.ietf.org/html/draft-ietf-idnabis-tables-05#sectio > n-9 > > > > _______________________________________________ > Idna-update mailing list > Idna-update@alvestrand.no > http://www.alvestrand.no/mailman/listinfo/idna-update _______________________________________________ Idna-update mailing list Idna-update@alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update
- editorial comment to 2009-07 idnabis draft Nicolas Krebs
- Re: editorial comment to 2009-07 idnabis draft Patrik Fältström
- Re: editorial comment to 2009-07 idnabis draft John C Klensin
- Re: editorial comment to 2009-07 idnabis draft Vint Cerf
- Re: editorial comment to 2009-07 idnabis draft John C Klensin
- Re: editorial comment to 2009-07 idnabis draft Vint Cerf
- Re: editorial comment to 2009-07 idnabis draft Nicolas Krebs
- Re: editorial comment to 2009-07 idnabis draft John C Klensin
- Re: editorial comment to 2009-07 idnabis draft Patrik Fältström
- Re: editorial comment to 2009-07 idnabis draft John C Klensin
- Re: editorial comment to 2009-07 idnabis draft Nicolas Krebs