IETF Logo Mail Archive

Re: [httpapi] Introduction

"Salz, Rich" <rsalz@akamai.com> Sat, 09 January 2021 17:40 UTC

Return-Path: <rsalz@akamai.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 3CB543A13C9 for <httpapi@ietfa.amsl.com>; Sat, 9 Jan 2021 09:40:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level:
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 cHLV8HUsQ1cH for <httpapi@ietfa.amsl.com>; Sat, 9 Jan 2021 09:40:26 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 6A1003A13C8 for <httpapi@ietf.org>; Sat, 9 Jan 2021 09:40:26 -0800 (PST)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 109HXxVY015459; Sat, 9 Jan 2021 17:40:25 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=bCP2yipRRS8EXr4PT4otdoE+7uDqJGdN+8i1P6mysR4=; b=drVLzHLKFfzWLURYzRGdKIViTRM6lTL/Z0En2+XHityf6CWEZwTZyVN3J67ZQ+sdBMpu axQ1E8s5wYa/YK7EC6C2WObJZcXkRhz+uHRFon6LVJm9JFyp1HjCZv4bY5ZH16JNyzVV DUfLCDEM2BEC6PbLBbpWnPgPPLpMV4HbMZyQ0UdMVt8FEFHNEw7UGaJAHlabUb6wR4E9 h7uiRfZtTC80WYZMjlMgbF1h0hP6qhiZzd+G2P4Zvov8gTXFDANk5z2Uh6zmbfgt8Pmg fLpdXtlUO+8xk+BPY04MuobsMQ1OtP5myC9VUoUO+P6u6ilTYiCdhVXKi5ckfp9CO12/ hQ==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 35y5e06vf1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 09 Jan 2021 17:40:25 +0000
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 109HZ7t8016609; Sat, 9 Jan 2021 09:40:24 -0800
Received: from email.msg.corp.akamai.com ([172.27.123.53]) by prod-mail-ppoint5.akamai.com with ESMTP id 35ybbe0gbx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 09 Jan 2021 09:40:24 -0800
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 9 Jan 2021 12:40:23 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Sat, 9 Jan 2021 12:40:23 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Christoph Kappestein <christoph.kappestein@gmail.com>, "httpapi@ietf.org" <httpapi@ietf.org>
Thread-Topic: [httpapi] Introduction
Thread-Index: AQHW5o2MTfOy5tg/IUqCBSkAUmxvDKofj+aA
Date: Sat, 09 Jan 2021 17:40:22 +0000
Message-ID: <C1F0E0CE-61E4-41F3-AAF1-AB64D8311A40@akamai.com>
References: <CALcRZn4YSC9w4VA7J=UfEoUrKDLwfoTTU38GHA5CQ9xdHVPDhA@mail.gmail.com>
In-Reply-To: <CALcRZn4YSC9w4VA7J=UfEoUrKDLwfoTTU38GHA5CQ9xdHVPDhA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.45.21010502
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: text/plain; charset="utf-8"
Content-ID: <18D580F63BEE414D971D7DF143688BC6@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-09_09:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 malwarescore=0 mlxscore=0 mlxlogscore=999 suspectscore=0 spamscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101090117
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-09_09:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 adultscore=0 impostorscore=0 mlxscore=0 bulkscore=0 priorityscore=1501 phishscore=0 lowpriorityscore=0 suspectscore=0 spamscore=0 mlxlogscore=999 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101090117
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.60) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint5
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/wV88Bhywa0jAQYsAGTI9n15XlH0>
Subject: Re: [httpapi] Introduction
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 09 Jan 2021 17:40:28 -0000

>    We have started this since there is currently no great standard which describes
    JSON payloads and is optimized for code generation. So if this a topic which you
    want address I would be happy to share my experiences.

The IETF has had a couple of working groups on JSON; you can find the "concluded" ones at https://datatracker.ietf.org/group/concluded/ and the active ones at https://datatracker.ietf.org/wg/  Look for "json" in the name.  Even concluded groups still have their mailing list kept open. I don't know if that will be helpful or not.  As for whether or not this WG wants to discuss this, it's up to the WG to decide if they're interested (by having this kind of discussion on the mailing list), and if necessary to work with the Area Director to determine if we need to modify the WG charter or not.

>    I am not too familiar with the process to comment an RFC but is there in general
    a form where I can provide written feedback to existing specifications or is
    this done through this mailing list?

RFC's are published documents, not drafts; the name "request for comments" is a node to IETF history.  How to provide feedback on published RFC's depends on the amount and nature of feedback.  If you have a well-contained technical error, you want to report an "errata" against the RFC.  If it's more philosophical or just "more", it might be better to find the WG that published the RFC and post to that mailing list (see above).  To find the WG for rfc 1234, go to https://www.rfc-editor.org/info/rfc1234 and look at the "Source" label, which will have a link to the WG.

Hope this helps.  Welcome!

v2.23.0 | Report a Bug | By Email