Re: [PCN] Re: ECN support in a PCN domain
Lars Eggert <lars.eggert@nokia.com> Wed, 28 November 2007 18:12 UTC
Return-path: <pcn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxROk-0008Rf-5G; Wed, 28 Nov 2007 13:12:34 -0500
Received: from pcn by megatron.ietf.org with local (Exim 4.43) id 1IxROj-0008RS-6A for pcn-confirm+ok@megatron.ietf.org; Wed, 28 Nov 2007 13:12:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxROi-0008RJ-ST; Wed, 28 Nov 2007 13:12:32 -0500
Received: from smtp.nokia.com ([192.100.122.230] helo=mgw-mx03.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxROi-00067n-Au; Wed, 28 Nov 2007 13:12:32 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id lASIBlEj008159; Wed, 28 Nov 2007 20:12:29 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Nov 2007 20:12:15 +0200
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Nov 2007 20:12:14 +0200
Received: from [192.168.255.2] (essapo-nirac252204.europe.nokia.com [10.162.252.204]) by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lASICD09027474; Wed, 28 Nov 2007 20:12:13 +0200
Message-Id: <C1B136B8-A509-44E6-B548-668A23B0DE51@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: "ext pcn-bounces@ietf.org" <pcn-bounces@ietf.org>
In-Reply-To: <75A199C5D243C741BF3D3F1EBCEF9BA503B343D6@E03MVZ1-UKDY.domain1.systemhost.net>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [PCN] Re: ECN support in a PCN domain
Date: Wed, 28 Nov 2007 20:12:12 +0200
References: <75A199C5D243C741BF3D3F1EBCEF9BA503B343D6@E03MVZ1-UKDY.domain1.systemhost.net>
X-Mailer: Apple Mail (2.915)
X-OriginalArrivalTime: 28 Nov 2007 18:12:14.0785 (UTC) FILETIME=[3431DB10:01C831EA]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: pcn@ietf.org
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
Errors-To: pcn-bounces@ietf.org
On 2007-11-28, at 19:49, ext pcn-bounces@ietf.org wrote: > there was quite a lot of discussion (without resolution) whether it's > reasonable for a flow that uses PCN adm ctrl to also want e2e ECN for > rate adaptation (discussion both in terms of whether a flow would > actually ever want this, and how well the PCN mechanism would work if > flows were adapting like this). > this was resolved by saying that the support of e2e ecn is out of > scope > of initial charter of pcn. Huh? The charter says: All PCN mechanisms, including transport and encoding of (pre-congestion) information, are required to cleanly integrate with existing architectures and protocols such as DiffServ and ECN. "Cleanly integrate" doesn't mean "out of scope", it means "must work together with". TSVWG published RFC4774 to describe which alternate uses of the ECN bits are OK; the PCN mechanisms are supposed to instantiate such an accepted alternate use. Lars _______________________________________________ PCN mailing list PCN@ietf.org https://www1.ietf.org/mailman/listinfo/pcn
- [PCN] comments on draft-ietf-pcn-architecture-02 Georgios Karagiannis
- Re: [PCN] comments on draft-ietf-pcn-architecture… Lars Eggert
- RE: [PCN] comments on draft-ietf-pcn-architecture… Georgios Karagiannis
- RE: [PCN] comments on draft-ietf-pcn-architecture… philip.eardley
- RE: [PCN] comments on draft-ietf-pcn-architecture… Georgios Karagiannis
- RE: [PCN] comments on draft-ietf-pcn-architecture… philip.eardley
- ECN support in a PCN domain (was: Re: [PCN] comme… Magnus Westerlund
- RE: ECN support in a PCN domain (was: Re: [PCN] c… Geib, Ruediger
- RE: ECN support in a PCN domain (was: Re: [PCN] c… Jozef Babiarz
- RE: ECN support in a PCN domain (was: Re: [PCN] c… Geib, Ruediger
- RE: ECN support in a PCN domain (was: Re: [PCN] c… Jozef Babiarz
- RE: ECN support in a PCN domain (was: Re: [PCN] c… Geib, Ruediger
- RE: ECN support in a PCN domain (was: Re: [PCN] c… philip.eardley
- Re: ECN support in a PCN domain (was: Re: [PCN] c… Steven Blake
- [PCN] Re: ECN support in a PCN domain Magnus Westerlund
- [PCN] Re: ECN support in a PCN domain Steven Blake
- RE: [PCN] Re: ECN support in a PCN domain philip.eardley
- Re: [PCN] Re: ECN support in a PCN domain Lars Eggert
- [PCN] Architecture document / 5. Detailed functio… Geib, Ruediger
- RE: [PCN] Architecture document / 5. Detailed fun… philip.eardley
- RE: [PCN] Architecture document / 5. Detailed fun… Jozef Babiarz