Subject: [Isis-wg] isis-dst-src-routing WG adoption?

From: David Lamparter <[email-masked]>
Date: Wed, 4 Nov 2015 06:35:25 +0100

Hello IS-IS WG,

as the source/destination routing draft in rtgwg has been adopted as a
WG document, I'd like to proceed towards WG adoption (and early alloc)
on the IS-IS version.  The document has neither seen significant changes
lately nor are there open discussion items.  Also, Fred has confirmed
that consensus in v6ops is recommending dst/src routing for medium-size
multihomed enterprises on multiple PA IPv6 prefixes.

There is no on-site presentation planned for this @ Yokohama;  I'm under
the belief the adoption call can be done directly on this mailing list.

For reference, the relevant diff from -03 to -04 is pasted below.  I
did some text fudging on the multitopology use.

Cheers,

-David

diff:
@@ -267,10 +267,21 @@ IPv6 management    5       TBD-MT5
               MTID TBD-MT5 to carry associated reachability TLVs.</t>
         </list></t>
 
-        <t>It should be noted that implementing M-ISIS is thus a prerequirement
-          for supporting the protocol outlined in this document.  Even
-          installations that previously used only MTID 0 (i.e. no M-ISIS) will
-          need to start using MTID TBD-MT0.</t>
+        <t>Note that the different topology ID is the sole and only mechanism
+          of both capability detection and backwards compatibility.  D/S
+          routing will operate correctly if D/S routing information is put in
+          the same topology as non-D/S information, but adding an IS that does
+          not support D/S routing will then -undetectably- lead to incorrect
+          routing decisions, possibly including loops.</t>
+
+        <t>As this compatibility mechanism is not considered optional, M-ISIS
+          MUST therefore be implemented for supporting the protocol outlined in
+          this document.  Even installations that previously used only MTID 0
+          (i.e. no M-ISIS) would need to start using MTID TBD-MT0.</t>
+
+        <t>Systems that use topology IDs different than the values reserved by
+          IANA should apply the considerations from this section
+          analogously.</t>
       </section>
     </section>

----- Forwarded message from [email-masked] -----
Subject: New Version Notification for draft-baker-ipv6-isis-dst-src-routing-04.txt
Message-ID: <[email-masked]>
Date: Mon, 19 Oct 2015 11:46:06 -0700

A new version of I-D, draft-baker-ipv6-isis-dst-src-routing-04.txt
has been successfully submitted by David Lamparter and posted to the
IETF repository.

Name:		draft-baker-ipv6-isis-dst-src-routing
Revision:	04
Title:		IPv6 Source/Destination Routing using IS-IS
Document date:	2015-10-19
Group:		Individual Submission
Pages:		10
URL:            https://www.ietf.org/internet-drafts/draft-baker-ipv6-isis-dst-src-routing-04.txt
Status:         https://datatracker.ietf.org/doc/draft-baker-ipv6-isis-dst-src-routing/
Htmlized:       https://tools.ietf.org/html/draft-baker-ipv6-isis-dst-src-routing-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-baker-ipv6-isis-dst-src-routing-04

Abstract:
   This note describes the changes necessary for IS-IS to route IPv6
   traffic from a specified prefix to a specified prefix.

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

----- End forwarded message -----