
From nobody Sun Jul  3 02:08:09 2016
Return-Path: <duerst@it.aoyama.ac.jp>
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 E0E9512B03F for <urn@ietfa.amsl.com>; Sun,  3 Jul 2016 02:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.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 rx4xshSV02ke for <urn@ietfa.amsl.com>; Sun,  3 Jul 2016 02:08:05 -0700 (PDT)
Received: from JPN01-OS2-obe.outbound.protection.outlook.com (mail-os2jpn01on0090.outbound.protection.outlook.com [104.47.92.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DDE012B03C for <urn@ietf.org>; Sun,  3 Jul 2016 02:08:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Udazx1DwktGtIbYd9mrxqv6h5HXgtEG/bRpmHEB64AE=; b=aHe/jcRNnevir4g6dxZMRaru6UcAEvA1woTDYXn3YMMUNsMTI9mryF74QuQ8sr+lPgh5i8Ox17tfz71yQ4ctvk3NsCllqw4Eux42yXs7eyWlDLypk+0DI7yEublKBLM4ML+xCzveUOeY+2iD+7pE4BCtspb0nRRhGcl8X5FR3hU=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp; 
Received: from [192.168.1.2] (60.36.28.163) by TYXPR01MB0926.jpnprd01.prod.outlook.com (10.168.45.21) with Microsoft SMTP Server (TLS) id 15.1.534.14; Sun, 3 Jul 2016 09:08:00 +0000
To: John C Klensin <john-ietf@jck.com>
References: <B2C81940D78774C81B556AAE@JcK-HP8200>
From: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <4b828c5e-e662-5451-e053-605fdb63c53f@it.aoyama.ac.jp>
Date: Sun, 3 Jul 2016 18:07:50 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <B2C81940D78774C81B556AAE@JcK-HP8200>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [60.36.28.163]
X-ClientProxiedBy: OS2PR01CA0013.jpnprd01.prod.outlook.com (10.161.74.151) To TYXPR01MB0926.jpnprd01.prod.outlook.com (10.168.45.21)
X-MS-Office365-Filtering-Correlation-Id: 9a0b5b72-9c32-4746-2725-08d3a3218899
X-Microsoft-Exchange-Diagnostics: 1; TYXPR01MB0926; 2:TpMP7lEixTfBGPIwvtRjmqRtYuQHVTEpJg0FA+skswYUHMVGV5XPvAdFg+DAS2ppu15zztr3iWO/qRWjkTvJtc6ainea/E5eUH5bUmAQD7epi+wfPlwCuGm8DRwClGobSbaSHrlLqyeleLqwro51YxHAd+CW0FDYZIG1glhbF0Dw+NJco4E1dTK5DC4i7e9P; 3:0FmMmr8/vaVuXyNApJFhS7wa1hQlnvERP0zCvoZZhLwZXboFxVJr6r9rKHjKQbKuXCkKthTI8Vg7Snlp5+U6JTZuYG2yA9rpy2QiKTgZri24Z0FNri6hTggNdZ3E8KEj; 25:Q5iNTjWAY6R+Xo1Ic2cxzTCksprfDJlEhBiBRoiqf2qKSjn6ezKZT36qP0PCMdyfd8MTZPqahtvFLahCVlN/DorgtYpYeBd0TuHiClD/v1hM7E/c+9nIpy75ipbG7mIqHFqS3snrvYX6C/O6IdY+TW7G9YktNhfoUV76USC9SHIQ+8lB6qB/GLBQ7abV/WmeAO6ngpU9ZgnEsIjpfEqaIOAQv66cBvflaUAa4JY7shHqswgi8bTJMA7Pu3VIz08moMrd5JlZDL4nfxNBcWnEHvuuXZg9r2gQ5S5/p8Pgrg90YyLbr2d+Tq78OERinq06MrIJksYtEtE7jfJ3VghT2XCusi7/FxMO+qCj7N1JrI419QheFKzj5o+BtCgGw+aSdXyFdTjNk+FeOjvgR6UL94vL6JNTKj50Njtvq9j1uHc=; 31:SqMTufHBQYaqkXDAEHYUDG1mC5rCvyJpDJpgMHY3Bk5bkWo5rQqwzw7oErLoYWdtd3ykAkRXjjJ8d+vj4OkrSEHLvaMH9wmZP2fRBmepaaIxiSLeO9kDZMjeW+F42AN5VnjOayZLpzBfgym+BiWfjwbQ0OcyQrj2FVQuecfCge5G4s+Xbk+D273fow3duIkIFNOKzfE5qAmBhT+ztsHU3g==
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TYXPR01MB0926;
X-Microsoft-Antispam-PRVS: <TYXPR01MB0926D7CED443ED719C1B111ACA270@TYXPR01MB0926.jpnprd01.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040130)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041072)(6043046); SRVR:TYXPR01MB0926; BCL:0; PCL:0; RULEID:; SRVR:TYXPR01MB0926; 
X-Microsoft-Exchange-Diagnostics: 1; TYXPR01MB0926; 4:SdhnCNQb26nvj/odmTUuop9ZxgIEMcztVXvPbQHvR3DtNpckdB5VWd9wTa5/Tytw8KJzJLXm+J1CecB/7ajH3R+ISHLrG8/JT5Rkfmp2HmKqM87nYbvBDOX6jeIYWPvWz2SoAlysjf8b3XJEahyaMOuR/SjzLmP83Pbui1WQSeKtmDRnTKjaRYVyGddpgBd1FBfapDEiysNrEZO4Spw/cxKhpGS4m3x81xIH7XD54bUQ2rftuXCOSz7lib0mh8gsyny18IKlXFHpg+nX9yyA/iKttYtbjCZBnWDhRXpz2aBY8A587UI5xRRe12BcSna2iZ53UvTJGjy27P3yR2EhiQHT6Vr0UU0bmtYR0cdjP3Ik/CVds3IVMvEums9B32sJg0B1jtWrXM7K0yPzCT+k4w==
X-Forefront-PRVS: 09928BEC91
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(6049001)(7916002)(189002)(199003)(24454002)(101416001)(31696002)(33646002)(105586002)(106356001)(230783001)(97736004)(189998001)(110136002)(117156001)(4001350100001)(2906002)(4326007)(23676002)(47776003)(65956001)(65806001)(66066001)(68736007)(42186005)(31686004)(54356999)(76176999)(50986999)(86362001)(74482002)(7846002)(7736002)(305945005)(50466002)(64126003)(8676002)(586003)(3846002)(6116002)(77096005)(83506001)(2950100001)(81166006)(81156014)(230700001)(92566002)(65826006); DIR:OUT; SFP:1102; SCL:1; SRVR:TYXPR01MB0926; H:[192.168.1.2]; FPR:; SPF:None;  PTR:InfoNoRecords; MX:1; A:0; LANG:en; 
Received-SPF: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtUWVhQUjAxTUIwOTI2OzIzOjJxbm9nZDlzU2Uxd3kwaTlLZituTzJ1bW1q?= =?utf-8?B?UFVLNDBJWWpIWjBxbE5vZ2dHbkU3Rk5HK0ZVM0xlTXVTaXg0cXduS090S1Vh?= =?utf-8?B?V2Riem4zdEJoR21yc2cyc0xwam42RmV3eXNOOFU4eE9lVkhiQnpOQ2tWWGhW?= =?utf-8?B?dWw0NjAySHNtZ3lGb2NvZm9lUVlEMnpIeGVLSFBqRDFNVWM1K3g3L3pibTJK?= =?utf-8?B?K0N5bDRvcDE3aTkzcnZ4azZnbmFXL3YxRDFSMVhVbitHYlF2M2k2aWlFVzQ3?= =?utf-8?B?K3FGYWJUd3VuSkRPRFJTYk41STNpbUROTVRJODVzQkpCRUpnR0RTYjVmN25E?= =?utf-8?B?RXpjUUY4R3RydUtCdExWbEMxRHd1TlBvcDVnaFY4TzJ5a0hrS2lGaGt6MXlP?= =?utf-8?B?eEgyK0o4dzB0K25JWXV2aTlGTDRsWlhVWXEvNTlON08vNU91Q2hNNmNuWmR2?= =?utf-8?B?OUFGMEw0U1IzV3BQcmNkSUh0dFdSTS95UmZTSUtaanhpdE9LQUo2RVEvYTQ4?= =?utf-8?B?L3krMVVNNTBTZ3dSUTBzZTR1M3VRa1NkNTRSUFp1eDVxV2txZlNIblRDcXVR?= =?utf-8?B?Y2JIUGdqT29iK1BUVmI4bTNNaG1POUpyT2JYZ2owdFJYb21NMUlqR1YxZ0N5?= =?utf-8?B?NkdMTGNCVGo5elFOV1gvb2szb3FDaE4ycFhtUlpVeUw5cm1DblBYRnVSTlBG?= =?utf-8?B?dWJFeDlheFhZTTBYNzEwVklIRVY1QW8xTUp3a2I4b3ROY2ZONnp1R0lUa2hY?= =?utf-8?B?bWdIS01mQzFlVWVaOGJ3VnJla29GWW5XL29IQmVyKzhzdkJNUXFOQVNGMmd1?= =?utf-8?B?eFJFWjRvczRwbDdIZGhKTmk5UWFHOVg4ajArWDR5blVDeThwOXQ0ZGdOOW5s?= =?utf-8?B?L1c4WUxoVzJuRTAwMUQza2RTVURnNk9ndWpORWsvTEIrQTNEMTFGcVp5OXQr?= =?utf-8?B?NFcrKzlqSDdTaW5nQWYycjcrVkhBcm9NYStoSGZibXhXWEZaajR0WTFzb2pH?= =?utf-8?B?Smdmejc1U2R6UEUxMEFQWUNIanA5ZHZoUjNWaFE2S2Zkbnh2SmtBeXVvS01J?= =?utf-8?B?NEZ2Ui9yRHYrRmpDTFZwMXk2MkRXZ0tPSnFKZXYrSTFXZk1ZZkE0RWxra2Ni?= =?utf-8?B?bXdQdFV2MUd0eUI3SkRwYlo5SzdKcUo5NW9iQ3hZV0EwR0NiUDNoZEQ5amxC?= =?utf-8?B?eklGTjdxVDJ5Y1c4cksxbzdOc1FrQSs3bnZqL2l1NjRJR0p4cVRsbnNOM3NQ?= =?utf-8?B?YlNkeENiL0JaRTlpRm9nakNoV253MXFML3U2N0kyckNtT1ZYc0tPbUJhU0Jl?= =?utf-8?B?QjUzMURmKzJpY0JlVm5WOHRJN3E0QkdRUkhXRnB3VE1BOGF5V3dpaHNUL3ZI?= =?utf-8?B?VFk0MXJrejArakpORVpTd0d0bE11b0U2TUtFSmFMSjdVMFdxS0Vqck95bGZG?= =?utf-8?B?VEEyZEZKNGZXcTZXQktOR2xhdjNjLzl5b3hnTWlxUklZT1hFeEV1TmpkM1dt?= =?utf-8?B?OVZKK3VoK3ozSStNS292MWxvSGl0OCtKMmZ0SWRNUFlMem1naWErd0taT0NB?= =?utf-8?B?c1FzSVNNb04xejRmKzduRnFieUdiWmxaZHZZVkxVTHRjWVFKYWV2aFk2QWMz?= =?utf-8?B?bUZzTVpjNCswZ3NDU2dDY3dXa2lXTVNxY2tQdW1RL3BZRHFGa1FLdG5RPT0=?=
X-Microsoft-Exchange-Diagnostics: 1; TYXPR01MB0926; 6:0ZBb0qOeDtqKp03+MUNyRknlkizk3ushsjZJ4I6CcAS106Wn+9JE5baIkcOnLbTmbv9bjcCrykapPiN6XUkTUYaL09boVPu5StoFpPkFw2id1+q5VtX7DsyX6+sba0uwA7qB194d0sP7Yx05yNYLx6lwDjftIImW8oorFItSRT3Ijj+WmWL2Gvi9rGD4DXFFuMxG9SGK5WRk6HnowEtaZTxBW67dcojklM7Zj8BkTO1ODMJHPM7o2gFJu+XwhcfsK3mPyW7KxIGgcUqP8mzfQKZPN//Usn6RtfcmJt7ZVjRNQyiKpdL/qkD1Gjqnw5qR; 5:HYcXharJIaqKaKUl88VTj3YB9sEYkqwq5SiL+O1REjZtAlFbC9Yt5caoGQRudUdiaOZ4hNerrVs11j329uu3EUnhhUj4Yvn+eeCqC61HJlxsF/4xghVRiT6l6qwpucFgfoUiwcgJdnUZ2lt+41XaUQ==; 24:KNeR/bBFAoxSdr5JPOuCwNs92VCN6LL8LxHEb4esOiZApqkn08dSL7xBDkyBa5KBZsuzfA1ZrPaPSO3eCTnEIgmNG/+nQZ18KnkvLlwCrCs=; 7:K+DkZUlvk6CTFw/Bn/PUsh+T+OZ2Nru+zmHgFwVLQDVVhalpI3F/aJtB87ybkCzWp23E4V/0l5C0wPx/MhoS8KwcLyOZbsePdrH21hgEdldVOWwlLQpFPdWpfX4LTn8jUs7tSy1Mkep7LKQznR+4EaY77FcwXTVTf6S9cJP/NJw45cR4ruh/TjUq2VCU2rRV8hsuSg/Tt+4WIbnF4NRS2QkZh6wmD/acAglhq+M6H201RSp0xFB+QAeGVmKCUWNR
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Jul 2016 09:08:00.8657 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TYXPR01MB0926
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/5mSRoF5NlD3YgnmeW3lHgFNPQWk>
Cc: urn@ietf.org
Subject: Re: [urn] I-D Action: draft-ietf-urnbis-semantics-clarif-04.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jul 2016 09:08:08 -0000

Hello John,

Thanks for your mail. Sorry to be late in responding.

On 2016/06/30 01:00, John C Klensin wrote:
> (sorry... wrong address)
>
> Sean, Martin,
>
> One pre-call observation (at this point, I'm not sure I'll
> manage to make the call)...
>
> While we can debate how to fix semantics-clarif at length
> (including nit-picking about "abstractly correct", which I will
> happily change just to avoid spending time debating it),
>
> semantics-clarif _does not_ change, or try to change, 3986.

That's good to hear. But then the "update 3986" piece wouldn't be necessary.

Regards,   Martin.


> What it attempts to do is to establish some local context,
> relationships, and terminology for URNs that conflict with some
> people's reading of 3986.  If that is still not clear to a
> significant fraction of the WG, it is clear that a new editor is
> needed because I can't stand looking at it any more.
>
> But the bottom line seems to me to be the comment in another
> note that we should just make 2141bis conform to whatever 3986
> says about URIs.  I believe that the WG has already concluded
> that is impossible (at least as many participants in the WG
> under 3986) and that we need to move past it.  If that
> discussion is going to be reopened, let's do it explicitly,
> rather than trying to do it by debating the fine points of
> either of these URNBIS documents.
>
>    john


From nobody Sun Jul  3 10:12:45 2016
Return-Path: <john-ietf@jck.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE2C12B01D for <urn@ietfa.amsl.com>; Sun,  3 Jul 2016 10:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 rjK_YtCQKN2E for <urn@ietfa.amsl.com>; Sun,  3 Jul 2016 10:12:41 -0700 (PDT)
Received: from bsa2.jck.com (ns.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 3B97D128E19 for <urn@ietf.org>; Sun,  3 Jul 2016 10:12:41 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1bJkwg-0008LM-Hg; Sun, 03 Jul 2016 13:12:38 -0400
Date: Sun, 03 Jul 2016 13:12:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Martin_J=2E_D=C3=BCrst?= <duerst@it.aoyama.ac.jp>
Message-ID: <7A50CAD3988009BC38DE4CE7@JcK-HP8200>
In-Reply-To: <4b828c5e-e662-5451-e053-605fdb63c53f@it.aoyama.ac.jp>
References: <B2C81940D78774C81B556AAE@JcK-HP8200> <4b828c5e-e662-5451-e053-605fdb63c53f@it.aoyama.ac.jp>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/PHNY5lUA_5yKt8HJssDcF7mYKso>
Cc: urn@ietf.org
Subject: Re: [urn] I-D Action: draft-ietf-urnbis-semantics-clarif-04.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jul 2016 17:12:43 -0000

--On Sunday, July 03, 2016 18:07 +0900 "Martin J. D=C3=BCrst"
<duerst@it.aoyama.ac.jp> wrote:

>> semantics-clarif _does not_ change, or try to change, 3986.
>=20
> That's good to hear. But then the "update 3986" piece wouldn't
> be necessary.

Transcription error.  Removed from the working draft of -05 a
few days ago.

Just to clarify in case it hasn't been clear from other notes,
my plan is to make one more pass through semantics-clarif to fix
that error and tidy up any typographical or editorial issues
that I (or others) identify, get -05 posted, and then stop work
on the document.  If changes are wanted beyond -05, someone will
have to convince the co-chairs that additional work on the
document is worthwhile and find an editor because, unless
something very significant happens, I'm through after -05 is
posted.

I do intend to take another look at the use of "believe" in the
context of your remark about religion.  I will see if the text
can easily be clarified to make it clear that the issue is an
honest difference of opinion among people who interpret 3986
differently and decisions that the WG is not going to try to
deliver a definitive interpretation (which would imply updating
3986), not, e.g., religious belief.  However, I'm not going to
spend a lot of time and energy on it.  While I would welcome
suggested textual changes, I'm not going to spend time on-list
debating them or refining language in ways that would be more
appropriate if we were headed for RFC publication.   Again, I
can be persuaded otherwise, but my most likely response would be
"find another editor".

While I could (and would) change my mind (particularly if I get
instructions from the co-chairs to the contrary), my current
plan is to not issue -05 until we are close to IETF LC on
2141bis.  I don't need the distraction of having the fuss with
this document and don't believe anyone else does either.

    best,
      john



From nobody Fri Jul  8 08:12:43 2016
Return-Path: <barryleiba@gmail.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C1CD12B047 for <urn@ietfa.amsl.com>; Fri,  8 Jul 2016 08:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=gmail.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 IGLajeCZskLk for <urn@ietfa.amsl.com>; Fri,  8 Jul 2016 08:12:39 -0700 (PDT)
Received: from mail-yw0-x242.google.com (mail-yw0-x242.google.com [IPv6:2607:f8b0:4002:c05::242]) (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 5360E12D0CF for <urn@ietf.org>; Fri,  8 Jul 2016 08:12:39 -0700 (PDT)
Received: by mail-yw0-x242.google.com with SMTP id l125so8633395ywb.1 for <urn@ietf.org>; Fri, 08 Jul 2016 08:12:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:from:date:message-id:subject:to; bh=GyCz7Q+R6sU5pRolp0jng3u9fYWO+MWj2DmKWtld13g=; b=o4XHbL1jWuAinwZoJrTHlOrMpcAcxXmYR9UYjYF4KDqWDJDWbSqtesoz9ZxKh72bYx wEJ5iCNhfhfQtw5pylYSgSEKZipfQK85FPLXIFu8Kq0cIhzKdHLzg/TYH+QyKGO0O75V ZIQubCtszPe4H5MWzSrh+GYZRwhRmKpLmrrlI+OLhTaMVaPBYY4/513O8FMi75VJJEtw Xii8u8GDkq6MsC7qPfFefX02kqEcWFVqnOItYwakJbZ0xNGG34FV9BZUAGpa0YIfCkH8 z8vWN/GNVkBDiRV2Lt191JyDhRV4JuGm4whBmjXKJCjOr9W42t+rB0MhGI1fCtrNWIII ujaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=GyCz7Q+R6sU5pRolp0jng3u9fYWO+MWj2DmKWtld13g=; b=MAC336+lV6xprJAdFQTZ9HMNRmDZEYF4lCxJEf5r5/iwnprRK/bIr7vSYT81umkFl1 PFmnEgRXp82BMLK5o6zTN05kcOzyKSXeJJUMyzO6nO5rvd/gU298aG3JI/5F/KPbRjyo xOvh2FT3C9SMGcWwS/tZHghVG3V3QXVT8Z0LredH5+/+LODLnoCC0a6inutEWFrEQ8qV v5bdFF38UwjrC6XhDb7L0U3f+WVfB8JXYK99OEjeKuD+mgHNKdqNjnBY6sLuqDeNg5qA SDfT9VydVuN7CZTmOfjqHMUdnD+2ueowWGxwcp0MsLSp1WZXM2ljfwcswmGQ/q1ypV5/ zyTQ==
X-Gm-Message-State: ALyK8tJLPgFlnQgw7OiKv6OlJwzuTOswrwaMlyq2mN0+gu2IaBcfbHrBT6nycDr5IQ2oynvnVWAW7Esca9qK7w==
X-Received: by 10.129.161.86 with SMTP id y83mr4831629ywg.190.1467990758344; Fri, 08 Jul 2016 08:12:38 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.83.33.137 with HTTP; Fri, 8 Jul 2016 08:12:37 -0700 (PDT)
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 8 Jul 2016 11:12:37 -0400
X-Google-Sender-Auth: dwNGDQzlAdPFRbgNNIRsguGcOuU
Message-ID: <CALaySJ+2QF_gBBW369z2VDYLJ1TEiJf3Naeo+RO1a4VzcE3+ZA@mail.gmail.com>
To: "urn@ietf.org" <urn@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/9cudZSjqZKB6s4NgMfLtJtS8mAw>
Subject: [urn] Notes from the URNbis virtual meeting
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 15:12:41 -0000

My apologies for having not posted this sooner; I wrote them up the
next day and got some review, but wasn't able to follow up until now.
I will figure out how to post these to the datatracker forthwith.

Barry, as chair

----------------------
29 June 2016

Start at 12:05 NY time

Attendance:
Alexey Melnikov (AD)
Andy Newton (chair)
Barry Leiba (chair)
Henry Thompson
John Klensin
Juha Hakala
Julian Reschke
Peter Saint-Andre
Sean Leonard

Semantics clarification
- meant to set the stage
- need to be sure we're on the same page with respect to it, and that's all
- not "update" 3986, but look at the principles that
semantics-clarification set out
- a bit of background on how s-c came about
- - maintain syntax compatibility for URNs, but not necessarily semantics
- - how are fragments interpreted in URNs?
- concern: we can't break generic URI processors
- claim: you still need to understand the URI scheme...
- - ...so any processor that doesn't understand the "urn:" scheme
can't process them anyway
- - ...and any processor that does will know what to do with it
- - comment that generic URI processing is basically limited to
generic parsing (which is all that 3986 talks about), and that any
further processing, including resolution, needs knowledge of the URI
scheme
- discussion of those points -- agreement so far
- discussion brings up an issue in 2141bis Section 4.3 ("URNs and
Relative References", text from April 2015) Need to work on that text,
but it's editorial, not a fundamental issue.  Henry is willing to work
with John and Peter on text.
- The document has served its purpose and will not have any further
major work.  The point is to make sure that 2141bis reflects the
principles outlined here.

2141bis Issues:

1. URN equivalence
- Sean is concerned that just "equivalence" is unclear and confusing
- Agreement that equivalence as specified here ends at the bytes in
the URN, and that "equivalence" such as "names the same document",
while a reasonable thing to consider, is out of scope here
- We're in agreement about what the document needs to say, but we need
to settle on terms to go with the definitions -- at minimum, putting
the hyphen back into "URN-equivalence".  Sean prefers "lexical
equivalence", but John is conccerned that that term creates new
ambiguities and that the document needs to distinguish among various
types of equivalence, two of which it addresses now and some that it
does not:
- 3986 baseline equivalence: octet-by-octet identity across the entire string.
- URN-equivalence: whatever it is that 2141bis specifies as
scheme-specific equivalence.
- Namespace-equivalence: whatever 2141bis should say about equivalence
within a specific namespace, which could be further specified in the
namespace definitions.
- Other forms of equivalence that depending on dereferencing or object
retrieval, which ought to be well out of scope here.

2. Usage of the term "urn" -- used for different things, and sloppily
(related to name and namespace)
- General cleanup will be done: Peter has already agreed to start that.
- Cleaning it up fully will probably take more than one pass, and will
require careful review.

3. Ordering of components, and the issue of "?=" or "?+" appearing in
a q-component
- Discussion of the advantages and disadvantages of flexible ordering
vs limiting the acceptable content of the components.
- Decision to require r-component to come before q-component, so that
the "?+" delimiter for r-component can't be confused as being part of
the query.
- Decision to remove restriction on "?=" and "?+" in q-component.  The
q-component will only end with "#" or end-of-string.

4. Discussion of f-component text (Section 2.3.3)
- Decision not to change that -- what's there was difficult to arrive
at, and we will stay with it.
- But see the comment above about the relative reference text in
Section 4.3, which will interact with this.
- CREF3 (at the beginning of 2.3.3) will be removed.

Chairs thank everyone for taking the time to attend; we were able to
resolve what we intended to.

End at 13:59 NY time

Steaming audio:
https://ietf.webex.com/ietf/ldr.php?RCID=201acf77f3c0b85c3dbb2522869314da
Download audio:
https://ietf.webex.com/ietf/lsr.php?RCID=0be6a5705f32a5c45f91ba3c7b772830
----------------------

