IETF Logo Mail Archive

[alto] [IANA #1230654] [Errata Verified] RFC7285 (6876)

Amanda Baber via RT <iana-matrix@iana.org> Fri, 13 May 2022 19:58 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D561C15EB3A for <alto@ietfa.amsl.com>; Fri, 13 May 2022 12:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 pg9AkKs9Thgv for <alto@ietfa.amsl.com>; Fri, 13 May 2022 12:58:12 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (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 29602C15EB28 for <alto@ietf.org>; Fri, 13 May 2022 12:58:12 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 1AB75E1218; Fri, 13 May 2022 19:58:11 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id C62DA2099D; Fri, 13 May 2022 19:58:06 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-matrix@iana.org>
Reply-To: iana-matrix@iana.org
In-Reply-To: <20220512220950.4BEC71330F3@rfcpa.amsl.com>
References: <RT-Ticket-1230654@icann.org> <20220512220950.4BEC71330F3@rfcpa.amsl.com>
Message-ID: <rt-4.4.3-15384-1652471886-1534.1230654-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1230654
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
To: rfc-editor@rfc-editor.org
CC: yry@cs.yale.edu, w.roome@alcatel-lucent.com, sprevidi@cisco.com, shalunov@shlang.com, richard_woundy@cable.comcast.com, repenno@cisco.com, ralimi@google.com, mohamed.boucadair@orange.com, martin.h.duke@gmail.com, ietf-alto@skiesel.de, alto@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Fri, 13 May 2022 19:58:06 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/J0BoUdQW1rV_hrFaTsYyj5f65vM>
X-Mailman-Approved-At: Sat, 14 May 2022 10:12:36 -0700
Subject: [alto] [IANA #1230654] [Errata Verified] RFC7285 (6876)
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.34
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2022 19:58:16 -0000

Hi all,

This question relates to both 6874 and 6876:

Should "priv:" be removed from the ALTO Cost Metrics and ALTO Endpoint Property Types registries? See

https://www.iana.org/assignments/alto-protocol

If so, should we add the note "Note: Identifiers prefixed with 'priv:' are reserved for Private Use (see RFC 7285, Section 10.8.2)" to the top of each registry?

We'll need Martin to sign off on any registry changes.

thanks,

Amanda Baber
IANA Operations Manager

On Thu May 12 22:09:51 2022, rfc-editor@rfc-editor.org wrote:
> The following errata report has been verified for RFC7285,
>  "Application-Layer Traffic Optimization (ALTO) Protocol".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6876
> 
> --------------------------------------
> Status: Verified
> Type: Technical
> 
> Reported by: Mohamed BOUCADAIR <mohamed.boucadair@orange.com>
> Date Reported: 2022-03-09
> Verified by: Martin Duke (IESG)
> 
> Section: 14.3
> 
> Original Text
> -------------
> +------------+--------------------+
> | Identifier | Intended Semantics |
> +------------+--------------------+
> | pid        | See Section 7.1.1  |
> | priv:      | Private use        |
> +------------+--------------------+
> 
> Table 4: ALTO Endpoint Property Types
> 
> 
> Corrected Text
> --------------
> +------------+--------------------+
> | Identifier | Intended Semantics |
> +------------+--------------------+
> | pid        | See Section 7.1.1  |
> +------------+--------------------+
> 
> Table 4: ALTO Endpoint Property Types
> 
> Note: Identifiers prefixed with "priv:" are
> reserved for Private Use (see Section 10.8.2.)
> 
> 
> Notes
> -----
> priv: is not an identifier, but a prefix.
> 
> --------------------------------------
> RFC7285 (draft-ietf-alto-protocol-27)
> --------------------------------------
> Title               : Application-Layer Traffic Optimization (ALTO)
> Protocol
> Publication Date    : September 2014
> Author(s)           : R. Alimi, Ed., R. Penno, Ed., Y. Yang, Ed., S.
> Kiesel, S. Previdi, W. Roome, S. Shalunov, R. Woundy
> Category            : PROPOSED STANDARD
> Source              : Application-Layer Traffic Optimization
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email