IETF Logo Mail Archive

Re: [tcpm] Moving forward draft-touch-sne on independent stream?

"touch@strayalpha.com" <touch@strayalpha.com> Mon, 29 November 2021 21:30 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 556643A0A1E; Mon, 29 Nov 2021 13:30:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level:
X-Spam-Status: No, score=-1.318 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, HTML_MESSAGE=0.001, 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 sKZYHeSU0sf8; Mon, 29 Nov 2021 13:30:16 -0800 (PST)
Received: from server217-1.web-hosting.com (server217-1.web-hosting.com [198.54.114.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 F17C73A0A05; Mon, 29 Nov 2021 13:30:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding: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=Ihhtr8yrsWT3QmXGFZGoydnrMKN3uvFV3im4cqIzedE=; b=aqs9xeKDkzqkpzrkmFNtZwEBUz QwFT6NgT16CtsxUr4NfnQiHvkyqwacoc+CD6gXwPIRB9vqn9tRLvHG+w4i52x8wzUTYH/mMoQc/05 LWqPrHy86v2QjyvNDgH67fSa7NLqvtF4d/vMeYfaFSxUl4BojFsqf7vvpWLg3+LSN+5zSIz1Vjsn1 Rs/OimsdHLc7xAHjYFzMBoO5RaqPcx0cVGeD7/FIKPWtKfDo10UFYh+LV22B+kX3wHoYTZaXhp2G4 pPpAgzNmBWw8kRg/Q1I8aETqcc80feAjbAkN02YkfckKHzWeBJRKYkQ3m61R1eZEuutuHdF4a0Etx idy4zEuA==;
Received: from cpe-172-114-237-88.socal.res.rr.com ([172.114.237.88]:64674 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <touch@strayalpha.com>) id 1mroDy-00CSEF-1t; Mon, 29 Nov 2021 16:30:14 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_416F7F20-E2B9-4E42-81D2-AB60921C2932"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <CAAK044QNMxToQ_ZJVKhSbtje0SvpKJkvcyw9L8-_D1asJ1hPhQ@mail.gmail.com>
Date: Mon, 29 Nov 2021 13:30:07 -0800
Cc: Martin Duke <martin.h.duke@gmail.com>, "tcpm@ietf.org" <tcpm@ietf.org>, "tcpm-chairs@ietf.org" <tcpm-chairs@ietf.org>
Message-Id: <FAC88164-7B97-4989-9E9C-21DEEC5387E4@strayalpha.com>
References: <8de93237209d4fc7ab062bbc24217999@hs-esslingen.de> <CAM4esxSKH_QTsVb5-nLOxVY3_f8-=wxhhutrkdWR2btH0njciA@mail.gmail.com> <CAAK044QNMxToQ_ZJVKhSbtje0SvpKJkvcyw9L8-_D1asJ1hPhQ@mail.gmail.com>
To: Yoshifumi Nishida <nsd.ietf@gmail.com>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
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/rpzxr8j3C1ue4NZy1YVdKQpygB0>
Subject: Re: [tcpm] Moving forward draft-touch-sne on independent stream?
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: Mon, 29 Nov 2021 21:30:22 -0000

Yoshi,

I believe you are referring to draft-touch-tcpm-tcp-syn-ext-opt; I am awaiting WG decision on having that doc become an experimental WG doc.

The query below is for the sequence number extension solution that primarily affects TCP-AO option implementations and other such uses of sequence numbers. The two docs are not related.

The sequence number extension is example code; it need not be a standard.

Joe

—
Joe Touch, temporal epistemologist
www.strayalpha.com

> On Nov 29, 2021, at 12:28 PM, Yoshifumi Nishida <nsd.ietf@gmail.com> wrote:
> 
> Hi Martin,
> 
> This is just my opinion as an individual contributor.
> I prefer to discuss this draft in the WG more rather than publishing it as an IS.
> I think SYN option space extension is an important feature for TCP's future, so I think it would be better to have a standardized solution for it.
> Also, I don't see strong benefits to publish it for now.
> --
> Yoshi
> 
> On Mon, Nov 29, 2021 at 11:29 AM Martin Duke <martin.h.duke@gmail.com <mailto:martin.h.duke@gmail.com>> wrote:
> The conflict review is now in my inbox, and we will discuss it on December 2nd. If there are any concerns about this, please say so immediately.
> 
> On Tue, Jul 6, 2021 at 1:05 PM Scharf, Michael <Michael.Scharf@hs-esslingen.de <mailto:Michael.Scharf@hs-esslingen.de>> wrote:
> Hi all,
> 
> Joe has submitted draft-touch-sne to the ISE asking for publication of an RFC on the Independent Stream. (Background: An RFC on Independent Stream is not an IETF standard.)
> 
> Publication on independent stream would be possible provided that the document does not conflict with TCPM or other IETF work. An obvious alternative would be homing the document in TCPM (or TSVWG) as an official WG item - but this is not what is currently proposed.
> 
> A link to the document is:
> 
> https://datatracker.ietf.org/doc/html/draft-touch-sne <https://datatracker.ietf.org/doc/html/draft-touch-sne>
> 
> Note that the current header field "TCPM" would have to be replaced in the further publication process, as documents on the independent stream are not the outcome of an IETF WG.
> 
> The TCPM chairs have reviewed draft-touch-sne. Our current understanding that there would be no harm caused by such an independent stream publication. As far as RFC 5925 is affected, we assume that an Errata would be possible and sufficient.
> 
> Before we get back to the ISE regarding this document, we would like to cross-check whether our understanding is indeed the TCPM consensus:
> 
> Are there any concerns inside the TCPM community regarding a publication of draft-touch-sne draft-touch-sne on independent stream? If so, please speak up!
> 
> Thanks
> 
> Michael
> on behalf of all chairs
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org <mailto:tcpm@ietf.org>
> https://www.ietf.org/mailman/listinfo/tcpm <https://www.ietf.org/mailman/listinfo/tcpm>
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm

v2.23.0 | Report a Bug | By Email