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

Hi Naiming,

This is Kay.

>  ] 	So then, how to make adjacent between legacy ISIS software which
>  ] 	only supports IPv4 and M-ISIS capable software which only supports
>  ] 	IPv6?
>  ] 
>  ] 	Legacy IS-IS software requires same network layer topology support
>  ] 	in a area that is mensioned in RFC 1195.
> 
> 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 value
	   which M-ISIS software only support IPv6 puts in for this case?

	   IPv4 and IPv6 NLPIDs or IPv4 NLPID only?

	2) Some implementation checks if the IP Interface Address TLV is
	   in the same subnetwork or not to form an adjacency as
	   stated in draft-ietf-isis-ip-interoperable-00.txt section 13.

	   How does M-ISIS software which only supports IPv6 get the IPv4
	   subnetwork information for this link?

> don't put IPv4 IS pnode neighbor TLV in the LSP, so your IPv4
> neighbor will fail on backlink check during the SPF, thus will not
> use you as a nexthop.

	I know OSPFv2 specification has the "link back check" in 
	the spec, RFC 2328 section 16.1(p. 163).

	But I didn't see it in ISO 10589 nor RFC 1195.

	Could you point out where it's documented or is that an
	unwritten spec?

Thank you,

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