From 5656d10666cd890faa8df4630bef469749182bfb Mon Sep 17 00:00:00 2001
From: Eric Beahan <eric.beahan@elastic.co>
Date: Tue, 8 Sep 2020 11:08:25 -0500
Subject: [PATCH] assigning rfc number and date

---
 .../{0000-host-identifiers.md => 0006-host-identifiers.md}    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename rfcs/text/{0000-host-identifiers.md => 0006-host-identifiers.md} (94%)

diff --git a/rfcs/text/0000-host-identifiers.md b/rfcs/text/0006-host-identifiers.md
similarity index 94%
rename from rfcs/text/0000-host-identifiers.md
rename to rfcs/text/0006-host-identifiers.md
index 5643120ac0..3a5effe383 100644
--- a/rfcs/text/0000-host-identifiers.md
+++ b/rfcs/text/0006-host-identifiers.md
@@ -1,8 +1,8 @@
-# 0000: Host Identifiers
+# 0006: Host Identifiers
 <!-- Leave this ID at 0000. The ECS team will assign a unique, contiguous RFC number upon merging the initial stage of this RFC. -->
 
 - Stage: **0 (strawperson)** <!-- Update to reflect target stage. See https://elastic.github.io/ecs/stages.html -->
-- Date: **TBD** <!-- The ECS team sets this date at merge time. This is the date of the latest stage advancement. -->
+- Date: **2020-09-08** <!-- The ECS team sets this date at merge time. This is the date of the latest stage advancement. -->
 
 <!--
 As you work on your RFC, use the "Stage N" comments to guide you in what you should focus on, for the stage you're targeting.