
From akatlas@gmail.com  Wed Nov  2 16:31:39 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 07BF811E8091 for <rtgwg@ietfa.amsl.com>; Wed,  2 Nov 2011 16:31:39 -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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVya4mqKalAh for <rtgwg@ietfa.amsl.com>; Wed,  2 Nov 2011 16:31:38 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7E3ED11E8102 for <rtgwg@ietf.org>; Wed,  2 Nov 2011 16:31:38 -0700 (PDT)
Received: by iaeo4 with SMTP id o4so830828iae.31 for <rtgwg@ietf.org>; Wed, 02 Nov 2011 16:31:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=gTu2bjVH3NBOat1Z7EewpBQOJ7QCge16/SDAl31PBwo=; b=xUfBeY85bMb57jW7wzMsnTcF8fwO45jYVG+6mqTSpnf6K6HiMcuV18EnZM0Zavo9e+ pPOXHBjF9aG6lJyXvIF4ercxe0+ivn71raG5cmLd/ZwBM9QNcvdMHsi0rL0MsEUHMK6p 5381NjPBRZgtGAINyq3F2JpTyFRqJBtiLEjV8=
MIME-Version: 1.0
Received: by 10.50.161.131 with SMTP id xs3mr934111igb.23.1320276698226; Wed, 02 Nov 2011 16:31:38 -0700 (PDT)
Received: by 10.50.203.10 with HTTP; Wed, 2 Nov 2011 16:31:38 -0700 (PDT)
Date: Wed, 2 Nov 2011 19:31:38 -0400
Message-ID: <CAG4d1rdWPGt2zKZDLakR0=5oSpNr5drhLDKyQt6U9SEJ1yT-SQ@mail.gmail.com>
Subject: RTGWG Agenda for IETF 82
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: Wed, 02 Nov 2011 23:31:39 -0000

Our current agenda is attached and uploaded at:

http://www.ietf.org/proceedings/82/agenda/rtgwg.htm

Topic	                                                          Draft=09
                                   Presenter	       Time Allotted

1) Draft Status & Charter Discussion=09
               	    Alia Atlas &         	15 mins

                                             Alvaro Retano
2) Composite Link Framework &	       draft-so-yong-rtgwg-cl-framework
&           Ning So                15 mins
    Requirements                               draft-ietf-rtgwg-cl-requirem=
ent

3) IP/LDP Fast-Reroute using =09
draft-atlas-rtgwg-mrt-frr-architecture-01      Alia Atlas &
30 mins
Maximally Redundant Trees  (MRTs)
                          Gabor Enyedi

4) MRT Algorithms=09
draft-enyedi-rtgwg-mrt-frr-algorithm-00        Alia Atlas
30 mins

                                             Gabor Enyedi
5) IP Fast-Reroute with Fast Notification	draft-csaszar-ipfrr-fn-02
               Andr=E1s Cs=E1sz=E1r	25 mins


Alia

From alvaro.retana@hp.com  Wed Nov  2 18:15:22 2011
Return-Path: <alvaro.retana@hp.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 6BD4E21F9CDA for <rtgwg@ietfa.amsl.com>; Wed,  2 Nov 2011 18:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cJfV9Ovf36r for <rtgwg@ietfa.amsl.com>; Wed,  2 Nov 2011 18:15:20 -0700 (PDT)
Received: from g4t0017.houston.hp.com (g4t0017.houston.hp.com [15.201.24.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7FFE921F9D05 for <rtgwg@ietf.org>; Wed,  2 Nov 2011 18:15:20 -0700 (PDT)
Received: from G4W3011G.americas.hpqcorp.net (g4w3011g.houston.hp.com [16.234.25.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g4t0017.houston.hp.com (Postfix) with ESMTPS id 051B5380F4 for <rtgwg@ietf.org>; Thu,  3 Nov 2011 01:15:20 +0000 (UTC)
Received: from G1W0394.americas.hpqcorp.net (16.236.31.4) by G4W3011G.americas.hpqcorp.net (16.234.25.125) with Microsoft SMTP Server (TLS) id 14.1.289.1; Thu, 3 Nov 2011 01:13:19 +0000
Received: from GVW1338EXA.americas.hpqcorp.net ([16.236.29.12]) by G1W0394.americas.hpqcorp.net ([16.236.31.4]) with mapi; Thu, 3 Nov 2011 01:13:18 +0000
From: "Retana, Alvaro" <alvaro.retana@hp.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Thu, 3 Nov 2011 01:13:16 +0000
Subject: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcyZxcP89g4D8M6cQf2SYlusNaQ5hQ==
Message-ID: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net>
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_24646CE17826CF4A8DF71F9856C7E656592F156FE5GVW1338EXAame_"
MIME-Version: 1.0
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: Thu, 03 Nov 2011 01:15:22 -0000

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

Hi!

We're in the process of updating the WG charter and the list of milestones.

The main objective of the update is to clarify that FRR-related topics are =
officially part of this WG - the main change is contained in the second par=
agraph.  Please take a look below and send your comments.

For reference, here's the current charter:  http://tools.ietf.org/wg/rtgwg/=
charters

Thanks!

Alvaro.




The Routing area receives occasional proposals for the development and
publication of RFCs dealing with routing topics, but for which the
required work does not yet rise to the level where a new working group is
justified, yet the topic does not fit with an existing working group,
and it is either not ready for a BOF or a single BOF would not
provide the time to ensure a mature proposal. The RTGWG will serve as
the forum for developing these types of proposals.

The RTGWG also focuses on enhancements to hop-by-hop distributed routing
related to fast-reroute and loop-free convergence.  A specific goal of
fast-reroute mechanisms is to provide up to complete coverage when the
potential failure would not partition the network.  All work in this
area should be specifically evaluated by the WG in terms of practicality
and applicability to deployed networks.

The RTGWG mailing list will be used to discuss the proposals as they
arise. The working group will meet if there are one or more active
proposals that require discussion.

The working group milestones will be updated as needed to reflect the
proposals currently being worked on and the target dates for their
completion. New milestones will be first reviewed by the IESG. The
working group will be on-going as long as the ADs believe it serves a
useful purpose.


Apr 2012 Submit Composite-Link Requirements to IESG for publication as
Informational
Apr 2012 Submit Ordered FIB architecture to IESG for publication as Informa=
tional
Nov 2012 Submit Composite-Link Framework to IESG for publication as Informa=
tional
Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to  IES=
G for publication as Proposed Standard
Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute Archite=
cture


--_000_24646CE17826CF4A8DF71F9856C7E656592F156FE5GVW1338EXAame_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 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;}
@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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi!<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We&#8217;r=
e in the process of updating the WG charter and the list of milestones.<o:p=
></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>T=
he main objective of the update is to clarify that FRR-related topics are o=
fficially part of this WG &#8211; the main change is contained in the secon=
d paragraph. &nbsp;Please take a look below and send your comments.<o:p></o=
:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>For r=
eference, here&#8217;s the current charter:&nbsp; <a href=3D"http://tools.i=
etf.org/wg/rtgwg/charters">http://tools.ietf.org/wg/rtgwg/charters</a><o:p>=
</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Th=
anks!<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMs=
oNormal>Alvaro.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:Consolas'>The Routing area receives o=
ccasional proposals for the development and <o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>publicat=
ion of RFCs dealing with routing topics, but for which the <o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Cons=
olas'>required work does not yet rise to the level where a new working grou=
p is <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10=
.0pt;font-family:Consolas'>justified, yet the topic does not fit with an ex=
isting working group, <o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:Consolas'>and it is either not ready for =
a BOF or a single BOF would not <o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:10.0pt;font-family:Consolas'>provide the time to e=
nsure a mature proposal. The RTGWG will serve as <o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>the =
forum for developing these types of proposals.<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>&nbsp;<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;f=
ont-family:Consolas'>The RTGWG also focuses on enhancements to hop-by-hop d=
istributed routing <o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:Consolas'>related to fast-reroute and loop=
-free convergence.&nbsp; A specific goal of <o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>fast-rer=
oute mechanisms is to provide up to complete coverage when the <o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:=
Consolas'>potential failure would not partition the network.&nbsp; All work=
 in this <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:10.0pt;font-family:Consolas'>area should be specifically evaluated by the=
 WG in terms of practicality <o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:10.0pt;font-family:Consolas'>and applicability to dep=
loyed networks.<span style=3D'color:black'><o:p></o:p></span></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>&nb=
sp;<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0=
pt;font-family:Consolas'>The RTGWG mailing list will be used to discuss the=
 proposals as they <o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:Consolas'>arise. The working group will me=
et if there are one or more active <o:p></o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:10.0pt;font-family:Consolas'>proposals that req=
uire discussion.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:Consolas'>&nbsp;<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>The work=
ing group milestones will be updated as needed to reflect the <o:p></o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:C=
onsolas'>proposals currently being worked on and the target dates for their=
 <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt=
;font-family:Consolas'>completion. New milestones will be first reviewed by=
 the IESG. The <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:10.0pt;font-family:Consolas'>working group will be on-going as long=
 as the ADs believe it serves a <o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:10.0pt;font-family:Consolas'>useful purpose.<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:Consolas'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:Consolas'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>Apr=
 2012 Submit Composite-Link Requirements to IESG for publication as <o:p></=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fa=
mily:Consolas'>Informational <o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:10.0pt;font-family:Consolas'>Apr 2012 Submit Ordered =
FIB architecture to IESG for publication as Informational<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consol=
as'>Nov 2012 Submit Composite-Link Framework to IESG for publication as Inf=
ormational <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:10.0pt;font-family:Consolas'>Apr 2013 Submit specification on Advanced =
IP Fast Reroute mechanism to&nbsp; IESG for publication as Proposed Standar=
d <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0p=
t;font-family:Consolas'>Apr 2012 Submit initial Internet Draft on Multicast=
 IP Fast Reroute Architecture<o:p></o:p></span></p><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p></div></body></html>=

--_000_24646CE17826CF4A8DF71F9856C7E656592F156FE5GVW1338EXAame_--

From Andras.Csaszar@ericsson.com  Thu Nov  3 03:55:41 2011
Return-Path: <Andras.Csaszar@ericsson.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 09C2311E80D3 for <rtgwg@ietfa.amsl.com>; Thu,  3 Nov 2011 03:55:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.94
X-Spam-Level: 
X-Spam-Status: No, score=-5.94 tagged_above=-999 required=5 tests=[AWL=0.358,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rfwFrs9c2OZG for <rtgwg@ietfa.amsl.com>; Thu,  3 Nov 2011 03:55:39 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 42E9411E80A6 for <rtgwg@ietf.org>; Thu,  3 Nov 2011 03:55:39 -0700 (PDT)
X-AuditID: c1b4fb39-b7cb2ae000001bd8-c6-4eb273295e42
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 4E.44.07128.A2372BE4; Thu,  3 Nov 2011 11:55:38 +0100 (CET)
Received: from ESESSCMS0363.eemea.ericsson.se ([169.254.1.47]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Thu, 3 Nov 2011 11:55:37 +0100
From: =?Windows-1252?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
To: "Retana, Alvaro" <alvaro.retana@hp.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Thu, 3 Nov 2011 11:55:36 +0100
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcyZxcP89g4D8M6cQf2SYlusNaQ5hQATj9bQ
Message-ID: <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: multipart/alternative; boundary="_000_8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28ESESSCMS0363e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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: Thu, 03 Nov 2011 10:55:41 -0000

--_000_8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28ESESSCMS0363e_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi!

I think the proposed charter text is OK.
Comments:

- I have the feeling that we should add LDP-MPLS explicitly. I know that im=
plicitly we mean IPFRR for IP and LDP, too. And I also see that we have the=
 "enhancements to hop-by-hop distributed routing related to fast-reroute" p=
ortion in the proposed charter, which includes LDP. But still maybe saying =
LDP-MPLS explicitly would be good for clarity.

- The same goes for multicast. I see the last milestone is for multicast, t=
hat's OK, but maybe we should add it explicitly to the charter text.

- Another thought regarding LDP, again: Do we have a position on whether an=
 LDP-only FRR solution (i.e. which would not work for plain IP) but provide=
s 100% coverage is of interest? Or do we want to have a solution that is ap=
plicable to both plain IP and LDP-MPLS?

Maybe we should add something like this to the charter text: "...A specific=
 goal of fast-reroute mechanisms is to provide up to complete coverage when=
 the potential failure would not partition the network. The RTGWG seeks FRR=
 solutions for both unicast and multicast on pure IP and LDP/mLDP-MPLS netw=
orks."

- With some folks we were discussing in the background that the WG might pr=
ofit from an informational doc which lists/overviews and compares objective=
ly all the proposed solutions. There is a pletora of proposals out there, s=
ome might have not even appeared at the IETF. Of course, we don't necessari=
ly need to state such a doc explicitly as a milestone, I don't know.

- If the multicast milestone is Apr 2012, then it should be earlier. Or if =
it was meant for Apr 2013, then the year needs to be corrected.

Andras


________________________________
From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of R=
etana, Alvaro
Sent: 2011. november 3. 2:13
To: rtgwg@ietf.org
Subject: Charter Update (Discussion)

Hi!

We=92re in the process of updating the WG charter and the list of milestone=
s.

The main objective of the update is to clarify that FRR-related topics are =
officially part of this WG =96 the main change is contained in the second p=
aragraph.  Please take a look below and send your comments.

For reference, here=92s the current charter:  http://tools.ietf.org/wg/rtgw=
g/charters

Thanks!

Alvaro.




The Routing area receives occasional proposals for the development and
publication of RFCs dealing with routing topics, but for which the
required work does not yet rise to the level where a new working group is
justified, yet the topic does not fit with an existing working group,
and it is either not ready for a BOF or a single BOF would not
provide the time to ensure a mature proposal. The RTGWG will serve as
the forum for developing these types of proposals.

The RTGWG also focuses on enhancements to hop-by-hop distributed routing
related to fast-reroute and loop-free convergence.  A specific goal of
fast-reroute mechanisms is to provide up to complete coverage when the
potential failure would not partition the network.  All work in this
area should be specifically evaluated by the WG in terms of practicality
and applicability to deployed networks.

The RTGWG mailing list will be used to discuss the proposals as they
arise. The working group will meet if there are one or more active
proposals that require discussion.

The working group milestones will be updated as needed to reflect the
proposals currently being worked on and the target dates for their
completion. New milestones will be first reviewed by the IESG. The
working group will be on-going as long as the ADs believe it serves a
useful purpose.


Apr 2012 Submit Composite-Link Requirements to IESG for publication as
Informational
Apr 2012 Submit Ordered FIB architecture to IESG for publication as Informa=
tional
Nov 2012 Submit Composite-Link Framework to IESG for publication as Informa=
tional
Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to  IES=
G for publication as Proposed Standard
Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute Archite=
cture


--_000_8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28ESESSCMS0363e_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =3D=
=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =3D=20
"urn:schemas-microsoft-com:office:odc" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =3D=20
"http://microsoft.com/officenet/conferencing" XMLNS:D =3D "DAV:" XMLNS:Repl=
 =3D=20
"http://schemas.microsoft.com/repl/" xmlns:mt =3D=20
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =3D=20
"http://www.passport.com/NameSpace.xsd" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sub =3D=20
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =3D=
=20
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =3D=20
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =3D=20
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =3D=20
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =3D=20
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =3D=20
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =3D=20
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mv=
er =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
=3D=20
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =3D=
=20
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
=3D=20
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =3D=
=20
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksServ=
ice"=20
XMLNS:Z =3D "urn:schemas-microsoft-com:" xmlns:st =3D "=01"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DWindows-125=
2">
<META content=3D"MSHTML 6.00.6002.18510" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Consolas;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
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 vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>Hi!</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>I think the proposed charter text is OK.</FONT></SPAN></DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>Comments:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>- I have the feeling that we should add LDP-MPLS explicitly=
. I=20
know that implicitly we mean IPFRR for IP and LDP, too. And I also see that=
=20
</FONT></SPAN><SPAN class=3D290233310-03112011><FONT face=3DArial color=3D#=
008000>we=20
have the "enhancements to hop-by-hop distributed routing related to=20
fast-reroute" portion in the proposed charter, which includes LDP. But stil=
l=20
maybe saying LDP-MPLS explicitly would be good for clarity.</FONT></SPAN></=
DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>- The same goes for multicast. I see the last milestone is =
for=20
multicast, that's OK, but maybe we should add it explicitly to the charter=
=20
text.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>- Another thought regarding LDP, again: Do we have a positi=
on on=20
whether an LDP-only FRR solution (i.e. which would not work for plain IP) b=
ut=20
provides 100% coverage&nbsp;is of interest? Or do we want to have a solutio=
n=20
that is applicable to both plain IP and LDP-MPLS?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>Maybe we should add something like this to the charter text=
: "...A=20
specific goal of fast-reroute mechanisms is to provide up to complete cover=
age=20
when the potential failure would not partition the network. <U>The RTGWG se=
eks=20
FRR solutions for both unicast and multicast on pure IP and LDP/mLDP-MPLS=20
networks.</U>"</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>- With some folks we were discussing in the background that=
 the WG=20
might profit from an informational&nbsp;doc which lists/overviews and compa=
res=20
objectively all the proposed solutions. There is a pletora of proposals out=
=20
there, some might have not even&nbsp;appeared at the IETF. Of course, we do=
n't=20
necessarily need to state such a doc explicitly as a milestone, I don't=20
know.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>- If the multicast milestone is Apr 2012, then it should be=
=20
earlier. Or if it was meant for Apr 2013, then the year needs to be=20
corrected.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000>Andras</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=3DA=
rial=20
color=3D#008000></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #008000 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> rtgwg-bounces@ietf.org=20
  [mailto:rtgwg-bounces@ietf.org] <B>On Behalf Of </B>Retana,=20
  Alvaro<BR><B>Sent:</B> 2011. november 3. 2:13<BR><B>To:</B>=20
  rtgwg@ietf.org<BR><B>Subject:</B> Charter Update=20
  (Discussion)<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DWordSection1>
  <P class=3DMsoNormal>Hi!<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>We=92re in the process of updating the WG charter an=
d the=20
  list of milestones.<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>The main objective of the update is to clarify that=
=20
  FRR-related topics are officially part of this WG =96 the main change is=
=20
  contained in the second paragraph. &nbsp;Please take a look below and sen=
d=20
  your comments.<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>For reference, here=92s the current charter:&nbsp; <=
A=20
  href=3D"http://tools.ietf.org/wg/rtgwg/charters">http://tools.ietf.org/wg=
/rtgwg/charters</A><o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>Thanks!<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal>Alvaro.<o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">The=20
  Routing area receives occasional proposals for the development and=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">publication of RFCs deal=
ing=20
  with routing topics, but for which the <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">required work does not y=
et rise=20
  to the level where a new working group is <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">justified, yet the topic=
 does=20
  not fit with an existing working group, <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">and it=20
  is either not ready for a BOF or a single BOF would not <o:p></o:p></SPAN=
></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">provide the time to ensu=
re a=20
  mature proposal. The RTGWG will serve as <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">the=20
  forum for developing these types of proposals.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPAN>=
</P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">The=20
  RTGWG also focuses on enhancements to hop-by-hop distributed routing=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">related to fast-reroute =
and=20
  loop-free convergence.&nbsp; A specific goal of <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">fast-reroute mechanisms =
is to=20
  provide up to complete coverage when the <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">potential failure would =
not=20
  partition the network.&nbsp; All work in this <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">area=20
  should be specifically evaluated by the WG in terms of practicality=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">and=20
  applicability to deployed networks.<SPAN=20
  style=3D"COLOR: black"><o:p></o:p></SPAN></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPAN>=
</P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">The=20
  RTGWG mailing list will be used to discuss the proposals as they=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">arise.=20
  The working group will meet if there are one or more active=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">proposals that require=20
  discussion.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPAN>=
</P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">The=20
  working group milestones will be updated as needed to reflect the=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">proposals currently bein=
g=20
  worked on and the target dates for their <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">completion. New mileston=
es will=20
  be first reviewed by the IESG. The <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">working group will be on=
-going=20
  as long as the ADs believe it serves a <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">useful=20
  purpose.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPAN>=
</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPAN>=
</P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">Apr=20
  2012 Submit Composite-Link Requirements to IESG for publication as=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">Informational=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">Apr=20
  2012 Submit Ordered FIB architecture to IESG for publication as=20
  Informational<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">Nov=20
  2012 Submit Composite-Link Framework to IESG for publication as Informati=
onal=20
  <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">Apr=20
  2013 Submit specification on Advanced IP Fast Reroute mechanism to&nbsp; =
IESG=20
  for publication as Proposed Standard <o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consola=
s">Apr=20
  2012 Submit initial Internet Draft on Multicast IP Fast Reroute=20
  Architecture<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

--_000_8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28ESESSCMS0363e_--

From Andras.Csaszar@ericsson.com  Thu Nov  3 07:56:48 2011
Return-Path: <Andras.Csaszar@ericsson.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 BDD9211E808E for <rtgwg@ietfa.amsl.com>; Thu,  3 Nov 2011 07:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.985
X-Spam-Level: 
X-Spam-Status: No, score=-5.985 tagged_above=-999 required=5 tests=[AWL=0.313,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R2-UEFaoCsLu for <rtgwg@ietfa.amsl.com>; Thu,  3 Nov 2011 07:56:47 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id D2B0E11E80CA for <rtgwg@ietf.org>; Thu,  3 Nov 2011 07:56:46 -0700 (PDT)
X-AuditID: c1b4fb39-b7cb2ae000001bd8-cf-4eb2abad952b
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 5E.36.07128.DABA2BE4; Thu,  3 Nov 2011 15:56:46 +0100 (CET)
Received: from ESESSCMS0363.eemea.ericsson.se ([169.254.1.47]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Thu, 3 Nov 2011 15:56:45 +0100
From: =?Windows-1252?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
To: "Retana, Alvaro" <alvaro.retana@hp.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Thu, 3 Nov 2011 15:56:43 +0100
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcyZxcP89g4D8M6cQf2SYlusNaQ5hQATj9bQAAiIGyA=
Message-ID: <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se>
In-Reply-To: <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: multipart/alternative; boundary="_000_8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3BESESSCMS0363e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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: Thu, 03 Nov 2011 14:56:48 -0000

--_000_8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3BESESSCMS0363e_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Some further comments:

We probably shoud define "failure" a bit more clear. Single link, single no=
de, SRLG (local or remote), multiple failures.

And also we probably should discuss this part a bit: "A specific goal of fa=
st-reroute mechanisms is to provide up to complete coverage".

In my view, the target solution, while being practical, should be able to p=
rovide

1. Complete coverage for all single link, single node and single SRLG (loca=
l and remote) failures and for a reasonable number of pre-configured multip=
le failure cases deemed important by the operator.


If we can't find such a practical solution then we can fall back to a solut=
ion, which provides
2. Complete coverage for all single link, single node and single SRLG (loca=
l and remote) failures.

If we can't find such a practical solution then we can fall back to a solut=
ion, which provides
3. Complete coverage for all single link, single node and single local SRLG=
 failures.

If we can't find such a practical solution then we can fall back to a solut=
ion, which provides
4. Complete coverage for all single link and single node failures.

Only  if we can't find such a practical solution, should we fall back to a =
solution, which provides
5. Coverage higher than LFA for many/most single link and single node failu=
res.

Andr=E1s


________________________________
From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of A=
ndr=E1s Cs=E1sz=E1r
Sent: 2011. november 3. 11:56
To: Retana, Alvaro; rtgwg@ietf.org
Subject: RE: Charter Update (Discussion)

Hi!

I think the proposed charter text is OK.
Comments:

- I have the feeling that we should add LDP-MPLS explicitly. I know that im=
plicitly we mean IPFRR for IP and LDP, too. And I also see that we have the=
 "enhancements to hop-by-hop distributed routing related to fast-reroute" p=
ortion in the proposed charter, which includes LDP. But still maybe saying =
LDP-MPLS explicitly would be good for clarity.

- The same goes for multicast. I see the last milestone is for multicast, t=
hat's OK, but maybe we should add it explicitly to the charter text.

- Another thought regarding LDP, again: Do we have a position on whether an=
 LDP-only FRR solution (i.e. which would not work for plain IP) but provide=
s 100% coverage is of interest? Or do we want to have a solution that is ap=
plicable to both plain IP and LDP-MPLS?

Maybe we should add something like this to the charter text: "...A specific=
 goal of fast-reroute mechanisms is to provide up to complete coverage when=
 the potential failure would not partition the network. The RTGWG seeks FRR=
 solutions for both unicast and multicast on pure IP and LDP/mLDP-MPLS netw=
orks."

- With some folks we were discussing in the background that the WG might pr=
ofit from an informational doc which lists/overviews and compares objective=
ly all the proposed solutions. There is a pletora of proposals out there, s=
ome might have not even appeared at the IETF. Of course, we don't necessari=
ly need to state such a doc explicitly as a milestone, I don't know.

- If the multicast milestone is Apr 2012, then it should be earlier. Or if =
it was meant for Apr 2013, then the year needs to be corrected.

Andras


________________________________
From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of R=
etana, Alvaro
Sent: 2011. november 3. 2:13
To: rtgwg@ietf.org
Subject: Charter Update (Discussion)

Hi!

We=92re in the process of updating the WG charter and the list of milestone=
s.

The main objective of the update is to clarify that FRR-related topics are =
officially part of this WG =96 the main change is contained in the second p=
aragraph.  Please take a look below and send your comments.

For reference, here=92s the current charter:  http://tools.ietf.org/wg/rtgw=
g/charters

Thanks!

Alvaro.




The Routing area receives occasional proposals for the development and
publication of RFCs dealing with routing topics, but for which the
required work does not yet rise to the level where a new working group is
justified, yet the topic does not fit with an existing working group,
and it is either not ready for a BOF or a single BOF would not
provide the time to ensure a mature proposal. The RTGWG will serve as
the forum for developing these types of proposals.

The RTGWG also focuses on enhancements to hop-by-hop distributed routing
related to fast-reroute and loop-free convergence.  A specific goal of
fast-reroute mechanisms is to provide up to complete coverage when the
potential failure would not partition the network.  All work in this
area should be specifically evaluated by the WG in terms of practicality
and applicability to deployed networks.

The RTGWG mailing list will be used to discuss the proposals as they
arise. The working group will meet if there are one or more active
proposals that require discussion.

The working group milestones will be updated as needed to reflect the
proposals currently being worked on and the target dates for their
completion. New milestones will be first reviewed by the IESG. The
working group will be on-going as long as the ADs believe it serves a
useful purpose.


Apr 2012 Submit Composite-Link Requirements to IESG for publication as
Informational
Apr 2012 Submit Ordered FIB architecture to IESG for publication as Informa=
tional
Nov 2012 Submit Composite-Link Framework to IESG for publication as Informa=
tional
Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to  IES=
G for publication as Proposed Standard
Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute Archite=
cture


--_000_8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3BESESSCMS0363e_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =3D=
=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =3D=20
"urn:schemas-microsoft-com:office:odc" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =3D=20
"http://microsoft.com/officenet/conferencing" XMLNS:D =3D "DAV:" XMLNS:Repl=
 =3D=20
"http://schemas.microsoft.com/repl/" xmlns:mt =3D=20
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =3D=20
"http://www.passport.com/NameSpace.xsd" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sub =3D=20
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =3D=
=20
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =3D=20
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =3D=20
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =3D=20
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =3D=20
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =3D=20
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =3D=20
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mv=
er =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
=3D=20
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =3D=
=20
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
=3D=20
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =3D=
=20
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksServ=
ice"=20
XMLNS:Z =3D "urn:schemas-microsoft-com:" xmlns:st =3D "=01"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DWindows-125=
2">
<META content=3D"MSHTML 6.00.6002.18510" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Consolas;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
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 vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>Some further comments:</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>We probably shoud define "failure" a bit more cl=
ear.=20
Single link, single node, SRLG (local or remote), multiple=20
failures.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>And also we probably should discuss this part a =
bit: "A=20
specific goal of fast-reroute mechanisms is to provide<U> up to </U>complet=
e=20
coverage".</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>In my view, the target solution<U>, while being=
=20
practical,</U> should be able to provide</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT><FONT face=3DArial color=3D#008000=
><SPAN=20
class=3D585403714-03112011></SPAN></FONT><FONT face=3DArial color=3D#008000=
><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>1. <U>Complete</U> coverage for all single link,=
 single=20
node and <U>single SRLG (local and remote)</U> failures and for <U>a reason=
able=20
number of pre-configured multiple failure cases</U> deemed important by the=
=20
operator.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>If we can't find such a practical solution then =
we can=20
fall back to a solution, which provides</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>2. <U>Complete</U> coverage for all single link,=
 single=20
node and <U>single SRLG (local and remote)</U>=20
failures.</SPAN></FONT></DIV></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT><FONT face=3DArial color=3D#008000=
><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>If we can't find such a practical solution then =
we can=20
fall back to a solution, which provides</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>3. <U>Complete</U> coverage for all single link,=
 single=20
node and <U>single local SRLG</U> failures.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011><SPAN class=3D585403714-03112011>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>If we can't find such a practical solution then =
we can=20
fall back to a solution, which provides</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>4. <U>Complete</U> coverage for all single link=
=20
and&nbsp;single node failures.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>Only&nbsp;<SPAN class=3D585403714-03112011><SPAN=
=20
class=3D585403714-03112011> i<FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>f we can't find such a practical solution, shoul=
d we=20
fall back to a solution, which provides</SPAN></FONT>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>5. <U>Coverage higher than LFA </U>for <U>many/m=
ost=20
</U>single link and&nbsp;single node failures.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011>Andr=E1s</SPAN></FONT></DIV></SPAN></FONT></DIV>=
</SPAN></SPAN></SPAN></FONT></DIV></SPAN></FONT></DIV></SPAN></SPAN></FONT>=
</DIV></SPAN></FONT></DIV></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#008000><SPAN=20
class=3D585403714-03112011></SPAN></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #008000 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> rtgwg-bounces@ietf.org=20
  [mailto:rtgwg-bounces@ietf.org] <B>On Behalf Of </B>Andr=E1s=20
  Cs=E1sz=E1r<BR><B>Sent:</B> 2011. november 3. 11:56<BR><B>To:</B> Retana,=
 Alvaro;=20
  rtgwg@ietf.org<BR><B>Subject:</B> RE: Charter Update=20
  (Discussion)<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>Hi!</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>I think the proposed charter text is OK.</FONT></SPAN></D=
IV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>Comments:</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>- I have the feeling that we should add LDP-MPLS explicit=
ly. I=20
  know that implicitly we mean IPFRR for IP and LDP, too. And I also see th=
at=20
  </FONT></SPAN><SPAN class=3D290233310-03112011><FONT face=3DArial color=
=3D#008000>we=20
  have the "enhancements to hop-by-hop distributed routing related to=20
  fast-reroute" portion in the proposed charter, which includes LDP. But st=
ill=20
  maybe saying LDP-MPLS explicitly would be good for=20
clarity.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>- The same goes for multicast. I see the last milestone i=
s for=20
  multicast, that's OK, but maybe we should add it explicitly to the charte=
r=20
  text.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>- Another thought regarding LDP, again: Do we have a posi=
tion on=20
  whether an LDP-only FRR solution (i.e. which would not work for plain IP)=
 but=20
  provides 100% coverage&nbsp;is of interest? Or do we want to have a solut=
ion=20
  that is applicable to both plain IP and LDP-MPLS?</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>Maybe we should add something like this to the charter te=
xt:=20
  "...A specific goal of fast-reroute mechanisms is to provide up to comple=
te=20
  coverage when the potential failure would not partition the network. <U>T=
he=20
  RTGWG seeks FRR solutions for both unicast and multicast on pure IP and=20
  LDP/mLDP-MPLS networks.</U>"</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>- With some folks we were discussing in the background th=
at the=20
  WG might profit from an informational&nbsp;doc which lists/overviews and=
=20
  compares objectively all the proposed solutions. There is a pletora of=20
  proposals out there, some might have not even&nbsp;appeared at the IETF. =
Of=20
  course, we don't necessarily need to state such a doc explicitly as a=20
  milestone, I don't know.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>- If the multicast milestone is Apr 2012, then it should =
be=20
  earlier. Or if it was meant for Apr 2013, then the year needs to be=20
  corrected.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000>Andras</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D290233310-03112011><FONT face=
=3DArial=20
  color=3D#008000></FONT></SPAN>&nbsp;</DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #008000 2px so=
lid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> rtgwg-bounces@ietf.org=20
    [mailto:rtgwg-bounces@ietf.org] <B>On Behalf Of </B>Retana,=20
    Alvaro<BR><B>Sent:</B> 2011. november 3. 2:13<BR><B>To:</B>=20
    rtgwg@ietf.org<BR><B>Subject:</B> Charter Update=20
    (Discussion)<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV class=3DWordSection1>
    <P class=3DMsoNormal>Hi!<o:p></o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal>We=92re in the process of updating the WG charter =
and the=20
    list of milestones.<o:p></o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal>The main objective of the update is to clarify tha=
t=20
    FRR-related topics are officially part of this WG =96 the main change i=
s=20
    contained in the second paragraph. &nbsp;Please take a look below and s=
end=20
    your comments.<o:p></o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal>For reference, here=92s the current charter:&nbsp;=
 <A=20
    href=3D"http://tools.ietf.org/wg/rtgwg/charters">http://tools.ietf.org/=
wg/rtgwg/charters</A><o:p></o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal>Thanks!<o:p></o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal>Alvaro.<o:p></o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">The=20
    Routing area receives occasional proposals for the development and=20
    <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">publication of RFCs de=
aling=20
    with routing topics, but for which the <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">required work does not=
 yet=20
    rise to the level where a new working group is <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">justified, yet the top=
ic does=20
    not fit with an existing working group, <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">and=20
    it is either not ready for a BOF or a single BOF would not=20
    <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">provide the time to en=
sure a=20
    mature proposal. The RTGWG will serve as <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">the=20
    forum for developing these types of proposals.<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPA=
N></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">The=20
    RTGWG also focuses on enhancements to hop-by-hop distributed routing=20
    <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">related to fast-rerout=
e and=20
    loop-free convergence.&nbsp; A specific goal of <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">fast-reroute mechanism=
s is to=20
    provide up to complete coverage when the <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">potential failure woul=
d not=20
    partition the network.&nbsp; All work in this <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">area=20
    should be specifically evaluated by the WG in terms of practicality=20
    <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">and=20
    applicability to deployed networks.<SPAN=20
    style=3D"COLOR: black"><o:p></o:p></SPAN></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPA=
N></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">The=20
    RTGWG mailing list will be used to discuss the proposals as they=20
    <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">arise. The working gro=
up will=20
    meet if there are one or more active <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">proposals that require=
=20
    discussion.<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPA=
N></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">The=20
    working group milestones will be updated as needed to reflect the=20
    <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">proposals currently be=
ing=20
    worked on and the target dates for their <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">completion. New milest=
ones=20
    will be first reviewed by the IESG. The <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">working group will be=
=20
    on-going as long as the ADs believe it serves a <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">useful=20
    purpose.<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPA=
N></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">&nbsp;<o:p></o:p></SPA=
N></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">Apr=20
    2012 Submit Composite-Link Requirements to IESG for publication as=20
    <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Consolas">Informational=20
    <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">Apr=20
    2012 Submit Ordered FIB architecture to IESG for publication as=20
    Informational<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">Nov=20
    2012 Submit Composite-Link Framework to IESG for publication as=20
    Informational <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">Apr=20
    2013 Submit specification on Advanced IP Fast Reroute mechanism to&nbsp=
;=20
    IESG for publication as Proposed Standard <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Conso=
las">Apr=20
    2012 Submit initial Internet Draft on Multicast IP Fast Reroute=20
    Architecture<o:p></o:p></SPAN></P>
    <P=20
class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BO=
DY></HTML>

--_000_8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3BESESSCMS0363e_--

From akatlas@gmail.com  Fri Nov  4 11:22:55 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 8097521F8B17 for <rtgwg@ietfa.amsl.com>; Fri,  4 Nov 2011 11:22:55 -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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2kVkyEgQQ4b for <rtgwg@ietfa.amsl.com>; Fri,  4 Nov 2011 11:22:55 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 091C621F8B0B for <rtgwg@ietf.org>; Fri,  4 Nov 2011 11:22:54 -0700 (PDT)
Received: by ggnv1 with SMTP id v1so3174206ggn.31 for <rtgwg@ietf.org>; Fri, 04 Nov 2011 11:22:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=8XwW3HwUEdVlSSSoK2+inGFJlbHwqZ+Yksxo9rdX8IY=; b=ElpZObOtaeanS/VvoSiQ6lO5zDagRJlJa0cIoM9LMWE1g7fMsoZljXnoTK0dnBp78n sbZPdht7AO8836frp5ucwpnVdsUXQHuJE2OClhDC4NGzIrbza8hBpmXJFhdb5F3bXSjW TDQ81Jlt8opYngg9BvcSxmxwpxiAd5VKxhCRM=
MIME-Version: 1.0
Received: by 10.50.207.99 with SMTP id lv3mr13793651igc.16.1320430974378; Fri, 04 Nov 2011 11:22:54 -0700 (PDT)
Received: by 10.50.203.10 with HTTP; Fri, 4 Nov 2011 11:22:54 -0700 (PDT)
Date: Fri, 4 Nov 2011 14:22:54 -0400
Message-ID: <CAG4d1retwUA2XQZo3h5zDGijSOfCwFf4zjTUdo92Q5aH+O6GUg@mail.gmail.com>
Subject: fast-reroute with maximally redundant trees
From: Alia Atlas <akatlas@gmail.com>
To: rtgwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
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, 04 Nov 2011 18:22:55 -0000

As you may have seen, we updated
draft-atlas-rtgwg-mrt-frr-architecture-01 and have also added
draft-enyedi-rtgwg-mrt-frr-algorithm-00, which describes the logic and
methods for the MRT algorithm.

At IETF 82, we expect to have a good amount of time for questions and
discussion about Fast-Reroute with MRT, as well as discussing the
changes and basics of the algorithm draft.

I would really appreciate any comments and questions about
fast-reroute with MRTs.  The ability to provide complete coverage when
a failure doesn't partition the network makes this technology very
interesting to me.

Thanks,
Alia  (WG chair hat off)

From russw@riw.us  Sat Nov  5 06:13:52 2011
Return-Path: <russw@riw.us>
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 5BCE221F8593 for <rtgwg@ietfa.amsl.com>; Sat,  5 Nov 2011 06:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level: 
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[AWL=0.197,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KIAvkqvlpPdK for <rtgwg@ietfa.amsl.com>; Sat,  5 Nov 2011 06:13:52 -0700 (PDT)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id 0506921F8497 for <rtgwg@ietf.org>; Sat,  5 Nov 2011 06:13:52 -0700 (PDT)
Received: from rtp-isp-nat1.cisco.com ([64.102.254.33]:52014 helo=[10.117.153.102]) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RMg4F-0007Zh-07 for rtgwg@ietf.org; Sat, 05 Nov 2011 09:13:51 -0400
Message-ID: <4EB53693.3040806@riw.us>
Date: Sat, 05 Nov 2011 09:13:55 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
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, 05 Nov 2011 13:13:52 -0000

> We’re in the process of updating the WG charter and the list of milestones.

These look fine to me...

:-)

Russ


From imc.shand@googlemail.com  Mon Nov  7 09:34:34 2011
Return-Path: <imc.shand@googlemail.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 94E6721F8B66 for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:34:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.299,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4N3rSqe++IU for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:34:33 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id C517521F8B65 for <rtgwg@ietf.org>; Mon,  7 Nov 2011 09:34:32 -0800 (PST)
Received: by wwf22 with SMTP id 22so5230042wwf.1 for <rtgwg@ietf.org>; Mon, 07 Nov 2011 09:34:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=OTYjQhONYRLzFKPRRRnvLV9H40BaQhgx6MPDOQNS2wk=; b=lTyyk4x8aORoM/1tEZXmrKqhe/fGSShXFGk1AP0DM+9/eetyLFsAwY//wSb+kcD/ea QGkeNH6wOKOZEHDKrOkkxcz5/2wSYXGdzFdjIGhgWxeFKVOyGjY9ES8B6T2wNV2A1p3b ylglWJq2g2C1U5tVpj7rrDi90dqL8l0aQGQBw=
Received: by 10.227.202.70 with SMTP id fd6mr29969477wbb.27.1320687271996; Mon, 07 Nov 2011 09:34:31 -0800 (PST)
Received: from [192.168.1.166] (188-220-40-104.zone11.bethere.co.uk. [188.220.40.104]) by mx.google.com with ESMTPS id en13sm28465205wbb.22.2011.11.07.09.34.25 (version=SSLv3 cipher=OTHER); Mon, 07 Nov 2011 09:34:26 -0800 (PST)
Message-ID: <4EB81698.4030700@googlemail.com>
Date: Mon, 07 Nov 2011 17:34:16 +0000
From: Mike Shand <imc.shand@googlemail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net>
Content-Type: multipart/alternative; boundary="------------080100000305010103060500"
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, 07 Nov 2011 17:34:34 -0000

This is a multi-part message in MIME format.
--------------080100000305010103060500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

That seems to describe what the WG does fairly well.

Fine with me.

     Mike

On 03/11/2011 01:13, Retana, Alvaro wrote:
>
> Hi!
>
> We're in the process of updating the WG charter and the list of 
> milestones.
>
> The main objective of the update is to clarify that FRR-related topics 
> are officially part of this WG -- the main change is contained in the 
> second paragraph.  Please take a look below and send your comments.
>
> For reference, here's the current charter: 
> http://tools.ietf.org/wg/rtgwg/charters
>
> Thanks!
>
> Alvaro.
>
> The Routing area receives occasional proposals for the development and
>
> publication of RFCs dealing with routing topics, but for which the
>
> required work does not yet rise to the level where a new working group is
>
> justified, yet the topic does not fit with an existing working group,
>
> and it is either not ready for a BOF or a single BOF would not
>
> provide the time to ensure a mature proposal. The RTGWG will serve as
>
> the forum for developing these types of proposals.
>
> The RTGWG also focuses on enhancements to hop-by-hop distributed routing
>
> related to fast-reroute and loop-free convergence.  A specific goal of
>
> fast-reroute mechanisms is to provide up to complete coverage when the
>
> potential failure would not partition the network.  All work in this
>
> area should be specifically evaluated by the WG in terms of practicality
>
> and applicability to deployed networks.
>
> The RTGWG mailing list will be used to discuss the proposals as they
>
> arise. The working group will meet if there are one or more active
>
> proposals that require discussion.
>
> The working group milestones will be updated as needed to reflect the
>
> proposals currently being worked on and the target dates for their
>
> completion. New milestones will be first reviewed by the IESG. The
>
> working group will be on-going as long as the ADs believe it serves a
>
> useful purpose.
>
> Apr 2012 Submit Composite-Link Requirements to IESG for publication as
>
> Informational
>
> Apr 2012 Submit Ordered FIB architecture to IESG for publication as 
> Informational
>
> Nov 2012 Submit Composite-Link Framework to IESG for publication as 
> Informational
>
> Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism 
> to  IESG for publication as Proposed Standard
>
> Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute 
> Architecture
>
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


--------------080100000305010103060500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    That seems to describe what the WG does fairly well.<br>
    <br>
    Fine with me.<br>
    <br>
    &nbsp;&nbsp;&nbsp; Mike<br>
    <br>
    On 03/11/2011 01:13, Retana, Alvaro wrote:
    <blockquote
cite="mid:24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 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;}
@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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">Hi!<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">We&#8217;re in the process of updating the WG
          charter and the list of milestones.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">The main objective of the update is to
          clarify that FRR-related topics are officially part of this WG
          &#8211; the main change is contained in the second paragraph.
          &nbsp;Please take a look below and send your comments.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">For reference, here&#8217;s the current charter:&nbsp;
          <a moz-do-not-send="true"
            href="http://tools.ietf.org/wg/rtgwg/charters">http://tools.ietf.org/wg/rtgwg/charters</a><o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Thanks!<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Alvaro.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">The Routing
            area receives occasional proposals for the development and <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">publication of
            RFCs dealing with routing topics, but for which the <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">required work
            does not yet rise to the level where a new working group is
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">justified, yet
            the topic does not fit with an existing working group, <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">and it is
            either not ready for a BOF or a single BOF would not <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">provide the
            time to ensure a mature proposal. The RTGWG will serve as <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">the forum for
            developing these types of proposals.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">&nbsp;<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">The RTGWG also
            focuses on enhancements to hop-by-hop distributed routing <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">related to
            fast-reroute and loop-free convergence.&nbsp; A specific goal of
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">fast-reroute
            mechanisms is to provide up to complete coverage when the <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">potential
            failure would not partition the network.&nbsp; All work in this <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">area should be
            specifically evaluated by the WG in terms of practicality <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">and
            applicability to deployed networks.<span style="color:black"><o:p></o:p></span></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">&nbsp;<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">The RTGWG
            mailing list will be used to discuss the proposals as they <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">arise. The
            working group will meet if there are one or more active <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">proposals that
            require discussion.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">&nbsp;<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">The working
            group milestones will be updated as needed to reflect the <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">proposals
            currently being worked on and the target dates for their <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">completion.
            New milestones will be first reviewed by the IESG. The <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">working group
            will be on-going as long as the ADs believe it serves a <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">useful
            purpose.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">&nbsp;<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">&nbsp;<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">Apr 2012
            Submit Composite-Link Requirements to IESG for publication
            as <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">Informational
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">Apr 2012
            Submit Ordered FIB architecture to IESG for publication as
            Informational<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">Nov 2012
            Submit Composite-Link Framework to IESG for publication as
            Informational <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">Apr 2013
            Submit specification on Advanced IP Fast Reroute mechanism
            to&nbsp; IESG for publication as Proposed Standard <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:Consolas">Apr 2012
            Submit initial Internet Draft on Multicast IP Fast Reroute
            Architecture<o:p></o:p></span></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
rtgwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rtgwg@ietf.org">rtgwg@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/rtgwg">https://www.ietf.org/mailman/listinfo/rtgwg</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080100000305010103060500--

From ning.so@verizon.com  Mon Nov  7 09:38:02 2011
Return-Path: <ning.so@verizon.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 5F5DA21F8C0D for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.864
X-Spam-Level: 
X-Spam-Status: No, score=-2.864 tagged_above=-999 required=5 tests=[AWL=0.734,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pOfMe4DJ6hCa for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:38:00 -0800 (PST)
Received: from fldsmtpe02.verizon.com (fldsmtpe02.verizon.com [140.108.26.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4831121F8B38 for <rtgwg@ietf.org>; Mon,  7 Nov 2011 09:38:00 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by fldsmtpe02.verizon.com with ESMTP; 07 Nov 2011 17:37:59 +0000
From: "So, Ning" <ning.so@verizon.com>
X-IronPort-AV: E=Sophos;i="4.69,471,1315180800";  d="scan'208,217";a="175209732"
Received: from fhdp1lumxc7hb01.verizon.com (HELO FHDP1LUMXC7HB01.us.one.verizon.com) ([166.68.59.188]) by fldsmtpi03.verizon.com with ESMTP; 07 Nov 2011 17:37:59 +0000
Received: from FHDP1LUMXC7V41.us.one.verizon.com ([169.254.1.133]) by FHDP1LUMXC7HB01.us.one.verizon.com ([166.68.59.188]) with mapi; Mon, 7 Nov 2011 12:37:59 -0500
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Mon, 7 Nov 2011 12:37:57 -0500
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: Acydc4f14GinKCIfTgGN7ApK5j8NPwAAGC6Q
Message-ID: <6665BC1FEA04AB47B1F75FA641C43BC08F9B4E29@FHDP1LUMXC7V41.us.one.verizon.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <4EB81698.4030700@googlemail.com>
In-Reply-To: <4EB81698.4030700@googlemail.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_6665BC1FEA04AB47B1F75FA641C43BC08F9B4E29FHDP1LUMXC7V41u_"
MIME-Version: 1.0
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, 07 Nov 2011 17:38:02 -0000

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

Alvaro,

This looks fine to me.


Best regards,

Ning So
Verizon Corporate Technology
(office) 972-729-7905
(Cell) 972-955-0914




On 03/11/2011 01:13, Retana, Alvaro wrote:
Hi!

We're in the process of updating the WG charter and the list of milestones.

The main objective of the update is to clarify that FRR-related topics are =
officially part of this WG - the main change is contained in the second par=
agraph.  Please take a look below and send your comments.

For reference, here's the current charter:  http://tools.ietf.org/wg/rtgwg/=
charters

Thanks!

Alvaro.




The Routing area receives occasional proposals for the development and
publication of RFCs dealing with routing topics, but for which the
required work does not yet rise to the level where a new working group is
justified, yet the topic does not fit with an existing working group,
and it is either not ready for a BOF or a single BOF would not
provide the time to ensure a mature proposal. The RTGWG will serve as
the forum for developing these types of proposals.

The RTGWG also focuses on enhancements to hop-by-hop distributed routing
related to fast-reroute and loop-free convergence.  A specific goal of
fast-reroute mechanisms is to provide up to complete coverage when the
potential failure would not partition the network.  All work in this
area should be specifically evaluated by the WG in terms of practicality
and applicability to deployed networks.

The RTGWG mailing list will be used to discuss the proposals as they
arise. The working group will meet if there are one or more active
proposals that require discussion.

The working group milestones will be updated as needed to reflect the
proposals currently being worked on and the target dates for their
completion. New milestones will be first reviewed by the IESG. The
working group will be on-going as long as the ADs believe it serves a
useful purpose.


Apr 2012 Submit Composite-Link Requirements to IESG for publication as
Informational
Apr 2012 Submit Ordered FIB architecture to IESG for publication as Informa=
tional
Nov 2012 Submit Composite-Link Framework to IESG for publication as Informa=
tional
Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to  IES=
G for publication as Proposed Standard
Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute Archite=
cture





_______________________________________________

rtgwg mailing list

rtgwg@ietf.org<mailto:rtgwg@ietf.org>

https://www.ietf.org/mailman/listinfo/rtgwg


--_000_6665BC1FEA04AB47B1F75FA641C43BC08F9B4E29FHDP1LUMXC7V41u_
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-micr=
osoft-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"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 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";
	color:black;}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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 bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'color:#1F497D'>Alvaro,<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DM=
soNormal><span style=3D'color:#1F497D'>This looks fine to me.&nbsp; <o:p></=
o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbs=
p;</o:p></span></p><div><p class=3DMsoNormal><span style=3D'color:#1F497D'>=
&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
0.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Best regards,</span><=
span style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'color:#1F497D'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F=
497D'>Ning So</span><span style=3D'color:#1F497D'><o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans=
-serif";color:#1F497D'>Verizon Corporate Technology<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","san=
s-serif";color:#1F497D'>(office) 972-729-7905</span><span style=3D'color:#1=
F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>(Cell) 972-955-0914<=
/span><span style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNor=
mal><span style=3D'color:#1F497D'>&nbsp;</span><span style=3D'color:#1F497D=
'><o:p></o:p></span></p></div><p class=3DMsoNormal><span style=3D'color:#1F=
497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><br><br>On 03/11/201=
1 01:13, Retana, Alvaro wrote: <o:p></o:p></p><p class=3DMsoNormal>Hi!<o:p>=
</o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>We=
&#8217;re in the process of updating the WG charter and the list of milesto=
nes.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMso=
Normal>The main objective of the update is to clarify that FRR-related topi=
cs are officially part of this WG &#8211; the main change is contained in t=
he second paragraph. &nbsp;Please take a look below and send your comments.=
<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNorm=
al>For reference, here&#8217;s the current charter:&nbsp; <a href=3D"http:/=
/tools.ietf.org/wg/rtgwg/charters">http://tools.ietf.org/wg/rtgwg/charters<=
/a><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoN=
ormal>Thanks!<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p cl=
ass=3DMsoNormal>Alvaro.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p=
></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<=
o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNorma=
l><span style=3D'font-size:10.0pt;font-family:Consolas'>The Routing area re=
ceives occasional proposals for the development and </span><o:p></o:p></p><=
p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>p=
ublication of RFCs dealing with routing topics, but for which the </span><o=
:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fami=
ly:Consolas'>required work does not yet rise to the level where a new worki=
ng group is </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-=
size:10.0pt;font-family:Consolas'>justified, yet the topic does not fit wit=
h an existing working group, </span><o:p></o:p></p><p class=3DMsoNormal><sp=
an style=3D'font-size:10.0pt;font-family:Consolas'>and it is either not rea=
dy for a BOF or a single BOF would not </span><o:p></o:p></p><p class=3DMso=
Normal><span style=3D'font-size:10.0pt;font-family:Consolas'>provide the ti=
me to ensure a mature proposal. The RTGWG will serve as </span><o:p></o:p><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consola=
s'>the forum for developing these types of proposals.</span><o:p></o:p></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>=
&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:1=
0.0pt;font-family:Consolas'>The RTGWG also focuses on enhancements to hop-b=
y-hop distributed routing </span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:Consolas'>related to fast-reroute and=
 loop-free convergence.&nbsp; A specific goal of </span><o:p></o:p></p><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>fast=
-reroute mechanisms is to provide up to complete coverage when the </span><=
o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fam=
ily:Consolas'>potential failure would not partition the network.&nbsp; All =
work in this </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:Consolas'>area should be specifically evaluated by=
 the WG in terms of practicality </span><o:p></o:p></p><p class=3DMsoNormal=
><span style=3D'font-size:10.0pt;font-family:Consolas'>and applicability to=
 deployed networks.</span><o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:Consolas'>&nbsp;</span><o:p></o:p></p><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>The =
RTGWG mailing list will be used to discuss the proposals as they </span><o:=
p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-famil=
y:Consolas'>arise. The working group will meet if there are one or more act=
ive </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:Consolas'>proposals that require discussion.</span><o:p></o=
:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Con=
solas'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:Consolas'>The working group milestones will be upd=
ated as needed to reflect the </span><o:p></o:p></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:Consolas'>proposals currently bei=
ng worked on and the target dates for their </span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>completi=
on. New milestones will be first reviewed by the IESG. The </span><o:p></o:=
p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Cons=
olas'>working group will be on-going as long as the ADs believe it serves a=
 </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt=
;font-family:Consolas'>useful purpose.</span><o:p></o:p></p><p class=3DMsoN=
ormal><span style=3D'font-size:10.0pt;font-family:Consolas'>&nbsp;</span><o=
:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fami=
ly:Consolas'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:Consolas'>Apr 2012 Submit Composite-Link R=
equirements to IESG for publication as </span><o:p></o:p></p><p class=3DMso=
Normal><span style=3D'font-size:10.0pt;font-family:Consolas'>Informational =
</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;=
font-family:Consolas'>Apr 2012 Submit Ordered FIB architecture to IESG for =
publication as Informational</span><o:p></o:p></p><p class=3DMsoNormal><spa=
n style=3D'font-size:10.0pt;font-family:Consolas'>Nov 2012 Submit Composite=
-Link Framework to IESG for publication as Informational </span><o:p></o:p>=
</p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consol=
as'>Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to&=
nbsp; IESG for publication as Proposed Standard </span><o:p></o:p></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>Apr 2=
012 Submit initial Internet Draft on Multicast IP Fast Reroute Architecture=
</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3D=
MsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New Roman","se=
rif"'><br><br><br><o:p></o:p></span></p><pre>______________________________=
_________________<o:p></o:p></pre><pre>rtgwg mailing list<o:p></o:p></pre><=
pre><a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><o:p></o:p></pre><p=
re><a href=3D"https://www.ietf.org/mailman/listinfo/rtgwg">https://www.ietf=
.org/mailman/listinfo/rtgwg</a><o:p></o:p></pre><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p>&nbsp=
;</o:p></span></p></div></body></html>=

--_000_6665BC1FEA04AB47B1F75FA641C43BC08F9B4E29FHDP1LUMXC7V41u_--

From jgs@bgp.nu  Mon Nov  7 09:40:21 2011
Return-Path: <jgs@bgp.nu>
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 0BE5E21F8B38 for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:40:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.043
X-Spam-Level: 
X-Spam-Status: No, score=-102.043 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWq4S+3WnNxg for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:40:20 -0800 (PST)
Received: from bgp.nu (bgp.nu [147.28.0.53]) by ietfa.amsl.com (Postfix) with ESMTP id 55CF221F8C0F for <rtgwg@ietf.org>; Mon,  7 Nov 2011 09:40:20 -0800 (PST)
Received: from sa-nc-apg-175.static.jnpr.net (natint3.juniper.net [66.129.224.36]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by bgp.nu (Postfix) with ESMTP id 7844666CF2F; Mon,  7 Nov 2011 12:40:15 -0500 (EST)
Subject: Re: Charter Update (Discussion)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: "John G. Scudder" <jgs@bgp.nu>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net>
Date: Mon, 7 Nov 2011 09:40:18 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A14250E2-7FC1-45D9-9410-517112206DE6@bgp.nu>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net>
To: "Retana, Alvaro" <alvaro.retana@hp.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "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, 07 Nov 2011 17:40:21 -0000

This looks good, possibly with the consideration of Andras' first set of =
comments.

--John

On Nov 2, 2011, at 6:13 PM, Retana, Alvaro wrote:

> Hi!
> =20
> We=92re in the process of updating the WG charter and the list of =
milestones.
> =20
> The main objective of the update is to clarify that FRR-related topics =
are officially part of this WG =96 the main change is contained in the =
second paragraph.  Please take a look below and send your comments.
> =20
> For reference, here=92s the current charter:  =
http://tools.ietf.org/wg/rtgwg/charters
> =20
> Thanks!
> =20
> Alvaro.
> =20
> =20
> =20
> =20
> The Routing area receives occasional proposals for the development and
> publication of RFCs dealing with routing topics, but for which the
> required work does not yet rise to the level where a new working group =
is
> justified, yet the topic does not fit with an existing working group,
> and it is either not ready for a BOF or a single BOF would not
> provide the time to ensure a mature proposal. The RTGWG will serve as
> the forum for developing these types of proposals.
> =20
> The RTGWG also focuses on enhancements to hop-by-hop distributed =
routing
> related to fast-reroute and loop-free convergence.  A specific goal of
> fast-reroute mechanisms is to provide up to complete coverage when the
> potential failure would not partition the network.  All work in this
> area should be specifically evaluated by the WG in terms of =
practicality
> and applicability to deployed networks.
> =20
> The RTGWG mailing list will be used to discuss the proposals as they
> arise. The working group will meet if there are one or more active
> proposals that require discussion.
> =20
> The working group milestones will be updated as needed to reflect the
> proposals currently being worked on and the target dates for their
> completion. New milestones will be first reviewed by the IESG. The
> working group will be on-going as long as the ADs believe it serves a
> useful purpose.
> =20
> =20
> Apr 2012 Submit Composite-Link Requirements to IESG for publication as
> Informational
> Apr 2012 Submit Ordered FIB architecture to IESG for publication as =
Informational
> Nov 2012 Submit Composite-Link Framework to IESG for publication as =
Informational
> Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to =
 IESG for publication as Proposed Standard
> Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute =
Architecture
> =20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From jgs@bgp.nu  Mon Nov  7 09:41:25 2011
Return-Path: <jgs@bgp.nu>
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 476F521F86A0 for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:41:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.893
X-Spam-Level: 
X-Spam-Status: No, score=-101.893 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id enKc4Isltdnx for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:41:24 -0800 (PST)
Received: from bgp.nu (bgp.nu [147.28.0.53]) by ietfa.amsl.com (Postfix) with ESMTP id 615C121F8573 for <rtgwg@ietf.org>; Mon,  7 Nov 2011 09:41:24 -0800 (PST)
Received: from sa-nc-apg-175.static.jnpr.net (natint3.juniper.net [66.129.224.36]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by bgp.nu (Postfix) with ESMTP id 9BE0066CF2F; Mon,  7 Nov 2011 12:41:12 -0500 (EST)
Subject: Re: Charter Update (Discussion)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: "John G. Scudder" <jgs@bgp.nu>
In-Reply-To: <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se>
Date: Mon, 7 Nov 2011 09:41:16 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se>
To: =?iso-8859-1?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "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, 07 Nov 2011 17:41:25 -0000

Some of this seems too detailed for a charter, and like it might go =
better in a requirements document.  (Did we do one of those, years ago?  =
It might be worth updating even so.)

--John

On Nov 3, 2011, at 7:56 AM, Andr=E1s Cs=E1sz=E1r wrote:

> Some further comments:
> =20
> We probably shoud define "failure" a bit more clear. Single link, =
single node, SRLG (local or remote), multiple failures.
> =20
> And also we probably should discuss this part a bit: "A specific goal =
of fast-reroute mechanisms is to provide up tocomplete coverage".
> =20
> In my view, the target solution, while being practical, should be able =
to provide
> =20
> 1. Complete coverage for all single link, single node and single SRLG =
(local and remote) failures and for a reasonable number of =
pre-configured multiple failure cases deemed important by the operator.
> =20
> =20
> If we can't find such a practical solution then we can fall back to a =
solution, which provides
> 2. Complete coverage for all single link, single node and single SRLG =
(local and remote) failures.
> =20
> If we can't find such a practical solution then we can fall back to a =
solution, which provides
> 3. Complete coverage for all single link, single node and single local =
SRLG failures.
> =20
> If we can't find such a practical solution then we can fall back to a =
solution, which provides
> 4. Complete coverage for all single link and single node failures.
> =20
> Only  if we can't find such a practical solution, should we fall back =
to a solution, which provides
> 5. Coverage higher than LFA for many/most single link and single node =
failures.
> =20
> Andr=E1s
> =20
>=20
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf =
Of Andr=E1s Cs=E1sz=E1r
> Sent: 2011. november 3. 11:56
> To: Retana, Alvaro; rtgwg@ietf.org
> Subject: RE: Charter Update (Discussion)
>=20
> Hi!
> =20
> I think the proposed charter text is OK.
> Comments:
> =20
> - I have the feeling that we should add LDP-MPLS explicitly. I know =
that implicitly we mean IPFRR for IP and LDP, too. And I also see that =
we have the "enhancements to hop-by-hop distributed routing related to =
fast-reroute" portion in the proposed charter, which includes LDP. But =
still maybe saying LDP-MPLS explicitly would be good for clarity.
> =20
> - The same goes for multicast. I see the last milestone is for =
multicast, that's OK, but maybe we should add it explicitly to the =
charter text.
> =20
> - Another thought regarding LDP, again: Do we have a position on =
whether an LDP-only FRR solution (i.e. which would not work for plain =
IP) but provides 100% coverage is of interest? Or do we want to have a =
solution that is applicable to both plain IP and LDP-MPLS?
> =20
> Maybe we should add something like this to the charter text: "...A =
specific goal of fast-reroute mechanisms is to provide up to complete =
coverage when the potential failure would not partition the network. The =
RTGWG seeks FRR solutions for both unicast and multicast on pure IP and =
LDP/mLDP-MPLS networks."
> =20
> - With some folks we were discussing in the background that the WG =
might profit from an informational doc which lists/overviews and =
compares objectively all the proposed solutions. There is a pletora of =
proposals out there, some might have not even appeared at the IETF. Of =
course, we don't necessarily need to state such a doc explicitly as a =
milestone, I don't know.
> =20
> - If the multicast milestone is Apr 2012, then it should be earlier. =
Or if it was meant for Apr 2013, then the year needs to be corrected.
> =20
> Andras
> =20
>=20
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf =
Of Retana, Alvaro
> Sent: 2011. november 3. 2:13
> To: rtgwg@ietf.org
> Subject: Charter Update (Discussion)
>=20
> Hi!
> =20
> We=92re in the process of updating the WG charter and the list of =
milestones.
> =20
> The main objective of the update is to clarify that FRR-related topics =
are officially part of this WG =96 the main change is contained in the =
second paragraph.  Please take a look below and send your comments.
> =20
> For reference, here=92s the current charter:  =
http://tools.ietf.org/wg/rtgwg/charters
> =20
> Thanks!
> =20
> Alvaro.
> =20
> =20
> =20
> =20
> The Routing area receives occasional proposals for the development and
> publication of RFCs dealing with routing topics, but for which the
> required work does not yet rise to the level where a new working group =
is
> justified, yet the topic does not fit with an existing working group,
> and it is either not ready for a BOF or a single BOF would not
> provide the time to ensure a mature proposal. The RTGWG will serve as
> the forum for developing these types of proposals.
> =20
> The RTGWG also focuses on enhancements to hop-by-hop distributed =
routing
> related to fast-reroute and loop-free convergence.  A specific goal of
> fast-reroute mechanisms is to provide up to complete coverage when the
> potential failure would not partition the network.  All work in this
> area should be specifically evaluated by the WG in terms of =
practicality
> and applicability to deployed networks.
> =20
> The RTGWG mailing list will be used to discuss the proposals as they
> arise. The working group will meet if there are one or more active
> proposals that require discussion.
> =20
> The working group milestones will be updated as needed to reflect the
> proposals currently being worked on and the target dates for their
> completion. New milestones will be first reviewed by the IESG. The
> working group will be on-going as long as the ADs believe it serves a
> useful purpose.
> =20
> =20
> Apr 2012 Submit Composite-Link Requirements to IESG for publication as
> Informational
> Apr 2012 Submit Ordered FIB architecture to IESG for publication as =
Informational
> Nov 2012 Submit Composite-Link Framework to IESG for publication as =
Informational
> Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to =
 IESG for publication as Proposed Standard
> Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute =
Architecture
> =20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From jeff.tantsura@ericsson.com  Mon Nov  7 09:42:40 2011
Return-Path: <jeff.tantsura@ericsson.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 B604021F8AC3 for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:42:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5H447fOBezPc for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:42:38 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id BE70E21F8AB9 for <rtgwg@ietf.org>; Mon,  7 Nov 2011 09:42:38 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pA7HfKLY026929 for <rtgwg@ietf.org>; Mon, 7 Nov 2011 11:42:38 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.52]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Mon, 7 Nov 2011 12:42:33 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Mon, 7 Nov 2011 12:42:32 -0500
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: Acydc4m6O4SAOy1hTme9M2crKQXzIQAAObfg
Message-ID: <0ED867EB33AB2B45AAB470D5A64CDBF618198384A7@EUSAACMS0701.eamcs.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <4EB81698.4030700@googlemail.com>
In-Reply-To: <4EB81698.4030700@googlemail.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_0ED867EB33AB2B45AAB470D5A64CDBF618198384A7EUSAACMS0701e_"
MIME-Version: 1.0
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, 07 Nov 2011 17:42:40 -0000

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

Hi,

With Andras's comments incorporated looks good to me.

Regards,
Jeff

From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of M=
ike Shand
Sent: Monday, November 07, 2011 9:34 AM
To: rtgwg@ietf.org
Subject: Re: Charter Update (Discussion)

That seems to describe what the WG does fairly well.

Fine with me.

    Mike

On 03/11/2011 01:13, Retana, Alvaro wrote:
Hi!

We're in the process of updating the WG charter and the list of milestones.

The main objective of the update is to clarify that FRR-related topics are =
officially part of this WG - the main change is contained in the second par=
agraph.  Please take a look below and send your comments.

For reference, here's the current charter:  http://tools.ietf.org/wg/rtgwg/=
charters

Thanks!

Alvaro.




The Routing area receives occasional proposals for the development and
publication of RFCs dealing with routing topics, but for which the
required work does not yet rise to the level where a new working group is
justified, yet the topic does not fit with an existing working group,
and it is either not ready for a BOF or a single BOF would not
provide the time to ensure a mature proposal. The RTGWG will serve as
the forum for developing these types of proposals.

The RTGWG also focuses on enhancements to hop-by-hop distributed routing
related to fast-reroute and loop-free convergence.  A specific goal of
fast-reroute mechanisms is to provide up to complete coverage when the
potential failure would not partition the network.  All work in this
area should be specifically evaluated by the WG in terms of practicality
and applicability to deployed networks.

The RTGWG mailing list will be used to discuss the proposals as they
arise. The working group will meet if there are one or more active
proposals that require discussion.

The working group milestones will be updated as needed to reflect the
proposals currently being worked on and the target dates for their
completion. New milestones will be first reviewed by the IESG. The
working group will be on-going as long as the ADs believe it serves a
useful purpose.


Apr 2012 Submit Composite-Link Requirements to IESG for publication as
Informational
Apr 2012 Submit Ordered FIB architecture to IESG for publication as Informa=
tional
Nov 2012 Submit Composite-Link Framework to IESG for publication as Informa=
tional
Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to  IES=
G for publication as Proposed Standard
Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute Archite=
cture





_______________________________________________

rtgwg mailing list

rtgwg@ietf.org<mailto:rtgwg@ietf.org>

https://www.ietf.org/mailman/listinfo/rtgwg


--_000_0ED867EB33AB2B45AAB470D5A64CDBF618198384A7EUSAACMS0701e_
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-micr=
osoft-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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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 bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'color:#1F497D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'color:#1F497D'>With Andras&#8217;s comments incorporate=
d looks good to me.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;color:#1F497D'>Regards,<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;color:#1F497D'>Jeff<o:=
p></o:p></span></p></div><p class=3DMsoNormal><span style=3D'color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border-top:soli=
d #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'=
>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans=
-serif";color:windowtext'> rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@iet=
f.org] <b>On Behalf Of </b>Mike Shand<br><b>Sent:</b> Monday, November 07, =
2011 9:34 AM<br><b>To:</b> rtgwg@ietf.org<br><b>Subject:</b> Re: Charter Up=
date (Discussion)<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p><p class=3DMsoNormal>That seems to describe what the WG d=
oes fairly well.<br><br>Fine with me.<br><br>&nbsp;&nbsp;&nbsp; Mike<br><br=
>On 03/11/2011 01:13, Retana, Alvaro wrote: <o:p></o:p></p><p class=3DMsoNo=
rmal>Hi!<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=
=3DMsoNormal>We&#8217;re in the process of updating the WG charter and the =
list of milestones.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p=
><p class=3DMsoNormal>The main objective of the update is to clarify that F=
RR-related topics are officially part of this WG &#8211; the main change is=
 contained in the second paragraph. &nbsp;Please take a look below and send=
 your comments.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal>For reference, here&#8217;s the current charter:&nbsp; <a=
 href=3D"http://tools.ietf.org/wg/rtgwg/charters">http://tools.ietf.org/wg/=
rtgwg/charters</a><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p>=
<p class=3DMsoNormal>Thanks!<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p>=
</o:p></p><p class=3DMsoNormal>Alvaro.<o:p></o:p></p><p class=3DMsoNormal>&=
nbsp;<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMs=
oNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>The =
Routing area receives occasional proposals for the development and </span><=
o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fam=
ily:Consolas'>publication of RFCs dealing with routing topics, but for whic=
h the </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:1=
0.0pt;font-family:Consolas'>required work does not yet rise to the level wh=
ere a new working group is </span><o:p></o:p></p><p class=3DMsoNormal><span=
 style=3D'font-size:10.0pt;font-family:Consolas'>justified, yet the topic d=
oes not fit with an existing working group, </span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>and it i=
s either not ready for a BOF or a single BOF would not </span><o:p></o:p></=
p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas=
'>provide the time to ensure a mature proposal. The RTGWG will serve as </s=
pan><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:Consolas'>the forum for developing these types of proposals.</span=
><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:Consolas'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:Consolas'>The RTGWG also focuses on enhan=
cements to hop-by-hop distributed routing </span><o:p></o:p></p><p class=3D=
MsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>related to =
fast-reroute and loop-free convergence.&nbsp; A specific goal of </span><o:=
p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-famil=
y:Consolas'>fast-reroute mechanisms is to provide up to complete coverage w=
hen the </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size=
:10.0pt;font-family:Consolas'>potential failure would not partition the net=
work.&nbsp; All work in this </span><o:p></o:p></p><p class=3DMsoNormal><sp=
an style=3D'font-size:10.0pt;font-family:Consolas'>area should be specifica=
lly evaluated by the WG in terms of practicality </span><o:p></o:p></p><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>and =
applicability to deployed networks.</span><o:p></o:p></p><p class=3DMsoNorm=
al><span style=3D'font-size:10.0pt;font-family:Consolas'>&nbsp;</span><o:p>=
</o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:=
Consolas'>The RTGWG mailing list will be used to discuss the proposals as t=
hey </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:Consolas'>arise. The working group will meet if there are o=
ne or more active </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D=
'font-size:10.0pt;font-family:Consolas'>proposals that require discussion.<=
/span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;f=
ont-family:Consolas'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span=
 style=3D'font-size:10.0pt;font-family:Consolas'>The working group mileston=
es will be updated as needed to reflect the </span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>proposal=
s currently being worked on and the target dates for their </span><o:p></o:=
p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Cons=
olas'>completion. New milestones will be first reviewed by the IESG. The </=
span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:Consolas'>working group will be on-going as long as the ADs belie=
ve it serves a </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:10.0pt;font-family:Consolas'>useful purpose.</span><o:p></o:p></p><=
p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>&=
nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10=
.0pt;font-family:Consolas'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal=
><span style=3D'font-size:10.0pt;font-family:Consolas'>Apr 2012 Submit Comp=
osite-Link Requirements to IESG for publication as </span><o:p></o:p></p><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>In=
formational </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-=
size:10.0pt;font-family:Consolas'>Apr 2012 Submit Ordered FIB architecture =
to IESG for publication as Informational</span><o:p></o:p></p><p class=3DMs=
oNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>Nov 2012 Subm=
it Composite-Link Framework to IESG for publication as Informational </span=
><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:Consolas'>Apr 2013 Submit specification on Advanced IP Fast Reroute m=
echanism to&nbsp; IESG for publication as Proposed Standard </span><o:p></o=
:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Con=
solas'>Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute =
Architecture</span><o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p=
><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times Ne=
w Roman","serif"'><br><br><br><o:p></o:p></span></p><pre>__________________=
_____________________________<o:p></o:p></pre><pre>rtgwg mailing list<o:p><=
/o:p></pre><pre><a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><o:p></=
o:p></pre><pre><a href=3D"https://www.ietf.org/mailman/listinfo/rtgwg">http=
s://www.ietf.org/mailman/listinfo/rtgwg</a><o:p></o:p></pre><p class=3DMsoN=
ormal><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"=
'><o:p>&nbsp;</o:p></span></p></div></body></html>=

--_000_0ED867EB33AB2B45AAB470D5A64CDBF618198384A7EUSAACMS0701e_--

From akatlas@gmail.com  Mon Nov  7 09:47:14 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 413DC21F8B49 for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:47:14 -0800 (PST)
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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VcYZdt-E+8Qa for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 09:47:13 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA2621F8B37 for <rtgwg@ietf.org>; Mon,  7 Nov 2011 09:47:13 -0800 (PST)
Received: by qadc10 with SMTP id c10so4650331qad.31 for <rtgwg@ietf.org>; Mon, 07 Nov 2011 09:47:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=0n2SM6shWwg49T+ibe2hqYZovfQlKMYXUJleUq6dJsY=; b=i9h4daydUESX1o+LV0xDSuRiK25nyY6LrJlyCbAf8OSlhrEDwWAmuteWPeLAasT6lL xw1z6Au5NM/h47Oc63HmsTV6eTZAnvIbZQwfVneYxKtHcMyNkZt050s3ak57k6m1l2SC dHlZzKQFPG+QViCOVarINNSVYEfL+f/jJciqU=
MIME-Version: 1.0
Received: by 10.50.189.231 with SMTP id gl7mr47538128igc.44.1320688030961; Mon, 07 Nov 2011 09:47:10 -0800 (PST)
Received: by 10.50.203.10 with HTTP; Mon, 7 Nov 2011 09:47:10 -0800 (PST)
In-Reply-To: <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu>
Date: Mon, 7 Nov 2011 12:47:10 -0500
Message-ID: <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com>
Subject: Re: Charter Update (Discussion)
From: Alia Atlas <akatlas@gmail.com>
To: "John G. Scudder" <jgs@bgp.nu>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "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, 07 Nov 2011 17:47:14 -0000

We do have framework RFCs, but not requirements documents.

A question that we're actively looking for feedback on is whether the
WG wants to focus first on complete coverage solutions in the hope of
having a small set of solutions, on solutions that solve pieces of the
problem for some networks, or simply to evaluate solutions as they
come up.

Since a part of this re-chartering is to clarify that the design focus
for hop-by-hop fast-reroute activity is in RTGWG, I agree that we
should explicitly call out LDP and multicast since the wording isn't
as assertive about that.

Alia

2011/11/7 John G. Scudder <jgs@bgp.nu>:
> Some of this seems too detailed for a charter, and like it might go bette=
r in a requirements document. =A0(Did we do one of those, years ago? =A0It =
might be worth updating even so.)
>
> --John
>
> On Nov 3, 2011, at 7:56 AM, Andr=E1s Cs=E1sz=E1r wrote:
>
>> Some further comments:
>>
>> We probably shoud define "failure" a bit more clear. Single link, single=
 node, SRLG (local or remote), multiple failures.
>>
>> And also we probably should discuss this part a bit: "A specific goal of=
 fast-reroute mechanisms is to provide up tocomplete coverage".
>>
>> In my view, the target solution, while being practical, should be able t=
o provide
>>
>> 1. Complete coverage for all single link, single node and single SRLG (l=
ocal and remote) failures and for a reasonable number of pre-configured mul=
tiple failure cases deemed important by the operator.
>>
>>
>> If we can't find such a practical solution then we can fall back to a so=
lution, which provides
>> 2. Complete coverage for all single link, single node and single SRLG (l=
ocal and remote) failures.
>>
>> If we can't find such a practical solution then we can fall back to a so=
lution, which provides
>> 3. Complete coverage for all single link, single node and single local S=
RLG failures.
>>
>> If we can't find such a practical solution then we can fall back to a so=
lution, which provides
>> 4. Complete coverage for all single link and single node failures.
>>
>> Only =A0if we can't find such a practical solution, should we fall back =
to a solution, which provides
>> 5. Coverage higher than LFA for many/most single link and single node fa=
ilures.
>>
>> Andr=E1s
>>
>>
>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf O=
f Andr=E1s Cs=E1sz=E1r
>> Sent: 2011. november 3. 11:56
>> To: Retana, Alvaro; rtgwg@ietf.org
>> Subject: RE: Charter Update (Discussion)
>>
>> Hi!
>>
>> I think the proposed charter text is OK.
>> Comments:
>>
>> - I have the feeling that we should add LDP-MPLS explicitly. I know that=
 implicitly we mean IPFRR for IP and LDP, too. And I also see that we have =
the "enhancements to hop-by-hop distributed routing related to fast-reroute=
" portion in the proposed charter, which includes LDP. But still maybe sayi=
ng LDP-MPLS explicitly would be good for clarity.
>>
>> - The same goes for multicast. I see the last milestone is for multicast=
, that's OK, but maybe we should add it explicitly to the charter text.
>>
>> - Another thought regarding LDP, again: Do we have a position on whether=
 an LDP-only FRR solution (i.e. which would not work for plain IP) but prov=
ides 100% coverage is of interest? Or do we want to have a solution that is=
 applicable to both plain IP and LDP-MPLS?
>>
>> Maybe we should add something like this to the charter text: "...A speci=
fic goal of fast-reroute mechanisms is to provide up to complete coverage w=
hen the potential failure would not partition the network. The RTGWG seeks =
FRR solutions for both unicast and multicast on pure IP and LDP/mLDP-MPLS n=
etworks."
>>
>> - With some folks we were discussing in the background that the WG might=
 profit from an informational doc which lists/overviews and compares object=
ively all the proposed solutions. There is a pletora of proposals out there=
, some might have not even appeared at the IETF. Of course, we don't necess=
arily need to state such a doc explicitly as a milestone, I don't know.
>>
>> - If the multicast milestone is Apr 2012, then it should be earlier. Or =
if it was meant for Apr 2013, then the year needs to be corrected.
>>
>> Andras
>>
>>
>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf O=
f Retana, Alvaro
>> Sent: 2011. november 3. 2:13
>> To: rtgwg@ietf.org
>> Subject: Charter Update (Discussion)
>>
>> Hi!
>>
>> We=92re in the process of updating the WG charter and the list of milest=
ones.
>>
>> The main objective of the update is to clarify that FRR-related topics a=
re officially part of this WG =96 the main change is contained in the secon=
d paragraph. =A0Please take a look below and send your comments.
>>
>> For reference, here=92s the current charter: =A0http://tools.ietf.org/wg=
/rtgwg/charters
>>
>> Thanks!
>>
>> Alvaro.
>>
>>
>>
>>
>> The Routing area receives occasional proposals for the development and
>> publication of RFCs dealing with routing topics, but for which the
>> required work does not yet rise to the level where a new working group i=
s
>> justified, yet the topic does not fit with an existing working group,
>> and it is either not ready for a BOF or a single BOF would not
>> provide the time to ensure a mature proposal. The RTGWG will serve as
>> the forum for developing these types of proposals.
>>
>> The RTGWG also focuses on enhancements to hop-by-hop distributed routing
>> related to fast-reroute and loop-free convergence. =A0A specific goal of
>> fast-reroute mechanisms is to provide up to complete coverage when the
>> potential failure would not partition the network. =A0All work in this
>> area should be specifically evaluated by the WG in terms of practicality
>> and applicability to deployed networks.
>>
>> The RTGWG mailing list will be used to discuss the proposals as they
>> arise. The working group will meet if there are one or more active
>> proposals that require discussion.
>>
>> The working group milestones will be updated as needed to reflect the
>> proposals currently being worked on and the target dates for their
>> completion. New milestones will be first reviewed by the IESG. The
>> working group will be on-going as long as the ADs believe it serves a
>> useful purpose.
>>
>>
>> Apr 2012 Submit Composite-Link Requirements to IESG for publication as
>> Informational
>> Apr 2012 Submit Ordered FIB architecture to IESG for publication as Info=
rmational
>> Nov 2012 Submit Composite-Link Framework to IESG for publication as Info=
rmational
>> Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to =
=A0IESG for publication as Proposed Standard
>> Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute Arch=
itecture
>>
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>

From imc.shand@googlemail.com  Mon Nov  7 10:00:26 2011
Return-Path: <imc.shand@googlemail.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 C368621F8BF6 for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 10:00:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aWo8iGr2h7o6 for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 10:00:25 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 62ED021F8B7D for <rtgwg@ietf.org>; Mon,  7 Nov 2011 10:00:25 -0800 (PST)
Received: by wyg30 with SMTP id 30so668557wyg.31 for <rtgwg@ietf.org>; Mon, 07 Nov 2011 10:00:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=2BABnCiPakT6foTDvBDnpfUQg8a+exL94uoo/UaS4d8=; b=gyHR4XQd1pb7tVdSs64dvNz49gYguQiqlgmmeZD7bNpCBuVyb1hENylYWE19xSSYOS cq1SM2hpz/AzZeDCA7XHkqLBm8UI8IvRCldiwuhVczIs6lyN5hns8orm2dMlP1Jw7sfW cAGMOisAYtPrZ9o+qCKEHWxlEd7hznmetiXps=
Received: by 10.216.220.196 with SMTP id o46mr7459387wep.46.1320688824420; Mon, 07 Nov 2011 10:00:24 -0800 (PST)
Received: from [192.168.1.166] (188-220-40-104.zone11.bethere.co.uk. [188.220.40.104]) by mx.google.com with ESMTPS id x40sm28558415wbn.19.2011.11.07.10.00.22 (version=SSLv3 cipher=OTHER); Mon, 07 Nov 2011 10:00:23 -0800 (PST)
Message-ID: <4EB81CAD.4080402@googlemail.com>
Date: Mon, 07 Nov 2011 18:00:13 +0000
From: Mike Shand <imc.shand@googlemail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com>
In-Reply-To: <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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, 07 Nov 2011 18:00:26 -0000

On 07/11/2011 17:47, Alia Atlas wrote:
> We do have framework RFCs, but not requirements documents.
>
> A question that we're actively looking for feedback on is whether the
> WG wants to focus first on complete coverage solutions in the hope of
> having a small set of solutions, on solutions that solve pieces of the
> problem for some networks, or simply to evaluate solutions as they
> come up.

While I have always been in favour of complete coverage solutions, I do 
think that we need to consider the tradeoff between complexity (not just 
computational complexity, but implementation, deployment and operational 
complexity) and complete coverage. So I wouldn't like to exclude non 
complete coverage solutions (and indeed to some extent all solutions 
that cannot deal with arbitrary combinations of failures are in some 
sense incomplete) from consideration, especially if they are "low cost" 
compared to more complete solutions.
>
> Since a part of this re-chartering is to clarify that the design focus
> for hop-by-hop fast-reroute activity is in RTGWG, I agree that we
> should explicitly call out LDP and multicast since the wording isn't
> as assertive about that.
Yes, agreed.

     Mike


>
> Alia
>
> 2011/11/7 John G. Scudder<jgs@bgp.nu>:
>> Some of this seems too detailed for a charter, and like it might go better in a requirements document.  (Did we do one of those, years ago?  It might be worth updating even so.)
>>
>> --John
>>
>> On Nov 3, 2011, at 7:56 AM, András Császár wrote:
>>
>>> Some further comments:
>>>
>>> We probably shoud define "failure" a bit more clear. Single link, single node, SRLG (local or remote), multiple failures.
>>>
>>> And also we probably should discuss this part a bit: "A specific goal of fast-reroute mechanisms is to provide up tocomplete coverage".
>>>
>>> In my view, the target solution, while being practical, should be able to provide
>>>
>>> 1. Complete coverage for all single link, single node and single SRLG (local and remote) failures and for a reasonable number of pre-configured multiple failure cases deemed important by the operator.
>>>
>>>
>>> If we can't find such a practical solution then we can fall back to a solution, which provides
>>> 2. Complete coverage for all single link, single node and single SRLG (local and remote) failures.
>>>
>>> If we can't find such a practical solution then we can fall back to a solution, which provides
>>> 3. Complete coverage for all single link, single node and single local SRLG failures.
>>>
>>> If we can't find such a practical solution then we can fall back to a solution, which provides
>>> 4. Complete coverage for all single link and single node failures.
>>>
>>> Only  if we can't find such a practical solution, should we fall back to a solution, which provides
>>> 5. Coverage higher than LFA for many/most single link and single node failures.
>>>
>>> András
>>>
>>>
>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of András Császár
>>> Sent: 2011. november 3. 11:56
>>> To: Retana, Alvaro; rtgwg@ietf.org
>>> Subject: RE: Charter Update (Discussion)
>>>
>>> Hi!
>>>
>>> I think the proposed charter text is OK.
>>> Comments:
>>>
>>> - I have the feeling that we should add LDP-MPLS explicitly. I know that implicitly we mean IPFRR for IP and LDP, too. And I also see that we have the "enhancements to hop-by-hop distributed routing related to fast-reroute" portion in the proposed charter, which includes LDP. But still maybe saying LDP-MPLS explicitly would be good for clarity.
>>>
>>> - The same goes for multicast. I see the last milestone is for multicast, that's OK, but maybe we should add it explicitly to the charter text.
>>>
>>> - Another thought regarding LDP, again: Do we have a position on whether an LDP-only FRR solution (i.e. which would not work for plain IP) but provides 100% coverage is of interest? Or do we want to have a solution that is applicable to both plain IP and LDP-MPLS?
>>>
>>> Maybe we should add something like this to the charter text: "...A specific goal of fast-reroute mechanisms is to provide up to complete coverage when the potential failure would not partition the network. The RTGWG seeks FRR solutions for both unicast and multicast on pure IP and LDP/mLDP-MPLS networks."
>>>
>>> - With some folks we were discussing in the background that the WG might profit from an informational doc which lists/overviews and compares objectively all the proposed solutions. There is a pletora of proposals out there, some might have not even appeared at the IETF. Of course, we don't necessarily need to state such a doc explicitly as a milestone, I don't know.
>>>
>>> - If the multicast milestone is Apr 2012, then it should be earlier. Or if it was meant for Apr 2013, then the year needs to be corrected.
>>>
>>> Andras
>>>
>>>
>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of Retana, Alvaro
>>> Sent: 2011. november 3. 2:13
>>> To: rtgwg@ietf.org
>>> Subject: Charter Update (Discussion)
>>>
>>> Hi!
>>>
>>> We’re in the process of updating the WG charter and the list of milestones.
>>>
>>> The main objective of the update is to clarify that FRR-related topics are officially part of this WG – the main change is contained in the second paragraph.  Please take a look below and send your comments.
>>>
>>> For reference, here’s the current charter:  http://tools.ietf.org/wg/rtgwg/charters
>>>
>>> Thanks!
>>>
>>> Alvaro.
>>>
>>>
>>>
>>>
>>> The Routing area receives occasional proposals for the development and
>>> publication of RFCs dealing with routing topics, but for which the
>>> required work does not yet rise to the level where a new working group is
>>> justified, yet the topic does not fit with an existing working group,
>>> and it is either not ready for a BOF or a single BOF would not
>>> provide the time to ensure a mature proposal. The RTGWG will serve as
>>> the forum for developing these types of proposals.
>>>
>>> The RTGWG also focuses on enhancements to hop-by-hop distributed routing
>>> related to fast-reroute and loop-free convergence.  A specific goal of
>>> fast-reroute mechanisms is to provide up to complete coverage when the
>>> potential failure would not partition the network.  All work in this
>>> area should be specifically evaluated by the WG in terms of practicality
>>> and applicability to deployed networks.
>>>
>>> The RTGWG mailing list will be used to discuss the proposals as they
>>> arise. The working group will meet if there are one or more active
>>> proposals that require discussion.
>>>
>>> The working group milestones will be updated as needed to reflect the
>>> proposals currently being worked on and the target dates for their
>>> completion. New milestones will be first reviewed by the IESG. The
>>> working group will be on-going as long as the ADs believe it serves a
>>> useful purpose.
>>>
>>>
>>> Apr 2012 Submit Composite-Link Requirements to IESG for publication as
>>> Informational
>>> Apr 2012 Submit Ordered FIB architecture to IESG for publication as Informational
>>> Nov 2012 Submit Composite-Link Framework to IESG for publication as Informational
>>> Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to  IESG for publication as Proposed Standard
>>> Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute Architecture
>>>
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From akatlas@gmail.com  Mon Nov  7 10:06:15 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 9713A11E808B for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 10:06:15 -0800 (PST)
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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44jgO3mVIv9A for <rtgwg@ietfa.amsl.com>; Mon,  7 Nov 2011 10:06:14 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5E34111E8087 for <rtgwg@ietf.org>; Mon,  7 Nov 2011 10:06:13 -0800 (PST)
Received: by ggnv1 with SMTP id v1so6505634ggn.31 for <rtgwg@ietf.org>; Mon, 07 Nov 2011 10:06:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=MtLksGYerShJTBsD4vY8g41hB/mIrexbBh775x6uOiE=; b=c6tac4GwWw628KE8w+ehUiuVTOERxr5mumlw/7iufDSqnYZQc/5v8zuNxN3gDMM98q LAdsGL+/ssXzBndDCfYttZaHXmGuTN6biUqubtFdHigfCbvz+YBk4An8O3CGZB3YISW6 c6GNdkAv4c55++LJQzMPR1YVvXyWq/maWf0Lc=
MIME-Version: 1.0
Received: by 10.50.189.231 with SMTP id gl7mr47625751igc.44.1320689170752; Mon, 07 Nov 2011 10:06:10 -0800 (PST)
Received: by 10.50.203.10 with HTTP; Mon, 7 Nov 2011 10:06:10 -0800 (PST)
In-Reply-To: <4EB81CAD.4080402@googlemail.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com>
Date: Mon, 7 Nov 2011 13:06:10 -0500
Message-ID: <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com>
Subject: Re: Charter Update (Discussion)
From: Alia Atlas <akatlas@gmail.com>
To: Mike Shand <imc.shand@googlemail.com>
Content-Type: text/plain; charset=windows-1252
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: Mon, 07 Nov 2011 18:06:15 -0000

Hi Mike,

Yes, I certainly agree that it is a tradeoff between complexity (all
aspects) and coverage.  I'm concerned that we don't end up with too
many different and minimally compatible solutions.

Alia

On Mon, Nov 7, 2011 at 1:00 PM, Mike Shand <imc.shand@googlemail.com> wrote=
:
> On 07/11/2011 17:47, Alia Atlas wrote:
>>
>> We do have framework RFCs, but not requirements documents.
>>
>> A question that we're actively looking for feedback on is whether the
>> WG wants to focus first on complete coverage solutions in the hope of
>> having a small set of solutions, on solutions that solve pieces of the
>> problem for some networks, or simply to evaluate solutions as they
>> come up.
>
> While I have always been in favour of complete coverage solutions, I do
> think that we need to consider the tradeoff between complexity (not just
> computational complexity, but implementation, deployment and operational
> complexity) and complete coverage. So I wouldn't like to exclude non
> complete coverage solutions (and indeed to some extent all solutions that
> cannot deal with arbitrary combinations of failures are in some sense
> incomplete) from consideration, especially if they are "low cost" compare=
d
> to more complete solutions.
>>
>> Since a part of this re-chartering is to clarify that the design focus
>> for hop-by-hop fast-reroute activity is in RTGWG, I agree that we
>> should explicitly call out LDP and multicast since the wording isn't
>> as assertive about that.
>
> Yes, agreed.
>
> =A0 =A0Mike
>
>
>>
>> Alia
>>
>> 2011/11/7 John G. Scudder<jgs@bgp.nu>:
>>>
>>> Some of this seems too detailed for a charter, and like it might go
>>> better in a requirements document. =A0(Did we do one of those, years ag=
o? =A0It
>>> might be worth updating even so.)
>>>
>>> --John
>>>
>>> On Nov 3, 2011, at 7:56 AM, Andr=E1s Cs=E1sz=E1r wrote:
>>>
>>>> Some further comments:
>>>>
>>>> We probably shoud define "failure" a bit more clear. Single link, sing=
le
>>>> node, SRLG (local or remote), multiple failures.
>>>>
>>>> And also we probably should discuss this part a bit: "A specific goal =
of
>>>> fast-reroute mechanisms is to provide up tocomplete coverage".
>>>>
>>>> In my view, the target solution, while being practical, should be able
>>>> to provide
>>>>
>>>> 1. Complete coverage for all single link, single node and single SRLG
>>>> (local and remote) failures and for a reasonable number of pre-configu=
red
>>>> multiple failure cases deemed important by the operator.
>>>>
>>>>
>>>> If we can't find such a practical solution then we can fall back to a
>>>> solution, which provides
>>>> 2. Complete coverage for all single link, single node and single SRLG
>>>> (local and remote) failures.
>>>>
>>>> If we can't find such a practical solution then we can fall back to a
>>>> solution, which provides
>>>> 3. Complete coverage for all single link, single node and single local
>>>> SRLG failures.
>>>>
>>>> If we can't find such a practical solution then we can fall back to a
>>>> solution, which provides
>>>> 4. Complete coverage for all single link and single node failures.
>>>>
>>>> Only =A0if we can't find such a practical solution, should we fall bac=
k to
>>>> a solution, which provides
>>>> 5. Coverage higher than LFA for many/most single link and single node
>>>> failures.
>>>>
>>>> Andr=E1s
>>>>
>>>>
>>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
>>>> Of Andr=E1s Cs=E1sz=E1r
>>>> Sent: 2011. november 3. 11:56
>>>> To: Retana, Alvaro; rtgwg@ietf.org
>>>> Subject: RE: Charter Update (Discussion)
>>>>
>>>> Hi!
>>>>
>>>> I think the proposed charter text is OK.
>>>> Comments:
>>>>
>>>> - I have the feeling that we should add LDP-MPLS explicitly. I know th=
at
>>>> implicitly we mean IPFRR for IP and LDP, too. And I also see that we h=
ave
>>>> the "enhancements to hop-by-hop distributed routing related to fast-re=
route"
>>>> portion in the proposed charter, which includes LDP. But still maybe s=
aying
>>>> LDP-MPLS explicitly would be good for clarity.
>>>>
>>>> - The same goes for multicast. I see the last milestone is for
>>>> multicast, that's OK, but maybe we should add it explicitly to the cha=
rter
>>>> text.
>>>>
>>>> - Another thought regarding LDP, again: Do we have a position on wheth=
er
>>>> an LDP-only FRR solution (i.e. which would not work for plain IP) but
>>>> provides 100% coverage is of interest? Or do we want to have a solutio=
n that
>>>> is applicable to both plain IP and LDP-MPLS?
>>>>
>>>> Maybe we should add something like this to the charter text: "...A
>>>> specific goal of fast-reroute mechanisms is to provide up to complete
>>>> coverage when the potential failure would not partition the network. T=
he
>>>> RTGWG seeks FRR solutions for both unicast and multicast on pure IP an=
d
>>>> LDP/mLDP-MPLS networks."
>>>>
>>>> - With some folks we were discussing in the background that the WG mig=
ht
>>>> profit from an informational doc which lists/overviews and compares
>>>> objectively all the proposed solutions. There is a pletora of proposal=
s out
>>>> there, some might have not even appeared at the IETF. Of course, we do=
n't
>>>> necessarily need to state such a doc explicitly as a milestone, I don'=
t
>>>> know.
>>>>
>>>> - If the multicast milestone is Apr 2012, then it should be earlier. O=
r
>>>> if it was meant for Apr 2013, then the year needs to be corrected.
>>>>
>>>> Andras
>>>>
>>>>
>>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
>>>> Of Retana, Alvaro
>>>> Sent: 2011. november 3. 2:13
>>>> To: rtgwg@ietf.org
>>>> Subject: Charter Update (Discussion)
>>>>
>>>> Hi!
>>>>
>>>> We=92re in the process of updating the WG charter and the list of
>>>> milestones.
>>>>
>>>> The main objective of the update is to clarify that FRR-related topics
>>>> are officially part of this WG =96 the main change is contained in the=
 second
>>>> paragraph. =A0Please take a look below and send your comments.
>>>>
>>>> For reference, here=92s the current charter:
>>>> =A0http://tools.ietf.org/wg/rtgwg/charters
>>>>
>>>> Thanks!
>>>>
>>>> Alvaro.
>>>>
>>>>
>>>>
>>>>
>>>> The Routing area receives occasional proposals for the development and
>>>> publication of RFCs dealing with routing topics, but for which the
>>>> required work does not yet rise to the level where a new working group
>>>> is
>>>> justified, yet the topic does not fit with an existing working group,
>>>> and it is either not ready for a BOF or a single BOF would not
>>>> provide the time to ensure a mature proposal. The RTGWG will serve as
>>>> the forum for developing these types of proposals.
>>>>
>>>> The RTGWG also focuses on enhancements to hop-by-hop distributed routi=
ng
>>>> related to fast-reroute and loop-free convergence. =A0A specific goal =
of
>>>> fast-reroute mechanisms is to provide up to complete coverage when the
>>>> potential failure would not partition the network. =A0All work in this
>>>> area should be specifically evaluated by the WG in terms of practicali=
ty
>>>> and applicability to deployed networks.
>>>>
>>>> The RTGWG mailing list will be used to discuss the proposals as they
>>>> arise. The working group will meet if there are one or more active
>>>> proposals that require discussion.
>>>>
>>>> The working group milestones will be updated as needed to reflect the
>>>> proposals currently being worked on and the target dates for their
>>>> completion. New milestones will be first reviewed by the IESG. The
>>>> working group will be on-going as long as the ADs believe it serves a
>>>> useful purpose.
>>>>
>>>>
>>>> Apr 2012 Submit Composite-Link Requirements to IESG for publication as
>>>> Informational
>>>> Apr 2012 Submit Ordered FIB architecture to IESG for publication as
>>>> Informational
>>>> Nov 2012 Submit Composite-Link Framework to IESG for publication as
>>>> Informational
>>>> Apr 2013 Submit specification on Advanced IP Fast Reroute mechanism to
>>>> =A0IESG for publication as Proposed Standard
>>>> Apr 2012 Submit initial Internet Draft on Multicast IP Fast Reroute
>>>> Architecture
>>>>
>>>> _______________________________________________
>>>> rtgwg mailing list
>>>> rtgwg@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>

From Andras.Csaszar@ericsson.com  Tue Nov  8 09:21:00 2011
Return-Path: <Andras.Csaszar@ericsson.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 7D87A11E807F for <rtgwg@ietfa.amsl.com>; Tue,  8 Nov 2011 09:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.048
X-Spam-Level: 
X-Spam-Status: No, score=-6.048 tagged_above=-999 required=5 tests=[AWL=0.251,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohydsGEOsjzM for <rtgwg@ietfa.amsl.com>; Tue,  8 Nov 2011 09:20:59 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB5A21F8B67 for <rtgwg@ietf.org>; Tue,  8 Nov 2011 09:20:58 -0800 (PST)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-36-4eb964f9ab8b
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id E7.D7.13753.9F469BE4; Tue,  8 Nov 2011 18:20:57 +0100 (CET)
Received: from ESESSCMS0363.eemea.ericsson.se ([169.254.1.47]) by esessmw0184.eemea.ericsson.se ([10.2.3.53]) with mapi; Tue, 8 Nov 2011 18:20:56 +0100
From: =?Windows-1252?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, Alia Atlas <akatlas@gmail.com>, Mike Shand <imc.shand@googlemail.com>
Date: Tue, 8 Nov 2011 18:20:54 +0100
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: Acydd/NqyPadXY4dSp6vqwzRrviJ0gAu3RAQ
Message-ID: <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com>
In-Reply-To: <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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, 08 Nov 2011 17:21:00 -0000

I think we should first see if there is a solution which provides full cove=
rage and practical (=3Dreasonable complexity).=20

One problem with non-full-coverage solutions is bidirectional coverage. I.e=
. even if a flow is covered for a failure in one direction it may not be co=
vered in the reverse direction which is, for most applications, equal to no=
t being covered at all. This property is often neglected in coverage estima=
tes. As an example consider the LFA unfirendly sub-topologies like longer-t=
han-triangle rings. In those rings it might seem that the failures on the o=
pposing side to the exit point are covered by the LFA. But they are not cov=
ered in the reverse direction. Might be a factor to consider for PQ and co =
too.

Being involved, I obviously think that there are practical enough solutions=
 for full coverage: draft-atlas-rtgwg-mrt-frr-architecture-01 would be one =
such solution within the local repair principle, while draft-csaszar-ipfrr-=
fn-02 would also be such a solution not based on local repair.

Both MRT-FRR and IPFRR-FN can be said to provide full failure coverage(*) a=
nd both seem to be more complex at first sight than they really are (includ=
ing implementation considerations). And both have running code already.

(*):
With MRT-FRR, full failure coverage means all single link and single node f=
ailures, and (we strongly suspect) single local SRLG failures. We hope that=
 single generic SRLG failures can be solved, too, but would really welcome =
ideas and thoughts here.

IPFRR-FN provides coverage for single link and single node failures as well=
 as all single generic SRLG failures and it is even capable to cover a reas=
onable number of pre-configured multiple failure cases deemed important by =
the operator.

There are clearly other tradeoff factors besides coverage and complexity su=
ch as backup path length, incremental deployability, support of IP or LDP o=
r both, etc.

Regards,
Andr=E1s


> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org]=20
> On Behalf Of Alia Atlas
> Sent: 2011. november 7. 19:06
> To: Mike Shand
> Cc: rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>=20
> Hi Mike,
>=20
> Yes, I certainly agree that it is a tradeoff between complexity (all
> aspects) and coverage.  I'm concerned that we don't end up=20
> with too many different and minimally compatible solutions.
>=20
> Alia
>=20
> On Mon, Nov 7, 2011 at 1:00 PM, Mike Shand=20
> <imc.shand@googlemail.com> wrote:
> > On 07/11/2011 17:47, Alia Atlas wrote:
> >>
> >> We do have framework RFCs, but not requirements documents.
> >>
> >> A question that we're actively looking for feedback on is=20
> whether the=20
> >> WG wants to focus first on complete coverage solutions in=20
> the hope of=20
> >> having a small set of solutions, on solutions that solve pieces of=20
> >> the problem for some networks, or simply to evaluate solutions as=20
> >> they come up.
> >
> > While I have always been in favour of complete coverage=20
> solutions, I=20
> > do think that we need to consider the tradeoff between=20
> complexity (not=20
> > just computational complexity, but implementation, deployment and=20
> > operational
> > complexity) and complete coverage. So I wouldn't like to=20
> exclude non=20
> > complete coverage solutions (and indeed to some extent all=20
> solutions=20
> > that cannot deal with arbitrary combinations of failures=20
> are in some=20
> > sense
> > incomplete) from consideration, especially if they are "low cost"=20
> > compared to more complete solutions.
> >>
> >> Since a part of this re-chartering is to clarify that the design=20
> >> focus for hop-by-hop fast-reroute activity is in RTGWG, I=20
> agree that=20
> >> we should explicitly call out LDP and multicast since the wording=20
> >> isn't as assertive about that.
> >
> > Yes, agreed.
> >
> > =A0 =A0Mike
> >
> >
> >>
> >> Alia
> >>
> >> 2011/11/7 John G. Scudder<jgs@bgp.nu>:
> >>>
> >>> Some of this seems too detailed for a charter, and like=20
> it might go=20
> >>> better in a requirements document. =A0(Did we do one of=20
> those, years=20
> >>> ago? =A0It might be worth updating even so.)
> >>>
> >>> --John
> >>>
> >>> On Nov 3, 2011, at 7:56 AM, Andr=E1s Cs=E1sz=E1r wrote:
> >>>
> >>>> Some further comments:
> >>>>
> >>>> We probably shoud define "failure" a bit more clear.=20
> Single link,=20
> >>>> single node, SRLG (local or remote), multiple failures.
> >>>>
> >>>> And also we probably should discuss this part a bit: "A specific=20
> >>>> goal of fast-reroute mechanisms is to provide up=20
> tocomplete coverage".
> >>>>
> >>>> In my view, the target solution, while being practical,=20
> should be=20
> >>>> able to provide
> >>>>
> >>>> 1. Complete coverage for all single link, single node and single=20
> >>>> SRLG (local and remote) failures and for a reasonable number of=20
> >>>> pre-configured multiple failure cases deemed important=20
> by the operator.
> >>>>
> >>>>
> >>>> If we can't find such a practical solution then we can=20
> fall back to=20
> >>>> a solution, which provides 2. Complete coverage for all single=20
> >>>> link, single node and single SRLG (local and remote) failures.
> >>>>
> >>>> If we can't find such a practical solution then we can=20
> fall back to=20
> >>>> a solution, which provides 3. Complete coverage for all single=20
> >>>> link, single node and single local SRLG failures.
> >>>>
> >>>> If we can't find such a practical solution then we can=20
> fall back to=20
> >>>> a solution, which provides 4. Complete coverage for all=20
> single link=20
> >>>> and single node failures.
> >>>>
> >>>> Only =A0if we can't find such a practical solution, should we fall=20
> >>>> back to a solution, which provides 5. Coverage higher=20
> than LFA for=20
> >>>> many/most single link and single node failures.
> >>>>
> >>>> Andr=E1s
> >>>>
> >>>>
> >>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On=20
> >>>> Behalf Of Andr=E1s Cs=E1sz=E1r
> >>>> Sent: 2011. november 3. 11:56
> >>>> To: Retana, Alvaro; rtgwg@ietf.org
> >>>> Subject: RE: Charter Update (Discussion)
> >>>>
> >>>> Hi!
> >>>>
> >>>> I think the proposed charter text is OK.
> >>>> Comments:
> >>>>
> >>>> - I have the feeling that we should add LDP-MPLS=20
> explicitly. I know=20
> >>>> that implicitly we mean IPFRR for IP and LDP, too. And I=20
> also see=20
> >>>> that we have the "enhancements to hop-by-hop distributed=20
> routing related to fast-reroute"
> >>>> portion in the proposed charter, which includes LDP. But still=20
> >>>> maybe saying LDP-MPLS explicitly would be good for clarity.
> >>>>
> >>>> - The same goes for multicast. I see the last milestone is for=20
> >>>> multicast, that's OK, but maybe we should add it=20
> explicitly to the=20
> >>>> charter text.
> >>>>
> >>>> - Another thought regarding LDP, again: Do we have a position on=20
> >>>> whether an LDP-only FRR solution (i.e. which would not work for=20
> >>>> plain IP) but provides 100% coverage is of interest? Or=20
> do we want=20
> >>>> to have a solution that is applicable to both plain IP=20
> and LDP-MPLS?
> >>>>
> >>>> Maybe we should add something like this to the charter=20
> text: "...A=20
> >>>> specific goal of fast-reroute mechanisms is to provide up to=20
> >>>> complete coverage when the potential failure would not partition=20
> >>>> the network. The RTGWG seeks FRR solutions for both unicast and=20
> >>>> multicast on pure IP and LDP/mLDP-MPLS networks."
> >>>>
> >>>> - With some folks we were discussing in the background=20
> that the WG=20
> >>>> might profit from an informational doc which lists/overviews and=20
> >>>> compares objectively all the proposed solutions. There=20
> is a pletora=20
> >>>> of proposals out there, some might have not even appeared at the=20
> >>>> IETF. Of course, we don't necessarily need to state such a doc=20
> >>>> explicitly as a milestone, I don't know.
> >>>>
> >>>> - If the multicast milestone is Apr 2012, then it should be=20
> >>>> earlier. Or if it was meant for Apr 2013, then the year=20
> needs to be corrected.
> >>>>
> >>>> Andras
> >>>>
> >>>>
> >>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On=20
> >>>> Behalf Of Retana, Alvaro
> >>>> Sent: 2011. november 3. 2:13
> >>>> To: rtgwg@ietf.org
> >>>> Subject: Charter Update (Discussion)
> >>>>
> >>>> Hi!
> >>>>
> >>>> We=92re in the process of updating the WG charter and the list of=20
> >>>> milestones.
> >>>>
> >>>> The main objective of the update is to clarify that FRR-related=20
> >>>> topics are officially part of this WG =96 the main change is=20
> >>>> contained in the second paragraph. =A0Please take a look=20
> below and send your comments.
> >>>>
> >>>> For reference, here=92s the current charter:
> >>>> =A0http://tools.ietf.org/wg/rtgwg/charters
> >>>>
> >>>> Thanks!
> >>>>
> >>>> Alvaro.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> The Routing area receives occasional proposals for the=20
> development=20
> >>>> and publication of RFCs dealing with routing topics, but=20
> for which=20
> >>>> the required work does not yet rise to the level where a new=20
> >>>> working group is justified, yet the topic does not fit with an=20
> >>>> existing working group, and it is either not ready for a=20
> BOF or a=20
> >>>> single BOF would not provide the time to ensure a mature=20
> proposal.=20
> >>>> The RTGWG will serve as the forum for developing these types of=20
> >>>> proposals.
> >>>>
> >>>> The RTGWG also focuses on enhancements to hop-by-hop distributed=20
> >>>> routing related to fast-reroute and loop-free convergence. =A0A=20
> >>>> specific goal of fast-reroute mechanisms is to provide up to=20
> >>>> complete coverage when the potential failure would not partition=20
> >>>> the network. =A0All work in this area should be specifically=20
> >>>> evaluated by the WG in terms of practicality and=20
> applicability to deployed networks.
> >>>>
> >>>> The RTGWG mailing list will be used to discuss the proposals as=20
> >>>> they arise. The working group will meet if there are one or more=20
> >>>> active proposals that require discussion.
> >>>>
> >>>> The working group milestones will be updated as needed=20
> to reflect=20
> >>>> the proposals currently being worked on and the target dates for=20
> >>>> their completion. New milestones will be first reviewed by the=20
> >>>> IESG. The working group will be on-going as long as the=20
> ADs believe=20
> >>>> it serves a useful purpose.
> >>>>
> >>>>
> >>>> Apr 2012 Submit Composite-Link Requirements to IESG for=20
> publication=20
> >>>> as Informational Apr 2012 Submit Ordered FIB=20
> architecture to IESG=20
> >>>> for publication as Informational Nov 2012 Submit Composite-Link=20
> >>>> Framework to IESG for publication as Informational Apr=20
> 2013 Submit=20
> >>>> specification on Advanced IP Fast Reroute mechanism to
> >>>> =A0IESG for publication as Proposed Standard Apr 2012=20
> Submit initial=20
> >>>> Internet Draft on Multicast IP Fast Reroute Architecture
> >>>>
> >>>> _______________________________________________
> >>>> rtgwg mailing list
> >>>> rtgwg@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/rtgwg
> >>>
> >>> _______________________________________________
> >>> rtgwg mailing list
> >>> rtgwg@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/rtgwg
> >>>
> >> _______________________________________________
> >> rtgwg mailing list
> >> rtgwg@ietf.org
> >> https://www.ietf.org/mailman/listinfo/rtgwg
> >
> > _______________________________________________
> > rtgwg mailing list
> > rtgwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtgwg
> >
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
> =

From stbryant@cisco.com  Tue Nov  8 09:54:14 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 35E9621F8B02 for <rtgwg@ietfa.amsl.com>; Tue,  8 Nov 2011 09:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.356
X-Spam-Level: 
X-Spam-Status: No, score=-109.356 tagged_above=-999 required=5 tests=[AWL=1.243, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZLVnCOuiZMVl for <rtgwg@ietfa.amsl.com>; Tue,  8 Nov 2011 09:54:13 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 7575B21F8AF8 for <rtgwg@ietf.org>; Tue,  8 Nov 2011 09:54:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=981; q=dns/txt; s=iport; t=1320774853; x=1321984453; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=KBtxM8AZ9FOGXO18bvsUGjaKEbA2cHPnJCfeWe9O0ts=; b=JYA/KltWb4eDaNZUIqbG4aQn80FXgfUlJuyma8CG6MDVF95AwHxm4X46 2In6kbnAt1IOttmBhNFwxMQFXe5gG6BMGgxv2qafNaIGpUE5W2YHenXXm JNhwXE60L758tc9lYrOos5WYdxOdRdXgqk7YBV3OEp4fQcK6WjIJMf4pq M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtUHANlruU6Q/khR/2dsb2JhbABEmmCNH4IigQWBcgEBAQQSAQIBHAEFQBELGAkWDwkDAgECAUUTCAEBFwegRwGDLg8Bm1GJLQSUIZFu
X-IronPort-AV: E=Sophos;i="4.69,477,1315180800"; d="scan'208";a="121099981"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 08 Nov 2011 17:54:12 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA8Hs8dD021994 for <rtgwg@ietf.org>; Tue, 8 Nov 2011 17:54:12 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id pA8Hs8Nn009402; Tue, 8 Nov 2011 17:54:08 GMT
Message-ID: <4EB96CBF.7040501@cisco.com>
Date: Tue, 08 Nov 2011 17:54:07 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se>
In-Reply-To: <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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: Tue, 08 Nov 2011 17:54:14 -0000

On 08/11/2011 17:20, András Császár wrote:
> I think we should first see if there is a solution which provides full coverage and practical (=reasonable complexity).
>
> One problem with non-full-coverage solutions is bidirectional coverage. I.e. even if a flow is covered for a failure in one direction it may not be covered in the reverse direction which is, for most applications, equal to not being covered at all. This property is often neglected in coverage estimates. As an example consider the LFA unfirendly sub-topologies like longer-than-triangle rings. In those rings it might seem that the failures on the opposing side to the exit point are covered by the LFA. But they are not covered in the reverse direction. Might be a factor to consider for PQ and co too.
Can you give me an example here?

I would expect a ring to have symmetric properties except when there are 
asymmetric costs, but normally assymetric costs are a configuration 
accident.

Stewart

From Andras.Csaszar@ericsson.com  Wed Nov  9 02:59:52 2011
Return-Path: <Andras.Csaszar@ericsson.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 64B0621F8C1F for <rtgwg@ietfa.amsl.com>; Wed,  9 Nov 2011 02:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.071
X-Spam-Level: 
X-Spam-Status: No, score=-6.071 tagged_above=-999 required=5 tests=[AWL=0.228,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PrBAs+7ydgW for <rtgwg@ietfa.amsl.com>; Wed,  9 Nov 2011 02:59:51 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 97E2D21F8C21 for <rtgwg@ietf.org>; Wed,  9 Nov 2011 02:59:51 -0800 (PST)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-b9-4eba5d26eb15
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 4F.E4.13753.62D5ABE4; Wed,  9 Nov 2011 11:59:50 +0100 (CET)
Received: from ESESSCMS0363.eemea.ericsson.se ([153.88.115.183]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Wed, 9 Nov 2011 11:59:50 +0100
From: =?Windows-1252?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Wed, 9 Nov 2011 11:59:49 +0100
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcyeP29s6+gG42LfSDm1b4sPn9931AAjFD0g
Message-ID: <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com>
In-Reply-To: <4EB96CBF.7040501@cisco.com>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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, 09 Nov 2011 10:59:52 -0000

Hi Stewart, this phenomenon occurs with symmetric costs with LFA.

Trying to sketch an example:

       2        2
[Src]-----[A]------[B]
  |                 |
 1|                 |1
  |                 |
 [C]-------------[Dest]
          2

Now for Src->Dest traffic, the link failure of Src-C can be remedied with L=
FA, as Src may pass the packet to A which is an LFA. For backwards traffic =
(e.g. TCP Acks) this link failure cannot be solved by C with LFA, so ultima=
tely the Src-Dest traffic is screwed.


Andr=E1s


> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org]=20
> On Behalf Of Stewart Bryant
> Sent: 2011. november 8. 18:54
> To: rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>=20
> On 08/11/2011 17:20, Andr=E1s Cs=E1sz=E1r wrote:
> > I think we should first see if there is a solution which=20
> provides full coverage and practical (=3Dreasonable complexity).
> >
> > One problem with non-full-coverage solutions is=20
> bidirectional coverage. I.e. even if a flow is covered for a=20
> failure in one direction it may not be covered in the reverse=20
> direction which is, for most applications, equal to not being=20
> covered at all. This property is often neglected in coverage=20
> estimates. As an example consider the LFA unfirendly=20
> sub-topologies like longer-than-triangle rings. In those=20
> rings it might seem that the failures on the opposing side to=20
> the exit point are covered by the LFA. But they are not=20
> covered in the reverse direction. Might be a factor to=20
> consider for PQ and co too.
> Can you give me an example here?
>=20
> I would expect a ring to have symmetric properties except=20
> when there are asymmetric costs, but normally assymetric=20
> costs are a configuration accident.
>=20
> Stewart
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
> =

From stbryant@cisco.com  Wed Nov  9 09:56:32 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 A93E221F84ED for <rtgwg@ietfa.amsl.com>; Wed,  9 Nov 2011 09:56:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.302
X-Spam-Level: 
X-Spam-Status: No, score=-107.302 tagged_above=-999 required=5 tests=[AWL=-1.003, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wl+ULwYBI8pV for <rtgwg@ietfa.amsl.com>; Wed,  9 Nov 2011 09:56:31 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 6CBF921F84DD for <rtgwg@ietf.org>; Wed,  9 Nov 2011 09:56:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=2592; q=dns/txt; s=iport; t=1320861390; x=1322070990; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=XyXsftvNS2fN/FQ/yuiD0NrNwkpkQHY5G0iCa34IFBo=; b=d/DopB3npDnqovbbwqbg7uWyDjwBdEjz39hbi+ciKzTJEsQbCwf4BmVD hdylGANfh4stwboJzoFyohi6e6g9hUWWnLLwv6mK88aw/qokUswfJP0lr xB8Cuxc7gRMNg4YRjSgAJoYloHoIBDkQE1DCP7vXqfnlsJpTyvdfeMUuC Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAIy+uk6Q/khM/2dsb2JhbAA8BqokgQWBcgEBAQQBAQEPAQIBEQsBBTYKAQwECxEEAQEBCRYIBwkDAgECARUfCQgGDQEFAgEBFweHaJh1AYMuDwGbWoZZgyYElCWRcg
X-IronPort-AV: E=Sophos;i="4.69,484,1315180800";  d="scan'208";a="2742062"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 09 Nov 2011 17:56:29 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pA9HuThL020728; Wed, 9 Nov 2011 17:56:29 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id pA9HuSpi019237; Wed, 9 Nov 2011 17:56:28 GMT
Message-ID: <4EBABECC.2060701@cisco.com>
Date: Wed, 09 Nov 2011 17:56:28 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: =?windows-1252?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se>
In-Reply-To: <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
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, 09 Nov 2011 17:56:32 -0000

Hi András

Yes, it is true that for that topology fragment there is no 
bidirectional LFA solution.

However you were talking about rings, and surely it's unusual for a ring 
topology to have non-uniform costs.

If we consider tunnel solution with forced first hop the solution would 
work.

C tunnels to A with forced first hop (C-Dest), decap and A to Src.
Src LFAs to A, A sends to B, B sends to Dest

- Stewart

On 09/11/2011 10:59, András Császár wrote:
> Hi Stewart, this phenomenon occurs with symmetric costs with LFA.
>
> Trying to sketch an example:
>
>         2        2
> [Src]-----[A]------[B]
>    |                 |
>   1|                 |1
>    |                 |
>   [C]-------------[Dest]
>            2
>
> Now for Src->Dest traffic, the link failure of Src-C can be remedied with LFA, as Src may pass the packet to A which is an LFA. For backwards traffic (e.g. TCP Acks) this link failure cannot be solved by C with LFA, so ultimately the Src-Dest traffic is screwed.
>
>
> András
>
>
>> -----Original Message-----
>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org]
>> On Behalf Of Stewart Bryant
>> Sent: 2011. november 8. 18:54
>> To: rtgwg@ietf.org
>> Subject: Re: Charter Update (Discussion)
>>
>> On 08/11/2011 17:20, András Császár wrote:
>>> I think we should first see if there is a solution which
>> provides full coverage and practical (=reasonable complexity).
>>> One problem with non-full-coverage solutions is
>> bidirectional coverage. I.e. even if a flow is covered for a
>> failure in one direction it may not be covered in the reverse
>> direction which is, for most applications, equal to not being
>> covered at all. This property is often neglected in coverage
>> estimates. As an example consider the LFA unfirendly
>> sub-topologies like longer-than-triangle rings. In those
>> rings it might seem that the failures on the opposing side to
>> the exit point are covered by the LFA. But they are not
>> covered in the reverse direction. Might be a factor to
>> consider for PQ and co too.
>> Can you give me an example here?
>>
>> I would expect a ring to have symmetric properties except
>> when there are asymmetric costs, but normally assymetric
>> costs are a configuration accident.
>>
>> Stewart
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From gabor.sandor.enyedi@ericsson.com  Wed Nov  9 12:54:36 2011
Return-Path: <gabor.sandor.enyedi@ericsson.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 E904511E8093 for <rtgwg@ietfa.amsl.com>; Wed,  9 Nov 2011 12:54:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AvnuzL8ZKH-e for <rtgwg@ietfa.amsl.com>; Wed,  9 Nov 2011 12:54:36 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 0DED611E8080 for <rtgwg@ietf.org>; Wed,  9 Nov 2011 12:54:33 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-ae-4ebae8894bbd
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id FB.63.09514.988EABE4; Wed,  9 Nov 2011 21:54:33 +0100 (CET)
Received: from ESESSCMS0359.eemea.ericsson.se ([169.254.1.79]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Wed, 9 Nov 2011 21:54:32 +0100
From: =?iso-8859-1?Q?G=E1bor_S=E1ndor_Enyedi?= <gabor.sandor.enyedi@ericsson.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, =?iso-8859-1?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
Date: Wed, 9 Nov 2011 21:54:31 +0100
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcyfCOv7fBu2aMZrTpuaVomQrCJU2QAFejYA
Message-ID: <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com>
In-Reply-To: <4EBABECC.2060701@cisco.com>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "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: Wed, 09 Nov 2011 20:54:37 -0000

Hi Steward,


That's forced first hop won't help; I can always add an extra node against =
such tricks. :)

        4       4
 [Src]-----[A]------[B]
    |                 |
   2|                 |1
    |                 |
   [C]-----[D]-----[Dest]
        1       3

You cannot solve this without "directed forwarding" (forcing B with some ma=
gic to forward packets to A instead of to Dest). Think on that phenomenon l=
ike this: until you have only P chance to protect a failure, protecting it =
in both directions will always be P*P<P until P<1. :)


Gabor


-----Original Message-----
From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of S=
tewart Bryant
Sent: Wednesday, November 09, 2011 6:56 PM
To: Andr=E1s Cs=E1sz=E1r
Cc: rtgwg@ietf.org
Subject: Re: Charter Update (Discussion)


Hi Andr=E1s

Yes, it is true that for that topology fragment there is no bidirectional L=
FA solution.

However you were talking about rings, and surely it's unusual for a ring to=
pology to have non-uniform costs.

If we consider tunnel solution with forced first hop the solution would wor=
k.

C tunnels to A with forced first hop (C-Dest), decap and A to Src.
Src LFAs to A, A sends to B, B sends to Dest

- Stewart

On 09/11/2011 10:59, Andr=E1s Cs=E1sz=E1r wrote:
> Hi Stewart, this phenomenon occurs with symmetric costs with LFA.
>
> Trying to sketch an example:
>
>         2        2
> [Src]-----[A]------[B]
>    |                 |
>   1|                 |1
>    |                 |
>   [C]-------------[Dest]
>            2
>
> Now for Src->Dest traffic, the link failure of Src-C can be remedied with=
 LFA, as Src may pass the packet to A which is an LFA. For backwards traffi=
c (e.g. TCP Acks) this link failure cannot be solved by C with LFA, so ulti=
mately the Src-Dest traffic is screwed.
>
>
> Andr=E1s
>
>
>> -----Original Message-----
>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On=20
>> Behalf Of Stewart Bryant
>> Sent: 2011. november 8. 18:54
>> To: rtgwg@ietf.org
>> Subject: Re: Charter Update (Discussion)
>>
>> On 08/11/2011 17:20, Andr=E1s Cs=E1sz=E1r wrote:
>>> I think we should first see if there is a solution which
>> provides full coverage and practical (=3Dreasonable complexity).
>>> One problem with non-full-coverage solutions is
>> bidirectional coverage. I.e. even if a flow is covered for a failure=20
>> in one direction it may not be covered in the reverse direction which=20
>> is, for most applications, equal to not being covered at all. This=20
>> property is often neglected in coverage estimates. As an example=20
>> consider the LFA unfirendly sub-topologies like longer-than-triangle=20
>> rings. In those rings it might seem that the failures on the opposing=20
>> side to the exit point are covered by the LFA. But they are not=20
>> covered in the reverse direction. Might be a factor to consider for=20
>> PQ and co too.
>> Can you give me an example here?
>>
>> I would expect a ring to have symmetric properties except when there=20
>> are asymmetric costs, but normally assymetric costs are a=20
>> configuration accident.
>>
>> Stewart
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>>


--
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


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

From stbryant@cisco.com  Wed Nov  9 17:14:18 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 007DC11E8098 for <rtgwg@ietfa.amsl.com>; Wed,  9 Nov 2011 17:14:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.265
X-Spam-Level: 
X-Spam-Status: No, score=-107.265 tagged_above=-999 required=5 tests=[AWL=-0.966, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2bzfvc2rI3hV for <rtgwg@ietfa.amsl.com>; Wed,  9 Nov 2011 17:14:17 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id CBCBC11E8088 for <rtgwg@ietf.org>; Wed,  9 Nov 2011 17:14:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=4102; q=dns/txt; s=iport; t=1320887657; x=1322097257; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ZLDA1GzwCB9UM0dG28Nhtm+SOwQVzERncmNzDuBNPCA=; b=XPdoV/8Rz/zmfoY6gYsSyc/izgYs8OqfX1KxKgIL3CUdg2lk91L4u/VJ iYTonXlh8cyYpN8m1vmQloCHZNKXdHbsLS24YehbnA5bhucuFcs6Rt4eQ WC5zW1raeA9WJnpT7YCsrQn9qKTg7KSV9ZSnQsR0Rsk41GMCZ1Pe1Qqhv M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At4AAJQku06Q/khN/2dsb2JhbAA+Bpooj3yBBYFyAQEBBAEBAQ8BAgERCwEFNgoBDAQLEQQBAQEJFggHCQMCAQIBFR8JCAYNAQUCAQEXB4domGgBgy4PAZtPhlmDJgSUJZFy
X-IronPort-AV: E=Sophos;i="4.69,486,1315180800";  d="scan'208";a="2758820"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 10 Nov 2011 01:14:14 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAA1EEbm010381; Thu, 10 Nov 2011 01:14:14 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id pAA1EBlF013835; Thu, 10 Nov 2011 01:14:11 GMT
Message-ID: <4EBB2563.5010302@cisco.com>
Date: Thu, 10 Nov 2011 01:14:11 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?G=E1bor_S=E1ndor_Enyedi?= <gabor.sandor.enyedi@ericsson.com>
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se>
In-Reply-To: <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
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: Thu, 10 Nov 2011 01:14:18 -0000

On 09/11/2011 20:54, Gábor Sándor Enyedi wrote:
> Hi Steward,
>
>
> That's forced first hop won't help; I can always add an extra node against such tricks. :)
>
>          4       4
>   [Src]-----[A]------[B]
>      |                 |
>     2|                 |1
>      |                 |
>     [C]-----[D]-----[Dest]
>          1       3
>
> You cannot solve this without "directed forwarding" (forcing B with some magic to forward packets to A instead of to Dest). Think on that phenomenon like this: until you have only P chance to protect a failure, protecting it in both directions will always be P*P<P until P<1. :)
>
>
> Gabor
>
We would have solved that in the original tunnels draft with directed 
forwarding at B.

However you have not answered my point that practical rings (as opposed 
to ring fragments in mesh topologies) normally have equal cost per hop.

Stewart


> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Wednesday, November 09, 2011 6:56 PM
> To: András Császár
> Cc: rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>
>
> Hi András
>
> Yes, it is true that for that topology fragment there is no bidirectional LFA solution.
>
> However you were talking about rings, and surely it's unusual for a ring topology to have non-uniform costs.
>
> If we consider tunnel solution with forced first hop the solution would work.
>
> C tunnels to A with forced first hop (C-Dest), decap and A to Src.
> Src LFAs to A, A sends to B, B sends to Dest
>
> - Stewart
>
> On 09/11/2011 10:59, András Császár wrote:
>> Hi Stewart, this phenomenon occurs with symmetric costs with LFA.
>>
>> Trying to sketch an example:
>>
>>          2        2
>> [Src]-----[A]------[B]
>>     |                 |
>>    1|                 |1
>>     |                 |
>>    [C]-------------[Dest]
>>             2
>>
>> Now for Src->Dest traffic, the link failure of Src-C can be remedied with LFA, as Src may pass the packet to A which is an LFA. For backwards traffic (e.g. TCP Acks) this link failure cannot be solved by C with LFA, so ultimately the Src-Dest traffic is screwed.
>>
>>
>> András
>>
>>
>>> -----Original Message-----
>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On
>>> Behalf Of Stewart Bryant
>>> Sent: 2011. november 8. 18:54
>>> To: rtgwg@ietf.org
>>> Subject: Re: Charter Update (Discussion)
>>>
>>> On 08/11/2011 17:20, András Császár wrote:
>>>> I think we should first see if there is a solution which
>>> provides full coverage and practical (=reasonable complexity).
>>>> One problem with non-full-coverage solutions is
>>> bidirectional coverage. I.e. even if a flow is covered for a failure
>>> in one direction it may not be covered in the reverse direction which
>>> is, for most applications, equal to not being covered at all. This
>>> property is often neglected in coverage estimates. As an example
>>> consider the LFA unfirendly sub-topologies like longer-than-triangle
>>> rings. In those rings it might seem that the failures on the opposing
>>> side to the exit point are covered by the LFA. But they are not
>>> covered in the reverse direction. Might be a factor to consider for
>>> PQ and co too.
>>> Can you give me an example here?
>>>
>>> I would expect a ring to have symmetric properties except when there
>>> are asymmetric costs, but normally assymetric costs are a
>>> configuration accident.
>>>
>>> Stewart
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From Andras.Csaszar@ericsson.com  Thu Nov 10 01:31:44 2011
Return-Path: <Andras.Csaszar@ericsson.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 B37CF21F84D6 for <rtgwg@ietfa.amsl.com>; Thu, 10 Nov 2011 01:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.09
X-Spam-Level: 
X-Spam-Status: No, score=-6.09 tagged_above=-999 required=5 tests=[AWL=0.209,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gsSB6gK1GX6H for <rtgwg@ietfa.amsl.com>; Thu, 10 Nov 2011 01:31:44 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 85FD721F84D7 for <rtgwg@ietf.org>; Thu, 10 Nov 2011 01:31:43 -0800 (PST)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-71-4ebb99fe4807
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id CE.66.13753.EF99BBE4; Thu, 10 Nov 2011 10:31:42 +0100 (CET)
Received: from ESESSCMS0363.eemea.ericsson.se ([169.254.1.212]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Thu, 10 Nov 2011 10:31:42 +0100
From: =?iso-8859-1?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Thu, 10 Nov 2011 10:31:41 +0100
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcyfRhBAAeUvsLhCRcif/cTxc76jiwAQO+xA
Message-ID: <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com>
In-Reply-To: <4EBB2563.5010302@cisco.com>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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: Thu, 10 Nov 2011 09:31:44 -0000

See inline...

> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]=20
> Sent: 2011. november 10. 2:14
> To: G=E1bor S=E1ndor Enyedi
> Cc: Andr=E1s Cs=E1sz=E1r; rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>=20
> On 09/11/2011 20:54, G=E1bor S=E1ndor Enyedi wrote:
> > Hi Steward,
> >
> >
> > That's forced first hop won't help; I can always add an extra node=20
> > against such tricks. :)
> >
> >          4       4
> >   [Src]-----[A]------[B]
> >      |                 |
> >     2|                 |1
> >      |                 |
> >     [C]-----[D]-----[Dest]
> >          1       3
> >
> > You cannot solve this without "directed forwarding" (forcing B with=20
> > some magic to forward packets to A instead of to Dest).=20
> Think on that=20
> > phenomenon like this: until you have only P chance to protect a=20
> > failure, protecting it in both directions will always be=20
> P*P<P until P<1. :)
> >
> >
> > Gabor
> >
> We would have solved that in the original tunnels draft with=20
> directed forwarding at B.
>=20
> However you have not answered my point that practical rings=20
> (as opposed to ring fragments in mesh topologies) normally=20
> have equal cost per hop.

Well, yes, you can of course substitute the above costs with hops, resultin=
g in a long cycle.
Then of course we can say that such long cycles normally don't exist.

But then, this brings back to question No 0. :-) Do we need a solution that=
 works in arbitrary cases?

One point I tried to have is that the normal coverage metrics used until no=
w (e.g. for LFA coverage tests) let things show up a little nicer than they=
 really are. I.e. coverage p vs p^2 as Gabor wrote.

We gave the operators one tool (LFA) already which they can try to switch o=
n but with which they cannot be sure if it really works or for which prefix=
es it actually work. We say instead, tune your network topology a little bi=
t, play with your link costs than you might get it to work better but even =
then it still might not work without getting close to full-mesh topo :-).

Do we want to give them yet-another tool with which they can again just hop=
e for "good luck" for their existing topologies and existing link metrics? =
(I know this is a little exaggerated...)


Andras



>=20
> Stewart
>=20
>=20
> > -----Original Message-----
> > From: rtgwg-bounces@ietf.org=20
> [mailto:rtgwg-bounces@ietf.org] On Behalf=20
> > Of Stewart Bryant
> > Sent: Wednesday, November 09, 2011 6:56 PM
> > To: Andr=E1s Cs=E1sz=E1r
> > Cc: rtgwg@ietf.org
> > Subject: Re: Charter Update (Discussion)
> >
> >
> > Hi Andr=E1s
> >
> > Yes, it is true that for that topology fragment there is no=20
> bidirectional LFA solution.
> >
> > However you were talking about rings, and surely it's=20
> unusual for a ring topology to have non-uniform costs.
> >
> > If we consider tunnel solution with forced first hop the=20
> solution would work.
> >
> > C tunnels to A with forced first hop (C-Dest), decap and A to Src.
> > Src LFAs to A, A sends to B, B sends to Dest
> >
> > - Stewart
> >
> > On 09/11/2011 10:59, Andr=E1s Cs=E1sz=E1r wrote:
> >> Hi Stewart, this phenomenon occurs with symmetric costs with LFA.
> >>
> >> Trying to sketch an example:
> >>
> >>          2        2
> >> [Src]-----[A]------[B]
> >>     |                 |
> >>    1|                 |1
> >>     |                 |
> >>    [C]-------------[Dest]
> >>             2
> >>
> >> Now for Src->Dest traffic, the link failure of Src-C can=20
> be remedied with LFA, as Src may pass the packet to A which=20
> is an LFA. For backwards traffic (e.g. TCP Acks) this link=20
> failure cannot be solved by C with LFA, so ultimately the=20
> Src-Dest traffic is screwed.
> >>
> >>
> >> Andr=E1s
> >>
> >>
> >>> -----Original Message-----
> >>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On=20
> >>> Behalf Of Stewart Bryant
> >>> Sent: 2011. november 8. 18:54
> >>> To: rtgwg@ietf.org
> >>> Subject: Re: Charter Update (Discussion)
> >>>
> >>> On 08/11/2011 17:20, Andr=E1s Cs=E1sz=E1r wrote:
> >>>> I think we should first see if there is a solution which
> >>> provides full coverage and practical (=3Dreasonable complexity).
> >>>> One problem with non-full-coverage solutions is
> >>> bidirectional coverage. I.e. even if a flow is covered=20
> for a failure=20
> >>> in one direction it may not be covered in the reverse direction=20
> >>> which is, for most applications, equal to not being=20
> covered at all.=20
> >>> This property is often neglected in coverage estimates. As an=20
> >>> example consider the LFA unfirendly sub-topologies like=20
> >>> longer-than-triangle rings. In those rings it might seem that the=20
> >>> failures on the opposing side to the exit point are=20
> covered by the=20
> >>> LFA. But they are not covered in the reverse direction.=20
> Might be a=20
> >>> factor to consider for PQ and co too.
> >>> Can you give me an example here?
> >>>
> >>> I would expect a ring to have symmetric properties except=20
> when there=20
> >>> are asymmetric costs, but normally assymetric costs are a=20
> >>> configuration accident.
> >>>
> >>> Stewart
> >>> _______________________________________________
> >>> rtgwg mailing list
> >>> rtgwg@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/rtgwg
> >>>
> >
> > --
> > For corporate legal information go to:
> >
> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> >
> >
> > _______________________________________________
> > rtgwg mailing list
> > rtgwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtgwg
> >
>=20
>=20
> --
> For corporate legal information go to:
>=20
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>=20
>=20
> =

From gabor.sandor.enyedi@ericsson.com  Thu Nov 10 02:11:25 2011
Return-Path: <gabor.sandor.enyedi@ericsson.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 9256921F8508 for <rtgwg@ietfa.amsl.com>; Thu, 10 Nov 2011 02:11:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QdN-X+Pwl+Hf for <rtgwg@ietfa.amsl.com>; Thu, 10 Nov 2011 02:11:24 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 6F0A221F8505 for <rtgwg@ietf.org>; Thu, 10 Nov 2011 02:11:24 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-66-4ebba34b3eb6
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id FC.62.09514.B43ABBE4; Thu, 10 Nov 2011 11:11:23 +0100 (CET)
Received: from ESESSCMS0359.eemea.ericsson.se ([169.254.1.79]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Thu, 10 Nov 2011 11:11:23 +0100
From: =?iso-8859-1?Q?G=E1bor_S=E1ndor_Enyedi?= <gabor.sandor.enyedi@ericsson.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Thu, 10 Nov 2011 11:11:21 +0100
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcyfRhMgwGVfi4kmSLCzYpYgLCDz8gASRVJQ
Message-ID: <EFAB865EBEFB734CA1FABD543B2E0E2E25147B77D3@ESESSCMS0359.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com>
In-Reply-To: <4EBB2563.5010302@cisco.com>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "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: Thu, 10 Nov 2011 10:11:25 -0000

This discussion on rings and costs is worthless: first, you cannot force a =
customer to use uniform link costs, so there will be such rings; second, An=
dr=E1s only showed you an example, but the phenomenon is not bounded to rin=
gs, you can find it in other networks as well.

Gabor

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]=20
Sent: Thursday, November 10, 2011 2:14 AM
To: G=E1bor S=E1ndor Enyedi
Cc: Andr=E1s Cs=E1sz=E1r; rtgwg@ietf.org
Subject: Re: Charter Update (Discussion)

On 09/11/2011 20:54, G=E1bor S=E1ndor Enyedi wrote:
> Hi Steward,
>
>
> That's forced first hop won't help; I can always add an extra node=20
> against such tricks. :)
>
>          4       4
>   [Src]-----[A]------[B]
>      |                 |
>     2|                 |1
>      |                 |
>     [C]-----[D]-----[Dest]
>          1       3
>
> You cannot solve this without "directed forwarding" (forcing B with=20
> some magic to forward packets to A instead of to Dest). Think on that=20
> phenomenon like this: until you have only P chance to protect a=20
> failure, protecting it in both directions will always be P*P<P until=20
> P<1. :)
>
>
> Gabor
>
We would have solved that in the original tunnels draft with directed forwa=
rding at B.

However you have not answered my point that practical rings (as opposed to =
ring fragments in mesh topologies) normally have equal cost per hop.

Stewart


> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf=20
> Of Stewart Bryant
> Sent: Wednesday, November 09, 2011 6:56 PM
> To: Andr=E1s Cs=E1sz=E1r
> Cc: rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>
>
> Hi Andr=E1s
>
> Yes, it is true that for that topology fragment there is no bidirectional=
 LFA solution.
>
> However you were talking about rings, and surely it's unusual for a ring =
topology to have non-uniform costs.
>
> If we consider tunnel solution with forced first hop the solution would w=
ork.
>
> C tunnels to A with forced first hop (C-Dest), decap and A to Src.
> Src LFAs to A, A sends to B, B sends to Dest
>
> - Stewart
>
> On 09/11/2011 10:59, Andr=E1s Cs=E1sz=E1r wrote:
>> Hi Stewart, this phenomenon occurs with symmetric costs with LFA.
>>
>> Trying to sketch an example:
>>
>>          2        2
>> [Src]-----[A]------[B]
>>     |                 |
>>    1|                 |1
>>     |                 |
>>    [C]-------------[Dest]
>>             2
>>
>> Now for Src->Dest traffic, the link failure of Src-C can be remedied wit=
h LFA, as Src may pass the packet to A which is an LFA. For backwards traff=
ic (e.g. TCP Acks) this link failure cannot be solved by C with LFA, so ult=
imately the Src-Dest traffic is screwed.
>>
>>
>> Andr=E1s
>>
>>
>>> -----Original Message-----
>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On=20
>>> Behalf Of Stewart Bryant
>>> Sent: 2011. november 8. 18:54
>>> To: rtgwg@ietf.org
>>> Subject: Re: Charter Update (Discussion)
>>>
>>> On 08/11/2011 17:20, Andr=E1s Cs=E1sz=E1r wrote:
>>>> I think we should first see if there is a solution which
>>> provides full coverage and practical (=3Dreasonable complexity).
>>>> One problem with non-full-coverage solutions is
>>> bidirectional coverage. I.e. even if a flow is covered for a failure=20
>>> in one direction it may not be covered in the reverse direction=20
>>> which is, for most applications, equal to not being covered at all.=20
>>> This property is often neglected in coverage estimates. As an=20
>>> example consider the LFA unfirendly sub-topologies like=20
>>> longer-than-triangle rings. In those rings it might seem that the=20
>>> failures on the opposing side to the exit point are covered by the=20
>>> LFA. But they are not covered in the reverse direction. Might be a=20
>>> factor to consider for PQ and co too.
>>> Can you give me an example here?
>>>
>>> I would expect a ring to have symmetric properties except when there=20
>>> are asymmetric costs, but normally assymetric costs are a=20
>>> configuration accident.
>>>
>>> Stewart
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>


--
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From ietf-ipr@ietf.org  Sun Nov 13 19:28:44 2011
Return-Path: <ietf-ipr@ietf.org>
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 547831F0CCE; Sun, 13 Nov 2011 19:28:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.411
X-Spam-Level: 
X-Spam-Status: No, score=-102.411 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kyvl2r5-CKNq; Sun, 13 Nov 2011 19:28:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6E1E1F0CC9; Sun, 13 Nov 2011 19:28:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: gchoudhury@att.com, dwfedyk@nortelnetworks.com, bimhoff@planetspork.com, chris@ipath.net, traveendra@huawei.com, azinin@cisco.com, 
Subject: IPR Disclosure: Telefonaktiebolaget LM Ericsson (publ)'s Statement about IPR related to RFC 5286
X-Test-IDTracker: no
Message-ID: <20111114032843.20907.52529.idtracker@ietfa.amsl.com>
Date: Sun, 13 Nov 2011 19:28:43 -0800
X-Mailman-Approved-At: Sun, 13 Nov 2011 21:12:30 -0800
Cc: adrian@olddog.co.uk, stbryant@cisco.com, ipr-announce@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, 14 Nov 2011 03:28:44 -0000

Dear G Choudhury, Don Fedyk, Brent Imhoff, Christian Martin, Raveendra Torv=
i, Alex Zinin:

 An IPR disclosure that pertains to your RFC entitled "Basic Specification =
for
IP Fast Reroute: Loop-Free Alternates" (RFC5286) was submitted to the IETF
Secretariat on 2011-11-13 and has been posted on the "IETF Page of Intellec=
tual
Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1650/). The =
title
of the IPR disclosure is "Telefonaktiebolaget LM Ericsson (publ)'s Statement
about IPR related to RFC 5286."");

The IETF Secretariat


From akatlas@gmail.com  Sun Nov 13 21:56:04 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 BF6A911E81F7 for <rtgwg@ietfa.amsl.com>; Sun, 13 Nov 2011 21:56:04 -0800 (PST)
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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dt+U1ae+jid2 for <rtgwg@ietfa.amsl.com>; Sun, 13 Nov 2011 21:56:04 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3783111E81F5 for <rtgwg@ietf.org>; Sun, 13 Nov 2011 21:56:04 -0800 (PST)
Received: by iaeo4 with SMTP id o4so8849848iae.31 for <rtgwg@ietf.org>; Sun, 13 Nov 2011 21:56:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=4/oaiTk0QeI+/o70mM/rHh77/rlPWDVGa5564BTmYXo=; b=MNMMP8ruh6M3tB80z+wPI6WffKXjFsWGlslMV84mol+8Ef1NuwBWPSOgdAsvoM574v NxBa85qbzYJmmboVy1weWl+AkK+NU+PUy+936v140mKP3pI6DQDHisd1NgZYF65fKPtY EsRh84z26/8/UcaShVVvJRNF7fzHAuqAfMTrw=
MIME-Version: 1.0
Received: by 10.50.100.232 with SMTP id fb8mr16183944igb.8.1321250163798; Sun, 13 Nov 2011 21:56:03 -0800 (PST)
Received: by 10.50.184.229 with HTTP; Sun, 13 Nov 2011 21:56:03 -0800 (PST)
Date: Mon, 14 Nov 2011 00:56:03 -0500
Message-ID: <CAG4d1reS8cJpty_r23v_FUO_cmwJzHiO-A79fGrij9P+kQVF3Q@mail.gmail.com>
Subject: volunteers for scribe?
From: Alia Atlas <akatlas@gmail.com>
To: rtgwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
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, 14 Nov 2011 05:56:04 -0000

It'd be good to have a volunteer or two for scribe before our meeting on Thurs.

Any volunteers before we have to waste time on this in the meeting?

Thanks,
Alia

From sriganeshkini@gmail.com  Tue Nov 15 13:37:33 2011
Return-Path: <sriganeshkini@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 3317F11E80B2 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 13:37:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.827
X-Spam-Level: 
X-Spam-Status: No, score=-2.827 tagged_above=-999 required=5 tests=[AWL=-0.149, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wkETC8SbCgpw for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 13:37:28 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7DA11E80BA for <rtgwg@ietf.org>; Tue, 15 Nov 2011 13:37:27 -0800 (PST)
Received: by wwe3 with SMTP id 3so326782wwe.1 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 13:37:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=10sbm+D6QEaQKGmSLnAlJYBEWR+FldcKBQmBWt5f8tc=; b=CyHzKOEMY6vkNgOtozAiEAjrfgokP8bb8uXaG0lM4FWHM4E8m1hX6RdLkEpIh/7txZ I0mG2Dl1H5a3Kg8IBbDMLn1juHKYf4YHJ4aT0EbJIrqT2txE0x1TfsZUM+RgvZ9p/tTU Of2NhRvZeggK9fTsqZ4JX+Fb8MOP5XBQYXqKw=
Received: by 10.227.199.200 with SMTP id et8mr16213493wbb.13.1321393046105; Tue, 15 Nov 2011 13:37:26 -0800 (PST)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.216.10.141 with HTTP; Tue, 15 Nov 2011 13:36:55 -0800 (PST)
In-Reply-To: <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Tue, 15 Nov 2011 13:36:55 -0800
X-Google-Sender-Auth: rjSYortTXXvw80qW_pxsu3ulKr8
Message-ID: <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com>
Subject: Re: Charter Update (Discussion)
To: =?UTF-8?B?QW5kcsOhcyBDc8Ohc3rDoXI=?= <Andras.Csaszar@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.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: Tue, 15 Nov 2011 21:37:33 -0000

Hi,

I agree that having a solution with full coverage is very useful
because it removes the need for complicated analysis to determine what
is protected versus what is not (and worse, how that changes as the
topology change). But the solution has to be simple for it to get
deployed.

One approach using MPLS that solves this using extensions to a single
protocol (LDP) is given in draft-kini-mpls-frr-ldp.

2011/11/10 Andr=C3=A1s Cs=C3=A1sz=C3=A1r <Andras.Csaszar@ericsson.com>:
> See inline...
>
>> -----Original Message-----
>> From: Stewart Bryant [mailto:stbryant@cisco.com]
>> Sent: 2011. november 10. 2:14
>> To: G=C3=A1bor S=C3=A1ndor Enyedi
>> Cc: Andr=C3=A1s Cs=C3=A1sz=C3=A1r; rtgwg@ietf.org
>> Subject: Re: Charter Update (Discussion)
>>
>> On 09/11/2011 20:54, G=C3=A1bor S=C3=A1ndor Enyedi wrote:
>> > Hi Steward,
>> >
>> >
>> > That's forced first hop won't help; I can always add an extra node
>> > against such tricks. :)
>> >
>> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A04 =C2=A0 =C2=A0 =C2=A0 4
>> > =C2=A0 [Src]-----[A]------[B]
>> > =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 |
>> > =C2=A0 =C2=A0 2| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |1
>> > =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 |
>> > =C2=A0 =C2=A0 [C]-----[D]-----[Dest]
>> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01 =C2=A0 =C2=A0 =C2=A0 3
>> >
>> > You cannot solve this without "directed forwarding" (forcing B with
>> > some magic to forward packets to A instead of to Dest).
>> Think on that
>> > phenomenon like this: until you have only P chance to protect a
>> > failure, protecting it in both directions will always be
>> P*P<P until P<1. :)
>> >
>> >
>> > Gabor
>> >
>> We would have solved that in the original tunnels draft with
>> directed forwarding at B.
>>
>> However you have not answered my point that practical rings
>> (as opposed to ring fragments in mesh topologies) normally
>> have equal cost per hop.
>
> Well, yes, you can of course substitute the above costs with hops, result=
ing in a long cycle.
> Then of course we can say that such long cycles normally don't exist.
>
> But then, this brings back to question No 0. :-) Do we need a solution th=
at works in arbitrary cases?
>
> One point I tried to have is that the normal coverage metrics used until =
now (e.g. for LFA coverage tests) let things show up a little nicer than th=
ey really are. I.e. coverage p vs p^2 as Gabor wrote.
>
> We gave the operators one tool (LFA) already which they can try to switch=
 on but with which they cannot be sure if it really works or for which pref=
ixes it actually work. We say instead, tune your network topology a little =
bit, play with your link costs than you might get it to work better but eve=
n then it still might not work without getting close to full-mesh topo :-).
>
> Do we want to give them yet-another tool with which they can again just h=
ope for "good luck" for their existing topologies and existing link metrics=
? (I know this is a little exaggerated...)
>
>
> Andras
>
>
>
>>
>> Stewart
>>
>>
>> > -----Original Message-----
>> > From: rtgwg-bounces@ietf.org
>> [mailto:rtgwg-bounces@ietf.org] On Behalf
>> > Of Stewart Bryant
>> > Sent: Wednesday, November 09, 2011 6:56 PM
>> > To: Andr=C3=A1s Cs=C3=A1sz=C3=A1r
>> > Cc: rtgwg@ietf.org
>> > Subject: Re: Charter Update (Discussion)
>> >
>> >
>> > Hi Andr=C3=A1s
>> >
>> > Yes, it is true that for that topology fragment there is no
>> bidirectional LFA solution.
>> >
>> > However you were talking about rings, and surely it's
>> unusual for a ring topology to have non-uniform costs.
>> >
>> > If we consider tunnel solution with forced first hop the
>> solution would work.
>> >
>> > C tunnels to A with forced first hop (C-Dest), decap and A to Src.
>> > Src LFAs to A, A sends to B, B sends to Dest
>> >
>> > - Stewart
>> >
>> > On 09/11/2011 10:59, Andr=C3=A1s Cs=C3=A1sz=C3=A1r wrote:
>> >> Hi Stewart, this phenomenon occurs with symmetric costs with LFA.
>> >>
>> >> Trying to sketch an example:
>> >>
>> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A02 =C2=A0 =C2=A0 =C2=A0 =C2=A02
>> >> [Src]-----[A]------[B]
>> >> =C2=A0 =C2=A0 | =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |
>> >> =C2=A0 =C2=A01| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |1
>> >> =C2=A0 =C2=A0 | =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |
>> >> =C2=A0 =C2=A0[C]-------------[Dest]
>> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 2
>> >>
>> >> Now for Src->Dest traffic, the link failure of Src-C can
>> be remedied with LFA, as Src may pass the packet to A which
>> is an LFA. For backwards traffic (e.g. TCP Acks) this link
>> failure cannot be solved by C with LFA, so ultimately the
>> Src-Dest traffic is screwed.
>> >>
>> >>
>> >> Andr=C3=A1s
>> >>
>> >>
>> >>> -----Original Message-----
>> >>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On
>> >>> Behalf Of Stewart Bryant
>> >>> Sent: 2011. november 8. 18:54
>> >>> To: rtgwg@ietf.org
>> >>> Subject: Re: Charter Update (Discussion)
>> >>>
>> >>> On 08/11/2011 17:20, Andr=C3=A1s Cs=C3=A1sz=C3=A1r wrote:
>> >>>> I think we should first see if there is a solution which
>> >>> provides full coverage and practical (=3Dreasonable complexity).
>> >>>> One problem with non-full-coverage solutions is
>> >>> bidirectional coverage. I.e. even if a flow is covered
>> for a failure
>> >>> in one direction it may not be covered in the reverse direction
>> >>> which is, for most applications, equal to not being
>> covered at all.
>> >>> This property is often neglected in coverage estimates. As an
>> >>> example consider the LFA unfirendly sub-topologies like
>> >>> longer-than-triangle rings. In those rings it might seem that the
>> >>> failures on the opposing side to the exit point are
>> covered by the
>> >>> LFA. But they are not covered in the reverse direction.
>> Might be a
>> >>> factor to consider for PQ and co too.
>> >>> Can you give me an example here?
>> >>>
>> >>> I would expect a ring to have symmetric properties except
>> when there
>> >>> are asymmetric costs, but normally assymetric costs are a
>> >>> configuration accident.
>> >>>
>> >>> Stewart
>> >>> _______________________________________________
>> >>> rtgwg mailing list
>> >>> rtgwg@ietf.org
>> >>> https://www.ietf.org/mailman/listinfo/rtgwg
>> >>>
>> >
>> > --
>> > For corporate legal information go to:
>> >
>> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>> >
>> >
>> > _______________________________________________
>> > rtgwg mailing list
>> > rtgwg@ietf.org
>> > https://www.ietf.org/mailman/listinfo/rtgwg
>> >
>>
>>
>> --
>> For corporate legal information go to:
>>
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>
>>
>>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>



--=20
- Sri

From stbryant@cisco.com  Tue Nov 15 14:14:15 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 1586221F8573 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 14:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.261
X-Spam-Level: 
X-Spam-Status: No, score=-109.261 tagged_above=-999 required=5 tests=[AWL=1.338, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GgHwgndc-8mE for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 14:14:11 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id BD3F011E8099 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 14:14:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=537; q=dns/txt; s=iport; t=1321395250; x=1322604850; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=qHFfOIqjl8wHtBMvUKXO1CDW5I9Gib7jlzlu1JhiLp8=; b=hF+rImwOQrglT30BXxkmBU0VzJC20Ug/N2cqEBssaiqQYwJbidqbZCfL TUJL5152jqVK+otA3bvlvTMwX36aA7ET6Vc2UxXjCJzTKY/xrGH5pR83/ c8qz3XmXSUEr5//NL/Qo1gBPiXAbLaaSl05WheNM6Zm+WV8YhERjCfBPa Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqcFAGTjwk6Q/khR/2dsb2JhbABChQGiSYIkgQWBcgEBAQQSAQIBDRVAARALGAICBRYLAgIJAwIBAgFFBg0BBwEBFweiBgGDLg8BiRuRd4Ewh0uBFgSUMpF6
X-IronPort-AV: E=Sophos;i="4.69,517,1315180800"; d="scan'208";a="121700106"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 15 Nov 2011 22:14:09 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAFME9Oe025035; Tue, 15 Nov 2011 22:14:09 GMT
Received: from dhcp-40a3.meeting.ietf.org (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id pAFME5JT017578; Tue, 15 Nov 2011 22:14:07 GMT
Message-ID: <4EC2E42D.2010403@cisco.com>
Date: Tue, 15 Nov 2011 22:14:05 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Sriganesh Kini <sriganesh.kini@ericsson.com>
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com>
In-Reply-To: <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
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: Tue, 15 Nov 2011 22:14:15 -0000

On 15/11/2011 21:36, Sriganesh Kini wrote:
> Hi,
>
> I agree that having a solution with full coverage is very useful
> because it removes the need for complicated analysis to determine what
> is protected versus what is not (and worse, how that changes as the
> topology change). But the solution has to be simple for it to get
> deployed.
>
> One approach using MPLS that solves this using extensions to a single
> protocol (LDP) is given in draft-kini-mpls-frr-ldp.
It the approach extensible to an IP context?

Stewart



From sriganeshkini@gmail.com  Tue Nov 15 14:30:29 2011
Return-Path: <sriganeshkini@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 8CC3411E80DD for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 14:30:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.927
X-Spam-Level: 
X-Spam-Status: No, score=-2.927 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5aNmmikBcVsF for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 14:30:25 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3904C11E80CC for <rtgwg@ietf.org>; Tue, 15 Nov 2011 14:30:25 -0800 (PST)
Received: by wwe3 with SMTP id 3so390807wwe.1 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 14:30:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=LM2VkBtX2Ur44Y5Tu+nMVZwHhg7PkLE7klzwDCqUwWg=; b=GrbhTpSwgiecKuEeE/S1kM9Nui4E5cpAYyGYqXIVhfIH5+WatG848De6jlwkL4ajqn 9hyB3HakEZS+1OxQmqKFJn/GzBP6OPF3fnMDHxxsnBFvhwd3oACjHenPQkoOEU5u5Hru TbM59L9xa3EqxN+oLT4I4RxyUyrrxe+V3T8RA=
Received: by 10.216.163.194 with SMTP id a44mr5058285wel.1.1321396223166; Tue, 15 Nov 2011 14:30:23 -0800 (PST)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.216.10.141 with HTTP; Tue, 15 Nov 2011 14:29:52 -0800 (PST)
In-Reply-To: <4EC2E42D.2010403@cisco.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFB28@ESESSCMS0363.eemea.ericsson.se> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Tue, 15 Nov 2011 14:29:52 -0800
X-Google-Sender-Auth: wC5pS2wZYr6NAq0LOrndTPH2XXY
Message-ID: <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com>
Subject: Re: Charter Update (Discussion)
To: stbryant@cisco.com
Content-Type: text/plain; charset=UTF-8
Cc: "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: Tue, 15 Nov 2011 22:30:29 -0000

IP is addressed via MPLS. If IP forwarding were to be used
exclusively, then it becomes complicated. With MPLS being extended to
more parts of the network than just the core, it seems that is not as
much of a concern.

On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant <stbryant@cisco.com> wrote:
> On 15/11/2011 21:36, Sriganesh Kini wrote:
>>
>> Hi,
>>
>> I agree that having a solution with full coverage is very useful
>> because it removes the need for complicated analysis to determine what
>> is protected versus what is not (and worse, how that changes as the
>> topology change). But the solution has to be simple for it to get
>> deployed.
>>
>> One approach using MPLS that solves this using extensions to a single
>> protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>
> It the approach extensible to an IP context?
>
> Stewart
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>



-- 
- Sri

From stbryant@cisco.com  Tue Nov 15 15:08: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 C19681F0C68 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 15:08:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.292
X-Spam-Level: 
X-Spam-Status: No, score=-109.292 tagged_above=-999 required=5 tests=[AWL=1.307, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ajmzTItNBLmn for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 15:08:40 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB851F0C55 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 15:08:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=1581; q=dns/txt; s=iport; t=1321398520; x=1322608120; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=vCNy3LHKlp6MV7FhMtyR2oglmT3OrGEznIspMiqpGfU=; b=diwRV8qrCen3bmOSNp0f2aZuxiqoCziQvWklat5KDOv1oSHl4Hka8ss+ kc6+RCslBDDl1iBqxhz4/EjDAM+ChIe1Od977Gxnd9udEQTYOx7IPotT+ DaCZJZyRMZ4SqSUFsJQ4O/nR4g/jGWJO8iGsfkCsO8PlMCzDysR9S4RUJ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAOLvwk6Q/khN/2dsb2JhbABDhQGkcIEFgXIBAQEEAQEBDwECAQ0VNgoBEAsYAgIFFgsCAgkDAgECARUwBg0BBQIBARcHh2iaIwGDLg8BiRuRd4Ewh0uBFgSUMpF6
X-IronPort-AV: E=Sophos;i="4.69,517,1315180800"; d="scan'208";a="59930748"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 15 Nov 2011 23:08:39 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAFN8c2K012144; Tue, 15 Nov 2011 23:08:38 GMT
Received: from dhcp-40a3.meeting.ietf.org (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id pAFN8ZDa019969; Tue, 15 Nov 2011 23:08:36 GMT
Message-ID: <4EC2F0F2.5010400@cisco.com>
Date: Tue, 15 Nov 2011 23:08:34 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Sriganesh Kini <sriganesh.kini@ericsson.com>
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com>
In-Reply-To: <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
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: Tue, 15 Nov 2011 23:08:40 -0000

Unfortunately whether MPLS is used in a particular
network segment or not is a complex and sometimes
emotive issue.

If we decide that the best solution is to use MPLS
we then face the issue of what to do about networks
that decline to support MPLS. Do we declare
non-MPLS networks out of scope for IPFRR, or do
we work on another non-MPLS solution?

- Stewart


On 15/11/2011 22:29, Sriganesh Kini wrote:
> IP is addressed via MPLS. If IP forwarding were to be used
> exclusively, then it becomes complicated. With MPLS being extended to
> more parts of the network than just the core, it seems that is not as
> much of a concern.
>
> On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>  wrote:
>> On 15/11/2011 21:36, Sriganesh Kini wrote:
>>> Hi,
>>>
>>> I agree that having a solution with full coverage is very useful
>>> because it removes the need for complicated analysis to determine what
>>> is protected versus what is not (and worse, how that changes as the
>>> topology change). But the solution has to be simple for it to get
>>> deployed.
>>>
>>> One approach using MPLS that solves this using extensions to a single
>>> protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>> It the approach extensible to an IP context?
>>
>> Stewart
>>
>>
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>>
>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From eosborne@cisco.com  Tue Nov 15 16:20:19 2011
Return-Path: <eosborne@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 C78B321F8AEE for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 16:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X81Ze-F-pnUS for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 16:20:19 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id F0D6E21F8AE1 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 16:20:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eosborne@cisco.com; l=2345; q=dns/txt; s=iport; t=1321402819; x=1322612419; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=o0KOX3N4PNswts5SXOv+3pcAEYzxj7j1sFPXHkJVpSU=; b=Sd1mv6V862y5/gfx0IODCJg2JWNlBbt1Un+ZqVNNphVvF6en4gcTBscJ kkhRFQbcyiwxNE0K1hoQMO/7efAbkq5PdaCrCxWIsDuMDQwmTYfYi3yx8 p+5HlNOnh37XbBwiNV0/7Wg3LyjEhLOBPt3dQepR0UBlhgIUOaq+haTxZ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwAAGMBw06tJXG+/2dsb2JhbABDmWqQCIEFgXIBAQEEAQEBDwEdCjQLDAQCAQgRBAEBAQoGFwEGASYfCQgBAQQBEggTB4domjkBnlCJLmMEiBORY4xV
X-IronPort-AV: E=Sophos;i="4.69,517,1315180800"; d="scan'208";a="36338734"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-8.cisco.com with ESMTP; 16 Nov 2011 00:20:18 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAG0KICS031260;  Wed, 16 Nov 2011 00:20:18 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Nov 2011 18:20:18 -0600
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: Charter Update (Discussion)
Date: Tue, 15 Nov 2011 18:20:15 -0600
Message-ID: <D29E470202D67745B61059870F433B54079CCF59@XMB-RCD-202.cisco.com>
In-Reply-To: <4EC2F0F2.5010400@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Charter Update (Discussion)
Thread-Index: Acyj64X5WWaPQoBdSpGnv6FxRg7qiQACdSKQ
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net><8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se><7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu><CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com><4EB81CAD.4080402@googlemail.com><CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com><8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se><4EB96CBF.7040501@cisco.com><8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se><4EBABECC.2060701@cisco.com><EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se><4EBB2563.5010302@cisco.com><8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se><CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com><4EC2E42D.2010403@cisco.com><CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>, "Sriganesh Kini" <sriganesh.kini@ericsson.com>
X-OriginalArrivalTime: 16 Nov 2011 00:20:18.0473 (UTC) FILETIME=[853F3990:01CCA3F5]
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: Wed, 16 Nov 2011 00:20:19 -0000

> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
> Of Stewart Bryant (stbryant)
> Sent: Wednesday, November 16, 2011 7:09 AM
> To: Sriganesh Kini
> Cc: rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>=20
>=20
> Unfortunately whether MPLS is used in a particular network segment or
not
> is a complex and sometimes emotive issue.
>=20
> If we decide that the best solution is to use MPLS we then face the
issue of
> what to do about networks that decline to support MPLS. Do we declare
> non-MPLS networks out of scope for IPFRR, or do we work on another
non-
> MPLS solution?

I think you also have to wrestle with the opposite problem.  If you
declare that convergence schemes which require MPLS to provide 100%
coverage are within scope, what exactly is out of scope? =20



eric

>=20
> - Stewart
>=20
>=20
> On 15/11/2011 22:29, Sriganesh Kini wrote:
> > IP is addressed via MPLS. If IP forwarding were to be used
> > exclusively, then it becomes complicated. With MPLS being extended
to
> > more parts of the network than just the core, it seems that is not
as
> > much of a concern.
> >
> > On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>
> wrote:
> >> On 15/11/2011 21:36, Sriganesh Kini wrote:
> >>> Hi,
> >>>
> >>> I agree that having a solution with full coverage is very useful
> >>> because it removes the need for complicated analysis to determine
> >>> what is protected versus what is not (and worse, how that changes
as
> >>> the topology change). But the solution has to be simple for it to
> >>> get deployed.
> >>>
> >>> One approach using MPLS that solves this using extensions to a
> >>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
> >> It the approach extensible to an IP context?
> >>
> >> Stewart
> >>
> >>
> >> _______________________________________________
> >> rtgwg mailing list
> >> rtgwg@ietf.org
> >> https://www.ietf.org/mailman/listinfo/rtgwg
> >>
> >
> >
>=20
>=20
> --
> For corporate legal information go to:
>=20
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>=20
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

From jeff.tantsura@ericsson.com  Tue Nov 15 18:24:48 2011
Return-Path: <jeff.tantsura@ericsson.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 DE90E11E81A9 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 18:24:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id heakXC8ArMdi for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 18:24:44 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5FFEB21F8E6A for <rtgwg@ietf.org>; Tue, 15 Nov 2011 18:24:44 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pAG2OhSH024788 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 15 Nov 2011 20:24:43 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.111]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 15 Nov 2011 21:24:42 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>
Date: Tue, 15 Nov 2011 21:24:46 -0500
Subject: Re: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcykBuXE98Q3WSHXSY6gVcmDb87l0w==
Message-ID: <C24D3780-4028-4959-9688-3468105650C1@ericsson.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <D29E470202D67745B61059870F433B54079CCF59@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B54079CCF59@XMB-RCD-202.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, Sriganesh Kini <sriganesh.kini@ericsson.com>, "Stewart Bryant \(stbryant\)" <stbryant@cisco.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: Wed, 16 Nov 2011 02:24:49 -0000

I believe we are looking for a solution providing 100% coverage for both IP=
 only and IP/MPLS networks with emphasis on full coverage.


Regards,
Jeff

On Nov 16, 2011, at 8:20 AM, "Eric Osborne (eosborne)" <eosborne@cisco.com>=
 wrote:

>=20
>=20
>> -----Original Message-----
>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
>> Of Stewart Bryant (stbryant)
>> Sent: Wednesday, November 16, 2011 7:09 AM
>> To: Sriganesh Kini
>> Cc: rtgwg@ietf.org
>> Subject: Re: Charter Update (Discussion)
>>=20
>>=20
>> Unfortunately whether MPLS is used in a particular network segment or
> not
>> is a complex and sometimes emotive issue.
>>=20
>> If we decide that the best solution is to use MPLS we then face the
> issue of
>> what to do about networks that decline to support MPLS. Do we declare
>> non-MPLS networks out of scope for IPFRR, or do we work on another
> non-
>> MPLS solution?
>=20
> I think you also have to wrestle with the opposite problem.  If you
> declare that convergence schemes which require MPLS to provide 100%
> coverage are within scope, what exactly is out of scope? =20
>=20
>=20
>=20
> eric
>=20
>>=20
>> - Stewart
>>=20
>>=20
>> On 15/11/2011 22:29, Sriganesh Kini wrote:
>>> IP is addressed via MPLS. If IP forwarding were to be used
>>> exclusively, then it becomes complicated. With MPLS being extended
> to
>>> more parts of the network than just the core, it seems that is not
> as
>>> much of a concern.
>>>=20
>>> On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>
>> wrote:
>>>> On 15/11/2011 21:36, Sriganesh Kini wrote:
>>>>> Hi,
>>>>>=20
>>>>> I agree that having a solution with full coverage is very useful
>>>>> because it removes the need for complicated analysis to determine
>>>>> what is protected versus what is not (and worse, how that changes
> as
>>>>> the topology change). But the solution has to be simple for it to
>>>>> get deployed.
>>>>>=20
>>>>> One approach using MPLS that solves this using extensions to a
>>>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>>>> It the approach extensible to an IP context?
>>>>=20
>>>> Stewart
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> rtgwg mailing list
>>>> rtgwg@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>>=20
>>>=20
>>>=20
>>=20
>>=20
>> --
>> For corporate legal information go to:
>>=20
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>=20
>>=20
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

From stbryant@cisco.com  Tue Nov 15 18:28:57 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 707AD11E81BE for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 18:28:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.322
X-Spam-Level: 
X-Spam-Status: No, score=-107.322 tagged_above=-999 required=5 tests=[AWL=-0.723, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T91ji05yvo9h for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 18:28:53 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id DA86011E818F for <rtgwg@ietf.org>; Tue, 15 Nov 2011 18:28:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=3056; q=dns/txt; s=iport; t=1321410533; x=1322620133; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=6AY0hKamEiRz65q7TeP2bknydb8zgh6hIsKqxJCTXy0=; b=mTKJpmJ9HHhA75harCo0iR5+7qgjxIazIMaUIrdsMdj9GASzbeU2t1CC 1tkOglw6Bhj0+3HcM3CiNG7DBzfRh0E9C84saMaD8+fjY8ZEV2lBhVOUe AR+qswCqyRd1xa06/GJRIRD0eYdCM2TXMSsSHCr4Kb2ChJ68arYLyAhiv Y=;
X-IronPort-AV: E=Sophos;i="4.69,518,1315180800";  d="scan'208";a="3162208"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-4.cisco.com with ESMTP; 16 Nov 2011 02:28:52 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAG2SqN6005799; Wed, 16 Nov 2011 02:28:52 GMT
Received: from dhcp-1222.meeting.ietf.org (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id pAG2SmvQ026625; Wed, 16 Nov 2011 02:28:49 GMT
Message-ID: <4EC31FDF.2070205@cisco.com>
Date: Wed, 16 Nov 2011 02:28:47 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Jeff Tantsura <jeff.tantsura@ericsson.com>
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <D29E470202D67745B61059870F433B54079CCF59@XMB-RCD-202.cisco.com> <C24D3780-4028-4959-9688-3468105650C1@ericsson.com>
In-Reply-To: <C24D3780-4028-4959-9688-3468105650C1@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, Sriganesh Kini <sriganesh.kini@ericsson.com>
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, 16 Nov 2011 02:28:57 -0000

... in which case we have to be careful not to force MPLS

Stewart

On 16/11/2011 02:24, Jeff Tantsura wrote:
> I believe we are looking for a solution providing 100% coverage for both IP only and IP/MPLS networks with emphasis on full coverage.
>
>
> Regards,
> Jeff
>
> On Nov 16, 2011, at 8:20 AM, "Eric Osborne (eosborne)"<eosborne@cisco.com>  wrote:
>
>>
>>> -----Original Message-----
>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
>>> Of Stewart Bryant (stbryant)
>>> Sent: Wednesday, November 16, 2011 7:09 AM
>>> To: Sriganesh Kini
>>> Cc: rtgwg@ietf.org
>>> Subject: Re: Charter Update (Discussion)
>>>
>>>
>>> Unfortunately whether MPLS is used in a particular network segment or
>> not
>>> is a complex and sometimes emotive issue.
>>>
>>> If we decide that the best solution is to use MPLS we then face the
>> issue of
>>> what to do about networks that decline to support MPLS. Do we declare
>>> non-MPLS networks out of scope for IPFRR, or do we work on another
>> non-
>>> MPLS solution?
>> I think you also have to wrestle with the opposite problem.  If you
>> declare that convergence schemes which require MPLS to provide 100%
>> coverage are within scope, what exactly is out of scope?
>>
>>
>>
>> eric
>>
>>> - Stewart
>>>
>>>
>>> On 15/11/2011 22:29, Sriganesh Kini wrote:
>>>> IP is addressed via MPLS. If IP forwarding were to be used
>>>> exclusively, then it becomes complicated. With MPLS being extended
>> to
>>>> more parts of the network than just the core, it seems that is not
>> as
>>>> much of a concern.
>>>>
>>>> On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>
>>> wrote:
>>>>> On 15/11/2011 21:36, Sriganesh Kini wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I agree that having a solution with full coverage is very useful
>>>>>> because it removes the need for complicated analysis to determine
>>>>>> what is protected versus what is not (and worse, how that changes
>> as
>>>>>> the topology change). But the solution has to be simple for it to
>>>>>> get deployed.
>>>>>>
>>>>>> One approach using MPLS that solves this using extensions to a
>>>>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>>>>> It the approach extensible to an IP context?
>>>>>
>>>>> Stewart
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> rtgwg mailing list
>>>>> rtgwg@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>>>
>>>>
>>>
>>> --
>>> For corporate legal information go to:
>>>
>>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>>
>>>
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From sriganeshkini@gmail.com  Tue Nov 15 19:11:48 2011
Return-Path: <sriganeshkini@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 1EF0C21F9038 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 19:11:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.939
X-Spam-Level: 
X-Spam-Status: No, score=-2.939 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8UAdk9iaVbSu for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 19:11:44 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id D338421F9032 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 19:11:43 -0800 (PST)
Received: by wwe5 with SMTP id 5so5224599wwe.13 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 19:11:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=hAO3Tm8WyVhYFDKBcKuZCJIWxcJhqwi0FB3yehg3jAA=; b=E0T/b9hRXrDks9d3zTxO3szJ2/h1TPCNvGnoOh2rxQ2q6/FzOvh++z3JdsHerBwlX9 CYdaL/MVR0o3CllQrF0Pc2DsXywzU4ek7jY6SnXm7LU2RrG9QTFGP0oUdJbGM5BTcU1p 3mWcMy5tA1PokZZwaNpi576CEkvnDJuZQMgCw=
Received: by 10.216.177.134 with SMTP id d6mr2521606wem.16.1321413101307; Tue, 15 Nov 2011 19:11:41 -0800 (PST)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.216.10.141 with HTTP; Tue, 15 Nov 2011 19:11:10 -0800 (PST)
In-Reply-To: <4EC2F0F2.5010400@cisco.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Wed, 16 Nov 2011 11:11:10 +0800
X-Google-Sender-Auth: riwzU_75bAZPZM6hWT6SDKiU64k
Message-ID: <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTdXKUckads5aTshwQ@mail.gmail.com>
Subject: Re: Charter Update (Discussion)
To: "stbryant@cisco.com" <stbryant@cisco.com>
Content-Type: text/plain; charset=UTF-8
Cc: "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: Wed, 16 Nov 2011 03:11:48 -0000

Solutions that use exclusively IP have been seen to run the risk of
issues such as incomplete coverage or complexity (or both), ...etc.
Networks that decline to support MPLS would be similarly affected.
Solutions that use MPLS and have full coverage and are deployable seem
possible. If we declare non-MPLS(read as IP) networks out of scope of
IPFRR that would be quite confusing :-). IMO there is value in an IP
only solution that is simple and has full coverage. If there isn't one
then MPLS based solutions seem a better option.

On Tue, Nov 15, 2011 at 3:08 PM, Stewart Bryant <stbryant@cisco.com> wrote:
>
> Unfortunately whether MPLS is used in a particular
> network segment or not is a complex and sometimes
> emotive issue.
>
> If we decide that the best solution is to use MPLS
> we then face the issue of what to do about networks
> that decline to support MPLS. Do we declare
> non-MPLS networks out of scope for IPFRR, or do
> we work on another non-MPLS solution?
>
> - Stewart
>
>
> On 15/11/2011 22:29, Sriganesh Kini wrote:
>>
>> IP is addressed via MPLS. If IP forwarding were to be used
>> exclusively, then it becomes complicated. With MPLS being extended to
>> more parts of the network than just the core, it seems that is not as
>> much of a concern.
>>
>> On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>
>>  wrote:
>>>
>>> On 15/11/2011 21:36, Sriganesh Kini wrote:
>>>>
>>>> Hi,
>>>>
>>>> I agree that having a solution with full coverage is very useful
>>>> because it removes the need for complicated analysis to determine what
>>>> is protected versus what is not (and worse, how that changes as the
>>>> topology change). But the solution has to be simple for it to get
>>>> deployed.
>>>>
>>>> One approach using MPLS that solves this using extensions to a single
>>>> protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>>>
>>> It the approach extensible to an IP context?
>>>
>>> Stewart
>>>
>>>
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>
>>
>>
>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>



-- 
- Sri

From eosborne@cisco.com  Tue Nov 15 19:27:26 2011
Return-Path: <eosborne@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 C3ACA11E80A6 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 19:27:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6qVW4gy1k-aS for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 19:27:22 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 74FEB11E80F1 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 19:27:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eosborne@cisco.com; l=3636; q=dns/txt; s=iport; t=1321414042; x=1322623642; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=dF8Ej3wziNYMxgFBE855LMFYFaUECzFpsgt475a9du8=; b=RWXI6eIZ1hXrgxXWw9TGZlVhaQiqaO1No1d82BpCIawIrWGTj0d+GQH1 iY/HirOHndG+fbH49RlUHsBdR51XVpwXFixcTIyWILwJncNG/fyUsd7j3 ULZzZ/8UHnhDFzQkeQ26fqjBzcJn7RCjhnl2nNOYfzXlF1Nv+0B4NxOQa k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnsAAMYsw06tJXG//2dsb2JhbABDmWqQCIEFgXIBAQEDAQEBAQ8BHQo0CwUHBAIBCBEEAQEBCgYXAQYBJh8JCAEBBAESCBMHh2AImjoBnlmJNGMEiBSRZIxX
X-IronPort-AV: E=Sophos;i="4.69,518,1315180800"; d="scan'208";a="36395938"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-1.cisco.com with ESMTP; 16 Nov 2011 03:27:21 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAG3RKqO027163;  Wed, 16 Nov 2011 03:27:20 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Nov 2011 21:27:20 -0600
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: Charter Update (Discussion)
Date: Tue, 15 Nov 2011 21:27:17 -0600
Message-ID: <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com>
In-Reply-To: <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTdXKUckads5aTshwQ@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcykDXxUlX7fbDtCS/W+exa4MEDBsAAAbAtQ
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net><8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se><7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu><CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com><4EB81CAD.4080402@googlemail.com><CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com><8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se><4EB96CBF.7040501@cisco.com><8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se><4EBABECC.2060701@cisco.com><EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se><4EBB2563.5010302@cisco.com><8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se><CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com><4EC2E42D.2010403@cisco.com><CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com><4EC2F0F2.5010400@cisco.com> <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJT dXKUckad s5aTshwQ@mail.gmail.com>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Sriganesh Kini" <sriganesh.kini@ericsson.com>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>
X-OriginalArrivalTime: 16 Nov 2011 03:27:20.0530 (UTC) FILETIME=[A61D3B20:01CCA40F]
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: Wed, 16 Nov 2011 03:27:26 -0000

> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
> Of Sriganesh Kini
> Sent: Wednesday, November 16, 2011 11:11 AM
> To: Stewart Bryant (stbryant)
> Cc: rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>=20
> Solutions that use exclusively IP have been seen to run the risk of
issues such
> as incomplete coverage or complexity (or both), ...etc.
> Networks that decline to support MPLS would be similarly affected.
> Solutions that use MPLS and have full coverage and are deployable seem
> possible. If we declare non-MPLS(read as IP) networks out of scope of
IPFRR
> that would be quite confusing :-).

Perhaps...but so would declaring that 'IPFRR' contained MPLS.  I always
looked looked at it as:

- first we had MPLS FRR, which we just called FRR.
- then, for those that were not interested in MPLS FRR, IPFRR was
introduced.  Implicitly the name 'IPFRR' excludes MPLS.

To now redefine IPFRR to say that the 'IP' part refers to client traffic
rather than the forwarding technology which builds your protection is
revisionist and probably contentious.

> IMO there is value in an IP only solution
> that is simple and has full coverage. If there isn't one then MPLS
based
> solutions seem a better option.
>=20

But we're not debating value of various solutions, we're debating
charter and thus where those solutions come from.



eric


> On Tue, Nov 15, 2011 at 3:08 PM, Stewart Bryant <stbryant@cisco.com>
> wrote:
> >
> > Unfortunately whether MPLS is used in a particular network segment
or
> > not is a complex and sometimes emotive issue.
> >
> > If we decide that the best solution is to use MPLS we then face the
> > issue of what to do about networks that decline to support MPLS. Do
we
> > declare non-MPLS networks out of scope for IPFRR, or do we work on
> > another non-MPLS solution?
> >
> > - Stewart
> >
> >
> > On 15/11/2011 22:29, Sriganesh Kini wrote:
> >>
> >> IP is addressed via MPLS. If IP forwarding were to be used
> >> exclusively, then it becomes complicated. With MPLS being extended
to
> >> more parts of the network than just the core, it seems that is not
as
> >> much of a concern.
> >>
> >> On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>
> >>  wrote:
> >>>
> >>> On 15/11/2011 21:36, Sriganesh Kini wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I agree that having a solution with full coverage is very useful
> >>>> because it removes the need for complicated analysis to determine
> >>>> what is protected versus what is not (and worse, how that changes
> >>>> as the topology change). But the solution has to be simple for it
> >>>> to get deployed.
> >>>>
> >>>> One approach using MPLS that solves this using extensions to a
> >>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
> >>>
> >>> It the approach extensible to an IP context?
> >>>
> >>> Stewart
> >>>
> >>>
> >>> _______________________________________________
> >>> rtgwg mailing list
> >>> rtgwg@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/rtgwg
> >>>
> >>
> >>
> >
> >
> > --
> > For corporate legal information go to:
> >
> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> >
> >
> > _______________________________________________
> > rtgwg mailing list
> > rtgwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtgwg
> >
>=20
>=20
>=20
> --
> - Sri
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

From russw@riw.us  Tue Nov 15 19:28:33 2011
Return-Path: <russw@riw.us>
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 A4D4811E80B7 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 19:28:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.571
X-Spam-Level: 
X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UFsSlL6JCwRc for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 19:28:33 -0800 (PST)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id 30E8A11E8081 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 19:28:33 -0800 (PST)
Received: from [107.17.45.77] (port=49839) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RQWAn-00016Y-OQ; Tue, 15 Nov 2011 22:28:30 -0500
Message-ID: <4EC32DD7.1000007@riw.us>
Date: Tue, 15 Nov 2011 22:28:23 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Sriganesh Kini <sriganesh.kini@ericsson.com>
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTdXKUckads5aTshwQ@mail.gmail.com>
In-Reply-To: <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTdXKUckads5aTshwQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.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: Wed, 16 Nov 2011 03:28:33 -0000

> IPFRR that would be quite confusing :-). IMO there is value in an IP
> only solution that is simple and has full coverage. If there isn't one
> then MPLS based solutions seem a better option.

I would argue that we strive for a solution that's all IP, no MPLS.
Let's not give up the hunt because the problem is hard.

BTW, there are simple solutions with little additional state, but they
don't provide anything like optimal paths. The problem isn't finding the
second topology, it's in finding a second topology that's anything like
acceptable.

:-)

Russ

From jeff.tantsura@ericsson.com  Tue Nov 15 20:19:30 2011
Return-Path: <jeff.tantsura@ericsson.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 5A2FB11E8116 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 20:19:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASw8PA3dVByc for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 20:19:25 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE0411E810C for <rtgwg@ietf.org>; Tue, 15 Nov 2011 20:19:25 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAG4JLxY025067; Tue, 15 Nov 2011 22:19:22 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.111]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 15 Nov 2011 23:19:16 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>
Date: Tue, 15 Nov 2011 23:19:13 -0500
Subject: Re: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcykFuannpDpO+eyT3evFp8B6sAv6w==
Message-ID: <91DFDBB0-A7B0-4697-89A7-DD899419C737@ericsson.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJT dXKUckad s5aTshwQ@mail.gmail.com> <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>, Sriganesh Kini <sriganesh.kini@ericsson.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: Wed, 16 Nov 2011 04:19:30 -0000

IMHO it just wouldn't make sense to do "IP or MPLS only" FRR.
While majority uses MPLS we can't ignore those who can't / won't do so.
I think we should clearly separate between full coverage but more complex t=
o implement  solutions ie MRT or FN vs partial coverage but relatively easi=
er to implement solution - LFA as an example

Regards,
Jeff

On Nov 16, 2011, at 11:27, "Eric Osborne (eosborne)" <eosborne@cisco.com> w=
rote:

>=20
>=20
>> -----Original Message-----
>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
>> Of Sriganesh Kini
>> Sent: Wednesday, November 16, 2011 11:11 AM
>> To: Stewart Bryant (stbryant)
>> Cc: rtgwg@ietf.org
>> Subject: Re: Charter Update (Discussion)
>>=20
>> Solutions that use exclusively IP have been seen to run the risk of
> issues such
>> as incomplete coverage or complexity (or both), ...etc.
>> Networks that decline to support MPLS would be similarly affected.
>> Solutions that use MPLS and have full coverage and are deployable seem
>> possible. If we declare non-MPLS(read as IP) networks out of scope of
> IPFRR
>> that would be quite confusing :-).
>=20
> Perhaps...but so would declaring that 'IPFRR' contained MPLS.  I always
> looked looked at it as:
>=20
> - first we had MPLS FRR, which we just called FRR.
> - then, for those that were not interested in MPLS FRR, IPFRR was
> introduced.  Implicitly the name 'IPFRR' excludes MPLS.
>=20
> To now redefine IPFRR to say that the 'IP' part refers to client traffic
> rather than the forwarding technology which builds your protection is
> revisionist and probably contentious.
>=20
>> IMO there is value in an IP only solution
>> that is simple and has full coverage. If there isn't one then MPLS
> based
>> solutions seem a better option.
>>=20
>=20
> But we're not debating value of various solutions, we're debating
> charter and thus where those solutions come from.
>=20
>=20
>=20
> eric
>=20
>=20
>> On Tue, Nov 15, 2011 at 3:08 PM, Stewart Bryant <stbryant@cisco.com>
>> wrote:
>>>=20
>>> Unfortunately whether MPLS is used in a particular network segment
> or
>>> not is a complex and sometimes emotive issue.
>>>=20
>>> If we decide that the best solution is to use MPLS we then face the
>>> issue of what to do about networks that decline to support MPLS. Do
> we
>>> declare non-MPLS networks out of scope for IPFRR, or do we work on
>>> another non-MPLS solution?
>>>=20
>>> - Stewart
>>>=20
>>>=20
>>> On 15/11/2011 22:29, Sriganesh Kini wrote:
>>>>=20
>>>> IP is addressed via MPLS. If IP forwarding were to be used
>>>> exclusively, then it becomes complicated. With MPLS being extended
> to
>>>> more parts of the network than just the core, it seems that is not
> as
>>>> much of a concern.
>>>>=20
>>>> On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>
>>>> wrote:
>>>>>=20
>>>>> On 15/11/2011 21:36, Sriganesh Kini wrote:
>>>>>>=20
>>>>>> Hi,
>>>>>>=20
>>>>>> I agree that having a solution with full coverage is very useful
>>>>>> because it removes the need for complicated analysis to determine
>>>>>> what is protected versus what is not (and worse, how that changes
>>>>>> as the topology change). But the solution has to be simple for it
>>>>>> to get deployed.
>>>>>>=20
>>>>>> One approach using MPLS that solves this using extensions to a
>>>>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>>>>>=20
>>>>> It the approach extensible to an IP context?
>>>>>=20
>>>>> Stewart
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> rtgwg mailing list
>>>>> rtgwg@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>>>=20
>>>>=20
>>>>=20
>>>=20
>>>=20
>>> --
>>> For corporate legal information go to:
>>>=20
>>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>>=20
>>>=20
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>=20
>>=20
>>=20
>>=20
>> --
>> - Sri
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

From akatlas@gmail.com  Tue Nov 15 21:33:31 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 A2E021F0C6F for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 21:33:31 -0800 (PST)
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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IMElz31wi8hZ for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 21:33:27 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id CAEDD1F0CC1 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 21:33:26 -0800 (PST)
Received: by mail-gx0-f172.google.com with SMTP id r5so3597055ggn.31 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 21:33:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=tlkXGyNwEgwi9cPtwfTHcc2+lNiYU+RreW7GqlMTE9o=; b=lKRFIrNpC0DnfeHtjThLGiakhQTKeTvUCoa6QKzyjNGzYl0fv2DomXAA3NAA1OxskB M54/p2e+LJ9nkkXyDkhQsdFOWnUySQ++EAWySHI8u171nUzPhqX+VO34lE7Fzeg+VdfD Hs317BFiz1xm8PsX6HnLFK9r2d0ne0YaYH/S8=
MIME-Version: 1.0
Received: by 10.50.47.168 with SMTP id e8mr31632284ign.15.1321421605114; Tue, 15 Nov 2011 21:33:25 -0800 (PST)
Received: by 10.50.184.229 with HTTP; Tue, 15 Nov 2011 21:33:24 -0800 (PST)
In-Reply-To: <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTdXKUckads5aTshwQ@mail.gmail.com> <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com>
Date: Wed, 16 Nov 2011 00:33:24 -0500
Message-ID: <CAG4d1rd4nRU6wncAxVqUQHq70o-jgZ6+UH7hZRPGXAD43h2QGw@mail.gmail.com>
Subject: Re: Charter Update (Discussion)
From: Alia Atlas <akatlas@gmail.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rtgwg@ietf.org, "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>, Sriganesh Kini <sriganesh.kini@ericsson.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: Wed, 16 Nov 2011 05:33:31 -0000

IPFRR has always included LDP-FRR as well.   Both are clearly
hop-by-hop distributed routing - hence the wording in the charter.

There's RSVP-TE FRR and that is clearly for explicitly routed paths -
which is clearly not hop-by-hop distributed routing.

Since an RSVP-TE LSP can be a forwarding adjacency that appears as a
link in the IGP, of course there is the potential for an IP/LDP FRR
solution to use a TE LSP as a link.

Solutions that require explicitly routed paths to be computed in a
non-distributed fashion seem out of the problem scope to me.

Alia

On Tue, Nov 15, 2011 at 10:27 PM, Eric Osborne (eosborne)
<eosborne@cisco.com> wrote:
>
>
>> -----Original Message-----
>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
>> Of Sriganesh Kini
>> Sent: Wednesday, November 16, 2011 11:11 AM
>> To: Stewart Bryant (stbryant)
>> Cc: rtgwg@ietf.org
>> Subject: Re: Charter Update (Discussion)
>>
>> Solutions that use exclusively IP have been seen to run the risk of
> issues such
>> as incomplete coverage or complexity (or both), ...etc.
>> Networks that decline to support MPLS would be similarly affected.
>> Solutions that use MPLS and have full coverage and are deployable seem
>> possible. If we declare non-MPLS(read as IP) networks out of scope of
> IPFRR
>> that would be quite confusing :-).
>
> Perhaps...but so would declaring that 'IPFRR' contained MPLS. =A0I always
> looked looked at it as:
>
> - first we had MPLS FRR, which we just called FRR.
> - then, for those that were not interested in MPLS FRR, IPFRR was
> introduced. =A0Implicitly the name 'IPFRR' excludes MPLS.
>
> To now redefine IPFRR to say that the 'IP' part refers to client traffic
> rather than the forwarding technology which builds your protection is
> revisionist and probably contentious.
>
>> IMO there is value in an IP only solution
>> that is simple and has full coverage. If there isn't one then MPLS
> based
>> solutions seem a better option.
>>
>
> But we're not debating value of various solutions, we're debating
> charter and thus where those solutions come from.
>
>
>
> eric
>
>
>> On Tue, Nov 15, 2011 at 3:08 PM, Stewart Bryant <stbryant@cisco.com>
>> wrote:
>> >
>> > Unfortunately whether MPLS is used in a particular network segment
> or
>> > not is a complex and sometimes emotive issue.
>> >
>> > If we decide that the best solution is to use MPLS we then face the
>> > issue of what to do about networks that decline to support MPLS. Do
> we
>> > declare non-MPLS networks out of scope for IPFRR, or do we work on
>> > another non-MPLS solution?
>> >
>> > - Stewart
>> >
>> >
>> > On 15/11/2011 22:29, Sriganesh Kini wrote:
>> >>
>> >> IP is addressed via MPLS. If IP forwarding were to be used
>> >> exclusively, then it becomes complicated. With MPLS being extended
> to
>> >> more parts of the network than just the core, it seems that is not
> as
>> >> much of a concern.
>> >>
>> >> On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>
>> >> =A0wrote:
>> >>>
>> >>> On 15/11/2011 21:36, Sriganesh Kini wrote:
>> >>>>
>> >>>> Hi,
>> >>>>
>> >>>> I agree that having a solution with full coverage is very useful
>> >>>> because it removes the need for complicated analysis to determine
>> >>>> what is protected versus what is not (and worse, how that changes
>> >>>> as the topology change). But the solution has to be simple for it
>> >>>> to get deployed.
>> >>>>
>> >>>> One approach using MPLS that solves this using extensions to a
>> >>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>> >>>
>> >>> It the approach extensible to an IP context?
>> >>>
>> >>> Stewart
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> rtgwg mailing list
>> >>> rtgwg@ietf.org
>> >>> https://www.ietf.org/mailman/listinfo/rtgwg
>> >>>
>> >>
>> >>
>> >
>> >
>> > --
>> > For corporate legal information go to:
>> >
>> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>> >
>> >
>> > _______________________________________________
>> > rtgwg mailing list
>> > rtgwg@ietf.org
>> > https://www.ietf.org/mailman/listinfo/rtgwg
>> >
>>
>>
>>
>> --
>> - Sri
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>

From sriganeshkini@gmail.com  Tue Nov 15 22:00:50 2011
Return-Path: <sriganeshkini@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 3A6841F0D25 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 22:00:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.947
X-Spam-Level: 
X-Spam-Status: No, score=-2.947 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2EwGvjFEj8A for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 22:00:45 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 29A531F0CBF for <rtgwg@ietf.org>; Tue, 15 Nov 2011 22:00:45 -0800 (PST)
Received: by wwe3 with SMTP id 3so734851wwe.1 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 22:00:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=+lTntKdectvyV2J4wNHF9yJs8keTp9OBk7Ubq87RZsU=; b=BI495wdfJRnX/aK7RflnvUUCMMioZlQRU9ZxzjoIVu1yIAPIAHpGz+oj2vDY817Ykp Pj3AtrnwnebCOZmKa/9XY3dekJWnl3k+KmKrJxwQgrdG8/xuuy2U1pjYad01p75OO6sa AFSd9EwElT2C4l/lXr0y5/tl9VCPApQLxYupo=
Received: by 10.216.9.204 with SMTP id 54mr306594wet.1.1321423244139; Tue, 15 Nov 2011 22:00:44 -0800 (PST)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.216.10.141 with HTTP; Tue, 15 Nov 2011 22:00:14 -0800 (PST)
In-Reply-To: <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTdXKUckads5aTshwQ@mail.gmail.com> <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Wed, 16 Nov 2011 14:00:14 +0800
X-Google-Sender-Auth: UoXfiwXl4ePi3V8BUHonP4RGH8U
Message-ID: <CAOndX-t5Z=kOR0wZDkQCv44dwLhq-YceKk=GY4J4wxaDeHiEAg@mail.gmail.com>
Subject: Re: Charter Update (Discussion)
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>
Content-Type: text/plain; charset=UTF-8
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "Stewart Bryant\(stbryant\)" <stbryant@cisco.com>, Sriganesh Kini <sriganesh.kini@ericsson.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: Wed, 16 Nov 2011 06:00:50 -0000

Inline

- Sri

Sent from my iPad

On Nov 16, 2011, at 11:27 AM, "Eric Osborne (eosborne)"
<eosborne@cisco.com> wrote:

>
>
>> -----Original Message-----
>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
>> Of Sriganesh Kini
>> Sent: Wednesday, November 16, 2011 11:11 AM
>> To: Stewart Bryant (stbryant)
>> Cc: rtgwg@ietf.org
>> Subject: Re: Charter Update (Discussion)
>>
>> Solutions that use exclusively IP have been seen to run the risk of
> issues such
>> as incomplete coverage or complexity (or both), ...etc.
>> Networks that decline to support MPLS would be similarly affected.
>> Solutions that use MPLS and have full coverage and are deployable seem
>> possible. If we declare non-MPLS(read as IP) networks out of scope of
> IPFRR
>> that would be quite confusing :-).
>
> Perhaps...but so would declaring that 'IPFRR' contained MPLS.  I always

The IPFRR LFA RFC refers to protecting LDP LSP traffic. Maybe that is
the source of the confusion ?

> looked looked at it as:
>
> - first we had MPLS FRR, which we just called FRR.
> - then, for those that were not interested in MPLS FRR, IPFRR was
> introduced.  Implicitly the name 'IPFRR' excludes MPLS.

Are you saying that RFC 5286 should have left out MPLS ? But that is
not the point. LFA should not be interpreted as IP only protection
mechanism. Rather it should be viewed as a technology that can protect
traffic along shortest paths. This may be IP or LDP LSP traffic.

>
> To now redefine IPFRR to say that the 'IP' part refers to client traffic
> rather than the forwarding technology which builds your protection is
> revisionist and probably contentious.
>
>> IMO there is value in an IP only solution
>> that is simple and has full coverage. If there isn't one then MPLS
> based
>> solutions seem a better option.
>>
>
> But we're not debating value of various solutions, we're debating
> charter and thus where those solutions come from.

I agree. I was just responding to Stewart on where the work is.

>
>
>
> eric
>
>
>> On Tue, Nov 15, 2011 at 3:08 PM, Stewart Bryant <stbryant@cisco.com>
>> wrote:
>>>
>>> Unfortunately whether MPLS is used in a particular network segment
> or
>>> not is a complex and sometimes emotive issue.
>>>
>>> If we decide that the best solution is to use MPLS we then face the
>>> issue of what to do about networks that decline to support MPLS. Do
> we
>>> declare non-MPLS networks out of scope for IPFRR, or do we work on
>>> another non-MPLS solution?
>>>
>>> - Stewart
>>>
>>>
>>> On 15/11/2011 22:29, Sriganesh Kini wrote:
>>>>
>>>> IP is addressed via MPLS. If IP forwarding were to be used
>>>> exclusively, then it becomes complicated. With MPLS being extended
> to
>>>> more parts of the network than just the core, it seems that is not
> as
>>>> much of a concern.
>>>>
>>>> On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>
>>>> wrote:
>>>>>
>>>>> On 15/11/2011 21:36, Sriganesh Kini wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I agree that having a solution with full coverage is very useful
>>>>>> because it removes the need for complicated analysis to determine
>>>>>> what is protected versus what is not (and worse, how that changes
>>>>>> as the topology change). But the solution has to be simple for it
>>>>>> to get deployed.
>>>>>>
>>>>>> One approach using MPLS that solves this using extensions to a
>>>>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>>>>>
>>>>> It the approach extensible to an IP context?
>>>>>
>>>>> Stewart
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> rtgwg mailing list
>>>>> rtgwg@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> For corporate legal information go to:
>>>
>>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>>
>>>
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>
>>
>>
>>
>> --
>> - Sri
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

From Andras.Csaszar@ericsson.com  Tue Nov 15 22:05:55 2011
Return-Path: <Andras.Csaszar@ericsson.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 C07551F0D32 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 22:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.806
X-Spam-Level: 
X-Spam-Status: No, score=-5.806 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBaHAGguyzd9 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 22:05:55 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id E41871F0D2E for <rtgwg@ietf.org>; Tue, 15 Nov 2011 22:05:54 -0800 (PST)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-c6-4ec352c17cbc
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 1A.06.13753.1C253CE4; Wed, 16 Nov 2011 07:05:53 +0100 (CET)
Received: from ESESSCMS0363.eemea.ericsson.se ([169.254.1.166]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Wed, 16 Nov 2011 07:05:53 +0100
From: =?iso-8859-1?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
To: Alia Atlas <akatlas@gmail.com>, "Eric Osborne (eosborne)" <eosborne@cisco.com>
Date: Wed, 16 Nov 2011 07:05:49 +0100
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcykIUmmgiU/Es5PQba7L4xCxkhaOAAA1I7w
Message-ID: <8DCD771BDA4A394E9BCBA8932E83929749CBFE6351@ESESSCMS0363.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTdXKUckads5aTshwQ@mail.gmail.com> <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com> <CAG4d1rd4nRU6wncAxVqUQHq70o-jgZ6+UH7hZRPGXAD43h2QGw@mail.gmail.com>
In-Reply-To: <CAG4d1rd4nRU6wncAxVqUQHq70o-jgZ6+UH7hZRPGXAD43h2QGw@mail.gmail.com>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>, Sriganesh Kini <sriganesh.kini@ericsson.com>, "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: Wed, 16 Nov 2011 06:05:55 -0000

> IPFRR has always included LDP-FRR as well.   Both are clearly
> hop-by-hop distributed routing - hence the wording in the charter.

Are we also considering FRR for Ethernet/SPB? ;-) ;-) It is hop-by-hop dist=
ributed routing.

So I still hold on to my first email in this thread: we should be explicit =
in the charter. Writing LDP and IP specifically, unicast and multicast, ASB=
R protection, and all the things we target.


> There's RSVP-TE FRR and that is clearly for explicitly routed=20
> paths - which is clearly not hop-by-hop distributed routing.
>=20
> Since an RSVP-TE LSP can be a forwarding adjacency that=20
> appears as a link in the IGP, of course there is the=20
> potential for an IP/LDP FRR solution to use a TE LSP as a link.

Agree, and since there is already an MPLS-only solution, I don't see to wor=
k on yet another (even if it's LDP).

I argue that working on an LDP-only solution is only justified if we do not=
 find a full-coverage IP&LDP concept that is practical enough. (A side-note=
, though: even if the concept is the same for IP and LDP, the lower-level d=
etails will be of course different for the two.)

Andr=E1s=

From imc.shand@googlemail.com  Tue Nov 15 22:15:49 2011
Return-Path: <imc.shand@googlemail.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 34D6A11E80F1 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 22:15:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level: 
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xdDM74ErNsr2 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 22:15:44 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9CC4711E80D9 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 22:15:44 -0800 (PST)
Received: by wwe5 with SMTP id 5so91621wwe.13 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 22:15:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=2UdCPXOzlr+WJKWA0zChQKEyz/oir2OavVR5VGSi6Sc=; b=G4q5t0zZSnxpH5iinERl+HRuElj8NMtwMpyl/Avt5ZMNnWo+5lJK7a/1ucDOt6Q5jO Qc4lb/1hVDd894DJ8BQlYaC/2X0h6BuxwXD5iQSATrI03O51QXnWl+HeWoN9z5bbvL/N Wo2LY71pa2ixu6wVJ1Qikf7UjxmDRBwXWJwqI=
Received: by 10.216.137.193 with SMTP id y43mr4974676wei.108.1321424143608; Tue, 15 Nov 2011 22:15:43 -0800 (PST)
Received: from [192.168.1.174] (188-220-40-104.zone11.bethere.co.uk. [188.220.40.104]) by mx.google.com with ESMTPS id a27sm31544462wbp.16.2011.11.15.22.15.42 (version=SSLv3 cipher=OTHER); Tue, 15 Nov 2011 22:15:42 -0800 (PST)
Message-ID: <4EC3550B.5080703@googlemail.com>
Date: Wed, 16 Nov 2011 06:15:39 +0000
From: Mike Shand <imc.shand@googlemail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: Charter Update (Discussion)
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTdXKUckads5aTshwQ@mail.gmail.com> <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com> <CAG4d1rd4nRU6wncAxVqUQHq70o-jgZ6+UH7hZRPGXAD43h2QGw@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929749CBFE6351@ESESSCMS0363.eemea.ericsson.se>
In-Reply-To: <8DCD771BDA4A394E9BCBA8932E83929749CBFE6351@ESESSCMS0363.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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, 16 Nov 2011 06:15:49 -0000

I agree. We should be working on pure IP solutions which can also be 
used with LDP.

Mike

On 16/11/2011 06:05, András Császár wrote:
>> IPFRR has always included LDP-FRR as well.   Both are clearly
>> hop-by-hop distributed routing - hence the wording in the charter.
> Are we also considering FRR for Ethernet/SPB? ;-) ;-) It is hop-by-hop distributed routing.
>
> So I still hold on to my first email in this thread: we should be explicit in the charter. Writing LDP and IP specifically, unicast and multicast, ASBR protection, and all the things we target.
>
>
>> There's RSVP-TE FRR and that is clearly for explicitly routed
>> paths - which is clearly not hop-by-hop distributed routing.
>>
>> Since an RSVP-TE LSP can be a forwarding adjacency that
>> appears as a link in the IGP, of course there is the
>> potential for an IP/LDP FRR solution to use a TE LSP as a link.
> Agree, and since there is already an MPLS-only solution, I don't see to work on yet another (even if it's LDP).
>
> I argue that working on an LDP-only solution is only justified if we do not find a full-coverage IP&LDP concept that is practical enough. (A side-note, though: even if the concept is the same for IP and LDP, the lower-level details will be of course different for the two.)
>
> András
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


From eosborne@cisco.com  Tue Nov 15 22:27:21 2011
Return-Path: <eosborne@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 3EFEC21F92B9 for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 22:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhKLWqvrxhyj for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 22:27:17 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id D8B2711E814B for <rtgwg@ietf.org>; Tue, 15 Nov 2011 22:27:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eosborne@cisco.com; l=5336; q=dns/txt; s=iport; t=1321424837; x=1322634437; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=PV/X8EhaOcjkH3SoeyXdhXhg6aFCT1P/hjPIEt8+n3c=; b=lnpgIKDjSxLvZAC98yobj8YTzqR1z71bScEUBb0Bho2fAUWhiClsa5OD n22nPMH799lKMpOIPm4JsEr7Jx0UqL9GHRYJ10TsnqytD0yhIsixCquby odV07ZBgqPJhsJmA/zIl+xuwe2+0pZWKxmeJ6i+coHvI4fpQ2MtcoDZsV 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnsAAPVWw06tJV2Z/2dsb2JhbABDmWqQCIEFgXIBAQEDAQEBAQ8BHT4LDAQCAQgOAwQBAQEKBhcBBgEgBh8JCAEBBBMIEweHYAiaIgGeVIk0YwSHYzGRZIUHh1A
X-IronPort-AV: E=Sophos;i="4.69,519,1315180800"; d="scan'208";a="36433543"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-1.cisco.com with ESMTP; 16 Nov 2011 06:27:16 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAG6RGL4025254;  Wed, 16 Nov 2011 06:27:16 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 00:27:16 -0600
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: Charter Update (Discussion)
Date: Wed, 16 Nov 2011 00:27:12 -0600
Message-ID: <D29E470202D67745B61059870F433B54079CD001@XMB-RCD-202.cisco.com>
In-Reply-To: <CAG4d1rd4nRU6wncAxVqUQHq70o-jgZ6+UH7hZRPGXAD43h2QGw@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcykIUQn/o6UDcVsR1uIrfKW/veqXgAB2rwg
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net><8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se><7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu><CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com><4EB81CAD.4080402@googlemail.com><CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com><8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se><4EB96CBF.7040501@cisco.com><8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se><4EBABECC.2060701@cisco.com><EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se><4EBB2563.5010302@cisco.com><8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se><CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com><4EC2E42D.2010403@cisco.com><CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com><4EC2F0F2.5010400@cisco.com><CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTd XKUckads 5aTshwQ@mail .gmail.com><D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com> <CAG4d1rd4nRU6wncAxVqUQHq70o-jgZ6+UH7hZRPGXAD43h2QGw@mail.gmail.com>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Alia Atlas" <akatlas@gmail.com>
X-OriginalArrivalTime: 16 Nov 2011 06:27:16.0034 (UTC) FILETIME=[C8BC6A20:01CCA428]
Cc: rtgwg@ietf.org, "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>, Sriganesh Kini <sriganesh.kini@ericsson.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: Wed, 16 Nov 2011 06:27:21 -0000

> -----Original Message-----
> From: Alia Atlas [mailto:akatlas@gmail.com]
> Sent: Wednesday, November 16, 2011 1:33 PM
> To: Eric Osborne (eosborne)
> Cc: Sriganesh Kini; Stewart Bryant (stbryant); rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>=20
> IPFRR has always included LDP-FRR as well.   Both are clearly
> hop-by-hop distributed routing - hence the wording in the charter.
>=20
> There's RSVP-TE FRR and that is clearly for explicitly routed paths - =
which is
> clearly not hop-by-hop distributed routing.
>=20
> Since an RSVP-TE LSP can be a forwarding adjacency that appears as a =
link in
> the IGP, of course there is the potential for an IP/LDP FRR solution =
to use a TE
> LSP as a link.
>=20
> Solutions that require explicitly routed paths to be computed in a =
non-
> distributed fashion seem out of the problem scope to me.

OK, so solutions which use TE LSPs as FAs for FRR are OK but computing =
the paths and destinations for those LSPs is not?



eric

>=20
> Alia
>=20
> On Tue, Nov 15, 2011 at 10:27 PM, Eric Osborne (eosborne)
> <eosborne@cisco.com> wrote:
> >
> >
> >> -----Original Message-----
> >> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On
> >> Behalf Of Sriganesh Kini
> >> Sent: Wednesday, November 16, 2011 11:11 AM
> >> To: Stewart Bryant (stbryant)
> >> Cc: rtgwg@ietf.org
> >> Subject: Re: Charter Update (Discussion)
> >>
> >> Solutions that use exclusively IP have been seen to run the risk of
> > issues such
> >> as incomplete coverage or complexity (or both), ...etc.
> >> Networks that decline to support MPLS would be similarly affected.
> >> Solutions that use MPLS and have full coverage and are deployable
> >> seem possible. If we declare non-MPLS(read as IP) networks out of
> >> scope of
> > IPFRR
> >> that would be quite confusing :-).
> >
> > Perhaps...but so would declaring that 'IPFRR' contained MPLS. =A0I
> > always looked looked at it as:
> >
> > - first we had MPLS FRR, which we just called FRR.
> > - then, for those that were not interested in MPLS FRR, IPFRR was
> > introduced. =A0Implicitly the name 'IPFRR' excludes MPLS.
> >
> > To now redefine IPFRR to say that the 'IP' part refers to client
> > traffic rather than the forwarding technology which builds your
> > protection is revisionist and probably contentious.
> >
> >> IMO there is value in an IP only solution that is simple and has =
full
> >> coverage. If there isn't one then MPLS
> > based
> >> solutions seem a better option.
> >>
> >
> > But we're not debating value of various solutions, we're debating
> > charter and thus where those solutions come from.
> >
> >
> >
> > eric
> >
> >
> >> On Tue, Nov 15, 2011 at 3:08 PM, Stewart Bryant =
<stbryant@cisco.com>
> >> wrote:
> >> >
> >> > Unfortunately whether MPLS is used in a particular network =
segment
> > or
> >> > not is a complex and sometimes emotive issue.
> >> >
> >> > If we decide that the best solution is to use MPLS we then face =
the
> >> > issue of what to do about networks that decline to support MPLS. =
Do
> > we
> >> > declare non-MPLS networks out of scope for IPFRR, or do we work =
on
> >> > another non-MPLS solution?
> >> >
> >> > - Stewart
> >> >
> >> >
> >> > On 15/11/2011 22:29, Sriganesh Kini wrote:
> >> >>
> >> >> IP is addressed via MPLS. If IP forwarding were to be used
> >> >> exclusively, then it becomes complicated. With MPLS being =
extended
> > to
> >> >> more parts of the network than just the core, it seems that is =
not
> > as
> >> >> much of a concern.
> >> >>
> >> >> On Tue, Nov 15, 2011 at 2:14 PM, Stewart
> >> >> Bryant<stbryant@cisco.com>
> >> >> =A0wrote:
> >> >>>
> >> >>> On 15/11/2011 21:36, Sriganesh Kini wrote:
> >> >>>>
> >> >>>> Hi,
> >> >>>>
> >> >>>> I agree that having a solution with full coverage is very =
useful
> >> >>>> because it removes the need for complicated analysis to
> >> >>>> determine what is protected versus what is not (and worse, how
> >> >>>> that changes as the topology change). But the solution has to =
be
> >> >>>> simple for it to get deployed.
> >> >>>>
> >> >>>> One approach using MPLS that solves this using extensions to a
> >> >>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
> >> >>>
> >> >>> It the approach extensible to an IP context?
> >> >>>
> >> >>> Stewart
> >> >>>
> >> >>>
> >> >>> _______________________________________________
> >> >>> rtgwg mailing list
> >> >>> rtgwg@ietf.org
> >> >>> https://www.ietf.org/mailman/listinfo/rtgwg
> >> >>>
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > For corporate legal information go to:
> >> >
> >> > =
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> >> >
> >> >
> >> > _______________________________________________
> >> > rtgwg mailing list
> >> > rtgwg@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/rtgwg
> >> >
> >>
> >>
> >>
> >> --
> >> - Sri
> >> _______________________________________________
> >> rtgwg mailing list
> >> rtgwg@ietf.org
> >> https://www.ietf.org/mailman/listinfo/rtgwg
> > _______________________________________________
> > rtgwg mailing list
> > rtgwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtgwg
> >

From sriganeshkini@gmail.com  Tue Nov 15 23:03:17 2011
Return-Path: <sriganeshkini@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 0CFC711E81CE for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 23:03:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.952
X-Spam-Level: 
X-Spam-Status: No, score=-2.952 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XBFmoHiA2j4g for <rtgwg@ietfa.amsl.com>; Tue, 15 Nov 2011 23:03:12 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 07BDA11E81C6 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 23:03:11 -0800 (PST)
Received: by wyf28 with SMTP id 28so129018wyf.31 for <rtgwg@ietf.org>; Tue, 15 Nov 2011 23:03:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=8F3eeNCoUUFfOtRr8bC8cajeeISi7KWkcOAiHZ5sWYk=; b=kpTfF7B9E69Kmgc9nKz9AQFshV3BiVoBWtFms9iMsy9DR5iJncD85ofEha/J7+rgq4 oqdo99/M9QS1xj9E4dFhRflU0frLSbVvmMm2YpG0Kc40gX9bfwxLQ6EWJ187qm1yqTPs RJExt6TVP7hKwyttCB0tF6yFKseZ4aWAAqHO4=
Received: by 10.216.131.42 with SMTP id l42mr330377wei.16.1321426991110; Tue, 15 Nov 2011 23:03:11 -0800 (PST)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.216.10.141 with HTTP; Tue, 15 Nov 2011 23:02:40 -0800 (PST)
In-Reply-To: <CAG4d1rd4nRU6wncAxVqUQHq70o-jgZ6+UH7hZRPGXAD43h2QGw@mail.gmail.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <CAOndX-u229b3QG9sVvF-K7vOqbJ2T5WgJTdXKUckads5aTshwQ@mail.gmail.com> <D29E470202D67745B61059870F433B54079CCFC2@XMB-RCD-202.cisco.com> <CAG4d1rd4nRU6wncAxVqUQHq70o-jgZ6+UH7hZRPGXAD43h2QGw@mail.gmail.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Wed, 16 Nov 2011 15:02:40 +0800
X-Google-Sender-Auth: Y70o2j5EQ2FNa-HKwIMKOoTpVF8
Message-ID: <CAOndX-sUtWpU6yoCb5Y2Jv0tQz+9oCHFNuiFYM4AhBB64-iM7A@mail.gmail.com>
Subject: Re: Charter Update (Discussion)
To: Alia Atlas <akatlas@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>, Sriganesh Kini <sriganesh.kini@ericsson.com>, "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: Wed, 16 Nov 2011 07:03:17 -0000

We need to clearly distinguish between path type of the protected
traffic versus that of the backup. I agree that protected traffic in
IP as well as MPLS (LDP) is hop-by-hop routed.

What possibly makes it confusing is that the backup path may contain
parts that are explicitly computed and other parts that are not. Even
in LFA the first hop of backup path is explicitly routed, and to
protect that direction of traffic does not even need distributed
backup computation (since the next hop from PLR is using a normal
routed path) !

- Sri

Sent from my iPad

On Nov 16, 2011, at 1:33 PM, Alia Atlas <akatlas@gmail.com> wrote:

> IPFRR has always included LDP-FRR as well.   Both are clearly
> hop-by-hop distributed routing - hence the wording in the charter.
>
> There's RSVP-TE FRR and that is clearly for explicitly routed paths -
> which is clearly not hop-by-hop distributed routing.
>
> Since an RSVP-TE LSP can be a forwarding adjacency that appears as a
> link in the IGP, of course there is the potential for an IP/LDP FRR
> solution to use a TE LSP as a link.
>
> Solutions that require explicitly routed paths to be computed in a
> non-distributed fashion seem out of the problem scope to me.
>
> Alia
>
> On Tue, Nov 15, 2011 at 10:27 PM, Eric Osborne (eosborne)
> <eosborne@cisco.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
>>> Of Sriganesh Kini
>>> Sent: Wednesday, November 16, 2011 11:11 AM
>>> To: Stewart Bryant (stbryant)
>>> Cc: rtgwg@ietf.org
>>> Subject: Re: Charter Update (Discussion)
>>>
>>> Solutions that use exclusively IP have been seen to run the risk of
>> issues such
>>> as incomplete coverage or complexity (or both), ...etc.
>>> Networks that decline to support MPLS would be similarly affected.
>>> Solutions that use MPLS and have full coverage and are deployable seem
>>> possible. If we declare non-MPLS(read as IP) networks out of scope of
>> IPFRR
>>> that would be quite confusing :-).
>>
>> Perhaps...but so would declaring that 'IPFRR' contained MPLS.  I always
>> looked looked at it as:
>>
>> - first we had MPLS FRR, which we just called FRR.
>> - then, for those that were not interested in MPLS FRR, IPFRR was
>> introduced.  Implicitly the name 'IPFRR' excludes MPLS.
>>
>> To now redefine IPFRR to say that the 'IP' part refers to client traffic
>> rather than the forwarding technology which builds your protection is
>> revisionist and probably contentious.
>>
>>> IMO there is value in an IP only solution
>>> that is simple and has full coverage. If there isn't one then MPLS
>> based
>>> solutions seem a better option.
>>>
>>
>> But we're not debating value of various solutions, we're debating
>> charter and thus where those solutions come from.
>>
>>
>>
>> eric
>>
>>
>>> On Tue, Nov 15, 2011 at 3:08 PM, Stewart Bryant <stbryant@cisco.com>
>>> wrote:
>>>>
>>>> Unfortunately whether MPLS is used in a particular network segment
>> or
>>>> not is a complex and sometimes emotive issue.
>>>>
>>>> If we decide that the best solution is to use MPLS we then face the
>>>> issue of what to do about networks that decline to support MPLS. Do
>> we
>>>> declare non-MPLS networks out of scope for IPFRR, or do we work on
>>>> another non-MPLS solution?
>>>>
>>>> - Stewart
>>>>
>>>>
>>>> On 15/11/2011 22:29, Sriganesh Kini wrote:
>>>>>
>>>>> IP is addressed via MPLS. If IP forwarding were to be used
>>>>> exclusively, then it becomes complicated. With MPLS being extended
>> to
>>>>> more parts of the network than just the core, it seems that is not
>> as
>>>>> much of a concern.
>>>>>
>>>>> On Tue, Nov 15, 2011 at 2:14 PM, Stewart Bryant<stbryant@cisco.com>
>>>>>  wrote:
>>>>>>
>>>>>> On 15/11/2011 21:36, Sriganesh Kini wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I agree that having a solution with full coverage is very useful
>>>>>>> because it removes the need for complicated analysis to determine
>>>>>>> what is protected versus what is not (and worse, how that changes
>>>>>>> as the topology change). But the solution has to be simple for it
>>>>>>> to get deployed.
>>>>>>>
>>>>>>> One approach using MPLS that solves this using extensions to a
>>>>>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>>>>>>
>>>>>> It the approach extensible to an IP context?
>>>>>>
>>>>>> Stewart
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> rtgwg mailing list
>>>>>> rtgwg@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> For corporate legal information go to:
>>>>
>>>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>>>
>>>>
>>>> _______________________________________________
>>>> rtgwg mailing list
>>>> rtgwg@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>>
>>>
>>>
>>>
>>> --
>>> - Sri
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

From eosborne@cisco.com  Wed Nov 16 17:08:28 2011
Return-Path: <eosborne@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 B8B5921F8E62 for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 17:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ztH-Yl5jpOUG for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 17:08:28 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 9808221F8E01 for <rtgwg@ietf.org>; Wed, 16 Nov 2011 17:08:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eosborne@cisco.com; l=3733; q=dns/txt; s=iport; t=1321492107; x=1322701707; h=mime-version:content-transfer-encoding:subject:date: message-id:references:from:to:cc; bh=4KWFCRcXf5Vlr28MsX07MDrY3rvpHZiSR6RLgeD+xzk=; b=PF3NKUA92NQ+c9ac+iXdw+Dl2UdB28aXUOo4AKL8TOPMrdPDDiEIejkv 0FFoCyZT2Yin+NHefBDb9Ib6Dt2JRfvBs7ZaaP0scNgGtnoCUZc9taGlf dXKXCL9tgxBTluhz4wvn69Lk5EE0ZjAU1mgLgrX1ukCuEgY4Mb26QQYbi A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AowAAJ1dxE6tJXG//2dsb2JhbABCmXiQDoEFgXIBAQEDAQEBAQ8BHQo0CwwEAgEIEQQBAQEKBhcBBgEmHwkIAQEEARIIEweHYAiUZAGeaIk0YwSIFJFkjFc
X-IronPort-AV: E=Sophos;i="4.69,523,1315180800"; d="scan'208";a="36735326"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-6.cisco.com with ESMTP; 17 Nov 2011 01:08:27 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAH18Rsd023779;  Thu, 17 Nov 2011 01:08:27 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 19:08:26 -0600
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: Charter Update (Discussion)
Date: Wed, 16 Nov 2011 19:08:25 -0600
Message-ID: <D29E470202D67745B61059870F433B54079CD496@XMB-RCD-202.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Charter Update (Discussion)
Thread-Index: Acyj64X5WWaPQoBdSpGnv6FxRg7qiQACdSKQADPIOaA=
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net><8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se><7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu><CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com><4EB81CAD.4080402@googlemail.com><CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com><8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se><4EB96CBF.7040501@cisco.com><8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se><4EBABECC.2060701@cisco.com><EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se><4EBB2563.5010302@cisco.com><8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se><CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com><4EC2E42D.2010403@cisco.com><CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> 
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>, "Sriganesh Kini" <sriganesh.kini@ericsson.com>
X-OriginalArrivalTime: 17 Nov 2011 01:08:26.0992 (UTC) FILETIME=[6959FF00:01CCA4C5]
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: Thu, 17 Nov 2011 01:08:28 -0000

Self-replying....what if the charter said something like "RTGWG focuses
on IGP-based protection mechanisms which require no multihop explicit
routing and which attempt to provide 100% failure coverage" or something
along those lines? =20

'no multihop explicit routing' is deliberately  intended to exclude not
just TE LSPs but also static TP LSPs and whatever other explicit path
steering mechanisms we come up with (IP Options?  A zombie outbreak of
CR-LDP?).  It allows for the small bit of explicit routing that LFA
does, picking an OIF not in the RIB. =20

"attempts to provide 100% coverage" is to recognize that there are
multiple solutions to the problem (LFA, MRT, whatever we come up with
next).  All can provide 100% coverage in the right topology, but some
can't cover all scenarios; it may be that the scenarios which can't be
100% covered are not of interest to those who wish to deploy a
particular technology.


Language lawyering aside, does this seem like a reasonable approach?


eric


> -----Original Message-----
> From: Eric Osborne (eosborne)
> Sent: Wednesday, November 16, 2011 8:20 AM
> To: Stewart Bryant (stbryant); Sriganesh Kini
> Cc: rtgwg@ietf.org
> Subject: RE: Charter Update (Discussion)
>=20
>=20
>=20
> > -----Original Message-----
> > From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On
Behalf
> > Of Stewart Bryant (stbryant)
> > Sent: Wednesday, November 16, 2011 7:09 AM
> > To: Sriganesh Kini
> > Cc: rtgwg@ietf.org
> > Subject: Re: Charter Update (Discussion)
> >
> >
> > Unfortunately whether MPLS is used in a particular network segment
or
> > not is a complex and sometimes emotive issue.
> >
> > If we decide that the best solution is to use MPLS we then face the
> > issue of what to do about networks that decline to support MPLS. Do
we
> > declare non-MPLS networks out of scope for IPFRR, or do we work on
> > another non- MPLS solution?
>=20
> I think you also have to wrestle with the opposite problem.  If you
declare
> that convergence schemes which require MPLS to provide 100% coverage
> are within scope, what exactly is out of scope?
>=20
>=20
>=20
> eric
>=20
> >
> > - Stewart
> >
> >
> > On 15/11/2011 22:29, Sriganesh Kini wrote:
> > > IP is addressed via MPLS. If IP forwarding were to be used
> > > exclusively, then it becomes complicated. With MPLS being extended
> > > to more parts of the network than just the core, it seems that is
> > > not as much of a concern.
> > >
> > > On Tue, Nov 15, 2011 at 2:14 PM, Stewart
Bryant<stbryant@cisco.com>
> > wrote:
> > >> On 15/11/2011 21:36, Sriganesh Kini wrote:
> > >>> Hi,
> > >>>
> > >>> I agree that having a solution with full coverage is very useful
> > >>> because it removes the need for complicated analysis to
determine
> > >>> what is protected versus what is not (and worse, how that
changes
> > >>> as the topology change). But the solution has to be simple for
it
> > >>> to get deployed.
> > >>>
> > >>> One approach using MPLS that solves this using extensions to a
> > >>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
> > >> It the approach extensible to an IP context?
> > >>
> > >> Stewart
> > >>
> > >>
> > >> _______________________________________________
> > >> rtgwg mailing list
> > >> rtgwg@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/rtgwg
> > >>
> > >
> > >
> >
> >
> > --
> > For corporate legal information go to:
> >
> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> >
> >
> > _______________________________________________
> > rtgwg mailing list
> > rtgwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtgwg

From jeff.tantsura@ericsson.com  Wed Nov 16 17:33:46 2011
Return-Path: <jeff.tantsura@ericsson.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 3220C11E8082 for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 17:33:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SILxyzofcDMN for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 17:33:45 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6C83611E8081 for <rtgwg@ietf.org>; Wed, 16 Nov 2011 17:33:45 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pAH1XiTa008568 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 16 Nov 2011 19:33:44 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.111]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Wed, 16 Nov 2011 20:33:43 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>
Date: Wed, 16 Nov 2011 20:33:48 -0500
Subject: Re: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcykyPEFQxTxDW3RRYeCuxFer0A8kg==
Message-ID: <176F9110-B559-4128-9AD1-5B14385032F5@ericsson.com>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <D29E470202D67745B61059870F433B54079CD496@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B54079CD496@XMB-RCD-202.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, Sriganesh Kini <sriganesh.kini@ericsson.com>, "Stewart Bryant \(stbryant\)" <stbryant@cisco.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: Thu, 17 Nov 2011 01:33:46 -0000

Eric,

Self-rephrasing - if a solution to provide 100% coverage is topology depend=
ent then it simply doesn't provide 100%, there's no "right topology" to app=
ly to every network.=20
However - if you look at rtgwg agenda - there are at least 2 proposals to p=
rovide 100% coverage in virtually any topology (given there's a backup)

Regards,
Jeff

On Nov 17, 2011, at 9:08 AM, "Eric Osborne (eosborne)" <eosborne@cisco.com>=
 wrote:

> Self-replying....what if the charter said something like "RTGWG focuses
> on IGP-based protection mechanisms which require no multihop explicit
> routing and which attempt to provide 100% failure coverage" or something
> along those lines? =20
>=20
> 'no multihop explicit routing' is deliberately  intended to exclude not
> just TE LSPs but also static TP LSPs and whatever other explicit path
> steering mechanisms we come up with (IP Options?  A zombie outbreak of
> CR-LDP?).  It allows for the small bit of explicit routing that LFA
> does, picking an OIF not in the RIB. =20
>=20
> "attempts to provide 100% coverage" is to recognize that there are
> multiple solutions to the problem (LFA, MRT, whatever we come up with
> next).  All can provide 100% coverage in the right topology, but some
> can't cover all scenarios; it may be that the scenarios which can't be
> 100% covered are not of interest to those who wish to deploy a
> particular technology.
>=20
>=20
> Language lawyering aside, does this seem like a reasonable approach?
>=20
>=20
> eric
>=20
>=20
>> -----Original Message-----
>> From: Eric Osborne (eosborne)
>> Sent: Wednesday, November 16, 2011 8:20 AM
>> To: Stewart Bryant (stbryant); Sriganesh Kini
>> Cc: rtgwg@ietf.org
>> Subject: RE: Charter Update (Discussion)
>>=20
>>=20
>>=20
>>> -----Original Message-----
>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On
> Behalf
>>> Of Stewart Bryant (stbryant)
>>> Sent: Wednesday, November 16, 2011 7:09 AM
>>> To: Sriganesh Kini
>>> Cc: rtgwg@ietf.org
>>> Subject: Re: Charter Update (Discussion)
>>>=20
>>>=20
>>> Unfortunately whether MPLS is used in a particular network segment
> or
>>> not is a complex and sometimes emotive issue.
>>>=20
>>> If we decide that the best solution is to use MPLS we then face the
>>> issue of what to do about networks that decline to support MPLS. Do
> we
>>> declare non-MPLS networks out of scope for IPFRR, or do we work on
>>> another non- MPLS solution?
>>=20
>> I think you also have to wrestle with the opposite problem.  If you
> declare
>> that convergence schemes which require MPLS to provide 100% coverage
>> are within scope, what exactly is out of scope?
>>=20
>>=20
>>=20
>> eric
>>=20
>>>=20
>>> - Stewart
>>>=20
>>>=20
>>> On 15/11/2011 22:29, Sriganesh Kini wrote:
>>>> IP is addressed via MPLS. If IP forwarding were to be used
>>>> exclusively, then it becomes complicated. With MPLS being extended
>>>> to more parts of the network than just the core, it seems that is
>>>> not as much of a concern.
>>>>=20
>>>> On Tue, Nov 15, 2011 at 2:14 PM, Stewart
> Bryant<stbryant@cisco.com>
>>> wrote:
>>>>> On 15/11/2011 21:36, Sriganesh Kini wrote:
>>>>>> Hi,
>>>>>>=20
>>>>>> I agree that having a solution with full coverage is very useful
>>>>>> because it removes the need for complicated analysis to
> determine
>>>>>> what is protected versus what is not (and worse, how that
> changes
>>>>>> as the topology change). But the solution has to be simple for
> it
>>>>>> to get deployed.
>>>>>>=20
>>>>>> One approach using MPLS that solves this using extensions to a
>>>>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
>>>>> It the approach extensible to an IP context?
>>>>>=20
>>>>> Stewart
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> rtgwg mailing list
>>>>> rtgwg@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>>>>=20
>>>>=20
>>>>=20
>>>=20
>>>=20
>>> --
>>> For corporate legal information go to:
>>>=20
>>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>>=20
>>>=20
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

From eosborne@cisco.com  Wed Nov 16 17:45:02 2011
Return-Path: <eosborne@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 7D50B11E80BB for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 17:45:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Hks1nbn50EL for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 17:44:56 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id A3BD911E8081 for <rtgwg@ietf.org>; Wed, 16 Nov 2011 17:44:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eosborne@cisco.com; l=5532; q=dns/txt; s=iport; t=1321494296; x=1322703896; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=c8FvtDwhqGiuudx8WNKzeGDjqWFb7afdNJ/hTEcxeuo=; b=IP1fdiekgKKhSfni95HGY1qXbdM8MR2qgS11+aLofuf8GcazypCBoHwu cjv6ngjRVzozqSMnql4/lmJ312lIBczr+7SmM38nj2cVxFcxeNIC4nSIU oEzaFAmDPnTT3mBoqblXN/7PQQ5IYwAL3Mm8ED5ie+g5b8OBde7sfld8d w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArQAAPNmxE6tJV2Z/2dsb2JhbABCmXiQDoEFgXIBAQEDAQEBAQ8BHQo0CwUHBAIBCBEEAQEBCgYXAQYBJh8JCAEBBBMIEweHYAiUdwGeZ4k0YwSIFJFkjFc
X-IronPort-AV: E=Sophos;i="4.69,524,1315180800"; d="scan'208";a="36762467"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 17 Nov 2011 01:44:56 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAH1iuUH020432;  Thu, 17 Nov 2011 01:44:56 GMT
Received: from xmb-rcd-202.cisco.com ([72.163.62.209]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 16 Nov 2011 19:44:55 -0600
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: Charter Update (Discussion)
Date: Wed, 16 Nov 2011 19:44:54 -0600
Message-ID: <D29E470202D67745B61059870F433B54079CD4A8@XMB-RCD-202.cisco.com>
In-Reply-To: <176F9110-B559-4128-9AD1-5B14385032F5@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcykyPEFQxTxDW3RRYeCuxFer0A8kgAATUZA
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <D29E470202D67745B61 059870F4 33B54079CD49 6@XMB-RCD-202.cisco.com> <176F9110-B559-4128-9AD1-5B14385032F5@ericsson.com>
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "Jeff Tantsura" <jeff.tantsura@ericsson.com>
X-OriginalArrivalTime: 17 Nov 2011 01:44:55.0864 (UTC) FILETIME=[82055B80:01CCA4CA]
Cc: rtgwg@ietf.org, Sriganesh Kini <sriganesh.kini@ericsson.com>, "Stewart Bryant \(stbryant\)" <stbryant@cisco.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: Thu, 17 Nov 2011 01:45:02 -0000

> -----Original Message-----
> From: Jeff Tantsura [mailto:jeff.tantsura@ericsson.com]
> Sent: Thursday, November 17, 2011 9:34 AM
> To: Eric Osborne (eosborne)
> Cc: Stewart Bryant (stbryant); Sriganesh Kini; rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>=20
> Eric,
>=20
> Self-rephrasing - if a solution to provide 100% coverage is topology
> dependent then it simply doesn't provide 100%, there's no "right
topology"
> to apply to every network.

No, and I don't think we need to be in the business of standardizing
topologies.  But look at it the other way.  If a technology provides
100% coverage in some real-world technologies that people are using
today but provides 98% in other topologies that are also in use, that
technology seems appropriate for the first case.  Whether it's
appropriate for the second is up to the operator of the second.

Right?

> However - if you look at rtgwg agenda - there are at least 2 proposals
to
> provide 100% coverage in virtually any topology (given there's a
backup)
>=20

I admit I have not read them.  But I think the nuance here hinges on
'*virtually* any topology'.  If a technology provides 100% in many cases
and 98% in many others, is that not 'virtually' all?




eric

> Regards,
> Jeff
>=20
> On Nov 17, 2011, at 9:08 AM, "Eric Osborne (eosborne)"
> <eosborne@cisco.com> wrote:
>=20
> > Self-replying....what if the charter said something like "RTGWG
> > focuses on IGP-based protection mechanisms which require no multihop
> > explicit routing and which attempt to provide 100% failure coverage"
> > or something along those lines?
> >
> > 'no multihop explicit routing' is deliberately  intended to exclude
> > not just TE LSPs but also static TP LSPs and whatever other explicit
> > path steering mechanisms we come up with (IP Options?  A zombie
> > outbreak of CR-LDP?).  It allows for the small bit of explicit
routing
> > that LFA does, picking an OIF not in the RIB.
> >
> > "attempts to provide 100% coverage" is to recognize that there are
> > multiple solutions to the problem (LFA, MRT, whatever we come up
with
> > next).  All can provide 100% coverage in the right topology, but
some
> > can't cover all scenarios; it may be that the scenarios which can't
be
> > 100% covered are not of interest to those who wish to deploy a
> > particular technology.
> >
> >
> > Language lawyering aside, does this seem like a reasonable approach?
> >
> >
> > eric
> >
> >
> >> -----Original Message-----
> >> From: Eric Osborne (eosborne)
> >> Sent: Wednesday, November 16, 2011 8:20 AM
> >> To: Stewart Bryant (stbryant); Sriganesh Kini
> >> Cc: rtgwg@ietf.org
> >> Subject: RE: Charter Update (Discussion)
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On
> > Behalf
> >>> Of Stewart Bryant (stbryant)
> >>> Sent: Wednesday, November 16, 2011 7:09 AM
> >>> To: Sriganesh Kini
> >>> Cc: rtgwg@ietf.org
> >>> Subject: Re: Charter Update (Discussion)
> >>>
> >>>
> >>> Unfortunately whether MPLS is used in a particular network segment
> > or
> >>> not is a complex and sometimes emotive issue.
> >>>
> >>> If we decide that the best solution is to use MPLS we then face
the
> >>> issue of what to do about networks that decline to support MPLS.
Do
> > we
> >>> declare non-MPLS networks out of scope for IPFRR, or do we work on
> >>> another non- MPLS solution?
> >>
> >> I think you also have to wrestle with the opposite problem.  If you
> > declare
> >> that convergence schemes which require MPLS to provide 100%
coverage
> >> are within scope, what exactly is out of scope?
> >>
> >>
> >>
> >> eric
> >>
> >>>
> >>> - Stewart
> >>>
> >>>
> >>> On 15/11/2011 22:29, Sriganesh Kini wrote:
> >>>> IP is addressed via MPLS. If IP forwarding were to be used
> >>>> exclusively, then it becomes complicated. With MPLS being
extended
> >>>> to more parts of the network than just the core, it seems that is
> >>>> not as much of a concern.
> >>>>
> >>>> On Tue, Nov 15, 2011 at 2:14 PM, Stewart
> > Bryant<stbryant@cisco.com>
> >>> wrote:
> >>>>> On 15/11/2011 21:36, Sriganesh Kini wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> I agree that having a solution with full coverage is very
useful
> >>>>>> because it removes the need for complicated analysis to
> > determine
> >>>>>> what is protected versus what is not (and worse, how that
> > changes
> >>>>>> as the topology change). But the solution has to be simple for
> > it
> >>>>>> to get deployed.
> >>>>>>
> >>>>>> One approach using MPLS that solves this using extensions to a
> >>>>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
> >>>>> It the approach extensible to an IP context?
> >>>>>
> >>>>> Stewart
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> rtgwg mailing list
> >>>>> rtgwg@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/rtgwg
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> For corporate legal information go to:
> >>>
> >>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> >>>
> >>>
> >>> _______________________________________________
> >>> rtgwg mailing list
> >>> rtgwg@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/rtgwg
> > _______________________________________________
> > rtgwg mailing list
> > rtgwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtgwg

From jeff.tantsura@ericsson.com  Wed Nov 16 18:08:31 2011
Return-Path: <jeff.tantsura@ericsson.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 35FA01F0C3D for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 18:08:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vb3-sOJv3GWJ for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 18:08:30 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6BDF821F8B10 for <rtgwg@ietf.org>; Wed, 16 Nov 2011 18:08:30 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAH28SrA000708; Wed, 16 Nov 2011 20:08:29 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.111]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Wed, 16 Nov 2011 21:08:23 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>
Date: Wed, 16 Nov 2011 21:08:21 -0500
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcykyPEFQxTxDW3RRYeCuxFer0A8kgAATUZAAACpy3A=
Message-ID: <0ED867EB33AB2B45AAB470D5A64CDBF6181ACF5316@EUSAACMS0701.eamcs.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <D29E470202D67745B61059870F4	33B54079CD49 6@XMB-RCD-202.cisco.com> <176F9110-B559-4128-9AD1-5B14385032F5@ericsson.com> <D29E470202D67745B61059870F433B54079CD4A8@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B54079CD4A8@XMB-RCD-202.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, Sriganesh Kini <sriganesh.kini@ericsson.com>, "Stewart Bryant \(stbryant\)" <stbryant@cisco.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: Thu, 17 Nov 2011 02:08:31 -0000

Eric,

What I meant with "virtually" is that there must be a backup in order to us=
e one, there is no uncovered 2%.

Regards,
Jeff =20

-----Original Message-----
From: Eric Osborne (eosborne) [mailto:eosborne@cisco.com]=20
Sent: Wednesday, November 16, 2011 17:45
To: Jeff Tantsura
Cc: Stewart Bryant (stbryant); Sriganesh Kini; rtgwg@ietf.org
Subject: RE: Charter Update (Discussion)



> -----Original Message-----
> From: Jeff Tantsura [mailto:jeff.tantsura@ericsson.com]
> Sent: Thursday, November 17, 2011 9:34 AM
> To: Eric Osborne (eosborne)
> Cc: Stewart Bryant (stbryant); Sriganesh Kini; rtgwg@ietf.org
> Subject: Re: Charter Update (Discussion)
>=20
> Eric,
>=20
> Self-rephrasing - if a solution to provide 100% coverage is topology
> dependent then it simply doesn't provide 100%, there's no "right
topology"
> to apply to every network.

No, and I don't think we need to be in the business of standardizing
topologies.  But look at it the other way.  If a technology provides
100% coverage in some real-world technologies that people are using
today but provides 98% in other topologies that are also in use, that
technology seems appropriate for the first case.  Whether it's
appropriate for the second is up to the operator of the second.

Right?

> However - if you look at rtgwg agenda - there are at least 2 proposals
to
> provide 100% coverage in virtually any topology (given there's a
backup)
>=20

I admit I have not read them.  But I think the nuance here hinges on
'*virtually* any topology'.  If a technology provides 100% in many cases
and 98% in many others, is that not 'virtually' all?




eric

> Regards,
> Jeff
>=20
> On Nov 17, 2011, at 9:08 AM, "Eric Osborne (eosborne)"
> <eosborne@cisco.com> wrote:
>=20
> > Self-replying....what if the charter said something like "RTGWG
> > focuses on IGP-based protection mechanisms which require no multihop
> > explicit routing and which attempt to provide 100% failure coverage"
> > or something along those lines?
> >
> > 'no multihop explicit routing' is deliberately  intended to exclude
> > not just TE LSPs but also static TP LSPs and whatever other explicit
> > path steering mechanisms we come up with (IP Options?  A zombie
> > outbreak of CR-LDP?).  It allows for the small bit of explicit
routing
> > that LFA does, picking an OIF not in the RIB.
> >
> > "attempts to provide 100% coverage" is to recognize that there are
> > multiple solutions to the problem (LFA, MRT, whatever we come up
with
> > next).  All can provide 100% coverage in the right topology, but
some
> > can't cover all scenarios; it may be that the scenarios which can't
be
> > 100% covered are not of interest to those who wish to deploy a
> > particular technology.
> >
> >
> > Language lawyering aside, does this seem like a reasonable approach?
> >
> >
> > eric
> >
> >
> >> -----Original Message-----
> >> From: Eric Osborne (eosborne)
> >> Sent: Wednesday, November 16, 2011 8:20 AM
> >> To: Stewart Bryant (stbryant); Sriganesh Kini
> >> Cc: rtgwg@ietf.org
> >> Subject: RE: Charter Update (Discussion)
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On
> > Behalf
> >>> Of Stewart Bryant (stbryant)
> >>> Sent: Wednesday, November 16, 2011 7:09 AM
> >>> To: Sriganesh Kini
> >>> Cc: rtgwg@ietf.org
> >>> Subject: Re: Charter Update (Discussion)
> >>>
> >>>
> >>> Unfortunately whether MPLS is used in a particular network segment
> > or
> >>> not is a complex and sometimes emotive issue.
> >>>
> >>> If we decide that the best solution is to use MPLS we then face
the
> >>> issue of what to do about networks that decline to support MPLS.
Do
> > we
> >>> declare non-MPLS networks out of scope for IPFRR, or do we work on
> >>> another non- MPLS solution?
> >>
> >> I think you also have to wrestle with the opposite problem.  If you
> > declare
> >> that convergence schemes which require MPLS to provide 100%
coverage
> >> are within scope, what exactly is out of scope?
> >>
> >>
> >>
> >> eric
> >>
> >>>
> >>> - Stewart
> >>>
> >>>
> >>> On 15/11/2011 22:29, Sriganesh Kini wrote:
> >>>> IP is addressed via MPLS. If IP forwarding were to be used
> >>>> exclusively, then it becomes complicated. With MPLS being
extended
> >>>> to more parts of the network than just the core, it seems that is
> >>>> not as much of a concern.
> >>>>
> >>>> On Tue, Nov 15, 2011 at 2:14 PM, Stewart
> > Bryant<stbryant@cisco.com>
> >>> wrote:
> >>>>> On 15/11/2011 21:36, Sriganesh Kini wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> I agree that having a solution with full coverage is very
useful
> >>>>>> because it removes the need for complicated analysis to
> > determine
> >>>>>> what is protected versus what is not (and worse, how that
> > changes
> >>>>>> as the topology change). But the solution has to be simple for
> > it
> >>>>>> to get deployed.
> >>>>>>
> >>>>>> One approach using MPLS that solves this using extensions to a
> >>>>>> single protocol (LDP) is given in draft-kini-mpls-frr-ldp.
> >>>>> It the approach extensible to an IP context?
> >>>>>
> >>>>> Stewart
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> rtgwg mailing list
> >>>>> rtgwg@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/rtgwg
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> For corporate legal information go to:
> >>>
> >>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> >>>
> >>>
> >>> _______________________________________________
> >>> rtgwg mailing list
> >>> rtgwg@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/rtgwg
> > _______________________________________________
> > rtgwg mailing list
> > rtgwg@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtgwg

From Andras.Csaszar@ericsson.com  Wed Nov 16 18:43:23 2011
Return-Path: <Andras.Csaszar@ericsson.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 B150521F8B50 for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 18:43:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.112
X-Spam-Level: 
X-Spam-Status: No, score=-6.112 tagged_above=-999 required=5 tests=[AWL=0.187,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kt0zikPZqgou for <rtgwg@ietfa.amsl.com>; Wed, 16 Nov 2011 18:43:23 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id D15D121F8B4C for <rtgwg@ietf.org>; Wed, 16 Nov 2011 18:43:22 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-f1-4ec474c99d9d
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id B7.38.09514.9C474CE4; Thu, 17 Nov 2011 03:43:21 +0100 (CET)
Received: from ESESSCMS0363.eemea.ericsson.se ([169.254.1.166]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Thu, 17 Nov 2011 03:43:21 +0100
From: =?iso-8859-1?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
To: "Eric Osborne (eosborne)" <eosborne@cisco.com>, Jeff Tantsura <jeff.tantsura@ericsson.com>
Date: Thu, 17 Nov 2011 03:43:19 +0100
Subject: RE: Charter Update (Discussion)
Thread-Topic: Charter Update (Discussion)
Thread-Index: AcykyPEFQxTxDW3RRYeCuxFer0A8kgAATUZAAAEvH9A=
Message-ID: <8DCD771BDA4A394E9BCBA8932E83929749CC30BB22@ESESSCMS0363.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E656592F156FE5@GVW1338EXA.americas.hpqcorp.net> <8DCD771BDA4A394E9BCBA8932E83929744C6CDFD3B@ESESSCMS0363.eemea.ericsson.se> <7C6D5E84-76C4-4EB5-852A-5B2EDE451B2D@bgp.nu> <CAG4d1rcr_ejXQTBud81BHa7ahsLieLoPpjnmGwCa_Lc0VA9beQ@mail.gmail.com> <4EB81CAD.4080402@googlemail.com> <CAG4d1rc1nfsjku+gL25SGA=mXwst2omOu0jt80vu8KrrJkB+zA@mail.gmail.com> <8DCD771BDA4A394E9BCBA8932E83929744C6D96B49@ESESSCMS0363.eemea.ericsson.se> <4EB96CBF.7040501@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B813E@ESESSCMS0363.eemea.ericsson.se> <4EBABECC.2060701@cisco.com> <EFAB865EBEFB734CA1FABD543B2E0E2E25147B76EB@ESESSCMS0359.eemea.ericsson.se> <4EBB2563.5010302@cisco.com> <8DCD771BDA4A394E9BCBA8932E83929744D01B85FD@ESESSCMS0363.eemea.ericsson.se> <CAOndX-sCCADE3=oouTvv1gs5P-iE+GEzvGJVvyqaEf=QQhqNYw@mail.gmail.com> <4EC2E42D.2010403@cisco.com> <CAOndX-uwqpCEfmYy9wZHux8G66R5GHcRGo+Wvb54FAPN6A0gjw@mail.gmail.com> <4EC2F0F2.5010400@cisco.com> <D29E470202D67745B61 059870F4	33B54079CD49 6@XMB-RCD-202.cisco.com>	<176F9110-B559-4128-9AD1-5B14385032F5@ericsson.com> <D29E470202D67745B61059870F433B54079CD4A8@XMB-RCD-202.cisco.com>
In-Reply-To: <D29E470202D67745B61059870F433B54079CD4A8@XMB-RCD-202.cisco.com>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>, Sriganesh Kini <sriganesh.kini@ericsson.com>, "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: Thu, 17 Nov 2011 02:43:23 -0000

> > Self-rephrasing - if a solution to provide 100% coverage is=20
> topology=20
> > dependent then it simply doesn't provide 100%, there's no "right
> topology"
> > to apply to every network.
>=20
> No, and I don't think we need to be in the business of=20
> standardizing topologies.  But look at it the other way.  If=20
> a technology provides 100% coverage in some real-world=20
> technologies that people are using today but provides 98% in=20
> other topologies that are also in use, that technology seems=20
> appropriate for the first case.  Whether it's appropriate for=20
> the second is up to the operator of the second.

Well, certainly we should not standardise topologies. :-) Maybe providing g=
uidelines on how to build/extend topologies to be more suitable for non-ful=
l coverage solutions. Work has already been done on this e.g. for LFA.

Up to now, concerns regarding non-full-coverage solutions are the following=
:

1. bidirectional coverage (i.e. when a solution claims e.g. 90% coverage, i=
t could be closer to 80% in reality for practical traffic).

2. Potential struggle by the operator on knowing which of the traffic flow/=
failure cases are covered and which are not covered.

3. Potential struggle by the operator on knowing how exactly coverage chang=
es after topology changes.

4. This has not been mentioned yet, but I do feel that if a proper 100% sol=
ution gets standardised and gets trusted by operators, then in a couple of =
years operator topology design guidelines could be relaxed *somewhat* towar=
ds a *little* less-dense connectivity, as to rely a little bit more on netw=
ork layer redundancy instead of parallel or near-parallel links close to ea=
ch other and quite dense mesh. So it could result in some cost reduction in=
 the future.

5. There is talk on pushing IP/MPLS (LDP) down towards access, where topolo=
gies are not so meshy but a full-coverage solution could work with a few cr=
oss-links.

Background for 4 and 5: non-full-coverage solutions perform the better, the=
 more densly meshed the topology is, while a 100% solution could work also =
on a relatively rare topo.

Andras

From ietf@thomasclausen.org  Thu Nov 17 03:41:54 2011
Return-Path: <ietf@thomasclausen.org>
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 4472421F9A5F for <rtgwg@ietfa.amsl.com>; Thu, 17 Nov 2011 03:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.131
X-Spam-Level: 
X-Spam-Status: No, score=-1.131 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id La9ZMaKkWkXJ for <rtgwg@ietfa.amsl.com>; Thu, 17 Nov 2011 03:41:53 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id B8CBE21F9A5A for <rtgwg@ietf.org>; Thu, 17 Nov 2011 03:41:53 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 821F5CD186 for <rtgwg@ietf.org>; Thu, 17 Nov 2011 03:41:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 8B8A68162F; Thu, 17 Nov 2011 03:41:50 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [172.20.3.103] (unknown [203.69.99.17]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 490878162E; Thu, 17 Nov 2011 03:41:50 -0800 (PST)
Subject: To detail what I said at the mike today when we talked FRF
Content-Transfer-Encoding: quoted-printable
From: Thomas Heide Clausen <ietf@thomasclausen.org>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (9A334)
Message-Id: <28B06B07-5915-44D1-A436-0B82FDFB8784@thomasclausen.org>
Date: Thu, 17 Nov 2011 19:42:20 +0800
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Mime-Version: 1.0 (1.0)
Cc: Herberg Ulrich <ulrich@herberg.name>
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: Thu, 17 Nov 2011 11:41:54 -0000

Dear all,

In the FRR discussion at the mike today, I indicated that some work targetin=
g FRR in LLNs might be worth looking at (and/or bring it into this wg).

The draft I mentioned was this:

      http://tools.ietf.org/html/draft-cardenas-dff-03

I'm not an author of this I-D, but I Cc Ulrich, who is, and who can probably=
 say something much more intelligently than I can about it.

Best,

Thomas


--=20
Thomas Heide Clausen
http://www.thomasclausen.org/

"Payload (noun): wasted bandwidth between headers" (C.Lavenu 2011)


From ulrich@herberg.name  Thu Nov 17 16:00:19 2011
Return-Path: <ulrich@herberg.name>
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 E1DBF11E808E for <rtgwg@ietfa.amsl.com>; Thu, 17 Nov 2011 16:00:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.943
X-Spam-Level: 
X-Spam-Status: No, score=-2.943 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9WoRpi+2prLS for <rtgwg@ietfa.amsl.com>; Thu, 17 Nov 2011 16:00:13 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id E824411E808C for <rtgwg@ietf.org>; Thu, 17 Nov 2011 16:00:12 -0800 (PST)
Received: by wwe5 with SMTP id 5so3459857wwe.13 for <rtgwg@ietf.org>; Thu, 17 Nov 2011 16:00:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UWZEhWLO3x460LWPcp8TJ6EXu8SgT/TBm1AuU9Nm1Kk=; b=uBaxHC9TUigXSjhEgvGa47G8rURCQIj8UnGDdaf7upDdWYiolCNLaKqsk0EHnEtgJm NNwIJd5R5R57qS+XSvVRE7hSbztuaU0L/jesHc1OCMVmtjUgz3kJFzCubfK0HFMZjE3E EmhhWjW2NYecbrTVUz63aiHxnyyeWo7ghwdnc=
MIME-Version: 1.0
Received: by 10.227.197.201 with SMTP id el9mr506827wbb.8.1321574410191; Thu, 17 Nov 2011 16:00:10 -0800 (PST)
Received: by 10.216.88.6 with HTTP; Thu, 17 Nov 2011 16:00:10 -0800 (PST)
In-Reply-To: <28B06B07-5915-44D1-A436-0B82FDFB8784@thomasclausen.org>
References: <28B06B07-5915-44D1-A436-0B82FDFB8784@thomasclausen.org>
Date: Fri, 18 Nov 2011 08:00:10 +0800
Message-ID: <CAK=bVC950LyMtZHN-ki1yEsz61xa_=C4r-0rTepVpZ7mpiaxGA@mail.gmail.com>
Subject: Re: To detail what I said at the mike today when we talked FRF
From: Ulrich Herberg <ulrich@herberg.name>
To: Thomas Heide Clausen <ietf@thomasclausen.org>
Content-Type: multipart/alternative; boundary=001517478b124382ee04b1f7053e
Cc: "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: Fri, 18 Nov 2011 00:00:20 -0000

--001517478b124382ee04b1f7053e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

Our draft basically describes a data forwarding mechanism, currently
specified for 6lowpan (but it would be doable to add the same mechanism for
IP as well). The idea is that a node first tries to forward a data packet
along the route proposed by the routing protocol. However, if the topology
has changed or a link has become very unstable, instead of dropping the
packet, the node tries to find alternate paths towards the destination by
applying a "depth-first search" in the network, possibly updating the route
cost in the routing protocol. This allows for increasing the delivery ratio
until the route has been corrected by the routing protocol. The advantage
is that one requires fewer updates of the control plane, which may have
negative effects on an already unstable topology (e.g. by flooding RREQ or
LSAs).
We have done a number of simulations and also real tests with several
hundred nodes at Fujitsu which showed a performance improvement. If you are
interested in reading the draft, I would appreciate any kind of feedback.

I-D
http://tools.ietf.org/html/draft-cardenas-dff

We have code both for the real testbed and for the simulator. Moreover, I
am currently developing open source code.

Some results in a paper (not yet available, but I will see if I can spin
out a research report and upload that somewhere with public access)
*Comparison of Data Forwarding Mechanisms for AMI Networks.* Sandra
C=E9spedes, Alvaro A. C=E1rdenas, Tadashige Iwao. 2012 IEEE Innovative Smar=
t
Grid Technologies Conference (ISGT). January 17-19, 2012.

Best regards
Ulrich

On Thu, Nov 17, 2011 at 7:42 PM, Thomas Heide Clausen <
ietf@thomasclausen.org> wrote:

>
> Dear all,
>
> In the FRR discussion at the mike today, I indicated that some work
> targeting FRR in LLNs might be worth looking at (and/or bring it into thi=
s
> wg).
>
> The draft I mentioned was this:
>
>      http://tools.ietf.org/html/draft-cardenas-dff-03
>
> I'm not an author of this I-D, but I Cc Ulrich, who is, and who can
> probably say something much more intelligently than I can about it.
>
> Best,
>
> Thomas
>
>
> --
> Thomas Heide Clausen
> http://www.thomasclausen.org/
>
> "Payload (noun): wasted bandwidth between headers" (C.Lavenu 2011)
>
>

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

Hi all,<br><br>Our draft basically describes a data forwarding mechanism, c=
urrently specified for=20
6lowpan (but it would be doable to add the same mechanism for IP as=20
well). The idea is that a node first tries to forward a data packet=20
along the route proposed by the routing protocol. However, if the=20
topology has changed or a link has become very unstable, instead of=20
dropping the packet, the node tries to find alternate paths towards the=20
destination by applying a &quot;depth-first search&quot; in the network, po=
ssibly=20
updating the route cost in the routing protocol. This allows for=20
increasing the delivery ratio until the route has been corrected by the=20
routing protocol. The advantage is that one requires fewer updates of=20
the control plane, which may have negative effects on an already=20
unstable topology (e.g. by flooding RREQ or LSAs). <br>
We have done a number of simulations and also real tests with several=20
hundred nodes at Fujitsu which showed a performance improvement. If you are=
=20
interested in reading the draft, I would appreciate any kind of=20
feedback.<br><br>I-D<br>
<a href=3D"http://tools.ietf.org/html/draft-cardenas-dff" target=3D"_blank"=
>http://tools.ietf.org/html/draft-cardenas-dff</a><br><br>We have code both=
 for the real testbed and for the simulator. Moreover, I am currently devel=
oping open source code.<br>
<br>Some results in a paper (not yet available, but I will see if I can spi=
n out a research report and upload that somewhere with public access)<br><b=
>Comparison of Data Forwarding Mechanisms for AMI=20
Networks.</b>  Sandra C=E9spedes, Alvaro A. C=E1rdenas,
Tadashige Iwao. 2012 IEEE Innovative Smart Grid Technologies
Conference (ISGT). January 17-19, 2012.

<br><br>Best regards<br><font color=3D"#888888">Ulrich </font><br><br><div =
class=3D"gmail_quote">On Thu, Nov 17, 2011 at 7:42 PM, Thomas Heide Clausen=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@thomasclausen.org" target=3D"=
_blank">ietf@thomasclausen.org</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Dear all,<br>
<br>
In the FRR discussion at the mike today, I indicated that some work targeti=
ng FRR in LLNs might be worth looking at (and/or bring it into this wg).<br=
>
<br>
The draft I mentioned was this:<br>
<br>
 =A0 =A0 =A0<a href=3D"http://tools.ietf.org/html/draft-cardenas-dff-03" ta=
rget=3D"_blank">http://tools.ietf.org/html/draft-cardenas-dff-03</a><br>
<br>
I&#39;m not an author of this I-D, but I Cc Ulrich, who is, and who can pro=
bably say something much more intelligently than I can about it.<br>
<br>
Best,<br>
<br>
Thomas<br>
<font color=3D"#888888"><br>
<br>
--<br>
Thomas Heide Clausen<br>
<a href=3D"http://www.thomasclausen.org/" target=3D"_blank">http://www.thom=
asclausen.org/</a><br>
<br>
&quot;Payload (noun): wasted bandwidth between headers&quot; (C.Lavenu 2011=
)<br>
<br>
</font></blockquote></div><br>

--001517478b124382ee04b1f7053e--

From akatlas@gmail.com  Thu Nov 17 20:43:11 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 268CF11E809D for <rtgwg@ietfa.amsl.com>; Thu, 17 Nov 2011 20:43:11 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uObuCHlb-ieM for <rtgwg@ietfa.amsl.com>; Thu, 17 Nov 2011 20:43:10 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4C411E808B for <rtgwg@ietf.org>; Thu, 17 Nov 2011 20:43:10 -0800 (PST)
Received: by iaeo4 with SMTP id o4so3843814iae.31 for <rtgwg@ietf.org>; Thu, 17 Nov 2011 20:43:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tlr0sD0FbuP3qj0Rh9nD8fKBfEa3iJj23eIjUQCnKfk=; b=Q6zV68RbUT5BE1NVbA39LNrpsI3T05OGfCfRmo6ntnm21dePcG90DprkrCrX3dd6HW Gu3haInFTcsXQ/qqOAf/7RVvZZ1MOPpDI16PH7rvvo4/hjSw10uC/OPVDbK7vlD+xCNH U1yXYuBd+Vlc2g/5huNawtEEY2s1ELEBV4jTE=
MIME-Version: 1.0
Received: by 10.43.53.1 with SMTP id vo1mr1073638icb.2.1321591388102; Thu, 17 Nov 2011 20:43:08 -0800 (PST)
Received: by 10.50.184.229 with HTTP; Thu, 17 Nov 2011 20:43:08 -0800 (PST)
In-Reply-To: <CAK=bVC950LyMtZHN-ki1yEsz61xa_=C4r-0rTepVpZ7mpiaxGA@mail.gmail.com>
References: <28B06B07-5915-44D1-A436-0B82FDFB8784@thomasclausen.org> <CAK=bVC950LyMtZHN-ki1yEsz61xa_=C4r-0rTepVpZ7mpiaxGA@mail.gmail.com>
Date: Thu, 17 Nov 2011 23:43:08 -0500
Message-ID: <CAG4d1re_zsVBUAPbt6dfaOQhngGKJOM+v+ho5eGLRviriCw-xg@mail.gmail.com>
Subject: Re: To detail what I said at the mike today when we talked FRF
From: Alia Atlas <akatlas@gmail.com>
To: Ulrich Herberg <ulrich@herberg.name>
Content-Type: multipart/alternative; boundary=bcaec529958939dfa804b1faf93a
Cc: "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: Fri, 18 Nov 2011 04:43:11 -0000

--bcaec529958939dfa804b1faf93a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I think that it would be very beneficial to discuss this work in rtgwg.
 There may be some experience we can bring to bear.

I personally am not familiar with the different characteristics of 6lowpan
compared to IP.  Could you summarize or send a pointer?

Regards,
Alia

On Friday, November 18, 2011, Ulrich Herberg <ulrich@herberg.name> wrote:
> Hi all,
>
> Our draft basically describes a data forwarding mechanism, currently
specified for 6lowpan (but it would be doable to add the same mechanism for
IP as well). The idea is that a node first tries to forward a data packet
along the route proposed by the routing protocol. However, if the topology
has changed or a link has become very unstable, instead of dropping the
packet, the node tries to find alternate paths towards the destination by
applying a "depth-first search" in the network, possibly updating the route
cost in the routing protocol. This allows for increasing the delivery ratio
until the route has been corrected by the routing protocol. The advantage
is that one requires fewer updates of the control plane, which may have
negative effects on an already unstable topology (e.g. by flooding RREQ or
LSAs).
> We have done a number of simulations and also real tests with several
hundred nodes at Fujitsu which showed a performance improvement. If you are
interested in reading the draft, I would appreciate any kind of feedback.
>
> I-D
> http://tools.ietf.org/html/draft-cardenas-dff
>
> We have code both for the real testbed and for the simulator. Moreover, I
am currently developing open source code.
>
> Some results in a paper (not yet available, but I will see if I can spin
out a research report and upload that somewhere with public access)
> Comparison of Data Forwarding Mechanisms for AMI Networks. Sandra
C=E9spedes, Alvaro A. C=E1rdenas, Tadashige Iwao. 2012 IEEE Innovative Smar=
t
Grid Technologies Conference (ISGT). January 17-19, 2012.
>
> Best regards
> Ulrich
>
> On Thu, Nov 17, 2011 at 7:42 PM, Thomas Heide Clausen <
ietf@thomasclausen.org> wrote:
>>
>> Dear all,
>>
>> In the FRR discussion at the mike today, I indicated that some work
targeting FRR in LLNs might be worth looking at (and/or bring it into this
wg).
>>
>> The draft I mentioned was this:
>>
>>      http://tools.ietf.org/html/draft-cardenas-dff-03
>>
>> I'm not an author of this I-D, but I Cc Ulrich, who is, and who can
probably say something much more intelligently than I can about it.
>>
>> Best,
>>
>> Thomas
>>
>>
>> --
>> Thomas Heide Clausen
>> http://www.thomasclausen.org/
>>
>> "Payload (noun): wasted bandwidth between headers" (C.Lavenu 2011)
>>
>
>

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

I think that it would be very beneficial to discuss this work in rtgwg. =A0=
There may be some experience we can bring to bear.<br><br>I personally am n=
ot familiar with the different characteristics of 6lowpan compared to IP. =
=A0Could you summarize or send a pointer?<br>
<br>Regards,<br>Alia<br><br>On Friday, November 18, 2011, Ulrich Herberg &l=
t;<a href=3D"mailto:ulrich@herberg.name">ulrich@herberg.name</a>&gt; wrote:=
<br>&gt; Hi all,<br>&gt;<br>&gt; Our draft basically describes a data forwa=
rding mechanism, currently specified for 6lowpan (but it would be doable to=
 add the same mechanism for IP as well). The idea is that a node first trie=
s to forward a data packet along the route proposed by the routing protocol=
. However, if the topology has changed or a link has become very unstable, =
instead of dropping the packet, the node tries to find alternate paths towa=
rds the destination by applying a &quot;depth-first search&quot; in the net=
work, possibly updating the route cost in the routing protocol. This allows=
 for increasing the delivery ratio until the route has been corrected by th=
e routing protocol. The advantage is that one requires fewer updates of the=
 control plane, which may have negative effects on an already unstable topo=
logy (e.g. by flooding RREQ or LSAs).<br>
&gt; We have done a number of simulations and also real tests with several =
hundred nodes at Fujitsu which showed a performance improvement. If you are=
 interested in reading the draft, I would appreciate any kind of feedback.<=
br>
&gt;<br>&gt; I-D<br>&gt; <a href=3D"http://tools.ietf.org/html/draft-carden=
as-dff">http://tools.ietf.org/html/draft-cardenas-dff</a><br>&gt;<br>&gt; W=
e have code both for the real testbed and for the simulator. Moreover, I am=
 currently developing open source code.<br>
&gt;<br>&gt; Some results in a paper (not yet available, but I will see if =
I can spin out a research report and upload that somewhere with public acce=
ss)<br>&gt; Comparison of Data Forwarding Mechanisms for AMI Networks. Sand=
ra C=E9spedes, Alvaro A. C=E1rdenas, Tadashige Iwao. 2012 IEEE Innovative S=
mart Grid Technologies Conference (ISGT). January 17-19, 2012.<br>
&gt;<br>&gt; Best regards<br>&gt; Ulrich<br>&gt;<br>&gt; On Thu, Nov 17, 20=
11 at 7:42 PM, Thomas Heide Clausen &lt;<a href=3D"mailto:ietf@thomasclause=
n.org">ietf@thomasclausen.org</a>&gt; wrote:<br>&gt;&gt;<br>&gt;&gt; Dear a=
ll,<br>
&gt;&gt;<br>&gt;&gt; In the FRR discussion at the mike today, I indicated t=
hat some work targeting FRR in LLNs might be worth looking at (and/or bring=
 it into this wg).<br>&gt;&gt;<br>&gt;&gt; The draft I mentioned was this:<=
br>
&gt;&gt;<br>&gt;&gt; =A0 =A0 =A0<a href=3D"http://tools.ietf.org/html/draft=
-cardenas-dff-03">http://tools.ietf.org/html/draft-cardenas-dff-03</a><br>&=
gt;&gt;<br>&gt;&gt; I&#39;m not an author of this I-D, but I Cc Ulrich, who=
 is, and who can probably say something much more intelligently than I can =
about it.<br>
&gt;&gt;<br>&gt;&gt; Best,<br>&gt;&gt;<br>&gt;&gt; Thomas<br>&gt;&gt;<br>&g=
t;&gt;<br>&gt;&gt; --<br>&gt;&gt; Thomas Heide Clausen<br>&gt;&gt; <a href=
=3D"http://www.thomasclausen.org/">http://www.thomasclausen.org/</a><br>&gt=
;&gt;<br>
&gt;&gt; &quot;Payload (noun): wasted bandwidth between headers&quot; (C.La=
venu 2011)<br>&gt;&gt;<br>&gt;<br>&gt;

--bcaec529958939dfa804b1faf93a--

From ulrich@herberg.name  Thu Nov 17 23:31:25 2011
Return-Path: <ulrich@herberg.name>
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 B7D4F21F9504 for <rtgwg@ietfa.amsl.com>; Thu, 17 Nov 2011 23:31:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.946
X-Spam-Level: 
X-Spam-Status: No, score=-2.946 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ZHh-awdTYEq for <rtgwg@ietfa.amsl.com>; Thu, 17 Nov 2011 23:31:24 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id F2B7D21F94F8 for <rtgwg@ietf.org>; Thu, 17 Nov 2011 23:31:23 -0800 (PST)
Received: by wwe5 with SMTP id 5so3895421wwe.13 for <rtgwg@ietf.org>; Thu, 17 Nov 2011 23:31:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8OD1Viy+NCbZZWjlP6vcX93XVJ/XEtZyI4F0OTfUQus=; b=A+Y9l3wguaEf7V+bDK37p7w4tWiwjdx4izIQ1MgSoa/Czrg3DDXMNoxq2vJjSvmx4l xAomCi05DL0+XJZanmOun2T6Gf+IrRWw9A54T3XzbEinCOguWF3ddGcQOpUR7sKsQ1y6 RXXU+Ik7xeJ88OzjnwCMD9MrznbU6jBbiAftQ=
MIME-Version: 1.0
Received: by 10.227.206.213 with SMTP id fv21mr1199654wbb.8.1321601480996; Thu, 17 Nov 2011 23:31:20 -0800 (PST)
Received: by 10.216.88.6 with HTTP; Thu, 17 Nov 2011 23:31:20 -0800 (PST)
In-Reply-To: <CAG4d1re_zsVBUAPbt6dfaOQhngGKJOM+v+ho5eGLRviriCw-xg@mail.gmail.com>
References: <28B06B07-5915-44D1-A436-0B82FDFB8784@thomasclausen.org> <CAK=bVC950LyMtZHN-ki1yEsz61xa_=C4r-0rTepVpZ7mpiaxGA@mail.gmail.com> <CAG4d1re_zsVBUAPbt6dfaOQhngGKJOM+v+ho5eGLRviriCw-xg@mail.gmail.com>
Date: Fri, 18 Nov 2011 15:31:20 +0800
Message-ID: <CAK=bVC_9tkgWv2ymDVrCrgz2WuaoNMPitwoqjgGNaioWxyKNLA@mail.gmail.com>
Subject: Re: To detail what I said at the mike today when we talked FRF
From: Ulrich Herberg <ulrich@herberg.name>
To: Alia Atlas <akatlas@gmail.com>
Content-Type: multipart/alternative; boundary=0015174c0f32cf397304b1fd5288
Cc: "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: Fri, 18 Nov 2011 07:31:25 -0000

--0015174c0f32cf397304b1fd5288
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Alia,

it's great to hear that the work is of interest for the WG.

Essentially, the current specification is a mesh-under mechanism (i.e. on
layer 2.5), using the 6lowpan headers, as that is where we got our
experience from and have implementations. However, I see no problem of
adding a layer of abstraction in the draft making it possible to run the
mechanism on both layer 2.5 (6lowpan) and layer 3 (IPv6). The 6lowpan
architecture is well described in RFC4944, and our current draft relies on
that specification.

I found the link to the paper I mentioned in my first email:
http://www.flacp.fujitsulabs.com/~cardenas/Papers/forwarding-comparison-2.p=
df

I will also try to ask my management if I can disclose our results from the
real deployment.

Regards
Ulrich

On Fri, Nov 18, 2011 at 12:43 PM, Alia Atlas <akatlas@gmail.com> wrote:

> I think that it would be very beneficial to discuss this work in rtgwg.
>  There may be some experience we can bring to bear.
>
> I personally am not familiar with the different characteristics of 6lowpa=
n
> compared to IP.  Could you summarize or send a pointer?
>
> Regards,
> Alia
>
>
> On Friday, November 18, 2011, Ulrich Herberg <ulrich@herberg.name> wrote:
> > Hi all,
> >
> > Our draft basically describes a data forwarding mechanism, currently
> specified for 6lowpan (but it would be doable to add the same mechanism f=
or
> IP as well). The idea is that a node first tries to forward a data packet
> along the route proposed by the routing protocol. However, if the topolog=
y
> has changed or a link has become very unstable, instead of dropping the
> packet, the node tries to find alternate paths towards the destination by
> applying a "depth-first search" in the network, possibly updating the rou=
te
> cost in the routing protocol. This allows for increasing the delivery rat=
io
> until the route has been corrected by the routing protocol. The advantage
> is that one requires fewer updates of the control plane, which may have
> negative effects on an already unstable topology (e.g. by flooding RREQ o=
r
> LSAs).
> > We have done a number of simulations and also real tests with several
> hundred nodes at Fujitsu which showed a performance improvement. If you a=
re
> interested in reading the draft, I would appreciate any kind of feedback.
> >
> > I-D
> > http://tools.ietf.org/html/draft-cardenas-dff
> >
> > We have code both for the real testbed and for the simulator. Moreover,
> I am currently developing open source code.
> >
> > Some results in a paper (not yet available, but I will see if I can spi=
n
> out a research report and upload that somewhere with public access)
> > Comparison of Data Forwarding Mechanisms for AMI Networks. Sandra
> C=E9spedes, Alvaro A. C=E1rdenas, Tadashige Iwao. 2012 IEEE Innovative Sm=
art
> Grid Technologies Conference (ISGT). January 17-19, 2012.
> >
> > Best regards
> > Ulrich
> >
> > On Thu, Nov 17, 2011 at 7:42 PM, Thomas Heide Clausen <
> ietf@thomasclausen.org> wrote:
> >>
> >> Dear all,
> >>
> >> In the FRR discussion at the mike today, I indicated that some work
> targeting FRR in LLNs might be worth looking at (and/or bring it into thi=
s
> wg).
> >>
> >> The draft I mentioned was this:
> >>
> >>      http://tools.ietf.org/html/draft-cardenas-dff-03
> >>
> >> I'm not an author of this I-D, but I Cc Ulrich, who is, and who can
> probably say something much more intelligently than I can about it.
> >>
> >> Best,
> >>
> >> Thomas
> >>
> >>
> >> --
> >> Thomas Heide Clausen
> >> http://www.thomasclausen.org/
> >>
> >> "Payload (noun): wasted bandwidth between headers" (C.Lavenu 2011)
> >>
> >
> >
>

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

Alia,<br><br>it&#39;s great to hear that the work is of interest for the WG=
. <br><br>Essentially, the current specification is a mesh-under mechanism =
(i.e. on layer 2.5), using the 6lowpan headers, as that is where we got our=
 experience from and have implementations. However, I see no problem of add=
ing a layer of abstraction in the draft making it possible to run the mecha=
nism on both layer 2.5 (6lowpan) and layer 3 (IPv6). The 6lowpan architectu=
re is well described in RFC4944, and our current draft relies on that speci=
fication.<br>
<br>I found the link to the paper I mentioned in my first email:<br><a href=
=3D"http://www.flacp.fujitsulabs.com/~cardenas/Papers/forwarding-comparison=
-2.pdf">http://www.flacp.fujitsulabs.com/~cardenas/Papers/forwarding-compar=
ison-2.pdf</a><br>
<br>I will also try to ask my management if I can disclose our results from=
 the real deployment. <br><br>Regards<br>Ulrich<br><br><div class=3D"gmail_=
quote">On Fri, Nov 18, 2011 at 12:43 PM, Alia Atlas <span dir=3D"ltr">&lt;<=
a href=3D"mailto:akatlas@gmail.com">akatlas@gmail.com</a>&gt;</span> wrote:=
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">I think that it would be very beneficial to=
 discuss this work in rtgwg. =A0There may be some experience we can bring t=
o bear.<br>
<br>I personally am not familiar with the different characteristics of 6low=
pan compared to IP. =A0Could you summarize or send a pointer?<br>
<br>Regards,<br><font color=3D"#888888">Alia</font><div><div></div><div cla=
ss=3D"h5"><br><br>On Friday, November 18, 2011, Ulrich Herberg &lt;<a href=
=3D"mailto:ulrich@herberg.name" target=3D"_blank">ulrich@herberg.name</a>&g=
t; wrote:<br>
&gt; Hi all,<br>&gt;<br>&gt; Our draft basically describes a data forwardin=
g mechanism, currently specified for 6lowpan (but it would be doable to add=
 the same mechanism for IP as well). The idea is that a node first tries to=
 forward a data packet along the route proposed by the routing protocol. Ho=
wever, if the topology has changed or a link has become very unstable, inst=
ead of dropping the packet, the node tries to find alternate paths towards =
the destination by applying a &quot;depth-first search&quot; in the network=
, possibly updating the route cost in the routing protocol. This allows for=
 increasing the delivery ratio until the route has been corrected by the ro=
uting protocol. The advantage is that one requires fewer updates of the con=
trol plane, which may have negative effects on an already unstable topology=
 (e.g. by flooding RREQ or LSAs).<br>

&gt; We have done a number of simulations and also real tests with several =
hundred nodes at Fujitsu which showed a performance improvement. If you are=
 interested in reading the draft, I would appreciate any kind of feedback.<=
br>

&gt;<br>&gt; I-D<br>&gt; <a href=3D"http://tools.ietf.org/html/draft-carden=
as-dff" target=3D"_blank">http://tools.ietf.org/html/draft-cardenas-dff</a>=
<br>&gt;<br>&gt; We have code both for the real testbed and for the simulat=
or. Moreover, I am currently developing open source code.<br>

&gt;<br>&gt; Some results in a paper (not yet available, but I will see if =
I can spin out a research report and upload that somewhere with public acce=
ss)<br>&gt; Comparison of Data Forwarding Mechanisms for AMI Networks. Sand=
ra C=E9spedes, Alvaro A. C=E1rdenas, Tadashige Iwao. 2012 IEEE Innovative S=
mart Grid Technologies Conference (ISGT). January 17-19, 2012.<br>

&gt;<br>&gt; Best regards<br>&gt; Ulrich<br>&gt;<br>&gt; On Thu, Nov 17, 20=
11 at 7:42 PM, Thomas Heide Clausen &lt;<a href=3D"mailto:ietf@thomasclause=
n.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt; wrote:<br>&gt;&gt;<=
br>
&gt;&gt; Dear all,<br>
&gt;&gt;<br>&gt;&gt; In the FRR discussion at the mike today, I indicated t=
hat some work targeting FRR in LLNs might be worth looking at (and/or bring=
 it into this wg).<br>&gt;&gt;<br>&gt;&gt; The draft I mentioned was this:<=
br>

&gt;&gt;<br>&gt;&gt; =A0 =A0 =A0<a href=3D"http://tools.ietf.org/html/draft=
-cardenas-dff-03" target=3D"_blank">http://tools.ietf.org/html/draft-carden=
as-dff-03</a><br>&gt;&gt;<br>&gt;&gt; I&#39;m not an author of this I-D, bu=
t I Cc Ulrich, who is, and who can probably say something much more intelli=
gently than I can about it.<br>

&gt;&gt;<br>&gt;&gt; Best,<br>&gt;&gt;<br>&gt;&gt; Thomas<br>&gt;&gt;<br>&g=
t;&gt;<br>&gt;&gt; --<br>&gt;&gt; Thomas Heide Clausen<br>&gt;&gt; <a href=
=3D"http://www.thomasclausen.org/" target=3D"_blank">http://www.thomasclaus=
en.org/</a><br>
&gt;&gt;<br>
&gt;&gt; &quot;Payload (noun): wasted bandwidth between headers&quot; (C.La=
venu 2011)<br>&gt;&gt;<br>&gt;<br>&gt;
</div></div></blockquote></div><br>

--0015174c0f32cf397304b1fd5288--

From alvaro.retana@hp.com  Mon Nov 28 07:55:45 2011
Return-Path: <alvaro.retana@hp.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 1D97B21F8CFC for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 07:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oSUbAWrb-Fot for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 07:55:44 -0800 (PST)
Received: from g1t0028.austin.hp.com (g1t0028.austin.hp.com [15.216.28.35]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5F421F8CE9 for <rtgwg@ietf.org>; Mon, 28 Nov 2011 07:55:44 -0800 (PST)
Received: from G5W2206G.americas.hpqcorp.net (g5w2206g.atlanta.hp.com [16.228.43.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g1t0028.austin.hp.com (Postfix) with ESMTPS id A47AC1C3C7 for <rtgwg@ietf.org>; Mon, 28 Nov 2011 15:55:43 +0000 (UTC)
Received: from G2W0893.americas.hpqcorp.net (16.238.89.28) by G5W2206G.americas.hpqcorp.net (16.228.43.185) with Microsoft SMTP Server (TLS) id 14.1.289.1; Mon, 28 Nov 2011 15:55:02 +0000
Received: from GVW1338EXA.americas.hpqcorp.net ([16.236.29.12]) by G2W0893.americas.hpqcorp.net ([16.238.89.28]) with mapi; Mon, 28 Nov 2011 15:55:01 +0000
From: "Retana, Alvaro" <alvaro.retana@hp.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Mon, 28 Nov 2011 15:54:59 +0000
Subject: IETF 82 Minutes
Thread-Topic: IETF 82 Minutes
Thread-Index: Acyt5hUxIifISUpJT1W79sgw2C+A0Q==
Message-ID: <24646CE17826CF4A8DF71F9856C7E65659572B63D4@GVW1338EXA.americas.hpqcorp.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-hashedpuzzle: Y8I= AxzS BMw5 BPSU Bna+ COPH Cztc C2Ig DHz4 DJxE EIXo GB6b GR9l Gxq2 HBKh HVvH; 1; cgB0AGcAdwBnAEAAaQBlAHQAZgAuAG8AcgBnAA==; Sosha1_v1; 7; {4A8BCA05-2631-4AC7-9FB7-264CC8E8B7D2}; YQBsAHYAYQByAG8ALgByAGUAdABhAG4AYQBAAGgAcAAuAGMAbwBtAA==; Mon, 28 Nov 2011 15:54:59 GMT;SQBFAFQARgAgADgAMgAgAE0AaQBuAHUAdABlAHMA
x-cr-puzzleid: {4A8BCA05-2631-4AC7-9FB7-264CC8E8B7D2}
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_24646CE17826CF4A8DF71F9856C7E65659572B63D4GVW1338EXAame_"
MIME-Version: 1.0
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, 28 Nov 2011 15:55:45 -0000

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

FYI

We just published the minutes from Taipei:  http://www.ietf.org/proceedings=
/82/minutes/rtgwg.txt

Many thanks to John Scudder for being our scribe.

Alvaro.


--_000_24646CE17826CF4A8DF71F9856C7E65659572B63D4GVW1338EXAame_
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-micr=
osoft-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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>FYI<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We just pu=
blished the minutes from Taipei:&nbsp; <a href=3D"http://www.ietf.org/proce=
edings/82/minutes/rtgwg.txt">http://www.ietf.org/proceedings/82/minutes/rtg=
wg.txt</a><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>Many thanks to John Scudder for being our scribe.<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Alvaro.<o:=
p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_24646CE17826CF4A8DF71F9856C7E65659572B63D4GVW1338EXAame_--

From alvaro.retana@hp.com  Mon Nov 28 07:56:14 2011
Return-Path: <alvaro.retana@hp.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 DC89A21F8A6C for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 07:56:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PFKkXW0IRigV for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 07:56:13 -0800 (PST)
Received: from g1t0028.austin.hp.com (g1t0028.austin.hp.com [15.216.28.35]) by ietfa.amsl.com (Postfix) with ESMTP id E145A21F8C1C for <rtgwg@ietf.org>; Mon, 28 Nov 2011 07:56:12 -0800 (PST)
Received: from G2W1953G.americas.hpqcorp.net (gvt0525.austin.hp.com [16.238.8.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g1t0028.austin.hp.com (Postfix) with ESMTPS id 7A00F1C3A6; Mon, 28 Nov 2011 15:56:12 +0000 (UTC)
Received: from G1W1331.americas.hpqcorp.net (16.236.60.36) by G2W1953G.americas.hpqcorp.net (16.238.8.185) with Microsoft SMTP Server (TLS) id 14.1.289.1; Mon, 28 Nov 2011 15:55:56 +0000
Received: from GVW1338EXA.americas.hpqcorp.net ([16.236.29.12]) by G1W1331.americas.hpqcorp.net ([16.236.60.36]) with mapi; Mon, 28 Nov 2011 15:55:56 +0000
From: "Retana, Alvaro" <alvaro.retana@hp.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Date: Mon, 28 Nov 2011 15:55:54 +0000
Subject: Updated rtgwg Charter
Thread-Topic: Updated rtgwg Charter
Thread-Index: Acyt5jYQC6668Sw+TBSoJkrEFnQU2w==
Message-ID: <24646CE17826CF4A8DF71F9856C7E65659572B63D6@GVW1338EXA.americas.hpqcorp.net>
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_24646CE17826CF4A8DF71F9856C7E65659572B63D6GVW1338EXAame_"
MIME-Version: 1.0
Cc: Alia Atlas <akatlas@juniper.net>, "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, 28 Nov 2011 15:56:15 -0000

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

Stewart/Adrian:

I included below the updated rtgwg charter for your final review before ask=
ing the IESG for publication.

The charter has been discussed in the mailing list (cc'd) and then at the l=
ast in-person meeting in Taipei.

Thanks!

Alvaro.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Working Group Name:
                Routing Area Working Group (rtgwg)

IETF Area:
                Routing Area

Chairs:
                Alia Atlas <akatlas@gmail.com<mailto:akatlas@gmail.com>>
                Alvaro Retana <alvaro.retana@hp.com<mailto:alvaro.retana@hp=
.com>>

Routing Area Directors:
                Stewart Bryant <stbryant@cisco.com<mailto:stbryant@cisco.co=
m>>
                Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.=
uk>>

Responsible Area Director:
                Stewart Bryant <stbryant@cisco.com<mailto:stbryant@cisco.co=
m>>

Mailing List:
                Address:rtgwg@ietf.org<mailto:rtgwg@ietf.org>
To Subscribe:rtgwg-request@ietf.org<mailto:rtgwg-request@ietf.org>
Archive: http://www.ietf.org/mail-archive/web/rtgwg/

Description of the Working Group:

The Routing area receives occasional proposals for the development and
publication of RFCs dealing with routing topics, but for which the
required work does not yet rise to the level where a new working group is
justified, yet the topic does not fit with an existing working group,
and it is either not ready for a BOF or a single BOF would not
provide the time to ensure a mature proposal. The RTGWG will serve as
the forum for developing these types of proposals.

The RTGWG also focuses on enhancements to hop-by-hop distributed routing
related to fast-reroute and loop-free convergence.  A specific goal of
fast-reroute mechanisms is to provide up to complete coverage when the
potential failure would not partition the network.  All work in this
area should be specifically evaluated by the WG in terms of practicality
and applicability to deployed networks.

The RTGWG mailing list will be used to discuss the proposals as they
arise. The working group will meet if there are one or more active
proposals that require discussion.

The working group milestones will be updated as needed to reflect the
proposals currently being worked on and the target dates for their
completion. New milestones will be first reviewed by the IESG. The
working group will be on-going as long as the ADs believe it serves a
useful purpose.

Goals and Milestones:

Mar 2012             Submit IP Fast Re-Route Using Not-via Addresses to IES=
G for publication as Informational
Nov 2012             Submit Composite-Link Requirements to IESG for publica=
tion as Informational
Nov 2012             Submit Ordered FIB architecture to IESG for publicatio=
n as Informational
Nov 2012             Submit initial Internet Draft on Multicast IP Fast Rer=
oute Architecture
Nov 2012             Submit Composite-Link Framework to IESG for publicatio=
n as Informational
Apr 2013              Submit specification on Advanced IP Fast Reroute mech=
anism to  IESG for publication as Proposed Standard

--_000_24646CE17826CF4A8DF71F9856C7E65659572B63D6GVW1338EXAame_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.square
	{mso-style-name:square;}
.MsoChpDefault
	{mso-style-type:export-only;}
@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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Stewart/Adrian:<=
o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorma=
l>I included below the updated rtgwg charter for your final review before a=
sking the IESG for publication.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p><p class=3DMsoNormal>The charter has been discussed in the mai=
ling list (cc&#8217;d) and then at the last in-person meeting in Taipei.<o:=
p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>=
Thanks!<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3D=
MsoNormal>Alvaro.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
p class=3DMsoNormal>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoN=
ormal>Working Group Name: <o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; Routing Area Working Group (rtgwg)<o:p></o:p></p><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p><p class=3DMsoNormal>IETF Area:<o:p></o:p></p><p class=
=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; Routing Area<o:p></o:p></p><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Chairs:<o:p></o:p></p><p class=
=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; <span lang=3DES-CR>Alia Atlas &lt;</span><a hr=
ef=3D"mailto:akatlas@gmail.com"><span lang=3DES-CR>akatlas@gmail.com</span>=
</a><span lang=3DES-CR>&gt;<o:p></o:p></span></p><p class=3DMsoNormal><span=
 lang=3DES-CR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alvaro Retana &lt;<a href=3D"mailto:alvaro.re=
tana@hp.com">alvaro.retana@hp.com</a>&gt;<o:p></o:p></span></p><p class=3DM=
soNormal><span lang=3DES-CR><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorma=
l><span lang=3DES-CR>Routing Area Directors:<o:p></o:p></span></p><p class=
=3DMsoNormal><span lang=3DES-CR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Stewart Bryant &lt;<=
a href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a>&gt;<o:p></o:p><=
/p><p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Adrian Farrel &lt;<a href=3D"mailto=
:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt;<o:p></o:p></p><p class=3D=
MsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Responsible Area Direct=
or:<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stewart Bryant &lt;<=
a href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</a>&gt;<o:p></o:p><=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Mailing L=
ist:<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Address:<a href=3D"=
mailto:rtgwg@ietf.org">rtgwg@ietf.org</a> <o:p></o:p></p><p class=3DMsoNorm=
al style=3D'text-indent:.5in'>To Subscribe:<a href=3D"mailto:rtgwg-request@=
ietf.org">rtgwg-request@ietf.org</a> <o:p></o:p></p><p class=3DMsoNormal st=
yle=3D'text-indent:.5in'>Archive: <a href=3D"http://www.ietf.org/mail-archi=
ve/web/rtgwg/">http://www.ietf.org/mail-archive/web/rtgwg/</a><o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Descriptio=
n of the Working Group:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><p class=3DMsoNormal>The Routing area receives occasional proposals fo=
r the development and <o:p></o:p></p><p class=3DMsoNormal>publication of RF=
Cs dealing with routing topics, but for which the <o:p></o:p></p><p class=
=3DMsoNormal>required work does not yet rise to the level where a new worki=
ng group is <o:p></o:p></p><p class=3DMsoNormal>justified, yet the topic do=
es not fit with an existing working group, <o:p></o:p></p><p class=3DMsoNor=
mal>and it is either not ready for a BOF or a single BOF would not <o:p></o=
:p></p><p class=3DMsoNormal>provide the time to ensure a mature proposal. T=
he RTGWG will serve as <o:p></o:p></p><p class=3DMsoNormal>the forum for de=
veloping these types of proposals.<o:p></o:p></p><p class=3DMsoNormal>&nbsp=
;<o:p></o:p></p><p class=3DMsoNormal>The RTGWG also focuses on enhancements=
 to hop-by-hop distributed routing <o:p></o:p></p><p class=3DMsoNormal>rela=
ted to fast-reroute and loop-free convergence.&nbsp; A specific goal of <o:=
p></o:p></p><p class=3DMsoNormal>fast-reroute mechanisms is to provide up t=
o complete coverage when the <o:p></o:p></p><p class=3DMsoNormal>potential =
failure would not partition the network.&nbsp; All work in this <o:p></o:p>=
</p><p class=3DMsoNormal>area should be specifically evaluated by the WG in=
 terms of practicality <o:p></o:p></p><p class=3DMsoNormal>and applicabilit=
y to deployed networks.<span style=3D'color:black'><o:p></o:p></span></p><p=
 class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>The RTGWG mail=
ing list will be used to discuss the proposals as they <o:p></o:p></p><p cl=
ass=3DMsoNormal>arise. The working group will meet if there are one or more=
 active <o:p></o:p></p><p class=3DMsoNormal>proposals that require discussi=
on.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoN=
ormal>The working group milestones will be updated as needed to reflect the=
 <o:p></o:p></p><p class=3DMsoNormal>proposals currently being worked on an=
d the target dates for their <o:p></o:p></p><p class=3DMsoNormal>completion=
. New milestones will be first reviewed by the IESG. The <o:p></o:p></p><p =
class=3DMsoNormal>working group will be on-going as long as the ADs believe=
 it serves a <o:p></o:p></p><p class=3DMsoNormal>useful purpose.<o:p></o:p>=
</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Goals an=
d Milestones:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cl=
ass=3DMsoNormal>Mar 2012&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; Submit IP Fast Re-Route Using Not-via Addresses to IE=
SG for publication as Informational<o:p></o:p></p><p class=3DMsoNormal>Nov =
2012 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sub=
mit Composite-Link Requirements to IESG for publication as Informational <o=
:p></o:p></p><p class=3DMsoNormal>Nov 2012 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Submit Ordered FIB architecture to IESG =
for publication as Informational<o:p></o:p></p><p class=3DMsoNormal>Nov 201=
2 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Submit=
 initial Internet Draft on Multicast IP Fast Reroute Architecture<o:p></o:p=
></p><p class=3DMsoNormal>Nov 2012 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Submit Composite-Link Framework to IESG for publ=
ication as Informational <o:p></o:p></p><p class=3DMsoNormal>Apr 2013 &nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Submit =
specification on Advanced IP Fast Reroute mechanism to&nbsp; IESG for publi=
cation as Proposed Standard <o:p></o:p></p></div></body></html>=

--_000_24646CE17826CF4A8DF71F9856C7E65659572B63D6GVW1338EXAame_--

From alvaro.retana@hp.com  Mon Nov 28 07:56:44 2011
Return-Path: <alvaro.retana@hp.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 753E221F8A6C for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 07:56:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5waoXpM8Oeg1 for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 07:56:43 -0800 (PST)
Received: from g4t0015.houston.hp.com (g4t0015.houston.hp.com [15.201.24.18]) by ietfa.amsl.com (Postfix) with ESMTP id 679BD21F8726 for <rtgwg@ietf.org>; Mon, 28 Nov 2011 07:56:43 -0800 (PST)
Received: from G1W0400.americas.hpqcorp.net (g1w0400.americas.hpqcorp.net [16.236.31.10]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g4t0015.houston.hp.com (Postfix) with ESMTPS id F12C38489 for <rtgwg@ietf.org>; Mon, 28 Nov 2011 15:56:42 +0000 (UTC)
Received: from G1W0396.americas.hpqcorp.net (16.236.31.9) by G1W0400.americas.hpqcorp.net (16.236.31.10) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 28 Nov 2011 15:56:18 +0000
Received: from GVW1338EXA.americas.hpqcorp.net ([16.236.29.12]) by G1W0396.americas.hpqcorp.net ([16.236.31.9]) with mapi; Mon, 28 Nov 2011 15:56:18 +0000
From: "Retana, Alvaro" <alvaro.retana@hp.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Mon, 28 Nov 2011 15:56:17 +0000
Subject: Adoption of the MRT Architecture Draft as WG Document
Thread-Topic: Adoption of the MRT Architecture Draft as WG Document
Thread-Index: Acyt5kOsRZxYt/msRm2zvww9/zcpsg==
Message-ID: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
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_24646CE17826CF4A8DF71F9856C7E65659572B63D8GVW1338EXAame_"
MIME-Version: 1.0
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, 28 Nov 2011 15:56:44 -0000

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

Hi!

As discussed at the meeting in Taipei, this e-mail is a call for adoption o=
f the MRT Architecture draft as a WG item.  There was strong support in the=
 room.

http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture

As was also suggested at the meeting, the multicast-related sections (4.3 a=
nd 4.4) will be moved into a separate document (to be discussed separately)=
.


It was also brought up that the draft has an IPR claim attached to it.  The=
 following links are to the IPR claim and to the application itself (provid=
ed by the authors):

https://datatracker.ietf.org/ipr/1594/
http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO2010055408&r=
ecNum=3D1&docAn=3DIB2009007467&queryString=3DFP:%28PCT/IB2009/007467%29&max=
Rec=3D1<blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?docId=
=3DWO2010055408&recNum=3D1&docAn=3DIB2009007467&queryString=3DFP:(PCT/IB200=
9/007467)&maxRec=3D1>

As a reminder, having an IPR claim does not disqualify a draft from advanci=
ng in the IETF, being adopted by a working group or from eventually becomin=
g a standard.  It just represents one more item to be considered by the wor=
king group.    http://www.ietf.org/ipr/policy.html


Please post your opinions and votes about adoption to the list.  We will ke=
ep this discussion open until Dec/12, 2011.

Thanks!

Alvaro.

--_000_24646CE17826CF4A8DF71F9856C7E65659572B63D8GVW1338EXAame_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi!<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>As discuss=
ed at the meeting in Taipei, this e-mail is a call for adoption of the MRT =
Architecture draft as a WG item.&nbsp; There was strong support in the room=
.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal><a href=3D"http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-archite=
cture">http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture</a=
><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal>As was also suggested at the meeting, the multicast-related sections (4=
.3 and 4.4) will be moved into a separate document (to be discussed separat=
ely).<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>It was also brought up th=
at the draft has an IPR claim attached to it.&nbsp; The following links are=
 to the IPR claim and to the application itself (provided by the authors):<=
o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorma=
l><a href=3D"https://datatracker.ietf.org/ipr/1594/">https://datatracker.ie=
tf.org/ipr/1594/</a><o:p></o:p></p><p class=3DMsoNormal><span style=3D'colo=
r:green'><a href=3D"blocked::http://www.wipo.int/patentscope/search/en/deta=
il.jsf?docId=3DWO2010055408&amp;recNum=3D1&amp;docAn=3DIB2009007467&amp;que=
ryString=3DFP:(PCT/IB2009/007467)&amp;maxRec=3D1">http://www.wipo.int/paten=
tscope/search/en/detail.jsf?docId=3DWO2010055408&amp;recNum=3D1&amp;docAn=
=3DIB2009007467&amp;queryString=3DFP:%28PCT/IB2009/007467%29&amp;maxRec=3D1=
</a></span><o:p></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 c=
lass=3DMsoNormal>As a reminder, having an IPR claim does not disqualify a d=
raft from advancing in the IETF, being adopted by a working group or from e=
ventually becoming a standard.&nbsp; It just represents one more item to be=
 considered by the working group.&nbsp; &nbsp;&nbsp;<a href=3D"http://www.i=
etf.org/ipr/policy.html">http://www.ietf.org/ipr/policy.html</a><o:p></o:p>=
</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p><p class=3DMsoNormal>Please post your opinions and votes about=
 adoption to the list.&nbsp; We will keep this discussion open until Dec/12=
, 2011.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3D=
MsoNormal>Thanks!<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
p class=3DMsoNormal>Alvaro.<o:p></o:p></p></div></body></html>=

--_000_24646CE17826CF4A8DF71F9856C7E65659572B63D8GVW1338EXAame_--

From wim.henderickx@alcatel-lucent.com  Mon Nov 28 08:03:37 2011
Return-Path: <wim.henderickx@alcatel-lucent.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 2461521F8BDB for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 08:03:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QViK2kie+cyx for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 08:03:36 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id 1B1CE21F8BE4 for <rtgwg@ietf.org>; Mon, 28 Nov 2011 08:03:34 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pASG3Ka8009413 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 28 Nov 2011 17:03:25 +0100
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.42]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Mon, 28 Nov 2011 17:03:21 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: "Retana, Alvaro" <alvaro.retana@hp.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Mon, 28 Nov 2011 17:03:17 +0100
Subject: RE: Adoption of the MRT Architecture Draft as WG Document
Thread-Topic: Adoption of the MRT Architecture Draft as WG Document
Thread-Index: Acyt5kOsRZxYt/msRm2zvww9/zcpsgAAPZNQ
Message-ID: <14C7F4F06DB5814AB0DE29716C4F6D671BE40A5A@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: nl-NL, en-US
Content-Type: multipart/alternative; boundary="_000_14C7F4F06DB5814AB0DE29716C4F6D671BE40A5AFRMRSSXCHMBSB1d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
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, 28 Nov 2011 16:03:37 -0000

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

support

From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of R=
etana, Alvaro
Sent: maandag 28 november 2011 16:56
To: rtgwg@ietf.org
Subject: Adoption of the MRT Architecture Draft as WG Document

Hi!

As discussed at the meeting in Taipei, this e-mail is a call for adoption o=
f the MRT Architecture draft as a WG item.  There was strong support in the=
 room.

http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture

As was also suggested at the meeting, the multicast-related sections (4.3 a=
nd 4.4) will be moved into a separate document (to be discussed separately)=
.


It was also brought up that the draft has an IPR claim attached to it.  The=
 following links are to the IPR claim and to the application itself (provid=
ed by the authors):

https://datatracker.ietf.org/ipr/1594/
http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO2010055408&r=
ecNum=3D1&docAn=3DIB2009007467&queryString=3DFP:%28PCT/IB2009/007467%29&max=
Rec=3D1<blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?docId=
=3DWO2010055408&recNum=3D1&docAn=3DIB2009007467&queryString=3DFP:(PCT/IB200=
9/007467)&maxRec=3D1>

As a reminder, having an IPR claim does not disqualify a draft from advanci=
ng in the IETF, being adopted by a working group or from eventually becomin=
g a standard.  It just represents one more item to be considered by the wor=
king group.    http://www.ietf.org/ipr/policy.html


Please post your opinions and votes about adoption to the list.  We will ke=
ep this discussion open until Dec/12, 2011.

Thanks!

Alvaro.

--_000_14C7F4F06DB5814AB0DE29716C4F6D671BE40A5AFRMRSSXCHMBSB1d_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUI=
V=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"><meta name=3DG=
enerator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>support<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:no=
ne;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMso=
Normal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","san=
s-serif"'> rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] <b>On Beh=
alf Of </b>Retana, Alvaro<br><b>Sent:</b> maandag 28 november 2011 16:56<br=
><b>To:</b> rtgwg@ietf.org<br><b>Subject:</b> Adoption of the MRT Architect=
ure Draft as WG Document<o:p></o:p></span></p></div></div><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi!<o:p></o:p></p><p class=3D=
MsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>As discussed at the mee=
ting in Taipei, this e-mail is a call for adoption of the MRT Architecture =
draft as a WG item.&nbsp; There was strong support in the room.<o:p></o:p><=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a href=
=3D"http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture">http=
://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture</a><o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>As was =
also suggested at the meeting, the multicast-related sections (4.3 and 4.4)=
 will be moved into a separate document (to be discussed separately).<o:p><=
/o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p><p class=3DMsoNormal>It was also brought up that the draf=
t has an IPR claim attached to it.&nbsp; The following links are to the IPR=
 claim and to the application itself (provided by the authors):<o:p></o:p><=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a href=
=3D"https://datatracker.ietf.org/ipr/1594/">https://datatracker.ietf.org/ip=
r/1594/</a><o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:green'>=
<a href=3D"blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?do=
cId=3DWO2010055408&amp;recNum=3D1&amp;docAn=3DIB2009007467&amp;queryString=
=3DFP:(PCT/IB2009/007467)&amp;maxRec=3D1">http://www.wipo.int/patentscope/s=
earch/en/detail.jsf?docId=3DWO2010055408&amp;recNum=3D1&amp;docAn=3DIB20090=
07467&amp;queryString=3DFP:%28PCT/IB2009/007467%29&amp;maxRec=3D1</a></span=
><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-f=
amily:"Times New Roman","serif"'>&nbsp;<o:p></o:p></span></p><p class=3DMso=
Normal>As a reminder, having an IPR claim does not disqualify a draft from =
advancing in the IETF, being adopted by a working group or from eventually =
becoming a standard.&nbsp; It just represents one more item to be considere=
d by the working group.&nbsp; &nbsp;&nbsp;<a href=3D"http://www.ietf.org/ip=
r/policy.html">http://www.ietf.org/ipr/policy.html</a><o:p></o:p></p><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p><p class=3DMsoNormal>Please post your opinions and votes about adoption =
to the list.&nbsp; We will keep this discussion open until Dec/12, 2011.<o:=
p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>=
Thanks!<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3D=
MsoNormal>Alvaro.<o:p></o:p></p></div></body></html>=

--_000_14C7F4F06DB5814AB0DE29716C4F6D671BE40A5AFRMRSSXCHMBSB1d_--

From jeff.tantsura@ericsson.com  Mon Nov 28 08:52:15 2011
Return-Path: <jeff.tantsura@ericsson.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 0D6E521F8CF5 for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 08:52:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MTXTy0ww1WIz for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 08:52:14 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id D4A0121F8CEE for <rtgwg@ietf.org>; Mon, 28 Nov 2011 08:52:09 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pASGq8SY015199 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtgwg@ietf.org>; Mon, 28 Nov 2011 10:52:09 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Mon, 28 Nov 2011 11:52:07 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "Retana, Alvaro" <alvaro.retana@hp.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Mon, 28 Nov 2011 11:52:06 -0500
Subject: RE: Adoption of the MRT Architecture Draft as WG Document
Thread-Topic: Adoption of the MRT Architecture Draft as WG Document
Thread-Index: Acyt5kOsRZxYt/msRm2zvww9/zcpsgAB8Kow
Message-ID: <0ED867EB33AB2B45AAB470D5A64CDBF6181C10F0AE@EUSAACMS0701.eamcs.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
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_0ED867EB33AB2B45AAB470D5A64CDBF6181C10F0AEEUSAACMS0701e_"
MIME-Version: 1.0
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, 28 Nov 2011 16:52:15 -0000

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

Hi,

Yes/support

Regards,
Jeff

From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of R=
etana, Alvaro
Sent: Monday, November 28, 2011 7:56 AM
To: rtgwg@ietf.org
Subject: Adoption of the MRT Architecture Draft as WG Document

Hi!

As discussed at the meeting in Taipei, this e-mail is a call for adoption o=
f the MRT Architecture draft as a WG item.  There was strong support in the=
 room.

http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture

As was also suggested at the meeting, the multicast-related sections (4.3 a=
nd 4.4) will be moved into a separate document (to be discussed separately)=
.


It was also brought up that the draft has an IPR claim attached to it.  The=
 following links are to the IPR claim and to the application itself (provid=
ed by the authors):

https://datatracker.ietf.org/ipr/1594/
http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO2010055408&r=
ecNum=3D1&docAn=3DIB2009007467&queryString=3DFP:%28PCT/IB2009/007467%29&max=
Rec=3D1<blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?docId=
=3DWO2010055408&recNum=3D1&docAn=3DIB2009007467&queryString=3DFP:(PCT/IB200=
9/007467)&maxRec=3D1>

As a reminder, having an IPR claim does not disqualify a draft from advanci=
ng in the IETF, being adopted by a working group or from eventually becomin=
g a standard.  It just represents one more item to be considered by the wor=
king group.    http://www.ietf.org/ipr/policy.html


Please post your opinions and votes about adoption to the list.  We will ke=
ep this discussion open until Dec/12, 2011.

Thanks!

Alvaro.

--_000_0ED867EB33AB2B45AAB470D5A64CDBF6181C10F0AEEUSAACMS0701e_
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-micr=
osoft-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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>Yes/support<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p class=3DMso=
Normal><span style=3D'color:#1F497D'>Regards,<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'color:#1F497D'>Jeff</span><span style=3D'color:=
black'><o:p></o:p></span></p></div><p class=3DMsoNormal><span style=3D'colo=
r:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;borde=
r-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:<=
/span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
'> rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] <b>On Behalf Of <=
/b>Retana, Alvaro<br><b>Sent:</b> Monday, November 28, 2011 7:56 AM<br><b>T=
o:</b> rtgwg@ietf.org<br><b>Subject:</b> Adoption of the MRT Architecture D=
raft as WG Document<o:p></o:p></span></p></div></div><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi!<o:p></o:p></p><p class=3DMsoNo=
rmal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>As discussed at the meeting =
in Taipei, this e-mail is a call for adoption of the MRT Architecture draft=
 as a WG item.&nbsp; There was strong support in the room.<o:p></o:p></p><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a href=3D"htt=
p://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture">http://tool=
s.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture</a><o:p></o:p></p><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>As was also su=
ggested at the meeting, the multicast-related sections (4.3 and 4.4) will b=
e moved into a separate document (to be discussed separately).<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p><p class=3DMsoNormal>It was also brought up that the draft has a=
n IPR claim attached to it.&nbsp; The following links are to the IPR claim =
and to the application itself (provided by the authors):<o:p></o:p></p><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a href=3D"https=
://datatracker.ietf.org/ipr/1594/">https://datatracker.ietf.org/ipr/1594/</=
a><o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:green'><a href=
=3D"blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DW=
O2010055408&amp;recNum=3D1&amp;docAn=3DIB2009007467&amp;queryString=3DFP:(P=
CT/IB2009/007467)&amp;maxRec=3D1">http://www.wipo.int/patentscope/search/en=
/detail.jsf?docId=3DWO2010055408&amp;recNum=3D1&amp;docAn=3DIB2009007467&am=
p;queryString=3DFP:%28PCT/IB2009/007467%29&amp;maxRec=3D1</a></span><o:p></=
o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"T=
imes New Roman","serif"'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal>A=
s a reminder, having an IPR claim does not disqualify a draft from advancin=
g in the IETF, being adopted by a working group or from eventually becoming=
 a standard.&nbsp; It just represents one more item to be considered by the=
 working group.&nbsp; &nbsp;&nbsp;<a href=3D"http://www.ietf.org/ipr/policy=
.html">http://www.ietf.org/ipr/policy.html</a><o:p></o:p></p><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cl=
ass=3DMsoNormal>Please post your opinions and votes about adoption to the l=
ist.&nbsp; We will keep this discussion open until Dec/12, 2011.<o:p></o:p>=
</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thanks!<=
o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorma=
l>Alvaro.<o:p></o:p></p></div></body></html>=

--_000_0ED867EB33AB2B45AAB470D5A64CDBF6181C10F0AEEUSAACMS0701e_--

From russw@riw.us  Mon Nov 28 08:56:45 2011
Return-Path: <russw@riw.us>
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 79EB421F8CC5 for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 08:56:45 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WoBGRLJ+FAQD for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 08:56:45 -0800 (PST)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id EF62021F8531 for <rtgwg@ietf.org>; Mon, 28 Nov 2011 08:56:44 -0800 (PST)
Received: from rrcs-24-199-145-66.midsouth.biz.rr.com ([24.199.145.66]:38134 helo=[192.168.3.115]) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RV4VX-0006cH-QV for rtgwg@ietf.org; Mon, 28 Nov 2011 11:56:44 -0500
Message-ID: <4ED3BD3B.2040105@riw.us>
Date: Mon, 28 Nov 2011 11:56:27 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: Adoption of the MRT Architecture Draft as WG Document
References: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
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, 28 Nov 2011 16:56:45 -0000

Support.

:-)

Russ

On 11/28/2011 10:56 AM, Retana, Alvaro wrote:
> Hi!
> 
>  
> 
> As discussed at the meeting in Taipei, this e-mail is a call for
> adoption of the MRT Architecture draft as a WG item.  There was strong
> support in the room.
> 
>  
> 
> http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture
> 
>  
> 
> As was also suggested at the meeting, the multicast-related sections
> (4.3 and 4.4) will be moved into a separate document (to be discussed
> separately).
> 
>  
> 
>  
> 
> It was also brought up that the draft has an IPR claim attached to it. 
> The following links are to the IPR claim and to the application itself
> (provided by the authors):
> 
>  
> 
> https://datatracker.ietf.org/ipr/1594/
> 
> http://www.wipo.int/patentscope/search/en/detail.jsf?docId=WO2010055408&recNum=1&docAn=IB2009007467&queryString=FP:%28PCT/IB2009/007467%29&maxRec=1
> <blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?docId=WO2010055408&recNum=1&docAn=IB2009007467&queryString=FP:(PCT/IB2009/007467)&maxRec=1>
> 
>  
> 
> As a reminder, having an IPR claim does not disqualify a draft from
> advancing in the IETF, being adopted by a working group or from
> eventually becoming a standard.  It just represents one more item to be
> considered by the working group.    http://www.ietf.org/ipr/policy.html
> 
>  
> 
>  
> 
> Please post your opinions and votes about adoption to the list.  We will
> keep this discussion open until Dec/12, 2011.
> 
>  
> 
> Thanks!
> 
>  
> 
> Alvaro.
> 
> 
> 
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

From akatlas@gmail.com  Mon Nov 28 08:59:21 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 B059521F8B29 for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 08:59:21 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rB7IUzRu5es for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 08:59:21 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0A55721F8B07 for <rtgwg@ietf.org>; Mon, 28 Nov 2011 08:59:20 -0800 (PST)
Received: by iaeo4 with SMTP id o4so11009425iae.31 for <rtgwg@ietf.org>; Mon, 28 Nov 2011 08:59:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=m6XzydS1DkgrfPnykP0/UWpgCHIUyJC6qNWkXQZdSDg=; b=GpPHEYYehhT3BlAg9CI6krbZw0LpQiKQb9J6GkUNnhzw3PgHIf+UV4p3J9F9L1Y8f2 L3o3bLXa6oey4TRZj7uuh+jqU7wrYQXvhwfB3+3zfR4FsR3tkSjaTaY9g7r74tjE99ZY SFaJsw7dAcf+iIMF1kqJx4SbMHiNoSTC28+iA=
MIME-Version: 1.0
Received: by 10.231.70.7 with SMTP id b7mr3147330ibj.49.1322499558844; Mon, 28 Nov 2011 08:59:18 -0800 (PST)
Received: by 10.50.184.229 with HTTP; Mon, 28 Nov 2011 08:59:18 -0800 (PST)
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
References: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
Date: Mon, 28 Nov 2011 11:59:18 -0500
Message-ID: <CAG4d1rfSRGrQumSOoBHtncBvi-_KhGDwu5bmibk=i1to_X5oaw@mail.gmail.com>
Subject: Re: Adoption of the MRT Architecture Draft as WG Document
From: Alia Atlas <akatlas@gmail.com>
To: "Retana, Alvaro" <alvaro.retana@hp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "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, 28 Nov 2011 16:59:21 -0000

Support (of course, as a co-author)

On Mon, Nov 28, 2011 at 10:56 AM, Retana, Alvaro <alvaro.retana@hp.com> wro=
te:
> Hi!
>
>
>
> As discussed at the meeting in Taipei, this e-mail is a call for adoption=
 of
> the MRT Architecture draft as a WG item.=A0 There was strong support in t=
he
> room.
>
>
>
> http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture
>
>
>
> As was also suggested at the meeting, the multicast-related sections (4.3
> and 4.4) will be moved into a separate document (to be discussed
> separately).
>
>
>
>
>
> It was also brought up that the draft has an IPR claim attached to it.=A0=
 The
> following links are to the IPR claim and to the application itself (provi=
ded
> by the authors):
>
>
>
> https://datatracker.ietf.org/ipr/1594/
>
> http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO2010055408=
&recNum=3D1&docAn=3DIB2009007467&queryString=3DFP:%28PCT/IB2009/007467%29&m=
axRec=3D1
>
>
>
> As a reminder, having an IPR claim does not disqualify a draft from
> advancing in the IETF, being adopted by a working group or from eventuall=
y
> becoming a standard.=A0 It just represents one more item to be considered=
 by
> the working group.=A0 =A0=A0http://www.ietf.org/ipr/policy.html
>
>
>
>
>
> Please post your opinions and votes about adoption to the list.=A0 We wil=
l
> keep this discussion open until Dec/12, 2011.
>
>
>
> Thanks!
>
>
>
> Alvaro.
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
>

From andrew.lange@alcatel-lucent.com  Mon Nov 28 14:10:33 2011
Return-Path: <andrew.lange@alcatel-lucent.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 F037C21F8C91 for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 14:10:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssJttsKULgdi for <rtgwg@ietfa.amsl.com>; Mon, 28 Nov 2011 14:10:08 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 908B921F8C43 for <rtgwg@ietf.org>; Mon, 28 Nov 2011 14:09:56 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id pASM9msv026912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 28 Nov 2011 16:09:48 -0600 (CST)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pASM9lYZ010721 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 28 Nov 2011 16:09:48 -0600
Received: from neo-89.vpn.ind.alcatel.com (135.3.62.246) by USNAVSXCHHUB02.ndc.alcatel-lucent.com (135.3.39.111) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 28 Nov 2011 16:09:47 -0600
Subject: Re: Adoption of the MRT Architecture Draft as WG Document
MIME-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-14-613600729"
From: Andrew Lange <andrew.lange@alcatel-lucent.com>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
Date: Mon, 28 Nov 2011 14:09:44 -0800
Message-ID: <4451E50E-3E25-422D-877F-69BE4397524C@alcatel-lucent.com>
References: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
To: "Retana, Alvaro" <alvaro.retana@hp.com>
X-Mailer: Apple Mail (2.1084)
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
X-Mailman-Approved-At: Mon, 28 Nov 2011 14:13:12 -0800
Cc: "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, 28 Nov 2011 22:10:33 -0000

--Apple-Mail-14-613600729
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

Support.

Andrew

On Nov 28, 2011, at 7:56 AM, Retana, Alvaro wrote:

> Hi!
> =20
> As discussed at the meeting in Taipei, this e-mail is a call for =
adoption of the MRT Architecture draft as a WG item.  There was strong =
support in the room.
> =20
> http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture
> =20
> As was also suggested at the meeting, the multicast-related sections =
(4.3 and 4.4) will be moved into a separate document (to be discussed =
separately).
> =20
> =20
> It was also brought up that the draft has an IPR claim attached to it. =
 The following links are to the IPR claim and to the application itself =
(provided by the authors):
> =20
> https://datatracker.ietf.org/ipr/1594/
> =
http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO2010055408&=
recNum=3D1&docAn=3DIB2009007467&queryString=3DFP:%28PCT/IB2009/007467%29&m=
axRec=3D1
> =20
> As a reminder, having an IPR claim does not disqualify a draft from =
advancing in the IETF, being adopted by a working group or from =
eventually becoming a standard.  It just represents one more item to be =
considered by the working group.    http://www.ietf.org/ipr/policy.html
> =20
> =20
> Please post your opinions and votes about adoption to the list.  We =
will keep this discussion open until Dec/12, 2011.
> =20
> Thanks!
> =20
> Alvaro.
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg


--Apple-Mail-14-613600729
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"

<html><head><base href=3D"x-msg://89/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; =
">Support.<div><br></div><div>Andrew</div><div><br><div><div>On Nov 28, =
2011, at 7:56 AM, Retana, Alvaro wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; ">Hi!<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; ">As discussed at the meeting in =
Taipei, this e-mail is a call for adoption of the MRT Architecture draft =
as a WG item.&nbsp; There was strong support in the =
room.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><a =
href=3D"http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture"=
 style=3D"color: blue; text-decoration: underline; =
">http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture</a><o:=
p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">As was also =
suggested at the meeting, the multicast-related sections (4.3 and 4.4) =
will be moved into a separate document (to be discussed =
separately).<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; ">It was also brought up that =
the draft has an IPR claim attached to it.&nbsp; The following links are =
to the IPR claim and to the application itself (provided by the =
authors):<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><a href=3D"https://datatracker.ietf.org/ipr/1594/" =
style=3D"color: blue; text-decoration: underline; =
">https://datatracker.ietf.org/ipr/1594/</a><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><span style=3D"color: green; "><a =
href=3D"blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?docI=
d=3DWO2010055408&amp;recNum=3D1&amp;docAn=3DIB2009007467&amp;queryString=3D=
FP:(PCT/IB2009/007467)&amp;maxRec=3D1" style=3D"color: blue; =
text-decoration: underline; =
">http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO201005540=
8&amp;recNum=3D1&amp;docAn=3DIB2009007467&amp;queryString=3DFP:%28PCT/IB20=
09/007467%29&amp;maxRec=3D1</a></span><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><span style=3D"font-size: 12pt; font-family: 'Times New =
Roman', serif; ">&nbsp;<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">As a reminder, =
having an IPR claim does not disqualify a draft from advancing in the =
IETF, being adopted by a working group or from eventually becoming a =
standard.&nbsp; It just represents one more item to be considered by the =
working group.&nbsp; &nbsp;&nbsp;<a =
href=3D"http://www.ietf.org/ipr/policy.html" style=3D"color: blue; =
text-decoration: underline; =
">http://www.ietf.org/ipr/policy.html</a><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; ">Please post your opinions and votes about adoption to the =
list.&nbsp; We will keep this discussion open until Dec/12, =
2011.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
">Thanks!<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; =
">Alvaro.<o:p></o:p></div></div>__________________________________________=
_____<br>rtgwg mailing list<br><a href=3D"mailto:rtgwg@ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">rtgwg@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/rtgwg" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/rtgwg</a><br></div></span></blockq=
uote></div><br></div></body></html>=

--Apple-Mail-14-613600729--

From bruno.decraene@orange.com  Tue Nov 29 00:12:57 2011
Return-Path: <bruno.decraene@orange.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 7A7AC1F0C41 for <rtgwg@ietfa.amsl.com>; Tue, 29 Nov 2011 00:12:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lVXwMWN+28ar for <rtgwg@ietfa.amsl.com>; Tue, 29 Nov 2011 00:12:56 -0800 (PST)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id C87D221F8593 for <rtgwg@ietf.org>; Tue, 29 Nov 2011 00:12:55 -0800 (PST)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 8E8698B8005; Tue, 29 Nov 2011 09:05:24 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id 7D2498B8001; Tue, 29 Nov 2011 09:05:24 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Nov 2011 09:04:00 +0100
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_01CCAE6D.733ABD58"
Subject: RE: Adoption of the MRT Architecture Draft as WG Document
Date: Tue, 29 Nov 2011 09:03:59 +0100
Message-ID: <FE8F6A65A433A744964C65B6EDFDC24002A56223@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Adoption of the MRT Architecture Draft as WG Document
Thread-Index: Acyt5kOsRZxYt/msRm2zvww9/zcpsgAhxE4g
References: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
From: <bruno.decraene@orange.com>
To: <alvaro.retana@hp.com>
X-OriginalArrivalTime: 29 Nov 2011 08:04:00.0329 (UTC) FILETIME=[73BC4B90:01CCAE6D]
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, 29 Nov 2011 08:12:57 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCAE6D.733ABD58
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Support.

=20

From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf
Of Retana, Alvaro
Sent: Monday, November 28, 2011 4:56 PM
To: rtgwg@ietf.org
Subject: Adoption of the MRT Architecture Draft as WG Document

=20

Hi!

=20

As discussed at the meeting in Taipei, this e-mail is a call for
adoption of the MRT Architecture draft as a WG item.  There was strong
support in the room.

=20

http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture

=20

As was also suggested at the meeting, the multicast-related sections
(4.3 and 4.4) will be moved into a separate document (to be discussed
separately).

=20

=20

It was also brought up that the draft has an IPR claim attached to it.
The following links are to the IPR claim and to the application itself
(provided by the authors):

=20

https://datatracker.ietf.org/ipr/1594/

http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO2010055408=
&
recNum=3D1&docAn=3DIB2009007467&queryString=3DFP:%28PCT/IB2009/007467%29&=
maxRe
c=3D1
<blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO=
2
010055408&recNum=3D1&docAn=3DIB2009007467&queryString=3DFP:(PCT/IB2009/00=
7467)
&maxRec=3D1>=20

=20

As a reminder, having an IPR claim does not disqualify a draft from
advancing in the IETF, being adopted by a working group or from
eventually becoming a standard.  It just represents one more item to be
considered by the working group.    http://www.ietf.org/ipr/policy.html

=20

=20

Please post your opinions and votes about adoption to the list.  We will
keep this discussion open until Dec/12, 2011.

=20

Thanks!

=20

Alvaro.


------_=_NextPart_001_01CCAE6D.733ABD58
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:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" 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 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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=3DFR link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Support.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] <b>On Behalf Of =
</b>Retana, Alvaro<br><b>Sent:</b> Monday, November 28, 2011 4:56 =
PM<br><b>To:</b> rtgwg@ietf.org<br><b>Subject:</b> Adoption of the MRT =
Architecture Draft as WG Document<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>Hi!<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>As discussed at the meeting in Taipei, this e-mail is a =
call for adoption of the MRT Architecture draft as a WG item.&nbsp; =
There was strong support in the room.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><a =
href=3D"http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture=
">http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture</a><o=
:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>As was also suggested at the meeting, the multicast-related =
sections (4.3 and 4.4) will be moved into a separate document (to be =
discussed separately).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>It was also brought up that the draft has an IPR claim =
attached to it.&nbsp; The following links are to the IPR claim and to =
the application itself (provided by the =
authors):<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><a =
href=3D"https://datatracker.ietf.org/ipr/1594/">https://datatracker.ietf.=
org/ipr/1594/</a><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:green'><a =
href=3D"blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?doc=
Id=3DWO2010055408&amp;recNum=3D1&amp;docAn=3DIB2009007467&amp;queryString=
=3DFP:(PCT/IB2009/007467)&amp;maxRec=3D1">http://www.wipo.int/patentscope=
/search/en/detail.jsf?docId=3DWO2010055408&amp;recNum=3D1&amp;docAn=3DIB2=
009007467&amp;queryString=3DFP:%28PCT/IB2009/007467%29&amp;maxRec=3D1</a>=
</span><span lang=3DEN-US><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>As a reminder, having an IPR claim does not disqualify a =
draft from advancing in the IETF, being adopted by a working group or =
from eventually becoming a standard.&nbsp; It just represents one more =
item to be considered by the working group.&nbsp; &nbsp;&nbsp;<a =
href=3D"http://www.ietf.org/ipr/policy.html">http://www.ietf.org/ipr/poli=
cy.html</a><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Please post your opinions and votes about adoption to the =
list.&nbsp; We will keep this discussion open until Dec/12, =
2011.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Thanks!<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Alvaro.<o:p></o:p></span></p></div></div></body></html>
------_=_NextPart_001_01CCAE6D.733ABD58--

From Andras.Csaszar@ericsson.com  Tue Nov 29 03:02:58 2011
Return-Path: <Andras.Csaszar@ericsson.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 6DD3521F84FD for <rtgwg@ietfa.amsl.com>; Tue, 29 Nov 2011 03:02:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85C39PoT3ARU for <rtgwg@ietfa.amsl.com>; Tue, 29 Nov 2011 03:02:57 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id C724D21F84D8 for <rtgwg@ietf.org>; Tue, 29 Nov 2011 03:02:51 -0800 (PST)
X-AuditID: c1b4fb3d-b7b5fae00000219a-34-4ed4bbda3400
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 82.88.08602.ADBB4DE4; Tue, 29 Nov 2011 12:02:50 +0100 (CET)
Received: from ESESSCMS0363.eemea.ericsson.se ([169.254.1.109]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Tue, 29 Nov 2011 12:02:50 +0100
From: =?iso-8859-1?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>
To: "Retana, Alvaro" <alvaro.retana@hp.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Date: Tue, 29 Nov 2011 12:02:48 +0100
Subject: RE: Adoption of the MRT Architecture Draft as WG Document
Thread-Topic: Adoption of the MRT Architecture Draft as WG Document
Thread-Index: Acyt5kOsRZxYt/msRm2zvww9/zcpsgAoAJow
Message-ID: <8DCD771BDA4A394E9BCBA8932E8392974B0B87E460@ESESSCMS0363.eemea.ericsson.se>
References: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
In-Reply-To: <24646CE17826CF4A8DF71F9856C7E65659572B63D8@GVW1338EXA.americas.hpqcorp.net>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: hu-HU, en-US
Content-Type: multipart/alternative; boundary="_000_8DCD771BDA4A394E9BCBA8932E8392974B0B87E460ESESSCMS0363e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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, 29 Nov 2011 11:02:58 -0000

--_000_8DCD771BDA4A394E9BCBA8932E8392974B0B87E460ESESSCMS0363e_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Yes/support (co-author).

Andr=E1s

________________________________
From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of R=
etana, Alvaro
Sent: 2011. november 28. 16:56
To: rtgwg@ietf.org
Subject: Adoption of the MRT Architecture Draft as WG Document

Hi!

As discussed at the meeting in Taipei, this e-mail is a call for adoption o=
f the MRT Architecture draft as a WG item.  There was strong support in the=
 room.

http://tools.ietf.org/html/draft-atlas-rtgwg-mrt-frr-architecture

As was also suggested at the meeting, the multicast-related sections (4.3 a=
nd 4.4) will be moved into a separate document (to be discussed separately)=
.


It was also brought up that the draft has an IPR claim attached to it.  The=
 following links are to the IPR claim and to the application itself (provid=
ed by the authors):

https://datatracker.ietf.org/ipr/1594/
http://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO2010055408&r=
ecNum=3D1&docAn=3DIB2009007467&queryString=3DFP:%28PCT/IB2009/007467%29&max=
Rec=3D1<blocked::http://www.wipo.int/patentscope/search/en/detail.jsf?docId=
=3DWO2010055408&recNum=3D1&docAn=3DIB2009007467&queryString=3DFP:(PCT/IB200=
9/007467)&maxRec=3D1>

As a reminder, having an IPR claim does not disqualify a draft from advanci=
ng in the IETF, being adopted by a working group or from eventually becomin=
g a standard.  It just represents one more item to be considered by the wor=
king group.    http://www.ietf.org/ipr/policy.html


Please post your opinions and votes about adoption to the list.  We will ke=
ep this discussion open until Dec/12, 2011.

Thanks!

Alvaro.

--_000_8DCD771BDA4A394E9BCBA8932E8392974B0B87E460ESESSCMS0363e_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html xmlns=
=3D"http://www.w3.org/TR/REC-html40" xmlns:v=3D"urn:schemas-microsoft-com:v=
ml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sche=
mas-microsoft-com:office:word" xmlns:x=3D"urn:schemas-microsoft-com:office:=
excel" xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" xmlns:a=3D"u=
rn:schemas-microsoft-com:office:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1=
-A29F-00AA00C14882" xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" x=
mlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" xmln=
s:b=3D"urn:schemas-microsoft-com:office:publisher" xmlns:ss=3D"urn:schemas-=
microsoft-com:office:spreadsheet" xmlns:c=3D"urn:schemas-microsoft-com:offi=
ce:component:spreadsheet" xmlns:odc=3D"urn:schemas-microsoft-com:office:odc=
" xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"ht=
tp://www.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/e=
nvelope/" xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" XMLNS:D=
=3D"DAV:" XMLNS:Repl=3D"http://schemas.microsoft.com/repl/" xmlns:mt=3D"htt=
p://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2=3D"http://sch=
emas.microsoft.com/office/excel/2003/xml" xmlns:ppda=3D"http://www.passport=
.com/NameSpace.xsd" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/so=
ap/ois/" xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/director=
y/" xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://sch=
emas.microsoft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.co=
m/data/udc" xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sub=3D"htt=
p://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec=3D"http:=
//www.w3.org/2001/04/xmlenc#" xmlns:sp=3D"http://schemas.microsoft.com/shar=
epoint/" xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" xmlns:=
xsi=3D"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs=3D"http://sche=
mas.microsoft.com/data/udc/soap" xmlns:udcxf=3D"http://schemas.microsoft.co=
m/data/udc/xmlfile" xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/p=
arttopart" xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflo=
w/" xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" xm=
lns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi=3D=
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mv=
er=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m=
=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http:/=
/schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp=3D"http:=
//microsoft.com/sharepoint/webpartpages" xmlns:ex12t=3D"http://schemas.micr=
osoft.com/exchange/services/2006/types" xmlns:ex12m=3D"http://schemas.micro=
soft.com/exchange/services/2006/messages" xmlns:pptsl=3D"http://schemas.mic=
rosoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl=3D"http://microsoft.co=
m/webservices/SharePointPortalServer/PublishedLinksService" XMLNS:Z=3D"urn:=
schemas-microsoft-com:" xmlns:st=3D"&#1;"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta content=3D"MSHTML 6.00.6002.18510" name=3D"GENERATOR">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
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=3D"EN-US" vlink=3D"purple" link=3D"blue">
<div dir=3D"ltr" align=3D"left"><span class=3D"173410111-29112011"><font fa=
ce=3D"Arial" color=3D"#008000">Yes/support (co-author).</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"173410111-29112011"><font fa=
ce=3D"Arial" color=3D"#008000"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"173410111-29112011"><font fa=
ce=3D"Arial" color=3D"#008000">Andr=E1s</font></span></div><br>
<blockquote dir=3D"ltr" style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDE=
R-LEFT: #008000 2px solid; MARGIN-RIGHT: 0px">
  <div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"l=
eft">
  <hr tabindex=3D"-1">
  <font face=3D"Tahoma" size=3D"2"><b>From:</b> rtgwg-bounces@ietf.org=20
  [mailto:rtgwg-bounces@ietf.org] <b>On Behalf Of </b>Retana,=20
  Alvaro<br><b>Sent:</b> 2011. november 28. 16:56<br><b>To:</b>=20
  rtgwg@ietf.org<br><b>Subject:</b> Adoption of the MRT Architecture Draft =
as WG=20
  Document<br></font><br></div>
  <div></div>
  <div class=3D"WordSection1">
  <p class=3D"MsoNormal">Hi!<o:p></o:p></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal">As discussed at the meeting in Taipei, this e-mail=
 is a=20
  call for adoption of the MRT Architecture draft as a WG item.&nbsp; There=
 was=20
  strong support in the room.<o:p></o:p></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-atlas-=
rtgwg-mrt-frr-architecture">http://tools.ietf.org/html/draft-atlas-rtgwg-mr=
t-frr-architecture</a><o:p></o:p></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal">As was also suggested at the meeting, the multicas=
t-related=20
  sections (4.3 and 4.4) will be moved into a separate document (to be disc=
ussed=20
  separately).<o:p></o:p></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal">It was also brought up that the draft has an IPR c=
laim=20
  attached to it.&nbsp; The following links are to the IPR claim and to the=
=20
  application itself (provided by the authors):<o:p></o:p></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal"><a href=3D"https://datatracker.ietf.org/ipr/1594/"=
>https://datatracker.ietf.org/ipr/1594/</a><o:p></o:p></p>
  <p class=3D"MsoNormal"><span style=3D"COLOR: green"><a href=3D"blocked::h=
ttp://www.wipo.int/patentscope/search/en/detail.jsf?docId=3DWO2010055408&am=
p;recNum=3D1&amp;docAn=3DIB2009007467&amp;queryString=3DFP:(PCT/IB2009/0074=
67)&amp;maxRec=3D1">http://www.wipo.int/patentscope/search/en/detail.jsf?do=
cId=3DWO2010055408&amp;recNum=3D1&amp;docAn=3DIB2009007467&amp;queryString=
=3DFP:%28PCT/IB2009/007467%29&amp;maxRec=3D1</a></span><o:p></o:p></p>
  <p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Time=
s New Roman','serif'">&nbsp;<o:p></o:p></span></p>
  <p class=3D"MsoNormal">As a reminder, having an IPR claim does not disqua=
lify a=20
  draft from advancing in the IETF, being adopted by a working group or fro=
m=20
  eventually becoming a standard.&nbsp; It just represents one more item to=
 be=20
  considered by the working group.&nbsp; &nbsp;&nbsp;<a href=3D"http://www.=
ietf.org/ipr/policy.html">http://www.ietf.org/ipr/policy.html</a><o:p></o:p=
></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal">Please post your opinions and votes about adoption=
 to the=20
  list.&nbsp; We will keep this discussion open until Dec/12,=20
  2011.<o:p></o:p></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal">Thanks!<o:p></o:p></p>
  <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
  <p class=3D"MsoNormal">Alvaro.<o:p></o:p></p></div></blockquote></body></=
html>

--_000_8DCD771BDA4A394E9BCBA8932E8392974B0B87E460ESESSCMS0363e_--
