[tcpm] Fwd: New Version Notification for draft-ietf-tcpm-rfc793bis-14.txt

Wesley Eddy <wes@mti-systems.com> Tue, 30 July 2019 17:56 UTC

Return-Path: <wes@mti-systems.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 3AACF1201F3 for <tcpm@ietfa.amsl.com>; Tue, 30 Jul 2019 10:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mti-systems-com.20150623.gappssmtp.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 pW72ejEj8eJc for <tcpm@ietfa.amsl.com>; Tue, 30 Jul 2019 10:56:43 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 527171201ED for <tcpm@ietf.org>; Tue, 30 Jul 2019 10:56:43 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id j6so10380345ioa.5 for <tcpm@ietf.org>; Tue, 30 Jul 2019 10:56:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20150623.gappssmtp.com; s=20150623; h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=d0XjghlW4S8XxCoOB3qAFQ/B6P3Pugncgb6Y66/tQSg=; b=yndK57sbu53+2iPraXq5db0nJIndLsS4s5q4niiOVsGIiuH3TYjxot/TxLRDdzLwmv mHqqieaJhgjsGgwmDD8i87YEYCLBVrQvmC/C6mkP3Og8Jb0BF0gyMCSJRCX6cE9PeaaS gk11KIjvmurwV4wCG/SwP/FJIVP8k6r+LWifKQeK9EN0QLXLt7JkuMV/Up9S9SqDRnNq K4vmRkx+caOxkjQp8VgY9VNhlCPtrDIss+jwnx06cJhVFuNsvR3vJcO9JFjC4NSn+37T yV9REm0qWio8qEcjJ5xbXJCFkPSBw7EByTXF+GNpBM7ANUrUUFFlHQiumxCPFS7ZJnqq lmHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=d0XjghlW4S8XxCoOB3qAFQ/B6P3Pugncgb6Y66/tQSg=; b=f+8ClROuYS4TSY8YXyiJ6LmS2XONV0mLiVE3vqr8A5S9qfpF+hecBXjxn3F/mSoLAZ UMBZkqt7Dtjt1LIjOMxpfbLzeNBhPROAWkBSmHdLANFnWAW1UwyO+lfVD2for3Wv//D4 2I+fLJAsfxfL3CcRY63ucRpQp67z5Iwv33GY2W0U7vnO9XCgPoOsULq62Vamr1AX8R54 2Q8n5ELVyTZ5dDY13+36o66mISarwDQ0K327bW0uuvwOJrvyVavOKm+WvMKyPdOlGjpW kH6MBQixlAxECzbD/tQ6D8Qyu1slVZkC45AYqYMwjItS27WL5feBcrKhrh1nGHA8dylb 9D/A==
X-Gm-Message-State: APjAAAWUYqVsAfUPk7U1nWdwI5sQqNLnCKxWtCocRDpZ+IFSi9awXKNO DxkccdsBo1raqzyWogvWORDKa9m7
X-Google-Smtp-Source: APXvYqzflNAU5J9ah6Okfo7EcBv12xFIIPnuVUMWOVLClXQZeMjUuWAVgREHxxWXMIn5hS0uuIHq9w==
X-Received: by 2002:a5e:d618:: with SMTP id w24mr19791417iom.73.1564509402505; Tue, 30 Jul 2019 10:56:42 -0700 (PDT)
Received: from [192.168.1.119] (rrcs-69-135-1-122.central.biz.rr.com. [69.135.1.122]) by smtp.gmail.com with ESMTPSA id e22sm49855080iob.66.2019.07.30.10.56.41 for <tcpm@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jul 2019 10:56:41 -0700 (PDT)
References: <156450882804.14172.17458284787319017749.idtracker@ietfa.amsl.com>
To: tcpm IETF list <tcpm@ietf.org>
From: Wesley Eddy <wes@mti-systems.com>
X-Forwarded-Message-Id: <156450882804.14172.17458284787319017749.idtracker@ietfa.amsl.com>
Message-ID: <10a8eba2-0d55-bd5d-ad22-4884f485a3de@mti-systems.com>
Date: Tue, 30 Jul 2019 13:56:39 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <156450882804.14172.17458284787319017749.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------46C7CFE1476C865BA66146F4"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/G0ALn2ZRc8nFty-f5NzRAiHiYiw>
Subject: [tcpm] Fwd: New Version Notification for draft-ietf-tcpm-rfc793bis-14.txt
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: Tue, 30 Jul 2019 17:56:46 -0000

Hello, this incorporates some small cleanups that accumulated prior to 
the IETF meeting, as well as some of the feedback received since then on 
the mailing list.

A couple specific things not yet done (because it doesn't look like we 
converged on the list yet):

- Did not yet change reserved bits to "unassigned" (nor indicate them in 
the IANA considerations section).  Rod Grimes has a good point about 
these being very commonly referred to as "the reserved bits" in other 
places.  I'm thinking we could add a note to say that in IANA terms 
they're "Unassigned" to add the clarity that Mohamed is advocating, but 
not change the name?

- Did not yet move section 2.1.

- Did not yet remove the note about my confusion on MUST vs SHOULD 
regarding reporting of excessive retransmissions in RFC 1122 (will 
confirm on the mailing list the "no change" proposal that was suggested 
at the meeting)



-------- Forwarded Message --------
Subject: 	New Version Notification for draft-ietf-tcpm-rfc793bis-14.txt
Date: 	Tue, 30 Jul 2019 10:47:08 -0700
From: 	internet-drafts@ietf.org
To: 	Wesley M. Eddy <wes@mti-systems.com>om>, Wesley Eddy 
<wes@mti-systems.com>




A new version of I-D, draft-ietf-tcpm-rfc793bis-14.txt
has been successfully submitted by Wesley M. Eddy and posted to the
IETF repository.

Name: draft-ietf-tcpm-rfc793bis
Revision: 14
Title: Transmission Control Protocol Specification
Document date: 2019-07-30
Group: tcpm
Pages: 104
URL: https://www.ietf.org/internet-drafts/draft-ietf-tcpm-rfc793bis-14.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-tcpm-rfc793bis/
Htmlized: https://tools.ietf.org/html/draft-ietf-tcpm-rfc793bis-14
Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-rfc793bis
Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-tcpm-rfc793bis-14

Abstract:
This document specifies the Internet's Transmission Control Protocol
(TCP). TCP is an important transport layer protocol in the Internet
stack, and has continuously evolved over decades of use and growth of
the Internet. Over this time, a number of changes have been made to
TCP as it was specified in RFC 793, though these have only been
documented in a piecemeal fashion. This document collects and brings
those changes together with the protocol specification from RFC 793.
This document obsoletes RFC 793, as well as 879, 2873, 6093, 6429,
6528, and 6691 that updated parts of RFC 793. It updates RFC 1122,
and should be considered as a replacement for the portions of that
document dealing with TCP requirements. It updates RFC 5961 due to a
small clarification in reset handling while in the SYN-RECEIVED
state.

RFC EDITOR NOTE: If approved for publication as an RFC, this should
be marked additionally as "STD: 7" and replace RFC 793 in that role.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat