IETF Logo Mail Archive

Re: [Isis-wg] draft-noguchi-isis-protocol-topology-00.txt

Noguchi Kay <kay@ipinfusion.com> Thu, 06 February 2003 20:36 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03338 for <isis-wg-archive@odin.ietf.org>; Thu, 6 Feb 2003 15:36:25 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h16Kh0u29830 for isis-wg-archive@odin.ietf.org; Thu, 6 Feb 2003 15:43:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Kh0p29827 for <isis-wg-web-archive@optimus.ietf.org>; Thu, 6 Feb 2003 15:43:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03302 for <isis-wg-web-archive@ietf.org>; Thu, 6 Feb 2003 15:35:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Kfkp29664; Thu, 6 Feb 2003 15:41:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Ke9p29626 for <isis-wg@optimus.ietf.org>; Thu, 6 Feb 2003 15:40:09 -0500
Received: from giga.kayz.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03215 for <isis-wg@ietf.org>; Thu, 6 Feb 2003 15:33:03 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=giga.kayz.org) by giga.kayz.org with esmtp (Exim 3.35 #1 (Debian)) id 18gsl1-00055e-00; Thu, 06 Feb 2003 12:36:27 -0800
Message-ID: <87wukdgn91.wl@giga.kayz.org>
From: Noguchi Kay <kay@ipinfusion.com>
To: Naiming Shen <naiming@redback.com>
Cc: Noguchi Kay <kay@ipinfusion.com>, stefano previdi <sprevidi@cisco.com>, isis-wg@ietf.org
Subject: Re: [Isis-wg] draft-noguchi-isis-protocol-topology-00.txt
In-Reply-To: <20030205221638.66D9F3E9B28@prattle.redback.com>
References: <kay@ipinfusion.com>
X-Mailer: Wanderlust/2.8.1
MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi")
Content-Type: text/plain; charset="US-ASCII"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 06 Feb 2003 12:36:26 -0800

Hi Naiming,

This is Kay.

>  ] > NLPIDs for both v4 and v6. the adjacency status will be determined by
>  ] > the MT status.
>  ] 
>  ] 	But how to adjacent with legacy IPv4/IPv6 IS-IS software which
>  ] 	enables IPv4 routing but disables IPv6 routing.
>  ] 
>  ] 	In this case, legacy software means the software doesn't support
>  ] 	M-ISIS capability.
>  ] 
>  ] 	That kind of legacy software doesn't allow to make adjacent
>  ] 	with neighbors which contains IPv4 and IPv6 NLPIDs in IIH
>  ] 	Protocols Supported TLV.
> 
> do you have information on which vendor's isis software actually does
> that (not forming adjacency because neighbor supports more than my
> own nlpid) ?

	Before the implementation topic, could you point out
	which spec states it and how?

Thank you,

								kay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg

v2.38.3 | Report a Bug | By Email | System Status