3 files changed, 60 insertions, 0 deletions
diff --git a/commons/ims/readme.rst b/commons/ims/readme.rst
new file mode 100644
index 00000000..e69de29b
--- /dev/null
+++ b/commons/ims/readme.rst
diff --git a/commons/mobile/readme.rst b/commons/mobile/readme.rst
new file mode 100644
index 00000000..e69de29b
--- /dev/null
+++ b/commons/mobile/readme.rst
diff --git a/commons/traffic-profile-guidelines.rst b/commons/traffic-profile-guidelines.rst
new file mode 100644
index 00000000..ffef50fe
--- /dev/null
+++ b/commons/traffic-profile-guidelines.rst
@@ -0,0 +1,60 @@
+================================
+OPNFV traffic profile guidelines
+================================
+
+.. contents::
+
+.. _introduction:
+
+------------
+Introduction
+------------
+
+In order to have consistent profiles for testing, it has been suggested to define and store traffic profiles based on operator representative scenario. 
+
+These reference profiles may be used by any test projects, unitary, functional or performance tests. It is possible to adapt them to specific testcases. It is recommended to use them in order to avoid getting as many profiles as tests. It should be helpful to compare the results of test scenario.
+
+.. _howto:
+
+-------------------------
+How to use these profiles
+-------------------------
+
+The directory of the traffic profiles may be described as follow::
+ 
+ ├── commons
+   ├── ims
+   │   └── readme.rst
+   ├── mobile
+   │   └── readme.rst
+   └── traffic-profile-guidelines.rst
+
+the readme.rst details the profile.
+
+
+.. _overview:
+
+------------------------
+Traffic profile overview
+------------------------
+
+The current profiles are available:
+ * Mobile traffic
+ * IMS residential traffic
+ * ...
+
+Mobile traffic
+==============
+
+IMS residential traffic
+=======================
+
+
+
+
+
+.. _reference:
+
+---------
+reference
+---------