[httpapi] Francesca Palombini's Yes on draft-ietf-httpapi-linkset-08: (with COMMENT)

Francesca Palombini via Datatracker <noreply@ietf.org> Tue, 01 March 2022 14:11 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: httpapi@ietf.org
Delivered-To: httpapi@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 085533A00AE; Tue, 1 Mar 2022 06:11:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francesca Palombini via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-httpapi-linkset@ietf.org, httpapi-chairs@ietf.org, httpapi@ietf.org, rsalz@akamai.com, rsalz@akamai.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <164614389601.20425.17125858696094463715@ietfa.amsl.com>
Date: Tue, 01 Mar 2022 06:11:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/UjDTTuWC4yi9u6ZfAd-pH15ZnCM>
Subject: [httpapi] Francesca Palombini's Yes on draft-ietf-httpapi-linkset-08: (with COMMENT)
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 14:11:36 -0000

Francesca Palombini has entered the following ballot position for
draft-ietf-httpapi-linkset-08: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-httpapi-linkset/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Lars rightfully noted that two Downref (not in the downref registry) escaped
the IETF Last Call automatically generated text:

  ** Downref: Normative reference to an Informational RFC: RFC 6906
   [RFC6906]  Wilde, E., "The 'profile' Link Relation Type", RFC 6906,
              DOI 10.17487/RFC6906, March 2013,
              <https://www.rfc-editor.org/info/rfc6906>.

  ** Downref: Normative reference to an Informational RFC: RFC 7284
   [RFC7284]  Lanthaler, M., "The Profile URI Registry", RFC 7284,
              DOI 10.17487/RFC7284, June 2014,
              <https://www.rfc-editor.org/info/rfc7284>.

In conformance with https://www.ietf.org/rfc/rfc8067.html, I believe there is
no need for starting another LC for the document including these references,
and I ask the rest of the IESG to pay particular attention to the
appropriateness of these two downward references, as part of their IESG
evaluation.