IETF Logo Mail Archive

RE: Composite Link Requirements as WG document

"Mcdysan, David E" <dave.mcdysan@verizon.com> Tue, 10 November 2009 12:57 UTC

Return-Path: <dave.mcdysan@verizon.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 B75BB3A68F0 for <rtgwg@core3.amsl.com>; Tue, 10 Nov 2009 04:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.623
X-Spam-Level:
X-Spam-Status: No, score=-2.623 tagged_above=-999 required=5 tests=[AWL=0.976, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 BxqUeQteC7Uo for <rtgwg@core3.amsl.com>; Tue, 10 Nov 2009 04:57:54 -0800 (PST)
Received: from tpamail4.verizon.com (tpamail4.verizon.com [192.76.82.161]) by core3.amsl.com (Postfix) with ESMTP id D92963A68B7 for <rtgwg@ietf.org>; Tue, 10 Nov 2009 04:57:53 -0800 (PST)
Received: from smtpftw3.verizon.com (smtpftw3.verizon.com [138.83.140.92]) by tpamail4.verizon.com (8.13.6/8.13.3) with ESMTP id nAACjP7c026446; Tue, 10 Nov 2009 07:45:33 -0500 (EST)
Received: from ftwintrmemf2.verizon.com (ftwintrmemf2.verizon.com [138.83.131.184]) by smtpftw3.verizon.com (8.13.3/8.13.3) with ESMTP id nAACw5Ao009447; Tue, 10 Nov 2009 07:58:05 -0500 (EST)
X-AuditID: 8a5383b8-b7b7bae000003c5d-5f-4af9635dd1c9
Received: from smtpftw3.verizon.com ( [138.83.140.92]) by ftwintrmemf2.verizon.com (EMF) with SMTP id A2.11.15453.D5369FA4; Tue, 10 Nov 2009 07:58:05 -0500 (EST)
Received: from FHDP1CCMXCG02.us.one.verizon.com ([166.68.240.34]) by smtpftw3.verizon.com (8.13.3/8.13.3) with ESMTP id nAACvxCR009298; Tue, 10 Nov 2009 07:58:05 -0500 (EST)
Received: from FHDP1LUMXCV14.us.one.verizon.com ([166.68.125.35]) by FHDP1CCMXCG02.us.one.verizon.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 10 Nov 2009 07:58:05 -0500
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 07:57:20 -0500
Message-ID: <793F49BA1FC821409F99F10862A0E4DB049DB190@FHDP1LUMXCV14.us.one.verizon.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: Acph5bwn6dVL5BavT1ih9cWSA+vikQAH5TeQ
References: <920D04EF-71DA-4CCA-9E9C-51F3F1FD237C@juniper.net>
From: "Mcdysan, David E" <dave.mcdysan@verizon.com>
To: "John G. Scudder" <jgs@juniper.net>, rtgwg@ietf.org
X-OriginalArrivalTime: 10 Nov 2009 12:58:05.0037 (UTC) FILETIME=[716651D0:01CA6205]
X-Brightmail-Tracker: AAAAAA==
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 12:57:54 -0000

Support. 

> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] 
> On Behalf Of John G. Scudder
> Sent: Tuesday, November 10, 2009 4: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