From nobody Thu Apr 5 16:38:47 2018 Return-Path: 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 BA66D12EA67 for ; Thu, 5 Apr 2018 16:38:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.692 X-Spam-Level: * X-Spam-Status: No, score=1.692 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 gl_M4gh-Zl3I for ; Thu, 5 Apr 2018 16:38:33 -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 A30CF12E037 for ; Thu, 5 Apr 2018 16:38:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1522971513; bh=JoFhxT1iE0pLEwKTf0h4DYkEOQia8sXC+RECdtqRt94=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=KHrCHGH08k/e8NCqciPwQJO3reJ/OZEYZGDZk/4xGJnizDZTaD6MjoRZqnK6ZiF1Y6Xn1+hRmhbtE7RzDRD/TCkvRD5uRhT17oLJwxGtf5NHhfOKqNS63cKweKV+yUO8F63o4jN9EIm/NTpC843VfoJlCJk7sxDrJuqEtGeI/4t7vwFBmZ0Dhfq//K/agFbs7J9u0x5NGX5CJ+oWvfK5d9xC5/pKeiaEoNeDa0h3KasJuK9XiGWuzRXznq5+cFhZRfryXWI/cbyBVmU0h0QkPASwFgeRyJihYGj3i7WzNUAto94nOgjPdRLTQUgzlNM0GLMW5rOwL8yZNGek8P5nZw== X-YMail-OSG: P8N4V7YVM1lFxb78oq3ed0oxF5aXNkWusxdqhqvS.1GNvTc6cZNI5kmtRZbofJ7 NiiR7GeBXm8mXSifBLpniTwJsTijQlM.8KNJyIgChRHhTAnKFvyJwfG6Cn880Q6B7ti5rQ1Yxmxz pAr6tsXzhoF7tkzIA016O_K6EvbIqLYSmAchmYruhMKdZWGgHacS8SGkQlukYD.qhYe.ScyJj0AR LeTOeZCcaeNXQ5MtSWx271mpDisn752.zWBZ4dDziekOuQapohoCHqvjYnPZfocE9ciOh97q1xmW Ks0T4rVOFyLaZy8OmV5XwaPI9VpGKnWXRa_qeRcGcsOl69pb3OiJy4A8y5WbFYRUg88Di0yUmob_ .0ULc6HaE.e0oi18RiQ.RVI7AZTfXdjeJdjnv.RzISRx9trd2DctX.Pdd1gUVRFFhdHJvJu5bhmA uZM.0tbrfYqNmKXGbfC0KxAv4FI2tGkCp2a2skCL2R_ki0frLozPAXPnea.PvUxT0WXI_IBilUxz .bzWhYam8S13HToOGfO8- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Thu, 5 Apr 2018 23:38:33 +0000 Date: Thu, 5 Apr 2018 23:38:27 +0000 (UTC) From: R Atarius Reply-To: R Atarius To: "Dale R. Worley" Cc: "urn@ietf.org" , "l.svensson@dnb.de" , "georg.mayer.huawei@gmx.com" , "ben@nostrum.com" , "jbakker@blackberry.com" Message-ID: <1897592677.2154655.1522971507196@mail.yahoo.com> In-Reply-To: <87605gsykv.fsf@hobgoblin.ariadne.com> References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2154654_963342265.1522971507192" X-Mailer: WebService/1.1.11701 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: Subject: Re: [urn] Expert review needed X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Apr 2018 23:38:46 -0000 ------=_Part_2154654_963342265.1522971507192 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Dale, Thanks for reviewing this and please see my inline comments. thanks againRoozbeh From: Dale R. Worley To: R Atarius =20 Cc: urn@ietf.org; l.svensson@dnb.de; georg.mayer.huawei@gmx.com; ben@nostru= m.com; jbakker@blackberry.com Sent: Tuesday, March 27, 2018 7:50 PM Subject: Re: [urn] Expert review needed =20 R Atarius writes: > The new revision (16) is now available. > https://www.ietf.org/id/draft-atarius-dispatch-meid-urn-16.txt The new version looks quite good.=C2=A0 I've a few comments, listed in text order: Abstract =C2=A0 This document defines a Uniform Resource Name (URN) namespace for th= e =C2=A0 Third Generation Partnership Project (3GPP2) and a Namespace Specifi= c =C2=A0 String (NSS) for the Mobile Equipment Identity (MEID). I may have the terminology wrong, but comparing to the next sentence, you might want to change "Third Generation Partnership Project (3GPP2)" to "Third Generation Partnership Project 2 (3GPP2)". [Roozbeh] OK and thanks! ***************************************************************************= ************* 3.=C2=A0 Namespace Registration Template =C2=A0 Registration organization: =C2=A0 Name: 3GPP2 You might want to spell this out as "Third Generation Partnership Project 2 (3GPP2)". [Roozbeh]: OK! ***************************************************************************= ************* =C2=A0 future-pp2-specifier =3D future-specifier *( ":" 1*( pchar / "/" )) This ABNF is correct, but somewhat obscure.=C2=A0 Looking at it quickly, it appears to specify a sequence of "words" separated by ":", where each word contains at least one character which is not ":".=C2=A0 But in fact, can be ":", so this has the same effect as =C2=A0 future-pp2-specifier =3D future-specifier [ ":" 1*( pchar / "/" ) ] That is, the (which cannot contain ":") can be followed by ":" and then by one or more (pchar / "/"), with the latter containing ":" in arbitrary places. So if the ABNF specifies what you want, you might consider the latter formulation as being more expressive of your intentions. [Roozbeh] OK, I can write this as the one you suggested which is =C2=A0future-pp2-specifier =3D future-specifier [ ":" 1*( pchar / "/" ) ] ***************************************************************************= ************* =C2=A0 can comprise any ASCII characters compliant =C2=A0 with URN syntax in [RFC8141]. Actually, there are sequences of ASCII characters compliant with URN syntax in [RFC8141] which cannot be -- RFC 8141 prescribes that the NSS is "pchar *(pchar / "/")", but can only start with , which does not include "~", , ":", or "@", which are all included in . You might want to omit this sentence.=C2=A0 Alternatively, it is true that the part of after ":" can be any NSS string. Though that part is slightly more general than NSS, since it can start with "/", and NSS cannot.=C2=A0 But it's not clear to me that anything you can say along these lines is both completely accurate and easier to understand than the ABNF. [Roozbeh] I choose to omit the sentence then. ***************************************************************************= ************* =C2=A0 Rules for Lexical Equivalence: =C2=A0 Two 3GPP2 MEID URNs are equivalent if they have the same 'meidval' i= n =C2=A0 the same sequential order.=C2=A0 Two future 3GPP2 MEID URNs are equi= valent =C2=A0 if they have the same 'meidval'and 'future-pp2-specifier' in the sam= e =C2=A0 sequential order. The second sentence needs to be rewritten, because of course, no URN contains both and .=C2=A0 Indeed, it seems like you can get the effect you want by simply saying: =C2=A0 Two 3GPP2 MEID URNs are equivalent if they have the same character =C2=A0 string as . 4.2.3.=C2=A0 Check Digit =C2=A0 This is a single hexadecimal digit (bits 1-4 of octet 8) and is used =C2=A0 as assurance of integrity in error-prone operations, e.g. when used =C2=A0 with certain types of readers during inventory management operations= . =C2=A0 The check digit is not transmitted by the mobile equipment and are =C2=A0 not used in the MEID URN. In section 4.2, for completeness, you give a lot of information that is not strictly required.=C2=A0 However you don't give the really non-trivial bit of information:=C2=A0 the formula for the check digit.=C2=A0 After read= ing this section, I was left curious what the check digit formula actually is! Dale =20 ------=_Part_2154654_963342265.1522971507192 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Dale= ,

<= /span>
Thanks for reviewing this and please = see my inline comments.

thanks again
Roozbeh


From: Dale R. Worley <worley@ariadne.c= om>
To: R Atarius &= lt;r_atarius@yahoo.com>
Cc: urn@ietf.org; l.svensson@dnb.de; georg.mayer.huawei@gmx.com; ben@n= ostrum.com; jbakker@blackberry.com
Subject: Re: [urn] Expert review needed

R Atarius <r_atarius@yahoo.com> writes:> The new revision (16) is now available.
> https://www.ietf.org/id/draft-ata= rius-dispatch-meid-urn-16.txt

The = new version looks quite good.  I've a few comments, listed in text
order:

Abstract

  This document defines a Uniform Resou= rce Name (URN) namespace for the
  Third Generation= Partnership Project (3GPP2) and a Namespace Specific
&nb= sp; String (NSS) for the Mobile Equipment Identity (MEID).

I may have the terminology wrong, but comparing to th= e next sentence,
you might want to change "Third Generati= on Partnership Project (3GPP2)"
to "Third Generation Part= nership Project 2 (3GPP2)".

[Roozbeh] OK and thanks!

****************************************************= ************************************

3.  Namespace Registration Template

  Registration organization:
<= br clear=3D"none">  Name: 3GPP2

= You might want to spell this out as "Third Generation Partnership
Project 2 (3GPP2)".

[Roozbeh]: OK!

********************************= ********************************************************

  future-pp2-specifier =3D future-specifier *( ":" 1*( pchar / "/= " ))

This ABNF is correct, but somewha= t obscure.  Looking at it quickly, it
appears to spe= cify a sequence of "words" separated by ":", where each
w= ord contains at least one character which is not ":".  But in fact,<pchar> can be ":", so this has the same effect as
  future-pp2-specifier =3D future-= specifier [ ":" 1*( pchar / "/" ) ]

Th= at is, the <future-specifier> (which cannot contain ":") can be follo= wed
by ":" and then by one or more (pchar / "/"), with th= e latter containing
":" in arbitrary places.

So if the ABNF specifies what you want, you might = consider the latter
formulation as being more expressive = of your intentions.

[Roozbeh] OK, I can write this as the one you suggested which is

 future= -pp2-specifier =3D future-specifier [ ":" 1*( pchar / "/" ) ]


***********************************= *****************************************************
  <future-pp2-specifier> can comprise any ASCII= characters compliant
  with URN syntax in [RFC8141= ].

Actually, there are sequences of AS= CII characters compliant with URN
syntax in [RFC8141] whi= ch cannot be <future-pp2-specifier> -- RFC 8141
pre= scribes that the NSS is "pchar *(pchar / "/")", but
<f= uture-pp2-specifier> can only start with <pp2-char>, which does no= t
include "~", <sub-delims>, ":", or "@", which are= all included in
<pchar>.

You might want to omit this sentence.  Alternatively, it i= s true that
the part of <future-pp2-specifier> afte= r ":" can be any NSS string.
Though that part is slightly= more general than NSS, since it can start
with "/", and = NSS cannot.  But it's not clear to me that anything you
can say along these lines is both completely accurate and easier to
understand than the ABNF.

[Roozbeh] I = choose to omit the sentence then.

************************************************************= ****************************

  Rules for Lexical Equivalen= ce:

  Two 3GPP2 MEID URNs are eq= uivalent if they have the same 'meidval' in
  the s= ame sequential order.  Two future 3GPP2 MEID URNs are equivalent
  if they have the same 'meidval'and 'future-pp2-specifi= er' in the same
  sequential order.

The second sentence needs to be rewritten, because of= course, no URN
contains both <meidval> and <fut= ure-pp2-specifier>.  Indeed, it seems
like you ca= n get the effect you want by simply saying:

  Two 3GPP2 MEID URNs are equivalent if they have the same char= acter
  string as <pp2-NSS>.

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-pr= one 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 t= hat is
not strictly required.  However you don't giv= e the really non-trivial
bit of information:  the fo= rmula for the check digit.  After reading
this secti= on, I was left curious what the check digit formula actually

is!


Dale
<= br clear=3D"none">


------=_Part_2154654_963342265.1522971507192-- From nobody Thu Apr 5 16:42:37 2018 Return-Path: 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 7F3F512D87A for ; Thu, 5 Apr 2018 16:42:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.692 X-Spam-Level: * X-Spam-Status: No, score=1.692 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 uemO-mc2qgM8 for ; Thu, 5 Apr 2018 16:42:34 -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 053A212D875 for ; Thu, 5 Apr 2018 16:42:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1522971753; bh=bG25qegSTXmlosm3wTMCtZk7cXBfByOuXPm4i+aCKs8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=KA3AbM36YB1X3g6w1H16rAOKrJL8fU0E9CpDiLQOp2F0hZGfGRXWZLEaP2NTBn2SKP5kv9WuSFYnS6qZVFyEkbAjw759dG81P3XNPJ65oLGGdlNErplS0Yb5/n8XrVdvKnmH4b3cM7SfzMwuTcJxZgRaxo4luLag0PNrB1uKiXYANGg5ocBl+mrSibav6qq7vTqAPA47VqOeftxF8yOmI8wWQXBDb5F14NicBeyuIvtGedtiD/zZSfNr/faPrZRJsqpXbeuwEQsX5TE1oOA+4w5uukYobV7W/WxuEdoTa944atr6pHvoWk7vSKP1nn1CatYm+YJ9l9jZaqBrIHHIrw== X-YMail-OSG: X_epeToVM1kHmUeVYNsC26tTQCYLbik8yfvFg8CS5o1ZHoiqHwsGffCHDXG5tAN WSGmcqP.BQwBvZ1VedFxUd9pXDnE6tqND0Ov52zcG0gHhkZTHTHVHEKjlFkU7vNbHT_rsITnF6Fw aKfdkkOKd51XKSV5r14AuIaAPt5HPS3JpSGTzmw5WKNNcaT_CW9hNTMD7wjaJuFOJQqDzE70aid2 dUzGa8F41uCqXYDdv92ojcaGt4mZLEv3vsQKbgI3knYEyla5XNaDfQFZtEGe8TrQXeHPZ7qNjFzj 7frhuXOAQyouvGDFWRP_pfxKBAlHsV5HGNwXmigi1Sr8c_IMYEt_9B0fROwUwAYIqdHOzA5psAR9 L_xqS.qD6H4SK70QAegq5mpgPzttTfiADt0e4WcZP2k010PsOyYrlHgdUAIC1dDyxq2NjFs2nVKe hwJcGhn2FwAWQHShRmqQm9vFSnvdewCArmYMjR7KUUXmYdlgaj8yMUHGwOu7hYae3CItM_OzrcoB jq1Rjj9eEDhHDC9B8LHQ- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Thu, 5 Apr 2018 23:42:33 +0000 Date: Thu, 5 Apr 2018 23:42:16 +0000 (UTC) From: R Atarius Reply-To: R Atarius To: "Dale R. Worley" Cc: "urn@ietf.org" , "l.svensson@dnb.de" , "georg.mayer.huawei@gmx.com" , "ben@nostrum.com" , "jbakker@blackberry.com" Message-ID: <467098619.2168581.1522971736851@mail.yahoo.com> In-Reply-To: <1897592677.2154655.1522971507196@mail.yahoo.com> References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2168580_1164675746.1522971736847" X-Mailer: WebService/1.1.11701 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Apr 2018 23:42:35 -0000 ------=_Part_2168580_1164675746.1522971736847 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable << PLEASE IGNORE THE PREVIOUS MAIL WHICH WAS INCOMPLETE!>>> =20 Hi Dale, Thanks for reviewing this and please see my inline comments. thanks againRoozbeh From: Dale R. Worley To: R Atarius =20 Cc: urn@ietf.org; l.svensson@dnb.de; georg.mayer.huawei@gmx.com; ben@nostru= m.com; jbakker@blackberry.com Sent: Tuesday, March 27, 2018 7:50 PM Subject: Re: [urn] Expert review needed =20 R Atarius writes: > The new revision (16) is now available. > https://www.ietf.org/id/draft-atarius-dispatch-meid-urn-16.txt The new version looks quite good.=C2=A0 I've a few comments, listed in text order: Abstract =C2=A0 This document defines a Uniform Resource Name (URN) namespace for th= e =C2=A0 Third Generation Partnership Project (3GPP2) and a Namespace Specifi= c =C2=A0 String (NSS) for the Mobile Equipment Identity (MEID). I may have the terminology wrong, but comparing to the next sentence, you might want to change "Third Generation Partnership Project (3GPP2)" to "Third Generation Partnership Project 2 (3GPP2)". [Roozbeh] OK and thanks! ***************************************************************************= ************* 3.=C2=A0 Namespace Registration Template =C2=A0 Registration organization: =C2=A0 Name: 3GPP2 You might want to spell this out as "Third Generation Partnership Project 2 (3GPP2)". [Roozbeh]: OK! ***************************************************************************= ************* =C2=A0 future-pp2-specifier =3D future-specifier *( ":" 1*( pchar / "/" )) This ABNF is correct, but somewhat obscure.=C2=A0 Looking at it quickly, it appears to specify a sequence of "words" separated by ":", where each word contains at least one character which is not ":".=C2=A0 But in fact, can be ":", so this has the same effect as =C2=A0 future-pp2-specifier =3D future-specifier [ ":" 1*( pchar / "/" ) ] That is, the (which cannot contain ":") can be followed by ":" and then by one or more (pchar / "/"), with the latter containing ":" in arbitrary places. So if the ABNF specifies what you want, you might consider the latter formulation as being more expressive of your intentions. [Roozbeh] OK, I can write this as the one you suggested which is =C2=A0future-pp2-specifier =3D future-specifier [ ":" 1*( pchar / "/" ) ] ***************************************************************************= ************* =C2=A0 can comprise any ASCII characters compliant =C2=A0 with URN syntax in [RFC8141]. Actually, there are sequences of ASCII characters compliant with URN syntax in [RFC8141] which cannot be -- RFC 8141 prescribes that the NSS is "pchar *(pchar / "/")", but can only start with , which does not include "~", , ":", or "@", which are all included in . You might want to omit this sentence.=C2=A0 Alternatively, it is true that the part of after ":" can be any NSS string. Though that part is slightly more general than NSS, since it can start with "/", and NSS cannot.=C2=A0 But it's not clear to me that anything you can say along these lines is both completely accurate and easier to understand than the ABNF. [Roozbeh] I choose to omit the sentence then. ***************************************************************************= ************* =C2=A0 Rules for Lexical Equivalence: =C2=A0 Two 3GPP2 MEID URNs are equivalent if they have the same 'meidval' i= n =C2=A0 the same sequential order.=C2=A0 Two future 3GPP2 MEID URNs are equi= valent =C2=A0 if they have the same 'meidval'and 'future-pp2-specifier' in the sam= e =C2=A0 sequential order. The second sentence needs to be rewritten, because of course, no URN contains both and .=C2=A0 Indeed, it seems like you can get the effect you want by simply saying: =C2=A0 Two 3GPP2 MEID URNs are equivalent if they have the same character =C2=A0 string as . [Roozbeh] : OK! ***************************************************************************= ************* 4.2.3.=C2=A0 Check Digit =C2=A0 This is a single hexadecimal digit (bits 1-4 of octet 8) and is used =C2=A0 as assurance of integrity in error-prone operations, e.g. when used =C2=A0 with certain types of readers during inventory management operations= . =C2=A0 The check digit is not transmitted by the mobile equipment and are =C2=A0 not used in the MEID URN. In section 4.2, for completeness, you give a lot of information that is not strictly required.=C2=A0 However you don't give the really non-trivial bit of information:=C2=A0 the formula for the check digit.=C2=A0 After read= ing this section, I was left curious what the check digit formula actuallyis! [Roozbeh]: OK but can I leave it as it is? Dale =20 =20 ------=_Part_2168580_1164675746.1522971736847 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
&= lt;< PLEASE IGNORE THE PREVIOUS MAIL WHICH WAS INCOMPLETE!>>>


=

Hi Dale,

<= span id=3D"yiv1135978737yui_3_16_0_ym19_1_1522960715829_31368">Thanks for r= eviewing this and please see my inline comments.

<= /span>
= thanks again
Roozb= eh


From: Dale R. Worley <worley@ariadne.com> To: R Ata= rius <r_atarius@yahoo.com>
Cc: urn@ietf.org; l.svensson@dnb.de; georg.mayer.h= uawei@gmx.com; ben@nostrum.com; jbakker@blackberry.com
<= b>Sent: Tuesday, March 27, 201= 8 7:50 PM
Subject:<= /span> Re: [urn] Expert review needed

R Atarius <r_atarius@yahoo.com> writes:
> The new revision (16) is now available.
&= gt; https://www.ietf.org/= id/draft-atarius-dispatch-meid-urn-16.txt

The new version looks quite good.  I've a few comments, list= ed in text
order:

Ab= stract

  This document defines a= Uniform Resource Name (URN) namespace for the
  Th= ird Generation Partnership Project (3GPP2) and a Namespace Specific
  String (NSS) for the Mobile Equipment Identity (MEID).
I may have the terminology wrong, but c= omparing to the next sentence,
you might want to change "= Third Generation Partnership Project (3GPP2)"
to "Third G= eneration Partnership Project 2 (3GPP2)".

[Ro= ozbeh] OK and thanks!

**********************************************= ******************************************

3.  Namespace Regist= ration Template

  Registration o= rganization:

  Name: 3GPP2

You might want to spell this out as "Third = Generation Partnership
Project 2 (3GPP2)".

[Roozbeh]: OK!

***********************= *****************************************************************

  future-pp2-specifier =3D future-specif= ier *( ":" 1*( pchar / "/" ))

This ABN= F is correct, but somewhat obscure.  Looking at it quickly, it
appears to specify a sequence of "words" separated by ":", where= each
word contains at least one character which is not "= :".  But in fact,
<pchar> can be ":", so this = has the same effect as

  future-= pp2-specifier =3D future-specifier [ ":" 1*( pchar / "/" ) ]

That is, the <future-specifier> (which cannot = contain ":") can be followed
by ":" and then by one or mo= re (pchar / "/"), with the latter containing
":" in arbit= rary places.

So if the ABNF specifies = what you want, you might consider the latter
formulation = as being more expressive of your intentions.

=
= [Roozbeh] OK, I can write this as the one you suggested which is

 future-pp2-specifier =3D future-specifier [ ":" 1= *( pchar / "/" ) ]


************************= ****************************************************************

  <future-pp2-specifier> can compr= ise any ASCII characters compliant
  with URN synta= x in [RFC8141].

Actually, there are se= quences of ASCII characters compliant with URN
syntax in = [RFC8141] which cannot be <future-pp2-specifier> -- RFC 8141
prescribes that the NSS is "pchar *(pchar / "/")", but
<future-pp2-specifier> can only start with <pp2-char>= , which does not
include "~", <sub-delims>, ":", or= "@", which are all included in
<pchar>.

You might want to omit this sentence.  Al= ternatively, it is true that
the part of <future-pp2-s= pecifier> after ":" can be any NSS string.
Though that= part is slightly more general than NSS, since it can start
with "/", and NSS cannot.  But it's not clear to me that anything y= ou
can say along these lines is both completely accurate = and easier to
understand than the ABNF.

[Roozbeh] I choose to omit the sentence then.

****= ***************************************************************************= *********

  Rules for Lexical Equivalence:
  Two 3GPP2 MEID URNs are equivale= nt if they have the same 'meidval' in
  the same se= quential order.  Two future 3GPP2 MEID URNs are equivalent
  if they have the same 'meidval'and 'future-pp2-specifier' in= the same
  sequential order.
The second sentence needs to be rewritten, because of cours= e, no URN
contains both <meidval> and <future-pp= 2-specifier>.  Indeed, it seems
like you can get = the effect you want by simply saying:

=   Two 3GPP2 MEID URNs are equivalent if they have the same character<= br clear=3D"none">  string as <pp2-NSS>.

[Roozbe= h] : OK!


**************************************************************= **************************

4.2.3. = ; Check Digit

  This is a single= hexadecimal digit (bits 1-4 of octet 8) and is used
&nbs= p; as assurance of integrity in error-prone operations, e.g. when used
  with certain types of readers during inventory manag= ement operations.
  The check digit is not transmit= ted by the mobile equipment and are
  not used in t= he MEID URN.

In section 4.2, for compl= eteness, you give a lot of information that is
not strict= ly 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 c= heck digit formula actually
is!

[Roozbeh]: OK but can I leave it as= it is?


Dale



=


------=_Part_2168580_1164675746.1522971736847-- From nobody Wed Apr 11 05:28:56 2018 Return-Path: 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 B8A5A126CE8 for ; Wed, 11 Apr 2018 05:28:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no 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 C7ZzRXYItr2Y for ; Wed, 11 Apr 2018 05:28:53 -0700 (PDT) Received: from mail.dnb.de (mail.dnb.de [193.175.100.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33EB1126CB6 for ; Wed, 11 Apr 2018 05:28:52 -0700 (PDT) Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by mail.dnb.de (Postfix) with ESMTP id 7C3FC44C0BE6; Wed, 11 Apr 2018 14:28:50 +0200 (CEST) X-AuditID: 0a453fe7-d25ff70000000f94-4a-5acdff820944 Received: from dnbf-ex.AD.DDB.DE (dnbf-ex.AD.DDB.DE [10.69.63.244]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id 89.34.03988.28FFDCA5; Wed, 11 Apr 2018 14:28:50 +0200 (CEST) Received: from dnbf-ex.AD.DDB.DE (10.69.63.244) by dnbf-ex.AD.DDB.DE (10.69.63.244) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.669.32; Wed, 11 Apr 2018 14:28:48 +0200 Received: from dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7]) by dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7%4]) with mapi id 15.01.0669.032; Wed, 11 Apr 2018 14:28:48 +0200 From: "Svensson, Lars" To: R Atarius CC: "urn@ietf.org" , "georg.mayer.huawei@gmx.com" , "ben@nostrum.com" , "jbakker@blackberry.com" , "Dale R. Worley (worley@ariadne.com)" Thread-Topic: << PLEASE IGNORE THE PREV. MAIL>> [urn] Expert review needed Thread-Index: AQHTxj+bm9nzWsXj0kCSDe1z6LFY5KPywF2AgAABEQCACMzdoA== Date: Wed, 11 Apr 2018 12:28:48 +0000 Message-ID: References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> In-Reply-To: <467098619.2168581.1522971736851@mail.yahoo.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.12.174] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrEIcWRmVeSWpSXmKPExsXC5Wr/Rbfp/9kogw/d4hbzO0+zW7xawmXR sOIEo0XPBUuLqc0fmCxenihzYPOYvP8rs8eshrXsHnfvL2TyWLLkJ5PHrJ1PWDxmzTrMFMAW xWWTkpqTWZZapG+XwJXR3Jpc0CVa8eDZXdYGxiMiXYycHBICJhJ/3r1k7GLk4hASOMQo8WTO CijnMaPEpF1n2SGcLYwSHWtfAjnsHGwCWhLvM0CaRQSUJfqP72cCsZkFvjFKnFkvCmILC3hK nLtwFijOAVTjJfHquhJEuZPEnXN/WUFsFgFViYP3XrKB2LwCphIPbh1kgdh0hlHi87R5LCAJ TgFbiZs7doLZjAKyEhs2nGeG2CUusenZd1aIBwQkluyBiEsIiEq8fPwPKq4gcfneVrAbmAU0 Jdbv0odoVZSY0v2QHWKvoMTJmU9YJjCKzUIydRZCxywkHbOQdCxgZFnFyFecm26ol5iil5KS pJeSuokREnXPdzD2XXI5xCjAwajEw/vn9pkoIdbEsuLK3EOM/hxMSqK88zzORgnxJeWnVGYk FmfEF5XmpBYrifAefwEU5oULJ5XmZCvJ8TbOB4qKw0WLS4sLMpMz80uL40uLcoDRxcEM1Hr0 N0hrSmJlVWpRPsTAQ4zSHCxK4rwv9zFECAmkJ5akZqemFqQWwWQjODiUJHjb/gE1ChalpqdW pGXmlMCkgfoa/gJlBJBlwA5S5LXyBXpIClkC3U1MHJyHGH04eIAOewgyhbe4IDG3ODMdarYw rxxIlAcmCjZXlrdwAVBQDCaIauYpxlSON209PcwcTy5P62EWYsnLz0uVEuc9DHK+AEhPRmke 3PVSYrwzQYbxI0mALJFS4P3w/VSUkCSSOKo9rxg9gZEmzNsLMpcHmCURrhbi9QcJckMFwY6W 4S0B2SMKFUM3ywcY2yK8x3zOgIKgJLEEOQg4FoCDACoKDQIWSBBABVGNk2pgTPO/4bl29g/h e+LrfdTSpeTu2VsErPwiwNmWlXL/tdB9Qb+2BL+UKx3asxrl9yTvqH0lffH4vptJU3qYLyl6 eM+Yc9Ip55JcvKmh4H7uid8PpqdtMX23Tixn5s+VC+pn3log/mVPa8z3TJWcTSULArq9M1J/ dh+exriir2LNZ9uGiPB98ypnKrEUZyQaajEXFScCAOoyeOG1BAAA Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 12:28:56 -0000 SGkgUm96YmVoLA0KDQpKdXN0IGEgbWlub3IgY29tbWVudCBmcm9tIG1lIChidXQgSSdsbCByZWFk IHRoZSBjb21wbGV0ZSBkcmFmdCB3aGVuIHRoZSBuZXcgdmVyc2lvbiBpcyBwdWJsaXNoZWQpOg0K DQpPbiBGcmlkYXksIEFwcmlsIDA2LCAyMDE4IDE6NDIgQU0sIFIgQXRhcml1cyBbbWFpbHRvOnJf YXRhcml1c0B5YWhvby5jb21dIHdyb3RlOg0KDQpbLi4uXQ0KDQo+IDQuMi4zLsKgIENoZWNrIERp Z2l0DQo+IA0KPiDCoCBUaGlzIGlzIGEgc2luZ2xlIGhleGFkZWNpbWFsIGRpZ2l0IChiaXRzIDEt NCBvZiBvY3RldCA4KSBhbmQgaXMgdXNlZA0KPiDCoCBhcyBhc3N1cmFuY2Ugb2YgaW50ZWdyaXR5 IGluIGVycm9yLXByb25lIG9wZXJhdGlvbnMsIGUuZy4gd2hlbiB1c2VkDQo+IMKgIHdpdGggY2Vy dGFpbiB0eXBlcyBvZiByZWFkZXJzIGR1cmluZyBpbnZlbnRvcnkgbWFuYWdlbWVudCBvcGVyYXRp b25zLg0KPiDCoCBUaGUgY2hlY2sgZGlnaXQgaXMgbm90IHRyYW5zbWl0dGVkIGJ5IHRoZSBtb2Jp bGUgZXF1aXBtZW50IGFuZCBhcmUNCj4gwqAgbm90IHVzZWQgaW4gdGhlIE1FSUQgVVJOLg0KPiAN Cj4gSW4gc2VjdGlvbiA0LjIsIGZvciBjb21wbGV0ZW5lc3MsIHlvdSBnaXZlIGEgbG90IG9mIGlu Zm9ybWF0aW9uIHRoYXQgaXMNCj4gbm90IHN0cmljdGx5IHJlcXVpcmVkLsKgIEhvd2V2ZXIgeW91 IGRvbid0IGdpdmUgdGhlIHJlYWxseSBub24tdHJpdmlhbA0KPiBiaXQgb2YgaW5mb3JtYXRpb246 wqAgdGhlIGZvcm11bGEgZm9yIHRoZSBjaGVjayBkaWdpdC7CoCBBZnRlciByZWFkaW5nDQo+IHRo aXMgc2VjdGlvbiwgSSB3YXMgbGVmdCBjdXJpb3VzIHdoYXQgdGhlIGNoZWNrIGRpZ2l0IGZvcm11 bGEgYWN0dWFsbHkNCj4gaXMhDQo+IA0KPiBbUm9vemJlaF06IE9LIGJ1dCBjYW4gSSBsZWF2ZSBp dCBhcyBpdCBpcz8NCg0KSSB0aGluayB0aGF0IHRlY2huaWNhbGx5IHlvdSBjb3VsZCwgYnV0IEkg YWxzbyBhZ3JlZSB3aXRoIERhbGUgdGhhdCBpdCBtaWdodCBiZSBjb25mdXNpbmcgdG8gc3VwcGx5 IG5vbi1yZXF1aXJlZCBpbmZvcm1hdGlvbi4gU2luY2UgdGhlIGNoZWNrIGRpZ2l0IGlzIG5vdCB1 c2VkIGluIHRoZSBNRUlEIFVSTiwgaXQgbWlnaHQgYmUgYmV0dGVyIHRvIG9taXQgdGhpcyBwYXJh Z3JhcGggb3IgdG8gcmVwaHJhc2UgaXQgYXMNCg0KIlRoaXMgaXMgYSBzaW5nbGUgaGV4YWRlY2lt YWwgZGlnaXQgKGJpdHMgMS00IG9mIG9jdGV0IDgpLiBUaGUgY2hlY2sgZGlnaXQgaXMgbm90IHRy YW5zbWl0dGVkIGJ5IHRoZSBtb2JpbGUgZXF1aXBtZW50IGFuZCBpcyBub3QgdXNlZCBpbiB0aGUg TUVJRCBVUk4uIg0KDQpMb29raW5nIG1vcmUgY2xvc2VseSBhdCBzZWN0aW9uIDQuMiwgaXQgZmVl bHMgYSBiaXQgYXdrd2FyZCB0aGF0IHlvdSBmaXJzdCBkZWZpbmUgdGhlIHBhcnRzIG9mIHRoZSBN RUlEIGZvcm1hdCBhbmQgdGhlbiBnbyBvbiB0byBwdXQgdGhlbSB0b2dldGhlci4gWW91IG1pZ2h0 IHdhbnQgdG8gY29uc2lkZXIgcmVwaHJhc2luZyBhcyBmb2xsb3dzOg0KDQo0LjIgTUVJRCBGb3Jt YXQNClRoZSBNRUlEIGZvcm1hdCBpcyAxNSBoZXhhZGVjaW1hbCBkaWdpdHMgZW5jb2RlZCBpbiA4 IG9jdGV0cyBhcyBkZWZpbmVkIGluIFtTLlIwMDQ4LUFdLiBUaGUgZmlyc3QgZWlnaHQgaGV4YWRl Y2ltYWwgZGlnaXRzIGNvbnN0aXR1dGUgdGhlIG1hbnVmYWN0dXJlciBjb2RlLCB0aGUgbmV4dCBz aXggaGV4YWRlY2ltYWwgZGlnaXRzIHRoZSBzZXJpYWwgbnVtYmVyIHdpdGhpbiB0aGUgbWFudWZh Y3R1cmVyIGNvZGUuIFRoZSBsYXN0IGhleGFkZWNpbWFsIGRpZ2l0IGlzIGEgY2hlY2sgZGlnaXQu IEZvciBtb3JlIGRldGFpbHMgb24gdGhlIGhleGFkZWNpbWFsIGVuY29kaW5nIGNmLiA0LjIuNC4N Cg0KNC4yLjQgSGV4YWRlY2ltYWwgRW5jb2RpbmcNClRoZSBmb2xsb3dpbmcgZmlndXJlIC4uLiBb WC5TMDAwOC1BXS4NCg0KQmVzdCwNCg0KTGFycw0KDQo= From nobody Wed Apr 11 14:09:50 2018 Return-Path: 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 ; 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 ; 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 ; 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 (UTC) From: R Atarius Reply-To: R Atarius To: "Svensson, Lars" Cc: "urn@ietf.org" , "georg.mayer.huawei@gmx.com" , "ben@nostrum.com" , "jbakker@blackberry.com" , "Dale R. Worley (worley@ariadne.com)" Message-ID: <492366533.1285812.1523480980508@mail.yahoo.com> In-Reply-To: References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2018 21:09:48 -0000 ------=_Part_1285811_1223867362.1523480980504 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Lars please see below thanksRoozbeh From: "Svensson, Lars" To: R Atarius =20 Cc: "urn@ietf.org" ; "georg.mayer.huawei@gmx.com" ; "ben@nostrum.com" ; "jbakker@blackberry= .com" ; "Dale R. Worley (worley@ariadne.com)" Sent: Wednesday, April 11, 2018 5:28 AM Subject: RE: << PLEASE IGNORE THE PREV. MAIL>> [urn] Expert review needed =20 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] w= rote: [...] > 4.2.3.=C2=A0 Check Digit >=20 > =C2=A0 This is a single hexadecimal digit (bits 1-4 of octet 8) and is us= ed > =C2=A0 as assurance of integrity in error-prone operations, e.g. when use= d > =C2=A0 with certain types of readers during inventory management operatio= ns. > =C2=A0 The check digit is not transmitted by the mobile equipment and are > =C2=A0 not used in the MEID URN. >=20 > In section 4.2, for completeness, you give a lot of information that is > not strictly required.=C2=A0 However you don't give the really non-trivia= l > bit of information:=C2=A0 the formula for the check digit.=C2=A0 After re= ading > this section, I was left curious what the check digit formula actually > is! >=20 > [Roozbeh]: OK but can I leave it as it is? I think that technically you could, but I also agree with Dale that it migh= t 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. I= f 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. Yo= u 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 manufac= turer code. The last hexadecimal digit is a check digit. For more details o= n 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 s= hould not be any text below 4.2 when there are 4.2.1, 4.2.2, etc. I can cre= ate a new subsection as "4.2.1 Overview"=C2=A0 with the text you proposed a= nd shift other subsection with 0.0.1. Will that help? Best, Lars =20 ------=_Part_1285811_1223867362.1523480980504 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Lars

please see below

thanks
Roozbeh<= /div>


From: "Svensson, Lars" <L.Sve= nsson@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@nos= trum.com>; "jbakker@blackberry.com" <jbakker@blackberry.com>; "Dal= e R. Worley (worley@ariadne.com)" <worley@ariadne.com>
Sent: Wednesday, April 11, 2018 5:28= AM
Subject: RE: <&= lt; PLEASE IGNORE THE PREV. MAIL>> [urn] Expert review needed

Hi Rozbeh,

Just a minor comment fr= om 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 hexade= cimal 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 mana= gement operations.
>   The check digit is not tra= nsmitted by the mobile equipment and are
>   not = used in the MEID URN.
>
> In sec= tion 4.2, for completeness, you give a lot of information that is
> not strictly required.  However you don't give the real= ly non-trivial
> bit of information:  the formula= for the check digit.  After reading
> this secti= on, I was left curious what the check digit formula actually
> is!
>
> [Roozbeh]: OK b= ut can I leave it as it is?


I th= ink 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 reph= rase it as

"This is a single hexadecim= al digit (bits 1-4 of octet 8). The check digit is not transmitted by the m= obile equipment and is not used in the MEID URN."

[Roozbeh] I b= elieve 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. Ple= ase let me know.

*********************************************************************= *************************************************

Looking more closely at section 4= .2, it feels a bit awkward that you first define the parts of the MEID form= at and then go on to put them together. You might want to consider rephrasi= ng 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 m= anufacturer code, the next six hexadecimal digits the serial number within = the manufacturer code. The last hexadecimal digit is a check digit. For mor= e details on the hexadecimal encoding cf. 4.2.4.

4.2.4 Hexad= ecimal Encoding
The following figure ... [X.S0008-A].

[Roozbeh] I think that is what is called a "hanging se= ction", 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 th= e text you proposed and shift other subsection with 0.0.1. Will that help?<= /div>


B= est,

Lars



------=_Part_1285811_1223867362.1523480980504-- From nobody Thu Apr 12 11:43:57 2018 Return-Path: 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 3D42D12DA09 for ; Thu, 12 Apr 2018 11:43:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 A9NOIm8W0-lr for ; Thu, 12 Apr 2018 11:43:53 -0700 (PDT) Received: from mail.dnb.de (mail.dnb.de [193.175.100.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E65C7126DED for ; Thu, 12 Apr 2018 11:43:52 -0700 (PDT) Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by mail.dnb.de (Postfix) with ESMTP id 2CB2053AAAA2; Thu, 12 Apr 2018 20:43:50 +0200 (CEST) X-AuditID: 0a453fe7-d3dff70000000f94-d5-5acfa8e556c2 Received: from dnbf-ex.AD.DDB.DE (dnbf-ex.AD.DDB.DE [10.69.63.244]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id 8F.BE.03988.5E8AFCA5; Thu, 12 Apr 2018 20:43:49 +0200 (CEST) Received: from dnbf-ex.AD.DDB.DE (10.69.63.244) by dnbf-ex.AD.DDB.DE (10.69.63.244) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.669.32; Thu, 12 Apr 2018 20:43:47 +0200 Received: from dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7]) by dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7%4]) with mapi id 15.01.0669.032; Thu, 12 Apr 2018 20:43:47 +0200 From: "Svensson, Lars" To: R Atarius CC: "urn@ietf.org" , "georg.mayer.huawei@gmx.com" , "ben@nostrum.com" , "jbakker@blackberry.com" , "Dale R. Worley (worley@ariadne.com)" Thread-Topic: << PLEASE IGNORE THE PREV. MAIL>> [urn] Expert review needed Thread-Index: AQHT0dluCZ10H8YVO0ektNwRNnBvdKP9ds3g Date: Thu, 12 Apr 2018 18:43:47 +0000 Message-ID: References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> <492366533.1285812.1523480980508@mail.yahoo.com> In-Reply-To: <492366533.1285812.1523480980508@mail.yahoo.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.69.146] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMIcWRmVeSWpSXmKPExsXC5Wr/RffpivNRBj2rLC3md55mt3i1hMui YcUJRoueC5YWU5s/MFm8PFHmwOYxef9XZo9ZDWvZPe7eX8jksWTJTyaPWTufsHjMmnWYKYAt issmJTUnsyy1SN8ugSujv3Mya8E35Yqvt/8wNTA2KHcxcnJICJhIzN+zmLWLkYtDSOAQo8Tp tx9YIJzHjBIPJs5lhnC2MErc2T2DqYuRnYNNQEvifQZIs4iAskT/8f1MIDazwDdGiTPrRUFs YQFPiXMXzgLFOYBqvCReXVeCKDeSuNMynw3EZhFQldjQfQ+slVfAVOLPuidQa1czSexo2MIO kuAUsJU423MSrIhRQFZiw4bzzBC7xCU2PfvOCvGAgMSSPRBxCQFRiZeP/0HFFSWuz/vCDHID s4CmxPpd+hCtihJTuh+yQ+wVlDg58wnLBEaxWUimzkLomIWkYxaSjgWMLKsY+Ypz0w31ElP0 UlKS9FJSNzFC4u75Dsa+Sy6HGAU4GJV4eP/UnY8SYk0sK67MPcToz8GkJMq7MQYoxJeUn1KZ kVicEV9UmpNarCTCO2cOUJgXLpxUmpOtJMfbOP9slJA4XLS4tLggMzkzv7Q4vrQoBxhdHMxA rbUNIK0piZVVqUX5EAMPMUpzsCiJ877cxxAhJJCeWJKanZpakFoEk43g4FCS4NVdDtQoWJSa nlqRlplTApMG6pv67lyUkACyDNhBirxWvmeihKSQJdDdxMTBeYjRh4MH6LCHy0AOKy5IzC3O TIeaLcxbPx8oygMTBZsry1u4AOhRMZggqpmnGFM53rT19DBzPLk8rYdZiCUvPy9VSpz3IMj5 AiA9GaV5cNdLifHOBBnGjyQBskRKgTfxE9BXkkjiqPa8YvQERpow70yQuTzAPIlwtRCv42Kg IDdUEOxoGd4SkD2iUDF0s3yAsS3Ce8znDCgIShJLkIOAA6SRByYKDQIWSBBABVGNk2pgXJAn brtGxd9ge5tXWcK/O//37cvdyBv62W8/v5NSwqPKjp2yZxeacl/XfB/wVEF0sqqIZ8i8i1Lt Lxfpc37Y+lDbNT7s7J5LGjuTL+bnHilymlBvm8ri9FzxpvS5Cye1Nmqv2OP5bttCaQMbkdKu Z64aLz9KlRicuyMiJsHp+XG2hWfov6IEJZbijERDLeai4kQAoLp6VbYEAAA= Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 18:43:56 -0000 SGkgUm9vemJlaCwNCg0KT24gV2VkbmVzZGF5LCBBcHJpbCAxMSwgMjAxOCAxMToxMCBQTSwgUiBB dGFyaXVzIFttYWlsdG86cl9hdGFyaXVzQHlhaG9vLmNvbV0gd3JvdGU6DQpbLi4uXQ0KPiANCj4g T24gRnJpZGF5LCBBcHJpbCAwNiwgMjAxOCAxOjQyIEFNLCBSIEF0YXJpdXMgW21haWx0bzptYWls dG86cl9hdGFyaXVzQHlhaG9vLmNvbV0NCj4gd3JvdGU6DQo+IA0KPiANCj4gWy4uLl0NCj4gDQo+ ID4gNC4yLjMuwqAgQ2hlY2sgRGlnaXQNCj4gPg0KPiA+IMKgIFRoaXMgaXMgYSBzaW5nbGUgaGV4 YWRlY2ltYWwgZGlnaXQgKGJpdHMgMS00IG9mIG9jdGV0IDgpIGFuZCBpcyB1c2VkDQo+ID4gwqAg YXMgYXNzdXJhbmNlIG9mIGludGVncml0eSBpbiBlcnJvci1wcm9uZSBvcGVyYXRpb25zLCBlLmcu IHdoZW4gdXNlZA0KPiA+IMKgIHdpdGggY2VydGFpbiB0eXBlcyBvZiByZWFkZXJzIGR1cmluZyBp bnZlbnRvcnkgbWFuYWdlbWVudCBvcGVyYXRpb25zLg0KPiA+IMKgIFRoZSBjaGVjayBkaWdpdCBp cyBub3QgdHJhbnNtaXR0ZWQgYnkgdGhlIG1vYmlsZSBlcXVpcG1lbnQgYW5kIGFyZQ0KPiA+IMKg IG5vdCB1c2VkIGluIHRoZSBNRUlEIFVSTi4NCj4gPg0KPiA+IEluIHNlY3Rpb24gNC4yLCBmb3Ig Y29tcGxldGVuZXNzLCB5b3UgZ2l2ZSBhIGxvdCBvZiBpbmZvcm1hdGlvbiB0aGF0IGlzDQo+ID4g bm90IHN0cmljdGx5IHJlcXVpcmVkLsKgIEhvd2V2ZXIgeW91IGRvbid0IGdpdmUgdGhlIHJlYWxs eSBub24tdHJpdmlhbA0KPiA+IGJpdCBvZiBpbmZvcm1hdGlvbjrCoCB0aGUgZm9ybXVsYSBmb3Ig dGhlIGNoZWNrIGRpZ2l0LsKgIEFmdGVyIHJlYWRpbmcNCj4gPiB0aGlzIHNlY3Rpb24sIEkgd2Fz IGxlZnQgY3VyaW91cyB3aGF0IHRoZSBjaGVjayBkaWdpdCBmb3JtdWxhIGFjdHVhbGx5DQo+ID4g aXMhDQo+ID4NCj4gPiBbUm9vemJlaF06IE9LIGJ1dCBjYW4gSSBsZWF2ZSBpdCBhcyBpdCBpcz8N Cj4gDQo+IA0KPiBJIHRoaW5rIHRoYXQgdGVjaG5pY2FsbHkgeW91IGNvdWxkLCBidXQgSSBhbHNv IGFncmVlIHdpdGggRGFsZSB0aGF0IGl0IG1pZ2h0IGJlIGNvbmZ1c2luZw0KPiB0byBzdXBwbHkg bm9uLXJlcXVpcmVkIGluZm9ybWF0aW9uLiBTaW5jZSB0aGUgY2hlY2sgZGlnaXQgaXMgbm90IHVz ZWQgaW4gdGhlIE1FSUQgVVJOLA0KPiBpdCBtaWdodCBiZSBiZXR0ZXIgdG8gb21pdCB0aGlzIHBh cmFncmFwaCBvciB0byByZXBocmFzZSBpdCBhcw0KPiANCj4gIlRoaXMgaXMgYSBzaW5nbGUgaGV4 YWRlY2ltYWwgZGlnaXQgKGJpdHMgMS00IG9mIG9jdGV0IDgpLiBUaGUgY2hlY2sgZGlnaXQgaXMg bm90DQo+IHRyYW5zbWl0dGVkIGJ5IHRoZSBtb2JpbGUgZXF1aXBtZW50IGFuZCBpcyBub3QgdXNl ZCBpbiB0aGUgTUVJRCBVUk4uIg0KPiANCj4gW1Jvb3piZWhdIEkgYmVsaWV2ZSB0aGF0J3MgaG93 IEkgc3RhcnRlZCBidXQgSSByZWNlaXZlZCBjb21tZW50cyBhYm91dCBpdHMgZnVuY3Rpb25hbGl0 eQ0KPiBhbmQgdGhhdCdzIHdoeSBJIGFkZGVkIHRoYXQgc2VudGVuY2UuIEkgYW0gZ29vZCBlaXRo ZXIgd2F5LiBJZiB0aGF0IG1ha2VzIHlvdSwgRGFsZQ0KPiBhbmQgSUVURiBjb21tdW5pdHkgc2F0 aXNmaWVkIHRoZW4gSSBjYW4gcmVtb3ZlIHRoYXQgc2VudGVuY2UuIFBsZWFzZSBsZXQgbWUga25v dy4NCg0KT0ssIHNvIHlvdSdyZSBkYW1uZWQgaWYgeW91IGRvIGFuZCBkYW1uZWQgaWYgeW91IGRv bid0Li4uIEknbSBmaW5lIGVpdGhlciB3YXksIHRvbywgc28gaWYgbm90IERhbGUgb3IgYW55b25l IGVsc2Ugb2JqZWN0cywgeW91IGNhbiBsZWF2ZSB0aGUgc2VudGVuY2UgYXMgaXQgaXMuDQoNCj4g DQo+ICoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioNCj4gKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqDQo+IA0KPiBMb29raW5nIG1vcmUgY2xvc2VseSBhdCBzZWN0aW9uIDQuMiwg aXQgZmVlbHMgYSBiaXQgYXdrd2FyZCB0aGF0IHlvdSBmaXJzdCBkZWZpbmUgdGhlDQo+IHBhcnRz IG9mIHRoZSBNRUlEIGZvcm1hdCBhbmQgdGhlbiBnbyBvbiB0byBwdXQgdGhlbSB0b2dldGhlci4g WW91IG1pZ2h0IHdhbnQgdG8NCj4gY29uc2lkZXIgcmVwaHJhc2luZyBhcyBmb2xsb3dzOg0KPiAN Cj4gNC4yIE1FSUQgRm9ybWF0DQo+IFRoZSBNRUlEIGZvcm1hdCBpcyAxNSBoZXhhZGVjaW1hbCBk aWdpdHMgZW5jb2RlZCBpbiA4IG9jdGV0cyBhcyBkZWZpbmVkIGluIFtTLlIwMDQ4LQ0KPiBBXS4g VGhlIGZpcnN0IGVpZ2h0IGhleGFkZWNpbWFsIGRpZ2l0cyBjb25zdGl0dXRlIHRoZSBtYW51ZmFj dHVyZXIgY29kZSwgdGhlIG5leHQgc2l4DQo+IGhleGFkZWNpbWFsIGRpZ2l0cyB0aGUgc2VyaWFs IG51bWJlciB3aXRoaW4gdGhlIG1hbnVmYWN0dXJlciBjb2RlLiBUaGUgbGFzdA0KPiBoZXhhZGVj aW1hbCBkaWdpdCBpcyBhIGNoZWNrIGRpZ2l0LiBGb3IgbW9yZSBkZXRhaWxzIG9uIHRoZSBoZXhh ZGVjaW1hbCBlbmNvZGluZyBjZi4NCj4gNC4yLjQuDQo+IDQuMi40IEhleGFkZWNpbWFsIEVuY29k aW5nDQo+IFRoZSBmb2xsb3dpbmcgZmlndXJlIC4uLiBbWC5TMDAwOC1BXS4NCj4gW1Jvb3piZWhd IEkgdGhpbmsgdGhhdCBpcyB3aGF0IGlzIGNhbGxlZCBhICJoYW5naW5nIHNlY3Rpb24iLCBzaW5j ZSB0aGVyZSBzaG91bGQgbm90IGJlDQo+IGFueSB0ZXh0IGJlbG93IDQuMiB3aGVuIHRoZXJlIGFy ZSA0LjIuMSwgNC4yLjIsIGV0Yy4gSSBjYW4gY3JlYXRlIGEgbmV3IHN1YnNlY3Rpb24gYXMNCj4g IjQuMi4xIE92ZXJ2aWV3IsKgIHdpdGggdGhlIHRleHQgeW91IHByb3Bvc2VkIGFuZCBzaGlmdCBv dGhlciBzdWJzZWN0aW9uIHdpdGggMC4wLjEuIFdpbGwNCj4gdGhhdCBoZWxwPw0KDQpUaGF0J3Mg bW9yZSBhIHF1ZXN0aW9uIG9mIHN0eWxlIHRoYW4gYSB0ZWNobmljYWwgcXVlc3Rpb24uLi4gSSBk b24ndCBrbm93IHdoYXQgdGhlIElFVEYgU3R5bGUgR3VpZGUgKFRNKSBoYXMgdG8gc2F5IG9uIHRo ZSB0b3BpYyBidXQgdGhlcmUgYXJlIHF1aXRlIGEgZmV3IFJGQ3MgdGhhdCBoYXZlIHRleHQgYXQg dGhlIGJlZ2lubmluZyBvZiBhIHNlY3Rpb24gYW5kIHRoZW4gY29udGludWUgaW4gc3Vic2VjdGlv bnMuIFJGQyA4MTQxIGlzIG9uZSBleGFtcGxlLCB3aGVyZSBzZWN0aW9uIDEgWzFdIGhhcyBhIGZh aXJseSBsb25nIHRleHQgYW5kIHRoZW4gY29udGludWVzIHRvIHNwZWNpZnkgdGhpbmdzIGluIDEu MSwgMS4yIGV0Yy4NCg0KSSdtIGZpbmUgZWl0aGVyIHdheS4NCg0KWzFdIGh0dHBzOi8vdG9vbHMu aWV0Zi5vcmcvaHRtbC9yZmM4MTQxI3NlY3Rpb24tMQ0KDQpCZXN0LA0KDQpMYXJzIA0KDQo= From nobody Thu Apr 12 11:50:40 2018 Return-Path: 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 8563F12DA18 for ; Thu, 12 Apr 2018 11:50:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 8zosVvb6l6Ze for ; Thu, 12 Apr 2018 11:50:30 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 740D4126C83 for ; Thu, 12 Apr 2018 11:50:30 -0700 (PDT) Received: from [10.0.1.91] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w3CIoCC5049357 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 12 Apr 2018 13:50:13 -0500 (CDT) (envelope-from ben@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.91] From: Ben Campbell Message-Id: <37455AEC-D586-4141-B0B1-4AB18102CDC2@nostrum.com> Content-Type: multipart/signed; boundary="Apple-Mail=_647FB788-C402-4714-9DDB-D591B02EF577"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Date: Thu, 12 Apr 2018 13:50:11 -0500 In-Reply-To: <492366533.1285812.1523480980508@mail.yahoo.com> Cc: "Svensson, Lars" , "urn@ietf.org" , "georg.mayer.huawei@gmx.com" , "jbakker@blackberry.com" , "Dale R. Worley (worley@ariadne.com)" To: R Atarius References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> <492366533.1285812.1523480980508@mail.yahoo.com> X-Mailer: Apple Mail (2.3445.6.18) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 18:50:33 -0000 --Apple-Mail=_647FB788-C402-4714-9DDB-D591B02EF577 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 HI Roozbeh and others, When deciding what to fix, please remember we are late in the process = for non-critical fixes. When in doubt, please lean towards leaving = things is=E2=80=9D. Thanks! Ben. > On Apr 11, 2018, at 4:09 PM, R Atarius wrote: >=20 > Hi Lars >=20 > please see below >=20 > thanks > Roozbeh >=20 >=20 > From: "Svensson, Lars" > To: R Atarius > Cc: "urn@ietf.org" ; "georg.mayer.huawei@gmx.com" = ; "ben@nostrum.com" ; = "jbakker@blackberry.com" ; "Dale R. Worley = (worley@ariadne.com)" > Sent: Wednesday, April 11, 2018 5:28 AM > Subject: RE: << PLEASE IGNORE THE PREV. MAIL>> [urn] Expert review = needed >=20 > Hi Rozbeh, >=20 > Just a minor comment from me (but I'll read the complete draft when = the new version is published): >=20 > On Friday, April 06, 2018 1:42 AM, R Atarius = [mailto:r_atarius@yahoo.com] wrote: >=20 >=20 > [...] >=20 > > 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? >=20 >=20 > 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 >=20 > "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." >=20 > [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. >=20 > = **************************************************************************= ******************************************** >=20 > 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: >=20 > 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. >=20 > 4.2.4 Hexadecimal Encoding > The following figure ... [X.S0008-A]. >=20 > [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? >=20 >=20 > Best, >=20 > Lars --Apple-Mail=_647FB788-C402-4714-9DDB-D591B02EF577 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrPqmMACgkQgFZKbJXz 1A0TlQ//W7iOD3uZ7T/iL3xqCCN9gcFhYWRiZ4hGl9fkjr46xx4ntVsx5BE2hVqg Uov1rkaPVwQaQnqCFXZYt7bykrFE7uUY6wMX/oUdboe5psUWXsNk0W0OabO5yTO4 7mgaUyzYrILbIpFCRtjHjSjtCDVVTacgfak7B4y47ZNo0zTqzET7QqCYiki4k0zc MGGPuILRQeRBsk3KB6l+Ah2cDBh5RcsZ5x0swgQV4h2AXwuMkurQt0yhgsgm53br S0nzKepZNzLW/TICzmX6+xwSQKHdlLOwN0CGELS+hl5k8qlPIHgdXnwX1Hoiaz9W 6SuisOs0yrzqtVoJfljdv/DYapUBeskPavmy+J/oBctOqECvocjKuv4HMn6SBGQc Hz5oxEONndv6FgHmteeCWQOxXf/aGlPH7EIzLqeQreL9MNy3lr7pSFD8WwZ8gKKc Sfu+0j1gKmkhv0m/OYavnW/WE6dHMftGuh1GTrmvUWjdz+5qF5nxA7D65htAzWZV CU09hAHH7gYrG7P/KPwluoXtSwyfcPEELxopCHTHk/Tj//D7+IzHCY04E9hIKH78 L8/5VVLy/4hSsD5epBbOCMYOJtJXAjFoDKcLB0chxZrE9hvrwQmVTZcNDzg5VUAL BPCUONNr62er0HfNeTwglwSbKsZBL5LegrlRtcf5/TDFgMKY0KI= =fj3h -----END PGP SIGNATURE----- --Apple-Mail=_647FB788-C402-4714-9DDB-D591B02EF577-- From nobody Thu Apr 12 12:28:21 2018 Return-Path: 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 C0E8A12D87F for ; Thu, 12 Apr 2018 12:28:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 vVbmEW71Bp2M for ; Thu, 12 Apr 2018 12:28:17 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 58C69128959 for ; Thu, 12 Apr 2018 12:28:17 -0700 (PDT) Received: from [10.0.1.91] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w3CJS5Vd055564 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 12 Apr 2018 14:28:06 -0500 (CDT) (envelope-from ben@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.91] From: Ben Campbell Message-Id: <9F94F4AB-2511-46A9-A4BD-21CA930B5B56@nostrum.com> Content-Type: multipart/signed; boundary="Apple-Mail=_607BE06F-C2B1-41BD-9A5A-7952AAADABB3"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Date: Thu, 12 Apr 2018 14:28:04 -0500 In-Reply-To: <37455AEC-D586-4141-B0B1-4AB18102CDC2@nostrum.com> Cc: "georg.mayer.huawei@gmx.com" , "urn@ietf.org" , "Dale R. Worley (worley@ariadne.com)" , "Svensson, Lars" , "jbakker@blackberry.com" To: R Atarius References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> <492366533.1285812.1523480980508@mail.yahoo.com> <37455AEC-D586-4141-B0B1-4AB18102CDC2@nostrum.com> X-Mailer: Apple Mail (2.3445.6.18) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 19:28:20 -0000 --Apple-Mail=_607BE06F-C2B1-41BD-9A5A-7952AAADABB3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Oops, I meant to say =E2=80=9Cas is=E2=80=9D. Ben. > On Apr 12, 2018, at 1:50 PM, Ben Campbell wrote: >=20 > HI Roozbeh and others, >=20 > When deciding what to fix, please remember we are late in the process = for non-critical fixes. When in doubt, please lean towards leaving = things is=E2=80=9D. >=20 > Thanks! >=20 > Ben. >=20 >> On Apr 11, 2018, at 4:09 PM, R Atarius wrote: >>=20 >> Hi Lars >>=20 >> please see below >>=20 >> thanks >> Roozbeh >>=20 >>=20 >> From: "Svensson, Lars" >> To: R Atarius >> Cc: "urn@ietf.org" ; "georg.mayer.huawei@gmx.com" = ; "ben@nostrum.com" ; = "jbakker@blackberry.com" ; "Dale R. Worley = (worley@ariadne.com)" >> Sent: Wednesday, April 11, 2018 5:28 AM >> Subject: RE: << PLEASE IGNORE THE PREV. MAIL>> [urn] Expert review = needed >>=20 >> Hi Rozbeh, >>=20 >> Just a minor comment from me (but I'll read the complete draft when = the new version is published): >>=20 >> On Friday, April 06, 2018 1:42 AM, R Atarius = [mailto:r_atarius@yahoo.com] wrote: >>=20 >>=20 >> [...] >>=20 >>> 4.2.3. Check Digit >>>=20 >>> 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. >>>=20 >>> 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! >>>=20 >>> [Roozbeh]: OK but can I leave it as it is? >>=20 >>=20 >> 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 >>=20 >> "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." >>=20 >> [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. >>=20 >> = **************************************************************************= ******************************************** >>=20 >> 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: >>=20 >> 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. >>=20 >> 4.2.4 Hexadecimal Encoding >> The following figure ... [X.S0008-A]. >>=20 >> [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? >>=20 >>=20 >> Best, >>=20 >> Lars >=20 > _______________________________________________ > urn mailing list > urn@ietf.org > https://www.ietf.org/mailman/listinfo/urn --Apple-Mail=_607BE06F-C2B1-41BD-9A5A-7952AAADABB3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrPs0QACgkQgFZKbJXz 1A3rTA//cGdjp9gawV+TMgTsLlpfHlCI0YGG80cb6Br2kl0XsNIU+itVKBLM52Us LLsv5F/bDiaPC8TcDmjPtJmxUgPvruAmcYY3/gWzPNymldgv+Q6Txbp4FMicTM4J RzrEq3JePJeCN/zGy06JXCc9eFUkvMGDL9qxNK0ybxzYxDTqtLskWFUkT33Z9O5Z WSwqHVVBtO1uGTEp/JtYpqv6sTUQOq6FO7s3ZErwVr/FAPBG2/1foYjXmRGMINPs 4GZBHu20R2B0T+c1rdNYz8kxWusqWFtDfnNuNYzEafjtkdpllD+a++erBYQCJHlS tCnlvbj8VC/xoo/DDCSIyer6cmvNUx+k1vFcrsU3niF741ho1I1sLCIPybxXeg5w v3H6fq4NBLYeJw6zJRtMs3WYCPCJHlZx6Eutx1FoUS2z3p198jDMqZNlUyKDQkV6 m5UMhUW1SHztEjGqdS8ucp71afrQTBtJcOtCKnQ8khrj+D4SaZyaUoqXYU3G9Rij XTPjL5hhvPSslz4C5uYHJcIzCQDMF04ZMycVYkiTw5EX4+zHwTfLB2w13+vMVS8f AGu76YA8rf/M1L3fTrS9Z1xFt+RH7nl9tY7DtmQ1HbJzq+t5XUECRSsS2fOSC1J6 aKUL5TXUT7I0suUWkyourltW5KE0b5kGCCBPFrfrSh79fIbPYQo= =4ppe -----END PGP SIGNATURE----- --Apple-Mail=_607BE06F-C2B1-41BD-9A5A-7952AAADABB3-- From nobody Thu Apr 12 14:58:46 2018 Return-Path: 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 6961512D77A for ; Thu, 12 Apr 2018 14:58:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 tiMpqzj3Gu9h for ; Thu, 12 Apr 2018 14:58:42 -0700 (PDT) Received: from sonic310-27.consmr.mail.gq1.yahoo.com (sonic310-27.consmr.mail.gq1.yahoo.com [98.137.69.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 2D9A312AF83 for ; Thu, 12 Apr 2018 14:58:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1523570321; bh=5mKd6bq9lZuHhxl2U4Dt/L2UiXzozEFjgfEIopc7Gk0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=qwoFERK9uFzReDG4z451mS1GAe1XOjJFMTgVOZJN1NkElvdLOktXMhuwA1llUAxVUuuOA91sTS+09MXuJ1oTKVP2ZdorbHyj4s5zu5E9OLXzUsseqM4KBG0Ug2KStd9RRrEdjR0AlprjcZLryIVgueKVQaThJZ0hMkfwM08AdKI4TyHvOIFxKpfJx7TdtPClQ26T7frXvni2g90yIKdjtfFH9wTNEeLqtlQGv1bsjdHapodHjpsrpBnEeK70q5jd5EQEvV8kYkuQnmmEQs8OJp/l40btaXeqkMr9EsEluKfh9ApuFq1rkqh7DSAUzE99XlLqocgAGMy9HCAqrDASIg== X-YMail-OSG: 6YqtzfUVM1kgzRisVSbDeuhhb3ldQy.6Y6bfZiUgFbBeewLLmA3p2_bVuRMDveN KwPpdb8PC_VOpurQuP2VwdnHtB482ag3rkcyUdt7Un2SVm2zGyzM.34wMPUjbIyPjdGuLdMdW5Pp JsyqwSRIor3xTfgfzAgzbCyGNjcgmmunKVBjeYMDjKv6q13OMqKbD86ZvRIgyla1gqI_j5bq7psM iURdo6H1_0stCA1amaOogEc4fn5XL0sH34hghujnlDvS2W5uuSQ_Db6njS4EUFd2z3m1iqnqHbbX 0hyxByjsxcAo3GHV8AGTTwGXG6LVxsQJxuDupSx2m1VU3homc8JlR1C5YcUF_YbrxLLKIAQaA9hg dOCmGWVeXIQCybwcWpHsZ7RKyG4B.ve6BQ0cxK38hHoc5UfELX3pEbmo2qmrhk0JaeSPwBozQ.mN Zg30ZC4rz7LGSXykBILDeqlhiMCSMAIGESvzCIHJ_BUfwgSQQ1UYt5gNnc_jDVIlhv3TYDr5opJV PdGLZTda9WV8kwZV.swGkl3FqK5QmN6pF Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Thu, 12 Apr 2018 21:58:41 +0000 Date: Thu, 12 Apr 2018 21:58:21 +0000 (UTC) From: R Atarius Reply-To: R Atarius To: "Svensson, Lars" Cc: "urn@ietf.org" , "georg.mayer.huawei@gmx.com" , "ben@nostrum.com" , "jbakker@blackberry.com" , "Dale R. Worley (worley@ariadne.com)" Message-ID: <312034622.1622289.1523570301763@mail.yahoo.com> In-Reply-To: References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> <492366533.1285812.1523480980508@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1622288_710798712.1523570301762" 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 21:58:44 -0000 ------=_Part_1622288_710798712.1523570301762 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable HiPlease see below ThanksRoozbeh [...] > 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 >=20 > "This is a single hexadecimal digit (bits 1-4 of octet 8). The check digi= t is not > transmitted by the mobile equipment and is not used in the MEID URN." >=20 > [Roozbeh] I believe that's how I started but I received comments about it= s 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. OK, so you're damned if you do and damned if you don't... I'm fine either w= ay, too, so if not Dale or anyone else objects, you can leave the sentence = as it is. [Roozbeh] I leave then as it is. ***************************************************************************= ******************************************* >=20 > Looking more closely at section 4.2, it feels a bit awkward that you firs= t define the > parts of the MEID format and then go on to put them together. You might w= ant to > consider rephrasing as follows: >=20 > 4.2 MEID Format > The MEID format is 15 hexadecimal digits encoded in 8 octets as defined i= n [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 la= st > hexadecimal digit is a check digit. For more details on the hexadecimal e= ncoding 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 s= ubsection as > "4.2.1 Overview"=C2=A0 with the text you proposed and shift other subsect= ion with 0.0.1. Will > that help? That's more a question of style than a technical question... I don't know w= hat the IETF Style Guide (TM) has to say on the topic but there are quite a= few RFCs that have text at the beginning of a section and then continue in= subsections. RFC 8141 is one example, where section 1 [1] has a fairly lon= g text and then continues to specify things in 1.1, 1.2 etc. I'm fine either way. [1] https://tools.ietf.org/html/rfc8141#section-1 [Roozbeh] I created an overview section and added your comment. Best, Lars=20 =20 ------=_Part_1622288_710798712.1523570301762 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi
Please se= e below

Thanks
Roozbeh

[...]
=
> I think that technically you could, but I also agree with Dale = that it might be confusing
> to supply non-required in= formation. 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
&= gt; and that's why I added that sentence. I am good either way. If that mak= es you, Dale
> and IETF community satisfied then I can= remove that sentence. Please let me know.

OK, so you're damned if you do and damned if you don't... I'm fine eit= her way, too, so if not Dale or anyone else objects, you can leave the sent= ence as it is.

[Roozbeh] I leave then as it is.
*************************************************************************= *********************************************
>
> Looking more closely at section 4.2, it feels a bit awkwa= rd that you first define the
> parts of the MEID forma= t 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 hexad= ecimal digits encoded in 8 octets as defined in [S.R0048-
> A]. The first eight hexadecimal digits constitute the manufacturer co= de, the next six
> hexadecimal digits the serial numbe= r 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 Encod= ing
> 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?

That's more a question of style than a technical q= uestion... I don't know what the IETF Style Guide (TM) has to say on the to= pic but there are quite a few RFCs that have text at the beginning of a sec= tion and then continue in subsections. RFC 8141 is one example, where secti= on 1 [1] has a fairly long text and then continues to specify things in 1.1= , 1.2 etc.

I'm fine either way.

[1] https://tools.ietf.org/h= tml/rfc8141#section-1

[Roozbeh] I created an overview section and added your com= ment.

=
Best,

Lars



------=_Part_1622288_710798712.1523570301762-- From nobody Thu Apr 12 15:00:42 2018 Return-Path: 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 6C31812D77A for ; Thu, 12 Apr 2018 15:00:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 bdfP7WIL616m for ; Thu, 12 Apr 2018 15:00:38 -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 95CE012AF83 for ; Thu, 12 Apr 2018 15:00:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1523570438; bh=tJWu/P9tXfTLxEST3UGYveZjqtq3g1kTDbWIEoquSSw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=aWqAOPVJ2oshC8baCSD5SqvZqeAVrB+yP9pIPcxlkRsg+4I7pketOUO7PzyZlpcUjGFD4uSbV9kJAFRCjSm74dy6duiALj9oRD9M+D+1wU8ZPc8nzVLpbdQiVc5PGWSqhkirFiY7zh2V2pcSvdju57fmSHsf+TyV2rqyYwTug3N3CEfylvGzPH8imigyv50rVGqG9yGZKtx9tCqQcGq3j+/5u+V8h7T9mt231+Yvu/9LQ17O2hOSQsvWW4Pksu3pyT5024hPpgHqG5pbV0BjneUr+O5Rg16OgqWoQr1jQ7cf5rJ++h62eOxCxKv6Bk8J+11tfunNEKza/zF6kYBBCQ== X-YMail-OSG: q8zoPuUVM1mLZOu83yB3jjE3lmkTYluvDRZqVM2duGnn5AsIv1MyWtFU04zq5Ta 0rnsr5px1QCrYyOYYP8Imd1vyWfy8wS4gwNi5dcP8tNvQyh28ChuLCyp4gLB9DpNOxus8A8Lp4Hw 8Fet_c5Ysq8mc9fh5ilozNMuGjoWFEZIWaAKb8c8OvwP4W3XrMEjq2Uzd3kRvyQkunpL41KcKB3m sAt6EYjijbK6igLQu6R_ZK2ooNYd0tNBFGnKF55GjAg2KCq7mu8kVhPZTGS9Jt4nLcXi_qkMs7aj SvP6ryGVljAY7bYzIGVH1QazOgdfS0T0OhD0Y_Kf_mMrr3trokR2hCLRa_09B_UXqFvmjQuwJJa9 ODmYyvP4McsihQDVTznKkNR5Z6AsJPf5ggDeDqsiWxCkFkeFpk.rW.xiB.5Pv2WxmCiFjiRAjofy 5R5kZuGbnbUvFlaZoROU6EfnmBsWZ3N3VgQGL2od47lygcn0zLr4YiTcpkSsWA6hnFRTY.CLUJu4 tOQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Thu, 12 Apr 2018 22:00:38 +0000 Date: Thu, 12 Apr 2018 22:00:37 +0000 (UTC) From: R Atarius Reply-To: R Atarius To: Ben Campbell Cc: "georg.mayer.huawei@gmx.com" , "urn@ietf.org" , "Dale R. Worley (worley@ariadne.com)" , "Svensson, Lars" , "jbakker@blackberry.com" Message-ID: <1745166994.1623590.1523570437335@mail.yahoo.com> In-Reply-To: <9F94F4AB-2511-46A9-A4BD-21CA930B5B56@nostrum.com> References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> <492366533.1285812.1523480980508@mail.yahoo.com> <37455AEC-D586-4141-B0B1-4AB18102CDC2@nostrum.com> <9F94F4AB-2511-46A9-A4BD-21CA930B5B56@nostrum.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1623589_1199000987.1523570437332" 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 22:00:41 -0000 ------=_Part_1623589_1199000987.1523570437332 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable thanks, I added Lars's comments and if there is no more comments and everyone is sa= tisfied, I can create a new document.=C2=A0 From: Ben Campbell To: R Atarius =20 Cc: "georg.mayer.huawei@gmx.com" ; "urn@ietf.or= g" ; "Dale R. Worley (worley@ariadne.com)" ; "Svensson, Lars" ; "jbakker@blackberry.com" Sent: Thursday, April 12, 2018 12:28 PM Subject: Re: [urn] << PLEASE IGNORE THE PREV. MAIL>> Expert review needed =20 Oops, I meant to say =E2=80=9Cas is=E2=80=9D. Ben. > On Apr 12, 2018, at 1:50 PM, Ben Campbell wrote: >=20 > HI Roozbeh and others, >=20 > When deciding what to fix, please remember we are late in the process for= non-critical fixes. When in doubt, please lean towards leaving things is= =E2=80=9D. >=20 > Thanks! >=20 > Ben. >=20 >> On Apr 11, 2018, at 4:09 PM, R Atarius wrote: >>=20 >> Hi Lars >>=20 >> please see below >>=20 >> thanks >> Roozbeh >>=20 >>=20 >> From: "Svensson, Lars" >> To: R Atarius >> Cc: "urn@ietf.org" ; "georg.mayer.huawei@gmx.com" ; "ben@nostrum.com" ; "jbakker@blackbe= rry.com" ; "Dale R. Worley (worley@ariadne.com)" >> Sent: Wednesday, April 11, 2018 5:28 AM >> Subject: RE: << PLEASE IGNORE THE PREV. MAIL>> [urn] Expert review neede= d >>=20 >> Hi Rozbeh, >>=20 >> Just a minor comment from me (but I'll read the complete draft when the = new version is published): >>=20 >> On Friday, April 06, 2018 1:42 AM, R Atarius [mailto:r_atarius@yahoo.com= ] wrote: >>=20 >>=20 >> [...] >>=20 >>> 4.2.3.=C2=A0 Check Digit >>>=20 >>>=C2=A0 This is a single hexadecimal digit (bits 1-4 of octet 8) and is u= sed >>>=C2=A0 as assurance of integrity in error-prone operations, e.g. when us= ed >>>=C2=A0 with certain types of readers during inventory management operati= ons. >>>=C2=A0 The check digit is not transmitted by the mobile equipment and ar= e >>>=C2=A0 not used in the MEID URN. >>>=20 >>> In section 4.2, for completeness, you give a lot of information that is >>> not strictly required.=C2=A0 However you don't give the really non-triv= ial >>> bit of information:=C2=A0 the formula for the check digit.=C2=A0 After = reading >>> this section, I was left curious what the check digit formula actually >>> is! >>>=20 >>> [Roozbeh]: OK but can I leave it as it is? >>=20 >>=20 >> I think that technically you could, but I also agree with Dale that it m= ight 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 >>=20 >> "This is a single hexadecimal digit (bits 1-4 of octet 8). The check dig= it is not transmitted by the mobile equipment and is not used in the MEID U= RN." >>=20 >> [Roozbeh] I believe that's how I started but I received comments about i= ts 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 th= at sentence. Please let me know. >>=20 >> ************************************************************************= ********************************************** >>=20 >> Looking more closely at section 4.2, it feels a bit awkward that you fir= st define the parts of the MEID format and then go on to put them together.= You might want to consider rephrasing as follows: >>=20 >> 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 manufactu= rer code, the next six hexadecimal digits the serial number within the manu= facturer code. The last hexadecimal digit is a check digit. For more detail= s on the hexadecimal encoding cf. 4.2.4. >>=20 >> 4.2.4 Hexadecimal Encoding >> The following figure ... [X.S0008-A]. >>=20 >> [Roozbeh] I think that is what is called a "hanging section", since ther= e 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"=C2=A0 with the text you propose= d and shift other subsection with 0.0.1. Will that help? >>=20 >>=20 >> Best, >>=20 >> Lars >=20 > _______________________________________________ > urn mailing list > urn@ietf.org > https://www.ietf.org/mailman/listinfo/urn =20 ------=_Part_1623589_1199000987.1523570437332 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
thanks= ,

=
I added Lars's comment= s and if there is no more comments and everyone is satisfied, I can create = a new document. 


=
= From: Ben Campbell <ben= @nostrum.com>
To: R= Atarius <r_atarius@yahoo.com>
Cc: "georg.mayer.huawei@gmx.com" <georg.mayer.huawei@gmx.= com>; "urn@ietf.org" <urn@ietf.org>; "Dale R. Worley (worley@ariad= ne.com)" <worley@ariadne.com>; "Svensson, Lars" <L.Svensson@dnb.de= >; "jbakker@blackberry.com" <jbakker@blackberry.com>
Sent: Thursday, April 12, 2018 12:2= 8 PM
Subject: Re: [urn= ] << PLEASE IGNORE THE PREV. MAIL>> Expert review needed
<= /font>

Oops, I m= eant to say =E2=80=9Cas is=E2=80=9D.

B= en.

> On Apr 12, 2018, at 1:50 PM, = Ben Campbell <ben@nostrum.com> wrote:
>
> HI Roozbeh and others,
>= ;
> When deciding what to fix, please remember we are= late in the process for non-critical fixes. When in doubt, please lean tow= ards leaving things is=E2=80=9D.
>
= > Thanks!
>
> Ben.
>
>> On Apr 11, 2018, at 4:09 PM, R A= tarius <r_atarius@yahoo.com> wrote:
>>
>> Hi Lars
>&= gt;
>> please see below
>>=
>> thanks
>> Roozbeh
>>
>>
>&= gt; From: "Svensson, Lars" <L.Svensson@dnb.de>
>> To: R Atarius <r_atarius@yahoo.= com>
>> Cc: "urn@ietf.org" <u= rn@ietf.org>; "georg.mayer.huawei@gm= x.com" <georg.mayer.huawei@gmx.com>; "ben@nostrum.com" <ben@nostrum.com&g= t;; "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
>>
&g= t;> Hi Rozbeh,
>>
>> Ju= st a minor comment from me (but I'll read the complete draft when the new v= ersion 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
>>>&nbs= p; as assurance of integrity in error-prone operations, e.g. when used
>>>  with certain types of readers during inven= tory 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 r= equired.  However you don't give the really non-trivial
>>> bit of information:  the formula for the check digit.=   After reading
>>> this section, I was lef= t curious what the check digit formula actually
>>&= gt; is!
>>>
>>> [Roo= zbeh]: 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, i= t might be better to omit this paragraph or to rephrase it as
>>
>> "This is a single hexadecimal dig= it (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 rece= ived 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 clos= ely 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 c= onsider 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 firs= t eight hexadecimal digits constitute the manufacturer code, the next six h= exadecimal digits the serial number within the manufacturer code. The last = hexadecimal digit is a check digit. For more details on the hexadecimal enc= oding cf. 4.2.4.
>>
>> 4.2= .4 Hexadecimal Encoding
>> The following figure ...= [X.S0008-A].
>>
>> [Roozb= eh] 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 shi= ft other subsection with 0.0.1. Will that help?
>> =
>>
>> Best,
>>
>> Lars
>
> _______________________________________________
> urn mailing list
>= ; https://www.ietf.org/mailman/listinfo/urn



------=_Part_1623589_1199000987.1523570437332-- From nobody Thu Apr 12 15:02:46 2018 Return-Path: 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 99A4A12D80E for ; Thu, 12 Apr 2018 15:02:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=MvkfUYsH; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=GTHrvT+N 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 fEYwsplmmuLB for ; Thu, 12 Apr 2018 15:02:38 -0700 (PDT) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B4EE12D77C for ; Thu, 12 Apr 2018 15:02:38 -0700 (PDT) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id E3C7421A75; Thu, 12 Apr 2018 18:02:37 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 12 Apr 2018 18:02:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=T76sqWKdtr+zD2zfP3jLqnhp71tYK S6IIteuPRp/630=; b=MvkfUYsHFIgUUa403n5uFaFOQuZNHyjAMo6fbCzi1cwJO c/T7wlOyp315VFJ0R10B4xZPmru68/MU7mpW9WYUrL8741sBJDFJ9Fu5S9P6iCxo mF4c7bR/coJtebe2KLfBHgbFT8YFQNVnvbxUkJUr8ZlHBYg0YNNOU3v3dqdvAeR5 j7GRUMvM4dGoxsDZBd5Y6MbYIW9UzOP6+qYNQxcFXvqO4oRhy7Mx1D1nWuOIb1vX XO8MtE1+5nXrFdVxCiKyEpwEB+lA7ryFOPc5UP8hd0s+uyIIkzaS/xqgNdgLbEQG 5M7ihhqRdSAQJfDoO3CNeYGN9sgTd0R+2ezDk7JZg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=T76sqW Kdtr+zD2zfP3jLqnhp71tYKS6IIteuPRp/630=; b=GTHrvT+Nkycpi9oAnLC+dt UbU74UBm6O7I8v/Bsp5UDa1ClL3PLGr30YOWTPaXxXZ0+DGuBTUENEphLMksdnh+ 3d+Jw6d49qoDcx7JnmQVUGT3hksbVe9HoxFZo1x4QSNrkCSVja2AOJvKEtVN0dY4 UgbGez4FU0FH8zQgP8wPfNFn19pKHbyLoiISRsORz+Z/vCWkc6/NkCyG+4zw/5qs 61dMyFjl4ubeaCRsj7TJsS23m3qUUVD3ERddAgmhpV8xat9EWNjciTUzCFp6a8uK igge8FDIFViHXCSQg0chGO0UNEQfSwLCodNL+ND67nBrQuCZ8+5/7uACMppSqTsA == X-ME-Sender: Received: from aither.local (unknown [76.25.3.152]) by mail.messagingengine.com (Postfix) with ESMTPA id 354AF10282; Thu, 12 Apr 2018 18:02:37 -0400 (EDT) To: urn@ietf.org References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> <492366533.1285812.1523480980508@mail.yahoo.com> <37455AEC-D586-4141-B0B1-4AB18102CDC2@nostrum.com> <9F94F4AB-2511-46A9-A4BD-21CA930B5B56@nostrum.com> <1745166994.1623590.1523570437335@mail.yahoo.com> From: Peter Saint-Andre Openpgp: preference=signencrypt Autocrypt: addr=stpeter@stpeter.im; prefer-encrypt=mutual; keydata= xsFNBFETDzsBEAC0FOv1N3ZJzIIxN6cKD475KVS9CHDPeYpegcOIPnL5eY1DCHeh/IwS1S7R CePtmiybNoV9FsI4PKUknzXQxA6LVEdAR/LUlhgJKjq+gsgp8lqbEILhg13ecH66HwLS9rar bQkC47T7kL8miIPBFC6E3A4Lq1L+eueO6UcLhKgoYkMxOjdiWrMgKTnVpch5ydLkPm/z0Zo8 zRgqlPuTLeCrXXZYnjHXLVFN2xy04UzOs7P5u5KVfx5Z7uQisr8pXtyLd6SpTZo6SHgKBv15 uz0rqXhsJojiGtOXfWznAjaS5FUOORq9CklG5cMOUAT8TNftv0ktsxaWDL1ELDVQPy1m7mtz o+VREG+0xmU6AjMo/GHblW1UU7MI9yCiuMLsp/HLrFuiosqLVZ85wuLQ2junPe3tK8h15Ucx IXAcpQ1VqIaDQFbeuLOXJTF8YHpHdpHYt/ZM1ll7ZBKGAo8yd7uF7wJ9D3gUazwdz9fFjWV7 oIk7ATwOlFllzmWDn+M2ygbHOGUGMX5hSaa8eDSieiR2QoLdn27Fip7kMBTJ2+GISrfnJTN/ OQvmj0DXXAdxHmu2C4QgmZbkge35n129yzXn9NcqzrGLroV62lL3LgX6cSbiH5i7GgWY6CAP b1pMogV0K475n9FvOSDRiG4QSO5yqKiA3OP5aKrIRp2TNAk4IwARAQABzSZQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBzdHBldGVyLmltPsLBeQQTAQIAIwUCURMPOwIbAwcLCQgHAwIB BhUIAgkKCwQWAgMBAh4BAheAAAoJEOoGpJErxa2p6bgQAKpxu07cMDOLc4+EG8H19NWXIVVy bOEvfGuHYZaLKkPrhrMZwJiOwBpyISNRt9qzX1eLCVaojaoEVX6kD8MGc5zKFfiJZy3j7lBW l+Ybr7FfXYy2BbAXKx49e1n6ci9LmBrmVfAEaxtDNPITZ9N9oUAb9vS0nrG036EwteEHAveQ vlDjO7lhz6+Cv7lZQgBj9rZ6khfcQ4S3nSCQaKLQ9Iav4fqxI7SfuPKnx6quHX3JNLGnVo3w l+j/foCK0iTrmtHxCI3kc/bx6g32pRjHEPX0ALMBhmzU2uca+TE0zCEC96mgYXAUCwdnCFWy beIEbt6pz65iML13kAVAq0H/GqncnMGN0MbOatnw1Tdz/vkLojIy7QbPcQ0plUFxv5491xPf IrHhOWdRXp6WUt88fcqhT6MHZpVRtusj2ornKVVn+Y0GLsMMCTcrXJRG7Ao1YV72t/pJpzfG WSaaxolxDIZ6B+76jrIhUhiWgo/4nf+DN6BIlCZQ6j6xxjjx462cu02kuhIILTk2pzaMOufT BWx0uJhZk/KP2Fay/41pX7pvVOwRC4uIlKsLnJKLPS7EDa4BUUxENfd/9LqOGwlII8BbSe98 PLMI8sXkcigc3UXMVda9ll0YhQa+lbP1NaszmnBhwuiCsgnPGbImsJuRzgEEgckwP/dNeyr6 MlFMyfaezsFNBFETDzsBEADBzOsEHpUmhkRUjH9Tek87dn5P/Yh/L/HptgCGk40TL/C+kYdk d3HyteMEf061PNmsS/Rq8k37Fu3VODYb9SPYKxtgksKSYUtIkPKvao09K9QNWPqyWuNf0F+i AjVMUudaEVFJ7bHF310RDwLY5IvLeCXxtvG+Vv/i+g77d2WdPDp+zLJ8306C4yBKjSJV8xW0 cn2fd7NviIEN6cNHTsZNDZVMlgYPrxnwSq8GTEPGC7HsLIwGcx3hIe9QjnPw9CpAmQENpDEy WcxgF5uwo2NJECoDswKz1Nb0gfawF3ZIbD+GcLujTu94iJuVg25jATWm9wTgcfZo4UPllRGX dIb8uWwUFQlLQgd4ROLZZtXNGmHIymJrV2crx53gxup+1j0XqhlzKg8xbImWhEfS9oHZkRK8 VHgmWSIt7TNwNir6N5j3lqwWVBhnu6GzF01sKGNySlqNRbd0fqhakCkK71b8ot8tYTcYG5Lg 10z6HTbgQx2UwLthUjqbblDQ+GLmrOhiWklLXRsnlnPMwnEyFePAnsT5tasy2Cn9qjpttNDa h7PB8iFUi9mtTF/XDVgpFaB5G3CDV7Q2NgbAI6g6QhLIAmXzSP635G83mda0TKXHQXHDyLJT Tn+WVFU7t4m4uLt+0DsWU8jXHQWyUTNG9WPUrXhusDUAPHxFCQ/n/lQVBwARAQABwsFfBBgB AgAJBQJREw87AhsMAAoJEOoGpJErxa2pqfgP/ApN+TRu2bBIgaw1dr3AznSSha84DIpXUDh3 udZvQrGbUtz8/mA+e3iZEN/cmmBw2LGlAuQoJNILTZQ318yTP+E5QU7fJH7FVsohUyvrMfyt 3IMA9jg0Z9MuloLezvIjjMfFeNa0ROgDb/ubOT7JQzi1kwN8Lu3lO80HwqBHXEeOLoislUSn ZajRKvITbKWkZ6PHRjlMw1Wk4oIi6VLHgGgj79zzL3uhML2663m7imShvz1QcHTwvyR5i8cZ bNOEkotZyERiA1p7YHuruS+QvTi3ZPoQbnMUB3a7py9d11bw1+w3LiAUGZE/z5hBWOFxYtw+ w/U/Vx0BwJGYlwU3M2W20uEXe+qxz7wnakygKjmLiD2z4njfKjcNCiV3FmXrpmWgADln1c4j fxDh0NrndrsM8FPDf1TMPtOZgFDkKripc9xkZ/25P6xn27oTOHWKcAC0QhxSH+HuVBBRk8Ag F+zAbDZe4/L6+kanSrycIXW+wCzwBq61aWsz2QhhuKjozVkhk4dRG+CfjzAFjnyxwYERn3uX VKQAwTwcdNcTI9RV98IsNrw9Y4lJEAg6CjNPmiD5+EASycqaOuToRSGukr8sOQLWLPyTnez/ aG8Xf7a+fntWzK2HuDYoSDhJJrylWw/lMklOBm4wtMeNA0zcQH6AQV/GzQVQkSGqrLuMVIV/ Message-ID: Date: Thu, 12 Apr 2018 16:02:36 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1745166994.1623590.1523570437335@mail.yahoo.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 22:02:42 -0000 Please do. :-) On 4/12/18 4:00 PM, R Atarius wrote: > thanks, > > I added Lars's comments and if there is no more comments and everyone is > satisfied, I can create a new document.  > > > ------------------------------------------------------------------------ > *From:* Ben Campbell > *To:* R Atarius > *Cc:* "georg.mayer.huawei@gmx.com" ; > "urn@ietf.org" ; "Dale R. Worley (worley@ariadne.com)" > ; "Svensson, Lars" ; > "jbakker@blackberry.com" > *Sent:* Thursday, April 12, 2018 12:28 PM > *Subject:* Re: [urn] << PLEASE IGNORE THE PREV. MAIL>> Expert review needed > > Oops, I meant to say “as isâ€. > > Ben. > >> On Apr 12, 2018, at 1:50 PM, Ben Campbell > wrote: >> >> HI Roozbeh and others, >> >> When deciding what to fix, please remember we are late in the process > for non-critical fixes. When in doubt, please lean towards leaving > things isâ€. >> >> Thanks! >> >> Ben. >> >>> On Apr 11, 2018, at 4:09 PM, R Atarius > wrote: >>> >>> Hi Lars >>> >>> please see below >>> >>> thanks >>> Roozbeh >>> >>> >>> From: "Svensson, Lars" > >>> To: R Atarius > >>> Cc: "urn@ietf.org " >; "georg.mayer.huawei@gmx.com > " >; "ben@nostrum.com > " >; > "jbakker@blackberry.com " > >; "Dale R. > Worley (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 >> >> _______________________________________________ >> urn mailing list > >> urn@ietf.org > >> https://www.ietf.org/mailman/listinfo/urn > > > > > > _______________________________________________ > urn mailing list > urn@ietf.org > https://www.ietf.org/mailman/listinfo/urn > From nobody Thu Apr 12 15:23:35 2018 Return-Path: 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 C8C5C12D77C for ; Thu, 12 Apr 2018 15:23:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 hU6X04Z89-me for ; Thu, 12 Apr 2018 15:23:32 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 32F0512895E for ; Thu, 12 Apr 2018 15:23:32 -0700 (PDT) Received: from [10.0.1.91] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w3CMNHLA084149 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 12 Apr 2018 17:23:17 -0500 (CDT) (envelope-from ben@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.91] From: Ben Campbell Message-Id: <03AD190B-FC47-4DED-B3B5-187CF132150A@nostrum.com> Content-Type: multipart/signed; boundary="Apple-Mail=_258CD913-3108-4845-9D5E-DC5A3B031832"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Date: Thu, 12 Apr 2018 17:23:16 -0500 In-Reply-To: <1745166994.1623590.1523570437335@mail.yahoo.com> Cc: "georg.mayer.huawei@gmx.com" , "urn@ietf.org" , "Dale R. Worley (worley@ariadne.com)" , "Svensson, Lars" , "jbakker@blackberry.com" To: R Atarius References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> <492366533.1285812.1523480980508@mail.yahoo.com> <37455AEC-D586-4141-B0B1-4AB18102CDC2@nostrum.com> <9F94F4AB-2511-46A9-A4BD-21CA930B5B56@nostrum.com> <1745166994.1623590.1523570437335@mail.yahoo.com> X-Mailer: Apple Mail (2.3445.6.18) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 22:23:35 -0000 --Apple-Mail=_258CD913-3108-4845-9D5E-DC5A3B031832 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Please submit a new version at your earliest convenience. Thanks! Ben. > On Apr 12, 2018, at 5:00 PM, R Atarius wrote: >=20 > thanks, >=20 > I added Lars's comments and if there is no more comments and everyone = is satisfied, I can create a new document. >=20 >=20 > From: Ben Campbell > To: R Atarius > Cc: "georg.mayer.huawei@gmx.com" ; = "urn@ietf.org" ; "Dale R. Worley (worley@ariadne.com)" = ; "Svensson, Lars" ; = "jbakker@blackberry.com" > Sent: Thursday, April 12, 2018 12:28 PM > Subject: Re: [urn] << PLEASE IGNORE THE PREV. MAIL>> Expert review = needed >=20 > Oops, I meant to say =E2=80=9Cas is=E2=80=9D. >=20 > Ben. >=20 > > On Apr 12, 2018, at 1:50 PM, Ben Campbell wrote: > > > > HI Roozbeh and others, > > > > When deciding what to fix, please remember we are late in the = process for non-critical fixes. When in doubt, please lean towards = leaving things is=E2=80=9D. > > > > Thanks! > > > > Ben. > > > >> On Apr 11, 2018, at 4:09 PM, R Atarius wrote: > >> > >> Hi Lars > >> > >> please see below > >> > >> thanks > >> Roozbeh > >> > >> > >> From: "Svensson, Lars" > >> To: R Atarius > >> Cc: "urn@ietf.org" ; "georg.mayer.huawei@gmx.com" = ; "ben@nostrum.com" ; = "jbakker@blackberry.com" ; "Dale R. Worley = (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 > > > > _______________________________________________ > > urn mailing list >=20 > > urn@ietf.org >=20 > > https://www.ietf.org/mailman/listinfo/urn >=20 >=20 >=20 --Apple-Mail=_258CD913-3108-4845-9D5E-DC5A3B031832 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrP3FQACgkQgFZKbJXz 1A1RlA/8CDDaa4Bu0dO0Ma0wCFQgzqrmKDD677WuFgXA45+rBWwWPpblqA+yQlCV ZxQq/4E+lkjBWGAos7ys/rs816MrBXPEvgShUyQpytnBWQznekmH5ITV+MmftaBA n3jDIfQS85eg4f8AowS5eLwJbWl7yZrjtAGZAbEdmA92bet+NEMNioq2yRGubgGV KbG7kYoXMEpEQD5jMEh+3dyLK80qmRxdDgmHLyP1dWgrllrtp4rJZFXTSpoVIakG kBqvgs/wmxFnoozZNakIPyznqoGf07kP4O7XUYVVbYlkmuABhpVhicF07mAebu25 z9ranOR1zgCCyXtR7r3w6Q+qMEKdlrP013Gi1F9FMVEKEQrB6/J+6Oo5um6mYv1P +9i4+KKa7Ocs/V1bnQymL4/t2yBiXfFN53xbzR4+TOgsPL2Gemr/9fR9AxnTMU+m wafSaxkB0KEnuz6GrdzYGrVMWp11/QHd/QdVLNHMMf+H4EkFIfc2PPl7Y6hcK15/ D4vad2dRTINtn5Fygw+U0qrXzjUC2b8J31Sj4a9T4Ldkh0ct15szzofroH/RD6H0 z/mnCtI3E1JBuI39B4sLS0/lFbU95lYlghd35fPJlOrbSWnLwYLQlfuDmeMqE5Ne TD37b2rfAlMosj3Pl8gY7x9gL5TuCDkyHNDHwgmxLratQP4SJC0= =J1b0 -----END PGP SIGNATURE----- --Apple-Mail=_258CD913-3108-4845-9D5E-DC5A3B031832-- From nobody Thu Apr 12 16:53:56 2018 Return-Path: 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 94663124D6C for ; Thu, 12 Apr 2018 16:53:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 hZ1XkdXLknnI for ; Thu, 12 Apr 2018 16:53:53 -0700 (PDT) Received: from sonic310-28.consmr.mail.gq1.yahoo.com (sonic310-28.consmr.mail.gq1.yahoo.com [98.137.69.154]) (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 CC9601277BB for ; Thu, 12 Apr 2018 16:53:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1523577232; bh=qPX2CqiFaPlTNkrCly9AIVyGM0/cZg8BmIrTNJHcG60=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=BE9qUlqDz3992Y+6LDVPH2EEWyRtBZfD0JSotGYvEorDjsPL3JWnmflSrUS9dtMA77+JGlsbim2260Q8m0s5LavBtnqTvdAvjSeaG0x4tm/SSBU385uhZedP4era7A5p2VKooo9fhm5ur89epw/RzKCAr5r+JBZwJNFe7JUhOdNr5x5sfHL5QkYxe7FFltRMGIL0ekhukwrE5dyBnujF0deLUZOxw10H5jwCpHZuWTDBviGQturlYBJhtDp1B22U9mi1dwUPrHFCUPixeEaBU6aPBxAa7kHov3BQuRJX0x78x1m1QwDJ7MPyIqbAcvFDsgGkoDdlfDuh82ycd08fZw== X-YMail-OSG: UIx3j3gVM1ksR8yqEU2sJMLCLbMcOz_YwbP2FgAiW83a408h_YHP2Nna6NHAMKj eugDREeM8hurca56HRPL6a5H74f0gpqqfDLfDWuF6uOkDuQnAHw6DKjU8qH3YmfygkBn343E0dGc BI2b.Io7omToZ6ogVlMOOnmP1hH2wgO2AItyMnJSs4yrhTnLcpYSE4FlVxVQYjHsghvDlDLFMgKi vD94aHxLPbRQa9u.sm_J4_pymtME2KEiIm7SMR3j3ZFfLhHhIM4nQUDg5j_I49mxNZor5uozk6NA XEnd2yvZmlrTw_zJ93nB7_aGvDHwbWJPidcXPlYzL2E5jDrjj0Ay4SkKIIQR0H244WQunu1sAGvf 5TXkehArzMwcBT3JPEmhX3uUiE8cLL8YV92G0A4rPH0fMULFXsoBDpQy4SdlYBRyD9CfCVlV3hmW 6K80sDsa1MkbGY85lurldAG.CXAyJj7gGOebS5eGC7CTrThKaNfsGetorB5z4NSxnMRnWJyxlkOe 9vQ_rCmFtaqYcmBUwkwW8.5wwGw1HiRwqwn4.kbWUMp3IUioeO39ijM85jKK.jY8wItc- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Thu, 12 Apr 2018 23:53:52 +0000 Date: Thu, 12 Apr 2018 23:52:31 +0000 (UTC) From: R Atarius Reply-To: R Atarius To: Ben Campbell , Georg Mayer , John-Luc Bakker , "Dale R. Worley" , Lars Svensson , "urn@ietf.org" Message-ID: <1152249163.1658635.1523577151047@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1658634_118228108.1523577151046" References: <1152249163.1658635.1523577151047.ref@mail.yahoo.com> 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: Subject: [urn] draft-atarius-dispatch-meid-urn-17 X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 23:53:55 -0000 ------=_Part_1658634_118228108.1523577151046 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello all, new revision has been uploaded.=C2=A0 https://www.ietf.org/id/draft-atarius-dispatch-meid-urn-17.txt thanksRoozbeh=C2=A0 ------=_Part_1658634_118228108.1523577151046 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello all,

new revision has been = uploaded. 



thanks
Roozbeh 
------=_Part_1658634_118228108.1523577151046-- From nobody Thu Apr 12 19:02:59 2018 Return-Path: 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 8992D124D6C for ; Thu, 12 Apr 2018 19:02:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=LZhfyAqz; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ZlZiQ9on 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 2UIkkWXs6JSv for ; Thu, 12 Apr 2018 19:02:55 -0700 (PDT) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78ADE124205 for ; Thu, 12 Apr 2018 19:02:55 -0700 (PDT) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 9C8A121B99; Thu, 12 Apr 2018 22:02:54 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 12 Apr 2018 22:02:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=McNiMt21oQKVZb6CgfHk4gzREWwCH Tc3PM4hNwSfsUk=; b=LZhfyAqzvmpGAi3muIQOx9LqwIPcT33YPYOnM/IV87HWf 4JxxJjgrur2f/5yAT8MuRqAB7W8O56NOJLASP6dxSEGTQJnaZUE9ootUDuXgX5n/ y1cQ1/8Jn9fP3ZG1gu1yCv7lrabUuyeK4dfYAL/uEeZZH6bVm//PvDhBhLY2dbGF k2eCQdnosFCn/uJLf6C7MPm6ZiAl6f0U6WiAnuFun2xF+jHwDn3buTiIELQFOlO/ SvMIva4X3i2ry/mFxqfvsbfiHC5pZgfuNUAieCV5pNA6uBkIRuUOa296rzqvDmeN AGAEdFSQ9KA61UxXMZHYhCVlcjn6BhsCXqpgBiqow== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=McNiMt 21oQKVZb6CgfHk4gzREWwCHTc3PM4hNwSfsUk=; b=ZlZiQ9onGE389VSiDFVtyA 7sh+WO/fKLqgUdWAOuTD7oga/us2umPl6gO7cmNoTG09y2LjHcNmc+YpDNXTjVue 64kNtnI/1dUGpi4Wu2p8L6XkZhv8J9wyhHj75/WNaPb7VXdGrlCCkBa5frWtrg33 waIk3MZkaMRAZ5PmsFrYLPS4GwmCXYY+huV6NVPKykJYN5xd/OkkUE2wO33s350O zVoyKYewflqVkpfBJfSE0/B9KPUh36rvQboNUstJGLfvtWXsUF/SJLpFhWxEVYp4 jNJdVr+vBcrYWSioDs/9FR+jIpTCqwloNoiqKOj6b0xLk4qf8ukgl0xxMzGJiKFg == X-ME-Sender: Received: from aither.local (unknown [76.25.3.152]) by mail.messagingengine.com (Postfix) with ESMTPA id DD19110281; Thu, 12 Apr 2018 22:02:53 -0400 (EDT) To: urn@ietf.org References: <1152249163.1658635.1523577151047.ref@mail.yahoo.com> <1152249163.1658635.1523577151047@mail.yahoo.com> From: Peter Saint-Andre Openpgp: preference=signencrypt Autocrypt: addr=stpeter@stpeter.im; prefer-encrypt=mutual; keydata= xsFNBFETDzsBEAC0FOv1N3ZJzIIxN6cKD475KVS9CHDPeYpegcOIPnL5eY1DCHeh/IwS1S7R CePtmiybNoV9FsI4PKUknzXQxA6LVEdAR/LUlhgJKjq+gsgp8lqbEILhg13ecH66HwLS9rar bQkC47T7kL8miIPBFC6E3A4Lq1L+eueO6UcLhKgoYkMxOjdiWrMgKTnVpch5ydLkPm/z0Zo8 zRgqlPuTLeCrXXZYnjHXLVFN2xy04UzOs7P5u5KVfx5Z7uQisr8pXtyLd6SpTZo6SHgKBv15 uz0rqXhsJojiGtOXfWznAjaS5FUOORq9CklG5cMOUAT8TNftv0ktsxaWDL1ELDVQPy1m7mtz o+VREG+0xmU6AjMo/GHblW1UU7MI9yCiuMLsp/HLrFuiosqLVZ85wuLQ2junPe3tK8h15Ucx IXAcpQ1VqIaDQFbeuLOXJTF8YHpHdpHYt/ZM1ll7ZBKGAo8yd7uF7wJ9D3gUazwdz9fFjWV7 oIk7ATwOlFllzmWDn+M2ygbHOGUGMX5hSaa8eDSieiR2QoLdn27Fip7kMBTJ2+GISrfnJTN/ OQvmj0DXXAdxHmu2C4QgmZbkge35n129yzXn9NcqzrGLroV62lL3LgX6cSbiH5i7GgWY6CAP b1pMogV0K475n9FvOSDRiG4QSO5yqKiA3OP5aKrIRp2TNAk4IwARAQABzSZQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBzdHBldGVyLmltPsLBeQQTAQIAIwUCURMPOwIbAwcLCQgHAwIB BhUIAgkKCwQWAgMBAh4BAheAAAoJEOoGpJErxa2p6bgQAKpxu07cMDOLc4+EG8H19NWXIVVy bOEvfGuHYZaLKkPrhrMZwJiOwBpyISNRt9qzX1eLCVaojaoEVX6kD8MGc5zKFfiJZy3j7lBW l+Ybr7FfXYy2BbAXKx49e1n6ci9LmBrmVfAEaxtDNPITZ9N9oUAb9vS0nrG036EwteEHAveQ vlDjO7lhz6+Cv7lZQgBj9rZ6khfcQ4S3nSCQaKLQ9Iav4fqxI7SfuPKnx6quHX3JNLGnVo3w l+j/foCK0iTrmtHxCI3kc/bx6g32pRjHEPX0ALMBhmzU2uca+TE0zCEC96mgYXAUCwdnCFWy beIEbt6pz65iML13kAVAq0H/GqncnMGN0MbOatnw1Tdz/vkLojIy7QbPcQ0plUFxv5491xPf IrHhOWdRXp6WUt88fcqhT6MHZpVRtusj2ornKVVn+Y0GLsMMCTcrXJRG7Ao1YV72t/pJpzfG WSaaxolxDIZ6B+76jrIhUhiWgo/4nf+DN6BIlCZQ6j6xxjjx462cu02kuhIILTk2pzaMOufT BWx0uJhZk/KP2Fay/41pX7pvVOwRC4uIlKsLnJKLPS7EDa4BUUxENfd/9LqOGwlII8BbSe98 PLMI8sXkcigc3UXMVda9ll0YhQa+lbP1NaszmnBhwuiCsgnPGbImsJuRzgEEgckwP/dNeyr6 MlFMyfaezsFNBFETDzsBEADBzOsEHpUmhkRUjH9Tek87dn5P/Yh/L/HptgCGk40TL/C+kYdk d3HyteMEf061PNmsS/Rq8k37Fu3VODYb9SPYKxtgksKSYUtIkPKvao09K9QNWPqyWuNf0F+i AjVMUudaEVFJ7bHF310RDwLY5IvLeCXxtvG+Vv/i+g77d2WdPDp+zLJ8306C4yBKjSJV8xW0 cn2fd7NviIEN6cNHTsZNDZVMlgYPrxnwSq8GTEPGC7HsLIwGcx3hIe9QjnPw9CpAmQENpDEy WcxgF5uwo2NJECoDswKz1Nb0gfawF3ZIbD+GcLujTu94iJuVg25jATWm9wTgcfZo4UPllRGX dIb8uWwUFQlLQgd4ROLZZtXNGmHIymJrV2crx53gxup+1j0XqhlzKg8xbImWhEfS9oHZkRK8 VHgmWSIt7TNwNir6N5j3lqwWVBhnu6GzF01sKGNySlqNRbd0fqhakCkK71b8ot8tYTcYG5Lg 10z6HTbgQx2UwLthUjqbblDQ+GLmrOhiWklLXRsnlnPMwnEyFePAnsT5tasy2Cn9qjpttNDa h7PB8iFUi9mtTF/XDVgpFaB5G3CDV7Q2NgbAI6g6QhLIAmXzSP635G83mda0TKXHQXHDyLJT Tn+WVFU7t4m4uLt+0DsWU8jXHQWyUTNG9WPUrXhusDUAPHxFCQ/n/lQVBwARAQABwsFfBBgB AgAJBQJREw87AhsMAAoJEOoGpJErxa2pqfgP/ApN+TRu2bBIgaw1dr3AznSSha84DIpXUDh3 udZvQrGbUtz8/mA+e3iZEN/cmmBw2LGlAuQoJNILTZQ318yTP+E5QU7fJH7FVsohUyvrMfyt 3IMA9jg0Z9MuloLezvIjjMfFeNa0ROgDb/ubOT7JQzi1kwN8Lu3lO80HwqBHXEeOLoislUSn ZajRKvITbKWkZ6PHRjlMw1Wk4oIi6VLHgGgj79zzL3uhML2663m7imShvz1QcHTwvyR5i8cZ bNOEkotZyERiA1p7YHuruS+QvTi3ZPoQbnMUB3a7py9d11bw1+w3LiAUGZE/z5hBWOFxYtw+ w/U/Vx0BwJGYlwU3M2W20uEXe+qxz7wnakygKjmLiD2z4njfKjcNCiV3FmXrpmWgADln1c4j fxDh0NrndrsM8FPDf1TMPtOZgFDkKripc9xkZ/25P6xn27oTOHWKcAC0QhxSH+HuVBBRk8Ag F+zAbDZe4/L6+kanSrycIXW+wCzwBq61aWsz2QhhuKjozVkhk4dRG+CfjzAFjnyxwYERn3uX VKQAwTwcdNcTI9RV98IsNrw9Y4lJEAg6CjNPmiD5+EASycqaOuToRSGukr8sOQLWLPyTnez/ aG8Xf7a+fntWzK2HuDYoSDhJJrylWw/lMklOBm4wtMeNA0zcQH6AQV/GzQVQkSGqrLuMVIV/ Message-ID: Date: Thu, 12 Apr 2018 20:02:52 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1152249163.1658635.1523577151047@mail.yahoo.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [urn] draft-atarius-dispatch-meid-urn-17 X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 02:02:58 -0000 On 4/12/18 5:52 PM, R Atarius wrote: > Hello all, > > new revision has been uploaded.  > > https://www.ietf.org/id/draft-atarius-dispatch-meid-urn-17.txt Thanks, Roozbeh. My apologies for not commenting on earlier versions of this document. Herewith some comments. 1. The title talks about MEID but this is really a registration for 3GPP2 as an organization, isn't it? That's a bit confusing. 2. The document uses the template from RFC 3406, not the updated template from RFC 8141. Would you mind modernizing Section 3? 3. HEX is defined as uppercase only. If lexical equivalence to lowercase a-f is desired, let's specify that in the registration. 4. This registration seems to fall under the fast-track registration policy (Section 6.3 of RFC 8141) and thus could point to [S.R0048-A] for many details (e.g., much of Section 4.2 in this Internet-Draft). Making these changes should not be too onerous, and might make the document shorter and simpler. Peter From nobody Thu Apr 12 20:02:13 2018 Return-Path: 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 6C7611243F6 for ; Thu, 12 Apr 2018 20:02:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=A49HJHai; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jCKdP0JN 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 6_08-lGAkk7C for ; Thu, 12 Apr 2018 20:02:11 -0700 (PDT) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3690B120227 for ; Thu, 12 Apr 2018 20:02:11 -0700 (PDT) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 7FC9D21B7C; Thu, 12 Apr 2018 23:02:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 12 Apr 2018 23:02:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=T3nr9vZm/UBljCfH9FpqLvdMlFyNx pgbs5FolLf+uj0=; b=A49HJHaiu7syv81IpwxlTQ5cNNaZprNbNrAT+fOBedcH1 j/QljGUFlqGbB9kO2jYl5RvGePKpUY0Tr48KQhhfY6wmsU+54doB0jGR6qx1SmUK aIY5NQGzdnb43yd6UdEmmpUeXkzydOzYjsL9Eh2KxckvXmtu1x5C3RvbJVCDcBvu FFr3SI1R3//YDg+HWSG8Wu6RppYXHXsebAr1x6qJCBG7jwhoPYEQ0Yvayp/9hamr IWPQtOI3+wv2vxJarwGwtlPHvntbIkl8VJrb0+TyCcd7GT1hUhGlBRzXFNzy9Nhi 0G/KcrLx7iU6hp26CsocAJeCpHepboGp0i6CAcLeQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=T3nr9v Zm/UBljCfH9FpqLvdMlFyNxpgbs5FolLf+uj0=; b=jCKdP0JNKhd1IBRMWOwmZm 9wImRA7odwxcDhL/WKJFPwIuGcXs1QyahWSQs+TwUEdmXt4aZHm1Og8OFG66Y9kE Wo3F/6pAd27HRZPuJAfT2mW7cSYYNo0vT1i2MMKNrvryXUgWGgDBwpFvfXJmtNbP q+ezdyrqRTuBcA8Gg4t7+pnsihLjbeypfFZ+HADfr0HOcB8qWboSRxGGQRe4j29D yEHPj+Dm1EfKQEWehNfNyV95AzitP0bHI2h1ijSNP0SvHBrCLwlieGRxFzRkFn2h P3DvLgDmIy76jFCXsiJS5yC15j8vgvDgE/J/qyDGGlVfUvNzm1LytRuegfiqMlVg == X-ME-Sender: Received: from aither.local (unknown [76.25.3.152]) by mail.messagingengine.com (Postfix) with ESMTPA id EB8F410281; Thu, 12 Apr 2018 23:02:09 -0400 (EDT) To: =?UTF-8?Q?J=c3=b6rg_Walther?= , "urn@ietf.org" References: <8E4ECACBF388FC48B761D111DDCD969BD2ECD873@GPS-SRV02E.smmt.co.uk> <8E4ECACBF388FC48B761D111DDCD969BD2ECEE76@GPS-SRV02E.smmt.co.uk> From: Peter Saint-Andre Openpgp: preference=signencrypt Autocrypt: addr=stpeter@stpeter.im; prefer-encrypt=mutual; keydata= xsFNBFETDzsBEAC0FOv1N3ZJzIIxN6cKD475KVS9CHDPeYpegcOIPnL5eY1DCHeh/IwS1S7R CePtmiybNoV9FsI4PKUknzXQxA6LVEdAR/LUlhgJKjq+gsgp8lqbEILhg13ecH66HwLS9rar bQkC47T7kL8miIPBFC6E3A4Lq1L+eueO6UcLhKgoYkMxOjdiWrMgKTnVpch5ydLkPm/z0Zo8 zRgqlPuTLeCrXXZYnjHXLVFN2xy04UzOs7P5u5KVfx5Z7uQisr8pXtyLd6SpTZo6SHgKBv15 uz0rqXhsJojiGtOXfWznAjaS5FUOORq9CklG5cMOUAT8TNftv0ktsxaWDL1ELDVQPy1m7mtz o+VREG+0xmU6AjMo/GHblW1UU7MI9yCiuMLsp/HLrFuiosqLVZ85wuLQ2junPe3tK8h15Ucx IXAcpQ1VqIaDQFbeuLOXJTF8YHpHdpHYt/ZM1ll7ZBKGAo8yd7uF7wJ9D3gUazwdz9fFjWV7 oIk7ATwOlFllzmWDn+M2ygbHOGUGMX5hSaa8eDSieiR2QoLdn27Fip7kMBTJ2+GISrfnJTN/ OQvmj0DXXAdxHmu2C4QgmZbkge35n129yzXn9NcqzrGLroV62lL3LgX6cSbiH5i7GgWY6CAP b1pMogV0K475n9FvOSDRiG4QSO5yqKiA3OP5aKrIRp2TNAk4IwARAQABzSZQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBzdHBldGVyLmltPsLBeQQTAQIAIwUCURMPOwIbAwcLCQgHAwIB BhUIAgkKCwQWAgMBAh4BAheAAAoJEOoGpJErxa2p6bgQAKpxu07cMDOLc4+EG8H19NWXIVVy bOEvfGuHYZaLKkPrhrMZwJiOwBpyISNRt9qzX1eLCVaojaoEVX6kD8MGc5zKFfiJZy3j7lBW l+Ybr7FfXYy2BbAXKx49e1n6ci9LmBrmVfAEaxtDNPITZ9N9oUAb9vS0nrG036EwteEHAveQ vlDjO7lhz6+Cv7lZQgBj9rZ6khfcQ4S3nSCQaKLQ9Iav4fqxI7SfuPKnx6quHX3JNLGnVo3w l+j/foCK0iTrmtHxCI3kc/bx6g32pRjHEPX0ALMBhmzU2uca+TE0zCEC96mgYXAUCwdnCFWy beIEbt6pz65iML13kAVAq0H/GqncnMGN0MbOatnw1Tdz/vkLojIy7QbPcQ0plUFxv5491xPf IrHhOWdRXp6WUt88fcqhT6MHZpVRtusj2ornKVVn+Y0GLsMMCTcrXJRG7Ao1YV72t/pJpzfG WSaaxolxDIZ6B+76jrIhUhiWgo/4nf+DN6BIlCZQ6j6xxjjx462cu02kuhIILTk2pzaMOufT BWx0uJhZk/KP2Fay/41pX7pvVOwRC4uIlKsLnJKLPS7EDa4BUUxENfd/9LqOGwlII8BbSe98 PLMI8sXkcigc3UXMVda9ll0YhQa+lbP1NaszmnBhwuiCsgnPGbImsJuRzgEEgckwP/dNeyr6 MlFMyfaezsFNBFETDzsBEADBzOsEHpUmhkRUjH9Tek87dn5P/Yh/L/HptgCGk40TL/C+kYdk d3HyteMEf061PNmsS/Rq8k37Fu3VODYb9SPYKxtgksKSYUtIkPKvao09K9QNWPqyWuNf0F+i AjVMUudaEVFJ7bHF310RDwLY5IvLeCXxtvG+Vv/i+g77d2WdPDp+zLJ8306C4yBKjSJV8xW0 cn2fd7NviIEN6cNHTsZNDZVMlgYPrxnwSq8GTEPGC7HsLIwGcx3hIe9QjnPw9CpAmQENpDEy WcxgF5uwo2NJECoDswKz1Nb0gfawF3ZIbD+GcLujTu94iJuVg25jATWm9wTgcfZo4UPllRGX dIb8uWwUFQlLQgd4ROLZZtXNGmHIymJrV2crx53gxup+1j0XqhlzKg8xbImWhEfS9oHZkRK8 VHgmWSIt7TNwNir6N5j3lqwWVBhnu6GzF01sKGNySlqNRbd0fqhakCkK71b8ot8tYTcYG5Lg 10z6HTbgQx2UwLthUjqbblDQ+GLmrOhiWklLXRsnlnPMwnEyFePAnsT5tasy2Cn9qjpttNDa h7PB8iFUi9mtTF/XDVgpFaB5G3CDV7Q2NgbAI6g6QhLIAmXzSP635G83mda0TKXHQXHDyLJT Tn+WVFU7t4m4uLt+0DsWU8jXHQWyUTNG9WPUrXhusDUAPHxFCQ/n/lQVBwARAQABwsFfBBgB AgAJBQJREw87AhsMAAoJEOoGpJErxa2pqfgP/ApN+TRu2bBIgaw1dr3AznSSha84DIpXUDh3 udZvQrGbUtz8/mA+e3iZEN/cmmBw2LGlAuQoJNILTZQ318yTP+E5QU7fJH7FVsohUyvrMfyt 3IMA9jg0Z9MuloLezvIjjMfFeNa0ROgDb/ubOT7JQzi1kwN8Lu3lO80HwqBHXEeOLoislUSn ZajRKvITbKWkZ6PHRjlMw1Wk4oIi6VLHgGgj79zzL3uhML2663m7imShvz1QcHTwvyR5i8cZ bNOEkotZyERiA1p7YHuruS+QvTi3ZPoQbnMUB3a7py9d11bw1+w3LiAUGZE/z5hBWOFxYtw+ w/U/Vx0BwJGYlwU3M2W20uEXe+qxz7wnakygKjmLiD2z4njfKjcNCiV3FmXrpmWgADln1c4j fxDh0NrndrsM8FPDf1TMPtOZgFDkKripc9xkZ/25P6xn27oTOHWKcAC0QhxSH+HuVBBRk8Ag F+zAbDZe4/L6+kanSrycIXW+wCzwBq61aWsz2QhhuKjozVkhk4dRG+CfjzAFjnyxwYERn3uX VKQAwTwcdNcTI9RV98IsNrw9Y4lJEAg6CjNPmiD5+EASycqaOuToRSGukr8sOQLWLPyTnez/ aG8Xf7a+fntWzK2HuDYoSDhJJrylWw/lMklOBm4wtMeNA0zcQH6AQV/GzQVQkSGqrLuMVIV/ Message-ID: <4249d300-077a-fd18-d9df-b3c9a6a9c20c@stpeter.im> Date: Thu, 12 Apr 2018 21:02:09 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <8E4ECACBF388FC48B761D111DDCD969BD2ECEE76@GPS-SRV02E.smmt.co.uk> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [urn] urn-registration-template-jaif-v2.txt X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 03:02:12 -0000 On 12/10/17 11:51 PM, Jörg Walther wrote: > Dear all, Hi Jörg, Thanks for your patience. I just realized that no one from the review team has commented on your document (which you sent to the list just as I was starting a new job). > please find attached the request to register the urn:jaif for the Joint Automotive Industry Forum. Your updated registration request looks good to me, and addresses the feedback I provided last June. > I kindly ask for conducting the registration process. I will ping the other members of the review team to see if they have any comments. Peter From nobody Thu Apr 12 20:08:21 2018 Return-Path: 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 3DFF21243F6 for ; Thu, 12 Apr 2018 20:08:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.685 X-Spam-Level: X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no 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 yLlCQiMqa-eS for ; Thu, 12 Apr 2018 20:08:19 -0700 (PDT) Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCE0D120227 for ; Thu, 12 Apr 2018 20:08:18 -0700 (PDT) Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-04v.sys.comcast.net with ESMTP id 6p4Dfclt2KNik6p4TfNe9w; Fri, 13 Apr 2018 03:08:17 +0000 Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-14v.sys.comcast.net with SMTP id 6p4QfQ4pLLr2I6p4Rf45GR; Fri, 13 Apr 2018 03:08:16 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w3D38DnP017848; Thu, 12 Apr 2018 23:08:13 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w3D38CWR017837; Thu, 12 Apr 2018 23:08:12 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: R Atarius Cc: ben@nostrum.com, georg.mayer.huawei@gmx.com, jbakker@blackberry.com, l.svensson@dnb.de, urn@ietf.org In-Reply-To: <1152249163.1658635.1523577151047@mail.yahoo.com> (r_atarius@yahoo.com) Sender: worley@ariadne.com (Dale R. Worley) Date: Thu, 12 Apr 2018 23:08:11 -0400 Message-ID: <87h8ofiz1g.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfMreq+DaKVt3NNIW08JWuHkfhhyzQomvl4RvyMV2rb710EJQV+FwV7DTuRZGZOZ4igaQoqXO9aJ8a1kB1sApqd4IcWqivI3ySmpjMbK3Iagx0laYzf9m pIFZqvI10RlF0jSFMxAv7r8hCcLknFeGjALjAhosVfrpp0gqtFivsSq4vjDrtkSqsiA4ZXXg+ST2tJcSpGb62OlNhXtV+cCeZPJGx+RzZvvHx2EJwIh2RQhG RRLIFGxqKqPP+3RCe+5kUxeirhYA9eeFhtbxKpm68o3x5WPFXfOTIoadiIduby5qIVvJv+Gk7xQ9acREz+v77w== Archived-At: Subject: Re: [urn] draft-atarius-dispatch-meid-urn-17 X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 03:08:20 -0000 R Atarius writes: > Hello all, > new revision has been uploaded. > https://www.ietf.org/id/draft-atarius-dispatch-meid-urn-17.txt Interestingly, the only item where Roozbeh did not follow my suggestion, the description of the check digit, is thoroughly explained in the Wikipedia article: https://en.wikipedia.org/wiki/Mobile_equipment_identifier The article also discusses the relationship of MEIDs to ESNs and IMEIs. Given that the check digit is not present in the URN and is reasonably well documented in the public literature, I agree that there is no need to give the somewhat elaborate details of the check digit system in the RFC. Dale From nobody Thu Apr 12 20:37:06 2018 Return-Path: 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 E7A411241F8 for ; Thu, 12 Apr 2018 20:37:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.999 X-Spam-Level: X-Spam-Status: No, score=-0.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, FREEMAIL_REPLYTO=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 cGUB_1DxckYf for ; Thu, 12 Apr 2018 20:37:03 -0700 (PDT) Received: from sonic310-28.consmr.mail.gq1.yahoo.com (sonic310-28.consmr.mail.gq1.yahoo.com [98.137.69.154]) (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 2A3361205D3 for ; Thu, 12 Apr 2018 20:37:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1523590622; bh=xPVGjDtdkPfbNkiu/JrulQaFkCoRAu+qH1BqXmlKm94=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=GcBjv+Sko07wd32BAoRb6K0llF3ZRa4JDth1Bl+DAaq4vSUga02k7N9KRh/dTxevYetZ+82/7kOOtwNjJGTBODoJobL5Di/a30mB+/cNIZC7YIptByArhIYwv4XAo/a+Oh/nmnppErgU6eenLi+x/psTD2dX1SC8C3z+1cyQkqM3hN4/7zWeScatCSO63y3AEroTmzkuno7SqnXqbywoqUmF6KjwiY847S5xaK4fFZV8wYACo2IFsK5OhUvtFD/yNCCeidC36dfKBJxK9IGajotzUOeMSWB+h2JbsT2aQbDoHq/Izc4zeqMHMBFsvb4TqeHoh3gr2BjY1t7qrlG+kw== X-YMail-OSG: BvYBhOEVM1mfKH28bvDBiV6G5bsBVhdUPAJ4_dqWUjtXbfqeFvQtM.vanxJwsOo ln7B1rbC2e8xjmHkCs08iav9NG8nn39c60hpi7xaNTAD8M.WVF9fz4C42nPevQtTSI.YHx7u7rzf 5st.Y3i_L5hBNrZln7CFv8CBpLBKcdWkYr5vZwJHFXM2xy5duvhjdHsGRFueHuxNxfAGz9SgswBR P4y6uGzab4sCXmtPb.Z88Gwnpl1lWUOEe6qRY98s73.Gl_MJGh7TjWhHJwgzLUephUDosVF7gGWu ic1.ZqjFGyxN78Wqv5ugbtupduuxj4oUMZgGWyl6Zbn_c23Xf_YmpIXCFX.bM.o0U9D_gWDljUgr N42e7Oxuxx.1JJL4QVwb063iCrdgOFtMhkdi8k99Gakoj7ipRfHESKtU8HVFGn6Ek1EMUvjDSYrF 2wtC1MyC.mE5u4WERl_9uaawt3tsXhKFfdWovmgnAih.xP5k0rIYPIM0KQGfw9nruQo8ylKS7TQ- - Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Fri, 13 Apr 2018 03:37:02 +0000 Date: Fri, 13 Apr 2018 03:36:57 +0000 (UTC) From: R Atarius Reply-To: R Atarius To: "Dale R. Worley" Cc: "ben@nostrum.com" , "georg.mayer.huawei@gmx.com" , "jbakker@blackberry.com" , "l.svensson@dnb.de" , "urn@ietf.org" , R A Message-ID: <567683303.1698864.1523590617180@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1698863_1643945374.1523590617178" References: <567683303.1698864.1523590617180.ref@mail.yahoo.com> 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: Subject: Re: [urn] draft-atarius-dispatch-meid-urn-17 X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 03:37:05 -0000 ------=_Part_1698863_1643945374.1523590617178 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Dale, I am a bit lost with your claim. Anyways, as I asked you before I can ask y= ou again if I can leave as it is since it may be good for the reader to hav= e that information in the document. Since I have yet not read the link you = sent so I am not sure what the Wikipedia has listed and if it is better tha= n the text I have in the draft. However, if you agree that it is beneficial= for the reader to have this in the document but you think that text needs = to be massaged to be better, please let me know. ThanksRoozbeh =C2=A0 From: Dale R. Worley To: R Atarius =20 Cc: ben@nostrum.com; georg.mayer.huawei@gmx.com; jbakker@blackberry.com; l.= svensson@dnb.de; urn@ietf.org Sent: Thursday, April 12, 2018 8:08 PM Subject: Re: draft-atarius-dispatch-meid-urn-17 =20 R Atarius writes: > Hello all, > new revision has been uploaded. > https://www.ietf.org/id/draft-atarius-dispatch-meid-urn-17.txt Interestingly, the only item where Roozbeh did not follow my suggestion, the description of the check digit, is thoroughly explained in the Wikipedia article: https://en.wikipedia.org/wiki/Mobile_equipment_identifier The article also discusses the relationship of MEIDs to ESNs and IMEIs. Given that the check digit is not present in the URN and is reasonably well documented in the public literature, I agree that there is no need to give the somewhat elaborate details of the check digit system in the RFC. Dale =20 ------=_Part_1698863_1643945374.1523590617178 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Dale,

I am a bit lost with your = claim. Anyways, as I asked you before I can ask you again if I can leave as= it is since it may be good for the reader to have that information in the = document. Since I have yet not read the link you sent so I am not sure what= the Wikipedia has listed and if it is better than the text I have in the d= raft. However, if you agree that it is beneficial for the reader to have th= is in the document but you think that text needs to be massaged to be bette= r, please let me know.

Thanks
Roozbeh


 


=
From: Dale R. Worley <worley@ariadne.com><= br clear=3D"none"> To: R At= arius <r_atarius@yahoo.com>
Cc: ben@nostrum.com; georg.mayer.huawei@gmx.com; = jbakker@blackberry.com; l.svensson@dnb.de; urn@ietf.org
= Sent: Thursday, April 12, 2= 018 8:08 PM
Subject= : Re: draft-atarius-dispatch-meid-urn-17

R Atarius <r_atarius@yahoo.com> writes:

> = Hello all,
> new revision has been uploaded.
> https://ww= w.ietf.org/id/draft-atarius-dispatch-meid-urn-17.txt


Interestingly, the only item where Roozbeh did not= follow my suggestion,
the description of the check digit= , is thoroughly explained in the
Wikipedia article:
https://en.wikipe= dia.org/wiki/Mobile_equipment_identifier
The article = also discusses the relationship of MEIDs to ESNs and IMEIs.

Given that the check digit is not present in the URN = and is reasonably
well documented in the public literatur= e, I agree that there is no need
to give the somewhat ela= borate details of the check digit system in the
RFC.

Dale



------=_Part_1698863_1643945374.1523590617178-- From nobody Fri Apr 13 06:35:27 2018 Return-Path: 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 99D90120721 for ; Fri, 13 Apr 2018 06:35:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no 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 5OaAzJJhIDD4 for ; Fri, 13 Apr 2018 06:35:23 -0700 (PDT) Received: from mail.dnb.de (mail.dnb.de [193.175.100.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B87001200F1 for ; Fri, 13 Apr 2018 06:35:22 -0700 (PDT) Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by mail.dnb.de (Postfix) with ESMTP id 1BA624EDEDA9; Fri, 13 Apr 2018 15:35:20 +0200 (CEST) X-AuditID: 0a453fe7-d3dff70000000f94-b9-5ad0b21708f0 Received: from dnbf-ex.AD.DDB.DE (dnbf-ex.AD.DDB.DE [10.69.63.244]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id 01.03.03988.712B0DA5; Fri, 13 Apr 2018 15:35:19 +0200 (CEST) Received: from dnbf-ex.AD.DDB.DE (10.69.63.244) by dnbf-ex.AD.DDB.DE (10.69.63.244) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.669.32; Fri, 13 Apr 2018 15:35:18 +0200 Received: from dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7]) by dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7%4]) with mapi id 15.01.0669.032; Fri, 13 Apr 2018 15:35:18 +0200 From: "Svensson, Lars" To: R Atarius CC: "urn@ietf.org" , "georg.mayer.huawei@gmx.com" , "ben@nostrum.com" , "jbakker@blackberry.com" , "Dale R. Worley (worley@ariadne.com)" Thread-Topic: << PLEASE IGNORE THE PREV. MAIL>> [urn] Expert review needed Thread-Index: AQHT0dluCZ10H8YVO0ektNwRNnBvdKP9ds3ggAAWt4CAAScF0A== Date: Fri, 13 Apr 2018 13:35:17 +0000 Message-ID: References: <698733931.1704912.1521336419037@mail.yahoo.com> <87605gsykv.fsf@hobgoblin.ariadne.com> <1897592677.2154655.1522971507196@mail.yahoo.com> <467098619.2168581.1522971736851@mail.yahoo.com> <492366533.1285812.1523480980508@mail.yahoo.com> <312034622.1622289.1523570301763@mail.yahoo.com> In-Reply-To: <312034622.1622289.1523570301763@mail.yahoo.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.69.149] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPIcWRmVeSWpSXmKPExsXC5Wr/RVd804Uog/4ZphbzO0+zW7xawmXR sOIEo0XPBUuLqc0fmCxenihzYPOYvP8rs8eshrXsHnfvL2TyWLLkJ5PHrJ1PWDxmzTrMFMAW xWWTkpqTWZZapG+XwJVx7pNMwQexioP3TzA2MC4R62Lk4JAQMJFovuvQxcjFISRwiFHiy5JJ bBDOY0aJx5snsEM4WxglXtw6xdLFyM7BJqAl8T6ji5GTQ0RAWaL/+H4mEJtZ4BujxJn1oiC2 sICnxLkLZ5lA5osIeEm8uq4EUe4k8e/bC7ByFgFViZ+PlrCAlPAKmEocfpoAEhYS6GKWWHFF HcTmFLCVmPu2gxHEZhSQldiw4TwzxCZxiU3PvrOC2BICAhJL9kDEJQREJV4+/gcVV5TY9fMT O8h4ZgFNifW79CFaFSWmdD9kB7F5BQQlTs58wjKBUWwWkqmzEDpmIemYhaRjASPLKka+4tx0 Q73EFL2UlCS9lNRNjJB4e76Dse+SyyFGAQ5GJR7eP3Xno4RYE8uKK3MPMfpzMCmJ8m6MAQrx JeWnVGYkFmfEF5XmpBYrifD2tl+IEuKFCyeV5mQryfE2zj8bJSQOFy0uLS7ITM7MLy2OLy3K AUYWBzNQ67/5IK0piZVVqUX5EAMPMUpzsCiJ877cxxAhJJCeWJKanZpakFoEk43g4FCS4I3b CNQoWJSanlqRlplTApMG6suaBpQRQJYBO0iRd6cDUEIKWQLdTUwcnIcYfTh4gA5LApnPW1yQ mFucmQ41W5h3+XKgKA9MFGyuLG/hAqBHxWCCqGaeYkzleNPW08PM8eTytB5mIZa8/LxUKXHe KJDxAiA9GaV5cNdLifHOBBnGjyQBskRKgTfx07koIUkkcVR7XjF6AiNNmPfBBpADgfkR4Woh 3ifrgYLcUEGwo2V4S0D2iELF0M3yAca2CO8Pe3AQlCSWIAcBB0gjD0wUGgQskCCACqIaJ9XA yCfnKjD9WO8T3aitwTf29nh933zQurx57i7l+HfPAmcdi/Jz549i/pYkcjqDJ+baa7v6tz7z WlUl9jDPD1g4o73WjWuVeAqvWr/nzx0/OU6su1zG41+txn2NV3H95vz3kYZ7+1m1TzpLqV5U +6611Kky4q2CaQ/7n+RX79+5SDx0TP2wZzeLEktxRqKhFnNRcSIAYQOHoLIEAAA= Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 13:35:26 -0000 T24gVGh1cnNkYXksIEFwcmlsIDEyLCAyMDE4IDExOjU4IFBNLCBSIEF0YXJpdXMgW21haWx0bzpy X2F0YXJpdXNAeWFob28uY29tXSB3cm90ZToNCg0KDQpbLi4uXQ0KPiA+IFtSb296YmVoXSBJIGJl bGlldmUgdGhhdCdzIGhvdyBJIHN0YXJ0ZWQgYnV0IEkgcmVjZWl2ZWQgY29tbWVudHMgYWJvdXQg aXRzDQo+IGZ1bmN0aW9uYWxpdHkNCj4gPiBhbmQgdGhhdCdzIHdoeSBJIGFkZGVkIHRoYXQgc2Vu dGVuY2UuIEkgYW0gZ29vZCBlaXRoZXIgd2F5LiBJZiB0aGF0IG1ha2VzIHlvdSwNCj4gRGFsZQ0K PiA+IGFuZCBJRVRGIGNvbW11bml0eSBzYXRpc2ZpZWQgdGhlbiBJIGNhbiByZW1vdmUgdGhhdCBz ZW50ZW5jZS4gUGxlYXNlIGxldCBtZSBrbm93Lg0KPiANCj4gT0ssIHNvIHlvdSdyZSBkYW1uZWQg aWYgeW91IGRvIGFuZCBkYW1uZWQgaWYgeW91IGRvbid0Li4uIEknbSBmaW5lIGVpdGhlciB3YXks IHRvbywgc28NCj4gaWYgbm90IERhbGUgb3IgYW55b25lIGVsc2Ugb2JqZWN0cywgeW91IGNhbiBs ZWF2ZSB0aGUgc2VudGVuY2UgYXMgaXQgaXMuDQo+IA0KPiBbUm9vemJlaF0gSSBsZWF2ZSB0aGVu IGFzIGl0IGlzLg0KDQpPSy4NCg0KPiA+IExvb2tpbmcgbW9yZSBjbG9zZWx5IGF0IHNlY3Rpb24g NC4yLCBpdCBmZWVscyBhIGJpdCBhd2t3YXJkIHRoYXQgeW91IGZpcnN0IGRlZmluZSB0aGUNCj4g PiBwYXJ0cyBvZiB0aGUgTUVJRCBmb3JtYXQgYW5kIHRoZW4gZ28gb24gdG8gcHV0IHRoZW0gdG9n ZXRoZXIuIFlvdSBtaWdodCB3YW50IHRvDQo+ID4gY29uc2lkZXIgcmVwaHJhc2luZyBhcyBmb2xs b3dzOg0KPiA+DQo+ID4gNC4yIE1FSUQgRm9ybWF0DQo+ID4gVGhlIE1FSUQgZm9ybWF0IGlzIDE1 IGhleGFkZWNpbWFsIGRpZ2l0cyBlbmNvZGVkIGluIDggb2N0ZXRzIGFzIGRlZmluZWQgaW4NCj4g W1MuUjAwNDgtDQo+ID4gQV0uIFRoZSBmaXJzdCBlaWdodCBoZXhhZGVjaW1hbCBkaWdpdHMgY29u c3RpdHV0ZSB0aGUgbWFudWZhY3R1cmVyIGNvZGUsIHRoZSBuZXh0IHNpeA0KPiA+IGhleGFkZWNp bWFsIGRpZ2l0cyB0aGUgc2VyaWFsIG51bWJlciB3aXRoaW4gdGhlIG1hbnVmYWN0dXJlciBjb2Rl LiBUaGUgbGFzdA0KPiA+IGhleGFkZWNpbWFsIGRpZ2l0IGlzIGEgY2hlY2sgZGlnaXQuIEZvciBt b3JlIGRldGFpbHMgb24gdGhlIGhleGFkZWNpbWFsIGVuY29kaW5nIGNmLg0KPiA+IDQuMi40Lg0K PiA+IDQuMi40IEhleGFkZWNpbWFsIEVuY29kaW5nDQo+ID4gVGhlIGZvbGxvd2luZyBmaWd1cmUg Li4uIFtYLlMwMDA4LUFdLg0KPiA+IFtSb296YmVoXSBJIHRoaW5rIHRoYXQgaXMgd2hhdCBpcyBj YWxsZWQgYSAiaGFuZ2luZyBzZWN0aW9uIiwgc2luY2UgdGhlcmUgc2hvdWxkIG5vdCBiZQ0KPiA+ IGFueSB0ZXh0IGJlbG93IDQuMiB3aGVuIHRoZXJlIGFyZSA0LjIuMSwgNC4yLjIsIGV0Yy4gSSBj YW4gY3JlYXRlIGEgbmV3IHN1YnNlY3Rpb24NCj4gYXMNCj4gPiAiNC4yLjEgT3ZlcnZpZXciwqAg d2l0aCB0aGUgdGV4dCB5b3UgcHJvcG9zZWQgYW5kIHNoaWZ0IG90aGVyIHN1YnNlY3Rpb24gd2l0 aCAwLjAuMS4NCj4gV2lsbA0KPiA+IHRoYXQgaGVscD8NCj4gDQo+IFRoYXQncyBtb3JlIGEgcXVl c3Rpb24gb2Ygc3R5bGUgdGhhbiBhIHRlY2huaWNhbCBxdWVzdGlvbi4uLiBJIGRvbid0IGtub3cg d2hhdCB0aGUgSUVURg0KPiBTdHlsZSBHdWlkZSAoVE0pIGhhcyB0byBzYXkgb24gdGhlIHRvcGlj IGJ1dCB0aGVyZSBhcmUgcXVpdGUgYSBmZXcgUkZDcyB0aGF0IGhhdmUgdGV4dA0KPiBhdCB0aGUg YmVnaW5uaW5nIG9mIGEgc2VjdGlvbiBhbmQgdGhlbiBjb250aW51ZSBpbiBzdWJzZWN0aW9ucy4g UkZDIDgxNDEgaXMgb25lDQo+IGV4YW1wbGUsIHdoZXJlIHNlY3Rpb24gMSBbMV0gaGFzIGEgZmFp cmx5IGxvbmcgdGV4dCBhbmQgdGhlbiBjb250aW51ZXMgdG8gc3BlY2lmeSB0aGluZ3MNCj4gaW4g MS4xLCAxLjIgZXRjLg0KPiANCj4gSSdtIGZpbmUgZWl0aGVyIHdheS4NCj4gDQo+IFsxXSBodHRw czovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjODE0MSNzZWN0aW9uLTENCj4gDQo+IFtSb296YmVo XSBJIGNyZWF0ZWQgYW4gb3ZlcnZpZXcgc2VjdGlvbiBhbmQgYWRkZWQgeW91ciBjb21tZW50Lg0K DQpPSy4gDQoNClRoYW5rcywNCg0KTGFycw0KDQo= From nobody Sun Apr 22 19:33:06 2018 Return-Path: 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 16FAF126DCA for ; Sun, 22 Apr 2018 19:33:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.685 X-Spam-Level: X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no 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 kgFTiMVTQ1FY for ; Sun, 22 Apr 2018 19:33:04 -0700 (PDT) Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8117124B0A for ; Sun, 22 Apr 2018 19:33:03 -0700 (PDT) Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id ARHrfMR8A6RoKARHrfVQt5; Mon, 23 Apr 2018 02:33:03 +0000 Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-17v.sys.comcast.net with SMTP id ARHnfw5WPoKh6ARHpfMEtn; Mon, 23 Apr 2018 02:33:02 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w3N2Ww3i030129; Sun, 22 Apr 2018 22:32:59 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w3N2WvPk030126; Sun, 22 Apr 2018 22:32:57 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: R Atarius Cc: ben@nostrum.com, georg.mayer.huawei@gmx.com, jbakker@blackberry.com, l.svensson@dnb.de, urn@ietf.org, r_atarius@yahoo.com In-Reply-To: <567683303.1698864.1523590617180@mail.yahoo.com> (r_atarius@yahoo.com) Sender: worley@ariadne.com (Dale R. Worley) Date: Sun, 22 Apr 2018 22:32:57 -0400 Message-ID: <87wowybqjq.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfATD8XjH7+76uaTwys6YsDJTzawPvZPu3FQlDBmWfUjNztvSXGmJjqGuaRxxOf8n+fGYwKPqMRg2sNjmiQpjLm2l/LJ7vxzH9EbXEfqgZtmgJPhs+7Tv l2ZGpc3I0J6aU3iuNJkz9eFxQK8ELzA4n1RNRg8pQESLnBBOuz7MOsJAWCETWebLQw5HuRggBKqeigdNpTB1sOMgA4UxMERJ87EnIwQ0mNp4GLAaF4UA1w5j 4Hj+SiTMvw9JYu3u1LlqKiZAhCvup8y/PdCGW04FIXPNQUlOKYcsNumSeM/bocW31zEyGeMdMtr9l628PNxtPw== Archived-At: Subject: Re: [urn] draft-atarius-dispatch-meid-urn-17 X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2018 02:33:05 -0000 R Atarius writes: > I am a bit lost with your claim. Anyways, as I asked you before I can > ask you again if I can leave as it is since it may be good for the > reader to have that information in the document. Since I have yet not > read the link you sent so I am not sure what the Wikipedia has listed > and if it is better than the text I have in the draft. However, if you > agree that it is beneficial for the reader to have this in the > document but you think that text needs to be massaged to be better, > please let me know. Well, I said in the message that you quote, "I agree that there is no need to give the somewhat elaborate details of the check digit system in the RFC." So: I think there is no need to give the details of the check digit system in the RFC. Dale From nobody Mon Apr 23 03:13:57 2018 Return-Path: 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 E6B38120454 for ; Mon, 23 Apr 2018 03:13:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no 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 eR_u503kjXQu for ; Mon, 23 Apr 2018 03:13:52 -0700 (PDT) Received: from mail.dnb.de (prodfix-out0.dnb.de [193.175.100.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75DD81243F6 for ; Mon, 23 Apr 2018 03:13:51 -0700 (PDT) Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by mail.dnb.de (Postfix) with ESMTP id 0550C40AB7F8; Mon, 23 Apr 2018 12:13:50 +0200 (CEST) X-AuditID: 0a453fe7-d3dff70000000f94-ff-5addb1dd9c06 Received: from dnbf-ex.AD.DDB.DE (dnbf-ex.AD.DDB.DE [10.69.63.244]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id A1.D0.03988.DD1BDDA5; Mon, 23 Apr 2018 12:13:49 +0200 (CEST) Received: from dnbf-ex.AD.DDB.DE (10.69.63.244) by dnbf-ex.AD.DDB.DE (10.69.63.244) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.669.32; Mon, 23 Apr 2018 12:13:48 +0200 Received: from dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7]) by dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7%4]) with mapi id 15.01.0669.032; Mon, 23 Apr 2018 12:13:48 +0200 From: "Svensson, Lars" To: R Atarius , "urn@ietf.org" Thread-Topic: draft-atarius-dispatch-meid-urn-17 Thread-Index: AQHT0rmWLZlmUxw1oUGto2l9eb7pK6QOL/YA Date: Mon, 23 Apr 2018 10:13:48 +0000 Message-ID: <6a449a9a570f4389844e2374c285db7d@dnb.de> References: <1152249163.1658635.1523577151047.ref@mail.yahoo.com> <1152249163.1658635.1523577151047@mail.yahoo.com> In-Reply-To: <1152249163.1658635.1523577151047@mail.yahoo.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.69.180] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA12TfUhTURjGO3d323F68nh1eVxZeSMqMVehZRAWfZCFmQlhLMqu7eamc5N7 N9GgDwiijxGRFbmg+sPEPkCLysoo2Aq1EGNFmGUfZMYiMioqQ6x7dqfN/rm85/fe5znPfV8u 1HA/9CZod7pFySk4eJ2BNaxa+n1u35U+y7xTp8053seLc07s+8IsY/IaGoaYPJ8vwBQyFsMS q+iwV4uSOXebwfbn0xBTNayruf/6PLMX9OsOgRhIcBa5U39TfwgYIIf9gBx5flCrHt4B8jkQ ZNXDNUB6mtqVgx7qcDoZtFFxEl5OBgdbGVonYjN50TmiVfk8Ehq+p1PrBcTvPcbSmsUzycHb 9H0IEc4mzV8QxRz2kH3BR2FpDM4ljQ86AK0BTiUtLd0aWmtwMrk68FOrZsak4Y7KCTaS0LuR CE8jgZ4mPbXX4Dmk+bZZlaaR44ff6mmNcALprO9njwKjL8rV90/hi1L4ohTnAHsRTJQry+Zn CtZMq7U00ypeBeoiPtwER4Ir/QBDwMchb0afhdMK1XJtpR+shwxvRE92KWhiqctaaxNkW4nk cYgyn4SCzQpGY7jU46jgp6IBu0KTx6jskavs2+0uj1zikRzKhqBGkcoFVGoVaneKkks19IPJ kOWTUejuhE0cLhPcYoUoVonSaHcThDxB31sUYYIklok1O+wO92hb0c3Zr3RwdCccKA31p7y0 cKboxv+ZGBjjB/kwTgmWS/2RXCVUyvayiHciClIaN0rDvqmoolyBk0bheM+HoAJ+2u/1amDH 4HHl2f/kpFfDsU6XUzQlo1pqh6nS5nGOfYNpEnpjUqLGRzXoVabpKKOj18KlRPHxt30Ea5TV JSLjFRpT+c3+ZedQE91SbASGo09BMo1ujLD/vfKVnSehA3RqSHYL7uhBSOXhQURoZBCV6iAi cLydaS+I/1Vyq6uRf7yzK+7h7kvHtKH3L4qr22fp02MXzFjXtifXfHbz3Vmvi9oCM1ZP23Bj y+pga138Yv1AT5th7aOas6nF3qeFr+qG4u1b63Gva0Xi1xPLL/T+XJi/0FW06Ftedv6Z7qyc yxtnF+ueJ2iflk+eWfcr+DvQerqmoCkl1HH92dZFPCvbhPnpGkkW/gIQBnGBiQQAAA== Archived-At: Subject: Re: [urn] draft-atarius-dispatch-meid-urn-17 X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2018 10:13:56 -0000 SGkgUm9vemJlaCwNCg0KT24gRnJpZGF5LCBBcHJpbCAxMywgMjAxOCAxOjUzIEFNLCBSIEF0YXJp dXMgW21haWx0bzpyX2F0YXJpdXNAeWFob28uY29tXSB3cm90ZToNCg0KPiBuZXcgcmV2aXNpb24g aGFzIGJlZW4gdXBsb2FkZWQuDQo+IA0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1h dGFyaXVzLWRpc3BhdGNoLW1laWQtdXJuLTE3LnR4dA0KDQpUaGFua3MsIGFzIHByb21pc2VkIEkn dmUgbm93IHJlYWQgdGhlIGNvbXBsZXRlIEktRCBhZ2Fpbi4NCg0KVGluaWVzdCBuaXRzOg0KDQox KSBUaGUgZGVjbGFyYXRpb24gb2Ygc3ludGFjdGljIHN0cnVjdHVyZSB1c2VzICJwY2hhciIgYW5k ICJwY3QtZW5jb2RlZCIgd2l0aG91dCBkZWZpbmluZyB0aGVtIGFueXdoZXJlLiBZb3UgbWlnaHQg d2FudCB0byBhZGQgc29tZXRoaW5nIGFsb25nIHRoZSBsaW5lcyAiJ3BjaGFyJyBhbmQgJ3BjdC1l bmNvZGVkJyBhcmUgZGVmaW5lZCBpbiBSRkMgMzk4NiIuDQoNCjIpIEluIHRoZSByZWZlcmVuY2Vz IHNlY3Rpb24sIHRoZSBlbnRyeSBmb3IgU0MuUjQwMDItMCBoYXMgIlZlcnNpb24gMTAuMCIgaW4g dGhlIHRleHQgYnV0IHRoZSBVUkwgYW5kIHRoZSBsaW5rZWQgZG9jdW1lbnQgc2F5IFZlcnNpb24g MTIuMC4NCg0KQmVzdCwNCg0KTGFycw0K From nobody Mon Apr 23 03:23:36 2018 Return-Path: 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 4530F1243F6 for ; Mon, 23 Apr 2018 03:23:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no 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 Sbiv-A3GQeZV for ; Mon, 23 Apr 2018 03:23:34 -0700 (PDT) Received: from mail.dnb.de (mail.dnb.de [193.175.100.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D59A4120454 for ; Mon, 23 Apr 2018 03:23:33 -0700 (PDT) Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by mail.dnb.de (Postfix) with ESMTP id 30A8840AB7F8; Mon, 23 Apr 2018 12:23:32 +0200 (CEST) X-AuditID: 0a453fe7-d3dff70000000f94-31-5addb4236f81 Received: from dnbf-ex.AD.DDB.DE (dnbf-ex.AD.DDB.DE [10.69.63.244]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id 1A.D0.03988.324BDDA5; Mon, 23 Apr 2018 12:23:32 +0200 (CEST) Received: from dnbf-ex.AD.DDB.DE (10.69.63.244) by dnbf-ex.AD.DDB.DE (10.69.63.244) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.669.32; Mon, 23 Apr 2018 12:23:30 +0200 Received: from dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7]) by dnbf-ex.AD.DDB.DE ([fe80::3576:7565:4f15:49c7%4]) with mapi id 15.01.0669.032; Mon, 23 Apr 2018 12:23:30 +0200 From: "Svensson, Lars" To: =?Windows-1252?Q?J=F6rg_Walther?= CC: Peter Saint-Andre , "urn@ietf.org" Thread-Topic: [Marketing Mail] Re: [urn] urn-registration-template-jaif-v2.txt Thread-Index: AQHT0tPUunqFbd3r5Uu8aOeodDrE+KQOM//w Date: Mon, 23 Apr 2018 10:23:30 +0000 Message-ID: <4ef1b928a18d42d6a1274dcd5de08235@dnb.de> References: <8E4ECACBF388FC48B761D111DDCD969BD2ECD873@GPS-SRV02E.smmt.co.uk> <8E4ECACBF388FC48B761D111DDCD969BD2ECEE76@GPS-SRV02E.smmt.co.uk> <4249d300-077a-fd18-d9df-b3c9a6a9c20c@stpeter.im> In-Reply-To: <4249d300-077a-fd18-d9df-b3c9a6a9c20c@stpeter.im> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.69.180] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA12Ta2wMURTH3Z2pvV293E7b3Wu9B5HS1iMkTVA+IJVQxCO1HzC1093V7e5m ZrdaIupV2pT6QESDUkuKpK16S2mzTUQJZRvSSovY0gfBB+9HmdmZ1tS3M79z///zzzkZSDEF 0AwdLi8vuDgnO9hAGxbO+5Q44XK7ZVrwDEguf0qS79SWUMmHd33UzadS/f7vulR/fWVE6vHa Lmo5ZTHMsfJORw4vTE3ZYLD3vCuhPZX63Od/xuSD1xFFIBISPJN8a7irLwIGyOAAIO8bn+iU jxAgdR0ttPyKwZcBubVXUujhYDyZfLDLNBbPJp8uXAr7UHgxaar/Rcl1DF5Kep6GKOVNGjl6 8xWt1DPIjooyvVzTeCK59rtRJ9cIzyLnSq4CZVIDIGX584sAhJE4hbyomCdjgEeR6uomShll IjVvvqrxMfHXKpzgONId6lX5ONLQUqFX3k8jHx6Wqdop5Oypt5QyNpo0Hu2gDwJjqca2VCMp 1UhKNZKTgD4PhorZtulJnDXJas1IsvI1QDlP53VwILggADAEbBQqTmi3MBFcjpiXHQDLoI6N Q83bJDQ0w23Ns3Oifb3gc/IiG4uCVRJG/TjD58xiR6M3Doma+qnoEz2OjQ63T1zvE5zSuSAl ScU0WWrl8rbwglsxDIARkGZNqPv2oHQG2zgvn8XzHl7o66ZDyBK095IkjBZ4G5+b6XB6+9qS Lr5A6mBtJxxoHOoY3mZhzNrG/5l0MDIAlsAoKVjoohxM9HDZosOmesegYLVEo/po2HcUytok QWMfHOh5D/DwXUFxMQV7W+v2Uwztcrt4swkNkeNjWWP3ufrTm43opVkKOUzTkIeYx6KEu88s zHANHzinByyWjhaDftbIAaXf7l9qBlXI9xmiwnDokUiUQ8ep7H+vJdK1Y9E+eV9I9HJe7QqE TeEVqFRdQbayAhUOtDPng3Uj3Z/R1k5w4tCiz9HpO/MTl36ZG6G/H2x+6/3YFps74nZzUpen unx/+xHrr941B49N2syUt+wx3tqy+zFzpdBWmKLvvlF4OC3+d5vftPZHYkfT8fE5Va1Ttz+I +cOetS/c7eBv1nXXpOwbu81458CjVQ9DxtaVp1dsXZ0pdumvp3deYWnRzk2fTAki9xdutROj mQQAAA== Archived-At: Subject: Re: [urn] [Marketing Mail] Re: urn-registration-template-jaif-v2.txt X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2018 10:23:35 -0000 Hello J=F6rg, On Friday, April 13, 2018 5:02 AM, urn [mailto:urn-bounces@ietf.org] On Beh= alf Of Peter Saint-Andre wrote: > Hi J=F6rg, >=20 > Thanks for your patience. I just realized that no one from the review > team has commented on your document (which you sent to the list just as > I was starting a new job). >=20 > > please find attached the request to register the urn:jaif for the Joint= Automotive > Industry Forum. >=20 > Your updated registration request looks good to me, and addresses the > feedback I provided last June. >=20 > > I kindly ask for conducting the registration process. >=20 > I will ping the other members of the review team to see if they have any > comments. No technical comments from me, the registration seems OK.=20 One editorial nit: "There are no known interopreability issues" should probably be " There are= no known interoperability issues". Best, Lars=20 From nobody Mon Apr 23 19:07:08 2018 Return-Path: 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 853AB12E034 for ; Mon, 23 Apr 2018 19:07:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.685 X-Spam-Level: X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no 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 rxOqas3x2h2H for ; Mon, 23 Apr 2018 19:07:05 -0700 (PDT) Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7487E1205F0 for ; Mon, 23 Apr 2018 19:07:05 -0700 (PDT) Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-08v.sys.comcast.net with ESMTP id AnDDfhDqUWnVVAnMGfTht0; Tue, 24 Apr 2018 02:07:04 +0000 Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-14v.sys.comcast.net with ESMTPA id AnMEfzMKMZTy4AnMFfaiQf; Tue, 24 Apr 2018 02:07:04 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w3O272kw010100; Mon, 23 Apr 2018 22:07:02 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w3O271tI010087; Mon, 23 Apr 2018 22:07:01 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: jwalther@odette.org, urn@ietf.org In-Reply-To: <4249d300-077a-fd18-d9df-b3c9a6a9c20c@stpeter.im> Sender: worley@ariadne.com (Dale R. Worley) Date: Mon, 23 Apr 2018 22:07:00 -0400 Message-ID: <87a7ttbbnf.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfBvDmBoiq63EdxGgq+sP46ETvuGdhV5h7zUpcDbeCHBHINEkB7Apu9BNghfMBomqZe8ZZ7bXvyAFfEPtCiG5EHADUO/x+RmffM0mbBgNTBmA9RR/6+kv kYI9QQA9RCYIhZstCJ25Jh0RcBMAjca9cVwFfXEXktIG49rKnukZZUKZE3w3Lq4L4E6lOyAV7D0SB3D1j9VywrWjLL4hPWxQZsasJBDrGqhDBAhV8Ui230+6 kngKNabfXVn+BymPaFDaWPaI+dTVOrRVqNx/Hr3vONZ7JJh0UfDEck5+3KlnMzFn Archived-At: Subject: Re: [urn] urn-registration-template-jaif-v2.txt X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2018 02:07:06 -0000 I lost track of this submission as well. It's quite well-done and straightforward. My only comments are a couple of very minor editorial things. > The urn is not expected to become part of an IETF standard. I think you want to change "urn" to "URN namespace" here. > Syntax: > > The Namespace Specific String (NSS) of all URNs assigned by the > JAIF will have the following hierarchical structure: There are a couple of place where you say "the JAIF", whereas most are simply "JAIF". You probably want to make these consistent. Dale From nobody Mon Apr 23 19:38:28 2018 Return-Path: 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 3571112420B for ; Mon, 23 Apr 2018 19:38:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 2PcAGyCTtdWy for ; Mon, 23 Apr 2018 19:38:24 -0700 (PDT) Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A83341205F0 for ; Mon, 23 Apr 2018 19:38:24 -0700 (PDT) Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from ) id 1fAnqZ-000OcH-FO for urn@ietf.org; Mon, 23 Apr 2018 22:38:23 -0400 Date: Mon, 23 Apr 2018 22:38:18 -0400 From: John C Klensin To: urn@ietf.org Message-ID: <6008C02A5F4975EE5BF85578@PSB> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-SA-Exim-Connect-IP: 198.252.137.10 X-SA-Exim-Mail-From: klensin@jck.com X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false Archived-At: Subject: [urn] FWD: Last Call: (Using National Bibliography Numbers as Uniform Resource Names) to Informational RFC X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2018 02:38:26 -0000 Hi. Since this document started out as a WG work item (as draft-ietf-urnbis-rfc3188bis-nbn-urn) before the WG decided that, with the direction RFC 8141 (2141bis) was taking, the WG did not need to process it, I'm forwarding the Last Call announcement in case anyone wants to read the current version and comment who doesn't see the IETF announcement list. Comments to the IETF list or as noted below; comments posted to this list might easily be missed and ignored. john ---------- Forwarded Message ---------- Date: Monday, April 23, 2018 14:39 -0700 From: The IESG To: IETF-Announce Cc: alexey.melnikov@isode.com, draft-hakala-urn-nbn-rfc3188bis@ietf.org, stpeter@mozilla.com Subject: Last Call: (Using National Bibliography Numbers as Uniform Resource Names) to Informational RFC The IESG has received a request from an individual submitter to consider the following document: - 'Using National Bibliography Numbers as Uniform Resource Names' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2018-05-21. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract National Bibliography Numbers, NBNs, are used by the national libraries and other organizations in order to identify resources in their collections. Generally, NBNs are applied to resources that are not catered for by established (standard) identifier systems such as ISBN. A URN (Uniform Resource Names) namespace for NBNs was established in 2001 in RFC 3188. Since then, several European national libraries have implemented URN:NBN-based systems. This document replaces RFC 3188 and defines how NBNs can be supported within the updated URN framework. A revised namespace registration (version 4) compliant to RFC 8141 is included. The file can be obtained via https://datatracker.ietf.org/doc/draft-hakala-urn-nbn-rfc3188bis/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-hakala-urn-nbn-rfc3188bis /ballot/ No IPR declarations have been submitted directly on this I-D. ---------- End Forwarded Message ---------- From nobody Mon Apr 23 20:04:28 2018 Return-Path: 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 25E6F12E048 for ; Mon, 23 Apr 2018 20:04:28 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To" X-Spam-Flag: NO X-Spam-Score: -1.684 X-Spam-Level: X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no 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 gdNDrbOlo6Ey for ; Mon, 23 Apr 2018 20:04:26 -0700 (PDT) Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C56C612E040 for ; Mon, 23 Apr 2018 20:04:26 -0700 (PDT) Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id AmhofmhSnQ4H5AoFlfKSws; Tue, 24 Apr 2018 03:04:25 +0000 Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-10v.sys.comcast.net with ESMTPA id AoFkfI8Dv5dFNAoFkfmNhf; Tue, 24 Apr 2018 03:04:25 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w3O34Ntf013442; Mon, 23 Apr 2018 23:04:23 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w3O34NNS013439; Mon, 23 Apr 2018 23:04:23 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: "OTA\, Hiroshi" To: Cc: "TSB SG15 Secretariat\, ITU" In-Reply-To: (L.Svensson@dnb.de) Sender: worley@ariadne.com (Dale R. Worley) Date: Mon, 23 Apr 2018 23:04:23 -0400 Message-ID: <87r2n59ufc.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfGy548JIZIvl+S3S6FXCCc1XZJCjUg8E0XeYjxiYRbhz0LqhJyot5M+fkuGmbzbYPR/J6wCiTj5x/6DiS7FRXMbbBYE8/tsORHyWj5cNZK4yYWjQB0b2 0gBi1AV3EvOMctHp7brzH4mlLFm+Yrzdr+OQyf4pfgf+clZPRmGJZri//qzLv0lRwXd7ggjrlJTPaiEUQf3nHAZiIWII1y8zFpWBR2rkzMkuHCzaQigvLfHI 4qLzH56fVgeqllloot+FeTGdVSihod+bypdryP7ussMzp5O+xsb2IJnyqCo5me4s Archived-At: Subject: Re: [urn] URN review team coordination X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2018 03:04:28 -0000 >> 3. The status of the "ITU" registration request is unclear to me - I've >> seen nothing further since November: >> >> https://www.ietf.org/mail-archive/web/urn/current/msg03832.html My apologies for not reviewing this document before now. draft-itu-urn looks quite fine to me, with this one consideration: By default, two URNs within a namespace are "equivalent" only if they are exactly identical after the following transformations: (1) the initial "urn:itu" part is converted to lower-cse (2) in every %-encoding "%xx", the last two characters are converted to upper case if they are letters In this case, it means that the "ITU-Sector" component must be in lower case, and the following portion of the URN is case-sensitive (except within %-encodings). If you want more lenient rules for URN equivalence, they need to be spelled out in the registration template. Dale From nobody Tue Apr 24 19:36:10 2018 Return-Path: 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 B517412711E for ; Tue, 24 Apr 2018 19:36:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.685 X-Spam-Level: X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no 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 qD1DNveQVCxo for ; Tue, 24 Apr 2018 19:36:07 -0700 (PDT) Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 780C6120725 for ; Tue, 24 Apr 2018 19:36:07 -0700 (PDT) Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-02v.sys.comcast.net with ESMTP id B9wFfBQk6qwLXBAHufnC5o; Wed, 25 Apr 2018 02:36:06 +0000 Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-19v.sys.comcast.net with ESMTPA id BAHsfsGZu3rorBAHtfCdoz; Wed, 25 Apr 2018 02:36:05 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w3P2a4b4025717; Tue, 24 Apr 2018 22:36:04 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w3P2a3Bx025712; Tue, 24 Apr 2018 22:36:03 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: steve@advance-software.com, urn@ietf.org In-Reply-To: Sender: worley@ariadne.com (Dale R. Worley) Date: Tue, 24 Apr 2018 22:36:03 -0400 Message-ID: <87bme89fn0.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfJyGiKpK39sw58vBvBgnqNrYxXL1Tb3bBBXLtr6APJ6IZBupDjQf+NGhd3SFEyG579YDIe+yik+9gPU9YXnW9DyKaf1Wdb8wrNkS/k8nWZTl9lZPs+fE eZ3ib11bxtGZzo1YeGlv5dCzyZ2jK0Y50p4AQ5YbfWM/f/fo99vKNcHSUMiFp8xyAD/NfV8c360unYMdDzu7VospAGuNRA76vkbRcMWM9ROLki4+nQcAhrou kCgkakb6OfIHqhdxrhTehVezqLftu1GZcBx8VK2GQeY= Archived-At: Subject: Re: [urn] Request to register a URN (urn:xsg) for virtual reality 3D web use X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Apr 2018 02:36:09 -0000 One way to get a start on registering urn:xsg is to make a list of things ("resources") you'd like to give names to, paired with URNs which you think would be good names for them. This helps bring to the surface your implicit knowledge of what you want and need from urn:xsg:... . Send that list (along with the descriptions that will come to mind) to urn@ietf.org and we can discuss what would be good ways to get the results you want. (People on the mailing list have a lot of experience in adjusting the details of systems of URNs.) Once you've clarified the technical details of what you want, it will likely be much easier to write the URN registration request. Dale From nobody Fri Apr 27 02:14:28 2018 Return-Path: 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 4B6EF1267BB for ; Fri, 27 Apr 2018 02:14:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.902 X-Spam-Level: X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 kUI19q5RZIKU for ; Fri, 27 Apr 2018 02:14:23 -0700 (PDT) Received: from itu1out.svc.unicc.org (itu1out.svc.unicc.org [192.91.247.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E58C120454 for ; Fri, 27 Apr 2018 02:14:22 -0700 (PDT) Received: from TUCM04.TUECSP.UNICC.ORG (unknown [10.81.38.71]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by iccpfxor01.svc.unicc.org (Postfix) with ESMTPS id BCC193FF19; Fri, 27 Apr 2018 09:14:20 +0000 (UTC) Received: from TUCM04.TUECSP.UNICC.ORG (10.81.38.71) by TUCM04.TUECSP.UNICC.ORG (10.81.38.71) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 27 Apr 2018 09:14:20 +0000 Received: from TUCM04.TUECSP.UNICC.ORG ([10.81.38.71]) by TUCM04.TUECSP.UNICC.ORG ([10.81.38.71]) with mapi id 15.00.1293.002; Fri, 27 Apr 2018 09:14:20 +0000 From: "OTA, Hiroshi" To: "Dale R. Worley" , "urn@ietf.org" CC: "TSB SG15 Secretariat, ITU" , Scott Mansfield Thread-Topic: URN review team coordination Thread-Index: AQHT23j1IhHQBKo44kKGqkG1jsio96QUVC3g Date: Fri, 27 Apr 2018 09:14:20 +0000 Message-ID: References: (L.Svensson@dnb.de) <87r2n59ufc.fsf@hobgoblin.ariadne.com> In-Reply-To: <87r2n59ufc.fsf@hobgoblin.ariadne.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.81.64.102] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [urn] URN review team coordination X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2018 09:14:26 -0000 Hi Dale, Thank you for your feedback. It is well noted. Currently, we are seeking an endorsement from the General Secretariat of IT= U as suggested by John in his e-mail at https://www.ietf.org/mail-archive/w= eb/urn/current/msg03832.html . Sorry for not responding earlier. It is ta= king much longer than expected. As soon as we have got the endorsement, we= will submit our request according to the "Fast Track" as in 6.3 of RFC8141= . Regards, Hiroshi --- Hiroshi OTA, Advisor, ITU-T SG15 International Telecommunication Union Place des Nations CH-1211 Geneva 20 Switzerland Tel: +41 22 730 6356 Fax: +41 22 730 5853 E-mail: hiroshi.ota@itu.int -----Original Message----- From: Dale R. Worley =20 Sent: Tuesday, April 24, 2018 05:04 To: OTA, Hiroshi ; urn@ietf.org Cc: TSB SG15 Secretariat, ITU Subject: Re: URN review team coordination >> 3. The status of the "ITU" registration request is unclear to me -=20 >> I've seen nothing further since November: >>=20 >> https://www.ietf.org/mail-archive/web/urn/current/msg03832.html My apologies for not reviewing this document before now. draft-itu-urn looks quite fine to me, with this one consideration: By defa= ult, two URNs within a namespace are "equivalent" only if they are exactly = identical after the following transformations: (1) the initial "urn:itu" part is converted to lower-cse (2) in every %-encoding "%xx", the last two characters are converted to upp= er case if they are letters In this case, it means that the "ITU-Sector" component must be in lower cas= e, and the following portion of the URN is case-sensitive (except within %-= encodings). If you want more lenient rules for URN equivalence, they need to be spelled= out in the registration template. Dale From nobody Mon Apr 30 19:25:00 2018 Return-Path: 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 7A30912DA21 for ; Mon, 30 Apr 2018 17:39:06 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To" X-Spam-Flag: NO X-Spam-Score: -1.684 X-Spam-Level: X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no 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 uAJQRZCvEbRe for ; Mon, 30 Apr 2018 17:39:04 -0700 (PDT) Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB11212DA18 for ; Mon, 30 Apr 2018 17:39:04 -0700 (PDT) Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id DJAEfV5gVwmrZDJJvfrTNE; Tue, 01 May 2018 00:39:03 +0000 Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-19v.sys.comcast.net with ESMTPA id DJJpfMMHl3rorDJJpfNyKd; Tue, 01 May 2018 00:39:00 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w410ctfp029169; Mon, 30 Apr 2018 20:38:56 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w410cqD9029152; Mon, 30 Apr 2018 20:38:52 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: pierluigi.spinosa@gmail.com, enrico.francesconi@ittig.cnr.it, caterina.lupo@gmail.com To: urn@ietf.org Cc: Alexey Melnikov , Barry Leiba Cc: Peter Saint-Andre Cc: john-ietf@jck.com, L.Svensson@dnb.de, juha.hakala@helsinki.fi In-Reply-To: <72446a5a-ec31-cc7e-d00a-11029ed941b3@stpeter.im> Sender: worley@ariadne.com (Dale R. Worley) Date: Mon, 30 Apr 2018 20:38:52 -0400 Message-ID: <87a7tk6wgz.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfHlzIZLErR9CYme6LJXYgvmjYTQvNy2KEIJomV2q0nHuSKHGx8BEiZDyekiqYJSaxjrR2UBzkr21qrc1mES4pj8og17+R6YhDpxQxMc/Zbf4kof/mTHK g8cHipYKLFopne1wSQbBWEmH7ERrASYsluCHg4JCOY3fEqpGL0x2WdRrNuxbETs/44qAUZ1UbY1RgPs8w30P1fkj84csrnPAOJObd+oFUqrLKNF6cvnW5CBX Fxj/rkj63iAE3BDMW8Omb8EA8ou9GCWSLXoRfZeTon85bJcv4HHucAYrn5PW2CWWDTBKMnBBSu0xAM84D3a8iQEB+bt3fcBN+KyB8DOG3u2wmFz2mYF7pMQP h4Vwdjy0crWMZokHCoF7kYbRs4xB7auQ6NVij68d33fQ3/y8LvaCe1t4GysYrHnoHLMfxhdBK1RXZ0j37xbPmS445thXOd7d9Kdkk8Q2ntKQse7+/EQDP0vS oLlOa8q+iock4Br9O3Q0f12HMLZa1KKaPdPjKlnD09pLpXbyf2qeqOT2HtjR1nmMlHM74BUEKYDgN65Z Archived-At: X-Mailman-Approved-At: Mon, 30 Apr 2018 19:24:58 -0700 Subject: [urn] Moving ahead with draft-spinosa-urn-lex X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2018 00:39:06 -0000 My apologies for not working on this earlier. The current draft of "urn-lex" is draft-spinosa-urn-lex-12. People have criticized its proposed URN system in many ways, but it seems to me that most of the criticisms are "bibliographic", they concern good ways to create identifiers for written works. As such, the IETF is not a good forum for correcting most of those problems. My proposal is that we implement "rough consensus and running code" -- obtain a usable registration of the "lex" URN namespace so that the authors and ITTIG can put the "lex" URNs into practice. The process of using the URNs will educate the authors regarding the correct resolution of the various problems, and will likely cause them to later submit a revised registration. That is, the registration we create at this time will be understood to be experimental in nature. In order to be suitable as an "experimental" registration, there are a few problems that must be resolved: 1. The URN syntax must conform to the generic URN syntax. 2. The requirements of uniqueness and persistence must be met. (That is, any URN designates at most one resource, and the resource that it designates must not change over time. However, it is permissible to have multiple URNs designate the same resource.) 3. The process or authority that assigns each URN must be well-defined. Item 1 is taken care of, in that the syntax in -12 conforms (as far as I can tell) to the URN syntax in RFC 8141. Item 2 is the responsibility of the Jurisdictional Registrars, in the same way that the naming authorities of many other URN namespaces are responsible for uniqueness and persistence. Item 3 requires that a registry of jurisdiction codes and Jurisdictional Registrars be maintained. Section 11.2 of the -12 draft proposes that IANA maintain the registry. Given the experimental nature of the URN registration, it seems to me to be premature to involve IANA, especially since the principles that the Designated Export must implement are likely to change over time. Instead, it seems to me that the best choice for registrar is ITTIG-CNR, the proposer and developer of the URN namespace. When the namespace definition is transitioned to a non-experimental status (including fixing a good set of policies to assign jurisdiction codes), the registry can be transferred to IANA to implement the proven policies. Following this path requires only small changes for -13, viz., updating section 11.2. Dale ---------------------------------------------------------------------- Archived discussions: https://www.ietf.org/mail-archive/web/urn/current/msg03828.html 16 Nov 2017 "urn:lex draft v. 12" https://www.ietf.org/mail-archive/web/urn/current/msg03811.html starting 20 Sep 2017 "Request for new URN namespace review: LEX" Message-Id: <1505909590.1544977.1112321704.5FEB92F9@webmail.messagingengine.com> https://www.ietf.org/mail-archive/web/urn-nid/current/msg01270.html starting 29 Apr 2014 "Publication request for draft-spinosa-urn-lex" Message-Id: https://www.ietf.org/mail-archive/web/urn-nid/current/msg01204.html starting 27 Mar 2013 "Application for a formal URN NID" Message-Id: <23A64284-6B03-4B24-B680-54A61E96BECA at ittig.cnr.it> https://www.ietf.org/mail-archive/web/urn-nid/current/msg01059.html 15 Oct 2009 "URN LEX Namespace submission" From nobody Mon Apr 30 22:17:54 2018 Return-Path: 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 AFEC212E880 for ; Mon, 30 Apr 2018 22:08:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.418 X-Spam-Level: X-Spam-Status: No, score=-1.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no 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 maQo3Ny2dJOb for ; Mon, 30 Apr 2018 22:08:32 -0700 (PDT) Received: from mail-it0-f44.google.com (mail-it0-f44.google.com [209.85.214.44]) (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 5B261129C6D for ; Mon, 30 Apr 2018 22:08:32 -0700 (PDT) Received: by mail-it0-f44.google.com with SMTP id i136-v6so3589730ita.2 for ; Mon, 30 Apr 2018 22:08:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rzZntfv1RMmqJaO+sfKLusoioWitOhOTq6SUPOz8Uk0=; b=D/cLUqTLDwvxn/WubVQBHGM88LKQceIae/1otcgaLapNsbcL6dDACWqOICUfuUkB0h pewfls+sVSO6Agb8AlRwv64vYJx5j6LUZqJ4oHUPyRzhm4yMPg+G6bsFfN+1PNs9Mczp /6XifMcbFSPkMHUZNLHcUTTt4CZUEOP/EdeXJhC3gBuHtsprY4N+zy06UcmY85+3/AKs G9xM1wLZG62VYlk2WzgiEqnTU3JsY7elEcwiWZGYYhuU5GFb7DPjDK8u0Qm6KVBjYqoz 9LRGH/oGfZrroI4KpZmRkrsYvbZTTnTylG6BP9f9QaPJXueJMoA3KVn7HmKhKtsMmzB+ vlog== X-Gm-Message-State: ALQs6tDTvFORraomrvKWxTlhZs/EJKt8A00qsuk/4lujvRnT5QgJF7RO U7NAzkdx1J4uVKwSk+gaomfNYNsfbTjEYBend5s= X-Google-Smtp-Source: AB8JxZohlhFQXnapi4S8hF2I+/Hd1JVESrCEwM4SHN5K50g4/0PbdplfmhjPTS7fw1LS2iAz7oFAPmzOU5FackSbHsw= X-Received: by 2002:a24:4151:: with SMTP id x78-v6mr7928176ita.0.1525151311512; Mon, 30 Apr 2018 22:08:31 -0700 (PDT) MIME-Version: 1.0 References: <72446a5a-ec31-cc7e-d00a-11029ed941b3@stpeter.im> <87a7tk6wgz.fsf@hobgoblin.ariadne.com> In-Reply-To: <87a7tk6wgz.fsf@hobgoblin.ariadne.com> From: Barry Leiba Date: Tue, 01 May 2018 05:08:20 +0000 Message-ID: To: "Dale R. Worley" Cc: Alexey Melnikov , L.Svensson@dnb.de, Peter Saint-Andre , caterina.lupo@gmail.com, enrico.francesconi@ittig.cnr.it, john-ietf@jck.com, juha.hakala@helsinki.fi, pierluigi.spinosa@gmail.com, urn@ietf.org Content-Type: multipart/alternative; boundary="00000000000026ccbc056b1df6e9" Archived-At: X-Mailman-Approved-At: Mon, 30 Apr 2018 22:17:53 -0700 Subject: Re: [urn] Moving ahead with draft-spinosa-urn-lex X-BeenThere: urn@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Revisions to URN RFCs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2018 05:08:35 -0000 --00000000000026ccbc056b1df6e9 Content-Type: text/plain; charset="UTF-8" Thanks for this, Dale: this seems like a reasonable way forward to me, at this time. Do others agree? Barry On Mon, Apr 30, 2018 at 8:39 PM Dale R. Worley wrote: > My apologies for not working on this earlier. > > The current draft of "urn-lex" is draft-spinosa-urn-lex-12. People have > criticized its proposed URN system in many ways, but it seems to me that > most of the criticisms are "bibliographic", they concern good ways to > create identifiers for written works. As such, the IETF is not a good > forum for correcting most of those problems. > > My proposal is that we implement "rough consensus and running code" -- > obtain a usable registration of the "lex" URN namespace so that the > authors and ITTIG can put the "lex" URNs into practice. The process of > using the URNs will educate the authors regarding the correct resolution > of the various problems, and will likely cause them to later submit a > revised registration. > > That is, the registration we create at this time will be understood to > be experimental in nature. > > In order to be suitable as an "experimental" registration, there are a > few problems that must be resolved: > > 1. The URN syntax must conform to the generic URN syntax. > > 2. The requirements of uniqueness and persistence must be met. (That > is, any URN designates at most one resource, and the resource that it > designates must not change over time. However, it is permissible to > have multiple URNs designate the same resource.) > > 3. The process or authority that assigns each URN must be well-defined. > > Item 1 is taken care of, in that the syntax in -12 conforms (as far as I > can tell) to the URN syntax in RFC 8141. > > Item 2 is the responsibility of the Jurisdictional Registrars, in the > same way that the naming authorities of many other URN namespaces are > responsible for uniqueness and persistence. > > Item 3 requires that a registry of jurisdiction codes and Jurisdictional > Registrars be maintained. Section 11.2 of the -12 draft proposes that > IANA maintain the registry. Given the experimental nature of the URN > registration, it seems to me to be premature to involve IANA, especially > since the principles that the Designated Export must implement are > likely to change over time. Instead, it seems to me that the best > choice for registrar is ITTIG-CNR, the proposer and developer of the URN > namespace. > > When the namespace definition is transitioned to a non-experimental > status (including fixing a good set of policies to assign jurisdiction > codes), the registry can be transferred to IANA to implement the proven > policies. > > Following this path requires only small changes for -13, viz., updating > section 11.2. > > Dale > ---------------------------------------------------------------------- > Archived discussions: > > https://www.ietf.org/mail-archive/web/urn/current/msg03828.html > 16 Nov 2017 > "urn:lex draft v. 12" > > https://www.ietf.org/mail-archive/web/urn/current/msg03811.html > starting 20 Sep 2017 > "Request for new URN namespace review: LEX" > Message-Id: < > 1505909590.1544977.1112321704.5FEB92F9@webmail.messagingengine.com> > > https://www.ietf.org/mail-archive/web/urn-nid/current/msg01270.html > starting 29 Apr 2014 > "Publication request for draft-spinosa-urn-lex" > Message-Id: vG0pVAy8e45N5aQ@mail.gmail.com> > > https://www.ietf.org/mail-archive/web/urn-nid/current/msg01204.html > starting 27 Mar 2013 > "Application for a formal URN NID" > Message-Id: <23A64284-6B03-4B24-B680-54A61E96BECA at ittig.cnr.it> > > https://www.ietf.org/mail-archive/web/urn-nid/current/msg01059.html > 15 Oct 2009 > "URN LEX Namespace submission" > -- Barry -- Barry Leiba (barryleiba@computer.org) http://internetmessagingtechnology.org/ --00000000000026ccbc056b1df6e9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for this, Dale: this seems like a reasonable way f= orward to me, at this time.
Do others agree?

Barry

On Mon, Apr 30, 2018 at 8:39 PM Dale R. Worley <worley@ariadne.com> wrote:
My apologies for not working on this ear= lier.

The current draft of "urn-lex" is draft-spinosa-urn-lex-12.=C2=A0= People have
criticized its proposed URN system in many ways, but it seems to me that most of the criticisms are "bibliographic", they concern good way= s to
create identifiers for written works.=C2=A0 As such, the IETF is not a good=
forum for correcting most of those problems.

My proposal is that we implement "rough consensus and running code&quo= t; --
obtain a usable registration of the "lex" URN namespace so that t= he
authors and ITTIG can put the "lex" URNs into practice.=C2=A0 The= process of
using the URNs will educate the authors regarding the correct resolution of the various problems, and will likely cause them to later submit a
revised registration.

That is, the registration we create at this time will be understood to
be experimental in nature.

In order to be suitable as an "experimental" registration, there = are a
few problems that must be resolved:

1. The URN syntax must conform to the generic URN syntax.

2. The requirements of uniqueness and persistence must be met.=C2=A0 (That<= br> is, any URN designates at most one resource, and the resource that it
designates must not change over time.=C2=A0 However, it is permissible to have multiple URNs designate the same resource.)

3. The process or authority that assigns each URN must be well-defined.

Item 1 is taken care of, in that the syntax in -12 conforms (as far as I can tell) to the URN syntax in RFC 8141.

Item 2 is the responsibility of the Jurisdictional Registrars, in the
same way that the naming authorities of many other URN namespaces are
responsible for uniqueness and persistence.

Item 3 requires that a registry of jurisdiction codes and Jurisdictional Registrars be maintained.=C2=A0 Section 11.2 of the -12 draft proposes that=
IANA maintain the registry.=C2=A0 Given the experimental nature of the URN<= br> registration, it seems to me to be premature to involve IANA, especially since the principles that the Designated Export must implement are
likely to change over time.=C2=A0 Instead, it seems to me that the best
choice for registrar is ITTIG-CNR, the proposer and developer of the URN namespace.

When the namespace definition is transitioned to a non-experimental
status (including fixing a good set of policies to assign jurisdiction
codes), the registry can be transferred to IANA to implement the proven
policies.

Following this path requires only small changes for -13, viz., updating
section 11.2.

Dale
----------------------------------------------------------------------
Archived discussions:

https://www.ietf.org/mail-archive/web= /urn/current/msg03828.html
16 Nov 2017
"urn:lex draft v. 12"

https://www.ietf.org/mail-archive/web= /urn/current/msg03811.html
starting 20 Sep 2017
"Request for new URN namespace review: LEX"
Message-Id: <1505909590.1544977.1112321704.= 5FEB92F9@webmail.messagingengine.com>

https://www.ietf.org/mail-archive= /web/urn-nid/current/msg01270.html
starting 29 Apr 2014
"Publication request for draft-spinosa-urn-lex"
Message-Id: <CALaySJJk5YiCQZqt6WoWkqfAzi2A04HEAH=3DvG0pVAy8e45N5aQ@mail.gmail.c= om>

https://www.ietf.org/mail-archive= /web/urn-nid/current/msg01204.html
starting 27 Mar 2013
"Application for a formal URN NID"
Message-Id: <23A64284-6B03-4B24-B680-54A61E96BECA at ittig.cnr.it>

https://www.ietf.org/mail-archive= /web/urn-nid/current/msg01059.html
15 Oct 2009
"URN LEX Namespace submission"
--
Barry
--
Barry Leiba =C2=A0(barryleiba@computer.= org)
http://internetmessagingtechnology.org/
--00000000000026ccbc056b1df6e9--