Re: RFC1812 (fwd)

MegaZone (megazone@livingston.com)
Wed, 27 Nov 1996 01:49:20 -0800 (PST)

Once upon a time Bradley Dunn shaped the electrons to say...
>* Section 3.3.4
>* The MTU of each logical interface MUST be configurable within the
>* range of legal MTUs for the interface.
>How do you set the MTU on ether0?

Someone shoot me down if I'm wrong - but isn't the MTU for ethernet a
fixed value?

>* Section 4.2.3.4
>* Routers MUST support discontiguous subnetworks.
>Does Livingston support discontiguous subnets?

We will in 3.5. It's on PM-3s now, other boxes in the next few weeks.

>* Section 7.2.1
>* A router that implements any routing protocol (other than static
>* routes) MUST IMPLEMENT OSPF (see Section [7.2.2]). A router MAY
>* implement additional IGPs.
>**
>Is OSPF implemented in released, general-availability software?

On PM-3s yes. Same as last answer.

>* Section 7.4
>* A router that supports a dynamic routing protocol MUST allow static
>* routes to be defined with any metric valid for the routing protocol
>* used. The router MUST provide the ability for the user to specify a
>* list of static routes that may or may not be propagated through the
>* routing protocol.
>How does one control what static routes are distributed into RIP?

You can't right now (don't think you can in 3.5 either, but I'm not sure.)

>**
>* Section 7.5.2
>* Filtering of routing information allows control of paths used by a
>* router to forward packets it receives. A router should be selective
>* in which sources of routing information it listens to and what routes
>* it believes. Therefore, a router MUST provide the ability to
>* specify:
>*
>* o On which logical interfaces routing information will be accepted

This we do.

>* and which routes will be accepted from each logical interface.

This we don't do.

>* o Whether all routes or only a default route is advertised on a
>* logical interface.

Hmm. I think what we do now is all routes except default or all routes AND
default. But not JUST default. I'll have to check on that.

>Some of the requirements I wasn't sure about and didn't feel like testing
>(like ICMP redirects, ICMP address mask request/reply, ICMP router
>discovery, SNMP stuff, etc...).

I'll read the RFC as soon as I get time (probably over this long weekend)
it is a hefty one.

-MZ

--
Livingston Enterprises - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com
For support requests: support@livingston.com  <http://www.livingston.com/> 
Snail mail: 4464 Willow Road, Pleasanton, CA 94588