[OSPF] Extensible LSAs
"Fred Baker (fred)" <firstname.lastname@example.org> Fri, 03 May 2013 17:10 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E999B21F99DC for <email@example.com>; Fri, 3 May 2013 10:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-108 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([22.214.171.124]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DRCDscPd3owo for <firstname.lastname@example.org>; Fri, 3 May 2013 10:10:24 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [126.96.36.199]) by ietfa.amsl.com (Postfix) with ESMTP id 1D25E21F9896 for <email@example.com>; Fri, 3 May 2013 08:58:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; firstname.lastname@example.org; l=4837; q=dns/txt; s=iport; t=1367596711; x=1368806311; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=3XgXnlaq1T3aUCX/yIyv6zNvc4+jIedBTKxPF19UL4I=; b=gasJQ9mZKA3aJlBhA/VLbe6HLyKkHpzxy1qsxjHgk6OAHkNaJ4AUlPqN lmrE5jRecgvoenm9iNWsjvX+OWcUkQArWQeGZdhPpRkLnWCKLBmciFvsz YSnNtyFR9ktUaUo5VJ2AmXIFVwVZn7fz50nNBpK4otshUwphcZiANw9Y4 M=;
X-IronPort-AV: E=Sophos;i="4.87,605,1363132800"; d="scan'208";a="206140649"
Received: from rcdn-core2-6.cisco.com ([188.8.131.52]) by rcdn-iport-8.cisco.com with ESMTP; 03 May 2013 15:58:16 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [184.108.40.206]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r43FwG93006561 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <email@example.com>; Fri, 3 May 2013 15:58:16 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-rcd-x07.cisco.com ([220.127.116.11]) with mapi id 14.02.0318.004; Fri, 3 May 2013 10:58:15 -0500
From: "Fred Baker (fred)" <firstname.lastname@example.org>
To: "email@example.com" <firstname.lastname@example.org>
Thread-Topic: Extensible LSAs
Date: Fri, 03 May 2013 15:58:15 +0000
Content-Type: text/plain; charset="us-ascii"
Subject: [OSPF] Extensible LSAs
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 17:10:47 -0000
As I started at the past IETF meeting, there has been some additional work on extensible LSAs, egress routing, and building access control into routing (which in my mind is primarily useful in data centers). Interested in your remarks. http://tools.ietf.org/html/draft-acee-ospfv3-lsa-extend "OSPFv3 LSA Extendibility", Acee Lindem, Sina Mirtorabi, Abhay Roy, Fred Baker, 1-May-13 http://tools.ietf.org/html/draft-baker-ipv6-ospf-dst-flowlabel-routing diff: http://tinyurl.com/ct9wn6g "Using OSPFv3 with Role-Based Access Control", Fred Baker, 2-May-13 http://tools.ietf.org/html/draft-baker-ipv6-ospf-dst-src-routing diff: http://tinyurl.com/ctcshzb "IPv6 Source/Destination Routing using OSPFv3", Fred Baker, 2-May-13 To diff from the previous drafts, if you want one, you want to do this following. This is what the tiny url gets you. http://tools.ietf.org/rfcdiff? url1=http://tools.ietf.org/id/draft-baker-ipv6-ospf-dst-src-routing-00.txt &url2=http://tools.ietf.org/id/draft-baker-ipv6-ospf-dst-src-routing-02.txt http://tools.ietf.org/rfcdiff? url1=http://tools.ietf.org/id/draft-baker-ipv6-ospf-dst-flowlabel-routing-00.txt &url2=http://tools.ietf.org/id/draft-baker-ipv6-ospf-dst-flowlabel-routing-02.txt I'll save you one question, though. I get asked frequently why these didn't follow MT-OSPF or MI-OSPF, and commented on this in the meeting in Orlando. The reason is that neither is fundamentally a topology or instance question. MT-OSPF OSPF presumes that some non-null set of links in a topology are either absent from some of the topologies or that metrics differ, so that routes in one topology differ from those in another. This is about qualification of routes - a scalable access list or policy route, if you will. One could integrate it with MT-OSPF within a network, but the most immediate use cases aren't helped by it. Consider egress routing in a multihomed network, the use case presented by homenet. We have a network with two or more upstreams, each of which allocates a PA prefix to the network. In homenet's case and probably for small networks, The technique described in draft-ietf-ospf-ospfv3-autoconfig-02.txt is used to allocate a /64 prefix from each PA prefix to each LAN in the domain. Links derive their metrics from bandwidth, and might in effect use hop count. So the different "topologies" are identical. What differs between them is that there are multiple default routes, and due to BCP 38 implementation upstream, we want to direct traffic using a given ISP's PA prefix to that ISP. So we want to attach a source prefix to each default (AS-external, most likely, or at least an intra-as-prefix) route. Internal routes, in that case, will likely accept "any" source including external sources, which is to say that they are advertised without a source prefix. The concept of source/destination routing is extensible to intra-area or inter-area routing as well as egress routing. The use cases are most likely something about security - there is some domain within the network that only certain other parts of the network are permitted to reach. That is, of course, more hypothetical at this point. As to the use of the flow label, in a multi-tenant data center, that is a *lot* of topologies. I think it has scaling issues. As to Multi-Instance, suppose I put a set of VMs on a LAN that are part of one tenant and another set of VMs in a different tenant. Yes, I probably put them into different subnets. But how do instances actually help me there? They don't, really. What the SDN folks are doing right now is segregating the network using overlays - GRE tunnels, VLANs, or some such thing. That mostly has the effect of making it difficult for the network to do anything, or to optimize the application in any way from a network perspective. I'd like to keep the application stuff at the application layer and enable the network to support the application. So to my way of thinking, the applications should think in terms of communicating with each other as instances - names, addresses given by some controller, or whatever - and are given those by the controller that created them using whatever protocol it uses. Part of what they are given, one of half a dozen parameters they are already given, is a tenant number for access control to put into the flow label. The controller can similarly configure the OSPF instance on their favorite router to advertise the subnet(s) in question with those tenant numbers. Voila, they have communication that is supported in the network architecture, and with this they are given the communication isolation they're looking for.
- [OSPF] Extensible LSAs Fred Baker (fred)