IPv6 Source/Destination Routing using IS-IS
draft-baker-ipv6-isis-dst-src-routing-06

Document Type Active Internet-Draft (candidate for isis WG)
Last updated 2016-10-24 (latest revision 2016-10-18)
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         F.J. Baker
Internet-Draft                                              D. Lamparter
Intended status: Standards Track                                  NetDEF
Expires: April 21, 2017                                 October 18, 2016

              IPv6 Source/Destination Routing using IS-IS
                draft-baker-ipv6-isis-dst-src-routing-06

Abstract

   This note describes the changes necessary for IS-IS to route IPv6
   traffic from a specified prefix to a specified prefix.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 21, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

Baker & Lamparter        Expires April 21, 2017                 [Page 1]
Internet-Draft      IS-IS Source/Destination Routing        October 2016

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Theory of Routing . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Notation  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Dealing with ambiguity  . . . . . . . . . . . . . . . . .   4
     2.3.  Multi-topology Routing  . . . . . . . . . . . . . . . . .   5
   3.  Protocol encoding for IPv6 Source Prefix information  . . . .   6
     3.1.  Source Prefix sub-TLV . . . . . . . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Correctness considerations . . . . . . . . . . . . .   8
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   This specification defines how to exchange destination/source routing
   [I-D.ietf-rtgwg-dst-src-routing] information in IS-IS for IPv6
   [RFC5308] routing environments.  To this extent, a new sub-TLV for an
   IPv6 [RFC2460] Source Prefix is added, and Multi Topology Routing
   [RFC5120] is employed to address compatibility and isolation
   concerns.

   The router MUST implement the Destination/Source Routing mechanism
   described in [I-D.ietf-rtgwg-dst-src-routing].  This implies not
   simply routing "to a destination", but routing "to that destination
   AND from a specified source".  The obvious application is egress
   routing, as required for a multihomed entity with a provider-
   allocated prefix from each of several upstream networks.  Traffic
   within the network could be source/destination routed as well, or
   could be implicitly or explicitly routed from "any prefix", ::/0.
   Other use cases are described in
   [I-D.baker-rtgwg-src-dst-routing-use-cases].  If a FIB contains a
   route to a given destination from one or more prefixes not including
   ::/0, and a given packet destined there that has a source address
   that is in none of them, the packet in effect has no route, just as
   if the destination itself were not in the route table.

Baker & Lamparter        Expires April 21, 2017                 [Page 2]
Show full document text