Re: [Isis-wg] Fwd: New Version Notification for draft-franke-isis-over-ipv6-00.txt

Karsten Thomann <> Sun, 05 July 2015 18:38 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 9FA651ABD3E for <>; Sun, 5 Jul 2015 11:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pst-_oBKG-sQ for <>; Sun, 5 Jul 2015 11:38:12 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5577F1ABD38 for <>; Sun, 5 Jul 2015 11:38:12 -0700 (PDT)
Received: from linne.localnet ( by linfreserv (Axigen) with (ECDHE-RSA-AES256-SHA encrypted) ESMTPSA id 07FC0D; Sun, 5 Jul 2015 20:38:01 +0200
From: Karsten Thomann <>
Date: Sun, 05 Jul 2015 20:37:49 +0000
Message-ID: <2393971.qq7UIhEPqS@linne>
User-Agent: KMail/ (Windows/6.1; KDE/4.13.3; i686; git-a6cb62d; 2014-12-22)
In-Reply-To: <>
References: <> <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nextPart1739081.a8bX9vACiG"
Content-Transfer-Encoding: 7Bit
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 6
Archived-At: <>
Subject: Re: [Isis-wg] Fwd: New Version Notification for draft-franke-isis-over-ipv6-00.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 05 Jul 2015 18:38:14 -0000

Hi Christian,

some comments from my side:
I'm not sure if we really need this encapsulation, as there are not many links layers left, but you 
should at least mention that it avoids some problems with switches dropping ISIS LSPs if it's 
encapsulated in IPv6

In my opinion you should also add to the IANA Considereations section that the allocation of the 
protocol number should be modified to something like "ISIS over IP" or only "ISIS", as it is a bit 
misleading that it's currently "ISIS over IPv4"

Also there should be at least some information about the coexistence of "standard" ISIS Routers 
and "ISIS over IPv6" routers. Example would be to allow only one ISIS encapsulation per interface 
and ignore the other (Router running ISIS over IPv6 with adjacencies would ignore standard ISIS 
PDUs and vice versa)
If you're not specifying it there arise problems with DIS routers.

/of transmitted the PDUs/of transmitted PDUs/

Karsten Thomann

Am Freitag, 3. Juli 2015, 20:50:41 schrieb Christian Franke:
> Dear all,
> In this new draft, I'd like to propose an alternative method to transmit
> IS-IS PDUs. By using IPv6 as transport, it makes the protocol less
> dependent on specific link-layers.
> There are two interoperable free software implementations for this which
> will be published until the IETF in Prague and which will be presented
> there during Bits-N-Bites.
> I'd be happy to receive your feedback.
> -Christian
> -------- Forwarded Message --------
> Subject: New Version Notification for draft-franke-isis-over-ipv6-00.txt
> Date: Fri, 03 Jul 2015 11:27:10 -0700
> From:
> To: Christian Franke <>rg>, Christian Franke
> <>
> A new version of I-D, draft-franke-isis-over-ipv6-00.txt
> has been successfully submitted by Christian Franke and posted to the
> IETF repository.
> Name:		draft-franke-isis-over-ipv6
> Revision:	00
> Title:		IS-IS over IPv6
> Document date:	2015-07-03
> Group:		Individual Submission
> Pages:		5
> URL:
> Status:
> Htmlized:
> Abstract:
>    In this draft, a method to transmit IS-IS PDUs as IPv6 packets is
>    described.  While the default encapsulation of IS-IS is specified
>    directly on top of the link-layer, making it necessary for IS-IS to
>    be specified for each link-layer it should be used on, the proposed
>    method allows for IS-IS to run on any link-layers supporting IPv6.
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> The IETF Secretariat