Re: [urn] << PLEASE IGNORE THE PREV. MAIL>> Expert review needed

R Atarius <r_atarius@yahoo.com> Wed, 11 April 2018 21:09 UTC

Return-Path: <r_atarius@yahoo.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E256127876 for <urn@ietfa.amsl.com>; Wed, 11 Apr 2018 14:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nPB3SSiSd3I4 for <urn@ietfa.amsl.com>; Wed, 11 Apr 2018 14:09:46 -0700 (PDT)
Received: from sonic317-27.consmr.mail.gq1.yahoo.com (sonic317-27.consmr.mail.gq1.yahoo.com [98.137.66.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 268BD124217 for <urn@ietf.org>; Wed, 11 Apr 2018 14:09:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1523480985; bh=EOTN+gcZlvmj5H5fLbCev6BViD0muHnZ4MdlnyM3v/g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=I7kofY4/r8mj+t3dA9YgoLBpg2aOx93cuVHZuo5xQGytgvtS3sDVuWV/jq6hEnZ4oU4AJ4Pfna72npN7OcO0ubmW3xnyr2MhAK/55Pk2Np9YRE6sNdBP2Umc/312sOUF941jGAXDttuGpNj7qCHkIeP2KxDjwc4eGYXYclqU1MIW2ooCXbv8z4zYsZM1KrAlUr7fmtcTRy/GfLHVs2EmnSlM7rIJf4Pb5DJGttcjNTlofMaWp+ykCOjuWKFgCwex1J3r/oLOyZwC0jH/v/wwjjbAnYwXcJTF2S9W1lkzNUXJ9y3/cWwl+Th1vjUy5LiwjLvJtGLY/0VDdmiyfSUNLw==
X-YMail-OSG: nAILLzcVM1kkMeZIXf56fLSZHW_Kz7fEyhHdXxls5U3yYaHyN4oXcJ5afw49p_Z 4Gc0QyKr3L2hWeIBW7YDEuPfJ4wpq2tJCo3OJBqM9uz43jLY6JI05A1oQ1GMs5hZAqJOBLJ7wkiQ WFTMevCqsiyq1kq035WQ3M0BEBYVFuhpz_0DgQ9GC9vfv.tdy6ry1L6pB1OVSmudT6psrRbL2llx K6O59lFYD.tA1AslGa6ynzkfAokQohgD6fVWmKFxhhK1tlo8iM1Oqz3uMy4gjMr.1YLfYlguGgok PGvuJR6OfgAfTwBJqyeh5Sh4P2trVn47crcVRcFpNmYu20zAEFINA1BfiVzYT6m8h2cuBrtCF4RJ _HUcszJv8BstIUCkt9t1Fl7FBej7Dkx7sB4rOfYvAcdB2AtMDC_3rnYSy215V2RpQhdrXvop8T4t jvOEF203YMofLKhug0nwT4BWybkz.jDS51wZeCB8C.an_AIuRM_zZlCwBfiKgg5tkGtRwxQ7Pv05 qXAMgoG77NQ_cOnQNtYU-
Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Wed, 11 Apr 2018 21:09:45 +0000
Date: Wed, 11 Apr 2018 21:09:40 +0000
From: R Atarius <r_atarius@yahoo.com>
Reply-To: R Atarius <r_atarius@yahoo.com>
To: "Svensson, Lars" <L.Svensson@dnb.de>
Cc: "urn@ietf.org" <urn@ietf.org>, "georg.mayer.huawei@gmx.com" <georg.mayer.huawei@gmx.com>, "ben@nostrum.com" <ben@nostrum.com>, "jbakker@blackberry.com" <jbakker@blackberry.com>, "Dale R. Worley (worley@ariadne.com)" <worley@ariadne.com>
Message-ID: <492366533.1285812.1523480980508@mail.yahoo.com>
In-Reply-To: <e738cbb9b17043fa917f21ce9c2fbb78@dnb.de>
References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> <e738cbb9b17043fa917f21ce9c2fbb78@dnb.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_1285811_1223867362.1523480980504"
X-Mailer: WebService/1.1.11745 YahooMailNeo Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/MQslrP4bLYVrYBi_FQKZw1DCI6Y>
Subject: Re: [urn] << PLEASE IGNORE THE PREV. MAIL>> Expert review needed
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2018 21:09:48 -0000

Hi Lars
please see below
thanksRoozbeh

      From: "Svensson, Lars" <L.Svensson@dnb.de>
 To: R Atarius <r_atarius@yahoo.com> 
Cc: "urn@ietf.org" <urn@ietf.org>; "georg.mayer.huawei@gmx.com" <georg.mayer.huawei@gmx.com>; "ben@nostrum.com" <ben@nostrum.com>; "jbakker@blackberry.com" <jbakker@blackberry.com>; "Dale R. Worley (worley@ariadne.com)" <worley@ariadne.com>
 Sent: Wednesday, April 11, 2018 5:28 AM
 Subject: RE: << PLEASE IGNORE THE PREV. MAIL>> [urn] Expert review needed
   
Hi Rozbeh,

Just a minor comment from me (but I'll read the complete draft when the new version is published):

On Friday, April 06, 2018 1:42 AM, R Atarius [mailto:r_atarius@yahoo.com] wrote:

[...]

> 4.2.3.  Check Digit
> 
>   This is a single hexadecimal digit (bits 1-4 of octet 8) and is used
>   as assurance of integrity in error-prone operations, e.g. when used
>   with certain types of readers during inventory management operations.
>   The check digit is not transmitted by the mobile equipment and are
>   not used in the MEID URN.
> 
> In section 4.2, for completeness, you give a lot of information that is
> not strictly required.  However you don't give the really non-trivial
> bit of information:  the formula for the check digit.  After reading
> this section, I was left curious what the check digit formula actually
> is!
> 
> [Roozbeh]: OK but can I leave it as it is?

I think that technically you could, but I also agree with Dale that it might be confusing to supply non-required information. Since the check digit is not used in the MEID URN, it might be better to omit this paragraph or to rephrase it as

"This is a single hexadecimal digit (bits 1-4 of octet 8). The check digit is not transmitted by the mobile equipment and is not used in the MEID URN."
[Roozbeh] I believe that's how I started but I received comments about its functionality and that's why I added that sentence. I am good either way. If that makes you, Dale and IETF community satisfied then I can remove that sentence. Please let me know.
**********************************************************************************************************************

Looking more closely at section 4.2, it feels a bit awkward that you first define the parts of the MEID format and then go on to put them together. You might want to consider rephrasing as follows:

4.2 MEID Format
The MEID format is 15 hexadecimal digits encoded in 8 octets as defined in [S.R0048-A]. The first eight hexadecimal digits constitute the manufacturer code, the next six hexadecimal digits the serial number within the manufacturer code. The last hexadecimal digit is a check digit. For more details on the hexadecimal encoding cf. 4.2.4.

4.2.4 Hexadecimal Encoding
The following figure ... [X.S0008-A].

[Roozbeh] I think that is what is called a "hanging section", since there should not be any text below 4.2 when there are 4.2.1, 4.2.2, etc. I can create a new subsection as "4.2.1 Overview"  with the text you proposed and shift other subsection with 0.0.1. Will that help?

Best,

Lars