From 805efc7df1b33f65cae02a6d56c9679c59c7707c Mon Sep 17 00:00:00 2001
From: Julie Tibshirani <julie.tibshirani@elastic.co>
Date: Mon, 18 Jun 2018 08:21:41 -0700
Subject: [PATCH] Clarify that IP range data can be specified in CIDR notation.
 (#31374)

(cherry picked from commit 3f5ebb862de56efed4edcdb8b338590cb54be6f5)
---
 docs/reference/mapping/types/range.asciidoc | 24 +++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/docs/reference/mapping/types/range.asciidoc b/docs/reference/mapping/types/range.asciidoc
index 3013204e4ca21..a7ab6346176cb 100644
--- a/docs/reference/mapping/types/range.asciidoc
+++ b/docs/reference/mapping/types/range.asciidoc
@@ -168,6 +168,30 @@ This query produces a similar result:
 --------------------------------------------------
 // TESTRESPONSE[s/"took": 13/"took" : $body.took/]
 
+[[ip-range]]
+==== IP Range
+
+In addition to the range format above, IP ranges can be provided in
+https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation[CIDR] notation:
+
+[source,js]
+--------------------------------------------------
+PUT range_index/_mapping/_doc
+{
+  "properties": {
+    "ip_whitelist": {
+      "type": "ip_range"
+    }
+  }
+}
+
+PUT range_index/_doc/2
+{
+  "ip_whitelist" : "192.168.0.0/16"
+}
+--------------------------------------------------
+// CONSOLE
+// TEST[setup:range_index]
 
 [[range-params]]
 ==== Parameters for range fields