[Babel-users] Fwd: [homenet] Egress Routing Discussion

[Dave Taht]

a bunch of thoughts towards src/dest routing from ietfers...

---------- Forwarded message ----------
From: Fred Baker (fred) <fred at cisco.com>
Date: Thu, Feb 21, 2013 at 9:22 AM
Subject: [homenet] Egress Routing Discussion
To: "homenet at ietf.org Group" <homenet at ietf.org>
Cc: "isis-chairs at tools.ietf.org" <isis-chairs at tools.ietf.org>, "
ospf-chairs at tools.ietf.org" <ospf-chairs at tools.ietf.org>


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.
_______________________________________________
homenet mailing list
homenet at ietf.org
https://www.ietf.org/mailman/listinfo/homenet



-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/babel-users/attachments/20130221/017de2ed/attachment.html>