From b0604a21108c2319904388115f049f2542ee5795 Mon Sep 17 00:00:00 2001
From: david <david@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Tue, 30 Aug 2011 20:26:12 +0000
Subject: [PATCH] Document link-local IPv6 zone IDs.

---
 docs/refguide.xml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/refguide.xml b/docs/refguide.xml
index f5c625dea..90ca02abe 100644
--- a/docs/refguide.xml
+++ b/docs/refguide.xml
@@ -214,6 +214,19 @@ for Internet surveys and research.</para>
 address or hostname.  CIDR and octet ranges aren't yet supported for
 IPv6.</para>
 
+<indexterm><primary>link-local IPv6 address</primary><see>IPv6 address, link-local</see></indexterm>
+<indexterm><primary>IPv6 address</primary><secondary>link-local</secondary></indexterm>
+<indexterm><primary>zone ID (IPv6 address)</primary></indexterm>
+<para>
+IPv6 addresses with non-global scope need to have a zone ID suffix. On
+Unix systems, this is a percent sign followed by an interface name; a
+complete address might be <literal>fe80::a8bb:ccff:fedd:eeff%eth0</literal>.
+On Windows, use an interface index number in place of an interface name:
+<literal>fe80::a8bb:ccff:fedd:eeff%1</literal>. You can see a list of
+interface indexes by running the command
+<command>netsh.exe interface ipv6 show interface</command>.
+</para>
+
 <para>Nmap accepts multiple host specifications on the command line,
 and they don't need to be the same type.  The command <command>nmap
 scanme.nmap.org 192.168.0.0/8 10.0.0,1,3-7.-</command> does what