IETF Logo Mail Archive

[homenet] Egress Routing Discussion

"Fred Baker (fred)" <fred@cisco.com> Thu, 21 February 2013 17:22 UTC

Return-Path: <fred@cisco.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 6103A21F8CA7 for <homenet@ietfa.amsl.com>; Thu, 21 Feb 2013 09:22:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.462
X-Spam-Level:
X-Spam-Status: No, score=-110.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2+on-uZTDUGn for <homenet@ietfa.amsl.com>; Thu, 21 Feb 2013 09:22:24 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 2D31721F8CAC for <homenet@ietf.org>; Thu, 21 Feb 2013 09:22:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2588; q=dns/txt; s=iport; t=1361467344; x=1362676944; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=VM7sgl2JAz/EpcOcIzJiSBcE8UN7yy/Zrq2WxguNS5U=; b=Bi4EH1l+PADYCPdcG7jrAyFwBFOCgwbkHgyEznby9f9UUVO0P1AGFKg5 sA587AMO6YK+InvBlXjn1EXoXOYDSeufBxKy/b3gq+qQBtfQs3eXe7ZUX 62t0jEpHx/X5314PR0yfusuViNwIeoA9ISOfUJSiWYTxrKOVh932A9Guk Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAMJWJlGtJXG+/2dsb2JhbABFwHyBBBZzgiEBBDo/EgEqFEInBA4NiAoMvxKNPQqBFjGCZmEDl1OPQYMHgWkJFx4
X-IronPort-AV: E=Sophos;i="4.84,710,1355097600"; d="scan'208";a="179710636"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-7.cisco.com with ESMTP; 21 Feb 2013 17:22:23 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r1LHMMqe010310 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Feb 2013 17:22:22 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Thu, 21 Feb 2013 11:22:22 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Thread-Topic: Egress Routing Discussion
Thread-Index: AQHOEFgCGK9BIkojDUCI/aEwNxU6xw==
Date: Thu, 21 Feb 2013 17:22:22 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B79DAEF@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.247.253]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DFBECB43A23A1842A894041B060BB695@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "isis-chairs@tools.ietf.org" <isis-chairs@tools.ietf.org>, "ospf-chairs@tools.ietf.org" <ospf-chairs@tools.ietf.org>
Subject: [homenet] Egress Routing Discussion
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: Thu, 21 Feb 2013 17:22:25 -0000

In Atlanta, Mark asked Lorenzo and I to put together a draft of an approach to source/destination, and especially egress, routing. I pulled together a plan of attack that I applied to both IPv4 and IPv6, and to both IS-IS and OSPF and sought review from a limited list including Lorenzo; this includes capabilities for at least one other use case I'm looking at. Mark asked me to cut that down to make things separately implementable (which they would be anyway, but to make it apparent). So I have broken it into components.

So we have several drafts in play at this IETF.

Shu Yang documented his work in Quagga, in which he implemented source/destination routing as a multi-topology routing model.

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, 18-Feb-13

Ole Troan and Lorenzo Colitti documented their model, which is strictly egress routing based on the OSPF AS-prefix-LSA and the assumption of automated prefix allocation. This is not multi-topology; it in effect tags the default route advertised as a route from an alternate universe.

http://tools.ietf.org/html/draft-troan-homenet-sadr
  "IPv6 Multihoming with Source Address Dependent Routing (SADR)", Ole
  Troan, Lorenzo Colitti, 18-Feb-13

I have documented my approach, which provides the generalized concept, is built into the routing protocols IS-IS and OSPF, and also addresses at least one other "tagged routing" option, which is to look at flow labels.

http://tools.ietf.org/html/draft-baker-ipv6-isis-automatic-prefix
  "Automated prefix allocation in IS-IS", Fred Baker, 18-Feb-13

http://tools.ietf.org/html/draft-baker-ipv6-isis-dst-flowlabel-routing
  "Using IS-IS with Role-Based Access Control", Fred Baker, 17-Feb-13

http://tools.ietf.org/html/draft-baker-ipv6-isis-dst-src-routing
  "IPv6 Source/Destination Routing using IS-IS", Fred Baker, 17-Feb-13

http://tools.ietf.org/html/draft-baker-ipv6-ospf-dst-flowlabel-routing
  "Using OSPFv3 with Role-Based Access Control", Fred Baker, 17-Feb-13

http://tools.ietf.org/html/draft-baker-ipv6-ospf-dst-src-routing
  "IPv6 Source/Destination Routing using OSPFv3", Fred Baker, 17-Feb-13

http://tools.ietf.org/html/draft-baker-ipv6-ospf-extensible
  "Extensible OSPF LSAs", Fred Baker, 17-Feb-13

I'll say why I think mine is the correct approach in another email, as I imagine my colleagues will for theirs. But the working group should consider the question.

v2.23.0 | Report a Bug | By Email