From nobody Tue Mar 1 23:15:22 2022 Return-Path: X-Original-To: dispatch@ietf.org Delivered-To: dispatch@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DECE3A12C8; Tue, 1 Mar 2022 23:15:20 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: dispatch@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.46.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: dispatch@ietf.org Message-ID: <164620532021.18018.9332482490862091283@ietfa.amsl.com> Date: Tue, 01 Mar 2022 23:15:20 -0800 Archived-At: Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-17.txt X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2022 07:15:20 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dispatch WG of the IETF. Title : ECMAScript Media Types Updates Authors : Matthew A. Miller Myles Borins Mathias Bynens Bradley Farias Filename : draft-ietf-dispatch-javascript-mjs-17.txt Pages : 16 Date : 2022-03-01 Abstract: This document describes the registration of media types for the ECMAScript and JavaScript programming languages and conformance requirements for implementations of these types. This document obsoletes RFC4329, "Scripting Media Types", replacing the previous registrations for "text/javascript" and "application/javascript" with information and requirements aligned with common usage and implementation experiences. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-17 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dispatch-javascript-mjs-17 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts From nobody Wed Mar 2 10:27:27 2022 Return-Path: X-Original-To: dispatch@ietf.org Delivered-To: dispatch@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F81A3A0ABD; Wed, 2 Mar 2022 10:27:23 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 7.46.0 Auto-Submitted: auto-generated Precedence: bulk Cc: Ben Campbell , The IESG , ben@nostrum.com, dispatch-chairs@ietf.org, dispatch@ietf.org, draft-ietf-dispatch-javascript-mjs@ietf.org, francesca.palombini@ericsson.com, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-ID: <164624564302.18092.4739852600836327579@ietfa.amsl.com> Date: Wed, 02 Mar 2022 10:27:23 -0800 Archived-At: Subject: [dispatch] Document Action: 'ECMAScript Media Types Updates' to Informational RFC (draft-ietf-dispatch-javascript-mjs-17.txt) X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2022 18:27:25 -0000 The IESG has approved the following document: - 'ECMAScript Media Types Updates' (draft-ietf-dispatch-javascript-mjs-17.txt) as Informational RFC This document is the product of the Dispatch Working Group. The IESG contact persons are Murray Kucherawy and Francesca Palombini. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/ Technical Summary This document updates the ECMAScript media types to prefer "text/ javascript", obsoletes other related media types, and introduces the new .mjs extension for JavaScript modules in order to align with implementation experience and industry practice. This document obsoletes RFC4329, "Scripting Media Types". Working Group Summary When this document was adopted by DISPATCH, it was a fairly simple update of RFC 4329 to update the IANA registrations to prefer "text/ javascript" and to mark other related media types as "OBSOLETE". The draft was changed to obsolete RFC 4329 due to WGLC feedback. That document has issues primarily related to how one determines text encoding and the use of file extensions to determine whether content should be interpreted as a module or script. This draft makes minor updates to that original text to align with current operational reality, but it does not attempt to "fix" them in ways that do not reflect current practice. This resulted in some discontent among reviewers who would prefer cleaner fixes vs. document existing practice. There have also been discontent about unnecessary and somewhat convoluted normative language in RFC 4329. This draft does not attempt to fix that in general, although it has made some simplifications in the text about determining the character-encoding scheme. Document Quality The procedures in the draft are understood by this shepherd to be implemented by most web browsers. The draft has undergone i18n and media-type reviews. John Levine performed a helpful early i18n review of version 07 on 8 May 2020. That review and follow on discussion resulted in improvements in version 08. The draft was posted to the media-type mailing list on 17 May, 2021. The resulting media-type discussion mainly rehashed issues already discussed (see "Working Group Summary") Personnel The responsible AD is Francesca Palombini. The shepherd is Ben Campbell. RFC Editor Note Please add the IESG Note. IESG Note This document records the relationship between the work of Ecma International's Technical Committee 39 and the media types used to identify relevant payloads. That relationship was developed outside of the IETF, and as a result is unfortunately not aligned with the best practices of BCP 13. Consequently, consensus exists in the IETF to document the relationship and update the relevant IANA registrations for those media types, but this is not an IETF endorsement of the media types chosen for this work. From nobody Fri Mar 4 11:29:00 2022 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B10433A0C9F for ; Fri, 4 Mar 2022 11:28:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.91 X-Spam-Level: X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 LdxVbkg6uEqi for ; Fri, 4 Mar 2022 11:28:54 -0800 (PST) Received: from smtp87.ord1c.emailsrvr.com (smtp87.ord1c.emailsrvr.com [108.166.43.87]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D6193A0B57 for ; Fri, 4 Mar 2022 11:28:54 -0800 (PST) X-Auth-ID: fluffy@iii.ca Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 5C9FFA00D6; Fri, 4 Mar 2022 14:28:49 -0500 (EST) Message-ID: Date: Fri, 4 Mar 2022 12:28:45 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Content-Language: en-US To: dispatch@ietf.org, dispatch-chairs@ietf.org From: Cullen Jennings Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Classification-ID: 3aa1b078-29f1-4de9-9e52-70f6570070a1-1-1 Archived-At: Subject: [dispatch] Request for agenda time for Game Moves over RTP X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2022 19:28:59 -0000 I would like to figure out how/where to proceed with draft-jennings-dispatch-game-state-over-rtp This draft describes a format for encoding game moves and the state of game objects over RTP. Cisco is using it for an AR/VR hologram conferencing system but there are a range of uses cases. Could we get some time to discuss where to do this work? Thank you, Cullen From nobody Fri Mar 4 12:55:06 2022 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 980333A1049; Fri, 4 Mar 2022 12:55:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.109 X-Spam-Level: X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 R4cPXcwi7UJ6; Fri, 4 Mar 2022 12:54:59 -0800 (PST) Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-db5eur03on060c.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0a::60c]) (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 637073A1046; Fri, 4 Mar 2022 12:54:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FgkH767Si1rRw8pBdNWPl3rOl0Ti8GlIQlCqecm8eEMXBe6JrHfpK+kYnHEQmKyogIVpSgrqCYN/0CWlwTLhVTK48tBhIRofkBnlHWXHwMGMbyfFs3Z9UBXBIrXOSsg9yIeHQ5xIlJb9wndnJQ32wqQcZWTVcgfvdqezzizdcag5Iwn2/pKtC1ir+TNP+cpymD3gLuaVYQy2ZwUVt0aa4N1aT3jJjG5ek34IfqXL9dS5i/ppk2lnAqsUlzIU1oTpTwfe734s9X+Iar2eqF9kYTUSuc7M30r2WcAfm9jRVOMroOzA2S0/2k+oPXA7ujKY1Z3SxCQH2PkZ6QIB8R5mMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=B3urqQj9aMPnhJaGuErbm4WIB8BCSZl1oAttDKUij3M=; b=BMzOSOpHdaikPXlJpPiEuwdyBcG0TRoUeXP7VjHQ5Tx2A5NEuHORvOyUO8DLZf2tjMB+0nKvmBDN800uGwj+7K5EMQDggtjT29EZpNh+rlYA6BtUNV/C3WXNQ/yB+Ocy1YZB6c02vLZGfiFm/dmdNmLb8Q83qjD8EmX6Tdpv7yjY/rRKvsHn8Psii6+wRo4wCh6LXx2uhZREQwOUUZ0922dqzbbXf7cCDCHJhygneD8/9ndZbP9GXqui59ZeMY+PbwF4hhpGMBwV/+tQwdmOeQdfaS2U1cbh7ldlix8AVh8sMAA54EiFM2yO78DenYaedl3yR3/2jXF2XyhuVqpR+Q== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=B3urqQj9aMPnhJaGuErbm4WIB8BCSZl1oAttDKUij3M=; b=Kccj3QZN0/W+P3+0pUvBudiBArWMUJJE9wNeZ1sj8xFusIFe1TBn3g/q4QqofYqxD1NgWh6clhhdE/hvdLutwbVZj0iJ0DAyKBoT39VAsHRVKIz4WYUIssy3f2EOE7FpYiX5SkIPGk9moiFlOfuAmKfA/d3QpW11UrDq/mdMEfg= Received: from PA4PR07MB8414.eurprd07.prod.outlook.com (2603:10a6:102:2a2::6) by AM7PR07MB6405.eurprd07.prod.outlook.com (2603:10a6:20b:132::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5038.11; Fri, 4 Mar 2022 20:54:49 +0000 Received: from PA4PR07MB8414.eurprd07.prod.outlook.com ([fe80::f154:6b1c:52f1:cba]) by PA4PR07MB8414.eurprd07.prod.outlook.com ([fe80::f154:6b1c:52f1:cba%7]) with mapi id 15.20.5061.004; Fri, 4 Mar 2022 20:54:49 +0000 From: Magnus Westerlund To: "dispatch@ietf.org" , "dispatch-chairs@ietf.org" , "fluffy@iii.ca" Thread-Topic: [dispatch] Request for agenda time for Game Moves over RTP Thread-Index: AQHYL/4kL3t3b/O7XE21bmeCm5GhtqyvtC6A Date: Fri, 4 Mar 2022 20:54:49 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US, sv-SE Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-mailer: Evolution 3.28.5-0ubuntu0.18.04.2 authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 8e059f00-cb9b-4af3-6088-08d9fe2138f7 x-ms-traffictypediagnostic: AM7PR07MB6405:EE_ x-microsoft-antispam-prvs: x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: BUF/CMUfRLmqkKo6he7Um5Q+VTQuw3se1U9uobAyjoE+RZzf1HpxGQxNHeTu7mhGYXEKg8MgiADMtfcIlxsOSdPxl9rMzQeqvP/ZxqhIbfmuFSpnhyw8ywLKOWZVok2y04WgpGR1vEUEaHYUAuCWfXJwpeTk2LyWgvw+lhoX3z+FTYIRqPToHUqgQA12HnRMFweG140ytcVW60YiqDYJFzp2nCfpxYDfHrSomHuQiFhWcrDpvSLYbbSTtIzkPANtC9NrlS3wls0/l7JU8PAqpLOnHmrGarJEKZ3F+yVijIK0pfJ281+p01z3E44+hHArjGcVp5NNwZ/vSWjAWbKOdx6L6utEgk3KPsZ9GMqmCOJIdpCr1CFoM0WqhfzxkO9xMoK9JUJLe/uHJ+HeTpRBvuRbdhBJK6TQtgDZZ8ZnnawSohwuIg7cr6+0iGXtY8/EXzzgXA+P8vaufuYLGWzaNqPy5xSCy80axPTYuiSJ2oe5V0660UOtcQHMcFxUwvPs++Na5KjBBBLBjvQ+E5wVZ1V3N4A28Wz+Ie9gnDTrAL41hy0PNqzIauC11jFd4bk3SNMzVmXpZoBCDiA/L3XuGsyPmtKq1eY2MZcUwQ/4HsGiUERCJogFh/hWqbyKw4DOqchPb4VzpplMHiEjGtCL4o4mN8MgljATFKPKLWtWoLjilsekxUXaHmWUjIv/UFxEe15JTzvoGA1c1wOA3s4U7+z67eiUpqOuXOfYr/aXB3L7GCQY1d6tMR0wRHOFI+cY2NALIxrEqnHkkzYrnXb1y+v84zUQVLvxQXvIp7ngh9spApX8o+C225W4BsF3yqZHDX7q9hraSvY1QTBtIctVFjbjlaH5hK82rCs6nhfRP6Gg3Me9SdMbc53mIcGlLDj37GBqafbzkvQl1VanFHpLgw== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PA4PR07MB8414.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(4636009)(366004)(186003)(2616005)(26005)(91956017)(82960400001)(71200400001)(36756003)(38070700005)(110136005)(38100700002)(2906002)(66946007)(76116006)(66476007)(66446008)(64756008)(66556008)(8676002)(316002)(5660300002)(6506007)(6512007)(166002)(122000001)(99936003)(86362001)(44832011)(8936002)(6486002)(966005)(508600001)(83380400001)(99106002); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?utf-8?B?MVA1cnM0WGVaN0Z2VVFkZGdTSndIOEpqcWxjRzJlMkNoeDFkZGFvTXhpOHZj?= =?utf-8?B?QkV0MkhJS2VaTno5aUlYeFRuYWxLT3pPSnA0dDAxTGNnTVdjVjF3Z2xicUVk?= =?utf-8?B?Y0dodU1veHpmN0FDMTZVSW11R2Vpdk5jaHpsNGN5bjl0ZkVHNDc2Q0gwVldQ?= =?utf-8?B?Y0ozUHNSUHBMeUU4K1NJRGhoZlVGTFhqcWRBY1F1aDFQUEVqZS9UeVhWamgx?= =?utf-8?B?K2RSVEE5WVBCWmMyMDdYVGFUZzJHeUU5YzdsY3dlM3BPMWNmeXhvZUx5dlFn?= =?utf-8?B?TisyOWNDSGNIN2dQbGhxekQ2RHhtUlMrL3NOQnZNY2dlS2RTR2xsK0gvWWM3?= =?utf-8?B?Z3E4N3k5dHQwSXhOZWI3Vzl3U1ZsUDBnTzkwOWh2RWFSV2JnRVdLRDNOdURD?= =?utf-8?B?a3hVN2xXOHN3cUJtbWd1K3N3L3UvT2ZiQW9KME1HY0hQRkFUNEtnN2ZTRCtS?= =?utf-8?B?R0JCeEZOV3FlUmlwZzRiNVRRMXFnNVhGRFZ5allVemIrYTRkd09YYjVkeFNR?= =?utf-8?B?M3VJUDgxY1NaZTBrVDhmSkU3UmZsdkxuR1dSQXEwYWp1bEVHazdLUmQ1N09V?= =?utf-8?B?N3F6cWJsYjF1TEFoVnR4SUs4UHdHenVjODg2Tm9kM3kyU2czYXVFVFN0NHJZ?= =?utf-8?B?ZktJaVJ6dDdkWXl0TENwcWFrRFc1WWdNbGVETnI1amR4bGExZGp5aUNkT1cz?= =?utf-8?B?Y2F1eFFqMUg5Q1JmTlpkVzVBNjU3dFVqU3NMbllaZFN0ZENUT0VjVzM4bFho?= =?utf-8?B?WmtFZGYzdjZvdGU0ZldvY1B3K2ljdVBIWG94cEczUTYzd3VZTkY1eGZjTC84?= =?utf-8?B?YUxGQVBNd05Dbk04akNOVTNscTlmdk9kbFhPZzFGaElUMzVQc3Y2eVRGM2xq?= =?utf-8?B?S1FBRGtNZjhTOEgwM1N5dkRIS0VPaHFZM3oyRU1VQm55clZiMi9qL2NsV2xP?= =?utf-8?B?dUc5dHJUcitrbTZTWmhEMlpqRVBXNVEvd2JnRnpsb09rY0tkSVI0cG9uY1N5?= =?utf-8?B?OE9qc252dm1RZ1dLM013STdzcmdmZGdpYWxLN2JaeFpKeEpBd29zcE1IcWJ5?= =?utf-8?B?QXYrODVpSUtNQXZQY3I1Nm9ZbnV5SFFZUk9iY0FxNHJYSzJ4Ly9oeFZjUGR3?= =?utf-8?B?ekNNbG9UOXJDcGQzSzhJdUJmWnJaRXJQRVhObm42N3Z5eUZ2WTJiR0VVRS9J?= =?utf-8?B?bFFOZmtrN2ViYlprQkxNL010MENNcmNJcGQ0c2w0UkFXN0RTUzVxVG02cmtm?= =?utf-8?B?VTRpeUZQb3JuTmo1Z0g3TndvL0JMdWRkSDNmdGNucTRYckRkVWo3Y2ZPYTZF?= =?utf-8?B?RllvNTFvaG00QkJOd3R3dnlDeGRRMjJVc1l3MmM1bzV5ZnlDSnVXSHU0K3Mv?= =?utf-8?B?azBHNTM1MkhrcEdSQzZCczNnUWNjUG0ybTlHUHJwUEJJNm1veHFBc3NGbnB6?= =?utf-8?B?bTZma3B5amljL2VpYit0VW5zeE5CRG54d2Z1UUJtejdvSExnVG8vdkJ0d0tV?= =?utf-8?B?WGs3Q2NaMi84S2NGN1dNb2VNRWkyckRSOTNVMDhjMFowQVh0THNQS2U3YVhy?= =?utf-8?B?NEY1QUFWenBwUGJBUXpVTHhxVW9RM0hQaS9hOVNqbEpOUmxITGNDbDl2c2FO?= =?utf-8?B?bWIreTZvTFRpNHUwMHYwWXZ5ejlmS292L1ZYVnFnc1BTV05jc05XU0o3YTZS?= =?utf-8?B?aWREbjRudjRBeWNTci9GMXloVFVRSEQ1K3BMZ2V4a2NFSnBLSm1OZ3MxZkRt?= =?utf-8?B?YWEwdk1uZ2F5TVZSK080QXlleHhvOTJDYzJoWnZKeDA3YTZCanRBOXplWTJC?= =?utf-8?B?aTFxWXJwano4bXBpOG5kMjNEYzVjK0U3WkVOZ0tQMThrQlAxbFQ5ckYvOTBu?= =?utf-8?B?Z2JmZE5oTVpBSGtrWmpMN2ZZRmFZZ0g5cU53UDg4alp4QjloY3Z2ZGJ6Z1Iv?= =?utf-8?B?a0ZXVVk4c2lEVzM1aEQwa1lLZHBFWGtjSGhqSEg2V1dhVS9UZTNaYVNHaG9q?= =?utf-8?B?TzZCVGk4RXU1UTJ0T0Zlc2JLL3FrSlNVeUtuNzU3MVFlRWZnbWcvcFFiaUVI?= =?utf-8?B?ZGd1Z1duUFJLbWtGK3kwdW1saWdLazJtaUtmWjRrSnE2SFJTaE5TMnJtNlhN?= =?utf-8?B?WUNhSk50THpiY25PTGI5bUxtakJYQnFobkJFZFhjTG1lZTJhN3ZNdkFUSWd5?= =?utf-8?B?NXo2TTlHdkNvTElRTlcycjNzV2tJRzRrS0ZROU9aNTVNVExDVDJUVGU4UUJX?= =?utf-8?Q?uHdJPtWEeQGrz/oMHAOKJYW7zQZNe8Ro+YEgUPnFsc=3D?= Content-Type: multipart/signed; micalg="sha-256"; protocol="application/x-pkcs7-signature"; boundary="=-2wX/FLHDBrVCaJ+5L4ry" MIME-Version: 1.0 X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: PA4PR07MB8414.eurprd07.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 8e059f00-cb9b-4af3-6088-08d9fe2138f7 X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2022 20:54:49.1966 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: dcFD5G2mrmFUk1XfIMwV8bD5w7IVo6lHjOmZgvKwYbDtVMC531V2IinkT1HC02kIY+U2Vef0+gcuANh2xwGrYz6OgFIFC9SaHvGPpNnMKTY= X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR07MB6405 Archived-At: Subject: Re: [dispatch] Request for agenda time for Game Moves over RTP X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2022 20:55:04 -0000 --=-2wX/FLHDBrVCaJ+5L4ry Content-Type: multipart/alternative; boundary="=-KYToT4bCD4ukVZ9jRzwt" --=-KYToT4bCD4ukVZ9jRzwt Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Cullen, As AVTCORE is the WG that is chartered to standardized RTP Payload formats I would think it belongs there. Any specific reason you have for not taking it there? I would note that this appear to have some similarities with the MIDI RTP payload format. Although you appear to indicate that is actually have less problematic issues than what resulted in the recovery journal solution in RFC 6295=20 https://datatracker.ietf.org/doc/rfc6295/ I think the input aspects like head, and hands location and direction are fairly straight forward streaming sources that appears to match RTP model for sources. Cheers Magnus On Fri, 2022-03-04 at 12:28 -0700, Cullen Jennings wrote: > I would like to figure out how/where to proceed with >=20 > draft-jennings-dispatch-game-state-over-rtp >=20 > This draft describes a format for encoding game moves and the state of= =20 > game objects over RTP. Cisco is using it for an AR/VR hologram=20 > conferencing system but there are a range of uses cases. >=20 > Could we get some time to discuss where to do this work? >=20 > Thank you, Cullen >=20 >=20 >=20 >=20 > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch >=20 --=-KYToT4bCD4ukVZ9jRzwt Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Hi Cullen,

As AVTCORE is the WG that is c= hartered to standardized RTP Payload formats I would think it belongs there= . Any specific reason you have for not taking it there? I would note that t= his appear to have some similarities with the MIDI RTP payload format. Alt= hough you appear to indicate that is actually have less problematic issues = than what resulted in the recovery journal solution in RFC 6295 https://datatracker.ietf.org/doc= /rfc6295/

I think the input aspects like head,= and hands location and direction are fairly straight forward streaming sou= rces that appears to match RTP model for sources.

= Cheers

Magnus


<= div>On Fri, 2022-03-04 at 12:28 -0700, Cullen Jennings wrote:
I would like to figure out how/where to proceed wit=
h

draft-jennings-dispatch-game-state-over-rtp

This draft describes a format for encoding game moves =
and the state of 
game objects over RTP. Cisco is using it for an=
 AR/VR hologram 
conferencing system but there are a range of use=
s cases.

Could we get some time to discuss where t=
o do this work?

Thank you, Cullen




_____________________=
__________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman=
/listinfo/dispatch



--=-KYToT4bCD4ukVZ9jRzwt--

--=-2wX/FLHDBrVCaJ+5L4ry
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCErYw
ggX0MIID3KADAgECAg8BdlE9InYZOYLl1zGep4IwDQYJKoZIhvcNAQELBQAwRzELMAkGA1UEBhMC
U0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENB
IHYzMB4XDTIwMTIxMTA5NTg0OVoXDTIzMTIxMjA5NTg0OVowXjERMA8GA1UECgwIRXJpY3Nzb24x
GjAYBgNVBAMMEU1hZ251cyBXZXN0ZXJsdW5kMS0wKwYJKoZIhvcNAQkBFh5tYWdudXMud2VzdGVy
bHVuZEBlcmljc3Nvbi5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCIT6U9ddUp
UCEryIA27xtF8WsRAIfc5jBavfu0OGDmwITYYRD2PaMEdEK+I4dqz0f6xcCrDnBk2Xj+JxjhaRkq
TAifJZima9WE2JoI/uq8UsS2HJWlhspAwKx1osARgtRiMjRZZyyfiRZLbgXHWYpnTt3i9QsuX/uo
9oZFWpDCbZee4Il9uldsUcuBLZx2PyZvBvC8KCUaBXsZX6bwV7hssRVn+BgFCuEievJMx0khTRVh
i9goObxu5Jl44RtwbZNYB1UE1IzRWEZw+b3cEvXiQjPl2e3ytMZSmhy+IaKmjxES6ODiuh51KAcm
PZfZIaX2djmD76YGi+ETmnb8Xm3dAgMBAAGjggHEMIIBwDAfBgNVHSMEGDAWgBQcexmel5x2rCA9
2NzjkWrj2y2mUzAdBgNVHQ4EFgQUICO/88T0EQvEUm5+HVt/d9Mm+Z8wDgYDVR0PAQH/BAQDAgWg
MFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3Np
dG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMCkGA1UdEQQiMCCBHm1hZ251cy53ZXN0ZXJs
dW5kQGVyaWNzc29uLmNvbTBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0LnRlbGlh
LmNvbS9lcmljc3Nvbm5saW5kaXZpZHVhbGNhdjMuY3JsMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggr
BgEFBQcDAjCBggYIKwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3Qu
dGVsaWEuY29tMEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2Vy
aWNzc29ubmxpbmRpdmlkdWFsY2F2My5jZXIwDQYJKoZIhvcNAQELBQADggIBANRZXQy+lUW97uaL
uApOixnDKLpUoz+N/5Owd/9illmbxQDEY1/pPs4KJSvw88p+F3bmOzb+fLUNa6Mi/2Tw83FzEVmO
3RqzKtca+I9GDpRQ8oWL7hrUPJoNacidSZLmAP4L4kwHIhvGNX4f1c/oB4fAkP/xZsAAxYi7nKxd
XA2n/KMWNkezyB9BSsD8ZOS4pWU8UaZjd5r0fzqM5zQbU4EPqHa8jFMSMz1UrYXPKKxl6E4WA3TE
w1oLjcli0NWGQHyQ+3Kh7fe6zPoXfLd/2EQjr2o76ssgoqd2V1Mx5TRHdUyxjIMPEOVYpvcerNUB
hEBkaOQ9FugYcMhMc8BF7nQZq+hsL/T7idg4gE2sEfNdK9RBf/EVH10GMrmbadqTycztD1gUL3dV
Qxik4TCMxIctt9XqtTGHaMewZLQAXp/sHWlU/vmz9brcuzYQ9YVd5hTendGMUyGhWPV/KvxouKPK
zdrGeEqUQCeBwWgQASQNOrpTzMJwZAV/Ww3ExQCjHvflvUQzVuU0sC6AEVkgqMATIXS6h6rjLL31
pjt2JV84XRjF5afYkcRIHTsrtcoWeFtOu/GpZNhtq+tde0QvnkSsjczMWU0gKk0hXBmXwEGUimuD
Vq/Wvr0mr18d9mKA6xPNQOfn/VL5CWXa11OtOjj8WsTy3XUpyJ6dc9Z72TmKMIIF9DCCA9ygAwIB
AgIPAXZRPSJ2GTmC5dcxnqeCMA0GCSqGSIb3DQEBCwUAMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQK
DAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MzAeFw0yMDEy
MTEwOTU4NDlaFw0yMzEyMTIwOTU4NDlaMF4xETAPBgNVBAoMCEVyaWNzc29uMRowGAYDVQQDDBFN
YWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJARYebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nz
b24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAiE+lPXXVKVAhK8iANu8bRfFr
EQCH3OYwWr37tDhg5sCE2GEQ9j2jBHRCviOHas9H+sXAqw5wZNl4/icY4WkZKkwInyWYpmvVhNia
CP7qvFLEthyVpYbKQMCsdaLAEYLUYjI0WWcsn4kWS24Fx1mKZ07d4vULLl/7qPaGRVqQwm2XnuCJ
fbpXbFHLgS2cdj8mbwbwvCglGgV7GV+m8Fe4bLEVZ/gYBQrhInryTMdJIU0VYYvYKDm8buSZeOEb
cG2TWAdVBNSM0VhGcPm93BL14kIz5dnt8rTGUpocviGipo8REujg4roedSgHJj2X2SGl9nY5g++m
BovhE5p2/F5t3QIDAQABo4IBxDCCAcAwHwYDVR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMw
HQYDVR0OBBYEFCAjv/PE9BELxFJufh1bf3fTJvmfMA4GA1UdDwEB/wQEAwIFoDBVBgNVHSAETjBM
MEoGDCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1c3Qu
dGVsaWFzb25lcmEuY29tL0NQUzApBgNVHREEIjAggR5tYWdudXMud2VzdGVybHVuZEBlcmljc3Nv
bi5jb20wSAYDVR0fBEEwPzA9oDugOYY3aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nz
b25ubGluZGl2aWR1YWxjYXYzLmNybDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwgYIG
CCsGAQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBI
BggrBgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5k
aXZpZHVhbGNhdjMuY2VyMA0GCSqGSIb3DQEBCwUAA4ICAQDUWV0MvpVFve7mi7gKTosZwyi6VKM/
jf+TsHf/YpZZm8UAxGNf6T7OCiUr8PPKfhd25js2/ny1DWujIv9k8PNxcxFZjt0asyrXGviPRg6U
UPKFi+4a1DyaDWnInUmS5gD+C+JMByIbxjV+H9XP6AeHwJD/8WbAAMWIu5ysXVwNp/yjFjZHs8gf
QUrA/GTkuKVlPFGmY3ea9H86jOc0G1OBD6h2vIxTEjM9VK2FzyisZehOFgN0xMNaC43JYtDVhkB8
kPtyoe33usz6F3y3f9hEI69qO+rLIKKndldTMeU0R3VMsYyDDxDlWKb3HqzVAYRAZGjkPRboGHDI
THPARe50GavobC/0+4nYOIBNrBHzXSvUQX/xFR9dBjK5m2nak8nM7Q9YFC93VUMYpOEwjMSHLbfV
6rUxh2jHsGS0AF6f7B1pVP75s/W63Ls2EPWFXeYU3p3RjFMhoVj1fyr8aLijys3axnhKlEAngcFo
EAEkDTq6U8zCcGQFf1sNxMUAox735b1EM1blNLAugBFZIKjAEyF0uoeq4yy99aY7diVfOF0YxeWn
2JHESB07K7XKFnhbTrvxqWTYbavrXXtEL55ErI3MzFlNICpNIVwZl8BBlIprg1av1r69Jq9fHfZi
gOsTzUDn5/1S+Qll2tdTrTo4/FrE8t11KcienXPWe9k5ijCCBsIwggSqoAMCAQICEFO4foPhnJko
k7CbSRzsuOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmExHzAdBgNVBAMM
FlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUxMDI3MTIxNjQ2WjBH
MQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIElu
ZGl2aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDs8t8AALhQ8qe7
2FS3xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfSTm+7meisbhkqUXkL7fFzoe4iIZCh
/VuYUaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbXILlLhRummTdDdxhVW4Leo0awEhfLf98M
vWxzwCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfpVdiCulPTlmsmV2RSBSAwqBshZYRcQBIDfqmd
vkaoP9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2PUmE0rhu+Zs0nujnwhljPA2/8b8v9tGixD1zbtT7
zoM2Ot1menJpFp4zJVSfdKVgtoWqg5t2H/E0XY1LwJez89W07nscEocyBmpC+zJAmKxKhzEWqIyP
1UrZaEIFu+hO+s0Nm8sOUMa4TlG4rAUikc5U5TmUIGBRQGxulYhfAzqSYf8oLUMLky1DOa9eRu3s
p0FdQDEzQlnF/h1L4AK1MOkX1vS+fLgOvBo5LRU1fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25a
EvAA+yrrplCh/kYvSBjvZibz9Obbwx4yqS77/NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUU
kBUrrvijPDaGK5FNVSaioGvkC7IKioITKffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCC
AbQwgYoGCCsGAQUFBwEBBH4wfDAtBggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFz
b25lcmEuY29tMEsGCCsGAQUFBzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVy
YS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAE
TjBMMEoGDCsGAQQBgg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1
c3QudGVsaWFzb25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3JsLTMudHJ1
c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1UdJQQWMBQGCCsG
AQUFBwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7GZ6XnHasID3Y3OOR
auPbLaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0GCSqGSIb3DQEBCwUAA4IC
AQBQWGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDUJQEPRs5QtaZiObNHCZ7mmSNM
Vek4lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHGvw5RY6vRlZrj0uKvdASzYL4KMaB7
m3NwurNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYnnl2t3D3oBX2NZCQysshUcqRdUbkS13HT
CIChMuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwfixWms+C8sF0r9qN1uJGx6ELPOiFrLfNtcMNM
MbAqRHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ85AKjqzBnLSsjRGgbMgJ+xKtngmvEA155JmoKfUD7
DRbP6Kp14/Y9XFbR/WuDj84bYNKXe4HdDc1P+UMYm16m2L6LkIIoRlx0A5mi+K7jewuGqzFKkaPN
mJ0RLCi+4d4/47Zs3DC3PUNOxdOEEHf4kkdWOaSIuj3TQYhNv+LsgF0uijiBmaz2zUFDa2bcIkKa
kDZfAFM4HoHz8K2BZRaHKWhd3dZua/tlSiqokUFX2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i
0bqGahxlHYzl/QyEG/dujp3lewuVjCI0mPDkZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+W
kDGCAsowggLGAgEBMFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdlE9InYZOYLl1zGep4IwDQYJYIZIAWUD
BAIBBQCgggFBMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTIyMDMw
NDIwNTQ0N1owLwYJKoZIhvcNAQkEMSIEIGGsZaaWc5tK0XEWVafGD8rr73xlJFN5BBAlrJxDg8uF
MGkGCSsGAQQBgjcQBDFcMFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYD
VQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdlE9InYZOYLl1zGep4IwawYLKoZI
hvcNAQkQAgsxXKBaMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwc
RXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIPAXZRPSJ2GTmC5dcxnqeCMA0GCSqGSIb3DQEB
AQUABIIBAFeyUn5Xuy3nfL6XPCOZr+rrmGAB01i8yHyxF5wNsdP5W8vidAVWYCzUQ7rUoF3qSOdP
Xj67P6egwpGm6BE7BhQ9DNSDbjCbdazvxwHqxDW9y2HTd5k5vqNBTbqpyI6Ja1cz/CAdcIu12hCo
SpP4qtLvFSNMAqH8i6RhaBOt1j0/3MsCDXMwE7I5XFmIimNylBBKRRBYD7wednDopdlgdKzbr4pO
TRwJUE3zOv9Obe2FXpemHy+1qtxuRYvQGWkV++8qpe9LBG2ZCho46npoelGAicTAGw5bAkQ+Osea
1pU6nCDx5szNL8qaVTzPsRGILpy8f2yU6QXulxv9z6lMyeYAAAAAAAA=


--=-2wX/FLHDBrVCaJ+5L4ry--


From nobody Mon Mar  7 17:15:13 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D39583A0115 for ; Mon,  7 Mar 2022 17:15:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWJqkH5goXX9 for ; Mon,  7 Mar 2022 17:15:07 -0800 (PST)
Received: from smtp111.iad3a.emailsrvr.com (smtp111.iad3a.emailsrvr.com [173.203.187.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8CE13A00E3 for ; Mon,  7 Mar 2022 17:15:07 -0800 (PST)
X-Auth-ID: fluffy@iii.ca
Received: by smtp22.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 7F6BD188F;  Mon,  7 Mar 2022 20:15:05 -0500 (EST)
Message-ID: <5942a407-7db4-4667-da63-692a1c0d842e@iii.ca>
Date: Mon, 7 Mar 2022 18:15:06 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Magnus Westerlund , "dispatch@ietf.org" , Avt@ietf.org
References:  
From: Cullen Jennings 
In-Reply-To: 
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Classification-ID: a60aa920-e64f-4578-9cf5-c397611a6687-1-1
Archived-At: 
Subject: Re: [dispatch] Request for agenda time for Game Moves over RTP
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 08 Mar 2022 01:15:11 -0000

Perhaps AVTCORE is the right place but I'm not sure. ( Adding Avt@ietf 
to thread  )

This draft is more about defining the encoding of the position of 
objects and players than defining RTP Payload Format. It's more like the 
MIDI 1.0 specification, which I think of as a Media Format, plus the 
stuff in RFC 6295 that defined the Payload Format for MIDI.

This game state draft also needs the RTP Payload Format and clearly the 
expertise for Payload Format is in AVTCORE, but it was less clear to me 
that the other parts of actually defining the data and encoding of what 
goes in the Payload Format is in scope for AVTCORE.

I would be fine with doing this all in AVTCORE if that is all in the 
scope of AVTCORE. I can also imagine some scheme where it got split into 
two drafts (one for payload format and one for media format) but I am 
less keen on that as it just spreads stuff around too much for something 
that is pretty basic.

You have pretty solid history on all groups AVT and what is in scope so 
if you thought this fits in AVTCORE, I would glad to just pursue that 
path. I do want to figure out where to move this forward at this IETF 
and not still be asking where to do the work 6 months from now.



On 3/4/2022 1:54 PM, Magnus Westerlund wrote:
> Hi Cullen,
> 
> As AVTCORE is the WG that is chartered to standardized RTP Payload 
> formats I would think it belongs there. Any specific reason you have for 
> not taking it there? I would note that this appear to have some 
> similarities with the MIDI RTP payload format. Although you appear to 
> indicate that is actually have less problematic issues than what 
> resulted in the recovery journal solution in RFC 6295 
> https://datatracker.ietf.org/doc/rfc6295/ 
> 
> 
> I think the input aspects like head, and hands location and direction 
> are fairly straight forward streaming sources that appears to match RTP 
> model for sources.
> 
> Cheers
> 
> Magnus
> 
> 
> On Fri, 2022-03-04 at 12:28 -0700, Cullen Jennings wrote:
>> I would like to figure out how/where to proceed with
>>
>> draft-jennings-dispatch-game-state-over-rtp
>>
>> This draft describes a format for encoding game moves and the state of
>> game objects over RTP. Cisco is using it for an AR/VR hologram
>> conferencing system but there are a range of uses cases.
>>
>> Could we get some time to discuss where to do this work?
>>
>> Thank you, Cullen
>>
>>
>>
>>
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org  
>> https://www.ietf.org/mailman/listinfo/dispatch  
>>


From nobody Mon Mar  7 18:47:15 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E25F3A0A55 for ; Mon,  7 Mar 2022 18:47:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level: 
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ducksong.com header.b=UhgE50IR; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b=j0Jnjip2
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 57NPQc6isg2i for ; Mon,  7 Mar 2022 18:47:07 -0800 (PST)
Received: from outbound2p.ore.mailhop.org (outbound2p.ore.mailhop.org [54.187.218.212]) (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 A35673A0A52 for ; Mon,  7 Mar 2022 18:47:07 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1646707627; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=cVQIvUGG2VLsmQo8km+jeeTy62y7lmae6v9kHvPMaCK3yxUnfedr9NdyISpEhVA5gYxZ5csVCeuEt YgDYjNeaj6eJ0kL3eQgGRLvgObQDCR7nSa71CkDbo7O8lBKa9cqkiy0+A9GEv7PtkFwj/XgsiqTiSI +ZTvrnwxpOsx4Apv+A+yX5IzJnCsyyi4atpPSryscZGbyLAh7vn8SqLOPGYjnE+svICD3kMC90H6sS yT0hcwEOtJXdKVsRuZVp2GLY8wZjIJZW1e1ezEd6uwWapIHGIwBTaDe1A/Sj9WrmbLcxdlHrvsHME8 qjf0X2wjLf9wdfQ8G9aB8e/OD4OAsew==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:dkim-signature:dkim-signature:from; bh=E62gSZt85BAagenM2KmDLHgIpRQEffS2HzQXTbgxsRU=; b=lp/luE/8NftUQda+wAqMY2Qxp1/IpaesJ7ujC+en0HnC/Q0Myi4tZpkBN2XYymwaohjvcecQGAiCi BfRozy788mOF8qB1tUKYFAJFPEr+1KYHNwxYQv7sMGWcatV++lwoAEagAoQslef4BZO8e5ZvRfTxXJ BaZxw756VlsAEJIxiDroXlK4JprVTj58WswtnAB1RYWAZ5xqoAWqpm6DFbqFN5vxrjcltqMBJJS1tv S1sdSG6EFcfXJSEgaCNr7eTjMnP2y7LADnM85bxX1cV0g/UmDuivBy/GaNuHffb6CraH3U+qnmHJ9F raXIgusBfst85IBUqZHfnytTkpgjuyA==
ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=pass smtp.mailfrom=ducksong.com smtp.remote-ip=209.85.128.172; dmarc=none header.from=ducksong.com; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ducksong.com; s=duo-1537391512170-ea99bbb3; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=E62gSZt85BAagenM2KmDLHgIpRQEffS2HzQXTbgxsRU=; b=UhgE50IRf+Au9+xvU9ovkt4M2VhCbHQXdj2OUp2yOFMHgFZCgZi3A8UNYynptcD1GuC8/TObSPjzl qIv+JO7iCa3wk/EaBJwqyTUBtIgw28R9wvR1kJ0EiSGjlrtEaO0Ifrvo6AGzTmyhfRiSBpgojgLvwq qBfXCq5j7Gtq6MD0=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=E62gSZt85BAagenM2KmDLHgIpRQEffS2HzQXTbgxsRU=; b=j0Jnjip2LFsWfUuHZAnlmjVVpQoe513Mhvg7P9ojmq/DiITml4vw6YdvO1W/2ocbH8ohoFbiCuk2l 74FY+i8UgVO7W/tAlzzB2C7KHETwpzj4s5kST6EDfhS6LmPyMzH9PscvXVGgF2uEqpwSbX9zaIAnaH RPSqT5LDtsGL0HRIIXSlkhMQv8o0bpuHngzhv0VSHum5algTFQ2tHRgvSu3x9dO7JrfuPEKmA/RIGQ AobSLek9D/O//2tuF2FDMRpWWLh6hrFab7GFHyaSkgwMIzDGYlYmR51TDgnZ1MgKJoKZ9jQKvuc0BC 0mVh47+sup0+7x9zz78jRgiNdrblgFg==
X-Originating-IP: 209.85.128.172
X-MHO-RoutePath: bWNtYW51cw==
X-MHO-User: 098ad614-9e8a-11ec-a6d6-89389772cfc7
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from mail-yw1-f172.google.com (mail-yw1-f172.google.com [209.85.128.172]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id 098ad614-9e8a-11ec-a6d6-89389772cfc7; Tue, 08 Mar 2022 02:47:05 +0000 (UTC)
Received: by mail-yw1-f172.google.com with SMTP id 00721157ae682-2d6d0cb5da4so186606157b3.10;  Mon, 07 Mar 2022 18:47:04 -0800 (PST)
X-Gm-Message-State: AOAM531X74KF1OLrgnOMFJitjHlu+Vd/ykGc8b9Asz15d3i+Oq3I8K1B lHmq/cCCvIRd4C/HznDbPQ4SKdNc7XAH0os0L4w=
X-Google-Smtp-Source: ABdhPJwFUq/hAbOLYUyZu3hzP562qF2fOUR/VApNANz1yUsroS5YUcPs8vknlWnubP/1zOEO8XTIgH1DiIXynNz6k/U=
X-Received: by 2002:a81:6f54:0:b0:2db:c989:845c with SMTP id k81-20020a816f54000000b002dbc989845cmr11277539ywc.298.1646707624212; Mon, 07 Mar 2022 18:47:04 -0800 (PST)
MIME-Version: 1.0
References:   <5942a407-7db4-4667-da63-692a1c0d842e@iii.ca>
In-Reply-To: <5942a407-7db4-4667-da63-692a1c0d842e@iii.ca>
From: Patrick McManus 
Date: Mon, 7 Mar 2022 21:46:53 -0500
X-Gmail-Original-Message-ID: 
Message-ID: 
To: Cullen Jennings 
Cc: Magnus Westerlund , "dispatch@ietf.org" , Avt@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fd7e7705d9abfede"
Archived-At: 
Subject: Re: [dispatch] Request for agenda time for Game Moves over RTP
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 08 Mar 2022 02:47:13 -0000

--000000000000fd7e7705d9abfede
Content-Type: text/plain; charset="UTF-8"

I hope AVTCORE will have a discussion about adopting this. If they decline
to do so we can certainly make room for that on the dispatch agenda as a
backup.

On Mon, Mar 7, 2022 at 8:15 PM Cullen Jennings  wrote:

>
> Perhaps AVTCORE is the right place but I'm not sure. ( Adding Avt@ietf
> to thread  )
>
> This draft is more about defining the encoding of the position of
> objects and players than defining RTP Payload Format. It's more like the
> MIDI 1.0 specification, which I think of as a Media Format, plus the
> stuff in RFC 6295 that defined the Payload Format for MIDI.
>
> This game state draft also needs the RTP Payload Format and clearly the
> expertise for Payload Format is in AVTCORE, but it was less clear to me
> that the other parts of actually defining the data and encoding of what
> goes in the Payload Format is in scope for AVTCORE.
>
> I would be fine with doing this all in AVTCORE if that is all in the
> scope of AVTCORE. I can also imagine some scheme where it got split into
> two drafts (one for payload format and one for media format) but I am
> less keen on that as it just spreads stuff around too much for something
> that is pretty basic.
>
> You have pretty solid history on all groups AVT and what is in scope so
> if you thought this fits in AVTCORE, I would glad to just pursue that
> path. I do want to figure out where to move this forward at this IETF
> and not still be asking where to do the work 6 months from now.
>
>
>
> On 3/4/2022 1:54 PM, Magnus Westerlund wrote:
> > Hi Cullen,
> >
> > As AVTCORE is the WG that is chartered to standardized RTP Payload
> > formats I would think it belongs there. Any specific reason you have for
> > not taking it there? I would note that this appear to have some
> > similarities with the MIDI RTP payload format. Although you appear to
> > indicate that is actually have less problematic issues than what
> > resulted in the recovery journal solution in RFC 6295
> > https://datatracker.ietf.org/doc/rfc6295/
> > 
> >
> > I think the input aspects like head, and hands location and direction
> > are fairly straight forward streaming sources that appears to match RTP
> > model for sources.
> >
> > Cheers
> >
> > Magnus
> >
> >
> > On Fri, 2022-03-04 at 12:28 -0700, Cullen Jennings wrote:
> >> I would like to figure out how/where to proceed with
> >>
> >> draft-jennings-dispatch-game-state-over-rtp
> >>
> >> This draft describes a format for encoding game moves and the state of
> >> game objects over RTP. Cisco is using it for an AR/VR hologram
> >> conferencing system but there are a range of uses cases.
> >>
> >> Could we get some time to discuss where to do this work?
> >>
> >> Thank you, Cullen
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> dispatch mailing list
> >> dispatch@ietf.org  
> >> https://www.ietf.org/mailman/listinfo/dispatch  <
> https://www.ietf.org/mailman/listinfo/dispatch>
> >>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>
>

--000000000000fd7e7705d9abfede
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


I hope AVTCORE will have a discussion about adopting this.=
 If they decline to do so we can certainly make room for that on the dispat=
ch agenda as a backup.

On Mon, Mar 7, 2022 at 8:15 PM Cullen Jennings <fluffy@iii.ca> wrote:


Perhaps AVTCORE is the right place but I'm not sure. ( Adding Avt@ietf =


to thread=C2=A0 )



This draft is more about defining the encoding of the position of 

objects and players than defining RTP Payload Format. It's more like th=
e 

MIDI 1.0 specification, which I think of as a Media Format, plus the 

stuff in RFC 6295 that defined the Payload Format for MIDI.



This game state draft also needs the RTP Payload Format and clearly the 
expertise for Payload Format is in AVTCORE, but it was less clear to me 
that the other parts of actually defining the data and encoding of what 
goes in the Payload Format is in scope for AVTCORE.



I would be fine with doing this all in AVTCORE if that is all in the 

scope of AVTCORE. I can also imagine some scheme where it got split into 
two drafts (one for payload format and one for media format) but I am 

less keen on that as it just spreads stuff around too much for something 
that is pretty basic.



You have pretty solid history on all groups AVT and what is in scope so 
if you thought this fits in AVTCORE, I would glad to just pursue that 

path. I do want to figure out where to move this forward at this IETF 

and not still be asking where to do the work 6 months from now.







On 3/4/2022 1:54 PM, Magnus Westerlund wrote:

> Hi Cullen,

> 

> As AVTCORE is the WG that is chartered to standardized RTP Payload 
> formats I would think it belongs there. Any specific reason you have f=
or 

> not taking it there? I would note that this appear to have some 

> similarities with the MIDI RTP payload format. Although you appear to =


> indicate that is actually have less problematic issues than what 

> resulted in the recovery journal solution in RFC 6295 

> https://datatracker.ietf.org/doc/rfc6295/ 

> <https://datatracker.ietf.org/doc/rfc6295/><=
br>
> 

> I think the input aspects like head, and hands location and direction =


> are fairly straight forward streaming sources that appears to match RT=
P 

> model for sources.

> 

> Cheers

> 

> Magnus

> 

> 

> On Fri, 2022-03-04 at 12:28 -0700, Cullen Jennings wrote:

>> I would like to figure out how/where to proceed with

>>

>> draft-jennings-dispatch-game-state-over-rtp

>>

>> This draft describes a format for encoding game moves and the stat=
e of

>> game objects over RTP. Cisco is using it for an AR/VR hologram

>> conferencing system but there are a range of uses cases.

>>

>> Could we get some time to discuss where to do this work?

>>

>> Thank you, Cullen

>>

>>

>>

>>

>> _______________________________________________

>> dispatch mailing list

>> dispatch@ie=
tf.org=C2=A0 <mailto:dispatch@ietf.org>

>> https://www.ietf.org/mailman/listinfo/dispatc=
h=C2=A0 <https://www.ietf.org/mailman/listinfo/=
dispatch>

>>



_______________________________________________

dispatch mailing list

dispatch@ietf.org

https://www.ietf.org/mailman/listinfo/dispatch






--000000000000fd7e7705d9abfede--


From nobody Mon Mar  7 23:35:38 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2610C3A0A1F for ; Mon,  7 Mar 2022 23:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_MIME_MALF=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=wire-com.20210112.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 Cd8hQakecfra for ; Mon,  7 Mar 2022 23:35:30 -0800 (PST)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 73B0A3A0A10 for ; Mon,  7 Mar 2022 23:35:30 -0800 (PST)
Received: by mail-pl1-x62b.google.com with SMTP id e13so16312886plh.3 for ; Mon, 07 Mar 2022 23:35:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wire-com.20210112.gappssmtp.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=DEPD4foG+xsGeF1bULM422GtD4m4SgYFJjXYsPNE7z0=; b=COJ0qfmU8uIL03iVapw/Tm1eWv0gHR1HmOIpL2HYbqdPh+r9OBBUDqWkrozSLjbXpI ompCNA6YRUuw6D6jm15dpWZTmzDYMzH4qfLWIHDiHYL/S1Av5fVh8BwmOdSv3LrfHSIh 5s7zS3uwcNwzJV9r7l4u5WG8GKvxaqcOeGdD/idPg+C0s0nKSxtyiBmsH/2rUXetdfQ6 /qLIafrEQ3wusGQEKUIwM+laCMYrw5BbSJ2NqxZM392ah/oGzqOmx7AJWIsVVJzgsWa/ vsPFImGZ9oNVpQdxngHDoPFFtl/rGzIfE4TUnnoxEVxB9u6sxoPueAjIa8BtRVE63uwJ 7tBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=DEPD4foG+xsGeF1bULM422GtD4m4SgYFJjXYsPNE7z0=; b=hNpbeAnPLaveZouFdSjgyn/trTYc/+YQLtH4TZFvbHjDcusoyzDecR2O02frgUxIEc TpiuWFlWTmanYMa3LsqC04itJeTXP3mPMmPHPrIWYmign0+k9Ay9Vw8foxd63OwbotON 1C/h9hDLs4olLuiUHWVj33bJ42Qr00xxyUyaFLM7Lo0gfk6xBlJZbzgqR/tyRHJRDa19 nRetBmYEGMEF+KdHXlMC2/JBn3yWimk47+wCQazJhdzlX0T8WQwzVVTlMUWYayQK/hHt sWyXNjNphucpKXczyHtTXyPcIuvCL46vqbJ4OnFoAMKmSYPOdz+4TI6QU1nsvD30es4P oRrA==
X-Gm-Message-State: AOAM5323htByopVzaCWpdghS09OL70WR7H3WNFKYPY+0DS0si8pi12ge 2mxfJKDDySXwx/e3VSkCj+lpzT5M201CM60k6wmKh7Ux2n86v+fG
X-Google-Smtp-Source: ABdhPJxk/zjW+BJiQJqLCG1MRS+0XLFC3PSnUnxkwiftB9s2VOTqLOoGw3Tv1k43rwcsygg2qcqlpcbFTbIVQWOwO6Q=
X-Received: by 2002:a17:90a:c252:b0:1bc:52a8:cac8 with SMTP id d18-20020a17090ac25200b001bc52a8cac8mr3234108pjx.61.1646724929290; Mon, 07 Mar 2022 23:35:29 -0800 (PST)
MIME-Version: 1.0
From: Rohan Mahy 
Date: Tue, 8 Mar 2022 08:35:18 +0100
Message-ID: 
To: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="00000000000074173205d9b006cc"
Archived-At: 
Subject: [dispatch] Discussion about Instant Messaging inside the MLS protocol
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 08 Mar 2022 07:35:35 -0000

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

Hi,

I just submitted two new drafts about what happens inside the MLS
(Messaging Layer Security) protocol [0]. Many messaging services (Signal,
Telegram, WhatsApp, Wire) use variations on the DoubleRatchet protocol for
end-to-end encryption involving two clients. MLS defines a standardized
layer for end-to-end encrypting communication to an entire group, and was
largely motivated by extending DoubleRatchet security properties
efficiently to groups. Since the contents are encrypted, it seemed valuable
to define a format for basic interoperability for messaging systems.

The main draft [1] is mostly a profile of other things like CPIM and
various MIME headers.
[1] https://www.ietf.org/archive/id/draft-mahy-dispatch-immi-content-00.htm=
l
Please note that due to a formatting error as I was submitting, the
multipart/alternative example got truncated. I'm including it at the bottom
of this email.

The companion draft [2] defines two MLS extensions for negotiating MIME
types.
[2]
https://www.ietf.org/archive/id/draft-mahy-dispatch-immi-mls-mime-00.html

MLS has a narrow charter in the security area. [1] has really nothing to do
with the MLS protocol and requires app/art expertise. [2] is an extension
to MLS but has as much to do with MIME as with MLS and needs minimal
security expertise.

Dispatch seems as good a place as any to discuss this, so please have a
look and comment here.
Thanks,
-rohan

-----------
Omitted example from draft-mahy-dispatch-immi-content-00:

Content-type: multipart/alternative; boundary=3DXcrSXMwuRwk9

--XcrSXMwuRwk9
Content-type: message/cpim

From: 
DateTime: 2022-02-08T22:13:45-00:00
Message-ID: <28fd19857ad7@example.com>

Content-Type: text/plain; charset=3Dutf-8

Test Message
--XcrSXMwuRwk9
Content-type: application/vnd.examplevendor-fancy-im-message


--XcrSXMwuRwk9


*Rohan Mahy  *l  Vice President Engineering, Architecture

Chat: @rohan_wire on Wire



[0] https://www.ietf.org/archive/id/draft-ietf-mls-protocol-13.html


Wire  - Secure team messaging.

*Zeta Project Germany GmbH  *l  Rosenthaler Stra=C3=9Fe 40,
10178
Berlin,

Germany


Gesch=C3=A4ftsf=C3=BChrer/Managing Director: Morten J. Broegger

HRB 149847 beim Handelsregister Charlottenburg, Berlin

VAT-ID DE288748675

--00000000000074173205d9b006cc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Hi,

I just submitted two new=
 drafts about what happens inside the MLS (Messaging Layer Security) protoc=
ol [0]. Many messaging services (Signal, Telegram, WhatsApp, Wire) use vari=
ations on the DoubleRatchet protocol for end-to-end encryption involving tw=
o clients. MLS defines a standardized layer for end-to-end encrypting commu=
nication to an entire group, and was largely motivated by extending DoubleR=
atchet security properties efficiently to groups. Since the contents are en=
crypted, it seemed valuable to define a format for basic interoperability f=
or messaging systems. 

The main draft [1] is m=
ostly a profile of other things like CPIM and various MIME headers.
[1] https://www.ietf.org/archive/id/draft-mahy-dispatch-immi-c=
ontent-00.html
Please note that due to a formatting error as =
I was submitting, the multipart/alternative example got truncated. I'm =
including it at the bottom of this email.

The =
companion draft [2] defines two MLS extensions for negotiating MIME types.<=
br>

MLS has a narrow c=
harter in the security area. [1] has really nothing to do with the MLS prot=
ocol and requires app/art expertise. [2] is an extension to MLS but has as =
much to do with MIME as with MLS and needs minimal security expertise.

Dispatch seems as good a place as any to discuss this,=
 so please have a look and comment here.
Thanks,
-rohan=


-----------
Omitted example from dr=
aft-mahy-dispatch-immi-content-00:

Content-ty=
pe: multipart/alternative; boundary=3DXcrSXMwuRwk9

--XcrSXMwuRwk9Content-type: message/cpim

From: <im:alice-smith@example.com>
DateTime: 2022-02-0=
8T22:13:45-00:00
Message-ID: <28fd19857ad7@example.com>

Content-Type: text/plain; char=
set=3Dutf-8

Test Message
--XcrSXMwuRwk9
Content-type: applicat=
ion/vnd.examplevendor-fancy-im-message

<content of example vendor=
's fancy proprietary format>
--XcrSXMwuRwk9

<=
/div>

Rohan Mahy=C2=A0 l=C2=A0 Vice President Engineering, Archi=
tecture
Cha=
t: @rohan_wire on=C2=A0Wire
=
=C2=A0
[0] htt=
ps://www.ietf.org/archive/id/draft-ietf-mls-protocol-13.html

Wire=C2=A0- Secure team mess=
aging.
Zeta Project Germany GmbH=
=C2=A0=C2=A0l=C2=A0=C2=A0Rosenthaler Stra=C3=9Fe 40,=C2=A010178 Berlin,=
=C2=A0Germany
Gesch=C3=A4ftsf=C3=BChrer/Managing Director: Morten J=
. Broegger=C2=A0
<=
/span>
HRB 149847 beim Handelsregister Cha=
rlottenburg, Berlin
VAT-ID DE288748675


--00000000000074173205d9b006cc--


From nobody Fri Mar 11 11:22:32 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16F4B3A114A for ; Fri, 11 Mar 2022 11:22:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level: 
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 3ZUA_7XJq42p for ; Fri, 11 Mar 2022 11:22:29 -0800 (PST)
Received: from mail-il1-x12a.google.com (mail-il1-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 99C243A1143 for ; Fri, 11 Mar 2022 11:22:29 -0800 (PST)
Received: by mail-il1-x12a.google.com with SMTP id d3so6657237ilr.10 for ; Fri, 11 Mar 2022 11:22:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:from:date:message-id:subject:to; bh=gegbSkNThEUud8U3OMFBZOjzwBbWoY3zkUnxYvijTo4=; b=ggZi/UkPGAmiqNLNnO8BEfEawysP/cpU+woY/+LFO8Qk3AnDfi82iUHY0sP7Q1dy1D Wfqev5/0nja8MHVgrg9eIlg5hJCpt2VFIEnvZJpQxovgQYPkmdrXc+i6wS8aLuhwiDrn E3JC+4CFzupq2MhCPJ0MuMaT4q3yWMKddRljPQ3XstwtocMd75PQzQE/AABaDQ5PEx7S 6wb+O299HVqQhd01tkosqP/Cd+UDd9FF7X2wbdshdQC7COgD61hoa1LRX1V8tJJ4i+eL mVMQjYVZ0ezEjnmQRHScuFraGzQ6WEFSr8ejAh1U6H0zMw7Ip9SdTLl6R3qP23acrsvQ fnFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=gegbSkNThEUud8U3OMFBZOjzwBbWoY3zkUnxYvijTo4=; b=wZnUUK0OVNXybzbcgUncIUlhlB/vpAFktAfTm+RIzPrLD4eHZ1OsmmJfic1Yme6ky9 nsZpOyWLqhPS/P9AIg17TQT55Ef1olaTptumHOKSWkvOd0HFvCyTZsbFziIyRtsnmAQW 8QJQR7CYzI+veTth0JVGmiQWQU5Q3r0VUmxIu46uA9k715SEGyHa+lpsyKPr3U/m3ZoL M34trPPleAYh9jA2CFvYE/6O3QW/Ef8e+u1qGtfZ/IdJ1dbqrba/6jQydDWyOtM/ahPM JHQa15MDq+CVwMNQ0Wjruhx74qrayKf6ORgv8XvqI9q8FRGepUMIPYkA9Y0cFGlZm8J1 llBA==
X-Gm-Message-State: AOAM5325MSgQMBWQiCCPYZ6OX7Z9ZSwednQXPyljd5/qgPyVgNnNPTCD FFtNo7P3CdEaM2JlSN0L0FphXQEcDhKxANQIbEl2dTP0Z18=
X-Google-Smtp-Source: ABdhPJyAPBLF7RBswbYAPx2Iq6+vgvrzTwIffrbwvabhW1IC/NPm0idqI9D0p8UV98Npi9fqIKQZvHKoWfgOuCMtxgY=
X-Received: by 2002:a92:c888:0:b0:2c2:fb23:1cf with SMTP id w8-20020a92c888000000b002c2fb2301cfmr8671004ilo.301.1647026548714; Fri, 11 Mar 2022 11:22:28 -0800 (PST)
MIME-Version: 1.0
From: Kirsty Paine 
Date: Fri, 11 Mar 2022 19:22:18 +0000
Message-ID: 
To: DISPATCH list 
Content-Type: multipart/alternative; boundary="0000000000005f316605d9f6406c"
Archived-At: 
Subject: [dispatch] Dispatch session agenda for 113
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 11 Mar 2022 19:22:31 -0000

--0000000000005f316605d9f6406c
Content-Type: text/plain; charset="UTF-8"

Hi dispatchers,

You can now find the draft agenda for the IETF 113 dispatch meeting on the
datatracker:
https://datatracker.ietf.org/doc/agenda-113-dispatch/

Please also see the associated drafts for our session, which are listed on
this page:
https://datatracker.ietf.org/meeting/113/session/dispatch

If there are comments or amendments needed, please get in touch.

Kirsty

--0000000000005f316605d9f6406c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Hi dispatchers,

You can now find the dr=
aft agenda for the IETF 113 dispatch meeting on the datatracker:

Please also see the associated drafts for our session, which are listed =
on this page:

If there are comments or amendments need=
ed, please get in touch.=C2=A0

Kirsty


--0000000000005f316605d9f6406c--


From nobody Fri Mar 11 14:33:07 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B3953A10A4 for ; Fri, 11 Mar 2022 14:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 G_vZNwkKrBV5 for ; Fri, 11 Mar 2022 14:32:45 -0800 (PST)
Received: from smtp75.iad3b.emailsrvr.com (smtp75.iad3b.emailsrvr.com [146.20.161.75]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DF893A10C0 for ; Fri, 11 Mar 2022 14:32:15 -0800 (PST)
X-Auth-ID: fluffy@iii.ca
Received: by smtp18.relay.iad3b.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id CAD94E00F5;  Fri, 11 Mar 2022 17:32:13 -0500 (EST)
Message-ID: 
Date: Fri, 11 Mar 2022 14:32:16 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.2
Content-Language: en-US
To: Patrick McManus 
Cc: Magnus Westerlund , "dispatch@ietf.org" , Avt@ietf.org
References:   <5942a407-7db4-4667-da63-692a1c0d842e@iii.ca> 
From: Cullen Jennings 
In-Reply-To: 
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Classification-ID: d11ae09c-7774-47b1-88f5-c00f360773e6-1-1
Archived-At: 
Subject: Re: [dispatch] [AVTCORE] Request for agenda time for Game Moves over RTP
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 11 Mar 2022 22:32:48 -0000

On 3/7/2022 6:46 PM, Patrick McManus wrote:
> I hope AVTCORE will have a discussion about adopting this. If they 
> decline to do so we can certainly make room for that on the dispatch 
> agenda as a backup.
> 

Slight problem is that AVTCORE meeting is after the Dispatch meeting but 
this is going to be on the AVTCORE agenda so I think this sounds like a 
reasonable plan as long as the AVTCORE chairs don't see it as outside 
the scope of AVTCORE.



From nobody Sat Mar 12 15:56:16 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93A7A3A0C7A for ; Sat, 12 Mar 2022 15:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level: 
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.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 2954bgEyUZmT for ; Sat, 12 Mar 2022 15:54:54 -0800 (PST)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 C60943A0C66 for ; Sat, 12 Mar 2022 15:54:54 -0800 (PST)
Received: by mail-il1-x12d.google.com with SMTP id o12so8519436ilg.5 for ; Sat, 12 Mar 2022 15:54:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MESXRBy/h1vzeC5GMERGEBwPMw1Ce1/0V0/J3322Ml8=; b=Grj0Hzmu3JPgAhO2V9PJND3jtrTYFm/wYpi/HPSUU/IhVzRye306HxTbIsRNawHN46 DYt05huPWdbWXpGAjnsx6uLX7H10FjDc2/gHu3OdlAHgviS1rmV6h9uiy4xHMOkiIzpV R5tHqMDoZLxbpUuwY8dFTsMlsO04nxcgFZe7fQy/ag69cV15kz746WjrXKCBpQmsTysn reJGqB1G5pRFU/7B5n94advfw5E3IQewkDBOFQjtY6FeJECSYknkPPwxJK2yfAEZp2bZ t/onrHRAY12M4V36IYf5LRPdCnZOaoeM4V1UucxTsKeK0zSBULuQVcwTRUWA702AzrQU 5Yhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MESXRBy/h1vzeC5GMERGEBwPMw1Ce1/0V0/J3322Ml8=; b=S10yGe8x5pw0egfsKb2CrR5aWhusDH32yVepq8m4MT8/CnVwZGpG3R0WUaFeZku9YG ZdMxpyiRqq3SnyVKM/XAVcVnB0L6zMzESjUmiIJ9YEN6RH1DyIPWYIQ7oRJ8SOUCZ2h7 umM5aEsDfYabhoi68af+qYnhyF1KlDE7qk+cxUDIf/da/sJNVSkKTdsoZaRotUcDB++E X7eSfCPKLQvumcH+G0Skr9sBGcZUw/ByeLhpZxW8XG0UAXN2ZT9RSdSN3Pl/EcPj3uaA 8czfhl2fosh5f998vpwlx1yiNw6CIoCAynfrnJUBJqdSvM5YPBImflgWD18VCxCM28SA EPxA==
X-Gm-Message-State: AOAM530QKtwsMV4FGbIdkXL2pjHpXDRX6tLR9hh4gkFdWT+3qfB92vNm TeEBkL4LtHWJ9ahWQRPdU1ryqGeiInAKvdBCrPFrYw==
X-Google-Smtp-Source: ABdhPJxU8vwh8GueBLL01eCCyhzWacmmulwGX2cBC2iGOQGevkmhHWHBdUA9ac5FAo/bZ7+23dT7IY7BiLGQiStJWFg=
X-Received: by 2002:a92:c547:0:b0:2c6:5f91:e87a with SMTP id a7-20020a92c547000000b002c65f91e87amr13456475ilj.10.1647129293678; Sat, 12 Mar 2022 15:54:53 -0800 (PST)
MIME-Version: 1.0
References: <6dac86b0eb3b96490dadffdc0f1d307a@openethics.ai>
In-Reply-To: <6dac86b0eb3b96490dadffdc0f1d307a@openethics.ai>
From: Eric Rescorla 
Date: Sat, 12 Mar 2022 15:54:17 -0800
Message-ID: 
To: n.lukianets@openethics.ai
Cc: art@ietf.org, IETF SecDispatch , DISPATCH , hrpc@irtf.org
Content-Type: multipart/alternative; boundary="00000000000072ff2d05da0e2c22"
Archived-At: 
Subject: Re: [dispatch] [Secdispatch] Open Ethics Transparency Protocol
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 12 Mar 2022 23:55:03 -0000

--00000000000072ff2d05da0e2c22
Content-Type: text/plain; charset="UTF-8"

Leading with the [SEC]DISPATCH questions, I don't think we should do
anything here. I would feel differently if there were a significantly
stronger showing of general interest and more evidence that this could
be practically achieved.


I had a fair amount of trouble figuring out what this document was
trying to achieve. My best understanding is that this is intended to
be a machine-readable description of the data processing practices of
a given entity. The current document seems to mix several things:

- A mechanism for retrieving these statements via HTTP
- A schema for the contents of these statements
- A log-based transparency system

The details of all of this are fairly thin and I doubt could be implemented
interoperably. For instance, here's the section on Immutable storage:

   Both the signature integrity hash and the Disclosure SHOULD be stored
   in the log-centric root database and MAY be mirrored by other
   distributed databases for redundancy and safety.

This doesn't seem to define a specific protocol.


My primary question is whether this is a good idea. I have two primary
concerns:

1. Is there real demand for this?
2. Is it going to work.

On the former front, I'd like to hear whether there is a critical mass
of sites which would publish this kind of label. AFAICT nobody has
jumped in to say so on the thread. That seems like a prerequisite for
any IETF activity here.


On the latter piece, the main prior art that I am aware of in
attempting to provide machine-readable descriptions of this sort is
P3P, and I think it's generally agreed that that didn't work out. It's
not clear to me that it's really possible to define a sensible
taxonomy of this kind of information processing.

The description of what goes in the JSON is quite thin and doesn't
seem anywhere near detailed enough to understand the information
processing that a given entity performs.  The label generator linked
to in this draft has a bunch of multiple choice questions, e.g.,

  [ ] Open Source Code
  [ ] Proprietary Source Code

  Code development and reuse

  Please describe choices made for development and for use of existing code
libraries.

First, it's not clear why they are mutually exclusive, as I could use
both. Second, it seems like nearly all the interesting information is
going to be in the freeform portion, which badly undercuts the whole
enterprise.

-Ekr











On Mon, Jan 31, 2022 at 8:13 AM  wrote:

> Hi everyone,
> Nikita Lukianets from the Open Ethics initiative here.
>
> I've been working on the mechanisms to enable transparency for data
> collection and data processing practices for autonomous systems and
> specifically, those powered by machine learning models. Since 2020 I
> have started to draft a guiding document to reflect ways disclosures
> could be submitted, verified, and exchanged. Eventually, I would like to
> see how this work could result in an open standard.
>
> I've chosen IETF as a home for this work as AI-powered applications are
> becoming ubiquitous. Therefore, we should start looking at them from the
> internet standard and supply chain perspectives.
> There's an emergent need to bring a legally-agnostic and standardized
> way to describe these systems from privacy, security, fairness,
> datasets, and explainability stances.
>
> The idea is simple
> * Following the example of the food (construction, pharma, electrical
> appliance) industry, we need every application to (voluntary) disclose
> the "ingredients", e.g. how data is collected and outputs are produced.
> * We need to have a standard way (protocol) to represent each disclosure
> in human- and machine-readable formats, validate, verify and process
> them.
> * Complex apps will involve chaining the disclosures for the components
> involved.
>
>
> My motivation is to continue the discussion here and get feedback
> allowing us to iterate on the protocol. I'd like to bring this
> discussion to a relevant group or/and welcome the creation of the new
> one, also potentially bringing the conversation to the IETF meeting in
> Vienna.
>
> Below are the links with more info
> Article to bring the context, in plain English
>
> https://lukianets.medium.com/why-algorithmic-transparency-needs-a-protocol-2b6d5098572f
>
> The IETF I-D
>
> https://datatracker.ietf.org/doc/draft-lukianets-open-ethics-transparency-protocol/
>
> GitHub repo
> https://github.com/OpenEthicsAI/OETP
>
> Thanks a lot for your help and thoughts
>
>
> Nikita Lukianets
> Founder, CTO PocketConfidant
> Founder Open Ethics initiative
> Twitter: @nikiluk
> https://fr.linkedin.com/in/nikiluk
> Schedule a 30 min call: https://lukianets.com/meet/
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch
>

--00000000000072ff2d05da0e2c22
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Leading with the [SEC]DISPATCH questions, I don't thin=
k we should do
anything here. I would feel differently if there were a s=
ignificantly
stronger showing of general interest and more evidence that=
 this could
be practically achieved.


I had a fair amount of t=
rouble figuring out what this document was
trying to achieve. My best un=
derstanding is that this is intended to
be a machine-readable descriptio=
n of the data processing practices of
a given entity. The current docume=
nt seems to mix several things:

- A mechanism for retrieving these s=
tatements via HTTP
- A schema for the contents of these statements
- =
A log-based transparency system

The details of all of this are fairl=
y thin and I doubt could be implemented
interoperably. For instance, her=
e's the section on Immutable storage:

=C2=A0 =C2=A0Both the sign=
ature integrity hash and the Disclosure SHOULD be stored
=C2=A0 =C2=A0in=
 the log-centric root database and MAY be mirrored by other
=C2=A0 =C2=
=A0distributed databases for redundancy and safety.

This doesn't=
 seem to define a specific protocol.


My primary question is whet=
her this is a good idea. I have two primary
concerns:

1. Is there=
 real demand for this?
2. Is it going to work.

On the former fron=
t, I'd like to hear whether there is a critical mass
of sites which =
would publish this kind of label. AFAICT nobody has
jumped in to say so =
on the thread. That seems like a prerequisite for
any IETF activity here=
.


On the latter piece, the main prior art that I am aware of in<=
br>attempting to provide machine-readable descriptions of this sort is
P=
3P, and I think it's generally agreed that that didn't work out. It=
's
not clear to me that it's really possible to define a sensibl=
e
taxonomy of this kind of information processing.

The descriptio=
n of what goes in the JSON is quite thin and doesn't
seem anywhere n=
ear detailed enough to understand the information
processing that a give=
n entity performs.=C2=A0 The label generator linked
to in this draft has=
 a bunch of multiple choice questions, e.g.,

=C2=A0 [ ] Open Source =
Code
=C2=A0 [ ] Proprietary Source Code

=C2=A0 Code development a=
nd reuse

=C2=A0 Please describe choices made for development and for=
 use of existing code libraries.

First, it's not clear why they =
are mutually exclusive, as I could use
both. Second, it seems like nearl=
y all the interesting information is
going to be in the freeform portion=
, which badly undercuts the whole
enterprise. 

-Ekr










On Mon, Jan 31, 2022 at 8:13 AM <n.lukianets@openethics.ai> wro=
te:
Hi everyone,=


Nikita Lukianets from the Open Ethics initiative here.



I've been working on the mechanisms to enable transparency for data 
collection and data processing practices for autonomous systems and 

specifically, those powered by machine learning models. Since 2020 I 

have started to draft a guiding document to reflect ways disclosures 

could be submitted, verified, and exchanged. Eventually, I would like to 
see how this work could result in an open standard.



I've chosen IETF as a home for this work as AI-powered applications are=
 

becoming ubiquitous. Therefore, we should start looking at them from the 
internet standard and supply chain perspectives.

There's an emergent need to bring a legally-agnostic and standardized <=
br>
way to describe these systems from privacy, security, fairness, 

datasets, and explainability stances.



The idea is simple

* Following the example of the food (construction, pharma, electrical 

appliance) industry, we need every application to (voluntary) disclose 

the "ingredients", e.g. how data is collected and outputs are pro=
duced.

* We need to have a standard way (protocol) to represent each disclosure 
in human- and machine-readable formats, validate, verify and process 

them.

* Complex apps will involve chaining the disclosures for the components 
involved.





My motivation is to continue the discussion here and get feedback 

allowing us to iterate on the protocol. I'd like to bring this 

discussion to a relevant group or/and welcome the creation of the new 

one, also potentially bringing the conversation to the IETF meeting in 

Vienna.



Below are the links with more info

Article to bring the context, in plain English

https://lukia=
nets.medium.com/why-algorithmic-transparency-needs-a-protocol-2b6d5098572f<=
/a>



The IETF I-D

https://datatrack=
er.ietf.org/doc/draft-lukianets-open-ethics-transparency-protocol/



GitHub repo

https://github.com/OpenEthicsAI/OETP



Thanks a lot for your help and thoughts





Nikita Lukianets

Founder, CTO PocketConfidant

Founder Open Ethics initiative

Twitter: @nikiluk

https://fr.linkedin.com/in/nikiluk

Schedule a 30 min call: https://lukianets.com/meet/



_______________________________________________

Secdispatch mailing list

Secdispatch@ietf.=
org

https://www.ietf.org/mailman/listinfo/secdispatch




--00000000000072ff2d05da0e2c22--


From nobody Sun Mar 13 18:39:20 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61E663A1853 for ; Sun, 13 Mar 2022 18:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.995
X-Spam-Level: 
X-Spam-Status: No, score=-0.995 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 ih6fE9rWU7hC for ; Sun, 13 Mar 2022 18:38:46 -0700 (PDT)
Received: from resqmta-c1p-023462.sys.comcast.net (resqmta-c1p-023462.sys.comcast.net [IPv6:2001:558:fd00:56::2]) (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 C3AB13A18A8 for ; Sun, 13 Mar 2022 18:38:46 -0700 (PDT)
Received: from resomta-c1p-022589.sys.comcast.net ([96.102.18.236]) by resqmta-c1p-023462.sys.comcast.net with ESMTP id TZc1nTpDm0s9JTZfWniXI1; Mon, 14 Mar 2022 01:38:42 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1647221922; bh=ceZb4bYf6mTj2bVaKdtt6wiStJwPhcUQBbh5cQSx4Mo=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=KRpQ3yqy9NJ0uTB6zuTYUJ6+C3oyS0ZDp65L5VzsG0qV6dzMlIpJoMjB6JhiTaxSZ nKPwJKZTEqmtcjSKr4A9wQL1u8IGfchzm9Or+yLWUl82Kg0DmTG+y3KzUE1SlHsgZB eIQrokyM7gUmAsp9qPleZP9qUBrpxlk4SXAVT0dMZRDJMLHP0iDBmf7lFg+EybSgfe RzFcqmBFcXq2pVfHxdGUvGNjfC24MarXes41y2VQwMrHFOVZdpqmXoaBK1MNWvxJK2 /HJxjcXqzxU0ooK4lKKrmFW7AlAYGgZbE3jiWzhNogoxK+dt1OGvR+8b911LTMrF+r g/ol0CJ85cAgA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::c53a]) by resomta-c1p-022589.sys.comcast.net with ESMTPA id TZfTnF2I7GBB2TZfTnhrWx; Mon, 14 Mar 2022 01:38:42 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 22E1ccTK025748 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Sun, 13 Mar 2022 21:38:38 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 22E1cbqS025745; Sun, 13 Mar 2022 21:38:37 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: n.lukianets@openethics.ai
Cc: art@ietf.org, secdispatch@ietf.org, dispatch@ietf.org, hrpc@irtf.org
In-Reply-To: <6dac86b0eb3b96490dadffdc0f1d307a@openethics.ai> (n.lukianets@openethics.ai)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 13 Mar 2022 21:38:37 -0400
Message-ID: <87fsnlcnz6.fsf@hobgoblin.ariadne.com>
Archived-At: 
Subject: Re: [dispatch] [art] Open Ethics Transparency Protocol
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 14 Mar 2022 01:38:52 -0000

n.lukianets@openethics.ai writes:
> Nikita Lukianets from the Open Ethics initiative here.
>
> I've been working on the mechanisms to enable transparency for data 
> collection and data processing practices for autonomous systems and 
> specifically, those powered by machine learning models. Since 2020 I 
> have started to draft a guiding document to reflect ways disclosures 
> could be submitted, verified, and exchanged. Eventually, I would like to 
> see how this work could result in an open standard.

I have feelings which are similar to other respondents.  I phrase it
that the IETF is not the correct place for this work because the central
problem is at the application layer (and possibly above that, at the
political layer ... and certainly above that, at the cultural layer):
being transparent presupposes a suitable way to describe "data
collection and data processing practices" in "disclosures".

Once somebody defines a way to represent these disclosures as concrete
document objects, then there may be some protocol issues regarding how
to "submit, verify, and exchange" them.  But that still seems to be more
like the presentation layer, how you associate disclosure documents with
web sites etc. which they describe, which sounds like a W3C specialty.

Dale


From nobody Mon Mar 14 10:48:09 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50B043A0EAC; Mon, 14 Mar 2022 10:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level: 
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 7K_1yiZRLkjP; Mon, 14 Mar 2022 10:48:02 -0700 (PDT)
Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) (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 739DE3A0E9A; Mon, 14 Mar 2022 10:48:02 -0700 (PDT)
Received: by mail-ua1-x929.google.com with SMTP id 63so6938403uaw.10; Mon, 14 Mar 2022 10:48:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CZbukwNW/dFU1Voju35rVmSlGGkoXR5Wd45xreU5KXE=; b=TMq7RoC6hH1IW8xMKn3ZrihhUHYvxQCvD52ZmZ/o2B5LDRhLSyMJT4dzjigkAnQCcE z1bOsv3cNrQJfhQfiA0nDr8LwaCAvh2PBWas1KlUn0mi4sPOdAJikdWArcXokW5ES9Kp tqwBkWyaMHVfsUFw6rwJtGFmDuOj7ImDHi+IjQcXrEx1GNrmjyu64akMATvEqMJtQYUu 8LQldG0926cRnpjjsiMU4ZAuXQe0BZ2/qRA5boUBeWKgw8lI/cfVnQdj4ahh23cdFrsq b/1Rqn82do5rwGvVb3s/o0kYV6AEb6hCmrILmQyoqCs38MLr8GB6RC+TZvbzzs1jl4ne rYYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CZbukwNW/dFU1Voju35rVmSlGGkoXR5Wd45xreU5KXE=; b=WPleDuoF3RQMxRarbPbJwm70GZQy/igevNaIVclz0i2kNjCG7WekoIqy99UPl+AIb2 8Gh7V3WkNIc3/LblvXXbNAbCMEnbaIhKmb73OgB4BrPnk8746+dKiBcnpb4k6jZGYZ4t CycyrQu27OyzXjwP5pgtlrbyJ8WbS6cQRuep4IR3UDzzWW80iBWrvW3rXkaBj9QjEFP9 W/Y0fJS0yggwPsASXkClb2FOT+HiEh1C2crmVHXfFGponRrw5q4Y4K/4t4g9JtJvZkxG Mo0laqULuNHRK0aod1so9f3VR/A39aS5F6w42ySJVUQ5Jw+3wn0J87oZ/AbPp53w6jn2 Fdqg==
X-Gm-Message-State: AOAM53272QQ4PBbmIBGfBZpcA6vCY1o2A1CDU6HksgKcEpiV6WMxbgiz pPuEmBtPtvGWWfRXqnza+t3/UFo8/ADRIS5rx/rsEgIaTvc=
X-Google-Smtp-Source: ABdhPJxU6fMyDEVSV6+JNfxlvv3eeEnzicHlfFQyGNEs0oz13Pp8Edj7jb/ATeCSVTyOrdiYftcMjRjqEyaCXdW83NI=
X-Received: by 2002:ab0:6192:0:b0:34a:1607:b2fd with SMTP id h18-20020ab06192000000b0034a1607b2fdmr9356467uan.65.1647280081172; Mon, 14 Mar 2022 10:48:01 -0700 (PDT)
MIME-Version: 1.0
References: <6dac86b0eb3b96490dadffdc0f1d307a@openethics.ai> <87fsnlcnz6.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87fsnlcnz6.fsf@hobgoblin.ariadne.com>
From: Kathleen Moriarty 
Date: Mon, 14 Mar 2022 13:47:25 -0400
Message-ID: 
To: "Dale R. Worley" 
Cc: n.lukianets@openethics.ai, DISPATCH ,  "gen-art@ietf.org" , IETF SecDispatch , hrpc@irtf.org
Content-Type: multipart/alternative; boundary="000000000000157d6905da31483e"
Archived-At: 
Subject: Re: [dispatch] [Secdispatch] [art] Open Ethics Transparency Protocol
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 14 Mar 2022 17:48:08 -0000

--000000000000157d6905da31483e
Content-Type: text/plain; charset="UTF-8"

Greetings!

I agree with the prior assessment that this is similar to the Software Bill
of Materials work, at least in objectives. That is flexible in terms of
what formats will be acceptable (3) to provide a manifest on software and
many have selected SPDX, then it's digitally signed (code signing). There's
another proposal for this upcoming meeting that will link these for use in
supply chain assurance using Remote Attestation. It might be worth
reviewing that proposal to look for similarities in addition to reviewing
the document from the NTIA on the minimum set of elements for an SBOM.

There's a requirement in the US to any organization that sells to the
federal government to provide an SBOM related to the US executive order
from May 2021.  As such, there's traction on this approach already. With
that said, EKR also pointed out the proposal in this thread is at the
application layer. There may be a possibility for your work to use the
standards being adopted that could accelerate your progress. The next part
would be to determine if that work requires adoption and further
standardization or if the existing formats suffice for what needs to be
interoperable.

At this point, I don't see a time slot being useful, but please respond
with your thoughts if I'm missing something. I hope this is helpful.

Thank you,
Kathleen
co-chair of SecDispatch

On Sun, Mar 13, 2022 at 9:39 PM Dale R. Worley  wrote:

> n.lukianets@openethics.ai writes:
> > Nikita Lukianets from the Open Ethics initiative here.
> >
> > I've been working on the mechanisms to enable transparency for data
> > collection and data processing practices for autonomous systems and
> > specifically, those powered by machine learning models. Since 2020 I
> > have started to draft a guiding document to reflect ways disclosures
> > could be submitted, verified, and exchanged. Eventually, I would like to
> > see how this work could result in an open standard.
>
> I have feelings which are similar to other respondents.  I phrase it
> that the IETF is not the correct place for this work because the central
> problem is at the application layer (and possibly above that, at the
> political layer ... and certainly above that, at the cultural layer):
> being transparent presupposes a suitable way to describe "data
> collection and data processing practices" in "disclosures".
>
> Once somebody defines a way to represent these disclosures as concrete
> document objects, then there may be some protocol issues regarding how
> to "submit, verify, and exchange" them.  But that still seems to be more
> like the presentation layer, how you associate disclosure documents with
> web sites etc. which they describe, which sounds like a W3C specialty.
>
> Dale
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch
>


-- 

Best regards,
Kathleen

--000000000000157d6905da31483e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Greetings!

I agree with the prior asses=
sment that this is similar to the Software Bill of Materials work, at least=
 in objectives. That is flexible in terms of what formats will be acceptabl=
e (3) to provide a manifest on software and many have selected SPDX, then i=
t's digitally signed (code signing). There's another proposal for t=
his upcoming meeting that will link these for use in supply chain assurance=
 using Remote Attestation. It might be worth reviewing=C2=A0that proposal t=
o look for similarities in addition to reviewing the document from the NTIA=
 on the minimum=C2=A0set of elements for an SBOM.

=
There's a requirement in the US to any organization that sells to the f=
ederal government=C2=A0to provide an SBOM related to the US executive order=
 from May 2021.=C2=A0 As such, there's traction on this approach alread=
y. With that=C2=A0said, EKR also pointed out the proposal=C2=A0in this thre=
ad is at the application layer. There may be a possibility for your work to=
 use the standards being adopted that could accelerate your progress. The n=
ext part would be to determine if that work requires adoption and further s=
tandardization or if the existing formats suffice for what needs to be inte=
roperable.

At this point, I don't see a time s=
lot being useful, but please respond with your thoughts if I'm missing =
something. I hope this is helpful.

Thank you,
Kathleen
co-chair of SecDispatch

On Sun, Mar 13, 2022=
 at 9:39 PM Dale R. Worley <worley=
@ariadne.com> wrote:
=
n.lukianets@openethics.ai writes:

> Nikita Lukianets from the Open Ethics initiative here.

>

> I've been working on the mechanisms to enable transparency for dat=
a 

> collection and data processing practices for autonomous systems and 
> specifically, those powered by machine learning models. Since 2020 I <=
br>
> have started to draft a guiding document to reflect ways disclosures <=
br>
> could be submitted, verified, and exchanged. Eventually, I would like =
to 

> see how this work could result in an open standard.



I have feelings which are similar to other respondents.=C2=A0 I phrase it
that the IETF is not the correct place for this work because the central
problem is at the application layer (and possibly above that, at the

political layer ... and certainly above that, at the cultural layer):

being transparent presupposes a suitable way to describe "data

collection and data processing practices" in "disclosures".<=
br>


Once somebody defines a way to represent these disclosures as concrete

document objects, then there may be some protocol issues regarding how

to "submit, verify, and exchange" them.=C2=A0 But that still seem=
s to be more

like the presentation layer, how you associate disclosure documents with
web sites etc. which they describe, which sounds like a W3C specialty.



Dale



_______________________________________________

Secdispatch mailing list

Secdispatch@ietf.=
org

https://www.ietf.org/mailman/listinfo/secdispatch




-- 

Best regards,
Kathleen


--000000000000157d6905da31483e--


From nobody Mon Mar 14 11:19:57 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AEE63A1C9B; Mon, 14 Mar 2022 11:19:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.964
X-Spam-Level: 
X-Spam-Status: No, score=-0.964 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=openethics.ai
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 z9bxlZNNfcmC; Mon, 14 Mar 2022 11:19:31 -0700 (PDT)
Received: from nlskm21.hostsila.org (nlskm21.hostsila.org [88.218.28.6]) (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 CEC143A152F; Mon, 14 Mar 2022 11:18:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=openethics.ai; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Cc:To:From:In-Reply-To:Message-ID:Subject:Date:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:References:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=QKAciHHkTAj08qu+SqKhgG/IbKKsy1a3i4o/4jb1PjE=; b=Fq4mRElRf+EnPB4M+Ak/bctlTf LJRWDGAVXXm0lDqh6jwy2U5BiMHDfhxxFxtziK5KW4381ze+Lb2GTabDITT/gbD+fnt9qm/rDppz9 3uMv2CyXH7H+pEXC7CPyiKhcTzUBHKgjXfCVOWIJRlM0cnf73OaCVrMfurbOBmhoEuNqEUsFCGp0P 7gnDYXSAmj3DDsypFp5fZeD/9COWH8UdsCFLUaEaX4yiXvPno6zPUTIl8My+OjCS8HaWD35qpZNbn 79Pay1C+xFRDt6ESPwMz1S7cVw9zBzgjTGdqNCSfv5iq7894/uS0b92/9S1D4JQ7Vi3lR9JChYfq5 mEz9zTzQ==;
Received: from [193.93.216.247] (port=41316 helo=[192.168.0.112]) by nlskm21.hostsila.org with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1nTpGm-005zDH-7P; Mon, 14 Mar 2022 20:18:10 +0200
Date: Mon, 14 Mar 2022 20:18:09 +0200
Message-ID: <6e01731e-1473-4240-843a-5d6b365f1012@email.android.com>
X-Android-Message-ID: <6e01731e-1473-4240-843a-5d6b365f1012@email.android.com>
In-Reply-To: 
From: Nikita Lukianets 
To: Kathleen Moriarty 
Cc: "Dale R. Worley" , DISPATCH , "gen-art@ietf.org" , IETF SecDispatch , hrpc@irtf.org, Nikita Lukianets 
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-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - nlskm21.hostsila.org
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - openethics.ai
X-Get-Message-Sender-Via: nlskm21.hostsila.org: authenticated_id: n.lukianets@openethics.ai
X-Authenticated-Sender: nlskm21.hostsila.org: n.lukianets@openethics.ai
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: 
Subject: Re: [dispatch] [Secdispatch] [art] Open Ethics Transparency Protocol
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 14 Mar 2022 18:19:44 -0000

PGRpdiBkaXI9J2F1dG8nPkhpIGV2ZXJ5b25lLDxkaXYgZGlyPSJhdXRvIj5SZWxhdGVkIHRvIHRo
ZSBkaXNjbG9zdXJlIGZvcm1hdHMsIHdlIGFyZSBhZG9wdGluZyBNb2RlbCBDYXJkcyBhbmQgRGF0
YSBTaGVldHMgdG8gYSBzaW1wbGUgSlNPTiBmaWxlIGhpZXJhcmNoeSB3aGljaCBjb3VsZCBiZSBw
YXJzZWQgYW5kIGNoZWNrZWQgYW5kIGV4dGVuZGVkIHVzaW5nIGFueSBwcm9ncmFtbWluZyBsYW5n
dWFnZS4mbmJzcDs8YnI+PC9kaXY+PGRpdiBkaXI9ImF1dG8iPjxicj48L2Rpdj48ZGl2IGRpcj0i
YXV0byI+VGhlIGNvcmUgaWRlYSBiZWhpbmQgaXMgbWFraW5nIG1hY2hpbmUtcmVhZGFibGUgYW5k
IGh1bWFuLXJlYWRhYmxlIGxhYmVscyBpbnRlcm9wZXJhYmxlIGFuZCB0cnVzdGVkIHRoYW5rcyB0
byBhIGNoYWluZWQgdmFsaWRhdGlvbiBwcm9jZXNzLiBTaW1wbGUgdmlzdWFsIGV4YW1wbGUgZm9y
IGl0IGV4aXN0cyBpbiBjcmVhdGl2ZSBjb21tb25zIGdlbmVyYXRvcnMgdGhvdWdoIGhhcyBubyBt
YWNoaW5lLXJlYWRhYmxlIGNvbXBvbmVudC4mbmJzcDs8L2Rpdj48ZGl2IGRpcj0iYXV0byI+PGJy
PjwvZGl2PjxkaXYgZGlyPSJhdXRvIj5JIGFwb2xvZ2l6ZSBmb3Igbm90IHJlc3BvbmRpbmcgdG8g
dGhlIGNvbW1lbnRzLiBTb21lIG9mIHlvdSBtYXkga25vdyB0aGF0IEknbSBjdXJyZW50bHkgaW4g
VWtyYWluZSBhbmQgdGhpbmdzIGFyZSwgaG93IGNvdWxkIEkgc2F5IGl0Li4uICJjb21wbGV4Ii4g
SSBkb24ndCBoYXZlIHJlbGlhYmxlIGludGVybmV0IGNvbm5lY3Rpb24gdGhlc2UgbGFzdCBkYXlz
LCBlc3BlY2lhbGx5IHdoZW4gd2UgaGF2ZSB0byBzdGF5IGF0IHRoZSBib21iIHNoZWx0ZXJzLiZu
YnNwOzxicj48L2Rpdj48ZGl2IGRpcj0iYXV0byI+PGJyPjwvZGl2PjxkaXYgZGlyPSJhdXRvIj5J
bmRlZWQsIEFwcGxpY2F0aW9uIGxheWVyIHNlZW1zIG1vc3QgdmlhYmxlIG9wdGlvbiBoZXJlIGFu
ZCBJIGhvcGUgdGhvc2UgaW50ZXJlc3RlZCBjb3VsZCBqb2luIHRoZSBzZXNzaW9uIGluIGFydC1k
aXNwYXRjaCwgd2hpbGUgSSdsbCB0cnkgdG8gbWFrZSBzdXJlIEkgYWRkcmVzcyBwcmV2aW91c2x5
IG1lbnRpb25lZCBjb21tZW50cywgZXNwZWNpYWxseSB0aG9zZSByZWxhdGVkIHRvIGltcGxlbWVu
dGF0aW9uIGFuZCBleGFtcGxlcy4mbmJzcDs8L2Rpdj48ZGl2IGRpcj0iYXV0byI+PGJyPjwvZGl2
PjxkaXYgZGlyPSJhdXRvIj5CZXN0LCZuYnNwOzwvZGl2PjxkaXYgZGlyPSJhdXRvIj5OaWtpdGEg
THVraWFuZXRzJm5ic3A7PC9kaXY+PGRpdiBkaXI9ImF1dG8iPjxicj48L2Rpdj48ZGl2IGRpcj0i
YXV0byI+PGJyPjwvZGl2PjxkaXYgZGlyPSJhdXRvIj48YnI+PC9kaXY+PGJyPjxkaXYgY2xhc3M9
ImdtYWlsX2V4dHJhIiBkaXI9ImF1dG8iPjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+T24g
TWFyIDE0LCAyMDIyIDE5OjQ3LCBLYXRobGVlbiBNb3JpYXJ0eSAmbHQ7a2F0aGxlZW4ubW9yaWFy
dHkuaWV0ZkBnbWFpbC5jb20mZ3Q7IHdyb3RlOjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+PGJsb2Nr
cXVvdGUgY2xhc3M9InF1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6
MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+PGRpdiBkaXI9Imx0ciI+R3JlZXRpbmdz
ITxkaXY+PGJyPjwvZGl2PjxkaXY+SSBhZ3JlZSB3aXRoIHRoZSBwcmlvciBhc3Nlc3NtZW50IHRo
YXQgdGhpcyBpcyBzaW1pbGFyIHRvIHRoZSBTb2Z0d2FyZSBCaWxsIG9mIE1hdGVyaWFscyB3b3Jr
LCBhdCBsZWFzdCBpbiBvYmplY3RpdmVzLiBUaGF0IGlzIGZsZXhpYmxlIGluIHRlcm1zIG9mIHdo
YXQgZm9ybWF0cyB3aWxsIGJlIGFjY2VwdGFibGUgKDMpIHRvIHByb3ZpZGUgYSBtYW5pZmVzdCBv
biBzb2Z0d2FyZSBhbmQgbWFueSBoYXZlIHNlbGVjdGVkIFNQRFgsIHRoZW4gaXQncyBkaWdpdGFs
bHkgc2lnbmVkIChjb2RlIHNpZ25pbmcpLiBUaGVyZSdzIGFub3RoZXIgcHJvcG9zYWwgZm9yIHRo
aXMgdXBjb21pbmcgbWVldGluZyB0aGF0IHdpbGwgbGluayB0aGVzZSBmb3IgdXNlIGluIHN1cHBs
eSBjaGFpbiBhc3N1cmFuY2UgdXNpbmcgUmVtb3RlIEF0dGVzdGF0aW9uLiBJdCBtaWdodCBiZSB3
b3J0aCByZXZpZXdpbmcmbmJzcDt0aGF0IHByb3Bvc2FsIHRvIGxvb2sgZm9yIHNpbWlsYXJpdGll
cyBpbiBhZGRpdGlvbiB0byByZXZpZXdpbmcgdGhlIGRvY3VtZW50IGZyb20gdGhlIE5USUEgb24g
dGhlIG1pbmltdW0mbmJzcDtzZXQgb2YgZWxlbWVudHMgZm9yIGFuIFNCT00uPC9kaXY+PGRpdj48
YnI+PC9kaXY+PGRpdj5UaGVyZSdzIGEgcmVxdWlyZW1lbnQgaW4gdGhlIFVTIHRvIGFueSBvcmdh
bml6YXRpb24gdGhhdCBzZWxscyB0byB0aGUgZmVkZXJhbCBnb3Zlcm5tZW50Jm5ic3A7dG8gcHJv
dmlkZSBhbiBTQk9NIHJlbGF0ZWQgdG8gdGhlIFVTIGV4ZWN1dGl2ZSBvcmRlciBmcm9tIE1heSAy
MDIxLiZuYnNwOyBBcyBzdWNoLCB0aGVyZSdzIHRyYWN0aW9uIG9uIHRoaXMgYXBwcm9hY2ggYWxy
ZWFkeS4gV2l0aCB0aGF0Jm5ic3A7c2FpZCwgRUtSIGFsc28gcG9pbnRlZCBvdXQgdGhlIHByb3Bv
c2FsJm5ic3A7aW4gdGhpcyB0aHJlYWQgaXMgYXQgdGhlIGFwcGxpY2F0aW9uIGxheWVyLiBUaGVy
ZSBtYXkgYmUgYSBwb3NzaWJpbGl0eSBmb3IgeW91ciB3b3JrIHRvIHVzZSB0aGUgc3RhbmRhcmRz
IGJlaW5nIGFkb3B0ZWQgdGhhdCBjb3VsZCBhY2NlbGVyYXRlIHlvdXIgcHJvZ3Jlc3MuIFRoZSBu
ZXh0IHBhcnQgd291bGQgYmUgdG8gZGV0ZXJtaW5lIGlmIHRoYXQgd29yayByZXF1aXJlcyBhZG9w
dGlvbiBhbmQgZnVydGhlciBzdGFuZGFyZGl6YXRpb24gb3IgaWYgdGhlIGV4aXN0aW5nIGZvcm1h
dHMgc3VmZmljZSBmb3Igd2hhdCBuZWVkcyB0byBiZSBpbnRlcm9wZXJhYmxlLjwvZGl2PjxkaXY+
PGJyPjwvZGl2PjxkaXY+QXQgdGhpcyBwb2ludCwgSSBkb24ndCBzZWUgYSB0aW1lIHNsb3QgYmVp
bmcgdXNlZnVsLCBidXQgcGxlYXNlIHJlc3BvbmQgd2l0aCB5b3VyIHRob3VnaHRzIGlmIEknbSBt
aXNzaW5nIHNvbWV0aGluZy4gSSBob3BlIHRoaXMgaXMgaGVscGZ1bC48L2Rpdj48ZGl2Pjxicj48
L2Rpdj48ZGl2PlRoYW5rIHlvdSw8L2Rpdj48ZGl2PkthdGhsZWVuPC9kaXY+PGRpdj5jby1jaGFp
ciBvZiBTZWNEaXNwYXRjaDwvZGl2PjwvZGl2Pjxicj48ZGl2IGNsYXNzPSJlbGlkZWQtdGV4dCI+
PGRpdiBkaXI9Imx0ciI+T24gU3VuLCBNYXIgMTMsIDIwMjIgYXQgOTozOSBQTSBEYWxlIFIuIFdv
cmxleSAmbHQ7PGEgaHJlZj0ibWFpbHRvOndvcmxleUBhcmlhZG5lLmNvbSI+d29ybGV5QGFyaWFk
bmUuY29tPC9hPiZndDsgd3JvdGU6PGJyPjwvZGl2PjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW46
MHB4IDBweCAwcHggMC44ZXg7Ym9yZGVyLWxlZnQ6MXB4IHNvbGlkIHJnYiggMjA0ICwgMjA0ICwg
MjA0ICk7cGFkZGluZy1sZWZ0OjFleCI+PGEgaHJlZj0ibWFpbHRvOm4ubHVraWFuZXRzQG9wZW5l
dGhpY3MuYWkiPm4ubHVraWFuZXRzQG9wZW5ldGhpY3MuYWk8L2E+IHdyaXRlczo8YnI+CiZndDsg
TmlraXRhIEx1a2lhbmV0cyBmcm9tIHRoZSBPcGVuIEV0aGljcyBpbml0aWF0aXZlIGhlcmUuPGJy
PgomZ3Q7PGJyPgomZ3Q7IEkndmUgYmVlbiB3b3JraW5nIG9uIHRoZSBtZWNoYW5pc21zIHRvIGVu
YWJsZSB0cmFuc3BhcmVuY3kgZm9yIGRhdGEgPGJyPgomZ3Q7IGNvbGxlY3Rpb24gYW5kIGRhdGEg
cHJvY2Vzc2luZyBwcmFjdGljZXMgZm9yIGF1dG9ub21vdXMgc3lzdGVtcyBhbmQgPGJyPgomZ3Q7
IHNwZWNpZmljYWxseSwgdGhvc2UgcG93ZXJlZCBieSBtYWNoaW5lIGxlYXJuaW5nIG1vZGVscy4g
U2luY2UgMjAyMCBJIDxicj4KJmd0OyBoYXZlIHN0YXJ0ZWQgdG8gZHJhZnQgYSBndWlkaW5nIGRv
Y3VtZW50IHRvIHJlZmxlY3Qgd2F5cyBkaXNjbG9zdXJlcyA8YnI+CiZndDsgY291bGQgYmUgc3Vi
bWl0dGVkLCB2ZXJpZmllZCwgYW5kIGV4Y2hhbmdlZC4gRXZlbnR1YWxseSwgSSB3b3VsZCBsaWtl
IHRvIDxicj4KJmd0OyBzZWUgaG93IHRoaXMgd29yayBjb3VsZCByZXN1bHQgaW4gYW4gb3BlbiBz
dGFuZGFyZC48YnI+Cjxicj4KSSBoYXZlIGZlZWxpbmdzIHdoaWNoIGFyZSBzaW1pbGFyIHRvIG90
aGVyIHJlc3BvbmRlbnRzLiZuYnNwOyBJIHBocmFzZSBpdDxicj4KdGhhdCB0aGUgSUVURiBpcyBu
b3QgdGhlIGNvcnJlY3QgcGxhY2UgZm9yIHRoaXMgd29yayBiZWNhdXNlIHRoZSBjZW50cmFsPGJy
Pgpwcm9ibGVtIGlzIGF0IHRoZSBhcHBsaWNhdGlvbiBsYXllciAoYW5kIHBvc3NpYmx5IGFib3Zl
IHRoYXQsIGF0IHRoZTxicj4KcG9saXRpY2FsIGxheWVyIC4uLiBhbmQgY2VydGFpbmx5IGFib3Zl
IHRoYXQsIGF0IHRoZSBjdWx0dXJhbCBsYXllcik6PGJyPgpiZWluZyB0cmFuc3BhcmVudCBwcmVz
dXBwb3NlcyBhIHN1aXRhYmxlIHdheSB0byBkZXNjcmliZSAiZGF0YTxicj4KY29sbGVjdGlvbiBh
bmQgZGF0YSBwcm9jZXNzaW5nIHByYWN0aWNlcyIgaW4gImRpc2Nsb3N1cmVzIi48YnI+Cjxicj4K
T25jZSBzb21lYm9keSBkZWZpbmVzIGEgd2F5IHRvIHJlcHJlc2VudCB0aGVzZSBkaXNjbG9zdXJl
cyBhcyBjb25jcmV0ZTxicj4KZG9jdW1lbnQgb2JqZWN0cywgdGhlbiB0aGVyZSBtYXkgYmUgc29t
ZSBwcm90b2NvbCBpc3N1ZXMgcmVnYXJkaW5nIGhvdzxicj4KdG8gInN1Ym1pdCwgdmVyaWZ5LCBh
bmQgZXhjaGFuZ2UiIHRoZW0uJm5ic3A7IEJ1dCB0aGF0IHN0aWxsIHNlZW1zIHRvIGJlIG1vcmU8
YnI+Cmxpa2UgdGhlIHByZXNlbnRhdGlvbiBsYXllciwgaG93IHlvdSBhc3NvY2lhdGUgZGlzY2xv
c3VyZSBkb2N1bWVudHMgd2l0aDxicj4Kd2ViIHNpdGVzIGV0Yy4gd2hpY2ggdGhleSBkZXNjcmli
ZSwgd2hpY2ggc291bmRzIGxpa2UgYSBXM0Mgc3BlY2lhbHR5Ljxicj4KPGJyPgpEYWxlPGJyPgo8
YnI+Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPgpT
ZWNkaXNwYXRjaCBtYWlsaW5nIGxpc3Q8YnI+CjxhIGhyZWY9Im1haWx0bzpTZWNkaXNwYXRjaEBp
ZXRmLm9yZyI+U2VjZGlzcGF0Y2hAaWV0Zi5vcmc8L2E+PGJyPgo8YSBocmVmPSJodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NlY2Rpc3BhdGNoIj5odHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NlY2Rpc3BhdGNoPC9hPjxicj4KPC9ibG9ja3F1b3RlPjwv
ZGl2PjxiciBjbGVhcj0iYWxsIj48ZGl2Pjxicj48L2Rpdj4tLSA8YnI+PGRpdiBkaXI9Imx0ciI+
PGRpdiBkaXI9Imx0ciI+PGJyPjxkaXY+QmVzdCByZWdhcmRzLDwvZGl2PjxkaXY+S2F0aGxlZW48
L2Rpdj48L2Rpdj48L2Rpdj4KPC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48L2Rpdj48L2Rpdj4=


From nobody Wed Mar 16 08:14:41 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 706453A18FF; Wed, 16 Mar 2022 08:13:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 ptgPwTyPVhls; Wed, 16 Mar 2022 08:13:32 -0700 (PDT)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on20626.outbound.protection.outlook.com [IPv6:2a01:111:f400:7d00::626]) (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 684E03A08CF; Wed, 16 Mar 2022 08:13:30 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ANo+gw/lfotT9wVKwQD589g7SMj4rjVD46tr+KAEhs93vIL+cvW7HVhn1JRbfesrpD7xMulLpTrcHm9UrboRfoydw2xBNdGMzRblZi41VaSr7qdKqttb+4CY5FLxGy0iYyX7Wlo49xlUgI79bZlp6CnRgUEjqfFWZ4mEe31mf1Wt9+XyxyYsCcTGgcPb4i0x/Kx4pA1z3D4JpWYioU2L4mwPIm6UI4H8MaLOtTkG9+6L8cNgsJy6yORQUl84mesZeP3I6x46cykuYDYbI6QCT+PhaVAEet/IQdHun582bpQmlcsgYRxJdMtF3g7b6yXsFFxOXMToJJhIHt3CADReXA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=l+aipP0WiJi3JZbtIB/DRAv1S7YFVYfnt1Bc5PjQcT8=; b=AhoUKzxZVIPUYQTclHxWn5Lwjb/yTnRc4MPxzg86GAIC8Pkyjh+h6NeTKk3WNz/vTZ9Wx2m28VWG/oPIDWJtKd+zLQAPJHBAurwqv4iVKCDglk7aUnzZY+jEv51DP1uBsHldDwiNwhES4yNPtwaGjaQ1YiRqf7Q5BNKqWISqAJQeI905r7TyHvoHIXxw70XlTIbo4XOTCbwbW3FxZCYux7FnvQtwm6THqpWJLWPtTxn4PBUderXxmcSOnpy/HDtsngKbwdlaa08X8eda9dh76BzKX3UnlBlZZSzOYKn1kapknuHNI06ebQzYm+QOLnoy2ajMzBiZEhJGLwijYQ+pkQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=l+aipP0WiJi3JZbtIB/DRAv1S7YFVYfnt1Bc5PjQcT8=; b=MyrM686+07LuNVmeA05wiTLd/UzIPxNh+gLYTbiws0YeXeC8jb+s5M3JwLdOkwQEoO2JshVVVFbgrMfgQwAHMEKo9B/LKVhzYWfUGJhjzY6vMue2xHRrR+efwxQhogXcD9Ihfd09NPJDuMSMcxPYkc4azLbyJbWqU9ZUjbG3XdY=
Received: from HE1PR07MB4217.eurprd07.prod.outlook.com (2603:10a6:7:96::33) by AM5PR0701MB2836.eurprd07.prod.outlook.com (2603:10a6:203:46::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5081.15; Wed, 16 Mar 2022 15:13:22 +0000
Received: from HE1PR07MB4217.eurprd07.prod.outlook.com ([fe80::a10e:4f8d:2a7f:ffac]) by HE1PR07MB4217.eurprd07.prod.outlook.com ([fe80::a10e:4f8d:2a7f:ffac%5]) with mapi id 15.20.5081.014; Wed, 16 Mar 2022 15:13:22 +0000
From: Francesca Palombini 
To: "art@ietf.org" 
CC: "dispatch@ietf.org" , "media-types@ietf.org" 
Thread-Topic: Interested in chairing a WG?
Thread-Index: AQHYOUOmaW3AQJ60B0qrfQzQxL5+0g==
Date: Wed, 16 Mar 2022 15:13:22 +0000
Message-ID: 
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 323aaeef-6807-4773-a3ce-08da075f82f7
x-ms-traffictypediagnostic: AM5PR0701MB2836:EE_
x-microsoft-antispam-prvs: 
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: eomoTo/lxpZyefckix6nTE9rX7Cb6fFsyWNPavp+TYhX9BhR8Bbn64zCHL5eRHAxufEF+IWnllSv4quPM1rIktHDMycfGOOMKkvNBXtvJ3++3LTLB9JGUnsgCZhWMMhR+3yt8DGHLSQxnzqnQmf7xuwmqxP6fX3/cQYUkKz51UfzOUVFY7/k+apdnsMeboaTCvp9P7OqC8gyNEwzb5ZoEeHtoHQNbhj8Txz1iI60ZWTpR1lmR6z++ET234A2HM3dgQjF0fVx6u3JKhEbZv6XHmil2m8WtfyAtjQe5SAH9hN1nO5cgfwAaHbFnuhlbptxj5hr2Rj/Q0UNAJSv4Wq35gu092SFUBLx7StqO6javd0w+67qzFItEzZCfmxwPy9Bm7J90U0zGbl89hwajUEYm5Zljs1l8ltK2WXqju72rJd4azlC7gfQ+qYQAszfIanebpYnombsasrFleFwYLtDP+N1GV8sc0LMii9lQngCbXTJldif+Ur+RK6kILFR62U+gHDFNwb9DEkWQ4cUpjdo7Ub29A6PvMzWSUnT+PjaxaPmJcDVxRQLppEZQKJDPnO8DYbW/7nhypJT4fZXaLBIUFWOz7eFWY+xI6C9YUT5KQg3kMOlkn+ypfKIWL2rLUCc6bBvZO/hezpziXJ/EZY7HwPUx22Sk7mMDoP91LhLysf1BftxSlZAA+zGVTUa4OWbd1Hg3bBxHYLds8q6kcoml2JP5D7iv9ySvlwEazbBO8U=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB4217.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(13230001)(4636009)(366004)(82960400001)(122000001)(5660300002)(7696005)(6506007)(44832011)(86362001)(2906002)(38100700002)(9686003)(83380400001)(38070700005)(55016003)(186003)(33656002)(66446008)(76116006)(64756008)(8676002)(66476007)(66556008)(66946007)(4326008)(508600001)(450100002)(91956017)(6916009)(8936002)(54906003)(71200400001)(316002)(52536014)(95394004); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?G2LtuEIFCnB249Gukp27d2HlumXW689SMYR6rDYQkFftZYPNf7q6nUHPcFC6?= =?us-ascii?Q?lfqhmHf/buXRw2GM9X/bC5t2GnHgvxZAUJ6Zqgq1eDl+zFo8jK5Q7KoqEFTp?= =?us-ascii?Q?wDdtnj0I4n+ceprLXdhtxJtpN4azTlBSsuvj+53JvSk6x/JqfbrJ3tXSQj6F?= =?us-ascii?Q?Q1lK6ieKdFHOdS5NeKH46pdAXaGxh0Lc+ccBHxK8ebDmUZt77WmprTqzfXxJ?= =?us-ascii?Q?glqNWzI6zBPpBr8JH2T0LEJTUKlDfEbIdB4Uyf9pLfyEbA7M4nBMromzYWHM?= =?us-ascii?Q?IVQ/jStJdDcDT+Che4FeLoZTfM7uqo7tJLTn6R46yvcAr5CQ8QHnypA5cfRe?= =?us-ascii?Q?Vdlaz+JbZ0S5AKPDe7Fk522lgq04hmsE4cfgtfxt0nDtgiPmOv8iteGyYrGp?= =?us-ascii?Q?0ixH6maQJ8vlDOR/58YdMnvHnYlIOMwzp92W+fcqORGIdTLH6j1M23d3sFcw?= =?us-ascii?Q?zrotSJh93MoZqWQMjTbpmE3vI6YEgOBlwRdptBT4fq1LTXAX83TUEoYGKN1w?= =?us-ascii?Q?t/fflazKWCSuMaaH5cSC8nKa7gqTVWPA1nY/6TpkWYCqV33PmSTK8Z++l9Gu?= =?us-ascii?Q?S2E2GKBh2zHMpjmOV3SnxopkcEcrOAmYx7n4FHcJ5BreFgIXYPJ/Vvu/nZxL?= =?us-ascii?Q?5dRrcr8AGNgka1zxGkqPDy6wDTZeEvG4+6Jlg+oSJhtLNS3NELitADSSvbaH?= =?us-ascii?Q?tDx6iER/ucH2DbxHKpO9rzx9vYy3kl8j9lxFUXyT65gP05AiXGfehxmtRkNG?= =?us-ascii?Q?nZtmeyerwOidAWi8iLjkFra50vX1ZYBcspmVF0lejhf7Ct17XZIp10hNMioY?= =?us-ascii?Q?+F2Szy7gv3rRThyyrX7wnA+rQ1gSS8J5GWaQMZaVAo+3RHrxFEzTSL0Q19sC?= =?us-ascii?Q?aQ/TFixA9iijUf6vyqFcmwtD/iHwlK26UH9q49eF9XiNeiF3E78vhyAIDcC+?= =?us-ascii?Q?/DW1Qr23IigRinjBHezvdwzFApP2PslkeoQmIwgLS2zwHFyGm1nZT06Qbmvn?= =?us-ascii?Q?bP240RluQerD1IT/Omw1LgmVG6HL1s4TyXBKoFY/ATctTgzbFVH8JtkHhJWI?= =?us-ascii?Q?PrCBwGfilQSCyEHjsXrDkh2NEP7at6rC8Kf9/qaYLgG5lnHJQLT86jgLNQj5?= =?us-ascii?Q?20YevalgV/xPC0v3f5Aj9/MIYgXUS9mwg7Es8lBwATF6ziovVgiN1H8eo8Nv?= =?us-ascii?Q?QPUyOnwf+tmVriggvBgt283aGWs4rPvKrojonAhD/OKZ6MyhoK3KBHaz7IGU?= =?us-ascii?Q?vXfG/Y1cLAiHl4GgyR3Ri5A4IrFb5r7gxF2KsZbPIzid49QeKG8WO3Nc9xU0?= =?us-ascii?Q?KRik0p/DxX6TNgL+XHzm6V/5GDTSG4ttpBVnKmizBZUvpluZw02V0lMWaSkR?= =?us-ascii?Q?4MjSkhPbN2osLhNbCIQU6RBULD26V+29CT21TMSjnXYcTrpKlFj8FjX5Xsfg?= =?us-ascii?Q?AD5calIgOm0i2vTlgPn0iwWXKSk68Nm8y/ntu8oOZQ/qGqTBoJ68rPUjr+Io?= =?us-ascii?Q?nYYUNILAd025bjJzH/ZUHYtB2L40dpNq3hWpXywkUNt4FWQqMQxoMGUHC8Ac?= =?us-ascii?Q?R1D9EuNyKAl7smtfAlONe4JIU/rofz7268UfllF3?=
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB42173501878C422B41A46DAD98119HE1PR07MB4217eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB4217.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 323aaeef-6807-4773-a3ce-08da075f82f7
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Mar 2022 15:13:22.1589 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: KJ7lDb26Ch4oy1bXTufwoPaH9Jzap3gjnc1Fi9FCxws2DYkVdBB51MI/qU2SkEaXDno2k4zB5d4WTc8aE/9mWvFb0doIe7hzqJKTg05JCtGoxY3IUYexKxyRm8bKH+cK
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2836
Archived-At: 
Subject: [dispatch] Interested in chairing a WG?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 16 Mar 2022 15:13:43 -0000

--_000_HE1PR07MB42173501878C422B41A46DAD98119HE1PR07MB4217eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

The IETF functions best when there is a robust and diverse pipeline of cand=
idates in WG leadership positions. Murray and I would like to grow the pool=
 of candidates to select from when any WG chair positions in the Applicatio=
ns and Real-Time (ART) area need to be filled, and we are also actively loo=
king for people to fill in existing open positions. WGs that need chairs at=
 the moment or in the close future are Mediaman and Dispatch. Additionally,=
 if you have interest in both ART and security topics, do reach out as we o=
ften have working groups that are cross-area.

If you are interested in chairing, or know someone who would be interested =
in chairing, or even know someone who is not chairing but would be a good f=
it for the role, please email us privately.  Chairs with no prior experienc=
e are great, as we often pair experienced chairs with those new to the role=
. If you have any questions about the role, the process, or anything else, =
please reach out.

Chairs, feel free to forward this mail to your working groups.

Thanks, and looking forward to talking to you.
Francesca

--_000_HE1PR07MB42173501878C422B41A46DAD98119HE1PR07MB4217eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable











Hi all,<=
/span>


 


The IETF functions =
best when there is a robust and diverse pipeline of candidates in WG leader=
ship positions. Murray and I would like to grow the pool of candidates to s=
elect from when any WG chair positions
 in the Applications and Real-Time (ART) area need to be filled, and we are=
 also actively looking for people to fill in existing open positions. WGs t=
hat need chairs at the moment or in the close future are Mediaman and Dispa=
tch. Additionally, if you have interest
 in both ART and security topics, do reach out as we often have working gro=
ups that are cross-area.


 


If you are interest=
ed in chairing, or know someone who would be interested in chairing, or eve=
n know someone who is not chairing but would be a good fit for the role, pl=
ease email us privately.  Chairs with
 no prior experience are great, as we often pair experienced chairs with th=
ose new to the role. If you have any questions about the role, the process,=
 or anything else, please reach out.


 


Chairs, feel free t=
o forward this mail to your working groups.


 


Thanks, and looking=
 forward to talking to you.


Francesca






--_000_HE1PR07MB42173501878C422B41A46DAD98119HE1PR07MB4217eurp_--


From nobody Sun Mar 20 12:36:44 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 666913A08F5 for ; Sun, 20 Mar 2022 12:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level: 
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 L4m9d6v0VbHW for ; Sun, 20 Mar 2022 12:36:35 -0700 (PDT)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 6C6913A08FF for ; Sun, 20 Mar 2022 12:36:35 -0700 (PDT)
Received: by mail-pg1-x52e.google.com with SMTP id o8so8894843pgf.9 for ; Sun, 20 Mar 2022 12:36:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=iktOUTCJKJhrxtuzH97IK4PcqWompRJ7XrZRT8su6nY=; b=nJ58YLTkwB9IzGqK5LNxsXs04l4XihnoBKPy1o790z0x4+hQG+XLTWXBq5pz9ZY1MH zfMt/UvTPJdE7We1MTC5PHJLgkw6q+6i0rtQ5fL7iOaevX9/pUiDQy2KXkiQ9p6Rwt05 4C+AZ4gN36sDLPHc0TFDHTSRwrimRkV4MSMStcW7XOWSRT8negQq05qrkvPl8uFivGzd eto4ixFAsOn9UaKCoylS1tHLbI9OX/kiWTgr5Qhf5X2je7sA80ASVj7ZIJZAhj0HnimB ImfNkt5sMjUWY47AFtKete6YxNX85yPjYPhH4DAH5Cr5M+PcSDEOruNtAZJhoi3VlH76 ZLLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iktOUTCJKJhrxtuzH97IK4PcqWompRJ7XrZRT8su6nY=; b=RH9Gz7efwj1OmHXOHfkJ22iN8DFF/4zLSXxlJ/6O2hz/Zx6Mh3cvYvLJQZZsC1cYKK ITAEA93qwTLv72Avdhll1m+epMaUvkewJ5kYWhMY/5HBnBQ7JW2iFO/SlACT9nJHUxo2 U8iT779zm7zHRx83QjyKMkjUYzD3n8ylYuIco7+fg5v5UI86gughkYt/NepcagJqll0m ZxdPXxDm2Lg9Vxlpp9CpF+UZ0AVVhos1FyYVBO3bHtP7JMS2VG0bYF/hVx6y1ciNm62X +CJldKEYHlUhyriZhbzKqGVztQuYYvUsB1k7K5OLzXnYEm4NVuTLi/d0pxvUqkPoE8bU sm5Q==
X-Gm-Message-State: AOAM532oIGepdkIh4Etr36+B/CMzVgxN37XIP+T2VjUB92YQ6mgOvnXC vjRF1l+5D2jo42wBzCpJUQ6Y009RAgW79A==
X-Google-Smtp-Source: ABdhPJwc6UgkgjnPlGc3KeLS0q4wvTbNDaTXbFQOGdC0171mpn/BKMHKjcGQDpbcYLVUM6/2WYyZBw==
X-Received: by 2002:a05:6a00:1501:b0:4f7:5773:f3f6 with SMTP id q1-20020a056a00150100b004f75773f3f6mr20692068pfu.31.1647804994221;  Sun, 20 Mar 2022 12:36:34 -0700 (PDT)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id j7-20020a17090a31c700b001c6dbb70c94sm4864519pjf.18.2022.03.20.12.36.32 for  (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 20 Mar 2022 12:36:33 -0700 (PDT)
References: <164777505469.16668.4298414376334371664@ietfa.amsl.com>
To: dispatch@ietf.org
From: Brian E Carpenter 
X-Forwarded-Message-Id: <164777505469.16668.4298414376334371664@ietfa.amsl.com>
Message-ID: <7358e2fc-3adf-6b75-405f-9b97d8981659@gmail.com>
Date: Mon, 21 Mar 2022 08:36:29 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <164777505469.16668.4298414376334371664@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: 
Subject: [dispatch] Fwd: I-D Action: draft-ietf-6man-rfc6874bis-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sun, 20 Mar 2022 19:36:41 -0000

FYI, 6MAN has now adopted this draft. There's also a simplification of the
security considerations, following a perceptive comment by Ted Hardie.

As a reminder, we are not asking for action by DISPATCH, but of course
we'd welcome feedback.

Regards
    Brian Carpenter


-------- Forwarded Message --------
Subject: I-D Action: draft-ietf-6man-rfc6874bis-00.txt
Date: Sun, 20 Mar 2022 04:17:34 -0700
From: internet-drafts@ietf.org
Reply-To: internet-drafts@ietf.org, ipv6@ietf.org
To: i-d-announce@ietf.org
CC: ipv6@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance WG of the IETF.

         Title           : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
         Authors         : Brian Carpenter
                           Stuart Cheshire
                           Robert M. Hinden
	Filename        : draft-ietf-6man-rfc6874bis-00.txt
	Pages           : 11
	Date            : 2022-03-19

Abstract:
    This document describes how the zone identifier of an IPv6 scoped
    address, defined as  in the IPv6 Scoped Address Architecture
    (RFC 4007), can be represented in a literal IPv6 address and in a
    Uniform Resource Identifier that includes such a literal address.  It
    updates the URI Generic Syntax and Internationalized Resource
    Identifier specifications (RFC 3986, RFC 3987) accordingly, and
    obsoletes RFC 6874.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-rfc6874bis/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-6man-rfc6874bis-00.html


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From nobody Mon Mar 21 05:57:26 2022
Return-Path: 
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5E393A003C; Mon, 21 Mar 2022 05:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level: 
X-Spam-Status: No, score=-4.397 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, 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 s7VNXgn4eJ6g; Mon, 21 Mar 2022 05:57:22 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 6E0EB3A0D30; Mon, 21 Mar 2022 05:57:19 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id e22so16522546ioe.11; Mon, 21 Mar 2022 05:57:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:from:date:message-id:subject:to:cc; bh=BGK1ufcatI2Y0G1lniCOxdjF+hMdjtSyCld/GKDvVe0=; b=R+IWTDp+yyr2ZXSd4ilmzwUxGC1QHP6htt69pv4c4ddS0Pyxi7A1Ou76KmB4+vf9q4 nlL9WAiMw4Zb7vMJwQEyrdzc5JDb2HNk90iIgL/dWlXRIdLQ3ghW9tDSI00jZWns4oOJ Z6t7/DwabmzUO0DwdE8An/cbZdVJvTp/4xlvPa5d82MWrGspMUWEuqfBSN7pHnSE81bg mSV7pKe+K51JImru9Jx0SbBhSHWdeppeVSu55Q8+/MH5SYE6dWUXxzi2x/AkzwMIkgEV 6PnFkbEFvccayAo4cVN8rTeyjL260bg+V532zwrcjBT5KgaxSx6rOYJAe/aW1HiaoiaW pdPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=BGK1ufcatI2Y0G1lniCOxdjF+hMdjtSyCld/GKDvVe0=; b=D/kWOxFdusqRkLndAnDzrSy3yIPAPdx2HmS4kXh2TuV/x1advtnkT0pd8XBuHJA5uC CNHaDSsquaRDBKSTCKRYSaQYefusPQSYW7Sm0AJQias4QZFY8YLAI5oytPzodDmqOiEB nLTn1MB5r/PqhciR+cyMOfrG+dc3NV05v1ZtrrWql6ciMBeoMvEoZPlJS3I7Hsw+kxLZ 54jyGS0JauA5dGFurQTAkx6a84upqtzK6PVy9RZSrwMrsLgoxPLPJB8Em6IsWjpT9/ni 3V9+1+BucV/lrR5wHT4qhEVHCBKh9gZp9TEyZHEJ+IA3T8nvVtorLN68CwSXVNfk485X P6JA==
X-Gm-Message-State: AOAM530gVvSx9q72/Di+3P7c6BfBLmjR0IFDu1H1vYris/XCipLVXi33 dt374++QpQgp4VhcgokoXsr73vmXWu5TEH2QFmfEZqb2Nin4Ow==
X-Google-Smtp-Source: ABdhPJz1d7vM2AzU4AlZTeYqyd+rtsiWQkRLS0Ff9X2zDAe5kjIRDrk3MLy85P76SMXdMe8WD6tXb9AMd4U7L+/l59w=
X-Received: by 2002:a5e:c246:0:b0:645:d2d3:1e76 with SMTP id w6-20020a5ec246000000b00645d2d31e76mr9452409iop.55.1647867438288; Mon, 21 Mar 2022 05:57:18 -0700 (PDT)
MIME-Version: 1.0
From: Kirsty Paine 
Date: Mon, 21 Mar 2022 12:57:07 +0000
Message-ID: 
To: DISPATCH list 
Cc: dispatch chairs , dispatch-ads@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004bd46f05daba09fc"
Archived-At: 
Subject: [dispatch] IETF 113 notes & dispatch outcomes
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 21 Mar 2022 12:57:25 -0000

--0000000000004bd46f05daba09fc
Content-Type: text/plain; charset="UTF-8"

Hi dispatchers,

Thanks again to all our presenters for bringing their work to DISPATCH, our
note-takers, and to the active dispatch community for input on the ways
forward for these drafts.

And a huge thank you to Bron, for stepping in to co-chair with me today at
short notice.

You can find notes for the session uploaded here:
https://datatracker.ietf.org/meeting/113/materials/minutes-113-dispatch-01.html

If you have corrections, please email the dispatch-chairs (CC'd).

As a summary, here are the outcomes and highlights from the session:

DISPATCH outcomes:

   - Complaint Feedback Loop Header: work should go forward, possibly under
   new WG for wider email maintenance if the community has interest - creation
   and next steps to be led by Murray (AD).
   - ECH Config: Interest in the work to progress, but not clear which WG
   (DNSOp, TLS, HTTPBIS all suggested) or area (ART or SEC). Discussion on
   dispatch mailing list.
   - Updated Use of the Expires Message Header Field: recommend for
   AD-sponsorship
   - IMMI: recommend for WG-forming BoF
   - Open Ethics: Interesting work and a good problem, but too big for the
   IETF in its current form. Recommend to work with the community/on the
   dispatch list to describe the IETF-specific parts and problems of this
   ecosystem.

ART Area:

   -

   The side meeting on Event Streaming Open Network is on Wednesday 23rd at
   16:00 in Grand Klimt Hall 3.


Have a great week, and see you around!

Kirsty

--0000000000004bd46f05daba09fc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Hi dispatchers,
=

Thanks again to all our presenters for bringing their work to DISPATCH, =
our note-takers, and to the active dispatch community for input on the ways=
 forward for these drafts. 
And a huge thank you to Bron, for step=
ping in to co-chair with me today at short notice.

You can fin=
d notes for the session uploaded here: https://datatracker=
.ietf.org/meeting/113/materials/minutes-113-dispatch-01.html
=

=
I=
f you have corrections, please email the dispatch-chairs (CC'd).=


As a summary, here are the outcomes and highlights from the session:=


DISPATCH outcomes:
    =

  • Complaint Feedback Loop Header:=
 work should go forward, possibly under new WG for wider email maintenance =
if the community has interest - creation and next steps to be led by Murray=
 (AD).
  • ECH Co=
nfig: Interest in the work to progress, but not clear which WG (DNSOp, TLS,=
 HTTPBIS all suggested) or area (ART or SEC). Discussion on dispatch mailin=
g list.
  • Updat=
ed Use of the Expires Message Header Field: recommend for AD-sponsorship
  • IMMI: recommend=
 for WG-forming BoF
  • Open Ethics: Interesting work and a good problem, but too big for th=
e IETF in its current form. Recommend to work with the community/on the dis=
patch list to describe the IETF-specific parts and problems of this ecosyst=
em.
ART Area:
    The side mee=
ting on Event Streaming Open Network is on Wednesday 23rd at 16:00 in Grand=
 Klimt Hall 3.

Have a great week, and see you around!

Kirsty



--0000000000004bd46f05daba09fc--