Skip to main content

Homenet IS-IS Profile
draft-lamparter-homenet-isis-profile-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Author David Lamparter
Last updated 2015-07-22
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-lamparter-homenet-isis-profile-00
Homenet Working Group                                       D. Lamparter
Internet-Draft                                                    NetDEF
Intended status: Standards Track                           July 22, 2015
Expires: January 23, 2016

                         Homenet IS-IS Profile
                draft-lamparter-homenet-isis-profile-00

Abstract

   This (pointer) document describes the neccessary bits and pieces of
   IS-IS that a homenet targeted implementation would need to implement.

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 January 23, 2016.

Copyright Notice

   Copyright (c) 2015 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

Lamparter               Expires January 23, 2016                [Page 1]
Internet-Draft           Homenet IS-IS Profile                 July 2015

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Required specifications . . . . . . . . . . . . . . . . . . .   2
   3.  Parameter choices . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Optional additions for IPv4 operation . . . . . . . . . . . .   4
   5.  Security and Privacy Considerations . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Homenet, as seen by the IETF Homenet working group, operates as a set
   of IPv6 routers performing source/destination based routing.  Since
   an arbitrary number of routers in an arbitrary dynamic topology is to
   be supported, a dynamic routing protocol is needed.  This document
   outlines how to apply IS-IS for this.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Required specifications

   The following (parts of) specifications MUST be implemented for a
   homenet IS-IS router:

   Parts of ISO 10589-2002: [IS-IS]

   o  Section 6.1, Level 1 Intermediate System

   o  Section 6.2, bullet a) - broadcast subnetworks

   o  Section 6, remainder (6.3 - 6.8.4)

   o  Section 7, Level 1 IS function only

      *  exclude Section 7.2.2 (replaced by wide metrics)

      *  exclude Section 7.2.9 (Level 2 interactions)

      *  exclude Section 7.2.10 (Partition repair)

Lamparter               Expires January 23, 2016                [Page 2]
Internet-Draft           Homenet IS-IS Profile                 July 2015

      *  exclude Section 7.4 (Forwarding process), replaced by IPv6
         forwarder behavior

   o  Sections 8.2 and 8.4

   o  Section 9, excluding PDU types specific to Level 2 operation

   o  Sections 10.1 and 10.2

   Generally speaking, a homenet IS-IS implementation needs to operate
   in a network consisting purely of Level 1 Intermediate Systems.

   The following updates to the IS-IS specification:

   o  [RFC5120], M-ISIS: Multitopology Routing

   o  [RFC5303], IS-IS 3-way Adjacency TLV

   o  [RFC5305], IS-IS Extensions for Traffic Engineering

      *  wide metrics and IP prefix encoding

      *  Sub-TLVs 3, 9, 10, 11, 18 not required

   o  [RFC5308], Routing IPv6 with IS-IS

   o  [I-D.liu-isis-auto-conf], IS-IS Autoconfiguration

   o  [I-D.baker-ipv6-isis-dst-src-routing], IS-IS IPv6 Source/
      Destination Routing

   o  [I-D.lamparter-isis-p2mp], IS-IS Point to Multipoint operation

   o  [I-D.franke-isis-over-ipv6], IS-IS over IPv6

   And, finally, IPv6 source/destination routing behavior as specified
   in [I-D.lamparter-rtgwg-dst-src-routing].

3.  Parameter choices

   Most configuration parameters are specified in
   [I-D.liu-isis-auto-conf] as part of IS-IS autoconfiguration.

   Homenet uses the following additional parameter choices:

   o  IPv6 is routed in M-ISIS topology with MTID #2.

   o  IPv4, if supported, is routed in the base topology (MTID #0).

Lamparter               Expires January 23, 2016                [Page 3]
Internet-Draft           Homenet IS-IS Profile                 July 2015

4.  Optional additions for IPv4 operation

   Supporting IPv4 for backwards compatibility requires implementation
   of [RFC1195].

5.  Security and Privacy Considerations

   This document has no independent security or privacy concerns.  Those
   in the referenced documents apply.

6.  Acknowledgements

   Juliusz Chroboczek pointed out the need for this document.

7.  References

7.1.  Normative References

   [I-D.baker-ipv6-isis-dst-src-routing]
              Baker, F., "IPv6 Source/Destination Routing using IS-IS",
              draft-baker-ipv6-isis-dst-src-routing-01 (work in
              progress), August 2013.

   [I-D.franke-isis-over-ipv6]
              Franke, C., "IS-IS over IPv6", draft-franke-isis-over-
              ipv6-00 (work in progress), July 2015.

   [I-D.lamparter-isis-p2mp]
              Franke, C. and D. Lamparter, "IS-IS Point-to-Multipoint
              operation", draft-lamparter-isis-p2mp-00 (work in
              progress), July 2015.

   [I-D.lamparter-rtgwg-dst-src-routing]
              Lamparter, D., "Destination/Source Routing", draft-
              lamparter-rtgwg-dst-src-routing-01 (work in progress),
              June 2015.

   [I-D.liu-isis-auto-conf]
              Liu, B., Decraene, B., Farrer, I., and M. Abrahamsson,
              "ISIS Auto-Configuration", draft-liu-isis-auto-conf-05
              (work in progress), June 2015.

   [IS-IS]    ISO/IEC, "Intermediate System to Intermediate System
              Intra-Domain Routing Exchange Protocol for use in
              Conjunction with the Protocol for Providing the
              Connectionless-mode Network Service (ISO 8473)", ISO/IEC
              10589:2002, Second Edition, 2002.

Lamparter               Expires January 23, 2016                [Page 4]
Internet-Draft           Homenet IS-IS Profile                 July 2015

   [RFC1195]  Callon, R.W., "Use of OSI IS-IS for routing in TCP/IP and
              dual environments", RFC 1195, DOI 10.17487/RFC1195,
              December 1990, <http://www.rfc-editor.org/info/rfc1195>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC5120]  Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi
              Topology (MT) Routing in Intermediate System to
              Intermediate Systems (IS-ISs)", RFC 5120, February 2008.

   [RFC5303]  Katz, D., Saluja, R., and D. Eastlake, "Three-Way
              Handshake for IS-IS Point-to-Point Adjacencies", RFC 5303,
              October 2008.

   [RFC5305]  Li, T. and H. Smit, "IS-IS Extensions for Traffic
              Engineering", RFC 5305, DOI 10.17487/RFC5305, October
              2008, <http://www.rfc-editor.org/info/rfc5305>.

   [RFC5308]  Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, October
              2008.

7.2.  Informative References

   [I-D.sarikaya-6man-sadr-overview]
              Sarikaya, B., "Overview of Source Address Dependent
              Routing", draft-sarikaya-6man-sadr-overview-01 (work in
              progress), September 2014.

Author's Address

   David Lamparter
   NetDEF
   Leipzig  04103
   Germany

   Email: david@opensourcerouting.org

Lamparter               Expires January 23, 2016                [Page 5]