IETF Logo Mail Archive

Re: [tsvwg] Protocol ossification in draft-ietf-tsvwg-transport-encrypt-07.txt

Joe Touch <touch@strayalpha.com> Tue, 09 July 2019 04:35 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E34CB12023F for <tsvwg@ietfa.amsl.com>; Mon, 8 Jul 2019 21:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.218
X-Spam-Level:
X-Spam-Status: No, score=-1.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 e8hLZKLYcgn6 for <tsvwg@ietfa.amsl.com>; Mon, 8 Jul 2019 21:35:56 -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 F2CB01200FD for <tsvwg@ietf.org>; Mon, 8 Jul 2019 21:35:55 -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: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=vn+H7RuLnVmY8wnoW8oz8JWr3qdPgdmP/3qbLd29C7w=; b=APNkdiEdd/XyvkLexNCPEhTix hmR2FL04bohFD+BpZINDkdfXsHNPoiwy+EC42pbbZNRb2zeG+Rtgzk5HOJoNDRmon2XVyxQgu41O3 sdtaGZqCrBITaZO7COMlDawb2KoYOBIYQUm+mORtuhf5+Vjxo4YyFLMyVdBOqTI1NqIWtoQM6xa4J lZybc1kCH16J7iAOWzvXJRLDpLn1xRY4Q5996g1q8pAun2W/AGTn4JtS4ozg0wnZGhO9Wqp/jIxC8 0UDKbAjMYdJTtF7wRIogXKjafRpqcey0A//PgcvkpYpnyFebgZKVsSEs5A5iHFwI/XfrZAqVMia9p KKQcy6w/g==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:49950 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1hkhr1-002pyO-NE; Tue, 09 Jul 2019 00:35:52 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_7046E967-F2A5-43B8-8074-6E5D495FD79B"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <CALx6S36-WfCs_BW5iGQzoZHq6HBsLMyEDagkMOmg8VgvEWWeew@mail.gmail.com>
Date: Mon, 08 Jul 2019 21:35:46 -0700
Cc: tsvwg <tsvwg@ietf.org>
Message-Id: <21E819F0-77A1-496C-9B3A-6EF9A8678D5D@strayalpha.com>
References: <CALx6S36-WfCs_BW5iGQzoZHq6HBsLMyEDagkMOmg8VgvEWWeew@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
X-Mailer: Apple Mail (2.3445.9.1)
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/tsvwg/7OVpPmFedM34JbO8qiXSTY5S5tY>
Subject: Re: [tsvwg] Protocol ossification in draft-ietf-tsvwg-transport-encrypt-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2019 04:35:58 -0000


> On Jul 8, 2019, at 8:05 AM, Tom Herbert <tom@herbertland.com> wrote:
> 
> "A reliance on the presence and semantics of specific header
> information  leads to ossification…"


Relying on the semantics of a protocol header is also called a standard. 

> “...In some case this could be benign or advantageous to
> the protocol”

> I am dubious about any statement that protocol ossification of
> transport layer by middleboxes is a good thing.


Ossification and stability are two sides of exactly the same coin.

It’s called ossification when the variation of a standard is no longer supported, e.g., because of middleboxes assumptions beyond that defined by the standard.

It’s called stability when we can rely on a set of definitions that constrain arbitrary variation in controlled ways.

Joe

v2.23.0 | Report a Bug | By Email