From nobody Mon Oct 1 02:16:01 2018 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 DE1381277C8; Mon, 1 Oct 2018 02:15:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9yAqWIubVbmb; Mon, 1 Oct 2018 02:15:58 -0700 (PDT) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.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 1A26E124C04; Mon, 1 Oct 2018 02:15:57 -0700 (PDT) Received: from [192.168.178.66] ([77.21.39.2]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MQ6C0-1gK3Rb3mVc-00M23a; Mon, 01 Oct 2018 11:15:55 +0200 Received: from [192.168.178.66] ([77.21.39.2]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MQ6C0-1gK3Rb3mVc-00M23a; Mon, 01 Oct 2018 11:15:55 +0200 From: "Dirk Kutscher" To: din@irtf.org Cc: dinrg-chairs@irtf.org Date: Mon, 01 Oct 2018 11:15:50 +0200 X-Mailer: MailMate (1.12r5523) Message-ID: <02E2CA08-2254-4A47-9805-0920CF018357@dkutscher.net> MIME-Version: 1.0 Content-Type: text/plain; markup=markdown X-Provags-ID: V03:K1:sYRclm4uLrnC6yhUeSxeYlYnOZklRu2/ai90f3YELnInvXlPR+c EIGeSyMAU/J90e34GdGMTTxGQK1qnBjN8f4rrvkPNrolgbQ23NG6A3DBeqjCxi3303mk5Re SGEHz5ntMrG4EiZzenvuHYyMHg1SPZzLyVxGxpnVj3/ao1KFQJWLF+qh2O8xvqh/ZDPxdZh e2AojDtvgr64ocIMMiXbg== X-UI-Out-Filterresults: notjunk:1;V01:K0:j93tR+Ebh4g=:/dPrbE5indNqmQJeokgoFf qjFS1wJRlX8AWCoYkZ04nM1w4RBeR8TrfHjyIxuFuS5Hz/fyEyLHjoQxdaFG2agHON7c87+jt 9TSUVPiDX4WaHtuXTEqGEX20X2zKuaV4BgQOvyQIkVi6rNNeGIsKFVEj+TS6JWFo2adiZuBRz wXe8UyhBPboq+0pSvBPHvZMyz27nYLruePQWgDU16YYVfE5E6v1hfwRO8ooUfClusq64Ru5Uj vP30VjSQV9npVzPnFeNmyI5hnep4VvkBBxPGcM0veIocIQV372NMts21u1HtOZpw4JDq8YUIc hwFwZdE7HaMYz9vbZMM0+8CPM56G8BQFKsNRiTcSghFHSSzUx4zYh3RcSAyPSR1mEOW9tEWl6 GiVNWKefiHlJi/QPVfcX7soI2C9PuUNp6STpSIC2jm5T0PH1d7ccA67vc0a1scYp4UpRpYktG tURcsitJQJGUDKVX0OF4Ls5OjW15+fBJpyefCJMVN/HsPkynKJsYvH5h2kXKJnWjVXn8v9K+4 UDPkz0nraQzMT3QM+Gjx55uI7nXAJNtZCNBN23UyV8db9zgZc0YsPa9F+fzarpeyBx3GHEjuL 9AqHr2V0YTcgjmf2LUlW0DrGJcha+Wqgn2UFcbSSLVTpvSVZAK8qX42AQfBMQDFyufZ0FmXGu jZDXkh2v0129EmYsJ8c1atueH9EKO8hPi7oFFnDiJa4FzGXClDzRJSE3NoqFU7xvWzhf7hrEb 2XxyuqYhKc5+Y3ya Archived-At: Subject: [Din] Inviting proposals for DINRG agenda items @ IETF-103 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, 01 Oct 2018 09:16:00 -0000 Hello DINRG, we are starting the agenda planning for DINRG @ IETF-103 in Bangkok. Please let us know in case you are interested to present/discuss something. Thanks, Melinda and Dirk From nobody Tue Oct 2 09:09:11 2018 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 4B194130E72; Tue, 2 Oct 2018 09:09:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.1 X-Spam-Level: * X-Spam-Status: No, score=1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001] 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 z5y4leDHFiKC; Tue, 2 Oct 2018 09:09:08 -0700 (PDT) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.135]) (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 4A5A6130E63; Tue, 2 Oct 2018 09:09:07 -0700 (PDT) Received: from [192.168.215.128] ([85.133.27.70]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MT7ip-1gIkZi0U87-00UX8k; Tue, 02 Oct 2018 18:09:05 +0200 Received: from [192.168.215.128] ([85.133.27.70]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MT7ip-1gIkZi0U87-00UX8k; Tue, 02 Oct 2018 18:09:05 +0200 Date: Tue, 02 Oct 2018 17:09:01 +0100 Message-ID: <589c3bef-a806-4343-a3a3-14a0e2708dad@email.android.com> X-Android-Message-ID: <589c3bef-a806-4343-a3a3-14a0e2708dad@email.android.com> In-Reply-To: From: Dirk Kutscher To: Nathan Aw Cc: din@irtf.org, dinrg-chairs@irtf.org Importance: Normal X-Priority: 3 X-MSMail-Priority: Normal MIME-Version: 1.0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:HS8pErg4g0LUzBAr1AmybOhmg5STclNu34uQlPfjFzJFt5lWp7g 2rRqhBHY04t6JCmmofQgQ6d6IBuzxPz/+P6nZ7coctaJeVCfigr940VekWOlc5hMnrmshS9 xorDbvB1lzbJM9gvxD+rKauDQnaAuyGgmerRn+DPbyy+I6MJRvK9d2WtFGuEy9mb8fxOVqr 2IgZskkXfM+W1VxbVOmfg== X-UI-Out-Filterresults: notjunk:1;V01:K0:haVS2r4mtFk=:geWcAWIQsG4TXBixrOn2h8 lDJuPNdTnf2uRPrbRCvf4+2ggw60TXc95MHNGQV0WsjQlnWFLVef969QeG2unL29hOtJJsDIm 0bc2UTsP8fdnkZ5KAsSJhDCCvUK41eNSCR54X3wnxb6K2RO1hTFcrHL/knE+JEnQhCzD9Sa/Y iJ2Epf6As1rKsTeI295sU1oUDrnzuXc+0RaayhHVQ26CxeMKslyPr5vQwyJr3mlZY/ecfeth3 kNL5EvIifOjeUB0ZPgEc0COR45DzCzoq2hgs4H4sFSoYvUtYLz9f+7oWtSDGqz6QnOlfEuVMZ lm6VDLHySJ/gqE54Qitwk2AdkOcZ7oD0IHt0JJQX0R2sI2xYxfmIab1Pkd6cl+Vx9fy8Ofo6N cw344spdUf2mjUxg/fs8x2sz/2/jNWHKIGoFHkzTJwHxsWmv2V/+imOjMvxC7hExbuO/0eM2F 5we34r0nqGQ0MP/jDtW4sOc+EfHwxR4ANxL/2WCjZzLO5qrN9mqu2HrL9/d4SqF7PRL/LS7ya 0HwDpypQLrnDkLP3BHfzBNUh+fjFfLyU5pl47k/AUiqN36Ki06T7bKKePLy3c6TS8TQKSBrpX hDo+7SBh1rbHMO1jdHaWFTXWg6wGBe8j7/9N49nqYhuyYzr5WzGUjz4oYOI2slK5pPiRK0GvR PEv8KAdUrByPbqwH0ORTTAIUYQal5c/4ndG2x4LrNZMgCN6uxTZ7mH3xu4kC0D9MoPwzQdGo6 lONyBCRrfzyVsmHj Archived-At: Subject: Re: [Din] Inviting proposals for DINRG agenda items @ IETF-103 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, 02 Oct 2018 16:09:10 -0000 PGRpdiBkaXI9J2F1dG8nPkhpIE5hdGhhbiw8ZGl2IGRpcj0iYXV0byI+PGJyPjwvZGl2PjxkaXYg ZGlyPSJhdXRvIj50aGUgSUVURi0xMDMgbWVldGluZyBpbiBCYW5na29rIHJ1bnMgZnJvbSBOb3Zl bWJlciAzcmQgdG8gOXRoLjwvZGl2PjxkaXYgZGlyPSJhdXRvIj48YnI+PC9kaXY+PGRpdiBkaXI9 ImF1dG8iPkRJTlJHIG1lZXRpbmdzIGFyZSBvcGVuIGFzIGFyZSBtb3N0IElSVEYgcmVzZWFyY2gg Z3JvdXAgbWVldGluZ3MgYW5kIGFsbCBJRVRGIFdHIG1lZXRpbmdzLjwvZGl2PjxkaXYgZGlyPSJh dXRvIj48YnI+PC9kaXY+PGRpdiBkaXI9ImF1dG8iPlNlZSB5b3UgaW4gQmFuZ2tvayw8L2Rpdj48 ZGl2IGRpcj0iYXV0byI+PGJyPjwvZGl2PjxkaXYgZGlyPSJhdXRvIj5EaXJrPC9kaXY+PC9kaXY+ PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+QW0g MDEuMTAuMjAxOCAxNjo0MiBzY2hyaWViIE5hdGhhbiBBdyAmbHQ7bmF0aGFuLm1rLmF3QGdtYWls LmNvbSZndDs6PGJyIHR5cGU9ImF0dHJpYnV0aW9uIiAvPjxibG9ja3F1b3RlIGNsYXNzPSJxdW90 ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3Bh ZGRpbmctbGVmdDoxZXgiPjxkaXYgZGlyPSJhdXRvIj48ZGl2PkhlbGxvIERpcmssPGRpdiBkaXI9 ImF1dG8iPjxiciAvPjwvZGl2PjxkaXYgZGlyPSJhdXRvIj5JIGFtIGtlZW4uIFdoZW4gd2lsbCB0 aGUgSUVURiAxMDMgaW4gQmFuZ2tvayBoZWxkPzwvZGl2PjxkaXYgZGlyPSJhdXRvIj48YnIgLz48 L2Rpdj48ZGl2IGRpcj0iYXV0byI+QXMgSSByZXNpZGUgaW4gU2luZ2Fwb3JlLCBvbmx5IDMgaG91 cnMgYXdheSBmcm9tIFRoYWlsYW5kLCBJIHdpbGwgd2lzaCB0byBqb2luLsKgPC9kaXY+PGRpdiBk aXI9ImF1dG8iPjxiciAvPjwvZGl2PjxkaXYgZGlyPSJhdXRvIj5JcyB0aGlzIGFuIGludml0YXRp b24tb25seSBldmVudD88L2Rpdj48ZGl2IGRpcj0iYXV0byI+PGJyIC8+PC9kaXY+PGRpdiBkaXI9 ImF1dG8iPlRoYW5rIHlvdTxiciAvPjxiciAvPjxkaXYgZGF0YS1zbWFydG1haWw9ImdtYWlsX3Np Z25hdHVyZSIgZGlyPSJhdXRvIj5OYXRoYW4gQXc8L2Rpdj48L2Rpdj48YnIgLz48YnIgLz48ZGl2 IGNsYXNzPSJlbGlkZWQtdGV4dCI+PGRpdiBkaXI9Imx0ciI+T24gTW9uLCAxIE9jdCAyMDE4LCAx NzoxNiBEaXJrIEt1dHNjaGVyLCAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlldGYmIzY0O2RrdXRzY2hl ci5uZXQiPmlldGYmIzY0O2RrdXRzY2hlci5uZXQ8L2E+Jmd0OyB3cm90ZTo8YnIgLz48L2Rpdj48 YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luOjAgMCAwIDAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2Nj IHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPkhlbGxvIERJTlJHLDxiciAvPg0KPGJyIC8+DQp3ZSBh cmUgc3RhcnRpbmcgdGhlIGFnZW5kYSBwbGFubmluZyBmb3IgRElOUkcgJiM2NDsgSUVURi0xMDMg aW4gQmFuZ2tvay48YnIgLz4NCjxiciAvPg0KUGxlYXNlIGxldCB1cyBrbm93IGluIGNhc2UgeW91 IGFyZSBpbnRlcmVzdGVkIHRvIHByZXNlbnQvZGlzY3VzcyBzb21ldGhpbmcuPGJyIC8+DQo8YnIg Lz4NClRoYW5rcyw8YnIgLz4NCk1lbGluZGEgYW5kIERpcms8YnIgLz4NCjxiciAvPg0KX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnIgLz4NCkRpbiBtYWls aW5nIGxpc3Q8YnIgLz4NCjxhIGhyZWY9Im1haWx0bzpEaW4mIzY0O2lydGYub3JnIj5EaW4mIzY0 O2lydGYub3JnPC9hPjxiciAvPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1h bi9saXN0aW5mby9kaW4iPmh0dHBzOi8vd3d3LmlydGYub3JnL21haWxtYW4vbGlzdGluZm8vZGlu PC9hPjxiciAvPg0KPC9ibG9ja3F1b3RlPjwvZGl2PjwvZGl2PjwvZGl2Pg0KPC9ibG9ja3F1b3Rl PjwvZGl2Pjxicj48L2Rpdj4= From nobody Wed Oct 3 08:26:31 2018 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 0C81A1312C5; Wed, 3 Oct 2018 08:26:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 KzgsInvLim2f; Wed, 3 Oct 2018 08:26:28 -0700 (PDT) Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (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 7D35E1312C3; Wed, 3 Oct 2018 08:26:28 -0700 (PDT) Received: by mail-ot1-x331.google.com with SMTP id o21so5647461otb.13; Wed, 03 Oct 2018 08:26:28 -0700 (PDT) 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=qv5U2VgucKQZSdeINvWp3fpFaA/eMoXqhhnlURahEuA=; b=E3LtnTLLnmPAXRJcvb97+OVO3IILS1A9LSMP6SuDM/d04VL65IanjOkHqfuZa6Hs6Q SoMbWVSJupVexvJSr8wDNC/vFg0XrH3cKQsk0utgjSw3tlBTOdY87ou+HaBgEKLg7oYt aCxTy227UosaAJzlGQfWxf361Y33npiV9y2PNTcWSG/zFmO1uSOtXs+UIDtDOXIamfYa IyzMmuiT07FCQ/uYX9rXc+Qlva16+y69JQKo9+SFV/rdMcE3PHKyHRTT6zva8z/1BsqN qtL20gLFdFE2Nig7Uok6NIrDW47T1sDfNm48T7vOPhKx7Zw9lEW5g/2thHO0wWhmNxFd HbzA== 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=qv5U2VgucKQZSdeINvWp3fpFaA/eMoXqhhnlURahEuA=; b=T8CEJTeoYysK0eKiPzZFFfTqAfQT7hWU7oROgIQgNxELRVb1brx0fyWcwut/TG/fRM vAv+kqdbtwFy2ICnSJyI3AOIwVDJLbi3wU8BIWx/lWLGn5krPzmyyjhinJR/LHLxXEUH mmpjL5XYBTvXY8+hNllJuUi/a94BIeCdyJ2hJFR3tmWnR6+cppKByTwHAx6u4y3rp2U8 dujDxI/Cdfe0lrtEAh+FRTfwk/X9Laq2dUj9T11exNS3gQm6gGJis/hPIDiIy+Cd525i 57V4VDg/f5BSTKpaxEAkZsb/qDfc52QwW5PIRTp2VqMET7A836rOxend0m6k/HTUfkns jChw== X-Gm-Message-State: ABuFfohEx9qztlfofKYnB0WgEp6rd/Iwldsl4h4ocvRaLJNy34y/Del5 MMKYk4Xq73qTjbaB+2q7NOTd0RYIVAUin1EnXSY= X-Google-Smtp-Source: ACcGV63z+d5tftwWeSK9Nyz6WM7t4g0na+u5j2fOfeTmBNQxMY8Xv3kyVJGCHM+Qxj53htaDllMhlgglUVbcUPeZRZY= X-Received: by 2002:a9d:59ae:: with SMTP id u46mr1046072oth.243.1538580387880; Wed, 03 Oct 2018 08:26:27 -0700 (PDT) MIME-Version: 1.0 References: <02E2CA08-2254-4A47-9805-0920CF018357@dkutscher.net> In-Reply-To: <02E2CA08-2254-4A47-9805-0920CF018357@dkutscher.net> From: Alexander Mayrhofer Date: Wed, 3 Oct 2018 17:26:16 +0200 Message-ID: To: Dirk Kutscher Cc: din@irtf.org, dinrg-chairs@irtf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Din] Inviting proposals for DINRG agenda items @ IETF-103 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, 03 Oct 2018 15:26:30 -0000 Hello Melinda, Dirk, as mentioned before, i'd like to talk about https://tools.ietf.org/html/draft-mayrhofer-did-dns-00. I think i would need about 10 minutes, most of that time would be spent on explaining the background of DIDs (Decentralized Identifiers), unless those are widely known to the research group already. best, Alex On Mon, Oct 1, 2018 at 11:16 AM Dirk Kutscher wrote: > > Hello DINRG, > > we are starting the agenda planning for DINRG @ IETF-103 in Bangkok. > > Please let us know in case you are interested to present/discuss something. > > Thanks, > Melinda and Dirk > > _______________________________________________ > Din mailing list > Din@irtf.org > https://www.irtf.org/mailman/listinfo/din From nobody Fri Oct 5 16:02:09 2018 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 59D42128CF2; Fri, 5 Oct 2018 16:01:50 -0700 (PDT) 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 RmxGxXE5Lt3X; Fri, 5 Oct 2018 16:01:47 -0700 (PDT) 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 4059812872C; Fri, 5 Oct 2018 16:01:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w95N1h5K027980; Sat, 6 Oct 2018 01:01:43 +0200 (CEST) Received: from [192.168.217.102] (p54A6C3C7.dip0.t-ipconnect.de [84.166.195.199]) (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 42Rlcl3YPszDXqZ; Sat, 6 Oct 2018 01:01:43 +0200 (CEST) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 X-Mao-Original-Outgoing-Id: 560473301.606288-c7fe6422b2715fe968046003cdd4f56d Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Sat, 6 Oct 2018 01:01:42 +0200 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 @ IETF103: 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: Fri, 05 Oct 2018 23:01:51 -0000 Here is my usual eclectic condensed agenda based on the DRAFT AGENDA for IETF103. Remember that there is still quite some potential for changes. cbor/teep and 6tisch/suit are annoying but probably livable. No qirg for core goers... All times are ICT (Indochina Time) =3D=3D UTC +7 hours. There is no daylight saving time in effect in Thailand. DST will have ended in Europe by then (e.g., CET =3D UTC+0100) and will end in the US during the initial weekend (On Sun, Nov 4; e.g. EST =3D UTC-0500). (You can get pure UTC times on https://datatracker.ietf.org/meeting/agenda-utc, for those who want to listen from remote.) Please note that the Friday schedule is still evolving; plan to stick around until 13:20 or you may miss interesting conversations. Gr=C3=BC=C3=9Fe, Carsten SATURDAY/SUNDAY, November 3/4. 2018 -- Hackathon (including various interops) (Centre Ville) -- Sun 1700-1900 Welcome Reception - Garden at Queen's Park -- Sun 1800-2000 Hot RFC Lightning Talks - Thai Chitlada 3 MONDAY, November 5, 2018 0900-1100 Morning Session I Thai Chitlada 3 IRTF*** dinrg Decentralized Internet Infrastructure = Proposed RG Meeting 1 OPS v6ops IPv6 Operations WG Boromph. 1/2 RTG *** roll Routing Over Low power and Lossy = networks WG Thai Chitlada 1 SEC secdispatch Security Dispatch WG Thai Chitlada 2 TSV taps Transport Services WG 1120-1220 Morning Session II Thai Chitlada 1 IRTF cfrg Crypto Forum Thai Chitlada 2 TSV tsvarea Transport Area Open Meeting 1350-1550 Afternoon Session I Boromph. 1/2 ART *** core Constrained RESTful Environments WG Meeting 2 OPS anima Autonomic Networking Integrated Model = and Approach WG Thai Chitlada 2 SEC tls Transport Layer Security WG Thai Chitlada 3 TSV tsvwg Transport Area Working Group WG 1610-1810 Afternoon Session II Meeting 1 INT *** 6lo IPv6 over Networks of = Resource-constrained Nodes WG Thai Chitlada 1 IRTF irtfopen IRTF Open Meeting Thai Chitlada 2 SEC mls Messaging Layer Security WG TUESDAY, November 6, 2018 0900-1100 Morning Session I Thai Chitlada 2 ART httpbis Hypertext Transfer Protocol WG Meeting 1 INT *** lpwan IPv6 over Low Power Wide-Area Networks = WG Boromph. 1/2 SEC oauth Web Authorization Protocol WG 1120-1220 Morning Session II Thai Chitlada 3 INT ipwave IP Wireless Access in Vehicular = Environments WG Meeting 2 SEC oauth Web Authorization Protocol WG 1350-1550 Afternoon Session I Thai Chitlada 3 INT 6man IPv6 Maintenance WG Thai Chitlada 2 SEC rats Remote ATtestation ProcedureS BOF Thai Chitlada 1 TSV quic QUIC WG 1610-1810 Afternoon Session II Thai Chitlada 1 IRTF maprg Measurement and Analysis for Protocols Meeting 2 IRTF*** t2trg Thing-to-Thing WEDNESDAY, November 7, 2018 0900-1100 Morning Session ! Thai Chitlada 3 ART *** cbor Concise Binary Object Representation = Maintenance and Extensions WG Boromph. 3 RTG bier Bit Indexed Explicit Replication WG Meeting 1 SEC *** teep Trusted Execution Environment = Provisioning WG Boromph. 1/2 SEC tokbind Token Binding WG Thai Chitlada 1 TSV quic QUIC WG 1120-1220 Morning Session II Boromph. 1/2 INT *** lwig Light-Weight Implementation Guidance WG Thai Chitlada 1 SEC tls Transport Layer Security WG Thai Chitlada 2 TSV tsvwg Transport Area Working Group WG 1350-1520 Afternoon Session I Meeting 1 GEN wugh WGs Using GitHub BOF Thai Chitlada 3 INT homenet Home Networking WG Meeting 2 IRTF panrg Path Aware Networking RG 1540-1710 Afternoon Session II Meeting 1 ART dispatch Dispatch WG - Joint with ARTAREA Thai Chitlada 3 INT intarea Internet Area Working Group WG Meeting 2 IRTF pearg Privacy Enhancements and Assessments = Proposed Research Group Boromph. 3 RTG babel Babel routing protocol WG Boromph. 1/2 RTG rift Routing In Fat Trees WG THURSDAY, November 8, 2018 0900-1100 Morning Session I Thai Chitlada 1 ART httpbis Hypertext Transfer Protocol WG Boromph. 4 INT *** 6tisch IPv6 over the TSCH mode of IEEE = 802.15.4e WG Meeting 1 IRTF icnrg Information-Centric Networking Thai Chitlada 2 SEC *** suit Software Updates for Internet of Things = WG 1120-1220 Morning Session II Thai Chitlada 2 ART *** core Constrained RESTful Environments WG Thai Chitlada 3 IRTF qirg Quantum Internet Proposed Research Group Boromph. 4 RTG bier Bit Indexed Explicit Replication WG Thai Chitlada 1 SEC mls Messaging Layer Security WG Meeting 2 TSV rmcat RTP Media Congestion Avoidance = Techniques WG 1350-1550 Afternoon Session I Meeting 1 INT dnssd Extensions for Scalable DNS Service = Discovery WG Thai Chitlada 2 RTG detnet Deterministic Networking WG Thai Chitlada 1 SEC saag Security Area Open Meeting 1610-1810 Afternoon Session II Thai Chitlada 3 RTG rtgarea Routing Area Open Meeting Thai Chitlada 1 SEC *** ace Authentication and Authorization for = Constrained Environments WG Boromph. 1/2 SEC acme Automated Certificate Management = Environment WG FRIDAY, November 9, 2018 Various ad-hoc meetings, please see https://trac.ietf.org/trac/ietf/meeting/wiki/103sidemeetings#FRIDAY -- 0900..1320 T2TRG work meeting -- 1000..??? COIN (Computing in the Network) From nobody Wed Oct 17 07:40:50 2018 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 BBD36130DE3; Wed, 17 Oct 2018 07:40:33 -0700 (PDT) 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 l_mNTGujUmzq; Wed, 17 Oct 2018 07:40:31 -0700 (PDT) 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 A7634130DDE; Wed, 17 Oct 2018 07:40:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w9HEeIrG029861; Wed, 17 Oct 2018 16:40:23 +0200 (CEST) Received: from [192.168.217.114] (p54A6CA9F.dip0.t-ipconnect.de [84.166.202.159]) (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 42Zvwf2Dxpz1Bqf; Wed, 17 Oct 2018 16:40:18 +0200 (CEST) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 X-Mao-Original-Outgoing-Id: 561480016.121739-51f36c93b1d85dd445e675488f4c9abe Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Wed, 17 Oct 2018 16:40:17 +0200 Message-Id: <6B9735FC-AD2D-4D8D-ABEA-D6D741233322@tzi.org> 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 @ IETF103: "FINAL" 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: Wed, 17 Oct 2018 14:40:34 -0000 Here is my usual eclectic condensed agenda based on the "FINAL" AGENDA for IETF103. A few changes from the DRAFT AGENDA. I waited a bit with sending this as a few more side meetings have become known, as well. Of course, "FINAL" doesn't mean final. cbor/teep and 6tisch/ace (was suit) are annoying but probably livable. qirg no longer conflicts with core :-). dinrg is now on top of lpwan. secdispatch on top of t2trg will all but make sure no security people attend t2trg. All times are ICT (Indochina Time) =3D=3D UTC +7 hours. There is no daylight saving time in effect in Thailand. DST will have ended in Europe by then (e.g., CET =3D UTC+0100) and will end in the US during the initial weekend (On Sun, Nov 4; e.g. EST =3D UTC-0500). (You can get pure UTC times on https://datatracker.ietf.org/meeting/agenda-utc, for those who want to listen from remote.) Please note that the Friday schedule is still evolving; plan to stick around until 13:20 or you may miss interesting conversations. Gr=C3=BC=C3=9Fe, Carsten SATURDAY/SUNDAY, November 3/4. 2018 -- Hackathon (including various interops) (Centre Ville), e.g.: T2TRG WISHI, possibly some CBOR, LPWAN, TLS 1.3, EST-COAPS, TEEP Please see https://trac.ietf.org/trac/ietf/meeting/wiki/103hackathon -- Sun 1700-1900 Welcome Reception - Garden at Queen's Park -- Sun 1800-2000 Hot RFC Lightning Talks - Chitlada 3 MONDAY, November 5, 2018 0900-1100 Morning Session I Chitlada 2 ART dispatch Dispatch WG - Joint with ARTAREA Meeting 1 OPS v6ops IPv6 Operations WG Boromph. 1/2 RTG *** roll Routing Over Low power and Lossy = networks WG Meeting 2 SEC oauth Web Authorization Protocol WG 1120-1220 Morning Session II Chitlada 1 IRTF cfrg Crypto Forum Chitlada 2 TSV tsvarea Transport Area Open Meeting 1350-1550 Afternoon Session I Boromph. 1/2 ART *** core Constrained RESTful Environments WG Meeting 1 OPS anima Autonomic Networking Integrated Model = and Approach WG Chitlada 2 SEC tls Transport Layer Security WG Chitlada 3 TSV tsvwg Transport Area Working Group WG 1610-1810 Afternoon Session II Meeting 2 INT *** 6lo IPv6 over Networks of = Resource-constrained Nodes WG Chitlada 1 IRTF irtfopen IRTF Open Meeting Chitlada 2 SEC mls Messaging Layer Security WG TUESDAY, November 6, 2018 0900-1100 Morning Session I Chitlada 1 ART httpbis Hypertext Transfer Protocol WG Meeting 1 INT *** lpwan IPv6 over Low Power Wide-Area Networks = WG Meeting 2 IRTF*** dinrg Decentralized Internet Infrastructure = Proposed RG Boromph. 4 SEC tokbind Token Binding WG 1120-1220 Morning Session II Chitlada 3 INT ipwave IP Wireless Access in Vehicular = Environments WG Chitlada 2 IRTF qirg Quantum Internet Proposed Research Group Meeting 1 SEC oauth Web Authorization Protocol WG 1350-1550 Afternoon Session I Chitlada 3 INT 6man IPv6 Maintenance WG Chitlada 2 SEC rats Remote ATtestation ProcedureS BOF Chitlada 1 TSV quic QUIC WG 1610-1810 Afternoon Session II Chitlada 1 IRTF maprg Measurement and Analysis for Protocols Meeting 1 IRTF*** t2trg Thing-to-Thing Meeting 2 SEC secdispatch Security Dispatch WG Pagoda -- 1700..1800 CACAO side meeting Apartment 3 -- 1800..2000 IoT Onboarding side meeting (lear/mcr) WEDNESDAY, November 7, 2018 0900-1100 Morning Session I Chitlada 3 ART *** cbor Concise Binary Object Representation = Maintenance and Extensions WG Boromph. 3 RTG bier Bit Indexed Explicit Replication WG Meeting 2 SEC *** teep Trusted Execution Environment = Provisioning WG Chitlada 1 TSV quic QUIC WG 1120-1220 Morning Session II Meeting 2 INT *** lwig Light-Weight Implementation Guidance WG Chitlada 1 SEC tls Transport Layer Security WG Chitlada 2 TSV tsvwg Transport Area Working Group WG 1350-1520 Afternoon Session I Meeting 2 GEN wugh WGs Using GitHub BOF Chitlada 3 INT homenet Home Networking WG Meeting 1 IRTF panrg Path Aware Networking RG -- 1400..1500 IoT Onboarding Mechanisms side meeting 1540-1710 Afternoon Session II Chitlada 3 INT intarea Internet Area Working Group WG Meeting 1 IRTF pearg Privacy Enhancements and Assessments = Proposed Research Group Boromph. 3 RTG babel Babel routing protocol WG Boromph. 1/2 RTG rift Routing In Fat Trees WG Meeting 2 TSV taps Transport Services WG THURSDAY, November 8, 2018 0900-1100 Morning Session I Chitlada 1 ART httpbis Hypertext Transfer Protocol WG Meeting 2 IRTF icnrg Information-Centric Networking Chitlada 2 SEC *** suit Software Updates for Internet of Things = WG 1120-1220 Morning Session II Chitlada 2 ART *** core Constrained RESTful Environments WG Boromph. 1/2 RTG bier Bit Indexed Explicit Replication WG Chitlada 1 SEC mls Messaging Layer Security WG Meeting 1 TSV rmcat RTP Media Congestion Avoidance = Techniques WG 1350-1550 Afternoon Session I Meeting 2 INT dnssd Extensions for Scalable DNS Service = Discovery WG Chitlada 2 RTG detnet Deterministic Networking WG Chitlada 1 SEC saag Security Area Open Meeting 1610-1810 Afternoon Session II Boromph. 3 INT *** 6tisch IPv6 over the TSCH mode of IEEE = 802.15.4e WG Chitlada 3 RTG rtgarea Routing Area Open Meeting Chitlada 1 SEC *** ace Authentication and Authorization for = Constrained Environments WG Boromph. 1/2 SEC acme Automated Certificate Management = Environment WG FRIDAY, November 9, 2018 Various ad-hoc meetings, please see https://trac.ietf.org/trac/ietf/meeting/wiki/103sidemeetings#FRIDAY Boromph. 4 -- 0900..1320 T2TRG work meeting Boromph. 3 -- 1000..1200 COIN (Computing in the Network) From nobody Fri Oct 19 11:59:48 2018 Return-Path: X-Original-To: din@irtf.org Delivered-To: din@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 16B991310DF; Fri, 19 Oct 2018 11:56:31 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: din@irtf.org, irtf-chair@irtf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.87.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153997539108.6592.10094921575804778428.idtracker@ietfa.amsl.com> Date: Fri, 19 Oct 2018 11:56:31 -0700 Archived-At: Subject: [Din] dinrg - Requested session has been scheduled for IETF 103 X-BeenThere: din@irtf.org X-Mailman-Version: 2.1.29 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, 19 Oct 2018 18:56:38 -0000 Dear Melinda Shore, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. dinrg Session 1 (2:00 requested) Tuesday, 6 November 2018, Morning Session I 0900-1100 Room Name: Meeting 2 size: 150 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/103/sessions/dinrg.ics Request Information: --------------------------------------------------------- Working Group Name: Decentralized Internet Infrastructure Proposed RG Area Name: IRTF Session Requester: Melinda Shore Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 70 Conflicts to Avoid: First Priority: icnrg trans Second Priority: ace tls saag People who must be present: Melinda Shore Dirk Kutscher Allison Mankin Resources Requested: Special Requests: Please avoid conflict with the rats BOF (first priority) should it be approved --------------------------------------------------------- From nobody Mon Oct 22 14:38:10 2018 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 B915412D4F1 for ; Mon, 22 Oct 2018 14:38:08 -0700 (PDT) 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 My7b5S0A8xvv for ; Mon, 22 Oct 2018 14:38:06 -0700 (PDT) Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 8E765126BED for ; Mon, 22 Oct 2018 14:38:06 -0700 (PDT) Received: by mail-pg1-x52d.google.com with SMTP id z2-v6so3224176pgp.0 for ; Mon, 22 Oct 2018 14:38:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=qCcPe/XhnqLrfSs0KjnPhTI2AeoKC3Du44VvDEMTDbg=; b=PykNYniR1MrOnTIRvSPKKJfAsyLCtP6Zqv2+j/IYZAYXHXdI0ulQWeTrLgUKt6t5sc 8lOGQGN2i5sAIqA5+e8WSCxMGbvgf9n+a1htN/6sZ1aFrJBHDCr5PSoVDEyKxKSPwplo PM8UE7uDTXhsJ4EmnlTeaj7z9njE3MGQbJzlXtuSpgJiVb7Bp1FP8y7yyU4GngnmJtAm PiXbdSSw0M07jV1CGsoaAGl/eztUfJimQPVQVsHgb6s+cDqe+6YyJC/UaEXvN/gehtsO MqP6rDaDVATIVUjFwLA5A9iI/AOb61V1fnGPAhaM3XnPMpEv9TLp1qhtnvbDJMNQmXCd H9wA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=qCcPe/XhnqLrfSs0KjnPhTI2AeoKC3Du44VvDEMTDbg=; b=q8ta6znPxjN2c42E9BfKbL6rHSchQchzq/R81ZaIZdvQJ6lIC7QjYMDkqtLDC+BHlm gT6EJKBwhB9P/4+PKmq5C2844/PsHzZIt37eg6TTilPDhLH7zug6JsDp2S5rxTMoA7aB eySJzszO7jfJre+lUoiMQYviTl/kpnGglHVOH0qkoISYibspc75ZuoyJqJsF4MwvbR8Z NuT5Au53FeRWe6o6QUlbciMcj3ETsEoICwbKuy3z2cZVBzCnqLvKYDgtpTVFkYNt6wCj iztzmglw0wEuYpHOSBno1aQWTTxT4XTBrIqP9Y0YFrRJe9mmNNttJcNJV3cozj3LKbCd oEAA== X-Gm-Message-State: ABuFfoj0VTlyANQmnT9yZvq/MD3UvKiMb2rif7e17jJL4Yuax3PsPUkO ey72HgymXkjN4cayVwldBKzD X-Google-Smtp-Source: ACcGV60mPEMHYWqPhHfCU9Lsz5JnBvAT5UYonYkz/yqoamFvwW4zX/iqcah3nD/VfL3LZUEdeE2SCQ== X-Received: by 2002:a62:302:: with SMTP id 2-v6mr46229318pfd.145.1540244284870; Mon, 22 Oct 2018 14:38:04 -0700 (PDT) Received: from aspen.local (216-67-35-146-radius.dynamic.acsalaska.net. [216.67.35.146]) by smtp.gmail.com with ESMTPSA id l1-v6sm2073544pgm.8.2018.10.22.14.38.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Oct 2018 14:38:04 -0700 (PDT) To: "din@irtf.org" , Dirk Kutscher From: Melinda Shore Message-ID: Date: Mon, 22 Oct 2018 13:38:02 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [Din] Rough draft of agenda for IETF 103 posted 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, 22 Oct 2018 21:38:09 -0000 Hi, all: The first crack at an agenda for the upcoming meeting has been posted, here: https://datatracker.ietf.org/meeting/103/materials/agenda-103-dinrg-00.html. Please send comments, corrections, requests, etc. If you're on the agenda and there's no link to your paper, please send a link if you've got one. Thanks, and see you all soon! Melinda -- Melinda Shore melinda.shore@nomountain.net Software longa, hardware brevis From nobody Tue Oct 23 04:59:56 2018 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 8D129130DFE for ; Tue, 23 Oct 2018 04:59:54 -0700 (PDT) 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=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 eByfm5p2svyO for ; Tue, 23 Oct 2018 04:59:52 -0700 (PDT) Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 6D51E130DE2 for ; Tue, 23 Oct 2018 04:59:52 -0700 (PDT) Received: by mail-lf1-x12f.google.com with SMTP id c16so891293lfj.8 for ; Tue, 23 Oct 2018 04:59:52 -0700 (PDT) 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=pGwG/HL0sYfWC/uk/0S4MeCBPApFwA4ofpQEaZGX64w=; b=TPyXPJI1deW3/8a9/GM2h/UYTb4qhVVTqZeI3jCvT0VjeRa2hucIbFNGZjGZJ0zOmJ V9nxAG16VEjG2ToO+417RICvrqx5QxhMJuCKterVMHk3MOnGEdOQ6phlFhXQmvk8g/03 qQqHynA1xI+dE5lT28FRcSDbFL8LN/LmaqjzHv+EE6llyU9DXJ2KL7QZ7kp1RpoCcqdt 2PwFa1nOcqRyEFQqUJHLzD4zvsT+Kr8a6umL4hdATqm9cBFg+3i/zx/beLBnpVNS/NGv Gg3lZ3T5bnobIwKe71hcOy/aD5Gr0nbXyWBNQlTdiqv2AAZGpsQhwa1ibHzdBAi5rKgu 8Ncg== 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=pGwG/HL0sYfWC/uk/0S4MeCBPApFwA4ofpQEaZGX64w=; b=dUN+ZOmjI9amLPwwhq1Mh2I3tmWyJN9SIIDlkC+lZUCt0YsS5Ljefv/+ehDnJ4Dg/S Kq9yEl1Mdi/ovwa/bPLH7OtVCQZ/fuLCVp9NOBiFjNMGLF1uo3uuZZBpyF8OgKo/+Z8W jrj+HriXe/XuFB4hpBQRtQP3QsmNSSaUa/VXevpdvtX8jIySZUMeWiD7ljRgFcDbbHGx g0/Ao/7ukgxIC9A3xWSVnAkVqLvqqx1w5fKpNBo+KmJdXYreOA2qTAitW0MkJXVzqMPN 5e2wb30Be+FC45SC7U/OIR/kA9qRBhq1cRuXLckiPCdzoSE6lxzfP1qhTgrqBJJrcEij tY3Q== X-Gm-Message-State: ABuFfogq9PPeB9dctmtLxxhBLHwh+CFbXcO5Nhs6lxwICGTqNNTjZhOR i1Oi0Fwk/RY17urYT5A9LyW71D07A9V4mMd2S/Aa/M0A X-Google-Smtp-Source: ACcGV60jyEDaEvK+SvvKF9mFAgC94aPX5RjIu2NmeN8ld/n3s/vJSCO8nuppkLhSGCnETK4uZBHeoawajBC/ZTt0qrc= X-Received: by 2002:a19:639b:: with SMTP id v27mr10857497lfi.95.1540295990036; Tue, 23 Oct 2018 04:59:50 -0700 (PDT) MIME-Version: 1.0 From: Piers Powlesland Date: Tue, 23 Oct 2018 12:59:39 +0100 Message-ID: To: din@irtf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Din] draft-mazieres-dinrg-scp-04 (page 16) transitioning from prepare to commit. 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, 23 Oct 2018 11:59:55 -0000 At the end of section 3.6 there is the following statement. A node leaves the PREPARE phase and proceeds to the COMMIT phase when there is some ballot "b" for which the node confirms "prepare(b)" and accepts "commit(b)". (If nodes never changed quorum slice mid- protocol, it would suffice to accept "commit(b)". Also waiting to confirm "prepare(b)" makes it easier to recover from liveness failures by removing Byzantine faulty nodes from quorum slices.) I'm trying to understand how we know that when a node accepts commit(b), the network will come to agreement on b.value. I'm considering the case where nodes do not change slice mid-protocol where a node accepts commit(b) via quorum threshold. So far I have come up with this: We know that the quorum of nodes nodes that have voted to commit(b) cannot vote for another ballot, although they potentially could accept commit for a different ballot and they could also abort their vote for commit(b). But we know that a vote to commit(b) indicates that these nodes have left the nomination phase and therefore can only change the value in their ballots through accepting incompatible ballots via blocking threshold, since we have seen a quorum of nodes vote commit(b) we know that there is at least one of these nodes in all quorums and therefore no quorum could accept, prepared or committed, any ballot with a value other than b. So we can say securely that the nodes we have seen vote commit(b), cannot accept a commit with a different value or abort their vote. Now I'm wondering how do we know at this point that the network will not get stuck? For instance how do we know that a quorum that contains one of the nodes that has voted to commit(b), may not have nodes that vote for a higher incompatible ballot, that they can never accept? So my thinking thus far is that: The node that has voted to commit(b) in this quorum must have seen every node in the quorum accept prepare(b). If we consider any one of those nodes that have accepted prepare(b), in order for it to accept a new ballot prepared it will need to hear from the rest of its quorum and when it does hear from the rest of its quorum, it will in fact confirm prepare(b) at which point the node stops considering new values for its ballots. So we can see that nodes will not get stuck voting for higher incompatible ballots. It would be good to know if I'm on the right track or If I have gone off the deep end? And also I'm still not clear at all on why nodes changing mid slice makes it necessary to confirm prepare(b) and accept commit(b) so any explanation of that would be great! Thanks, Piers From nobody Tue Oct 23 09:36:09 2018 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 5DE6A130F80 for ; Tue, 23 Oct 2018 09:36:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] 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 gqBDnR_4qQbn for ; Tue, 23 Oct 2018 09:36:00 -0700 (PDT) Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 F0FBD131000 for ; Tue, 23 Oct 2018 09:35:59 -0700 (PDT) Received: by mail-pf1-x42e.google.com with SMTP id q1-v6so940926pfh.10 for ; Tue, 23 Oct 2018 09:35:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=sodDDG2ngWsnKDIrpVMs8d7VldApPjDG1vEE+J93AuQ=; b=z9zvGRPh06Pp0dg0CEEM9N2m4pw9QRtpF9xZBzkSasY9DoR0/Wehel9+kCDwp/dgBp yjGUEv6hOE/nEGENNOOcWMW7tbPrv47JP4jZK25hdjrMxWAf0iPE/NEQd2VuWXME9Fa1 VIwhW1UWAJfDNRxshzMHCSX1CeHAMehqX19sypxrmC6vPhb2gYWbtqhEgPqiDzi3NXj7 Z2jQZi1WrqokQFpDCs1wcf6RUAKDsEXDUqQczrkrMRDYLyKb6GUIjWcTkdKq6q/xtGHm K7oVDjtJs9UbD/YIHK8fkj5aITVSP7v479ErGTyqlVa5i19VxO+FAGVZ5MQ4iPGpYgop orBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=sodDDG2ngWsnKDIrpVMs8d7VldApPjDG1vEE+J93AuQ=; b=c5uRvaiuQKiQ29H3t3hv/ZHMs8Qa4gZnjkaRGCPYG4dRMfB6jtzqExuiisvQH76dm3 d+ZABE1/wytnsZU0MepZ2wXlvKryTMixyx3yIUNaYH22R0RYkhdnGUKS40RyufZWfrhl wfwig8UITXo1kX6+Vh2Dy6xk5b7mBwZhUYDRF7FLTxEq/IDH6JCO8HvVk7VzweeNxpim KAXAaU/GCWAXWP0Q7sQ1ZZjt/FN+YI/yZ+6tVgr5GQATNiYZXWDsl5XfZhJxVoxlfNNj CCcvUKi5XEJI8/WbAHogAqfbSIZI00a+A6zAp88Wizs3/mTn63ZGRD/w4gvHsG1/LKVY j2IQ== X-Gm-Message-State: AGRZ1gJzO0y1qqLEYOrMBDkIRgO+A0C5xoIowaY49wUncE6ETJWqERub OZ+LP9JkpimNCcBt5mOKGqvSaZrcnw== X-Google-Smtp-Source: AJdET5chtlf5MPiKifUx9/PoaeLktmTjxOo3Grh0GpXaEgfZahBGfraJfmQsqxAObNCcmd7uqcttzA== X-Received: by 2002:a63:84c7:: with SMTP id k190mr7010500pgd.333.1540312558909; Tue, 23 Oct 2018 09:35:58 -0700 (PDT) Received: from aspen.local (216-67-35-146-radius.dynamic.acsalaska.net. [216.67.35.146]) by smtp.gmail.com with ESMTPSA id y71-v6sm3511991pfk.70.2018.10.23.09.35.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Oct 2018 09:35:58 -0700 (PDT) To: "din@irtf.org" From: Melinda Shore Message-ID: Date: Tue, 23 Oct 2018 08:35:56 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [Din] Webinar for new meeting participants 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, 23 Oct 2018 16:36:08 -0000 Hi: The IETF is holding several newcomers' webinars this week, and it may interest people who are planning on being in Bangkok but haven't participated in IETF meetings in the past. More info here: https://www.ietf.org/how/meetings/103/newcomers/ Melinda -- Melinda Shore melinda.shore@nomountain.net Software longa, hardware brevis From nobody Thu Oct 25 02:29:14 2018 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 E62AB130DEB for ; Thu, 25 Oct 2018 02:29:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.3 X-Spam-Level: X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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=aalto.fi 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 eYt45oagoQxX for ; Thu, 25 Oct 2018 02:29:10 -0700 (PDT) Received: from smtp-out-01.aalto.fi (smtp-out-01.aalto.fi [130.233.228.120]) (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 B1D28130DFD for ; Thu, 25 Oct 2018 02:29:09 -0700 (PDT) Received: from smtp-out-01.aalto.fi (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 33405115590_BD18C40B for ; Thu, 25 Oct 2018 09:26:24 +0000 (GMT) Received: from exng2.org.aalto.fi (exng2.org.aalto.fi [130.233.223.21]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client CN "exng2.org.aalto.fi", Issuer "org.aalto.fi RootCA" (not verified)) by smtp-out-01.aalto.fi (Sophos Email Appliance) with ESMTPS id D7B1D115509_BD18C3FF for ; Thu, 25 Oct 2018 09:26:23 +0000 (GMT) Received: from exng5.org.aalto.fi (130.233.223.24) by exng2.org.aalto.fi (130.233.223.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Thu, 25 Oct 2018 12:29:05 +0300 Received: from exng2.org.aalto.fi (130.233.223.21) by exng5.org.aalto.fi (130.233.223.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Thu, 25 Oct 2018 12:29:05 +0300 Received: from exng2.org.aalto.fi ([fe80::e847:c271:7155:1b29]) by exng2.org.aalto.fi ([fe80::e847:c271:7155:1b29%18]) with mapi id 15.01.1466.012; Thu, 25 Oct 2018 12:29:05 +0300 From: Nikander Pekka To: "din@irtf.org" Thread-Topic: Decentralised IoT Systems and Security - NDSS DISS Workshop 2019: DL Dec 7 Thread-Index: AQHUbEUsmn+c1I9aiUakxJddKb4Lsw== Date: Thu, 25 Oct 2018 09:29:05 +0000 Message-ID: <97FF0E8A-94F3-461E-866D-873BCDA875F1@aalto.fi> Accept-Language: en-GB, fi-FI, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mailer: Apple Mail (2.3445.9.1) x-originating-ip: [130.233.0.5] Content-Type: text/plain; charset="us-ascii" Content-ID: <63A0CD31AD1B9F49BD0C9DC51003854C@aalto.fi> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SASI-RCODE: 200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aalto.fi; h=from:to:subject:date:message-id:content-type:content-id:content-transfer-encoding:mime-version; s=its18; bh=DQMQ942+qP59GiA8HVAQdRAmJSEguLP+GdjFm/3xCU0=; b=UljgnOTwmdcPfxprJ+q27YhC8ir0m+voOf7VUzW6LAN9e2hKQUDEvSUU1IuazcKXLkyY/5X610Cvu31jalB0PtwCU0aYqZo4YLAgtkU+O0Vnam7XQyRqcy3b0PntZpDFtFexZrDdM2uYWXzAXx3EMUv77Rh/tTwhR/TwhbOS2Jla2rU06d0slZvj2zU53D60l0PpnvBjbK/iMtm7X8iolCorFaiUqx0F4Nuetsd8gCiqmDFYsrSGt2ZyU12sDj9qi1uMmXKuuzygTsWRfakp2GRHB6kDexxC1Xwbb3OvOuveOqfkTSMzDsqO9AtNoDm7+/5N3U1vWOLnMiwDyAYzhA== Archived-At: Subject: [Din] CFP: Decentralised IoT Systems and Security - NDSS DISS Workshop 2019: DL Dec 7 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, 25 Oct 2018 09:29:13 -0000 [apologies if you receive multiple copies of this] 2019 NDSS Symposium Workshop Decentralized IoT Systems and Security (DISS 2019) Call for Papers https://www.ee.ucl.ac.uk/~ipsaras/ndss-diss19.html The success of the Internet of Things (IoT) depends heavily on the extent o= f achieved interoperability, as well as on addressing the many security and= privacy challenges. Due to the multitude of types of devices, systems, and= protocols, and their scale of deployment and limited resources, some of th= ese systems will be extremely challenging to interconnect and secure. The u= nderlying edge network or edge-computing infrastructure, supporting the IoT= , will also need to provide security and privacy guarantees.=20 Given that IoT devices and edge networks are deployed by a multitude of pla= yers, decentralization has become a key enabling design goal of the system.= For example, recent advances in Distributed Ledger Technology (DLT) and Bl= ockchains can be incorporated to support decentralized security. In turn, d= ecentralized security through distributed trust can help overcome privacy c= oncerns and scalability bottlenecks, both of which are becoming increasingl= y serious in large-scale deployments, such as smart cities or Industry 4.0. A decentralized approach to IoT interconnection brings forth many opportuni= ties, but also important challenges, e.g., in state synchronization, trust = management, and the difficulties of operating with constrained devices and = networking modes. Following the spirit of the NDSS Symposium, the goal of this workshop is to= bring together researchers and practitioners to analyze and discuss the hu= ge potential, but also the inevitable limitations of decentralized operatio= n and security in the IoT space, in edge-computing, as well as in the wider= mobile computing environment. The workshop will accept early-stage, novel ideas that are likely to trigge= r discussion. The proposed topics include the following: + Enabling secure interoperability across IoT ecosystems, including ++ Applying blockchains and Distributed Ledger Technology to IoT and edge n= etwork infrastructure ++ Security and availability in multi-tiered IoT edge networks ++ Peer-to-Peer (P2P) security and privacy in IoT ++ Decentralized trust and rights management, including access control ++ Decentralized authentication and access management at the IoT edge + Other topics related to decentralized security in IoT, such as ++ Security and privacy trade-offs related to IoT scalability and decentral= ization ++ Cryptocurrencies, crypto-assets and cryptoeconomics in IoT and edge-comp= uting ++ Secure Service provisioning and migration in edge-computing environments ++ Sensor and Actuator Key Management and other Security Protocols ++ Smart Contracts for IoT, including formal verification of smart contract= s ++ Application of concepts from outside of the IoT to decentralized IoT sec= urity ++ Usable security for decentralized IoT and edge-computing Submission Instructions =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The workshop will accept papers between three to six pages in length, for p= ublication in post-workshop proceedings. Proceedings will be published by t= he Internet Society with the revised papers based on the workshop discussio= ns and reviewer comments. Papers shall be submitted for review in print-ready form using the NDSS pap= er template and the review will be single blind. For a paper to be publishe= d, at least one of the authors must attend the entire workshop, the paper m= ust be revised based on the discussion at the workshop, and the revised pap= er must be submitted in time for the publication deadline. Submissions and reviews will be handled by EasyChair: https://easychair.org= /conferences/?conf=3Ddiss2019 Important dates and venue =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Abstract submission: 07 December 2018 Paper Submissions Due: 14 December 2018 Decision Notice to Authors: 14 January 2019 The workshop is co-located with the 2019 NDSS Symposium, February 24-27, 20= 19 in San Diego, CA, USA. Workshop Organizers: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Salil Kanhere, UNSW, Australia George C. Polyzos, AUEB, Greece Workshop TPC co-chairs: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Pekka Nikander, Aalto, Finland Ioannis Psaras, UCL, UK Technical Programme Committee =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 Mustafa Al-Basaam, UCL, UK Dimitris Chatzopoulos, HKUST, Hong Kong Jon Crowcroft, University of Cambridge, UK Nikos Fotiou, AUEB, Greece Toru Hasegawa, University of Osaka, Japan Sotiris Ioannidis, FORTH, Greece Yki Kortesniemi, Aalto, Finland Michal Krol, UCL, UK Jun Kurihara, Zettant, Japan Nelly Leligou, University of West Attica, Greece Borje Ohlman, Ericsson, Sweden Joerg Ott, TU Munich, Germany Alex Pazaitis, TU Tallinn, Estonia and P2P Lab, Greece Christian Esteve Rothenberg, University of Campinas, Brazil Thomas C. Schmidt, Hamburg University of Applied Sciences, Germany Vasilios Siris, AUEB, Greece Alberto Sonnino, UCL, UK Panagiotis Trakadas, TEI of Sterea Ellada, Greece Spyros Voulgaris, AUEB, Greece Matthias Wahlisch, Freie Universitat Berlin, Germany From nobody Thu Oct 25 06:43:29 2018 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 5075F120072 for ; Thu, 25 Oct 2018 06:43:28 -0700 (PDT) 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=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 FB68W74j4S8P for ; Thu, 25 Oct 2018 06:43:26 -0700 (PDT) Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 8430F130E5A for ; Thu, 25 Oct 2018 06:43:24 -0700 (PDT) Received: by mail-lf1-x134.google.com with SMTP id n3-v6so6829861lfe.7 for ; Thu, 25 Oct 2018 06:43:24 -0700 (PDT) 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=FkA3GpWL1Zxv4JJavWcUjQXw2FTocGT7kLd4J6NV31c=; b=W5mD0bNowwQQerf3K3lRzNn2qRXtmWONN3PME+Jgpfq1Dq+/3VyNWGxlx8w7i+pAFz H+z+3hYkHPonm7UJlRW/MpS8wViYV6EVUGYn1U9jO+NU8QaqgZUYpurOFSF/igRg9IUF n+xmjG/J+xknvRoXG30S1ecTwCzLKjUjoiEL/VQvrvomvfWA8azzeEIdW5mawSrZfoiK 6ldsetcG22B8kPffzfbtINm5FUc7XAreO8jWL/VvJbfQh/CrHab04ImGo7Pl2HVePm12 QNSxLTeG/EvSRj1FsF2lRvfSdljOleIw4ACBDRc3dw1prgnIWenhPbz7015neICpWnGP NWOQ== 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=FkA3GpWL1Zxv4JJavWcUjQXw2FTocGT7kLd4J6NV31c=; b=sd45JcnPLAAZb83emDvH97VGKfpn9Y74XQxMd2EVaILlGKwH86werqZx65XPJjfder ZDeHM3T0ooC+D0MWwmcBRvguxvVkHPtnx1gwnmojWNQdsHhFsEtYSbt3qHWyqvLaJsmg 88gt37QxIevMsqw6CH02c+yzGVX7SPP+2ETXka0R+J4ouMr1Rr0pZwrSoYzDJJkOdWLZ lYj7hJorsX1T/yk6sCTYc7vYjbzaxrr7P7Z0RelOGcEjehm6J4L1skkxEsm3p4vlxcXg 7c+GF58ByKrbdHsn/1wZeaOmqpiNUyboQ9GbjdeBUfmKmHif9BGPpeseY3bi66rLLv0d iMdQ== X-Gm-Message-State: AGRZ1gJR2VLr3EUrfx/SeKfY+wv4cULA481p0txIJ4/FYY8nE6OIIa07 GBs2eRGOENaY/8sOZlir+liWf+p1lERS6AdhglCekuee X-Google-Smtp-Source: AJdET5fpnX7eLJeza0LOgn7Sf6pJ6j6idMh1Ekfdjp6cX0tAyZ7/21NLLuecTufDqI5RxZb2XQZmYej4w+U+vLqpwf8= X-Received: by 2002:ac2:434d:: with SMTP id o13-v6mr1248979lfl.129.1540475002292; Thu, 25 Oct 2018 06:43:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Piers Powlesland Date: Thu, 25 Oct 2018 14:43:11 +0100 Message-ID: To: din@irtf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Din] draft-mazieres-dinrg-scp-04 (page 16) transitioning from prepare to commit. 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, 25 Oct 2018 13:43:28 -0000 Thinking about this more I realise I made a mistake in my reasoning, please disregard my previous reasoning. I set out below a new description. It would be great to know if it is correct. I am still not clear on why a node needs to confirm prepare(b) and accept commit(b) when nodes can change slice mid protocol? At the point that a node accepts commit(b) they have seen a quorum vote commit(b). Seeing a node vote commit(b) lets us know that it has confirmed prepare(b). We can know at this point that the network cannot come to agree on any value other than b.value and that it also will not get stuck as long as messages are not delayed indefinitely. We can see that the network cannot come to agree on any other value since there are only 2 ways that new values can be introduced to a node. Either a new composite value is produced via nomination or a node accepts prepared a ballot via blocking threshold. Since nomination terminates once a node confirms prepare(b) no new values can be introduced via nomination. Given that we have seen a quorum of nodes confirm prepare(b) we know that for each node they must have at least one quorum slice contained entirely within the quorum. This means that none of the nodes in the quorum can reach blocking threshold for any other value than the one they prepared. So we can see that the nodes in the quorum that voted to commit(b) cannot change their value. Given that there will be at least one of the nodes who have confirmed prepare(b) in all other quorums we can see that the network cannot agree on any other value. How do we know that the network will come to agree on the value that has been accepted committed? Theorem 10 shows that any subset of nodes that also contain a quorum is v-blocking for at least one node not in the subset. If we expand the subset to include the v-blocked node the subset will still be v-blocking for at least one node outside the subset. We can continue this process till the entire network is contained in the subset, and hence all nodes have accepted the same value. On Tue, Oct 23, 2018 at 12:59 PM Piers Powlesland wrote: > > At the end of section 3.6 there is the following statement. > > A node leaves the PREPARE phase and proceeds to the COMMIT phase when > there is some ballot "b" for which the node confirms "prepare(b)" and > accepts "commit(b)". (If nodes never changed quorum slice mid- > protocol, it would suffice to accept "commit(b)". Also waiting to > confirm "prepare(b)" makes it easier to recover from liveness > failures by removing Byzantine faulty nodes from quorum slices.) > > I'm trying to understand how we know that when a node accepts > commit(b), the network will come to agreement on b.value. I'm > considering the case where nodes do not change slice mid-protocol > where a node accepts commit(b) via quorum threshold. > > So far I have come up with this: > > We know that the quorum of nodes nodes that have voted to commit(b) > cannot vote for another ballot, although they potentially could accept > commit for a different ballot and they could also abort their vote for > commit(b). > > But we know that a vote to commit(b) indicates that these nodes have > left the nomination phase and therefore can only change the value in > their ballots through accepting incompatible ballots via blocking > threshold, since we have seen a quorum of nodes vote commit(b) we know > that there is at least one of these nodes in all quorums and therefore > no quorum could accept, prepared or committed, any ballot with a > value other than b. > > So we can say securely that the nodes we have seen vote commit(b), > cannot accept a commit with a different value or abort their vote. > > Now I'm wondering how do we know at this point that the network will > not get stuck? For instance how do we know that a quorum that contains > one of the nodes that has voted to commit(b), may not have nodes that > vote for a higher incompatible ballot, that they can never accept? > > So my thinking thus far is that: > > The node that has voted to commit(b) in this quorum must have seen > every node in the quorum accept prepare(b). If we consider any one of > those nodes that have accepted prepare(b), in order for it to accept a > new ballot prepared it will need to hear from the rest of its quorum > and when it does hear from the rest of its quorum, it will in fact > confirm prepare(b) at which point the node stops considering new > values for its ballots. So we can see that nodes will not get stuck > voting for higher incompatible ballots. > > It would be good to know if I'm on the right track or If I have gone > off the deep end? And also I'm still not clear at all on why nodes > changing mid slice makes it necessary to confirm prepare(b) and accept > commit(b) so any explanation of that would be great! > > Thanks, > > Piers From nobody Thu Oct 25 19:00:41 2018 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 B87E5130E30 for ; Thu, 25 Oct 2018 19:00:39 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=eecs-berkeley-edu.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 olRleTxRBOof for ; Thu, 25 Oct 2018 19:00:37 -0700 (PDT) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 76A531294D7 for ; Thu, 25 Oct 2018 19:00:37 -0700 (PDT) Received: by mail-io1-xd2b.google.com with SMTP id a23-v6so6753653iod.7 for ; Thu, 25 Oct 2018 19:00:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eecs-berkeley-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=N+iyxsXn8T4CuhlnnSTHWTVl6bDB6NAISgwPeF41DYg=; b=xeUXMUZMXaYggy2X31B+2riallHI4h/yWavDBvQVTjrGgS/rxJ/sUURsGqnKjSgq9Y jmflHj6OWg+SMUveJj0+K0fOP7q0WuhG8cYydD/+CEszeRkOujxTBG6Mdeq55sqnz7rm HgfbT5re33SJPE/Fn5dacAIlm6A30A4dDRg98yGKWOwSQ08cMBlElOm0fcRzW1QK2nbL z/oAWrQRvpOPJ4FvcCWc4tP1fh6pVipY9KEiZEschOPhEHmEcqd6DxY83UUpJ0yf+A/u Fi3Z4INpW37kV+N9AQj5XskTaLhTdYTemMQvCHITciLjaZjw+koOrchrao5ghcN3QF4x rETQ== 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=N+iyxsXn8T4CuhlnnSTHWTVl6bDB6NAISgwPeF41DYg=; b=hp9Zbfi8I6Pw8K0IkC1qpDrme6KJZtkNkw+MD+G5BXKmmDhZsbJitZUX7xkrxf5mGt x+MOi4jW1OsOQKPB3IDbZKj4vnw70N7E6SPt1GFYmXSqbZQPD3bZr8q13bEBwULW/tpa ZXWAfBrHI+aNxHpaBH/Afabz0/nA0b40i6bIc2sLNJFZgB22U6SBZxPLiDuCP1bVK32b 0GBDS5QyUWFHvSbo5DFZ2c2kkmZHSXlUdg9B81LDBtDShp908CEmt/Bz+4x5bB43kV9A +/0Zax/MZsLtVkLniAs9V2RHVQ0409KRcIJIBEp0zqYR75/WCX8Nqf84VIWq7XTeSwHv 8GTA== X-Gm-Message-State: AGRZ1gJPLKhk19Ui1Wuxc3k8PJDvGd7qPE+9HbnIItHArTCXV9WYjuOt RaK4cd/3YFQEQypeD0J5Ftd1Z8YtRJTwEQRIXb42vZbV+Co= X-Google-Smtp-Source: AJdET5drB20xsIUjRVdqRxpXSRfhMPAZGcCH/6Dkb+/veJtfTe4HRhZ+NHRzIONwNejImFe+3NBVwHTS6t37O/rfHWo= X-Received: by 2002:a5e:d717:: with SMTP id v23-v6mr1075727iom.54.1540519236443; Thu, 25 Oct 2018 19:00:36 -0700 (PDT) MIME-Version: 1.0 From: Jean-Luc Watson Date: Thu, 25 Oct 2018 19:00:25 -0700 Message-ID: To: din@irtf.org Content-Type: multipart/alternative; boundary="000000000000dbb78e05791815b4" Archived-At: Subject: [Din] Updated DelMap draft 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, 26 Oct 2018 02:00:40 -0000 --000000000000dbb78e05791815b4 Content-Type: text/plain; charset="UTF-8" Hi all, We submitted an update to the delegated mappings draft earlier this week, which you can find at https://datatracker.ietf.org/doc/draft-watson-dinrg-delmap/. It has updates to the structure and interfaces to support bounds on the size of delegations, as well as extended discussion of security considerations. As always, we're happy to incorporate any feedback you have, and look forward to discussing it in person in Bangkok. Thanks, Jean-Luc --000000000000dbb78e05791815b4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
--000000000000dbb78e05791815b4-- From nobody Wed Oct 31 23:35:08 2018 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 296F812008A for ; Wed, 31 Oct 2018 23:35:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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 jsFvvx1ToRb0 for ; Wed, 31 Oct 2018 23:35:02 -0700 (PDT) Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (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 7B7051277CC for ; Wed, 31 Oct 2018 23:35:02 -0700 (PDT) Received: by mail-vs1-xe32.google.com with SMTP id w194so11582960vsc.11 for ; Wed, 31 Oct 2018 23:35:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=jYFVKE2xqKkIl4+1Twcd3OYf61EfELFXlFszOrR83wo=; b=bFvYdekAOgu/Sp0B1kgUU5Ej3Ad5ZUyLrmyzGDBSBn77GGEZj+ouKW/qAysxUFlSjg oeHl+TbFtnxKUCLcVaCyWOn5HNEXYMTe9FQZ9a6+4RVHqn0OAL4KiT9J+rcV6Da6P9pe FyAvd5EMdbUJx/c+NR2aYAqwNXvW7L4JAVgHGjPVJ7tB4GRSx27D2yC3z3DMKSakJWyb U6D7EhCA8b5KbnXAi3hCS2/n80Pap0kZrwMZ3CFY4RZQ35/NFCW3ttlu7EBtnCiBIC1U 0K/ACnSkHw5v5d5DwbhDpNpoV/Oxy8Ptrv9JbQa+xYTWjl/jnQJbLV8eE0OrA8cAtrf7 iWDQ== 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=jYFVKE2xqKkIl4+1Twcd3OYf61EfELFXlFszOrR83wo=; b=eBxPniEU1CkAVOACHP6mawSLbtdgKWtuHKGZCOy+I6t69/AD90mTKbRsttN1cfTnpY +0Ihb6REa8QVGpNkbH9SqjL31Qu+SBHuwycmVkxYFTaXRJLrkPwKbIG8eBG1C7omdxQv GatkzZClUyzXnJ63ZKaK5BUj6naoBexFV5JRy3N2LNwMEATzQ7iMkQp1/P8S4UVLzr5S RysB0+/PtZQbqQ95YLecoVoZLwJH9lvoYrdSYjhz4YCW6Vpf3+ZvQO6Q46X9UPXUTkha 0/iYdLR2O+S57ArrkQlbqqbIjpEgODVehNZEZyac8bK8/jsSOI1GBs33Go03T/HrHV1y oFRw== X-Gm-Message-State: AGRZ1gKJecNVCjfCQiZU1T1um2PjVtwrcyhmpswUDLphGxKvyXGcJUjv HrqIiyIFcCCVz9LjqMLjkQblk8LsoTK3gnjS/keM8tQ= X-Google-Smtp-Source: AJdET5eSVtttwG74ISI7rpCe4CQv9dr8yF4dz13kvQoCgJFCCrmGMMa6BzeXOE56s3yUzs+Xf/DLEcJFaCEesSi+AoU= X-Received: by 2002:a67:e15e:: with SMTP id o30mr2807643vsl.66.1541054101222; Wed, 31 Oct 2018 23:35:01 -0700 (PDT) MIME-Version: 1.0 References: <154104529553.5322.10827541457430264088.idtracker@ietfa.amsl.com> In-Reply-To: <154104529553.5322.10827541457430264088.idtracker@ietfa.amsl.com> From: Melinda Shore Date: Wed, 31 Oct 2018 22:34:49 -0800 Message-ID: To: din@irtf.org Content-Type: multipart/alternative; boundary="000000000000488b5e0579949ef0" Archived-At: Subject: [Din] Fwd: [103all] IETF 103 - Remote Participation Information 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, 01 Nov 2018 06:35:06 -0000 --000000000000488b5e0579949ef0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If you haven't seen this (and even if you have), here's how to participate in the upcoming meeting if you're unable to attend in person. Melinda ---------- Forwarded message --------- From: IETF Secretariat Date: Wed, Oct 31, 2018, 21:08 Subject: [103all] IETF 103 - Remote Participation Information To: IETF Announcement List Cc: , <103all@ietf.org> Can't make it to Bangkok? Participate remotely! The IETF offers a number of ways for remote attendees to audit or even contribute to IETF sessions throughout the meeting week. First, register for the meeting. There is no cost to register as a remote attendee, and by registering you will insure that you receive important updates on agenda changes and other things of interest to meeting attendees. Please register here: General remote participation information can be found here: . Below is a breakdown of some of the main services available. 1) Meetecho The Meetecho platform provides a synchronized view of the audio/video stream from the meeting room, which includes slides being presented and the presenter, as well as official IETF Jabber room. Meetecho will be supporting all eight of the working session tracks, as well as the Sunday tutorials, Host Speaker Series, and IETF Plenary. If you have a comment or a question, Meetecho enables you to ask it even if you are not in the room. For more information on how to join a Meetecho session, or to watch a recording after the session has concluded, see here: . To report issues with Meetecho, please send email to tickets@meeting.ietf.org. 2) Audio Stream If you only want to listen to the sessions, the audio stream is a good choice. All working sessions are streamed; links to the streams are available from the agenda, here: . To report issues with audio levels, please send email to mtd@ietf.org. 3) Jabber Rooms All IETF meeting sessions have a corresponding Jabber room. See here for link to the meeting agenda with corresponding Jabber rooms: . Whenever possible, an in-room volunteer monitors the Jabber room; this volunteer will stand at the microphone for remote attendees and relay their questions into the meeting room microphone so that people in the room can respond. More information on the IETF Jabber service is available here: . 4) Mailing Lists The 103attendees@ietf.org is for general discussion of things happening at the meeting; join the list if you want to hear about Bangkok restaurants and other topics of interest to those who are physically present at the meeting. Subscribe to 103attendees here: . The 103all@ietf.org list is for important announcements only and is not a discussion list. You automatically subscribed when you register as a remote participant. Being on 103all is essential if you want to hear about changes to meeting agenda or other important announcements. Subscribe to 103all here: . 5) Live video of several sessions, including the IETF Plenary and the IRTF Open Meeting, will be streamed live on YouTube. See for more information. After the meeting we will be sending a survey to all remote participants to get feedback on their experience; if you participate remotely, we=E2=80= =99d love to hear from you! And don=E2=80=99t forget to follow @ietf on Twitter! Only 2 days until the Bangkok IETF! --=20 103all mailing list 103all@ietf.org https://www.ietf.org/mailman/listinfo/103all --000000000000488b5e0579949ef0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If you haven't seen this (and even if you have), here= 's how to participate in the upcoming meeting if you're unable to a= ttend in person.

Melinda
=

---------- Forwarded = message ---------
From: = IETF Secretariat <ietf-secretariat@ietf.org>
Date: Wed, Oc= t 31, 2018, 21:08
Subject: [103all] IETF 103 - Remote Participation Info= rmation
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: <wgchairs@ietf.org>, <103all@ietf.org>


Can't make it to Bangkok= ? Participate remotely! The IETF offers a number
of ways for remote attendees to audit or even contribute to IETF
sessions throughout the meeting week.

First, register for the meeting. There is no cost to register as a
remote attendee, and by registering you will insure that you receive
important updates on agenda changes and other things of interest to
meeting attendees. Please register here:
<https://www.ietf.org/registrat= ion/ietf103/remotereg.py>

General remote participation information can be found here:
<https://ietf.org/how/meetings/103/remote/>. Below is a breakdown of
some of the main services available.

1) Meetecho
The Meetecho platform provides a synchronized view of the audio/video
stream from the meeting room, which includes slides being presented and the presenter, as well as official IETF Jabber room. Meetecho will be
supporting all eight of the working session tracks, as well as the
Sunday tutorials, Host Speaker Series, and IETF Plenary. If you have a
comment or a question, Meetecho enables you to ask it even if you are
not in the room. For more information on how to join a Meetecho session, or to watch a recording after the session has concluded, see here:
<http://ietf103.conf.meetecho.com/>. To report= issues with Meetecho,
please send email to tickets@meeting.ietf.org.

2) Audio Stream
If you only want to listen to the sessions, the audio stream is a good
choice. All working sessions are streamed; links to the streams are
available from the agenda, here:
<https://datatracker.ietf.org/meeting/1= 03/agenda>. To report issues with
audio levels, please send email to mtd@ietf.org.

3) Jabber Rooms
All IETF meeting sessions have a corresponding Jabber room. See here for link to the meeting agenda with corresponding Jabber rooms:
<https://datatracker.ietf.org/meeting/1= 03/agenda>. Whenever possible, an
in-room volunteer monitors the Jabber room; this volunteer will stand at the microphone for remote attendees and relay their questions into the
meeting room microphone so that people in the room can respond. More
information on the IETF Jabber service is available here:
<https://ietf.org/how/meetings/jabber/>.
4) Mailing Lists
The 103attendees@ietf.org is for general discussion of things happen= ing
at the meeting; join the list if you want to hear about Bangkok
restaurants and other topics of interest to those who are physically
present at the meeting. Subscribe to 103attendees here:
<https://www.ietf.org/mailman/listin= fo/103attendees>.

The 103all@ietf.org list is for important announcements only and is not a discussion list. You automatically subscribed when you register as a
remote participant. Being on 103all is essential if you want to hear
about changes to meeting agenda or other important announcements.
Subscribe to 103all here:
<https://www.ietf.org/mailman/listinfo/103= all>.

5) Live video of several sessions, including the IETF Plenary and the
IRTF Open Meeting, will be streamed live on YouTube. See
<https://www.ietf.org/live/> for more information.
After the meeting we will be sending a survey to all remote participants to get feedback on their experience; if you participate remotely, we=E2=80= =99d
love to hear from you! And don=E2=80=99t forget to follow @ietf on Twitter!=

Only 2 days until the Bangkok IETF!

--
103all mailing list
103= all@ietf.org
https://www.ietf.org/mailman/listinfo/103all<= /a>
--000000000000488b5e0579949ef0--