Re: [PCN] Re: WG Review: Congestion and Pre-Congestion Notification(pcn)

Lars Eggert <lars.eggert@nokia.com> Wed, 21 February 2007 10:13 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJoTP-0007BT-OR; Wed, 21 Feb 2007 05:13:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJoTK-00079v-BS; Wed, 21 Feb 2007 05:13:14 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJoTI-0007Cn-Si; Wed, 21 Feb 2007 05:13:14 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l1LA8wgl011048; Wed, 21 Feb 2007 12:09:18 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Feb 2007 12:12:52 +0200
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by esebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Feb 2007 12:12:52 +0200
Received: from [10.140.224.6] (essapo-nirac252168.europe.nokia.com [10.162.252.168]) by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l1LA84Em009630; Wed, 21 Feb 2007 12:09:14 +0200
In-Reply-To: <Pine.LNX.4.64.0702201146060.31760@netcore.fi>
References: <E1HH7PO-0007pM-7J@stiedprstage1.ietf.org> <Pine.LNX.4.64.0702191509450.2014@netcore.fi> <F222151D3323874393F83102D614E055068B8E2B@CORPUSMX20A.corp.emc.com> <Pine.LNX.4.64.0702201146060.31760@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <82D42A1B-D57A-41C5-9400-12E7206216D2@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Wed, 21 Feb 2007 10:12:01 +0200
To: ext Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 21 Feb 2007 10:12:53.0370 (UTC) FILETIME=[D96435A0:01C755A0]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070221120918-2B12FBB0-23C599DE/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: pcn@ietf.org, ietf@ietf.org, Black_David@emc.com, iesg@ietf.org
Subject: Re: [PCN] Re: WG Review: Congestion and Pre-Congestion Notification(pcn)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1434663426=="
Errors-To: ietf-bounces@ietf.org

On 2007-2-20, at 11:51, ext Pekka Savola wrote:
> It seems that are assuming the transport needs to happen in the  
> packet itself.  While this is a possible approach, I don't see that  
> it needs to be the only one.  For example, a mechanism where the  
> mutually trusting network components would have another channel to  
> convey this information (e.g., using SNMP, IPFIX, or the like)  
> might also apply.
>
> However, to be clear, I have no objection to using the ECN field(s)  
> if that does not hinder the current use (or lack thereof) of ECN.  
> What I specifically don't want is to define new fields for PCN,  
> especially extension headers or IP options.  I should have been  
> clearer with my objection.

Right, there are multiple ways to encode and transport congestion  
information to and from the egress. The charter has a milestone for  
the WG to discuss various options before picking one for the initial  
standards-track documents:

Nov 2007 Survey of Encoding and Transport Choices of (Pre-)Congestion
Information within a DiffServ Domain (Informational)

Lars


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf