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

Hi,

In order to be able to treat an IP network as a link type between
TRILL routers, TRILL needs to be able to send TRILL IS-IS packets
between TRILL routers in a manner that does not interact with use of
IS-IS within the IP network. So I've thought a fair amount about IS-IS
over IP. There has been a TRILL WG draft on this for some time.

I think you are right that the correct thing for IPv6 is to use the
port's IPv6 address as the SNPA.

Your isis-over-ipv6 draft says that SNPAs don't occur on the wire,
just within IS-IS routers. But I believe they occur in IS-IS Hellos.
See TLV #6, referred to as "IIS Neighbors" in IANA's TLV table and
shown in ISO/IEC 10589-2002 Second Edition in Clause 9.5, item "a",
page 68. I just checked and that IS-IS TLV is specified as being
limited to 48-bit SNPAs. Looking further, the ISO/IEC standard seems
to have a TLV #7, shown in item "b" on that page for specifying
neighbor SNPAs and that TLV #7 does have an SNPA length field so they
could be some other length. Maybe I'm confused, but, it appears that
the IETF has re-assigned TLV #7 to be Instance Identifier (RFC6822).
Since you say there are interoperable implementations of your draft,
am I confused or do they have some solution to the above problem?
Perhaps, since Hellos are link local, the implementations just use
fixed size 128-bit SNPAs in their IIS Neighbors TLVs over IPv6,
contrary to the ISO specification, and this was left out of the draft?

(This is not a problem for TRILL over IP as TRILL uses the TRILL
Neighbor TLV (#145, RFC 7176) which does provide an SNPA length
field.)

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Fri, Jul 3, 2015 at 2:50 PM, Christian Franke
<chris@opensourcerouting.org> wrote:
> 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: internet-drafts@ietf.org
> To: Christian Franke <chris@opensourcerouting.org>, Christian Franke
> <chris@opensourcerouting.org>
>
>
> 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:
> https://www.ietf.org/internet-drafts/draft-franke-isis-over-ipv6-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-franke-isis-over-ipv6/
> Htmlized:       https://tools.ietf.org/html/draft-franke-isis-over-ipv6-00
>
>
> 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 tools.ietf.org.
>
> The IETF Secretariat
>
>
>
>
>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg
>