[homenet] Comments on src-based routing in general

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 29 July 2013 08:44 UTC

Return-Path: <alexandru.petrescu@gmail.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 60EB521F9FBD for <homenet@ietfa.amsl.com>; Mon, 29 Jul 2013 01:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.032
X-Spam-Level:
X-Spam-Status: No, score=-10.032 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 XbTOetfmPH70 for <homenet@ietfa.amsl.com>; Mon, 29 Jul 2013 01:44:50 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id B2C1421F9F8F for <homenet@ietf.org>; Mon, 29 Jul 2013 01:44:42 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r6T8if1v002065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <homenet@ietf.org>; Mon, 29 Jul 2013 10:44:41 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r6T8ie30017797 for <homenet@ietf.org>; Mon, 29 Jul 2013 10:44:40 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.86.8]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r6T8iRxq013388 for <homenet@ietf.org>; Mon, 29 Jul 2013 10:44:40 +0200
Message-ID: <51F62B6B.4090709@gmail.com>
Date: Mon, 29 Jul 2013 10:44:27 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: homenet@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [homenet] Comments on src-based routing in general
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: Mon, 29 Jul 2013 08:44:57 -0000

Hello,

I wanted to make a few informal comments following the J. Chroboczek
presentation of "Source-specific Routing"
draft-boutier-homenet-source-specific-routing-00
today at Berlin IETF Homenet WG mtg.

It is tempting to formalize the prefix and IPv6 addresses into sets and
subsets and relationships between them.  But that relies on an
assumption that 'longest-prefix match' algorithm is precisely known.  It
is not, there is no RFC about it AFAIK.  There are many fuzzy aspects in
the implementation of longest-prefix match (e.g. to disambiguate between
ifaces).

Given that, it is next to impossible to come up with a specification
which is src-based routing (instead of dst-based).

About the problem: I heard said the problem being to ISPs present in the
same homenet, and need to forward the packet to the right ISP based on
the src address.  If that is so, then a first step to realize it would
be to send _some_ traffic to an ISP and the rest to the other.  That
could be still achieved with dst-based routing, but with specific routes
(i.e. for services specific to that ISP use that dst-based specific route).

About the question whether this shows up somewhere else than in
homenets.  One other protocol which uses mandatory src-based routing is
Proxy Mobile IPv6 (the MAG needs it).  One would make sure that way of
doing src-based routing is compatible to homenet.

Two-cents worth,

Alex