RE: [PCN] PCN (Pre-Congestion Notification) draft charter

"Kwok-Ho Chan" <khchan@nortel.com> Tue, 19 September 2006 14:18 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GPgR6-0007Ck-US; Tue, 19 Sep 2006 10:18:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GPgR6-00070o-6c for pcn@ietf.org; Tue, 19 Sep 2006 10:18:56 -0400
Received: from zcars04f.nortel.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPgI8-0006pi-TN for pcn@ietf.org; Tue, 19 Sep 2006 10:09:42 -0400
Received: from zrtphxm1.corp.nortel.com (zrtphxm1.corp.nortel.com [47.140.202.50]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id k8JE9Co27762; Tue, 19 Sep 2006 10:09:12 -0400 (EDT)
Received: from KCHAN-2K3.nortel.com ([47.16.54.125] RDNS failed) by zrtphxm1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Sep 2006 10:08:45 -0400
Message-Id: <6.2.5.6.0.20060919100148.03d9e198@nortel.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 19 Sep 2006 10:08:45 -0400
To: Lucy Yong <lucyyong@huawei.com>
From: Kwok-Ho Chan <khchan@nortel.com>
Subject: RE: [PCN] PCN (Pre-Congestion Notification) draft charter
In-Reply-To: <000801c6d8de$a4316e00$a5087c0a@china.huawei.com>
References: <6439282641581441A36F7F6F83ED2ED2CBF845@S4DE8PSAAFQ.mitte.t-com.de> <000801c6d8de$a4316e00$a5087c0a@china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-OriginalArrivalTime: 19 Sep 2006 14:08:46.0017 (UTC) FILETIME=[1EFF8310:01C6DBF5]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: pcn@ietf.org, "'Geib, Ruediger'" <Ruediger.Geib@t-systems.com>
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pre-Congestion Notification Discussion 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

Lucy:
I will add the following issue as part of the Problem Statement Open 
Issues List:
Issue B.10:
Considerations for the operation of PCN with different lower layers 
(below the IP layer).
One of these is MPLS, but IP also operate over other link layers.
Should the PCN BOF/WG work on resolving how PCN may operate over 
different link layers?

This will be (in about 30 minutes) reflected in:
http://standards.nortel.com/pcn/ProblemStatementDraftIssuesList.txt

This is just the documentation of this issue so we can address this.
Please continue this discussion on the list using Issue B.10 in subject line.

Thank you very much!
-- Kwok --

At 11:50 AM 9/15/2006, Lucy Yong wrote:
>Hello Anna,
>
>I agree with Ruediger. I think PCN WG should tackle IP/MPLS together because
>more and more high available applications use MPLS transport mechanism. IP
>based marking may not effectively improve the application QoS. It would be
>better to study both together.
>
>Best Regards,
>Lucy
>
>-----Original Message-----
>From: Geib, Ruediger [mailto:Ruediger.Geib@t-systems.com]
>Sent: Friday, September 15, 2006 2:03 AM
>To: acharny@cisco.com
>Cc: pcn@ietf.org
>Subject: RE: [PCN] PCN (Pre-Congestion Notification) draft charter
>
>Hello Anna,
>
>I'd think that issues related to ecn should continue to be
>discussed within the tsvwg, no matter whether they are
>related to mpls, ip or pcn. At the same time, drafts relevant
>for PCN need to be discussed and announced to the PCN BOF/WG.
>And mpls-ecn certainly is one of them. So my position is
>discussion in both WGs. If it was of help in transforming
>the pcn bof to the pcn WG, then I'd favour the PCN bof as
>the home of draft-davie-ecn-mpls.
>
>Regards,
>
>Rudiger
>
>|-----Original Message-----
>|From: Anna Charny (acharny) [mailto:acharny@cisco.com]
>|Sent: Wednesday, September 13, 2006 8:37 AM
>|To: YongLucy 73674; pcn@ietf.org
>|Subject: RE: [PCN] PCN (Pre-Congestion Notification) draft charter
>|
>|
>|Hi Lucy,
>|
>|Thank you for your post.  Our initial assumption was that mpls-ecn work
>|will continue within tsvwg (see draft-davie-ecn-mpls).  I guess it is a
>|question to the list and the working group chairs on whether
>|this should be undertaken within the PCN WG (assuming it be formed).
>|One argument for keeping it within tsvwg is that it has broader
>|application than the proposed scope for the PCN BoF/new WG.  But we
>|are open to comments/suggestions on this.
>|
>|Anna
>|
>|-----Original Message-----
>|From: YongLucy 73674 [mailto:lucyyong@huawei.com]
>|Sent: Tuesday, September 12, 2006 11:16 PM
>|To: pcn@ietf.org
>|Subject: [PCN] PCN (Pre-Congestion Notification) draft charter
>|
>|Hello Every One,
>|
>|It is great to organize a BOF on PCN. This is a very important function
>|for QoS. The draft charter covers many features from IP perspectives (I
>|think). Should we also cover features from MPLS perspective? Something
>|like PCN per LSP. How could PCN contain the sufficient informaton for
>|edge router or CL to take an action on it? For multiple
>|segements having congestion potential, could a consolidated PCN be
>|propagated to the ingress or egress edge router?
>|Should RSVP be used in PCN for a LSP or a bit is inserted in packets?
>|
>|Anyway this is a good starting point.
>|
>|Best Regards,
>|Lucy Yong
>|
>|
>|***************************************************************
>|*********
>|*******************
>| This email and its attachments contain confidential information from
>|HUAWEI, which is intended only for the person or entity whose
>|address is
>|listed above. Any use of the information contained herein in any way
>|(including, but not limited to, total or partial disclosure,
>|reproduction, or dissemination) by persons other than the intended
>|recipient(s) is prohibited. If you receive this e-mail in error, please
>|notify the sender by phone or email immediately and delete it!
>|
>|***************************************************************
>|*********
>|*******************
>|
>|
>|_______________________________________________
>|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
>
>
>
>_______________________________________________
>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