IETF Logo Mail Archive

Re: [homenet] source routing requirements for routing protocols

Lorenzo Colitti <lorenzo@google.com> Mon, 29 July 2013 13:36 UTC

Return-Path: <lorenzo@google.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 338AF21F9302 for <homenet@ietfa.amsl.com>; Mon, 29 Jul 2013 06:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 N84SuAjhokBG for <homenet@ietfa.amsl.com>; Mon, 29 Jul 2013 06:36:06 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 1A85A21F9B0C for <homenet@ietf.org>; Mon, 29 Jul 2013 06:36:03 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id er7so9200753obc.4 for <homenet@ietf.org>; Mon, 29 Jul 2013 06:36:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=EpDzk3BwLfvoSNmS1VqbE27kX3l/fNJ29U3i8VDvBHE=; b=lbedzVkEeCpm8uqP6vVAzSzgzVob0Uj3mNtuNa+ASv/cB5KYZGKWj2IGoSNxCtCDy4 kUgAxmlPiYtI75hW8ubfo5g23iAwOGhvqRpzYoKX31Owbv+zMsO8IAWUy+49eNc0ejw+ phlQrgo7Rt1mn+Kv6uYd0r0nFlzp7BN3nmH28OwZ6uO/cFlwXiVWxqaQz7N0I+sbzWbX /1wSlNrlWLgKsy3kalinewhN7kjzx2IwMUK+hqmP46Bw9W//7y8ixZ+Den0Ym6da+AGp ERbXh1P/t6wLZ+urs+C8NBdUZum+bE9j2PAk/ocmYEW/4E/Fji/aB1FoQvRm/a/p0CO1 HpmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=EpDzk3BwLfvoSNmS1VqbE27kX3l/fNJ29U3i8VDvBHE=; b=j5ZhGe1LFB8/t4YSHAW0k7hWyQiV9RQ/uVTzYPw5Llh0BP/fJSzzDG8JoqsOhoV2UN QdAUQ5WfNMQPg4sLujcsYa7VgBZisynt0nrl2CTdUKMzRtRs3mBmAqThTdXJZ1o47xB2 1KwEWWAxJZ/Dx+AVaZv0EXJ5ip2w9VLSpF+Nsl0kNy24o3OXE/QWmziN6ivxHH9Jc5Tq QCLIE6vlTv931iiv9h/j88OGy75/wOeHVgGR7dR3WhhQho9g2IWp60ellMZosRr2AfrJ C0VIQ0ih0WPQMWE5NfFcfu1AEQYTEZ77Tyvlm4obBEEoDMbJczIRvxY6fuY3ezk0A3JU jRmA==
X-Received: by 10.43.181.136 with SMTP id pi8mr21010623icc.10.1375104962250; Mon, 29 Jul 2013 06:36:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.228.144 with HTTP; Mon, 29 Jul 2013 06:35:41 -0700 (PDT)
In-Reply-To: <10806.1375097238@sandelman.ca>
References: <6856.1375095717@sandelman.ca> <10806.1375097238@sandelman.ca>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 29 Jul 2013 15:35:41 +0200
Message-ID: <CAKD1Yr1E3ai9bP4OXbNCH=v_uCXpK_Yf2_cccAYwAv2b8v7e8A@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="001a11c35008cdf48204e2a692fe"
X-Gm-Message-State: ALoCoQmVqrnAI2QqRn8a42b0QrdxqOu+74mtyGP2zDo/FtydhnOXTYErxIhHCTcnBwwViMXod7kNWRT/Y+J7s1l2X5ORnRpZIh8kQxbeoAtbWSR/h+iBnJaBNIIh0ZNtros3Ik+W0+kIRvNuJ9ilyBuZysm4G2KkhaBvwhChWkbqKHRESVcluikhOLW84aJV8JgX4jVG1+cu
Cc: "homenet@ietf.org" <homenet@ietf.org>, David Lamparter <equinox@diac24.net>
Subject: Re: [homenet] source routing requirements for routing protocols
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 13:36:07 -0000

On Mon, Jul 29, 2013 at 1:27 PM, Michael Richardson
<mcr+ietf@sandelman.ca>wrote:

> 1) if we are going to introduce a new route to deal with the
>    conflict, then the routing protocol must be able to express
>    what might appear to be multiple routes to the same dest/prefix.
>

I believe the routes only need to be local and do not need to appear on the
wire and in the routing protocol (in fact, they don't even need to be
stored locally; the draft claims that they can be recalculated when adding
/ removing real routes from the FIB).

As regards the reason for existence of the routes themselves, David
Lamparter tells me that he has in fact gotten the Linux IPv6 source routing
code (the mythical CONFIG_IPV6_SUBTREES?) to work on 3.8. Attempting to CC
a randomly-found email address I have for him so he can comment directly.
David?

v2.23.0 | Report a Bug | By Email