Re: [conex] Potentially interesting ConEx problem
"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Wed, 06 March 2013 19:46 UTC
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: conex@ietfa.amsl.com
Delivered-To: conex@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5AE321F8263 for <conex@ietfa.amsl.com>; Wed, 6 Mar 2013 11:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.319
X-Spam-Level:
X-Spam-Status: No, score=-7.319 tagged_above=-999 required=5 tests=[AWL=-1.070, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MHjwfXhEGkf5 for <conex@ietfa.amsl.com>; Wed, 6 Mar 2013 11:46:25 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [62.23.212.56]) by ietfa.amsl.com (Postfix) with ESMTP id 3148021F8235 for <conex@ietf.org>; Wed, 6 Mar 2013 11:46:25 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r26JjM3t013624 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 6 Mar 2013 20:46:22 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Wed, 6 Mar 2013 20:46:08 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, ConEx IETF list <conex@ietf.org>
Date: Wed, 06 Mar 2013 20:46:07 +0100
Thread-Topic: [conex] Potentially interesting ConEx problem
Thread-Index: Ac4aKma/D1i9fNTWSYqZZ0RmqnleZQAdiCZD
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AB12C1E0A@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <CAH56bmD5c3KjVxg3gf9utBTQDLQS3HnxjVbpYf1Bby=iOB85bQ@mail.gmail.com> <201303050953.r259rCTS000573@bagheera.jungle.bt.co.uk> <CAH56bmAn5MzD8UVAXKEoQf-kWdeyM-08QM9mxUT0pLDyx4xVDA@mail.gmail.com> <354A9577-4AE9-4094-93B8-2778E9B6A80A@cisco.com> <CAH56bmBKsVfo2-2gL6sKAYT18XSrq2N31YEViwp0ZxTSBbWYOQ@mail.gmail.com>, <alpine.DEB.2.00.1303060616540.14991@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1303060616540.14991@uplift.swm.pp.se>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: Re: [conex] Potentially interesting ConEx problem
X-BeenThere: conex@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Congestion Exposure working group discussion list <conex.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/conex>, <mailto:conex-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/conex>
List-Post: <mailto:conex@ietf.org>
List-Help: <mailto:conex-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/conex>, <mailto:conex-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 19:46:27 -0000
Mikael, I do not understand how a congestion manager solves the problem raised here. Also, since you seem to be unhappy with TCPM, please recall that at least I was interested in seeing empirical data for the timer problem you described (e. g., real OS traces). But that discussion would be better suited for the TCPM list, imho. Actually, I do think that another recent TCPM discussion is closer related to this question: http://www.ietf.org/mail-archive/web/tcpm/current/msg06829.html (But Matt is certainly aware of this already, and it doesn't solve the problem). Another random idea that comes into my mind is the Quick-Start nonce mechanism. In Quick-Start one can ensure that certain actions can only be performed by downstream routers. Sure, this is not what is needed here, but maybe another interesting pointer? Michael ________________________________________ Von: conex-bounces@ietf.org [conex-bounces@ietf.org] im Auftrag von Mikael Abrahamsson [swmike@swm.pp.se] Gesendet: Mittwoch, 6. März 2013 06:20 An: ConEx IETF list Betreff: Re: [conex] Potentially interesting ConEx problem On Tue, 5 Mar 2013, Matt Mathis wrote: > The question I was asking was can ConEx help the content provider know > which bottleneck prevails? Bob? I tried to get the TCP people look into this, but got shot down. They didn't feel TCP would work better by knowing more, or I guess they didn't want to handle th complexity. My idea was that TCP would over time "find out" what the access looked like if it indeed was the only thing congesting, and even that the connection manager on the machine would inform TCP what the properties of the primary connection was (speed, buffering, retransmits, half/full duplex etc), and if something substantial (like the link going down or coming up, speed changed etc) happened, TCP would be informed of this. They felt it was better to have TCP find out by itself instead of getting fed this information via some API. -- Mikael Abrahamsson email: swmike@swm.pp.se _______________________________________________ conex mailing list conex@ietf.org https://www.ietf.org/mailman/listinfo/conex
- Re: [conex] Potentially interesting ConEx problem Bob Briscoe
- Re: [conex] Potentially interesting ConEx problem Matt Mathis
- Re: [conex] Potentially interesting ConEx problem John Leslie
- Re: [conex] Potentially interesting ConEx problem Andrew McLachlan (amclachl)
- Re: [conex] Potentially interesting ConEx problem Matt Mathis
- Re: [conex] Potentially interesting ConEx problem Mikael Abrahamsson
- Re: [conex] Potentially interesting ConEx problem Matt Mathis
- Re: [conex] Potentially interesting ConEx problem Mikael Abrahamsson
- Re: [conex] Potentially interesting ConEx problem Scharf, Michael (Michael)
- Re: [conex] Potentially interesting ConEx problem Mikael Abrahamsson
- Re: [conex] Potentially interesting ConEx problem Mirja Kuehlewind
- Re: [conex] Potentially interesting ConEx problem Bob Briscoe
- Re: [conex] Potentially interesting ConEx problem Bob Briscoe