Re: [mpls] "Traffic Management" (was Re: Poll on renaming of EXP field)

"Shah, Himanshu" <hshah@ciena.com> Tue, 19 August 2008 18:40 UTC

Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9ABBA3A6AFE; Tue, 19 Aug 2008 11:40:21 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71A233A6AFE for <mpls@core3.amsl.com>; Tue, 19 Aug 2008 11:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oHWihySFIDpu for <mpls@core3.amsl.com>; Tue, 19 Aug 2008 11:40:19 -0700 (PDT)
Received: from hicks.ciena.com (hicks.ciena.com [63.118.34.22]) by core3.amsl.com (Postfix) with ESMTP id 85CD13A69E4 for <mpls@ietf.org>; Tue, 19 Aug 2008 11:40:19 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAPSvqkg/dicW/2dsb2JhbAC3BIFY
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Aug 2008 14:39:50 -0400
Message-ID: <6535C9CED6F87446B41D20EF170F23620E36BF@mamxm01.ciena.com>
In-Reply-To: <48AB1194.6000902@alumni.nd.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls] "Traffic Management" (was Re: Poll on renaming of EXP field)
Thread-Index: AckCKgvBZ7Ic6TU0QzShPre6GVDj3gAAMK9g
From: "Shah, Himanshu" <hshah@ciena.com>
To: John Kenney <johnkenney@alumni.nd.edu>, Francois Le Faucheur IMAP <flefauch@cisco.com>
X-OriginalArrivalTime: 19 Aug 2008 18:40:04.0866 (UTC) FILETIME=[FF1BBE20:01C9022A]
Cc: mpls@ietf.org
Subject: Re: [mpls] "Traffic Management" (was Re: Poll on renaming of EXP field)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org

Ditto.

No to CoS, Yes to TM...

/himanshu

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org]On Behalf Of
> John Kenney
> Sent: Tuesday, August 19, 2008 2:32 PM
> To: Francois Le Faucheur IMAP
> Cc: mpls@ietf.org
> Subject: Re: [mpls] "Traffic Management" (was Re: Poll on renaming of
> EXP field)
> 
> 
> My "No" vote is a vote in favor of "Traffic Management"
> 
> Francois Le Faucheur IMAP wrote:
> > Hi,
> >
> > Someone earlier suggested "Traffic Management". While it can most 
> > certainly be argued this would not be a perfect name either 
> (or other 
> > names would be closer to "perfection"), is there a good 
> argument I am 
> > missing for why "COS" is obviously better (or more "good 
> enough") than 
> > "Traffic Management"? (considering we want to capture both Diffserv 
> > and ECN/PCN use of EXP field)
> >
> > Thanks
> >
> > Francois
> >
> >
> > On 18 Aug 2008, at 22:23, George Swallow wrote:
> >
> >> During the last call on "EXP field" renamed to  "CoS Field"
> >> draft-ietf-mpls-cosfield-def-04.txt, there were comments on
> >> alternatives to the name COS.
> >>
> >> This message initiates a two week poll on whether the name COS
> >> is good enough, or if some other name is needed.  The poll closes
> >> 23:59 Sept 1 GMT.
> >>
> >> Please answer with a simple yes or no.  You may send any 
> additional 
> >> comment
> >> in a separate message (with a different subject line).
> >>
> >> ...George
> >>
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> >
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls