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

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