Fix documentation for EVS types

diff --git a/man/man5/dictionary.5 b/man/man5/dictionary.5
index d685081..7b3b86d 100644 (file)
--- a/man/man5/dictionary.5
+++ b/man/man5/dictionary.5
@@ -10,7 +10,7 @@
 .RE
 .sp
 ..
-.TH dictionary 5 "16 Mar 2011"
+.TH dictionary 5 "12 Jun 2015"
 .SH NAME
 dictionary \- RADIUS dictionary file
 .SH DESCRIPTION
@@ -141,9 +141,6 @@ digit) are 1, 2, and 4.  The support values for the number of length
 octets (i.e. the second digit) are 0, 1, and 2.  Any combination of
 those values will work.
 
-You can also use "format=Extended-Vendor-Specific-1", through
-"format=Extended-Vendor-Specific-6".  These define VSAs in the
-"extended vendor-specific" space.
 .TP 0.5i
 .B BEGIN-VENDOR vendor-name
 Define the start of a block of Vendor-Specific attributes.  All of the
@@ -152,6 +149,12 @@ named vendor, until the block is closed by an "END-VENDOR" statement.
 
 This practice is preferred to placing the vendor name at the end of an
 \fIATTRIBUTE\fP  definition.
+
+For VSAs in the RFC 6929 "Extended vendor-specific" space, a format
+can be specified following the "vendor-name".  The format should be
+"format=Extended-Vendor-Specific-1", through
+"format=Extended-Vendor-Specific-6".  The matching "END-VENDOR" should
+just have the "vendor-name", without the format string.
 .TP 0.5i
 .B END-VENDOR vendor-name
 End a previously defined BEGIN-VENDOR block.  The "vendor-name" must match.
@@ -179,3 +182,4 @@ the attribute number should be used instead.
 .BR RFC2865,
 .BR RFC2866,
 .BR RFC2868
+.BR RFC6929