
From stpeter@stpeter.im  Wed May  5 14:49:37 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 836763A6D39 for <urn@core3.amsl.com>; Wed,  5 May 2010 14:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.153
X-Spam-Level: 
X-Spam-Status: No, score=-2.153 tagged_above=-999 required=5 tests=[AWL=0.446,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PJZyCYrVbIK5 for <urn@core3.amsl.com>; Wed,  5 May 2010 14:49:36 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 651163A6D37 for <urn@ietf.org>; Wed,  5 May 2010 14:49:33 -0700 (PDT)
Received: from moveme.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 02EC840E2C; Wed,  5 May 2010 15:49:18 -0600 (MDT)
Message-ID: <4BE1E7DB.2060702@stpeter.im>
Date: Wed, 05 May 2010 15:49:15 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
References: <201004280802.KAA11778@TR-Sys.de> <4BD863CA.3050004@renci.org>	<4BD8772D.7080601@network-heretics.com> <4BD87BEA.9070309@renci.org>	<4BD888C7.5080801@network-heretics.com> <4BD89B92.8000501@renci.org>	<4BD8BF32.7030201@network-heretics.com> <4BD8CB0F.5030602@renci.org>	<r2h6e04e83a1004281752k594791f7l3d72ab4016a7d8cc@mail.gmail.com>	<4BD973E9.8020903@it.aoyama.ac.jp> <h2n6e04e83a1004290740w6cb0cd84p8b077353486835d8@mail.gmail.com>
In-Reply-To: <h2n6e04e83a1004290740w6cb0cd84p8b077353486835d8@mail.gmail.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms070007010804030505000707"
Cc: "urn@ietf.org" <urn@ietf.org>, Keith Moore <moore@network-heretics.com>
Subject: Re: [urn] fragment identifiers, Re: rfc2141bis [was: Re: A first cut 	at the Draft Charter ...]
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 May 2010 21:49:37 -0000

This is a cryptographically signed message in MIME format.

--------------ms070007010804030505000707
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 4/29/10 8:40 AM, Ted Hardie wrote:
> On Thu, Apr 29, 2010 at 4:56 AM, "Martin J. D=C3=BCrst"
> <duerst@it.aoyama.ac.jp> wrote:
>> Hello Ted,
>>
>  You might note, for example, that
>>> the XMPP namespaces that use URNs include at least one with a fragmen=
t
>>> identifier:
>>>
>>> http://xmpp.org/registrar/namespaces.html
>>
>> That would be urn:xmpp:langtrans#items.
>>
>=20
> Yes.

We have people here who can fix that. :)

/psa



--------------ms070007010804030505000707
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIWnDCC
B1cwggY/oAMCAQICAVUwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBT
aWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQTAeFw0wOTA3MDYwMDAwMDFaFw0xMDA3MDYyMzU5NTlaMIHCMQswCQYDVQQG
EwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRlbnZlcjEiMCAGA1UEChMZWE1Q
UCBTdGFuZGFyZHMgRm91bmRhdGlvbjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0
aWZpY2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcN
AQkBFhJzdHBldGVyQHN0cGV0ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQCas7Mrnh02GakN8sft+HJpU4MwBxEgrGDZ2ZzUxDDt2sEhM+9Q74h955MtgMhK3TeBf6Hs
hDh/8Z9G//k2qNA0M2S5rejTqrmW0Jabca/L7BUZ0GhnU2N/2zeciFUmuZ4A2l1T5IMX2ZVP
XnNIaefBtbImJAbDz3T0vxkzTtcqgW3wL83PMDiqiuM+e1k+VPvOW4f5ZSGkPIhYCDpWqNE5
wZvjrLNMc8jZOPs9DrsYuIVwU72Vhy1tkEh+w6YpYHrdEUAe+eKe6TuxqZ60e9z3O36uiV//
Ms274iD6PbA/IGazJgaAdg6tvPehwTYGJAGmv3PsJKkLGjgoh+RrrM1LAgMBAAGjggOKMIID
hjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFOyws3XWgIY9FP1POVqjdZP9Lu38MB0GA1UdEQQWMBSBEnN0cGV0ZXJA
c3RwZXRlci5pbTCBqAYDVR0jBIGgMIGdgBR7iZySlyShhEcCy3T8LvSs3DLl86GBgaR/MH0x
CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg
RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eYIBDzCCAUcGA1UdIASCAT4wggE6MIIBNgYLKwYBBAGBtTcBAgAw
ggElMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQG
CCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMIG8
BggrBgEFBQcCAjCBrzAUFg1TdGFydENvbSBMdGQuMAMCAQEagZZMaW1pdGVkIExpYWJpbGl0
eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRoZSBTdGFydENv
bSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwYwYDVR0fBFwwWjAroCmgJ4YlaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vY3J0dTMtY3JsLmNybDAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNz
bC5jb20vY3J0dTMtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0
cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczMvY2xpZW50L2NhMEIGCCsGAQUFBzAC
hjZodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MzLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUA
A4IBAQBgv4xFXZqDKSOtnPOVbqOh1brj7oxRaVYk7N0MJG7x9Y/wkO3iwRwizVLcC1bA+D/R
gyFilXx6IQWE63Ge2tu+Y4w5QoHYwuUFQuBZuxvZpOa3ykdgPlBQaBM8m+Ien0skwNggaizA
X9Pc/sMLpP3jkO1iSF4agy4r5Ed+4G10mP5X0zO3gQwq9Uj4F9tX+58kU+fM1P8Sh+BYR4r/
kSbKE3tWcMaKblWPGwX0nYD26Je7Qb+uX/J5lCgozBrHXQWq8N98iklASf2pv+32Oi1dEjmM
UgAm/J2+YmxaI02+c+H6QH8+F3RUjCiRg9XqUNjcrNrnTFnm/iMMZADktsXPMIIHVzCCBj+g
AwIBAgIBVTANBgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBMB4XDTA5MDcwNjAwMDAwMVoXDTEwMDcwNjIzNTk1OVowgcIxCzAJBgNVBAYTAlVTMREw
DwYDVQQIEwhDb2xvcmFkbzEPMA0GA1UEBxMGRGVudmVyMSIwIAYDVQQKExlYTVBQIFN0YW5k
YXJkcyBGb3VuZGF0aW9uMSwwKgYDVQQLEyNTdGFydENvbSBUcnVzdGVkIENlcnRpZmljYXRl
IE1lbWJlcjEaMBgGA1UEAxMRUGV0ZXIgU2FpbnQtQW5kcmUxITAfBgkqhkiG9w0BCQEWEnN0
cGV0ZXJAc3RwZXRlci5pbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJqzsyue
HTYZqQ3yx+34cmlTgzAHESCsYNnZnNTEMO3awSEz71DviH3nky2AyErdN4F/oeyEOH/xn0b/
+Tao0DQzZLmt6NOquZbQlptxr8vsFRnQaGdTY3/bN5yIVSa5ngDaXVPkgxfZlU9ec0hp58G1
siYkBsPPdPS/GTNO1yqBbfAvzc8wOKqK4z57WT5U+85bh/llIaQ8iFgIOlao0TnBm+Oss0xz
yNk4+z0Ouxi4hXBTvZWHLW2QSH7Dpilget0RQB754p7pO7GpnrR73Pc7fq6JX/8yzbviIPo9
sD8gZrMmBoB2Dq2896HBNgYkAaa/c+wkqQsaOCiH5GuszUsCAwEAAaOCA4owggOGMAkGA1Ud
EwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV
HQ4EFgQU7LCzddaAhj0U/U85WqN1k/0u7fwwHQYDVR0RBBYwFIESc3RwZXRlckBzdHBldGVy
LmltMIGoBgNVHSMEgaAwgZ2AFHuJnJKXJKGERwLLdPwu9KzcMuXzoYGBpH8wfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5ggEPMIIBRwYDVR0gBIIBPjCCATowggE2BgsrBgEEAYG1NwECADCCASUwLgYI
KwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUH
AgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgbwGCCsGAQUF
BwICMIGvMBQWDVN0YXJ0Q29tIEx0ZC4wAwIBARqBlkxpbWl0ZWQgTGlhYmlsaXR5LCByZWFk
IHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFy
dHNzbC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0
c3NsLmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9j
cnR1My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2Nz
cC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNV
HRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBAGC/
jEVdmoMpI62c85Vuo6HVuuPujFFpViTs3QwkbvH1j/CQ7eLBHCLNUtwLVsD4P9GDIWKVfHoh
BYTrcZ7a275jjDlCgdjC5QVC4Fm7G9mk5rfKR2A+UFBoEzyb4h6fSyTA2CBqLMBf09z+wwuk
/eOQ7WJIXhqDLivkR37gbXSY/lfTM7eBDCr1SPgX21f7nyRT58zU/xKH4FhHiv+RJsoTe1Zw
xopuVY8bBfSdgPbol7tBv65f8nmUKCjMGsddBarw33yKSUBJ/am/7fY6LV0SOYxSACb8nb5i
bFojTb5z4fpAfz4XdFSMKJGD1epQ2Nys2udMWeb+IwxkAOS2xc8wggfiMIIFyqADAgECAgEP
MA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQu
MSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQD
EyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAzMzJaFw0x
MjEwMjIyMTAzMzJaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEr
MCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMv
U3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC5o0luEj4gypQIp71Xi2TlXyLYrj9WkRy+d9BO
0FHPYnAsC99/jx/ibNRwIfAoFhZd+LDscdRSckvwuFSz0bKg3z+9o7cwlVAC9AwMWe8IM0Lx
c+8etYxsX4WIamG9fjzzi5GAW5ESKzzIN3SxHSplyGCWFwx/pgf1f4y6O9/ym+4f6zaDYP6B
x0r+SaJcr6eSGNm7X3EwX1v7XpRBY+aw019o7k72d0IX910F+XGt0OwNdM61Ff3FiTiexeUZ
bWxCGm6GZl+SQVG9xYVIgHQaLXoQF+g2wzrmKCbVcZhqH+hrlRnD6PfCuEyX/BR6PlAPRDlQ
6f1u3wqik+LF5P15AgMBAAGjggNbMIIDVzAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIBpjAd
BgNVHQ4EFgQUe4mckpckoYRHAst0/C70rNwy5fMwgagGA1UdIwSBoDCBnYAUTgvvGqRAW6UX
aYcwyjRoQ9BBrvKhgYGkfzB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEpMCcGA1UE
AxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHmCAQEwCQYDVR0SBAIwADA9Bggr
BgEFBQcBAQQxMC8wLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNydDBgBgNVHR8EWTBXMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2Et
Y3JsLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIIBXQYD
VR0gBIIBVDCCAVAwggFMBgsrBgEEAYG1NwEBBDCCATswLwYIKwYBBQUHAgEWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5z
dGFydGNvbS5vcmcvaW50ZXJtZWRpYXRlLnBkZjCB0AYIKwYBBQUHAgIwgcMwJxYgU3RhcnQg
Q29tbWVyY2lhbCAoU3RhcnRDb20pIEx0ZC4wAwIBARqBl0xpbWl0ZWQgTGlhYmlsaXR5LCBy
ZWFkIHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENl
cnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQu
c3RhcnRjb20ub3JnL3BvbGljeS5wZGYwEQYJYIZIAYb4QgEBBAQDAgAHMFAGCWCGSAGG+EIB
DQRDFkFTdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIEZyZWUgU1NMIEVt
YWlsIENlcnRpZmljYXRlczANBgkqhkiG9w0BAQUFAAOCAgEAUpcEDdsKFRCxFBxcSm+8oMTT
fpS7fbZkxWHx5fHDjvAgaBQ+oY0tk4xtbD6VxeHYjxI63+hj8jICnqeVXPe34Bu+XzekIn2T
lrnPCQobKdQF2p52QgUvIxSURed0jcBaCBV22DSKaUqDOzD/Tx6VQy78zpblXjRH7OALE/+H
jzJVmspdnBUUtQOLYgPo924xkxR25VDdgtEE5vAXa/g2oCeZhy0ZEO4NbgIayAYCJcJRDz0h
dD2Ahec65Kw6LB3N7VXEjiRR5/WoKwH/QteRzPJbFDc1somrApjm2cyg+5nbm1RHeFIz+GxX
luRrPztvhNcby0PtAjqwY1txi4sW0R6ZJPuZ2DZ1/dzckoFhyZgFyOX3SEkNXVLldjTzneFJ
FnVSzDbc720vq184jR7pYoI9+f5QJ96a0iLxEAG8SJ5auBwXI/w2FmKmwmdMvJ8/17+B4sMC
IRrXrDQl2xzpVXh/Qcmk5nf+w8HFmqATGy1OUAQbXga7AySAUaYhvvFk50u0bO5DiUGwzrJO
3TrwvaC2Ei4EFaBmIVgG7TfU5TaaY9IcJSCQ7AGUYE3RFSRpsLOoA3DsxP42YERgS/Nxw29+
YqZtPoO2QPbNpI7xnHVCfNBabx3oDIf438nFfv8spw5BQqBSbEF1izJA57eE64CzHnt7lB20
OFD11avYopwxggPKMIIDxgIBATCBkjCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBAgFVMAkGBSsOAwIaBQCgggIMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTEwMDUwNTIxNDkxNVowIwYJKoZIhvcNAQkEMRYEFK8djAHmpjjL9wLnnRdY
Hh/na5i7MF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBowYJ
KwYBBAGCNxAEMYGVMIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UE
AxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAVUw
gaUGCyqGSIb3DQEJEAILMYGVoIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQg
Q0ECAVUwDQYJKoZIhvcNAQEBBQAEggEAbzDVEoVxw481TB1N37JdRRBgVBFIbpKBt6e107iJ
v61j3oHlMV71IyQZlemNOUNR3KK26GuYuciC6MnuxtOcbp0lzKf1T/lQOt4m9NP2+Mj+1NLW
iR9CP1zaH8ldptEWpskgYbJcIQkpPx5t0Crm38VJh+VqvuvEvrQLrcBP+NQ5LIAG5wpbB7pg
1uXLuLjroEp1rYQWUl5YqMFHjHT9n2DCccnotdgmfXcaGF3bs2GTA3LgAG2En9lLj1I3rKIr
9PbPnFYCKM1c3Rb118HpTO2yMCQNKI12j8N9v06qjGtkpiwAdOOfbvKr9AhkxkI+qQAnxGW2
1Cz7rgIK9E2gwgAAAAAAAA==
--------------ms070007010804030505000707--

From A.Hoenes@TR-Sys.de  Thu May  6 11:22:36 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A705128C159 for <urn@core3.amsl.com>; Thu,  6 May 2010 11:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.307
X-Spam-Level: 
X-Spam-Status: No, score=-94.307 tagged_above=-999 required=5 tests=[AWL=-1.657, BAYES_99=3.5, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xxr5g4Gs7cIl for <urn@core3.amsl.com>; Thu,  6 May 2010 11:22:35 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 0CD1328C16B for <urn@ietf.org>; Thu,  6 May 2010 11:21:02 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA020420008; Thu, 6 May 2010 20:20:08 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id UAA25600; Thu, 6 May 2010 20:20:06 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201005061820.UAA25600@TR-Sys.de>
To: moore@network-heretics.com
Date: Thu, 6 May 2010 20:20:06 +0200 (MESZ)
In-Reply-To: <4BD9F303.6080103@network-heretics.com> from Keith Moore at Apr "29, " 2010 "04:58:43" pm
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Cc: urn@ietf.org
Subject: Re: [urn] Focus of the discussion
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 06 May 2010 18:22:36 -0000

Keith,
thanks again for your feedback.

> I am strongly of the opinion that the WG MUST be constrained from
> attempting to change the intent of the original URN specifications; or
> for that matter the specifications themselves except as necessary to
> clarify, correct errata, and reconcile apparent differences with other
> standards.

Are there indications in the first draft charter or in the initial
2141bis draft that have lead you to the conclusion somebody seriously
wanted to try to change URN fundamentals?
If you feel so, please tell us the details so that these can be adjusted.


> History suggests that discussions about naming are very contentious.
> They seem to bring people out of the woodwork who want this kind of name
> to serve whatever purpose they hope to serve, whether or not that is the
> intent behind that kind of name.  We had that problem with the original
> URN discussions.  We also had that problem with discussions around
> "human friendly names" and similar ideas.  To some degree we've even had
> that problems with discussions of URLs, and there is a long history of
> contention on use of DNS names.

The origin of this effort stems from custodians of cultural legacy, most
of them working directly for national libraries, and a few supporting
folks, including me -- in a role you might circumscribe as an inofficial
liaison to the IETF.  Some people contemporarily regard such folks as
overly conservative; but at least, they are not renowned as followers
of apparently short-lived hypes.
So far, I did not see any indication in the messages from PersID
that a fundamental shift in paradigm would even be considered.

The goal clearly is a revised set of documents compatible with
existing standards and matching the requirements of an evolving
distributed, international, URN resolution system for unambiguous
specifications, lying the foundation for interoperable implementations
of resolution services, and for future improved namespace definitions
that support these goals.
I hoped that would be clear from the submitted text.

>
> The battle for control of URNs needs to not be revisited.   Those
> decisions have already been made, and they were hard fought.  People who
> want URNs to be something significantly different than they were
> originally specified to be need to go elsewhere, or start from scratch
> to convince the community that a new kind of name is needed.  This is
> especially important to preserve the persistence qualities of URNs.

In a recent contribution to this list, it has been clarified that,
basically, URNs are the URIs of the 'urn' URI scheme -- nothing more
and nothing less -- and that each URI scheme has its specific set of
rules beyond the general rules in the URI standard.
The fact that this needed to be stated seems to be a dedicated,
a-posteriori justification for having (for the first time!) a formal
specification for the 'urn' URI scheme in the 2141bis draft, as you
can find instantiated in the -00 version.
Of course, the details of the draft are subject to WG discussion,
(but comments are welcome as well before WG formation); however,
the primary goal now is discussing, and eventually arriving at
consensus for, a WG charter.

>
> This needs to be made very clear in the group's charter, and right now
> there's not even a hint of that.
>
> Keith

Again: Do you see a hint to the contrary?  Where?

The proposed draft charter lists major goals.
Changing more fundamental things is not even mentioned there.
IMO, it is implied by the intent and practice of WG charters that
details are to be worked out in the WG, but that the WG is not
endowed to leave the grounds of what is written in the charter.

Where do you derive from the idea that this text would task the
proposed WG with tackling such work?  We are used to specify in the
charter the working plan of a WG, and not what the WG is _not_
planning -- otherwise we would quickly arrive at unreadable charters
of unbounded size.  When a WG wants to go beyond its charter, the
rules require re-chartering.  We currently are defining the tasks of
the WG; the first cut has been posted, and it does specify detailed
goals.

So once again (and this is directed to all readers of this list!),
please quote text parts you do not concur with or that you would like
to be amended, and supply text proposals for additions and/or changes,
if you believe they should be applied.
On the other hand, please feel free to state explicit support of the
current text or parts of it.


Kind regards,
  Alfred.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+


From moore@network-heretics.com  Thu May  6 11:36:01 2010
Return-Path: <moore@network-heretics.com>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 643723A6B96 for <urn@core3.amsl.com>; Thu,  6 May 2010 11:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.029
X-Spam-Level: 
X-Spam-Status: No, score=0.029 tagged_above=-999 required=5 tests=[AWL=-0.273,  BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9B4XUG4z-9TR for <urn@core3.amsl.com>; Thu,  6 May 2010 11:35:59 -0700 (PDT)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id 18AD03A6B73 for <urn@ietf.org>; Thu,  6 May 2010 11:35:59 -0700 (PDT)
Received: from lust.indecency.org (173-137-202-238.pools.spcsdns.net [173.137.202.238]) by m1.imap-partners.net (MOS 4.1.8-GA) with ESMTP id BRR95652 (AUTH admin@network-heretics.com); Thu, 6 May 2010 11:35:38 -0700
X-Mirapoint-Received-SPF: 173.137.202.238 lust.indecency.org <moore@network-heretics.com> 5 none
X-Mirapoint-Received-SPF: 173.137.202.238 lust.indecency.org <moore@network-heretics.com> 5 none
X-Mirapoint-Received-SPF: 173.137.202.238 lust.indecency.org <moore@network-heretics.com> 5 none
Message-ID: <4BE30BFA.5060606@network-heretics.com>
Date: Thu, 06 May 2010 14:35:38 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: =?UTF-8?B?QWxmcmVkIO+/vQ==?= <ah@TR-Sys.de>
References: <201005061820.UAA25600@TR-Sys.de>
In-Reply-To: <201005061820.UAA25600@TR-Sys.de>
Content-Type: multipart/alternative; boundary="------------070202000305060706030405"
Cc: urn@ietf.org
Subject: Re: [urn] Focus of the discussion
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 06 May 2010 18:36:01 -0000

This is a multi-part message in MIME format.
--------------070202000305060706030405
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Alfred,

You are missing my point.  It doesn't matter that the charter doesn't
say anything about changing URN fundamentals.  Nor does it matter that
the people who are pushing for this WG aren't interested in changing URN
fundamentals.  Once an IETF working group is formed, anyone can
participate in it, and the chair is bound to honor group consensus. 
Unless the charter expressly forbids changing URN fundamentals, it's
going to be impossible to keep the discussion on target for the group's
intended scope.  (Even with a "big stick" in the charter, it's likely to
be difficult.) 

Furthermore, IESG has sometimes had difficulty pushing back on groups
that exceed their mandate, unless the output of the group is clearly
outside of the bounds of the charter.

The best time to fight scope creep is before the group is actually
chartered.

Keith
> Keith,
> thanks again for your feedback.
>
>> I am strongly of the opinion that the WG MUST be constrained from
>> attempting to change the intent of the original URN specifications; or
>> for that matter the specifications themselves except as necessary to
>> clarify, correct errata, and reconcile apparent differences with other
>> standards.
>
> Are there indications in the first draft charter or in the initial
> 2141bis draft that have lead you to the conclusion somebody seriously
> wanted to try to change URN fundamentals?
> If you feel so, please tell us the details so that these can be adjusted.
>
>
>> History suggests that discussions about naming are very contentious.
>> They seem to bring people out of the woodwork who want this kind of name
>> to serve whatever purpose they hope to serve, whether or not that is the
>> intent behind that kind of name.  We had that problem with the original
>> URN discussions.  We also had that problem with discussions around
>> "human friendly names" and similar ideas.  To some degree we've even had
>> that problems with discussions of URLs, and there is a long history of
>> contention on use of DNS names.
>
> The origin of this effort stems from custodians of cultural legacy, most
> of them working directly for national libraries, and a few supporting
> folks, including me -- in a role you might circumscribe as an inofficial
> liaison to the IETF.  Some people contemporarily regard such folks as
> overly conservative; but at least, they are not renowned as followers
> of apparently short-lived hypes.
> So far, I did not see any indication in the messages from PersID
> that a fundamental shift in paradigm would even be considered.
>
> The goal clearly is a revised set of documents compatible with
> existing standards and matching the requirements of an evolving
> distributed, international, URN resolution system for unambiguous
> specifications, lying the foundation for interoperable implementations
> of resolution services, and for future improved namespace definitions
> that support these goals.
> I hoped that would be clear from the submitted text.
>
>>
>> The battle for control of URNs needs to not be revisited.   Those
>> decisions have already been made, and they were hard fought.  People who
>> want URNs to be something significantly different than they were
>> originally specified to be need to go elsewhere, or start from scratch
>> to convince the community that a new kind of name is needed.  This is
>> especially important to preserve the persistence qualities of URNs.
>
> In a recent contribution to this list, it has been clarified that,
> basically, URNs are the URIs of the 'urn' URI scheme -- nothing more
> and nothing less -- and that each URI scheme has its specific set of
> rules beyond the general rules in the URI standard.
> The fact that this needed to be stated seems to be a dedicated,
> a-posteriori justification for having (for the first time!) a formal
> specification for the 'urn' URI scheme in the 2141bis draft, as you
> can find instantiated in the -00 version.
> Of course, the details of the draft are subject to WG discussion,
> (but comments are welcome as well before WG formation); however,
> the primary goal now is discussing, and eventually arriving at
> consensus for, a WG charter.
>
>>
>> This needs to be made very clear in the group's charter, and right now
>> there's not even a hint of that.
>>
>> Keith
>
> Again: Do you see a hint to the contrary?  Where?
>
> The proposed draft charter lists major goals.
> Changing more fundamental things is not even mentioned there.
> IMO, it is implied by the intent and practice of WG charters that
> details are to be worked out in the WG, but that the WG is not
> endowed to leave the grounds of what is written in the charter.
>
> Where do you derive from the idea that this text would task the
> proposed WG with tackling such work?  We are used to specify in the
> charter the working plan of a WG, and not what the WG is _not_
> planning -- otherwise we would quickly arrive at unreadable charters
> of unbounded size.  When a WG wants to go beyond its charter, the
> rules require re-chartering.  We currently are defining the tasks of
> the WG; the first cut has been posted, and it does specify detailed
> goals.
>
> So once again (and this is directed to all readers of this list!),
> please quote text parts you do not concur with or that you would like
> to be amended, and supply text proposals for additions and/or changes,
> if you believe they should be applied.
> On the other hand, please feel free to state explicit support of the
> current text or parts of it.
>
>
> Kind regards,
>   Alfred.
>

--------------070202000305060706030405
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Alfred,<br>
<br>
You are missing my point.  It doesn't matter that the charter doesn't
say anything about changing URN fundamentals.  Nor does it matter that
the people who are pushing for this WG aren't interested in changing
URN fundamentals.  Once an IETF working group is formed, anyone can
participate in it, and the chair is bound to honor group consensus. 
Unless the charter expressly forbids changing URN fundamentals, it's
going to be impossible to keep the discussion on target for the group's
intended scope.  (Even with a "big stick" in the charter, it's likely
to be difficult.)  <br>
<br>
Furthermore, IESG has sometimes had difficulty pushing back on groups
that exceed their mandate, unless the output of the group is clearly
outside of the bounds of the charter.<br>
<br>
The best time to fight scope creep is before the group is actually
chartered.<br>
<br>
Keith<br>
<blockquote cite="mid:201005061820.UAA25600@TR-Sys.de" type="cite">
  <pre wrap=""><font face="courier">Keith,
thanks again for your feedback.

</font></pre>
  <blockquote type="cite">
    <pre wrap=""><font face="courier">I am strongly of the opinion that the WG MUST be constrained from
attempting to change the intent of the original URN specifications; or
for that matter the specifications themselves except as necessary to
clarify, correct errata, and reconcile apparent differences with other
standards.
</font></pre>
  </blockquote>
  <pre wrap=""><font face="courier">
Are there indications in the first draft charter or in the initial
2141bis draft that have lead you to the conclusion somebody seriously
wanted to try to change URN fundamentals?
If you feel so, please tell us the details so that these can be adjusted.


</font></pre>
  <blockquote type="cite">
    <pre wrap=""><font face="courier">History suggests that discussions about naming are very contentious.
They seem to bring people out of the woodwork who want this kind of name
to serve whatever purpose they hope to serve, whether or not that is the
intent behind that kind of name.  We had that problem with the original
URN discussions.  We also had that problem with discussions around
"human friendly names" and similar ideas.  To some degree we've even had
that problems with discussions of URLs, and there is a long history of
contention on use of DNS names.
</font></pre>
  </blockquote>
  <pre wrap=""><font face="courier">
The origin of this effort stems from custodians of cultural legacy, most
of them working directly for national libraries, and a few supporting
folks, including me -- in a role you might circumscribe as an inofficial
liaison to the IETF.  Some people contemporarily regard such folks as
overly conservative; but at least, they are not renowned as followers
of apparently short-lived hypes.
So far, I did not see any indication in the messages from PersID
that a fundamental shift in paradigm would even be considered.

The goal clearly is a revised set of documents compatible with
existing standards and matching the requirements of an evolving
distributed, international, URN resolution system for unambiguous
specifications, lying the foundation for interoperable implementations
of resolution services, and for future improved namespace definitions
that support these goals.
I hoped that would be clear from the submitted text.

</font></pre>
  <blockquote type="cite">
    <pre wrap=""><font face="courier">
The battle for control of URNs needs to not be revisited.   Those
decisions have already been made, and they were hard fought.  People who
want URNs to be something significantly different than they were
originally specified to be need to go elsewhere, or start from scratch
to convince the community that a new kind of name is needed.  This is
especially important to preserve the persistence qualities of URNs.
</font></pre>
  </blockquote>
  <pre wrap=""><font face="courier">
In a recent contribution to this list, it has been clarified that,
basically, URNs are the URIs of the 'urn' URI scheme -- nothing more
and nothing less -- and that each URI scheme has its specific set of
rules beyond the general rules in the URI standard.
The fact that this needed to be stated seems to be a dedicated,
a-posteriori justification for having (for the first time!) a formal
specification for the 'urn' URI scheme in the 2141bis draft, as you
can find instantiated in the -00 version.
Of course, the details of the draft are subject to WG discussion,
(but comments are welcome as well before WG formation); however,
the primary goal now is discussing, and eventually arriving at
consensus for, a WG charter.

</font></pre>
  <blockquote type="cite">
    <pre wrap=""><font face="courier">
This needs to be made very clear in the group's charter, and right now
there's not even a hint of that.

Keith
</font></pre>
  </blockquote>
  <pre wrap=""><font face="courier">
Again: Do you see a hint to the contrary?  Where?

The proposed draft charter lists major goals.
Changing more fundamental things is not even mentioned there.
IMO, it is implied by the intent and practice of WG charters that
details are to be worked out in the WG, but that the WG is not
endowed to leave the grounds of what is written in the charter.

Where do you derive from the idea that this text would task the
proposed WG with tackling such work?  We are used to specify in the
charter the working plan of a WG, and not what the WG is _not_
planning -- otherwise we would quickly arrive at unreadable charters
of unbounded size.  When a WG wants to go beyond its charter, the
rules require re-chartering.  We currently are defining the tasks of
the WG; the first cut has been posted, and it does specify detailed
goals.

So once again (and this is directed to all readers of this list!),
please quote text parts you do not concur with or that you would like
to be amended, and supply text proposals for additions and/or changes,
if you believe they should be applied.
On the other hand, please feel free to state explicit support of the
current text or parts of it.


Kind regards,
  Alfred.

</font></pre>
</blockquote>
</body>
</html>

--------------070202000305060706030405--

From stpeter@stpeter.im  Wed May 12 14:56:13 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFF423A6990 for <urn@core3.amsl.com>; Wed, 12 May 2010 14:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[AWL=0.690,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9NxG6xt5olG8 for <urn@core3.amsl.com>; Wed, 12 May 2010 14:56:12 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 750783A6956 for <urn@ietf.org>; Wed, 12 May 2010 14:56:12 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id AE7D740D06; Wed, 12 May 2010 15:56:01 -0600 (MDT)
Message-ID: <4BEB23EF.4040804@stpeter.im>
Date: Wed, 12 May 2010 15:55:59 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
References: <201004280802.KAA11778@TR-Sys.de>	<4BD83069.6060407@gmx.de>	<4BD83B51.7010100@renci.org>	<4BD83F7D.1050100@network-heretics.com>	<4BD845CD.4060100@renci.org>	<4BD847A2.8090204@network-heretics.com>	<4BD84969.9000109@renci.org>	<4BD86147.3030401@network-heretics.com>	<4BD863CA.3050004@renci.org>	<4BD8772D.7080601@network-heretics.com>	<4BD87BEA.9070309@renci.org> <4BD888C7.5080801@network-heretics.com>
In-Reply-To: <4BD888C7.5080801@network-heretics.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040402010402060303060701"
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] fragment identifiers, Re:  rfc2141bis [was: Re: A first cut at the Draft Charter ...]
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 May 2010 21:56:13 -0000

This is a cryptographically signed message in MIME format.

--------------ms040402010402060303060701
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 4/28/10 1:13 PM, Keith Moore wrote (in reply to Xiaoshu Wang):

>> But isn't it because things does not work well that this URN mailing
>> list is created?
>
> I have yet to understand the specific reasons why this list was created=
,
> other than to clean up a few very technical ambiguities and errata in
> the existing URN specifications and in how they relate to other
> specifications.   I'm not aware that these technical ambiguities or
> errata have caused any significant operational problems, though of
> course they might have.

That is my impression as well. Anyone who has a broader notion of our
work here had better speak up, because we need to be very clear on our
purpose from the beginning.

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms040402010402060303060701
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIWnDCC
B1cwggY/oAMCAQICAVUwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBT
aWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQTAeFw0wOTA3MDYwMDAwMDFaFw0xMDA3MDYyMzU5NTlaMIHCMQswCQYDVQQG
EwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRlbnZlcjEiMCAGA1UEChMZWE1Q
UCBTdGFuZGFyZHMgRm91bmRhdGlvbjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0
aWZpY2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcN
AQkBFhJzdHBldGVyQHN0cGV0ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQCas7Mrnh02GakN8sft+HJpU4MwBxEgrGDZ2ZzUxDDt2sEhM+9Q74h955MtgMhK3TeBf6Hs
hDh/8Z9G//k2qNA0M2S5rejTqrmW0Jabca/L7BUZ0GhnU2N/2zeciFUmuZ4A2l1T5IMX2ZVP
XnNIaefBtbImJAbDz3T0vxkzTtcqgW3wL83PMDiqiuM+e1k+VPvOW4f5ZSGkPIhYCDpWqNE5
wZvjrLNMc8jZOPs9DrsYuIVwU72Vhy1tkEh+w6YpYHrdEUAe+eKe6TuxqZ60e9z3O36uiV//
Ms274iD6PbA/IGazJgaAdg6tvPehwTYGJAGmv3PsJKkLGjgoh+RrrM1LAgMBAAGjggOKMIID
hjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFOyws3XWgIY9FP1POVqjdZP9Lu38MB0GA1UdEQQWMBSBEnN0cGV0ZXJA
c3RwZXRlci5pbTCBqAYDVR0jBIGgMIGdgBR7iZySlyShhEcCy3T8LvSs3DLl86GBgaR/MH0x
CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg
RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eYIBDzCCAUcGA1UdIASCAT4wggE6MIIBNgYLKwYBBAGBtTcBAgAw
ggElMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQG
CCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMIG8
BggrBgEFBQcCAjCBrzAUFg1TdGFydENvbSBMdGQuMAMCAQEagZZMaW1pdGVkIExpYWJpbGl0
eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRoZSBTdGFydENv
bSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwYwYDVR0fBFwwWjAroCmgJ4YlaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vY3J0dTMtY3JsLmNybDAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNz
bC5jb20vY3J0dTMtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0
cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczMvY2xpZW50L2NhMEIGCCsGAQUFBzAC
hjZodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MzLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUA
A4IBAQBgv4xFXZqDKSOtnPOVbqOh1brj7oxRaVYk7N0MJG7x9Y/wkO3iwRwizVLcC1bA+D/R
gyFilXx6IQWE63Ge2tu+Y4w5QoHYwuUFQuBZuxvZpOa3ykdgPlBQaBM8m+Ien0skwNggaizA
X9Pc/sMLpP3jkO1iSF4agy4r5Ed+4G10mP5X0zO3gQwq9Uj4F9tX+58kU+fM1P8Sh+BYR4r/
kSbKE3tWcMaKblWPGwX0nYD26Je7Qb+uX/J5lCgozBrHXQWq8N98iklASf2pv+32Oi1dEjmM
UgAm/J2+YmxaI02+c+H6QH8+F3RUjCiRg9XqUNjcrNrnTFnm/iMMZADktsXPMIIHVzCCBj+g
AwIBAgIBVTANBgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBMB4XDTA5MDcwNjAwMDAwMVoXDTEwMDcwNjIzNTk1OVowgcIxCzAJBgNVBAYTAlVTMREw
DwYDVQQIEwhDb2xvcmFkbzEPMA0GA1UEBxMGRGVudmVyMSIwIAYDVQQKExlYTVBQIFN0YW5k
YXJkcyBGb3VuZGF0aW9uMSwwKgYDVQQLEyNTdGFydENvbSBUcnVzdGVkIENlcnRpZmljYXRl
IE1lbWJlcjEaMBgGA1UEAxMRUGV0ZXIgU2FpbnQtQW5kcmUxITAfBgkqhkiG9w0BCQEWEnN0
cGV0ZXJAc3RwZXRlci5pbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJqzsyue
HTYZqQ3yx+34cmlTgzAHESCsYNnZnNTEMO3awSEz71DviH3nky2AyErdN4F/oeyEOH/xn0b/
+Tao0DQzZLmt6NOquZbQlptxr8vsFRnQaGdTY3/bN5yIVSa5ngDaXVPkgxfZlU9ec0hp58G1
siYkBsPPdPS/GTNO1yqBbfAvzc8wOKqK4z57WT5U+85bh/llIaQ8iFgIOlao0TnBm+Oss0xz
yNk4+z0Ouxi4hXBTvZWHLW2QSH7Dpilget0RQB754p7pO7GpnrR73Pc7fq6JX/8yzbviIPo9
sD8gZrMmBoB2Dq2896HBNgYkAaa/c+wkqQsaOCiH5GuszUsCAwEAAaOCA4owggOGMAkGA1Ud
EwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV
HQ4EFgQU7LCzddaAhj0U/U85WqN1k/0u7fwwHQYDVR0RBBYwFIESc3RwZXRlckBzdHBldGVy
LmltMIGoBgNVHSMEgaAwgZ2AFHuJnJKXJKGERwLLdPwu9KzcMuXzoYGBpH8wfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5ggEPMIIBRwYDVR0gBIIBPjCCATowggE2BgsrBgEEAYG1NwECADCCASUwLgYI
KwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUH
AgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgbwGCCsGAQUF
BwICMIGvMBQWDVN0YXJ0Q29tIEx0ZC4wAwIBARqBlkxpbWl0ZWQgTGlhYmlsaXR5LCByZWFk
IHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFy
dHNzbC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0
c3NsLmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9j
cnR1My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2Nz
cC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNV
HRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBAGC/
jEVdmoMpI62c85Vuo6HVuuPujFFpViTs3QwkbvH1j/CQ7eLBHCLNUtwLVsD4P9GDIWKVfHoh
BYTrcZ7a275jjDlCgdjC5QVC4Fm7G9mk5rfKR2A+UFBoEzyb4h6fSyTA2CBqLMBf09z+wwuk
/eOQ7WJIXhqDLivkR37gbXSY/lfTM7eBDCr1SPgX21f7nyRT58zU/xKH4FhHiv+RJsoTe1Zw
xopuVY8bBfSdgPbol7tBv65f8nmUKCjMGsddBarw33yKSUBJ/am/7fY6LV0SOYxSACb8nb5i
bFojTb5z4fpAfz4XdFSMKJGD1epQ2Nys2udMWeb+IwxkAOS2xc8wggfiMIIFyqADAgECAgEP
MA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQu
MSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQD
EyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAzMzJaFw0x
MjEwMjIyMTAzMzJaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEr
MCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMv
U3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC5o0luEj4gypQIp71Xi2TlXyLYrj9WkRy+d9BO
0FHPYnAsC99/jx/ibNRwIfAoFhZd+LDscdRSckvwuFSz0bKg3z+9o7cwlVAC9AwMWe8IM0Lx
c+8etYxsX4WIamG9fjzzi5GAW5ESKzzIN3SxHSplyGCWFwx/pgf1f4y6O9/ym+4f6zaDYP6B
x0r+SaJcr6eSGNm7X3EwX1v7XpRBY+aw019o7k72d0IX910F+XGt0OwNdM61Ff3FiTiexeUZ
bWxCGm6GZl+SQVG9xYVIgHQaLXoQF+g2wzrmKCbVcZhqH+hrlRnD6PfCuEyX/BR6PlAPRDlQ
6f1u3wqik+LF5P15AgMBAAGjggNbMIIDVzAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIBpjAd
BgNVHQ4EFgQUe4mckpckoYRHAst0/C70rNwy5fMwgagGA1UdIwSBoDCBnYAUTgvvGqRAW6UX
aYcwyjRoQ9BBrvKhgYGkfzB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEpMCcGA1UE
AxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHmCAQEwCQYDVR0SBAIwADA9Bggr
BgEFBQcBAQQxMC8wLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNydDBgBgNVHR8EWTBXMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2Et
Y3JsLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIIBXQYD
VR0gBIIBVDCCAVAwggFMBgsrBgEEAYG1NwEBBDCCATswLwYIKwYBBQUHAgEWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5z
dGFydGNvbS5vcmcvaW50ZXJtZWRpYXRlLnBkZjCB0AYIKwYBBQUHAgIwgcMwJxYgU3RhcnQg
Q29tbWVyY2lhbCAoU3RhcnRDb20pIEx0ZC4wAwIBARqBl0xpbWl0ZWQgTGlhYmlsaXR5LCBy
ZWFkIHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENl
cnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQu
c3RhcnRjb20ub3JnL3BvbGljeS5wZGYwEQYJYIZIAYb4QgEBBAQDAgAHMFAGCWCGSAGG+EIB
DQRDFkFTdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIEZyZWUgU1NMIEVt
YWlsIENlcnRpZmljYXRlczANBgkqhkiG9w0BAQUFAAOCAgEAUpcEDdsKFRCxFBxcSm+8oMTT
fpS7fbZkxWHx5fHDjvAgaBQ+oY0tk4xtbD6VxeHYjxI63+hj8jICnqeVXPe34Bu+XzekIn2T
lrnPCQobKdQF2p52QgUvIxSURed0jcBaCBV22DSKaUqDOzD/Tx6VQy78zpblXjRH7OALE/+H
jzJVmspdnBUUtQOLYgPo924xkxR25VDdgtEE5vAXa/g2oCeZhy0ZEO4NbgIayAYCJcJRDz0h
dD2Ahec65Kw6LB3N7VXEjiRR5/WoKwH/QteRzPJbFDc1somrApjm2cyg+5nbm1RHeFIz+GxX
luRrPztvhNcby0PtAjqwY1txi4sW0R6ZJPuZ2DZ1/dzckoFhyZgFyOX3SEkNXVLldjTzneFJ
FnVSzDbc720vq184jR7pYoI9+f5QJ96a0iLxEAG8SJ5auBwXI/w2FmKmwmdMvJ8/17+B4sMC
IRrXrDQl2xzpVXh/Qcmk5nf+w8HFmqATGy1OUAQbXga7AySAUaYhvvFk50u0bO5DiUGwzrJO
3TrwvaC2Ei4EFaBmIVgG7TfU5TaaY9IcJSCQ7AGUYE3RFSRpsLOoA3DsxP42YERgS/Nxw29+
YqZtPoO2QPbNpI7xnHVCfNBabx3oDIf438nFfv8spw5BQqBSbEF1izJA57eE64CzHnt7lB20
OFD11avYopwxggPKMIIDxgIBATCBkjCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBAgFVMAkGBSsOAwIaBQCgggIMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTEwMDUxMjIxNTU1OVowIwYJKoZIhvcNAQkEMRYEFP0xjjv+E0Kf/iOK7UPr
7iziI+gXMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBowYJ
KwYBBAGCNxAEMYGVMIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UE
AxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAVUw
gaUGCyqGSIb3DQEJEAILMYGVoIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQg
Q0ECAVUwDQYJKoZIhvcNAQEBBQAEggEAFCoq8Rf5jbRTVJEozCQ2I6Zk3YDb+dKmjPlLH6tt
/oA2/toRVpx7jivCqMJ6oNQ8d21FAblvsH4yMjOVik7huyQv4Aji13uKPtrFrQSx5v9TSyX6
nWKdogxaEK3W81uHzYBknOviL1+/QmeelHkuT6KZhwGDVOI5C2SeizCjYsu17WcaCXch6jkT
KEpQA+hZ397HXOknvspzIYoSWCbWn1l+TJD3auevC5epeWjAht5T4+b3NWThVw3V9G0LkP/B
mVFpWwMofKsdVoIAAdSVcIQsMpz6KtoOr2YUZEWL+XMvD96HUF6sr27mrnptY79w3PgGI2EV
Exy0NVhVFH82xAAAAAAAAA==
--------------ms040402010402060303060701--

From stpeter@stpeter.im  Wed May 12 15:23:29 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63CAB3A6802 for <urn@core3.amsl.com>; Wed, 12 May 2010 15:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.078
X-Spam-Level: 
X-Spam-Status: No, score=-0.078 tagged_above=-999 required=5 tests=[AWL=-1.294, BAYES_50=0.001, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YvtMiz0Ee+TL for <urn@core3.amsl.com>; Wed, 12 May 2010 15:23:27 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id CE4FD3A69B1 for <urn@ietf.org>; Wed, 12 May 2010 15:23:08 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9A6AB40D06; Wed, 12 May 2010 16:22:57 -0600 (MDT)
Message-ID: <4BEB2A3F.1090309@stpeter.im>
Date: Wed, 12 May 2010 16:22:55 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: =?UTF-8?B?QWxmcmVkIO+/vQ==?= <ah@TR-Sys.de>
References: <201004271705.TAA10987@TR-Sys.de>
In-Reply-To: <201004271705.TAA10987@TR-Sys.de>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020903000300050006080903"
Cc: urn@ietf.org
Subject: Re: [urn] A first cut at the Draft Charter for the proposed URNbis WG
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 May 2010 22:23:29 -0000

This is a cryptographically signed message in MIME format.

--------------ms020903000300050006080903
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Alfred,

Here is some feedback on the proposed charter. My apologies for the delay=
=2E

In general, RFC 5434 will give you plenty of good ideas about
formulating a charter. It is especially important to clearly define the
problem statement.

On 4/27/10 11:05 AM, Alfred =EF=BF=BD wrote:
> Folks,
> Based on work done by Juha Hakala in February, I have updated
> and amended the Draft Charter and hereby bring it to the urn list
> for discussion.   Comments welcome!
>=20
> Kind regards,
>   Alfred H=EF=BF=BDnes.
>=20
>=20
> ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
>=20
> Uniform Resource Names, Revised (URNbis) -- Draft Proposed WG Charter
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Last Modified:  2010-04-26 [AH]
>=20
> Chair(s):
>   o   Juha Hakala  <juha.hakala@helsinki.fi>
>   o   N.N.

The chairs will be chosen by the Area Directors. I agree that Juha is a
good candidate, but please leave this blank for now.

> Applications Area Director(s):
>   o   Alexey Melnikov  <alexey.melnikov@isode.com>
>   o   Peter Saint-Andre  <stpeter@stpeter.im>
>=20
> Applications Area Advisor:
>   o   Peter Saint-Andre  <stpeter@stpeter.im>

We don't yet know if which AD will be the advisor, so please leave this
blank.

> Mailing Lists:
>   General Discussion: urn@ietf.org
>   To Subscribe: https://www.ietf.org/mailman/listinfo/urn
>   Archive: http://www.ietf.org/mail-archive/web/urn/current/maillist.ht=
ml
>=20
>   Related lists (used for IANA registration procedures (BCP 35/66):
>     urn-nid@ietf.org, uri-review@ietf.org
>=20
> Additional information will be available at:
>   http://tools.ietf.org/wg/urnbis

Not yet assigned, so please leave this blank.

In fact you can delete everything up to this point because it's
administrivia. :)

> Description of Working Group:
>=20
>   Uniform Resource Names (URNs) are persistent identifiers for
>   information resources. =20

RFC 2141 says:

   Uniform Resource Names (URNs) are intended to serve as persistent,
   location-independent, resource identifiers.

I think the "location-independent" part is important so people don't
think that URNs exist for the purpose of resolving a URN into a location
where the representation of a resource can be retrieved.

> The RFCs defining URNs and services based on
>   them were published 1997-2001.  Since then, the URN system has gained=


Are URNs really a "system"?

>   popularity.  Among the more traditional parties with deep interest in=

>   persistent identifiers and making heavy use of URNs are national
>   libraries; solely within this area, tens of millions of resources
>   have been assigned URNs; this enables efficient searching of and
>   persistent linking to these documents.
>=20
>   This working group is chartered to revise the key RFCs describing the=

>   URN system, including RFC 2141 (URN Syntax) and RFC 4306 (Namespace
>   Definition Mechanisms),=20

I think we need to be very clear about what kind of revisions we're
talking about here.

> update important URN namespace specifications,

I think we'll want to list these separately and limit the scope of the
WG to only the listed namespace specifications (to be expanded only on
rechartering).

>   and to screen and update RFCs describing URN resolution principles
>   and practices.

Do we really want to take on URN resolution?

>   For RFC 2141, this revision will include in particular: an update of
>   the formal syntax specification in the light of the URI Standard
>   (STD 66, RFC 3986) using the ABNF from STD 68 (RFC 5234), a revision
>   of URN examples from imaginary ones into existing URNs in current
>   namespaces, providing a formal IANA registration for the 'urn' URI
>   scheme using the template from BCP 35 (RFC 4395),=20

Do we have agreement that the URN space is founded in a URI scheme?

> and an update of
>   the section describing how URNs are resolved in the Internet.

By "section" do you mean RFCs 2169 and 2483?

>   RFC 4306 (BCP 66) needs a less pervasive update, mostly to align it
>   with the current IANA procedures and terminology as defined in BCP 26=

>   (RFC 5226).
>=20
>   Regarding URN Namespace specifications, the WG will focus on updates
>   for the definitions of URNs based on bibliographic identifier systems=
,
>   in particular RFC 3187 (URN Namespace for International Standard Book=

>   Numbers) and RFC 3188 (URN Namespace for National Bibliography
>   Numbers).  In both cases, the respective identifier system and/or the=

>   institutions and roles involved in their assignment and resolution
>   have evolved significantly since these RFCs have been published.
>   In particular, the URN:ISBN namespace needs to be extended according
>   to the revision of the international ISBN standard, and the usage of
>   the URN:NBNs has grown rapidly and there is a need to align the
>   namespace registration with experience and current practice.
>   In a second stage, RFC 3044 (URN Namespace for International Series
>   Standard Number) will be checked for the necessity of an update.

Those efforts seem worthwhile, although again we'll want to tightly
scope the work.

>   Thus, in support of the current international efforts to establish a
>   distributed, linked system of URN resolution systems for bibliographi=
c
>   identifiers, the primary aim of the WG is an updated set of standards=

>   documents, which is needed to assure uniformity and interoperability
>   of the URN resolution services.

Is this new work, or revision of existing work?

>   Alongside the modernization of these core RFCs for URNs and specific
>   URN namespaces, the working group will also consider a revision of
>   earlier RFCs related to the principles of URNs and URN resolution,
>   such as RFC 2483 (URI Resolution services necessary for URN
>   resolution), RFC 2276 (Architectural principles of Uniform Resource
>   Name Resolution), RFC 1737 (Functional requirements for Uniform
>   Resource Names) and RFC 2169 (A trivial convention for using HTTP in
>   URN resolution).  All these must be checked; if the document is still=

>   deemed relevant, it will be modernized.

That sounds like a lot of work. Perhaps a phased approach will be needed?=


>   The working group will also consider the possibility of publishing
>   Best Current Practices on how to resolve the URNs utilizing the
>   existing Internet protocols such as HTTP.  This BCP will be based on
>   the European URN resolution infrastructure under construction in the
>   project PersID.

Do we have references or I-Ds about that work? How can the URNbis WG (if
formed) collaborate with the PersID project?

>   Since the revised specifications will be based on existing production=

>   systems and provide important guidelines for future implementers,
>   the WG aims at publishing the RFCs on the Standards Track and will tr=
y
>   to advance the core document at least to Draft Standard status as fas=
t
>   as possible.

What is "the core document"? Do we think it will need to be cycled at
Proposed Standard? If so, let's clarify that. Pushing for Draft Standard
might be premature.

>   The WG can take on work to update other well-established URN namespac=
e
>   definitions upon a case-by-case decision.

Perhaps text like this would be helpful:

   Although the group may provide advice regarding other URN namespaces,
   it will prioritize work on the above-mentioned namespaces first and
   will take on additional tasks as official milestones only after
   rechartering.

I think that if we don't have some text like that, the IESG will be
concerned about the open-ended nature of the charter.

> Input documents:
>=20
>   RFC 2141
>   RFC 3406
>=20
>   RFC 3187
>   RFC 3188
>=20
>   RFC 2483
>   RFC 2276
>   RFC 1737
>   RFC 2169
>=20
> Goals and Milestones (preliminary):
>=20
>   Feb 2010   Initial WG formation as 'URN-R' (outside the IETF)
>   Mar 2010   WG work plan completed, brought to IETF APP Area
>   May 2010   first Internet-Drafts for most important core document
>              revisions
>   Jul 2010   Presentation of the group & early results at IETF 78 (BoF)=

>   Aug 2010   Formal establishment of the IETF WG

Those might be helpful to you, but none of them belong in the milestones
for the WG since they would predate WG formation.

>   Dec 2010   WG Last Call on WG core document set
>   Feb 2011   core document set forwarded to IESG
>       2011   work on supporting documents (guidelines, URN resolution)
>       2012   implementation report for promoting 2141bis to Draft Std.

We don't need to define detailed milestones at this time -- IMHO it is
more important to come to agreement on the problem statement and
deliverables. The milestones will flow from that.

> Internet-Drafts:
>=20
>   draft-ah-rfc2141bis-urn          (-00: March 2010)
>   draft-hakala-rfc3187bis-isbn-urn (-00: March 2010)
>   draft-hakala-rfc3188bis-nbn-urn  (-00 due for week 18/2010)
>=20
> Request For Comments:
>=20
>   none so far

Naturally. :)

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms020903000300050006080903
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIWnDCC
B1cwggY/oAMCAQICAVUwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBT
aWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQTAeFw0wOTA3MDYwMDAwMDFaFw0xMDA3MDYyMzU5NTlaMIHCMQswCQYDVQQG
EwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRlbnZlcjEiMCAGA1UEChMZWE1Q
UCBTdGFuZGFyZHMgRm91bmRhdGlvbjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0
aWZpY2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcN
AQkBFhJzdHBldGVyQHN0cGV0ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQCas7Mrnh02GakN8sft+HJpU4MwBxEgrGDZ2ZzUxDDt2sEhM+9Q74h955MtgMhK3TeBf6Hs
hDh/8Z9G//k2qNA0M2S5rejTqrmW0Jabca/L7BUZ0GhnU2N/2zeciFUmuZ4A2l1T5IMX2ZVP
XnNIaefBtbImJAbDz3T0vxkzTtcqgW3wL83PMDiqiuM+e1k+VPvOW4f5ZSGkPIhYCDpWqNE5
wZvjrLNMc8jZOPs9DrsYuIVwU72Vhy1tkEh+w6YpYHrdEUAe+eKe6TuxqZ60e9z3O36uiV//
Ms274iD6PbA/IGazJgaAdg6tvPehwTYGJAGmv3PsJKkLGjgoh+RrrM1LAgMBAAGjggOKMIID
hjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFOyws3XWgIY9FP1POVqjdZP9Lu38MB0GA1UdEQQWMBSBEnN0cGV0ZXJA
c3RwZXRlci5pbTCBqAYDVR0jBIGgMIGdgBR7iZySlyShhEcCy3T8LvSs3DLl86GBgaR/MH0x
CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg
RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eYIBDzCCAUcGA1UdIASCAT4wggE6MIIBNgYLKwYBBAGBtTcBAgAw
ggElMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQG
CCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMIG8
BggrBgEFBQcCAjCBrzAUFg1TdGFydENvbSBMdGQuMAMCAQEagZZMaW1pdGVkIExpYWJpbGl0
eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRoZSBTdGFydENv
bSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwYwYDVR0fBFwwWjAroCmgJ4YlaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vY3J0dTMtY3JsLmNybDAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNz
bC5jb20vY3J0dTMtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0
cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczMvY2xpZW50L2NhMEIGCCsGAQUFBzAC
hjZodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MzLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUA
A4IBAQBgv4xFXZqDKSOtnPOVbqOh1brj7oxRaVYk7N0MJG7x9Y/wkO3iwRwizVLcC1bA+D/R
gyFilXx6IQWE63Ge2tu+Y4w5QoHYwuUFQuBZuxvZpOa3ykdgPlBQaBM8m+Ien0skwNggaizA
X9Pc/sMLpP3jkO1iSF4agy4r5Ed+4G10mP5X0zO3gQwq9Uj4F9tX+58kU+fM1P8Sh+BYR4r/
kSbKE3tWcMaKblWPGwX0nYD26Je7Qb+uX/J5lCgozBrHXQWq8N98iklASf2pv+32Oi1dEjmM
UgAm/J2+YmxaI02+c+H6QH8+F3RUjCiRg9XqUNjcrNrnTFnm/iMMZADktsXPMIIHVzCCBj+g
AwIBAgIBVTANBgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBMB4XDTA5MDcwNjAwMDAwMVoXDTEwMDcwNjIzNTk1OVowgcIxCzAJBgNVBAYTAlVTMREw
DwYDVQQIEwhDb2xvcmFkbzEPMA0GA1UEBxMGRGVudmVyMSIwIAYDVQQKExlYTVBQIFN0YW5k
YXJkcyBGb3VuZGF0aW9uMSwwKgYDVQQLEyNTdGFydENvbSBUcnVzdGVkIENlcnRpZmljYXRl
IE1lbWJlcjEaMBgGA1UEAxMRUGV0ZXIgU2FpbnQtQW5kcmUxITAfBgkqhkiG9w0BCQEWEnN0
cGV0ZXJAc3RwZXRlci5pbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJqzsyue
HTYZqQ3yx+34cmlTgzAHESCsYNnZnNTEMO3awSEz71DviH3nky2AyErdN4F/oeyEOH/xn0b/
+Tao0DQzZLmt6NOquZbQlptxr8vsFRnQaGdTY3/bN5yIVSa5ngDaXVPkgxfZlU9ec0hp58G1
siYkBsPPdPS/GTNO1yqBbfAvzc8wOKqK4z57WT5U+85bh/llIaQ8iFgIOlao0TnBm+Oss0xz
yNk4+z0Ouxi4hXBTvZWHLW2QSH7Dpilget0RQB754p7pO7GpnrR73Pc7fq6JX/8yzbviIPo9
sD8gZrMmBoB2Dq2896HBNgYkAaa/c+wkqQsaOCiH5GuszUsCAwEAAaOCA4owggOGMAkGA1Ud
EwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV
HQ4EFgQU7LCzddaAhj0U/U85WqN1k/0u7fwwHQYDVR0RBBYwFIESc3RwZXRlckBzdHBldGVy
LmltMIGoBgNVHSMEgaAwgZ2AFHuJnJKXJKGERwLLdPwu9KzcMuXzoYGBpH8wfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5ggEPMIIBRwYDVR0gBIIBPjCCATowggE2BgsrBgEEAYG1NwECADCCASUwLgYI
KwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUH
AgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgbwGCCsGAQUF
BwICMIGvMBQWDVN0YXJ0Q29tIEx0ZC4wAwIBARqBlkxpbWl0ZWQgTGlhYmlsaXR5LCByZWFk
IHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFy
dHNzbC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0
c3NsLmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9j
cnR1My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2Nz
cC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNV
HRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBAGC/
jEVdmoMpI62c85Vuo6HVuuPujFFpViTs3QwkbvH1j/CQ7eLBHCLNUtwLVsD4P9GDIWKVfHoh
BYTrcZ7a275jjDlCgdjC5QVC4Fm7G9mk5rfKR2A+UFBoEzyb4h6fSyTA2CBqLMBf09z+wwuk
/eOQ7WJIXhqDLivkR37gbXSY/lfTM7eBDCr1SPgX21f7nyRT58zU/xKH4FhHiv+RJsoTe1Zw
xopuVY8bBfSdgPbol7tBv65f8nmUKCjMGsddBarw33yKSUBJ/am/7fY6LV0SOYxSACb8nb5i
bFojTb5z4fpAfz4XdFSMKJGD1epQ2Nys2udMWeb+IwxkAOS2xc8wggfiMIIFyqADAgECAgEP
MA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQu
MSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQD
EyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAzMzJaFw0x
MjEwMjIyMTAzMzJaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEr
MCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMv
U3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC5o0luEj4gypQIp71Xi2TlXyLYrj9WkRy+d9BO
0FHPYnAsC99/jx/ibNRwIfAoFhZd+LDscdRSckvwuFSz0bKg3z+9o7cwlVAC9AwMWe8IM0Lx
c+8etYxsX4WIamG9fjzzi5GAW5ESKzzIN3SxHSplyGCWFwx/pgf1f4y6O9/ym+4f6zaDYP6B
x0r+SaJcr6eSGNm7X3EwX1v7XpRBY+aw019o7k72d0IX910F+XGt0OwNdM61Ff3FiTiexeUZ
bWxCGm6GZl+SQVG9xYVIgHQaLXoQF+g2wzrmKCbVcZhqH+hrlRnD6PfCuEyX/BR6PlAPRDlQ
6f1u3wqik+LF5P15AgMBAAGjggNbMIIDVzAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIBpjAd
BgNVHQ4EFgQUe4mckpckoYRHAst0/C70rNwy5fMwgagGA1UdIwSBoDCBnYAUTgvvGqRAW6UX
aYcwyjRoQ9BBrvKhgYGkfzB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEpMCcGA1UE
AxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHmCAQEwCQYDVR0SBAIwADA9Bggr
BgEFBQcBAQQxMC8wLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNydDBgBgNVHR8EWTBXMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2Et
Y3JsLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIIBXQYD
VR0gBIIBVDCCAVAwggFMBgsrBgEEAYG1NwEBBDCCATswLwYIKwYBBQUHAgEWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5z
dGFydGNvbS5vcmcvaW50ZXJtZWRpYXRlLnBkZjCB0AYIKwYBBQUHAgIwgcMwJxYgU3RhcnQg
Q29tbWVyY2lhbCAoU3RhcnRDb20pIEx0ZC4wAwIBARqBl0xpbWl0ZWQgTGlhYmlsaXR5LCBy
ZWFkIHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENl
cnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQu
c3RhcnRjb20ub3JnL3BvbGljeS5wZGYwEQYJYIZIAYb4QgEBBAQDAgAHMFAGCWCGSAGG+EIB
DQRDFkFTdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIEZyZWUgU1NMIEVt
YWlsIENlcnRpZmljYXRlczANBgkqhkiG9w0BAQUFAAOCAgEAUpcEDdsKFRCxFBxcSm+8oMTT
fpS7fbZkxWHx5fHDjvAgaBQ+oY0tk4xtbD6VxeHYjxI63+hj8jICnqeVXPe34Bu+XzekIn2T
lrnPCQobKdQF2p52QgUvIxSURed0jcBaCBV22DSKaUqDOzD/Tx6VQy78zpblXjRH7OALE/+H
jzJVmspdnBUUtQOLYgPo924xkxR25VDdgtEE5vAXa/g2oCeZhy0ZEO4NbgIayAYCJcJRDz0h
dD2Ahec65Kw6LB3N7VXEjiRR5/WoKwH/QteRzPJbFDc1somrApjm2cyg+5nbm1RHeFIz+GxX
luRrPztvhNcby0PtAjqwY1txi4sW0R6ZJPuZ2DZ1/dzckoFhyZgFyOX3SEkNXVLldjTzneFJ
FnVSzDbc720vq184jR7pYoI9+f5QJ96a0iLxEAG8SJ5auBwXI/w2FmKmwmdMvJ8/17+B4sMC
IRrXrDQl2xzpVXh/Qcmk5nf+w8HFmqATGy1OUAQbXga7AySAUaYhvvFk50u0bO5DiUGwzrJO
3TrwvaC2Ei4EFaBmIVgG7TfU5TaaY9IcJSCQ7AGUYE3RFSRpsLOoA3DsxP42YERgS/Nxw29+
YqZtPoO2QPbNpI7xnHVCfNBabx3oDIf438nFfv8spw5BQqBSbEF1izJA57eE64CzHnt7lB20
OFD11avYopwxggPKMIIDxgIBATCBkjCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBAgFVMAkGBSsOAwIaBQCgggIMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTEwMDUxMjIyMjI1NVowIwYJKoZIhvcNAQkEMRYEFA7ZDa/152U700VbknB8
zRdnrdbPMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBowYJ
KwYBBAGCNxAEMYGVMIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UE
AxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAVUw
gaUGCyqGSIb3DQEJEAILMYGVoIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQg
Q0ECAVUwDQYJKoZIhvcNAQEBBQAEggEAi/+Fvcqgl/ce/TQWxKw7mnRR4+rHARtcol2tp3UY
j58HgEQoAeinqnmTU4En8GoOY05yasUZqHpFpcFWtim5pyUXE6jySvvhrm2vcLUam8cbDQrJ
iEpjkIfho00D/xiyCW2ViIqstmaHm0uHYqia6KBmRWpMqSnMTzXvLS+mZYX+psZ4s6zPnLGu
IlYtZkqV76yExsVfpZWl+zgFkCQt/7709qInojN08fKOcagy+Lv8jP7WwCfjHFKXWjCxcYrj
dvKt3uo4qmjSxyVV/FfU6k+EDbD9u+AerEDAYCDg9LMZpQmSH1YmTIbcAbAt8nPOpMuzd5Z0
6tQp7Jt6dfNIzwAAAAAAAA==
--------------ms020903000300050006080903--

From stpeter@stpeter.im  Thu May 13 19:56:24 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 683D33A69ED for <urn@core3.amsl.com>; Thu, 13 May 2010 19:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.122
X-Spam-Level: 
X-Spam-Status: No, score=-1.122 tagged_above=-999 required=5 tests=[AWL=-0.937, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHFMfOZ-1nkF for <urn@core3.amsl.com>; Thu, 13 May 2010 19:56:23 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 5725E3A6977 for <urn@ietf.org>; Thu, 13 May 2010 19:56:23 -0700 (PDT)
Received: from squire.local (dsl-228-182.dynamic-dsl.frii.net [216.17.228.182]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 327C340E5C for <urn@ietf.org>; Thu, 13 May 2010 20:56:13 -0600 (MDT)
Message-ID: <4BECBBCB.6080703@stpeter.im>
Date: Thu, 13 May 2010 20:56:11 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "urn@ietf.org" <urn@ietf.org>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030500030703010106010800"
Subject: [urn] old list archives
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 14 May 2010 02:56:24 -0000

This is a cryptographically signed message in MIME format.

--------------ms030500030703010106010800
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks to Matt Larson of VeriSign and Steve Young of the Secretariat,
plus the gracious intercession of Leslie Daigle, messages from the old
URN WG between 1997 and 1999 are now included in our list archives:

http://www.ietf.org/mail-archive/web/urn/current/maillist.html

Enjoy!

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms030500030703010106010800
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIWnDCC
B1cwggY/oAMCAQICAVUwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBT
aWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQTAeFw0wOTA3MDYwMDAwMDFaFw0xMDA3MDYyMzU5NTlaMIHCMQswCQYDVQQG
EwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRlbnZlcjEiMCAGA1UEChMZWE1Q
UCBTdGFuZGFyZHMgRm91bmRhdGlvbjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0
aWZpY2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcN
AQkBFhJzdHBldGVyQHN0cGV0ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQCas7Mrnh02GakN8sft+HJpU4MwBxEgrGDZ2ZzUxDDt2sEhM+9Q74h955MtgMhK3TeBf6Hs
hDh/8Z9G//k2qNA0M2S5rejTqrmW0Jabca/L7BUZ0GhnU2N/2zeciFUmuZ4A2l1T5IMX2ZVP
XnNIaefBtbImJAbDz3T0vxkzTtcqgW3wL83PMDiqiuM+e1k+VPvOW4f5ZSGkPIhYCDpWqNE5
wZvjrLNMc8jZOPs9DrsYuIVwU72Vhy1tkEh+w6YpYHrdEUAe+eKe6TuxqZ60e9z3O36uiV//
Ms274iD6PbA/IGazJgaAdg6tvPehwTYGJAGmv3PsJKkLGjgoh+RrrM1LAgMBAAGjggOKMIID
hjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFOyws3XWgIY9FP1POVqjdZP9Lu38MB0GA1UdEQQWMBSBEnN0cGV0ZXJA
c3RwZXRlci5pbTCBqAYDVR0jBIGgMIGdgBR7iZySlyShhEcCy3T8LvSs3DLl86GBgaR/MH0x
CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg
RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eYIBDzCCAUcGA1UdIASCAT4wggE6MIIBNgYLKwYBBAGBtTcBAgAw
ggElMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQG
CCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMIG8
BggrBgEFBQcCAjCBrzAUFg1TdGFydENvbSBMdGQuMAMCAQEagZZMaW1pdGVkIExpYWJpbGl0
eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRoZSBTdGFydENv
bSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwYwYDVR0fBFwwWjAroCmgJ4YlaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vY3J0dTMtY3JsLmNybDAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNz
bC5jb20vY3J0dTMtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0
cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczMvY2xpZW50L2NhMEIGCCsGAQUFBzAC
hjZodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MzLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUA
A4IBAQBgv4xFXZqDKSOtnPOVbqOh1brj7oxRaVYk7N0MJG7x9Y/wkO3iwRwizVLcC1bA+D/R
gyFilXx6IQWE63Ge2tu+Y4w5QoHYwuUFQuBZuxvZpOa3ykdgPlBQaBM8m+Ien0skwNggaizA
X9Pc/sMLpP3jkO1iSF4agy4r5Ed+4G10mP5X0zO3gQwq9Uj4F9tX+58kU+fM1P8Sh+BYR4r/
kSbKE3tWcMaKblWPGwX0nYD26Je7Qb+uX/J5lCgozBrHXQWq8N98iklASf2pv+32Oi1dEjmM
UgAm/J2+YmxaI02+c+H6QH8+F3RUjCiRg9XqUNjcrNrnTFnm/iMMZADktsXPMIIHVzCCBj+g
AwIBAgIBVTANBgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBMB4XDTA5MDcwNjAwMDAwMVoXDTEwMDcwNjIzNTk1OVowgcIxCzAJBgNVBAYTAlVTMREw
DwYDVQQIEwhDb2xvcmFkbzEPMA0GA1UEBxMGRGVudmVyMSIwIAYDVQQKExlYTVBQIFN0YW5k
YXJkcyBGb3VuZGF0aW9uMSwwKgYDVQQLEyNTdGFydENvbSBUcnVzdGVkIENlcnRpZmljYXRl
IE1lbWJlcjEaMBgGA1UEAxMRUGV0ZXIgU2FpbnQtQW5kcmUxITAfBgkqhkiG9w0BCQEWEnN0
cGV0ZXJAc3RwZXRlci5pbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJqzsyue
HTYZqQ3yx+34cmlTgzAHESCsYNnZnNTEMO3awSEz71DviH3nky2AyErdN4F/oeyEOH/xn0b/
+Tao0DQzZLmt6NOquZbQlptxr8vsFRnQaGdTY3/bN5yIVSa5ngDaXVPkgxfZlU9ec0hp58G1
siYkBsPPdPS/GTNO1yqBbfAvzc8wOKqK4z57WT5U+85bh/llIaQ8iFgIOlao0TnBm+Oss0xz
yNk4+z0Ouxi4hXBTvZWHLW2QSH7Dpilget0RQB754p7pO7GpnrR73Pc7fq6JX/8yzbviIPo9
sD8gZrMmBoB2Dq2896HBNgYkAaa/c+wkqQsaOCiH5GuszUsCAwEAAaOCA4owggOGMAkGA1Ud
EwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV
HQ4EFgQU7LCzddaAhj0U/U85WqN1k/0u7fwwHQYDVR0RBBYwFIESc3RwZXRlckBzdHBldGVy
LmltMIGoBgNVHSMEgaAwgZ2AFHuJnJKXJKGERwLLdPwu9KzcMuXzoYGBpH8wfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5ggEPMIIBRwYDVR0gBIIBPjCCATowggE2BgsrBgEEAYG1NwECADCCASUwLgYI
KwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUH
AgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgbwGCCsGAQUF
BwICMIGvMBQWDVN0YXJ0Q29tIEx0ZC4wAwIBARqBlkxpbWl0ZWQgTGlhYmlsaXR5LCByZWFk
IHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFy
dHNzbC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0
c3NsLmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9j
cnR1My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2Nz
cC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNV
HRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBAGC/
jEVdmoMpI62c85Vuo6HVuuPujFFpViTs3QwkbvH1j/CQ7eLBHCLNUtwLVsD4P9GDIWKVfHoh
BYTrcZ7a275jjDlCgdjC5QVC4Fm7G9mk5rfKR2A+UFBoEzyb4h6fSyTA2CBqLMBf09z+wwuk
/eOQ7WJIXhqDLivkR37gbXSY/lfTM7eBDCr1SPgX21f7nyRT58zU/xKH4FhHiv+RJsoTe1Zw
xopuVY8bBfSdgPbol7tBv65f8nmUKCjMGsddBarw33yKSUBJ/am/7fY6LV0SOYxSACb8nb5i
bFojTb5z4fpAfz4XdFSMKJGD1epQ2Nys2udMWeb+IwxkAOS2xc8wggfiMIIFyqADAgECAgEP
MA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQu
MSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQD
EyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAzMzJaFw0x
MjEwMjIyMTAzMzJaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEr
MCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMv
U3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC5o0luEj4gypQIp71Xi2TlXyLYrj9WkRy+d9BO
0FHPYnAsC99/jx/ibNRwIfAoFhZd+LDscdRSckvwuFSz0bKg3z+9o7cwlVAC9AwMWe8IM0Lx
c+8etYxsX4WIamG9fjzzi5GAW5ESKzzIN3SxHSplyGCWFwx/pgf1f4y6O9/ym+4f6zaDYP6B
x0r+SaJcr6eSGNm7X3EwX1v7XpRBY+aw019o7k72d0IX910F+XGt0OwNdM61Ff3FiTiexeUZ
bWxCGm6GZl+SQVG9xYVIgHQaLXoQF+g2wzrmKCbVcZhqH+hrlRnD6PfCuEyX/BR6PlAPRDlQ
6f1u3wqik+LF5P15AgMBAAGjggNbMIIDVzAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIBpjAd
BgNVHQ4EFgQUe4mckpckoYRHAst0/C70rNwy5fMwgagGA1UdIwSBoDCBnYAUTgvvGqRAW6UX
aYcwyjRoQ9BBrvKhgYGkfzB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEpMCcGA1UE
AxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHmCAQEwCQYDVR0SBAIwADA9Bggr
BgEFBQcBAQQxMC8wLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNydDBgBgNVHR8EWTBXMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2Et
Y3JsLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIIBXQYD
VR0gBIIBVDCCAVAwggFMBgsrBgEEAYG1NwEBBDCCATswLwYIKwYBBQUHAgEWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5z
dGFydGNvbS5vcmcvaW50ZXJtZWRpYXRlLnBkZjCB0AYIKwYBBQUHAgIwgcMwJxYgU3RhcnQg
Q29tbWVyY2lhbCAoU3RhcnRDb20pIEx0ZC4wAwIBARqBl0xpbWl0ZWQgTGlhYmlsaXR5LCBy
ZWFkIHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENl
cnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQu
c3RhcnRjb20ub3JnL3BvbGljeS5wZGYwEQYJYIZIAYb4QgEBBAQDAgAHMFAGCWCGSAGG+EIB
DQRDFkFTdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIEZyZWUgU1NMIEVt
YWlsIENlcnRpZmljYXRlczANBgkqhkiG9w0BAQUFAAOCAgEAUpcEDdsKFRCxFBxcSm+8oMTT
fpS7fbZkxWHx5fHDjvAgaBQ+oY0tk4xtbD6VxeHYjxI63+hj8jICnqeVXPe34Bu+XzekIn2T
lrnPCQobKdQF2p52QgUvIxSURed0jcBaCBV22DSKaUqDOzD/Tx6VQy78zpblXjRH7OALE/+H
jzJVmspdnBUUtQOLYgPo924xkxR25VDdgtEE5vAXa/g2oCeZhy0ZEO4NbgIayAYCJcJRDz0h
dD2Ahec65Kw6LB3N7VXEjiRR5/WoKwH/QteRzPJbFDc1somrApjm2cyg+5nbm1RHeFIz+GxX
luRrPztvhNcby0PtAjqwY1txi4sW0R6ZJPuZ2DZ1/dzckoFhyZgFyOX3SEkNXVLldjTzneFJ
FnVSzDbc720vq184jR7pYoI9+f5QJ96a0iLxEAG8SJ5auBwXI/w2FmKmwmdMvJ8/17+B4sMC
IRrXrDQl2xzpVXh/Qcmk5nf+w8HFmqATGy1OUAQbXga7AySAUaYhvvFk50u0bO5DiUGwzrJO
3TrwvaC2Ei4EFaBmIVgG7TfU5TaaY9IcJSCQ7AGUYE3RFSRpsLOoA3DsxP42YERgS/Nxw29+
YqZtPoO2QPbNpI7xnHVCfNBabx3oDIf438nFfv8spw5BQqBSbEF1izJA57eE64CzHnt7lB20
OFD11avYopwxggPKMIIDxgIBATCBkjCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBAgFVMAkGBSsOAwIaBQCgggIMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTEwMDUxNDAyNTYxMVowIwYJKoZIhvcNAQkEMRYEFKP7zjvLlQCDvtg4S5de
kkpdYjtqMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBowYJ
KwYBBAGCNxAEMYGVMIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UE
AxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAVUw
gaUGCyqGSIb3DQEJEAILMYGVoIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQg
Q0ECAVUwDQYJKoZIhvcNAQEBBQAEggEAkObVDRVqOFhfYt6phikTwXvtpTWrmVKI+05c8bVw
Lamih8CnMnAOt4ux5sd0Bs1MC1+DFgErLJ27Gy0BhEthMOha5rjpyL4NoW2NEbGufeXqzJhj
SZebO7V7cIVXEI4sHVLP0ZOt+8sTaaDRQMc3jKzcI+7JTeC/1HFIFqeWqjfGuA9t5edxM9Re
anU5KtuOW2u0rN0gfhyjn6AGSnCcoaq3UKZI/q7WOpGoodXcwN3irhjbI/Uk33kLNXDMjAZs
TMS2I+RGT6URwUOATHM4aNOdYDNrmXrNrCbO/v0qZcsLeYvrsGzpZJVPPhJaro8+ffKGWmDE
XrjHbpVXYbSaqQAAAAAAAA==
--------------ms030500030703010106010800--

From juha.hakala@helsinki.fi  Sun May 16 23:25:09 2010
Return-Path: <juha.hakala@helsinki.fi>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86E973A6CFF for <urn@core3.amsl.com>; Sun, 16 May 2010 23:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.885
X-Spam-Level: 
X-Spam-Status: No, score=-0.885 tagged_above=-999 required=5 tests=[AWL=-1.899, BAYES_99=3.5, J_CHICKENPOX_34=0.6, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZmqX5rf3It7e for <urn@core3.amsl.com>; Sun, 16 May 2010 23:25:07 -0700 (PDT)
Received: from kill.it.helsinki.fi (kill.it.helsinki.fi [128.214.205.47]) by core3.amsl.com (Postfix) with ESMTP id C6A913A6D21 for <urn@ietf.org>; Sun, 16 May 2010 23:23:51 -0700 (PDT)
Received: from kill.it.helsinki.fi (kill.it.helsinki.fi [128.214.205.47]) by kill.it.helsinki.fi (8.13.1/8.13.1) with ESMTP id o4H6NYLo024611; Mon, 17 May 2010 09:23:34 +0300
Received: from [128.214.91.90] (kkkl25.lib.helsinki.fi [128.214.91.90]) by smtp-rs2.it.helsinki.fi (8.13.8/8.13.8) with ESMTP id o4H6NXrX004115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 17 May 2010 09:23:34 +0300
Message-ID: <4BF0E0E5.8010307@helsinki.fi>
Date: Mon, 17 May 2010 09:23:33 +0300
From: Juha Hakala <juha.hakala@helsinki.fi>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
References: <201005061820.UAA25600@TR-Sys.de> <4BE30BFA.5060606@network-heretics.com>
In-Reply-To: <4BE30BFA.5060606@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-HY-Tests: ALL_TRUSTED,SHORTCIRCUIT
Cc: =?UTF-8?B?QWxmcmVkIO+/vQ==?= <ah@TR-Sys.de>, urn@ietf.org
Subject: Re: [urn] Focus of the discussion
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 17 May 2010 06:25:09 -0000

Hello all,

Within the PersID project, nobody has an intention to change URN 
fundamentals. Therefore it should be easy to add a statement in the 
charter that no such changes will be done, in addition to formulating in 
more details the work that will actually be done.

One of our aims is to strengthen the status of URN-related RFCs. The 
current RFCs are informational or experimental, and as such they are not 
exactly carved in stone from IETF's point of view. However, they form a 
very useful basis for our work (and some of the RFCs took a lot of work 
to finish).

 From my point of view, the changes needed can be grouped in two 
categories: modernisation of namespace registrations and the check & 
strengthening of the base URN standards.

1. Namespaces

While most URN namespace registrations are no doubt OK, there are at 
least three that should be revised:

A. ISBN (International Standard Book Number): A new version of the ISBN 
standard was approved in 2007. Changes to the standard were non-trivial, 
and a thorough revision of RFC 3187 was needed. The version 00 of the 
RFC 3187bis has already been released. The staff of the ISBN 
International Centre has been informed about the revision and they have 
approved it.

B. ISSN (International Standard Serial Name) underwent a thorough 
revision a few years ago. The new version of the standard (2007) 
introduces ISSN-L (linking ISSN) which makes it necessary to rethink the 
way in which URN:ISSNs are resolved and update RFC 3044 accordingly. It 
is our intention to do this work in co-operation with the ISSN 
International Centre.

C. NBN (National Bibliography Number) namespace was registered (as RFC 
3188) before the national libraries or other users were actually using 
URN system. Now that millions of URN:NBNs have been assigned mainly to 
resources the national libraries have stored in their digital archives, 
it is time to check that the RFC accurately catches the ways in which 
URN:NBNs are assigned and resolved.

Please note that each namespace (identifier system) has its own rules as 
regards the nature of objects that can be identified. This rules may be 
quite rigid or very liberal. While the original scope of the URN 
developers was networked digital objects, there are several namespaces - 
including ISBN and ISSN - that cover a lot of digital objects, but also 
a lot of non-digital objects, in which case the URN can resolve to for 
instance the bibliographical description of the resource, and/or a 
service via which the resource can be ordered via Inter-library loan or 
digitized.

2. Check and strengthening of URN base standards

I am not a technical expert; my past & current practical work with URNs 
is related to namespace registration requests. (As an aside, given my 
appointment as the IETF - ISO TC 46 liaison officer it is possible that 
I'll be involved with more namespace registrations for ISO identifiers 
in the future.) With this caveat, my understanding of the practical 
implications of the working group's efforts is that they do not 
invalidate any past URN assigned, but allow more diversity in the future.

For example, from the character set point of view RFC 2141bis is both 
more liberal and more solid than the current RFC 2141, since the former 
builds upon RFC 3986, the latter on URL specification which was still 
only "work in progress". As an aside, in Finland there was an attempt to 
establish RFC 2141 as the national standard back in 2003-2004, but this 
effort failed due to the (according the external expert we used) 
outdated character set RFC 2141 allows in NID & NSS. With RFC 2141bis 
there should not be such a problem.

One issue that may be discussed in this list and elsewhere is the role & 
technical implementation of (DNS-based) resolver discovery services. The 
fact that no widely implemented RDS exist has not been missed the 
proponents of other persistent identifier systems (see 
http://www.doi.org/factsheets/DOIIdentifierSpecs.html). The relevant 
critical portion of the text was in 2010-05-17:

> URN architecture assumes a DNS-based Resolution Discovery Service (RDS) to find the service appropriate to the given URN scheme. However no such widely deployed RDS schemes currently exist: browsers cannot action URN strings without some additional programming in the form of a "plug-in". These carry no guarantee of ready interoperability with other deployments, which may require a different plug-in for each implementation and may use conflicting data approaches.

I have asked Norman Paskin to update this text with a short explanation 
(supplied by me) how URNs currently work in practice, in order to avoid 
an impression that there is a fundamental technical limitation in how 
the URNs work. I have no problems leaving all RDS-related RFCs in place, 
but it might be a good idea to describe somewhere how URNs are expressed 
as HTTP URIs and resolved, and the ways in which the project PersID will 
make the URN resolvers of the partners aware of each other & enable 
resolution data (URN - URL mappings) exchange between them.

Best regards,

Juha

Keith Moore wrote:
>   Alfred,
> 
> You are missing my point.  It doesn't matter that the charter doesn't 
> say anything about changing URN fundamentals.  Nor does it matter that 
> the people who are pushing for this WG aren't interested in changing URN 
> fundamentals.  Once an IETF working group is formed, anyone can 
> participate in it, and the chair is bound to honor group consensus.  
> Unless the charter expressly forbids changing URN fundamentals, it's 
> going to be impossible to keep the discussion on target for the group's 
> intended scope.  (Even with a "big stick" in the charter, it's likely to 
> be difficult.) 
> 
> Furthermore, IESG has sometimes had difficulty pushing back on groups 
> that exceed their mandate, unless the output of the group is clearly 
> outside of the bounds of the charter.
> 
> The best time to fight scope creep is before the group is actually 
> chartered.
> 
> Keith
>>  Keith,
>> thanks again for your feedback.
>>
>>  
>>>  I am strongly of the opinion that the WG MUST be constrained from
>>> attempting to change the intent of the original URN specifications; or
>>> for that matter the specifications themselves except as necessary to
>>> clarify, correct errata, and reconcile apparent differences with other
>>> standards.
>>>  
>>  
>> Are there indications in the first draft charter or in the initial
>> 2141bis draft that have lead you to the conclusion somebody seriously
>> wanted to try to change URN fundamentals?
>> If you feel so, please tell us the details so that these can be adjusted.
>>
>>
>>  
>>>  History suggests that discussions about naming are very contentious.
>>> They seem to bring people out of the woodwork who want this kind of name
>>> to serve whatever purpose they hope to serve, whether or not that is the
>>> intent behind that kind of name.  We had that problem with the original
>>> URN discussions.  We also had that problem with discussions around
>>> "human friendly names" and similar ideas.  To some degree we've even had
>>> that problems with discussions of URLs, and there is a long history of
>>> contention on use of DNS names.
>>>  
>>  
>> The origin of this effort stems from custodians of cultural legacy, most
>> of them working directly for national libraries, and a few supporting
>> folks, including me -- in a role you might circumscribe as an inofficial
>> liaison to the IETF.  Some people contemporarily regard such folks as
>> overly conservative; but at least, they are not renowned as followers
>> of apparently short-lived hypes.
>> So far, I did not see any indication in the messages from PersID
>> that a fundamental shift in paradigm would even be considered.
>>
>> The goal clearly is a revised set of documents compatible with
>> existing standards and matching the requirements of an evolving
>> distributed, international, URN resolution system for unambiguous
>> specifications, lying the foundation for interoperable implementations
>> of resolution services, and for future improved namespace definitions
>> that support these goals.
>> I hoped that would be clear from the submitted text.
>>
>>  
>>>  
>>> The battle for control of URNs needs to not be revisited.   Those
>>> decisions have already been made, and they were hard fought.  People who
>>> want URNs to be something significantly different than they were
>>> originally specified to be need to go elsewhere, or start from scratch
>>> to convince the community that a new kind of name is needed.  This is
>>> especially important to preserve the persistence qualities of URNs.
>>>  
>>  
>> In a recent contribution to this list, it has been clarified that,
>> basically, URNs are the URIs of the 'urn' URI scheme -- nothing more
>> and nothing less -- and that each URI scheme has its specific set of
>> rules beyond the general rules in the URI standard.
>> The fact that this needed to be stated seems to be a dedicated,
>> a-posteriori justification for having (for the first time!) a formal
>> specification for the 'urn' URI scheme in the 2141bis draft, as you
>> can find instantiated in the -00 version.
>> Of course, the details of the draft are subject to WG discussion,
>> (but comments are welcome as well before WG formation); however,
>> the primary goal now is discussing, and eventually arriving at
>> consensus for, a WG charter.
>>
>>  
>>>  
>>> This needs to be made very clear in the group's charter, and right now
>>> there's not even a hint of that.
>>>
>>> Keith
>>>  
>>  
>> Again: Do you see a hint to the contrary?  Where?
>>
>> The proposed draft charter lists major goals.
>> Changing more fundamental things is not even mentioned there.
>> IMO, it is implied by the intent and practice of WG charters that
>> details are to be worked out in the WG, but that the WG is not
>> endowed to leave the grounds of what is written in the charter.
>>
>> Where do you derive from the idea that this text would task the
>> proposed WG with tackling such work?  We are used to specify in the
>> charter the working plan of a WG, and not what the WG is _not_
>> planning -- otherwise we would quickly arrive at unreadable charters
>> of unbounded size.  When a WG wants to go beyond its charter, the
>> rules require re-chartering.  We currently are defining the tasks of
>> the WG; the first cut has been posted, and it does specify detailed
>> goals.
>>
>> So once again (and this is directed to all readers of this list!),
>> please quote text parts you do not concur with or that you would like
>> to be amended, and supply text proposals for additions and/or changes,
>> if you believe they should be applied.
>> On the other hand, please feel free to state explicit support of the
>> current text or parts of it.
>>
>>
>> Kind regards,
>>   Alfred.
>>
>>  
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn

-- 

  Juha Hakala
  Director of IT Development

  The National Library of Finland
  P.O.Box 15 (Unioninkatu 36, room 503), FIN-00014 Helsinki University
  Email juha.hakala@helsinki.fi, tel +358 50 382 7678




From A.Hoenes@TR-Sys.de  Sun May 16 23:30:23 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78D2B3A6CEC for <urn@core3.amsl.com>; Sun, 16 May 2010 23:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.994
X-Spam-Level: 
X-Spam-Status: No, score=-95.994 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2Ii04k-mX8z for <urn@core3.amsl.com>; Sun, 16 May 2010 23:30:22 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id C65063A6ABC for <urn@ietf.org>; Sun, 16 May 2010 23:30:20 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA082017767; Mon, 17 May 2010 08:29:27 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id IAA09838; Mon, 17 May 2010 08:29:26 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201005170629.IAA09838@TR-Sys.de>
To: stpeter@stpeter.im
Date: Mon, 17 May 2010 08:29:25 +0200 (MESZ)
In-Reply-To: <4BECBBCB.6080703@stpeter.im> from Peter Saint-Andre at May "13, " 2010 "08:56:11" pm
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Cc: urn@ietf.org
Subject: Re: [urn] old list archives
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 17 May 2010 06:30:23 -0000

Peter Saint-Andre wrote:

> Thanks to Matt Larson of VeriSign and Steve Young of the Secretariat,
> plus the gracious intercession of Leslie Daigle, messages from the old
> URN WG between 1997 and 1999 are now included in our list archives:
> 
> http://www.ietf.org/mail-archive/web/urn/current/maillist.html
> 
> Enjoy!
> 
> Peter
> 
> --
> Peter Saint-Andre
> https://stpeter.im/

Thanks to all who have contributed to this effort!

Kind regards,
  Alfred.


From A.Hoenes@TR-Sys.de  Wed May 19 13:24:28 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 75C1B3A6909; Wed, 19 May 2010 13:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.228
X-Spam-Level: 
X-Spam-Status: No, score=-95.228 tagged_above=-999 required=5 tests=[AWL=-0.594, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, J_CHICKENPOX_33=0.6, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xhr5ox8JwhLw; Wed, 19 May 2010 13:24:27 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 459043A6A17; Wed, 19 May 2010 13:23:52 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA097400571; Wed, 19 May 2010 22:22:51 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id WAA14371; Wed, 19 May 2010 22:22:50 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201005192022.WAA14371@TR-Sys.de>
To: urn@ietf.org, urn-nid@ietf.org
Date: Wed, 19 May 2010 22:22:49 +0200 (MESZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Subject: [urn] New Version Notification for draft-hakala-rfc3188bis-nbn-urn-00 (fwd)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 20:24:28 -0000

Folks,
an initial draft for a revised NBN URN namespace definition document
has been completed and submitted.
It targets the proposed URNbis WG we want to establish.

Comments welcome ...


----- Forwarded message from IETF I-D Submission Tool -----

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: Wed, 19 May 2010 13:12:52 -0700 (PDT)
> Message-Id: <20100519201252.71D493A68CB@core3.amsl.com>
> Subject: New Version Notification for draft-hakala-rfc3188bis-nbn-urn-00


A new version of I-D, draft-hakala-rfc3188bis-nbn-urn-00.txt
has been successfully submitted and posted to the IETF repository.

Filename:	 draft-hakala-rfc3188bis-nbn-urn
Revision:	 00
Title:		 Using National Bibliography Numbers as Uniform Resource Names
Creation_date:	 2010-05-19
WG ID:		 Independent Submission
Number_of_pages: 19

Abstract:

National Bibliography Numbers, NBNs, are widely used by the national
libraries and other organizations in order to identify various
resources such as monographs pre-dating the emergence of the ISBN
system or still images.  As a rule, NBNs are applied to all kinds of
resources that do not have an established identifier system of their
own.

Since 2001, there has been a URN (Uniform Resource Names) namespace
for NBNs, and during 2001-2009 millions of URN-based unique and
persistent NBNs have been assigned.  The namespace registration was
performed in RFC 3188 and applied to the NBNs known at that point.
No URN:NBN resolution services existed at the time when the RFC was
written.  Since then several countries have started using URN:NBNs to
identify electronic resources and to provide persistent links to
them.  To this end, many countries have established URN:NBN
resolution services that supply URN - URL linking.

This document replaces RFC 3188 and defines how NBNs can be supported
within the URN framework.  An updated namespace registration (version
4) is included.

Discussion

This document is an outcome of work performed in 2009-2010 as a part
of the project PersID (http://www.persid.org) revising the basic URN
RFCs, in order to bring them in alignment with the current URI
Standard (STD 63, RFC 3986), ABNF, and IANA guidelines, and to
establish a modern URN resolution system for bibliographic
identifiers.  This work is being brought to the IETF, and the intent
is to establish a "URNbis" (or similar) working group in the
Applications Area as soon as possible, which will then target this
and related work.

Comments are welcome on the urn@ietf.org or the urn-nid@ietf.org
mailing list (or sent to the authors).  Interested parties are also
invited to contribute to the WG formation process being discussed on
the former list.

<snip/>



The IETF Secretariat.


----- End of forwarded message from IETF I-D Submission Tool -----


Kind regards,
  Alfred.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+


From A.Hoenes@TR-Sys.de  Mon May 24 13:24:39 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF8103A6B0A for <urn@core3.amsl.com>; Mon, 24 May 2010 13:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.864
X-Spam-Level: 
X-Spam-Status: No, score=-95.864 tagged_above=-999 required=5 tests=[AWL=0.285, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OOCtn3zNr2AI for <urn@core3.amsl.com>; Mon, 24 May 2010 13:24:35 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id D2BBC3A67CC for <urn@ietf.org>; Mon, 24 May 2010 13:24:34 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA126942607; Mon, 24 May 2010 22:23:27 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id WAA22043; Mon, 24 May 2010 22:23:13 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201005242023.WAA22043@TR-Sys.de>
To: urn@ietf.org
Date: Mon, 24 May 2010 22:23:12 +0200 (MESZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 8bit
Subject: Re: [urn] A first cut at the Draft Charter
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 24 May 2010 20:24:40 -0000

Folks,
Juha and I have re-worked the draft URNbis charter to accommodate
the concers raised, and other comments received (thanks to all
contributors!).  The restructured and amended text hopefully
elaborates in sufficient detail on the problems the WG is going
to tackle and the specific tasks for it to be chartered initially,
so that the type of maintenance work intended should be pretty clear
even for people only passing by at this topic, without having read
the initial drafts already submitted to the IETF.

This version will be posted immediately in a distinct message,
to allow new threads to more easily refer to that "second cut".
The text has grown in size substantially; it was our intent to give
that degree of detail for the record and to base further reasoning
on it, but we seriously want to cut it back down to a more handy
volume by the BOF we target at IETF 78 in Maastricht.

Therefore, I'd appreciate to get feedback first on the reasoning
in this second cut on the draft charter (in order to get more
clarification if still regarded as necessary), and subsequently
suggestions on where to shorten the text.

We need to boost the discussion; the IETF calendar expects formal
BOF requests for IETF 78 by June 1st, and hence the general issues
with the charter (if any) should to be resolved by then.
Therefore, please provide feedback as soon as possible -- even if
you simply want to indicate support for the goals described in the
draft charter and your intent to actively participate in the
proposed URNbis WG.

Kind regards,
  Alfred HÎnes.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+


From A.Hoenes@TR-Sys.de  Mon May 24 13:35:52 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF91F3A6F17 for <urn@core3.amsl.com>; Mon, 24 May 2010 13:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.116
X-Spam-Level: 
X-Spam-Status: No, score=-95.116 tagged_above=-999 required=5 tests=[AWL=-0.482, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, J_CHICKENPOX_34=0.6, J_CHICKENPOX_35=0.6, MIME_8BIT_HEADER=0.3, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NhgnH75KPwQK for <urn@core3.amsl.com>; Mon, 24 May 2010 13:35:51 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 8F54F3A67FD for <urn@ietf.org>; Mon, 24 May 2010 13:35:49 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA127073295; Mon, 24 May 2010 22:34:56 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id WAA22059 for urn@ietf.org; Mon, 24 May 2010 22:34:54 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201005242034.WAA22059@TR-Sys.de>
To: urn@ietf.org
Date: Mon, 24 May 2010 22:34:54 +0200 (MESZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Subject: [urn] A second cut at the Draft Charter for the proposed URNbis WG
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 24 May 2010 20:35:52 -0000

Uniform Resource Names, Revised (URNbis) -- Draft Proposed WG Charter
========================================

Administrivia
+++++++++++++

  Last Modified:  2010-05-20  [AH]

  Chair(s):
    o   N.N.

  Applications Area Director(s):
    o   Alexey Melnikov  <alexey.melnikov@isode.com>
    o   Peter Saint-Andre  <stpeter@stpeter.im>

  Applications Area Advisor:
    o   N.N.

  Mailing Lists:
    o  General Discussion: urn@ietf.org
       To Subscribe:
         https://www.ietf.org/mailman/listinfo/urn
       Archive:
         http://www.ietf.org/mail-archive/web/urn/current/maillist.html

    o  Related lists (used for IANA registration procedures (BCP 35/66):
         urn-nid@ietf.org, uri-review@ietf.org

  Additional information will be available at:
    http://tools.ietf.org/wg/___


Description of Working Group
++++++++++++++++++++++++++++

  * * *  Problem Statement  * * *

  Uniform Resource Names (URNs) are location-independent, persistent
  identifiers for information resources.

  The RFCs defining URNs and services based on them were published
  in 1997-2001, based on old (or even provisional) basic documents
  on the concepts of URI, URL, and URN, and with almost no
  implementation experience.
  Since then, the URN system has gained significant popularity, and
  many URN Namespaces have been defined and registered with IANA.
  Among the more traditional parties with deep interest in persistent
  identifiers and making heavy use of URNs are national libraries;
  solely within this area, tens of millions of resources have been
  assigned URNs; this enables efficient searching of and persistent
  linking to these documents.  However, the evolving distributed,
  interlinked URN resolution system being built lacks a fundament
  that is consistent in terminology and formal description with
  present (Full) Internet Standards.

  The core URN RFCs -- RFC 2141 (URN Syntax) and RFC 4306 (Namespace
  Definition Mechanisms) -- were based on outdated framework documents.
  For instance, all References in RFC 2141 point to "work in progress"
  or documents that have been superseded at least once.
  Most importantly, since RFC 2141 was published before even the
  now-obsolete RFC 2396 was published, it is based on pre-2396 drafts
  and should be updated for consistency with the contemporary URI
  syntax and terminology reflected in STD 66, RFC 3986.  Additionally,
  since RFC 2141 predates RFC 2234, it uses for its syntax definitions
  an early form of BNF, not the ABNF commonly used in the IETF (first
  specified in RFC 2234, later evolved to the current STD 68, RFC 5234).
  All IANA considerations and procedures should now be based on the
  terminology and rules laid down in BCP 26, RFC 5226.

  The lack of a formal registration of the 'urn' URI scheme fosters
  recurring discussions on what URNs are.  Such formal registration
  is needed to clarify that URNs are specific URIs (namely those using
  the 'urn' URI scheme) and hence all general rules for URIs apply to
  URNs, in addition to the common rules for all URNs and particular
  scheme-specific rules.

  Key bibliographic identifier standards are ISBN and ISSN, which are
  based on ISO standards and cover books and serials, respectively.
  These ISO standards were revised in 2007 to clarify and extend the
  underlying namespaces; those changes should be reflected in the URN
  definitions so as to enable use of the extended forms of these
  identifiers in URNs.
  For materials not covered by ISBN, ISSN, or other formal standards,
  many national libraries and other institutions apply National
  Bibliography Numbers (NBNs). Their usage has increased a lot since
  a related URN namespace was specified in RFC 3188, and the deployment
  has proven that more flexibility was needed than provided by the RFC
  -- both for NBN syntax and for the distributed management of these
  identifiers.
  Thus, there is a need to revise these namespace registration to
  correctly reflect the current state of the art.

  Other (early) URN namespace definitions should be screened to verify
  their alignment with the existing and updated base identifier
  standards and updated RFCs, and to give advice to registrants
  in case mismatches/deficiencies were detected.

  The elaborations on URN resolution in early RFCs predate large-scale
  experience with URIs in general and URNs in particular, and they do
  predate the consolidation of terms achieved in a joint W3C / IETF
  collaboration (published for the IETF as RFC 3305).  Hence there is
  a need to revisit these Informational documents as well and provide
  updates, if necessary.  It also needs to be determined whether the
  implementation experiences from project PersID (and other existing
  URN resolution systems) deserve consolidation towards standardization
  to further interoperability of services and service user applications.


  * * *  Objectives for the Working Group  * * *

  This working group is chartered to update the key RFCs describing the
  URN system, including RFC 2141 (URN Syntax) and RFC 4306 (Namespace
  Definition Mechanisms), update selected URN namespace specifications
  including those for ISBN, NBN and ISSN, and to screen and update RFCs
  describing URN resolution principles and practices.
  For all document revisions, the stability of existing identifiers and
  backward compatibility with previous specifications (as far as possible
  with respect to existing Full Standards) are of foremost importance.

  Thus, in support of the current international efforts to establish a
  distributed, linked system of URN resolution systems for bibliographic
  identifiers, the primary aim of the WG is an updated set of documents,
  all on the Standards-Track.  These updates are needed to provide a
  normative foundation and assure uniformity and interoperability of the
  URN assignment and resolution concepts and procedures at the abstract
  level.

  Details and tasks (the WG will approach these tasks in roughly this
  order):

  a)  Core URN specifications

  For RFC 2141, this revision will include in particular:
  - an update of the formal syntax specification in the light of the
    URI Standard (STD 66, RFC 3986) using the ABNF from STD 68
    (RFC 5234);
  - a formal IANA registration for the 'urn' URI scheme using the
    current template from BCP 35 (RFC 4395);
  - a revised set of URN examples (the WG will determine whether the
    granted persistence of URNs allows usage of concrete, real-life
    URN examples -- as desired by implementers -- or whether a URN
    "example" namespace should be created for this purpose);
  - and an update of the sections describing how URNs are resolved
    in the Internet.

  RFC 4306 (BCP 66) needs a less pervasive update, mostly to align it
  with the current IANA procedures and terminology as defined in BCP 26
  (RFC 5226).

  b) URN Namespace specifications

  The WG will focus on updates for the definitions of URNs based on
  bibliographic identifier systems, in particular
  - RFC 3187 (URN Namespace for International Standard Book Numbers),
  - RFC 3188 (URN Namespace for National Bibliography Numbers), and
  - RFC 3044 (URN Namespace for International Serial Standard Number).

  In all these cases, the respective identifier system and/or the
  institutions and roles involved in their assignment and resolution
  have evolved since these RFCs have been published (see below for a
  sketch).
  The global importance of these identifier systems makes it highly
  desirable to have Standards-Track namespace definition documents.

  In particular, the URN:ISBN namespace needs to be extended according
  to the revision of the international ISBN standard, ISO 2108: A new
  version of the ISBN standard was approved in 2007.  Changes to the
  standard were non-trivial, and a thorough revision of RFC 3187 was
  needed.
    The version -00 of the RFC 3187bis I-D has already been submitted,
    and the staff of the ISBN International Centre has been informed
    about the revision, supports this work, and already has approved
    the technical changes contained in it.

  The ISSN (International Standard Serial Name) system (ISO 3297)
  underwent a thorough revision a few years ago. The new version of the
  standard (2007) introduces ISSN-L (linking ISSN), which makes it
  necessary to rethink the way in which URN:ISSNs are resolved, and to
  update RFC 3044 accordingly.  This work to revise RFC 3044 is being
  performed in co-operation with the ISSN International Centre.

  The NBN (National Bibliography Number) URN namespace was registered
  (by RFC 3188) before the national libraries or other users were
  actually using the URN system. Now that millions of URN:NBNs have
  been assigned mainly to resources the national libraries have stored
  in their digital archives, the WG will provide a revised namespace
  definition RFC that accurately catches the ways in which URN:NBNs are
  assigned and resolved in practice, and that is aligned with the basic
  standards and the revised core URN specifications.

  c)  URN resolution and resolution mechanisms

  Alongside the modernization of these core RFCs for URNs and specific
  URN namespaces, the working group will also consider a revision of
  earlier RFCs related to the principles of URNs and URN resolution,
  such as RFC 2483 (URI Resolution services necessary for URN
  resolution), RFC 2276 (Architectural principles of Uniform Resource
  Name Resolution), RFC 1737 (Functional requirements for Uniform
  Resource Names) and RFC 2169 (A trivial convention for using HTTP in
  URN resolution).  All these must be checked; if the document is still
  deemed relevant, it will be modernized as required to align it with
  contemporary IETF terminology and the state-of-the-art of URN
  resolution services.

  The working group will also consider the possibility of publishing
  Best Current Practices on how to resolve the URNs utilizing the
  existing Internet protocols such as HTTP.  Such BCP will be based on
  experience from large-scale URN resolution projects, in particular
  the European URN resolution infrastructure under construction in the
  project PersID.

  Since the revised specifications will be based on existing production
  systems and provide important guidelines for future implementers,
  the WG aims at publishing the RFCs on the Standards Track and will try
  to advance the core document at least to Draft Standard status as fast
  as possible.

  d) Further work

  The WG will offer advice to previous and new registrants of URN
  namespaces.  It will screen the legacy URN namespace definition
  documents and will provide advice to their registrants regarding
  necessary steps to bring these registrations in line with the
  existing standards and the revised URN core specifications, and
  regarding other issues, if such are found.

  The WG can take on work to update well-established URN namespace
  definitions other than the aforementioned cases of bibliographic
  identifier based URN namespaces, upon a case-by-case decision, and
  in collaboration with the respective original registrating party
  (or its legitimate successor); doing so will require an update to
  this charter.


WG Input / Output
+++++++++++++++++

Input documents:

  RFC 2141
  RFC 3406

  RFC 3187
  RFC 3188
  RFC 3044

  RFC 2483
  RFC 2276
  RFC 1737
  RFC 2169

Goals and Milestones (rough and preliminary):

  Dec 2010   WG Last Call on "core document set" ( a) + b) above )
  Feb 2011   core document set forwarded to IESG
      2011   work on supporting documents (guidelines, URN resolution)
      2012   implementation report for promoting 2141bis to Draft Std.

Internet-Drafts:

  draft-ah-rfc2141bis-urn          (-00: submitted March 2010)
  draft-hakala-rfc3187bis-isbn-urn (-00: submitted March 2010)
  draft-hakala-rfc3188bis-nbn-urn  (-00: submitted May 2010)

Request For Comments:

  none so far


From rden@loc.gov  Mon May 24 14:06:41 2010
Return-Path: <rden@loc.gov>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6021A3A6D10 for <urn@core3.amsl.com>; Mon, 24 May 2010 14:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.971
X-Spam-Level: 
X-Spam-Status: No, score=-2.971 tagged_above=-999 required=5 tests=[AWL=-0.787, BAYES_50=0.001, J_CHICKENPOX_34=0.6, J_CHICKENPOX_35=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CCVQVJUZ8R0D for <urn@core3.amsl.com>; Mon, 24 May 2010 14:06:38 -0700 (PDT)
Received: from sun8.loc.gov (sun8.loc.gov [140.147.249.48]) by core3.amsl.com (Postfix) with ESMTP id A65D83A6CFF for <urn@ietf.org>; Mon, 24 May 2010 14:06:35 -0700 (PDT)
Received: from lsdds9qg1 (lsdds9qg1.lib.loc.gov [140.147.175.24]) by sun8.loc.gov  with ESMTP id o4OL6NZw027520; Mon, 24 May 2010 17:06:23 -0400 (EDT)
From: "Ray Denenberg, Library of Congress" <rden@loc.gov>
To: "=?iso-8859-1?Q?'Alfred_H=CEnes'?=" <ah@TR-Sys.de>, <urn@ietf.org>
References: <201005242034.WAA22059@TR-Sys.de>
In-Reply-To: <201005242034.WAA22059@TR-Sys.de>
Date: Mon, 24 May 2010 17:06:24 -0400
Message-ID: <04c301cafb84$f7b416f0$e71c44d0$@gov>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acr7gLEnClfULy8tQOiwUWiKqKfBSQAA1oiA
Content-Language: en-us
Subject: Re: [urn] A second cut at the Draft Charter for the proposed URNbis WG
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 24 May 2010 21:06:41 -0000

  "The lack of a formal registration of the 'urn' URI scheme fosters
  recurring discussions on what URNs are.  "

Huh?  Is this to imply that 'urn' is not a URI scheme?  =20

http://www.iana.org/assignments/uri-schemes.html   says it is. =20

At least is says it is a "permanent" URI scheme.  Are you asserting that
it's never been formally registered (even though it's permanent, =
whatever
that means)?

--Ray



-----Original Message-----
From: urn-bounces@ietf.org [mailto:urn-bounces@ietf.org] On Behalf Of =
Alfred
H=CEnes
Sent: Monday, May 24, 2010 4:35 PM
To: urn@ietf.org
Subject: [urn] A second cut at the Draft Charter for the proposed URNbis =
WG

Uniform Resource Names, Revised (URNbis) -- Draft Proposed WG Charter
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Administrivia
+++++++++++++

  Last Modified:  2010-05-20  [AH]

  Chair(s):
    o   N.N.

  Applications Area Director(s):
    o   Alexey Melnikov  <alexey.melnikov@isode.com>
    o   Peter Saint-Andre  <stpeter@stpeter.im>

  Applications Area Advisor:
    o   N.N.

  Mailing Lists:
    o  General Discussion: urn@ietf.org
       To Subscribe:
         https://www.ietf.org/mailman/listinfo/urn
       Archive:
         http://www.ietf.org/mail-archive/web/urn/current/maillist.html

    o  Related lists (used for IANA registration procedures (BCP 35/66):
         urn-nid@ietf.org, uri-review@ietf.org

  Additional information will be available at:
    http://tools.ietf.org/wg/___


Description of Working Group
++++++++++++++++++++++++++++

  * * *  Problem Statement  * * *

  Uniform Resource Names (URNs) are location-independent, persistent
  identifiers for information resources.

  The RFCs defining URNs and services based on them were published
  in 1997-2001, based on old (or even provisional) basic documents
  on the concepts of URI, URL, and URN, and with almost no
  implementation experience.
  Since then, the URN system has gained significant popularity, and
  many URN Namespaces have been defined and registered with IANA.
  Among the more traditional parties with deep interest in persistent
  identifiers and making heavy use of URNs are national libraries;
  solely within this area, tens of millions of resources have been
  assigned URNs; this enables efficient searching of and persistent
  linking to these documents.  However, the evolving distributed,
  interlinked URN resolution system being built lacks a fundament
  that is consistent in terminology and formal description with
  present (Full) Internet Standards.

  The core URN RFCs -- RFC 2141 (URN Syntax) and RFC 4306 (Namespace
  Definition Mechanisms) -- were based on outdated framework documents.
  For instance, all References in RFC 2141 point to "work in progress"
  or documents that have been superseded at least once.
  Most importantly, since RFC 2141 was published before even the
  now-obsolete RFC 2396 was published, it is based on pre-2396 drafts
  and should be updated for consistency with the contemporary URI
  syntax and terminology reflected in STD 66, RFC 3986.  Additionally,
  since RFC 2141 predates RFC 2234, it uses for its syntax definitions
  an early form of BNF, not the ABNF commonly used in the IETF (first
  specified in RFC 2234, later evolved to the current STD 68, RFC 5234).
  All IANA considerations and procedures should now be based on the
  terminology and rules laid down in BCP 26, RFC 5226.

  The lack of a formal registration of the 'urn' URI scheme fosters
  recurring discussions on what URNs are.  Such formal registration
  is needed to clarify that URNs are specific URIs (namely those using
  the 'urn' URI scheme) and hence all general rules for URIs apply to
  URNs, in addition to the common rules for all URNs and particular
  scheme-specific rules.

  Key bibliographic identifier standards are ISBN and ISSN, which are
  based on ISO standards and cover books and serials, respectively.
  These ISO standards were revised in 2007 to clarify and extend the
  underlying namespaces; those changes should be reflected in the URN
  definitions so as to enable use of the extended forms of these
  identifiers in URNs.
  For materials not covered by ISBN, ISSN, or other formal standards,
  many national libraries and other institutions apply National
  Bibliography Numbers (NBNs). Their usage has increased a lot since
  a related URN namespace was specified in RFC 3188, and the deployment
  has proven that more flexibility was needed than provided by the RFC
  -- both for NBN syntax and for the distributed management of these
  identifiers.
  Thus, there is a need to revise these namespace registration to
  correctly reflect the current state of the art.

  Other (early) URN namespace definitions should be screened to verify
  their alignment with the existing and updated base identifier
  standards and updated RFCs, and to give advice to registrants
  in case mismatches/deficiencies were detected.

  The elaborations on URN resolution in early RFCs predate large-scale
  experience with URIs in general and URNs in particular, and they do
  predate the consolidation of terms achieved in a joint W3C / IETF
  collaboration (published for the IETF as RFC 3305).  Hence there is
  a need to revisit these Informational documents as well and provide
  updates, if necessary.  It also needs to be determined whether the
  implementation experiences from project PersID (and other existing
  URN resolution systems) deserve consolidation towards standardization
  to further interoperability of services and service user applications.


  * * *  Objectives for the Working Group  * * *

  This working group is chartered to update the key RFCs describing the
  URN system, including RFC 2141 (URN Syntax) and RFC 4306 (Namespace
  Definition Mechanisms), update selected URN namespace specifications
  including those for ISBN, NBN and ISSN, and to screen and update RFCs
  describing URN resolution principles and practices.
  For all document revisions, the stability of existing identifiers and
  backward compatibility with previous specifications (as far as =
possible
  with respect to existing Full Standards) are of foremost importance.

  Thus, in support of the current international efforts to establish a
  distributed, linked system of URN resolution systems for bibliographic
  identifiers, the primary aim of the WG is an updated set of documents,
  all on the Standards-Track.  These updates are needed to provide a
  normative foundation and assure uniformity and interoperability of the
  URN assignment and resolution concepts and procedures at the abstract
  level.

  Details and tasks (the WG will approach these tasks in roughly this
  order):

  a)  Core URN specifications

  For RFC 2141, this revision will include in particular:
  - an update of the formal syntax specification in the light of the
    URI Standard (STD 66, RFC 3986) using the ABNF from STD 68
    (RFC 5234);
  - a formal IANA registration for the 'urn' URI scheme using the
    current template from BCP 35 (RFC 4395);
  - a revised set of URN examples (the WG will determine whether the
    granted persistence of URNs allows usage of concrete, real-life
    URN examples -- as desired by implementers -- or whether a URN
    "example" namespace should be created for this purpose);
  - and an update of the sections describing how URNs are resolved
    in the Internet.

  RFC 4306 (BCP 66) needs a less pervasive update, mostly to align it
  with the current IANA procedures and terminology as defined in BCP 26
  (RFC 5226).

  b) URN Namespace specifications

  The WG will focus on updates for the definitions of URNs based on
  bibliographic identifier systems, in particular
  - RFC 3187 (URN Namespace for International Standard Book Numbers),
  - RFC 3188 (URN Namespace for National Bibliography Numbers), and
  - RFC 3044 (URN Namespace for International Serial Standard Number).

  In all these cases, the respective identifier system and/or the
  institutions and roles involved in their assignment and resolution
  have evolved since these RFCs have been published (see below for a
  sketch).
  The global importance of these identifier systems makes it highly
  desirable to have Standards-Track namespace definition documents.

  In particular, the URN:ISBN namespace needs to be extended according
  to the revision of the international ISBN standard, ISO 2108: A new
  version of the ISBN standard was approved in 2007.  Changes to the
  standard were non-trivial, and a thorough revision of RFC 3187 was
  needed.
    The version -00 of the RFC 3187bis I-D has already been submitted,
    and the staff of the ISBN International Centre has been informed
    about the revision, supports this work, and already has approved
    the technical changes contained in it.

  The ISSN (International Standard Serial Name) system (ISO 3297)
  underwent a thorough revision a few years ago. The new version of the
  standard (2007) introduces ISSN-L (linking ISSN), which makes it
  necessary to rethink the way in which URN:ISSNs are resolved, and to
  update RFC 3044 accordingly.  This work to revise RFC 3044 is being
  performed in co-operation with the ISSN International Centre.

  The NBN (National Bibliography Number) URN namespace was registered
  (by RFC 3188) before the national libraries or other users were
  actually using the URN system. Now that millions of URN:NBNs have
  been assigned mainly to resources the national libraries have stored
  in their digital archives, the WG will provide a revised namespace
  definition RFC that accurately catches the ways in which URN:NBNs are
  assigned and resolved in practice, and that is aligned with the basic
  standards and the revised core URN specifications.

  c)  URN resolution and resolution mechanisms

  Alongside the modernization of these core RFCs for URNs and specific
  URN namespaces, the working group will also consider a revision of
  earlier RFCs related to the principles of URNs and URN resolution,
  such as RFC 2483 (URI Resolution services necessary for URN
  resolution), RFC 2276 (Architectural principles of Uniform Resource
  Name Resolution), RFC 1737 (Functional requirements for Uniform
  Resource Names) and RFC 2169 (A trivial convention for using HTTP in
  URN resolution).  All these must be checked; if the document is still
  deemed relevant, it will be modernized as required to align it with
  contemporary IETF terminology and the state-of-the-art of URN
  resolution services.

  The working group will also consider the possibility of publishing
  Best Current Practices on how to resolve the URNs utilizing the
  existing Internet protocols such as HTTP.  Such BCP will be based on
  experience from large-scale URN resolution projects, in particular
  the European URN resolution infrastructure under construction in the
  project PersID.

  Since the revised specifications will be based on existing production
  systems and provide important guidelines for future implementers,
  the WG aims at publishing the RFCs on the Standards Track and will try
  to advance the core document at least to Draft Standard status as fast
  as possible.

  d) Further work

  The WG will offer advice to previous and new registrants of URN
  namespaces.  It will screen the legacy URN namespace definition
  documents and will provide advice to their registrants regarding
  necessary steps to bring these registrations in line with the
  existing standards and the revised URN core specifications, and
  regarding other issues, if such are found.

  The WG can take on work to update well-established URN namespace
  definitions other than the aforementioned cases of bibliographic
  identifier based URN namespaces, upon a case-by-case decision, and
  in collaboration with the respective original registrating party
  (or its legitimate successor); doing so will require an update to
  this charter.


WG Input / Output
+++++++++++++++++

Input documents:

  RFC 2141
  RFC 3406

  RFC 3187
  RFC 3188
  RFC 3044

  RFC 2483
  RFC 2276
  RFC 1737
  RFC 2169

Goals and Milestones (rough and preliminary):

  Dec 2010   WG Last Call on "core document set" ( a) + b) above )
  Feb 2011   core document set forwarded to IESG
      2011   work on supporting documents (guidelines, URN resolution)
      2012   implementation report for promoting 2141bis to Draft Std.

Internet-Drafts:

  draft-ah-rfc2141bis-urn          (-00: submitted March 2010)
  draft-hakala-rfc3187bis-isbn-urn (-00: submitted March 2010)
  draft-hakala-rfc3188bis-nbn-urn  (-00: submitted May 2010)

Request For Comments:

  none so far

_______________________________________________
urn mailing list
urn@ietf.org
https://www.ietf.org/mailman/listinfo/urn


From A.Hoenes@TR-Sys.de  Mon May 24 14:47:46 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94E733A6CE0 for <urn@core3.amsl.com>; Mon, 24 May 2010 14:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.4
X-Spam-Level: 
X-Spam-Status: No, score=-95.4 tagged_above=-999 required=5 tests=[AWL=-0.166,  BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gca4L3hJLcSf for <urn@core3.amsl.com>; Mon, 24 May 2010 14:47:44 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 236053A67F5 for <urn@ietf.org>; Mon, 24 May 2010 14:47:41 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA127527526; Mon, 24 May 2010 23:45:26 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id XAA22138; Mon, 24 May 2010 23:45:25 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201005242145.XAA22138@TR-Sys.de>
To: stpeter@stpeter.im
Date: Mon, 24 May 2010 23:45:24 +0200 (MESZ)
In-Reply-To: <4BEB2A3F.1090309@stpeter.im> from Peter Saint-Andre at May "12, " 2010 "04:22:55" pm
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 8bit
Cc: urn@ietf.org
Subject: Re: [urn] A first cut at the Draft Charter for the proposed URNbis WG
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 24 May 2010 21:47:46 -0000

Peter,
many thanks for your support and the detailed comments.
Juha Hakala already has responded to many details.  Below are my
notes (inline), after a revised draft charter has been produced.


At Wed, 12 May 2010 16:22:55 -0600, Peter Saint-Andre <stpeter@stpeter.im>
wrote:

> Hi Alfred,
>
> Here is some feedback on the proposed charter. My apologies for the
> delay.

We have discussed your comments (and other comments received)
and a second cut on the draft charter has just been posted.

>
> In general, RFC 5434 will give you plenty of good ideas about
> formulating a charter. It is especially important to clearly define
> the problem statement.

Of course, it already had been taken roughly in account earlier this
year when the procees to re-target the PersID / URN-R effort to the IETF
had been started.

>
> On 4/27/10 11:05 AM, Alfred HÎnes wrote:
>> Folks,
>> Based on work done by Juha Hakala in February, I have updated
>> and amended the Draft Charter and hereby bring it to the urn list
>> for discussion.   Comments welcome!
>>
>> ...
>>
>> ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
>>
>> Uniform Resource Names, Revised (URNbis) -- Draft Proposed WG Charter
>> ========================================
>>
>> Last Modified:  2010-04-26 [AH]
>>
>> Chair(s):
>>   o   Juha Hakala  <juha.hakala@helsinki.fi>
>>   o   N.N.
>
> The chairs will be chosen by the Area Directors. I agree that Juha is a
> good candidate, but please leave this blank for now.

Done.

>
>> Applications Area Director(s):
>>   o   Alexey Melnikov  <alexey.melnikov@isode.com>
>>   o   Peter Saint-Andre  <stpeter@stpeter.im>
>>
>> Applications Area Advisor:
>>   o   Peter Saint-Andre  <stpeter@stpeter.im>
>
> We don't yet know if which AD will be the advisor, so please leave this
> blank.

Done.

>
>> Mailing Lists:
>>   General Discussion: urn@ietf.org
>>   To Subscribe: https://www.ietf.org/mailman/listinfo/urn
>>   Archive: http://www.ietf.org/mail-archive/web/urn/current/maillist.html
>>
>>   Related lists (used for IANA registration procedures (BCP 35/66):
>>     urn-nid@ietf.org, uri-review@ietf.org
>>
>> Additional information will be available at:
>>   http://tools.ietf.org/wg/urnbis
>
> Not yet assigned, so please leave this blank.

Put in placeholder, but left list information.

>
> In fact you can delete everything up to this point because it's
> administrivia. :)

There's a lot of value in havint most of the information,
in particular for newcomers to the IETF.  And this way, the
submitted text hopefully better resembles current practice
of WG charters.

>
>> Description of Working Group:
>>
>>   Uniform Resource Names (URNs) are persistent identifiers for
>>   information resources.
>
> RFC 2141 says:
>
>    Uniform Resource Names (URNs) are intended to serve as persistent,
>    location-independent, resource identifiers.
>
> I think the "location-independent" part is important so people don't
> think that URNs exist for the purpose of resolving a URN into a location
> where the representation of a resource can be retrieved.

This quotation from RFC 2141 now is literally included in the
draft charter.

>
>> The RFCs defining URNs and services based on
>>   them were published 1997-2001.  Since then, the URN system has gained
>
> Are URNs really a "system"?

Anything structured somehow and composed of interacting components
is a system.
URNs are part of the structured URI framework; and for URNs, there are
the original namespaces underlying the URN NIDs and the related actors
and frequently computing systems for the assignment of identifiers and
achieving their uniqueness and persistence; so there is a lot of
structure and components.

>
>>   popularity.  Among the more traditional parties with deep interest
>>   in persistent identifiers and making heavy use of URNs are national
>>   libraries; solely within this area, tens of millions of resources
>>   have been assigned URNs; this enables efficient searching of and
>>   persistent linking to these documents.
>>
>>   This working group is chartered to revise the key RFCs describing
>>   the URN system, including RFC 2141 (URN Syntax) and RFC 4306
>>   (Namespace Definition Mechanisms),
>
> I think we need to be very clear about what kind of revisions we're
> talking about here.

The 'second cut' of the draft charter is significantly restructured
and amended and it elaborates at a much more detailed level on the
problem statement and the distinct tasks the WG is going to work on --
both at a high, summary level and down to the various existing RFCs,
grouped in core URN documents, URN namespace documents for
bibliographic identifiers, URN resolution, and "other".

>
>> update important URN namespace specifications,
>
> I think we'll want to list these separately and limit the scope of the
> WG to only the listed namespace specifications (to be expanded only on
> rechartering).

Essentially done, as already sketched above.

>
>>   and to screen and update RFCs describing URN resolution principles
>>   and practices.
>
> Do we really want to take on URN resolution?

Yes.  URNs would be an academic exercise without resolution.
The current namespace registration template requests detailed per-NID
considerations, and the needs of the implementation and deployment of
an interlinked resolution system for URNs based on bibliographic
identifiers is the basic driving force behind this effort.
The group shall review existing RFCs specifically dedicated to URN
resolution in general, determine the degree of their ongoing relevance,
and decide which documents deserve updates.

>
>>   For RFC 2141, this revision will include in particular: an update of
>>   the formal syntax specification in the light of the URI Standard
>>   (STD 66, RFC 3986) using the ABNF from STD 68 (RFC 5234), a revision
>>   of URN examples from imaginary ones into existing URNs in current
>>   namespaces, providing a formal IANA registration for the 'urn' URI
>>   scheme using the template from BCP 35 (RFC 4395),
>
> Do we have agreement that the URN space is founded in a URI scheme?

For the stakeholders of the BOF proposal, this has never been in doubt.
The lack of a formal URI scheme specification so far and the resulting
need for such is now spelled out even more clearly in the second cut
at the draft URNbis charter.

>
>> and an update of
>>   the section describing how URNs are resolved in the Internet.
>
> By "section" do you mean RFCs 2169 and 2483?

No, this statement was in context of RFC 2141[bis], and in particular
RFC 3406[bis].

>
>>   RFC 3406 (BCP 66) needs a less pervasive update, mostly to align it
>>   with the current IANA procedures and terminology as defined in BCP 26
>>   (RFC 5226).
>>
>>   Regarding URN Namespace specifications, the WG will focus on updates
>>   for the definitions of URNs based on bibliographic identifier systems,
>>   in particular RFC 3187 (URN Namespace for International Standard Book
>>   Numbers) and RFC 3188 (URN Namespace for National Bibliography
>>   Numbers).  In both cases, the respective identifier system and/or the
>>   institutions and roles involved in their assignment and resolution
>>   have evolved significantly since these RFCs have been published.
>>   In particular, the URN:ISBN namespace needs to be extended according
>>   to the revision of the international ISBN standard, and the usage of
>>   the URN:NBNs has grown rapidly and there is a need to align the
>>   namespace registration with experience and current practice.
>>   In a second stage, RFC 3044 (URN Namespace for International Series
>>   Standard Number) will be checked for the necessity of an update.
>
> Those efforts seem worthwhile, although again we'll want to tightly
> scope the work.

Please look at the revised draft charter.
We hope the restructured and amended text addresses thes concerns.

>
>>   Thus, in support of the current international efforts to establish a
>>   distributed, linked system of URN resolution systems for bibliographic
>>   identifiers, the primary aim of the WG is an updated set of standards
>>   documents, which is needed to assure uniformity and interoperability
>>   of the URN resolution services.
>
> Is this new work, or revision of existing work?

The work done in PersID is new, but based on seminal national work.
RFC 2141 is a Proposed Standard and RFC 3406 is a BCP, but RFC 2141
in its present form, has no chance of promotion on the Standards Track
because of their reliance on Obsoleted documents and the lack of
compatibility with the terminologu and formal description in present
Full Standards.  The URN namespace documents related to bibliographic
identifier systems presently are only Informational RFCs.
The National Libraries want to base their work on standards.

Therefore, the ultimate objective is to get PS for the revisions
of the latter documents immediately, and to progress a RFC 2141bis
document on the Internet Standards maturity latter as fast as
possible, following the time scale envisioned in BCP 09, and to
publish a revised BCP 66 compatible with current IANA guidelines.

>
>>   Alongside the modernization of these core RFCs for URNs and specific
>>   URN namespaces, the working group will also consider a revision of
>>   earlier RFCs related to the principles of URNs and URN resolution,
>>   such as RFC 2483 (URI Resolution services necessary for URN
>>   resolution), RFC 2276 (Architectural principles of Uniform Resource
>>   Name Resolution), RFC 1737 (Functional requirements for Uniform
>>   Resource Names) and RFC 2169 (A trivial convention for using HTTP in
>>   URN resolution).  All these must be checked; if the document is still
>>   deemed relevant, it will be modernized.
>
> That sounds like a lot of work. Perhaps a phased approach will be
> needed?

Indeed.
The order of mention in the 'first cut' was intended to reflect that
phased approach.  This is spelled out more explicitely in the revised
draft charter.

>
>>   The working group will also consider the possibility of publishing
>>   Best Current Practices on how to resolve the URNs utilizing the
>>   existing Internet protocols such as HTTP.  This BCP will be based on
>>   the European URN resolution infrastructure under construction in the
>>   project PersID.
>
> Do we have references or I-Ds about that work? How can the URNbis WG (if
> formed) collaborate with the PersID project?

We expect to have at least one representative of most organizations
participating in PersID will actively contribute to the WG.  We also
expect that the ISO registration authorities for ISBN and ISSN as well
as representatives from the Library of Congress (which is managing the
assignment of non-ISO 3166 branches for NBNs) will review the documents
produced by the WG.

>
>>   Since the revised specifications will be based on existing production
>>   systems and provide important guidelines for future implementers,
>>   the WG aims at publishing the RFCs on the Standards Track and will try
>>   to advance the core document at least to Draft Standard status as fast
>>   as possible.
>
> What is "the core document"? Do we think it will need to be cycled at
> Proposed Standard? If so, let's clarify that. Pushing for Draft Standard
> might be premature.

The "core URN specification" (under revision by the proposed WG)
is comprised of RFCs 2141 and 3406.  We do not want to exclude
prematurely the need to perfome another iteration on 2141bis for DS,
but it is our hope that an implementation report for 2141bis might
suffice for promotion to DS after the period specified by BCP 09.

It would doubtlessly be very much appreciated if it became viable
to also promote the other core WG documents (revised URN namespace
definition documents for bibliographic identifieds) on the STDs Track,
but past experience of the inertia in the IETF and IESG let me
personally doubt this can be achieved (help proof me the contrary!).

>
>>   The WG can take on work to update other well-established URN
>>   namespace definitions upon a case-by-case decision.
>
> Perhaps text like this would be helpful:
>
>    Although the group may provide advice regarding other URN namespaces,
>    it will prioritize work on the above-mentioned namespaces first and
>    will take on additional tasks as official milestones only after
>    rechartering.
>
> I think that if we don't have some text like that, the IESG will be
> concerned about the open-ended nature of the charter.

The revised draft charter text puts more emphasis on "offering advice",
i.e. offering a service to URN namespace registrants (like e.g. DHCWG
or DNSEXT do for DHCP/DNS related work in other WGs or by Individual
submisisons), and it spells out the need to update the charter if
the WG wants to undertake additional concrete document development
in that area.

>
>> Input documents:
>>
>>   RFC 2141
>>   RFC 3406
>>
>>   RFC 3187
>>   RFC 3188
>>
>>   RFC 2483
>>   RFC 2276
>>   RFC 1737
>>   RFC 2169
>>
>> Goals and Milestones (preliminary):
>>
>>   Feb 2010   Initial WG formation as 'URN-R' (outside the IETF)
>>   Mar 2010   WG work plan completed, brought to IETF APP Area
>>   May 2010   first Internet-Drafts for most important core document
>>              revisions
>>   Jul 2010   Presentation of the group & early results at IETF 78 (BoF)
>>   Aug 2010   Formal establishment of the IETF WG
>
> Those might be helpful to you, but none of them belong in the milestones
> for the WG since they would predate WG formation.

Was there for information purposes; dropped now.

>
>>   Dec 2010   WG Last Call on WG core document set
>>   Feb 2011   core document set forwarded to IESG
>>       2011   work on supporting documents (guidelines, URN resolution)
>>       2012   implementation report for promoting 2141bis to Draft Std.
>
> We don't need to define detailed milestones at this time -- IMHO it is
> more important to come to agreement on the problem statement and
> deliverables. The milestones will flow from that.

Left these four lines in the new version to outline the general idea
of the schedule we have in mind.

>
>> Internet-Drafts:
>>
>>   draft-ah-rfc2141bis-urn          (-00: March 2010)
>>   draft-hakala-rfc3187bis-isbn-urn (-00: March 2010)
>>   draft-hakala-rfc3188bis-nbn-urn  (-00 due for week 18/2010)

The latter has been submitted now (last week), thus updated this item.

>>
>> Request For Comments:
>>
>>   none so far
>
> Naturally. :)
>
> Peter
>
> --
> Peter Saint-Andre
> https://stpeter.im/


Kind regards,
  Alfred HÎnes.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+


From A.Hoenes@TR-Sys.de  Mon May 24 15:10:10 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 542DD3A6D00 for <urn@core3.amsl.com>; Mon, 24 May 2010 15:10:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.853
X-Spam-Level: 
X-Spam-Status: No, score=-95.853 tagged_above=-999 required=5 tests=[AWL=0.296, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GCm2NxdjDzen for <urn@core3.amsl.com>; Mon, 24 May 2010 15:10:06 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id D2BDD3A6CEC for <urn@ietf.org>; Mon, 24 May 2010 15:10:03 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA127678949; Tue, 25 May 2010 00:09:09 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id AAA22174; Tue, 25 May 2010 00:09:08 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201005242209.AAA22174@TR-Sys.de>
To: rden@loc.gov
Date: Tue, 25 May 2010 00:09:08 +0200 (MESZ)
In-Reply-To: <04c301cafb84$f7b416f0$e71c44d0$@gov> from "Ray Denenberg, Library of Congress" at May "24, " 2010 "05:06:24" pm
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Cc: urn@ietf.org
Subject: Re: [urn] A second cut at the Draft Charter for the proposed URNbis WG
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 24 May 2010 22:10:11 -0000

Ray,
thanks for your feedback.

>   "The lack of a formal registration of the 'urn' URI scheme fosters
>   recurring discussions on what URNs are.  "
>
> Huh?  Is this to imply that 'urn' is not a URI scheme?

No.  But there's no registration document for it (yet), as requested
by the current URI standard and its accompanying BCP for URI scheme
registrations, RFC 4395.
This is one of the steps for 2141bis !  -- cf.
  <http://tools.ietf.org/html/draft-ah-rfc2141bis-urn-00#section-7>

>
> http://www.iana.org/assignments/uri-schemes.html   says it is.
>
> At least is says it is a "permanent" URI scheme.  Are you asserting that
> it's never been formally registered (even though it's permanent, whatever
> that means)?

Yep.  RFC 2141 predates RFC 4395, and even RFC 2717.
Those days, Jon Postel was the RFC Editor and IANA, all in one person,
and IANA registrations have been done very informally, and not rarely
without much record.  :-)
The -00 version of the rfc2141bis draft recalls the history of the
related documents in its introduction; cf.
  <http://tools.ietf.org/html/draft-ah-rfc2141bis-urn-00#section-1.1>


>
> --Ray


Kind regards,
  Alfred.


P.S.: My apologies for a 'Freudian' typo in the draft charter:
  please read "RFC 3406" wherever erroneously "RFC 4306" is written.
  Some time ago, I dealt with the IKEv2-bis (4306bis) draft; that
  number must have been too sticky in my brain.  :-D


From A.Hoenes@TR-Sys.de  Mon May 31 02:20:52 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 245103A69FE; Mon, 31 May 2010 02:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.149
X-Spam-Level: 
X-Spam-Status: No, score=-96.149 tagged_above=-999 required=5 tests=[BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-6cdr36zdTa; Mon, 31 May 2010 02:20:51 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 8BE683A69EC; Mon, 31 May 2010 02:20:49 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA165417587; Mon, 31 May 2010 11:19:47 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id LAA03229; Mon, 31 May 2010 11:19:45 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201005310919.LAA03229@TR-Sys.de>
To: urn@ietf.org, apps-discuss@ietf.org
Date: Mon, 31 May 2010 11:19:45 +0200 (MESZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Subject: [urn] New Version Notification for draft-ah-rfc2141bis-urn-02 (fwd)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 31 May 2010 09:20:52 -0000

Folks,
the main reason for this update was adjusting the pointer for
discussion: the draft now points to the uri AT ietf.org list.

At this opportunity, a couple of clarifying remarks have been added,
based on items appearing in the discussion on the draft charter of
the proposed URNbis WG and the BoF proposal.
There are no technical changes since -00, but numerous editorial
improvements have been performed and the missing summary delta
information from RFC 2141 is now supplied in Appendix D.

Please note that -01 was erroneously submitted with a significant typo;
please ignore it.
The diff information from draft version -00 to -02 is available at:
  http://tools.ietf.org/rfcdiff?difftype=--hwdiff&url1=draft-ah-rfc2141bis-urn-00.txt&url2=draft-ah-rfc2141bis-urn-02.txt

Kind regards,
  Alfred.


----- Forwarded message from IETF I-D Submission Tool -----

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> To: ah@.TR-Sys.de
> Message-Id: <20100531090206.632E73A6A17@core3.amsl.com>
> Date: Mon, 31 May 2010 02:02:06 -0700 (PDT)
> Subject: New Version Notification for draft-ah-rfc2141bis-urn-02
>
> A new version of I-D, draft-ah-rfc2141bis-urn-02.txt
> has been successfully submitted by Alfred Hoenes and posted
> to the IETF repository.
>
> Filename:         draft-ah-rfc2141bis-urn
> Revision:         02
> Title:            Uniform Resource Name (URN) Syntax
> Creation_date:    2010-05-31
> WG ID:            Independent Submission
> Number_of_pages:  21
>
> Abstract:
>
> Uniform Resource Names (URNs) are intended to serve as persistent,
> location-independent, resource identifiers.  This document serves as
> the foundation of the 'urn' URI Scheme according to RFC 3986 and sets
> forward the canonical syntax for URNs, which subdivides URNs into
> "namespaces".  A discussion of both existing legacy and new
> namespaces and requirements for URN presentation and transmission are
> presented.  Finally, there is a discussion of URN equivalence and how
> to determine it.  This document supersedes RFC 2141.
>
> The requirements and procedures for URN Namespace registration
> documents are currently set forth in RFC 3406, which is also expected
> to be updated by an independent, revised specification.
>
> Discussion
>
> This draft version has been obtained by importing the text from RFC
> 2141 into modern tools and making a first round of updating steps.
> It is intended to serve as one of the starting points for an effort
> to bring URN RFCs in alignment with STD 63, STD 68, BCP 26, and the
> requirements from emerging distributed national and international URN
> resolution systems, and advance them on the IETF Standards Track.
>
> Comments are welcome on the uri@ietf.org mailing list (or sent to the
> document editor).
>
>
>
> The IETF Secretariat.
>

----- End of forwarded message from IETF I-D Submission Tool -----


From A.Hoenes@TR-Sys.de  Mon May 31 10:06:07 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A1643A67FF; Mon, 31 May 2010 10:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.149
X-Spam-Level: 
X-Spam-Status: No, score=-96.149 tagged_above=-999 required=5 tests=[BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8I42ag7u8lue; Mon, 31 May 2010 10:06:06 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 4AE943A67A1; Mon, 31 May 2010 10:06:04 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA167135499; Mon, 31 May 2010 19:05:00 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id TAA05428; Mon, 31 May 2010 19:04:58 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201005311704.TAA05428@TR-Sys.de>
To: urn@ietf.org, apps-discuss@ietf.org
Date: Mon, 31 May 2010 19:04:57 +0200 (MESZ)
References: <201005310919.LAA03229@TR-Sys.de>
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Subject: Re: [urn] New Version Notification for draft-ah-rfc2141bis-urn-02 (fwd)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 31 May 2010 17:06:07 -0000

Correction:

Of course, the final quotation in the announcement sent out earlier
today should say (as corrected in the -02 draft version):

                               vvvvvvvvvvvv
|  Comments are welcome on the urn@ietf.org mailing list (or sent to the
|  document editor).

My apologies for possible confusion.

Kind regards,
  Alfred.

