[Isis-wg] Support of "IP External ReachabilityInformation" TLV in L1 LSP

[Rajesh Saluja]

This is a multi-part message in MIME format.
--------------C94A52F37C99EEC1385B1C14
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Jeff Learman wrote:

> I find the following statement a little scary:
>
> > Including all examples of things that can cause
> > routing loops would make any document unreadable, IMHO.
>
> This seems like the antithesis of interoperability.
>
> I strongly recommend that any implementation options
> that can cause interoperability problems (such as persistent
> routing loops) be clearly identified, so that a purchaser
> can know whether or not equipment from different vendors
> will work together in a network.  Are there really a lot
> of these?
>
> Note that there are a number of temporary situations that
> can cause routing loops.  I'm not talking about these,
> because they're not interoperability problems, they're
> characteristics of the routing protocol that can be analyzed
> and discussed without referring to specific implementations.
>
> Best Regards,
> Jeff
>

I agree with Jeff. I do not know of any other persistent loop problems in IISIS.
If there are more, they should be documented. The issue I am raising is definitely
an interoperability issue and it is because of difference in what spec says and
what has been implemented. It would be better to fix this.

Thanks,
Rajesh



--------------C94A52F37C99EEC1385B1C14
Content-Type: text/x-vcard; charset=us-ascii;
 name="rsaluja.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Rajesh Saluja
Content-Disposition: attachment;
 filename="rsaluja.vcf"

begin:vcard 
n:Saluja;Rajesh
tel;fax:978 288 4837
tel;work:978 288 7791
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:rsaluja@baynetworks.com
fn:Rajesh Saluja
end:vcard

--------------C94A52F37C99EEC1385B1C14--