Re: [httpapi] Towards a hal+json RFC

Mike Kelly <mikekelly321@gmail.com> Wed, 04 October 2023 11:39 UTC

Return-Path: <mikekelly321@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F03C14E515 for <httpapi@ietfa.amsl.com>; Wed, 4 Oct 2023 04:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level:
X-Spam-Status: No, score=-1.854 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 OVPCJSnjeEK4 for <httpapi@ietfa.amsl.com>; Wed, 4 Oct 2023 04:39:08 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (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 64B3AC14F749 for <httpapi@ietf.org>; Wed, 4 Oct 2023 04:39:08 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id 98e67ed59e1d1-273e3d8b57aso475072a91.0 for <httpapi@ietf.org>; Wed, 04 Oct 2023 04:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696419547; x=1697024347; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2oNmx6VpP1wqe79vdlj0eZ0rAOpjLwp9BQzHg2HkJac=; b=hSgz271OiRthYIyYiXvIbscShoM4znLslK0OZxeicaCvJCO5Bx37CDBkoXJVYArTZG QFusq+/A/9H/VWfXd4duhmb8EdUuSostoTFNkG/wVPbM6t3wer3FFtTScONwYbRa1G+6 RYdSxk/NKWpe6Q2zxo+ZDy2+p1+t2yvWAflId13BFKb6yiYNhijwtKb3DfUzB0gbIFeY ZcV5ulgs/0tKc6MCJXx1f+sKNnsb/JNd1o/xuG1foGVgTZwkG1kHqF0l1AU4rPQkRZpm 5VHfrMaFPFAmPUnkSKtMFLslPrJI281NkBWcgSp5xj1IWHHsBDQr3MxoHLz0t2f54V3o ujoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696419547; x=1697024347; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2oNmx6VpP1wqe79vdlj0eZ0rAOpjLwp9BQzHg2HkJac=; b=Y4A8vwSR11//Xnu1h98gBl/EJy9cmDApjR7HOSOTA1WLNs8tr4D4DNnBdTn7SewCSi 8hRfZILC6vL1Uc8RZqJGjIDbpZM/ATzHZyX1P1P3e9FV/7ut38fDXSs+ZnOYe8vKKIlV sGUW+zPBneazQqWhvFTszNcXU9xxdFVpPLMyNoPlDKSGNL95bRXhoXMLi2LbzHp5kJEM bGuv2sm0qXxeffMJ8zZzgmP/UhD4RKbpkT0x8wcsQlLrpLri1NBAy16Qy7bWEOoHbtbQ kSYmqrxhdJzX9wlIrJJdFHbJk848U8Fl3hn6+tr6umr/1905HElUY6R8rjocUNdXdnO1 WFNw==
X-Gm-Message-State: AOJu0Yz+orltUAjSO8ec+G2JCCnkKEGdDZaoHfVC+rxN61eyILHGFlkt EshhYkQHCGDeKCWa8/QwlkDnJumgKGJCtZYW+l4DW/ldEP9T+g==
X-Google-Smtp-Source: AGHT+IG4dLZR8QIsGBoW7WHwJmxU53bqx8UwcPtg2FIXu+BQnL1iKXWjLQFqKL+M50AptByayRhAHit7Qg6Mv2oxlEs=
X-Received: by 2002:a17:90a:43c2:b0:26d:412d:9ce8 with SMTP id r60-20020a17090a43c200b0026d412d9ce8mr1820980pjg.0.1696419547346; Wed, 04 Oct 2023 04:39:07 -0700 (PDT)
MIME-Version: 1.0
References: <CANqiZJYb7iiRnkMXyVKXDTuqVCyuutzoArRxg_h653V8nzE+Tg@mail.gmail.com> <db12ee22-6816-e3e8-cb0d-6d9d1b85197d@dret.net> <CANqiZJY4hYhvG3SPPM9gicevP0fonaQtWZD2o5nNMEa+CSdehg@mail.gmail.com> <CAPBurBsM+DX8kEHgxgVt1B00idb6Zb1ZTB6pK1UWD39pFOaYNQ@mail.gmail.com> <CANqiZJb6A5PKX30QL=4fi6TeWESQKVq8eO3=Fo9JzGOUDTwXVg@mail.gmail.com> <MN2PR00MB067117B42669A6CCDD696439F0C4A@MN2PR00MB0671.namprd00.prod.outlook.com> <CANqiZJY_jmESjPm_fDbueF7iEJqmXP=x0Z6Dj5wOm9QyquSJYg@mail.gmail.com> <DM6PR00MB06654E266BD04BCAD1D287D3F0C4A@DM6PR00MB0665.namprd00.prod.outlook.com> <CANqiZJaNuhnP5Tp_miZdBs_sAtBWC__NkdWjVVOYSBgzG3nBcw@mail.gmail.com> <DM6PR00MB06653DD8120B3E7CD9168B4FF0C4A@DM6PR00MB0665.namprd00.prod.outlook.com> <CANqiZJa8HNQkrjx1B8nZg5eiZBzJy+1HHBpvC6ToqL-oe23Sdg@mail.gmail.com>
In-Reply-To: <CANqiZJa8HNQkrjx1B8nZg5eiZBzJy+1HHBpvC6ToqL-oe23Sdg@mail.gmail.com>
From: Mike Kelly <mikekelly321@gmail.com>
Date: Wed, 04 Oct 2023 12:38:55 +0100
Message-ID: <CANqiZJY3xzA=4jpwBzD++UWmtj7HcLgzFK9KtPouKFQTY86xVQ@mail.gmail.com>
To: Darrel Miller <Darrel.Miller@microsoft.com>
Cc: "httpapi@ietf.org" <httpapi@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000827a550606e27495"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/Y7OSjzv_JBIIVtiYn5PuzdkJw2Q>
Subject: Re: [httpapi] Towards a hal+json RFC
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Oct 2023 11:39:12 -0000

I figured it out and completed the remaining sections (I've assumed for now
that there are no IANA considerations, which I assume I can ammend if this
is corrected during the process?). Latest version is here:

https://datatracker.ietf.org/doc/draft-kelly-json-hal/10/

Assuming my assumption about IANA considerations is correct should I fire
an email to rfc-ise?

Cheers,
M



On Tue, Oct 3, 2023 at 3:28 PM Mike Kelly <mikekelly321@gmail.com> wrote:

> Alright. What sort of “security considerations” apply to a media type like
> hal? Processing is already covered by json?
>
> On Tue, 3 Oct 2023 at 14:52, Darrel Miller <Darrel.Miller@microsoft.com>
> wrote:
>
>> Ok, so step 1 is to have an ID.  Which you have here
>> https://datatracker.ietf.org/doc/html/draft-kelly-json-hal
>>
>> The next step is to email rfc-ise@rfc-editor.org with the information
>> listed on this page https://www.rfc-editor.org/about/independent/
>> However, I see two things that need to be taken care of first.  One is your
>> security considerations needs to be completed and the other is we need to
>> figure out what needs to be done about the IANA section.  If you work on
>> the Security Considerations, I'll do some reading about IANA requirements.
>>
>> Darrel
>>
>>
>>
>> ------------------------------
>> *From:* Mike Kelly <mikekelly321@gmail.com>
>> *Sent:* Tuesday, October 3, 2023 9:01 AM
>> *To:* Darrel Miller <Darrel.Miller@microsoft.com>
>> *Cc:* httpapi@ietf.org <httpapi@ietf.org>
>>
>> *Subject:* Re: [httpapi] Towards a hal+json RFC
>>
>> Alright sounds good to me. What do I need to do right now to get this
>> started? :)
>>
>> On Tue, 3 Oct 2023 at 13:59, Darrel Miller <Darrel.Miller@microsoft.com>
>> wrote:
>>
>> This isn't a high traffic list and I think there are probably a few
>> people on this list that would be interested in discovering more about the
>> independent submissions process, so I have no concerns if we keep the
>> discussions on list.  But feel free to email directly too.
>>
>> And just as a caveat, I haven't gone through this process before, so we
>> will be learning together 🙂
>>
>> Darrel
>>
>> ------------------------------
>> *From:* Mike Kelly <mikekelly321@gmail.com>
>> *Subject:* Re: [httpapi] Towards a hal+json RFC
>>
>> Hey Darrel, thanks so much for this. Very clear. Yes it does sound like
>> independent submission would be more appropriate. I think it also suits my
>> sensibilities better..! That being the case would it be better to this off
>> the mailing list as I could do with your guidance on how this process works.
>>
>> Cheers,
>> M
>>
>>