Re: [homenet] draft-boutier-homenet-source-specific-routing-00

Henning Rogge <hrogge@googlemail.com> Wed, 10 July 2013 14:56 UTC

Return-Path: <hrogge@googlemail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D6921F9A87 for <homenet@ietfa.amsl.com>; Wed, 10 Jul 2013 07:56:51 -0700 (PDT)
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 0ljhzx4RAPbJ for <homenet@ietfa.amsl.com>; Wed, 10 Jul 2013 07:56:50 -0700 (PDT)
Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 95DA621F9A1F for <homenet@ietf.org>; Wed, 10 Jul 2013 07:55:58 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id i13so7001199qae.20 for <homenet@ietf.org>; Wed, 10 Jul 2013 07:55:56 -0700 (PDT)
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=a6BECbqlaNoAfLsAvRtJKWwCoLp5DPRUpr8G+fP7ZuA=; b=PYumleGSlClTRkcVNDxDWEe1obb6xo2zWASPOOQtwc5v0M4e0+DJmngUR4dhKfAnyC okSKJbGJjqLIfPOJSM5Omf8jqY28vgZSUXLLrw2oDx68Wwbcv3GmnKuSBubqDJTPDLUr r4vue9dSEmYp00wXZGel2Y4eKeQC2GJ9YUxvYATS7BIraGdIwa71ZYwtMXCPXbwqSp1E nw3wWG9R9ipAWCqh/iQhk8PCIxFsWlcoWLg1vmjpy0YbJTos2IpZVvdNORfoTTVyQKRC aIr1FXYsJk3TdejrXE1O4aaWUsYrnVCs7NvkSBOzb2JifdEErCXjCsLzTMs+u72B2EAn mRqw==
X-Received: by 10.49.103.136 with SMTP id fw8mr25730766qeb.65.1373468156162; Wed, 10 Jul 2013 07:55:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.27.73 with HTTP; Wed, 10 Jul 2013 07:55:36 -0700 (PDT)
In-Reply-To: <87ppuq7epd.wl%jch@pps.univ-paris-diderot.fr>
References: <7ippuz4fb8.wl%jch@pps.univ-paris-diderot.fr> <CAKD1Yr3HZOJecNP6hE1yOBdGAxxXzMb5W23aPm9XhZv0fzKBUQ@mail.gmail.com> <7ibo6iw7ch.wl%jch@pps.univ-paris-diderot.fr> <CAKD1Yr0_yZsvw58hwjY++9RJT9urkKbX33zzwTjyWGTKK7RoVg@mail.gmail.com> <87ehbdi33a.wl%jch@pps.univ-paris-diderot.fr> <CAKD1Yr0x=j0tvkM2X8bGw4T538mnm7CV592GBHO76dSVhGLE7w@mail.gmail.com> <87wqp0lal6.wl%jch@pps.univ-paris-diderot.fr> <CAKD1Yr1knC76T14bcGY3kbYBMNfhvC9vACjguNaWCdRXxZ-4UA@mail.gmail.com> <87bo6bwzxn.wl%jch@pps.univ-paris-diderot.fr> <CAGnRvuqdhmYiUk5roQw0iNbyfm49Fixjo_44f_HcCLjKpZdYNA@mail.gmail.com> <8761wjwyt7.wl%jch@pps.univ-paris-diderot.fr> <CAGnRvuqX9fcYShdJVs9QocEdSOp3VJPHAnF1phF6XQ+V+NdEaQ@mail.gmail.com> <87ppuq7epd.wl%jch@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@googlemail.com>
Date: Wed, 10 Jul 2013 16:55:36 +0200
Message-ID: <CAGnRvup2yG6uw-qx2xmAbMLdOMADX7=nde12VP8ie0Lb26y7Ww@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "homenet@ietf.org" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] draft-boutier-homenet-source-specific-routing-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2013 14:56:51 -0000

On Wed, Jul 10, 2013 at 2:59 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> Still, as long as the different destinations for the source-routed
>> default-routes are in a source-route aware subnet it should work.
>
> Could you please clarify.  Have you identified another case where
> everything works out?

I am looking at the problem from the link-state point of view.

Lets assume there is a random mixture of source-routing aware and
non-aware routers. The only restriction is that there is a
source-aware path of routers between all gateways (gateways to the are
of course source-aware too).

There are two topologies in the network, the default topology all
routers participate in and a "source-aware" topology.

I see three cases when forwarding an IP packet with a "specific source
address" along the default route.

a) the router is not source-routing aware, which means it forwards the
packet along the normal default route
b) the router is source-routing aware, but has no source-aware path
towards the gateway. In this case it will still forward the packet
along the normal default route because it has no connected path to the
gateway selected by the source address (shortest path first result
should be empty).
c) the router is source-routing aware and has at least one path
towards the selected destination. In this case it will forward the
packet towards the selected gateway. The next hop will also be
source-aware, otherwise the link would not have been selected for the
"source-aware" topology.

Every non-source-aware default route will bring the traffic into the
source-aware region around the gateways, which mean they should reach
the desired gateway (even if it hit a different gateway first).

This should work with or without dropping data on the source-aware
topology on the non-source-aware routers.

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