IETF Logo Mail Archive

Re: [GNAP] Working group milestones

Yaron Sheffer <yaronf.ietf@gmail.com> Sun, 30 July 2023 18:00 UTC

Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65D19C1516F3 for <txauth@ietfa.amsl.com>; Sun, 30 Jul 2023 11:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=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=gmail.com
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 18Emc6iQRN7E for <txauth@ietfa.amsl.com>; Sun, 30 Jul 2023 11:00:40 -0700 (PDT)
Received: from mail-oa1-x2e.google.com (mail-oa1-x2e.google.com [IPv6:2001:4860:4864:20::2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A448EC1516FF for <txauth@ietf.org>; Sun, 30 Jul 2023 11:00:40 -0700 (PDT)
Received: by mail-oa1-x2e.google.com with SMTP id 586e51a60fabf-1bedeed4d91so177052fac.3 for <txauth@ietf.org>; Sun, 30 Jul 2023 11:00:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690740039; x=1691344839; h=mime-version:in-reply-to:references:thread-topic:message-id:cc:to :from:subject:date:user-agent:from:to:cc:subject:date:message-id :reply-to; bh=qAJ7MWJtQrL3+Rj6m9OZlkO+eN0pQoMDac/QHaRstQA=; b=frt+yvIROPKAyiKCHyJbBcWAFmqktL9sBL8fJ74UizoMgMYVFlelB83x8tpT0W5mXH SFuDeC1WbPy/z/icgR7PMdRicF0bmhy2qx+fj65TLVJA4n5VXlpPDxXh97asR98qPeF3 yGUCgQUmcwto1n9NusdKm+Q0NpxFC7f1v4iHTpRNjBfKYyKsCy7p/8sgD1PFCms8+GbL SNVUdeshIBeWOgXbz4sjVvKmtWo0QVg6KOs5v8E0INjMA8xD2WEHyCedCZZlEmzVXVIX 3qcY6ciRwyg6RmDAuFTLKrGiUtNYwV9RMUN0G3x4XM6dshcmO9YmM3MjMgqEq15FkzlE NgyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690740039; x=1691344839; h=mime-version:in-reply-to:references:thread-topic:message-id:cc:to :from:subject:date:user-agent:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=qAJ7MWJtQrL3+Rj6m9OZlkO+eN0pQoMDac/QHaRstQA=; b=MSLdhgaGyP7gLo6vjXLbZ3N7EJCuIZSR07JGamxljOvp/DY2u4maBa54I8ES4pIUXw /rA9IW5dGaynnZFb7Mxd8BgK2KVRVqqQgHftED4AMsQfqjGIeWfD7/uT4VuJQl/A9OnA 3iUZYJfp+bzCeDzHWDvMEScTiOVPgb8UF5D4Kqph/h/zCYwDI+AQhhkjUncZIDJgb2lZ hBAQf0Ayn+CnG8Pz7/9b9lUoftYXi+abc8zgK6Y5A+Lv+1OMCD/rMn+yJiUp3GsovNeH Ow3a5PXcxs/MZbYe6R0x9DXLHe/lYD3gwkX8WXLr//DhEGnkNjDazbz03lANSQCU7Gks bI/w==
X-Gm-Message-State: ABy/qLa0fGUOu0kWzrAa7CQ6lTY2H8ZQ8GtTKR/A1OvAz8TKytlnoOfk RpQtpVjzIUDMDKCCTjWkPM5RWiohoVWJCg==
X-Google-Smtp-Source: APBJJlHFhIrDllRZitOoibYYCHQmzg3TAuRtXI123hlbFGIgWLFtaJMJ6nPnfrKbUF7+JSDe66U6xw==
X-Received: by 2002:a05:6870:783:b0:1b7:5f57:c29d with SMTP id en3-20020a056870078300b001b75f57c29dmr8895966oab.23.1690740039339; Sun, 30 Jul 2023 11:00:39 -0700 (PDT)
Received: from [192.168.68.108] (IGLD-84-229-146-71.inter.net.il. [84.229.146.71]) by smtp.gmail.com with ESMTPSA id z131-20020a0dd789000000b005771bb5a25dsm2468165ywd.61.2023.07.30.11.00.37 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Jul 2023 11:00:38 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.75.23071400
Date: Sun, 30 Jul 2023 21:00:35 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: Justin Richer <jricher@mit.edu>
CC: GNAP Mailing List <txauth@ietf.org>
Message-ID: <06CD25A4-E660-4C32-97B8-EE7590B01B27@gmail.com>
Thread-Topic: [GNAP] Working group milestones
References: <4C43DF10-6D65-4EE3-9BD3-1C3C4C56988D@gmail.com> <CD42B2E3-E6F2-437F-8B48-3314280B477B@mit.edu>
In-Reply-To: <CD42B2E3-E6F2-437F-8B48-3314280B477B@mit.edu>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3773595638_2299151168"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/_iFjOdHAzEGiOLMcwUCfD-DR0NE>
Subject: Re: [GNAP] Working group milestones
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: GNAP <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2023 18:00:41 -0000

Hi Justin,

 

I agree that Appendix E covers the milestone reasonably well (see below), so I will remove the milestone.

 

Having said that, I don’t think that the initial part of App. E is clear enough on the semantics of the extension points (what can the sender do, what can the recipient do), and I would suggest the following text to replace the first sentence:

 

Extensions to this specification have a variety of places to alter the protocol, including many fields and objects that can have additional values in a registry (Section 11) established by this specification. For interoperability and to preserve the security of the protocol, extensions should register new values with IANA by following the specified mechanism. While it may technically be possible to extend the protocol by adding elements to JSON objects that are not governed by an IANA registry, a recipient may ignore such values but is also allowed to reject them.

 

Thanks,

                Yaron

 

 

From: Justin Richer <jricher@mit.edu>
Date: Friday, 28 July 2023 at 22:06
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Cc: GNAP Mailing List <txauth@ietf.org>
Subject: Re: [GNAP] Working group milestones

 

I believe this is covered sufficiently in the core document: 

 

https://datatracker.ietf.org/doc/html/draft-ietf-gnap-core-protocol#name-guidance-for-extensions

 

I don’t know if this needs to be tracked as a separate milestone or not, for process reasons, but like the key presentations (https://datatracker.ietf.org/doc/html/draft-ietf-gnap-core-protocol#name-securing-requests-from-the-) and migration paths (https://datatracker.ietf.org/doc/html/draft-ietf-gnap-core-protocol#name-compared-to-oauth-20) it’s in the core document so I would assume this milestone can just be deleted like those other two.

 

 — Justin

 



On Jul 28, 2023, at 11:52 AM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:

 

Hi,

 

Our AD nudged us to update the WG list of milestones. Some are done, a new one was added for the RS protocol, and 2 were removed as irrelevant.

 

We have this milestone that we’re not sure about:

 

Guidelines for use of protocol extension points to Working Group Last Call

 

Should we keep it as a separate draft? Is it appropriately covered in the core document? Should we pull the document, add text on extensibility and then resend to Roman?

 

Any thoughts are welcome.

 

Thanks,

                Yaron

-- 
TXAuth mailing list
TXAuth@ietf.org
https://www.ietf.org/mailman/listinfo/txauth

v2.23.0 | Report a Bug | By Email