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

Karsten Thomann <> Thu, 09 July 2015 19:33 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 06F391A002A for <>; Thu, 9 Jul 2015 12:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.961
X-Spam-Status: No, score=-0.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, 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 uuMfxtP-SzPt for <>; Thu, 9 Jul 2015 12:33:38 -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 E32371A001C for <>; Thu, 9 Jul 2015 12:33:37 -0700 (PDT)
Received: from linne.localnet ( by linfreserv (Axigen) with (ECDHE-RSA-AES256-SHA encrypted) ESMTPSA id 3E9C7B; Thu, 9 Jul 2015 21:33:27 +0200
From: Karsten Thomann <>
To: Christian Franke <>
Date: Thu, 09 Jul 2015 21:33:25 +0000
Message-ID: <5617720.UqPZcug5lP@linne>
User-Agent: KMail/ (Windows/6.1; KDE/4.13.3; i686; git-a6cb62d; 2014-12-22)
In-Reply-To: <>
References: <> <2393971.qq7UIhEPqS@linne> <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nextPart1611502.Ho4S8u9ID1"
Content-Transfer-Encoding: 7Bit
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 5
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: Thu, 09 Jul 2015 19:33:40 -0000

Hello Christian,

an example of a switch dropping ISIS packets is a GS2200 from Zyxel, it is even mentioned in the 
release notes of the (older) firmware.
In the pdf document page 12, fixed bug number 4.

Some additional comments:
3.1 SNPA
I would use the link local IP as a tie breaker, as on the subnet are only routers able to establish 
adjacencies if they are capable of ISIS over IPv6 and there is no backwards compatibillity needed 
in this case.

PPP for example makes sure there are unique Interface identifiers within the IPV6CP negotiation 
and Ethernet with DAD, protecting users against their own misconfiguration would be (almost) 

3.2 MTU
Why you're restricting the packet size to 1280bytes?
The ISIS Packets SHOULD be padded up to the maximum mtu size to detect mtu mismatches on 
the links. It is right not to use fragmentation, but this shouldn't require to limit the size to 1280 
Maybe add to the fragmentation related sentence that all fragmented ISIS packets MUST be 


Am Montag, 6. Juli 2015, 21:04:02 schrieb Christian Franke:
> Hello Karsten,
> thank you for your input. I have made appropriate changes to the draft,
> they can be seen here:
> On 07/05/2015 10:37 PM, Karsten Thomann wrote:
> > 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
> The homenet working group is currently in the process of selecting a
> routing protocol to use. In that discussion some people voiced concern
> that IS-IS would not be a good option since it was specified on top of
> layer 2 instead of layer 3. This draft and the demo implementation were
> done to address these concerns. On the one hand by showing that it
> doesn't take much to run IS-IS on top of layer 3 and on the other hand
> to provide a standardized way to do so, should the need arise.
> I was not aware that switches existed which drop IS-IS PDUs, although
> it's not that hard to imagine that there are switches which are broken
> in that way. Could you name examples for switches showing this behavior?
> -Christian