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

Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> Tue, 28 June 2022 12:53 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 B70D1C13A253; Tue, 28 Jun 2022 05:53:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zaheduzzaman Sarker 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.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>
Message-ID: <165642080074.47890.4087202101509957926@ietfa.amsl.com>
Date: Tue, 28 Jun 2022 05:53:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/9vBTrYJ0GNehwdthWcMUtYEl_Do>
Subject: [tcpm] Zaheduzzaman Sarker'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: Tue, 28 Jun 2022 12:53:20 -0000

Zaheduzzaman Sarker 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:


Thanks for working on this useful specification.

I have noted the following which I think needs cross checking to make the
meaning clear, it might be simple oversight or intentional. I would like to
which one is correct.

- Section 4 :
     - any reason why the leaf send_id and recv_id does not use normative
     "MUST" in the description?

     - how should we interpret strongly " RECOMMENDED"? is this a MUST or


I have some minor observations, which we might want to address -

- Section 3.1 : It is not clear to me what is the difference between a "Global
configuration" and "Policies". To me policies can include global configurations
that will valid for all the TCP sessions. So, it is not clear is policy is a
special case of global configuration or vise verse.  Also the term "Global"
here seems ambiguous. I kind of read that as a global variable definition,
still the text need to be clear about the scope of "Global" is self, global to
what context?

- What are we really following when we say "directly following from TCP
standards."? a reference is needed here to understand what is meant here.