
From stbryant@cisco.com  Fri Nov  1 10:17:26 2013
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 BCC2511E81A4 for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 10:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.488
X-Spam-Level: 
X-Spam-Status: No, score=-110.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 oFIXN0gMenOd for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 10:17:20 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id DA1D321E809A for <rtgwg@ietf.org>; Fri,  1 Nov 2013 10:17:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6613; q=dns/txt; s=iport; t=1383326228; x=1384535828; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=jXNPanlbGXa+lNtJF0m5YVJY1v6bM7ktRFcN5xkZxvs=; b=bD/PuYRy379HL4yLuOl0RKrrgLAHo1WmMUTh7kS/deM2pveAljPqLRvW 41WnwGW/92npq6eQvfuA4nrbps1ErId2qOYkZvJ1Kxv7YN760+hEA4FKV jtTS3gfde5eZBMZiRaNSYKZILkBV4MIBwqa8AF7v50ZA2dToSiR1IBCu+ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap8HACPhc1KQ/khM/2dsb2JhbABZgwc4ggS+M4EeFnSCJQEBAQMBAQEBLwEFNgoNBAsOAwQBAQEJFggHCQMCAQIBFR8JCAYBDAYCAQGHfQYNr1CNaY82KQaEKAOYCpIJgyY
X-IronPort-AV: E=Sophos;i="4.93,618,1378857600"; d="scan'208";a="161300734"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 01 Nov 2013 17:17:06 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rA1HH07J016267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Nov 2013 17:17:02 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rA1HGxRq029921; Fri, 1 Nov 2013 17:16:59 GMT
Message-ID: <5273E20B.3010809@cisco.com>
Date: Fri, 01 Nov 2013 17:16:59 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Chris Bowers <cbowers@juniper.net>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: issue #1 in candidate-draft-ietf-rtgwg-remote-lfa-03.txt
References: <d40eaf85e9434d87b36776203bc19142@BLUPR05MB292.namprd05.prod.outlook.com>
In-Reply-To: <d40eaf85e9434d87b36776203bc19142@BLUPR05MB292.namprd05.prod.outlook.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
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: Fri, 01 Nov 2013 17:17:26 -0000

SB> I changed the definition of remote LFA to

SB> The use of a PQ node rather than a neighbour of the repairing node 
as the next hop in an LFA repair.

SB> Which I think is more correct than the existing definition of the term.

SB> I have also changed the definition of PQ to

SB> A node which is a member of both the extended P-space and the 
Q-space. In remote LFA this is used as the repair tunnel endpoint.

SB> I also changed the text in 3.1 for consistency to
"In this document such a tunnel is termed a repair tunnel. The tail-end 
of this tunnel (the repair tunnel endpoint) is a "PQ node" and the 
repair mechanism is a “remote LFA”."



On 29/10/2013 15:38, Chris Bowers wrote:
> The text should use "repair tunnel endpoint" instead of "PQ node" when not specifically referring to a node identified by the cost-based RLFA algorithm in section 4.3.
>
> Section 3.1 describes the conditions that a node should satisfy to function as a viable repair tunnel endpoint.  In general, a node can be a valid repair tunnel endpoint (satisfying the conditions of section 3.1) without being a PQ-node (since the Q-space calculation is an approximation).
>
> I propose the following changes in the text to address this:
>
> Section 1:
> "Remote LFA - The tail-end of a repair tunnel.  This tail-end is a
> member of both the extended-P space the Q space.  It
> is also termed a "PQ" node."
> becomes:
> "Remote LFA - The tail-end of a repair tunnel.  A PQ node is always a viable repair tunnel endpoint,
> but a viable repair tunnel endpoint is not necessarily a PQ node. "
SB> I think that we were wrong to call a remote LFA a node, remote LFA 
is surely
SB> a method.


>
> Section 3.1:
> "In this document such a tunnel is termed a repair tunnel.  The tail-end of this tunnel is
> called a "remote LFA" or a "PQ node".
> becomes:
> "In this document such a tunnel is termed a repair tunnel.  The tail-end of this tunnel is
> called a "repair tunnel endpoint".
>
> Section 3.2:
> "The authors simply note that deployment in an MPLS/
> LDP environment is extremely simple and straight-forward as an LDP
> LSP from S to the PQ node is readily available,"
> becomes:
> "The authors simply note that deployment in an MPLS/
> LDP environment is extremely simple and straight-forward as an LDP
> LSP from S to the repair tunnel endpoint is readily available,"
>
> "the decapsulation occurs naturally at the penultimate hop
>   before the PQ node."
> becomes:
> "the decapsulation occurs naturally at the penultimate hop
>   before the repair tunnel endpoint."
>
> Section 4.2.1:
> " In Figure 1 the intersection of the E's Q-space with S's P-space defines the set of
> viable repair tunnel end-points, known as "PQ nodes". "
> becomes:
> " In Figure 1 the intersection of the E's Q-space with S's P-space defines a set of
> viable repair tunnel end-points, known as "PQ nodes". "

SB> I think that the original is correct, since it is the set. Isn't it?
>
> Section 6:
>   "1.  Detect when a packet has arrived on some interface I that is also
>          the interface used to reach the first hop on the RLFA path to PQ,
>          and drop the packet.  This is useful in the case of a ring
>          topology."
> becomes:
> 1.  Detect when a packet has arrived on some interface I that is also
>          the interface used to reach the first hop on the RLFA path to the repair tunnel endpoint,
>          and drop the packet.  This is useful in the case of a ring
>          topology."
> And:
> "2.  Require that the path from PQ to destination D never passes
>         through E (including in the ECMP case), i.e. only use node
>         protecting paths in which the cost PQ to D is strictly less than
>         the cost PQ to E plus the cost E to D."
> becomes:
> "2.  Require that the path from the tunnel endpoint to destination D never passes
>         through E (including in the ECMP case), i.e. only use node
>         protecting paths in which the cost from tunnel endpoint to D is strictly less than
>         the cost from tunnel endpoint to E plus the cost E to D."
>
> Section 7 has several references to PQ where a generic reference to repair tunnel endpoint is
> more appropriate.  Proposed text is shown below.
>    
>     Where this technique is used in an MPLS network using LDP [RFC5036],
>     S will need to push two labels onto the repair packet.  First it
>     needs to push the label used by the repair tunnel endpoint to reach the destination, and then it needs to
>     push its own label for the tunnel endpoint.  In the example Section 3.1 [sic], C plays the role
>     of the tunnel endpoint.   S already has
>     the first hop (B) label for  node C as a result of the
>     ordinary operation of LDP.  To get the label used by C for the
>     destination (D), S needs to establish a targeted LDP session with C.
>     The label stack for normal operation and RLFA operation is shown
>     below in Figure 4.
>
>     To establish an targeted LDP session with a candidate tunnel endpoint node the
>     repairing node (S) needs to know what IP address the tunnel endpoint is willing to use
>     for targeted LDP sessions.  Ideally this is provided by the tunnel endpoint
>     advertising this address in the IGP in use.  Which address is used,
>     how this is advertised in the IGP, and whether this is a special IP
>     address or an IP address also used for some other purpose is out of
>     scope for this document and must be specified in an IGP specific RFC.
>
> Note that the existing reference to "the example section 3.1" is not clear.
SB> I have inspected all instances of PQ and used some combination of
SB> remote LFA repair target, PQ and remote LFA repair target (PQ) as
SB> seemed appropriate

- Stewart

>
> -----Original Message-----
> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Monday, October 28, 2013 2:03 PM
> To: rtgwg@ietf.org
> Subject: candidate-draft-ietf-rtgwg-remote-lfa-03.txt
>
> I have edited draft-ietf-rtgwg-remote-lfa-03.txt, and in view of the cut-off have put a copy here:
>
> https://www.dropbox.com/s/kahbqvrsww40qua/candidate-draft-ietf-rtgwg-remote-lfa-03.txt
>
> 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 stbryant@cisco.com  Fri Nov  1 10:24:50 2013
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 98B5111E8230 for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 10:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.489
X-Spam-Level: 
X-Spam-Status: No, score=-110.489 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 gZel7FsSZBac for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 10:24:43 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 4B9CB11E822C for <rtgwg@ietf.org>; Fri,  1 Nov 2013 10:24:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9359; q=dns/txt; s=iport; t=1383326680; x=1384536280; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to; bh=wKlSf19MV51ZKRMb00LAuo6KTcmkIGBOb0B2ul+dz4M=; b=UKrfjN80WReMcHWqy0aHzIjaPZWZJQljdI09y0fu1VJv6wiuT5vkFJHV WUzOKSDXyX25WReSQbBzFAGOaebqvbtiyRpiAOFE4VZ0VLXEWyWUY+DuW yMJ5I66NUj7F+U3t2nsXsQByxyxHEBc0eaBctwwlC5E8vvk493lVzPhE/ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAAjjc1KQ/khM/2dsb2JhbABZgkNEiXC0AoJ9gR4WdIIlAQEBAwEtUQsLDgoJJQ8CRgYBDAgBAReHZga9PY9fhC4DmAqSCYMm
X-IronPort-AV: E=Sophos;i="4.93,618,1378857600"; d="scan'208,217";a="18715187"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 01 Nov 2013 17:24:39 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rA1HOWuF018475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Nov 2013 17:24:34 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rA1HOVqZ000287; Fri, 1 Nov 2013 17:24:32 GMT
Message-ID: <5273E3CF.40809@cisco.com>
Date: Fri, 01 Nov 2013 17:24:31 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Chris Bowers <cbowers@juniper.net>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: issue#2 in candidate-draft-ietf-rtgwg-remote-lfa-03.txt
References: <e906ad2fb95343698f83af4cde5d78f0@BLUPR05MB292.namprd05.prod.outlook.com>
In-Reply-To: <e906ad2fb95343698f83af4cde5d78f0@BLUPR05MB292.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------020108050005000809030706"
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: Fri, 01 Nov 2013 17:24:50 -0000

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

On 29/10/2013 16:36, Chris Bowers wrote:
> The text in section 4.2.1 and 4.2.2 describing the (unextended) P-space calculation should be removed.
>   
> I agree with the Editor's note below in the comments for the Compute_Extended_P_Space() function in the algorithm pseudocode that the "if statement may be redundant since the foreach interface intf in self loop catches all cases."  That is, calculating (unextended) P-space is not needed.
>   
> The original algorithm text was written to mirror the existing description in section 4.2.2.
> "  Another way to describe extended P-space is that it is the union of (
>     un-extended ) P-space and the set of destinations for which S has a
>     per-prefix LFA protecting the link S-E. i.e. the repair tunnel end
>     point can be reached either directly or using a per-prefix LFA."
>   
> If we are in agreement that the (unextended) P-space is not needed, then sections 4.2.1 and 4.2.2 should be rewritten to eliminate or lessen the importance of (unextended) P-space since it doesn't serve a useful purpose in the text (except to motivate why it makes sense to use extended P-space.)
>   
I think that it is useful to talk about P space and then show how we can 
extend
it in terms of enabling the reader to understand the solution.

It is not clear whether we need uP or just eP, because the forwarding
actions are different (in eP the first hop is not the normal path to 
that node
that is in the FIB).

A lot of this a matter for the implementer and not a matter of protocol
correctness.

> In particular, section 4.2.1 contains the following definition of a PQ-node:
>   
>     "In Figure 1 the intersection of the E's Q-space with S's P-space
>      defines the set of viable repair tunnel end-points, known as "PQ nodes". "
>   
> This definition contradicts the definition of the PQ node in section 1.
>   
> "PQ node- A node which is a member of both the extended P-space
>           and the Q-space."
I have changes this to "A node which is a member of both the (extended) 
P-space and the Q-space. In remote LFA this is used as the repair tunnel 
endpoint."
which covers both cases.
>   
> I am happy to provide new text for sections 4.2.1 and 4.2.2 if we are in basic agreement on this.
>   
> Chris
>   
>

Please look at the revised text and if you are in Vancouver, perhaps we 
can talk.

- Stewart


--------------020108050005000809030706
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">
    <div class="moz-cite-prefix">On 29/10/2013 16:36, Chris Bowers
      wrote:<br>
    </div>
    <blockquote
cite="mid:e906ad2fb95343698f83af4cde5d78f0@BLUPR05MB292.namprd05.prod.outlook.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 15 (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;}
@font-face
	{font-family:"Courier\000D\000A              New";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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","serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	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="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">
        <pre>The text in section 4.2.1 and 4.2.2 describing the (unextended) P-space calculation should be removed.&nbsp; <o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>I agree with the Editor&#8217;s note below in the comments for the Compute_Extended_P_Space() function in the algorithm pseudocode that the &#8220;if statement may be redundant since the foreach interface intf in self loop catches all cases.&#8221;&nbsp; That is, calculating (unextended) P-space is not needed.<o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>The original algorithm text was written to mirror the existing description in section 4.2.2.<o:p></o:p></pre>
        <pre>&#8220;&nbsp; Another way to describe extended P-space is that it is the union of (<o:p></o:p></pre>
        <pre>&nbsp;&nbsp; un-extended ) P-space and the set of destinations for which S has a<o:p></o:p></pre>
        <pre>&nbsp;&nbsp; per-prefix LFA protecting the link S-E. i.e. the repair tunnel end<o:p></o:p></pre>
        <pre>&nbsp;&nbsp; point can be reached either directly or using a per-prefix LFA.&#8221;<o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>If we are in agreement that the (unextended) P-space is not needed, then sections 4.2.1 and 4.2.2 should be rewritten to eliminate or lessen the importance of (unextended) P-space since it doesn&#8217;t serve a useful purpose in the text (except to motivate why it makes sense to use extended P-space.)<o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
      </div>
    </blockquote>
    I think that it is useful to talk about P space and then show how we
    can extend<br>
    it in terms of enabling the reader to understand the solution.<br>
    <br>
    It is not clear whether we need uP or just eP, because the
    forwarding<br>
    actions are different (in eP the first hop is not the normal path to
    that node<br>
    that is in the FIB).<br>
    <br>
    A lot of this a matter for the implementer and not a matter of
    protocol<br>
    correctness.<br>
    <br>
    <blockquote
cite="mid:e906ad2fb95343698f83af4cde5d78f0@BLUPR05MB292.namprd05.prod.outlook.com"
      type="cite">
      <div class="WordSection1">
        <pre>In particular, section 4.2.1 contains the following definition of a PQ-node:<o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>&nbsp;&nbsp; &#8220;In Figure 1 the intersection of the E's Q-space with S's P-space <o:p></o:p></pre>
        <pre>&nbsp;&nbsp;&nbsp;&nbsp;defines the set of viable repair tunnel end-points, known as "PQ nodes". &#8220;<o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>This definition contradicts the definition of the PQ node in section 1.&nbsp; <o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>&#8220;PQ node- A node which is a member of both the extended P-space<o:p></o:p></pre>
        <pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the Q-space.&#8221;</pre>
      </div>
    </blockquote>
    I have changes this to "A node which is a member of both the
    (extended) P-space and the Q-space. In remote LFA this is used as
    the repair tunnel endpoint."<br>
    which covers both cases.<br>
    <blockquote
cite="mid:e906ad2fb95343698f83af4cde5d78f0@BLUPR05MB292.namprd05.prod.outlook.com"
      type="cite">
      <div class="WordSection1">
        <pre><o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>I am happy to provide new text for sections 4.2.1 and 4.2.2 if we are in basic agreement on this.<o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>Chris<o:p></o:p></pre>
        <pre><o:p>&nbsp;</o:p></pre>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
      </div>
    </blockquote>
    <br>
    Please look at the revised text and if you are in Vancouver, perhaps
    we can talk.<br>
    <br>
    - Stewart<br>
    <br>
  </body>
</html>

--------------020108050005000809030706--

From stbryant@cisco.com  Fri Nov  1 10:57:06 2013
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 A7E9E11E8230 for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 10:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.491
X-Spam-Level: 
X-Spam-Status: No, score=-110.491 tagged_above=-999 required=5 tests=[AWL=0.108, 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 wN9Hhxq64FfP for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 10:57:01 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 67AA111E8173 for <rtgwg@ietf.org>; Fri,  1 Nov 2013 10:57:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=180; q=dns/txt; s=iport; t=1383328621; x=1384538221; h=message-id:date:from:reply-to:mime-version:to:subject: content-transfer-encoding; bh=yywPNTo0x+rz+CQuxZGcqbuHfcY3oEf4s+pSOuAPn6I=; b=eboIJ5AuaUh7m5t43HKney/hacI8I0kZ3FYCRtRFUtr3pFaIeOWc8dsg w+Yua2ray/81R5WUqpFreexHLmr2XPvEOloe5ZkWcmnQ2Vrc/+aTGDDK0 PGrP5FzwyU5FzY14BSvlhppzDRwuAacZRib7kgWshetGovuVMTNWCFbEE 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkGAIfqc1KQ/khN/2dsb2JhbABZgwc4wVUWbQeCZEA9FhgDAgECAUsNCAEBiAMNnAOHAoxUjWkElA0DmAqSCYMm
X-IronPort-AV: E=Sophos;i="4.93,618,1378857600"; d="scan'208";a="161302133"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 01 Nov 2013 17:56:59 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA1HusOE006797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <rtgwg@ietf.org>; Fri, 1 Nov 2013 17:56:55 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rA1HurpM002504; Fri, 1 Nov 2013 17:56:53 GMT
Message-ID: <5273EB65.5050909@cisco.com>
Date: Fri, 01 Nov 2013 17:56:53 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: candidate2-draft-ietf-rtgwg-remote-lfa-03.txt
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Fri, 01 Nov 2013 17:57:06 -0000

Candidate 2 now in dropbox

https://www.dropbox.com/s/yvzvvra3ie8ojv0/candidate2%20-draft-ietf-rtgwg-remote-lfa-03.txt

Will upload to IETF site as soon as am able

Stewart

From stbryant@cisco.com  Fri Nov  1 11:26:55 2013
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 84ADD11E814D for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 11:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.492
X-Spam-Level: 
X-Spam-Status: No, score=-110.492 tagged_above=-999 required=5 tests=[AWL=0.107, 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 m71lF-lkZM8K for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 11:26:50 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9350011E817F for <rtgwg@ietf.org>; Fri,  1 Nov 2013 11:26:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=269; q=dns/txt; s=iport; t=1383330408; x=1384540008; h=message-id:date:from:reply-to:mime-version:to:cc:subject: content-transfer-encoding; bh=0m+cjqDmU+TZ7LYFv7m6kZoqnMbbpEvjgf5EcaicVVw=; b=CGltqQH3XUOlUKJrTT6aJKT+C6CGgQ6bVC0RJ4BjkBphE0ei/5VLmto6 IXKdNrbprLrRhw4yS4RaY9NuXF/eq2cy49Q5g3RRREX4Mldm8JkbvoNod J/haOuV7hT6+75e1Kuw+97scG6ncKUa4WViorsc+qqVuHFA7buV07ptAI M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoGAI3xc1KQ/khM/2dsb2JhbABZgwc4wDaBHhZtB4JkQAE8FhgDAgECAUsNAQcBAYgDDaMAjFSNZwSPWIQ1A5gKkgmDJg
X-IronPort-AV: E=Sophos;i="4.93,618,1378857600"; d="scan'208";a="87840756"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 01 Nov 2013 18:26:47 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rA1IQeAD003011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Nov 2013 18:26:42 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rA1IQeAn004204; Fri, 1 Nov 2013 18:26:40 GMT
Message-ID: <5273F260.5090402@cisco.com>
Date: Fri, 01 Nov 2013 18:26:40 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: candidate2-draft-ietf-rtgwg-remote-lfa-03
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.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: Fri, 01 Nov 2013 18:26:55 -0000

I don't think this got posted as aparently too long so sending it as 
simple ascii

Candidate 2 now in dropbox

https://www.dropbox.com/s/yvzvvra3ie8ojv0/candidate2%20-draft 
ietf-rtgwg-remote-lfa-03.txt

Will upload to IETF site as soon as am able

Stewart

From stbryant@cisco.com  Fri Nov  1 12:37:13 2013
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 DBB3611E8146 for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 12:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.493
X-Spam-Level: 
X-Spam-Status: No, score=-110.493 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 NDn+kWYeGjA1 for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 12:37:09 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id AC76A21E80FB for <rtgwg@ietf.org>; Fri,  1 Nov 2013 12:37:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2324; q=dns/txt; s=iport; t=1383334628; x=1384544228; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=AlGGJWJt1KLzsq4qrlHgACQn2XG2f73TTBDK/cxiyPg=; b=NYZBXMsz7/Rh6CPYxcjgLduHF7cEmroJINZ9W47ZNzeESrFya5EsF363 H2sTtIEa17zeEEImtmmFmKI17Mq/zCYQWVh4Y0tVXX1NvdQGs1DK7jaPg fnVdoJA3Y96jm1mCwvtR95J6NITa1io0TM6r776KNrNwdsYNFkT2h7j/+ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEIAPcBdFKQ/khM/2dsb2JhbABZgwc4BAECRohrtn+BHxZ0giUBAQEEeAEQCwQBCQoJFg8JAwIBAgFFBg0BBwEBiAMIBa9PjWyPWAeELgOYCoEviyaFNIMmcQE
X-IronPort-AV: E=Sophos;i="4.93,618,1378857600";  d="scan'208,217";a="161304842"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 01 Nov 2013 19:37:07 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rA1Jb1Oo019636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Nov 2013 19:37:03 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rA1Jb0Yl007551; Fri, 1 Nov 2013 19:37:01 GMT
Message-ID: <527402DC.9060008@cisco.com>
Date: Fri, 01 Nov 2013 19:37:00 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>
Subject: Re: candidate2-draft-ietf-rtgwg-remote-lfa-03
References: <5273F260.5090402@cisco.com> <CAG4d1rc02FVu2G0K8SXquDwwcKer1393SGKTgYKsh0a7JDL7=w@mail.gmail.com>
In-Reply-To: <CAG4d1rc02FVu2G0K8SXquDwwcKer1393SGKTgYKsh0a7JDL7=w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070701020305070808070006"
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: Fri, 01 Nov 2013 19:37:14 -0000

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

Sorry for the typo.

The link is

https://www.dropbox.com/s/yvzvvra3ie8ojv0/candidate2%20-draft-ietf-rtgwg-remote-lfa-03.txt

or

*http://tinyurl.com/kwr5ytz

Stewart
*

On 01/11/2013 18:31, Alia Atlas wrote:
> https://www.dropbox.com/s/yvzvvra3ie8ojv0/candidate2%20-draft 
> ietf-rtgwg-remote-lfa-03.txt


-- 
For corporate legal information go to:

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


--------------070701020305070808070006
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">
    <div class="moz-cite-prefix">Sorry for the typo.<br>
      <br>
      The link is<br>
      <br>
<a class="moz-txt-link-freetext" href="https://www.dropbox.com/s/yvzvvra3ie8ojv0/candidate2%20-draft-ietf-rtgwg-remote-lfa-03.txt">https://www.dropbox.com/s/yvzvvra3ie8ojv0/candidate2%20-draft-ietf-rtgwg-remote-lfa-03.txt</a><br>
      <br>
      or <br>
      <br>
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      <b><a class="moz-txt-link-freetext" href="http://tinyurl.com/kwr5ytz">http://tinyurl.com/kwr5ytz</a><br>
        <br>
        Stewart<br>
      </b><br>
      <br>
      On 01/11/2013 18:31, Alia Atlas wrote:<br>
    </div>
    <blockquote
cite="mid:CAG4d1rc02FVu2G0K8SXquDwwcKer1393SGKTgYKsh0a7JDL7=w@mail.gmail.com"
      type="cite"><a moz-do-not-send="true"
        href="https://www.dropbox.com/s/yvzvvra3ie8ojv0/candidate2%20-draft"
        target="_blank">https://www.dropbox.com/s/yvzvvra3ie8ojv0/candidate2%20-draft</a>
      ietf-rtgwg-remote-lfa-03.txt</blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------070701020305070808070006--

From fred@cisco.com  Fri Nov  1 14:16:30 2013
Return-Path: <fred@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 599F411E8184 for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 14:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.523
X-Spam-Level: 
X-Spam-Status: No, score=-110.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 DpBaFfFL2RwI for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 14:16:25 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDFB11E8160 for <rtgwg@ietf.org>; Fri,  1 Nov 2013 14:16:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8299; q=dns/txt; s=iport; t=1383340561; x=1384550161; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=yzuAO90uXNtrmhYq07flxovC2O8KVCHufPbvO3GLJ7g=; b=UwSq3NFE82jr8cFxuk9u3LfZB2TZFHTardW5vGe1FYEBRefH6bIjtxwJ 8oFbRyTUd/NOeMiw23uMlGKdQXs0n3++Rn6Ow4GiwHijw/J7ORCWNnFJz kHWsWmedFvOdwK3f0WxWFQPv+rK3QZGessxM+r+KpFejsSGuVJjn82DWH Q=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikGAGgZdFKtJXG//2dsb2JhbABZgkNEOFO3LIhFgR8WdIIlAQEBAwEBAQFrCwULAgEIGAokIQYLJQIEDgUIBodnAwkGDbMyDYlrjGiCPy0EB4MggQ4DkC6BMIRBgxqLI4U3gyaCKg
X-IronPort-AV: E=Sophos;i="4.93,619,1378857600";  d="asc'?scan'208,217";a="279718315"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-4.cisco.com with ESMTP; 01 Nov 2013 21:16:00 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA1LG07v005511 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Nov 2013 21:16:00 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Fri, 1 Nov 2013 16:15:59 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Subject: Re: IETF 88 Agenda Items
Thread-Topic: IETF 88 Agenda Items
Thread-Index: AQHOvu+xvvXhYYVgF0uuaDZky93MeJoDBJsAgAkbnQCAAHecAIAEzTwA
Date: Fri, 1 Nov 2013 21:15:59 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA85741@xmb-rcd-x09.cisco.com>
References: <BBD66FD99311804F80324E8139B3C94E396BA6FD@xmb-aln-x15.cisco.com> <BBD66FD99311804F80324E8139B3C94E396F480A@xmb-aln-x15.cisco.com> <CA+RyBmVw4Pn2yMdXJ73r+VSdArCUvumQVrBHqKoyj1rhgR_iNw@mail.gmail.com>
In-Reply-To: <CA+RyBmVw4Pn2yMdXJ73r+VSdArCUvumQVrBHqKoyj1rhgR_iNw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.120]
Content-Type: multipart/signed; boundary="Apple-Mail=_43527D8F-2813-4579-883A-ACF8BC076C70"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
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, 01 Nov 2013 21:16:30 -0000

--Apple-Mail=_43527D8F-2813-4579-883A-ACF8BC076C70
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_473ECCDB-F5D8-4641-BFD5-53F6C8824A78"


--Apple-Mail=_473ECCDB-F5D8-4641-BFD5-53F6C8824A78
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 29, 2013, at 12:56 PM, Greg Mirsky <gregimirsky@gmail.com> wrote:

> Hi,
> this question may be more addressed to Fred Would the following fit as =
well or even better into SPRING WG:
> Requirements and Use Cases for Source/Destination Routing
>   =
http://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cases
>   Fred Baker   =20

Per https://datatracker.ietf.org/doc/charter-ietf-spring/, SPRING is =
about source routing (having the host indicate a set of routers that a =
packet must traverse, as in IPv4 source-route-and-record), not routing =
to a destination and using different destination routes depending on the =
source prefix. Happens to have one word in common, but no concepts.

> Unfortunately agenda for SPRING not yet available.
>=20
> Regards,
> Greg
>=20
>=20
>=20
> On Tue, Oct 29, 2013 at 9:48 AM, Alvaro Retana (aretana) =
<aretana@cisco.com> wrote:
> On 10/23/13 5:43 PM, "Alvaro Retana (aretana)" <aretana@cisco.com> =
wrote:
>=20
> I just published the draft agenda here:  =
https://datatracker.ietf.org/meeting/88/agenda/rtgwg/
>=20
> Just updated the agenda to the final one.
>=20
> Alvaro.
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>=20
>=20
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg

----------------------------------------------------
The ignorance of how to use new knowledge stockpiles exponentially.=20
   - Marshall McLuhan


--Apple-Mail=_473ECCDB-F5D8-4641-BFD5-53F6C8824A78
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 29, 2013, at 12:56 PM, Greg Mirsky &lt;<a =
href=3D"mailto:gregimirsky@gmail.com">gregimirsky@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Diso-8859-1"><div dir=3D"ltr"><div>Hi,<br></div>this question =
may be more addressed to Fred Would the following fit as well or even =
better into SPRING WG:<br><pre>Requirements and Use Cases for =
Source/Destination Routing
  <a =
href=3D"http://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-c=
ases">http://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cas=
es</a>
  Fred Baker    <br></pre></div></blockquote><div =
dir=3D"ltr"><pre><br></pre><pre>Per <a =
href=3D"https://datatracker.ietf.org/doc/charter-ietf-spring/">https://dat=
atracker.ietf.org/doc/charter-ietf-spring/</a>, SPRING is about source =
routing (having the host indicate a set of routers that a packet must =
traverse, as in IPv4 source-route-and-record), not routing to a =
destination and using different destination routes depending on the =
source prefix. Happens to have one word in common, but no =
concepts.</pre><pre><br></pre></div><blockquote type=3D"cite"><div =
dir=3D"ltr"><pre>Unfortunately agenda for SPRING not yet =
available.<br><br></pre><pre>Regards,<br></pre><pre>Greg<br></pre><br></di=
v><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, =
Oct 29, 2013 at 9:48 AM, Alvaro Retana (aretana) <span dir=3D"ltr">&lt;<a =
href=3D"mailto:aretana@cisco.com" =
target=3D"_blank">aretana@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">



<div =
style=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-wor=
d">
<div>On 10/23/13 5:43 PM, "Alvaro Retana (aretana)" &lt;<a =
href=3D"mailto:aretana@cisco.com" =
target=3D"_blank">aretana@cisco.com</a>&gt; wrote:</div>
<span>
<div><br>
</div>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 =
5;MARGIN:0 0 0 5">
<div =
style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;text-al=
ign:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;t=
ext-transform:none;font-size:14px;white-space:normal;font-family:Calibri,s=
ans-serif;word-spacing:0px">

I just published the draft agenda here: &nbsp;<a =
href=3D"https://datatracker.ietf.org/meeting/88/agenda/rtgwg" =
target=3D"_blank">https://datatracker.ietf.org/meeting/88/agenda/rtgwg</a>=
/</div>
</blockquote>
</span>
<div><br>
</div>
<div>Just updated the agenda to the final one.</div><span =
class=3D"HOEnZb"><font color=3D"#888888">
<div><br>
</div>
<div>Alvaro.</div>
</font></span></div>

<br>_______________________________________________<br>
rtgwg mailing list<br>
<a href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/rtgwg" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/rtgwg</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>rtgwg mailing =
list<br><a =
href=3D"mailto:rtgwg@ietf.org">rtgwg@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/rtgwg<br></blockquote></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); 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>----------------------------------------------------</div><div><spa=
n class=3D"Apple-style-span" style=3D"color: rgb(34, 34, 34); =
font-family: arial, sans-serif; line-height: 12px; font-size: small; =
">The&nbsp;</span><span class=3D"Apple-style-span" style=3D"color: =
rgb(34, 34, 34); font-family: arial, sans-serif; line-height: 12px; =
font-size: small; "><em style=3D"font-style: normal; color: rgb(0, 0, =
0); ">ignorance</em></span><span class=3D"Apple-style-span" =
style=3D"color: rgb(34, 34, 34); font-family: arial, sans-serif; =
line-height: 12px; font-size: small; ">&nbsp;of how to&nbsp;</span><span =
class=3D"Apple-style-span" style=3D"color: rgb(34, 34, 34); font-family: =
arial, sans-serif; line-height: 12px; font-size: small; "><em =
style=3D"font-style: normal; color: rgb(0, 0, 0); ">use =
new</em></span><span class=3D"Apple-style-span" style=3D"color: rgb(34, =
34, 34); font-family: arial, sans-serif; line-height: 12px; font-size: =
small; ">&nbsp;knowledge&nbsp;</span><span class=3D"Apple-style-span" =
style=3D"color: rgb(34, 34, 34); font-family: arial, sans-serif; =
line-height: 12px; font-size: small; "><em style=3D"font-style: normal; =
color: rgb(0, 0, 0); ">stockpiles exponentially</em></span><span =
class=3D"Apple-style-span" style=3D"color: rgb(34, 34, 34); font-family: =
arial, sans-serif; line-height: 12px; font-size: small; =
">.</span>&nbsp;</div><div>&nbsp;&nbsp; - Marshall McLuhan</div></span>
</div>
<br></body></html>=

--Apple-Mail=_473ECCDB-F5D8-4641-BFD5-53F6C8824A78--

--Apple-Mail=_43527D8F-2813-4579-883A-ACF8BC076C70
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSdBoObjEdbHIsm0MRAnYTAKDnMvkDnX6URnOhPXwjlOBrIuirPwCfX71X
KFeAZWEp0/Mhd3ANuJ0QVq4=
=kwYn
-----END PGP SIGNATURE-----

--Apple-Mail=_43527D8F-2813-4579-883A-ACF8BC076C70--

From stbryant@cisco.com  Fri Nov  1 09:46:49 2013
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 4967F11E827A for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 09:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.066
X-Spam-Level: 
X-Spam-Status: No, score=-108.066 tagged_above=-999 required=5 tests=[AWL=-2.368, BAYES_50=0.001, HTML_MESSAGE=0.001, MANGLED_SAVELE=2.3, 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 MhE3jmOsiWwb for <rtgwg@ietfa.amsl.com>; Fri,  1 Nov 2013 09:46:41 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD7811E822F for <rtgwg@ietf.org>; Fri,  1 Nov 2013 09:46:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=75655; q=dns/txt; s=iport; t=1383324396; x=1384533996; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to; bh=cBWz6EvcYG/VQCPSZwxOHqOQR3LE2HlSsbT+T295OSQ=; b=gwoGeUhaoa0rkTp38ABKymAd2Tu1a3rJa2lxord6bdMPyopVJv5suBCU 8ABVo7nkwJgkWrPauwyGzZCBwCOAiBbGbuiZACg/A0EW638YSNOXzCBEO hQ6RUTt5k0uI+935pGiVeVY+1uRM9L3B2WLgUlv9z1monJnWkKde9NqT4 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAODZc1KQ/khM/2dsb2JhbABPCoMHiXC2f4EeFnSCJQEBAQMBGgEMPggLBgsLIRYBAQ0JAwIBAgFFBgEMBgIBAReHZga9QI4OBwWBRYQuA5Qrg1+SCYMmgWk
X-IronPort-AV: E=Sophos;i="4.93,618,1378857600";  d="scan'208,217";a="161299846"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 01 Nov 2013 16:46:34 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rA1GkSvW006565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Nov 2013 16:46:29 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rA1GkR9E028445; Fri, 1 Nov 2013 16:46:27 GMT
Message-ID: <5273DAE3.2090706@cisco.com>
Date: Fri, 01 Nov 2013 16:46:27 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: stephane.litkowski@orange.com, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: candidate-draft-ietf-rtgwg-remote-lfa-03.txt
References: <526EB4FE.3020507@cisco.com> <5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr>
In-Reply-To: <5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr>
Content-Type: multipart/alternative; boundary="------------070602040000090003070008"
X-Mailman-Approved-At: Sun, 03 Nov 2013 08:31:03 -0800
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: Fri, 01 Nov 2013 16:46:49 -0000

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

On 29/10/2013 15:17, stephane.litkowski@orange.com wrote:

Stephane

Thank you for your comments.
>
>
>     Q-space        Q-space is the set of routers from which a specific
>                    router can be reached without any path (including
>                    equal cost path splits) transiting the protected link.
>
> [SLI] Should swap Q-Space and PQ node definition placement, as PQ node refers to Q-Space definition.
SB> Yes, but the list is in alphabetical order rather than in
SB> declarative order.
SB> I suggest that alphabetical is a normal ordering for
SB> such an index of terms.
>
> 2.  Introduction
>
>     RFC 5714 [RFC5714] describes a framework for IP Fast Re-route and
>     provides a summary of various proposed IPFRR solutions.  A basic
>     mechanism using loop-free alternates (LFAs) is described in [RFC5286]
>     that provides good repair coverage in many
>     topologies[I-D.filsfils-rtgwg-lfa-applicability], especially those
>     that are highly meshed.  However, some topologies, notably ring based
>     topologies are not well protected by LFAs alone.  This is illustrated
>     in Figure 1 below.
>     
>     [SLI] Replace [I-D.filsfils-rtgwg-lfa-applicability] by RFC6571
Good catch - done.
>     
>
>               S---E
>              /     \
>             A       D
>              \     /
>               B---C
>
>
>
>
> Bryant, et al.            Expires May 01, 2014                  [Page 3]
>
> Internet-Draft               Remote LFA FRR                 October 2013
>
>
>                       Figure 1: A simple ring topology
>
>     If all link costs are equal, the link S-E cannot be fully protected
>     by LFAs.  The destination C is an ECMP from S, and so can be
>     protected when S-E fails, but D and E are not protectable using LFAs
>
>     This draft describes extensions to the basic ([SLI] add "basic LFA repair ...") repair mechanism in
>     which tunnels are used to provide additional logical links which can
>     then be used as loop free alternates where none exist in the original
>     topology.  For example if a tunnel is provided between S and C as
>     shown in Figure 2 then C, now being a direct neighbor of S would
>     become an LFA for D and E. The non-failure traffic distribution is
>     not disrupted by the provision of such a tunnel since it is only used
>     for repair traffic and MUST NOT be used for normal traffic.
>
>            S---E
>           / \   \
>          A   \   D
>           \   \ /
>            B---C
>
>                      Figure 2: The addition of a tunnel
>
>     The use of this technique is not restricted to ring based topologies,
>     but is a general mechanism which can be used to enhance the
>     protection provided by LFAs.  A study of the protection achieved
>     using remote LFA in typical service provider core networks is
>     provided in Section 8, and a side by side comparison between LFA and
>     remote LFA is provided in Section 8.4.
>
>     Remote LFA is suitable for incremental deployment within a network,
>     including a network that is already deploying LFA.  Computation of
>     the repair path is relatively simple, and takes place exclusively on
>     the repairing node.  In MPLS networks the targeted LDP protocol
>     needed to learn the label binding at the repair tunnel endpoint is a
>     well understood and widely deployed technology.
>
>     This technique describes in this document is directed at providing
>     repairs in the case of link failures.  Considerations regarding node
>     failures are discussed in Section 6.
>
> 3.  Repair Paths
>
>     As with LFA FRR, when a router detects an adjacent link failure, it
>     uses one or more repair paths in place of the failed link.  Repair
>     paths are pre-computed in anticipation of later failures so they can
>     be promptly activated when a failure is detected.
>
>
>
>
> Bryant, et al.            Expires May 01, 2014                  [Page 4]
>
> Internet-Draft               Remote LFA FRR                 October 2013
>
>
>     A tunneled repair path tunnels traffic to some staging point in the
>     network from which it is assumed that, in the absence of multiple
>     failures, it will travel to its destination using normal forwarding
>     without looping back.  This is equivalent to providing a virtual
>     loop-free alternate to supplement the physical loop-free alternates.
>     Hence the name "Remote LFA FRR".  When a link cannot be entirely
>     protected with local LFA neighbors, the protecting router seeks the
>     help of a remote LFA staging point.
>     
>     [SLI] Not a good idea to seek rLFA only when LFA is not available (see manageability)
SB> This now says:
In its simplest form, when a link cannot be entirely protected with 
local LFA
neighbors, the protecting router seeks the help of a remote LFA staging 
point.
Network manageability considerations may lead to a repair strategy that
uses a remote LFA more frequently [I-D.ietf-rtgwg-lfa-manageability]

>
> 3.2.  Tunnel Requirements
>
>
>
>     automatically established as a basic property of LDP behavior.  The
>     performance of the encapsulation and decapsulation is also excellent
>     as encapsulation is just a push of one label (like conventional MPLS
>     TE FRR) and the decapsulation occurs naturally at the penultimate hop
>     before the PQ node.
>    [SLI] Ok the tunnel is already available, but you need some time to establish the protection (TLDP session establishment + label learning time).
> 	This is important to precise this.

SB> The text now says:

The performance of the encapsulation and decapsulation is efficient as 
encapsulation
is just a push of one label (like conventional MPLS TE FRR) and the 
decapsulation
occurs naturally at the penultimate hop before the PQ node. In the 
control plane,
a targeted LDP (TLDP) session is needed between the repairing node and the
repair tunnel endpoint, which will need to be established and the labels 
processed
before the tunnel can be used. The time to establish the TLDP session 
and acquire
labels will limit the speed at which a new tunnel can be put into 
service, but this
will not be a problem in normal operation.
> 	
>     When a failure is detected, it is necessary to immediately redirect
>     traffic to the repair path.  Consequently, the repair tunnel used
>     must be provisioned beforehand in anticipation of the failure.  Since
>     the location of the repair tunnels is dynamically determined it is
>     necessary to establish the repair tunnels without management action.
>     [SLI] s/management action/manual provisionning action/ , as management may be needed to tweak the best tunnel tailend.
SB> I have changed this to:
Since the location of the repair tunnels is dynamically determined it is
necessary to automatically establish the repair tunnels.

This covers both protocol and NMS and excludes humans.
>   
> 4.2.1.  Computing Repair Paths
>
>     In the case of Figure 1 the Q-space
>     comprises nodes C and D only.  Expressed in cost terms the set of
>     routers {Q} are those for which the shortest path cost E->Q is
>     strictly less than the shortest path cost E->S->Q.
>     
>     [SLI] Would it be Q->E less than Q->S->E

SB> Thanks

> 4.2.2.  Extended P-space
>
>
>
>     Another way to describe extended P-space is that it is the union of (
>     un-extended ) P-space and the set of destinations for which S has a
>     per-prefix LFA protecting the link S-E. i.e. the repair tunnel end
>     point can be reached either directly or using a per-prefix LFA.
>
>     	[SLI] Lack of precision about independancy of rLFA and LFA alternate choice is rLFA is using extended P space node.
> 	I would propose :
> 	
> 	"Even if extended P-space would be composed on nodes reachable through a per-prefix LFA, this does not conclude that the rLFA would inherit the best LFA to reach the PQ:
> 	rLFA an LFA MUST be completely independant. In other words, if S has N1 and N2 as LFAs to protection a destination P, and S wants to use P as PQ to protect a destination D.
> 	S must be able to program N1 as LFA to reach P and P through N2 to reach D for manageability reasons (refer to Section 9)."

SB> We are talking about different things. This is not about whether
SB> or not we use LFA and RLFA together. This is another way
SB> of expressing extended P-space. Extended P-space
SB> is everything that E can reach on its own + everything that
SB> it can reach by forcing the first hop to a directly connected
SB> neighbour - which is what a per-prefix LFA is. The
SB> para is purely tutorial, and can be removed.

>
>
> 	
> 4.2.3.  Selecting Repair Paths
>
>     The mechanisms described above will identify all the possible repair
>     tunnel end points that can be used to protect a particular link.  In
>     a well-connected network there are likely to be multiple possible
>     release points for each protected link.  All will deliver the packets
>     correctly so, arguably, it does not matter which is chosen.  However,
>     one repair tunnel end point may be preferred over the others on the
>     basis of path cost or some other selection criteria.
>
>     There is no technical requirement for the selection criteria to be
>     consistent across all routers, but such consistency may be desirable
>     from an operational point of view.  In general there are advantages
>     in choosing the repair tunnel end point closest (shortest metric) to
>     S. Choosing the closest maximises the opportunity for the traffic to
>     be load balanced once it has been released from the tunnel.  For
>     consistency in behavior is RECOMMENDED that member of the set of
>     routers {P} with the lowest cost S->P be the default choice for P. In
>     the event of a tie the router with the lowest node identifier SHOULD
>     be selected.
>     
>     [SLI] Need to replace P by PQ : "For
>     consistency in behavior is RECOMMENDED that member of the set of
>     routers {PQ} with the lowest cost S->PQ be the default choice for PQ."
>     
SB> Done.
>
> 4.3.  A Cost Based RLFA Algorithm
>
>     The preceding text has mostly described the computation of the remote
>     LFA repair point (PQ) in terms of the intersection of two
>     reachability graphs computed using SPFs.  This section describes a
>     method of computing the repair point using a cost based algorithm.
>     
>     [SLI] "repair point" is confusing as a repair point is a PLR and here we talk about PQ.
>     Could we use "Remote LFA" instead ?
SB> It now says:

The preceding text has mostly described the computation of the remote 
LFA repair
target (PQ) in terms of the intersection of two reachability graphs 
computed using
SPFs. This section describes a method of computing PQ using a cost based 
algorithm.

The first sentence reminds the reader what PQ is, so I think this is clear.
>     
>     The pseudo-code provides in this section avoids unnecessary SPF
>     computations, but for the sake of readability, it does not otherwise
>     try to optimize the code.  Unconventionally, but for clarity, we
>     provide the main algorithm followed its procedures.  In this
>     description D_opt(a,b) is the shortest distance from node a to node b
>     as computed by the SPF.
>
> 	[SLI] Changing the pseudocode and create a remote LFA function as step of rLFA computation are here mixed with subfunctions.
> 	Proposal here :

SB> The problem is with hitting the 72 col limit.
SB> I have marked this with comments
SB> Hopefully this is now clear.
>
> 	// Remote LFA computation function
> 	
> 	main {
> 	  //////////////////////////////////////////////////////////////////
>        //
>        // We have already computed the forward SPF from self to all nodes
>        // y in network and thus we know D_opt (self, y). This is needed
>        // for normal forwarding.
>        // However for completeness.
>
>        Compute_and_Store_Forward_SPF(self)
>
> 	  // Need to compute rSPF(self) to compute cost based Q Space (done only one time)
> 	  Compute_and_Store_Reverse_SPF(self)

SB> This was only done once in the original.
> 		
>        // To extend P-space we compute the SPF at each neighbour except
>        // the neighbour that is reached via the link being protected.
>        // We will also need D_opt(fail_intf.remote_node,y) so compute
>        // that at the same time.
>
>        foreach interface intf in self
>                Compute_and_Store_Forward_SPF(intf.remote_node)
> 		[SLI] I removed the Compute_Neighbor_SPFs as , IMHO, it complexifies the readability ...

SB> This is tricky, because whilst true, the implementation will
SB> need to know which are which since it normally needs to
SB> deal with them differently in the FIB code.
SB> However I have taken it out.

> 		
> 	  // Compute rLFA for each interface
> 	  foreach interface fail_intf in self
> 		Compute_RLFA(fail_intf)
> 	}
> 	
> 	Compute_RLFA(fail_intf) {
> 	
>        // Compute the set of nodes {P} reachable other than via the
>        // failed link
>
>        Compute_Extended_P_Space(fail_intf)
> 	[SLI] Adding "fail_intf" as parameter
SB> OK, although it was correct as a global.
> 	
>        // Compute the set of nodes that can reach the node on the far
>        // side of the failed link without traversing the failed link.
>
>        Compute_Q_Space(fail_intf)
> 	[SLI] Adding "fail_intf" as parameter

SB> See above
>
>        // Compute the set of candidate RLFA tunnel endpoints
>
>
>
>
> Bryant, et al.            Expires May 01, 2014                  [Page 9]
>
> Internet-Draft               Remote LFA FRR                 October 2013
>
>
>        Intersect_Extended_P_and_Q_Space()
>
>        // Make sure that we cannot get looping repairs when the
>        // failure is worse than expected.
>
>        if (guarantee_no_looping_on_worse_than_protected_failure)
>            Apply_Downstream_Constraint()
> }
>
>
> 	// Sub functions
> 	
>        /////////////////////////////////////////////////////////////////
>        //
>        // This computes the SPF from root, and stores the optimum
>        // distance from root to each node y
>
>        Compute_and_Store_Forward_SPF(root)
>            Compute_Forward_SPF(root)
>            foreach node y in network
>                store D_opt(root,y)
>
> 	[SLI] I would add a comment to the function :
> 	
>        Compute_and_Store_Forward_SPF(root)
>            Compute_Forward_SPF(root)		// A SPF may already been in cache and so may be no need to recompute it
>            foreach node y in network
>                store D_opt(root,y)
SB> That was covered in my comment in main.

>
>        /////////////////////////////////////////////////////////////////
>        //
>        // The reverse SPF computes the cost from each remote node to
>        // root. This is achieved by running the normal SPF algorithm,
>        // but using the link cost in the direction from the next hop
>        // back towards root in place of the link cost in the direction
>        // away from root towards the next hop.
>
>        Compute_and_Store_Reverse_SPF(root)
>            Compute_Reverse_SPF(root)
>            foreach node y in network
>                store D_opt(y,root)
>
>
>
>
>
> Bryant, et al.            Expires May 01, 2014                 [Page 10]
>
> Internet-Draft               Remote LFA FRR                 October 2013
>
>
>        /////////////////////////////////////////////////////////////////
>        //
>        // Calculate P space and then extend it by the P-spaces of each
>        // neighbour other than the one reachable via the link being
>        // protected. Note the strictly less than operator is needed to
>        // avoid ECMP issues.
>
>        Compute_Extended_P_Space()
>            foreach node y in network
>                y.in_extended_P_space = false
>                // Compute P-space
>                //
>                // Editor's note, I think that this if statement may be
>                // redundant since the foreach interface intf in self
>                // loop catches all cases.
> 			
> 			  [SLI] Yes, IMHO, this is redundant.
SB> I took it out
>                
> 			  //
>                // Editor's note D_opt(fail_intf.remote_node,y) requires
>                // an SPF from neighbour fail_intf.remote_node so did
>                // this as part of all neighbours SPF calculation
>                if (D_opt(self, y) <
>                        D_opt(self, fail_intf.remote_node) +
>                        D_opt(fail_intf.remote_node,y))
>                    y.in_extended_P_space = true
>                // Extend P-space to the P-spaces of all reachable
>                // neighbours
>                foreach interface intf in self
>                    if (intf.remote_node != fail_intf.remote_node)
>                        if ( D_opt(intf.remote_node, y) <
>                             D_opt(intf.remote_node, self) +
>                             D_opt(self,fail_intf.remote_node) +
>                             D_opt(fail_intf.remote_node,y) )
>                         y.in_extended_P_space = true
>
>
>
>        /////////////////////////////////////////////////////////////////
>        //
>
>        Compute_Q_Space(fail_intf)
>            // Compute the cost from every node the network to the
>            // node normally reachable across the failed link
>            Compute_and_Store_Reverse_SPF(fail_intf.remote_node)
>
>            // Compute the cost from every node the network to self
>             [SLI] Need to be removed I putted it in main code (optimize number of SPF)
SB> It is fine here. Main does not need to know about this calc since
SB> it is not shared.
>
>            foreach node y in network
>                if ( D_opt(y,fail_intf.remote_node) < D_opt(y,self) +
>
>
>
> Bryant, et al.            Expires May 01, 2014                 [Page 11]
>
> Internet-Draft               Remote LFA FRR                 October 2013
>
>
>                        D_opt(self,fail_intf.remote_node) )
>                    y.in_Q_space = true
>                else
>                    y.in_Q_space = false
>
>
>
>        /////////////////////////////////////////////////////////////////
>        //
>        // Compute set of nodes in both extended P-space and in Q-space
>
>        Intersect_Extended_P_and_Q_Space()
>            foreach node y in network
>                if ( y.in_extended_P_space && y.in_Q_space )
>                    y.valid_tunnel_endpoint = true
>                else
>                    y.valid_tunnel_endpoint = false
>
>
>
>        /////////////////////////////////////////////////////////////////
>        //
>        // A downstream route is one where the next hop is strictly
>        // closer to the destination. By sending the packet to a
>        // PQ node that is downstream, we know that if the PQ node
>        // detects a failure, it will not loop the packet back to self.
>        // This is useful when there are two failures, or a node has
>        // failed rather than a link.
>
>        Apply_Downstream_Constraint()
>            foreach node y in network
>                if (y.valid_tunnel_endpoint)
>                    Compute_and_Store_Forward_SPF(y)
>                    if ((D_opt(y,dest) < D_opt(self,dest))
>                        y.valid_tunnel_endpoint = true
>                    else
>                        y.valid_tunnel_endpoint = false
> 	[SLI] Based on my simulations, Compute_and_Store_Forward_SPF(y) would not be possible as number of y.valid_tunnel_endpoint == true is very high !
> 	So downstreamness could not be established so easily ... even if it's theorical working.
SB> Yes - well - whatever the consenus is I will leave it in or take it out

>            |    100    |
>           -P2---------P1-
>             \         /
>         1000 \       / 1000
>              PE1---PE2
>                  5
>
>                         Figure 3: Example SP topology
>
>     Clearly, full protection can be provided, using the techniques
>     described in this draft, by PE1 choosing P2 as a PQ node, and PE2
>     choosing P1 as a PQ node.
>     
>     [SLI] Would it be "PE1 choosing P1" and "PE2 choosing P2" ?
SB> yes, changed.
>
> 6.  Node Failures
>
>     When the failure is a node failure rather than a link failure there
>     is a danger that the RLFA repair will loop.  This is discussed in
>     detail in [I-D.bryant-ipfrr-tunnels].  In summary problem is that two
>     of more of E's neighbors each with E as the next hop to some
>     destination D may attempt to repair a packet addressed to destination
>     D via the other neighbor and then E, thus causing a loop to form.  As
>     will be noted from [I-D.bryant-ipfrr-tunnels], this can rapidly
>     become a complex problem to address.
>
>
>
>
>
>
> Bryant, et al.            Expires May 01, 2014                 [Page 13]
>
> Internet-Draft               Remote LFA FRR                 October 2013
>
>
>     There are a number of ways to minimize the probability of a loop
>     forming when a node failure occurs and there exists the possibility
>     that two of E's neighbors may form a mutual repair.
>
>     1.  Detect when a packet has arrived on some interface I that is also
>         the interface used to reach the first hop on the RLFA path to PQ,
>         and drop the packet.  This is useful in the case of a ring
>         topology.
> [SLI] This has several drawbacks, especially this may cause some "legal packet" drops ...
>   
This needs fixing in the commentary text below.
> 	
>     2.  Require that the path from PQ to destination D never passes
>         through E (including in the ECMP case), i.e. only use node
>         protecting paths in which the cost PQ to D is strictly less than
>         the cost PQ to E plus the cost E to D.
>
>     3.  Require that where the packet may pass through another neighbor
>         of E, that node is down stream (i.e. strictly closer to D than
>         the repairing node).  This means that some neighbor of E (X) can
>         repair via some other neighbor of E (Y), but Y cannot repair via
>         X.
>
>     Case 1 accepts that loops may form and suppresses them by dropping
>     packets.  Dropping packets may be considered less detrimental than
>     looping packets.

SB> I have added "This approach may also lead to dropping some 
legitimate packets."
> Cases 2 and 3 above prevent the formation of a
>     loop, but at the expense of a reduced repair coverage and at the cost
>     of additional complexity in the algorithm to compute the repair path.
>
>     The probability of a node failure and the consequences of node
>     failure in any particular topology will depend on the node design,
>     the particular topology in use, and node failure strategy (including
>     the null strategy).  It is recommended that a network operator
>     perform an analysis of the consequences and probability of node
>     failure in their network, and determine whether the incidence and
>     consequence of occurrence are acceptable.
>
>     This topic is further discussed in
>     [I-D.psarkar-rtgwg-rlfa-node-protection].
>
> 7.  Operation in an LDP environment
>
>     Where this technique is used in an MPLS network using LDP [RFC5036],
>     S will need to push two labels onto the repair packet.  First it
>     needs to push PQ's label to the destination, and then it needs to
>     push its own label for PQ.
>     
>     [SLI] If S is transit node, it swaps incoming label to PQ's label to the dest and then push.
>     So to simplify, I would say : "S need to push an additional label onto the repair packet".

SB> It now says:
"and S is a transit node, S will need to swap the top label in the stack 
for PQ's
label to the destination, and to push its own label for PQ. "
>     
>     In the example Section 3.1 S already has
>     [SLI] The example is in Section 2
SB> Thanks - corrected the anchor
>     
>     the first hop (B) label for the PQ node (C) as a result of the
>     [SLI] Would it be "the first hop (A)" ?

SB> Yes.
>     
>     ordinary operation of LDP.  To get the PQ node (C) label for the
>     destination (D), S needs to establish a targeted LDP session with C.
>     The label stack for normal operation and RLFA operation is shown
>     below in Figure 4.
>
>
>
> Bryant, et al.            Expires May 01, 2014                 [Page 14]
>
> Internet-Draft               Remote LFA FRR                 October 2013
>
>
>     +-----------------+     +-----------------+     +-----------------+
>     |    datalink     |     |    datalink     |     |    datalink     |
>     +-----------------+     +-----------------+     +-----------------+
>     | S's label for D |     | E's label for D |     | C's label for D |
>     +-----------------+     +-----------------+     +-----------------+
>     |    Payload      |     |    Payload      |     | B's label for C |
>     +-----------------+     +-----------------+     +-----------------+
>             X                       Y               |    Payload      |
>                                                     +-----------------+
>                                                              Z
>
>     X = Normal label stack packet arriving at S
>     Y = Normal label stack packet leaving S
>     Z = RLFA label stack to D via C as PQ node
>
> 	[SLI] In Z, would it be "A's label for C", as A is the nexthop to reach C from S.
SB> I think that actually there were two errors
SB> Here is what the stack needs to look like

+-----------------+ +-----------------+     +-----------------+
|    datalink     |     |    datalink     |     |    datalink |
+-----------------+     +-----------------+ +-----------------+
| S's label for D |     | E's label for D |     | A's label for C |
+-----------------+     +-----------------+ +-----------------+
|    Payload      |     |    Payload      |     | C's label for D |
+-----------------+     +-----------------+ +-----------------+
         X                       Y               |    Payload |
+-----------------+
                                                          Z

X = Normal label stack packet arriving at S
Y = Normal label stack packet leaving S
Z = RLFA label stack to D via C as PQ node

>
>                                   Figure 4
>
>     To establish an targeted LDP session with a candidate PQ node the
>     repairing node (S) needs to know what IP address PQ is willing to use
>     for targeted LDP sessions.  Ideally this is provided by PQ
>     advertising this address in the IGP in use.  Which address is used,
>     how this is advertised in the IGP, and whether this is a special IP
>     address or an IP address also used for some other purpose is out of
>     scope for this document and must be specified in an IGP specific RFC.
>
>     In the absence of a protocol to learn the preferred IP address for
>     targeted LDP, a tie-breaking mechanism is required.  Unless otherwise
>     configured, an LSR should attempt a targeted LDP session with the IP
>     address with the lowest numerical value advertised by the target LSR.
>     To determine the lowest numerical value the address is taken in
>     network byte order and cast to an integer of appropriate size.
>     
>     [SLI] I would suggest :
>     Unless otherwise
>     configured, an LSR should attempt a targeted LDP session by selecting the lowest internal /32 prefix advertised by the target LSR.
SB> That fails the IPv6 test !
SB> I think that "local IP address" is clear and version independent.
>     
>     [SLI] I would add also :
>     "If the TLDP session could not be established, no protection would be available until the establishment succeeds and a label for the destination has been learned from the PQ.
>     An implementation may advise the operator about the protection setup issue using any well known mechanism such as syslog or SNMP for example."
>     
SB> The text now says

"No protection is available until the TLDP session has been established
and a label for the destination has been learned from PQ. If for any
reason the TLDP session cannot not be established, an implementation
SHOULD advise the operator about the protection setup issue using
any well known mechanism such as syslog or SNMP."
>
>
>
>
>
> 8.3.  RLFA
>
>
>     In this study, RLFA is only used when necessary. i.e. when there is
>     at least one destination which is not reparable by a per destination
>     LFA, and a single PQ tunnel is used (if available) to repair traffic
>     to all such destinations.  The RLFA PQ points are computed using
>     extended P space and choosing the PQ node which has the lowest metric
>     cost from the repairing node.
>
>
>       +------+--------+--------+------+------+-------+-----+-----+------+
>       | topo | % prot |% gtd N | % PQ | # PQ | no PQ | p50 | p90 | p100 |
>       +------+--------+--------+------+------+-------+-----+-----+------+
>       |    1 | 99.7   | 53.3   | 21.2 |  295 |     3 |   1 |   5 |   14 |
>
>
>
> Bryant, et al.            Expires May 01, 2014                 [Page 17]
>
> Internet-Draft               Remote LFA FRR                 October 2013
>
>
>       |    2 | 97.5   | 52.4   | 0.2  |    7 |    40 |   0 |   0 |    2 |
>       |    3 | 99.999 | 58.4   | 0.7  |   63 |     5 |   0 |   1 |    5 |
>       |    4 | 99     | 74.8   | 16   | 1424 |    54 |   1 |   3 |   23 |
>       |    5 | 99.5   | 59.5   | 0.5  |  151 |     7 |   0 |   2 |    7 |
>       |    6 | 100    | 34.9   | 13.6 |   63 |     0 |   1 |   2 |    6 |
>       |    7 | 99.999 | 40.6   | 6.1  |   16 |     2 |   0 |   2 |    4 |
>       |    8 | 99.5   | 50.2   | 4.3  |  350 |    39 |   0 |   2 |   15 |
>       |    9 | 99.5   | 55     | 17.3 |  428 |     5 |   1 |   2 |   67 |
>       |   10 | 99.6   | 14.1   | 1    |   49 |     7 |   1 |   2 |    5 |
>       |   11 | 99.9   | 24.9   | 0.3  |   85 |     1 |   0 |   2 |    8 |
>       |   12 | 99.999 | 62.8   | 0.5  |  512 |     4 |   0 |   0 |    3 |
>       |   13 | 97.5   | 54.6   | 5.1  | 1188 |    95 |   0 |   2 |   27 |
>       |   14 | 100    | 48.6   | 0.7  |   79 |     0 |   0 |   2 |    4 |
>       +------+--------+--------+------+------+-------+-----+-----+------+
>
>
> 	 [SLi] Would be good to have the avg, and max number of PQs node available for a specific interface or globally for a node.
SB> That will not fit in the table and Mike has not given them to me.
SB> How critical is this, i.e. is it a showstopper to publication?

>
> 9.  Management Considerations
>
>     The management of LFA and remote LFA is the subject of ongoing work
>     withing the IETF[I-D.ietf-rtgwg-lfa-manageability] to which the
>     reader is referred.  In contrast to this text which recommends that
>     LFAs be preferred over remote LFAs,
>     [I-D.ietf-rtgwg-lfa-manageability] notes that there may be reason to
>     use remote LFAs even if ordinary LFAs are available.  This requires
>     further study.
>     
>     [SLI] I would remove "This requires further study.", as the problem is a true one, already proved, and there is already some implementations.
>     What would be the impact of always running rLFA ? I don't really see a reason to not do it by default.
SB> Until I-D.ietf-rtgwg-lfa-manageability is an RFC it is under
study in the IETF. The impact of always using rLFA is that you may
need more TLDP sessions, and depending on the implementation
you may need to use a longer path in the forwarder.
>     Computation is not a big deal and people who don't want remote LFA can choose to not activate it on a specific interface or node.
>     I don't want to see a "non good behavior" mentionned in the draft, just because one code is already running as you specified ... it may not be the good approach.
SB> This has nothing to do with existing implementations.
SB> It was the first approach proposed 13 years ago and is inherited
SB> from that early work.
>     I would propose to change your behavior and say always compute rLFA, and then tie break between all alternates.
SB> I think that the LFA rLFA choice is a local matter

SB> I have changed the text to

The management of LFA and remote LFA is the subject of ongoing work 
withing the IETF
[I-D.ietf-rtgwg-lfa-manageability] to which the reader is referred. 
Management considerations
may lead to a preference for the use of a remote LFA over an available 
LFA. This preference
is a matter for the network operator, and not a matter of protocol 
correctness.

- Stewart



--------------070602040000090003070008
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">
    <div class="moz-cite-prefix">On 29/10/2013 15:17,
      <a class="moz-txt-link-abbreviated" href="mailto:stephane.litkowski@orange.com">stephane.litkowski@orange.com</a> wrote:<br>
      <br>
      Stephane<br>
      <br>
      Thank you for your comments.<br>
    </div>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">


   Q-space        Q-space is the set of routers from which a specific
                  router can be reached without any path (including
                  equal cost path splits) transiting the protected link.

[SLI] Should swap Q-Space and PQ node definition placement, as PQ node refers to Q-Space definition.</pre>
    </blockquote>
    SB&gt; Yes, but the list is in alphabetical order rather than in <br>
    SB&gt; declarative order.<br>
    SB&gt; I suggest that alphabetical is a normal ordering for <br>
    SB&gt; such an index of terms.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

2.  Introduction

   RFC 5714 [RFC5714] describes a framework for IP Fast Re-route and
   provides a summary of various proposed IPFRR solutions.  A basic
   mechanism using loop-free alternates (LFAs) is described in [RFC5286]
   that provides good repair coverage in many
   topologies[I-D.filsfils-rtgwg-lfa-applicability], especially those
   that are highly meshed.  However, some topologies, notably ring based
   topologies are not well protected by LFAs alone.  This is illustrated
   in Figure 1 below.
   
   [SLI] Replace [I-D.filsfils-rtgwg-lfa-applicability] by RFC6571</pre>
    </blockquote>
    Good catch - done.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
   

             S---E
            /     \
           A       D
            \     /
             B---C




Bryant, et al.            Expires May 01, 2014                  [Page 3]
<span class="moz-txt-formfeed"></span>
Internet-Draft               Remote LFA FRR                 October 2013


                     Figure 1: A simple ring topology

   If all link costs are equal, the link S-E cannot be fully protected
   by LFAs.  The destination C is an ECMP from S, and so can be
   protected when S-E fails, but D and E are not protectable using LFAs

   This draft describes extensions to the basic ([SLI] add "basic LFA repair ...") repair mechanism in
   which tunnels are used to provide additional logical links which can
   then be used as loop free alternates where none exist in the original
   topology.  For example if a tunnel is provided between S and C as
   shown in Figure 2 then C, now being a direct neighbor of S would
   become an LFA for D and E. The non-failure traffic distribution is
   not disrupted by the provision of such a tunnel since it is only used
   for repair traffic and MUST NOT be used for normal traffic.

          S---E
         / \   \
        A   \   D
         \   \ /
          B---C

                    Figure 2: The addition of a tunnel

   The use of this technique is not restricted to ring based topologies,
   but is a general mechanism which can be used to enhance the
   protection provided by LFAs.  A study of the protection achieved
   using remote LFA in typical service provider core networks is
   provided in Section 8, and a side by side comparison between LFA and
   remote LFA is provided in Section 8.4.

   Remote LFA is suitable for incremental deployment within a network,
   including a network that is already deploying LFA.  Computation of
   the repair path is relatively simple, and takes place exclusively on
   the repairing node.  In MPLS networks the targeted LDP protocol
   needed to learn the label binding at the repair tunnel endpoint is a
   well understood and widely deployed technology.

   This technique describes in this document is directed at providing
   repairs in the case of link failures.  Considerations regarding node
   failures are discussed in Section 6.

3.  Repair Paths

   As with LFA FRR, when a router detects an adjacent link failure, it
   uses one or more repair paths in place of the failed link.  Repair
   paths are pre-computed in anticipation of later failures so they can
   be promptly activated when a failure is detected.




Bryant, et al.            Expires May 01, 2014                  [Page 4]
<span class="moz-txt-formfeed"></span>
Internet-Draft               Remote LFA FRR                 October 2013


   A tunneled repair path tunnels traffic to some staging point in the
   network from which it is assumed that, in the absence of multiple
   failures, it will travel to its destination using normal forwarding
   without looping back.  This is equivalent to providing a virtual
   loop-free alternate to supplement the physical loop-free alternates.
   Hence the name "Remote LFA FRR".  When a link cannot be entirely
   protected with local LFA neighbors, the protecting router seeks the
   help of a remote LFA staging point. 
   
   [SLI] Not a good idea to seek rLFA only when LFA is not available (see manageability)</pre>
    </blockquote>
    SB&gt; This now says:<br>
    In its simplest form, when a link cannot be entirely protected with
    local LFA <br>
    neighbors, the protecting router seeks the help of a remote LFA
    staging point. <br>
    Network manageability considerations may lead to a repair strategy
    that <br>
    uses a remote LFA more frequently [I-D.ietf-rtgwg-lfa-manageability]<br>
    <br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

3.2.  Tunnel Requirements



   automatically established as a basic property of LDP behavior.  The
   performance of the encapsulation and decapsulation is also excellent
   as encapsulation is just a push of one label (like conventional MPLS
   TE FRR) and the decapsulation occurs naturally at the penultimate hop
   before the PQ node.
  [SLI] Ok the tunnel is already available, but you need some time to establish the protection (TLDP session establishment + label learning time).
	This is important to precise this.</pre>
    </blockquote>
    <br>
    SB&gt; The text now says:<br>
    <br>
    The performance of the encapsulation and decapsulation is efficient
    as encapsulation <br>
    is just a push of one label (like conventional MPLS TE FRR) and the
    decapsulation <br>
    occurs naturally at the penultimate hop before the PQ node. In the
    control plane, <br>
    a targeted LDP (TLDP) session is needed between the repairing node
    and the <br>
    repair tunnel endpoint, which will need to be established and the
    labels processed <br>
    before the tunnel can be used. The time to establish the TLDP
    session and acquire <br>
    labels will limit the speed at which a new tunnel can be put into
    service, but this <br>
    will not be a problem in normal operation.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
	
   When a failure is detected, it is necessary to immediately redirect
   traffic to the repair path.  Consequently, the repair tunnel used
   must be provisioned beforehand in anticipation of the failure.  Since
   the location of the repair tunnels is dynamically determined it is
   necessary to establish the repair tunnels without management action.
   [SLI] s/management action/manual provisionning action/ , as management may be needed to tweak the best tunnel tailend.</pre>
    </blockquote>
    SB&gt; I have changed this to:<br>
    Since the location of the repair tunnels is dynamically determined
    it is <br>
    necessary to automatically establish the repair tunnels. <br>
    <br>
    This covers both protocol and NMS and excludes humans.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
 
4.2.1.  Computing Repair Paths

   In the case of Figure 1 the Q-space
   comprises nodes C and D only.  Expressed in cost terms the set of
   routers {Q} are those for which the shortest path cost E-&gt;Q is
   strictly less than the shortest path cost E-&gt;S-&gt;Q. 
   
   [SLI] Would it be Q-&gt;E less than Q-&gt;S-&gt;E</pre>
    </blockquote>
    <br>
    SB&gt; Thanks<br>
    <br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
4.2.2.  Extended P-space



   Another way to describe extended P-space is that it is the union of (
   un-extended ) P-space and the set of destinations for which S has a
   per-prefix LFA protecting the link S-E. i.e. the repair tunnel end
   point can be reached either directly or using a per-prefix LFA.

   	[SLI] Lack of precision about independancy of rLFA and LFA alternate choice is rLFA is using extended P space node.
	I would propose :
	
	"Even if extended P-space would be composed on nodes reachable through a per-prefix LFA, this does not conclude that the rLFA would inherit the best LFA to reach the PQ: 
	rLFA an LFA MUST be completely independant. In other words, if S has N1 and N2 as LFAs to protection a destination P, and S wants to use P as PQ to protect a destination D. 
	S must be able to program N1 as LFA to reach P and P through N2 to reach D for manageability reasons (refer to Section 9)."</pre>
    </blockquote>
    <br>
    SB&gt; We are talking about different things. This is not about
    whether<br>
    SB&gt; or not we use LFA and RLFA together. This is another way<br>
    SB&gt; of expressing extended P-space. Extended P-space<br>
    SB&gt; is everything that E can reach on its own + everything that<br>
    SB&gt; it can reach by forcing the first hop to a directly connected<br>
    SB&gt; neighbour - which is what a per-prefix LFA is. The <br>
    SB&gt; para is purely tutorial, and can be removed.<br>
    <br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">


	
4.2.3.  Selecting Repair Paths

   The mechanisms described above will identify all the possible repair
   tunnel end points that can be used to protect a particular link.  In
   a well-connected network there are likely to be multiple possible
   release points for each protected link.  All will deliver the packets
   correctly so, arguably, it does not matter which is chosen.  However,
   one repair tunnel end point may be preferred over the others on the
   basis of path cost or some other selection criteria.

   There is no technical requirement for the selection criteria to be
   consistent across all routers, but such consistency may be desirable
   from an operational point of view.  In general there are advantages
   in choosing the repair tunnel end point closest (shortest metric) to
   S. Choosing the closest maximises the opportunity for the traffic to
   be load balanced once it has been released from the tunnel.  For
   consistency in behavior is RECOMMENDED that member of the set of
   routers {P} with the lowest cost S-&gt;P be the default choice for P. In
   the event of a tie the router with the lowest node identifier SHOULD
   be selected.
   
   [SLI] Need to replace P by PQ : "For
   consistency in behavior is RECOMMENDED that member of the set of
   routers {PQ} with the lowest cost S-&gt;PQ be the default choice for PQ."
   </pre>
    </blockquote>
    SB&gt; Done.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

4.3.  A Cost Based RLFA Algorithm

   The preceding text has mostly described the computation of the remote
   LFA repair point (PQ) in terms of the intersection of two
   reachability graphs computed using SPFs.  This section describes a
   method of computing the repair point using a cost based algorithm.
   
   [SLI] "repair point" is confusing as a repair point is a PLR and here we talk about PQ.
   Could we use "Remote LFA" instead ?</pre>
    </blockquote>
    SB&gt; It now says:<br>
    <br>
    The preceding text has mostly described the computation of the
    remote LFA repair <br>
    target (PQ) in terms of the intersection of two reachability graphs
    computed using <br>
    SPFs. This section describes a method of computing PQ using a cost
    based algorithm. <br>
    <br>
    The first sentence reminds the reader what PQ is, so I think this is
    clear.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
   
   The pseudo-code provides in this section avoids unnecessary SPF
   computations, but for the sake of readability, it does not otherwise
   try to optimize the code.  Unconventionally, but for clarity, we
   provide the main algorithm followed its procedures.  In this
   description D_opt(a,b) is the shortest distance from node a to node b
   as computed by the SPF.

	[SLI] Changing the pseudocode and create a remote LFA function as step of rLFA computation are here mixed with subfunctions.
	Proposal here :</pre>
    </blockquote>
    <br>
    SB&gt; The problem is with hitting the 72 col limit.<br>
    SB&gt; I have marked this with comments<br>
    SB&gt; Hopefully this is now clear.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

	// Remote LFA computation function
	
	main {
	  //////////////////////////////////////////////////////////////////
      //
      // We have already computed the forward SPF from self to all nodes
      // y in network and thus we know D_opt (self, y). This is needed
      // for normal forwarding.
      // However for completeness.

      Compute_and_Store_Forward_SPF(self)

	  // Need to compute rSPF(self) to compute cost based Q Space (done only one time)
	  Compute_and_Store_Reverse_SPF(self)</pre>
    </blockquote>
    <br>
    SB&gt; This was only done once in the original.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
		
      // To extend P-space we compute the SPF at each neighbour except
      // the neighbour that is reached via the link being protected.
      // We will also need D_opt(fail_intf.remote_node,y) so compute
      // that at the same time.

      foreach interface intf in self
              Compute_and_Store_Forward_SPF(intf.remote_node)
		[SLI] I removed the Compute_Neighbor_SPFs as , IMHO, it complexifies the readability ...</pre>
    </blockquote>
    <br>
    SB&gt; This is tricky, because whilst true, the implementation will<br>
    SB&gt; need to know which are which since it normally needs to<br>
    SB&gt; deal with them differently in the FIB code.<br>
    SB&gt; However I have taken it out.<br>
    <br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
		
	  // Compute rLFA for each interface
	  foreach interface fail_intf in self
		Compute_RLFA(fail_intf)
	}
	
	Compute_RLFA(fail_intf) {
	
      // Compute the set of nodes {P} reachable other than via the
      // failed link

      Compute_Extended_P_Space(fail_intf)
	[SLI] Adding "fail_intf" as parameter</pre>
    </blockquote>
    SB&gt; OK, although it was correct as a global.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
	
      // Compute the set of nodes that can reach the node on the far
      // side of the failed link without traversing the failed link.

      Compute_Q_Space(fail_intf)
	[SLI] Adding "fail_intf" as parameter</pre>
    </blockquote>
    <br>
    SB&gt; See above<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

      // Compute the set of candidate RLFA tunnel endpoints




Bryant, et al.            Expires May 01, 2014                  [Page 9]
<span class="moz-txt-formfeed"></span>
Internet-Draft               Remote LFA FRR                 October 2013


      Intersect_Extended_P_and_Q_Space()

      // Make sure that we cannot get looping repairs when the
      // failure is worse than expected.

      if (guarantee_no_looping_on_worse_than_protected_failure)
          Apply_Downstream_Constraint()
}


	// Sub functions
	
      /////////////////////////////////////////////////////////////////
      //
      // This computes the SPF from root, and stores the optimum
      // distance from root to each node y

      Compute_and_Store_Forward_SPF(root)
          Compute_Forward_SPF(root)
          foreach node y in network
              store D_opt(root,y)

	[SLI] I would add a comment to the function :
	
      Compute_and_Store_Forward_SPF(root)
          Compute_Forward_SPF(root)		// A SPF may already been in cache and so may be no need to recompute it
          foreach node y in network
              store D_opt(root,y)
</pre>
    </blockquote>
    SB&gt; That was covered in my comment in main.<br>
    <br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

      /////////////////////////////////////////////////////////////////
      //
      // The reverse SPF computes the cost from each remote node to
      // root. This is achieved by running the normal SPF algorithm,
      // but using the link cost in the direction from the next hop
      // back towards root in place of the link cost in the direction
      // away from root towards the next hop.

      Compute_and_Store_Reverse_SPF(root)
          Compute_Reverse_SPF(root)
          foreach node y in network
              store D_opt(y,root)





Bryant, et al.            Expires May 01, 2014                 [Page 10]
<span class="moz-txt-formfeed"></span>
Internet-Draft               Remote LFA FRR                 October 2013


      /////////////////////////////////////////////////////////////////
      //
      // Calculate P space and then extend it by the P-spaces of each
      // neighbour other than the one reachable via the link being
      // protected. Note the strictly less than operator is needed to
      // avoid ECMP issues.

      Compute_Extended_P_Space()
          foreach node y in network
              y.in_extended_P_space = false
              // Compute P-space
              //
              // Editor's note, I think that this if statement may be
              // redundant since the foreach interface intf in self
              // loop catches all cases.
			  
			  [SLI] Yes, IMHO, this is redundant.</pre>
    </blockquote>
    SB&gt; I took it out<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
              
			  //
              // Editor's note D_opt(fail_intf.remote_node,y) requires
              // an SPF from neighbour fail_intf.remote_node so did
              // this as part of all neighbours SPF calculation
              if (D_opt(self, y) &lt;
                      D_opt(self, fail_intf.remote_node) +
                      D_opt(fail_intf.remote_node,y))
                  y.in_extended_P_space = true
              // Extend P-space to the P-spaces of all reachable
              // neighbours
              foreach interface intf in self
                  if (intf.remote_node != fail_intf.remote_node)
                      if ( D_opt(intf.remote_node, y) &lt;
                           D_opt(intf.remote_node, self) +
                           D_opt(self,fail_intf.remote_node) +
                           D_opt(fail_intf.remote_node,y) )
                       y.in_extended_P_space = true



      /////////////////////////////////////////////////////////////////
      //

      Compute_Q_Space(fail_intf)
          // Compute the cost from every node the network to the
          // node normally reachable across the failed link
          Compute_and_Store_Reverse_SPF(fail_intf.remote_node)

          // Compute the cost from every node the network to self
           [SLI] Need to be removed I putted it in main code (optimize number of SPF)</pre>
    </blockquote>
    SB&gt; It is fine here. Main does not need to know about this calc
    since<br>
    SB&gt; it is not shared.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

          foreach node y in network
              if ( D_opt(y,fail_intf.remote_node) &lt; D_opt(y,self) +



Bryant, et al.            Expires May 01, 2014                 [Page 11]
<span class="moz-txt-formfeed"></span>
Internet-Draft               Remote LFA FRR                 October 2013


                      D_opt(self,fail_intf.remote_node) )
                  y.in_Q_space = true
              else
                  y.in_Q_space = false



      /////////////////////////////////////////////////////////////////
      //
      // Compute set of nodes in both extended P-space and in Q-space

      Intersect_Extended_P_and_Q_Space()
          foreach node y in network
              if ( y.in_extended_P_space &amp;&amp; y.in_Q_space )
                  y.valid_tunnel_endpoint = true
              else
                  y.valid_tunnel_endpoint = false



      /////////////////////////////////////////////////////////////////
      //
      // A downstream route is one where the next hop is strictly
      // closer to the destination. By sending the packet to a
      // PQ node that is downstream, we know that if the PQ node
      // detects a failure, it will not loop the packet back to self.
      // This is useful when there are two failures, or a node has
      // failed rather than a link.

      Apply_Downstream_Constraint()
          foreach node y in network
              if (y.valid_tunnel_endpoint)
                  Compute_and_Store_Forward_SPF(y)
                  if ((D_opt(y,dest) &lt; D_opt(self,dest))
                      y.valid_tunnel_endpoint = true
                  else
                      y.valid_tunnel_endpoint = false
	[SLI] Based on my simulations, Compute_and_Store_Forward_SPF(y) would not be possible as number of y.valid_tunnel_endpoint == true is very high !
	So downstreamness could not be established so easily ... even if it's theorical working.</pre>
    </blockquote>
    SB&gt; Yes - well - whatever the consenus is I will leave it in or
    take it out<br>
    <br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
          |    100    |
         -P2---------P1-
           \         /
       1000 \       / 1000
            PE1---PE2
                5

                       Figure 3: Example SP topology

   Clearly, full protection can be provided, using the techniques
   described in this draft, by PE1 choosing P2 as a PQ node, and PE2
   choosing P1 as a PQ node.
   
   [SLI] Would it be "PE1 choosing P1" and "PE2 choosing P2" ?</pre>
    </blockquote>
    SB&gt; yes, changed.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

6.  Node Failures

   When the failure is a node failure rather than a link failure there
   is a danger that the RLFA repair will loop.  This is discussed in
   detail in [I-D.bryant-ipfrr-tunnels].  In summary problem is that two
   of more of E's neighbors each with E as the next hop to some
   destination D may attempt to repair a packet addressed to destination
   D via the other neighbor and then E, thus causing a loop to form.  As
   will be noted from [I-D.bryant-ipfrr-tunnels], this can rapidly
   become a complex problem to address.






Bryant, et al.            Expires May 01, 2014                 [Page 13]
<span class="moz-txt-formfeed"></span>
Internet-Draft               Remote LFA FRR                 October 2013


   There are a number of ways to minimize the probability of a loop
   forming when a node failure occurs and there exists the possibility
   that two of E's neighbors may form a mutual repair.

   1.  Detect when a packet has arrived on some interface I that is also
       the interface used to reach the first hop on the RLFA path to PQ,
       and drop the packet.  This is useful in the case of a ring
       topology.
[SLI] This has several drawbacks, especially this may cause some "legal packet" drops ...
 </pre>
    </blockquote>
    This needs fixing in the commentary text below.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
	   
   2.  Require that the path from PQ to destination D never passes
       through E (including in the ECMP case), i.e. only use node
       protecting paths in which the cost PQ to D is strictly less than
       the cost PQ to E plus the cost E to D.

   3.  Require that where the packet may pass through another neighbor
       of E, that node is down stream (i.e. strictly closer to D than
       the repairing node).  This means that some neighbor of E (X) can
       repair via some other neighbor of E (Y), but Y cannot repair via
       X.

   Case 1 accepts that loops may form and suppresses them by dropping
   packets.  Dropping packets may be considered less detrimental than
   looping packets.  </pre>
    </blockquote>
    <br>
    SB&gt; I have added "This approach may also lead to dropping some
    legitimate packets."<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">Cases 2 and 3 above prevent the formation of a
   loop, but at the expense of a reduced repair coverage and at the cost
   of additional complexity in the algorithm to compute the repair path.

   The probability of a node failure and the consequences of node
   failure in any particular topology will depend on the node design,
   the particular topology in use, and node failure strategy (including
   the null strategy).  It is recommended that a network operator
   perform an analysis of the consequences and probability of node
   failure in their network, and determine whether the incidence and
   consequence of occurrence are acceptable.

   This topic is further discussed in
   [I-D.psarkar-rtgwg-rlfa-node-protection].

7.  Operation in an LDP environment

   Where this technique is used in an MPLS network using LDP [RFC5036],
   S will need to push two labels onto the repair packet.  First it
   needs to push PQ's label to the destination, and then it needs to
   push its own label for PQ.  
   
   [SLI] If S is transit node, it swaps incoming label to PQ's label to the dest and then push.
   So to simplify, I would say : "S need to push an additional label onto the repair packet".</pre>
    </blockquote>
    <br>
    SB&gt; It now says:<br>
    "and S is a transit node, S will need to swap the top label in the
    stack for PQ's <br>
    label to the destination, and to push its own label for PQ. "<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
   
   In the example Section 3.1 S already has
   [SLI] The example is in Section 2</pre>
    </blockquote>
    SB&gt; Thanks - corrected the anchor<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
   
   the first hop (B) label for the PQ node (C) as a result of the
   [SLI] Would it be "the first hop (A)" ?</pre>
    </blockquote>
    <br>
    SB&gt; Yes.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
   
   ordinary operation of LDP.  To get the PQ node (C) label for the
   destination (D), S needs to establish a targeted LDP session with C.
   The label stack for normal operation and RLFA operation is shown
   below in Figure 4.



Bryant, et al.            Expires May 01, 2014                 [Page 14]
<span class="moz-txt-formfeed"></span>
Internet-Draft               Remote LFA FRR                 October 2013


   +-----------------+     +-----------------+     +-----------------+
   |    datalink     |     |    datalink     |     |    datalink     |
   +-----------------+     +-----------------+     +-----------------+
   | S's label for D |     | E's label for D |     | C's label for D |
   +-----------------+     +-----------------+     +-----------------+
   |    Payload      |     |    Payload      |     | B's label for C |
   +-----------------+     +-----------------+     +-----------------+
           X                       Y               |    Payload      |
                                                   +-----------------+
                                                            Z

   X = Normal label stack packet arriving at S
   Y = Normal label stack packet leaving S
   Z = RLFA label stack to D via C as PQ node

	[SLI] In Z, would it be "A's label for C", as A is the nexthop to reach C from S.</pre>
    </blockquote>
    SB&gt; I think that actually there were two errors<br>
    SB&gt; Here is what the stack needs to look like<br>
    <br>
    <font face="Courier New, Courier, monospace">+-----------------+&nbsp;&nbsp;&nbsp;&nbsp;
      +-----------------+&nbsp;&nbsp;&nbsp;&nbsp; +-----------------+<br>
      |&nbsp;&nbsp;&nbsp; datalink&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; datalink&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; datalink&nbsp;&nbsp;&nbsp;&nbsp;
      |<br>
      +-----------------+&nbsp;&nbsp;&nbsp;&nbsp; +-----------------+&nbsp;&nbsp;&nbsp;&nbsp;
      +-----------------+<br>
      | S's label for D |&nbsp;&nbsp;&nbsp;&nbsp; | E's label for D |&nbsp;&nbsp;&nbsp;&nbsp; | A's label for C
      |<br>
      +-----------------+&nbsp;&nbsp;&nbsp;&nbsp; +-----------------+&nbsp;&nbsp;&nbsp;&nbsp;
      +-----------------+<br>
      |&nbsp;&nbsp;&nbsp; Payload&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Payload&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; | C's label for D
      |<br>
      +-----------------+&nbsp;&nbsp;&nbsp;&nbsp; +-----------------+&nbsp;&nbsp;&nbsp;&nbsp;
      +-----------------+<br>
      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; X&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Y&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Payload&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      |<br>
      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      +-----------------+</font><br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Z<br>
    <br>
    X = Normal label stack packet arriving at S<br>
    Y = Normal label stack packet leaving S<br>
    Z = RLFA label stack to D via C as PQ node<br>
    <br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

                                 Figure 4

   To establish an targeted LDP session with a candidate PQ node the
   repairing node (S) needs to know what IP address PQ is willing to use
   for targeted LDP sessions.  Ideally this is provided by PQ
   advertising this address in the IGP in use.  Which address is used,
   how this is advertised in the IGP, and whether this is a special IP
   address or an IP address also used for some other purpose is out of
   scope for this document and must be specified in an IGP specific RFC.

   In the absence of a protocol to learn the preferred IP address for
   targeted LDP, a tie-breaking mechanism is required.  Unless otherwise
   configured, an LSR should attempt a targeted LDP session with the IP
   address with the lowest numerical value advertised by the target LSR.
   To determine the lowest numerical value the address is taken in
   network byte order and cast to an integer of appropriate size.
   
   [SLI] I would suggest :
   Unless otherwise
   configured, an LSR should attempt a targeted LDP session by selecting the lowest internal /32 prefix advertised by the target LSR.</pre>
    </blockquote>
    SB&gt; That fails the IPv6 test !<br>
    SB&gt; I think that "local IP address" is clear and version
    independent.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
   
   [SLI] I would add also :
   "If the TLDP session could not be established, no protection would be available until the establishment succeeds and a label for the destination has been learned from the PQ. 
   An implementation may advise the operator about the protection setup issue using any well known mechanism such as syslog or SNMP for example."
   </pre>
    </blockquote>
    SB&gt; The text now says<br>
    <br>
    "No protection is available until the TLDP session has been
    established <br>
    and a label for the destination has been learned from PQ. If for any
    <br>
    reason the TLDP session cannot not be established, an implementation
    <br>
    SHOULD advise the operator about the protection setup issue using <br>
    any well known mechanism such as syslog or SNMP."<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">





8.3.  RLFA


   In this study, RLFA is only used when necessary. i.e. when there is
   at least one destination which is not reparable by a per destination
   LFA, and a single PQ tunnel is used (if available) to repair traffic
   to all such destinations.  The RLFA PQ points are computed using
   extended P space and choosing the PQ node which has the lowest metric
   cost from the repairing node.


     +------+--------+--------+------+------+-------+-----+-----+------+
     | topo | % prot |% gtd N | % PQ | # PQ | no PQ | p50 | p90 | p100 |
     +------+--------+--------+------+------+-------+-----+-----+------+
     |    1 | 99.7   | 53.3   | 21.2 |  295 |     3 |   1 |   5 |   14 |



Bryant, et al.            Expires May 01, 2014                 [Page 17]
<span class="moz-txt-formfeed"></span>
Internet-Draft               Remote LFA FRR                 October 2013


     |    2 | 97.5   | 52.4   | 0.2  |    7 |    40 |   0 |   0 |    2 |
     |    3 | 99.999 | 58.4   | 0.7  |   63 |     5 |   0 |   1 |    5 |
     |    4 | 99     | 74.8   | 16   | 1424 |    54 |   1 |   3 |   23 |
     |    5 | 99.5   | 59.5   | 0.5  |  151 |     7 |   0 |   2 |    7 |
     |    6 | 100    | 34.9   | 13.6 |   63 |     0 |   1 |   2 |    6 |
     |    7 | 99.999 | 40.6   | 6.1  |   16 |     2 |   0 |   2 |    4 |
     |    8 | 99.5   | 50.2   | 4.3  |  350 |    39 |   0 |   2 |   15 |
     |    9 | 99.5   | 55     | 17.3 |  428 |     5 |   1 |   2 |   67 |
     |   10 | 99.6   | 14.1   | 1    |   49 |     7 |   1 |   2 |    5 |
     |   11 | 99.9   | 24.9   | 0.3  |   85 |     1 |   0 |   2 |    8 |
     |   12 | 99.999 | 62.8   | 0.5  |  512 |     4 |   0 |   0 |    3 |
     |   13 | 97.5   | 54.6   | 5.1  | 1188 |    95 |   0 |   2 |   27 |
     |   14 | 100    | 48.6   | 0.7  |   79 |     0 |   0 |   2 |    4 |
     +------+--------+--------+------+------+-------+-----+-----+------+


	 [SLi] Would be good to have the avg, and max number of PQs node available for a specific interface or globally for a node.</pre>
    </blockquote>
    SB&gt; That will not fit in the table and Mike has not given them to
    me.<br>
    SB&gt; How critical is this, i.e. is it a showstopper to
    publication?<br>
    <br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">

9.  Management Considerations

   The management of LFA and remote LFA is the subject of ongoing work
   withing the IETF[I-D.ietf-rtgwg-lfa-manageability] to which the
   reader is referred.  In contrast to this text which recommends that
   LFAs be preferred over remote LFAs,
   [I-D.ietf-rtgwg-lfa-manageability] notes that there may be reason to
   use remote LFAs even if ordinary LFAs are available.  This requires
   further study.
   
   [SLI] I would remove "This requires further study.", as the problem is a true one, already proved, and there is already some implementations.
   What would be the impact of always running rLFA ? I don't really see a reason to not do it by default. </pre>
    </blockquote>
    SB&gt; Until I-D.ietf-rtgwg-lfa-manageability is an RFC it is under<br>
    study in the IETF. The impact of always using rLFA is that you may<br>
    need more TLDP sessions, and depending on the implementation<br>
    you may need to use a longer path in the forwarder.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
   Computation is not a big deal and people who don't want remote LFA can choose to not activate it on a specific interface or node.
   I don't want to see a "non good behavior" mentionned in the draft, just because one code is already running as you specified ... it may not be the good approach.
</pre>
    </blockquote>
    SB&gt; This has nothing to do with existing implementations.<br>
    SB&gt; It was the first approach proposed 13 years ago and is
    inherited<br>
    SB&gt; from that early work.<br>
    <blockquote
cite="mid:5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr"
      type="cite">
      <pre wrap="">
   I would propose to change your behavior and say always compute rLFA, and then tie break between all alternates.</pre>
    </blockquote>
    SB&gt; I think that the LFA rLFA choice is a local matter<br>
    <br>
    SB&gt; I have changed the text to <br>
    <br>
    The management of LFA and remote LFA is the subject of ongoing work
    withing the IETF<br>
    [I-D.ietf-rtgwg-lfa-manageability] to which the reader is referred.
    Management considerations <br>
    may lead to a preference for the use of a remote LFA over an
    available LFA. This preference <br>
    is a matter for the network operator, and not a matter of protocol
    correctness.<br>
    <br>
    - Stewart<br>
    <br>
    <br>
  </body>
</html>

--------------070602040000090003070008--

From internet-drafts@ietf.org  Mon Nov  4 08:28:06 2013
Return-Path: <internet-drafts@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 DC25921E81C0; Mon,  4 Nov 2013 08:28:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 G1AcAk8D-cV7; Mon,  4 Nov 2013 08:28:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7637821E81A1; Mon,  4 Nov 2013 08:28:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-remote-lfa-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.82
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131104162800.10097.63712.idtracker@ietfa.amsl.com>
Date: Mon, 04 Nov 2013 08:28:00 -0800
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Nov 2013 16:28:07 -0000

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

	Title           : Remote LFA FRR
	Author(s)       : Stewart Bryant
                          Clarence Filsfils
                          Stefano Previdi
                          Mike Shand
                          Ning So
	Filename        : draft-ietf-rtgwg-remote-lfa-03.txt
	Pages           : 23
	Date            : 2013-11-04

Abstract:
   This draft describes an extension to the basic IP fast re-route
   mechanism described in RFC5286 that provides additional backup
   connectivity for link failures when none can be provided by the basic
   mechanisms.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtgwg-remote-lfa-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From cbowers@juniper.net  Mon Nov  4 13:54:23 2013
Return-Path: <cbowers@juniper.net>
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 AFE3821F9A44 for <rtgwg@ietfa.amsl.com>; Mon,  4 Nov 2013 13:54:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.384
X-Spam-Level: 
X-Spam-Status: No, score=-3.384 tagged_above=-999 required=5 tests=[AWL=-0.786, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 Bz8sWHRswMh4 for <rtgwg@ietfa.amsl.com>; Mon,  4 Nov 2013 13:54:17 -0800 (PST)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0187.outbound.messaging.microsoft.com [213.199.154.187]) by ietfa.amsl.com (Postfix) with ESMTP id 6771B21E81C6 for <rtgwg@ietf.org>; Mon,  4 Nov 2013 13:54:12 -0800 (PST)
Received: from mail133-db8-R.bigfish.com (10.174.8.241) by DB8EHSOBE004.bigfish.com (10.174.4.67) with Microsoft SMTP Server id 14.1.225.22; Mon, 4 Nov 2013 21:54:11 +0000
Received: from mail133-db8 (localhost [127.0.0.1])	by mail133-db8-R.bigfish.com (Postfix) with ESMTP id 9745B3E0187; Mon,  4 Nov 2013 21:54:11 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: VPS-19(zz9371Ic85fhzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz1d7338h1de098h1033IL17326ah8275bh8275dh18c673h1de097h186068hz2fh109h2a8h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h20f0h2216h9a9j1155h)
Received-SPF: pass (mail133-db8: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=cbowers@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(377454003)(199002)(189002)(80022001)(65816001)(63696002)(66066001)(54316002)(56776001)(77982001)(51856001)(74316001)(81542001)(74366001)(31966008)(59766001)(47976001)(53806001)(4396001)(74876001)(50986001)(47736001)(49866001)(46102001)(81342001)(54356001)(69226001)(74502001)(76796001)(76786001)(76576001)(56816003)(19300405004)(83072001)(15975445006)(16236675002)(81686001)(74706001)(76482001)(80976001)(15202345003)(47446002)(83322001)(33646001)(79102001)(19580395003)(74662001)(81816001)(85306002)(19580405001)(87266001)(2656002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB290; H:BLUPR05MB292.namprd05.prod.outlook.com; CLIP:66.129.224.36; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail133-db8 (localhost.localdomain [127.0.0.1]) by mail133-db8 (MessageSwitch) id 1383602048860166_8323; Mon,  4 Nov 2013 21:54:08 +0000 (UTC)
Received: from DB8EHSMHS017.bigfish.com (unknown [10.174.8.253])	by mail133-db8.bigfish.com (Postfix) with ESMTP id CDB7F42024B; Mon,  4 Nov 2013 21:54:08 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS017.bigfish.com (10.174.4.27) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 4 Nov 2013 21:54:08 +0000
Received: from BLUPR05MB290.namprd05.prod.outlook.com (10.141.23.24) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.371.2; Mon, 4 Nov 2013 21:54:06 +0000
Received: from BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) by BLUPR05MB290.namprd05.prod.outlook.com (10.141.23.24) with Microsoft SMTP Server (TLS) id 15.0.800.7; Mon, 4 Nov 2013 21:54:05 +0000
Received: from BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) by BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) with mapi id 15.00.0800.005; Mon, 4 Nov 2013 21:54:04 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Subject: RE: candidate-draft-ietf-rtgwg-remote-lfa-03.txt
Thread-Topic: candidate-draft-ietf-rtgwg-remote-lfa-03.txt
Thread-Index: AQHO2LIjOy90Cf2BZUmYRrdjv4oJLpoVmhVw
Date: Mon, 4 Nov 2013 21:54:03 +0000
Message-ID: <fcb35b14eecd49fd9cf93fda544cc6f6@BLUPR05MB292.namprd05.prod.outlook.com>
References: <526EB4FE.3020507@cisco.com> <5707_1383059865_526FD199_5707_3687_1_EEE55384044474429A926C625D0FCC8109902E3726@PUEXCB2F.nanterre.francetelecom.fr> <5273DAE3.2090706@cisco.com>
In-Reply-To: <5273DAE3.2090706@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.224.36]
x-forefront-prvs: 0020414413
Content-Type: multipart/alternative; boundary="_000_fcb35b14eecd49fd9cf93fda544cc6f6BLUPR05MB292namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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, 04 Nov 2013 21:54:23 -0000

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

Following up on an item discussed in the meeting.  We agreed that the parag=
raph in section 4.2.2 (see below) that describes extended P-space in terms =
of (local)LFA should be removed because this alternative description may co=
nfuse the reader more than it enlightens.

Chris

From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org] On Behalf Of S=
tewart Bryant
Sent: Friday, November 01, 2013 9:46 AM
To: stephane.litkowski@orange.com; rtgwg@ietf.org
Subject: Re: candidate-draft-ietf-rtgwg-remote-lfa-03.txt

-----------------
Snip
-----------------



4.2.2.  Extended P-space





   Another way to describe extended P-space is that it is the union of (

   un-extended ) P-space and the set of destinations for which S has a

   per-prefix LFA protecting the link S-E. i.e. the repair tunnel end

   point can be reached either directly or using a per-prefix LFA.



         [SLI] Lack of precision about independancy of rLFA and LFA alterna=
te choice is rLFA is using extended P space node.

  I would propose :



  "Even if extended P-space would be composed on nodes reachable through a =
per-prefix LFA, this does not conclude that the rLFA would inherit the best=
 LFA to reach the PQ:

  rLFA an LFA MUST be completely independant. In other words, if S has N1 a=
nd N2 as LFAs to protection a destination P, and S wants to use P as PQ to =
protect a destination D.

  S must be able to program N1 as LFA to reach P and P through N2 to reach =
D for manageability reasons (refer to Section 9)."

SB> We are talking about different things. This is not about whether
SB> or not we use LFA and RLFA together. This is another way
SB> of expressing extended P-space. Extended P-space
SB> is everything that E can reach on its own + everything that
SB> it can reach by forcing the first hop to a directly connected
SB> neighbour - which is what a per-prefix LFA is. The
SB> para is purely tutorial, and can be removed.



--_000_fcb35b14eecd49fd9cf93fda544cc6f6BLUPR05MB292namprd05pro_
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=3D"Generator" content=3D"Microsoft Word 15 (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:12.0pt;
	font-family:"Times New Roman","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","serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.moz-txt-formfeed
	{mso-style-name:moz-txt-formfeed;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Following up on an item d=
iscussed in the meeting.&nbsp; We agreed that the paragraph in section 4.2.=
2 (see below) that describes extended P-space in terms of (local)LFA
 should be removed because this alternative description may confuse the rea=
der more than it enlightens.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Chris<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:windowtext"> rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ie=
tf.org]
<b>On Behalf Of </b>Stewart Bryant<br>
<b>Sent:</b> Friday, November 01, 2013 9:46 AM<br>
<b>To:</b> stephane.litkowski@orange.com; rtgwg@ietf.org<br>
<b>Subject:</b> Re: candidate-draft-ietf-rtgwg-remote-lfa-03.txt<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><br>
<span style=3D"color:windowtext">-----------------</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:windowtext">Snip<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:windowtext">-----------------<o:p>=
</o:p></span></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><o:p>&nbsp;</o:p></pre>
<pre>4.2.2.&nbsp; Extended P-space<o:p></o:p></pre>
<pre><span style=3D"color:windowtext"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-right:.5in"><span style=3D"font-size:11.0pt;font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:windowtext"><o:p>&nbsp;<=
/o:p></span></pre>
<pre>&nbsp;&nbsp; Another way to describe extended P-space is that it is th=
e union of (<o:p></o:p></pre>
<pre>&nbsp;&nbsp; un-extended ) P-space and the set of destinations for whi=
ch S has a<o:p></o:p></pre>
<pre>&nbsp;&nbsp; per-prefix LFA protecting the link S-E. i.e. the repair t=
unnel end<o:p></o:p></pre>
<pre>&nbsp;&nbsp; point can be reached either directly or using a per-prefi=
x LFA.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [SLI] Lack of precision ab=
out independancy of rLFA and LFA alternate choice is rLFA is using extended=
 P space node.<o:p></o:p></pre>
<pre>&nbsp; I would propose :<o:p></o:p></pre>
<pre>&nbsp; <o:p></o:p></pre>
<pre>&nbsp; &quot;Even if extended P-space would be composed on nodes reach=
able through a per-prefix LFA, this does not conclude that the rLFA would i=
nherit the best LFA to reach the PQ: <o:p></o:p></pre>
<pre>&nbsp; rLFA an LFA MUST be completely independant. In other words, if =
S has N1 and N2 as LFAs to protection a destination P, and S wants to use P=
 as PQ to protect a destination D. <o:p></o:p></pre>
<pre>&nbsp; S must be able to program N1 as LFA to reach P and P through N2=
 to reach D for manageability reasons (refer to Section 9).&quot;<o:p></o:p=
></pre>
</blockquote>
<p class=3D"MsoNormal"><br>
SB&gt; We are talking about different things. This is not about whether<br>
SB&gt; or not we use LFA and RLFA together. This is another way<br>
SB&gt; of expressing extended P-space. Extended P-space<br>
SB&gt; is everything that E can reach on its own &#43; everything that<br>
SB&gt; it can reach by forcing the first hop to a directly connected<br>
SB&gt; neighbour - which is what a per-prefix LFA is. The <br>
SB&gt; para is purely tutorial, and can be removed.<br>
<br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>

--_000_fcb35b14eecd49fd9cf93fda544cc6f6BLUPR05MB292namprd05pro_--

From acee.lindem@ericsson.com  Tue Nov  5 06:40:10 2013
Return-Path: <acee.lindem@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 9100E21E82C4; Tue,  5 Nov 2013 06:40:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.646
X-Spam-Level: 
X-Spam-Status: No, score=-2.646 tagged_above=-999 required=5 tests=[AWL=-0.047, 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 HHF8b4ElR2v9; Tue,  5 Nov 2013 06:39:57 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6EFAE21F9EF2; Tue,  5 Nov 2013 06:39:37 -0800 (PST)
X-AuditID: c618062d-b7fd88e00000439f-9e-5279030e0e1c
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 70.D2.17311.E0309725; Tue,  5 Nov 2013 15:39:10 +0100 (CET)
Received: from EUSAAMB106.ericsson.se ([147.117.188.123]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0328.009; Tue, 5 Nov 2013 09:39:10 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Mark Townsley <mark@townsley.net>, "homenet@ietf.org Group" <homenet@ietf.org>, "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
Thread-Topic: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
Thread-Index: AQHO2jTJGWWoQUJXR0KPq+/59bDixA==
Date: Tue, 5 Nov 2013 14:39:09 +0000
Message-ID: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se>
In-Reply-To: <A8A941F6-FDC1-4F6A-A2D7-F4AEAA012BE9@townsley.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <71C2100729DED442BE0CA125754DEC36@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyuXRPrC4fc2WQwYfVNhbv151hs3i/6BCL xbQDD5gsLrz5zezA4jHl90ZWjyVLfjJ53J82kSmAOYrLJiU1J7MstUjfLoErY8a6IywFb9kr 7i0Wb2A8wNbFyMkhIWAicevvVXYIW0ziwr31QHEuDiGBI4wSM9/NYIRwljFK/N/yhhGkik1A R+L5o3/MILaIQJXEvp6NrCA2s4C8xNmrq8FqhAWiJPqWbYeqiZZYf/EAK4StJ3G18QALiM0i oCLx4vM5sBpeAV+J86+WgF3BKeAgsfTDMrAaRqCLvp9awwQxX1zi1pP5TBCXCkgs2XOeGcIW lXj5+B/YfFGg+d2zlrNCxJUlljzZzwLRqyOxYPcnoM84gGxribcNlhBhbYllC19DnSAocXLm E5YJjOKzkGybhaR7FkL3LCTds5B0L2BkXcXIUVqcWpabbmSwiREYb8ck2HR3MO55aXmIUZqD RUmc98tb5yAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjLqftTT0BAp5mqdJMue9undT9aDq o79+p7uzIn+xOZw54Kew8eyuMxstOY6edPhh2eEbOa9z8wO5FQIt/tmaMl9VZc/OF9q3o3zF 3Pk37uVWP9PZafSq69T7e14zFM7/cXBw5t0o/iMtK6+9Su1gKO+kia9PvhHb571lsouOMd/2 2QE1r5ZKeCmxFGckGmoxFxUnAgBqG2xXhQIAAA==
Cc: Routing WG <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, 05 Nov 2013 14:40:11 -0000

Hi Mark,
I attended and the majority of the discussion centered on whether the
problem could be solved with a simpler model such as a FIB per provider.
Fred pointed out that this would not handle overlapping source subnets and
the fact that it was possible to solve the general problem with a Patricia
tree and the installation disambiguating routes. Alvaro also commented
that there are use cases beyond homenet. As you'd expect, the next step
was that there needs to be more discussion on the RTG WG list (copied).
Thanks,
Acee

On 11/4/13 11:05 PM, "Mark Townsley" <mark@townsley.net> wrote:

>
>Was anyone on this list able to attend the rtgwg meeting today where Fred
>presented draft-baker-rtgwg-src-dst-routing-use-cases-00? I missed it,
>and would be interested in the reaction, feedback, or next steps (if any).
>
>Thanks,
>
>- Mark
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet


From fred@cisco.com  Tue Nov  5 07:20:08 2013
Return-Path: <fred@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 5F51C11E81FD; Tue,  5 Nov 2013 07:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.53
X-Spam-Level: 
X-Spam-Status: No, score=-110.53 tagged_above=-999 required=5 tests=[AWL=0.069, 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 H0Ets39VHFNk; Tue,  5 Nov 2013 07:20:03 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 5771A11E80FB; Tue,  5 Nov 2013 07:20:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1973; q=dns/txt; s=iport; t=1383664803; x=1384874403; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DI2qAnMM2yNZQk7jPEyzo+5c9nXlm2MOcdtHRtAVVEM=; b=mmaT9l6zpfwlmQhGcCMhTp5x7Yqzs6io6zD/mUQUm/KilSXdSafju2WL uikuQZEtKFQvwx972t5zxn3omZBpv74b+FBhVWxEvxJBkgSUPwABs+sOP q0yIUMDjlppK6sBVmkeqmc2+lrYIXcseuKQxvyKTrNm0Yz/QrPviC7Qs5 k=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAEoLeVKtJXG8/2dsb2JhbABZgwc4U75sS4EsFnSCJQEBAQMBAQEBawsFCwIBCBguJwslAgQOBQ6HbQYNvlEEj1kHgyCBDwOQLoEwhiySCYMmgio
X-IronPort-AV: E=Sophos;i="4.93,640,1378857600";  d="asc'?scan'208";a="277931861"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-9.cisco.com with ESMTP; 05 Nov 2013 15:19:56 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA5FJtao011820 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 15:19:55 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.122]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 09:19:55 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Acee Lindem <acee.lindem@ericsson.com>
Subject: Re: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
Thread-Topic: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
Thread-Index: AQHO2jp796+Fm6P3i0ymD2ohe6Z/Zw==
Date: Tue, 5 Nov 2013 15:19:54 +0000
Message-ID: <B6BB0DCD-D913-4E63-B33E-E6C74832FA92@cisco.com>
References: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se>
In-Reply-To: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.88.9]
Content-Type: multipart/signed; boundary="Apple-Mail=_6E6AE095-AF91-4A34-A4B8-2A91287B3778"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mark Townsley <mark@townsley.net>, Routing WG <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, 05 Nov 2013 15:20:08 -0000

--Apple-Mail=_6E6AE095-AF91-4A34-A4B8-2A91287B3778
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Yes, pretty much. 

On Nov 5, 2013, at 6:39 AM, Acee Lindem <acee.lindem@ericsson.com> wrote:

> Hi Mark,
> I attended and the majority of the discussion centered on whether the
> problem could be solved with a simpler model such as a FIB per provider.
> Fred pointed out that this would not handle overlapping source subnets and
> the fact that it was possible to solve the general problem with a Patricia
> tree and the installation disambiguating routes. Alvaro also commented
> that there are use cases beyond homenet. As you'd expect, the next step
> was that there needs to be more discussion on the RTG WG list (copied).
> Thanks,
> Acee
> 
> On 11/4/13 11:05 PM, "Mark Townsley" <mark@townsley.net> wrote:
> 
>> 
>> Was anyone on this list able to attend the rtgwg meeting today where Fred
>> presented draft-baker-rtgwg-src-dst-routing-use-cases-00? I missed it,
>> and would be interested in the reaction, feedback, or next steps (if any).
>> 
>> Thanks,
>> 
>> - Mark
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
> 

----------------------------------------------------
The ignorance of how to use new knowledge stockpiles exponentially. 
   - Marshall McLuhan


--Apple-Mail=_6E6AE095-AF91-4A34-A4B8-2A91287B3778
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSeQyXbjEdbHIsm0MRArjzAJ0Ut/lSm8vJf57sqy9pxuYhDRAFzwCg6ED1
BrJkz7v/TCZaHuijN22m+PE=
=fiZR
-----END PGP SIGNATURE-----

--Apple-Mail=_6E6AE095-AF91-4A34-A4B8-2A91287B3778--

From teco@inf-net.nl  Tue Nov  5 07:48:23 2013
Return-Path: <teco@inf-net.nl>
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 1AF8221E80FE for <rtgwg@ietfa.amsl.com>; Tue,  5 Nov 2013 07:48:23 -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 tEuh4FaZKyiL for <rtgwg@ietfa.amsl.com>; Tue,  5 Nov 2013 07:48:22 -0800 (PST)
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) by ietfa.amsl.com (Postfix) with ESMTP id 91C6E21E8198 for <rtgwg@ietf.org>; Tue,  5 Nov 2013 07:48:03 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id qd12so15211156ieb.33 for <rtgwg@ietf.org>; Tue, 05 Nov 2013 07:48:02 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=ShOBCkoLF6uigiHIV2ZRyTXCd4DRmxbTEvLv3rlimFk=; b=IadmV+wefD5uTiCQi0XgSDoBNHm+pwxSWN6dL8atpAzNX7lXIr1jEr8MAeskfZPULk cAdRdENyDwDfCChVXg0hRwJKAIXY/GR2rEJPfP+N/iPjJc25zQ/qJhPqG5d1yC2E62jH ta4k6nZEFiHfLvzjO/XBB1KpMZ8XeMx86++gIeqr95LnjsRvTNrjvl1EMqB00Vt2diMX XSUJmNzeAj6GArMFnU3ZMMKCz4PijiKqcP1ENYT+kKeMVg5Sa8nRRg2USW4fQLEoo+Gp +4KAbhmdXjUMFrM2TDv5kU4P4LkaFVZj9sO4wAljTbHwYIy38gef4P18AzNAb6OaHKSo hbgQ==
X-Gm-Message-State: ALoCoQkmeN06OE7QDMCVWPsfYS/K96yQBgWsx/p079c76+zNdJLTQi2j+tHceGXMBk6w72HRm+Zq
X-Received: by 10.50.61.179 with SMTP id q19mr16262512igr.33.1383666482414; Tue, 05 Nov 2013 07:48:02 -0800 (PST)
Received: from [142.131.18.140] ([64.114.24.114]) by mx.google.com with ESMTPSA id v2sm2655351igz.3.2013.11.05.07.48.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Nov 2013 07:48:01 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <B6BB0DCD-D913-4E63-B33E-E6C74832FA92@cisco.com>
Date: Tue, 5 Nov 2013 07:47:58 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <48E7C224-3A50-42BD-AF02-3F98D17200CA@inf-net.nl>
References: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se> <B6BB0DCD-D913-4E63-B33E-E6C74832FA92@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.1816)
X-Mailman-Approved-At: Tue, 05 Nov 2013 09:05:00 -0800
Cc: Mark Townsley <mark@townsley.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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, 05 Nov 2013 15:48:23 -0000

I=92m happy to confirm recent stable Linux kernel IPv6 subtrees cache =
problem is fixed. No need to do something special here, just give in =
some ip -6 route add default from PREFIX [ via ADDRESS ] [ dev STRING ] =
commands.
Sure we need to have a distribution mechanism having all routers know =
some form of (source_prefix, exit_link) mapping. If we take the =
limitation to support only default routes, a simple border router =
discovery and recursive FIB lookup will do. Select the route to the =
border router, or, on the border router, use the right exit link.
@Fred: I suggest you add my BRDP proposal in your list of efforts. No =
code yet. It is the blueprint for MultiSmartGateway for v6 in olrsd2, to =
replace SmartGateway tunnels which are used in current olsrd.org code.

Teco=20

Op 5 nov. 2013, om 07:19 heeft Fred Baker (fred) <fred@cisco.com> het =
volgende geschreven:

> Yes, pretty much.=20
>=20
> On Nov 5, 2013, at 6:39 AM, Acee Lindem <acee.lindem@ericsson.com> =
wrote:
>=20
>> Hi Mark,
>> I attended and the majority of the discussion centered on whether the
>> problem could be solved with a simpler model such as a FIB per =
provider.
>> Fred pointed out that this would not handle overlapping source =
subnets and
>> the fact that it was possible to solve the general problem with a =
Patricia
>> tree and the installation disambiguating routes. Alvaro also =
commented
>> that there are use cases beyond homenet. As you'd expect, the next =
step
>> was that there needs to be more discussion on the RTG WG list =
(copied).
>> Thanks,
>> Acee
>>=20
>> On 11/4/13 11:05 PM, "Mark Townsley" <mark@townsley.net> wrote:
>>=20
>>>=20
>>> Was anyone on this list able to attend the rtgwg meeting today where =
Fred
>>> presented draft-baker-rtgwg-src-dst-routing-use-cases-00? I missed =
it,
>>> and would be interested in the reaction, feedback, or next steps (if =
any).
>>>=20
>>> Thanks,
>>>=20
>>> - Mark
>>> _______________________________________________
>>> homenet mailing list
>>> homenet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/homenet
>>=20
>=20
> ----------------------------------------------------
> The ignorance of how to use new knowledge stockpiles exponentially.=20
>   - Marshall McLuhan
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From mark@townsley.net  Wed Nov  6 15:27:03 2013
Return-Path: <mark@townsley.net>
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 3C6E011E814F for <rtgwg@ietfa.amsl.com>; Wed,  6 Nov 2013 15:27:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level: 
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[AWL=0.889,  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 sX-yYfIMrEPt for <rtgwg@ietfa.amsl.com>; Wed,  6 Nov 2013 15:26:55 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9CDAE21E8064 for <rtgwg@ietf.org>; Wed,  6 Nov 2013 15:26:49 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id tp5so398891ieb.17 for <rtgwg@ietf.org>; Wed, 06 Nov 2013 15:26:49 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=QpZEKsiZs+yCT9nJfayHnVplSYexv3DopSi24q2cZZM=; b=FSUy730g+VQOVvIPXfWb3kAYI6M0+t2Bsn2E01Qe6oFmawpYoBYOy9b19yo/smKO8X w42Y/nJnhGoyUkKZG8sDwhjIhIIy0hfsIMCd1Tn9Bv4BtmHszkELj/AhfD45Qxn2PkIB DNmGGYs1VapgaBjZVBVvdvtMrX1nG7vSVTe76mnmR+JE0P07wjE52Fk3TvQU59RHnn8P 5SIvEU8MimHaVx0vkO/LJM+91J7XXVUJV5SzTjQyxVY/pJlfOkMRthsMOXmmWlJRRhg6 E34bP3lMOKlaGDNuBh2l7bVNCssp2sfaIEvml8UFm7FXOY5SkSVNig3nhADQ5fI78uXF b4aA==
X-Gm-Message-State: ALoCoQlYPULK65wdabYOebLoRYfaZ0yPH3zSBk052RTvNGVdtjtx5h3PAr5N4SIsKv/kzzy9PCYA
X-Received: by 10.43.60.139 with SMTP id ws11mr3739170icb.12.1383780408829; Wed, 06 Nov 2013 15:26:48 -0800 (PST)
Received: from dhcp-a4b2.meeting.ietf.org (dhcp-a4b2.meeting.ietf.org. [31.133.164.178]) by mx.google.com with ESMTPSA id l7sm814132igx.2.2013.11.06.15.26.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Nov 2013 15:26:48 -0800 (PST)
Subject: Re: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_E66CC528-5939-4BA5-8277-06CC7D6BA55A"
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <48E7C224-3A50-42BD-AF02-3F98D17200CA@inf-net.nl>
Date: Wed, 6 Nov 2013 15:26:45 -0800
Message-Id: <D5D7A086-FC1A-4835-B437-254BE965C666@townsley.net>
References: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se> <B6BB0DCD-D913-4E63-B33E-E6C74832FA92@cisco.com> <48E7C224-3A50-42BD-AF02-3F98D17200CA@inf-net.nl>
To: "Fred Baker (fred)" <fred@cisco.com>, Acee Lindem <acee.lindem@ericsson.com>
X-Mailer: Apple Mail (2.1283)
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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, 06 Nov 2013 23:27:03 -0000

--Apple-Mail=_E66CC528-5939-4BA5-8277-06CC7D6BA55A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


The derived requirements from =
draft-baker-rtgwg-src-dst-routing-use-cases (copied below) were based =
upon the outcome of a meeting at the last IETF in Berlin among the =
various "source plus destination routing" draft authors. Fred will be =
presenting this draft tomorrow in homenet. This functionality is =
fundamental to the operation of a multihomed homenet, so I'd like to get =
feedback (on list and during the meeting) on whether these are indeed =
the agreed upon requirements between the two groups.


  o  The routing protocol or mechanism includes a source prefix.  It is
      acceptable that a default source prefix of ::/0 (all addresses)
      applies to routes that don't specify a prefix.

   o  The routing protocol or mechanism includes a destination prefix,
      which may be a default route (::/0) or any more specific prefix up
      to and including a host route (/128).

   o  The FIB lookup yields the route with the most specific (e.g.
      longest-match) destination prefix that also matches the source
      prefix constraint, or no match.

Thanks,

- Mark

On Nov 5, 2013, at 7:47 AM, Teco Boot wrote:

> I=92m happy to confirm recent stable Linux kernel IPv6 subtrees cache =
problem is fixed. No need to do something special here, just give in =
some ip -6 route add default from PREFIX [ via ADDRESS ] [ dev STRING ] =
commands.
> Sure we need to have a distribution mechanism having all routers know =
some form of (source_prefix, exit_link) mapping. If we take the =
limitation to support only default routes, a simple border router =
discovery and recursive FIB lookup will do. Select the route to the =
border router, or, on the border router, use the right exit link.
> @Fred: I suggest you add my BRDP proposal in your list of efforts. No =
code yet. It is the blueprint for MultiSmartGateway for v6 in olrsd2, to =
replace SmartGateway tunnels which are used in current olsrd.org code.
>=20
> Teco=20
>=20
> Op 5 nov. 2013, om 07:19 heeft Fred Baker (fred) <fred@cisco.com> het =
volgende geschreven:
>=20
>> Yes, pretty much.=20
>>=20
>> On Nov 5, 2013, at 6:39 AM, Acee Lindem <acee.lindem@ericsson.com> =
wrote:
>>=20
>>> Hi Mark,
>>> I attended and the majority of the discussion centered on whether =
the
>>> problem could be solved with a simpler model such as a FIB per =
provider.
>>> Fred pointed out that this would not handle overlapping source =
subnets and
>>> the fact that it was possible to solve the general problem with a =
Patricia
>>> tree and the installation disambiguating routes. Alvaro also =
commented
>>> that there are use cases beyond homenet. As you'd expect, the next =
step
>>> was that there needs to be more discussion on the RTG WG list =
(copied).
>>> Thanks,
>>> Acee
>>>=20
>>> On 11/4/13 11:05 PM, "Mark Townsley" <mark@townsley.net> wrote:
>>>=20
>>>>=20
>>>> Was anyone on this list able to attend the rtgwg meeting today =
where Fred
>>>> presented draft-baker-rtgwg-src-dst-routing-use-cases-00? I missed =
it,
>>>> and would be interested in the reaction, feedback, or next steps =
(if any).
>>>>=20
>>>> Thanks,
>>>>=20
>>>> - Mark
>>>> _______________________________________________
>>>> homenet mailing list
>>>> homenet@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/homenet
>>>=20
>>=20
>> ----------------------------------------------------
>> The ignorance of how to use new knowledge stockpiles exponentially.=20=

>>  - Marshall McLuhan
>>=20
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>=20


--Apple-Mail=_E66CC528-5939-4BA5-8277-06CC7D6BA55A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><div>The derived requirements =
from&nbsp;draft-baker-rtgwg-src-dst-routing-use-cases (copied below) =
were based upon the outcome of a meeting at the last IETF in Berlin =
among the various "source plus destination routing" draft authors. Fred =
will be presenting this draft tomorrow in homenet. This functionality is =
fundamental to the operation of a multihomed homenet, so I'd like to get =
feedback (on list and during the meeting) on whether these are indeed =
the agreed upon requirements between the two =
groups.</div><div><br></div><div><br></div><div><pre class=3D"newpage" =
style=3D"font-size: 1em; margin-top: 0px; margin-bottom: 0px; =
page-break-before: always; color: rgb(0, 0, 0); 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; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">  o  =
The routing protocol or mechanism includes a source prefix.  It is
      acceptable that a default source prefix of ::/0 (all addresses)
      applies to routes that don't specify a prefix.

   o  The routing protocol or mechanism includes a destination prefix,
      which may be a default route (::/0) or any more specific prefix up
      to and including a host route (/128).

   o  The FIB lookup yields the route with the most specific (e.g.
      longest-match) destination prefix that also matches the source
      prefix constraint, or no =
match.</pre><div><br></div></div><div>Thanks,</div><div><br></div><div>- =
Mark</div><br><div><div>On Nov 5, 2013, at 7:47 AM, Teco Boot =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>I=92m happy to confirm recent stable Linux kernel =
IPv6 subtrees cache problem is fixed. No need to do something special =
here, just give in some ip -6 route add default from PREFIX [ via =
ADDRESS ] [ dev STRING ] commands.<br>Sure we need to have a =
distribution mechanism having all routers know some form of =
(source_prefix, exit_link) mapping. If we take the limitation to support =
only default routes, a simple border router discovery and recursive FIB =
lookup will do. Select the route to the border router, or, on the border =
router, use the right exit link.<br>@Fred: I suggest you add my BRDP =
proposal in your list of efforts. No code yet. It is the blueprint for =
MultiSmartGateway for v6 in olrsd2, to replace SmartGateway tunnels =
which are used in current <a href=3D"http://olsrd.org">olsrd.org</a> =
code.<br><br>Teco <br><br>Op 5 nov. 2013, om 07:19 heeft Fred Baker =
(fred) &lt;<a href=3D"mailto:fred@cisco.com">fred@cisco.com</a>&gt; het =
volgende geschreven:<br><br><blockquote type=3D"cite">Yes, pretty much. =
<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">On Nov 5, 2013, at 6:39 AM, Acee Lindem &lt;<a =
href=3D"mailto:acee.lindem@ericsson.com">acee.lindem@ericsson.com</a>&gt; =
wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Hi Mark,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I attended and the majority of =
the discussion centered on whether =
the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">problem could be solved with a simpler model such as a FIB =
per provider.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Fred pointed out that this would =
not handle overlapping source subnets =
and<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">the fact that it was possible to solve the general problem =
with a Patricia<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">tree and the installation =
disambiguating routes. Alvaro also =
commented<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">that there are use cases beyond =
homenet. As you'd expect, the next =
step<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">was that there needs to be more discussion on the RTG WG =
list (copied).<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Thanks,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Acee<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">On 11/4/13 11:05 PM, "Mark =
Townsley" &lt;<a =
href=3D"mailto:mark@townsley.net">mark@townsley.net</a>&gt; =
wrote:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Was =
anyone on this list able to attend the rtgwg meeting today where =
Fred<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">presented draft-baker-rtgwg-src-dst-routing-use-cases-00? =
I missed it,<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">and =
would be interested in the reaction, feedback, or next steps (if =
any).<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Thanks,<br></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">- =
Mark<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">homenet mailing =
list<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br></blockquote></bl=
ockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/homenet">https://www.ietf.or=
g/mailman/listinfo/homenet</a><br></blockquote></blockquote></blockquote><=
blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">----------------------------------------------------<br></bl=
ockquote><blockquote type=3D"cite">The ignorance of how to use new =
knowledge stockpiles exponentially. <br></blockquote><blockquote =
type=3D"cite"> &nbsp;- Marshall McLuhan<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">homenet mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/homenet">https://www.ietf.or=
g/mailman/listinfo/homenet</a><br></blockquote><br></div></blockquote></di=
v><br></body></html>=

--Apple-Mail=_E66CC528-5939-4BA5-8277-06CC7D6BA55A--

From equinox@spaceboyz.net  Wed Nov  6 15:51:44 2013
Return-Path: <equinox@spaceboyz.net>
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 7069421F9EE1; Wed,  6 Nov 2013 15:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 ONuLk4CYSBzN; Wed,  6 Nov 2013 15:51:41 -0800 (PST)
Received: from spaceboyz.net (spaceboyz.net [IPv6:2001:8d8:870:1000::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E23021F9ED2; Wed,  6 Nov 2013 15:51:40 -0800 (PST)
Received: from equinox by spaceboyz.net with local (Exim 4.80.1) (envelope-from <equinox@spaceboyz.net>) id 1VeCsr-0002e4-2c; Thu, 07 Nov 2013 00:51:37 +0100
Date: Thu, 7 Nov 2013 00:51:37 +0100
From: David Lamparter <equinox@diac24.net>
To: "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
Message-ID: <20131106235136.GI4891@spaceboyz.net>
References: <A8A941F6-FDC1-4F6A-A2D7-F4AEAA012BE9@townsley.net> <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: <equinox@spaceboyz.net>
X-Mailman-Approved-At: Wed, 06 Nov 2013 16:16:33 -0800
Cc: Mark Townsley <mark@townsley.net>
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, 06 Nov 2013 23:51:44 -0000

On Tue, Nov 05, 2013 at 02:39:09PM +0000, Acee Lindem wrote:
> Hi Mark,
> I attended and the majority of the discussion centered on whether the
> problem could be solved with a simpler model such as a FIB per provider.
> Fred pointed out that this would not handle overlapping source subnets and
> the fact that it was possible to solve the general problem with a Patricia
> tree and the installation disambiguating routes. Alvaro also commented
> that there are use cases beyond homenet. As you'd expect, the next step
> was that there needs to be more discussion on the RTG WG list (copied).

I disagree that it needs more discussion, at least on this particular
item.  It's an implementation detail.  The way it's currently described
does somewhat imply single-FIB, but it doesn't prescribe it, and in the
end it *is* the match behaviour we want - so, I'd just interpret it as
requirement on the _behaviour_ and if anyone wants to go with multiple
FIBs in their implementation, feel free...

(Yes, trying to put the "implementation detail" lid on the discussion
here.)

If anyone thinks we should have different match behaviour, that's a
different discussion (but I haven't heard anything in that direction.)
Describing the same match behaviour with multiple FIBs per source
doesn't sound easier to me.  I believe the current description is as
simple and down to it as it gets.


-David


P.S.: I'm not even sure if a "FIB per provider" model is actually
simpler, and I'm pretty certain the implementation is more complex.
You'd have to copy most of the FIB content to each of the FIBs,
dynamically create FIBs when upstreams appear/disappear (on remote
routers even), and then there's also the case of an upstream going down
=> its addresses being deprecated => host still using them for old local
connections => router should retain local connectivity for deprecated
prefix => router needs to retain FIB with timer.  Also needs to be done
with routes, but I'd prefer doing it on routes only, and not on routes
and FIBs.

And I almost deleted that PS - really, implementation detail!

> Thanks,
> Acee
> 
> On 11/4/13 11:05 PM, "Mark Townsley" <mark@townsley.net> wrote:
> 
> >Was anyone on this list able to attend the rtgwg meeting today where Fred
> >presented draft-baker-rtgwg-src-dst-routing-use-cases-00? I missed it,
> >and would be interested in the reaction, feedback, or next steps (if any).

From teco@inf-net.nl  Wed Nov  6 17:19:39 2013
Return-Path: <teco@inf-net.nl>
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 2F2ED11E81C7 for <rtgwg@ietfa.amsl.com>; Wed,  6 Nov 2013 17:19:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level: 
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=1.045,  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 WZ6XU3wXp1dY for <rtgwg@ietfa.amsl.com>; Wed,  6 Nov 2013 17:19:33 -0800 (PST)
Received: from mail-bk0-f42.google.com (mail-bk0-f42.google.com [209.85.214.42]) by ietfa.amsl.com (Postfix) with ESMTP id DD1A311E81CD for <rtgwg@ietf.org>; Wed,  6 Nov 2013 17:19:32 -0800 (PST)
Received: by mail-bk0-f42.google.com with SMTP id w16so99441bkz.29 for <rtgwg@ietf.org>; Wed, 06 Nov 2013 17:19:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=TarZnogPl+9E5DJ4B4CYlqH/vFqdo8PDyKMLjMUNQ2s=; b=g96iIcpq2DChC1mj+5Q2bKmdDLiVQcpPhgF/+8QTf3X9ynXZQOn+f16W46JJG7WNgV ZlxQJeYMjAFD3bK7tBBdqwDcbUHlP//w8XjLhvlTV4mPXSGewTS+waDHP1Gmq/mbYO2S pzHJwvlPNkWgyGJdHqQ5KCvFQktobeXdi162jpSeJE+XWfDA6V9CfVv4s9x+9YUSWdu/ ArY/Z+SLdRMogYEyws3cNouR92j+DPbKpZJDSvRQDEyEXS7mgJquDyqNLIv/CtrY8zRJ FEZtik5Kp5rkO6elNRSeNqaAmpB2ZYGNb42sCCFgj/eWFmjHxhZV1XQr1eHVbwcVo/wP dwzA==
X-Gm-Message-State: ALoCoQlKTAe20JxuVSIYYfVtyDTiE/J8EC9J2PqUxHoTrf+PPbHQOZzeEylUyeIU60DdNdwIs4aX
X-Received: by 10.204.247.71 with SMTP id mb7mr4159348bkb.7.1383787171205; Wed, 06 Nov 2013 17:19:31 -0800 (PST)
Received: from dhcp-a43c.meeting.ietf.org (dhcp-a43c.meeting.ietf.org. [31.133.164.60]) by mx.google.com with ESMTPSA id b6sm526682bko.16.2013.11.06.17.19.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Nov 2013 17:19:30 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <D5D7A086-FC1A-4835-B437-254BE965C666@townsley.net>
Date: Wed, 6 Nov 2013 17:19:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4365745-1D03-46CD-9C61-4C0A7DB8C289@inf-net.nl>
References: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se> <B6BB0DCD-D913-4E63-B33E-E6C74832FA92@cisco.com> <48E7C224-3A50-42BD-AF02-3F98D17200CA@inf-net.nl> <D5D7A086-FC1A-4835-B437-254BE965C666@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1816)
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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, 07 Nov 2013 01:19:39 -0000

Op 6 nov. 2013, om 15:26 heeft Mark Townsley <mark@townsley.net> het =
volgende geschreven:

>=20
> The derived requirements from =
draft-baker-rtgwg-src-dst-routing-use-cases (copied below) were based =
upon the outcome of a meeting at the last IETF in Berlin among the =
various "source plus destination routing" draft authors. Fred will be =
presenting this draft tomorrow in homenet. This functionality is =
fundamental to the operation of a multihomed homenet, so I'd like to get =
feedback (on list and during the meeting) on whether these are indeed =
the agreed upon requirements between the two groups.
>=20
>=20
>   o  The routing protocol or mechanism includes a source prefix.  It =
is
>       acceptable that a default source prefix of ::/0 (all addresses)
>       applies to routes that don't specify a prefix.
>=20
>    o  The routing protocol or mechanism includes a destination prefix,
>       which may be a default route (::/0) or any more specific prefix =
up
>       to and including a host route (/128).

For homenets and having ingress filtering as BCP, I think ::/0 routes =
with ::/0 source prefixes shall not be used. Also, for homenets I do not =
see a use case for non-::0 destination prefixes with non-::/0 source =
prefixes.

>=20
>=20
>    o  The FIB lookup yields the route with the most specific (e.g.
>       longest-match) destination prefix that also matches the source
>       prefix constraint, or no match.
I think this needs better specification. Something like:
   o  The FIB lookup yields the route with the most specific (e.g.
      longest-match) destination prefix, and thereafter use the most=20
      specific (e.g. longest-match) source prefix.

Or from troan-homenet-sadr:
   First a longest match lookup is done in the routing table for the
   destination address, then for the resulting set a longest matching
   lookup is done for the source address.

This is running code with recent Linux kernel, with enabled CONFIG_IPV6.

Teco

>=20
>=20
> Thanks,
>=20
> - Mark
>=20
> On Nov 5, 2013, at 7:47 AM, Teco Boot wrote:
>=20
>> I=92m happy to confirm recent stable Linux kernel IPv6 subtrees cache =
problem is fixed. No need to do something special here, just give in =
some ip -6 route add default from PREFIX [ via ADDRESS ] [ dev STRING ] =
commands.
>> Sure we need to have a distribution mechanism having all routers know =
some form of (source_prefix, exit_link) mapping. If we take the =
limitation to support only default routes, a simple border router =
discovery and recursive FIB lookup will do. Select the route to the =
border router, or, on the border router, use the right exit link.
>> @Fred: I suggest you add my BRDP proposal in your list of efforts. No =
code yet. It is the blueprint for MultiSmartGateway for v6 in olrsd2, to =
replace SmartGateway tunnels which are used in current olsrd.org code.
>>=20
>> Teco=20
>>=20
>> Op 5 nov. 2013, om 07:19 heeft Fred Baker (fred) <fred@cisco.com> het =
volgende geschreven:
>>=20
>>> Yes, pretty much.=20
>>>=20
>>> On Nov 5, 2013, at 6:39 AM, Acee Lindem <acee.lindem@ericsson.com> =
wrote:
>>>=20
>>>> Hi Mark,
>>>> I attended and the majority of the discussion centered on whether =
the
>>>> problem could be solved with a simpler model such as a FIB per =
provider.
>>>> Fred pointed out that this would not handle overlapping source =
subnets and
>>>> the fact that it was possible to solve the general problem with a =
Patricia
>>>> tree and the installation disambiguating routes. Alvaro also =
commented
>>>> that there are use cases beyond homenet. As you'd expect, the next =
step
>>>> was that there needs to be more discussion on the RTG WG list =
(copied).
>>>> Thanks,
>>>> Acee
>>>>=20
>>>> On 11/4/13 11:05 PM, "Mark Townsley" <mark@townsley.net> wrote:
>>>>=20
>>>>>=20
>>>>> Was anyone on this list able to attend the rtgwg meeting today =
where Fred
>>>>> presented draft-baker-rtgwg-src-dst-routing-use-cases-00? I missed =
it,
>>>>> and would be interested in the reaction, feedback, or next steps =
(if any).
>>>>>=20
>>>>> Thanks,
>>>>>=20
>>>>> - Mark
>>>>> _______________________________________________
>>>>> homenet mailing list
>>>>> homenet@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/homenet
>>>>=20
>>>=20
>>> ----------------------------------------------------
>>> The ignorance of how to use new knowledge stockpiles exponentially.=20=

>>>  - Marshall McLuhan
>>>=20
>>> _______________________________________________
>>> homenet mailing list
>>> homenet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/homenet
>>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From equinox@spaceboyz.net  Wed Nov  6 18:06:58 2013
Return-Path: <equinox@spaceboyz.net>
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 79AB711E8227; Wed,  6 Nov 2013 18:06:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 lS7x5HtLCj0P; Wed,  6 Nov 2013 18:06:57 -0800 (PST)
Received: from spaceboyz.net (spaceboyz.net [IPv6:2001:8d8:870:1000::1]) by ietfa.amsl.com (Postfix) with ESMTP id DFB5411E821D; Wed,  6 Nov 2013 18:06:50 -0800 (PST)
Received: from equinox by spaceboyz.net with local (Exim 4.80.1) (envelope-from <equinox@spaceboyz.net>) id 1VeEzg-0002JD-DM; Thu, 07 Nov 2013 03:06:48 +0100
Date: Thu, 7 Nov 2013 03:06:48 +0100
From: David Lamparter <equinox@diac24.net>
To: Teco Boot <teco@inf-net.nl>
Subject: Re: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
Message-ID: <20131107020648.GN4891@spaceboyz.net>
References: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se> <B6BB0DCD-D913-4E63-B33E-E6C74832FA92@cisco.com> <48E7C224-3A50-42BD-AF02-3F98D17200CA@inf-net.nl> <D5D7A086-FC1A-4835-B437-254BE965C666@townsley.net> <A4365745-1D03-46CD-9C61-4C0A7DB8C289@inf-net.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <A4365745-1D03-46CD-9C61-4C0A7DB8C289@inf-net.nl>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: <equinox@spaceboyz.net>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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, 07 Nov 2013 02:06:58 -0000

On Wed, Nov 06, 2013 at 05:19:27PM -0800, Teco Boot wrote:
> Op 6 nov. 2013, om 15:26 heeft Mark Townsley <mark@townsley.net> het volgende geschreven:
> >    o  The routing protocol or mechanism includes a destination prefix,
> >       which may be a default route (::/0) or any more specific prefix up
> >       to and including a host route (/128).
> 
> For homenets and having ingress filtering as BCP, I think ::/0 routes
> with ::/0 source prefixes shall not be used. Also, for homenets I do
> not see a use case for non-::0 destination prefixes with non-::/0
> source prefixes.

The NTT video service mentioned several times (forgot the name) is a
good example of non-::0 dst with non-::0 src.  Admittedly, you could
drop the source information without too much loss there, but I'm still
hopeful that we can somehow feed that information up into the host to
improve source address selection.

That use case also presents a nice demo of the non-match behaviour
because there will be no (dst ::0 src <videoprefix>) route, yielding an
automatÑ–c unreachable should a host try to go on the internet with its
video address.


-David

From teco@inf-net.nl  Wed Nov  6 23:32:23 2013
Return-Path: <teco@inf-net.nl>
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 B08B321E8098 for <rtgwg@ietfa.amsl.com>; Wed,  6 Nov 2013 23:32:23 -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 FUvr82Vnwngk for <rtgwg@ietfa.amsl.com>; Wed,  6 Nov 2013 23:32:17 -0800 (PST)
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by ietfa.amsl.com (Postfix) with ESMTP id CF41F21E8063 for <rtgwg@ietf.org>; Wed,  6 Nov 2013 23:32:16 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id aq17so230246iec.34 for <rtgwg@ietf.org>; Wed, 06 Nov 2013 23:32:16 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=wdP+OYv0r5wl3F5lNv6JMRgmdJZU2vP7eTCdUsX2juU=; b=E/Sa+np8rqOOTMy2jlPu4rfMtGdasP8k5ymV2WUiMaVxXLhWHABJyxddFgnpy+i4YX XCUhd+GpTo+437wOY5trrJDwi6UpE2UAvZVrBTFa5gLekBylyxD1v9zrgtOtI2XLJ0gp O/G02wFgeBZjfA3iTL5pAW5yU6ytJJ/14bIQFZI4G7VaaaKQs3XxsOayr0I29Kw7A2VB sq4iRJgjj4c/L5jAq8bwScuKpmDim2yIix5DuFjRsr9TUTUZoBDD60/75cpsJmNI3Ap3 ApXmSPzSKWYuTlNSDNKvJ3+kIFPLPpU1/HFIppNGaEdZSZdmnby74VCHh/Bp9+zSNi3z ggxg==
X-Gm-Message-State: ALoCoQmT+BZbqkceABSqVZcS7arMNu8zJcM9sBeD7F1x1miD+urxBPd1kHsuBjHZbULe/Z34C1sC
X-Received: by 10.50.61.35 with SMTP id m3mr1031053igr.56.1383809536262; Wed, 06 Nov 2013 23:32:16 -0800 (PST)
Received: from [142.131.18.140] ([64.114.24.114]) by mx.google.com with ESMTPSA id k6sm2893881igx.8.2013.11.06.23.32.14 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Nov 2013 23:32:15 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <20131107020648.GN4891@spaceboyz.net>
Date: Wed, 6 Nov 2013 23:32:13 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <706BB7CB-2165-4C46-B1F6-961662EA3E76@inf-net.nl>
References: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se> <B6BB0DCD-D913-4E63-B33E-E6C74832FA92@cisco.com> <48E7C224-3A50-42BD-AF02-3F98D17200CA@inf-net.nl> <D5D7A086-FC1A-4835-B437-254BE965C666@townsley.net> <A4365745-1D03-46CD-9C61-4C0A7DB8C289@inf-net.nl> <20131107020648.GN4891@spaceboyz.net>
To: David Lamparter <equinox@diac24.net>
X-Mailer: Apple Mail (2.1816)
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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, 07 Nov 2013 07:32:23 -0000

Op 6 nov. 2013, om 18:06 heeft David Lamparter <equinox@diac24.net> het =
volgende geschreven:

> On Wed, Nov 06, 2013 at 05:19:27PM -0800, Teco Boot wrote:
>> Op 6 nov. 2013, om 15:26 heeft Mark Townsley <mark@townsley.net> het =
volgende geschreven:
>>>   o  The routing protocol or mechanism includes a destination =
prefix,
>>>      which may be a default route (::/0) or any more specific prefix =
up
>>>      to and including a host route (/128).
>>=20
>> For homenets and having ingress filtering as BCP, I think ::/0 routes
>> with ::/0 source prefixes shall not be used. Also, for homenets I do
>> not see a use case for non-::0 destination prefixes with non-::/0
>> source prefixes.
>=20
> The NTT video service mentioned several times (forgot the name) is a
> good example of non-::0 dst with non-::0 src. =20

Why would ::/0 from SOURCE_PREFIX not work? It enables access to =
whatever prefix of the video service infrastructure.

Same model applies to VPN tunnel to enterprise network. It is a waste of =
energy to flood enterprise prefixes to VPN client. Sinking traffic with =
source VPN prefix will do.

Teco


> Admittedly, you could
> drop the source information without too much loss there, but I'm still
> hopeful that we can somehow feed that information up into the host to
> improve source address selection.
>=20
> That use case also presents a nice demo of the non-match behaviour
> because there will be no (dst ::0 src <videoprefix>) route, yielding =
an
> automat=D1=96c unreachable should a host try to go on the internet =
with its
> video address.
>=20
>=20
> -David


From fred@cisco.com  Thu Nov  7 08:46:31 2013
Return-Path: <fred@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 0F74321E81D7; Thu,  7 Nov 2013 08:46:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.406
X-Spam-Level: 
X-Spam-Status: No, score=-110.406 tagged_above=-999 required=5 tests=[AWL=0.193, 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 GfIFJp75IRmf; Thu,  7 Nov 2013 08:45:48 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 08ED321E81DA; Thu,  7 Nov 2013 08:45:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4082; q=dns/txt; s=iport; t=1383842711; x=1385052311; h=from:to:cc:subject:date:message-id:mime-version; bh=0fCRmUo2kyj0YZUSKGrF6CVkYbrAGNuWML0DY2sRDyQ=; b=NfOUmwcP+/OhaC1tiiXG7SAX/bZa2oYIGWvnzHLzSUHqi4oVzm5/hQJN ZksHptKQxuktbOuK02gTPuxSOr1Jiwz0auFmuG2zUCEx09t1RsS17nutl ncrr+pzDlTKdJ6UKALOTbmU1PN1uq0W+RRV1VppbJ8YPz0F9nEisWwPL/ 0=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAKXCe1KtJXG9/2dsb2JhbABagwc4U78OgSUWdIIseRIBgQAnBAENE4dzDbx0jg+BSoMngRADkC6BMIYugS+QW4Mmgio
X-IronPort-AV: E=Sophos;i="4.93,652,1378857600";  d="asc'?scan'208";a="282091699"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-4.cisco.com with ESMTP; 07 Nov 2013 16:45:08 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id rA7Gj8uB006053 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Nov 2013 16:45:08 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.122]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Thu, 7 Nov 2013 10:45:07 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Routing WG <rtgwg@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Tsinghua work on source/destination routing
Thread-Topic: Tsinghua work on source/destination routing
Thread-Index: AQHO29i28SykYfa5/UyGL9QietHsLg==
Date: Thu, 7 Nov 2013 16:45:06 +0000
Message-ID: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.75.25]
Content-Type: multipart/signed; boundary="Apple-Mail=_065270AE-DA93-4FAF-A37D-E241100F61F2"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, "v6ops@ietf.org WG" <v6ops@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, 07 Nov 2013 16:46:31 -0000

--Apple-Mail=_065270AE-DA93-4FAF-A37D-E241100F61F2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I'd like to draw your attention to a talk that will be given this =
morning in homenet. The context is:

=
http://datatracker.ietf.org/doc/draft-baker-rtgwg-src-dst-routing-use-case=
s
http://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cases
  "Requirements and Use Cases for Source/Destination Routing", Fred =
Baker,
  2013-08-13

http://datatracker.ietf.org/doc/draft-xu-homenet-traffic-class
http://tools.ietf.org/html/draft-xu-homenet-traffic-class
  "Traffic Class Routing Protocol in Home Networks", Mingwei Xu, Shu =
Yang,
  Jianping Wu, Fred Baker, 2013-10-21

http://datatracker.ietf.org/doc/draft-xu-homenet-twod-ip-routing
http://tools.ietf.org/html/draft-xu-homenet-twod-ip-routing
  "Two Dimensional-IP Routing Protocol in Home Networks", Mingwei Xu, =
Shu
  Yang, Jianping Wu, Dan Wang, 2013-08-22

http://datatracker.ietf.org/doc/draft-baker-ipv6-ospf-dst-src-routing
http://tools.ietf.org/html/draft-baker-ipv6-ospf-dst-src-routing
  "IPv6 Source/Destination Routing using OSPFv3", Fred Baker, 2013-08-28

http://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-lsa-extend
http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-lsa-extend
  "OSPFv3 LSA Extendibility", Acee Lindem, Sina Mirtorabi, Abhay Roy, =
Fred
  Baker, 2013-10-15

I had breakfast this morning with Shu Yang, who has been writing Quagga =
code for several years in the course of his PHd. He first implemented a =
source/destination model, reported on in =
draft-xu-homenet-twod-ip-routing, which was an MTR scheme. He tells me =
he found that very complex. He also listened to my talk in homenet =
around draft-baker-fun-routing-class, and has now implemented (if I =
understand him correctly) draft-ietf-ospf-ospfv3-lsa-extend and =
draft-baker-ipv6-ospf-dst-src-routing. The FIB implementation has a =
limitation: the source prefixes must be disjoint. However, given that, =
he has two FIB implementations, one of which has separate FIBs for each =
source prefix in play including ::/0 (so if there are M prefixes in the =
network, M+1 FIBs), and one of which is a single hierarchical M-Trie =
that looks up the destination and then the source. He has tested the =
code in simulation; the next step is testing in live networks.

Examples of use cases are generally around multi-prefix campus networks. =
There is a security use case that could be of value; at IETF 87, George =
Michaelson of APNIC reported on ULAs seen in his darknet. The short =
report is that he sees a fair bit of traffic with a ULA source address =
on the backbone. An interesting potential use of source/destination =
routing would counter that, and perhaps mitigate the need for ISP BCP 38 =
if generally deployed; in a case where a network is using a ULA and a =
global prefix (e.g., is not multihomed but has two prefixes, one of =
which is intended to only be used within its network), the default route =
to the network egress would use the global prefix as a source, and as a =
result traffic sent outside the network with a ULA source prefix would =
in effect have no route. The network could literally only emit traffic =
from its correct prefix.

I think this is relevant to the discussion of=20
	draft-baker-rtgwg-src-dst-routing-use-cases
	draft-ietf-ospf-ospfv3-lsa-extend
	draft-baker-ipv6-ospf-dst-src-routing
	draft-baker-ipv6-isis-dst-src-routing


--Apple-Mail=_065270AE-DA93-4FAF-A37D-E241100F61F2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSe8OSbjEdbHIsm0MRAo4JAKD1Gu32KozZNW+5Y1ee5sH14VA5XACg/9jZ
h0LqlvvqSnEfhdffbQ568wA=
=ofmZ
-----END PGP SIGNATURE-----

--Apple-Mail=_065270AE-DA93-4FAF-A37D-E241100F61F2--

From Fred.L.Templin@boeing.com  Thu Nov  7 09:08:24 2013
Return-Path: <Fred.L.Templin@boeing.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 7C4D321E81D8; Thu,  7 Nov 2013 09:08:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.527
X-Spam-Level: 
X-Spam-Status: No, score=-6.527 tagged_above=-999 required=5 tests=[AWL=0.072,  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 6U-OQ+jAgEBU; Thu,  7 Nov 2013 09:08:02 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB3C11E8188; Thu,  7 Nov 2013 09:07:38 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id rA7H7bgd012939; Thu, 7 Nov 2013 09:07:37 -0800
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id rA7H7aMq012929 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 7 Nov 2013 09:07:37 -0800
Received: from XCH-BLV-406.nw.nos.boeing.com (130.247.25.162) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Thu, 7 Nov 2013 09:07:36 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-406.nw.nos.boeing.com ([169.254.6.190]) with mapi id 14.03.0158.001; Thu, 7 Nov 2013 09:07:34 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker (fred)" <fred@cisco.com>, Routing WG <rtgwg@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: RE: Tsinghua work on source/destination routing
Thread-Topic: Tsinghua work on source/destination routing
Thread-Index: AQHO29i28SykYfa5/UyGL9QietHsLpoZ/WGA
Date: Thu, 7 Nov 2013 17:07:34 +0000
Message-ID: <2134F8430051B64F815C691A62D9831814AE3D@XCH-BLV-504.nw.nos.boeing.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com>
In-Reply-To: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, "v6ops@ietf.org WG" <v6ops@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, 07 Nov 2013 17:08:24 -0000

Hi Fred,

It is good to see this discussion, but an alternative approach that should
also be considered is tunneling. In the IRON approach at least, the end
user network gets a stable IPv6 prefix that is independent of the access
network IP addresses it gets from its ISPs. So, there is no need for source
address-based forwarding to ensure that packets sent via ISP A will not
have a source address from ISP B.

The use cases for tunneling are very broad, and probably overlap with the
ones you are considering in this approach. The relevant documents are here:

http://tools.ietf.org/html/draft-templin-ironbis
http://tools.ietf.org/html/draft-templin-intarea-vet
http://tools.ietf.org/html/draft-templin-intarea-seal
 =20
Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of=
 Fred Baker (fred)
> Sent: Thursday, November 07, 2013 8:45 AM
> To: Routing WG; ospf@ietf.org; isis-wg@ietf.org
> Cc: homenet@ietf.org Group; v6ops@ietf.org WG
> Subject: [v6ops] Tsinghua work on source/destination routing
>=20
> I'd like to draw your attention to a talk that will be given this morning=
 in homenet. The context is:
>=20
> http://datatracker.ietf.org/doc/draft-baker-rtgwg-src-dst-routing-use-cas=
es
> http://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cases
>   "Requirements and Use Cases for Source/Destination Routing", Fred Baker=
,
>   2013-08-13
>=20
> http://datatracker.ietf.org/doc/draft-xu-homenet-traffic-class
> http://tools.ietf.org/html/draft-xu-homenet-traffic-class
>   "Traffic Class Routing Protocol in Home Networks", Mingwei Xu, Shu Yang=
,
>   Jianping Wu, Fred Baker, 2013-10-21
>=20
> http://datatracker.ietf.org/doc/draft-xu-homenet-twod-ip-routing
> http://tools.ietf.org/html/draft-xu-homenet-twod-ip-routing
>   "Two Dimensional-IP Routing Protocol in Home Networks", Mingwei Xu, Shu
>   Yang, Jianping Wu, Dan Wang, 2013-08-22
>=20
> http://datatracker.ietf.org/doc/draft-baker-ipv6-ospf-dst-src-routing
> http://tools.ietf.org/html/draft-baker-ipv6-ospf-dst-src-routing
>   "IPv6 Source/Destination Routing using OSPFv3", Fred Baker, 2013-08-28
>=20
> http://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-lsa-extend
> http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-lsa-extend
>   "OSPFv3 LSA Extendibility", Acee Lindem, Sina Mirtorabi, Abhay Roy, Fre=
d
>   Baker, 2013-10-15
>=20
> I had breakfast this morning with Shu Yang, who has been writing Quagga c=
ode for several years in the
> course of his PHd. He first implemented a source/destination model, repor=
ted on in draft-xu-homenet-
> twod-ip-routing, which was an MTR scheme. He tells me he found that very =
complex. He also listened to
> my talk in homenet around draft-baker-fun-routing-class, and has now impl=
emented (if I understand him
> correctly) draft-ietf-ospf-ospfv3-lsa-extend and draft-baker-ipv6-ospf-ds=
t-src-routing. The FIB
> implementation has a limitation: the source prefixes must be disjoint. Ho=
wever, given that, he has two
> FIB implementations, one of which has separate FIBs for each source prefi=
x in play including ::/0 (so
> if there are M prefixes in the network, M+1 FIBs), and one of which is a =
single hierarchical M-Trie
> that looks up the destination and then the source. He has tested the code=
 in simulation; the next step
> is testing in live networks.
>=20
> Examples of use cases are generally around multi-prefix campus networks. =
There is a security use case
> that could be of value; at IETF 87, George Michaelson of APNIC reported o=
n ULAs seen in his darknet.
> The short report is that he sees a fair bit of traffic with a ULA source =
address on the backbone. An
> interesting potential use of source/destination routing would counter tha=
t, and perhaps mitigate the
> need for ISP BCP 38 if generally deployed; in a case where a network is u=
sing a ULA and a global
> prefix (e.g., is not multihomed but has two prefixes, one of which is int=
ended to only be used within
> its network), the default route to the network egress would use the globa=
l prefix as a source, and as
> a result traffic sent outside the network with a ULA source prefix would =
in effect have no route. The
> network could literally only emit traffic from its correct prefix.
>=20
> I think this is relevant to the discussion of
> 	draft-baker-rtgwg-src-dst-routing-use-cases
> 	draft-ietf-ospf-ospfv3-lsa-extend
> 	draft-baker-ipv6-ospf-dst-src-routing
> 	draft-baker-ipv6-isis-dst-src-routing


From furry13@gmail.com  Thu Nov  7 08:59:23 2013
Return-Path: <furry13@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 0CFB811E81CF; Thu,  7 Nov 2013 08:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599, NO_RELAYS=-0.001]
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 mFD7hSJxATaM; Thu,  7 Nov 2013 08:59:22 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id F31DA11E819E; Thu,  7 Nov 2013 08:59:21 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id cm18so657195qab.8 for <multiple recipients>; Thu, 07 Nov 2013 08:59:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=E6In2s4X0lJ4eSm+mhds+DubXv78BpYk2pyjpkrwmyo=; b=ctMeitCKZ8TbbL+9oJw1SmmbvTKcBI0lkcSORji2Hj8k1OMf0VY67d78WAMLm++LCN kT0sk/I7uw8MNp84l/u3Y/4e6ByYN8rIuwjSPL+3FubT8BuW4ohw+E9TMQhVkVxvXERW PRIkYADMSg1DSsJvL3GyxH4NWeP5f/oHwx7vCm4rm+/+ReuuyWWbBLMV4JschQq0K3XF 6NyXGEdogSeme+Qyun5s0bOzZda+JZnZ9JeWRQvwcIfQGnK5RHf6yYILkDukvCUzBa+3 umWRojvwrx//W4pElx60A5yy673ScRcj6o4QVQ1QVCWOSHvMEaPEWL5tG6IZfkenn2vp AScw==
X-Received: by 10.224.121.198 with SMTP id i6mr16184619qar.52.1383843556903; Thu, 07 Nov 2013 08:59:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.100.195 with HTTP; Thu, 7 Nov 2013 08:58:56 -0800 (PST)
In-Reply-To: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com>
From: Jen Linkova <furry13@gmail.com>
Date: Thu, 7 Nov 2013 17:58:56 +0100
Message-ID: <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com>
Subject: Re: [homenet] Tsinghua work on source/destination routing
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 07 Nov 2013 10:06:34 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <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, 07 Nov 2013 16:59:23 -0000

On Thu, Nov 7, 2013 at 5:45 PM, Fred Baker (fred) <fred@cisco.com> wrote:
> Examples of use cases are generally around multi-prefix campus networks. =
There is a security use case that could be of value; at IETF 87, George Mic=
haelson of APNIC reported on ULAs seen in his darknet. The short report is =
that he sees a fair bit of traffic with a ULA source address on the backbon=
e. An interesting potential use of source/destination routing would counter=
 that, and perhaps mitigate the need for ISP BCP 38 if generally deployed; =
in a case where a network is using a ULA and a global prefix (e.g., is not =
multihomed but has two prefixes, one of which is intended to only be used w=
ithin its network), the default route to the network egress would use the g=
lobal prefix as a source, and as a result traffic sent outside the network =
with a ULA source prefix would in effect have no route. The network could l=
iterally only emit traffic from its correct prefix.

Looks like we (finally) have a chance to enforce the requirement from
RFC4007, Section9:

"If transmitting the packet on the chosen next-hop interface
would cause the packet to leave the zone of the source
address, i.e.,
cross a zone boundary of the scope of the
source address, then the packet is discarded. "

I'm seeing plenty of packets from link-local sources to global
destinations which means that:
1) there are hosts with broken default address selection
AND
2) routers on the Internet do forward such packets (violating the rule
mentioned above).
Fixing #2 actually requires making forwarding decision based on src
and dst (which is not happening now).

More data (sorry, shameless plug :))
https://ripe67.ripe.net/presentations/288-Jen_RIPE67.pdf

--=20
SY, Jen Linkova aka Furry

From mcr@sandelman.ca  Thu Nov  7 09:08:53 2013
Return-Path: <mcr@sandelman.ca>
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 3A5BA11E8188; Thu,  7 Nov 2013 09:08:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level: 
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[AWL=0.105,  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 Lqn3VzTOZH1r; Thu,  7 Nov 2013 09:08:38 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id BD9E921E81EB; Thu,  7 Nov 2013 09:08:16 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 495D920315; Thu,  7 Nov 2013 13:19:54 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id CFF9963B88; Thu,  7 Nov 2013 12:08:03 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id BBB6063AED; Thu,  7 Nov 2013 12:08:03 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "homenet\@ietf.org Group" <homenet@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: [homenet] draft-baker-rtgwg-src-dst-routing-use-cases-00 in the rtgwg today
In-Reply-To: <A4365745-1D03-46CD-9C61-4C0A7DB8C289@inf-net.nl>
References: <94A203EA12AECE4BA92D42DBFFE0AE47030C88C1@eusaamb106.ericsson.se> <B6BB0DCD-D913-4E63-B33E-E6C74832FA92@cisco.com> <48E7C224-3A50-42BD-AF02-3F98D17200CA@inf-net.nl> <D5D7A086-FC1A-4835-B437-254BE965C666@townsley.net> <A4365745-1D03-46CD-9C61-4C0A7DB8C289@inf-net.nl>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 07 Nov 2013 12:08:03 -0500
Message-ID: <15319.1383844083@sandelman.ca>
Sender: mcr@sandelman.ca
X-Mailman-Approved-At: Thu, 07 Nov 2013 10:06:32 -0800
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, 07 Nov 2013 17:08:53 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


Teco Boot <teco@inf-net.nl> wrote:
    > For homenets and having ingress filtering as BCP, I think ::/0 routes
    > with ::/0 source prefixes shall not be used. Also, for homenets I do
    > not see a use case for non-::0 destination prefixes with non-::/0
    > source prefixes.=20

Access to the LLN in the home might only effectively work if you use the
(right?) ULA.=20=20=20=20

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUnvI8YqHRg3pndX9AQKr6AP+M9RXjvT5Jv/12OK4awSiLxVWw4HnfrMR
5dKiXCv+osokJN4EcR8IBMTYvKwJUwybfBZkQxGT8/Wl8lnk7dy2fP+C02sAk4LQ
I8ZB2yD41ipHG916acmsajy7K8KXjZYb5BP66t3gu7iGakD7Q3q6/1v3hbariWMy
le5S19wbQwI=
=hzeN
-----END PGP SIGNATURE-----
--=-=-=--

From fred@cisco.com  Thu Nov  7 10:11:47 2013
Return-Path: <fred@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 AF42611E825C; Thu,  7 Nov 2013 10:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.459
X-Spam-Level: 
X-Spam-Status: No, score=-110.459 tagged_above=-999 required=5 tests=[AWL=0.140, 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 ygeKZ7PYErcU; Thu,  7 Nov 2013 10:11:18 -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 9D21B21E8133; Thu,  7 Nov 2013 10:08:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=986; q=dns/txt; s=iport; t=1383847720; x=1385057320; h=from:to:cc:subject:date:message-id:mime-version; bh=rNK/n9rCVGgdrWVK7lKOh7zvyVM9B+Sud2AlGra6Uaw=; b=lSACkgCflrnEgvSZ6XicZvtQWUzA5vHJ4qOXZkXA+scHXeUsa3oVoBrw 8pmR4c69r60q/R4lGzpUQnAkdxdEMXmZ9k+eU4dLcgmXBsChloERdD3Cp 4TaVrgeT5+eBo0n0+LcRJkn5cePGdUiRuVoaxwOsBHK2bX48p/SRjodZY 8=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAJfWe1KtJV2Y/2dsb2JhbABagwc4U78PgSUWdIIseRIBFmonBA4Th3MNvFWPWYMngRADkC6BMIYugS+QW4Mmgio
X-IronPort-AV: E=Sophos;i="4.93,653,1378857600";  d="asc'?scan'208";a="282060211"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 07 Nov 2013 18:08:28 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA7I8Sw6007328 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Nov 2013 18:08:28 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.122]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Thu, 7 Nov 2013 12:08:27 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: John Scudder <jgs@juniper.net>
Subject: Examples of ambiguous routes
Thread-Topic: Examples of ambiguous routes
Thread-Index: AQHO2+RbrEyXDKtjRUG4o3lf57Melw==
Date: Thu, 7 Nov 2013 18:08:26 +0000
Message-ID: <53454CA8-8DAA-4E33-A241-2EEE5EFBCC40@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.116.80]
Content-Type: multipart/signed; boundary="Apple-Mail=_7E81D233-BFC4-43DD-A9B6-C252F79FEE64"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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, 07 Nov 2013 18:11:47 -0000

--Apple-Mail=_7E81D233-BFC4-43DD-A9B6-C252F79FEE64
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I looked at draft-baker-rtgwg-src-dst-routing-use-cases for the text I =
mentioned, and you are correct: it's not there.

It is in:
    =
http://tools.ietf.org/html/draft-baker-ipv6-ospf-dst-src-routing-03#sectio=
n-2.2

and its is-is counterpart. I'll copy that example into the use case =
draft.

--Apple-Mail=_7E81D233-BFC4-43DD-A9B6-C252F79FEE64
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSe9cZbjEdbHIsm0MRAiX/AJ48GVS36orIjvqME18X3CP2WtpnKwCgpQY5
mtpNKngfz666EzLro+F9RDQ=
=CDH2
-----END PGP SIGNATURE-----

--Apple-Mail=_7E81D233-BFC4-43DD-A9B6-C252F79FEE64--

From fred@cisco.com  Thu Nov  7 10:56:45 2013
Return-Path: <fred@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 B87CF21E8219; Thu,  7 Nov 2013 10:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.314
X-Spam-Level: 
X-Spam-Status: No, score=-110.314 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 thhb18A-2jfu; Thu,  7 Nov 2013 10:56:36 -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 44FE221E814E; Thu,  7 Nov 2013 10:56:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2305; q=dns/txt; s=iport; t=1383850583; x=1385060183; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=u94GyZUlvbj5d0RSc0jv9e9KFnokK1ampB+pehGsEe8=; b=WqFDHY2vr00esHogK1xhmoSghfdH2wWEnPh/NHdosE3U5u2QZY0pdtVn FsxjokHGScV9QHU3ygHrm3pUPEklOCA8vctnvlrG0uzB0xIqLqjNj0NHM Jt+VKHg0bURKi/5B/8D5piM80YMbbqYWln0sfXZ4+He7fu6iQqcIET+Mb w=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFACfhe1KtJXG8/2dsb2JhbABagweBC4J0vBuBJRZ0giUBAQEDASNWBQsCAQYCGCoCAiERJQIEDgUOh2EDCQaOOJteiFkNiWuMZ4E0gT4Hgms1gRADkC6BMIRDgWuMUoU4gyaBaUE
X-IronPort-AV: E=Sophos;i="4.93,653,1378857600";  d="asc'?scan'208";a="282096191"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-8.cisco.com with ESMTP; 07 Nov 2013 18:56:14 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA7IuDm0024565 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Nov 2013 18:56:14 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.122]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Thu, 7 Nov 2013 12:56:13 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
Thread-Topic: [v6ops] [homenet] Tsinghua work on source/destination routing
Thread-Index: AQHO2+sHHvd0L93ku0KOjrOyzNpCaA==
Date: Thu, 7 Nov 2013 18:56:12 +0000
Message-ID: <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com>
In-Reply-To: <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.116.80]
Content-Type: multipart/signed; boundary="Apple-Mail=_80C57558-2DEF-458E-9CFE-A2F1F43DB003"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Jen Linkova <furry13@gmail.com>, "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <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, 07 Nov 2013 18:56:48 -0000

--Apple-Mail=_80C57558-2DEF-458E-9CFE-A2F1F43DB003
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On Nov 7, 2013, at 10:42 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp>
 wrote:

> At Thu, 7 Nov 2013 17:58:56 +0100,
> Jen Linkova <furry13@gmail.com> wrote:
>=20
>> Looks like we (finally) have a chance to enforce the requirement from
>> RFC4007, Section9:
>>=20
>> "If transmitting the packet on the chosen next-hop interface
>> would cause the packet to leave the zone of the source
>> address, i.e.,
>> cross a zone boundary of the scope of the
>> source address, then the packet is discarded. "
>>=20
>> I'm seeing plenty of packets from link-local sources to global
>> destinations which means that:
>> 1) there are hosts with broken default address selection
>> AND
>=20
> (Probably an off-topic in this context but) this is not necessarily
> accurate.  If a host only has a link-local address but somehow knows
> the interface to send packets to a global destination, it would be
> able to send packets with source being link-local and destination
> being global, and validly (not breaking RFC 6724) so.  I believe it's
> more likely to be a broken network configuration than a broken host
> implementation.

I suspect it's some of each. The host should, I should think, set the =
hop limit to one on any packet that is to a link-local address, to =
ensure that the packet is not repeated by a broken router (apart from =
protocols that ask to have it set to 255 and have the receiving host =
check for that value). Also, upstream network's BCP 38 implementation =
sounds suspect, and I'm with Jen in wondering why a router forwarded the =
packet in the first place.

--Apple-Mail=_80C57558-2DEF-458E-9CFE-A2F1F43DB003
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSe+JKbjEdbHIsm0MRAqkbAJ0ZTLdAY6APMRY3oOWLS72wLTuVrwCcDl04
LiKakgQCjPuHp+Um7AUSCPs=
=cwKF
-----END PGP SIGNATURE-----

--Apple-Mail=_80C57558-2DEF-458E-9CFE-A2F1F43DB003--

From hermin.anggawijaya@gmail.com  Thu Nov  7 10:41:13 2013
Return-Path: <hermin.anggawijaya@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 BD6AC21E8216; Thu,  7 Nov 2013 10:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
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 ucC9URx8BT4c; Thu,  7 Nov 2013 10:41:04 -0800 (PST)
Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 96C1421E8118; Thu,  7 Nov 2013 10:40:40 -0800 (PST)
Received: by mail-ve0-f178.google.com with SMTP id db12so709930veb.37 for <multiple recipients>; Thu, 07 Nov 2013 10:40:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u2qlO4+/ho6hSd/jP4oKgCqCmXp49G5B3sLVqWRrR9Q=; b=BoRsuq3ZPJf+11hd3ALQkVoGKOTYWzwcTccKFC8pRi+9OxP1/WFDyRvYbriT7AIdre WaaT5A/nXgT5gY3oUhFl4//lQL5kNkeyXZDWgnc5MZrqpxMzT8eQovMwSuqpPHY0DaDs m6nF4v/QWVx1Y7FmcDcWJWSdy9AksysRARtyw0WoZourOAoGIflSLMUdRzQllGFXgXNH wDXSBvZe7HOP0cD7SGS2d0cAdkzG42Q78MKAQWh7wgZEHMjvvsvbdqD2Tt8JvOMJtVVs yNIOHcxqXQLeYCLsGhEaEht0CU/J6Sf7TXo+4XYjR/kjsgX0EHyMmoOjl0SjOkGtNdix n9bQ==
MIME-Version: 1.0
X-Received: by 10.220.47.10 with SMTP id l10mr1814747vcf.32.1383849608424; Thu, 07 Nov 2013 10:40:08 -0800 (PST)
Received: by 10.58.188.72 with HTTP; Thu, 7 Nov 2013 10:40:08 -0800 (PST)
In-Reply-To: <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com>
Date: Thu, 7 Nov 2013 10:40:08 -0800
Message-ID: <CAJgsEzVmg5hGwsgVFDKrzbmrBnKBOZ1oAXRp-K0ovtPhwENcNw@mail.gmail.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
From: Hermin Anggawijaya <hermin.anggawijaya@gmail.com>
To: Jen Linkova <furry13@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2a58c55340d04ea9a9896
X-Mailman-Approved-At: Thu, 07 Nov 2013 12:11:57 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <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, 07 Nov 2013 18:41:13 -0000

--001a11c2a58c55340d04ea9a9896
Content-Type: text/plain; charset=ISO-8859-1

> I'm seeing plenty of packets from link-local sources to global
destinations
> .....
> 2) routers on the Internet do forward such packets (violating the rule
mentioned above).
> Fixing #2 actually requires making forwarding decision based on src
> and dst (which is not happening now).

To fix the above issue, wouldn't address scope checking be enough, rather
than the [src,dst] based routing
discussed ?



On Thu, Nov 7, 2013 at 8:58 AM, Jen Linkova <furry13@gmail.com> wrote:

> On Thu, Nov 7, 2013 at 5:45 PM, Fred Baker (fred) <fred@cisco.com> wrote:
> > Examples of use cases are generally around multi-prefix campus networks.
> There is a security use case that could be of value; at IETF 87, George
> Michaelson of APNIC reported on ULAs seen in his darknet. The short report
> is that he sees a fair bit of traffic with a ULA source address on the
> backbone. An interesting potential use of source/destination routing would
> counter that, and perhaps mitigate the need for ISP BCP 38 if generally
> deployed; in a case where a network is using a ULA and a global prefix
> (e.g., is not multihomed but has two prefixes, one of which is intended to
> only be used within its network), the default route to the network egress
> would use the global prefix as a source, and as a result traffic sent
> outside the network with a ULA source prefix would in effect have no route.
> The network could literally only emit traffic from its correct prefix.
>
> Looks like we (finally) have a chance to enforce the requirement from
> RFC4007, Section9:
>
> "If transmitting the packet on the chosen next-hop interface
> would cause the packet to leave the zone of the source
> address, i.e.,
> cross a zone boundary of the scope of the
> source address, then the packet is discarded. "
>
> I'm seeing plenty of packets from link-local sources to global
> destinations which means that:
> 1) there are hosts with broken default address selection
> AND
> 2) routers on the Internet do forward such packets (violating the rule
> mentioned above).
> Fixing #2 actually requires making forwarding decision based on src
> and dst (which is not happening now).
>
> More data (sorry, shameless plug :))
> https://ripe67.ripe.net/presentations/288-Jen_RIPE67.pdf
>
> --
> SY, Jen Linkova aka Furry
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

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

<div dir=3D"ltr"><div><div><div><br>&gt; I&#39;m seeing plenty of packets f=
rom link-local sources to global
destinations<br>&gt; .....<br>&gt; 2) routers on the Internet do forward su=
ch packets (violating the rule=A0
mentioned above).<br>
&gt; Fixing #2 actually requires making forwarding decision based on src<br=
>
&gt; and dst (which is not happening now).<br><br></div>To fix the above is=
sue, wouldn&#39;t address scope checking be enough, rather than the [src,ds=
t] based routing<br>discussed ?<br></div></div><br></div><div class=3D"gmai=
l_extra">
<br><br><div class=3D"gmail_quote">On Thu, Nov 7, 2013 at 8:58 AM, Jen Link=
ova <span dir=3D"ltr">&lt;<a href=3D"mailto:furry13@gmail.com" target=3D"_b=
lank">furry13@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
<div class=3D"im">On Thu, Nov 7, 2013 at 5:45 PM, Fred Baker (fred) &lt;<a =
href=3D"mailto:fred@cisco.com">fred@cisco.com</a>&gt; wrote:<br>
&gt; Examples of use cases are generally around multi-prefix campus network=
s. There is a security use case that could be of value; at IETF 87, George =
Michaelson of APNIC reported on ULAs seen in his darknet. The short report =
is that he sees a fair bit of traffic with a ULA source address on the back=
bone. An interesting potential use of source/destination routing would coun=
ter that, and perhaps mitigate the need for ISP BCP 38 if generally deploye=
d; in a case where a network is using a ULA and a global prefix (e.g., is n=
ot multihomed but has two prefixes, one of which is intended to only be use=
d within its network), the default route to the network egress would use th=
e global prefix as a source, and as a result traffic sent outside the netwo=
rk with a ULA source prefix would in effect have no route. The network coul=
d literally only emit traffic from its correct prefix.<br>

<br>
</div>Looks like we (finally) have a chance to enforce the requirement from=
<br>
RFC4007, Section9:<br>
<br>
&quot;If transmitting the packet on the chosen next-hop interface<br>
would cause the packet to leave the zone of the source<br>
address, i.e.,<br>
cross a zone boundary of the scope of the<br>
source address, then the packet is discarded. &quot;<br>
<br>
I&#39;m seeing plenty of packets from link-local sources to global<br>
destinations which means that:<br>
1) there are hosts with broken default address selection<br>
AND<br>
2) routers on the Internet do forward such packets (violating the rule<br>
mentioned above).<br>
Fixing #2 actually requires making forwarding decision based on src<br>
and dst (which is not happening now).<br>
<br>
More data (sorry, shameless plug :))<br>
<a href=3D"https://ripe67.ripe.net/presentations/288-Jen_RIPE67.pdf" target=
=3D"_blank">https://ripe67.ripe.net/presentations/288-Jen_RIPE67.pdf</a><br=
>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
SY, Jen Linkova aka Furry<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/v6ops</a><br>
</font></span></blockquote></div><br></div>

--001a11c2a58c55340d04ea9a9896--

From jinmei.tatuya@gmail.com  Thu Nov  7 10:43:51 2013
Return-Path: <jinmei.tatuya@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 AAF5C21E80FE; Thu,  7 Nov 2013 10:43:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 okINNPS-ZsSB; Thu,  7 Nov 2013 10:43:51 -0800 (PST)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id ACF5721E8200; Thu,  7 Nov 2013 10:42:56 -0800 (PST)
Received: by mail-we0-f178.google.com with SMTP id q59so940992wes.37 for <multiple recipients>; Thu, 07 Nov 2013 10:42:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=qSpNWGJWc8rjvH5McFCgIlaLQdmSEewymyCi3yoAyv4=; b=EZRzPTnTbvgBw8XkN5Hb9OGWNoHcngut+YyyUiS6shC4hX3TStvkZ/gDZZcIsiOFNe PjpD3WhoTBXPeyv7sE3txP7nmBlwG6y7cLsEmCdcdZpPamOuMEpLPdCMsxanZV7FjTIY 1/HAN5T4IuSU4PrpCSAnUiAAwQLb//0mA1WOYqSwdNkV6Tysw/kZ+Ked384RXUqeTxiA Fe32h/5sipfcnUK6W0DWKF5AAEFQUXXRPkC/YPSQxkDEALjFjFFojdDk0MQQbeZRkOTr GTUF8NBIwomzeKh/3SNvpTaGeAIZBPzMesX6GXQvMfMQXaR1jt56+2QmYeW8+UzXPW5u s3tQ==
MIME-Version: 1.0
X-Received: by 10.180.37.134 with SMTP id y6mr3867788wij.48.1383849772295; Thu, 07 Nov 2013 10:42:52 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Thu, 7 Nov 2013 10:42:52 -0800 (PST)
In-Reply-To: <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com>
Date: Thu, 7 Nov 2013 10:42:52 -0800
X-Google-Sender-Auth: dO1-WPbSBrhdlegMd1UcgfRY9tY
Message-ID: <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: Jen Linkova <furry13@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Thu, 07 Nov 2013 12:11:56 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <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, 07 Nov 2013 18:43:51 -0000

At Thu, 7 Nov 2013 17:58:56 +0100,
Jen Linkova <furry13@gmail.com> wrote:

> Looks like we (finally) have a chance to enforce the requirement from
> RFC4007, Section9:
>
> "If transmitting the packet on the chosen next-hop interface
> would cause the packet to leave the zone of the source
> address, i.e.,
> cross a zone boundary of the scope of the
> source address, then the packet is discarded. "
>
> I'm seeing plenty of packets from link-local sources to global
> destinations which means that:
> 1) there are hosts with broken default address selection
> AND

(Probably an off-topic in this context but) this is not necessarily
accurate.  If a host only has a link-local address but somehow knows
the interface to send packets to a global destination, it would be
able to send packets with source being link-local and destination
being global, and validly (not breaking RFC 6724) so.  I believe it's
more likely to be a broken network configuration than a broken host
implementation.

--
JINMEI, Tatuya

From brian.e.carpenter@gmail.com  Thu Nov  7 11:21:45 2013
Return-Path: <brian.e.carpenter@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 7B73E11E828C; Thu,  7 Nov 2013 11:21:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, 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 rQ1Tixzmnvsa; Thu,  7 Nov 2013 11:21:44 -0800 (PST)
Received: from mail-bk0-x22b.google.com (mail-bk0-x22b.google.com [IPv6:2a00:1450:4008:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id DDACA11E828D; Thu,  7 Nov 2013 11:21:43 -0800 (PST)
Received: by mail-bk0-f43.google.com with SMTP id mz13so413479bkb.30 for <multiple recipients>; Thu, 07 Nov 2013 11:21:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bIabsIcHA6ZJfIhoiBbd8a0Et6dQt3lhQ/KaVsKekEo=; b=dL+dvjy21rbKNtySs8I4Ll7h2kZboPvNqZps7RDwYDKHeT2RBNL5X/exrJkQS0eYVL Pve9umjIctiRj9X+OiyAslgumzmlgQQbJ+Lsegj3DWVNMWbAG2v3TLAayhVuasTaMxdQ lrvN2etWMUlx4gCr5gwrGAX8bkGM+yE78ItqQpxGrbPUhkydcz4yJOgcyquDS0MpdZlg jrnhM60F210Pt1RK1+9qvxv31kxGcWBjNDIvYMTwLg4RIJinNwOjkII/UTBC4S3+YFR6 8JJMwyrpHPiiEg1enk1kdWOkE2oXqK9aPxY5pU5P12LkWLNnykUOW20a2mfMhmF2KdVg Vq8Q==
X-Received: by 10.204.171.142 with SMTP id h14mr7568747bkz.30.1383852102969; Thu, 07 Nov 2013 11:21:42 -0800 (PST)
Received: from [31.133.165.38] (dhcp-a526.meeting.ietf.org. [31.133.165.38]) by mx.google.com with ESMTPSA id no2sm3317936bkb.15.2013.11.07.11.21.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 07 Nov 2013 11:21:42 -0800 (PST)
Message-ID: <527BE84E.2000205@gmail.com>
Date: Fri, 08 Nov 2013 08:21:50 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com>	<CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com>	<CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com> <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com>
In-Reply-To: <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 07 Nov 2013 12:11:56 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Routing WG <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, 07 Nov 2013 19:21:45 -0000

On 08/11/2013 07:56, Fred Baker (fred) wrote:
> On Nov 7, 2013, at 10:42 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinm=
ei@wide.ad.jp>
>  wrote:
>=20
>> At Thu, 7 Nov 2013 17:58:56 +0100,
>> Jen Linkova <furry13@gmail.com> wrote:
>>
>>> Looks like we (finally) have a chance to enforce the requirement from=

>>> RFC4007, Section9:
>>>
>>> "If transmitting the packet on the chosen next-hop interface
>>> would cause the packet to leave the zone of the source
>>> address, i.e.,
>>> cross a zone boundary of the scope of the
>>> source address, then the packet is discarded. "
>>>
>>> I'm seeing plenty of packets from link-local sources to global
>>> destinations which means that:
>>> 1) there are hosts with broken default address selection
>>> AND
>> (Probably an off-topic in this context but) this is not necessarily
>> accurate.  If a host only has a link-local address but somehow knows
>> the interface to send packets to a global destination, it would be
>> able to send packets with source being link-local and destination
>> being global, and validly (not breaking RFC 6724) so.  I believe it's
>> more likely to be a broken network configuration than a broken host
>> implementation.
>=20
> I suspect it's some of each. The host should, I should think, set the h=
op limit to one on any packet that is to a link-local address, to ensure =
that the packet is not repeated by a broken router (apart from protocols =
that ask to have it set to 255 and have the receiving host check for that=
 value). Also, upstream network's BCP 38 implementation sounds suspect, a=
nd I'm with Jen in wondering why a router forwarded the packet in the fir=
st place.

Are you sure these packets come from hosts? There is a known case
which is a router generating ICMP reply packets that has no GUA
configured since all its peers are link-local.

   Brian


From furry13@gmail.com  Thu Nov  7 15:27:32 2013
Return-Path: <furry13@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 C5FB311E8103; Thu,  7 Nov 2013 15:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.247
X-Spam-Level: 
X-Spam-Status: No, score=-2.247 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
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 B-AXll9Qp05c; Thu,  7 Nov 2013 15:27:27 -0800 (PST)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id E2DF111E8278; Thu,  7 Nov 2013 15:27:24 -0800 (PST)
Received: by mail-qc0-f182.google.com with SMTP id n7so1108757qcx.13 for <multiple recipients>; Thu, 07 Nov 2013 15:27:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VQxqJWkh/3nQG4mmBLkm0StRghWMOeanJOFthn2unaI=; b=ObA7wKbqjnGrhn4fGDghxlX3wIDtEKJnddxAd0YQhbNUiUDMwGp30dW59QMy/GnDot WCTCYdliIjV80a4AC3UwI1qvWbm+gGBnx/cSQe3ev0bwFloNRuDiJyiMkFsskKNW2NBh 5BKDDnFJD7freyf/c3LC895SmXqTChuR4Uc4EBkDLxLddGWHdJSAAdwDyFrlWIfFAa7l 9Q8mg0BoZTQWzwvs4Z21XLl7qLRCfid9dO6iVG3pNJtUU5gNo7MEJHHrOuPJ1Nb+doiN KUnCzcwUenmitVaidupvB3XBkhLZlOBSodZxcoXUsXUu38q4jsuhYXoSuLbBzSwPEXro bUXQ==
X-Received: by 10.224.73.200 with SMTP id r8mr18903610qaj.72.1383866844074; Thu, 07 Nov 2013 15:27:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.100.195 with HTTP; Thu, 7 Nov 2013 15:27:04 -0800 (PST)
In-Reply-To: <CAJgsEzVmg5hGwsgVFDKrzbmrBnKBOZ1oAXRp-K0ovtPhwENcNw@mail.gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJgsEzVmg5hGwsgVFDKrzbmrBnKBOZ1oAXRp-K0ovtPhwENcNw@mail.gmail.com>
From: Jen Linkova <furry13@gmail.com>
Date: Fri, 8 Nov 2013 00:27:04 +0100
Message-ID: <CAFU7BAT0GWeaJq8h_03PjJRtHupSWSFVLVXJ-FRjpti-7W+aWg@mail.gmail.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
To: Hermin Anggawijaya <hermin.anggawijaya@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <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, 07 Nov 2013 23:27:32 -0000

On Thu, Nov 7, 2013 at 7:40 PM, Hermin Anggawijaya
<hermin.anggawijaya@gmail.com> wrote:
>> I'm seeing plenty of packets from link-local sources to global
>> destinations
>> .....
>
>> 2) routers on the Internet do forward such packets (violating the rule
>> mentioned above).
>> Fixing #2 actually requires making forwarding decision based on src
>> and dst (which is not happening now).
>
> To fix the above issue, wouldn't address scope checking be enough, rather
> than the [src,dst] based routing
> discussed ?

My point is that to do verify the scope, the router need to check
*source* address while making forwarding decision.
It looks like it is not happening now but it might get changed by
[src, dst] based routing.

> On Thu, Nov 7, 2013 at 8:58 AM, Jen Linkova <furry13@gmail.com> wrote:
>>
>> On Thu, Nov 7, 2013 at 5:45 PM, Fred Baker (fred) <fred@cisco.com> wrote:
>> > Examples of use cases are generally around multi-prefix campus networks.
>> > There is a security use case that could be of value; at IETF 87, George
>> > Michaelson of APNIC reported on ULAs seen in his darknet. The short report
>> > is that he sees a fair bit of traffic with a ULA source address on the
>> > backbone. An interesting potential use of source/destination routing would
>> > counter that, and perhaps mitigate the need for ISP BCP 38 if generally
>> > deployed; in a case where a network is using a ULA and a global prefix
>> > (e.g., is not multihomed but has two prefixes, one of which is intended to
>> > only be used within its network), the default route to the network egress
>> > would use the global prefix as a source, and as a result traffic sent
>> > outside the network with a ULA source prefix would in effect have no route.
>> > The network could literally only emit traffic from its correct prefix.
>>
>> Looks like we (finally) have a chance to enforce the requirement from
>> RFC4007, Section9:
>>
>> "If transmitting the packet on the chosen next-hop interface
>> would cause the packet to leave the zone of the source
>> address, i.e.,
>> cross a zone boundary of the scope of the
>> source address, then the packet is discarded. "
>>
>> I'm seeing plenty of packets from link-local sources to global
>> destinations which means that:
>> 1) there are hosts with broken default address selection
>> AND
>> 2) routers on the Internet do forward such packets (violating the rule
>> mentioned above).
>> Fixing #2 actually requires making forwarding decision based on src
>> and dst (which is not happening now).
>>
>> More data (sorry, shameless plug :))
>> https://ripe67.ripe.net/presentations/288-Jen_RIPE67.pdf
>>
>> --
>> SY, Jen Linkova aka Furry
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>
>



-- 
SY, Jen Linkova aka Furry

From furry13@gmail.com  Thu Nov  7 15:34:08 2013
Return-Path: <furry13@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 63EA321E80E6; Thu,  7 Nov 2013 15:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, NO_RELAYS=-0.001]
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 P+EBk6XBGArb; Thu,  7 Nov 2013 15:34:07 -0800 (PST)
Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com [IPv6:2607:f8b0:400d:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 38A7021E80DB; Thu,  7 Nov 2013 15:34:03 -0800 (PST)
Received: by mail-qe0-f50.google.com with SMTP id 1so1268699qee.9 for <multiple recipients>; Thu, 07 Nov 2013 15:34:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=7O5+0IPZlfYycRXZ63fTXsoFEt1xEUP2gAkfLHf8VPY=; b=Y6hzgmkGthS0k7kFOnKk8ajQR+nlB6wdYgohljjOQBHSzYoWAkjeJKc6XUCKEVW0PL DeASkE/F9uKgqnDQ/Pol3VWfr0R7et5s6ORCD/2slckuIhGGphLbJF39HnX+9UODuFLI WpCI+oRzgXxv/RgMks6SuSm2LExaeRqP/evbF6zMT3N2zQMyLC1WDo7wW9qvFPYXWSTQ h7q82BzPzPhfBpbpUqOGqO8Kc7ra0yeiM7Od19u1WSNTmDeMbPriTu8CMP6uCtNp8sea F8bW0rk6y9xXKAw0STkrn8sf3SbHM1V1zmIniMgYlfggFaFFHUYNrX8TFq7AfWeLD3DQ HNPw==
X-Received: by 10.224.162.211 with SMTP id w19mr18623220qax.59.1383867240454;  Thu, 07 Nov 2013 15:34:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.100.195 with HTTP; Thu, 7 Nov 2013 15:33:40 -0800 (PST)
In-Reply-To: <527BE84E.2000205@gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com> <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com> <527BE84E.2000205@gmail.com>
From: Jen Linkova <furry13@gmail.com>
Date: Fri, 8 Nov 2013 00:33:40 +0100
Message-ID: <CAFU7BATOG_Y4UtpRM9hu1qH7rV8_cxo0XHghrNt0xr5WUZuhiQ@mail.gmail.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <rtgwg@ietf.org>, =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
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, 07 Nov 2013 23:34:08 -0000

On Thu, Nov 7, 2013 at 8:21 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> I suspect it's some of each. The host should, I should think, set the ho=
p limit to one on any packet that is to a link-local address, to ensure tha=
t the packet is not repeated by a broken router (apart from protocols that =
ask to have it set to 255 and have the receiving host check for that value)=
. Also, upstream network's BCP 38 implementation sounds suspect, and I'm wi=
th Jen in wondering why a router forwarded the packet in the first place.
>
> Are you sure these packets come from hosts? There is a known case
> which is a router generating ICMP reply packets that has no GUA
> configured since all its peers are link-local.

I saw packets with link-local source/GUA destination coming from hosts
and from routers (I analyzed EUI-64-based IIDs) back in 2011. Now
majority of such traffic is TCP to our services and, again, IID checks
shows that these packets are from hosts.

--=20
SY, Jen Linkova aka Furry

From tjc@ecs.soton.ac.uk  Thu Nov  7 15:47:47 2013
Return-Path: <tjc@ecs.soton.ac.uk>
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 DF1CD21F9985; Thu,  7 Nov 2013 15:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.042,  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 7h6j0aIBkAd5; Thu,  7 Nov 2013 15:47:47 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 2759821F8F61; Thu,  7 Nov 2013 15:47:42 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id rA7NleBL014483;  Thu, 7 Nov 2013 23:47:40 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk rA7NleBL014483
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1383868060; bh=aQC6ux+DdJRqGiKUSnmuyE59k7g=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=BbsJgYUKzu9ypKwZ/p1SHAXB2ApZ26UeZWX319Wz8zZIQmqMXXJ7UubrSZ5Haqt/j 1t9aj8oIj7vzuuBsBCdxHPdPKcncGjYrHr6qZQoYXAYuA6ximPccleaFJwmdv8wfD5 uGuhyQS93uwYObgm6Pxc4FWzFOdcoTLF9vmWt3cc=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id pA6Nle0959602001IS ret-id none; Thu, 07 Nov 2013 23:47:40 +0000
Received: from wireless-v6.meeting.ietf.org (wireless-v6.meeting.ietf.org [IPv6:2001:67c:370:160:4cc9:61d9:dc83:b91] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id rA7NlUKi024624 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 7 Nov 2013 23:47:33 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAFU7BATOG_Y4UtpRM9hu1qH7rV8_cxo0XHghrNt0xr5WUZuhiQ@mail.gmail.com>
Date: Thu, 7 Nov 2013 23:47:30 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|eb37ece4e1e2766b695a6c19361975e1pA6Nle03tjc|ecs.soton.ac.uk|AB436AF3-E784-494F-BB51-4683024D001D@ecs.soton.ac.uk>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com> <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com> <527BE84E.2000205@gmail.com> <CAFU7BATOG_Y4UtpRM9hu1qH7rV8_cxo0XHghrNt0xr5WUZuhiQ@mail.gmail.com> <AB436AF3-E784-494F-BB51-4683024D001D@ecs.soton.ac.uk>
To: Jen Linkova <furry13@gmail.com>
X-Mailer: Apple Mail (2.1816)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=pA6Nle095960200100; tid=pA6Nle0959602001IS; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: rA7NleBL014483
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-Mailman-Approved-At: Thu, 07 Nov 2013 15:56:32 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Routing WG <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, 07 Nov 2013 23:47:48 -0000

On 7 Nov 2013, at 23:33, Jen Linkova <furry13@gmail.com> wrote:

> On Thu, Nov 7, 2013 at 8:21 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>=20
>>> I suspect it's some of each. The host should, I should think, set =
the hop limit to one on any packet that is to a link-local address, to =
ensure that the packet is not repeated by a broken router (apart from =
protocols that ask to have it set to 255 and have the receiving host =
check for that value). Also, upstream network's BCP 38 implementation =
sounds suspect, and I'm with Jen in wondering why a router forwarded the =
packet in the first place.
>>=20
>> Are you sure these packets come from hosts? There is a known case
>> which is a router generating ICMP reply packets that has no GUA
>> configured since all its peers are link-local.
>=20
> I saw packets with link-local source/GUA destination coming from hosts
> and from routers (I analyzed EUI-64-based IIDs) back in 2011. Now
> majority of such traffic is TCP to our services and, again, IID checks
> shows that these packets are from hosts.

Any specifc clues by vendor?

Tim=

From furry13@gmail.com  Thu Nov  7 15:58:44 2013
Return-Path: <furry13@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 4FFA011E8162; Thu,  7 Nov 2013 15:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599, NO_RELAYS=-0.001]
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 wnWRlTaXTLEI; Thu,  7 Nov 2013 15:58:43 -0800 (PST)
Received: from mail-qe0-x234.google.com (mail-qe0-x234.google.com [IPv6:2607:f8b0:400d:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id D485011E80FA; Thu,  7 Nov 2013 15:58:42 -0800 (PST)
Received: by mail-qe0-f52.google.com with SMTP id w7so1279465qeb.11 for <multiple recipients>; Thu, 07 Nov 2013 15:58:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KEwxCVBSWhFI/UFuCzdI+tCoaF/MKMGbRzKZZsmsJa0=; b=kbM59qpL/vtC4xbYMHivlKPXDCQj59HuNl4N6X4cjhBwFV+4xN4srdk1leJi+AgdM/ YSLVJ0mFLvA7TWA39mMlKkzod9dQPt+C4vj1+zY+bS3e38d1zffUEF8yOTqz2dD3uaWA 98kdD0Eo4gImCqkVndXjkaX14qqVTMJ/Xqt/beCMClxuINh27OwwEy4ateFBDNF2kRAQ CFSJlogeiYbjkKgXu5/zRhCa/He6pPuZ4vD+IMkQzf00esjXasXXbOe874nj+HFWtRD6 g/xeKRHvvYL/5iOy39LfuHeFq0KhQz1nvqYT0CECdhbbrOueqSR8vgBt7JBWzVmwmqu9 gJgw==
X-Received: by 10.49.51.103 with SMTP id j7mr17380153qeo.29.1383868722296; Thu, 07 Nov 2013 15:58:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.100.195 with HTTP; Thu, 7 Nov 2013 15:58:22 -0800 (PST)
In-Reply-To: <EMEW3|eb37ece4e1e2766b695a6c19361975e1pA6Nle03tjc|ecs.soton.ac.uk|AB436AF3-E784-494F-BB51-4683024D001D@ecs.soton.ac.uk>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com> <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com> <527BE84E.2000205@gmail.com> <AB436AF3-E784-494F-BB51-4683024D001D@ecs.soton.ac.uk> <CAFU7BATOG_Y4UtpRM9hu1qH7rV8_cxo0XHghrNt0xr5WUZuhiQ@mail.gmail.com> <EMEW3|eb37ece4e1e2766b695a6c19361975e1pA6Nle03tjc|ecs.soton.ac.uk|AB436AF3-E784-494F-BB51-4683024D001D@ecs.soton.ac.uk>
From: Jen Linkova <furry13@gmail.com>
Date: Fri, 8 Nov 2013 00:58:22 +0100
Message-ID: <CAFU7BATth3PjYBv0Tyv4GqZ_9ZuuaxHqw6DW5uQ2x0EJp8UxsQ@mail.gmail.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Routing WG <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, 07 Nov 2013 23:58:44 -0000

On Fri, Nov 8, 2013 at 12:47 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>> I saw packets with link-local source/GUA destination coming from hosts
>> and from routers (I analyzed EUI-64-based IIDs) back in 2011. Now
>> majority of such traffic is TCP to our services and, again, IID checks
>> shows that these packets are from hosts.
>
> Any specifc clues by vendor?

I decided not to put any names on the slides but I identified ~20
vendors (see slide #8 at
https://ripe67.ripe.net/presentations/288-Jen_RIPE67.pdf )

P.S. One more reason for me to like EUI-64-based IID ;-))

-- 
SY, Jen Linkova aka Furry

From hermin.anggawijaya@gmail.com  Thu Nov  7 16:14:11 2013
Return-Path: <hermin.anggawijaya@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 5C41E21E808A; Thu,  7 Nov 2013 16:14:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
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 RWeyFAY4R7L1; Thu,  7 Nov 2013 16:14:10 -0800 (PST)
Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 63DE421E80E6; Thu,  7 Nov 2013 16:13:40 -0800 (PST)
Received: by mail-vc0-f170.google.com with SMTP id hv10so936156vcb.29 for <multiple recipients>; Thu, 07 Nov 2013 16:13:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=c0lBn4r1XwQnCZPjY3+GvpMytpW+sYeasZHkcDgjCLA=; b=OSFUjs5d2mPjA1MIaMHTwWwyxswGlIpMyl+Yz/Jxe4aZlEAfMUhU8r4pE4joeEYcun DLZw79qyNgAqPRk5tfuC8NwUTcu4zwfJLINZlasXkjLcb+OkZI/gcB+sMXm4eO7ookvC xM9I6iDPG6bEA7paQtf5rxhmRshQIBhpGnU1/eivk7G9eaM33kjo+S+Kqerzk2JxorI2 8kAQadVEIWh3cyOxJC1gj190T6EtPR/00/WykzM3s1IUVqO4w6PhLOV+4fqylMuvx3Lm TvyM3nVn7CWMOzZ0aQNsuLin9sM/x0FTa5rEDSf2hLXa7uMJuGVeqW6G2hkXaizPM3eh rmmg==
MIME-Version: 1.0
X-Received: by 10.58.210.66 with SMTP id ms2mr9091736vec.10.1383869619794; Thu, 07 Nov 2013 16:13:39 -0800 (PST)
Received: by 10.58.188.72 with HTTP; Thu, 7 Nov 2013 16:13:39 -0800 (PST)
In-Reply-To: <CAFU7BAT0GWeaJq8h_03PjJRtHupSWSFVLVXJ-FRjpti-7W+aWg@mail.gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJgsEzVmg5hGwsgVFDKrzbmrBnKBOZ1oAXRp-K0ovtPhwENcNw@mail.gmail.com> <CAFU7BAT0GWeaJq8h_03PjJRtHupSWSFVLVXJ-FRjpti-7W+aWg@mail.gmail.com>
Date: Thu, 7 Nov 2013 16:13:39 -0800
Message-ID: <CAJgsEzU3-p3Osr53gYEmkL=agSfFTnFDQHvPM3dnfM20fvHckA@mail.gmail.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
From: Hermin Anggawijaya <hermin.anggawijaya@gmail.com>
To: Jen Linkova <furry13@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd6ae8c1a789604ea9f4126
X-Mailman-Approved-At: Thu, 07 Nov 2013 16:17:16 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <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, 08 Nov 2013 00:14:11 -0000

--047d7bd6ae8c1a789604ea9f4126
Content-Type: text/plain; charset=ISO-8859-1

<hermin.anggawijaya@gmail.com> wrote:
>> I'm seeing plenty of packets from link-local sources to global
>> destinations
>> .....
>
>> 2) routers on the Internet do forward such packets (violating the rule
>> mentioned above).
>> Fixing #2 actually requires making forwarding decision based on src
>> and dst (which is not happening now).
>
> To fix the above issue, wouldn't address scope checking be enough, rather
> than the [src,dst] based routing
> discussed ?

> My point is that to do verify the scope, the router need to check
> *source* address while making forwarding decision.
> It looks like it is not happening now but it might get changed by
> [src, dst] based routing.

scope checking does not need to look up any fib though whereas [src,dst]
forwarding does. I think scope checking feature is standard even on
switching silicons *today*.

But I think I understand what you are trying to say, we just have different
interpretation of the phrase [src,dst] forwarding. Thanks.




On Thu, Nov 7, 2013 at 3:27 PM, Jen Linkova <furry13@gmail.com> wrote:

> On Thu, Nov 7, 2013 at 7:40 PM, Hermin Anggawijaya
> <hermin.anggawijaya@gmail.com> wrote:
> >> I'm seeing plenty of packets from link-local sources to global
> >> destinations
> >> .....
> >
> >> 2) routers on the Internet do forward such packets (violating the rule
> >> mentioned above).
> >> Fixing #2 actually requires making forwarding decision based on src
> >> and dst (which is not happening now).
> >
> > To fix the above issue, wouldn't address scope checking be enough, rather
> > than the [src,dst] based routing
> > discussed ?
>
> My point is that to do verify the scope, the router need to check
> *source* address while making forwarding decision.
> It looks like it is not happening now but it might get changed by
> [src, dst] based routing.
>
> > On Thu, Nov 7, 2013 at 8:58 AM, Jen Linkova <furry13@gmail.com> wrote:
> >>
> >> On Thu, Nov 7, 2013 at 5:45 PM, Fred Baker (fred) <fred@cisco.com>
> wrote:
> >> > Examples of use cases are generally around multi-prefix campus
> networks.
> >> > There is a security use case that could be of value; at IETF 87,
> George
> >> > Michaelson of APNIC reported on ULAs seen in his darknet. The short
> report
> >> > is that he sees a fair bit of traffic with a ULA source address on the
> >> > backbone. An interesting potential use of source/destination routing
> would
> >> > counter that, and perhaps mitigate the need for ISP BCP 38 if
> generally
> >> > deployed; in a case where a network is using a ULA and a global prefix
> >> > (e.g., is not multihomed but has two prefixes, one of which is
> intended to
> >> > only be used within its network), the default route to the network
> egress
> >> > would use the global prefix as a source, and as a result traffic sent
> >> > outside the network with a ULA source prefix would in effect have no
> route.
> >> > The network could literally only emit traffic from its correct prefix.
> >>
> >> Looks like we (finally) have a chance to enforce the requirement from
> >> RFC4007, Section9:
> >>
> >> "If transmitting the packet on the chosen next-hop interface
> >> would cause the packet to leave the zone of the source
> >> address, i.e.,
> >> cross a zone boundary of the scope of the
> >> source address, then the packet is discarded. "
> >>
> >> I'm seeing plenty of packets from link-local sources to global
> >> destinations which means that:
> >> 1) there are hosts with broken default address selection
> >> AND
> >> 2) routers on the Internet do forward such packets (violating the rule
> >> mentioned above).
> >> Fixing #2 actually requires making forwarding decision based on src
> >> and dst (which is not happening now).
> >>
> >> More data (sorry, shameless plug :))
> >> https://ripe67.ripe.net/presentations/288-Jen_RIPE67.pdf
> >>
> >> --
> >> SY, Jen Linkova aka Furry
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> >
> >
>
>
>
> --
> SY, Jen Linkova aka Furry
>

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

<div dir=3D"ltr"><div>&lt;<a href=3D"mailto:hermin.anggawijaya@gmail.com">h=
ermin.anggawijaya@gmail.com</a>&gt; wrote:<br>
&gt;&gt; I&#39;m seeing plenty of packets from link-local sources to global=
<br>
&gt;&gt; destinations<br>
&gt;&gt; .....<br>
&gt;<br>
&gt;&gt; 2) routers on the Internet do forward such packets (violating the =
rule<br>
&gt;&gt; mentioned above).<br>
&gt;&gt; Fixing #2 actually requires making forwarding decision based on sr=
c<br>
&gt;&gt; and dst (which is not happening now).<br>
&gt;<br>
&gt; To fix the above issue, wouldn&#39;t address scope checking be enough,=
 rather<br>
&gt; than the [src,dst] based routing<br>
&gt; discussed ?<br>
<br>
&gt; My point is that to do verify the scope, the router need to check<br>
&gt; *source* address while making forwarding decision.<br>
&gt; It looks like it is not happening now but it might get changed by<br>
&gt; [src, dst] based routing.<br><br></div>scope checking does not need to=
 look up any fib though whereas [src,dst] forwarding does. I think scope ch=
ecking feature is standard even on switching silicons *today*.<br><br>
But I think I understand what you are trying to say, we just have different=
 interpretation of the phrase [src,dst] forwarding. Thanks.<br><br><br></di=
v><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Nov=
 7, 2013 at 3:27 PM, Jen Linkova <span dir=3D"ltr">&lt;<a href=3D"mailto:fu=
rry13@gmail.com" target=3D"_blank">furry13@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"><div class=3D"im">On Thu, Nov 7, 2013 at 7:4=
0 PM, Hermin Anggawijaya<br>
&lt;<a href=3D"mailto:hermin.anggawijaya@gmail.com">hermin.anggawijaya@gmai=
l.com</a>&gt; wrote:<br>
&gt;&gt; I&#39;m seeing plenty of packets from link-local sources to global=
<br>
&gt;&gt; destinations<br>
&gt;&gt; .....<br>
&gt;<br>
&gt;&gt; 2) routers on the Internet do forward such packets (violating the =
rule<br>
&gt;&gt; mentioned above).<br>
&gt;&gt; Fixing #2 actually requires making forwarding decision based on sr=
c<br>
&gt;&gt; and dst (which is not happening now).<br>
&gt;<br>
&gt; To fix the above issue, wouldn&#39;t address scope checking be enough,=
 rather<br>
&gt; than the [src,dst] based routing<br>
&gt; discussed ?<br>
<br>
</div>My point is that to do verify the scope, the router need to check<br>
*source* address while making forwarding decision.<br>
It looks like it is not happening now but it might get changed by<br>
[src, dst] based routing.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On Thu, Nov 7, 2013 at 8:58 AM, Jen Linkova &lt;<a href=3D"mailto:furr=
y13@gmail.com">furry13@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; On Thu, Nov 7, 2013 at 5:45 PM, Fred Baker (fred) &lt;<a href=3D"m=
ailto:fred@cisco.com">fred@cisco.com</a>&gt; wrote:<br>
&gt;&gt; &gt; Examples of use cases are generally around multi-prefix campu=
s networks.<br>
&gt;&gt; &gt; There is a security use case that could be of value; at IETF =
87, George<br>
&gt;&gt; &gt; Michaelson of APNIC reported on ULAs seen in his darknet. The=
 short report<br>
&gt;&gt; &gt; is that he sees a fair bit of traffic with a ULA source addre=
ss on the<br>
&gt;&gt; &gt; backbone. An interesting potential use of source/destination =
routing would<br>
&gt;&gt; &gt; counter that, and perhaps mitigate the need for ISP BCP 38 if=
 generally<br>
&gt;&gt; &gt; deployed; in a case where a network is using a ULA and a glob=
al prefix<br>
&gt;&gt; &gt; (e.g., is not multihomed but has two prefixes, one of which i=
s intended to<br>
&gt;&gt; &gt; only be used within its network), the default route to the ne=
twork egress<br>
&gt;&gt; &gt; would use the global prefix as a source, and as a result traf=
fic sent<br>
&gt;&gt; &gt; outside the network with a ULA source prefix would in effect =
have no route.<br>
&gt;&gt; &gt; The network could literally only emit traffic from its correc=
t prefix.<br>
&gt;&gt;<br>
&gt;&gt; Looks like we (finally) have a chance to enforce the requirement f=
rom<br>
&gt;&gt; RFC4007, Section9:<br>
&gt;&gt;<br>
&gt;&gt; &quot;If transmitting the packet on the chosen next-hop interface<=
br>
&gt;&gt; would cause the packet to leave the zone of the source<br>
&gt;&gt; address, i.e.,<br>
&gt;&gt; cross a zone boundary of the scope of the<br>
&gt;&gt; source address, then the packet is discarded. &quot;<br>
&gt;&gt;<br>
&gt;&gt; I&#39;m seeing plenty of packets from link-local sources to global=
<br>
&gt;&gt; destinations which means that:<br>
&gt;&gt; 1) there are hosts with broken default address selection<br>
&gt;&gt; AND<br>
&gt;&gt; 2) routers on the Internet do forward such packets (violating the =
rule<br>
&gt;&gt; mentioned above).<br>
&gt;&gt; Fixing #2 actually requires making forwarding decision based on sr=
c<br>
&gt;&gt; and dst (which is not happening now).<br>
&gt;&gt;<br>
&gt;&gt; More data (sorry, shameless plug :))<br>
&gt;&gt; <a href=3D"https://ripe67.ripe.net/presentations/288-Jen_RIPE67.pd=
f" target=3D"_blank">https://ripe67.ripe.net/presentations/288-Jen_RIPE67.p=
df</a><br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; SY, Jen Linkova aka Furry<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; v6ops mailing list<br>
&gt;&gt; <a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
&gt;<br>
&gt;<br>
<br>
<br>
<br>
--<br>
SY, Jen Linkova aka Furry<br>
</div></div></blockquote></div><br></div>

--047d7bd6ae8c1a789604ea9f4126--

From yangshu1988@gmail.com  Fri Nov  8 04:51:47 2013
Return-Path: <yangshu1988@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 17E4511E80EE; Fri,  8 Nov 2013 04:51:47 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 zmr2sIJ7Asjf; Fri,  8 Nov 2013 04:51:46 -0800 (PST)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id C600621F9F3D; Fri,  8 Nov 2013 04:51:45 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id ez12so2109967wid.17 for <multiple recipients>; Fri, 08 Nov 2013 04:51:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=w9+Jksh257ryDWT6JsZcR2sdObTNDhDJiMxLs2U5ZfQ=; b=f89r88L2kWPUJuyeJ8dFIDEuexwSsZnsgMEujWgT5vsb3tryyLnpKzy+4vP/PluMH7 +hWcL2sO317uzW9+MQcMIEGz8c8qJqlEgk9Ew0B7giGhJThxPgRtUckEKMMSUXyOJ/l/ NnExU+m72S0CEsA5WB+ntFPz0JX8OlTyctath451/Opz4eStVT9+lXg3HeDtF2Y6eQTI DkvYpsw1XeiDtRqfxuz5tv9yymxvnnrGSTJErgDttzzEYwZOjmA1orbTqV8XTlwsbUWo w5FHBOL53sXFVGWn2x7IWxmbq10fcI9XSlOep3NfsCgaWaVBS/lFxDqlMTexLSYKSAV3 lR4w==
MIME-Version: 1.0
X-Received: by 10.180.37.67 with SMTP id w3mr2274557wij.56.1383915104978; Fri, 08 Nov 2013 04:51:44 -0800 (PST)
Received: by 10.194.36.196 with HTTP; Fri, 8 Nov 2013 04:51:44 -0800 (PST)
In-Reply-To: <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr>
Date: Fri, 8 Nov 2013 20:51:44 +0800
Message-ID: <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com>
Subject: Re: [homenet] Tsinghua work on source/destination routing
From: Shu Yang <yangshu1988@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=e89a8f502cfa3b4f0f04eaa9d83b
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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, 08 Nov 2013 12:51:47 -0000

--e89a8f502cfa3b4f0f04eaa9d83b
Content-Type: text/plain; charset=ISO-8859-1

> Excellent.  Could we please have a look at the source code ?  (It was
> already promised in Berlin, if memory serves.)
We will make it public after testing it in live networks (we are still
implementing the Click code, and combining quagga and click
together).

If you want, I can send you the current version privately at this moment.

Shu Yang
Tsinghua University

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

<div dir=3D"ltr">&gt; Excellent. =A0Could we please have a look at the sour=
ce code ? =A0(It was<br>&gt; already promised in Berlin, if memory serves.)=
<br><div>We will make it public after testing it in live networks (we are s=
till</div>
<div>implementing the Click code, and combining quagga and click</div><div>=
together).</div><div><br></div><div>If you want, I can send you the current=
 version privately at this moment.</div><div><br></div><div>Shu Yang</div>
<div>Tsinghua University</div></div>

--e89a8f502cfa3b4f0f04eaa9d83b--

From jinmei.tatuya@gmail.com  Thu Nov  7 17:57:40 2013
Return-Path: <jinmei.tatuya@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 DC56321E812A; Thu,  7 Nov 2013 17:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 dLzrVN6gANzW; Thu,  7 Nov 2013 17:57:40 -0800 (PST)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 05ADB11E8202; Thu,  7 Nov 2013 17:57:39 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id p61so1350492wes.19 for <multiple recipients>; Thu, 07 Nov 2013 17:57:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zgVjAlROUt9KGVRQGhItVS8zPr5ljZRGBTbib1QjHiM=; b=rJHer06FyrS1ewUomJvoHJQnYcn5vTvLAFBMC17BKQF6wuoE02pUY8KXTM8NBjc8jK Usf5oWwelDe+4jfqU0JBl3ZUbc8LPtOOBbfGVow9For3wPZ1P3Uq4Jj9ReJAqiXmDezU 31ZEtlUq2GAp/ngFSRjTZoJ6T7pX+eT6c2DjzI3kAENbNyLt5D+d/wbYaxC7PnBsULNU /CREWzcxRgYXlzp6MHyWDIjbd5PQApe0WRXdKnqhttmztuYMFY2q1iqAVhefQdgF04Yl NHLcmlVgbTVoFooetx1TIE+BXLLMvjtvDzfIuUV0Nr6c2r+wOCFzwGzLKAOLQHjrMuzl LEWQ==
MIME-Version: 1.0
X-Received: by 10.180.208.49 with SMTP id mb17mr346685wic.64.1383875859119; Thu, 07 Nov 2013 17:57:39 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Thu, 7 Nov 2013 17:57:39 -0800 (PST)
In-Reply-To: <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com> <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com>
Date: Thu, 7 Nov 2013 17:57:39 -0800
X-Google-Sender-Auth: IRpez4kP4GKGXxyaI24a-YCdkQY
Message-ID: <CAJE_bqdJkwiYRrQGAtuhkaPOMFwPM=CHQbQXZBH7_swAKPJ6xA@mail.gmail.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Fri, 08 Nov 2013 10:03:50 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <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, 08 Nov 2013 01:57:41 -0000

At Thu, 7 Nov 2013 18:56:12 +0000,
"Fred Baker (fred)" <fred@cisco.com> wrote:

> >> I'm seeing plenty of packets from link-local sources to global
> >> destinations which means that:
> >> 1) there are hosts with broken default address selection
> >> AND
> >
> > (Probably an off-topic in this context but) this is not necessarily
> > accurate.  If a host only has a link-local address but somehow knows
> > the interface to send packets to a global destination, it would be
> > able to send packets with source being link-local and destination
> > being global, and validly (not breaking RFC 6724) so.  I believe it's
> > more likely to be a broken network configuration than a broken host
> > implementation.
>
> I suspect it's some of each. The host should, I should think, set
> the hop limit to one on any packet that is to a link-local address,

To make it sure: this is about the case of packets "from" a link-local
address.

> to ensure that the packet is not repeated by a broken router (apart
> from protocols that ask to have it set to 255 and have the receiving
> host check for that value). Also, upstream network's BCP 38

I'd note, from purely architectural point of view, that it's totally
valid a packet that has a link-local address is forwarded, as long as
the packet remains in the originating link zone.  That would be a very
unlikely case in practice, but can still happen, e.g., when a host
sends all packets to a router, expecting the router to forward it back
to the same link toward the destination.  RFC 4007 mentions such
cases.

That said, I see it should be a very rare case except for
implementation or operational errors.  So it may make sense to
introduce something similar to the IPV6_MULTICAST_HOPS socket option
defined in RFC 3493 and define its default value to be 1 for narrower
scopes.

> implementation sounds suspect, and I'm with Jen in wondering why a
> router forwarded the packet in the first place.

It's not surprising to me since the source address is not needed as
long as routing decision is only made based on the destination
address.  I noticed one popular router vendor didn't implement this
restriction of RFC 4007 correctly many years ago and even reported it
to the vendor, but (assuming it's still not fixed) just being "non
compliant" is probably not convincing enough for them to introduce
additional overhead in their forwarding logic.

--
JINMEI, Tatuya

From owen@delong.com  Thu Nov  7 18:44:28 2013
Return-Path: <owen@delong.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 1D90521F9CA5; Thu,  7 Nov 2013 18:44:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
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 EbA25ofl3BjO; Thu,  7 Nov 2013 18:44:21 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 33AEE11E815E; Thu,  7 Nov 2013 18:44:04 -0800 (PST)
Received: from [172.20.72.215] (63-235-172-7.dia.static.qwest.net [63.235.172.7]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id rA82g25L013739 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 7 Nov 2013 18:42:08 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com rA82g25L013739
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1383878531; bh=/hcgWLX/FyNGeFMpZeF8Wf+gEgo=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Message-Id:References:To; b=z3P5whR+oUL0EpAWKigfrNXryd64FqdSgwPD0dpLGUzMSqCNy6r1wzlG0QrMHQraZ Pq1Wp/2ApWgeHboCjup5Cr+dNlxcG6xI7jF+74HJO43fLGXzKjvSy3FSXRR3EEAmKN 5WRZNQv59sZrpVG+9oyDpdV/u52pyhQLwkqTrUXM=
Content-Type: multipart/alternative; boundary="Apple-Mail=_83FE3C79-55CD-4723-AE10-8E286E15210D"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAJE_bqdJkwiYRrQGAtuhkaPOMFwPM=CHQbQXZBH7_swAKPJ6xA@mail.gmail.com>
Date: Thu, 7 Nov 2013 18:42:02 -0800
Message-Id: <3447189B-394A-429E-A24B-29E6791B9109@delong.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com> <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com> <CAJE_bqdJkwiYRrQGAtuhkaPOMFwPM=CHQbQXZBH7_swAKPJ6xA@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Thu, 07 Nov 2013 18:42:11 -0800 (PST)
X-Mailman-Approved-At: Fri, 08 Nov 2013 10:03:50 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <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, 08 Nov 2013 02:44:28 -0000

--Apple-Mail=_83FE3C79-55CD-4723-AE10-8E286E15210D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

>> to ensure that the packet is not repeated by a broken router (apart
>> from protocols that ask to have it set to 255 and have the receiving
>> host check for that value). Also, upstream network's BCP 38
>=20
> I'd note, from purely architectural point of view, that it's totally
> valid a packet that has a link-local address is forwarded, as long as
> the packet remains in the originating link zone.  That would be a very
> unlikely case in practice, but can still happen, e.g., when a host
> sends all packets to a router, expecting the router to forward it back
> to the same link toward the destination.  RFC 4007 mentions such
> cases.

That is not correct=85

RFC 4291 says:

2.5.6.  Link-Local IPv6 Unicast Addresses

   Link-Local addresses are for use on a single link.  Link-Local
   addresses have the following format:

   |   10     |
   |  bits    |         54 bits         |          64 bits           |
   +----------+-------------------------+----------------------------+
   |1111111010|           0             |       interface ID         |
   +----------+-------------------------+----------------------------+

   Link-Local addresses are designed to be used for addressing on a
   single link for purposes such as automatic address configuration,
   neighbor discovery, or when no routers are present.

   Routers must not forward any packets with Link-Local source or
   destination addresses to other links.

It is quite clear that a packet with a link-local address in either =
field MUST not be forwarded.

>> implementation sounds suspect, and I'm with Jen in wondering why a
>> router forwarded the packet in the first place.
>=20
> It's not surprising to me since the source address is not needed as
> long as routing decision is only made based on the destination
> address.  I noticed one popular router vendor didn't implement this
> restriction of RFC 4007 correctly many years ago and even reported it
> to the vendor, but (assuming it's still not fixed) just being "non
> compliant" is probably not convincing enough for them to introduce
> additional overhead in their forwarding logic.

It's surprising to me and it means that the router is, by definition, =
not compliant with RFC 4291, ergo, the router is broken.

Owen


--Apple-Mail=_83FE3C79-55CD-4723-AE10-8E286E15210D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><blockquote type=3D"cite"><blockquote type=3D"cite">to ensure =
that the packet is not repeated by a broken router (apart<br>from =
protocols that ask to have it set to 255 and have the receiving<br>host =
check for that value). Also, upstream network's BCP =
38<br></blockquote><br>I'd note, from purely architectural point of =
view, that it's totally<br>valid a packet that has a link-local address =
is forwarded, as long as<br>the packet remains in the originating link =
zone. &nbsp;That would be a very<br>unlikely case in practice, but can =
still happen, e.g., when a host<br>sends all packets to a router, =
expecting the router to forward it back<br>to the same link toward the =
destination. &nbsp;RFC 4007 mentions =
such<br>cases.<br></blockquote><div><br></div>That is not =
correct=85</div><div><br></div><div>RFC 4291 =
says:</div><div><br></div><div><pre class=3D"newpage" style=3D"font-size: =
1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; =
"><span class=3D"h4" style=3D"line-height: 0pt; display: inline; =
font-size: 1em; font-weight: bold; "><h4 style=3D"line-height: 0pt; =
display: inline; font-size: 1em; "><a class=3D"selflink" =
name=3D"section-2.5.6" =
href=3D"http://tools.ietf.org/html/rfc4291#section-2.5.6" style=3D"color: =
black; text-decoration: none;">2.5.6</a>.  Link-Local IPv6 Unicast =
Addresses</h4></span>

   Link-Local addresses are for use on a single link.  Link-Local
   addresses have the following format:

   |   10     |
   |  bits    |         54 bits         |          64 bits           |
   +----------+-------------------------+----------------------------+
   |1111111010|           0             |       interface ID         |
   +----------+-------------------------+----------------------------+

   Link-Local addresses are designed to be used for addressing on a
   single link for purposes such as automatic address configuration,
   neighbor discovery, or when no routers are present.

   Routers must not forward any packets with Link-Local source or
   destination addresses to other links.</pre><div><br></div><div>It is =
quite clear that a packet with a link-local address in either field MUST =
not be forwarded.</div><div><br></div><blockquote =
type=3D"cite"><blockquote type=3D"cite">implementation sounds suspect, =
and I'm with Jen in wondering why a<br>router forwarded the packet in =
the first place.<br></blockquote><br>It's not surprising to me since the =
source address is not needed as<br>long as routing decision is only made =
based on the destination<br>address. &nbsp;I noticed one popular router =
vendor didn't implement this<br>restriction of RFC 4007 correctly many =
years ago and even reported it<br>to the vendor, but (assuming it's =
still not fixed) just being "non<br>compliant" is probably not =
convincing enough for them to introduce<br>additional overhead in their =
forwarding logic.<br></blockquote><div><br></div>It's surprising to me =
and it means that the router is, by definition, not compliant with RFC =
4291, ergo, the router is =
broken.</div><div><br></div><div>Owen</div><div><br></div></body></html>=

--Apple-Mail=_83FE3C79-55CD-4723-AE10-8E286E15210D--

From owen@delong.com  Thu Nov  7 18:44:31 2013
Return-Path: <owen@delong.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 7DF3711E81FA; Thu,  7 Nov 2013 18:44:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=0.225,  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 Vb293f3L-ynD; Thu,  7 Nov 2013 18:44:21 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 6C11821E80F4; Thu,  7 Nov 2013 18:44:15 -0800 (PST)
Received: from [172.20.72.215] (63-235-172-7.dia.static.qwest.net [63.235.172.7]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id rA82ct5Z013553 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 7 Nov 2013 18:38:56 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com rA82ct5Z013553
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1383878352; bh=N08vyre+erX5G3lix3bAakYdVjU=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=YajQ79gg0ct2CRuHOHM8s4VYhMnuZkN34g7fB0eh76TWG1yHDWPQYrmOfVbB4YMXn MrNxOzAT+G8nkqZl1N9/IL/UTULAy/cO9U9BQRt+z03WXmJ6KJt66Q9LbyTTHxS30w Y5AyIX9lr+ESMuo9d8S4Ztr/QttFtMmZvfpFTuGY=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAFU7BATOG_Y4UtpRM9hu1qH7rV8_cxo0XHghrNt0xr5WUZuhiQ@mail.gmail.com>
Date: Thu, 7 Nov 2013 18:38:46 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E06460D8-E347-40F3-A72E-6177C7817CB5@delong.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com> <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com> <527BE84E.2000205@gmail.com> <CAFU7BATOG_Y4UtpRM9hu1qH7rV8_cxo0XHghrNt0xr5WUZuhiQ@mail.gmail.com>
To: Jen Linkova <furry13@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Thu, 07 Nov 2013 18:39:12 -0800 (PST)
X-Mailman-Approved-At: Fri, 08 Nov 2013 10:03:50 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Routing WG <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, 08 Nov 2013 02:44:31 -0000

On Nov 7, 2013, at 3:33 PM, Jen Linkova <furry13@gmail.com> wrote:

> On Thu, Nov 7, 2013 at 8:21 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>=20
>>> I suspect it's some of each. The host should, I should think, set =
the hop limit to one on any packet that is to a link-local address, to =
ensure that the packet is not repeated by a broken router (apart from =
protocols that ask to have it set to 255 and have the receiving host =
check for that value). Also, upstream network's BCP 38 implementation =
sounds suspect, and I'm with Jen in wondering why a router forwarded the =
packet in the first place.
>>=20
>> Are you sure these packets come from hosts? There is a known case
>> which is a router generating ICMP reply packets that has no GUA
>> configured since all its peers are link-local.
>=20
> I saw packets with link-local source/GUA destination coming from hosts
> and from routers (I analyzed EUI-64-based IIDs) back in 2011. Now
> majority of such traffic is TCP to our services and, again, IID checks
> shows that these packets are from hosts.
>=20

It is not wrong for a node {host, router} to emit a packet with a =
link-local source and a destination in another scope.

It is wrong for a router to forward a packet containing a link-local =
scope address (source or destination). It is wrong to do so regardless =
of whether the outgoing link is the same as the incoming link or not.

Owen


From jinmei.tatuya@gmail.com  Thu Nov  7 23:17:38 2013
Return-Path: <jinmei.tatuya@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 DD3F811E8218; Thu,  7 Nov 2013 23:17:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 IX+L4pGE9rdE; Thu,  7 Nov 2013 23:17:38 -0800 (PST)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id C3AE221E80E0; Thu,  7 Nov 2013 23:17:36 -0800 (PST)
Received: by mail-we0-f181.google.com with SMTP id t60so1524537wes.26 for <multiple recipients>; Thu, 07 Nov 2013 23:17:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=GxIZfApjoyV+nJQNbnF4vln2jUUyesbBED7DhS9/xTU=; b=YG/a/a9ZXNxMiQY6bFIDwLtp/Bu1sDJgUs6DVX/Sy5fkxK5iqYP+BtuDvXAG/IIsBU YzlQs8j0GCs/MM98vRMMFokyeu1botPjUsBKmD/XqcUH6h5ZuDG9u0aSJeIh3l3/JmXL kgPzMDzUvmaeDmOFf8sb79Fy6A7OfSGrY2QRvaM7RB5+uKX/fLfXy+ENOGJ/UONt43+N ERa2DVL0OXMnR2m1YrVi7Xzo0V1yqHXhNUbLs9ZUHwEMN+buC0fKSOt4J87o1jf5t/kP hfcZJOIjjHYBX2ucdvON2/lRblHhFKc7+zRF5I6ocepA/y/SfI1wQLlP+re+kLFiUAVM 6w4g==
MIME-Version: 1.0
X-Received: by 10.180.77.19 with SMTP id o19mr1182464wiw.34.1383895055864; Thu, 07 Nov 2013 23:17:35 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Thu, 7 Nov 2013 23:17:35 -0800 (PST)
In-Reply-To: <E06460D8-E347-40F3-A72E-6177C7817CB5@delong.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com> <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com> <527BE84E.2000205@gmail.com> <CAFU7BATOG_Y4UtpRM9hu1qH7rV8_cxo0XHghrNt0xr5WUZuhiQ@mail.gmail.com> <E06460D8-E347-40F3-A72E-6177C7817CB5@delong.com>
Date: Thu, 7 Nov 2013 23:17:35 -0800
X-Google-Sender-Auth: rHXXLQBy-ng_y7xB_-RYYVzoPgU
Message-ID: <CAJE_bqdiPk=9J8zrh9mds=3wA32GBMdT9w0_4dHcR6Lnsn=CkA@mail.gmail.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
From: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
To: Owen DeLong <owen@delong.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 08 Nov 2013 10:03:50 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <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, 08 Nov 2013 07:17:39 -0000

At Thu, 7 Nov 2013 18:42:02 -0800,
Owen DeLong <owen@delong.com> wrote:

> > I'd note, from purely architectural point of view, that it's totally
> > valid a packet that has a link-local address is forwarded, as long as
> > the packet remains in the originating link zone. [...]
>
> That is not correct=85
>
> RFC 4291 says:
[...]
>    Routers must not forward any packets with Link-Local source or
>    destination addresses to other links.
>
> It is quite clear that a packet with a link-local address in either
> field MUST not be forwarded.

Don't forget the "to other links" part.  This make it valid, e.g.,
that a router forwards a packet with a link-local source address back
to the receiving link.  A stubborn person might still argue that
"other" can include the receiving link itself, and in a sense I admit
it might confuse readers.  In fact, such confusion is one of the
things RFC 4007 tried to clarify.  At the very least, I'm 100% sure
this is what Steve (Deering) intended when he co-authored the IPv6
addressing architecture spec and what he tried to clarify in RFC 4007
as a co-author of it.

> >> implementation sounds suspect, and I'm with Jen in wondering why a
> >> router forwarded the packet in the first place.
> >
> > It's not surprising to me since the source address is not needed as
> > long as routing decision is only made based on the destination
> > address.  I noticed one popular router vendor didn't implement this
> > restriction of RFC 4007 correctly many years ago and even reported it
> > to the vendor, but (assuming it's still not fixed) just being "non
> > compliant" is probably not convincing enough for them to introduce
> > additional overhead in their forwarding logic.
>
> It's surprising to me and it means that the router is, by definition, not=
 compliant with RFC 4291, ergo, the router is broken.

Of course it's broken.  But the existence of broken implementations is
not uncommon in general, so simply because something is broken doesn't
mean (to me) it's surprising there's such a thing.  And, in this
particular case, I can even see the incentive of being broken, so it's
not surprising to me at all.  But "surprising" is a subjective concept
anyway, so it's not surprising different people have different sense
of it:-)

--
JINMEI, Tatuya

From jch@pps.univ-paris-diderot.fr  Fri Nov  8 04:24:05 2013
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 52F8A11E8177; Fri,  8 Nov 2013 04:24:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 dPxEdgWx+ekd; Fri,  8 Nov 2013 04:24:01 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by ietfa.amsl.com (Postfix) with ESMTP id 503A111E8122; Fri,  8 Nov 2013 04:24:00 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id rA8CNuoF008925; Fri, 8 Nov 2013 13:23:56 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 9B2D45AD5F; Fri,  8 Nov 2013 13:23:56 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id lB5yMqrCzFxY; Fri,  8 Nov 2013 13:23:55 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0E5FB5AD5E; Fri,  8 Nov 2013 13:23:54 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.pps.univ-paris-diderot.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.80) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1Vel6Q-0008Om-Lx; Fri, 08 Nov 2013 13:23:54 +0100
Date: Fri, 08 Nov 2013 13:23:54 +0100
Message-ID: <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: [homenet] Tsinghua work on source/destination routing
In-Reply-To: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 08 Nov 2013 13:23:56 +0100 (CET)
X-Miltered: at korolev with ID 527CD7DC.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 527CD7DC.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 527CD7DC.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-Mailman-Approved-At: Fri, 08 Nov 2013 10:03:50 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, Routing WG <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, 08 Nov 2013 12:24:05 -0000

> The context is:

A pity you didn't cite any of the previous work on the subject:

  http://tools.ietf.org/html/draft-troan-homenet-sadr-01  

  https://github.com/fingon/hnet-core

  http://tools.ietf.org/html/draft-boutier-homenet-source-specific-routing
  http://git.wifi.pps.univ-paris-diderot.fr/?p=babels.git  
  
> I had breakfast this morning with Shu Yang, who has been writing
> Quagga code for several years in the course of his PHd.  [...]  and
> has now implemented (if I understand him correctly)
> draft-ietf-ospf-ospfv3-lsa-extend and
> draft-baker-ipv6-ospf-dst-src-routing.

Excellent.  Could we please have a look at the source code ?  (It was
already promised in Berlin, if memory serves.)

Regards,

-- Juliusz

From jch@pps.univ-paris-diderot.fr  Sun Nov 10 05:37:31 2013
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 6A80711E8190; Sun, 10 Nov 2013 05:37:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.505
X-Spam-Level: 
X-Spam-Status: No, score=-1.505 tagged_above=-999 required=5 tests=[AWL=-0.745, BAYES_05=-1.11, HELO_EQ_FR=0.35]
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 PQeQEEH1gsbp; Sun, 10 Nov 2013 05:37:19 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by ietfa.amsl.com (Postfix) with ESMTP id 0333D21F9E4F; Sun, 10 Nov 2013 05:37:07 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id rAADb3SM032731; Sun, 10 Nov 2013 14:37:03 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 0B0255AE60; Sun, 10 Nov 2013 14:37:03 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id uQAuzS8TC55g; Sun, 10 Nov 2013 14:37:02 +0100 (CET)
Received: from ijon.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 1245A5AE5C; Sun, 10 Nov 2013 14:37:01 +0100 (CET)
Received: from localhost ([127.0.0.1] helo=ijon.pps.jussieu.fr) by ijon.pps.jussieu.fr with esmtp (Exim 4.80) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1VfVCI-0002DH-Ln; Sun, 10 Nov 2013 14:37:02 +0100
Date: Sun, 10 Nov 2013 14:37:02 +0100
Message-ID: <87mwlcnzsx.wl%jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Shu Yang <yangshu1988@gmail.com>
Subject: Re: [homenet] Tsinghua work on source/destination routing
In-Reply-To: <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr> <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 10 Nov 2013 14:37:03 +0100 (CET)
X-Miltered: at korolev with ID 527F8BFF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 527F8BFF.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 527F8BFF.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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: Sun, 10 Nov 2013 13:37:34 -0000

> > Excellent.  Could we please have a look at the source code ?  (It was
> > already promised in Berlin, if memory serves.)

> We will make it public after testing it in live networks

Ah, I see.

> If you want, I can send you the current version privately at this moment.

I'd much prefer a public repository, something I can discuss freely
with people (and eventually cite) without worrying whether I'm disclosing
anything confidential.

-- Juliusz

From hermin.anggawijaya@gmail.com  Sun Nov 10 10:09:30 2013
Return-Path: <hermin.anggawijaya@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 86FD311E8146; Sun, 10 Nov 2013 10:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.932
X-Spam-Level: 
X-Spam-Status: No, score=-1.932 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
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 wHS5L7WFejO3; Sun, 10 Nov 2013 10:09:29 -0800 (PST)
Received: from mail-vb0-x22e.google.com (mail-vb0-x22e.google.com [IPv6:2607:f8b0:400c:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 3191A11E80E6; Sun, 10 Nov 2013 10:09:29 -0800 (PST)
Received: by mail-vb0-f46.google.com with SMTP id 10so2646151vbe.33 for <multiple recipients>; Sun, 10 Nov 2013 10:09:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zt2DnudiU+2cmNXFhvBjYwTX1+AL8PDS0Z1/nyUgE6k=; b=VP9u2GiBDteepBwT3GgkDjxd/5X66Nla2wpLpTKPaQsp2tTNq2u8ukfBoAcTT5vQ5Q 9g5L/Zem5QOjkEAiCehecKiFln2CfHHXA7eoWxQ/Qi00Wi3WyP82yoIoHRd60KG5XDm/ TgrQgYiNOf2qgN5g3y1k3HT6S845cfGAzMxx4xSjeWCNk/6eXUwGlCn+vq8Hvnsh3404 so1vZir4A4/xal8DReUbP5zZq+faVkBKsCXM0hQ8EMfMKMDlDCLlecIHZkJPAyik2GJr +S1iy6VGtZSOBxjbqGIN+1fOl6d1sD/XWK/RCFZ1pASiVGfjC4R/en6dWqkvOIG3mlT9 MWUA==
MIME-Version: 1.0
X-Received: by 10.52.111.161 with SMTP id ij1mr76560vdb.33.1384106968582; Sun, 10 Nov 2013 10:09:28 -0800 (PST)
Received: by 10.58.188.72 with HTTP; Sun, 10 Nov 2013 10:09:28 -0800 (PST)
In-Reply-To: <CAGnRvuqTN2TorVySF8ne=d+_tTk9w60eS+xRqmAm9+GeBeXx4w@mail.gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr> <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com> <87mwlcnzsx.wl%jch@pps.univ-paris-diderot.fr> <CAGnRvuqTN2TorVySF8ne=d+_tTk9w60eS+xRqmAm9+GeBeXx4w@mail.gmail.com>
Date: Sun, 10 Nov 2013 10:09:28 -0800
Message-ID: <CAJgsEzUw4STcUeZ01T2O_XmcgOZymyz45gcWdVkiVxSmZuQ+YQ@mail.gmail.com>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
From: Hermin Anggawijaya <hermin.anggawijaya@gmail.com>
To: Shu Yang <yangshu1988@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec54863463192eb04ead68457
Cc: "ospf@ietf.org" <ospf@ietf.org>, "v6ops@ietf.org WG" <v6ops@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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: Sun, 10 Nov 2013 18:09:30 -0000

--bcaec54863463192eb04ead68457
Content-Type: text/plain; charset=ISO-8859-1

I too would be interested in seeing the code if it's available in a public
repo.

cheers

Angga


On Sun, Nov 10, 2013 at 6:24 AM, Henning Rogge <hrogge@googlemail.com>wrote:

> On Sun, Nov 10, 2013 at 2:37 PM, Juliusz Chroboczek
> <jch@pps.univ-paris-diderot.fr> wrote:
> >> > Excellent.  Could we please have a look at the source code ?  (It was
> >> > already promised in Berlin, if memory serves.)
> >>
> >> If you want, I can send you the current version privately at this
> moment.
> >
> > I'd much prefer a public repository, something I can discuss freely
> > with people (and eventually cite) without worrying whether I'm disclosing
> > anything confidential.
>
> I agree with Juliusz, a public repository would be much better, even
> if it only contains "in development" code.
>
> If the code will be open sourced in the end anyways I don't see any
> drawbacks.
>
> Henning Rogge
>
> --
> We began as wanderers, and we are wanderers still. We have lingered
> long enough on the shores of the cosmic ocean. We are ready at last to
> set sail for the stars - Carl Sagan
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

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

<div dir=3D"ltr"><div><div>I too would be interested in seeing the code if =
it&#39;s available in a public repo.<br><br></div>cheers<br><br></div>Angga=
<br><div><div><div><div><div class=3D"gmail_extra"><br><br><div class=3D"gm=
ail_quote">
On Sun, Nov 10, 2013 at 6:24 AM, Henning Rogge <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:hrogge@googlemail.com" target=3D"_blank">hrogge@googlemail.com<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">On Sun, Nov 10, 2013 at 2:37 PM, Juliusz Chroboczek<br>
&lt;<a href=3D"mailto:jch@pps.univ-paris-diderot.fr">jch@pps.univ-paris-did=
erot.fr</a>&gt; wrote:<br>
&gt;&gt; &gt; Excellent. =A0Could we please have a look at the source code =
? =A0(It was<br>
&gt;&gt; &gt; already promised in Berlin, if memory serves.)<br>
&gt;&gt;<br>
</div><div class=3D"im">&gt;&gt; If you want, I can send you the current ve=
rsion privately at this moment.<br>
&gt;<br>
&gt; I&#39;d much prefer a public repository, something I can discuss freel=
y<br>
&gt; with people (and eventually cite) without worrying whether I&#39;m dis=
closing<br>
&gt; anything confidential.<br>
<br>
</div>I agree with Juliusz, a public repository would be much better, even<=
br>
if it only contains &quot;in development&quot; code.<br>
<br>
If the code will be open sourced in the end anyways I don&#39;t see any dra=
wbacks.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Henning Rogge<br>
<br>
--<br>
We began as wanderers, and we are wanderers still. We have lingered<br>
long enough on the shores of the cosmic ocean. We are ready at last to<br>
set sail for the stars - Carl Sagan<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________=
__________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/v6ops</a><br>
</div></div></blockquote></div><br></div></div></div></div></div></div>

--bcaec54863463192eb04ead68457--

From yangshu1988@gmail.com  Sun Nov 10 23:06:29 2013
Return-Path: <yangshu1988@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 32B8F21E8127; Sun, 10 Nov 2013 23:06:29 -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=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001]
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 57C5UHb85BLv; Sun, 10 Nov 2013 23:06:27 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA2C21E811A; Sun, 10 Nov 2013 23:06:06 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id q59so4247042wes.11 for <multiple recipients>; Sun, 10 Nov 2013 23:06:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5hidhRXKtLkFr2S1fTOLEVwKv0AQKter4JziILQkFOc=; b=fvrB88Uwe2WO+a+bWmjBRpAoQuS1Nk656ePHi1WSOzcTfajdntNgSUQaFjx2fBPY4M UeLhIe0/fjrWHSUyIbeZ2iB9eiNgjoFwOAMEUEZpoTGxuUhPYT87WKn3InqqPcBEoX/j QZIdGfWHinwCmfYNMGamOH6+dpOQcNJ7fUZeiAikV5SkveA2FfDyk/QPK9kbBh5nlEqL SdpeJ2TtLpm554dbv7w7Rs5fSwusC5iFC3cdYxM2pONqn8JW0skgvmlPQZknZxcNjELJ wcYXqg7qrLf2crOWvugNL0dYW7Q7uSsk9z8dRrZEotSrsfQcqXouhIaidGYeYwEGU/vI gy0A==
MIME-Version: 1.0
X-Received: by 10.180.85.226 with SMTP id k2mr11178775wiz.31.1384153566060; Sun, 10 Nov 2013 23:06:06 -0800 (PST)
Received: by 10.194.36.196 with HTTP; Sun, 10 Nov 2013 23:06:05 -0800 (PST)
In-Reply-To: <CAGnRvuqTN2TorVySF8ne=d+_tTk9w60eS+xRqmAm9+GeBeXx4w@mail.gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr> <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com> <87mwlcnzsx.wl%jch@pps.univ-paris-diderot.fr> <CAGnRvuqTN2TorVySF8ne=d+_tTk9w60eS+xRqmAm9+GeBeXx4w@mail.gmail.com>
Date: Mon, 11 Nov 2013 15:06:05 +0800
Message-ID: <CAL6OX+27_SxYH5=78pA2siy3fDg4p8TupWSUj10kH5sh4Lx5Tg@mail.gmail.com>
Subject: Re: [homenet] Tsinghua work on source/destination routing
From: Shu Yang <yangshu1988@gmail.com>
To: Henning Rogge <hrogge@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, "ospf@ietf.org" <ospf@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <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, 11 Nov 2013 07:06:29 -0000

> I agree with Juliusz, a public repository would be much better, even
> if it only contains "in development" code.
>
> If the code will be open sourced in the end anyways I don't see any drawbacks.
>
> Henning Rogge

Ok, we will make it public in this week.

Shu Yang

From hrogge@googlemail.com  Sun Nov 10 06:24:37 2013
Return-Path: <hrogge@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 7016121E808F; Sun, 10 Nov 2013 06:24:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 7F69NisDODam; Sun, 10 Nov 2013 06:24:36 -0800 (PST)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 4017811E80EA; Sun, 10 Nov 2013 06:24:36 -0800 (PST)
Received: by mail-qe0-f51.google.com with SMTP id t7so454854qeb.24 for <multiple recipients>; Sun, 10 Nov 2013 06:24:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Cx2jX8ap06xyOckh1Gs6MpCl1Kg/Q9NmtMYJ6WC1Kvw=; b=hgOBrYyFlklgxdCbAuwgL9t0GCKHEdHXykBPxx54uLlbNP+EgQNKmDVHm3wTI6uhvr MGT0d2Kdhb/uXCSgDGxA6ddrjjVxOih41/B4Yql2cCBsRf3eL9QH+6/8E4AYVm6Kk8XH XODz5svhSigCRfWs3TOSoyAoSxTjD6hiFeT5kpO7rYU2dDxlxOU6XxKBCZJnh57F8s4C XGX8BW8Drl6G8G+WAWqp4cQTOS2LopvWOKWKlPwPkZDEDO10lEneFFoKPIMY7kTXU/HV FI/504jvZMGSelmViqT3Pz1ZoG7u4ta8jzW+Uk+5ybcoHkOXIBrIjzrpko+xw+6J2xh6 XJng==
X-Received: by 10.224.171.196 with SMTP id i4mr41052709qaz.38.1384093475813; Sun, 10 Nov 2013 06:24:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.36.200 with HTTP; Sun, 10 Nov 2013 06:24:15 -0800 (PST)
In-Reply-To: <87mwlcnzsx.wl%jch@pps.univ-paris-diderot.fr>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr> <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com> <87mwlcnzsx.wl%jch@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@googlemail.com>
Date: Sun, 10 Nov 2013 15:24:15 +0100
Message-ID: <CAGnRvuqTN2TorVySF8ne=d+_tTk9w60eS+xRqmAm9+GeBeXx4w@mail.gmail.com>
Subject: Re: [homenet] Tsinghua work on source/destination routing
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Mon, 11 Nov 2013 08:02:41 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <rtgwg@ietf.org>, Shu Yang <yangshu1988@gmail.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: Sun, 10 Nov 2013 14:24:37 -0000

On Sun, Nov 10, 2013 at 2:37 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> > Excellent.  Could we please have a look at the source code ?  (It was
>> > already promised in Berlin, if memory serves.)
>>
>> If you want, I can send you the current version privately at this moment.
>
> I'd much prefer a public repository, something I can discuss freely
> with people (and eventually cite) without worrying whether I'm disclosing
> anything confidential.

I agree with Juliusz, a public repository would be much better, even
if it only contains "in development" code.

If the code will be open sourced in the end anyways I don't see any drawbacks.

Henning Rogge

-- 
We began as wanderers, and we are wanderers still. We have lingered
long enough on the shores of the cosmic ocean. We are ready at last to
set sail for the stars - Carl Sagan

From aretana@cisco.com  Mon Nov 11 12:48:08 2013
Return-Path: <aretana@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 B87F411E80EC for <rtgwg@ietfa.amsl.com>; Mon, 11 Nov 2013 12:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.586
X-Spam-Level: 
X-Spam-Status: No, score=-10.586 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 fpZlHAY0-IYX for <rtgwg@ietfa.amsl.com>; Mon, 11 Nov 2013 12:48:04 -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 3CC6021F9994 for <rtgwg@ietf.org>; Mon, 11 Nov 2013 12:48:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1195; q=dns/txt; s=iport; t=1384202881; x=1385412481; h=from:to:subject:date:message-id:mime-version; bh=/ikaa9d24pw7m+RX526M7NjNCWHu18BNGiYZOXEM+CU=; b=CBPKF0FjuoC/8xvZ6F5uC8OyXijyTKB5m0y+mKZATt6GBEtWBYDaOBS1 qpingPBJR3n59DZYoBz3sl3GDKuxwbZv6Qd7si654vnn2Y9RXqGvPeP5t KdD3BQh6AgD8W8bOoaPA1vZl4u8zPuYVBBqz6BE0dtxJkzYcc5ucRd05b 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqoHAKFBgVKtJV2d/2dsb2JhbABZgkNEOFOEErJNiXcWbQeCHBCBCwELAXQnBByHeA2dSaEWlBoDmA+SCoMmgio
X-IronPort-AV: E=Sophos;i="4.93,679,1378857600";  d="scan'208,217";a="283407271"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-5.cisco.com with ESMTP; 11 Nov 2013 20:48:00 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id rABKlxCn015284 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtgwg@ietf.org>; Mon, 11 Nov 2013 20:47:59 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.147]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Mon, 11 Nov 2013 14:47:59 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: IETF 88 MInutes Posted
Thread-Topic: IETF 88 MInutes Posted
Thread-Index: AQHO3x9O4VEcrJIXF06WBZEwuH9WPg==
Date: Mon, 11 Nov 2013 20:47:58 +0000
Message-ID: <CEA6ACAD.40DD6%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.15.4]
Content-Type: multipart/alternative; boundary="_000_CEA6ACAD40DD6aretanaciscocom_"
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, 11 Nov 2013 20:48:08 -0000

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

Hi!

Just posted the minutes from last week.

http://www.ietf.org/proceedings/88/minutes/minutes-88-rtgwg

Thanks to Acee for taking notes!

Alvaro.

--_000_CEA6ACAD40DD6aretanaciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <4A126117E978D149B544CD8189CBD9DC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Hi!</div>
<div><br>
</div>
<div>Just posted the minutes from last week.</div>
<div><br>
</div>
<div><a href=3D"http://www.ietf.org/proceedings/88/minutes/minutes-88-rtgwg=
">http://www.ietf.org/proceedings/88/minutes/minutes-88-rtgwg</a></div>
<div><br>
</div>
<div>Thanks to Acee for taking notes!</div>
<div><br>
</div>
<div>Alvaro.</div>
</body>
</html>

--_000_CEA6ACAD40DD6aretanaciscocom_--

From internet-drafts@ietf.org  Wed Nov 13 16:27:13 2013
Return-Path: <internet-drafts@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 19DF621E817A; Wed, 13 Nov 2013 16:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 QFYr9pTt1cHs; Wed, 13 Nov 2013 16:27:12 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D5121E80FF; Wed, 13 Nov 2013 16:27:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-cl-requirement-13.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131114002712.30560.44200.idtracker@ietfa.amsl.com>
Date: Wed, 13 Nov 2013 16:27:12 -0800
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Nov 2013 00:27:13 -0000

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

	Title           : Requirements for Advanced Multipath in MPLS Networks
	Author(s)       : Curtis Villamizar
                          Dave McDysan
                          So Ning
                          Andrew Malis
                          Lucy Yong
	Filename        : draft-ietf-rtgwg-cl-requirement-13.txt
	Pages           : 16
	Date            : 2013-11-13

Abstract:
   This document provides a set of requirements for Advanced Multipath
   in MPLS Networks.

   Advanced Multipath is a formalization of multipath techniques
   currently in use in IP and MPLS networks and a set of extensions to
   existing multipath techniques.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-cl-requirement

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-cl-requirement-13

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtgwg-cl-requirement-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From internet-drafts@ietf.org  Wed Nov 13 17:32:04 2013
Return-Path: <internet-drafts@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 2392721E80D9; Wed, 13 Nov 2013 17:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 Zt9F444w+Z5i; Wed, 13 Nov 2013 17:32:03 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F3A711E8121; Wed, 13 Nov 2013 17:32:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-cl-use-cases-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131114013203.30506.20183.idtracker@ietfa.amsl.com>
Date: Wed, 13 Nov 2013 17:32:03 -0800
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Nov 2013 01:32:04 -0000

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

	Title           : Advanced Multipath Use Cases and Design Considerations
	Author(s)       : So Ning
                          Andrew Malis
                          Dave McDysan
                          Lucy Yong
                          Curtis Villamizar
	Filename        : draft-ietf-rtgwg-cl-use-cases-05.txt
	Pages           : 24
	Date            : 2013-11-13

Abstract:
   Advanced Multipath is a formalization of multipath techniques
   currently in use in IP and MPLS networks and a set of extensions to
   existing multipath techniques.

   This document provides a set of use cases and design considerations
   for Advanced Multipath.  Existing practices are described.  Use cases
   made possible through Advanced Multipath extensions are described.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-cl-use-cases

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-cl-use-cases-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtgwg-cl-use-cases-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From psarkar@juniper.net  Mon Nov 18 08:24:46 2013
Return-Path: <psarkar@juniper.net>
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 1944C11E8178 for <rtgwg@ietfa.amsl.com>; Mon, 18 Nov 2013 08:24: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=[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 hULFR4RMaeYG for <rtgwg@ietfa.amsl.com>; Mon, 18 Nov 2013 08:24:41 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id 2236311E818F for <rtgwg@ietf.org>; Mon, 18 Nov 2013 08:23:31 -0800 (PST)
Received: from mail43-tx2-R.bigfish.com (10.9.14.244) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.22; Mon, 18 Nov 2013 16:23:31 +0000
Received: from mail43-tx2 (localhost [127.0.0.1])	by mail43-tx2-R.bigfish.com (Postfix) with ESMTP id 4DBF520344	for <rtgwg@ietf.org>; Mon, 18 Nov 2013 16:23:31 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -32
X-BigFish: VPS-32(z579ehz9371I936eI542Ia65R14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah8275dh1de097h186068hz2fh109h2a8h839h93fhd24hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail43-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=psarkar@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(377454003)(13464003)(377424004)(26614003)(199002)(189002)(53754006)(74366001)(66066001)(76482001)(65816001)(83072001)(54356001)(85306002)(33646001)(77982001)(15202345003)(56776001)(59766001)(76796001)(76786001)(49866001)(47736001)(50986001)(15975445006)(76576001)(47976001)(79102001)(4396001)(63696002)(87266001)(54316002)(80976001)(74706001)(19580395003)(53806001)(74502001)(74316001)(76176001)(74662001)(31966008)(80022001)(69226001)(2656002)(77096001)(47446002)(74876001)(51856001)(83322001)(87936001)(19580405001)(81686001)(46102001)(56816003)(81816001)(81542001)(81342001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BN1PR05MB518; H:BN1PR05MB520.namprd05.prod.outlook.com; CLIP:116.197.184.16; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail43-tx2 (localhost.localdomain [127.0.0.1]) by mail43-tx2 (MessageSwitch) id 1384791808848949_13873; Mon, 18 Nov 2013 16:23:28 +0000 (UTC)
Received: from TX2EHSMHS010.bigfish.com (unknown [10.9.14.233])	by mail43-tx2.bigfish.com (Postfix) with ESMTP id C69082600F8	for <rtgwg@ietf.org>; Mon, 18 Nov 2013 16:23:28 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS010.bigfish.com (10.9.99.110) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 18 Nov 2013 16:23:26 +0000
Received: from BN1PR05MB518.namprd05.prod.outlook.com (10.141.65.143) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.383.1; Mon, 18 Nov 2013 16:23:17 +0000
Received: from BN1PR05MB520.namprd05.prod.outlook.com (10.141.65.151) by BN1PR05MB518.namprd05.prod.outlook.com (10.141.65.143) with Microsoft SMTP Server (TLS) id 15.0.815.6; Mon, 18 Nov 2013 16:23:16 +0000
Received: from BN1PR05MB520.namprd05.prod.outlook.com ([169.254.14.188]) by BN1PR05MB520.namprd05.prod.outlook.com ([169.254.14.51]) with mapi id 15.00.0815.000; Mon, 18 Nov 2013 16:23:16 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Request comments and feedback on draft-psarkar-rtgwg-rlfa-node-protection-02
Thread-Topic: Request comments and feedback on draft-psarkar-rtgwg-rlfa-node-protection-02
Thread-Index: Ac7kec+aPhbutXedQa62HQuIIMqg7Q==
Date: Mon, 18 Nov 2013 16:23:15 +0000
Message-ID: <d81914fb281d4fa4861b878cb29f6149@BN1PR05MB520.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [116.197.184.16]
x-forefront-prvs: 00342DD5BC
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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, 18 Nov 2013 16:24:46 -0000

SGkgQWxsLA0KDQpXZSBoYXZlIG1lcmdlZCBkcmFmdC1wc2Fya2FyLXJ0Z3dnLXJsZmEtbm9kZS1w
cm90ZWN0aW9uIHdpdGggZHJhZnQtbGl0a293c2tpLW5vZGUtcHJvdGVjdC1yZW1vdGUtbGZhIGFu
ZCB1cGxvYWRlZCB0aGUgbmV4dCB2ZXJzaW9uLiBSZXF1ZXN0IHlvdSBhbGwgdG8gZ28gdGhyb3Vn
aCBpdCBhbmQgcHJvdmlkZSB5b3VyIGNvbW1lbnRzIGFuZCBmZWVkYmFjay4NCg0KVGhhbmtzIGFu
ZCBSZWdhcmRzLA0KLVB1c2hwYXNpcw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv
bTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYu
b3JnXSANClNlbnQ6IE1vbmRheSwgTm92ZW1iZXIgMTgsIDIwMTMgOToyMSBQTQ0KVG86IFNocmFk
ZGhhIEhlZ2RlOyBIYW5uZXMgR3JlZGxlcjsgY2Jvd2Vyc0A7IHBzYXJrYXJAOyBIYXJpc2ggUmFn
aHV2ZWVyOyBDaHJpcyBCb3dlcnM7IFB1c2hwYXNpcyBTYXJrYXI7IFN0ZXBoYW5lIExpdGtvd3Nr
aQ0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1wc2Fya2FyLXJ0
Z3dnLXJsZmEtbm9kZS1wcm90ZWN0aW9uLTAyLnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1E
LCBkcmFmdC1wc2Fya2FyLXJ0Z3dnLXJsZmEtbm9kZS1wcm90ZWN0aW9uLTAyLnR4dA0KaGFzIGJl
ZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBQdXNocGFzaXMgU2Fya2FyIGFuZCBwb3N0ZWQg
dG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6CSBkcmFmdC1wc2Fya2FyLXJ0Z3dn
LXJsZmEtbm9kZS1wcm90ZWN0aW9uDQpSZXZpc2lvbjoJIDAyDQpUaXRsZToJCSBSZW1vdGUtTEZB
IE5vZGUgUHJvdGVjdGlvbiBhbmQgTWFuYWdlYWJpbGl0eQ0KQ3JlYXRpb24gZGF0ZToJIDIwMTMt
MTEtMTgNCkdyb3VwOgkJIEluZGl2aWR1YWwgU3VibWlzc2lvbg0KTnVtYmVyIG9mIHBhZ2VzOiAx
NQ0KVVJMOiAgICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9k
cmFmdC1wc2Fya2FyLXJ0Z3dnLXJsZmEtbm9kZS1wcm90ZWN0aW9uLTAyLnR4dA0KU3RhdHVzOiAg
ICAgICAgICBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXBzYXJrYXItcnRn
d2ctcmxmYS1ub2RlLXByb3RlY3Rpb24NCkh0bWxpemVkOiAgICAgICAgaHR0cDovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtcHNhcmthci1ydGd3Zy1ybGZhLW5vZGUtcHJvdGVjdGlvbi0wMg0K
RGlmZjogICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1w
c2Fya2FyLXJ0Z3dnLXJsZmEtbm9kZS1wcm90ZWN0aW9uLTAyDQoNCkFic3RyYWN0Og0KICAgVGhl
IGxvb3AtZnJlZSBhbHRlcm5hdGVzIGNvbXB1dGVkIGZvbGxvd2luZyB0aGUgY3VycmVudCBSZW1v
dGUtTEZBDQogICBbSS1ELmlldGYtcnRnd2ctcmVtb3RlLWxmYV0gc3BlY2lmaWNhdGlvbiBnYXVy
YW50ZWVzIG9ubHkgbGluay0NCiAgIHByb3RlY3Rpb24uICBUaGUgcmVzdWx0aW5nIFJlbW90ZS1M
RkEgbmV4dGhvcHMgKGFsc28gY2FsbGVkIFBRLQ0KICAgbm9kZXMpLCBtYXkgbm90IGdhdXJhbnRl
ZSBub2RlLXByb3RlY3Rpb24gZm9yIGFsbCBkZXN0aW5hdGlvbnMgYmVpbmcNCiAgIHByb3RlY3Rl
ZCBieSBpdC4NCg0KICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgcHJvY2VkdXJlcyBmb3IgZGV0
ZXJtaW5pbmcgaWYgYSBnaXZlbiBQUS1ub2RlDQogICBwcm92aWRlcyBub2RlLXByb3RlY3Rpb24g
Zm9yIGEgc3BlY2lmaWMgZGVzdGluYXRpb24gb3Igbm90LiAgVGhlDQogICBkb2N1bWVudCBhbHNv
IHNob3dzIGhvdyB0aGUgc2FtZSBwcm9jZWR1cmUgY2FuIGJlIHV0aWxpc2VkIGZvcg0KICAgY29s
bGVjdGlvbiBvZiBjb21wbGV0ZSBjaGFyYWN0ZXJpc3RpY3MgZm9yIGFsdGVybmF0ZSBwYXRocy4N
CiAgIEtub3dsZWRnZSBhYm91dCB0aGUgY2hhcmFjdGVyaXN0aWNzIG9mIGFsbCBhbHRlcm5hdGUg
cGF0aCBpcw0KICAgcHJlY3Vyc29yeSB0byBhcHBseSBvcGVyYXRvciBkZWZpbmVkIHBvbGljeSBm
b3IgZWxpbWluYXRpbmcgcGF0aHMgbm90DQogICBmaXR0aW5nIGNvbnN0cmFpbnRzLg0KDQoNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICANCg0KDQpQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtl
IGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uIHVudGlsIHRo
ZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5v
cmcuDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg0KDQo=


From yangshu1988@gmail.com  Tue Nov 19 00:10:27 2013
Return-Path: <yangshu1988@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09AB71ACC85; Tue, 19 Nov 2013 00:10:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X_PdXOrqIuQh; Tue, 19 Nov 2013 00:10:25 -0800 (PST)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id EA8501ACC82; Tue, 19 Nov 2013 00:10:24 -0800 (PST)
Received: by mail-we0-f177.google.com with SMTP id p61so2604651wes.22 for <multiple recipients>; Tue, 19 Nov 2013 00:10:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ul8+qQpxkayDnb1bwSaehMZBdpQ7F9SZO/ZWdoshbdA=; b=e8LJRttNBhJjjeO9YydI4LA/YAJXcxGV24AiTglNXsc0QJ9HL+Z/I3rVuLnXggUbgP CcMPCeyoR0SpL96i6C02mt8KAcR4kvE5UV2xjrqtyu1k7zpyqHdTKD35OSJfoSc7YzdG kEhWtPYmz88i+RcWnSu4ZCXfPbETY/S+7QWZW/z9OLmkv4Dd1hVZu49QACO+s7YyK2bP N4hU2CEwj+SXTkfWjxXp8tzG1htbuIO147xCRe3O1qx21Q2kh0wmgUcVnVQNlHz6RiQy RrkvM4+qjA6q4OQAZX41ZY3vBjMKzL8U7SULjlZxPadCcb5mov+U7EJqXqqfSp45xevG mUgw==
MIME-Version: 1.0
X-Received: by 10.194.200.100 with SMTP id jr4mr5102157wjc.37.1384848618423; Tue, 19 Nov 2013 00:10:18 -0800 (PST)
Received: by 10.194.36.196 with HTTP; Tue, 19 Nov 2013 00:10:18 -0800 (PST)
In-Reply-To: <CAL6OX+27_SxYH5=78pA2siy3fDg4p8TupWSUj10kH5sh4Lx5Tg@mail.gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr> <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com> <87mwlcnzsx.wl%jch@pps.univ-paris-diderot.fr> <CAGnRvuqTN2TorVySF8ne=d+_tTk9w60eS+xRqmAm9+GeBeXx4w@mail.gmail.com> <CAL6OX+27_SxYH5=78pA2siy3fDg4p8TupWSUj10kH5sh4Lx5Tg@mail.gmail.com>
Date: Tue, 19 Nov 2013 16:10:18 +0800
Message-ID: <CAL6OX+0jM0pJ0gQFL7cQRwrvWXezKsfu=x8ATizWBCki5pnd2Q@mail.gmail.com>
Subject: Re: [homenet] Tsinghua work on source/destination routing
From: Shu Yang <yangshu1988@gmail.com>
To: Henning Rogge <hrogge@googlemail.com>
Content-Type: multipart/alternative; boundary=047d7bb03e1ef80e9104eb83316c
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, "ospf@ietf.org" <ospf@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Nov 2013 08:10:27 -0000

--047d7bb03e1ef80e9104eb83316c
Content-Type: text/plain; charset=ISO-8859-1

> Ok, we will make it public in this week.
The page for the project is here:
https://github.com/t-routing/traffic-class-routing-system-based-on-OSPFv3
It's still in development status, and we will keep improving it.

Shu Yang


On Mon, Nov 11, 2013 at 3:06 PM, Shu Yang <yangshu1988@gmail.com> wrote:

> > I agree with Juliusz, a public repository would be much better, even
> > if it only contains "in development" code.
> >
> > If the code will be open sourced in the end anyways I don't see any
> drawbacks.
> >
> > Henning Rogge
>
> Ok, we will make it public in this week.
>
> Shu Yang
>

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

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:12.7=
27272033691406px">&gt; Ok, we will make it public in this week.</span><br><=
div><span style=3D"font-family:arial,sans-serif;font-size:12.72727203369140=
6px">The page for the project is here:=A0</span><font face=3D"arial, sans-s=
erif"><a href=3D"https://github.com/t-routing/traffic-class-routing-system-=
based-on-OSPFv3">https://github.com/t-routing/traffic-class-routing-system-=
based-on-OSPFv3</a></font></div>
<div><font face=3D"arial, sans-serif">It&#39;s still in development status,=
 and we will keep improving it.</font></div><div><font face=3D"arial, sans-=
serif"><br></font></div><div><font face=3D"arial, sans-serif">Shu Yang</fon=
t></div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,=
 Nov 11, 2013 at 3:06 PM, Shu Yang <span dir=3D"ltr">&lt;<a href=3D"mailto:=
yangshu1988@gmail.com" target=3D"_blank">yangshu1988@gmail.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt; I agree with Juliusz,=
 a public repository would be much better, even<br>
&gt; if it only contains &quot;in development&quot; code.<br>
&gt;<br>
&gt; If the code will be open sourced in the end anyways I don&#39;t see an=
y drawbacks.<br>
&gt;<br>
&gt; Henning Rogge<br>
<br>
</div>Ok, we will make it public in this week.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Shu Yang<br>
</font></span></blockquote></div><br></div>

--047d7bb03e1ef80e9104eb83316c--

From jch@pps.univ-paris-diderot.fr  Tue Nov 19 02:22:49 2013
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6700D1AD8CD; Tue, 19 Nov 2013 02:22:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F9We4TGlFZnZ; Tue, 19 Nov 2013 02:22:47 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by ietfa.amsl.com (Postfix) with ESMTP id 5C5121AD8F4; Tue, 19 Nov 2013 02:22:47 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id rAJAMafL003582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Nov 2013 11:22:36 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/46573) with ESMTP id rAJAMaI5004749; Tue, 19 Nov 2013 11:22:36 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 1D97F5B449; Tue, 19 Nov 2013 11:22:36 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id ucBultFNswwi; Tue, 19 Nov 2013 11:22:34 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 817C45B446; Tue, 19 Nov 2013 11:22:34 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.pps.univ-paris-diderot.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.80) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1ViiS2-0007SV-9s; Tue, 19 Nov 2013 11:22:34 +0100
Date: Tue, 19 Nov 2013 11:22:34 +0100
Message-ID: <7i8uwky9lh.wl%jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Shu Yang <yangshu1988@gmail.com>
Subject: Re: [homenet] Tsinghua work on source/destination routing
In-Reply-To: <CAL6OX+0jM0pJ0gQFL7cQRwrvWXezKsfu=x8ATizWBCki5pnd2Q@mail.gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr> <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com> <87mwlcnzsx.wl%jch@pps.univ-paris-diderot.fr> <CAGnRvuqTN2TorVySF8ne=d+_tTk9w60eS+xRqmAm9+GeBeXx4w@mail.gmail.com> <CAL6OX+27_SxYH5=78pA2siy3fDg4p8TupWSUj10kH5sh4Lx5Tg@mail.gmail.com> <CAL6OX+0jM0pJ0gQFL7cQRwrvWXezKsfu=x8ATizWBCki5pnd2Q@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Tue, 19 Nov 2013 11:22:36 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 19 Nov 2013 11:22:36 +0100 (CET)
X-Miltered: at korolev with ID 528B3BEC.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 528B3BEC.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 528B3BEC.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 528B3BEC.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 528B3BEC.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 528B3BEC.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, Henning Rogge <hrogge@googlemail.com>, "ospf@ietf.org" <ospf@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Nov 2013 10:22:49 -0000

> > Ok, we will make it public in this week.

> The page for the project is here: https://github.com/t-routing/
> traffic-class-routing-system-based-on-OSPFv3

Thanks, but could you please point us at your code?  That's a full
Quagga tree merged with a full Click tree, with no development history.

(I've quickly checked the Quagga-FIB interface, and haven't found
anything new in there, but then perhaps I haven't looked hard enough.)

-- Juliusz

From markus.stenberg@iki.fi  Tue Nov 19 02:31:20 2013
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47FF51ADBE8; Tue, 19 Nov 2013 02:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_41=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c7WCcTnc7CxG; Tue, 19 Nov 2013 02:31:18 -0800 (PST)
Received: from kirsi1.inet.fi (mta-out.inet.fi [195.156.147.13]) by ietfa.amsl.com (Postfix) with ESMTP id EEAD81ADBF7; Tue, 19 Nov 2013 02:31:17 -0800 (PST)
Received: from kosame.lan (80.220.67.193) by kirsi1.inet.fi (8.5.140.03) (authenticated as stenma-47) id 526FA42301E20C0F; Tue, 19 Nov 2013 12:31:09 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Re: [homenet] Tsinghua work on source/destination routing
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <7i8uwky9lh.wl%jch@pps.univ-paris-diderot.fr>
Date: Tue, 19 Nov 2013 12:30:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC5DE74F-66EA-4531-B9A8-53B77F0BDF4F@iki.fi>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr> <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com> <87mwlcnzsx.wl%jch@pps.univ-paris-diderot.fr> <CAGnRvuqTN2TorVySF8ne=d+_tTk9w60eS+xRqmAm9+GeBeXx4w@mail.gmail.com> <CAL6OX+27_SxYH5=78pA2siy3fDg4p8TupWSUj10kH5sh4Lx5Tg@mail.gmail.com> <CAL6OX+0jM0pJ0gQFL7cQRwrvWXezKsfu=x8ATizWBCki5pnd2Q@mail.gmail.com> <7i8uwky9lh.wl%jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.1822)
X-Mailman-Approved-At: Tue, 19 Nov 2013 05:24:17 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, Henning Rogge <hrogge@googlemail.com>, Markus Stenberg <markus.stenberg@iki.fi>, "ospf@ietf.org" <ospf@ietf.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <rtgwg@ietf.org>, Shu Yang <yangshu1988@gmail.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Nov 2013 10:31:20 -0000

On 19.11.2013, at 12.22, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:

>>> Ok, we will make it public in this week.
>=20
>> The page for the project is here: https://github.com/t-routing/
>> traffic-class-routing-system-based-on-OSPFv3
>=20
> Thanks, but could you please point us at your code?  That's a full
> Quagga tree merged with a full Click tree, with no development =
history.
>=20
> (I've quickly checked the Quagga-FIB interface, and haven't found
> anything new in there, but then perhaps I haven=92t looked hard =
enough.)

Looks like the integration with click is done right from ospf6d and it =
never even goes to zebra.=20

Two tips for next github export:

- save history so it=92s more convenient to compare with baseline (now I =
needed to do fairly arcane diff due to non-clean tree + no history)

- put cleaned tree (no *~, no binaries such as *.o)

Kind of sad, I was hoping for general src+dst aware Quagga code :)

Cheers,

-Markus=

From yangshu1988@gmail.com  Wed Nov 20 00:20:34 2013
Return-Path: <yangshu1988@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0835E1AE38F; Wed, 20 Nov 2013 00:20:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.149
X-Spam-Level: 
X-Spam-Status: No, score=-1.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_41=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FlrAax9nT3vv; Wed, 20 Nov 2013 00:20:32 -0800 (PST)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id D12701AE38E; Wed, 20 Nov 2013 00:20:29 -0800 (PST)
Received: by mail-we0-f178.google.com with SMTP id u56so1588096wes.9 for <multiple recipients>; Wed, 20 Nov 2013 00:20:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wcXBKNUKBXMb/WisJ+FdIaRXRDpe0diY8Zc8y9Y6ets=; b=EcuZOs2Z65NyTre0dhSSTx/0vV5DnMz1XJWcmB6LqF6HcNr2LsAGABYsO5XLtDigqU mGg+LlSOJurFYo4459kct+4NvrW9Z/29jn4QIgoRY6WMiOSECLm7VysujEf4KTcivWgD dZt4PqcbQAZLcwTF6XaBhxOVBZUhAsLWJ6sEPNXVrw9jkBMuKdj9Vt15l3OUUoSEF7dM UyPcr3dkpYeTrSwXej/YAi57WdK0l+FyiN2OuNR1fsM6HrKaC+PEtzLiRsrHjnBeWZfl tA6dhln8Xwb+QtbpwI2MEwdU34Dvux/rhq/0u+1iY2TPVYojJTv/DoiGyMTyP4mKwfqc QMTQ==
MIME-Version: 1.0
X-Received: by 10.194.78.51 with SMTP id y19mr65093wjw.62.1384935623177; Wed, 20 Nov 2013 00:20:23 -0800 (PST)
Received: by 10.194.36.196 with HTTP; Wed, 20 Nov 2013 00:20:23 -0800 (PST)
In-Reply-To: <DC5DE74F-66EA-4531-B9A8-53B77F0BDF4F@iki.fi>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <7ivc0313qd.wl%jch@pps.univ-paris-diderot.fr> <CAL6OX+33okPcDFGxrGcTrxZbXg1dQFD=eDA=4fvj8sSWb-W3gQ@mail.gmail.com> <87mwlcnzsx.wl%jch@pps.univ-paris-diderot.fr> <CAGnRvuqTN2TorVySF8ne=d+_tTk9w60eS+xRqmAm9+GeBeXx4w@mail.gmail.com> <CAL6OX+27_SxYH5=78pA2siy3fDg4p8TupWSUj10kH5sh4Lx5Tg@mail.gmail.com> <CAL6OX+0jM0pJ0gQFL7cQRwrvWXezKsfu=x8ATizWBCki5pnd2Q@mail.gmail.com> <7i8uwky9lh.wl%jch@pps.univ-paris-diderot.fr> <DC5DE74F-66EA-4531-B9A8-53B77F0BDF4F@iki.fi>
Date: Wed, 20 Nov 2013 16:20:23 +0800
Message-ID: <CAL6OX+3a-qCxpyoxkKKHMDZuemDj1An=n-v2Lz2+av26j2J8cg@mail.gmail.com>
Subject: Re: [homenet] Tsinghua work on source/destination routing
From: Shu Yang <yangshu1988@gmail.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Content-Type: multipart/alternative; boundary=047d7beb9b5cdb3c0f04eb97738c
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@googlemail.com>, "ospf@ietf.org" <ospf@ietf.org>, liu zheng <liuzheng19890812@163.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Routing WG <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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, 20 Nov 2013 08:20:34 -0000

--047d7beb9b5cdb3c0f04eb97738c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi, Markus,

Sorry for uploading a version without any baseline, we have changed it.

We are using Click router, which can also be integrated with Quagga easily,
i.e., Quagga generates the src+dst routing entries and updates Click
through pre-defined interfaces (we will write a detailed Readme file). We
use it because 1) Click is quite modularized (we only need to modify the
two related modules); 2) we have such experiences before.

Shu Yang
Tsinghua University




On Tue, Nov 19, 2013 at 6:30 PM, Markus Stenberg <markus.stenberg@iki.fi>wr=
ote:

> On 19.11.2013, at 12.22, Juliusz Chroboczek <jch@pps.univ-paris-diderot.f=
r>
> wrote:
>
> >>> Ok, we will make it public in this week.
> >
> >> The page for the project is here: https://github.com/t-routing/
> >> traffic-class-routing-system-based-on-OSPFv3
> >
> > Thanks, but could you please point us at your code?  That's a full
> > Quagga tree merged with a full Click tree, with no development history.
> >
> > (I've quickly checked the Quagga-FIB interface, and haven't found
> > anything new in there, but then perhaps I haven=92t looked hard enough.=
)
>
> Looks like the integration with click is done right from ospf6d and it
> never even goes to zebra.
>
> Two tips for next github export:
>
> - save history so it=92s more convenient to compare with baseline (now I
> needed to do fairly arcane diff due to non-clean tree + no history)
>
> - put cleaned tree (no *~, no binaries such as *.o)
>
> Kind of sad, I was hoping for general src+dst aware Quagga code :)
>
> Cheers,
>
> -Markus

--047d7beb9b5cdb3c0f04eb97738c
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Markus,<div><br></div><div>Sorry for uploading a versi=
on without any baseline, we have changed it.</div><div><br></div><div>We ar=
e using Click router, which can also be integrated with Quagga easily, i.e.=
, Quagga generates the src+dst routing entries and updates Click through pr=
e-defined interfaces (we will write a detailed Readme file). We use it beca=
use 1) Click is quite modularized (we only need to modify the two related m=
odules); 2) we have such experiences before.</div>
<div><br></div><div>Shu Yang</div><div>Tsinghua University</div><div><br></=
div><div>=A0</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gm=
ail_quote">On Tue, Nov 19, 2013 at 6:30 PM, Markus Stenberg <span dir=3D"lt=
r">&lt;<a href=3D"mailto:markus.stenberg@iki.fi" target=3D"_blank">markus.s=
tenberg@iki.fi</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"><div class=3D"HOEnZb"><div class=3D"h5">On 1=
9.11.2013, at 12.22, Juliusz Chroboczek &lt;<a href=3D"mailto:jch@pps.univ-=
paris-diderot.fr">jch@pps.univ-paris-diderot.fr</a>&gt; wrote:<br>

<br>
&gt;&gt;&gt; Ok, we will make it public in this week.<br>
&gt;<br>
&gt;&gt; The page for the project is here: <a href=3D"https://github.com/t-=
routing/" target=3D"_blank">https://github.com/t-routing/</a><br>
&gt;&gt; traffic-class-routing-system-based-on-OSPFv3<br>
&gt;<br>
&gt; Thanks, but could you please point us at your code? =A0That&#39;s a fu=
ll<br>
&gt; Quagga tree merged with a full Click tree, with no development history=
.<br>
&gt;<br>
&gt; (I&#39;ve quickly checked the Quagga-FIB interface, and haven&#39;t fo=
und<br>
&gt; anything new in there, but then perhaps I haven=92t looked hard enough=
.)<br>
<br>
</div></div>Looks like the integration with click is done right from ospf6d=
 and it never even goes to zebra.<br>
<br>
Two tips for next github export:<br>
<br>
- save history so it=92s more convenient to compare with baseline (now I ne=
eded to do fairly arcane diff due to non-clean tree + no history)<br>
<br>
- put cleaned tree (no *~, no binaries such as *.o)<br>
<br>
Kind of sad, I was hoping for general src+dst aware Quagga code :)<br>
<br>
Cheers,<br>
<br>
-Markus</blockquote></div><br></div>

--047d7beb9b5cdb3c0f04eb97738c--

From stbryant@cisco.com  Fri Nov 22 08:57:47 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92A7E1AE1B6 for <rtgwg@ietfa.amsl.com>; Fri, 22 Nov 2013 08:57:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.511
X-Spam-Level: 
X-Spam-Status: No, score=-8.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B6DrhZzfYBGP for <rtgwg@ietfa.amsl.com>; Fri, 22 Nov 2013 08:57:45 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 39F8C1AE3EE for <rtgwg@ietf.org>; Fri, 22 Nov 2013 08:57:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13983; q=dns/txt; s=iport; t=1385139457; x=1386349057; h=message-id:date:from:reply-to:mime-version:to:subject; bh=2mo4Tg4AZdIgsTqWgQMHRK66LCCJTb9VT4G0FCDGtTo=; b=EWEq/Zr8W1VFrzfKTJI8EeultiJy4bF8WU3GjNj4z0utuLeEfDtuEWdu oeHRMryrTHj5fgQ3MCGyfpceLs2ccPJtm+59Z1M/7tvKGWZXDFWMgOz3p LSKKiDc9WG6xXC+DjEHEhzXv8OW1kxQn1pvBhxEPhxGpFBBIWebSG5wYm c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao4GAPWLj1KQ/khN/2dsb2JhbABZgkNEvkQWbQeCJQEBAQN5BjcWGAMCAQIBPwwNBgIBAYd3BqEZhwKZHo4lEQGFCQOYFJISgyiBcQ
X-IronPort-AV: E=Sophos;i="4.93,753,1378857600"; d="scan'208,217";a="439695"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 22 Nov 2013 16:57:36 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rAMGvU9w010005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <rtgwg@ietf.org>; Fri, 22 Nov 2013 16:57:31 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rAMGvTM7016284; Fri, 22 Nov 2013 16:57:29 GMT
Message-ID: <528F8CF9.9080104@cisco.com>
Date: Fri, 22 Nov 2013 16:57:29 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: relmote lfa draft edits
Content-Type: multipart/alternative; boundary="------------030306010308040205090708"
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 22 Nov 2013 16:57:47 -0000

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

Here you go...

On 11/5/13 9:38 AM, "Stewart Bryant"<stbryant@cisco.com>  wrote:

> Hi Acee
>
> Any chance of a copy of your mins - no matter how rough - so I
> can start on my doc actions.
>
> Stewart

    Remote LFA - Stewart Bryant (See slides)
      - See changes to current version in slides.
      - Steward does not want to merge with the node repair
        document. There was consensus in the room
        to move on w/o merging.

N/A to this revision

      - Extended P-space vs P space explained. Consesus is the
        example algorithm should include both the P-space
        and Extended P-space.

        Alia: Believes there is still confusion on P-space vs
        Extended P-space.

        Chris Bowers: Confusion with all the spaces in the
        document. Can it be simplifies?
   
        Stewart: Can move Extend P-space ahead of Q space in
         description.


Please look at the new section 4.2.1
To compute the repair path for link S-E we need to determine the set of routers which can be reached from S without traversing S-E, and match this with the set of routers from which the node E can be reached, by normal forwarding, without traversing the link S-E.

We will proceed as follows: we will describe how to compute the set of routers which can be reached from S without traversing S-E. We call this the S's P-space with respect to the failure of link S-E. We will then note that S is able to use P-Space of its neighbours since S can determine which neighbour it will use as the next hop for the repair. We call this the S's Extended P-Space with respect to the failure of link S-E. The use of extended P-Space allows greater repair coverage and is the preferred approach. Finally we will show how to compute the set of routers from which the node E can be reached, by normal forwarding, without traversing the link S-E. This is called the Q-space of E with respect to the link S-E. The selection of the prefered node from the set of nodes that an in both Extended P-Space and Q-Space is described in [4.2.2]

A suitable cost based algorithm to compute the set of nodes common to both extended P-space and Q-space is provide in [4.3]

Then theer is 4.2.1.1 P-Space, 4.2.1.2 Extended P-space and 4.2.1.3 Q-space



  - Cost Based Algorithm - Style question.
       
        Uma Chunduri - Why is algorithm not in appendix.
        Stewart - Graph vs Cost Reachability - both algorithms
         put into the main body.
        Uma - Perfers appendix.

I think the WG consensus has been to put it in the body.
I will move it if the chairs tell me the consensus is otherwise.

        Chris - The text says it is just an example.
        Uma - The downstream check is in the algorithm but not
         the text.
        Stewart - It was in the algorithm provided by Chris.
        Alia - RFC 5286 indicates that downstream checking can
         be avoid loops.

Added to the end of Section 4.2.2

As described in [RFC5286], always selecting a PQ node that is downstream with respect to the repairing node, prevents the formation of loops when the failure is worse than expected. The use of downstream nodes reduces the repair coverage, and operators are advised to determine whether adequate coverage is acheived before enabling this selection feature.

I also added a list of definitions of terms used in the algorithm text

  - LFA with RLFA versus only R-LFA
         
        Chris: The section with the alternate view creates
         confusion.
        Email from Chris: Following up on an item discussed in
         the meeting.  We agreed that the paragraph in section 4.2.2
         that describes extended P-space in terms of (local)LFA
         should be removed because this alternative description
         may confuse the reader more than it enlightens

Removed the text


        Stewart: Wants LFA to be the primary with RLFA added.
        Acee: LFA has advantage of providing Extended P-Space
         and working w/o tunneling.
        Hannes: Agrees and clarifies Stephane's comments.
        Uma: Agree with making LFA primary calculation.
        Stewart: Will add text on policy engine to decide on
         LFA and RFLA calculation applicability.
        Stewart: Points out that you can calculate both LFA
         and RLFA.

I have added to 4.2.2

It is a local matter whether the repair path selection policy used by the router favours LFA repairs over RLFA repairs. An LFA repair has the advantage of not requiring the use of tunnel, however  network manageability considerations may lead to a repair strategy that uses a remote LFA more frequently [I-D.ietf-rtgwg-lfa-manageability]

     
       - Targeted LDP Address

           - Advertise in protocol. This is preferred.  However,
             some boxes don't advertise.
           - Management configuration as a requirement.
           - Pick an address arbitrarily.
        
          Uma: What configuration is expected?
          Stewart: Could be silent since it is a vendor
            implementation issue.
          Hannes: Lowest IP address is useless. A node should
            be able to advertise that it doesn't support
            T-LDP.
          Rob Shakir - Draft should not remain silent on this
            issue.
          Stewart: Use Router-ID if not configured to do otherwise
            like using a different address.

The text now says:

In the absence of a protocol to learn the preferred IP address for targeted LDP, an LSR should attempt a targeted LDP session with the Router ID [RFC2328] [RFC5305] [RFC5340], unless it is configured otherwise.


          Uma: Do coverage numbers in include downstream
               protection?
          Stewart: No - will include numbers if they can be
               readily obtained.

I do not have these numbers

       - Figure 1 changed or not?
          Stewart: Will not be changed.
       - Final Comments?

Figure left alone

        Hannes: I don't understand relucance to merge with node
           protection.
         Stewart: Does not want to merge. Wants to finish draft. Node
           protection problem can quickly get out of control.
         Hannes: This would be valuable implementation experience.
         Alvaro: Already have "rough" consensus on moving forward
           with the draft.

When the online XML2RFC compiler comes back online I will compile and upload.

Stewart



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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-text-plain" wrap="true" graphical-quote="true"
      style="font-family: -moz-fixed; font-size: 12px;" lang="x-western">
      <pre wrap="">Here you go...

On 11/5/13 9:38 AM, "Stewart Bryant" <a class="moz-txt-link-rfc2396E" href="mailto:stbryant@cisco.com">&lt;stbryant@cisco.com&gt;</a> wrote:

</pre>
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">Hi Acee

Any chance of a copy of your mins - no matter how rough - so I
can start on my doc actions.

Stewart
</pre>
      </blockquote>
    </div>
    <pre wrap="">
   Remote LFA - Stewart Bryant (See slides) 
     - See changes to current version in slides. 
     - Steward does not want to merge with the node repair 
       document. There was consensus in the room
       to move on w/o merging. 

N/A to this revision

    &nbsp;- Extended P-space vs P space explained. Consesus is the
       example algorithm should include both the P-space
       and Extended P-space.  

       Alia: Believes there is still confusion on P-space vs
       Extended P-space. 

       Chris Bowers: Confusion with all the spaces in the
       document. Can it be simplifies? 
  
       Stewart: Can move Extend P-space ahead of Q space in
        description.  


Please look at the new section 4.2.1
To compute the repair path for link S-E we need to determine the set of routers which can be reached from S without traversing S-E, and match this with the set of routers from which the node E can be reached, by normal forwarding, without traversing the link S-E. 

We will proceed as follows: we will describe how to compute the set of routers which can be reached from S without traversing S-E. We call this the S's P-space with respect to the failure of link S-E. We will then note that S is able to use P-Space of its neighbours since S can determine which neighbour it will use as the next hop for the repair. We call this the S's Extended P-Space with respect to the failure of link S-E. The use of extended P-Space allows greater repair coverage and is the preferred approach. Finally we will show how to compute the set of routers from which the node E can be reached, by normal forwarding, without traversing the link S-E. This is called the Q-space of E with respect to the link S-E. The selection of the prefered node from the set of nodes that an in both Extended P-Space and Q-Space is described in [4.2.2]

A suitable cost based algorithm to compute the set of nodes common to both extended P-space and Q-space is provide in [4.3]

Then theer is 4.2.1.1 P-Space, 4.2.1.2 Extended P-space and 4.2.1.3 Q-space



&nbsp;- Cost Based Algorithm - Style question. 
      
       Uma Chunduri - Why is algorithm not in appendix. 
       Stewart - Graph vs Cost Reachability - both algorithms
        put into the main body. 
       Uma - Perfers appendix. 

I think the WG consensus has been to put it in the body.
I will move it if the chairs tell me the consensus is otherwise.

       Chris - The text says it is just an example. 
       Uma - The downstream check is in the algorithm but not
        the text. 
       Stewart - It was in the algorithm provided by Chris. 
       Alia - RFC 5286 indicates that downstream checking can 
        be avoid loops. 

Added to the end of Section 4.2.2

As described in [RFC5286], always selecting a PQ node that is downstream with respect to the repairing node, prevents the formation of loops when the failure is worse than expected. The use of downstream nodes reduces the repair coverage, and operators are advised to determine whether adequate coverage is acheived before enabling this selection feature.

I also added a list of definitions of terms used in the algorithm text

&nbsp;- LFA with RLFA versus only R-LFA 
        
       Chris: The section with the alternate view creates
        confusion. 
       Email from Chris: Following up on an item discussed in 
        the meeting.  We agreed that the paragraph in section 4.2.2
        that describes extended P-space in terms of (local)LFA 
        should be removed because this alternative description 
        may confuse the reader more than it enlightens

Removed the text 


      &nbsp;Stewart: Wants LFA to be the primary with RLFA added. 
       Acee: LFA has advantage of providing Extended P-Space 
        and working w/o tunneling. 
       Hannes: Agrees and clarifies Stephane's comments. 
       Uma: Agree with making LFA primary calculation. 
       Stewart: Will add text on policy engine to decide on
        LFA and RFLA calculation applicability. 
       Stewart: Points out that you can calculate both LFA
        and RLFA. 

I have added to 4.2.2

It is a local matter whether the repair path selection policy used by the router favours LFA repairs over RLFA repairs. An LFA repair has the advantage of not requiring the use of tunnel, however  network manageability considerations may lead to a repair strategy that uses a remote LFA more frequently [I-D.ietf-rtgwg-lfa-manageability]

    
      - Targeted LDP Address

          - Advertise in protocol. This is preferred.  However,
            some boxes don't advertise. 
          - Management configuration as a requirement. 
          - Pick an address arbitrarily. 
       
         Uma: What configuration is expected? 
         Stewart: Could be silent since it is a vendor
           implementation issue. 
         Hannes: Lowest IP address is useless. A node should
           be able to advertise that it doesn't support
           T-LDP. 
         Rob Shakir - Draft should not remain silent on this 
           issue. 
         Stewart: Use Router-ID if not configured to do otherwise 
           like using a different address.

The text now says:

In the absence of a protocol to learn the preferred IP address for targeted LDP, an LSR should attempt a targeted LDP session with the Router ID [RFC2328] [RFC5305] [RFC5340], unless it is configured otherwise.


        &nbsp;Uma: Do coverage numbers in include downstream
              protection? 
         Stewart: No - will include numbers if they can be 
              readily obtained. 

I do not have these numbers

      - Figure 1 changed or not? 
         Stewart: Will not be changed. 
      - Final Comments?

Figure left alone

      &nbsp;Hannes: I don't understand relucance to merge with node
          protection. 
        Stewart: Does not want to merge. Wants to finish draft. Node
          protection problem can quickly get out of control. 
        Hannes: This would be valuable implementation experience. 
        Alvaro: Already have "rough" consensus on moving forward 
          with the draft. 

When the online XML2RFC compiler comes back online I will compile and upload.

Stewart


</pre>
  </body>
</html>

--------------030306010308040205090708--

From internet-drafts@ietf.org  Fri Nov 22 13:13:35 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C4CA1AE0E5; Fri, 22 Nov 2013 13:13:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1P63SkBVLoTv; Fri, 22 Nov 2013 13:13:34 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 086C31AE14D; Fri, 22 Nov 2013 13:13:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-rtgwg-remote-lfa-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131122211333.31134.73441.idtracker@ietfa.amsl.com>
Date: Fri, 22 Nov 2013 13:13:33 -0800
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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, 22 Nov 2013 21:13:35 -0000

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

	Title           : Remote LFA FRR
	Author(s)       : Stewart Bryant
                          Clarence Filsfils
                          Stefano Previdi
                          Mike Shand
                          Ning So
	Filename        : draft-ietf-rtgwg-remote-lfa-04.txt
	Pages           : 24
	Date            : 2013-11-22

Abstract:
   This draft describes an extension to the basic IP fast re-route
   mechanism described in RFC5286 that provides additional backup
   connectivity for link failures when none can be provided by the basic
   mechanisms.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtgwg-remote-lfa-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From stbryant@cisco.com  Fri Nov 22 13:16:29 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4211AE20D for <rtgwg@ietfa.amsl.com>; Fri, 22 Nov 2013 13:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.025
X-Spam-Level: 
X-Spam-Status: No, score=-10.025 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rfiwG4N_EzPc for <rtgwg@ietfa.amsl.com>; Fri, 22 Nov 2013 13:16:27 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7111ADFD7 for <rtgwg@ietf.org>; Fri, 22 Nov 2013 13:16:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6119; q=dns/txt; s=iport; t=1385154979; x=1386364579; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to; bh=G3AEtXN3Zp6jZ7/aZSbtOI9Q6yVcMIO+AC9SZlmXbCw=; b=DOoPoeOHJF0VrXeV4BSJ8MRrbT5IeHIjKJH8Ib7UrPWolVlsY9DWyRmp sP9gr9VeU4HwElKOOW5R6/ncfWfYFbXQopHYif/JnbullcHciKhJAwXNS yMY3Se30xflfmauDX0kK5JI1XTr6OWO4azQ+JutQX0fLE8yQS4ld15pNm 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoYFAOTIj1KQ/khM/2dsb2JhbABZgwc4TYJ+uR2BIhZ0giUBAQEEI1QBDQQcAwECChYLAgIJAwIBAgEPLAIIBgEMBgIBAQWHZgMPCAWwK4hIDYgnF4x4gSQJEQE/GAaCZYFHA5YpgWuBMIsqhTiDKIFx
X-IronPort-AV: E=Sophos;i="4.93,753,1378857600";  d="scan'208,217,223";a="1099896"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 22 Nov 2013 21:16:17 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rAMLGBEo032223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Nov 2013 21:16:13 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id rAMLGAna029448; Fri, 22 Nov 2013 21:16:11 GMT
Message-ID: <528FC999.7000501@cisco.com>
Date: Fri, 22 Nov 2013 21:16:09 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg-chairs@tools.ietf.org" <rtgwg-chairs@tools.ietf.org>
Subject: Fwd: New Version Notification for draft-ietf-rtgwg-remote-lfa-04.txt
References: <20131122211334.31134.91996.idtracker@ietfa.amsl.com>
In-Reply-To: <20131122211334.31134.91996.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20131122211334.31134.91996.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------040405060007010403050200"
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 22 Nov 2013 21:16:29 -0000

This is a multi-part message in MIME format.
--------------040405060007010403050200
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


 From my previous email, you will see that I did
everything that was minuted at the IETF meeting
except the extra sim, which I have not been provided
with.

As duty editor, I think that we are now ready
for WG Last Call on this draft.

- Stewart

-------- Original Message --------
Subject: 	New Version Notification for draft-ietf-rtgwg-remote-lfa-04.txt
Date: 	Fri, 22 Nov 2013 13:13:34 -0800
From: 	<internet-drafts@ietf.org>
To: 	Mike Shand <imc.shand@gmail.com>, Stefano Previdi 
<sprevidi@cisco.com>, "So Ning" <ning.so@tatacommunications.com>, Ning 
So <ning.so@tatacommunications.com>, Clarence Filsfils 
<cfilsfil@cisco.com>, Stewart Bryant <stbryant@cisco.com>



A new version of I-D, draft-ietf-rtgwg-remote-lfa-04.txt
has been successfully submitted by Stewart Bryant and posted to the
IETF repository.

Filename:	 draft-ietf-rtgwg-remote-lfa
Revision:	 04
Title:		 Remote LFA FRR
Creation date:	 2013-11-22
Group:		 rtgwg
Number of pages: 24
URL:             http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-remote-lfa-04.txt
Status:          http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa
Htmlized:        http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa-04
Diff:            http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-remote-lfa-04

Abstract:
    This draft describes an extension to the basic IP fast re-route
    mechanism described in RFC5286 that provides additional backup
    connectivity for link failures when none can be provided by the basic
    mechanisms.


                                                                                   


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

.




--------------040405060007010403050200
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-forward-container">From my previous email, you will
      see that I did<br>
      everything that was minuted at the IETF meeting<br>
      except the extra sim, which I have not been provided<br>
      with.<br>
      <br>
      As duty editor, I think that we are now ready<br>
      for WG Last Call on this draft.<br>
      <br>
      - Stewart<br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>New Version Notification for
              draft-ietf-rtgwg-remote-lfa-04.txt</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Fri, 22 Nov 2013 13:13:34 -0800</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td><a class="moz-txt-link-rfc2396E" href="mailto:internet-drafts@ietf.org">&lt;internet-drafts@ietf.org&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td>Mike Shand <a class="moz-txt-link-rfc2396E" href="mailto:imc.shand@gmail.com">&lt;imc.shand@gmail.com&gt;</a>, Stefano Previdi
              <a class="moz-txt-link-rfc2396E" href="mailto:sprevidi@cisco.com">&lt;sprevidi@cisco.com&gt;</a>, "So Ning"
              <a class="moz-txt-link-rfc2396E" href="mailto:ning.so@tatacommunications.com">&lt;ning.so@tatacommunications.com&gt;</a>, Ning So
              <a class="moz-txt-link-rfc2396E" href="mailto:ning.so@tatacommunications.com">&lt;ning.so@tatacommunications.com&gt;</a>, Clarence Filsfils
              <a class="moz-txt-link-rfc2396E" href="mailto:cfilsfil@cisco.com">&lt;cfilsfil@cisco.com&gt;</a>, Stewart Bryant
              <a class="moz-txt-link-rfc2396E" href="mailto:stbryant@cisco.com">&lt;stbryant@cisco.com&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>A new version of I-D, draft-ietf-rtgwg-remote-lfa-04.txt
has been successfully submitted by Stewart Bryant and posted to the
IETF repository.

Filename:	 draft-ietf-rtgwg-remote-lfa
Revision:	 04
Title:		 Remote LFA FRR
Creation date:	 2013-11-22
Group:		 rtgwg
Number of pages: 24
URL:             <a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-remote-lfa-04.txt">http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-remote-lfa-04.txt</a>
Status:          <a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa">http://datatracker.ietf.org/doc/draft-ietf-rtgwg-remote-lfa</a>
Htmlized:        <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa-04">http://tools.ietf.org/html/draft-ietf-rtgwg-remote-lfa-04</a>
Diff:            <a class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-remote-lfa-04">http://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-remote-lfa-04</a>

Abstract:
   This draft describes an extension to the basic IP fast re-route
   mechanism described in RFC5286 that provides additional backup
   connectivity for link failures when none can be provided by the basic
   mechanisms.


                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

.

</pre>
      <br>
    </div>
    <br>
  </body>
</html>

--------------040405060007010403050200--

From iesg-secretary@ietf.org  Mon Nov 25 11:46:47 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97AE01ADF9B; Mon, 25 Nov 2013 11:46:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kEsSPzac8X2h; Mon, 25 Nov 2013 11:46:46 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5193F1ADBD3; Mon, 25 Nov 2013 11:46:46 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-rtgwg-cl-requirement-13.txt> (Requirements for Advanced Multipath in MPLS Networks) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20131125194646.14059.8711.idtracker@ietfa.amsl.com>
Date: Mon, 25 Nov 2013 11:46:46 -0800
Cc: rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
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, 25 Nov 2013 19:46:47 -0000

The IESG has received a request from the Routing Area Working Group WG
(rtgwg) to consider the following document:
- 'Requirements for Advanced Multipath in MPLS Networks'
  <draft-ietf-rtgwg-cl-requirement-13.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-12-09. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document provides a set of requirements for Advanced Multipath
   in MPLS Networks.

   Advanced Multipath is a formalization of multipath techniques
   currently in use in IP and MPLS networks and a set of extensions to
   existing multipath techniques.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-rtgwg-cl-requirement/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-rtgwg-cl-requirement/ballot/


No IPR declarations have been submitted directly on this I-D.

I draw readers attention to the following note in the Shepherds report:

"After the last WGLC completed, there was concern about the terminology of
composite link not quite matching that used in the ITU.  The draft has been
updated to use the term "Advanced Multipath" instead.  Some additional 
simplifications were also made by the authors' agreement."

In view of the changes to the text starting a second IETF Last Call.


From eric.wu@huawei.com  Thu Nov 28 22:40:37 2013
Return-Path: <eric.wu@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2CF91AE116 for <rtgwg@ietfa.amsl.com>; Thu, 28 Nov 2013 22:40:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.752
X-Spam-Level: 
X-Spam-Status: No, score=-1.752 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZQCD8TTfKARY for <rtgwg@ietfa.amsl.com>; Thu, 28 Nov 2013 22:40:34 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0D3C01A1F71 for <rtgwg@ietf.org>; Thu, 28 Nov 2013 22:40:33 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAV24620; Fri, 29 Nov 2013 06:40:31 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 29 Nov 2013 06:39:57 +0000
Received: from SZXEMA403-HUB.china.huawei.com (10.82.72.35) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 29 Nov 2013 06:40:29 +0000
Received: from SZXEMA508-MBX.china.huawei.com ([169.254.7.127]) by SZXEMA403-HUB.china.huawei.com ([10.82.72.35]) with mapi id 14.03.0158.001; Fri, 29 Nov 2013 14:40:17 +0800
From: "Wunan (Eric)" <eric.wu@huawei.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: comments//Re: I-D Action: draft-ietf-rtgwg-remote-lfa-04.txt
Thread-Topic: comments//Re: I-D Action: draft-ietf-rtgwg-remote-lfa-04.txt
Thread-Index: AQHO7M28zL7ugZD47kC+i3n7UTMOHA==
Date: Fri, 29 Nov 2013 06:40:16 +0000
Message-ID: <0F26584357FD124DB93F1535E4B0A65035D5309E@szxema508-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.87.25]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "Zhangxudong \(zhangxudong, VRP\)" <zhangxudong@huawei.com>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Nov 2013 06:40:38 -0000

SGkgU3Rld2FydCwNCg0KU29tZSB0aG91Z2h0cy4NCg0KMS4gRm9yIHRoZSB0ZXJtaW5vbG9neSBw
YXJ0LCBhcyBhIHJlYWRlciwgaSB0aGluayBpdCB3aWxsIGJlIG1vcmUgbG9naWNhbCB0byBnbyBh
bG9uZyB3aXRoIHRoaXMgb3JkZXIsIGp1c3QgbGlrZSBzZWN0aW9uIDQgZGlkLg0KUC1zcGFjZSwg
RXh0ZW5kZWQgUC1zcGFjZSwgUS1zcGFjZSwgUFEgbm9kZSwgUmVwYWlyIHR1bm5lbCwgUmVwYWly
IHR1bm5lbCBlbmQgdGhlbiBSZW1vdGUgTEZBLg0KVG8gdW5kZXJzdGFuZCB0aGUgZXhhY3QgY29u
Y2VwdCBvZiBFeHRlbmRlZCBQLXNwYWNlLCBpIGhhdmUgdG8gdW5kZXJzdGFuZCBQLXNwYWNlIGZp
cnN0IHdoaWNoIG5lZWRlZCB0byBqdW1wIGludG8gdGhlIHNlY3Rpb24gb2YgNC4yLjEuIA0KTWF5
YmUgdGhlIHRlcm1pbm9sb2d5IHBhcnQgY2FuIGV4cGxhaW4gaXRzZWxmIHdpdGhvdXQgcmVmZXJy
aW5nIGZvcm1hbCBzZWN0aW9uIHBsdXMgaXQgZG9uJ3QgaGF2ZSB0byBleHBsYWluIGV2ZXJ5dGhp
bmcgc2luY2UgZGV0YWlsIGlzIGluIHRoZSBmb2xsb3dpbmcgc2VjdGlvbi4NCg0KMi4gU2VjdGlv
biAzOiAiVGhpcyBpcyBlcXVpdmFsZW50IHRvIHByb3ZpZGluZyBhIHZpcnR1YWwgDQogICBsb29w
LWZyZWUgYWx0ZXJuYXRlIHRvIHN1cHBsZW1lbnQgdGhlIHBoeXNpY2FsIGxvb3AtZnJlZSBhbHRl
cm5hdGVzLg0KICAgSGVuY2UgdGhlIG5hbWUgIlJlbW90ZSBMRkEgRlJSIi4gIg0KSSBkaWRuJ3Qg
Z2V0IHRoZSAiSGVuY2UiLCBpIHRoaW5rIGlmICJIZW5jZSIgY29tZXMgb3V0LCBpdCBzaG91bGQg
YmUgIlZpcnR1YWwgTEZBIEZSUiIuIA0KUmVtb3RlIGRpZG4ndCBjb21lIGZyb20gdmlydHVhbCBp
IHRoaW5rLiBNYXliZSB0aGlzIGlzIG5vdCB0aGUgcGxhY2UgdG8gZXhwbGFpbiB0aGUgUkxGQSdz
IG9yaWdpbi4NCg0KMy4gU2VjdGlvbiAzLjI6ICJUaGUgZGVwbG95bWVudCBpbiBhbiBNUExTL0xE
UCBlbnZpcm9ubWVudCBpcw0KICAgcmVsYXRpdmVseSBzaW1wbGUgaW4gdGhlIGRhdGEgcGxhbmUg
YXMgYW4gTERQIExTUCBmcm9tIFMgdG8gdGhlDQogICByZXBhaXIgdHVubmVsIGVuZHBvaW50ICh0
aGUgc2VsZWN0ZWQgUFEgbm9kZSkgaXMgcmVhZGlseSBhdmFpbGFibGUsDQogICBhbmQgaGVuY2Ug
ZG9lcyBub3QgcmVxdWlyZSBhbnkgbmV3IHByb3RvY29sIGV4dGVuc2lvbiBvciBkZXNpZ24NCiAg
IGNoYW5nZS4gICINCiAgIA0KICAgU2VjdGlvbiA3OiAiVG8gZXN0YWJsaXNoIGFuIHRhcmdldGVk
IExEUCBzZXNzaW9uIHdpdGggYSBjYW5kaWRhdGUgcmVtb3RlIExGQQ0KICAgcmVwYWlyIHRhcmdl
dCBub2RlIHRoZSByZXBhaXJpbmcgbm9kZSAoUykgbmVlZHMgdG8ga25vdyB3aGF0IElQDQogICBh
ZGRyZXNzIHRoYXQgdGhlIHJlbW90ZSBMRkEgcmVwYWlyIHRhcmdldCBpcyB3aWxsaW5nIHRvIHVz
ZSBmb3INCiAgIHRhcmdldGVkIExEUCBzZXNzaW9ucy4gIElkZWFsbHkgdGhpcyBpcyBwcm92aWRl
ZCBieSB0aGUgcmVtb3RlIExGQQ0KICAgcmVwYWlyIHRhcmdldCBhZHZlcnRpc2luZyB0aGlzIGFk
ZHJlc3MgaW4gdGhlIElHUCBpbiB1c2UuICBXaGljaA0KICAgYWRkcmVzcyBpcyB1c2VkLCBob3cg
dGhpcyBpcyBhZHZlcnRpc2VkIGluIHRoZSBJR1AsIGFuZCB3aGV0aGVyIHRoaXMNCiAgIGlzIGEg
c3BlY2lhbCBJUCBhZGRyZXNzIG9yIGFuIElQIGFkZHJlc3MgYWxzbyB1c2VkIGZvciBzb21lIG90
aGVyDQogICBwdXJwb3NlIGlzIG91dCBvZiBzY29wZSBmb3IgdGhpcyBkb2N1bWVudCBhbmQgbXVz
dCBiZSBzcGVjaWZpZWQgaW4gYW4NCiAgIElHUCBzcGVjaWZpYyBSRkMuIg0KICAgDQpUTERQIHNl
c3Npb24gaXMgcGVyIGZhaWxlZCBsaW5rIGluIFJMRkEuIFNvIGl0IHNob3VsZCBiZSBlc3RhYmxp
c2hlZCBhdXRvbWF0aWNhbGx5IHdpdGhvdXQgbmV0d29yayBvcGVyYXRvcidzIGludm9sdm1lbnQu
DQpBcyBzdGF0ZWQgYWJvdmUsIHRoZSBpcCBhZGRyZXNzIHVzZWQgdG8gZXN0YWJsaXNoIFRMRFAg
c2hvdWxkIGhhdmUgb25lIHdheSB0byBhZHZlcnRpc2ViZS4NCkVzcGVjaWFsbHkgaW4gTVQgc2Nl
bmFyaW8sIG1heWJlIGkgd2FudCB0byB1c2UgZGlmZmVyZW50IGlwIGFkZHJlc3MgZm9yIGRpZmZl
cmVudCBNVC4NClRoZXNlIHRoaW5ncyBzaG91bGQgYmUgc3BlY2lmaWVkIGJ5IHNwZWNpZmljIFJG
Qy4NCg0KNC4gU2VjdGlvbiAzLjI6ICJDb25zZXF1ZW50bHksIHRoZSByZXBhaXIgdHVubmVsIHVz
ZWQNCiAgIG11c3QgYmUgcHJvdmlzaW9uZWQgYmVmb3JlaGFuZCBpbiBhbnRpY2lwYXRpb24gb2Yg
dGhlIGZhaWx1cmUuICBTaW5jZQ0KICAgdGhlIGxvY2F0aW9uIG9mIHRoZSByZXBhaXIgdHVubmVs
cyBpcyBkeW5hbWljYWxseSBkZXRlcm1pbmVkIGl0IGlzDQogICBuZWNlc3NhcnkgdG8gYXV0b21h
dGljYWxseSBlc3RhYmxpc2ggdGhlIHJlcGFpciB0dW5uZWxzLiAgIg0KDQpUaGUgcmVwYWlyIHR1
bm5lbHMgYXJlIGVzdGFibGlzaGVkIGJlZm9yZWhhbmQuIEFmdGVyIHRoZSBmYWlsdXJlIGhhcHBl
bmRlZCwgbmV0d29yayB3aWxsIGNvbnZlcmdlIGFnYWluLCANCmJ1dCB0aGlzIG9sZCByZXBhaXIg
dHVubmVsIGhhcyBkb25lIGl0cyB3b3JrLCBzbyB3aWxsIGl0IGJlIGJyb2tlbiBkb3duIHRvIHJl
Y2xhaW0gcmVzb3VyY2UgYW5kIHJlLWVzdGFibGlzaCB3aGVuIHJlY292ZXIgY29udmVyZ2VuY2Ug
aGFwcGVuZWQ/DQoNCjUuIFNlY3Rpb24gNC4zLCBJIHRoaW5rIHNvbWUgb2YgdGhlc2UgZnVuY3Rp
b25zIG1pc3NlZCBzb21lIHBhcmFtZXRlcnMuDQoNClNob3VsZCBpdCBiZSBsaWtlIHRoaXM6DQoN
CiAgICBDb21wdXRlX05laWdoYm9yX1NQRnMoc2VsZiwgZmFpbF9pbnRmKSAvL3NlbGYncyBuZWln
aG9iciBpcyBjb21wdXRpbmcNCiAgICANCiAgICBDb21wdXRlX0V4dGVuZGVkX1BfU3BhY2Uoc2Vs
ZiwgZmFpbF9pbnRmKSAvL3NlbGYgaXMgY29tcHV0aW5nIEVQDQogICAgDQogICAgQ29tcHV0ZV9R
X1NwYWNlKGRlc3QsIGZhaWxfaW50ZikgICAgLy9kZXN0IGlzIGNvbXB1dGluZyBRDQogICAgDQog
ICAgSW50ZXJzZWN0X0V4dGVuZGVkX1BfYW5kX1FfU3BhY2Uoc2VsZiwgZGVzdCwgZmFpbF9pbnRm
KSAvL1BRIGlzIHBlciBmYWlsX2ludGYNCiAgICANCiAgICAgICAgICBDb21wdXRlX0V4dGVuZGVk
X1BfU3BhY2UoZmFpbF9pbnRmKQ0KICAgICAgICAgIGZvcmVhY2ggbm9kZSB5IGluIG5ldHdvcmsN
CiAgICAgICAgICAgICAgeS5pbl9leHRlbmRlZF9QX3NwYWNlID0gZmFsc2UNCiAgICAgICAgICAg
ICAgLy8gRXh0ZW5kIFAtc3BhY2UgdG8gdGhlIFAtc3BhY2VzIG9mIGFsbCByZWFjaGFibGUNCiAg
ICAgICAgICAgICAgLy8gbmVpZ2hib3Vycw0KICAgICAgICAgICAgICBmb3JlYWNoIGludGVyZmFj
ZSBpbnRmIGluIHNlbGYNCiAgICAgICAgICAgICAgICAgIGlmIChpbnRmLnJlbW90ZV9ub2RlICE9
IGZhaWxfaW50Zi5yZW1vdGVfbm9kZSkgICAgLypJbiBicm9hZGNhc3QgbmV0d29yaywgDQogICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICppZiB0aGUgbGluayBkb3duIGl0IHdpbGwgYWZm
ZWN0IGFsbCBub2RlcyBvbiB0aGlzIGxpbmssIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAqbm90IG9ubHkgb25lIHJlbW90ZV9ub2RlLiAqLw0KICAgICAgICAgICAgICAgICAgICAg
IGlmICggRF9vcHQoaW50Zi5yZW1vdGVfbm9kZSwgeSkgPA0KICAgICAgICAgICAgICAgICAgICAg
ICAgICAgRF9vcHQoaW50Zi5yZW1vdGVfbm9kZSwgc2VsZikgKw0KICAgICAgICAgICAgICAgICAg
ICAgICAgICAgRF9vcHQoc2VsZixmYWlsX2ludGYucmVtb3RlX25vZGUpICsNCiAgICAgICAgICAg
ICAgICAgICAgICAgICAgIERfb3B0KGZhaWxfaW50Zi5yZW1vdGVfbm9kZSx5KSApDQogICAgICAg
ICAgICAgICAgICAgICAgIHkuaW5fZXh0ZW5kZWRfUF9zcGFjZSA9IHRydWUgICAgDQoNCg0KRXJp
Yw0KDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQq3orz+
yMs6IHJ0Z3dnIFtydGd3Zy1ib3VuY2VzQGlldGYub3JnXSC0+rHtIHJ0Z3dnLXJlcXVlc3RAaWV0
Zi5vcmcgW3J0Z3dnLXJlcXVlc3RAaWV0Zi5vcmddDQq3osvNyrG85DogMjAxM8TqMTHUwjI0yNUg
NDowMA0KytW8/sjLOiBydGd3Z0BpZXRmLm9yZw0K1vfM4jogcnRnd2cgRGlnZXN0LCBWb2wgMTA3
LCBJc3N1ZSAyMQ0KDQpTZW5kIHJ0Z3dnIG1haWxpbmcgbGlzdCBzdWJtaXNzaW9ucyB0bw0KICAg
ICAgICBydGd3Z0BpZXRmLm9yZw0KDQpUbyBzdWJzY3JpYmUgb3IgdW5zdWJzY3JpYmUgdmlhIHRo
ZSBXb3JsZCBXaWRlIFdlYiwgdmlzaXQNCiAgICAgICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9ydGd3Zw0Kb3IsIHZpYSBlbWFpbCwgc2VuZCBhIG1lc3NhZ2Ugd2l0aCBz
dWJqZWN0IG9yIGJvZHkgJ2hlbHAnIHRvDQogICAgICAgIHJ0Z3dnLXJlcXVlc3RAaWV0Zi5vcmcN
Cg0KWW91IGNhbiByZWFjaCB0aGUgcGVyc29uIG1hbmFnaW5nIHRoZSBsaXN0IGF0DQogICAgICAg
IHJ0Z3dnLW93bmVyQGlldGYub3JnDQoNCldoZW4gcmVwbHlpbmcsIHBsZWFzZSBlZGl0IHlvdXIg
U3ViamVjdCBsaW5lIHNvIGl0IGlzIG1vcmUgc3BlY2lmaWMNCnRoYW4gIlJlOiBDb250ZW50cyBv
ZiBydGd3ZyBkaWdlc3QuLi4iDQoNCg0KVG9kYXkncyBUb3BpY3M6DQoNCiAgIDEuIEktRCBBY3Rp
b246IGRyYWZ0LWlldGYtcnRnd2ctcmVtb3RlLWxmYS0wNC50eHQNCiAgICAgIChpbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmcpDQogICAyLiBGd2Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IN
CiAgICAgIGRyYWZ0LWlldGYtcnRnd2ctcmVtb3RlLWxmYS0wNC50eHQgKFN0ZXdhcnQgQnJ5YW50
KQ0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KTWVzc2FnZTogMQ0KRGF0ZTogRnJpLCAyMiBOb3YgMjAx
MyAxMzoxMzozMyAtMDgwMA0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnDQpUbzogaS1k
LWFubm91bmNlQGlldGYub3JnDQpDYzogcnRnd2dAaWV0Zi5vcmcNClN1YmplY3Q6IEktRCBBY3Rp
b246IGRyYWZ0LWlldGYtcnRnd2ctcmVtb3RlLWxmYS0wNC50eHQNCk1lc3NhZ2UtSUQ6IDwyMDEz
MTEyMjIxMTMzMy4zMTEzNC43MzQ0MS5pZHRyYWNrZXJAaWV0ZmEuYW1zbC5jb20+DQpDb250ZW50
LVR5cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9InV0Zi04Ig0KDQoNCkEgTmV3IEludGVybmV0LURy
YWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rv
cmllcy4NCiBUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBSb3V0aW5nIEFyZWEgV29y
a2luZyBHcm91cCBXb3JraW5nIEdyb3VwIG9mIHRoZSBJRVRGLg0KDQogICAgICAgIFRpdGxlICAg
ICAgICAgICA6IFJlbW90ZSBMRkEgRlJSDQogICAgICAgIEF1dGhvcihzKSAgICAgICA6IFN0ZXdh
cnQgQnJ5YW50DQogICAgICAgICAgICAgICAgICAgICAgICAgIENsYXJlbmNlIEZpbHNmaWxzDQog
ICAgICAgICAgICAgICAgICAgICAgICAgIFN0ZWZhbm8gUHJldmlkaQ0KICAgICAgICAgICAgICAg
ICAgICAgICAgICBNaWtlIFNoYW5kDQogICAgICAgICAgICAgICAgICAgICAgICAgIE5pbmcgU28N
CiAgICAgICAgRmlsZW5hbWUgICAgICAgIDogZHJhZnQtaWV0Zi1ydGd3Zy1yZW1vdGUtbGZhLTA0
LnR4dA0KICAgICAgICBQYWdlcyAgICAgICAgICAgOiAyNA0KICAgICAgICBEYXRlICAgICAgICAg
ICAgOiAyMDEzLTExLTIyDQoNCkFic3RyYWN0Og0KICAgVGhpcyBkcmFmdCBkZXNjcmliZXMgYW4g
ZXh0ZW5zaW9uIHRvIHRoZSBiYXNpYyBJUCBmYXN0IHJlLXJvdXRlDQogICBtZWNoYW5pc20gZGVz
Y3JpYmVkIGluIFJGQzUyODYgdGhhdCBwcm92aWRlcyBhZGRpdGlvbmFsIGJhY2t1cA0KICAgY29u
bmVjdGl2aXR5IGZvciBsaW5rIGZhaWx1cmVzIHdoZW4gbm9uZSBjYW4gYmUgcHJvdmlkZWQgYnkg
dGhlIGJhc2ljDQogICBtZWNoYW5pc21zLg0KDQoNCg0KVGhlIElFVEYgZGF0YXRyYWNrZXIgc3Rh
dHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6DQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1pZXRmLXJ0Z3dnLXJlbW90ZS1sZmENCg0KVGhlcmUncyBhbHNvIGEgaHRtbGl6
ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1pZXRmLXJ0Z3dnLXJlbW90ZS1sZmEtMDQNCg0KQSBkaWZmIGZyb20gdGhlIHByZXZpb3VzIHZl
cnNpb24gaXMgYXZhaWxhYmxlIGF0Og0KaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9
ZHJhZnQtaWV0Zi1ydGd3Zy1yZW1vdGUtbGZhLTA0DQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBt
YXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0K
dW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29s
cy5pZXRmLm9yZy4NCg0KSW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9u
eW1vdXMgRlRQIGF0Og0KZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCg0KDQoN
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpNZXNzYWdlOiAyDQpEYXRlOiBGcmks
IDIyIE5vdiAyMDEzIDIxOjE2OjA5ICswMDAwDQpGcm9tOiBTdGV3YXJ0IEJyeWFudCA8c3Ricnlh
bnRAY2lzY28uY29tPg0KVG86ICJydGd3Z0BpZXRmLm9yZyIgPHJ0Z3dnQGlldGYub3JnPiwgInJ0
Z3dnLWNoYWlyc0B0b29scy5pZXRmLm9yZyINCiAgICAgICAgPHJ0Z3dnLWNoYWlyc0B0b29scy5p
ZXRmLm9yZz4NClN1YmplY3Q6IEZ3ZDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KICAg
ICAgICBkcmFmdC1pZXRmLXJ0Z3dnLXJlbW90ZS1sZmEtMDQudHh0DQpNZXNzYWdlLUlEOiA8NTI4
RkM5OTkuNzAwMDUwMUBjaXNjby5jb20+DQpDb250ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJz
ZXQ9InV0Zi04IjsgRm9ybWF0PSJmbG93ZWQiDQoNCg0KIEZyb20gbXkgcHJldmlvdXMgZW1haWws
IHlvdSB3aWxsIHNlZSB0aGF0IEkgZGlkDQpldmVyeXRoaW5nIHRoYXQgd2FzIG1pbnV0ZWQgYXQg
dGhlIElFVEYgbWVldGluZw0KZXhjZXB0IHRoZSBleHRyYSBzaW0sIHdoaWNoIEkgaGF2ZSBub3Qg
YmVlbiBwcm92aWRlZA0Kd2l0aC4NCg0KQXMgZHV0eSBlZGl0b3IsIEkgdGhpbmsgdGhhdCB3ZSBh
cmUgbm93IHJlYWR5DQpmb3IgV0cgTGFzdCBDYWxsIG9uIHRoaXMgZHJhZnQuDQoNCi0gU3Rld2Fy
dA0KDQotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tDQpTdWJqZWN0OiAgICAgICAg
TmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1pZXRmLXJ0Z3dnLXJlbW90ZS1sZmEt
MDQudHh0DQpEYXRlOiAgIEZyaSwgMjIgTm92IDIwMTMgMTM6MTM6MzQgLTA4MDANCkZyb206ICAg
PGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZz4NClRvOiAgICAgTWlrZSBTaGFuZCA8aW1jLnNoYW5k
QGdtYWlsLmNvbT4sIFN0ZWZhbm8gUHJldmlkaQ0KPHNwcmV2aWRpQGNpc2NvLmNvbT4sICJTbyBO
aW5nIiA8bmluZy5zb0B0YXRhY29tbXVuaWNhdGlvbnMuY29tPiwgTmluZw0KU28gPG5pbmcuc29A
dGF0YWNvbW11bmljYXRpb25zLmNvbT4sIENsYXJlbmNlIEZpbHNmaWxzDQo8Y2ZpbHNmaWxAY2lz
Y28uY29tPiwgU3Rld2FydCBCcnlhbnQgPHN0YnJ5YW50QGNpc2NvLmNvbT4NCg0KDQoNCkEgbmV3
IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1pZXRmLXJ0Z3dnLXJlbW90ZS1sZmEtMDQudHh0DQpoYXMg
YmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFN0ZXdhcnQgQnJ5YW50IGFuZCBwb3N0ZWQg
dG8gdGhlDQpJRVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOiAgICAgICAgZHJhZnQtaWV0Zi1y
dGd3Zy1yZW1vdGUtbGZhDQpSZXZpc2lvbjogICAgICAgIDA0DQpUaXRsZTogICAgICAgICAgIFJl
bW90ZSBMRkEgRlJSDQpDcmVhdGlvbiBkYXRlOiAgIDIwMTMtMTEtMjINCkdyb3VwOiAgICAgICAg
ICAgcnRnd2cNCk51bWJlciBvZiBwYWdlczogMjQNClVSTDogICAgICAgICAgICAgaHR0cDovL3d3
dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1ydGd3Zy1yZW1vdGUtbGZhLTA0
LnR4dA0KU3RhdHVzOiAgICAgICAgICBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWlldGYtcnRnd2ctcmVtb3RlLWxmYQ0KSHRtbGl6ZWQ6ICAgICAgICBodHRwOi8vdG9vbHMu
aWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXJ0Z3dnLXJlbW90ZS1sZmEtMDQNCkRpZmY6ICAgICAg
ICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi1ydGd3Zy1y
ZW1vdGUtbGZhLTA0DQoNCkFic3RyYWN0Og0KICAgIFRoaXMgZHJhZnQgZGVzY3JpYmVzIGFuIGV4
dGVuc2lvbiB0byB0aGUgYmFzaWMgSVAgZmFzdCByZS1yb3V0ZQ0KICAgIG1lY2hhbmlzbSBkZXNj
cmliZWQgaW4gUkZDNTI4NiB0aGF0IHByb3ZpZGVzIGFkZGl0aW9uYWwgYmFja3VwDQogICAgY29u
bmVjdGl2aXR5IGZvciBsaW5rIGZhaWx1cmVzIHdoZW4gbm9uZSBjYW4gYmUgcHJvdmlkZWQgYnkg
dGhlIGJhc2ljDQogICAgbWVjaGFuaXNtcy4NCg0KDQoNCg0KDQpQbGVhc2Ugbm90ZSB0aGF0IGl0
IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9u
DQp1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRv
b2xzLmlldGYub3JnLg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQouDQoNCg0KDQotLS0tLS0t
LS0tLS0tLSBuZXh0IHBhcnQgLS0tLS0tLS0tLS0tLS0NCkFuIEhUTUwgYXR0YWNobWVudCB3YXMg
c2NydWJiZWQuLi4NClVSTDogPGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9y
dGd3Zy9hdHRhY2htZW50cy8yMDEzMTEyMi82MDQ3ZDE5Yi9hdHRhY2htZW50Lmh0bWw+DQoNCi0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpTdWJqZWN0OiBEaWdlc3QgRm9vdGVyDQoN
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpydGd3ZyBt
YWlsaW5nIGxpc3QNCnJ0Z3dnQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3J0Z3dnDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCkVu
ZCBvZiBydGd3ZyBEaWdlc3QsIFZvbCAxMDcsIElzc3VlIDIxDQoqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKg==
