Homenet Working Group D. Lamparter
Internet-Draft NetDEF
Intended status: Standards Track October 19, 2015
Expires: April 21, 2016

Homenet IS-IS Profile


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 April 21, 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

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]

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:

And, finally, IPv6 source/destination routing behavior as specified in [I-D.ietf-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:

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. and D. Lamparter, "IPv6 Source/Destination Routing using IS-IS", Internet-Draft draft-baker-ipv6-isis-dst-src-routing-04, October 2015.
[I-D.franke-isis-over-ipv6] Franke, C., "IS-IS over IPv6", Internet-Draft draft-franke-isis-over-ipv6-00, July 2015.
[I-D.ietf-rtgwg-dst-src-routing] Lamparter, D., "Destination/Source Routing", Internet-Draft draft-ietf-rtgwg-dst-src-routing-00, October 2015.
[I-D.lamparter-isis-p2mp] Franke, C., Lamparter, D. and C. Hopps, "IS-IS Point-to-Multipoint operation", Internet-Draft draft-lamparter-isis-p2mp-01, October 2015.
[I-D.liu-isis-auto-conf] Liu, B., Decraene, B., Farrer, I., Abrahamsson, M. and L. Ginsberg, "ISIS Auto-Configuration", Internet-Draft draft-liu-isis-auto-conf-06, October 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.
[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual environments", RFC 1195, DOI 10.17487/RFC1195, December 1990.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, 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, DOI 10.17487/RFC5120, February 2008.
[RFC5303] Katz, D., Saluja, R. and D. Eastlake 3rd, "Three-Way Handshake for IS-IS Point-to-Point Adjacencies", RFC 5303, DOI 10.17487/RFC5303, October 2008.
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic Engineering", RFC 5305, DOI 10.17487/RFC5305, October 2008.
[RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, DOI 10.17487/RFC5308, October 2008.

7.2. Informative References

[I-D.sarikaya-6man-sadr-overview] Sarikaya, B. and M. Boucadair, "Source Address Dependent Routing and Source Address Selection for IPv6 Hosts: Problem Space Overview", Internet-Draft draft-sarikaya-6man-sadr-overview-08, August 2015.

Author's Address

David Lamparter NetDEF Leipzig, 04103 Germany EMail: david@opensourcerouting.org