Re: [tcpm] draft-ietf-tcpm-urgent-data-06
Ronald Bonica <rbonica@juniper.net> Fri, 15 October 2010 21:07 UTC
Return-Path: <rbonica@juniper.net>
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 DEDCE3A6AF4 for <tcpm@core3.amsl.com>; Fri, 15 Oct 2010 14:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.492
X-Spam-Level:
X-Spam-Status: No, score=-106.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 f7CYHO3oxZQX for <tcpm@core3.amsl.com>; Fri, 15 Oct 2010 14:07:47 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by core3.amsl.com (Postfix) with ESMTP id 8F9F83A6BCC for <tcpm@ietf.org>; Fri, 15 Oct 2010 14:07:47 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKTLjC5rbQBwKbXn4aWAosMjeE7RlNqLF8@postini.com; Fri, 15 Oct 2010 14:09:10 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 15 Oct 2010 14:07:27 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 15 Oct 2010 17:07:26 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Jari Arkko <jari.arkko@piuha.net>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Date: Fri, 15 Oct 2010 17:07:25 -0400
Thread-Topic: [tcpm] draft-ietf-tcpm-urgent-data-06
Thread-Index: ActsrK9FyiS8C990TxaUdi0Nsb+GfQAAEPXA
Message-ID: <13205C286662DE4387D9AF3AC30EF456B020F14FEB@EMBX01-WF.jnpr.net>
References: <201009301549.RAA14282@TR-Sys.de> <13205C286662DE4387D9AF3AC30EF456B01839E20B@EMBX01-WF.jnpr.net> <31679F6B-0ACA-421F-8131-DA05B764A4A9@nokia.com> <13205C286662DE4387D9AF3AC30EF456B0201C2D1C@EMBX01-WF.jnpr.net> <FCF0200B-A1AF-4902-A110-D7EC08C39FEC@nokia.com> <4CB31ECF.6040307@gont.com.ar>, <1D4E3C6E-B0BF-4CAC-A01E-EC9CDAC14EE0@nokia.com> <C304DB494AC0C04C87C6A6E2FF5603DB481FB1C732@NDJSSCC01.ndc.nasa.gov> <4CB3CCBB.1030400@isi.edu> <675AC39A-0E6D-4014-850B-2A05389577C4@windriver.com> <4CB488F2.1070800@isi.edu> <4CB48DCE.7010606@isi.edu> <4CB8C1CF.1020106@piuha.net>
In-Reply-To: <4CB8C1CF.1020106@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: David Borman <david.borman@windriver.com>, Fernando Gont <fernando@gont.com.ar>, Joe Touch <touch@isi.edu>
Subject: Re: [tcpm] draft-ietf-tcpm-urgent-data-06
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, 15 Oct 2010 21:07:49 -0000
Looks good to me. > -----Original Message----- > From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On Behalf Of > Jari Arkko > Sent: Friday, October 15, 2010 5:04 PM > To: tcpm@ietf.org Extensions > Cc: David Borman; Fernando Gont; Joe Touch > Subject: Re: [tcpm] draft-ietf-tcpm-urgent-data-06 > > All, > > We discussed this yesterday in the IESG conference call. I would like > to > summarize my thinking about it and suggest a way forward. (There are a > few other ADs who have similar but perhaps not exactly the same > thoughts, but I'm the one who representing these thoughts with the > Discuss.) > > The main concern is that at least in my view, urgent data seems pretty > badly broken. It has potential interop problems if out of band mode is > used, mismatch of recommendations wrt real world implementations that > mostly use out of band mode as the default, etc. As far as I > understand, > when out of band mode is used the two end points have to agree about > the > semantics of the urgent pointer. It is reassuring that most > implementations that you tested actually use the same semantics, but we > an implementation that we do not know about or a middlebox could > disrupt > an application's understanding of the correct order and place of TCP > data from the other end. With this background, I felt that the document > stopped short of making clear enough recommendations about the use of > this feature. In the IESG we talked about what the right level of > "health warning" should be, and there were different opinions ranging > from text at the beginning of the document to formal deprecation of the > feature. > > I have a proposal below that takes the warning text approach. Note that > I'm not really changing anything substantive from what the document was > already saying, but if we publish a new RFC on urgent indications, it > seems reasonable to make it very clear that there are issues. If these > changes were made to the document I would be happy to clear my Discuss, > though I do know that Ron would probably would like to see an even more > drastic action. What does the working group think? > > Jari > > Change Abstract: > > OLD: > This document analyzes how current TCP implementations process TCP > urgent indications, and how the behavior of some widely-deployed > middle-boxes affect how urgent indications are processed by end > systems. This document updates the relevant specifications such > that > they accommodate current practice in processing TCP urgent > indications, provides advice to applications that make use of the > urgent mechanism, and raises awareness about the reliability of TCP > urgent indications in the current Internet. > NEW: > This document analyzes how current TCP implementations process TCP > urgent indications, and how the behavior of some widely-deployed > middle-boxes affect how urgent indications are processed by end > systems. This document updates the relevant specifications such that > they accommodate current practice in processing TCP urgent > indications, raises awareness about the reliability of TCP > urgent indications in the Internet and recommends against the use of > the > urgent indications (but provides advice to applications in case that > they do). > > Change Introduction: > > OLD: > This document analyzes how some current TCP implementations process > TCP urgent indications, and how the behavior of some widely-deployed > middle-boxes affect the processing of urgent indications by hosts. > This document updates RFC 793 [RFC0793], RFC 1011 [RFC1011], and RFC > 1122 [RFC1122] such that they accommodate current practice in > processing TCP urgent indications, provides advice to applications > using the urgent mechanism, and raises awareness about the > reliability of TCP urgent indications in the current Internet. > NEW: > This document analyzes how some current TCP implementations process > TCP urgent indications, and how the behavior of some widely-deployed > middle-boxes affect the processing of urgent indications by hosts. > This document updates RFC 793 [RFC0793], RFC 1011 [RFC1011], and RFC > 1122 [RFC1122] such that they accommodate current practice in > processing TCP urgent indications, provides advice to applications > using the urgent mechanism, and raises awareness about the > reliability of TCP urgent indications in the current Internet. > > Given the above issues and potential interoperability issues with > respect to the > currently common default mode operation, it is strongly recommended > that > applications do not employ urgent indications. Nevertheless, urgent > indications > are still retained as a mandatory part of the TCP protocol to > support the > few legacy applications that employ them. However, it is expected > that even > these applications will have difficulties in environments with > middle-boxes. > > _______________________________________________ > tcpm mailing list > tcpm@ietf.org > https://www.ietf.org/mailman/listinfo/tcpm
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Fernando Gont
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Fernando Gont
- [tcpm] draft-ietf-tcpm-urgent-data-06 Ronald Bonica
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Peter Saint-Andre
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 John Heffner
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 David Borman
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Joe Touch
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Anantha Ramaiah (ananth)
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Fernando Gont
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 David Borman
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Ronald Bonica
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Lars Eggert
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Jari Arkko
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Ronald Bonica
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Alfred Hönes
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Ronald Bonica
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Lars Eggert
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Ronald Bonica
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Lars Eggert
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Fernando Gont
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Lars Eggert
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Joe Touch
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 David Borman
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Joe Touch
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Joe Touch
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Jari Arkko
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Ronald Bonica
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Peter Saint-Andre
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 David Borman
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Joe Touch
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Jari Arkko
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Joe Touch
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Jari Arkko
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Joe Touch
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Ronald Bonica
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 David Borman
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Joe Touch
- Re: [tcpm] draft-ietf-tcpm-urgent-data-06 Jari Arkko