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

Naiming Shen <naiming@redback.com> Wed, 05 February 2003 22:20 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 RAA13120 for <isis-wg-archive@odin.ietf.org>; Wed, 5 Feb 2003 17:20:06 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15MQF802041 for isis-wg-archive@odin.ietf.org; Wed, 5 Feb 2003 17:26:15 -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 h15MQFp02038 for <isis-wg-web-archive@optimus.ietf.org>; Wed, 5 Feb 2003 17:26:15 -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 RAA13109 for <isis-wg-web-archive@ietf.org>; Wed, 5 Feb 2003 17:19:35 -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 h15MOGp01945; Wed, 5 Feb 2003 17:24:16 -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 h15MJfp01796 for <isis-wg@optimus.ietf.org>; Wed, 5 Feb 2003 17:19:41 -0500
Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12959 for <isis-wg@ietf.org>; Wed, 5 Feb 2003 17:13:01 -0500 (EST)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43]) by prattle.redback.com (Postfix) with ESMTP id 66D9F3E9B28; Wed, 5 Feb 2003 14:16:38 -0800 (PST)
To: Noguchi Kay <kay@ipinfusion.com>
Cc: stefano previdi <sprevidi@cisco.com>, isis-wg@ietf.org
Subject: Re: [Isis-wg] draft-noguchi-isis-protocol-topology-00.txt
In-reply-to: Mail from Noguchi Kay <kay@ipinfusion.com> dated Wed, 05 Feb 2003 12:08:54 PST <877kceij6x.wl@giga.kayz.org>
From: Naiming Shen <naiming@redback.com>
Message-Id: <20030205221638.66D9F3E9B28@prattle.redback.com>
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: Wed, 05 Feb 2003 14:16:38 -0800

Kay,

 ] 
 ] >  ] > on a Lan media, just announce all the possible NLPIDs, but only MT ID
 for
 ] >  ] > IPv6.
 ] >  ] 
 ] >  ] 	Two questions for this.
 ] >  ] 
 ] >  ] 	1) How to get the "all the possible NLPIDs" and what is the val
ue
 ] >  ] 	   which M-ISIS software only support IPv6 puts in for this cas
e?
 ] >  ] 
 ] >  ] 	   IPv4 and IPv6 NLPIDs or IPv4 NLPID only?
 ] > 
 ] > 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) ?

thanks.

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

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