[tcpm] Roman Danyliw's Discuss on draft-ietf-tcpm-yang-tcp-07: (with DISCUSS and COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 29 June 2022 15:26 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: tcpm@ietf.org
Delivered-To: tcpm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B607C14F73D; Wed, 29 Jun 2022 08:26:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-tcpm-yang-tcp@ietf.org, tcpm-chairs@ietf.org, tcpm@ietf.org, nsd.ietf@gmail.com, nsd.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 8.5.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <165651637903.27765.15214938683310593938@ietfa.amsl.com>
Date: Wed, 29 Jun 2022 08:26:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/6eAhQtMiqSE8yFNCGLAz-gc5Zxk>
Subject: [tcpm] Roman Danyliw's Discuss on draft-ietf-tcpm-yang-tcp-07: (with DISCUSS and COMMENT)
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.39
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2022 15:26:19 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-tcpm-yang-tcp-07: 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/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:


** B.2.  Thanks for providing an example of a TCP-AO configuration. 
Unfortunately, this isn’t a valid example example and it seems to be making
citations that don’t match.  Specifically:

-- “<crypto-algorithm>hmac-sha-256</crypto-algorithm>”

The algorithms usable by TCP-AO come from
 Only SHA1 and AES128 are registered.  As far as I tell, the only work to add
SHA256 is in an unadopted and expired draft

As aside, I think the algorithm name would have been SHA-256 or SHA256 (no

--    Per the link to RFC9235:

    The following example demonstrates how to model a TCP-AO [RFC5925]
   configuration for the example in TCP-AO Test Vectors [RFC9235].  The
   IP addresses and other parameters are taken from the test vectors.

RFC9235 doesn’t use SHA256; and uses KeyID 61 and 84.  Different KeyIDs are
used in this example.  Which parameters are being used from the test-vector?


Thank you to Hilarie Orman for the SECDIR review.

I concur with the SECDIR observation that “there are no statistics kept for
authentication failures.  If a shared key falls out of synch, the statistics
might help detect that.”  I appreciate the response
which recommends that this should be generically modeled.  I disagree that this
should be deferred. There is a very specific TCP-level primitive being
described here and it makes sense to me to provide a corresponding logging