home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zephyr.ens.tek.com!shaman!frip!andrew
- From: andrew@frip.WV.TEK.COM (Andrew Klossner)
- Newsgroups: comp.protocols.appletalk
- Subject: Re: AARP details clarification needed.
- Message-ID: <1660@shaman.wv.tek.com>
- Date: 27 Aug 92 00:00:48 GMT
- References: <1992Aug20.132650.6380@abbott.com>
- Sender: nobody@shaman.wv.tek.com
- Reply-To: andrew@frip.wv.tek.com
- Organization: Tektronix, Wilsonville, Oregon
- Lines: 35
-
- []
-
- "How many AARP Probe packets must be broadcast by the protocol
- stack attempting to verify that its tentative protocol address
- is not in use by any other node on the data link? [the book
- just says "a number" of probe pkts]"
-
- Send 10 packets at 0.2 second intervals. See the last paragraph on
- page 3-9.
-
- "From book: "If [an AARP] Response packet is not received
- "within a specified time interval," then AARP retransmits the
- Request packet. The question is, WHAT is the value of the
- time-out interval mentioned above? How long must AARP wait
- before retransmitting the Request packet?"
-
- Our products use the same parameters for AARP Request as for AARP
- Probe: we send 10 packets at 0.2 second intervals. This seems to work
- pretty well.
-
- "What is the timeout value that is allowed to expire before an
- AMT entry is aged?"
-
- We use 50 seconds, the maximum age for entries in the router cache.
- I'd be interested in what other implementations do.
-
- "Does a Macintosh end-node send the equivalent of a DECnet
- end-node's HELLO packet to refresh its router's AMT?"
-
- Not in general. PAP sessions exchange Tickle packets, which can have
- the side effect of keeping an AMT entry alive ... but they come at 60
- second intervals, which may be too long.
-
- -=- Andrew Klossner (andrew@frip.wv.tek.com)
- (uunet!tektronix!frip.WV.TEK!andrew)
-