RE: ECN support in a PCN domain (was: Re: [PCN] commentsondraft-ietf-pcn-architecture-02)

<philip.eardley@bt.com> Mon, 26 November 2007 13:18 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 1IwdrR-0003jV-PO; Mon, 26 Nov 2007 08:18:53 -0500
Received: from pcn by megatron.ietf.org with local (Exim 4.43) id 1IwdrQ-0003jP-Fd for pcn-confirm+ok@megatron.ietf.org; Mon, 26 Nov 2007 08:18:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwdrQ-0003jH-3t for pcn@ietf.org; Mon, 26 Nov 2007 08:18:52 -0500
Received: from smtp2.smtp.bt.com ([217.32.164.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwdrJ-0005Zp-B4 for pcn@ietf.org; Mon, 26 Nov 2007 08:18:52 -0500
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.65]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Nov 2007 13:18:44 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: ECN support in a PCN domain (was: Re: [PCN] commentsondraft-ietf-pcn-architecture-02)
Date: Mon, 26 Nov 2007 13:18:43 -0000
Message-ID: <75A199C5D243C741BF3D3F1EBCEF9BA503B343B5@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <9671A92C3C8B5744BC97F855F7CB6465134D396E@zcarhxm1.corp.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: ECN support in a PCN domain (was: Re: [PCN] commentsondraft-ietf-pcn-architecture-02)
Thread-Index: Acgs8zzt10S53v6qR8eaNn6LHzZkfQABDhEwAAC2KKAAR2ew0ACFlHXg
From: philip.eardley@bt.com
To: babiarz@nortel.com, Ruediger.Geib@t-systems.com, magnus.westerlund@ericsson.com, pcn@ietf.org
X-OriginalArrivalTime: 26 Nov 2007 13:18:44.0513 (UTC) FILETIME=[DED41910:01C8302E]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc:
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

Joe, whilst I personally agree that your suggestion is sensible, was
trying to keep the architecture draft independent of decisions about
encoding which are taken later in the WGs life. 

Rudiger
Yes, there are several possibilities. The one in the draft seemed the
safest (given that end point reaction is same to dropped pkt as CE).

phil

> -----Original Message-----
> From: Jozef Babiarz [mailto:babiarz@nortel.com]
> Sent: 23 November 2007 21:48
> To: Eardley,PL,Philip,CXR9 R; Ruediger.Geib@t-systems.com;
> magnus.westerlund@ericsson.com; pcn@ietf.org
> Subject: RE: ECN support in a PCN domain (was: Re: [PCN]
commentsondraft-
> ietf-pcn-architecture-02)
> 
> Phil, Ruediger and Magnus,
> 
> For Section 3.5, I would like to propose that it be replaced with the
> statement below.
> 
> If the WG choose to use ECN flied for convey PCN information through
the
> network. The PCN WG will request that IANA assign a DSCP value for PCN
> traffic class consistent with RFC3246 and with PCN marking behavior
> defined by this workgroup. The Diffserv code point should be referred
to
> as PCN.
> 
> Explanation:
> The PCN mechanism will use a new standardized DSCP and will reuse bits
> 14 & 15 (the ECN-field) of the IPv4 header for PCN therefore no impact
> to RFC3168, meaning that PCN and ECN can co-exist in the same network.
> 
> Could discuss other options but they get really messy.
> 
> Regards, Joe
> email:babiarz@nortel.com
> Telephone:613-763-6098
> -----Original Message-----
> From: philip.eardley@bt.com [mailto:philip.eardley@bt.com]
> Sent: November 22, 2007 6:34 AM
> To: Ruediger.Geib@t-systems.com; magnus.westerlund@ericsson.com;
> Babiarz, Jozef (CAR:0S03)
> Subject: RE: ECN support in a PCN domain (was: Re: [PCN]
> commentsondraft-ietf-pcn-architecture-02)
> 
> Joe, will leave this one to you as you thought about it more than I
did!
> Thanks
> phil
> 
> > -----Original Message-----
> > From: Geib, Ruediger [mailto:Ruediger.Geib@t-systems.com]
> > Sent: 22 November 2007 11:14
> > To: magnus.westerlund@ericsson.com
> > Cc: pcn@ietf.org
> > Subject: RE: ECN support in a PCN domain (was: Re: [PCN]
> commentsondraft-
> > ietf-pcn-architecture-02)
> >
> > Magnus,
> >
> > I agree to your request, I've asked Phil for a statement on the
> behaviour
> > of an ingress node receiving a PCN coloured packet in the
architecture
> > draft in my latest mail.
> >
> > I thougth about ignore and remark DSCP and ECN. Drop is a tough
> option.
> > Forward with DSCP Best Effort and unchanged ECM may be another one
(if
> > the DSCP is unknown on the ingress interface).
> >
> > There are more possibilities, depending on the PCN marking mechanism
> and
> > whether the ECN codepoints are used.
> >
> > Regards,
> >
> > Rudiger
> >
> > |>
> > |>    o  If a packet that is part of a PCN-flow arrives at a
> PCN-ingress-
> > |>       node with its CE (Congestion experienced) codepoint set,
then
> we
> > |>       assume that the PCN-ingress-node drops the packet.  After
its
> > |>       initial Charter is complete, the WG may decide to work on a
> > |>       mechanism (such as through a signalling extension) that
> enables
> > |>       ECN-marking to be carried transparently across the
> PCN-domain."
> > |
> > |This one really surprise me. How can you make this assumption? In
> case a
> > |ECN enabled flow with some packets CE marked arrive to the ingress
of
> > |the PCN domain and are within the limits for which the flow has
been
> > |admitted into the PCN domain, then the PCN domain has no right to
> > |summarily drop that packet as being less important than any of the
> > |unmarked packets. Only in cases if congestion actually is
experience
> > |within the PCN domain would a differential treatment of CE marked
> > |packets being warranted.
> > |
> > |Can someone please explain how the above assumptions still satisfy
> the
> > |following sentence in the charter?
> > |
> > |"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."
> > |
> > |
> > |Cheers
> > |
> > |Magnus Westerlund
> > |
> > |IETF Transport Area Director & TSVWG Chair
> >
>
|----------------------------------------------------------------------
> > |Multimedia Technologies, Ericsson Research EAB/TVM/M
> >
>
|----------------------------------------------------------------------
> > |Ericsson AB                | Phone +46 8 4048287
> > |Torshamsgatan 23           | Fax   +46 8 7575550
> > |S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> >
>
|----------------------------------------------------------------------
> > |
> > |
> > |_______________________________________________
> > |PCN mailing list
> > |PCN@ietf.org
> > |https://www1.ietf.org/mailman/listinfo/pcn
> > |
> >
> >
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pcn


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