Re: [tcpm] draft-eggert-tcpm-historicize-00

"Scheffenegger, Richard" <rs@netapp.com> Fri, 25 June 2010 15:07 UTC

Return-Path: <rs@netapp.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C212828C0F4 for <tcpm@core3.amsl.com>; Fri, 25 Jun 2010 08:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.556
X-Spam-Level:
X-Spam-Status: No, score=-4.556 tagged_above=-999 required=5 tests=[AWL=-0.557, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1tGDsPE3SVw1 for <tcpm@core3.amsl.com>; Fri, 25 Jun 2010 08:07:58 -0700 (PDT)
Received: from mx3.netapp.com (mx3.netapp.com [217.70.210.9]) by core3.amsl.com (Postfix) with ESMTP id 5F9093A6784 for <tcpm@ietf.org>; Fri, 25 Jun 2010 08:07:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,481,1272870000"; d="scan'208";a="167002390"
Received: from smtp3.europe.netapp.com ([10.64.2.67]) by mx3-out.netapp.com with ESMTP; 25 Jun 2010 08:08:05 -0700
Received: from amsrsexc1-prd.hq.netapp.com (webmail.europe.netapp.com [10.64.251.107]) by smtp3.europe.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id o5PF4tIL004136; Fri, 25 Jun 2010 08:07:28 -0700 (PDT)
Received: from LDCMVEXC1-PRD.hq.netapp.com ([10.65.251.107]) by amsrsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 25 Jun 2010 17:07:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 Jun 2010 16:07:12 +0100
Message-ID: <5FDC413D5FA246468C200652D63E627A0935F804@LDCMVEXC1-PRD.hq.netapp.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC580A0CE306@xmb-sjc-21c.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] draft-eggert-tcpm-historicize-00
Thread-Index: AcsTaELvChlaGVTORWuANEwU7pfW3QAWo8PAAAGP6oAAKxw48A==
References: <20100609151532.8E75E28C0D0@core3.amsl.com><33D3BDE9-7E8D-4DF0-B8D5-BFFC66CF9C99@nokia.com><2262C708-DF9A-4DD9-9378-D84C5AF330AC@nokia.com><C304DB494AC0C04C87C6A6E2FF5603DB48105A5A82@NDJSSCC01.ndc.nasa.gov> <0C53DCFB700D144284A584F54711EC580A0CE306@xmb-sjc-21c.amer.cisco.com>
From: "Scheffenegger, Richard" <rs@netapp.com>
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>, "Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov>, "Lars Eggert" <lars.eggert@nokia.com>, <tcpm@ietf.org>
X-OriginalArrivalTime: 25 Jun 2010 15:07:14.0360 (UTC) FILETIME=[18206B80:01CB1478]
Cc: "Biswas, Anumita" <Anumita.Biswas@netapp.com>
Subject: Re: [tcpm] draft-eggert-tcpm-historicize-00
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 25 Jun 2010 15:07:59 -0000

Anantha,

I think for purposes of documenting "legacy" implementations, the
RFC1146 would still be valid.

I will try to define the goal of that recent proposal again, at least as
far as I understand this, so that we are all on the same page here.

Our expirience has shown, that TCP often runs over links with much
higher error rates, than intended for the technology (ie. Design goal of
BER <= 1E-12 over Ethernet often has an actual BER >> 1E-12). If such
error-prone links are running at a high speed and with large segment
sizes (jumbo / giant frames), there exists the real problem that within
a short timeframe (weeks to months), TCP will deliver corrupted data, as
CRC-16 was not able to catch the error.

>From my point of view, I understood the recent discussions around
RFC1146 in such a way, that for the intended purpose, which is to
provide a stronger payload checksum (equivalent to SCTP levels), a new
option would be required rather than reusing the alternate checksum
option. The reasoning is that currently deployed gear, especially NAT /
PAT gateways - which have to re-calculate the TCP Checksum as the
Pseudo-Header is changed - might know about the originally defined
alternate checksum algorithms, but not the new ones.

Furthermore, RFC1146 specifically requires the Pseudo Header to be
included - which one wouldn't want to do if only payload CRC is
required.

Providing a Payload-only CRC (ie. as the first TCP option), would enable
the transparent forwarding of such a new option by NAT/PAT gateways
without any problems.


Of course, if RFC1146 could be extended to include algorithms which
actually "violate" some of the specs of it, but maintain using the same
TCP options with a new algorithm codepoint, that would be fine with me.

But this would probably ask for a new RFC obsoliting RFC1146 anyway (in
effect making it again historic :) ).


Does that make sense?

Thanks for your comments!

Richard



> -----Original Message-----
> From: Anantha Ramaiah (ananth) [mailto:ananth@cisco.com] 
> Sent: Donnerstag, 24. Juni 2010 20:17
> To: Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]; Lars 
> Eggert; tcpm@ietf.org
> Subject: Re: [tcpm] draft-eggert-tcpm-historicize-00
> 
> I have already communicated earlier that the TCP alternate 
> checksum option needs to be removed from this list. Reason 
> being it is still being used and there are proposals out 
> there that is trying to make use of this option. Other than 
> that point I am fine with this draft moving forward.
> 
> -Anantha
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
>