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

The use of the symbol WATCH_WAIT in draft 15 is incorrect. This issue is =
independent of whether the symbol is called WATCH_WAIT or =
DEFEND_INTERVAL.

The purpose of a symbolic name is to allow changes to the value to =
accommodate different situations without changes in the text of the =
document.

The symbol name must be the same for all networks but it's value may =
change from network to network. The current text only defines the =
*symbol name* for IEEE802 networks, rather than defining its value.

Proposed change in section 2.5

   (b) If a host currently has active TCP connections or other reasons
   to prefer to keep the same IPv4 address, and it has not seen any
   other conflicting ARP packets recently (for IEEE 802, within the last
                                           ^^^^^^^^^^^^^^
                                               DELETE
   WATCH_WAIT seconds) then it MAY elect to attempt to defend its
   address, by recording the time that the conflicting ARP packet was
   received, and then broadcasting one single ARP announcement, giving
   its own IP and hardware addresses as the sender addresses of the ARP.
   Having done this, the host can then continue to use the address
   normally without any further special action.  However, if this is not
   the first conflicting ARP packet the host has seen, and the time
   recorded for the previous conflicting ARP packet is recent (within
   WATCH_WAIT seconds for IEEE 802) then the host MUST immediately cease
                     ^^^^^^^^^^^^^
                         DELETE
   using this address and configure a new IPv4 Link-Local address as
   described above...
  =20
Becomes

   (b) If a host currently has active TCP connections or other reasons
   to prefer to keep the same IPv4 address, and it has not seen any
   other conflicting ARP packets recently (within the last
   WATCH_WAIT seconds) then it MAY elect to attempt to defend its
   address, by recording the time that the conflicting ARP packet was
   received, and then broadcasting one single ARP announcement, giving
   its own IP and hardware addresses as the sender addresses of the ARP.
   Having done this, the host can then continue to use the address
   normally without any further special action.  However, if this is not
   the first conflicting ARP packet the host has seen, and the time
   recorded for the previous conflicting ARP packet is recent (within
   WATCH_WAIT seconds) then the host MUST immediately cease
   using this address and configure a new IPv4 Link-Local address as
   described above...

and in section 9

   WATCH_WAIT          10 seconds  (time to continue to defend your =
address,
                                    for IEEE 802 networks)

Becomes

   WATCH_WAIT          10 seconds for IEEE 802 networks
                       currently unspecified for other network types
                       (time to continue to defend your address)


regards,
Philip Nye