
From marla.azinger@ftr.com  Wed Jun  1 08:38:35 2011
Return-Path: <marla.azinger@ftr.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8059E08E8; Wed,  1 Jun 2011 08:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlvJEVQ2g4Ej; Wed,  1 Jun 2011 08:38:33 -0700 (PDT)
Received: from frontiercorp.com (mail04.frontiercorp.com [66.133.172.21]) by ietfa.amsl.com (Postfix) with ESMTP id 80E60E08E3; Wed,  1 Jun 2011 08:38:32 -0700 (PDT)
Received: from ([10.162.69.10]) by mail04.frontiercorp.com with ESMTP with TLS id 4LZG4M1.270939180; Wed, 01 Jun 2011 11:38:29 -0400
Received: from ROCH-EXCH1.corp.pvt ([10.160.69.50]) by nyrofcswnexht01.corp.pvt ([10.162.69.10]) with mapi; Wed, 1 Jun 2011 11:38:28 -0400
From: "Azinger, Marla" <Marla.Azinger@FTR.com>
To: Gerald Ash <gash5107@yahoo.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Wed, 1 Jun 2011 11:38:26 -0400
Subject: RE: Generic Connection Admission Control (GCAC) Algorithm Specification	for IP/MPLS Networks
Thread-Topic: Generic Connection Admission Control (GCAC) Algorithm Specification	for IP/MPLS Networks
Thread-Index: AcwbxUsq48DaIgoHQ2i4idN8vz8NtwErJ1WQ
Message-ID: <2E2FECEBAE57CC4BAACDE67638305F1049E24E45BC@ROCH-EXCH1.corp.pvt>
References: <285128.82087.qm@web125919.mail.ne1.yahoo.com>
In-Reply-To: <285128.82087.qm@web125919.mail.ne1.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2E2FECEBAE57CC4BAACDE67638305F1049E24E45BCROCHEXCH1corp_"
MIME-Version: 1.0
X-esp: ESP<17>= SHA:<0> SHA_FLAGS:<0> UHA:<18> ISC:<0> BAYES:<-1>  SenderID:<0> DKIM:<0> TS:<0> SIG:<> DSC:<0> TRU_urllinks: <0> TRU_spam1: <0> TRU_playsites: <0> TRU_ru_spamsubj: <0> TRU_freehosting: <0> TRU_phish_spam: <0> TRU_scam_spam: <0> TRU_stock_spam: <0> TRU_embedded_image_spam: <0> TRU_money_spam: <0> URL Real-Time Signatures: <0> TRU_legal_spam: <0> TRU_watch_spam: <0> TRU_misc_spam: <0> TRU_profanity_spam: <0> TRU_html_image_spam: <0> TRU_adult_spam: <0> TRU_spam2: <0> TRU_medical_spam: <0> TRU_lotto_spam: <0> TRU_marketing_spam: <0>
X-Mailman-Approved-At: Wed, 01 Jun 2011 10:07:33 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 01 Jun 2011 15:38:35 -0000

--_000_2E2FECEBAE57CC4BAACDE67638305F1049E24E45BCROCHEXCH1corp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Jerry-

Did you get a response from anyone on this yet?

Cheers
Marla

________________________________
From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of G=
erald Ash
Sent: Thursday, May 26, 2011 9:51 AM
To: rtgwg@ietf.org
Cc: mpls@ietf.org
Subject: Generic Connection Admission Control (GCAC) Algorithm Specificatio=
n for IP/MPLS Networks

Hi,

Adrian has suggested that the RTGWG and the MPLS WG review the draft "Gener=
ic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS =
Networks", available at  http://www.ietf.org/id/draft-ash-gcac-algorithm-sp=
ec-00.txt (abstract below).
The underlying goal of the work is to specify an optional GCAC algorithm fo=
r IP/MPLS networks, to be adopted and implemented by vendors and service pr=
oviders, that interoperates between vendor equipment and across multiple se=
rvice provider domains.  This would be analogous to the PNNI GCAC that was =
widely adopted and helped promote interoperability of ATM networks.  In add=
ition, the approach:
o is based on CSPF, widely implemented by vendors
o does NOT include aspects of CAC that might be considered vendor proprieta=
ry implementations, such as detailed path selection mechanisms
o relies on available standard mechanisms for MPLS based networks, such as =
RSVP, DSTE, PCE...

Comments appreciated.

Thanks,
Jerry

From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ash-gcac-algorithm-spec-00.txt
X-RSN: 1/0/935/34473/37870

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

Title : Generic Connection Admission Control (GCAC) Algorithm Specification=
 for IP/MPLS Networks
Author(s) : G. Ash, D. McDysan
Filename : draft-ash-gcac-algorithm-spec-00.txt
Pages : 23
Date : 2011-1-11

This document presents a generic connection admission control (GCAC)
reference model and algorithm for IP/MPLS-based networks. Service
provider (SP) IP/MPLS networks need an MPLS GCAC mechanism, for
example, to reject voice over Internet Protocol (VoIP) calls when
additional calls would adversely affect calls already in progress.

Without MPLS GCAC, connections on congested links will suffer
degraded quality. The MPLS GCAC algorithm can be optionally
implemented in vendor equipment and deployed by service providers.
MPLS GCAC interoperates between vendor equipment and across multiple
service provider domains. The MPLS GCAC algorithm uses available
standard mechanisms for MPLS based networks, such as RSVP, DSTE, PCE,
NSIS, DiffServ, and OSPF. The MPLS GCAC algorithm does not include
aspects of CAC that might be considered vendor proprietary
implementations, such as detailed path selection mechanisms. MPLS
GCAC functions are implemented in a distributed manner to deliver the
objective QoS for specified QoS constraints. The source is able to
compute a source route with high likelihood that MPLS GCAC via
elements along the selected path will in fact admit the request.
MPLS GCAC is applicable to any service or flow that must meet an
objective QoS (delay, jitter, packet loss rate) for a specified
quantity of traffic.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ash-gcac-algorithm-spec-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

*****
Click below to download the attachment(s) in this message:
<A HREF=3D"http://www.ietf.org/ibin/c5i?mid=3D6&gid=3D0&rid=3D8&k1=3D935&fi=
le=3Di-d-announce.37870.1.txt">Attachment: draft_ash_gcac_algorithm_spec_00=
.txt</A> (1K)


________________________________
This communication is confidential. Frontier only sends and receives email =
on the basis of the terms set out at http://www.frontier.com/email_disclaim=
er.

--_000_2E2FECEBAE57CC4BAACDE67638305F1049E24E45BCROCHEXCH1corp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.19019">
</head>
<body>
<div dir=3D"ltr" align=3D"left"><span class=3D"097093815-01062011"><font co=
lor=3D"#0000ff">Jerry-</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"097093815-01062011"><font co=
lor=3D"#0000ff"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"097093815-01062011"><font co=
lor=3D"#0000ff">Did you get a response from anyone on this yet?</font></spa=
n></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"097093815-01062011"><font co=
lor=3D"#0000ff"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"097093815-01062011"><font co=
lor=3D"#0000ff">Cheers</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"097093815-01062011"><font co=
lor=3D"#0000ff">Marla</font></span></div>
<br>
<div dir=3D"ltr" lang=3D"en-us" class=3D"OutlookMessageHeader" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>From:</b> rtgwg-bounces@ietf.org [mailt=
o:rtgwg-bounces@ietf.org]
<b>On Behalf Of </b>Gerald Ash<br>
<b>Sent:</b> Thursday, May 26, 2011 9:51 AM<br>
<b>To:</b> rtgwg@ietf.org<br>
<b>Cc:</b> mpls@ietf.org<br>
<b>Subject:</b> Generic Connection Admission Control (GCAC) Algorithm Speci=
fication for IP/MPLS Networks<br>
</font><br>
</div>
<div></div>
<table border=3D"0" cellspacing=3D"0" cellpadding=3D"0">
<tbody>
<tr>
<td valign=3D"top">
<div _yuid=3D"yui_3_1_1_2_1306427587424223">Hi,</div>
<div>&nbsp;</div>
<div>Adrian has suggested that the RTGWG and the MPLS WG review&nbsp;the dr=
aft &quot;Generic
<span style=3D"BORDER-BOTTOM: #366388 2px dotted; CURSOR: hand" id=3D"lw_13=
06428212_0" class=3D"yshortcuts">
Connection Admission Control</span> (GCAC) Algorithm Specification for IP/M=
PLS Networks&quot;, available&nbsp;at &nbsp;<a href=3D"http://www.ietf.org/=
id/draft-ash-gcac-algorithm-spec-00.txt" rel=3D"nofollow" target=3D"_blank"=
><span id=3D"lw_1306428212_1" class=3D"yshortcuts">http://www.ietf.org/id/d=
raft-ash-gcac-algorithm-spec-00.txt</span></a>&nbsp;(abstract&nbsp;below).<=
br>
</div>
<div>The underlying goal of the work is to specify an optional GCAC algorit=
hm for IP/MPLS networks,&nbsp;to be adopted and implemented by vendors and =
service providers, that interoperates between vendor equipment and across m=
ultiple service provider domains.&nbsp; This
 would be analogous to the PNNI GCAC that was widely adopted and&nbsp;helpe=
d promote&nbsp;interoperability of ATM networks.&nbsp; In addition, the app=
roach:</div>
<div>o&nbsp;is&nbsp;based on&nbsp;CSPF, widely implemented by vendors</div>
<div>o&nbsp;does&nbsp;NOT include aspects of CAC that might be considered v=
endor proprietary implementations, such as detailed path selection mechanis=
ms</div>
<div>o relies on&nbsp;available standard mechanisms for MPLS based networks=
, such as RSVP, DSTE, PCE...</div>
<div>&nbsp;</div>
<div>Comments appreciated.</div>
<div>&nbsp;</div>
<div>Thanks,</div>
<div>Jerry</div>
<div>&nbsp;</div>
<div>From: <span style=3D"BORDER-BOTTOM: #366388 2px dotted; CURSOR: hand" =
id=3D"lw_1306428212_2" class=3D"yshortcuts">
Internet-Drafts@ietf.org</span>&nbsp;<br>
To: <span style=3D"BORDER-BOTTOM: #366388 2px dotted; CURSOR: hand" id=3D"l=
w_1306428212_3" class=3D"yshortcuts">
i-d-announce@ietf.org</span>&nbsp;<br>
Reply-to: Internet-Drafts@ietf.org&nbsp;<br>
Subject: I-D ACTION:draft-ash-gcac-algorithm-spec-00.txt&nbsp;<br>
X-RSN: 1/0/935/34473/37870&nbsp;<br>
&nbsp;<br>
A New Internet-Draft is available from the on-line Internet-Drafts &nbsp;<b=
r>
directories.<br>
&nbsp;<br>
Title : Generic Connection Admission Control (GCAC) Algorithm Specification=
 for IP/MPLS Networks&nbsp;<br>
Author(s) : G. Ash, D. McDysan&nbsp;<br>
Filename : draft-ash-gcac-algorithm-spec-00.txt&nbsp;<br>
Pages : 23&nbsp;<br>
Date : 2011-1-11&nbsp;<br>
&nbsp;<br>
This document presents a generic connection admission control (GCAC)&nbsp;<=
br>
<span id=3D"lw_1306428212_4" class=3D"yshortcuts">reference model</span> an=
d algorithm for IP/MPLS-based networks.
<span id=3D"lw_1306428212_5" class=3D"yshortcuts">Service&nbsp;<br>
provider</span> (SP) IP/MPLS networks need an MPLS GCAC mechanism, for&nbsp=
;<br>
example, to reject voice over Internet Protocol (VoIP) calls when&nbsp;<br>
additional calls would adversely affect calls already in progress.&nbsp;<br=
>
&nbsp;<br>
Without MPLS GCAC, connections on congested links will suffer&nbsp;<br>
degraded quality. The MPLS GCAC algorithm can be optionally&nbsp;<br>
implemented in vendor equipment and deployed by service providers.&nbsp;<br=
>
MPLS GCAC interoperates between vendor equipment and across multiple&nbsp;<=
br>
service provider domains. The MPLS GCAC algorithm uses available&nbsp;<br>
standard mechanisms for MPLS based networks, such as RSVP, DSTE, PCE,&nbsp;=
<br>
NSIS, DiffServ, and OSPF. The MPLS GCAC algorithm does not include&nbsp;<br=
>
aspects of CAC that might be considered vendor proprietary&nbsp;<br>
implementations, such as detailed path selection mechanisms. MPLS&nbsp;<br>
GCAC functions are implemented in a distributed manner to deliver the&nbsp;=
<br>
objective QoS for specified QoS constraints. The source is able to&nbsp;<br=
>
compute a <span style=3D"BORDER-BOTTOM: #366388 2px dotted; CURSOR: hand" i=
d=3D"lw_1306428212_6" class=3D"yshortcuts">
source route</span> with high likelihood that MPLS GCAC via&nbsp;<br>
elements along the selected path will in fact admit the request.&nbsp;<br>
MPLS GCAC is applicable to any service or flow that must meet an&nbsp;<br>
objective QoS (delay, jitter, <span id=3D"lw_1306428212_7" class=3D"yshortc=
uts">packet loss rate</span>) for a specified&nbsp;<br>
quantity of traffic.&nbsp;<br>
&nbsp;<br>
A URL for this Internet-Draft is:&nbsp;<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-ash-gcac-algorithm-spe=
c-00.txt" rel=3D"nofollow" target=3D"_blank"><span id=3D"lw_1306428212_8" c=
lass=3D"yshortcuts">http://www.ietf.org/internet-drafts/draft-ash-gcac-algo=
rithm-spec-00.txt</span></a></div>
<div><br>
Internet-Drafts are also available by anonymous FTP at:&nbsp;<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"nofollow" target=3D"=
_blank">ftp://ftp.ietf.org/internet-drafts/</a></div>
<div _yuid=3D"yui_3_1_1_2_1306427587424221"><br>
Below is the data which will enable a MIME compliant mail reader&nbsp;<br>
implementation to automatically retrieve the ASCII version of the&nbsp;<br>
Internet-Draft.&nbsp;<br>
_______________________________________________&nbsp;<br>
I-D-Announce mailing list&nbsp;<br>
I-D-Announce@ietf.org&nbsp;<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce" target=3D"_b=
lank"><span id=3D"lw_1306428212_9" class=3D"yshortcuts">https://www.ietf.or=
g/mailman/listinfo/i-d-announce</span></a>&nbsp;<br>
Internet-Draft directories: <a href=3D"http://www.ietf.org/shadow.html" tar=
get=3D"_blank">
<span id=3D"lw_1306428212_10" class=3D"yshortcuts">http://www.ietf.org/shad=
ow.html</span></a>&nbsp;<br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" target=3D"_blank">=
<span id=3D"lw_1306428212_11" class=3D"yshortcuts">ftp://ftp.ietf.org/ietf/=
1shadow-sites.txt</span></a>&nbsp;<br>
&nbsp;<br>
*****&nbsp;<br>
Click below to download the attachment(s) in this message:&nbsp;<br>
&lt;A HREF=3D&quot;<a href=3D"http://www.ietf.org/ibin/c5i?mid=3D6&amp;gid=
=3D0&amp;rid=3D8&amp;k1=3D935&amp;file=3Di-d-announce.37870.1.txt" target=
=3D"_blank"><span id=3D"lw_1306428212_12" class=3D"yshortcuts">http://www.i=
etf.org/ibin/c5i?mid=3D6&amp;gid=3D0&amp;rid=3D8&amp;k1=3D935&amp;file=3Di-=
d-announce.37870.1.txt</span></a>&quot;&gt;Attachment:
 draft_ash_gcac_algorithm_spec_00.txt&lt;/A&gt; (1K)&nbsp;<br>
</div>
</td>
</tr>
</tbody>
</table>
<br>
<hr>
<font face=3D"Verdana" color=3D"Gray" size=3D"2">This communication is conf=
idential. Frontier only sends and receives email on the basis of the terms =
set out at http://www.frontier.com/email_disclaimer.<br>
</font>
</body>
</html>

--_000_2E2FECEBAE57CC4BAACDE67638305F1049E24E45BCROCHEXCH1corp_--

From gash5107@yahoo.com  Mon Jun  6 12:15:13 2011
Return-Path: <gash5107@yahoo.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A41411E81CE for <rtgwg@ietfa.amsl.com>; Mon,  6 Jun 2011 12:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.184
X-Spam-Level: 
X-Spam-Status: No, score=-100.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzUXQJfhwKhR for <rtgwg@ietfa.amsl.com>; Mon,  6 Jun 2011 12:15:13 -0700 (PDT)
Received: from nm21-vm1.bullet.mail.ne1.yahoo.com (nm21-vm1.bullet.mail.ne1.yahoo.com [98.138.91.46]) by ietfa.amsl.com (Postfix) with SMTP id E156011E81CB for <rtgwg@ietf.org>; Mon,  6 Jun 2011 12:15:12 -0700 (PDT)
Received: from [98.138.90.54] by nm21.bullet.mail.ne1.yahoo.com with NNFMP; 06 Jun 2011 19:15:09 -0000
Received: from [98.138.87.4] by tm7.bullet.mail.ne1.yahoo.com with NNFMP; 06 Jun 2011 19:15:09 -0000
Received: from [127.0.0.1] by omp1004.mail.ne1.yahoo.com with NNFMP; 06 Jun 2011 19:14:39 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 634940.18739.bm@omp1004.mail.ne1.yahoo.com
Received: (qmail 86878 invoked by uid 60001); 6 Jun 2011 19:14:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1307387679; bh=CAdWvDJogHkcLqRFeuKn3UxFfLAQ6FvjebZjhSU6/DE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=r92JVlsopCD81BS/W+nSkk1WnJhjHbX76AEBLcLESWutQv3n1Jwaws7vnqcM/2YXC+wdtkmp7SqG+vIb76CxpHVypzLlNVQ9PZSckQTafJrVFVIwSbcT1kfLW4VU9BWQKp1A8avJAYWqVmL9GPuQI8sWMLVuo2z8RLdPSSW59fY=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=wnb29YzZUzK1olWUavmfYFL2/Eg/ubk+Ux9mtrB1gomQgGQIG4ApQA6hwNM9xz9DiFC5fMVsidUFqNOjfVjvXD6VnLMTgYhro4oTb9YY2tQjDz9zRElsXSk5bglLJEGm8Btw3a6hK5PFKMNgnlqFKpjNLezGD+DhUflgJPx1dkU=;
Message-ID: <435578.85269.qm@web125906.mail.ne1.yahoo.com>
X-YMail-OSG: t.aATosVM1kJRNhNjxCd35DbrLOuY.FPHYCWWPcCAjaeZ2V oucO.rLDi.nMOC9qeeem77EXzjCgx2lGhQXmxYTnXjYt4Pxi0OmX.2RKex9M k8s9qJdaVV9CL9.pLutHIxLVyPkggtMysNgSHl18UN2YKWTLQwSq0rm.D3ro se23C6QgdkN1lX7obJB9fx5yo7BodJo59neYt9Fs9enl06NAtx3ZTRxGKsMS 0j.EtkRNDA_Ndu61LpUUU0uWsvxjxGsCMAlp3IrqHCd0NZaGMw2rhG9XMZp6 lCqa_4UreAHTp5daGy85yGvX6O1zUG6cmpkDiyEzsf.DUaJMXgLJhKnQtx27 G4RLGZgdtCNX86A_HxJOz0e8kLJrPlEBau10_vQmJFH2fQEj1
Received: from [71.233.102.170] by web125906.mail.ne1.yahoo.com via HTTP; Mon, 06 Jun 2011 12:14:39 PDT
X-Mailer: YahooMailClassic/14.0.1 YahooMailWebService/0.8.111.303096
Date: Mon, 6 Jun 2011 12:14:39 -0700 (PDT)
From: Gerald Ash <gash5107@yahoo.com>
Subject: RE: Generic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS Networks
To: MarlaAzinger <Marla.Azinger@FTR.com>
In-Reply-To: <2E2FECEBAE57CC4BAACDE67638305F1049E24E45BC@ROCH-EXCH1.corp.pvt>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1924068722-1307387679=:85269"
Cc: "mpls@ietf.org" <mpls@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 06 Jun 2011 19:15:13 -0000

--0-1924068722-1307387679=:85269
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Marla,
=A0
Thanks for your email.=A0 Please see responses below.

Regards,
Jerry

>=20
>=20
> --- On Wed, 6/1/11, Azinger, Marla <Marla.Azinger@FTR.com> wrote:
>=20
>=20
>=A0 From: Azinger, Marla <Marla.Azinger@FTR.com>
>=A0 Subject: RE: Generic Connection Admission Control (GCAC) Algorithm=20
> Specification for IP/MPLS Networks
>=A0 To: "Gerald Ash" <gash5107@yahoo.com>, "rtgwg@ietf.org" <rtgwg@ietf.or=
g>
>=A0 Cc: "mpls@ietf.org" <mpls@ietf.org>
>=A0 Date: Wednesday, June 1, 2011, 11:38 AM
>=20
>=20
>=A0 Jerry-
>=20
>=A0 Did you get a response from anyone on this yet?
=A0
I got one off-line comment=20
"this work looks good to me and seems somewhat over due..."
=A0
Given all the experts on this topic in the MPLS WG & RTGWG, it's a bit surp=
rising=A0there hasn't been more response.=A0 Not that long ago this topic w=
ould probably have generated strong reaction.

>=20
>=A0 Cheers
>=A0 Marla
>=20
>=20
>=20
> -------------------------------------------------------------------------=
-----
>=A0 From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf=
 Of=20
> Gerald Ash
>=A0 Sent: Thursday, May 26, 2011 9:51 AM
>=A0 To: rtgwg@ietf.org
>=A0 Cc: mpls@ietf.org
>=A0 Subject: Generic Connection Admission Control (GCAC) Algorithm=20
> Specification for IP/MPLS Networks
>=20
>=20
>=A0=A0=A0=A0=A0=A0=A0 Hi,
>=20
>=A0=A0=A0=A0=A0=A0=A0 Adrian has suggested that the RTGWG and the MPLS WG =
review the draft=20
> "Generic Connection Admission Control (GCAC) Algorithm Specification for=
=20
> IP/MPLS Networks", available at=20
> http://www.ietf.org/id/draft-ash-gcac-algorithm-spec-00.txt (abstract=20
> below).
>=20
>=A0=A0=A0=A0=A0=A0=A0 The underlying goal of the work is to specify an opt=
ional GCAC=20
> algorithm for IP/MPLS networks, to be adopted and implemented by vendors =
and=20
> service providers, that interoperates between vendor equipment and across=
=20
> multiple service provider domains.=A0 This would be analogous to the PNNI=
 GCAC=20
> that was widely adopted and helped promote interoperability of ATM networ=
ks.=20
> In addition, the approach:
>=A0=A0=A0=A0=A0=A0=A0 o is based on CSPF, widely implemented by vendors
>=A0=A0=A0=A0=A0=A0=A0 o does NOT include aspects of CAC that might be cons=
idered vendor=20
> proprietary implementations, such as detailed path selection mechanisms
>=A0=A0=A0=A0=A0=A0=A0 o relies on available standard mechanisms for MPLS b=
ased networks,=20
> such as RSVP, DSTE, PCE...
>=20
>=A0=A0=A0=A0=A0=A0=A0 Comments appreciated.
>=20
>=A0=A0=A0=A0=A0=A0=A0 Thanks,
>=A0=A0=A0=A0=A0=A0=A0 Jerry
>=20
>=A0=A0=A0=A0=A0=A0=A0 From: Internet-Drafts@ietf.org
>=A0=A0=A0=A0=A0=A0=A0 To: i-d-announce@ietf.org
>=A0=A0=A0=A0=A0=A0=A0 Reply-to: Internet-Drafts@ietf.org
>=A0=A0=A0=A0=A0=A0=A0 Subject: I-D ACTION:draft-ash-gcac-algorithm-spec-00=
.txt
>=A0=A0=A0=A0=A0=A0=A0 X-RSN: 1/0/935/34473/37870
>=20
>=A0=A0=A0=A0=A0=A0=A0 A New Internet-Draft is available from the on-line I=
nternet-Drafts
>=A0=A0=A0=A0=A0=A0=A0 directories.
>=20
>=A0=A0=A0=A0=A0=A0=A0 Title : Generic Connection Admission Control (GCAC) =
Algorithm=20
> Specification for IP/MPLS Networks
>=A0=A0=A0=A0=A0=A0=A0 Author(s) : G. Ash, D. McDysan
>=A0=A0=A0=A0=A0=A0=A0 Filename : draft-ash-gcac-algorithm-spec-00.txt
>=A0=A0=A0=A0=A0=A0=A0 Pages : 23
>=A0=A0=A0=A0=A0=A0=A0 Date : 2011-1-11
>=20
>=A0=A0=A0=A0=A0=A0=A0 This document presents a generic connection admissio=
n control (GCAC)
>=A0=A0=A0=A0=A0=A0=A0 reference model and algorithm for IP/MPLS-based netw=
orks. Service
>=A0=A0=A0=A0=A0=A0=A0 provider (SP) IP/MPLS networks need an MPLS GCAC mec=
hanism, for
>=A0=A0=A0=A0=A0=A0=A0 example, to reject voice over Internet Protocol (VoI=
P) calls when
>=A0=A0=A0=A0=A0=A0=A0 additional calls would adversely affect calls alread=
y in progress.
>=20
>=A0=A0=A0=A0=A0=A0=A0 Without MPLS GCAC, connections on congested links wi=
ll suffer
>=A0=A0=A0=A0=A0=A0=A0 degraded quality. The MPLS GCAC algorithm can be opt=
ionally
>=A0=A0=A0=A0=A0=A0=A0 implemented in vendor equipment and deployed by serv=
ice providers.
>=A0=A0=A0=A0=A0=A0=A0 MPLS GCAC interoperates between vendor equipment and=
 across multiple
>=A0=A0=A0=A0=A0=A0=A0 service provider domains. The MPLS GCAC algorithm us=
es available
>=A0=A0=A0=A0=A0=A0=A0 standard mechanisms for MPLS based networks, such as=
 RSVP, DSTE,=20
> PCE,
>=A0=A0=A0=A0=A0=A0=A0 NSIS, DiffServ, and OSPF. The MPLS GCAC algorithm do=
es not include
>=A0=A0=A0=A0=A0=A0=A0 aspects of CAC that might be considered vendor propr=
ietary
>=A0=A0=A0=A0=A0=A0=A0 implementations, such as detailed path selection mec=
hanisms. MPLS
>=A0=A0=A0=A0=A0=A0=A0 GCAC functions are implemented in a distributed mann=
er to deliver=20
> the
>=A0=A0=A0=A0=A0=A0=A0 objective QoS for specified QoS constraints. The sou=
rce is able to
>=A0=A0=A0=A0=A0=A0=A0 compute a source route with high likelihood that MPL=
S GCAC via
>=A0=A0=A0=A0=A0=A0=A0 elements along the selected path will in fact admit =
the request.
>=A0=A0=A0=A0=A0=A0=A0 MPLS GCAC is applicable to any service or flow that =
must meet an
>=A0=A0=A0=A0=A0=A0=A0 objective QoS (delay, jitter, packet loss rate) for =
a specified
>=A0=A0=A0=A0=A0=A0=A0 quantity of traffic.
>=20
>=A0=A0=A0=A0=A0=A0=A0 A URL for this Internet-Draft is:
>=A0=A0=A0=A0=A0=A0=A0 http://www.ietf.org/internet-drafts/draft-ash-gcac-a=
lgorithm-spec-00.txt
>=20
>=A0=A0=A0=A0=A0=A0=A0 Internet-Drafts are also available by anonymous FTP =
at:
>=A0=A0=A0=A0=A0=A0=A0 ftp://ftp.ietf.org/internet-drafts/
>=20
>=A0=A0=A0=A0=A0=A0=A0 Below is the data which will enable a MIME compliant=
 mail reader
>=A0=A0=A0=A0=A0=A0=A0 implementation to automatically retrieve the ASCII v=
ersion of the
>=A0=A0=A0=A0=A0=A0=A0 Internet-Draft.
>=A0=A0=A0=A0=A0=A0=A0 _______________________________________________
>=A0=A0=A0=A0=A0=A0=A0 I-D-Announce mailing list
>=A0=A0=A0=A0=A0=A0=A0 I-D-Announce@ietf.org
>=A0=A0=A0=A0=A0=A0=A0 https://www.ietf.org/mailman/listinfo/i-d-announce
>=A0=A0=A0=A0=A0=A0=A0 Internet-Draft directories: http://www.ietf.org/shad=
ow.html
>=A0=A0=A0=A0=A0=A0=A0 or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=A0=A0=A0=A0=A0=A0=A0 *****
>=A0=A0=A0=A0=A0=A0=A0 Click below to download the attachment(s) in this me=
ssage:
>=A0=A0=A0=A0=A0=A0=A0 <A=20
> HREF=3D"http://www.ietf.org/ibin/c5i?mid=3D6&gid=3D0&rid=3D8&k1=3D935&fil=
e=3Di-d-announce.37870.1.txt">Attachment:=20
> draft_ash_gcac_algorithm_spec_00.txt</A> (1K)
>=20
>
--0-1924068722-1307387679=:85269
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<table cellspacing=3D"0" cellpadding=3D"0" border=3D"0" ><tr><td valign=3D"=
top" style=3D"font: inherit;"><DIV>Hi Marla,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks for your email.&nbsp; Please see responses below.<BR></DIV>
<DIV>Regards,</DIV>
<DIV>Jerry</DIV>
<DIV><BR>&gt; <BR>&gt; <BR>&gt; --- On Wed, 6/1/11, Azinger, Marla &lt;<A h=
ref=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:ma=
ilto:Marla.Azinger@FTR.com">Marla.Azinger@FTR.com</A>&gt; wrote:<BR>&gt; <B=
R>&gt; <BR>&gt;&nbsp; From: Azinger, Marla &lt;<A href=3D"mhtml:{B096A9AC-8=
D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:mailto:Marla.Azinger@FTR.c=
om">Marla.Azinger@FTR.com</A>&gt;<BR>&gt;&nbsp; Subject: RE: Generic Connec=
tion Admission Control (GCAC) Algorithm <BR>&gt; Specification for IP/MPLS =
Networks<BR>&gt;&nbsp; To: "Gerald Ash" &lt;<A href=3D"mhtml:{B096A9AC-8D5F=
-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:mailto:gash5107@yahoo.com">ga=
sh5107@yahoo.com</A>&gt;, "<A href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1=
B5E65A}mid://00000022/!x-usc:mailto:rtgwg@ietf.org">rtgwg@ietf.org</A>" &lt=
;<A href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-u=
sc:mailto:rtgwg@ietf.org">rtgwg@ietf.org</A>&gt;<BR>&gt;&nbsp; Cc: "<A
 href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:=
mailto:mpls@ietf.org">mpls@ietf.org</A>" &lt;<A href=3D"mhtml:{B096A9AC-8D5=
F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:mailto:mpls@ietf.org">mpls@i=
etf.org</A>&gt;<BR>&gt;&nbsp; Date: Wednesday, June 1, 2011, 11:38 AM<BR>&g=
t; <BR>&gt; <BR>&gt;&nbsp; Jerry-<BR>&gt; <BR>&gt;&nbsp; Did you get a resp=
onse from anyone on this yet?</DIV>
<DIV>&nbsp;</DIV>
<DIV>I got one off-line comment </DIV>
<DIV>"this work looks good to me and seems somewhat over due..."</DIV>
<DIV>&nbsp;</DIV>
<DIV>Given all the experts on this topic in the MPLS WG &amp; RTGWG, it's a=
 bit surprising&nbsp;there hasn't been more response.&nbsp; Not that long a=
go this topic would probably have generated strong reaction.</DIV>
<DIV><BR>&gt; <BR>&gt;&nbsp; Cheers<BR>&gt;&nbsp; Marla<BR>&gt; <BR>&gt; <B=
R>&gt; <BR>&gt; -----------------------------------------------------------=
-------------------<BR>&gt;&nbsp; From: <A href=3D"mhtml:{B096A9AC-8D5F-4D5=
A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:mailto:rtgwg-bounces@ietf.org">rt=
gwg-bounces@ietf.org</A> [mailto:rtgwg-bounces@ietf.org] On Behalf Of <BR>&=
gt; Gerald Ash<BR>&gt;&nbsp; Sent: Thursday, May 26, 2011 9:51 AM<BR>&gt;&n=
bsp; To: <A href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000=
022/!x-usc:mailto:rtgwg@ietf.org">rtgwg@ietf.org</A><BR>&gt;&nbsp; Cc: <A h=
ref=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:ma=
ilto:mpls@ietf.org">mpls@ietf.org</A><BR>&gt;&nbsp; Subject: Generic Connec=
tion Admission Control (GCAC) Algorithm <BR>&gt; Specification for IP/MPLS =
Networks<BR>&gt; <BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Hi,<BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Adrian
 has suggested that the RTGWG and the MPLS WG review the draft <BR>&gt; "Ge=
neric Connection Admission Control (GCAC) Algorithm Specification for <BR>&=
gt; IP/MPLS Networks", available at <BR>&gt; <A href=3D"mhtml:{B096A9AC-8D5=
F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:http://www.ietf.org/id/draft=
-ash-gcac-algorithm-spec-00.txt">http://www.ietf.org/id/draft-ash-gcac-algo=
rithm-spec-00.txt</A> (abstract <BR>&gt; below).<BR>&gt; <BR>&gt;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The underlying goal of the work is to spec=
ify an optional GCAC <BR>&gt; algorithm for IP/MPLS networks, to be adopted=
 and implemented by vendors and <BR>&gt; service providers, that interopera=
tes between vendor equipment and across <BR>&gt; multiple service provider =
domains.&nbsp; This would be analogous to the PNNI GCAC <BR>&gt; that was w=
idely adopted and helped promote interoperability of ATM networks. <BR>&gt;=
 In addition, the
 approach:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o is based on =
CSPF, widely implemented by vendors<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; o does NOT include aspects of CAC that might be considered vendo=
r <BR>&gt; proprietary implementations, such as detailed path selection mec=
hanisms<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o relies on avail=
able standard mechanisms for MPLS based networks, <BR>&gt; such as RSVP, DS=
TE, PCE...<BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Comme=
nts appreciated.<BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Thanks,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jerry<BR>&gt; <B=
R>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From: <A href=3D"mhtml:{B0=
96A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:mailto:Internet-Dr=
afts@ietf.org">Internet-Drafts@ietf.org</A><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; To: <A
 href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:=
mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A><BR>&gt;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Reply-to: <A href=3D"mhtml:{B096A9AC-8D5F-4D=
5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:mailto:Internet-Drafts@ietf.org"=
>Internet-Drafts@ietf.org</A><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Subject: I-D ACTION:draft-ash-gcac-algorithm-spec-00.txt<BR>&gt;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; X-RSN: 1/0/935/34473/37870<BR>&gt; <BR=
>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A New Internet-Draft is ava=
ilable from the on-line Internet-Drafts<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; directories.<BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; Title : Generic Connection Admission Control (GCAC) Algorithm <=
BR>&gt; Specification for IP/MPLS Networks<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; Author(s) : G. Ash, D.
 McDysan<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename : draft=
-ash-gcac-algorithm-spec-00.txt<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; Pages : 23<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date : =
2011-1-11<BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This d=
ocument presents a generic connection admission control (GCAC)<BR>&gt;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; reference model and algorithm for IP/=
MPLS-based networks. Service<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; provider (SP) IP/MPLS networks need an MPLS GCAC mechanism, for<BR>&gt;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; example, to reject voice over In=
ternet Protocol (VoIP) calls when<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; additional calls would adversely affect calls already in progress.=
<BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Without MPLS GC=
AC, connections on congested links will
 suffer<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; degraded quality.=
 The MPLS GCAC algorithm can be optionally<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; implemented in vendor equipment and deployed by service p=
roviders.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS GCAC inter=
operates between vendor equipment and across multiple<BR>&gt;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; service provider domains. The MPLS GCAC algori=
thm uses available<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; standa=
rd mechanisms for MPLS based networks, such as RSVP, DSTE, <BR>&gt; PCE,<BR=
>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NSIS, DiffServ, and OSPF. T=
he MPLS GCAC algorithm does not include<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; aspects of CAC that might be considered vendor proprietary<B=
R>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; implementations, such as d=
etailed path selection mechanisms.
 MPLS<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GCAC functions are =
implemented in a distributed manner to deliver <BR>&gt; the<BR>&gt;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; objective QoS for specified QoS constrai=
nts. The source is able to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; compute a source route with high likelihood that MPLS GCAC via<BR>&gt;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements along the selected path wi=
ll in fact admit the request.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; MPLS GCAC is applicable to any service or flow that must meet an<BR>&g=
t;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; objective QoS (delay, jitter, =
packet loss rate) for a specified<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; quantity of traffic.<BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; A URL for this Internet-Draft is:<BR>&gt;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; <A
 href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:=
http://www.ietf.org/internet-drafts/draft-ash-gcac-algorithm-spec-00.txt">h=
ttp://www.ietf.org/internet-drafts/draft-ash-gcac-algorithm-spec-00.txt</A>=
<BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet-Drafts=
 are also available by anonymous FTP at:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; <A href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid:=
//00000022/!x-usc:ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/i=
nternet-drafts/</A><BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Below is the data which will enable a MIME compliant mail reader<BR>&gt=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; implementation to automatically=
 retrieve the ASCII version of the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; Internet-Draft.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 _______________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; I-D-Announce mailing list<BR>&gt;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; <A href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5=
E65A}mid://00000022/!x-usc:mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.=
org</A><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A href=3D"mhtml:=
{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:https://www.iet=
f.org/mailman/listinfo/i-d-announce">https://www.ietf.org/mailman/listinfo/=
i-d-announce</A><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet=
-Draft directories: <A href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}=
mid://00000022/!x-usc:http://www.ietf.org/shadow.html">http://www.ietf.org/=
shadow.html</A><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or <A
 href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000022/!x-usc:=
ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-=
sites.txt</A><BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; **=
***<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Click below to downlo=
ad the attachment(s) in this message:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; &lt;A <BR>&gt; HREF=3D"<A href=3D'mhtml:{B096A9AC-8D5F-4D5A-AA=
CE-EC56A1B5E65A}mid://00000022/!x-usc:http://www.ietf.org/ibin/c5i?mid=3D6&=
amp;gid=3D0&amp;rid=3D8&amp;k1=3D935&amp;file=3Di-d-announce.37870.1.txt">A=
ttachment'>http://www.ietf.org/ibin/c5i?mid=3D6&amp;gid=3D0&amp;rid=3D8&amp=
;k1=3D935&amp;file=3Di-d-announce.37870.1.txt"&gt;Attachment</A>: <BR>&gt; =
draft_ash_gcac_algorithm_spec_00.txt&lt;/A&gt; (1K)<BR>&gt; <BR>&gt;</DIV><=
/td></tr></table>
--0-1924068722-1307387679=:85269--

From ning.so@verizonbusiness.com  Fri Jun 10 09:08:09 2011
Return-Path: <ning.so@verizonbusiness.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 859D911E8213 for <rtgwg@ietfa.amsl.com>; Fri, 10 Jun 2011 09:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZmhfYCxUaVon for <rtgwg@ietfa.amsl.com>; Fri, 10 Jun 2011 09:08:09 -0700 (PDT)
Received: from ashesmtp01.verizonbusiness.com (ashesmtp01.verizonbusiness.com [198.4.8.163]) by ietfa.amsl.com (Postfix) with ESMTP id DE13E11E820C for <rtgwg@ietf.org>; Fri, 10 Jun 2011 09:08:08 -0700 (PDT)
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 <0LML00F1R0THNO50@firewall.verizonbusiness.com> for rtgwg@ietf.org; Fri, 10 Jun 2011 16:08:06 +0000 (GMT)
Received: from pdcismtp01.vzbi.com ([unknown] [127.0.0.1]) by pdcismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LML006CP0TH8V00@pdcismtp01.vzbi.com> for rtgwg@ietf.org; Fri, 10 Jun 2011 16:08:05 +0000 (GMT)
Received: from ASHSRV139.mcilink.com ([unknown] [153.39.68.165]) by pdcismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LML006BE0TH7W00@pdcismtp01.vzbi.com> for rtgwg@ietf.org; Fri, 10 Jun 2011 16:08:05 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV139.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 10 Jun 2011 16:08:05 +0000
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: base64
Subject: RE: New Version Notification for draft-so-yong-rtgwg-cl-framework-04.txt
Date: Fri, 10 Jun 2011 16:07:58 +0000
Message-id: <14584D6EE26B314187A4F68BA2060600079F6CB3@ASHEVS008.mcilink.com>
In-reply-to: <20110610151529.1373.71073.idtracker@ietfa.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: New Version Notification for draft-so-yong-rtgwg-cl-framework-04.txt
Thread-index: AcwngT9zbmpAkTMISGevSXQCoy9/WAABglSg
References: <20110610151529.1373.71073.idtracker@ietfa.amsl.com>
From: "So, Ning" <ning.so@verizonbusiness.com>
To: rtgwg@ietf.org
X-OriginalArrivalTime: 10 Jun 2011 16:08:05.0203 (UTC) FILETIME=[94C75A30:01CC2788]
Cc: cvillamizar@infinera.com, "Malis, Andrew G \(Andy\)" <andrew.g.malis@verizon.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 10 Jun 2011 16:08:09 -0000

UGxlYXNlIG5vdGUgd2UgaGF2ZSB1cGxvYWRlZCBhIHJldmlzZWQgdmVyc2lvbiBvZiBDb21wb3Np
dGUgTGluayBGcmFtZXdvcmsgZHJhZnQuICBUaGlzIG5ldyByZXZpc2lvbiBpbmNsdWRlZCBkZXNj
cmlwdGlvbnMgb2YgcHJvdG9jb2xzIGNhbiBiZSB1c2VkIHRvIGltcGxlbWVudCBDb21wb3NpdGUg
TGluaywgYW5kIHNvbWUgZ2FwcyBleGlzdCB0aGF0IG5lZWQgcHJvdG9jb2wgc29sdXRpb25zLiAg
UGxlYXNlIGZlZWwgZnJlZSB0byBtYWtlIGNvbW1lbnRzIGFuZCBzdWdnZXN0aW9ucy4gIA0KDQpB
bGlhLA0KDQpCYXNlZCBvbiB5b3VyIHN0YXRlbWVudCBkdXJpbmcgdGhlIGxhc3QgbWVldGluZywg
Y2FuIHdlIGFkb3B0IHRoZSBjdXJyZW50IHZlcnNpb24gYXMgdGhlIFdHIGRyYWZ0PyAgV2UgY2Fu
IGNoYW5nZSB0aGUgbmFtZSBhbmQgcmVsb2FkIGlmIGFwcHJvdmVkLiAgVGhhbmtzLiANCg0KIA0K
QmVzdCByZWdhcmRzLA0KIA0KTmluZyBTbw0KTmV0d29yayBFdm9sdXRpb24gUGxhbm5pbmcNClZl
cml6b24sIEluYy4NCihvZmZpY2UpIDk3Mi03MjktNzkwNQ0KKENlbGwpIDk3Mi05NTUtMDkxNA0K
IA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGll
dGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6IEZyaWRheSwg
SnVuZSAxMCwgMjAxMSAxMDoxNSBBTQ0KVG86IGx1Y3l5b25nQGh1YXdlaS5jb20NCkNjOiBjdmls
bGFtaXphckBpbmZpbmVyYS5jb207IFNvLCBOaW5nOyB0b255LmxpQHRvbnkubGk7IE1jRHlzYW4s
IERhdmlkIEUgKERhdmUpOyBNYWxpcywgQW5kcmV3IEcgKEFuZHkpOyBsdWN5eW9uZ0BodWF3ZWku
Y29tDQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXNvLXlvbmct
cnRnd2ctY2wtZnJhbWV3b3JrLTA0LnR4dA0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQt
c28teW9uZy1ydGd3Zy1jbC1mcmFtZXdvcmstMDQudHh0IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBz
dWJtaXR0ZWQgYnkgTHVjeSBZb25nIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4N
Cg0KRmlsZW5hbWU6CSBkcmFmdC1zby15b25nLXJ0Z3dnLWNsLWZyYW1ld29yaw0KUmV2aXNpb246
CSAwNA0KVGl0bGU6CQkgQ29tcG9zaXRlIExpbmsgRnJhbWV3b3JrIGluIE11bHRpIFByb3RvY29s
IExhYmVsIFN3aXRjaGluZyAoTVBMUykNCkNyZWF0aW9uIGRhdGU6CSAyMDExLTA2LTA5DQpXRyBJ
RDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdlczogMTENCg0KQWJzdHJh
Y3Q6DQogICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBhIGNvbXBvc2l0ZSBsaW5rIGZyYW1ld29y
ayBpbiBNUExTIG5ldHdvcmsuDQogICBBIGNvbXBvc2l0ZSBsaW5rIGNvbnNpc3RzIG9mIGEgZ3Jv
dXAgb2YgaG9tb2dlbm91cyBvciBub24taG9tb2dlbm91cw0KICAgbGlua3MgdGhhdCBoYXZlIHRo
ZSBzYW1lIGZvcndhcmQgYWRqYWNlbmN5IGFuZCBjYW4gYmUgY29uc2lkZXJlZCBhcw0KICAgYSBz
aW5nbGUgVEUgbGluayBvciBhbiBJUCBsaW5rIGluIHJvdXRpbmcuIEEgY29tcG9zaXRlIGxpbmsg
cmVsaWVzDQogICBvbiBpdHMgY29tcG9uZW50IGxpbmtzIHRvIGNhcnJ5IHRoZSB0cmFmZmljIG92
ZXIgdGhlIGNvbXBvc2l0ZSBsaW5rLg0KICAgVGhlIGRvY3VtZW50IHNwZWNpZmllcyBjb21wb3Np
dGUgbGluayBmcmFtZXdvcmsuIEFwcGxpY2FiaWxpdHkgaXMNCiAgIGRlc2NyaWJlZCBmb3IgYSBz
aW5nbGUgcGFpciBvZiBNUExTLWNhcGFibGUgbm9kZXMsIGEgc2VxdWVuY2Ugb2YNCiAgIE1QTFMt
Y2FwYWJsZSBub2Rlcywgb3IgYSBzZXQgb2YgbGF5ZXIgbmV0d29ya3MgY29ubmVjdGluZyBNUExT
LQ0KICAgY2FwYWJsZSBub2Rlcy4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClRo
ZSBJRVRGIFNlY3JldGFyaWF0DQo=

From ning.so@verizonbusiness.com  Tue Jun 21 10:28:23 2011
Return-Path: <ning.so@verizonbusiness.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0338A11E8087 for <rtgwg@ietfa.amsl.com>; Tue, 21 Jun 2011 10:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3395J-MANggh for <rtgwg@ietfa.amsl.com>; Tue, 21 Jun 2011 10:28:22 -0700 (PDT)
Received: from ashesmtp02.verizonbusiness.com (ashesmtp02.verizonbusiness.com [198.4.8.166]) by ietfa.amsl.com (Postfix) with ESMTP id 2392911E8171 for <rtgwg@ietf.org>; Tue, 21 Jun 2011 10:28:21 -0700 (PDT)
Received: from pdcismtp03.vzbi.com ([unknown] [166.40.77.73]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LN500K1VHV8DY90@firewall.verizonbusiness.com> for rtgwg@ietf.org; Tue, 21 Jun 2011 17:28:20 +0000 (GMT)
Received: from pdcismtp03.vzbi.com ([unknown] [127.0.0.1]) by pdcismtp03.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LN5000HBHV8VK00@pdcismtp03.vzbi.com> for rtgwg@ietf.org; Tue, 21 Jun 2011 17:28:20 +0000 (GMT)
Received: from ASHSRV142.mcilink.com ([unknown] [153.39.68.168]) by pdcismtp03.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LN5000BLHV8UQ00@pdcismtp03.vzbi.com> for rtgwg@ietf.org; Tue, 21 Jun 2011 17:28:20 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV142.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 21 Jun 2011 17:28:20 +0000
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-version: 1.0
Content-type: multipart/alternative; boundary="----_=_NextPart_001_01CC3038.9CD9D79E"
Subject: Requesting adoption as WG draft
Date: Tue, 21 Jun 2011 17:28:19 +0000
Message-id: <14584D6EE26B314187A4F68BA206060007AF9AF1@ASHEVS008.mcilink.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: Requesting adoption as WG draft
Thread-index: AcwwOAA+2lCeP/jkTWyNQ4Enqa36XA==
From: "So, Ning" <ning.so@verizonbusiness.com>
To: rtgwg@ietf.org
X-OriginalArrivalTime: 21 Jun 2011 17:28:20.0214 (UTC) FILETIME=[9D4AF960:01CC3038]
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 21 Jun 2011 17:28:23 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC3038.9CD9D79E
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Dear WG chairs,

=20

Have you had a chance to look at the updated Composite Link Framework
draft (draft-so-yong-rtgwg-cl-framework-04
<http://datatracker.ietf.org/doc/draft-so-yong-rtgwg-cl-framework/> )?
Alia made the comment in last IETF meeting that this draft is likely to
be adopted as WG draft, because the Composite Link Requirement has
already passed WG last call.  Just want to check and see when will you
have some time to make the announcement.    Thanks a lot.

=20

=20

Best regards,

=20

Ning So

Network Evolution Planning

Verizon, Inc.

(office) 972-729-7905

(Cell) 972-955-0914

=20


------_=_NextPart_001_01CC3038.9CD9D79E
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Dear WG =
chairs,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Have you had a chance to look at the updated Composite =
Link Framework draft (<a =
href=3D"http://datatracker.ietf.org/doc/draft-so-yong-rtgwg-cl-framework/=
">draft-so-yong-rtgwg-cl-framework-04</a>)?&nbsp; Alia made the comment =
in last IETF meeting that this draft is likely to be adopted as WG =
draft, because the Composite Link Requirement has already passed WG last =
call.&nbsp; Just want to check and see when will you have some time to =
make the announcement.&nbsp; &nbsp;&nbsp;Thanks a lot.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Best =
regards,</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Ning =
So</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Network =
Evolution Planning</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Verizon, =
Inc.</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>(office) =
972-729-7905</span><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>(Cell) =
972-955-0914</span><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;</span><o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CC3038.9CD9D79E--

From akatlas@gmail.com  Tue Jun 21 11:10:52 2011
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBF0311E8086 for <rtgwg@ietfa.amsl.com>; Tue, 21 Jun 2011 11:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Wb0zvJbFjOw for <rtgwg@ietfa.amsl.com>; Tue, 21 Jun 2011 11:10:52 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 379AB11E8153 for <rtgwg@ietf.org>; Tue, 21 Jun 2011 11:10:52 -0700 (PDT)
Received: by pwj5 with SMTP id 5so116216pwj.31 for <rtgwg@ietf.org>; Tue, 21 Jun 2011 11:10:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vo3V8D0sN/6VLyLf93ueutsjsPhaKFCephsmaNAWKBs=; b=vG50Jacdo5pIOuojLqn2ZbzPHk0wmo44VVpeddMmyM6yO09SMSqZAwQYkl2l2xP8PD HSFCd7l/juTcxCRWstKsgaEA+Jf85IiYcSmq7W6RPH0exQt61wpb4JwzpdZmLZGejNOJ PRgg/3ScYluwah43T1AjSdOmSZAzbnx4/zFXw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=oPN4hT6aiEOfoXT4KXqy+uXwvdEOsKR8jZHNswkvZquSf5P9fU000DYdfnjYBy2/lm dVS+bnTV/2TMp3XM92XOjfCzotz5Vp6E5jLdw+A0qfw/XG+1UeQwQ70QaNYUOkOfMC4I ncFO5dQRnv2J9IdbwcxEUJACg4XDvdMg0f7xs=
MIME-Version: 1.0
Received: by 10.68.13.73 with SMTP id f9mr3247963pbc.100.1308679847486; Tue, 21 Jun 2011 11:10:47 -0700 (PDT)
Received: by 10.68.46.98 with HTTP; Tue, 21 Jun 2011 11:10:47 -0700 (PDT)
In-Reply-To: <14584D6EE26B314187A4F68BA206060007AF9AF1@ASHEVS008.mcilink.com>
References: <14584D6EE26B314187A4F68BA206060007AF9AF1@ASHEVS008.mcilink.com>
Date: Tue, 21 Jun 2011 14:10:47 -0400
Message-ID: <BANLkTim8YqME5-sTwdyDh+pyHN39fWYjTg@mail.gmail.com>
Subject: Re: Requesting adoption as WG draft
From: Alia Atlas <akatlas@gmail.com>
To: "So, Ning" <ning.so@verizonbusiness.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 21 Jun 2011 18:10:53 -0000

I will read carefully the new version in the next week.
Any acceptance as a WG draft would be after querying the list, of course.

That said, please read this updated draft and comment here.  It would be go=
od
to get this done and a decision made before the next IETF.

Alia


On Tue, Jun 21, 2011 at 1:28 PM, So, Ning <ning.so@verizonbusiness.com> wro=
te:
> Dear WG chairs,
>
>
>
> Have you had a chance to look at the updated Composite Link Framework dra=
ft
> (draft-so-yong-rtgwg-cl-framework-04)?=A0 Alia made the comment in last I=
ETF
> meeting that this draft is likely to be adopted as WG draft, because the
> Composite Link Requirement has already passed WG last call.=A0 Just want =
to
> check and see when will you have some time to make the announcement.
> =A0=A0Thanks a lot.
>
>
>
>
>
> Best regards,
>
>
>
> Ning So
>
> Network Evolution Planning
>
> Verizon, Inc.
>
> (office) 972-729-7905
>
> (Cell) 972-955-0914
>
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
>

From stbryant@cisco.com  Wed Jun 22 07:29:40 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7786811E8123; Wed, 22 Jun 2011 07:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.543
X-Spam-Level: 
X-Spam-Status: No, score=-110.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QLgaN7z2Er8h; Wed, 22 Jun 2011 07:29:39 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 26CB911E8108; Wed, 22 Jun 2011 07:29:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=606; q=dns/txt; s=iport; t=1308752979; x=1309962579; h=message-id:date:from:reply-to:mime-version:to:cc:subject: content-transfer-encoding; bh=HbbipZ6BAtjyMst4Nu4ohKt2ah0q4yujyvqS/VTQBWE=; b=ShcaA3KuSKOPm88AeTqujr4vpWh62dbTdIMVAJirXdeq9VfsmJvFbCyE /pp0U+ly8C63Bi5rZQRIFKAS7HROARn7x01VWy5HvDF3DliLQT8JLqTJE qa1KCPMg25CG0xm5ma2y8D3I+Qw0Scx95XPiZvzo1Na0wo6t/ux1owkMm s=;
X-IronPort-AV: E=Sophos;i="4.65,406,1304294400"; d="scan'208";a="96017818"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 22 Jun 2011 14:29:34 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5METYWL014869; Wed, 22 Jun 2011 14:29:34 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-116.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p5METWF5020425; Wed, 22 Jun 2011 15:29:33 +0100 (BST)
Message-ID: <4E01FC7D.5080209@cisco.com>
Date: Wed, 22 Jun 2011 15:30:21 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: RTGWG chairs
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org" <iesg@ietf.org>, 'Alexey Zinin' <azinin@cisco.com>, Alia Atlas <akatlas@juniper.net>, "John G. Scudder" <jgs@juniper.net>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 22 Jun 2011 14:29:40 -0000

This message is to announce a change to the leadership
of the Routing Area Working Group.

Alex Zinin, a founder chair of the working group, is
standing down due to pressure of other work.

John Scudder, has volunteered to stand down as chair
so that a we do not have two chairs from the same
company. John of course continues as chair of
the IDR working group.

I thank them for their hard work over the years in RTGWG.

I would like to welcome Alvaro Retana (alvaro.retana@hp.com)
as incoming RTGWG Chair to join Alia Atlas (akatlas@juniper.net)
who continues in the role.

- Stewart

From akatlas@gmail.com  Wed Jun 22 08:22:03 2011
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E67DC11E811B; Wed, 22 Jun 2011 08:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGzCE43yOfYF; Wed, 22 Jun 2011 08:22:02 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3496011E8117; Wed, 22 Jun 2011 08:22:02 -0700 (PDT)
Received: by pzk5 with SMTP id 5so639580pzk.31 for <multiple recipients>; Wed, 22 Jun 2011 08:22:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=o5uV/j2fhhNL7o9vGVajR71DmsExZ2ZRjP9Y3/EEcNw=; b=oL+SPiwuaXGNexZrEH5omW2ke2FGBQy4BNoV51RELFLFgcqTvjX4iSr7qaXm64fuxw LDZK+RaZLPlV6lqnyBuTe1XeXhHF8KLPmSOAaqJslIzLv0q9ZuIF8E3froiGafH8ZWYj EJg6P0tBHBDjYiUwdLV2GT5hgxXd89JXdkyCY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=vb0y7SSK0vzVDzOEU55ZmRJsi+JXs9kQLuXxBhMMMDJkcKtXYegRjgEAFmfGbseBkC F9K3ytNlEW+aGu2UhUz47Iea9vudJoFvc9DqzjEv4aNO2TyHagmunAdritpEhYSwm4OK S/epV5lm9T00IJyD3t4r/McT2fWJuzwQCTPrU=
MIME-Version: 1.0
Received: by 10.68.46.73 with SMTP id t9mr480610pbm.234.1308756121645; Wed, 22 Jun 2011 08:22:01 -0700 (PDT)
Received: by 10.68.46.98 with HTTP; Wed, 22 Jun 2011 08:22:01 -0700 (PDT)
In-Reply-To: <4E01FC7D.5080209@cisco.com>
References: <4E01FC7D.5080209@cisco.com>
Date: Wed, 22 Jun 2011 11:22:01 -0400
Message-ID: <BANLkTi=OJYp6T7CL1CeWr9_hptmqiwK8+g@mail.gmail.com>
Subject: Re: RTGWG chairs
From: Alia Atlas <akatlas@gmail.com>
To: stbryant@cisco.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: Alexey Zinin <azinin@cisco.com>, "John G. Scudder" <jgs@juniper.net>, Alia Atlas <akatlas@juniper.net>, "iesg@ietf.org" <iesg@ietf.org>, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 22 Jun 2011 15:22:03 -0000

I would also like to thank Alex & John for their work over the past
several years.
I look forward to working with Alvaro.

Alia

On Wed, Jun 22, 2011 at 10:30 AM, Stewart Bryant <stbryant@cisco.com> wrote:
>
> This message is to announce a change to the leadership
> of the Routing Area Working Group.
>
> Alex Zinin, a founder chair of the working group, is
> standing down due to pressure of other work.
>
> John Scudder, has volunteered to stand down as chair
> so that a we do not have two chairs from the same
> company. John of course continues as chair of
> the IDR working group.
>
> I thank them for their hard work over the years in RTGWG.
>
> I would like to welcome Alvaro Retana (alvaro.retana@hp.com)
> as incoming RTGWG Chair to join Alia Atlas (akatlas@juniper.net)
> who continues in the role.
>
> - Stewart
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>

From akatlas@gmail.com  Fri Jun 24 14:36:19 2011
Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE0F911E8111 for <rtgwg@ietfa.amsl.com>; Fri, 24 Jun 2011 14:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.585
X-Spam-Level: 
X-Spam-Status: No, score=-3.585 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bp4SJpsq6yVG for <rtgwg@ietfa.amsl.com>; Fri, 24 Jun 2011 14:36:19 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id F0FA011E809E for <rtgwg@ietf.org>; Fri, 24 Jun 2011 14:36:18 -0700 (PDT)
Received: by pwj5 with SMTP id 5so2194685pwj.31 for <rtgwg@ietf.org>; Fri, 24 Jun 2011 14:36:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=EUtW3wlgOeSflat9aK6iF+OB/+Qv5XB5XfP8iwNtyGo=; b=sdIgx2WtMApP6D2NxFq+9xv29g2klq9ZxPmNmZ2fVVETCPpuazHyvrqQyyiRnCRMwz xXc7v2TvRN7XBYZeu/uNm620f/IOOoDBSdNy7XYfIONB/bmxOCuyJUquQuuTaed0vnu+ XVrEi4XhqaRu1i8hEkc+dilNEtqMWLpyrOTfY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=kM2UYQtQG7OIge4wULR+Vn5Tz0538Y/qOqtrB6HCKSNVE2sTTYbT8hxm2Cg7Oxj2FH z3lT10DKs2A6vRGeLQk46aaG4jRNS3DHqzyrX4cIluIJghqI0yzukZmxyJAdG7FRlDbT w/BQisWS1qBzrPVee21RK5CzDZ3z8mdG37lQM=
MIME-Version: 1.0
Received: by 10.68.11.196 with SMTP id s4mr2048446pbb.301.1308951378457; Fri, 24 Jun 2011 14:36:18 -0700 (PDT)
Received: by 10.68.54.69 with HTTP; Fri, 24 Jun 2011 14:36:18 -0700 (PDT)
In-Reply-To: <BANLkTik8SkTz3fhR1pYmHQii-g6C1YHkxA@mail.gmail.com>
References: <20110624183513.7035311E81A8@ietfa.amsl.com> <BANLkTik8SkTz3fhR1pYmHQii-g6C1YHkxA@mail.gmail.com>
Date: Fri, 24 Jun 2011 17:36:18 -0400
Message-ID: <BANLkTimcRwjk8vAt9-NReVEvgB9X7CK5hg@mail.gmail.com>
Subject: Fwd: Please help the Nomcom
From: Alia Atlas <akatlas@gmail.com>
To: rtgwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 24 Jun 2011 21:36:19 -0000

FYI

---------- Forwarded message ----------
From: NomCom Chair <nomcom-chair@ietf.org>
Date: Fri, Jun 24, 2011 at 11:35 AM
Subject: Please help the Nomcom
To: Working Group Chairs <wgchairs@ietf.org>


Hi WG chairs,
=A0We have had a good response to the first call for volunteers but the
rate at which new volunteers are coming in is slowing down. The Nomcom
process is best served by a large pool of volunteers drawn from a wide
spectrum of IETF attendees. Where else would we find this wide spectrum
if not in the WG mailing lists.

I would really appreciate it if you can forward the message onto your
working group mailing lists.

The latest volunteer status and the second call for volunteers can be
found at
https://datatracker.ietf.org/ann/nomcom/2964/

Thanks in advance for your help.

Suresh Krishnan
Nomcom Chair 2011-2012
Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com
_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area

From azinin@cisco.com  Sat Jun 25 06:24:26 2011
Return-Path: <azinin@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC5D21F84F1; Sat, 25 Jun 2011 06:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NtixW9dwd5JE; Sat, 25 Jun 2011 06:24:25 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 783B321F84F0; Sat, 25 Jun 2011 06:24:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=azinin@cisco.com; l=2063; q=dns/txt; s=iport; t=1309008265; x=1310217865; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:from:to:cc; bh=hsTTPd+kMd4/DkYNoiCF8au0Kz3OvtRhwZNzu0kLR3w=; b=MrWZMZNLY/L0ktZNMvebqBfCwAwlrFbprLuGiW+iBVtDiUN0Fqiip780 imEyyDHkUQshkhc7BGFZ6PBHSQhjNH6BZiR+DOR/HTSdDz5IkTZoItTOu 9ttS6jit8Rl6s3e7PWaZx3I4IVVG7ZuU0aBg7AIdNrFBzZxR+809xamxZ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsAAN3dBU6tJV2Y/2dsb2JhbABTmByPLHetEp05hjAEhyyPToRAhwI
X-IronPort-AV: E=Sophos;i="4.65,424,1304294400"; d="scan'208";a="347191179"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by sj-iport-3.cisco.com with ESMTP; 25 Jun 2011 13:24:24 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5PDOOOl018517;  Sat, 25 Jun 2011 13:24:24 GMT
Received: from xmb-rcd-302.cisco.com ([72.163.63.17]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 25 Jun 2011 08:24:24 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: RTGWG chairs
Date: Sat, 25 Jun 2011 08:24:24 -0500
Message-ID: <48E0496A08C51449B1C8040CDF55DE1F0146B28F@XMB-RCD-302.cisco.com>
In-Reply-To: <BANLkTi=OJYp6T7CL1CeWr9_hptmqiwK8+g@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RTGWG chairs
Thread-Index: Acww8CieZjaipv4DQF2jcDHd5OskjgCSwqbc
From: "Alex Zinin (azinin)" <azinin@cisco.com>
To: <akatlas@gmail.com>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>
X-OriginalArrivalTime: 25 Jun 2011 13:24:24.0500 (UTC) FILETIME=[33613F40:01CC333B]
X-Mailman-Approved-At: Tue, 28 Jun 2011 06:57:32 -0700
Cc: jgs@juniper.net, akatlas@juniper.net, iesg@ietf.org, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sat, 25 Jun 2011 13:33:45 -0000

Alia, John, Stewart, folks-

Thanks a lot for all the work we've done together. I's been great to be =
part of real collaborative innovation that truly changes the way that IP =
networks are being built today. Very satisfying for a technologist like =
myself!

As you may have noticed, business priorities have taken most of my time, =
and it was only fair for me to step down. I am Glad to see Alvaro =
stepping into the WG chair role. He is a routing expert with an =
extensive practical experience and has been part of the IETF community =
for a long time. I am confident he will take the group to the new =
heights.

Thanks again, everyone, and see you at one of the future IETF meetings.

--
Alex Zinin

----- Original Message -----
From: Alia Atlas [mailto:akatlas@gmail.com]
Sent: Wednesday, June 22, 2011 10:22 AM
To: Stewart Bryant (stbryant)
Cc: rtgwg@ietf.org <rtgwg@ietf.org>; iesg@ietf.org <iesg@ietf.org>; Alex =
Zinin (azinin); Alia Atlas <akatlas@juniper.net>; John G. Scudder =
<jgs@juniper.net>
Subject: Re: RTGWG chairs

I would also like to thank Alex & John for their work over the past
several years.
I look forward to working with Alvaro.

Alia

On Wed, Jun 22, 2011 at 10:30 AM, Stewart Bryant <stbryant@cisco.com> =
wrote:
>
> This message is to announce a change to the leadership
> of the Routing Area Working Group.
>
> Alex Zinin, a founder chair of the working group, is
> standing down due to pressure of other work.
>
> John Scudder, has volunteered to stand down as chair
> so that a we do not have two chairs from the same
> company. John of course continues as chair of
> the IDR working group.
>
> I thank them for their hard work over the years in RTGWG.
>
> I would like to welcome Alvaro Retana (alvaro.retana@hp.com)
> as incoming RTGWG Chair to join Alia Atlas (akatlas@juniper.net)
> who continues in the role.
>
> - Stewart
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
