[Cbor] Éric Vyncke's Discuss on draft-ietf-cbor-network-addresses-09: (with DISCUSS and COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Tue, 05 October 2021 13:34 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B31063A0D6D; Tue, 5 Oct 2021 06:34:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-cbor-network-addresses@ietf.org, cbor-chairs@ietf.org, cbor@ietf.org, barryleiba@computer.org, barryleiba@computer.org, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.38.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <163344085669.17315.998599560097016034@ietfa.amsl.com>
Date: Tue, 05 Oct 2021 06:34:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/nLxdu8wfa4gh7JUcOnZagaCFxE8>
Subject: [Cbor] =?utf-8?q?=C3=89ric_Vyncke=27s_Discuss_on_draft-ietf-cbor?= =?utf-8?q?-network-addresses-09=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2021 13:34:18 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-cbor-network-addresses-09: Discuss

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/blog/handling-iesg-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-cbor-network-addresses/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thank you for the work put into this document.

Please find below two blocking DISCUSS points (probably easy to address), some
non-blocking COMMENT points (but replies would be appreciated even if only for
my own education), and some nits.

Special thanks to Barry Leiba for his concise shepherd's write-up but very
clear about the WG consensus.

Thank you also to Donald Eastlake for this INT directorate review that I am
vastly supporting:
https://mailarchive.ietf.org/arch/msg/int-dir/6Ox8iEBMqXkUoC2aUEF3wi4-c5g/

I hope that this helps to improve the document,

Regards,

-éric

== DISCUSS ==

Generic comment how are link-local address (LLA) with scope encoded ? I would
expect CBOR to work also on LLA only networks... At the bare minimum, please
state that link-local addresses cannot be encoded with their scope, hence, they
cannot represent an interface.

-- Section 3.1.3 --
How can 2 valid link-local addresses (fe80::1%eth0, fe80::1%eth1) can be
represented in order to identity two interfaces ?


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

== COMMENTS ==

I love how your start with IPv6 in section 3 and use the ASCII codes for '6'
and '4' ;-)

-- Section 3.2 --
Is there any reason why part of the IPv6 is in lowercase (as in RFC 5952) and
the other part in uppercase ? This is confusing to the reader (even if
hexadecimal numbers are obviously case insensitive).

== NITS ==

-- Abstract --
Should CBOR be expanded ?