Re: [drinks] "Substrate Protocol" instead of "Transport Protocol"

"Cartwright, Ken" <> Fri, 15 May 2015 15:03 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 602B61A00E4 for <>; Fri, 15 May 2015 08:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 34WB7daveMrr for <>; Fri, 15 May 2015 08:03:05 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 989C61A0010 for <>; Fri, 15 May 2015 08:03:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=tnsi; t=1431705929; x=1463241929; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ghGdqVi6WnNShvFT1938/v/6VBfybvpiFooCMnhwKHU=; b=TZ+8lm6DMzC9DAxcQ1IxbJBAD73SFMZoVG5xTma9VpZxGb+pVNjNOME7 a3ZfY2TbY0VI9wgJmfUFskcBrKt4E+RRx1G6MFS1a4Kx4DvXIOQpnE5ha CkjIpPOA3Jf4VrlLJ+Mt5RtR3YsXMkZVfa+QOUwYhLW5Et9ZOIQt1LE7J P3b2Mw47qbbf2Bs/WDSEe6bzzK56UShFBkd+HchZ57lXY4g8h75jfjp1d tCO5t+8i5W8WQ6pZ+PGX/fTzEBVaeN+S+EbLv+jD81ooJw87De+URw7Pb IfTXJghe4JEvQ4OpZPs0V8Nzz0me1U7MNjn3zVqjYcrBhDNyLze+qzf6E w==;
Authentication-Results:; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.13,434,1427756400"; d="scan'208";a="4669088"
Received: from unknown (HELO ([]) by with ESMTP/TLS/AES256-SHA; 15 May 2015 17:05:28 +0100
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1044.25; Fri, 15 May 2015 16:03:03 +0100
Received: from ([fe80::f1b8:5d9c:79d4:7f09]) by ([fe80::f1b8:5d9c:79d4:7f09%16]) with mapi id 15.00.1044.021; Fri, 15 May 2015 16:03:03 +0100
From: "Cartwright, Ken" <>
To: Alexander Mayrhofer <>, "" <>
Thread-Topic: "Substrate Protocol" instead of "Transport Protocol"
Thread-Index: AdCPHicMj7vAewJlS6W44FhadFoixwAAgPNQ
Date: Fri, 15 May 2015 15:03:02 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US, en-GB
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [drinks] "Substrate Protocol" instead of "Transport Protocol"
X-Mailman-Version: 2.1.15
Precedence: list
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 15 May 2015 15:03:08 -0000

Sound like a good point and a good solution.

+1 from me.

-----Original Message-----
From: drinks [] On Behalf Of Alexander Mayrhofer
Sent: Friday, May 15, 2015 10:55 AM
Subject: [drinks] "Substrate Protocol" instead of "Transport Protocol"


I'm currently working through the remaining COMMENTs and "near-DISCUSSes" on our documents, specifically the Framework document:

There was some significant concern about the use of the term "Transport" for an above-layer-4-protocol, sepcifically by Spencer and Martin. Spencer provided a compromise text, while Martin strongly leans towards changing our terminology. As Spencer wrote, the term "Substrate" could be used  instead of "Transport".

The SOAP document contains 24 instances of the word "transport", while the framework document contains 54 instances. Therefore, i think it would be reasonable effort to switch to "Substrate", and that would adress both Spencer's as well as Martin's comments.



drinks mailing list


This e-mail message is for the sole use of the intended recipient(s)and may
contain confidential and privileged information of Transaction Network Services.
Any unauthorized review, use, disclosure or distribution is prohibited. If you
are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.