Re: [tcpm] TCP Long Options - Why not as payload in SYNs?
"Adam Langley" <agl@imperialviolet.org> Mon, 14 July 2008 16:15 UTC
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8CB13A6B24; Mon, 14 Jul 2008 09:15:40 -0700 (PDT)
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 C76FA28C155 for <tcpm@core3.amsl.com>; Mon, 14 Jul 2008 09:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 3Yfj0ocOdMLY for <tcpm@core3.amsl.com>; Mon, 14 Jul 2008 09:15:39 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by core3.amsl.com (Postfix) with ESMTP id DA5313A6B54 for <tcpm@ietf.org>; Mon, 14 Jul 2008 09:15:38 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so4323449rvf.49 for <tcpm@ietf.org>; Mon, 14 Jul 2008 09:16:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=KAFERiCT1SQfAzLjmIyKY9HfmQTiW+Cm3dZLT0HJABw=; b=AJjrAZvcIctcL8HpiPntUrYJCqDNSfYo4BnDYEFqJCn4gbUun9wJB4LZWUedjEyM9g G1UjTjmOLI3362wngsm5YGXNclVPeDKrgVW1SozGGFn9rJDBF4kS90axLEDn9iC2CZhJ vl3jio+7O+llNZb33wEo1OS1PTlyiJpjv1bGo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=nldas/r6+o9RC1EJ+gfsJnS/EUBtN4YlXcjpSEjV9zbMhqe21LzTNQOT+cqRfqhktd Xkl3T875h4YsEtC48Y6arlamDOb1sj1RKF+JcYrisc5KtA7v60ZhAc8b8Sc5vwvCW/p4 sD2NFjZtTgQ4O3IO+hFKVtmCY3pHkTubxMNNM=
Received: by 10.141.78.14 with SMTP id f14mr6705975rvl.119.1216052164653; Mon, 14 Jul 2008 09:16:04 -0700 (PDT)
Received: by 10.141.186.3 with HTTP; Mon, 14 Jul 2008 09:16:04 -0700 (PDT)
Message-ID: <396556a20807140916h63312209m5c4a21f5c3c272a7@mail.gmail.com>
Date: Mon, 14 Jul 2008 09:16:04 -0700
From: Adam Langley <agl@imperialviolet.org>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <487B6A79.2040608@isi.edu>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080714121424.GA31382@ikr.uni-stuttgart.de> <396556a20807140648lb5f923x478665473667d807@mail.gmail.com> <487B6A79.2040608@isi.edu>
X-Google-Sender-Auth: 5214dfdd22eae872
Cc: andre.zuquete@ua.pt, tcpm@ietf.org, Sérgio Freire <sergio-s-freire@ptinovacao.pt>
Subject: Re: [tcpm] TCP Long Options - Why not as payload in SYNs?
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: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org
On Mon, Jul 14, 2008 at 8:02 AM, Joe Touch <touch@isi.edu> wrote: > AFAICT, ACKing the SYN and not the data is compliant, but rejecting the SYN > entirely doesn't appear to be - it should be called a bug, IMO. Sorry, that was written too early in the morning. The problematic cases, of course, are where the host ignores a SYN with a payload, and where it accepts such data as application level data. A host which ACKed the SYN and ignored the payload provides for easy backwards compatibility. AGL -- Adam Langley agl@imperialviolet.org http://www.imperialviolet.org _______________________________________________ tcpm mailing list tcpm@ietf.org https://www.ietf.org/mailman/listinfo/tcpm
- [tcpm] TCP Long Options - Why not as payload in S… Michael Scharf
- Re: [tcpm] TCP Long Options - Why not as payload … Adam Langley
- Re: [tcpm] TCP Long Options - Why not as payload … Joe Touch
- Re: [tcpm] TCP Long Options - Why not as payload … Michael Scharf
- Re: [tcpm] TCP Long Options - Why not as payload … Joe Touch
- Re: [tcpm] TCP Long Options - Why not as payload … Adam Langley
- Re: [tcpm] TCP Long Options - Why not as payload … Caitlin Bestler
- Re: [tcpm] TCP Long Options - Why not as payload … Joe Touch
- Re: [tcpm] TCP Long Options - Why not as payload … Joe Touch
- Re: [tcpm] TCP Long Options - Why not as payload … Joe Touch
- Re: [tcpm] TCP Long Options - Why not as payload … Christian Huitema
- Re: [tcpm] TCP Long Options - Why not as payload … Sergio Freire
- Re: [tcpm] TCP Long Options - Why not as payload … Joe Touch
- Re: [tcpm] TCP Long Options - Why not as payload … Adam Langley
- Re: [tcpm] TCP Long Options - Why not as payload … Joe Touch