Re: Soliciting viewpoints and comments on source/destination routing

Jeroen Massar <jeroen@massar.ch> Fri, 14 November 2014 22:32 UTC

Return-Path: <jeroen@massar.ch>
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 525831AD049 for <rtgwg@ietfa.amsl.com>; Fri, 14 Nov 2014 14:32:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] 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 itSoIlXx0srN for <rtgwg@ietfa.amsl.com>; Fri, 14 Nov 2014 14:32:27 -0800 (PST)
Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [46.20.246.101]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE90F1A1AA0 for <rtgwg@ietf.org>; Fri, 14 Nov 2014 14:32:27 -0800 (PST)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jeroen) by bastion.ch.unfix.org (Postfix) with ESMTPSA id 4F8041008709E; Fri, 14 Nov 2014 22:32:25 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=massar.ch; s=DKIM2009; t=1416004345; bh=+9u1dtkb+Cx/17OBQ4ZvYmjWHJ3OgNqAKrAR1JmFpqw=; h=Date:From:To:Subject:References:In-Reply-To; b=EFde4K2I4qWlJ6VX2I7TBZwPTazRW52Uupyx1R7rK/4lfXsV+QjYDl77hZcFDacqx KKiTiQ22UQwglhAfYCQQ0XhCtI1/5BSU8WwZqKXu86rnUG2bjGKcx1BkV9jNXN3qbr u5fsWMkWRBCdMfPvQo0qaKRZNKHykR+2W4acToVkFZwIAt1WeQR9Oz+S3EcuWWc0K4 CXoFeAYO944vOEH6kx06hRaPyss3SsceKTVINqiFePvYn+wxrd5w5GhlUKUzY6MT25 /OabU7vJ1kJK/o2TrJebISFoBfyue54D62PhyVfYNgrYRwiU0xpZoYbbcEoFY2nhTV 4brPifUFlI6LQ==
Message-ID: <546682F6.7070808@massar.ch>
Date: Fri, 14 Nov 2014 23:32:22 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: Soliciting viewpoints and comments on source/destination routing
References: <F4BF4405-D3E2-474A-A089-B4E896F094C2@cisco.com>
In-Reply-To: <F4BF4405-D3E2-474A-A089-B4E896F094C2@cisco.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtgwg/rzD7zkQ-HtZ2RrP-oIY_IQmbfl4
X-Mailman-Approved-At: Wed, 19 Nov 2014 10:24:28 -0800
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, 14 Nov 2014 22:32:29 -0000

On 2014-11-14 22:52, Fred Baker (fred) wrote:
> The chairs have asked me to solicit review and commentary on
> 
> https://datatracker.ietf.org/doc/draft-baker-rtgwg-src-dst-routing-use-cases
>
> 
https://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cases
> "Requirements and Use Cases for Source/Destination Routing", Fred
> Baker, 2014-10-21
> 
> There are at least two layers of discussion. One, as a working group,
> do we agree that there is a problem to solve here?

Not really as there are lots of people who are getting multiple
upstreams and are doing source based routing.

As an example:
http://blog.altimos.de/2013/07/ipv6-source-address-routing-with-multiple-uplinks-sixxs/

Mostly a 'solved' problem thus. But it depends on your use cases.

> I obviously think there is, but I am one voice.

I think it might be worthwhile documenting the pro/cons and how to do
things.

But RFC3178 does a reasonable job at that already, hence maybe you could
add to RFC3178 in the form of a 'bis' variant?

Greets,
 Jeroen