IETF Logo Mail Archive

Re: [tcpm] draft-tcpm-fastopen: interaction with ECN

"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Fri, 11 April 2014 17:43 UTC

Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63E951A0736 for <tcpm@ietfa.amsl.com>; Fri, 11 Apr 2014 10:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 pOAFdC9Stlqf for <tcpm@ietfa.amsl.com>; Fri, 11 Apr 2014 10:43:07 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2261A0731 for <tcpm@ietf.org>; Fri, 11 Apr 2014 10:43:07 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s3BHgxOm025064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 11 Apr 2014 12:43:00 -0500 (CDT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s3BHgwY9027417 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 11 Apr 2014 19:42:58 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.94]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Fri, 11 Apr 2014 19:42:58 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Bob Briscoe <bob.briscoe@bt.com>, "ycheng@google.com" <ycheng@google.com>
Thread-Topic: [tcpm] draft-tcpm-fastopen: interaction with ECN
Thread-Index: AQHPVNZJKcdbbfIVAEGt+UXS/0V9V5sMq2nw
Date: Fri, 11 Apr 2014 17:42:57 +0000
Message-ID: <655C07320163294895BBADA28372AF5D2A2684@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <201404101602.s3AG28nH001717@bagheera.jungle.bt.co.uk>
In-Reply-To: <201404101602.s3AG28nH001717@bagheera.jungle.bt.co.uk>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tcpm/O__SejIVJ8f6YGf4uwYlkNPhAGc
Cc: "draft-tcpm-fastopen@tools.ietf.org" <draft-tcpm-fastopen@tools.ietf.org>, tcpm IETF list <tcpm@ietf.org>
Subject: Re: [tcpm] draft-tcpm-fastopen: interaction with ECN
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
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: <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, 11 Apr 2014 17:43:09 -0000

Bob,

Indeed, the WGLC for draft-tcpm-fastopen has completed... I am about to forward the document to the AD.

Apparently, right now, draft-tcpm-fastopen does not comment on ECN at all, and I am not aware of any past discussion in TCPM.

Thus, my initial thinking would be that if ECN should be addressed in this document, it could be mentioned in section 7 as a topic for further experimentation - instead of adding normative text late in the process. 

Thoughts from the community (and the authors) would be welcome - but please recall that we are really past WGLC and I'd like to move the document forward within the next couple of days.

Michael



> -----Original Message-----
> From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Bob Briscoe
> Sent: Thursday, April 10, 2014 6:02 PM
> To: ycheng@google.com
> Cc: draft-tcpm-fastopen@tools.ietf.org; tcpm IETF list
> Subject: [tcpm] draft-tcpm-fastopen: interaction with ECN
> 
> Yuchung,
> 
> In draft-tcpm-fastopen, you may be able to get away with saying
> nothing about this, but..
> 
> 1) Just in case someone thinks it would be clever for a TFO client to
> resume use of ECN on a subsequent SYN, it may be best to clarify that:
> "TFO does not allow a subsequent connection to reuse the ECN
> capability negotiated in a previous connection. If TCP endpoints
> negotiate the use of ECN, they MUST apply the initialization rules
> (Section 6.1.1 of [RFC3168]) separately for each connection."
> 
> 
> 2) You might also want to recommend using RFC 5562 (ECN on SYN-ACK),
> just to give developers a tick-list of RFCs to use. However, if you
> plan to quickly move TFO on from experimental status, make sure you
> just say this 'for information', rather than as a normative
> reference, because 5562 is experimental.
> 
> 
> 
> I know this is my second comment after WGLC, but I thought it best to
> say something. (I was just getting the capability negotiation logic
> in Accurate ECN to interwork with TFO, when I realised this issue
> applied to classic ECN too.)
> 
> 
> Bob
> 
> 
> ________________________________________________________________
> Bob Briscoe,                                                  BT
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm

v2.23.0 | Report a Bug | By Email