Re: [tcpm] WGLC for draft-ietf-tcpm-converters-08

<philip.eardley@bt.com> Tue, 09 July 2019 10:13 UTC

Return-Path: <philip.eardley@bt.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 5CAE41203FC; Tue, 9 Jul 2019 03:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bt.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 JipulWSnOZEf; Tue, 9 Jul 2019 03:13:25 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEA51120401; Tue, 9 Jul 2019 03:13:24 -0700 (PDT)
Received: from tpw09926dag09e.domain1.systemhost.net (10.9.202.36) by BWP09926082.bt.com (10.36.82.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 9 Jul 2019 11:13:22 +0100
Received: from tpw09926dag05f.domain1.systemhost.net (10.9.202.24) by tpw09926dag09e.domain1.systemhost.net (10.9.202.36) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 9 Jul 2019 11:13:22 +0100
Received: from bwp09926085.bt.com (10.36.82.116) by tpw09926dag05f.domain1.systemhost.net (10.9.202.24) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 9 Jul 2019 11:13:22 +0100
Received: from GBR01-LO2-obe.outbound.protection.outlook.com (104.47.21.50) by smtpe1.intersmtp.com (10.36.82.116) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 9 Jul 2019 11:13:13 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bei0Skdoa0cYjwY/BZ2+DKo/9a9kLzKpY2roXjsvM0w=; b=HIVb/8uM0yhzo0Uuj/RRp/AOgdx4dqJYECG/ZqHXEasDqtU5JNQd50Zgy2+melbmmg6Ot7EG84wrQUBB+C/Ls/djcys40QOXOMOqQ4jwkHQtc/nK+iCeK75jf81wAfctSWNRZQsheZMkD74KdGT30yxGUvfczcG5Fg4V4VlQM/U=
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM (20.179.128.78) by LNXP123MB1979.GBRP123.PROD.OUTLOOK.COM (20.179.128.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.18; Tue, 9 Jul 2019 10:12:46 +0000
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::10d8:71fc:f4d3:8074]) by LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::10d8:71fc:f4d3:8074%7]) with mapi id 15.20.2052.020; Tue, 9 Jul 2019 10:12:45 +0000
From: <philip.eardley@bt.com>
To: <mohamed.boucadair@orange.com>, <Michael.Scharf@hs-esslingen.de>, <tcpm@ietf.org>
CC: <tcpm-chairs@ietf.org>
Thread-Topic: WGLC for draft-ietf-tcpm-converters-08
Thread-Index: AdUrckm1sQAV9Sf8TqW1iT6fsU2DwgBZdsDwACyBV3ACLRGJsA==
Date: Tue, 9 Jul 2019 10:12:43 +0000
Message-ID: <LNXP123MB25876DBB83C51976932E5FBCEBF10@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <6EC6417807D9754DA64F3087E2E2E03E2D35AB8E@rznt8114.rznt.rzdir.fht-esslingen.de> <LNXP123MB258781EFAC897351EDB153E2EBFD0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM> <787AE7BB302AE849A7480A190F8B93302EAAF429@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302EAAF429@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com;
x-originating-ip: [193.113.37.9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e69faac5-43b1-4403-b4c1-08d70455fcb5
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:LNXP123MB1979;
x-ms-traffictypediagnostic: LNXP123MB1979:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <LNXP123MB1979B9FA71F3A0099DC2E70DEBF10@LNXP123MB1979.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0093C80C01
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(346002)(376002)(136003)(39860400002)(52314003)(189003)(199004)(76176011)(14444005)(66476007)(64756008)(66446008)(66556008)(14454004)(86362001)(76116006)(66946007)(2201001)(316002)(26005)(110136005)(71190400001)(7696005)(33656002)(6246003)(73956011)(71200400001)(6506007)(2501003)(53936002)(256004)(99286004)(186003)(9686003)(102836004)(5660300002)(55016002)(6116002)(3846002)(6436002)(81156014)(446003)(7736002)(8936002)(6306002)(68736007)(52536014)(81166006)(4326008)(8676002)(229853002)(25786009)(4744005)(305945005)(476003)(66066001)(11346002)(478600001)(486006)(74316002)(2906002)(966005); DIR:OUT; SFP:1101; SCL:1; SRVR:LNXP123MB1979; H:LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: JzCB9PtF9Ujl6KtHdKUmzID1b0AxTWqzyoOIrIrCfA7ULsu3sNDCoD9OmPylMBEAXh8l5MDeZE5luwOTRt1OP34o5iVBTCEp1Q1iu1TNs1jRjDFVH5ZfhikibkkegUgFSWcUaMUEqBBMyeenum8KOSaY1FgPmtbsCVTz3bJa7LJOWg91WIVJGCp77y8+XdO0izLN4KYLVOtKT7X+y4rXGntwU9ZdFOPQUSrcA2/+lDGr4DFDdDUEwx52y712/WTcfHjs2VJH1OLBFr8Z8sNVZr9YJNPsFRhTAUGhqUCQtQCf85Xb4VQUhw67I/y+QMFNzw+Hq6AFgQUDkKR8oj0Co61UdB0zanwcyKWpXkC0eqyaZvhgwbmzWdLkMbHkQFQ7Oi0p7WTviFTIYGg9uHHB+kReV25vv3/JdK0IhpWbf+0=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e69faac5-43b1-4403-b4c1-08d70455fcb5
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2019 10:12:44.3608 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: philip.eardley@bt.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXP123MB1979
X-NAI-Spam-Flag: NO
X-NAI-Spam-Level: **
X-NAI-Spam-Threshold: 5
X-NAI-Spam-Score: 2
X-NAI-Spam-Report: 9 Rules triggered * 1 -- SJEY_DJEPYSY_W_SORT_LNK_1HTP_CTPLN * 0.5 -- SJEY_DJEPYSY * 0.2 -- SORT_LNK_1HTP_CTPLN * 0.1 -- GEN_SPAM_FEATRE * 0.1 -- SORT_LNK_1HTP_CTPLN_W_GEN_SPAM_FEATRE * 0.1 -- THREAD_INDX_INVALD_VAL * 0 -- EDT_SDHA_ADR_FRG * 0 -- EDT_SDHA_DMN_FRG * 0 -- RV6585
X-NAI-Spam-Version: 2.2.0.9309 : core <6585> : inlines <7115> : streams <1826840> : uri <2865511>
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/0959Zm7TsTnshsqVkch8_aCVEF4>
Subject: Re: [tcpm] WGLC for draft-ietf-tcpm-converters-08
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, 09 Jul 2019 10:13:28 -0000

> 
> I think it would be great if Section 3 was expanded into a "protocol 
> model" https://tools.ietf.org/html/rfc4101 in particular to expand on

[Med] Section 3 is purposely edited "to quickly grasp the essence of" the convert protocol. It focuses on the main design rationale that is use one single SYN to supply data to a converter. That supplied data is unambiguously distinguished by means of TLVs and location within the payload.  

[phil] that's exactly the purpose of a protocol model. The full protocol description is just for people who need to understand the details, implementers etc.
Anyway, I leave you to think about it and edit as you feel best.