Re: [ippm] Benjamin Kaduk's No Objection on draft-ietf-ippm-twamp-yang-11: (with COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Wed, 20 June 2018 19:19 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF9E13109F; Wed, 20 Jun 2018 12:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 69In3MXTPrZO; Wed, 20 Jun 2018 12:19:33 -0700 (PDT)
Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 E07101310AB; Wed, 20 Jun 2018 12:19:32 -0700 (PDT)
X-AuditID: 12074423-837ff70000007876-85-5b2aa8c30dae
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 98.B1.30838.3C8AA2B5; Wed, 20 Jun 2018 15:19:31 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id w5KJJU3v006705; Wed, 20 Jun 2018 15:19:31 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w5KJJPic021158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 20 Jun 2018 15:19:28 -0400
Date: Wed, 20 Jun 2018 14:19:25 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: "MORTON, ALFRED C (AL)" <acm@research.att.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-ippm-twamp-yang@ietf.org" <draft-ietf-ippm-twamp-yang@ietf.org>, Nalini Elkins <nalini.elkins@insidethestack.com>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
Message-ID: <20180620191925.GK4946@kduck.kaduk.org>
References: <152933869439.3647.15290297683322606646.idtracker@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CF4A92DDA6@njmtexg4.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CF4A92DDA6@njmtexg4.research.att.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmleLIzCtJLcpLzFFi42IRYrdT1z28Qiva4O55a4u+Q7MZLW4daWC0 mPFnIrPF6h3dbBY9D94xW3w+eYnRgc1jyZKfTB5bZtxi8vj/ZD5LAHMUl01Kak5mWWqRvl0C V0b3AfWCnfwVSxeeZG9gXMfTxcjJISFgInHsy3n2LkYuDiGBxUwS/65dZIFwNjJKnL12lBmk SkjgKpPEzi3cIDaLgKrEq68tLCA2m4CKREP3ZbAaEQEjibl75oA1Mwv0M0m0H28FGsvBISwQ KzFvElgvr4CxxIF905ghFkxhlFj8dgELREJQ4uTMJ2A2s4CWxI1/L5lAepkFpCWW/+MACXMK BEr0/1gBtktUQFlib98h9gmMArOQdM9C0j0LoXsBI/MqRtmU3Crd3MTMnOLUZN3i5MS8vNQi XTO93MwSvdSU0k2M4LB2Ud7B+LLP+xCjAAejEg/vjTCtaCHWxLLiytxDjJIcTEqivPw1QCG+ pPyUyozE4oz4otKc1OJDjBIczEoivGtmA+V4UxIrq1KL8mFS0hwsSuK8OYsYo4UE0hNLUrNT UwtSi2CyMhwcShK8J5YDNQoWpaanVqRl5pQgpJk4OEGG8wANj1wBMry4IDG3ODMdIn+KUVFK nLcQpFkAJJFRmgfXC0o7Etn7a14xigO9IszrA1LFA0xZcN2vgAYzAQ2ubgYbXJKIkJJqYHRr sv33JdKyf/r32V3GE3ab3nu9ze5ExJYJGreLpZa5G18ziilr0n9q1h709oDDlVl+7mvvn+mQ YlXdnuEndMbCdVZz3cVdU7rVPJYkr5tv+f9fVfHxHyUP07f0Kn30W6s6V7gjL1Lq8ibF9CMc q/44PS74WOr4lM3cu+hDxOc7hqv6LlyLCVNiKc5INNRiLipOBACTNOkqFgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/0a9aBZ3d_00A0ByyP1I71pqc1A8>
Subject: Re: [ippm] Benjamin Kaduk's No Objection on draft-ietf-ippm-twamp-yang-11: (with COMMENT)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2018 19:19:35 -0000

Hi Al,

On Tue, Jun 19, 2018 at 08:06:55PM +0000, MORTON, ALFRED C (AL) wrote:
> Hi Ben,
> 
> Just looking at your first comment for now:
> > 
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> > 
> > Perhaps I am confused and/or misreading things, but the descriptions
> > of the control-client and session-reflector include discussion of
> > 'sid' session identifiers as if they were always used, but the mode
> > bitmap includes a separate bit for negotiation of
> > 'individual-session-control' for session identifier usage.  Is there
> > some conflict between this mandatory/negotiable distinction, or are
> > they actually talking about different things?
> [acm] 
> 
> Yes, there is a small amount of confusion, easily 
> rectified I think.
> 
> All test sessions are assigned Session IDs (SIDs).
> Each SID is assigned during the session setup phase of operation.
> 
> All test sessions START and STOP with the those commands,
> *unless* the individual-session-control feature has been negotiated:
> 
>    [RFC5938] ... describes an OPTIONAL feature for TWAMP.  [RFC5357] TWAMP
>    (and OWAMP) start all previously requested and accepted test sessions
>    at once.  This feature allows the Control-Client to control
>    individual test sessions on the basis of their Session Identifier
>    (SID).  This feature permits a short-duration TWAMP test to start
>    (and/or stop) during a longer test.  This feature permits a specific
>    diagnostic test to begin if intermediate results indicate that the
>    test is warranted, for example.
> 
> Let us know if there is specific text you would like to modify,
> to avoid any confusion...

Thanks for the explanation.  I don't see any need to modify the text;
someone who actually pulls the references has a clear picture of what's
going on as-is.

-Benjamin