Re: Please review draft-ietf-zeroconf-ipv4-linklocal-15.txt !

Erik Guttman <[email protected]> Tue, 22 Jun 2004 14:46:03 +0200 (CEST)
Newsgroups gmane.ietf.zeroconf
Message-ID <[email protected]>

Folks,

This is additional material to what I posted already, concerning
changing DEFEND_INTERVAL to ANNOUNCE_WAIT in the last paragraph of
section 2.2.1

Suggested change:

  WAS
    If, by DEFEND_INTERVAL seconds after the transmission of the last ARP
    probe no conflicting ARP Reply or ARP probe has been received, then
    the host has successfully claimed the desired IPv4 Link-Local
    address.

  note: DEFEND_INTERVAL is 10 seconds

  BECOMES
    If, by ANNOUNCE_WAIT seconds after the transmission of the last ARP
    probe no conflicting ARP Reply or ARP probe has been received, then
    the host has successfully claimed the desired IPv4 Link-Local
    address.

  note:  ANNOUNCE_WAIT is proposed to be 1 second
   section: 2.2.1
   rationale: fixes a problem
   impact:

     This seriously impacts the protocol in that the host will wait either
     10 seconds or 1 second after the final probe in order to configure
     the address.  [I suggest that 2 seconds is the correct value here,
     as this is consistent with earlier work and only changed due to an
     editorial oversight.]

Note that in early drafts of the protocol, this was '2 seconds':

draft-ietf-zeroconf-ipv4-linklocal-07.txt

   If, by two seconds after the transmission of the last ARP probe
   no conflicting ARP reply has been received, then the host has
   successfully claimed the desired link-local address.

draft-ietf-zeroconf-ipv4-linklocal-12.txt &
draft-ietf-zeroconf-ipv4-linklocal-13.txt &
draft-ietf-zeroconf-ipv4-linklocal-14.txt

   If, by PROBE_MAX seconds after the transmission of the last ARP probe
   no conflicting ARP Reply or ARP probe has been received, then the
   host has successfully claimed the desired Link-Local IPv4 address.

  where:    PROBE_MAX              2 seconds

draft-ietf-zeroconf-ipv4-linklocal-15.txt

   If, by DEFEND_INTERVAL seconds after the transmission of the last ARP
   probe no conflicting ARP Reply or ARP probe has been received, then
   the host has successfully claimed the desired IPv4 Link-Local
   address.

  where:  DEFEND_INTERVAL     10 seconds  (after probes, wait for defense)