IETF Logo Mail Archive

RE: Composite Link Requirements as WG document

"So, Ning" <ning.so@verizonbusiness.com> Tue, 10 November 2009 15:27 UTC

Return-Path: <ning.so@verizonbusiness.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FB2A3A69E0 for <rtgwg@core3.amsl.com>; Tue, 10 Nov 2009 07:27:52 -0800 (PST)
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 DZW5eADdXnjZ for <rtgwg@core3.amsl.com>; Tue, 10 Nov 2009 07:27:51 -0800 (PST)
Received: from omzesmtp03a.verizonbusiness.com (omzesmtp03a.verizonbusiness.com [199.249.25.201]) by core3.amsl.com (Postfix) with ESMTP id 6D23E3A67E6 for <rtgwg@ietf.org>; Tue, 10 Nov 2009 07:27:51 -0800 (PST)
Received: from pdcismtp01.vzbi.com ([unknown] [166.40.77.67]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0KSW00L11G07TY00@firewall.verizonbusiness.com> for rtgwg@ietf.org; Tue, 10 Nov 2009 15:21:43 +0000 (GMT)
Received: from pdcismtp01.vzbi.com ([127.0.0.1]) by pdcismtp01.vzbi.com (Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007; 32bit)) with ESMTP id <0KSW008BOG06U400@pdcismtp01.vzbi.com> for rtgwg@ietf.org; Tue, 10 Nov 2009 15:21:43 +0000 (GMT)
Received: from ASHSRV139.mcilink.com ([153.39.68.165]) by pdcismtp01.vzbi.com (Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007; 32bit)) with ESMTP id <0KSW008GDG06MS00@pdcismtp01.vzbi.com> for rtgwg@ietf.org; Tue, 10 Nov 2009 15:21:42 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV139.mcilink.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 10 Nov 2009 15:21:42 +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: Composite Link Requirements as WG document
Date: Tue, 10 Nov 2009 15:21:40 +0000
Message-id: <14584D6EE26B314187A4F68BA2060600022ECC1B@ASHEVS008.mcilink.com>
In-reply-to: <920D04EF-71DA-4CCA-9E9C-51F3F1FD237C@juniper.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-topic: Composite Link Requirements as WG document
Thread-index: Acph5byfUjwDf66aRhGxgPKo9aVLVgAM7g7g
References: <920D04EF-71DA-4CCA-9E9C-51F3F1FD237C@juniper.net>
From: "So, Ning" <ning.so@verizonbusiness.com>
To: "John G. Scudder" <jgs@juniper.net>, rtgwg@ietf.org
X-OriginalArrivalTime: 10 Nov 2009 15:21:42.0695 (UTC) FILETIME=[81EC9370:01CA6219]
Cc: alia.atlas@bt.com, ZININ Alex <Alex.Zinin@alcatel-lucent.sg>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 15:27:52 -0000

Support.

Ning So
Lead Engineer
Enterprise Data Network and Traffic Planning
972-729-7905
 
-----Original Message-----
From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
Of John G. Scudder
Sent: Tuesday, November 10, 2009 3:08 AM
To: rtgwg@ietf.org
Cc: alia.atlas@bt.com; ZININ Alex
Subject: Composite Link Requirements as WG document

Folks,

At today's meeting we received a request to adopt draft-so-yong-mpls- 
ctg-requirement-00 as a working group document.  There was reasonably  
strong support in the room for doing so.  Please respond to the  
mailing list with your discussion, support or opposition (please do  
this even if you did so in person).  The deadline for comments is  
November 30.

Note that accepting the document simply means that the working group  
would begin working on requirements.  It does not imply blanket  
acceptance of the document as it now stands.

Thanks,

--John
_______________________________________________
rtgwg mailing list
rtgwg@ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg

v2.23.0 | Report a Bug | By Email