[Isis-wg] draft-lz-isis-relax-interfaces-limit-00

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Mon, 15 July 2013 21:51 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A57111E8219 for <isis-wg@ietfa.amsl.com>; Mon, 15 Jul 2013 14:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ob92sNuWleS5 for <isis-wg@ietfa.amsl.com>; Mon, 15 Jul 2013 14:51:30 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id A049911E822A for <isis-wg@ietf.org>; Mon, 15 Jul 2013 14:51:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1438; q=dns/txt; s=iport; t=1373925084; x=1375134684; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=2aaRtQvVMnqOac5/ipkttdVCTfEJIs67RKwigVl7zs0=; b=lJjwnxZjNK52KnebQgPDlV4Eh8BtOSf4l5iVlAVqdG/RmubKeeFfBR8/ vLL1ZpgBe8iPqUa3x1u/P2pdzY8ruf6HXtnb3658sGCqJ45ZTXQdkh06L 0ztFZ0LKoQ8oMLrQae94W5BTsJfoyNtZtFdYQOr2p+PKvkZpWrK7yjspb 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAGFu5FGtJXG+/2dsb2JhbABagwY0T8FcgRMWdIIlAQQ6PxIBKhRCJgEEAQ0NE4d1DLYwji0SdDGDEm0DmQWQJIMSgWkBHiA
X-IronPort-AV: E=Sophos;i="4.89,671,1367971200"; d="scan'208";a="232159416"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-9.cisco.com with ESMTP; 15 Jul 2013 21:51:17 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6FLpGPo011766 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Jul 2013 21:51:16 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.116]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Mon, 15 Jul 2013 16:51:16 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "linchangwang.04414@h3c.com" <linchangwang.04414@h3c.com>, "zhanghf@h3c.com" <zhanghf@h3c.com>, "vishwas.manral@hp.com" <vishwas.manral@hp.com>
Thread-Topic: draft-lz-isis-relax-interfaces-limit-00
Thread-Index: Ac6BogGr+t4mWtNBQsKf8gWcjol8Og==
Date: Mon, 15 Jul 2013 21:51:15 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F13443F20@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.67.88]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: [Isis-wg] draft-lz-isis-relax-interfaces-limit-00
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2013 21:51:42 -0000

Folks -

In regards to your recent draft submission:

http://tools.ietf.org/html/draft-lz-isis-relax-interfaces-limit-00

You state that the solution described long ago in http://tools.ietf.org/html/draft-ietf-isis-wg-255adj-02

"...suffers from restrictions required to maintain interoperability with systems that do not support the extensions."

Please elaborate on what these restrictions are and what interoperability issues have been seen in the field.

To my knowledge the problem you are trying to solve does not exist.

Also, in regards to your proposed solution, if you advertise IS-neighbors in the extended LSPs you will find this is not fully interoperable with ISs which do not support the proposed extension. This is why RFC 3786 originally proposed two operating modes. In mode 1 (fully interoperable w legacy systems) the only IS-neighbor which could be advertised in extended LSPs was a neighbor to the Originating IS. In Mode 2 this restriction was removed but it required a change in the SPF algorithm and therefore the entire network needed to be upgraded.  In RFC 5311 (which obsoleted RFC 3786) Mode 2 was removed and only Mode 1 is supported. But your proposal REQUIRES that extended LSPs advertise the IS-neighbors which were formed using the additional system-id (otherwise 2-way connectivity check will fail). This is NOT supported by RFC 5311.

   Les