Re: [Ppm] Versioning for DAP drafts

Martin Thomson <mt@lowentropy.net> Thu, 04 August 2022 00:57 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF4A6C157B34 for <ppm@ietfa.amsl.com>; Wed, 3 Aug 2022 17:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=Islry7qA; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gsvrM0ro
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V5_muNoFt5n4 for <ppm@ietfa.amsl.com>; Wed, 3 Aug 2022 17:57:08 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B8C7C14F736 for <ppm@ietf.org>; Wed, 3 Aug 2022 17:57:08 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E563C5C00BF for <ppm@ietf.org>; Wed, 3 Aug 2022 20:57:07 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Wed, 03 Aug 2022 20:57:07 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1659574627; x=1659661027; bh=vjHzXxvpbc i9mxkmJK1UW18dtJik7GxyRNJu7Fve01Y=; b=Islry7qAU5cVtbCoo1rhXQbt4A rbTTN7B7qFUp3WYv0Sb267XwvQsuCyNGZq7xoboznrbU2N5Z4OG/tzZZ2H9OYbf4 yvQBov2AF3J0SahD55SUaQUCQDWGsGheEWuZ2NGI+Ndt0gdjUp7Ebadms6bN6tKb wHO+rb//xivzW83hOrUY+WmU0XmBMtrGnzS751TZgp7HIwlxcqn7svx5BQLXItkP g7byq9aRzj2x6Utj7mZmbkM6Oqp2IgdOSo3tRSFC4su0uTz8ukV2Sa+nIbPSgl9A W2tWNS8sGspY0laGYKERE5sI2MAKiXan2ui/oa4yfQ5dvnd9H88/1L8J3ssA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1659574627; x=1659661027; bh=vjHzXxvpbci9mxkmJK1UW18dtJik 7GxyRNJu7Fve01Y=; b=gsvrM0roqWegOeM6etvMYieEUykXaRlRGt4Brm+ZBe5f pantm8Ax2nF385erfrhRWvXvMir6j4GHB3ld+OD0GGEKMHsvyUr+dp75l1XKvSQb 4go3b06euQwDkYSxpX2zYBysiWpFffvGv1+xNfVrbPDlgvBcBZzoF9zQR4hDpoTG vFRWOEFRbBCdkIpZlh0VefiyotviDOzFNxcKvO7pHHxtCOM9swIQkzNTxeFLA9HX HiIzQRFjti+5o4JDDJq32dSKHkngDMAIYqHOka+isDpDXhQ9A9gXGysWk3bwfrW5 W9JQna5yxpTPIRY7pBRkVh+SHTP9Mk94B0d2o6lciw==
X-ME-Sender: <xms:YxnrYg4KliOHzSYpQnhhbewZto2q2eXpa9oXVp5Y9vGXqpPL7Mv83A> <xme:YxnrYh74yKRToaqGJXYdmmm9X56Ry3iQH-T5JRJGtUKrD-U6WYslXJHtvPfc376z0 W7mlJJJbRrnlJ9o_cM>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvddvkedggedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpeekteeuieektdekleefke evhfekffevvdevgfekgfeluefgvdejjeegffeigedtjeenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvg ht
X-ME-Proxy: <xmx:YxnrYvfwhG_4eeP8_sCl1beib__9nc7c0Amyh_EWcDIOL8SmJlUVng> <xmx:YxnrYlLvr4bQHy0FEcAfYxl6-ruqLA06qsPNEX0GBRWawEo2lqn5lg> <xmx:YxnrYkJWyGEQcdwjNycvj8o_rt4MqGhifHTPQYtakY2B6SSgmGwQ5A> <xmx:YxnrYpVo7HieFqcvgkt0fTnDsB6K6R4R1Krv5bGPdXY6rPYZ9_cvHw>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id B2FE72340077; Wed, 3 Aug 2022 20:57:07 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.7.0-alpha0-758-ge0d20a54e1-fm-20220729.001-ge0d20a54
Mime-Version: 1.0
Message-Id: <1c878702-595e-4a85-85ca-a61fcd3d2981@beta.fastmail.com>
In-Reply-To: <CABN231qYCpEKD7bU6uKu24UfKwD-=1p1fvRHrN7qXBGnKBrAgw@mail.gmail.com>
References: <CAG2Zi233rdc9XVS7euSDjw4UtgEYUzR_7hozZFk1iHOCtnrE+w@mail.gmail.com> <CABN231pSMmxRXbiKHpQv8PDQEKyD=5icx-rnWJYdo=Nje73v4Q@mail.gmail.com> <CAG2Zi20oWT3MHh70-LpOfT26dtCmojR-CENe0Ykq+uo0+Qxkhg@mail.gmail.com> <CAG2Zi21Yjiu=syjo=RZaRc9w3u6POySXDUUQ3AoejHrBNztnfw@mail.gmail.com> <CABN231qYCpEKD7bU6uKu24UfKwD-=1p1fvRHrN7qXBGnKBrAgw@mail.gmail.com>
Date: Thu, 04 Aug 2022 10:56:48 +1000
From: Martin Thomson <mt@lowentropy.net>
To: ppm@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/9J_XWUwy6kS9Tg5SvRm4Z6LRrGY>
Subject: Re: [Ppm] Versioning for DAP drafts
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2022 00:57:13 -0000

On Thu, Aug 4, 2022, at 09:44, Tim Geoghegan wrote:
> I understand your desire to maintain a single branch and a single 
> deployment. Having read your initial post again, more carefully, I 
> think I am arguing for your option #3: 'instead of POSTing reports to 
> "/upload", clients would POST to "/02/upload"'.

This seems right.  As long as the protocol/API allows servers to choose how they lay out their resources (path, server name, whatever) then you can have a single deployment that supports multiple versions or one deployment per version at your discretion.  That's why we have RFC 8820.