Subject: Agenda topics for IETF-74
From: "John G. Scudder" <[email-masked]>
To: [email-masked]
Date: Tue, 3 Mar 2009 12:00:11 -0500
List-Id: <rtgwg.ietf.org>

Folks,

rtgwg will meet at IETF-74 on Monday March 23 from 1520 - 1720.  If  
you'd like an agenda slot, please send  email to the chairs.  Please  
also let us know how much time you think  you'll need.

Thanks,

--John, Alia and Alex

From [email-masked]  Thu Mar  5 05:00:01 2009
From: [email-masked]
To: [email-masked]
Subject: I-D Action:draft-ietf-rtgwg-lf-conv-frmwk-04.txt 
Date: Thu,  5 Mar 2009 05:00:01 -0800 (PST)
Cc: [email-masked]

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group Working Group of the IETF.

	Title           : A Framework for Loop-free Convergence
	Author(s)       : M. Shand, S. Bryant
	Filename        : draft-ietf-rtgwg-lf-conv-frmwk-04.txt
	Pages           : 22
	Date            : 2009-03-05

This draft describes mechanisms that may be used to prevent or to
suppress the formation of micro-loops when an IP or MPLS network
undergoes topology change due to failure, repair or management
action.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-lf-conv-frmwk-04.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.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-lf-conv-frmwk-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <[email-masked]>

--NextPart--

From [email-masked]  Mon Mar 16 13:10:58 2009
Date: Mon, 16 Mar 2009 13:11:38 -0700
Subject: Pls review draft-lebovitz-kmart-roadmap-01.txt
From: Gregory Lebovitz <[email-masked]>
To: [email-masked], [email-masked], [email-masked]
Cc: Ross Callon <[email-masked]>, Tim Polk <[email-masked]>, Pasi Eronen <[email-masked]>, Danny McPherson <[email-masked]>

--000325574d7ae491c50465420e7a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hey all,

The -01 draft that captures the goals, definition of work, and order of
priorities for securing routing protocol transports is here:
   http://www.ietf.org/internet-drafts/draft-lebovitz-kmart-roadmap-01.txt

This represents joint work of the IAB, RTG and SAAG areas, under the
guidance of the ADs of both.

This document will be presented in IETF74 at:
 - RTG WG
 - SAAG
 - SIDR (brief advertisement)
 - Others ? (pls let me know)

Pls respond with comments to me, and cc the [email-masked] mail list.

Gregory.

-- 
----
IETF related email from
Gregory M. Lebovitz
Juniper Networks

--000325574d7ae491c50465420e7a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hey all,</div>
<div>=A0</div>
<div>The -01 draft that captures the goals, definition of work, and order o=
f priorities for securing routing protocol transports is here:</div>
<div>=A0=A0 <a href=3D"http://www.ietf.org/internet-drafts/draft-lebovitz-k=
mart-roadmap-01.txt">http://www.ietf.org/internet-drafts/draft-lebovitz-kma=
rt-roadmap-01.txt</a> </div>
<div>=A0</div>
<div>This represents joint work of the IAB, RTG and SAAG areas, under the g=
uidance of the ADs of both.</div>
<div>=A0</div>
<div>This document will be presented in IETF74=A0at:</div>
<div>=A0- RTG WG</div>
<div>=A0- SAAG</div>
<div>=A0- SIDR (brief advertisement)</div>
<div>=A0- Others ? (pls let me know)</div>
<div>=A0</div>
<div>Pls respond with comments to me, and cc the <a href=3D"mailto:kmart@ie=
tf.org">[email-masked]</a> mail list.</div>
<div>=A0</div>
<div>Gregory.<br clear=3D"all"><br>-- <br>----<br>IETF related email from<b=
r>Gregory M. Lebovitz<br>Juniper Networks<br></div>

--000325574d7ae491c50465420e7a--

From [email-masked]  Mon Mar 23 16:25:51 2009
Date: Mon, 23 Mar 2009 16:26:56 -0700
From: Lou Berger <[email-masked]>
To: [email-masked]
Subject: comment on draft-so-yong-mpls-ctg-framework-requirement-01

Per Alex's request:

My point was that it would be useful to have a requirements document that:
1) identified the issues with today's solutions
2) identified operational requirements for an alternate solution

The document has a good start (or however Dave phrased id) of 1 in 
section 3.

The document has a start on 2,  but does so only in the context of a 
particular solution/approach, i.e., "Composite Transport Group 
Requirements".  For example the document states:
    Composite
    Transport Group (CTG) provides the local traffic engineering
    management/transport over multiple parallel links that solves this
    problem in MPLS networks.  ....
and
    Composite Transport Group (CTG) is the TE method to transport
    aggregated traffic over a composite link. ....

I think it would be really useful to identify the carrier requirements 
independent of the CTG solution.  For example the document could state:
- the solution must support multiple component links with different
   administrative costs
- the solution must support multiple routing instances per router
- the solution must support RSVP-TE LSPs
- the solution must support LDP LSPs
....

Once there is a clear understanding of requirements we can judge if the 
proposed solution is the one that the community wants to progress (or if 
there are alternatives.)

Hope this clarifies the point.

Lou