From nobody Tue Feb 5 23:04:12 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17A79128D09; Tue, 5 Feb 2019 23:04:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kXarXbBonoGi; Tue, 5 Feb 2019 23:04:08 -0800 (PST) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBC53124B0C; Tue, 5 Feb 2019 23:04:04 -0800 (PST) Received: from [192.168.45.81] ([176.74.57.181]) by mrelayeu.kundenserver.de (mreue109 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MKbc2-1gYeRK1lls-00L1uZ; Wed, 06 Feb 2019 08:04:02 +0100 From: "Dirk Kutscher" To: din@irtf.org Cc: dinrg-chairs@irtf.org Date: Wed, 06 Feb 2019 08:03:59 +0100 X-Mailer: MailMate (1.12.4r5594) Message-ID: MIME-Version: 1.0 X-Provags-ID: V03:K1:vMT0RY+FohayON1Ya/UqfwvVvyxPCCGMxcQBcqWK8qTiaI395O3 AaMlhz1z8CXny+4oH2yHJc07h6kMh8FaPAKTVkOoWpmQxhWnFv8fn0rigYsPyiNtCVCmQ5h oqxNodyGufCUJMwv3ryJ8hukrh/qyW6PkGukT67Xn996PfFqwFdHZBtOORN5OBs+EG3xtfc RkgnBwc3TvwQFefKiwyog== X-UI-Out-Filterresults: notjunk:1;V03:K0:6EkEGEvecOg=:HQWLvLPP+5Oy2YXWLuZ3hA ORrkQ3xehACikh2ojC9zHSdVPYK9VgTtcDD4ddu6bF0ryL5rDiwmmBXhMGuJOeSd42p/q3lwN Zhuf4uTolmjB2DchZhAlF1HQVCSLFGCqWBRqSu6rcaHhZd5sUXxaD4h1tInMi72PscFaoietS 5ZrvKVoztRPF6copnchMV3zQk7U15uumLkUdnpzpfcK0JWUunRdFCe0baimfWELtzdigfgfkE /o6NfmJi+kk/N2+LPKZC97GObMgTJkNAXD6l5wcZntBrrIrGuYa1CoS+kSnlortXZpgjV1PCv kmubfe8qkSA6cUp5zjQkOy+okDZVt40ZJl8b7Tjga1EzdC7fby9rkg/se8O6EW3x/FoV9iXMb 6/PwpIBppJz3KQHJLJ5IxMZRW6DMeRPaqOesdE9g925nAmX5zDN+x1zpl3PSFkECcIlRvixiw 4v6z2RJayJzVaUlfGkW5Bcfx5nCZeJMKjYwIfB4Z30gCviXljQOByXQVIaw18Q474Nzk07Hcm p8KVkBNvcHisN1nLzQAypnTsQyhcDCZcx73JLs2us+3CqzLXp1bc7CI/VFBNYk9/FL7onNhmj /AzINsqBnhI0rkGLptnQw/aoC016WJWEidTvfR5FGXJuuifuY/GxTxLA4a5ZZJiM8Ztw9aw+h 7Pz6ynL9TcM/VJuz4l3EyDAYnYpepvW+ugNxrvIYv9rsqHWHKFyOvSPl2VQvVw7BGbdjv0Kdh FF8c4L7Lgb5HzSh7vdFlPjPBG7GUutmTGfHGZLOhkQRfOhqAnTev2Cur0GI= Archived-At: Subject: [Din] Inviting proposals for DINRG agenda @ IETF-104 X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2019 07:04:11 -0000 Hello DINRG, we are starting the agenda planning for DINRG @ IETF-104 in Prague. Please let us know in case you are interested to present/discuss something. Thanks, Melinda and Dirk From nobody Thu Feb 7 00:14:41 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7E2D1310F3 for ; Thu, 7 Feb 2019 00:14:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.234 X-Spam-Level: X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MQcGCAkQs__m for ; Thu, 7 Feb 2019 00:14:37 -0800 (PST) Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA6B1130EF1 for ; Thu, 7 Feb 2019 00:14:37 -0800 (PST) Received: from fencepost.gnu.org ([2001:470:142:3::e]:47516) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1grepH-0002iA-NV for din@irtf.org; Thu, 07 Feb 2019 03:14:30 -0500 Received: from [2001:1620:fe9:0:52a9:7e19:f0bd:5dd6] (port=47802) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1grepG-0008RK-9M for din@irtf.org; Thu, 07 Feb 2019 03:14:27 -0500 To: din@irtf.org References: From: Christian Grothoff Openpgp: preference=signencrypt Autocrypt: addr=grothoff@gnunet.org; prefer-encrypt=mutual; keydata= mQINBFSG/g0BEADfUtc2WA8+OWiNVuNuaU5CIFB/6Netaem0tXAc5VF8c/Dr/BbteSG4ZAWg CGioO/sqQ08XbYSdot1/zybFqAaD2Tlz99+GFLDYSMSDv6SkaAww0cGbobjkAO3h1ojeR8gw j2+V2DuM9VLsmB0ITH3zXlLg1wbDUeIpOtk12DWqOTFN0v6xhV3JVdFsMmiM21iyo14FIxZm RTJulrwQFi/LcrUR7kDSjuwv3GzmVy6KSArri6fSZec4os6WJM69+N3kV3SwoWxjikfUodaF +kOMXRyfEDX2ebyvveIvMl2BxNu7JUnFY0AHXnxeNbfkpLCuFnH4cVvK14I+hHOa/JTnF77f 7sWb+E0588YLL7geWucJfw94OzM1z4l/BLSyYiY3PJWRUHwkY7FV3cQGgTfrvbX3afa9Vi2b KHbgsgnOpe55FFJTRhZlGJMrgeNsoRKeivFaSa3HLhkV56VG268IM7iao+soVfeWKTOOSQGV eG6VrY7MUjhNfBbYfuSOW9CdF3p3XbI8DF68id0OQRUIihS42+kSGCZVY31Mx8+bZj+7+Qhs hZrARdrdmDg5IvJykEpn7aKpfyhf1sCfu/gwrpZ90IcaYoeafk6qWcf8JL+5VYHewWjfZ7pF tlurt+hlrdNbqDQ9oHtIsevbgsPlh40BZ0kv2vLK5b+hQ5gd3QARAQABtChDaHJpc3RpYW4g R3JvdGhvZmYgPGdyb3Rob2ZmQGdudW5ldC5vcmc+iQI4BBMBAgAiBQJUhwfWAhsDBgsJCAcD AgYVCAIJCgsEFgIDAQIeAQIXgAAKCRCTnmvh4p/DzLo3EADDO4FO9ZSwG2dWMVqzSflJF2G1 SdNS0AnzP1B7YBv6WNqjtwDhYbo4txZiz+R3e0RSguhcURHCa1EVsTErBU9zHV9+p0mGJ310 rhst3Q54pXdQSVAU8wteKjghRoX+Tn0dldVfowRdYNHYb+g1ReuDc6V7yZV3/T3dQMOg4MTj ZbZGAF5qaYTmB8Tofuv5xtsqoXkj0h71qEMEbBbkekjZwYW35awloFfIEXFAM6d6ZBHDQ+TJ oTZN+RGAvSzirGTKhhS91vDsJ94DaoPiWtqaQm55cBxYZY/UMDSfGlsvkZDqGeT+aL/uBnvL O3KinYPCtYRbVzaEtaJ1r+CsZknB9eDuG7kuzVHMI8HkyqD/CaTKc5qk5a28vPvcbkupZzsr qJDu/e3CD16cJStwhLM79+CVp/ihDUS8yGiBS76ROfwOqI6niWw+oti7oGieb3QIxnRqYxDU b6UOe0mvGcrwxdrin1StvcW9HVghrvN4Mx+Ec1Us7SOcrybdL6ILgu9zMJTFJemPiuL6AGZL mzJ3m3uTu10WkqmG6Rj4fU5t7vBzNtFdj3E637jSMH2Fgkz3Athrad4+9tMBlvJXpzNJvYZ2 EzAIXLNYOCI5Cjhz5DguSIBJYc1EzTgwCPQv4w0Qg5aik9De24DHaghsdXrI3L1k78m88kjd vBzu3fmEzbkCDQRUhv4NARAAoi0SvMUnd5XSZVSmbwfge2p9KeGVVcaz99fgrUTgCwfovVd1 MEXh8FCtxja4xZiuwSGUARuPAXpzhcK1L9vai25GV+y4SALp3wg1/GrsHtEsm+wm7AeIq0ut XnjfnUzfliIIKwt0aGW/zGp/8rHNKh7JVUo0mPSMQfe+6tE2XOnuGDHj1ZyZalmBjVLJYMws I0tfAzU1fa0MOSnhvyP5TFFj6PWKSajEOsFuIR/zceZFtJbN24lbXYwohBDBY2Ajb0y8uYBi /h350UY2mwjKHYM3mxJD3AogWIBz5HD+ueWGUTBpKwLYmN7zVxDMdL7FqGonSw9NV1XxJ3IN 1DYPPdFKStRIUiSMzyj/pp6410ms+N1MtPXDIDdcOcmNHqcnkWqBYHXGi+sYyFpe+825N75d otpEipCnIcTCBjn3RdqFOzT4+airtL7eOkzmooqtPwvNO+4Uza8+W1PLibXqXWqD0uyi1Wn2 9asF+uOEfNA4TpTXT6Df5B1X88eoHccCpPUhiNqs7dX1ye78m9oicD9IoXj3PZ0le2tHXuFc lXjuffpOW6Wt+rbqMrFp4LA4H4UXafai9B5F1JMp+xdK+V0YUT0aQSZwdHyvNsGReRnuuZKH be0xokpVM+ndra2EpsV0C3csoDOWyu7yjUyFeTfAlYBb8rn8WuLnT8xzSJEAEQEAAYkCHwQY AQIACQUCVIb+DQIbDAAKCRCTnmvh4p/DzKGQD/wLhO70IEI06MqaP41im4X7suk4zGOAcBXA csZONq450CA/WHvoMKFoCPHfoC4e1jsoifG8+emfTQhWKwW3a5G/H90a8lY8pH9tqkVUPds5 m6fbWf16xkWUQpH8QQyLwhBIF8onclrDWAHPflpnWp+wso1vxN+WRh5vL1k8dpQLUkOBmE1o vl79/z1zzOYDkOWdQ1crU2EbOXalCmOASmiFhWiYk2aosBxbzGX0JKX5NyIUzz56i9vDYqjk DFYcMMx1Z9YXsvTjglMwnIfwPmvBBgQlwqg+LOts7XF0ZoBZ3NBLpIES0wheVjXtG/T7kZey 7XABVbxK2B4mIRFIvXnHbTEGzSyY7hLCshyCMQTDCoHDOKiNZmteqhHU4zXVgyhrxkYG9iID j9yb6PCjaFwgp42rz0lLqTgmpDEIrz1MaCglhTB68wTsHYx3SH+ClNGmgWTa8dS+l/s0hgE+ WknVGn6ShMkdyYLn3QxTRhZSmRv2hG7AYSemtLxi4lLoJ3kDHLMYAponhzxLYOtc8IyNrrRU 4Tj4keG2ssHSkC9kDIMqzX53ObGkVWN6Rvu+pmZ9iumrNqI/4PyrPi3mOE7ooIkh1L/MEu2c LNWaTG5QmOK0VtYN+3G2qzcjKEpQPIDgRdZ6i7fO6jgb0iy1UJUbAoLQgUTaX99KUKeyCuiG UA== Message-ID: Date: Thu, 7 Feb 2019 09:14:22 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="39tP9esiJ2KM0J0Uw3duAqE75LNka6PQW" X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] Archived-At: Subject: Re: [Din] Inviting proposals for DINRG agenda @ IETF-104 X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2019 08:14:40 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --39tP9esiJ2KM0J0Uw3duAqE75LNka6PQW Content-Type: multipart/mixed; boundary="FlV4jbjOlDA7WDm5HWDgsu82IIUfxcKbP"; protected-headers="v1" From: Christian Grothoff To: din@irtf.org Message-ID: Subject: Re: [Din] Inviting proposals for DINRG agenda @ IETF-104 References: In-Reply-To: --FlV4jbjOlDA7WDm5HWDgsu82IIUfxcKbP Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hello DIRNG, I could give a presentation on the GNU Name System, the decentralized privacy-preserving PKI used in GNUnet, if you are interested. Best regards, Christian On 2/6/19 8:03 AM, Dirk Kutscher wrote: > Hello DINRG, >=20 > we are starting the agenda planning for DINRG @ IETF-104 in Prague. >=20 > Please let us know in case you are interested to present/discuss someth= ing. >=20 > Thanks, > Melinda and Dirk >=20 > _______________________________________________ > Din mailing list > Din@irtf.org > https://www.irtf.org/mailman/listinfo/din >=20 --FlV4jbjOlDA7WDm5HWDgsu82IIUfxcKbP-- --39tP9esiJ2KM0J0Uw3duAqE75LNka6PQW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE2EI7yzJseQcDOSnHk55r4eKfw8wFAlxb6N4ACgkQk55r4eKf w8xoLA/9FTORYo09CCmfcB9gIt2h/57XWU6mZKks9newIextbgYwHJ6DDutDyjj0 5xxjUxSzzL9Whf4V4htOtzCsYugxp1QRT1bkCWjBQA090POlpRSA172CRXGU/F20 f1bDM1s4tMBHvA3iEnx1JjQqKv4sj8XRk9iA6JDXbfsGJPQT8fwkvyEw1hGgRmdI +8dQID3nx+4heei5BLwycFON3LDzVC+LRZKWcxowKol/MsIGK0ang+TjqbgXr9om 1d5aKMZbamq9hmCQFxlBc/4V4VBADbFCjGgQZNCD0MA9+yNuWaUhEagBkxEwFrT0 CxaSLyvbfMT+lCSxGByGqnQ4Z/XWW2zI54/HolhhGyohbD6xcpsaB33JiRctyrZK wfWpG1BHeCEAfOohIvwa+CF4zwT+kMm11txuJD0kCEyiR7y9UVhuImUErv0pYyZZ biCGoLnUClxRZAa5Eahl21GdggMwto2VihzqC3HspzjMpUjxRZALwpfDjqPC1sUB svssXU2NHj+OjcBKw+ud7xUjT3fDllhvO45HFvWXcFkS4NCS6xakvC2kqYtqZ6R7 CnOdgGnVeiuG+B6md0OolC1ZXnfNJZdbYNiF1UxznFkUxYteike6HrqWHLGgplaS DiWT6qk5WTUG1lQxqySvJFO3MDbzrOXVa5Jm62zZoyXeVlnGBzI= =cHoQ -----END PGP SIGNATURE----- --39tP9esiJ2KM0J0Uw3duAqE75LNka6PQW-- From nobody Fri Feb 8 05:59:07 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFF62126C01 for ; Fri, 8 Feb 2019 05:58:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gpz-y3tXBEJU for ; Fri, 8 Feb 2019 05:58:54 -0800 (PST) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8EAE1279E6 for ; Fri, 8 Feb 2019 05:58:53 -0800 (PST) Received: by mail-lf1-x133.google.com with SMTP id q11so2614975lfd.3 for ; Fri, 08 Feb 2019 05:58:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=YUivnc0m6hvg9VoEkexuZxYRnovzj62yubNYLJuOtvA=; b=fvf3t5yDy5ErC6pxt1DSZ8gWekBjIj6IhBkxUiqBaGrha43NnM3OwlCbF+e2sXtZsi w0q3Gq7Xk5tgIrN/yVFB1qRDVv24YDii8TLxxr9EiGtbgsR3H9ynfDXraeFxr9cZM3ZA aa5jdtIutzoZRfzwDqFO9/BJGLqhmlzjz2cM+2rBnTd/+hCMVyQVtbkYWwqUexBFvadp gzYeIiMrZ2gJr06x4IXpxbavfAmlVX6GkD8kwJ1zsB6u2yuYtthUPeUKZw0FMi78Rikp kmGhUEYuOsEXcDUgF3gfSKtMfxxJUTQ6uFDJYsUey6AY0+NpQ/XBxWLDnvBgs4I9dvnp 5/Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=YUivnc0m6hvg9VoEkexuZxYRnovzj62yubNYLJuOtvA=; b=twpBr5V2spWfY3AGYDRv4ZaLWcKUACTCOHUiuOF6JkzNUzSh4iSp/UGwrTP1GwqM0w 9mJJTIVbSd5gY2h7MTziuRmiSeevakSUyGOd+aU9hfZk2D1B4njvX/+RCcjnuZmmls34 YHbtntxACoAWpJPkvlZP9ZywsQGjbHzhE0GxFOke+PlNs/g3Lj+qVqyWiffzFfYm1g5u cRr5qIFF1V6b94c3sstTJT2xeasWVynN7596bA3Ee3q0oqpVZH0j1riGHWF0X+AU5pv2 uuRMW3pgAWVbsMXE9tF/GdHVYR54kGujxIXWymdV/GLhnLRTfrn8IQgUIYVcY6bhTf2B CvZw== X-Gm-Message-State: AHQUAuafFqWWHV1rfGEN827dX3mM3rlXLH7eMmUvKPIt/CuZSO+2tRg0 DAy3kn/UpG9Pxv0otAbquT4yBi7BVSRkgi6Xn3k4vg== X-Google-Smtp-Source: AHgI3IbvA+doRIzLWphvhZyHS7E/J8Afa4/5VnNPxq2nu6ls1fPw82cDb9fF3dsTGpUdOd9Uavc5ZCmJ4Ypq9oTMul4= X-Received: by 2002:ac2:561a:: with SMTP id v26mr13608672lfd.38.1549634329888; Fri, 08 Feb 2019 05:58:49 -0800 (PST) MIME-Version: 1.0 References: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> In-Reply-To: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> From: Alexander Mayrhofer Date: Fri, 8 Feb 2019 14:58:38 +0100 Message-ID: To: IETF DNSOP WG , din@irtf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Din] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2019 13:58:58 -0000 FYI, i've submitted a new revision of the DID-DNS draft (publishing Decentralized Identifiers in the DNS). The major changes in this revision are: - The registration for the _did Label is now performed via the Global Underscore Name registry (see draft-ietf-dnsop-attrleaf, currently in RFC editor queue) - The experimental "email" method uses _mailto._did as scope selector (rather than plain _did). This allows for clean seperation of other future services using the scheme. Feedback highly appreciated, Alex ---------- Forwarded message --------- From: Date: Fri, Feb 8, 2019 at 2:52 PM Subject: New Version Notification for draft-mayrhofer-did-dns-01.txt To: Dimitrij Klesev , Alexander Mayrhofer , Markus Sabadello A new version of I-D, draft-mayrhofer-did-dns-01.txt has been successfully submitted by Alexander Mayrhofer and posted to the IETF repository. Name: draft-mayrhofer-did-dns Revision: 01 Title: The Decentralized Identifier (DID) in the DNS Document date: 2019-02-08 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/internet-drafts/draft-mayrhofer-did-dns-01.txt Status: https://datatracker.ietf.org/doc/draft-mayrhofer-did-dns/ Htmlized: https://tools.ietf.org/html/draft-mayrhofer-did-dns-01 Htmlized: https://datatracker.ietf.org/doc/html/draft-mayrhofer-did-dns Diff: https://www.ietf.org/rfcdiff?url2=draft-mayrhofer-did-dns-01 Abstract: This document specifies the use of the URI Resource Record Type to publish Decentralized Identifiers (DIDs) in the DNS. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat From nobody Fri Feb 15 01:37:26 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C29E130F5F for ; Fri, 15 Feb 2019 01:37:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tUAhviMjMemu for ; Fri, 15 Feb 2019 01:37:16 -0800 (PST) Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DC6F130F8E for ; Fri, 15 Feb 2019 01:37:16 -0800 (PST) Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id C301B2804E8; Fri, 15 Feb 2019 10:37:14 +0100 (CET) Received: from relay01.prive.nic.fr (pa-th3.interco.nic.fr [192.134.4.74]) by mx4.nic.fr (Postfix) with ESMTP id BC94428047F; Fri, 15 Feb 2019 10:37:14 +0100 (CET) Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id B8F7B6424E49; Fri, 15 Feb 2019 10:37:14 +0100 (CET) Received: by b12.nic.fr (Postfix, from userid 1000) id B1FD1401CB; Fri, 15 Feb 2019 10:37:14 +0100 (CET) Date: Fri, 15 Feb 2019 10:37:14 +0100 From: Stephane Bortzmeyer To: Alexander Mayrhofer Cc: IETF DNSOP WG , din@irtf.org Message-ID: <20190215093714.t23ulbslbg52t2dp@nic.fr> References: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: Debian GNU/Linux 9.7 X-Kernel: Linux 4.9.0-8-amd64 x86_64 X-Charlie: Je suis Charlie Organization: NIC France X-URL: http://www.nic.fr/ User-Agent: NeoMutt/20170113 (1.7.2) Archived-At: Subject: Re: [Din] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2019 09:37:19 -0000 On Fri, Feb 08, 2019 at 02:58:38PM +0100, Alexander Mayrhofer wrote a message of 59 lines which said: > Feedback highly appreciated, I think that it is an important work because it brings the power of the DNS to many other identifier systems. So, I support it. May be more examples could help people figure out the use cases? "My Bitcoin address is at foobar.example" and then the Bitcoin software would query _did.foobar.example and get . I note that there exists already non-standard (and probably not really deployed) solutions in that space, some specific to a TLD Regarding draft -01: it seems OK to me. The only problem I find: > particularly the concerns around downgrade attacks when the record > is not signed Why downgrade attacks specifically? Without DNSSEC, a lot of attacks are possible. From nobody Fri Feb 15 10:47:07 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 333F4130EB3 for ; Fri, 15 Feb 2019 10:47:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bjs8lFDQuASH for ; Fri, 15 Feb 2019 10:47:02 -0800 (PST) Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6267F1271FF for ; Fri, 15 Feb 2019 10:47:02 -0800 (PST) Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 441MgR4kcJzD6P; Fri, 15 Feb 2019 19:46:59 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1550256419; bh=r8FfAtEL3sJH1OEalXB4D8W5DyAXB2yUUTETkY+brrk=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=nAKknvCN/uDhEAE54IG5ivURVoH7bI2Vq5uFmaFq5Z2vLA1bhIG+/VmllZklZcT5r M0n0Z8tUhkoiO0/y4iorbFGaPupmF7p9cPYra5gS+m3wTuF5CmjUv4Jvihszgxz8bL JY8pMnX9n94MxvwfjUKvFtbyBGI91q0k87ka4KfY= X-Virus-Scanned: amavisd-new at mx.nohats.ca Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id QXRaIdEsEQvS; Fri, 15 Feb 2019 19:46:58 +0100 (CET) Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 15 Feb 2019 19:46:57 +0100 (CET) Received: by bofh.nohats.ca (Postfix, from userid 1000) id 7E41C36FBA; Fri, 15 Feb 2019 13:46:56 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 7E41C36FBA Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 71EB040D358A; Fri, 15 Feb 2019 13:46:56 -0500 (EST) Date: Fri, 15 Feb 2019 13:46:56 -0500 (EST) From: Paul Wouters To: Stephane Bortzmeyer cc: Alexander Mayrhofer , IETF DNSOP WG , din@irtf.org In-Reply-To: <20190215093714.t23ulbslbg52t2dp@nic.fr> Message-ID: References: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> <20190215093714.t23ulbslbg52t2dp@nic.fr> User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Archived-At: Subject: Re: [Din] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2019 18:47:05 -0000 On Fri, 15 Feb 2019, Stephane Bortzmeyer wrote: > Subject: Re: [Din] Fwd: New Version Notification for > draft-mayrhofer-did-dns-01.txt I think this document should be Experimental and not Standards Track? The reference to 7929 should be normative, not informative, since you actually need to read a secion of 7929 to implement this document. I'm not sure if one should use _did.example.com for host names and _mailto._did.example.com for email addresses. I would keep that at the same level, eg: _hostname._did.example.com _mailto._did.example.com This technically also allows one to separate the two DNS zones more clearly (and could even be managed by a different group) I'm really on the fence for this document. On the one hand, it is good to have a memorable decentralized identifier, but on the other hand if you rely on DNS (and DNSSEC), is this identifier really still decentralised in the "we don't trust the USG or Verisign" way ? I guess if you interpret it as a migration strategy away from DNS, it is okay. Paul From nobody Fri Feb 15 11:47:32 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB01A130FF2 for ; Fri, 15 Feb 2019 11:47:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nomountain-net.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CA_QXf5nnMXU for ; Fri, 15 Feb 2019 11:47:28 -0800 (PST) Received: from mail-pg1-x543.google.com (mail-pg1-x543.google.com [IPv6:2607:f8b0:4864:20::543]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBC10131000 for ; Fri, 15 Feb 2019 11:47:28 -0800 (PST) Received: by mail-pg1-x543.google.com with SMTP id m1so5263265pgq.8 for ; Fri, 15 Feb 2019 11:47:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=z54FQAJNdCSUIrYq2YsY99KsIFBu5Cuxhv42fPIuKKY=; b=YgDe0EwfLjvp1hX57up2cr0j7hq3UbA+A713fPYzlL7YRm0IuIpQgv3MzDVsZU2GKR fFHvWNEpHRXy5CNLBR0rxJE1rve7yRWcYZtnT1kTt6Sqw+2kzEx5bBHd6n8mPMQYS2DT L+pYgS3dxEyHFWqcU6343iwjavVb1l/1aMWResuv3akj+FHFGMHoPnVenKUro4EJ1eaH BweUMzj89H3qNWCMwezfZlYHpXemOspa+Q5Ob4Ut46Xz6A3Aksyk5ojM9IKKDVtAgyBM Ii/14qAXv4paRQ4JUBJP28eKTweTuzIM7sqfN9Jo9i0zBg9oCqLrY/3/Vr+BaG+t7YdG sFug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=z54FQAJNdCSUIrYq2YsY99KsIFBu5Cuxhv42fPIuKKY=; b=D2I7GTXCTp1HmHEHXz5ULMjdj4ZJ7/duD7XYvzeMXpl7ZlyGaFZQgbwRHevR4wFhIz Ri8R8gV5Nl/ULPjuf3PbLFvQn3jQzLkkTqIQweINLlYR5J3iX6OWRARB8i5tVjc6VFdr 0F5cLqOfE+a8xOeHGkRpqaJmgZuOLiUV7my6JqN5iS/xuklUVkf7C19ZTHXmb/5sZtKn KKno9ERK/zQukkxDHcbr20RN39m2mdK8nChw4HYfNOfBcTqXBbo6m72FGkN3aUEGl74p rricJYQCDVeoZ4tBg9x7D1xlw/SJECca+ZHnyhKtZsZVV0akh5JR/SDus/iKMSQhdHCe 05CQ== X-Gm-Message-State: AHQUAuYD5jrVGYCc64eIUyiR+uLTnu1K7VrKUB7CpcmSvAo6qWQX/Tdt kDS56n4fmHmUUXOAb+b2CeOb X-Google-Smtp-Source: AHgI3Ia2LrvCoROuELnnvXrpITQGRY8Qs+IT1HjQdFp00fpp0vYXqAsR/5nOY0cc9xQ8AhMB86g/cg== X-Received: by 2002:a63:b94c:: with SMTP id v12mr6839382pgo.221.1550260048170; Fri, 15 Feb 2019 11:47:28 -0800 (PST) Received: from Melindas-MacBook-Pro.local ([216.67.81.81]) by smtp.gmail.com with ESMTPSA id p2sm8361866pfp.125.2019.02.15.11.47.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Feb 2019 11:47:27 -0800 (PST) To: Paul Wouters , Stephane Bortzmeyer Cc: IETF DNSOP WG , din@irtf.org, Alexander Mayrhofer References: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> <20190215093714.t23ulbslbg52t2dp@nic.fr> From: Melinda Shore Message-ID: <5a817aac-e553-d104-b9f0-f074fce235eb@nomountain.net> Date: Fri, 15 Feb 2019 10:47:26 -0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Din] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2019 19:47:31 -0000 On 2/15/19 9:46 AM, Paul Wouters wrote: > This technically also allows one to separate the two DNS zones more > clearly (and could even be managed by a different group) > > I'm really on the fence for this document. On the one hand, it is good > to have a memorable decentralized identifier, but on the other hand if > you rely on DNS (and DNSSEC), is this identifier really still > decentralised in the "we don't trust the USG or Verisign" way ? I think the question of whether or not to provide decentralized identifiers and whether or not this proposal delivers on the "decentralized" claim is out of our hands, as the core spec (which has a lot of additional problems) comes out of the W3C. I think the IETF's involvement is probably limited to their use of DNS in the resolution process. Melinda p.s. and it's probably worth pointing out that this work is being done in a W3C community group, so until it looks like it's actually going to be published as a WC3 spec I'm not sure I'd like to see IETF working group resources being spent on this. -- Software longa, hardware brevis PGP key fingerprint 4F68 2D93 2A17 96F8 20F2 34C0 DFB8 9172 9A76 DB8F From nobody Mon Feb 18 06:01:20 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92806130F61 for ; Mon, 18 Feb 2019 06:01:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W2Sz0R9Xc0_p for ; Mon, 18 Feb 2019 06:01:07 -0800 (PST) Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46428130F0F for ; Mon, 18 Feb 2019 06:01:07 -0800 (PST) Received: by mail-lj1-x230.google.com with SMTP id z25so6617611ljk.8 for ; Mon, 18 Feb 2019 06:01:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xrKMxa3eLLvIENo5zHYk34Tv2Ez2s6JXwIAaF9Z4Z70=; b=Dzj1McnijAKX1tMQM+90dUkr0SmKPokJDJz8IwUypLBsj2Sf8Eat3Eh5Uwr3zo+sgF ojVe4Czb7sMaJsQMsroK/nGfYH4xBGVej54IlAzAgELW99DyqmXsjIJtUjz0zYhtnn0r 6uh75uYqar9gN2mLHETNTutPqgzgntD3skhXo0fa/Q/5Re6htEjfLNY4gOkLsns+uu97 LRqwdd0FKxVECx9q7TvWKmVVnUOX504fbK3ljwCwpe9axj7dq6jFzLC+PeGJZBxbDqnj /C+P+PxMcC8bsgFNMPral4bsDSfNy9QnNMawFdTgsXM7JYF0/RXJxn6UoeFZlALWb56q IuUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xrKMxa3eLLvIENo5zHYk34Tv2Ez2s6JXwIAaF9Z4Z70=; b=l1ve9mK10HBXng27zFtFLKn+aqAfI5TV3j5iGVBwyNVJvTN0VP9Y/T6hoyKEEojVWj 24WKCqldyBi3woyxRWW3oB6sQlaCtIPe4g7FIwFEcfvl3T3nhqXzjIZurfvck4qR8kSC /U1oKUpvyEUT+/jafNnn0l4Y8RdToCzO2fJk69BbG2ev5yj0u1rauZwTNCO2TxdeijXX YHyS2ZtJ3dNnRr1ZWnMMnTf2OQsR+WnvOuFdPJX+aqBSiHTX+XMf8fNScxdRyI0Mt4Gm DjPAB/XQteLqFjEC/wLPNZQn5rHSqFzmCTe24w4zbJj7k61wWZ4Yyby2ceVjrHPVQUEz eEqQ== X-Gm-Message-State: AHQUAubN1M9mAYrJaL4x8wW3R69YlovuqPQJfNAe4xgAe4zdJbdPwKbm gsWI/N3/mya6wfZ4PJzdoqhDkjPwyTK0JupZMHA= X-Google-Smtp-Source: AHgI3IZA1EKSTmHE09ipOSQxS1BhyJsMXMnycZ0yt44y5du0fKczzsJqKvLQKkloBXhjOfbrNRWHAbHYQXOTQE3LHZQ= X-Received: by 2002:a2e:90cd:: with SMTP id o13mr4866643ljg.153.1550498465345; Mon, 18 Feb 2019 06:01:05 -0800 (PST) MIME-Version: 1.0 References: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> <20190215093714.t23ulbslbg52t2dp@nic.fr> In-Reply-To: <20190215093714.t23ulbslbg52t2dp@nic.fr> From: Alexander Mayrhofer Date: Mon, 18 Feb 2019 15:00:54 +0100 Message-ID: To: Stephane Bortzmeyer Cc: IETF DNSOP WG , din@irtf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Din] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2019 14:01:18 -0000 Stephane, all, [I feel cautious about continuing to cross-post this to dnsop as well as dinrg - however, it does apply to both areas, so i'll keep both groups in for now] On Fri, Feb 15, 2019 at 10:37 AM Stephane Bortzmeyer wrote: > I think that it is an important work because it brings the power of > the DNS to many other identifier systems. So, I support it. Thanks - great to hear. I'm hearing that DIDs are being used in more and more situations, so i think it makes sense to define that "bridging" protocol between the two "worlds. > May be more examples could help people figure out the use cases? "My > Bitcoin address is at foobar.example" and then the Bitcoin software > would query _did.foobar.example and get > . I will add more examples in the next revision. We also need to include an example for the "email address" use case. > I note that there exists already non-standard (and probably not really > deployed) solutions in that space, some specific to a TLD > > I'm aware of the .luxe initiative, however, i haven't yet seen any technical specifications about how the connection between DNS and Blockchains is performed. If anybody has a pointer, i'd definitely appreciate it. The other alternative proposal i've found is https://openalias.org/ - scroll down for their definition of the TXT record. They don't use DIDs as far as i understand, though. > Regarding draft -01: it seems OK to me. The only problem I find: > > > particularly the concerns around downgrade attacks when the record > > is not signed > > Why downgrade attacks specifically? Without DNSSEC, a lot of attacks > are possible. I agree, that section requires some rewording. I'm referring to the language in the OpenPGP DANE RFC here. I'm happy to work on more text, and open to suggestions :) best, Alex From nobody Mon Feb 18 06:14:24 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 768A8130F1D for ; Mon, 18 Feb 2019 06:14:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-rdjhog1gxj for ; Mon, 18 Feb 2019 06:14:20 -0800 (PST) Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7078712941A for ; Mon, 18 Feb 2019 06:14:20 -0800 (PST) Received: by mail-lj1-x235.google.com with SMTP id z25so6659405ljk.8 for ; Mon, 18 Feb 2019 06:14:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ho9vcddmU3HRwJCS+3N+h0qAJZHT5qftlioC/ynCTB4=; b=V5EZX+yIqVNFCvoSPJid3SEFP0WmsShcPDIilwzMKIO9FuSKwmoiyXK6cH+PKBX4gj 52K+4EC3SgSniwcr+TYLWnYStlY6+rjFKPEJn5cJtWTe/IL1WHa/5qW+WC0p8HgfPE4D 8QCUck7g5cNFfNBLWEVI/3n16SwvfR6cMM3EFHHRVqOSPC5fBTufjemmR24aF7n4CHmJ TWsPsBuhIDPgAw4ptgOUY6csl9ZQGVfLrWv6fZPfht5GNGOdUEKlG6wolOF/Aop6IH6z 29EozyNrWb4LwiS9M1C82GrdPy3R7RJflaARh4Ann+h2SkChWe1yMQ0u2H7dfF1epKLl WNTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ho9vcddmU3HRwJCS+3N+h0qAJZHT5qftlioC/ynCTB4=; b=e88+GD9QqdNywU/G3US2Hr6wbJQPJq34/paOt5Qu8szxTV0bTjOlufk29qs9EKRwi9 WEaYFSMGhotpqEP7rF6wIphB4ssyKZspJzLxFu3UR1uTMfWyRl+pup8Y0XohA4jOWKlN EAbCUIRQTzipJj/ynv7viCwwYs43e2lWE0k+p6Rc+s+PEtQUtYvvsIGc9wli6+AL6ORi vws1WNtwu7EuqaSm75PC/9x6vvJ/tAwKOvVdWRW621BYA2nRe9lX79rku5fEZ7bAd9O+ P+8DkYzJpIXmXz92k3VI3J4/ihMO6qHal4mBqTuX5Qil71/AkwCQWxZ80oYEe0kxFChd FPFQ== X-Gm-Message-State: AHQUAuZjaEnZcKIipGNDxxXl1EW7mCFSNMlYObXw31Nu4sQ7wvYwXbZm kVH/DjtKCSfDJuARPO9NRtYXzlKMMgEG/nLzK10= X-Google-Smtp-Source: AHgI3IZImlAD9XgP7ShpqK1vjOabjDDJGjamdIqEYzlPRj2gqTj72VsOrW/CRKAVl2cb5/YPNSncuutbk5MhVY8Gy30= X-Received: by 2002:a2e:4d7:: with SMTP id a84mr11701209ljf.86.1550499258613; Mon, 18 Feb 2019 06:14:18 -0800 (PST) MIME-Version: 1.0 References: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> <20190215093714.t23ulbslbg52t2dp@nic.fr> In-Reply-To: From: Alexander Mayrhofer Date: Mon, 18 Feb 2019 15:14:07 +0100 Message-ID: To: Paul Wouters Cc: Stephane Bortzmeyer , IETF DNSOP WG , din@irtf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Din] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2019 14:14:23 -0000 Paul, On Fri, Feb 15, 2019 at 7:47 PM Paul Wouters wrote: > I think this document should be Experimental and not Standards Track? I was torn when i did the first revision of this. I think it depends on the stability of Decentralized Identifiers themselves. Once that schema becomes widely used, i think any protocol that connects the DNS and DIDs should be Standards Track. But i leave that up to "higher forces" as soon as i find a suitable "home WG" for that. > The reference to 7929 should be normative, not informative, since > you actually need to read a secion of 7929 to implement this document. Agreed. I've considered replacing the "instruction diff" to OpenPGP with a full description in the document itself. The idea to use that scheme in email came in quite late before i wrote -00, so that section also reflects some laziness. With the "two label" hierarchy introduced in -01, i think a full description would be better anyways. Well do so in -02. Which, in turn, would allow the 7929 reference to stay informative. > I'm not sure if one should use _did.example.com for host names and > _mailto._did.example.com for email addresses. I would keep that at > the same level, eg: > > _hostname._did.example.com > _mailto._did.example.com I'd love to have a discussion about semantics of both options at some point. Maybe we can do a short meeting during IETF104? I know there are many ways to do that, and personally i'm not sure which way would be the "right" one. > This technically also allows one to separate the two DNS zones more > clearly (and could even be managed by a different group) Yep, introduces a zone cut. Then again, i'm not sure what (if we introduce that schema above) the semantics of a record right unter _did would be.. Or would that be disallowed? > I'm really on the fence for this document. On the one hand, it is good > to have a memorable decentralized identifier, but on the other hand if > you rely on DNS (and DNSSEC), is this identifier really still > decentralised in the "we don't trust the USG or Verisign" way ? The identifier is still fully decentralized, the method of discovery probably not. I've also heard that from folks from the Self Sovereign Identity community... However, they are seeking ways for people to discover DIDs. Commonly used are QR codes, but everyone is aware that replacing the QR code on an ATM machine would create an easy of "real world" phishing, so other methods of discovery are definitely worth investigating. > I guess if you interpret it as a migration strategy away from DNS, it is okay. Note that we could also create a "full loop" of verification. The DID document published behind a DID could include a link back to the domain name. I've not investigated that further, though, but it's an interesting area. So, would you be interested to discuss this in Prague? best, Alex From nobody Mon Feb 18 06:17:54 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2D8B130F0D for ; Mon, 18 Feb 2019 06:17:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iWnZg3SB3X9k for ; Mon, 18 Feb 2019 06:17:50 -0800 (PST) Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDDE112941A for ; Mon, 18 Feb 2019 06:17:49 -0800 (PST) Received: by mail-lf1-x130.google.com with SMTP id e27so12409980lfj.8 for ; Mon, 18 Feb 2019 06:17:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RLXbrScUAcZewqf8p39g2s4DCxgAmtLGF9pvUUvJuwE=; b=jgo0LEvk6tUBepJ4OkrNcd4zS/0HUrDFS+Rlew37qqz4ttZx8IYXbiNHFhPx/oEXM1 KZjgQnvsFmWWPa5d+0dc1FU3wBWIyDofKWiNhxM9zzbZF3FWFkiR+HtpY+O7kQrx1yOW vaGGAKiSDtuOTPyy7nP4gDO2Ha3tBJ/fZ6ihx55IbkPCGccnBt9DEAR6vrdCzfs64LUW r6gv9K2sz/fC3K+b+sDk0oiIcFMLt4fk0KFWCx1NI1Syz+6qbcNNyOfH4V9es6DbchcR DkcxNN4X7pDfbAxdL5wYqIWCEQgG3It0SVmdofQP0HBWb1GEvWGE2xTILbA7naDSe5gG r4Ng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RLXbrScUAcZewqf8p39g2s4DCxgAmtLGF9pvUUvJuwE=; b=fqBvCuIAjdnVwKucFxwQFmE2I258q4wxeGV+kBpKqm3nY9gqYQrvhOOI0dIZeLuhCU TtausIHEz48kYbRSlTDW/GMilKLlMYoh33lp7RFupnFjplcB7/4umN35If1qt0ZSJHZq dYrayhtxSFND0+CJgSBFtK6Mhws1UdWaqOme72K5BfppuoQXPfv/lEX31WvSaL1SJY2J cZ+rjubePZtK2feDD24QZwoHVArYpmEQlSuT9zJxMr0ZYsi7YUunec1u9bBIMDoYjS0H 0VAzNy4UKR3Sh0uZMMem9englYBZwP0gza2+lpry2BxcagbzonC+4GagO2jSCgHDuEuh u5MQ== X-Gm-Message-State: AHQUAuYA1dEGPhu6VQJJsRtOZu7VqIXmGQHGTzGUo+d10L2TDrilQSF2 jy8j+I1HNR/nbbo1VBl14JtRq5W4RnxW68smXhU= X-Google-Smtp-Source: AHgI3Iakqn8kL7je65jDGO9TXMqXiIMEhMQoHPfaUFzP1Ni2jINSEFvel0zdMWTXsaq8wi4UnIf+oGe7jv6WLpb6FNs= X-Received: by 2002:a19:7406:: with SMTP id v6mr321865lfe.33.1550499467974; Mon, 18 Feb 2019 06:17:47 -0800 (PST) MIME-Version: 1.0 References: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> <20190215093714.t23ulbslbg52t2dp@nic.fr> <5a817aac-e553-d104-b9f0-f074fce235eb@nomountain.net> In-Reply-To: <5a817aac-e553-d104-b9f0-f074fce235eb@nomountain.net> From: Alexander Mayrhofer Date: Mon, 18 Feb 2019 15:17:37 +0100 Message-ID: To: Melinda Shore Cc: Paul Wouters , Stephane Bortzmeyer , IETF DNSOP WG , din@irtf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Din] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2019 14:17:53 -0000 On Fri, Feb 15, 2019 at 8:47 PM Melinda Shore wrote: > I think the question of whether or not to provide > decentralized identifiers and whether or not this proposal > delivers on the "decentralized" claim is out of our hands, > as the core spec (which has a lot of additional problems) > comes out of the W3C. I think the IETF's involvement is > probably limited to their use of DNS in the resolution > process. I do agree. We provide the "link" from an IETF protocol to a protocol developed in another SDO. > p.s. and it's probably worth pointing out that this work is > being done in a W3C community group, so until it looks like > it's actually going to be published as a WC3 spec I'm not > sure I'd like to see IETF working group resources being > spent on this. Yes, exactly, this is a community group work right now. However, i do understand that the "upgrade" to a working group is currently underway. best, Alex From nobody Tue Feb 19 04:46:18 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E308A130ED7 for ; Tue, 19 Feb 2019 04:46:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.921 X-Spam-Level: X-Spam-Status: No, score=-5.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A4GUbxPeMCCY for ; Tue, 19 Feb 2019 04:46:10 -0800 (PST) Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58140130E91 for ; Tue, 19 Feb 2019 04:46:09 -0800 (PST) X-IronPort-AV: E=Sophos;i="5.58,388,1544482800"; d="scan'208";a="296651181" Received: from napsach022.hosting-cea.net (HELO [10.9.3.221]) ([192.54.209.59]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 19 Feb 2019 13:46:08 +0100 From: =?UTF-8?B?SsOpcsO0bWUgRnJhbsOnb2lz?= To: din@irtf.org Message-ID: <9ebf3c50-b1a2-1db1-82ff-a48210685ec1@inria.fr> Date: Tue, 19 Feb 2019 13:45:44 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Archived-At: Subject: [Din] IEEE ICBC 2019 - Call for Demos X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2019 12:46:13 -0000 IEEE ICBC 2019 (SEOUL, KOREA – May 14-17, 2019) - CALL FOR DEMOS Important Dates * Submission Deadline: March 15, 2019 * Acceptance Notification: March 29, 2019 * Camera Ready: April 5, 2019 Demo Paper Submission: The submissions should be done via JEMS (https//jems.sbc.org.br). Call for Demos: 2019 IEEE International Conference on Blockchain and Cryptocurrency (ICBC 2019, http://www.ieee-icbc.org/) invites proposals for demonstrations of research prototypes and decentralized applications. As a high-profile, leading edge forum for researchers and engineers in the field of blockchain and cryptocurrency, ICBC 2019 offers a unique opportunity to showcase applications, engage with a highly skilled and innovating audience and discuss emerging technologies and recent research prototypes with key thought leaders. Demonstrations showcasing working systems, innovative applications, groundbreaking ideas, and novel concepts related to blockchain and cryptocurrency are welcome. An award for the best demo will be presented at the ICBC 2019 closing ceremony. Submission Guidelines for Demos: Prospective contributors are expected to turn in a demo proposal in the form of a 2-page paper in IEEE conference double-column format, preferably incorporating a demo system architecture illustration. Demo papers will be peer-reviewed and accepted papers will be included in the electronic conference proceedings bundle provided to ICBC 2019 delegates and will be subsequently made available via IEEE Xplore. Demo papers should be submitted via jems by March 15, 2019; acceptance notifications will be sent no later than March 29, 2019 and camera ready versions should be uploaded via JEMS by April 5, 2019. The demo proposals will be reviewed by the ICBC 2019 demo program committee and will be approved based on availability of demo space as well as on the following criteria: * Extent and significance of the research contribution, * Potential impact on the audience, * Quality of the proposed implementation, * Presentation quality. At least one author of each accepted demo proposal is required to register for the ICBC 2019 at the full conference rate and present their demo at the scheduled demo session. Demonstrations Co-chairs Please feel free to contact the demo co-chairs if you have any questions regarding to the demo content or setup * Fan Long, U. of Toronto, Canada, * Jerome Francois, INRIA, France, * Dan Ford, IBM Research, USA, * Youngjoon Won, Hanyang University, Korea From nobody Fri Feb 22 07:03:18 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58C8F130DBE for ; Fri, 22 Feb 2019 07:03:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Vpiv-PGzlXo for ; Fri, 22 Feb 2019 07:03:08 -0800 (PST) Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20E4F12D84D for ; Fri, 22 Feb 2019 07:03:08 -0800 (PST) Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 445ZMr4wk6zJhw; Fri, 22 Feb 2019 16:03:04 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1550847784; bh=UMu5QpuZX2ngrZLyaCNL46T0Y7aWMwTY0w/QG7mv2CY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=n9VY7h5odGfC0UIUC1C2BLFX89pAWQGQmc8TRYjGSkdwvM/VYc/n+KnFQ2JKko+qC Oa4N8SyWYXsqmmyNDBn9hMTg7blc815ce1opALSJL+wfkYcMpmbOXz7WZIVt4+KCOS 65Kz65RjxiBh2djtM3NIz1VSmuOD1JqMg7649Iqk= X-Virus-Scanned: amavisd-new at mx.nohats.ca Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id umixOyv0KUCi; Fri, 22 Feb 2019 16:03:03 +0100 (CET) Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 22 Feb 2019 16:03:03 +0100 (CET) Received: by bofh.nohats.ca (Postfix, from userid 1000) id CDD6B379D; Fri, 22 Feb 2019 10:03:02 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca CDD6B379D Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C1BC340D358A; Fri, 22 Feb 2019 10:03:02 -0500 (EST) Date: Fri, 22 Feb 2019 10:03:02 -0500 (EST) From: Paul Wouters To: Alexander Mayrhofer cc: din@irtf.org, IETF DNSOP WG In-Reply-To: Message-ID: References: <154963392249.31188.16873618915255886209.idtracker@ietfa.amsl.com> <20190215093714.t23ulbslbg52t2dp@nic.fr> User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Archived-At: Subject: Re: [Din] [DNSOP] Fwd: New Version Notification for draft-mayrhofer-did-dns-01.txt X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2019 15:03:11 -0000 On Mon, 18 Feb 2019, Alexander Mayrhofer wrote: > On Fri, Feb 15, 2019 at 7:47 PM Paul Wouters wrote: >> I think this document should be Experimental and not Standards Track? > > I was torn when i did the first revision of this. I think it depends > on the stability of Decentralized Identifiers themselves. Once that > schema becomes widely used, i think any protocol that connects the DNS > and DIDs should be Standards Track. But i leave that up to "higher > forces" as soon as i find a suitable "home WG" for that. My idea was that if this is an IRTF document, not a DNSOP document, that it cannot be standards track? But I might be wrong about this. > Agreed. I've considered replacing the "instruction diff" to OpenPGP > with a full description in the document itself. that would be better, but with an informative reference so indeed people know this is the "common way" of doing this and not custom to this document. > Yep, introduces a zone cut. Then again, i'm not sure what (if we > introduce that schema above) the semantics of a record right unter > _did would be.. Or would that be disallowed? I would avoid putting something there directly, yes. > So, would you be interested to discuss this in Prague? Sure. I will also be in Prague the week before at NetDev. Paul From nobody Fri Feb 22 13:03:37 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16669130E79 for ; Fri, 22 Feb 2019 13:03:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.749 X-Spam-Level: X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QU5dKT2ft0sL for ; Fri, 22 Feb 2019 13:03:35 -0800 (PST) Received: from mail-it1-x12a.google.com (mail-it1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF26C130E5E for ; Fri, 22 Feb 2019 13:03:34 -0800 (PST) Received: by mail-it1-x12a.google.com with SMTP id l15so5244086iti.4 for ; Fri, 22 Feb 2019 13:03:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=LeXXtWSWPNCLi6TAdgWTYFiS4eI+s/MrfOvNzvn81f0=; b=sEV/YCHgX+fqXhip4CgNZF7qz0gV81JIYHwHH+2AqmH+X5Us0SbiR65YAOc277WHe4 1WwnrTMWf1qn5yGOaBg56qsZRrlOmdfleiT/r+LleuvHsgm1QLhnw7Uuc8BvhmH5DsXP UIKWd5iMODXVvZi6q3BvGBKwdwv1IleC1R7fMHSqCBtMVY7xuxUep5BoAGt6r0oNG/7K O9pxTL56GgQRbdo6Z+tNPNnXAxhc/kXBI4D7tRNgHqGXF0edtO6nlWHkk3MFJwcFe/kv GtwB0iEO2BzKxs6nXXHxcM/QQ3bVjsdvzvZcnElyncS3vFqip70FUggPtrcFuNZYZJ1j GsOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=LeXXtWSWPNCLi6TAdgWTYFiS4eI+s/MrfOvNzvn81f0=; b=iq6cgxJCQ9QzMeYbFGpwMsAJah13Y1vk96EOmbjk5Vyn6CwvBXa5/AEhX53LPFtJGz 7BzLcK3glWhQzjhYsf2K4NGz3NVcZRaEzFOC0f+I+3qcVXqfMCmOS76K1N6PHaPnSuph VjaouitjtBaBzh9oBDxStMapoKHOjm7FOLPZJbtGOgoHJ3T0aHPPeNHfK+gQZfSpiPoQ WHoOMVeAhADk0z6BD3TgtQVwBDfK0zTVSzgukYkcTzvrLndRHbBWBdE9CU99dxNTJyIc rzYZDPP13pZZ4HmWTpdcb1q8iAx+qzYG4tcxUWwvWbZtMPf1qAxtHyRY2KwZQtMmZ9FH tO1w== X-Gm-Message-State: AHQUAuazCOg1Rtl8Zx+4Bs7jp+6f9RX7w3aLTwPD/6HwFA1fBQx/AJRi 7xnMkPuUsqAhUyrqa9j1SZMsywZiKxsmjPwnjANuXQ== X-Google-Smtp-Source: AHgI3IYNUmrMmACZyoyzOm4OBzJmeztCVP7T651uXU3EOnXcrSdmYr7bswbqej+82cwvR06fQN85R7j72RgEc+HX9Fk= X-Received: by 2002:a24:ee81:: with SMTP id b123mr3421274iti.139.1550869413487; Fri, 22 Feb 2019 13:03:33 -0800 (PST) MIME-Version: 1.0 From: Ahmmad Ali Date: Sat, 23 Feb 2019 05:03:21 +0800 Message-ID: To: din@irtf.org Content-Type: multipart/alternative; boundary="0000000000007becbf058281ec62" Archived-At: Subject: [Din] (no subject) X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2019 21:03:36 -0000 --0000000000007becbf058281ec62 Content-Type: text/plain; charset="UTF-8" Ahmmad ali --0000000000007becbf058281ec62 Content-Type: text/html; charset="UTF-8"


Ahmmad ali
--0000000000007becbf058281ec62-- From nobody Fri Feb 22 21:01:53 2019 Return-Path: X-Original-To: din@ietfa.amsl.com Delivered-To: din@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62E09130EE8; Fri, 22 Feb 2019 21:01:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FuvpyfQC6akO; Fri, 22 Feb 2019 21:01:30 -0800 (PST) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE7DC128B33; Fri, 22 Feb 2019 21:01:29 -0800 (PST) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [134.102.200.7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x1N51L8r022935; Sat, 23 Feb 2019 06:01:26 +0100 (CET) Received: from [192.168.217.106] (p54A6C2FE.dip0.t-ipconnect.de [84.166.194.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 445wz451dKz1Bp8; Sat, 23 Feb 2019 06:01:20 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 X-Mao-Original-Outgoing-Id: 572590866.6634229-17fe8dc0b603461a6e0e2aefd59cfb91 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Sat, 23 Feb 2019 06:01:19 +0100 Message-Id: To: suit , teep@ietf.org, din@irtf.org, rats@ietf.org, eat@ietf.org X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [Din] Constrained Node/Network Cluster @ IETF104: DRAFT AGENDA X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Feb 2019 05:01:33 -0000 Here is my usual eclectic condensed agenda based on the DRAFT AGENDA for IETF104. Remember that there is still quite some potential for changes. cose/teep and lpwan/t2trg are some annoying conflicts that meet the eye. I also don't like that I'll have to miss the cacao BOF (vs. core), dinrg/suit, coinrg/git. All times are CET (Central European Time) =3D=3D UTC +1 hours. Note = that there is no daylight saving time in effect at the time in Europe (this starts on the Sunday *after* IETF). (You can get pure UTC times on https://datatracker.ietf.org/meeting/agenda-utc, for those who want to listen from remote.) Gr=C3=BC=C3=9Fe, Carsten SATURDAY/SUNDAY, March 23/24. 2019 -- Hackathon (including various interops) (Grand Hilton Ballroom) -- Sun 1700-1900 Welcome Reception - Congress Hall 1/2 -- Sun 1800-2000 Hot RFC Lightning Talks - Congress Hall 3 MONDAY, March 25, 2019 0900-1100 Morning Session I Congress H 3 ART dispatch Dispatch WG - Joint with ARTAREA Congress H 2 INT 6man IPv6 Maintenance WG Congress H 1 IRTF pearg Privacy Enhancements and Assessments = Proposed Research Group Karlin 3 RTG bier Bit Indexed Explicit Replication WG 1120-1220 Morning Session II Congress H 1 INT *** 6tisch IPv6 over the TSCH mode of IEEE = 802.15.4e WG Congress H 2 SEC tls Transport Layer Security WG Karlin 1/2 TSV rmcat RTP Media Congestion Avoidance = Techniques WG 1350-1550 Afternoon Session I Karlin 1/2 INT *** 6lo IPv6 over Networks of = Resource-constrained Nodes WG Congress H 2 IRTF irtfopen IRTF Open Meeting Congress H 3 SEC secdispatch Security Dispatch WG 1610-1810 Afternoon Session II Congress H 2 ART httpbis Hypertext Transfer Protocol WG Congress H 3 IAB smart Stopping Malware and Researching Threats Karlin 1/2 INT dnssd Extensions for Scalable DNS Service = Discovery WG Berlin/Brussels IRTF qirg Quantum Internet Proposed Research Group Karlin 3 RTG *** roll Routing Over Low power and Lossy = networks WG Athens/Barcel. SEC oauth Web Authorization Protocol WG Congress H 1 TSV tsvwg Transport Area Working Group WG TUESDAY, March 26, 2019 0900-1100 Morning Session I Karlin 3 ART uta Using TLS in Applications WG - 1000 - = 1100 Karlin 1/2 INT homenet Home Networking WG Congress H 3 RTG rtgarea Routing Area Open Meeting Berlin/Brussels SEC *** cose CBOR Object Signing and Encryption WG Grand Hilton BR SEC *** teep Trusted Execution Environment = Provisioning WG Congress H 2 TSV quic QUIC WG 1120-1220 Morning Session II Berlin/Brussels INT *** lwig Light-Weight Implementation Guidance WG Congress H 1 IRTF qirg Quantum Internet Proposed Research Group Athens/Barcel. RTG bier Bit Indexed Explicit Replication WG Congress H 3 TSV tsvwg Transport Area Working Group WG 1350-1550 Afternoon Session I Berlin/Brussels ART *** core Constrained RESTful Environments WG Congress H 3 OPS anima Autonomic Networking Integrated Model = and Approach WG Congress H 2 SEC mls Messaging Layer Security WG Grand Hilton BR TSV tsvarea Transport Area Open Meeting 1610-1810 Afternoon Session II Congress H 1 INT *** lpwan IPv6 over Low Power Wide-Area Networks = WG Congress H 3 IRTF*** t2trg Thing-to-Thing Congress H 2 SEC tls Transport Layer Security WG WEDNESDAY, March 27, 2019 0900-1100 Morning Session I Karlin 1/2 IRTF*** dinrg Decentralized Internet Infrastructure Congress H 3 RTG detnet Deterministic Networking WG Berlin/Brussels RTG rift Routing In Fat Trees WG Grand Hilton BR SEC *** suit Software Updates for Internet of Things = WG Congress H 2 TSV quic QUIC WG 1120-1320 Morning Session II Grand Hilton BR IRTF cfrg Crypto Forum - 12:20 - 13:20 Grand Hilton BR SEC acme Automated Certificate Management = Environment WG - 11:20 - 12:20 1500-1700 Afternoon Session I Grand Hilton BR OPS wgtlgo Technology Deep Dive - Modern Router = Architecture BOF THURSDAY, March 28, 2019 0900-1030 Morning Session I Karlin 3 ART *** cbor Concise Binary Object Representation = Maintenance and Extensions WG Congress H 3 IRTF panrg Path Aware Networking RG Athens/Barcel. RTG babel Babel routing protocol WG Congress H 1 SEC mls Messaging Layer Security WG Berlin/Brussels SEC oauth Web Authorization Protocol WG 1050-1220 Morning Session II Congress H 3 GEN git GitHub Integration and Tooling WG Congress H 1 IRTF coinrg Computing in the Network Congress H 2 IRTF maprg Measurement and Analysis for Protocols 1350-1550 Afternoon Session I Congress H 1 INT intarea Internet Area Working Group WG Grand Hilton BR SEC *** rats Remote ATtestation ProcedureS BOF 1610-1810 Afternoon Session II Grand Hilton BR ART httpbis Hypertext Transfer Protocol WG Karlin 1/2 INT *** paw Predictable and Available Wireless BOF Berlin/Brussels OPS v6ops IPv6 Operations WG Congress H 2 SEC saag Security Area Open Meeting FRIDAY, March 29, 2019 0900-1030 Morning Session I Congress H 3 ART *** core Constrained RESTful Environments WG Grand Hilton BR INT 6man IPv6 Maintenance WG Berlin/Brussels SEC cacao Collaborative Automated Course of Action = Operations for Cyber Security BOF 1050-1250 Morning Session II Athens/Barcel. INT ipwave IP Wireless Access in Vehicular = Environments WG Congress H 1 IRTF icnrg Information-Centric Networking Grand Hilton BR SEC *** ace Authentication and Authorization for = Constrained Environments WG Karlin 1/2 TSV taps Transport Services WG