IETF Logo Mail Archive

Re: [core] [httpapi] WG Last Call on draft-ietf-core-problem-details

Roberto Polli <robipolli@gmail.com> Fri, 13 May 2022 23:08 UTC

Return-Path: <robipolli@gmail.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B29C19E84F; Fri, 13 May 2022 16:08:28 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 Gsq-6lhEtFFm; Fri, 13 May 2022 16:08:27 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 9B674C19E84E; Fri, 13 May 2022 16:08:27 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id z26so10280513iot.8; Fri, 13 May 2022 16:08:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nxvrIXbscTfuL309wTRoTgRgsGxqwnZ5hSzt2ykpCH8=; b=XW5dHdz6Pv0YYE/7QkiSijt3kb4ScyDvgSfFNKoPJDbX3Cu3NAPr2usSGNMc42o9k7 BhQAd4nY9LVaxtzEwBhBdoi4NiICS+RoAQ6IVp0S91lyCseQHoHlUtH9G+m6des4sO/V r0GkpNdE/IiRHMRCAEnFaZ4z13UpurnOmyhaCiZatZ+f6boW0Tqoa0pG+qduvETgL/Zw vUvHZaqkaqaDYqUrGQhZzFxWtek6rdYbZ2i2PcupID8zuNy0aJanppXu//OhfhHhv/Al 0d1VO/s+UqQ/H/xkpIbhO4h+I7CZ3UbOgwJ1f/3e3PclUYGwXJqR0ic2n5QR4meOItQv DalA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nxvrIXbscTfuL309wTRoTgRgsGxqwnZ5hSzt2ykpCH8=; b=0tDSHVi0xRwgFYLvAoM+IYi8gPa2v7WqcVcaUp/rS3wulcUGFf3Fk1dUvpr+eh5lU9 rzYLqVtzNw4cmtxL3PqTi3Ckv6JNSc7Q6TGlu8PSPsiBTOLN9fyZ0iloel/B9w1+IZGm fbHX5ZNzcBYg7M/hAgB/Fr7CtFWo7sddZud146pMzzf1Wu6vWM9Pg7tpebg2nUTEJ+x6 753lrfiy76MZbbGuNiRKNk/kEBLJ1chPHSkuUjKzN2rVD4PfxqQRNYtH1pAP+G/2VQc1 PdpCBomS3VnUzyjZmTTwltTpA5JL40Kqv1Bqc0JqPjwou3ghdflB+jZoHsL8qyTe3bCg i/uQ==
X-Gm-Message-State: AOAM532C11seapQ6t6W1uW8hbO+2nljcNlfclbkbF3dke2e5MVu0pTmy xzle7QVlLJ//JCBFAjQkeht3GnyL75CCMtWPcLOZBT4azIk=
X-Google-Smtp-Source: ABdhPJzALgRKnR6rs/pshiNMDQmDOYw/Zo1/+omCO80JJIzm5DJzutnmL1YRpWAaP4oIi4qUGxnKbUdSwQaSXR6z26k=
X-Received: by 2002:a02:a507:0:b0:32b:543:d66 with SMTP id e7-20020a02a507000000b0032b05430d66mr3661635jam.146.1652483306858; Fri, 13 May 2022 16:08:26 -0700 (PDT)
MIME-Version: 1.0
References: <3a2fb1c8-5c50-fa7a-0672-a73c3b6f1a5f@ri.se>
In-Reply-To: <3a2fb1c8-5c50-fa7a-0672-a73c3b6f1a5f@ri.se>
From: Roberto Polli <robipolli@gmail.com>
Date: Sat, 14 May 2022 01:08:15 +0200
Message-ID: <CAP9qbHV8dEsNvkCd8=Gvn+htDnxqD4kAfO5TONx36S0t8tjK-g@mail.gmail.com>
To: Marco Tiloca <marco.tiloca=40ri.se@dmarc.ietf.org>
Cc: "core@ietf.org WG (core@ietf.org)" <core@ietf.org>, cbor@ietf.org, "httpapi@ietf.org" <httpapi@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/3YUl8kithuLL06_XR_E6pQaSl2Q>
Subject: Re: [core] [httpapi] WG Last Call on draft-ietf-core-problem-details
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2022 23:08:28 -0000

Dear all,

thanks for the opportunity of reviewing this document.

Il giorno mer 11 mag 2022 alle ore 17:59 Marco Tiloca
<marco.tiloca=40ri.se@dmarc.ietf.org> ha scritto:
> Please provide your comments and feedback by Tuesday, the 24th of May.
> https://datatracker.ietf.org/doc/html/draft-ietf-core-problem-details-03

In the media type registration, there's

>   Fragment identifier considerations:  The syntax and semantics of
>      fragment identifiers is as specified for "application/cbor".  (At
>      publication of RFC XXXX, there is no fragment identification
>      syntax defined for "application/cbor".)

With the registration of application/yaml and the +yaml structured
syntax suffix [1], we thought to
detach fragment identifier consideration of subtypes from the
application/yaml and +yaml.

For example: should a future fragment identifier spec for application/cbor be
compatible with all subtypes delegating it to the application/cbor?

Thanks for your work and have a nice day,
R.

[1]: https://github.com/ietf-wg-httpapi/mediatypes/blob/main/draft-ietf-httpapi-yaml-mediatypes.md

v2.23.0 | Report a Bug | By Email