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

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

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]

• Section 6.1, Level 1 Intermediate System
• Section 6.2, bullet a) - broadcast subnetworks
• Section 6, remainder (6.3 - 6.8.4)
• 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)
  • exclude Section 7.4 (Forwarding process), replaced by IPv6 forwarder behavior

• Sections 8.2 and 8.4
• Section 9, excluding PDU types specific to Level 2 operation
• 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:

• [RFC5120], M-ISIS: Multitopology Routing
• [RFC5303], IS-IS 3-way Adjacency TLV
• [RFC5305], IS-IS Extensions for Traffic Engineering
  • wide metrics and IP prefix encoding
  • Sub-TLVs 3, 9, 10, 11, 18 not required

• [RFC5308], Routing IPv6 with IS-IS
• [I-D.liu-isis-auto-conf], IS-IS Autoconfiguration
• [I-D.baker-ipv6-isis-dst-src-routing], IS-IS IPv6 Source/Destination Routing
• [I-D.lamparter-isis-p2mp], IS-IS Point to Multipoint operation
• [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:

• IPv6 is routed in M-ISIS topology with MTID #2.
• IPv4, if supported, is routed in the base topology (MTID #0).

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

7.2. Informative References

Author's Address