IETF Logo Mail Archive

Re: [httpapi] Introduction

"Salz, Rich" <rsalz@akamai.com> Sat, 09 January 2021 22:02 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 85D513A0365 for <httpapi@ietfa.amsl.com>; Sat, 9 Jan 2021 14:02:23 -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 x-YSV9BQNRjc for <httpapi@ietfa.amsl.com>; Sat, 9 Jan 2021 14:02:22 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 2E7DF3A0317 for <httpapi@ietf.org>; Sat, 9 Jan 2021 14:02:21 -0800 (PST)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 109Lx32M026938; Sat, 9 Jan 2021 22:01:38 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=NRseGrRd5Z9mGz3WO18blbFWhB+OgEl+Ha+wMOsCtYc=; b=WEq+JQmdwUayVVSJziHhUYECwNmMMTGV4CxPEdSFpsqQ3u1kplsgKOjndebwyrn5tRPy /ylg5k0rLD6aO1TJQAY9D/0kuoXe36aSVMl0k6Ktmv/y7xVl3NVFcFKuaOduuignE2+C ju6XO73/4z7RbYzruzF2M5lnqQ5s98Jj/hAn/RdjWZ1KvUJi1MXJF5eXdpfLwi8ffxaF eZ98A7SKKB2p8p1UH6NQmGLjHzb/s7XavoJ8D6M3Wqtn/02j+mKPId1dZ88o/Tk6Bdn+ By3YMF0uLndMM04Is2lggm3bafOpgxWPI/kxsojYmiM/JCaBhBgCNDRsFavSguuBVldL ug==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 35y5sb5c7e-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 09 Jan 2021 22:01:38 +0000
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 109LZS0H019577; Sat, 9 Jan 2021 17:01:38 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.57]) by prod-mail-ppoint1.akamai.com with ESMTP id 35y8q2s2ux-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 09 Jan 2021 17:01:38 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 9 Jan 2021 17:01:37 -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 17:01:37 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Christoph Kappestein <christoph.kappestein@gmail.com>, Erik Wilde <erik.wilde@dret.net>
CC: "httpapi@ietf.org" <httpapi@ietf.org>
Thread-Topic: [httpapi] Introduction
Thread-Index: AQHW5o2MTfOy5tg/IUqCBSkAUmxvDKof5kKAgAAheYD//9EngA==
Date: Sat, 09 Jan 2021 22:01:36 +0000
Message-ID: <8BC13893-6E08-4D29-9942-623392D1F546@akamai.com>
References: <CALcRZn4YSC9w4VA7J=UfEoUrKDLwfoTTU38GHA5CQ9xdHVPDhA@mail.gmail.com> <f5442133-47fd-f9a2-77e5-fd9a1548729b@dret.net> <CALcRZn5enQrw-8E4m6tFu_3Z5waZFprbs+V976YTXMAELi9SRQ@mail.gmail.com>
In-Reply-To: <CALcRZn5enQrw-8E4m6tFu_3Z5waZFprbs+V976YTXMAELi9SRQ@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: <857EBB4033EB8349A22CD85E2DA85236@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_13:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 malwarescore=0 mlxscore=0 bulkscore=0 adultscore=0 phishscore=0 suspectscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101090143
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-09_13:2021-01-07, 2021-01-09 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 malwarescore=0 phishscore=0 spamscore=0 mlxlogscore=969 suspectscore=0 impostorscore=0 bulkscore=0 clxscore=1015 priorityscore=1501 adultscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101090145
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.18) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint1
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/WpIdwmrpvaqd66RHy-_s8Zc8tO0>
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 22:02:24 -0000

>    @Julian just to get a better understanding, if we say that RFCs are finished
    documents, does this mean that also those draft RFCs i.e. listed here
    https://datatracker.ietf.org/wg/httpapi/documents  are finished? I totally
    understand that RFCs like 3986 are finished and will not change easily or only
    in case there is an actual error. But I assumed that we can evolve and iterate
    those "draft" RFCs easier until they become a "real" RFC. But this is only my
    understanding from an outsider perspective so please let me know whether this
    makes sense.

You are correct.  But the draft documents are called internet-drafts or I-D's; we don't use the term "draft RFC" because it leads to confusion.

The place to comment on those specific documents is by posting to the list.  Or raising issues on GitHub; https://github.com/ietf-wg-httpapi has repo's for each draft.

v2.23.0 | Report a Bug | By Email