From chiaki.ishikawa@ubin.jp Tue Jan 10 20:50:02 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E183A21F85DA for ; Tue, 10 Jan 2012 20:50:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.831 X-Spam-Level: * X-Spam-Status: No, score=1.831 tagged_above=-999 required=5 tests=[AWL=0.316, BAYES_00=-2.599, DEAR_SOMETHING=1.605, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HG-epkPdf74R for ; Tue, 10 Jan 2012 20:50:01 -0800 (PST) Received: from post.ubin.jp (post.ubin.jp [202.32.0.84]) by ietfa.amsl.com (Postfix) with ESMTP id F2E6721F85C4 for ; Tue, 10 Jan 2012 20:50:00 -0800 (PST) Received: from localhost (post [127.0.0.1]) by localhost.ubin.jp (Postfix) with SMTP id 85F5629AE0C for ; Wed, 11 Jan 2012 13:49:49 +0900 (JST) Received: from home.intra.ubin.jp (home.intra.ubin.jp [10.129.1.1]) by post.ubin.jp (Postfix) with ESMTP id BA9C329AE0C; Wed, 11 Jan 2012 13:49:47 +0900 (JST) Received: from localhost (localhost.localdomain [127.0.0.1]) by home.intra.ubin.jp (Postfix) with ESMTP id C3B60426988; Wed, 11 Jan 2012 13:49:56 +0900 (JST) X-Virus-Scanned: amavisd-new at ubin.jp Received: from home.intra.ubin.jp ([127.0.0.1]) by localhost (home.intra.ubin.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-zVi+6ggWga; Wed, 11 Jan 2012 13:49:56 +0900 (JST) Received: from [10.254.225.253] (debian-vbox-ci.ddns.intra.ubin.jp [10.254.225.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by home.intra.ubin.jp (Postfix) with ESMTP id 05E4542659B; Wed, 11 Jan 2012 13:49:56 +0900 (JST) Message-ID: <4F0D14F7.9000506@ubin.jp> Date: Wed, 11 Jan 2012 13:49:59 +0900 From: ishikawa User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: urn-nid@apps.ietf.org Subject: Re: A request for formal registration of "ucode" as URN References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> In-Reply-To: <4EF7E1B0.8000504@ubin.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: ishikawa X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 04:50:02 -0000 Hi, I know that the new year and other holidays got in the work flow (initial two week review), but I wonder if there are any comments to the formal request I sent. Thank you in advance for your attention. Sincerely, Chiaki Ishikawa On (2011年12月26日 11:53), ishikawa wrote: > FYI, the document is now accessible from > > https://datatracker.ietf.org/doc/draft-ishikawa-yrpunl-ucode-urn/ > > TIA and a Happy New Year to all. > > Sincerely, > Chiaki Ishikawa > > On (2011年12月22日 19:51), ishikawa wrote: >> Dear sirs/madams, >> >> After my initial submission attempt, I received an e-mail from >> Alfred Hoenes, the co-chair of URNBIS. Per his suggestion, I cancelled the >> original submission and re-named the document to >> >> draft-ishikawa-yrpunl-ucode-urn-00 >> >> and resubmitted. >> >> Attached the modified submission draft. >> I changed the reference to urnbis in the left column heading of the first >> page to urn also. (The date is also bumped by one. The date of the IETF >> server seems to have changed.) >> >> Thank you in advance for your attention. >> >> Sincerely, >> Chiaki Ishikawa >> >>> Speaking as an URNbis co-chair: >>> >>> IMHO, work on new URN namespaces, and hence this draft, >>> currently is out of charter for URNBIS working group >>> (cf. http://datatracker.ietf.org/wg/urnbis/charter/ ). >>> Hence, this draft should be submitted as an individual draft. >>> >>> Andy, do you agree? >>> If so, please act upon the formal refusal. >>> >>> Authors, please re-submit as draft-ishikawa-yrpunl-ucode-urn-00, >>> draft-ishikawa-urnbis-yrpunl-ucode-00, or similar. >>> >>> Kind regards, >>> Alfred H�nes. >>> >>> -- >>> +------------------------+--------------------------------------------+ | >>> TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | >>> Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 >>> Ditzingen | E-Mail: ah@TR-Sys.de | >>> +------------------------+--------------------------------------------+ >> >> >> On (2011年12月22日 14:37), ishikawa wrote: >>> Dear sirs/madams, >>> >>> Allow me to introduce myself. >>> >>> I am Chiaki Ishikawa of YRP Ubiquitous Networking Laboratory. >>> My office is an executive member of an NPO called T-Engine Forum which, >>> among other things, administrates uID Center which, in turn, manages >>> an identifier code system called "ucode". >>> >>> Here with the request of the team at uID center and the chair of T-Engine >>> Forum, I am applying for >>> the formal registration of "ucode". >>> >>> Attached is the copy of document with the document name which I am trying to >>> submit to IETF. >>> >>> draft-ietf-urnbis-yrpunl-ucode >>> >>> It is at the initial approval stage: >>> >>> https://datatracker.ietf.org/submit/status/37780/request/ >>> >>> So I think I am at the initial stage (step 2) of the following procedure. >>> (Instead of sending the Internet-Draft, I used the the mechanical submission >>> process since it seems preferred. But I am not entirely sure >>> when the initial approval stage passes. Hmm ...) >>> >>> Formal NID: >>> >>> 1. Write an Internet-Draft describing the namespace and include >>> the registration template, duly completed. Be sure to include >>> "Namespace Considerations", "Community Considerations" and >>> "IANA Considerations" sections, as described in Section 4.3. >>> >>> 2. Send the Internet-Draft to the I-D editor, and send a copy to >>> urn-nid@apps.ietf.org for technical review. >>> >>> 3. Update the Internet-Draft as necessary from comments, and >>> repeat steps 2 and 3 as needed. >>> >>> 4. Send a request to the IESG to publish the I-D as an RFC. The >>> IESG may request further changes (published as I-D revisions) >>> and/or direct discussion to designated working groups, area >>> experts, etc. >>> >>> 5. If the IESG approves the document for publication as an RFC, >>> send a request to IANA to register the requested NID. >>> >>> Please feel free to ask me questions. >>> >>> Thank you in advance for your attention. >>> >>> I wish you all a pleasant holiday season and a Happy New Year. >>> >>> Sincerely, >>> Chiaki Ishikawa >> > From ted.ietf@gmail.com Wed Jan 11 10:08:27 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E63A11E8094 for ; Wed, 11 Jan 2012 10:08:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.626 X-Spam-Level: X-Spam-Status: No, score=-2.626 tagged_above=-999 required=5 tests=[AWL=-0.632, BAYES_00=-2.599, DEAR_SOMETHING=1.605, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i2NGQ4sivDH7 for ; Wed, 11 Jan 2012 10:08:26 -0800 (PST) Received: from mail-gy0-f177.google.com (mail-gy0-f177.google.com [209.85.160.177]) by ietfa.amsl.com (Postfix) with ESMTP id 8708811E8086 for ; Wed, 11 Jan 2012 10:08:20 -0800 (PST) Received: by ghrr15 with SMTP id r15so575467ghr.22 for ; Wed, 11 Jan 2012 10:08:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=SuaRfFp037T6CiPqwaZEP1WeE6nx5l/XR+h9Mxwj3rs=; b=UsdMrDuKinrbysUuSECGEnvCO6FH4HKI4rFz251mwcDkAyvuj3zcCezQrUJjunknay v8B26qBABrEm95cdkCMCFLXgJKCs57cnjxXDMWxru8VIVArSnUaHZX2gjNJbi7l5+VtQ y9UYAX2xK+R5zZjL+MwOB6Y+horg+ZBnMk6kE= MIME-Version: 1.0 Received: by 10.236.157.10 with SMTP id n10mr33810752yhk.41.1326305300044; Wed, 11 Jan 2012 10:08:20 -0800 (PST) Received: by 10.236.116.165 with HTTP; Wed, 11 Jan 2012 10:08:20 -0800 (PST) In-Reply-To: <4F0D14F7.9000506@ubin.jp> References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> Date: Wed, 11 Jan 2012 10:08:20 -0800 Message-ID: Subject: Re: A request for formal registration of "ucode" as URN From: Ted Hardie To: ishikawa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 18:08:27 -0000 Ishikawa-san, Thank you very much for your note. I have reviewed the formal registration request, and I believe it is complete and largely correct. I would like to ask one clarifying question. As written now, the production seems to allow only the use of upper case A-F: =3D "0" / "1" / "2" / "3" / "4" / "5" / "6" / "7" / "8" / "9" / "A" / "B" / "C" / "D" / "E" / "F" I would suggest that it permit the use of lower case la-f as well, even if the preferred presentation format of the name uses the upper case. There are many hexadecimal representations which do not distinguish between the two, so I believe it would be better practice to permit them. Thanks again for the opportunity to review your draft, regards, Ted Hardie On Tue, Jan 10, 2012 at 8:49 PM, ishikawa wrote: > Hi, > > I know that the new year and other holidays got in the > work flow (initial two week review), > but I wonder if there are any comments to the > formal request I sent. > > > Thank you in advance for your attention. > > Sincerely, > Chiaki Ishikawa > > On (2011=E5=B9=B412=E6=9C=8826=E6=97=A5 11:53), ishikawa wrote: >> >> FYI, the document is now accessible from >> >> https://datatracker.ietf.org/doc/draft-ishikawa-yrpunl-ucode-urn/ >> >> TIA and a Happy New Year to all. >> >> Sincerely, >> Chiaki Ishikawa >> >> On (2011=E5=B9=B412=E6=9C=8822=E6=97=A5 19:51), ishikawa wrote: >>> >>> Dear sirs/madams, >>> >>> After my initial submission attempt, I received an e-mail from >>> Alfred Hoenes, the co-chair of URNBIS. Per his suggestion, I cancelled >>> the >>> original submission and re-named the document to >>> >>> draft-ishikawa-yrpunl-ucode-urn-00 >>> >>> and resubmitted. >>> >>> Attached the modified submission draft. >>> I changed the reference to urnbis in the left column heading of the fir= st >>> page to urn also. (The date is also bumped by one. The date of the IETF >>> server seems to have changed.) >>> >>> Thank you in advance for your attention. >>> >>> Sincerely, >>> Chiaki Ishikawa >>> >>>> Speaking as an URNbis co-chair: >>>> >>>> IMHO, work on new URN namespaces, and hence this draft, >>>> currently is out of charter for URNBIS working group >>>> (cf. http://datatracker.ietf.org/wg/urnbis/charter/ ). >>>> Hence, this draft should be submitted as an individual draft. >>>> >>>> Andy, do you agree? >>>> If so, please act upon the formal refusal. >>>> >>>> Authors, please re-submit as draft-ishikawa-yrpunl-ucode-urn-00, >>>> draft-ishikawa-urnbis-yrpunl-ucode-00, or similar. >>>> >>>> Kind regards, >>>> Alfred H=EF=BF=BDnes. >>>> >>>> -- >>>> +------------------------+--------------------------------------------= + >>>> | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | >>>> Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 >>>> Ditzingen | E-Mail: ah@TR-Sys.de | >>>> +------------------------+--------------------------------------------= + >>> >>> >>> >>> On (2011=E5=B9=B412=E6=9C=8822=E6=97=A5 14:37), ishikawa wrote: >>>> >>>> Dear sirs/madams, >>>> >>>> Allow me to introduce myself. >>>> >>>> I am Chiaki Ishikawa of YRP Ubiquitous Networking Laboratory. >>>> My office is an executive member of an NPO called T-Engine Forum which= , >>>> among other things, administrates uID Center which, in turn, manages >>>> an identifier code system called "ucode". >>>> >>>> Here with the request of the team at uID center and the chair of >>>> T-Engine >>>> Forum, I am applying for >>>> the formal registration of "ucode". >>>> >>>> Attached is the copy of document with the document name which I am >>>> trying to >>>> submit to IETF. >>>> >>>> draft-ietf-urnbis-yrpunl-ucode >>>> >>>> It is at the initial approval stage: >>>> >>>> https://datatracker.ietf.org/submit/status/37780/request/ >>>> >>>> So I think I am at the initial stage (step 2) of the following >>>> procedure. >>>> (Instead of sending the Internet-Draft, I used the the mechanical >>>> submission >>>> process since it seems preferred. But I am not entirely sure >>>> when the initial approval stage passes. Hmm ...) >>>> >>>> Formal NID: >>>> >>>> 1. Write an Internet-Draft describing the namespace and include >>>> the registration template, duly completed. Be sure to include >>>> "Namespace Considerations", "Community Considerations" and >>>> "IANA Considerations" sections, as described in Section 4.3. >>>> >>>> 2. Send the Internet-Draft to the I-D editor, and send a copy to >>>> urn-nid@apps.ietf.org for technical review. >>>> >>>> 3. Update the Internet-Draft as necessary from comments, and >>>> repeat steps 2 and 3 as needed. >>>> >>>> 4. Send a request to the IESG to publish the I-D as an RFC. The >>>> IESG may request further changes (published as I-D revisions) >>>> and/or direct discussion to designated working groups, area >>>> experts, etc. >>>> >>>> 5. If the IESG approves the document for publication as an RFC, >>>> send a request to IANA to register the requested NID. >>>> >>>> Please feel free to ask me questions. >>>> >>>> Thank you in advance for your attention. >>>> >>>> I wish you all a pleasant holiday season and a Happy New Year. >>>> >>>> Sincerely, >>>> Chiaki Ishikawa >>> >>> >> > > From stpeter@stpeter.im Wed Jan 11 14:27:08 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCDC121F8691 for ; Wed, 11 Jan 2012 14:27:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.817 X-Spam-Level: X-Spam-Status: No, score=-102.817 tagged_above=-999 required=5 tests=[AWL=-0.218, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IE3OekXrAVcl for ; Wed, 11 Jan 2012 14:27:08 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA6E21F8690 for ; Wed, 11 Jan 2012 14:27:08 -0800 (PST) Received: from normz.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C00E640058; Wed, 11 Jan 2012 15:36:09 -0700 (MST) Message-ID: <4F0E0CBA.1020806@stpeter.im> Date: Wed, 11 Jan 2012 15:27:06 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Ted Hardie Subject: Re: A request for formal registration of "ucode" as URN References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> In-Reply-To: X-Enigmail-Version: 1.3.4 OpenPGP: url=https://stpeter.im/stpeter.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: ishikawa , urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 22:27:08 -0000 On 1/11/12 11:08 AM, Ted Hardie wrote: > Ishikawa-san, > > Thank you very much for your note. I have reviewed the formal > registration request, and I believe it is complete and largely > correct. I would like to ask one clarifying question. As written > now, the production seems to allow only the use of upper > case A-F: > > = "0" / "1" / "2" / "3" / "4" / "5" / "6" / "7" / > "8" / "9" / "A" / "B" / "C" / "D" / "E" / "F" > > I would suggest that it permit the use of lower case la-f as well, > even if the preferred presentation format of the name uses the upper > case. There are many hexadecimal representations which do not > distinguish between the two, so I believe it would be better practice > to permit them. Hi Ted, That would be inconsistent with this sentence in Section 2 of draft-ishikawa-yrpunl-ucode-urn: The entire UCODE-URN is case-sensitive. Peter -- Peter Saint-Andre http://stpeter.im/ From ted.ietf@gmail.com Wed Jan 11 14:32:58 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6347A21F875D for ; Wed, 11 Jan 2012 14:32:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.358 X-Spam-Level: X-Spam-Status: No, score=-3.358 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mF3sEg106ZwG for ; Wed, 11 Jan 2012 14:32:56 -0800 (PST) Received: from mail-yx0-f177.google.com (mail-yx0-f177.google.com [209.85.213.177]) by ietfa.amsl.com (Postfix) with ESMTP id D86BD21F875C for ; Wed, 11 Jan 2012 14:32:55 -0800 (PST) Received: by yenl2 with SMTP id l2so749640yen.22 for ; Wed, 11 Jan 2012 14:32:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=uPIq3WG4moRpvLiG4sBVWoZXZtadupTCR12S9QiSj/Y=; b=EFrQfeyxjJvZpSWa9CFRt+kz9MDHiiFpx+ZjE6lVVgztsjtM5/e6QoXVkems+Ez7EJ ujsqwsGQdniTIKDiNpunM5rKLPcS+VAP3R8J2F+tJMqd0PK4SaS+PtHAQh1oGdfNt/u0 1M4E0BAom4MGLmVjR02MADO6eTM2tjk8i9y4I= MIME-Version: 1.0 Received: by 10.236.157.10 with SMTP id n10mr1425811yhk.41.1326321174362; Wed, 11 Jan 2012 14:32:54 -0800 (PST) Received: by 10.236.116.165 with HTTP; Wed, 11 Jan 2012 14:32:54 -0800 (PST) In-Reply-To: <4F0E0CBA.1020806@stpeter.im> References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> <4F0E0CBA.1020806@stpeter.im> Date: Wed, 11 Jan 2012 14:32:54 -0800 Message-ID: Subject: Re: A request for formal registration of "ucode" as URN From: Ted Hardie To: Peter Saint-Andre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: ishikawa , urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 22:32:58 -0000 On Wed, Jan 11, 2012 at 2:27 PM, Peter Saint-Andre wro= te: > >> I would suggest that it permit the use of lower case la-f as well, >> even if the preferred presentation format of the name uses the upper >> case. =A0There are many hexadecimal representations which do not >> distinguish between the two, so I believe it would be better practice >> to permit them. > > Hi Ted, > > That would be inconsistent with this sentence in Section 2 of > draft-ishikawa-yrpunl-ucode-urn: > > =A0 The entire UCODE-URN is case-sensitive. > I understand. From a registration perspective, this is clear. But from a practice perspective, it is my personal advice that this will likely lead to problems, because many hexadecimal parsers would treat a and A as equivalent. The authors are, of course, free to discard this suggestion if the constraints on their system are such that this will not arise. Ted > Peter > > -- > Peter Saint-Andre > http://stpeter.im/ From chiaki.ishikawa@ubin.jp Fri Jan 13 00:08:26 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1938C21F85CF for ; Fri, 13 Jan 2012 00:08:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.265 X-Spam-Level: * X-Spam-Status: No, score=1.265 tagged_above=-999 required=5 tests=[AWL=0.755, BAYES_50=0.001, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ffsyqXl80CV9 for ; Fri, 13 Jan 2012 00:08:25 -0800 (PST) Received: from post.ubin.jp (post.ubin.jp [202.32.0.84]) by ietfa.amsl.com (Postfix) with ESMTP id 11A6321F85CD for ; Fri, 13 Jan 2012 00:08:24 -0800 (PST) Received: from localhost (post [127.0.0.1]) by localhost.ubin.jp (Postfix) with SMTP id 906D329AC35; Fri, 13 Jan 2012 17:08:11 +0900 (JST) Received: from home.intra.ubin.jp (home.intra.ubin.jp [10.129.1.1]) by post.ubin.jp (Postfix) with ESMTP id A41FF29AC35; Fri, 13 Jan 2012 17:08:08 +0900 (JST) Received: from localhost (localhost.localdomain [127.0.0.1]) by home.intra.ubin.jp (Postfix) with ESMTP id BCCC542699F; Fri, 13 Jan 2012 17:08:17 +0900 (JST) X-Virus-Scanned: amavisd-new at ubin.jp Received: from home.intra.ubin.jp ([127.0.0.1]) by localhost (home.intra.ubin.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J1MnHwRIsk6a; Fri, 13 Jan 2012 17:08:16 +0900 (JST) Received: from [10.254.225.253] (debian-vbox-ci.ddns.intra.ubin.jp [10.254.225.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by home.intra.ubin.jp (Postfix) with ESMTP id 1072B426157; Fri, 13 Jan 2012 17:08:16 +0900 (JST) Message-ID: <4F0FE671.6070709@ubin.jp> Date: Fri, 13 Jan 2012 17:08:17 +0900 From: ishikawa User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Ted Hardie Subject: Re: A request for formal registration of "ucode" as URN References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> <4F0E0CBA.1020806@stpeter.im> In-Reply-To: Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 08:08:26 -0000 Dear Ted and Peter, This is Chiaki Ishikawa. Thank you for your comments. I take the suggestion from TED seriously, and I checked with the original developer of the specification for the intention behind the "case-sensitive" nature. It turns out that the hexadecimal string that represents ucode in urn would be directly translated into XML tags in some of the intended applications. (Some of them anyway.) XML tags are case-sensitive and that is why the capital letters only are allowed for hexadecimal "A", "B", "C", "D", "E" and "F" for keeping the uniqueness issue of XML tag names under control. (So I take that conversion to numeric value is less of an issue for this particular class of applications. XML is processed in character string space more or less.) So because of the nature of some planned applications (and some of them are large-scale deployment), this case-sensitivity dictating the use of capital letters only for hexadecimal string must be there. That is the comment from the ucode designers and ucode application developers. Thank you for your valuable time. Sincerely, Chiaki Ishikawa On (2012$BG/(B01$B7n(B12$BF|(B 07:32), Ted Hardie wrote: > On Wed, Jan 11, 2012 at 2:27 PM, Peter Saint-Andre wrote: >> >>> I would suggest that it permit the use of lower case la-f as well, >>> even if the preferred presentation format of the name uses the upper >>> case. There are many hexadecimal representations which do not >>> distinguish between the two, so I believe it would be better practice >>> to permit them. >> >> Hi Ted, >> >> That would be inconsistent with this sentence in Section 2 of >> draft-ishikawa-yrpunl-ucode-urn: >> >> The entire UCODE-URN is case-sensitive. >> > > I understand. From a registration perspective, this is clear. But > from a practice perspective, it is my personal advice that this will > likely lead to problems, because many hexadecimal parsers would treat > a and A as equivalent. The authors are, of course, free to discard > this suggestion if the constraints on their system are such that this > will not arise. > > Ted > > >> Peter >> >> -- >> Peter Saint-Andre >> http://stpeter.im/ > From ted.ietf@gmail.com Fri Jan 13 09:07:47 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6276021F85F1 for ; Fri, 13 Jan 2012 09:07:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.402 X-Spam-Level: X-Spam-Status: No, score=-4.402 tagged_above=-999 required=5 tests=[AWL=1.197, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jllAnCL1-QSn for ; Fri, 13 Jan 2012 09:07:46 -0800 (PST) Received: from mail-yw0-f49.google.com (mail-yw0-f49.google.com [209.85.213.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE2721F858F for ; Fri, 13 Jan 2012 09:07:46 -0800 (PST) Received: by yhjj72 with SMTP id j72so441129yhj.22 for ; Fri, 13 Jan 2012 09:07:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=r/rAFU5SACtCPWMZB79/LUa4TSE41bB9YCKanwhrtKk=; b=JMQUT0G8Mws7dT4VLaZwx+/ob3lTGcyX/vUOVbUeTGDihq8jRnz1qWUfI7rG9pOPkX idVsyBzU7GYVh6AQYaCKA63+SoqBAf3UxfE/hsQi45bCYF2sgtmgXtRBDQLG7+gsJ95s Bso1ifyNscsDok+x1XVsRZtn8eQrVDCLqAdI8= MIME-Version: 1.0 Received: by 10.236.121.168 with SMTP id r28mr3156532yhh.51.1326474465087; Fri, 13 Jan 2012 09:07:45 -0800 (PST) Received: by 10.236.116.165 with HTTP; Fri, 13 Jan 2012 09:07:45 -0800 (PST) In-Reply-To: <4F0FE671.6070709@ubin.jp> References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> <4F0E0CBA.1020806@stpeter.im> <4F0FE671.6070709@ubin.jp> Date: Fri, 13 Jan 2012 09:07:45 -0800 Message-ID: Subject: Re: A request for formal registration of "ucode" as URN From: Ted Hardie To: ishikawa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 17:07:47 -0000 Dear Ishikawa-san, Thank you for your careful consideration of the message. With this data, I believe that this registration is ready to proceed. regards, Ted 2012/1/13 ishikawa : > Dear Ted and Peter, > > This is Chiaki Ishikawa. > > Thank you for your comments. > > I take the suggestion from TED seriously, and > I checked with the original developer of the specification for the > intention behind the "case-sensitive" nature. > > It turns out that the hexadecimal string that represents ucode in urn > would be directly translated into XML tags in some of > the intended applications. (Some of them anyway.) > > XML tags are case-sensitive and that is why the capital letters only are > allowed for hexadecimal "A", "B", "C", "D", "E" and "F" for keeping the > uniqueness issue of XML tag names under control. > > (So I take that conversion to numeric value is less of an issue > for this particular class of applications. XML is processed in character > string space more or less.) > > So because of the nature of some planned applications (and some of them a= re > large-scale deployment), this case-sensitivity dictating the use of =C2= =A0capital > letters only for hexadecimal string must be there. That is the comment fr= om > the ucode designers and ucode application developers. > > Thank you for your valuable time. > > Sincerely, > Chiaki Ishikawa > > On (2012=E5=B9=B401=E6=9C=8812=E6=97=A5 07:32), Ted Hardie wrote: >> On Wed, Jan 11, 2012 at 2:27 PM, Peter Saint-Andre = =C2=A0wrote: >>> >>>> I would suggest that it permit the use of lower case la-f as well, >>>> even if the preferred presentation format of the name uses the upper >>>> case. =C2=A0There are many hexadecimal representations which do not >>>> distinguish between the two, so I believe it would be better practice >>>> to permit them. >>> >>> Hi Ted, >>> >>> That would be inconsistent with this sentence in Section 2 of >>> draft-ishikawa-yrpunl-ucode-urn: >>> >>> =C2=A0 =C2=A0The entire UCODE-URN is case-sensitive. >>> >> >> I understand. =C2=A0From a registration perspective, this is clear. =C2= =A0But >> from a practice perspective, it is my personal advice that this will >> likely lead to problems, because many hexadecimal parsers would treat >> a and A as equivalent. =C2=A0The authors are, of course, free to discard >> this suggestion if the constraints on their system are such that this >> will not arise. >> >> Ted >> >> >>> Peter >>> >>> -- >>> Peter Saint-Andre >>> http://stpeter.im/ >> > > From stpeter@stpeter.im Fri Jan 13 09:12:03 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D206421F84E7 for ; Fri, 13 Jan 2012 09:12:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.568 X-Spam-Level: X-Spam-Status: No, score=-103.568 tagged_above=-999 required=5 tests=[AWL=1.031, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BL519tof5ZeA for ; Fri, 13 Jan 2012 09:12:03 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 19BEF21F84DC for ; Fri, 13 Jan 2012 09:12:03 -0800 (PST) Received: from dhcp-64-101-72-243.cisco.com (unknown [64.101.72.243]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id CADD840058; Fri, 13 Jan 2012 10:21:09 -0700 (MST) Message-ID: <4F1065E1.7080208@stpeter.im> Date: Fri, 13 Jan 2012 10:12:01 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Ted Hardie Subject: Re: A request for formal registration of "ucode" as URN References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> <4F0E0CBA.1020806@stpeter.im> <4F0FE671.6070709@ubin.jp> In-Reply-To: X-Enigmail-Version: 1.3.4 OpenPGP: url=https://stpeter.im/stpeter.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: ishikawa , urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 17:12:03 -0000 Yes, I agree. I shall initiate IETF Last Call on this specification, so that the IESG can consider it before the end of my term at IETF 83. On 1/13/12 10:07 AM, Ted Hardie wrote: > Dear Ishikawa-san, > > Thank you for your careful consideration of the message. With this > data, I believe that this registration is ready to proceed. > > regards, > > Ted > > 2012/1/13 ishikawa : >> Dear Ted and Peter, >> >> This is Chiaki Ishikawa. >> >> Thank you for your comments. >> >> I take the suggestion from TED seriously, and >> I checked with the original developer of the specification for the >> intention behind the "case-sensitive" nature. >> >> It turns out that the hexadecimal string that represents ucode in urn >> would be directly translated into XML tags in some of >> the intended applications. (Some of them anyway.) >> >> XML tags are case-sensitive and that is why the capital letters only are >> allowed for hexadecimal "A", "B", "C", "D", "E" and "F" for keeping the >> uniqueness issue of XML tag names under control. >> >> (So I take that conversion to numeric value is less of an issue >> for this particular class of applications. XML is processed in character >> string space more or less.) >> >> So because of the nature of some planned applications (and some of them are >> large-scale deployment), this case-sensitivity dictating the use of capital >> letters only for hexadecimal string must be there. That is the comment from >> the ucode designers and ucode application developers. >> >> Thank you for your valuable time. >> >> Sincerely, >> Chiaki Ishikawa >> >> On (2012年01月12日 07:32), Ted Hardie wrote: >>> On Wed, Jan 11, 2012 at 2:27 PM, Peter Saint-Andre wrote: >>>> >>>>> I would suggest that it permit the use of lower case la-f as well, >>>>> even if the preferred presentation format of the name uses the upper >>>>> case. There are many hexadecimal representations which do not >>>>> distinguish between the two, so I believe it would be better practice >>>>> to permit them. >>>> >>>> Hi Ted, >>>> >>>> That would be inconsistent with this sentence in Section 2 of >>>> draft-ishikawa-yrpunl-ucode-urn: >>>> >>>> The entire UCODE-URN is case-sensitive. >>>> >>> >>> I understand. From a registration perspective, this is clear. But >>> from a practice perspective, it is my personal advice that this will >>> likely lead to problems, because many hexadecimal parsers would treat >>> a and A as equivalent. The authors are, of course, free to discard >>> this suggestion if the constraints on their system are such that this >>> will not arise. >>> >>> Ted >>> >>> >>>> Peter >>>> >>>> -- >>>> Peter Saint-Andre >>>> http://stpeter.im/ From chiaki.ishikawa@ubin.jp Mon Jan 16 20:51:42 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7D9121F84FD for ; Mon, 16 Jan 2012 20:51:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.439 X-Spam-Level: * X-Spam-Status: No, score=1.439 tagged_above=-999 required=5 tests=[AWL=0.329, BAYES_50=0.001, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_53=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJ1oGdLXQp7K for ; Mon, 16 Jan 2012 20:51:41 -0800 (PST) Received: from post.ubin.jp (post.ubin.jp [202.32.0.84]) by ietfa.amsl.com (Postfix) with ESMTP id 48F9D21F84F1 for ; Mon, 16 Jan 2012 20:51:41 -0800 (PST) Received: from localhost (post [127.0.0.1]) by localhost.ubin.jp (Postfix) with SMTP id 0B1E229ADC8; Tue, 17 Jan 2012 13:51:29 +0900 (JST) Received: from home.intra.ubin.jp (home.intra.ubin.jp [10.129.1.1]) by post.ubin.jp (Postfix) with ESMTP id C68CD29ADC8; Tue, 17 Jan 2012 13:51:22 +0900 (JST) Received: from localhost (localhost.localdomain [127.0.0.1]) by home.intra.ubin.jp (Postfix) with ESMTP id 0B176426178; Tue, 17 Jan 2012 13:51:32 +0900 (JST) X-Virus-Scanned: amavisd-new at ubin.jp Received: from home.intra.ubin.jp ([127.0.0.1]) by localhost (home.intra.ubin.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q2N2dkhiu9ul; Tue, 17 Jan 2012 13:51:30 +0900 (JST) Received: from [10.254.225.253] (debian-vbox-ci.ddns.intra.ubin.jp [10.254.225.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by home.intra.ubin.jp (Postfix) with ESMTP id DDFAA42615C; Tue, 17 Jan 2012 13:51:30 +0900 (JST) Message-ID: <4F14FE53.5000807@ubin.jp> Date: Tue, 17 Jan 2012 13:51:31 +0900 From: ishikawa User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Peter Saint-Andre , Ted Hardie Subject: Re: A request for formal registration of "ucode" as URN References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> <4F0E0CBA.1020806@stpeter.im> <4F0FE671.6070709@ubin.jp> <4F1065E1.7080208@stpeter.im> In-Reply-To: <4F1065E1.7080208@stpeter.im> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: ISHIKAWA Chiaki , urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2012 04:51:42 -0000 Dear Peter,Ted, and readers of the mailing list, I have uploaded a revised version of "draft-ishikawa-yrpunl-ucode-urn" to correct the mention of outdated RFC for URI syntax (from RFC 2396 to RFC 3986), and removed the use of "<", ">" from the non-terminal symbols in ABNF description of ucode urn name. This makes it easier to read the ABNF. (Per Peter's suggestion.) The newly submitted modified document is available at the following. https://datatracker.ietf.org/doc/draft-ishikawa-yrpunl-ucode-urn/ Thank you in advance for your attention. Sincerely, Chiaki Ishikawa On (2012$BG/(B01$B7n(B14$BF|(B 02:12), Peter Saint-Andre wrote: > Yes, I agree. > > I shall initiate IETF Last Call on this specification, so that the IESG > can consider it before the end of my term at IETF 83. > > On 1/13/12 10:07 AM, Ted Hardie wrote: >> Dear Ishikawa-san, >> >> Thank you for your careful consideration of the message. With this >> data, I believe that this registration is ready to proceed. >> >> regards, >> >> Ted >> >> 2012/1/13 ishikawa: >>> Dear Ted and Peter, >>> >>> This is Chiaki Ishikawa. >>> >>> Thank you for your comments. >>> >>> I take the suggestion from TED seriously, and >>> I checked with the original developer of the specification for the >>> intention behind the "case-sensitive" nature. >>> >>> It turns out that the hexadecimal string that represents ucode in urn >>> would be directly translated into XML tags in some of >>> the intended applications. (Some of them anyway.) >>> >>> XML tags are case-sensitive and that is why the capital letters only are >>> allowed for hexadecimal "A", "B", "C", "D", "E" and "F" for keeping the >>> uniqueness issue of XML tag names under control. >>> >>> (So I take that conversion to numeric value is less of an issue >>> for this particular class of applications. XML is processed in character >>> string space more or less.) >>> >>> So because of the nature of some planned applications (and some of them are >>> large-scale deployment), this case-sensitivity dictating the use of capital >>> letters only for hexadecimal string must be there. That is the comment from >>> the ucode designers and ucode application developers. >>> >>> Thank you for your valuable time. >>> >>> Sincerely, >>> Chiaki Ishikawa >>> >>> On (2012$BG/(B01$B7n(B12$BF|(B 07:32), Ted Hardie wrote: >>>> On Wed, Jan 11, 2012 at 2:27 PM, Peter Saint-Andre wrote: >>>>> >>>>>> I would suggest that it permit the use of lower case la-f as well, >>>>>> even if the preferred presentation format of the name uses the upper >>>>>> case. There are many hexadecimal representations which do not >>>>>> distinguish between the two, so I believe it would be better practice >>>>>> to permit them. >>>>> >>>>> Hi Ted, >>>>> >>>>> That would be inconsistent with this sentence in Section 2 of >>>>> draft-ishikawa-yrpunl-ucode-urn: >>>>> >>>>> The entire UCODE-URN is case-sensitive. >>>>> >>>> >>>> I understand. From a registration perspective, this is clear. But >>>> from a practice perspective, it is my personal advice that this will >>>> likely lead to problems, because many hexadecimal parsers would treat >>>> a and A as equivalent. The authors are, of course, free to discard >>>> this suggestion if the constraints on their system are such that this >>>> will not arise. >>>> >>>> Ted >>>> >>>> >>>>> Peter >>>>> >>>>> -- >>>>> Peter Saint-Andre >>>>> http://stpeter.im/ > From stpeter@stpeter.im Tue Jan 17 09:20:35 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84F1B21F861B for ; Tue, 17 Jan 2012 09:20:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.269 X-Spam-Level: X-Spam-Status: No, score=-103.269 tagged_above=-999 required=5 tests=[AWL=0.730, BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_53=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XffC-fJXx6Oh for ; Tue, 17 Jan 2012 09:20:34 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 7513E21F8579 for ; Tue, 17 Jan 2012 09:20:34 -0800 (PST) Received: from dhcp-64-101-72-243.cisco.com (unknown [64.101.72.243]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D863040058; Tue, 17 Jan 2012 10:29:53 -0700 (MST) Message-ID: <4F15ADE6.3070101@stpeter.im> Date: Tue, 17 Jan 2012 10:20:38 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: ishikawa Subject: Re: A request for formal registration of "ucode" as URN References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> <4F0E0CBA.1020806@stpeter.im> <4F0FE671.6070709@ubin.jp> <4F1065E1.7080208@stpeter.im> <4F14FE53.5000807@ubin.jp> In-Reply-To: <4F14FE53.5000807@ubin.jp> X-Enigmail-Version: 1.3.4 OpenPGP: url=https://stpeter.im/stpeter.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: urn-nid@apps.ietf.org X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2012 17:20:35 -0000 Thank you, Ishikawa-san. I have requested an IETF Last Call. Peter On 1/16/12 9:51 PM, ishikawa wrote: > Dear Peter,Ted, and readers of the mailing list, > > I have uploaded a revised version of "draft-ishikawa-yrpunl-ucode-urn" > to correct the mention of outdated > RFC for URI syntax (from RFC 2396 to RFC 3986), and > removed the use of "<", ">" from the non-terminal symbols > in ABNF description of ucode urn name. This makes it easier to read the > ABNF. (Per Peter's suggestion.) > > The newly submitted modified document is available at the following. > > https://datatracker.ietf.org/doc/draft-ishikawa-yrpunl-ucode-urn/ > > Thank you in advance for your attention. > > Sincerely, > Chiaki Ishikawa > > On (2012年01月14日 02:12), Peter Saint-Andre wrote: >> Yes, I agree. >> >> I shall initiate IETF Last Call on this specification, so that the IESG >> can consider it before the end of my term at IETF 83. >> >> On 1/13/12 10:07 AM, Ted Hardie wrote: >>> Dear Ishikawa-san, >>> >>> Thank you for your careful consideration of the message. With this >>> data, I believe that this registration is ready to proceed. >>> >>> regards, >>> >>> Ted >>> >>> 2012/1/13 ishikawa: >>>> Dear Ted and Peter, >>>> >>>> This is Chiaki Ishikawa. >>>> >>>> Thank you for your comments. >>>> >>>> I take the suggestion from TED seriously, and >>>> I checked with the original developer of the specification for the >>>> intention behind the "case-sensitive" nature. >>>> >>>> It turns out that the hexadecimal string that represents ucode in urn >>>> would be directly translated into XML tags in some of >>>> the intended applications. (Some of them anyway.) >>>> >>>> XML tags are case-sensitive and that is why the capital letters only are >>>> allowed for hexadecimal "A", "B", "C", "D", "E" and "F" for keeping the >>>> uniqueness issue of XML tag names under control. >>>> >>>> (So I take that conversion to numeric value is less of an issue >>>> for this particular class of applications. XML is processed in character >>>> string space more or less.) >>>> >>>> So because of the nature of some planned applications (and some of them are >>>> large-scale deployment), this case-sensitivity dictating the use of capital >>>> letters only for hexadecimal string must be there. That is the comment from >>>> the ucode designers and ucode application developers. >>>> >>>> Thank you for your valuable time. >>>> >>>> Sincerely, >>>> Chiaki Ishikawa >>>> >>>> On (2012年01月12日 07:32), Ted Hardie wrote: >>>>> On Wed, Jan 11, 2012 at 2:27 PM, Peter Saint-Andre wrote: >>>>>> >>>>>>> I would suggest that it permit the use of lower case la-f as well, >>>>>>> even if the preferred presentation format of the name uses the upper >>>>>>> case. There are many hexadecimal representations which do not >>>>>>> distinguish between the two, so I believe it would be better practice >>>>>>> to permit them. >>>>>> >>>>>> Hi Ted, >>>>>> >>>>>> That would be inconsistent with this sentence in Section 2 of >>>>>> draft-ishikawa-yrpunl-ucode-urn: >>>>>> >>>>>> The entire UCODE-URN is case-sensitive. >>>>>> >>>>> >>>>> I understand. From a registration perspective, this is clear. But >>>>> from a practice perspective, it is my personal advice that this will >>>>> likely lead to problems, because many hexadecimal parsers would treat >>>>> a and A as equivalent. The authors are, of course, free to discard >>>>> this suggestion if the constraints on their system are such that this >>>>> will not arise. >>>>> >>>>> Ted >>>>> >>>>> >>>>>> Peter >>>>>> >>>>>> -- >>>>>> Peter Saint-Andre >>>>>> http://stpeter.im/ From chiaki.ishikawa@ubin.jp Wed Jan 25 02:41:22 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 505B721F8646 for ; Wed, 25 Jan 2012 02:41:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.392 X-Spam-Level: * X-Spam-Status: No, score=1.392 tagged_above=-999 required=5 tests=[AWL=0.282, BAYES_50=0.001, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_53=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6nmQWO5FWk9 for ; Wed, 25 Jan 2012 02:41:21 -0800 (PST) Received: from post.ubin.jp (post.ubin.jp [202.32.0.84]) by ietfa.amsl.com (Postfix) with ESMTP id 3156021F864D for ; Wed, 25 Jan 2012 02:41:21 -0800 (PST) Received: from post.ubin.jp (post [127.0.0.1]) by localhost.ubin.jp (Postfix) with ESMTP id 97B9529AC38; Wed, 25 Jan 2012 19:41:10 +0900 (JST) Received: from home.intra.ubin.jp (home.intra.ubin.jp [10.129.1.1]) by post.ubin.jp (Postfix) with ESMTP id 8175829AB26; Wed, 25 Jan 2012 19:41:10 +0900 (JST) Received: from localhost (localhost.localdomain [127.0.0.1]) by home.intra.ubin.jp (Postfix) with ESMTP id E50CB426597; Wed, 25 Jan 2012 19:41:19 +0900 (JST) X-Virus-Scanned: amavisd-new at ubin.jp Received: from home.intra.ubin.jp ([127.0.0.1]) by localhost (home.intra.ubin.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8L8RONxFtAZv; Wed, 25 Jan 2012 19:41:18 +0900 (JST) Received: from [10.254.225.253] (debian-vbox-ci.ddns.intra.ubin.jp [10.254.225.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by home.intra.ubin.jp (Postfix) with ESMTP id 4CCAF426150; Wed, 25 Jan 2012 19:41:18 +0900 (JST) Message-ID: <4F1FDC5B.50802@ubin.jp> Date: Wed, 25 Jan 2012 19:41:31 +0900 From: ishikawa User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: urn-nid@apps.ietf.org Subject: Re: A request for formal registration of "ucode" as URN References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> <4F0E0CBA.1020806@stpeter.im> <4F0FE671.6070709@ubin.jp> <4F1065E1.7080208@stpeter.im> <4F14FE53.5000807@ubin.jp> <4F15ADE6.3070101@stpeter.im> In-Reply-To: <4F15ADE6.3070101@stpeter.im> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2012 10:41:22 -0000 Dear all, I have uploaded a very minor change to draft-ishikawa-yrpunl-ucode-urn-01.txt The change is that the use of "<" and ">" was not deleted in a couple of places. The two usages in main text part were missed when the usage was removed in ABNF description. E.g. vs ucode-number I noticed them and deleted the usage and now uploaded the "-02" version. (I am not sure if it is customary to update the submission and expiration date on the document, presumably it is, so I did.) The document is available at http://datatracker.ietf.org/doc/draft-ishikawa-yrpunl-ucode-urn/history/ Thank you in advance for your attention. Regards, Chiaki Ishikawa On (2012$BG/(B01$B7n(B18$BF|(B 02:20), Peter Saint-Andre wrote: > Thank you, Ishikawa-san. I have requested an IETF Last Call. > > Peter > > On 1/16/12 9:51 PM, ishikawa wrote: >> Dear Peter,Ted, and readers of the mailing list, >> >> I have uploaded a revised version of "draft-ishikawa-yrpunl-ucode-urn" >> to correct the mention of outdated >> RFC for URI syntax (from RFC 2396 to RFC 3986), and >> removed the use of "<",">" from the non-terminal symbols >> in ABNF description of ucode urn name. This makes it easier to read the >> ABNF. (Per Peter's suggestion.) >> >> The newly submitted modified document is available at the following. >> >> https://datatracker.ietf.org/doc/draft-ishikawa-yrpunl-ucode-urn/ >> >> Thank you in advance for your attention. >> >> Sincerely, >> Chiaki Ishikawa >> >> On (2012$BG/(B01$B7n(B14$BF|(B 02:12), Peter Saint-Andre wrote: >>> Yes, I agree. >>> >>> I shall initiate IETF Last Call on this specification, so that the IESG >>> can consider it before the end of my term at IETF 83. >>> >>> On 1/13/12 10:07 AM, Ted Hardie wrote: >>>> Dear Ishikawa-san, >>>> >>>> Thank you for your careful consideration of the message. With this >>>> data, I believe that this registration is ready to proceed. >>>> >>>> regards, >>>> >>>> Ted >>>> >>>> 2012/1/13 ishikawa: >>>>> Dear Ted and Peter, >>>>> >>>>> This is Chiaki Ishikawa. >>>>> >>>>> Thank you for your comments. >>>>> >>>>> I take the suggestion from TED seriously, and >>>>> I checked with the original developer of the specification for the >>>>> intention behind the "case-sensitive" nature. >>>>> >>>>> It turns out that the hexadecimal string that represents ucode in urn >>>>> would be directly translated into XML tags in some of >>>>> the intended applications. (Some of them anyway.) >>>>> >>>>> XML tags are case-sensitive and that is why the capital letters only are >>>>> allowed for hexadecimal "A", "B", "C", "D", "E" and "F" for keeping the >>>>> uniqueness issue of XML tag names under control. >>>>> >>>>> (So I take that conversion to numeric value is less of an issue >>>>> for this particular class of applications. XML is processed in character >>>>> string space more or less.) >>>>> >>>>> So because of the nature of some planned applications (and some of them are >>>>> large-scale deployment), this case-sensitivity dictating the use of capital >>>>> letters only for hexadecimal string must be there. That is the comment from >>>>> the ucode designers and ucode application developers. >>>>> >>>>> Thank you for your valuable time. >>>>> >>>>> Sincerely, >>>>> Chiaki Ishikawa >>>>> >>>>> On (2012$BG/(B01$B7n(B12$BF|(B 07:32), Ted Hardie wrote: >>>>>> On Wed, Jan 11, 2012 at 2:27 PM, Peter Saint-Andre wrote: >>>>>>> >>>>>>>> I would suggest that it permit the use of lower case la-f as well, >>>>>>>> even if the preferred presentation format of the name uses the upper >>>>>>>> case. There are many hexadecimal representations which do not >>>>>>>> distinguish between the two, so I believe it would be better practice >>>>>>>> to permit them. >>>>>>> >>>>>>> Hi Ted, >>>>>>> >>>>>>> That would be inconsistent with this sentence in Section 2 of >>>>>>> draft-ishikawa-yrpunl-ucode-urn: >>>>>>> >>>>>>> The entire UCODE-URN is case-sensitive. >>>>>>> >>>>>> >>>>>> I understand. From a registration perspective, this is clear. But >>>>>> from a practice perspective, it is my personal advice that this will >>>>>> likely lead to problems, because many hexadecimal parsers would treat >>>>>> a and A as equivalent. The authors are, of course, free to discard >>>>>> this suggestion if the constraints on their system are such that this >>>>>> will not arise. >>>>>> >>>>>> Ted >>>>>> >>>>>> >>>>>>> Peter >>>>>>> >>>>>>> -- >>>>>>> Peter Saint-Andre >>>>>>> http://stpeter.im/ > From evnikita2@gmail.com Fri Jan 27 21:44:18 2012 Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0087921F85D0 for ; Fri, 27 Jan 2012 21:44:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.647 X-Spam-Level: X-Spam-Status: No, score=-3.647 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UMwZN4cRnCH4 for ; Fri, 27 Jan 2012 21:44:17 -0800 (PST) Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3B31621F85BD for ; Fri, 27 Jan 2012 21:44:17 -0800 (PST) Received: by obbwc12 with SMTP id wc12so2937185obb.31 for ; Fri, 27 Jan 2012 21:44:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=HF9hSUG4fw7l5iDDSp05kURMYYz8pnfpAtxi4TQ1nNg=; b=kXxSTWlm3ad4Fu8FTwLQmCjkix80setNglP/JRELkADFt8jfe7iP/Z7k3l8mHUelDg oANBcY18Eoia3cl8Q9s3lVdU5eA6MAbLo2iMddpfu4n4gx6w1CGKn9wTRKsziMHXq1D9 vl9RpMGdB3BbwVZ4rzgff0dDmcKl6kspZpx3k= MIME-Version: 1.0 Received: by 10.182.144.68 with SMTP id sk4mr9514186obb.4.1327729451547; Fri, 27 Jan 2012 21:44:11 -0800 (PST) Received: by 10.182.213.71 with HTTP; Fri, 27 Jan 2012 21:44:11 -0800 (PST) Date: Sat, 28 Jan 2012 07:44:11 +0200 Message-ID: Subject: draft-godgrey-dtg-urn-01 From: Mykyta Yevstifeyev To: urn-nid@ietf.org Content-Type: multipart/alternative; boundary=14dae9399ce7513a8604b7901a7e X-Mailman-Approved-At: Sun, 29 Jan 2012 16:15:32 -0800 X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2012 05:44:18 -0000 --14dae9399ce7513a8604b7901a7e Content-Type: text/plain; charset=ISO-8859-1 Hello, I've just uploaded a new version of draft-godgrey-dtg-urn: http://tools.ietf.org/html/draft-godgrey-dtg-urn-01, which I would appreciate your comments on. Thanks in advance, Mykyta Yevstifeyev --14dae9399ce7513a8604b7901a7e Content-Type: text/html; charset=ISO-8859-1 Hello,

I've just uploaded a new version of draft-godgrey-dtg-urn: http://tools.ietf.org/html/draft-godgrey-dtg-urn-01, which I would appreciate your comments on.

Thanks in advance,
Mykyta Yevstifeyev
--14dae9399ce7513a8604b7901a7e--