Re: [httpapi] resolving issues
Herbert Van de Sompel <hvdsomp@gmail.com> Fri, 16 April 2021 17:53 UTC
Return-Path: <hvdsomp@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 497C83A2E18 for <httpapi@ietfa.amsl.com>; Fri, 16 Apr 2021 10:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, 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=gmail.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 AzFPtFV30MRx for <httpapi@ietfa.amsl.com>; Fri, 16 Apr 2021 10:53:35 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 861CD3A2E14 for <httpapi@ietf.org>; Fri, 16 Apr 2021 10:53:35 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id z1so33285230edb.8 for <httpapi@ietf.org>; Fri, 16 Apr 2021 10:53:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=ioeBITptwGuQfIxsI3bxaY2/xmvSUOhPuRrfUhYauOE=; b=oHRCznsW+QeuKmAAsN9yVr8hx6iKq3VWCtjrM5F5V8sZp6Ky/ECHtSJd1fUOsPo3Ih inmYXsJ/WfjkusrLDbwzFUe/I69mOJooTJ8spCFLXDK6Eba8H3HIq19M6u5yaKz5DBhY cky/M3i91tLqR4+WWDpwZmbok1KblT8+OJoimhl7bPOFgogK7wpoJftSM4BIJ4N2CFJC MT8w1chvyq1f3942kZM/CzbDaDJpMZy1B3AfjzzSGyu4OGD+hCsaoWBuOeyQMFjfiA7t 4GukptdUmIWGpiEAs/PgbZXYPIRKSiU8PDPQ46an8y19505bp3UIJn8cPbkU1B+8cgXO rt2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=ioeBITptwGuQfIxsI3bxaY2/xmvSUOhPuRrfUhYauOE=; b=gGACA0UMCon/VLCS6j97V0jPXWc/68XasN994ZpzmUZAKC9l2QeKn9hVCBOZv7mu4r e1KByff3HcZ7WCOr/1PAlp4npqO5GCI4dgyBBulMyPqOytjTIlVODRKhd0xqiiLa6yJv 1J49yEKOJZXGQUUSQ5/1xpnx0UScrzEs0F/tq53T2LsKvIJ9aTb52jgrsOnT+LiaZ+qy pl1su00RVxcMABC0x74fgSUWMFvQaka+2SJ7y3L91USOH6yALTIKAzb2FuiQ2CD+UkEt lxyWPnKCftTYPmqSpl42Q+76z21azgC5j62IcUKZOqb5ItIGG2QC4rH2ChboxbBhZGQm abtQ==
X-Gm-Message-State: AOAM530DQlR7Cg/pN5+kCYLkTY7zmmKNZ/pBASzmnyB0T0bCu2hJp+uY 6aiwW1eQmuuuj8rTaOKZqs4=
X-Google-Smtp-Source: ABdhPJwe8mFrnSz+XEfescsFHAanOL/yFFaxtfXSmUToBArYmZ2MEH/Eb6zp0c7/tghyX/5LXIs3ig==
X-Received: by 2002:a05:6402:176c:: with SMTP id da12mr11199121edb.325.1618595613207; Fri, 16 Apr 2021 10:53:33 -0700 (PDT)
Received: from [10.0.0.4] (88-117-75-43.adsl.highway.telekom.at. [88.117.75.43]) by smtp.gmail.com with ESMTPSA id cn2sm6196999edb.64.2021.04.16.10.53.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 16 Apr 2021 10:53:32 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-88C433D6-3890-4C7B-8A40-061A032E3D07"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Herbert Van de Sompel <hvdsomp@gmail.com>
In-Reply-To: <F8B8E93D-335E-4676-8251-686EF1DB4D1F@akamai.com>
Date: Fri, 16 Apr 2021 19:53:32 +0200
Cc: Sanjay Dalal <sanjay.dalal@cal.berkeley.edu>, mnot@mnot.net, Erik Wilde <erik.wilde@dret.net>, darrel.miller@microsoft.com, httpapi@ietf.org
Message-Id: <022C6A1E-1245-4E9D-B06E-1991AFE1BFD8@gmail.com>
References: <F8B8E93D-335E-4676-8251-686EF1DB4D1F@akamai.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
X-Mailer: iPad Mail (18D70)
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/bhrWLug4MA3k4Q2MbSkxXRvoK4M>
Subject: Re: [httpapi] resolving issues
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: Fri, 16 Apr 2021 17:53:39 -0000
On Apr 16, 2021, at 18:58, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote: > > > What is the process to bring an issue to its resolution? There are many issues opened and discussed on the Deprecation header and rfc7807bis. How do we bring them to conclusion so we have clarity in preparing a new draft? Please advise and also inform the maillist. > I’m kind of interested in this too with regard to the Link Set I-D. There’s one open issue that would really benefit from some expert opinions: https://github.com/ietf-wg-httpapi/linkset/issues/3 I also don’t know what the process is, but I did ask for feedback on the issue that Rich moved from the original GitHub repo to the HTTPAPI one, hoping that someone would have ideas that could lead to a resolution. Greetings Herbert > If the authors have a thoughts on how to address an issue (or issues), make a PR. If it’s just an editorial change (wordsmithing, move paragraphs, etc), feel free to merge once the co-authors agree. If it is a substantive change make a PR, and post a description to the mailing list encouraging feedback. If it’s a “big honkin change” then tell the chairs in the same message that you thinkg the WG should get consensus before being merged. > > WG chairs generally have flexibility to “do the right thing,” so if these processes don’t make sense, let us know. > > Hope this helps. > > -- > httpapi mailing list > httpapi@ietf.org > https://www.ietf.org/mailman/listinfo/httpapi
- Re: [httpapi] resolving issues Salz, Rich
- Re: [httpapi] resolving issues Herbert Van de Sompel