Re: [tcpm] WGLC for draft-ietf-tcpm-2140bis

Joseph Touch <touch@strayalpha.com> Fri, 19 June 2020 18:40 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F34E93A0D7C; Fri, 19 Jun 2020 11:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
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 Cqm5Mq5-Jadc; Fri, 19 Jun 2020 11:40:21 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 3EF193A0D41; Fri, 19 Jun 2020 11:40:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=58lj725iKwg4nLxZVIleC/sor3aZUdrhGZNVF1BeAJg=; b=Ox/Wjh68u0997nF7bAhNaJBPa t+l/A/quWwa/6WIfuea9ZQy4ZHN2fKHcQWmc+25k6beuFUfGhuXNnkhS9jkr0SpfFPSV8DDPr28L6 CZaQL5SYqnxu/Hsb8iMecp9AKwt7fxMWxaP4nDnHQqEtysD4XB3rqQQ81RO27Kf3Bvc3oskh0LCeB J2ZGyHWQqtBYfdt8pxDF6fMfwly4wwTfU5CE/932gmfR25EzY3CpJslh3iF1j65rlPIfYCJhwl1p2 XlrWalqbwOUvwQ03EkSjXyx0K6JovXX6tGKdtj7duVbUlowbUtP7TxPQUlHhEnouNeE0YPT1GvUgt Urx2GFJ+g==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:57357 helo=[192.168.1.14]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <touch@strayalpha.com>) id 1jmLw0-002Ams-6p; Fri, 19 Jun 2020 14:40:20 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <B23F3B99-8712-4106-9CFB-16176C572A1F@ericsson.com>
Date: Fri, 19 Jun 2020 11:40:15 -0700
Cc: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>, "tcpm@ietf.org" <tcpm@ietf.org>, tcpm-chairs <tcpm-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7840A9F4-48C7-4C41-8464-DB92A086F7A5@strayalpha.com>
References: <B23F3B99-8712-4106-9CFB-16176C572A1F@ericsson.com>
To: Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/_fzoB9AtTTww1kerK77Hz5ORWbM>
Subject: Re: [tcpm] WGLC for draft-ietf-tcpm-2140bis
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Fri, 19 Jun 2020 18:40:34 -0000

Hi, Mirja,

> On Jun 19, 2020, at 11:31 AM, Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org> wrote:
> 
> Hi Michael, hi all,
> 
> sorry for being late here but times are busy... so thanks for the extension.
> 
> Thanks to the authors for all the work on this bis doc. I only managed to have a brief review of the draft but I think it an interesting read with a lot of good updates. I think the document is basically ready for publication, however, I have two comments/questions. tThe first one is more a suggestion but the second point is something I think we should be should we have support for in the group before we move ahead.
> 
> 1) The security section could maybe also discuss if there are any implications for likability when caching any of these information and how to handle that. Looking at the diff, there was a section in the security consideration about information sharing of application-specific settings. So why was that removed? However, I think the document could even say more!
> 
> 2) I was quite surprised to see appendix C and that it is a FULL copy of draft-touch-tcpm-automatic-iw-03. I'm okay to discuss more considerations on the IW e.g. on the design principle level and most importantly maybe that a loss within the IW can/should impacting the cached value, and to do so even in the body of the doc, however, if I remember correctly there was a lot of discussion about the automated setting of IW in tcpm when the IW10 RFC was under discussion and no agreement reached in the group, so would rather just like to see a reference to the expired draft than copy and pasting the whole algorithm in the appendix of this draft.

The discussion was only whether there were specific settings that had been implemented. If we cite an expired draft, we need to basically add some info to explain what’s in the other doc (which we are supposed to treat as non-existent). I.e., if we’re citing an old draft for credit, it’s just a citation, but in this case we’re saying that the techniques in that draft *are* just a variant of what 2140 already suggests, only on a different timescale.

I.e., “discussing more considerations” is basically what that text already does. All the issues that are in the original doc were relevant for this one’s discussion on that issue.

Joe