From b9caaadaad5a5675acd41d16ddfaf7f084351b22 Mon Sep 17 00:00:00 2001
From: Karthik Sethuraman <karthik.sethuraman@necam.com>
Date: Mon, 10 Dec 2018 14:30:13 -0500
Subject: [PATCH 1/3] Change Logs for Release 2.1.1

---
 CHANGE_LOG/change-log.2.1.1.html | 293 +++++++++++++++++++++++++++++++
 CHANGE_LOG/change-log.2.1.1.md   | 125 +++++++++++++
 2 files changed, 418 insertions(+)
 create mode 100644 CHANGE_LOG/change-log.2.1.1.html
 create mode 100644 CHANGE_LOG/change-log.2.1.1.md
diff --git a/CHANGE_LOG/change-log.2.1.1.html b/CHANGE_LOG/change-log.2.1.1.html
new file mode 100644
index 00000000..2be95bda
--- /dev/null
+++ b/CHANGE_LOG/change-log.2.1.1.html
@@ -0,0 +1,293 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8">
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+    <meta name="viewport" content="width=device-width, initial-scale=1">
+    <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
+    <meta name="description" content="">
+    <meta name="author" content="">
+
+    <title>Change Log</title>
+
+        <!-- Latest compiled and minified CSS -->
+    <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css" integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u" crossorigin="anonymous">
+    <link rel="stylesheet" type="text/css" href="https://cdn.datatables.net/v/bs/dt-1.10.13/datatables.min.css"/>
+  </head>
+ <body>
+    	<div class="container" role="main">
+            <div class="row">
+                <h1>Change Log</h1>
+            </div>
+            
+            <div class="row">
+                <div class="header title">
+		    <h2>Commit Range: v2.1.0..HEAD</h2>
+                </div>
+                 <table id="commitTable" class="table table-bordered table-striped table-hover">
+                 <thead>
+                  <tr>
+                    <th>Date</th>
+                    <th>Author</th>
+                    <th>Commit</th>
+                  </tr>
+                  </thead>
+                  <tbody>
+                  
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-09T21:13:16&nbsp;</span>09-Dec-2018 21:13</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/8a98f669567cea1777fbf9719d4bb88161520bee'>8a98f669567cea1777fbf9719d4bb88161520bee</a>
+			    <br>
+                            README updates and minor cleanup
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-08T19:48:08&nbsp;</span>08-Dec-2018 19:48</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/ac011c1b35f01440c3c56174df871c9fa3e0eb8f'>ac011c1b35f01440c3c56174df871c9fa3e0eb8f</a>
+			    <br>
+                            TAPI Python client implementation
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-08T19:47:30&nbsp;</span>08-Dec-2018 19:47</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/6922098f42d82995e431aba070f5f1a90aa228c7'>6922098f42d82995e431aba070f5f1a90aa228c7</a>
+			    <br>
+                            cleanup and minor fixes
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-07T22:37:57&nbsp;</span>07-Dec-2018 22:37</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/1025912b1005198fd579cd8d454e6ad3fee4888a'>1025912b1005198fd579cd8d454e6ad3fee4888a</a>
+			    <br>
+                            basic topology api implementations
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-07T21:35:58&nbsp;</span>07-Dec-2018 21:35</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/88a8af56a6376d6ebf4dcd50d731a88fe910caba'>88a8af56a6376d6ebf4dcd50d731a88fe910caba</a>
+			    <br>
+                            ODU Context topology from earlier TAPI version - need update
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-07T21:34:44&nbsp;</span>07-Dec-2018 21:34</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/99e08b46da21a80c63ee8cf2f55ddac0176b6ac6'>99e08b46da21a80c63ee8cf2f55ddac0176b6ac6</a>
+			    <br>
+                            clean-up commented code
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-07T21:34:20&nbsp;</span>07-Dec-2018 21:34</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/e12a45f99a70c0eb3a29c595b86293226a82b902'>e12a45f99a70c0eb3a29c595b86293226a82b902</a>
+			    <br>
+                            TPD &amp; OLS Contexts topologies
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-04T23:17:36&nbsp;</span>04-Dec-2018 23:17</td>
+                        <td>Ai Hamano</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/c9ed33cdf01fd95b84cbc7f7b01d0f0d2d04eec4'>c9ed33cdf01fd95b84cbc7f7b01d0f0d2d04eec4</a>
+			    <br>
+                            Convert tabs into spaces and fix the indentation
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-29T16:32:45&nbsp;</span>29-Nov-2018 16:32</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/4996056d6fa1226bd6f9927b499c579897492502'>4996056d6fa1226bd6f9927b499c579897492502</a>
+			    <br>
+                            Initial commit of TAPI RI for v2.1.1 - also removed old RI
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-29T10:47:39&nbsp;</span>29-Nov-2018 10:47</td>
+                        <td>karthik-sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/90bce6ac0c84e793615902979605bd651d588fac'>90bce6ac0c84e793615902979605bd651d588fac</a>
+			    <br>
+                            Fix #196/#372: added MC-SIP, MC-CEP &amp; OTSi-CEP augments to RPCs
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-29T10:46:06&nbsp;</span>29-Nov-2018 10:46</td>
+                        <td>karthik-sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/743d49b3f42ed411561882bf60b77ad500c3630f'>743d49b3f42ed411561882bf60b77ad500c3630f</a>
+			    <br>
+                            Fix #196: Added getConnectionEndPointDetails RPC to tapi-connectivity
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-28T17:20:08&nbsp;</span>28-Nov-2018 17:20</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/84389eb4bf4eff80611d3aa9d902e84d1c8ca400'>84389eb4bf4eff80611d3aa9d902e84d1c8ca400</a>
+			    <br>
+                            Manual fix for missing ConnectivityService definition
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-27T21:59:29&nbsp;</span>27-Nov-2018 21:59</td>
+                        <td>karthik-sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/cdb2163d29bce31ea0af5da8f8a70437a8efb089'>cdb2163d29bce31ea0af5da8f8a70437a8efb089</a>
+			    <br>
+                            Fix #372: Generated .tree &amp; .oas files from the updated yang files
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-27T21:52:15&nbsp;</span>27-Nov-2018 21:52</td>
+                        <td>karthik-sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/4fa0699a1c64ff2d12ce72c44869e43bd8e5353d'>4fa0699a1c64ff2d12ce72c44869e43bd8e5353d</a>
+			    <br>
+                            Fix #372: Added &#39;key&#34; to complex data-types used as list attribute
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-27T21:12:52&nbsp;</span>27-Nov-2018 21:12</td>
+                        <td>karthik-sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/3bead76029659d2ab26ff7b7abcecf3dd7edb317'>3bead76029659d2ab26ff7b7abcecf3dd7edb317</a>
+			    <br>
+                            Fix #372: Added &#39;key&#34; to SpectrumBand &amp; CentralFrequency data-types
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-27T21:10:53&nbsp;</span>27-Nov-2018 21:10</td>
+                        <td>karthik-sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/21849dfa1725282276b5c515ed7110ae4caf8120'>21849dfa1725282276b5c515ed7110ae4caf8120</a>
+			    <br>
+                            Fix #372: Added &#39;key&#39; sub-statements to &#39;list&#39; outputs of RPCs
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-27T16:55:24&nbsp;</span>27-Nov-2018 16:55</td>
+                        <td>karthik-sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/cb6d9d4c903fa8a8b6802d1c22b0ec2a9a18181b'>cb6d9d4c903fa8a8b6802d1c22b0ec2a9a18181b</a>
+			    <br>
+                            Fix #372: Added &#39;key&#39; sub-statements to &#39;list&#39; outputs of RPCs
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-11-27T16:46:55&nbsp;</span>27-Nov-2018 16:46</td>
+                        <td>karthik-sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/0c566fe3b2c8efe925ddd5a7f9948f2df02a9b83'>0c566fe3b2c8efe925ddd5a7f9948f2df02a9b83</a>
+			    <br>
+                            Partial fix #196 - updated photonic-media with RPC augments
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-10-19T12:48:35&nbsp;</span>19-Oct-2018 12:48</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/433c06a4447182a52308132cf17ea1965d3fd98e'>433c06a4447182a52308132cf17ea1965d3fd98e</a>
+			    <br>
+                            Replaced Developer guide with Implementation guide
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-10-19T12:14:38&nbsp;</span>19-Oct-2018 12:14</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/9ad9b6d616ae11490e5a20c11748f771e16717cc'>9ad9b6d616ae11490e5a20c11748f771e16717cc</a>
+			    <br>
+                            Updated README based on TST approved TAPI 2.1 release notes
+                            
+                        </td>
+                    </tr>
+                    
+                    </tbody>
+                  </table>
+            </div>
+		</div>
+	
+        <script type="text/javascript" src="https://cdn.datatables.net/v/bs-3.3.7/jqc-1.12.4/dt-1.10.13/datatables.min.js"></script>
+        <script>
+        $(document).ready(function() {
+            $('#commitTable').DataTable({
+                'iDisplayLength':25,
+                "order": [[ 0, "desc" ]]
+            });
+        } );
+        </script>
+    </body>
+</html>
+
diff --git a/CHANGE_LOG/change-log.2.1.1.md b/CHANGE_LOG/change-log.2.1.1.md
new file mode 100644
index 00000000..fbded275
--- /dev/null
+++ b/CHANGE_LOG/change-log.2.1.1.md
@@ -0,0 +1,125 @@
+# Change Log
+## Commit Range: v2.1.0..HEAD
+
+
+* __README updates and minor cleanup__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Sun, 9 Dec 2018 21:13:16 -0500
+    [8a98f669567cea1777fbf9719d4bb88161520bee](https://github.com/OpenNetworkingFoundation/TAPI/commit/8a98f669567cea1777fbf9719d4bb88161520bee)
+    
+
+* __TAPI Python client implementation__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Sat, 8 Dec 2018 19:48:08 -0500
+    [ac011c1b35f01440c3c56174df871c9fa3e0eb8f](https://github.com/OpenNetworkingFoundation/TAPI/commit/ac011c1b35f01440c3c56174df871c9fa3e0eb8f)
+    
+
+* __cleanup and minor fixes__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Sat, 8 Dec 2018 19:47:30 -0500
+    [6922098f42d82995e431aba070f5f1a90aa228c7](https://github.com/OpenNetworkingFoundation/TAPI/commit/6922098f42d82995e431aba070f5f1a90aa228c7)
+    
+
+* __basic topology api implementations__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Fri, 7 Dec 2018 22:37:57 -0500
+    [1025912b1005198fd579cd8d454e6ad3fee4888a](https://github.com/OpenNetworkingFoundation/TAPI/commit/1025912b1005198fd579cd8d454e6ad3fee4888a)
+    
+
+* __ODU Context topology from earlier TAPI version - need update__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Fri, 7 Dec 2018 21:35:58 -0500
+    [88a8af56a6376d6ebf4dcd50d731a88fe910caba](https://github.com/OpenNetworkingFoundation/TAPI/commit/88a8af56a6376d6ebf4dcd50d731a88fe910caba)
+    
+
+* __clean-up commented code__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Fri, 7 Dec 2018 21:34:44 -0500
+    [99e08b46da21a80c63ee8cf2f55ddac0176b6ac6](https://github.com/OpenNetworkingFoundation/TAPI/commit/99e08b46da21a80c63ee8cf2f55ddac0176b6ac6)
+    
+
+* __TPD &amp; OLS Contexts topologies__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Fri, 7 Dec 2018 21:34:20 -0500
+    [e12a45f99a70c0eb3a29c595b86293226a82b902](https://github.com/OpenNetworkingFoundation/TAPI/commit/e12a45f99a70c0eb3a29c595b86293226a82b902)
+    
+
+* __Convert tabs into spaces and fix the indentation__
+
+    [Ai Hamano](mailto:ai.hamano@ntt-at.co.jp) - Wed, 5 Dec 2018 13:17:36 +0900
+    [c9ed33cdf01fd95b84cbc7f7b01d0f0d2d04eec4](https://github.com/OpenNetworkingFoundation/TAPI/commit/c9ed33cdf01fd95b84cbc7f7b01d0f0d2d04eec4)
+    
+
+* __Initial commit of TAPI RI for v2.1.1 - also removed old RI__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Thu, 29 Nov 2018 16:32:45 -0500
+    [4996056d6fa1226bd6f9927b499c579897492502](https://github.com/OpenNetworkingFoundation/TAPI/commit/4996056d6fa1226bd6f9927b499c579897492502)
+    
+
+* __Fix #196/#372: added MC-SIP, MC-CEP &amp; OTSi-CEP augments to RPCs__
+
+    [karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Thu, 29 Nov 2018 10:47:39 -0500
+    [90bce6ac0c84e793615902979605bd651d588fac](https://github.com/OpenNetworkingFoundation/TAPI/commit/90bce6ac0c84e793615902979605bd651d588fac)
+    
+
+* __Fix #196: Added getConnectionEndPointDetails RPC to tapi-connectivity__
+
+    [karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Thu, 29 Nov 2018 10:46:06 -0500
+    [743d49b3f42ed411561882bf60b77ad500c3630f](https://github.com/OpenNetworkingFoundation/TAPI/commit/743d49b3f42ed411561882bf60b77ad500c3630f)
+    
+
+* __Manual fix for missing ConnectivityService definition__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Wed, 28 Nov 2018 17:20:08 -0500
+    [84389eb4bf4eff80611d3aa9d902e84d1c8ca400](https://github.com/OpenNetworkingFoundation/TAPI/commit/84389eb4bf4eff80611d3aa9d902e84d1c8ca400)
+    
+
+* __Fix #372: Generated .tree &amp; .oas files from the updated yang files__
+
+    [karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Tue, 27 Nov 2018 21:59:29 -0500
+    [cdb2163d29bce31ea0af5da8f8a70437a8efb089](https://github.com/OpenNetworkingFoundation/TAPI/commit/cdb2163d29bce31ea0af5da8f8a70437a8efb089)
+    
+
+* __Fix #372: Added &#39;key&#34; to complex data-types used as list attribute__
+
+    [karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Tue, 27 Nov 2018 21:52:15 -0500
+    [4fa0699a1c64ff2d12ce72c44869e43bd8e5353d](https://github.com/OpenNetworkingFoundation/TAPI/commit/4fa0699a1c64ff2d12ce72c44869e43bd8e5353d)
+    
+
+* __Fix #372: Added &#39;key&#34; to SpectrumBand &amp; CentralFrequency data-types__
+
+    [karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Tue, 27 Nov 2018 21:12:52 -0500
+    [3bead76029659d2ab26ff7b7abcecf3dd7edb317](https://github.com/OpenNetworkingFoundation/TAPI/commit/3bead76029659d2ab26ff7b7abcecf3dd7edb317)
+    
+
+* __Fix #372: Added &#39;key&#39; sub-statements to &#39;list&#39; outputs of RPCs__
+
+    [karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Tue, 27 Nov 2018 21:10:53 -0500
+    [21849dfa1725282276b5c515ed7110ae4caf8120](https://github.com/OpenNetworkingFoundation/TAPI/commit/21849dfa1725282276b5c515ed7110ae4caf8120)
+    
+
+* __Fix #372: Added &#39;key&#39; sub-statements to &#39;list&#39; outputs of RPCs__
+
+    [karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Tue, 27 Nov 2018 16:55:24 -0500
+    [cb6d9d4c903fa8a8b6802d1c22b0ec2a9a18181b](https://github.com/OpenNetworkingFoundation/TAPI/commit/cb6d9d4c903fa8a8b6802d1c22b0ec2a9a18181b)
+    
+
+* __Partial fix #196 - updated photonic-media with RPC augments__
+
+    [karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Tue, 27 Nov 2018 16:46:55 -0500
+    [0c566fe3b2c8efe925ddd5a7f9948f2df02a9b83](https://github.com/OpenNetworkingFoundation/TAPI/commit/0c566fe3b2c8efe925ddd5a7f9948f2df02a9b83)
+    
+
+* __Replaced Developer guide with Implementation guide__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Fri, 19 Oct 2018 12:48:35 -0400
+    [433c06a4447182a52308132cf17ea1965d3fd98e](https://github.com/OpenNetworkingFoundation/TAPI/commit/433c06a4447182a52308132cf17ea1965d3fd98e)
+    
+
+* __Updated README based on TST approved TAPI 2.1 release notes__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Fri, 19 Oct 2018 12:14:38 -0400
+    [9ad9b6d616ae11490e5a20c11748f771e16717cc](https://github.com/OpenNetworkingFoundation/TAPI/commit/9ad9b6d616ae11490e5a20c11748f771e16717cc)
+    
+
+

From ac2ccf54b97bdf48afae2108f1f9a48a231c1ef7 Mon Sep 17 00:00:00 2001
From: Karthik Sethuraman <karthik.sethuraman@necam.com>
Date: Mon, 10 Dec 2018 15:25:36 -0500
Subject: [PATCH 2/3] Renamed YANG, TREE & OAS files with 2.1.1 revision date
 @2018-12-10

---
 ...10-16.yaml => tapi-common@2018-12-10.yaml} |  0
 ...yaml => tapi-connectivity@2018-12-10.yaml} |  0
 ...18-10-16.yaml => tapi-dsr@2018-12-10.yaml} |  0
 ...18-10-16.yaml => tapi-eth@2018-12-10.yaml} |  0
 ...yaml => tapi-notification@2018-12-10.yaml} |  0
 ...18-10-16.yaml => tapi-oam@2018-12-10.yaml} |  0
 ...18-10-16.yaml => tapi-odu@2018-12-10.yaml} |  0
 ... => tapi-path-computation@2018-12-10.yaml} |  0
 ...ml => tapi-photonic-media@2018-12-10.yaml} |  0
 ...-16.yaml => tapi-topology@2018-12-10.yaml} |  0
 ...l => tapi-virtual-network@2018-12-10.yaml} |  0
 RI/README.md                                  |  2 +-
 .../OpenInterfaceModelProfile/.project        | 11 ------
 UML/UmlProfiles/OpenModelProfile/.project     | 11 ------
 .../ProfileLifecycleProfile/.project          | 11 ------
 YANG/config-xmi2yang.json                     |  9 ++++-
 ...10-16.tree => tapi-common@2018-12-10.tree} |  0
 ...10-16.yang => tapi-common@2018-12-10.yang} | 34 ++++++++++-------
 ...tree => tapi-connectivity@2018-12-10.tree} |  0
 ...yang => tapi-connectivity@2018-12-10.yang} | 31 ++++++++++------
 ...18-10-16.tree => tapi-dsr@2018-12-10.tree} |  0
 ...18-10-16.yang => tapi-dsr@2018-12-10.yang} | 37 ++++++++++++-------
 ...18-10-16.tree => tapi-eth@2018-12-10.tree} |  0
 ...18-10-16.yang => tapi-eth@2018-12-10.yang} | 31 ++++++++++------
 ...tree => tapi-notification@2018-12-10.tree} |  0
 ...yang => tapi-notification@2018-12-10.yang} | 31 ++++++++++------
 ...18-10-16.tree => tapi-oam@2018-12-10.tree} |  0
 ...18-10-16.yang => tapi-oam@2018-12-10.yang} | 31 ++++++++++------
 ...18-10-16.tree => tapi-odu@2018-12-10.tree} |  0
 ...18-10-16.yang => tapi-odu@2018-12-10.yang} | 31 ++++++++++------
 ... => tapi-path-computation@2018-12-10.tree} |  0
 ... => tapi-path-computation@2018-12-10.yang} | 31 ++++++++++------
 ...ee => tapi-photonic-media@2018-12-10.tree} |  0
 ...ng => tapi-photonic-media@2018-12-10.yang} | 31 ++++++++++------
 ...-16.tree => tapi-topology@2018-12-10.tree} |  0
 ...-16.yang => tapi-topology@2018-12-10.yang} | 31 ++++++++++------
 ...e => tapi-virtual-network@2018-12-10.tree} |  0
 ...g => tapi-virtual-network@2018-12-10.yang} | 31 ++++++++++------
 38 files changed, 223 insertions(+), 171 deletions(-)
 rename OAS/{tapi-common@2018-10-16.yaml => tapi-common@2018-12-10.yaml} (100%)
 rename OAS/{tapi-connectivity@2018-10-16.yaml => tapi-connectivity@2018-12-10.yaml} (100%)
 rename OAS/{tapi-dsr@2018-10-16.yaml => tapi-dsr@2018-12-10.yaml} (100%)
 rename OAS/{tapi-eth@2018-10-16.yaml => tapi-eth@2018-12-10.yaml} (100%)
 rename OAS/{tapi-notification@2018-10-16.yaml => tapi-notification@2018-12-10.yaml} (100%)
 rename OAS/{tapi-oam@2018-10-16.yaml => tapi-oam@2018-12-10.yaml} (100%)
 rename OAS/{tapi-odu@2018-10-16.yaml => tapi-odu@2018-12-10.yaml} (100%)
 rename OAS/{tapi-path-computation@2018-10-16.yaml => tapi-path-computation@2018-12-10.yaml} (100%)
 rename OAS/{tapi-photonic-media@2018-10-16.yaml => tapi-photonic-media@2018-12-10.yaml} (100%)
 rename OAS/{tapi-topology@2018-10-16.yaml => tapi-topology@2018-12-10.yaml} (100%)
 rename OAS/{tapi-virtual-network@2018-10-16.yaml => tapi-virtual-network@2018-12-10.yaml} (100%)
 delete mode 100644 UML/UmlProfiles/OpenInterfaceModelProfile/.project
 delete mode 100644 UML/UmlProfiles/OpenModelProfile/.project
 delete mode 100644 UML/UmlProfiles/ProfileLifecycleProfile/.project
 rename YANG/{tapi-common@2018-10-16.tree => tapi-common@2018-12-10.tree} (100%)
 rename YANG/{tapi-common@2018-10-16.yang => tapi-common@2018-12-10.yang} (92%)
 rename YANG/{tapi-connectivity@2018-10-16.tree => tapi-connectivity@2018-12-10.tree} (100%)
 rename YANG/{tapi-connectivity@2018-10-16.yang => tapi-connectivity@2018-12-10.yang} (92%)
 rename YANG/{tapi-dsr@2018-10-16.tree => tapi-dsr@2018-12-10.tree} (100%)
 rename YANG/{tapi-dsr@2018-10-16.yang => tapi-dsr@2018-12-10.yang} (75%)
 rename YANG/{tapi-eth@2018-10-16.tree => tapi-eth@2018-12-10.tree} (100%)
 rename YANG/{tapi-eth@2018-10-16.yang => tapi-eth@2018-12-10.yang} (95%)
 rename YANG/{tapi-notification@2018-10-16.tree => tapi-notification@2018-12-10.tree} (100%)
 rename YANG/{tapi-notification@2018-10-16.yang => tapi-notification@2018-12-10.yang} (88%)
 rename YANG/{tapi-oam@2018-10-16.tree => tapi-oam@2018-12-10.tree} (100%)
 rename YANG/{tapi-oam@2018-10-16.yang => tapi-oam@2018-12-10.yang} (90%)
 rename YANG/{tapi-odu@2018-10-16.tree => tapi-odu@2018-12-10.tree} (100%)
 rename YANG/{tapi-odu@2018-10-16.yang => tapi-odu@2018-12-10.yang} (92%)
 rename YANG/{tapi-path-computation@2018-10-16.tree => tapi-path-computation@2018-12-10.tree} (100%)
 rename YANG/{tapi-path-computation@2018-10-16.yang => tapi-path-computation@2018-12-10.yang} (87%)
 rename YANG/{tapi-photonic-media@2018-10-16.tree => tapi-photonic-media@2018-12-10.tree} (100%)
 rename YANG/{tapi-photonic-media@2018-10-16.yang => tapi-photonic-media@2018-12-10.yang} (93%)
 rename YANG/{tapi-topology@2018-10-16.tree => tapi-topology@2018-12-10.tree} (100%)
 rename YANG/{tapi-topology@2018-10-16.yang => tapi-topology@2018-12-10.yang} (92%)
 rename YANG/{tapi-virtual-network@2018-10-16.tree => tapi-virtual-network@2018-12-10.tree} (100%)
 rename YANG/{tapi-virtual-network@2018-10-16.yang => tapi-virtual-network@2018-12-10.yang} (83%)

diff --git a/OAS/tapi-common@2018-10-16.yaml b/OAS/tapi-common@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-common@2018-10-16.yaml
rename to OAS/tapi-common@2018-12-10.yaml
diff --git a/OAS/tapi-connectivity@2018-10-16.yaml b/OAS/tapi-connectivity@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-connectivity@2018-10-16.yaml
rename to OAS/tapi-connectivity@2018-12-10.yaml
diff --git a/OAS/tapi-dsr@2018-10-16.yaml b/OAS/tapi-dsr@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-dsr@2018-10-16.yaml
rename to OAS/tapi-dsr@2018-12-10.yaml
diff --git a/OAS/tapi-eth@2018-10-16.yaml b/OAS/tapi-eth@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-eth@2018-10-16.yaml
rename to OAS/tapi-eth@2018-12-10.yaml
diff --git a/OAS/tapi-notification@2018-10-16.yaml b/OAS/tapi-notification@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-notification@2018-10-16.yaml
rename to OAS/tapi-notification@2018-12-10.yaml
diff --git a/OAS/tapi-oam@2018-10-16.yaml b/OAS/tapi-oam@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-oam@2018-10-16.yaml
rename to OAS/tapi-oam@2018-12-10.yaml
diff --git a/OAS/tapi-odu@2018-10-16.yaml b/OAS/tapi-odu@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-odu@2018-10-16.yaml
rename to OAS/tapi-odu@2018-12-10.yaml
diff --git a/OAS/tapi-path-computation@2018-10-16.yaml b/OAS/tapi-path-computation@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-path-computation@2018-10-16.yaml
rename to OAS/tapi-path-computation@2018-12-10.yaml
diff --git a/OAS/tapi-photonic-media@2018-10-16.yaml b/OAS/tapi-photonic-media@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-photonic-media@2018-10-16.yaml
rename to OAS/tapi-photonic-media@2018-12-10.yaml
diff --git a/OAS/tapi-topology@2018-10-16.yaml b/OAS/tapi-topology@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-topology@2018-10-16.yaml
rename to OAS/tapi-topology@2018-12-10.yaml
diff --git a/OAS/tapi-virtual-network@2018-10-16.yaml b/OAS/tapi-virtual-network@2018-12-10.yaml
similarity index 100%
rename from OAS/tapi-virtual-network@2018-10-16.yaml
rename to OAS/tapi-virtual-network@2018-12-10.yaml
diff --git a/RI/README.md b/RI/README.md
index 483726b9..79b14889 100644
--- a/RI/README.md
+++ b/RI/README.md
@@ -13,7 +13,7 @@ Currently the RI includes following implementations:
 These implementations have been tested on [Ubuntu 18.04.1 LTS](https://www.ubuntu.com/download/desktop).
 
 ## Coverage
-For this release (TAPI 2.1.1), the [tapi-photonic-media OpenAPI file](https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/OAS/tapi-photonic-media@402018-10-16.yaml) has been used to generate the server stubs.
+For this release (TAPI 2.1.1), the [tapi-photonic-media OpenAPI file](https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/OAS/tapi-photonic-media@402018-12-10.yaml) has been used to generate the server stubs.
 
 Only a limited set of following APIs have been implemented in this release:
 * _GET_ /data/context/
diff --git a/UML/UmlProfiles/OpenInterfaceModelProfile/.project b/UML/UmlProfiles/OpenInterfaceModelProfile/.project
deleted file mode 100644
index 7519bd9c..00000000
--- a/UML/UmlProfiles/OpenInterfaceModelProfile/.project
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>OpenInterfaceModelProfile</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-	</buildSpec>
-	<natures>
-	</natures>
-</projectDescription>
diff --git a/UML/UmlProfiles/OpenModelProfile/.project b/UML/UmlProfiles/OpenModelProfile/.project
deleted file mode 100644
index 632ad928..00000000
--- a/UML/UmlProfiles/OpenModelProfile/.project
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>OpenModelProfile</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-	</buildSpec>
-	<natures>
-	</natures>
-</projectDescription>
diff --git a/UML/UmlProfiles/ProfileLifecycleProfile/.project b/UML/UmlProfiles/ProfileLifecycleProfile/.project
deleted file mode 100644
index 5c85be2a..00000000
--- a/UML/UmlProfiles/ProfileLifecycleProfile/.project
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-  <name>ProfileLifecycleProfile</name>
-  <comment></comment>
-  <projects>
-  </projects>
-  <buildSpec>
-  </buildSpec>
-  <natures>
-  </natures>
-</projectDescription>
diff --git a/YANG/config-xmi2yang.json b/YANG/config-xmi2yang.json
index 9961c549..bbf5b3c4 100644
--- a/YANG/config-xmi2yang.json
+++ b/YANG/config-xmi2yang.json
@@ -2,12 +2,17 @@
   "tapi":{
     "namespace":"urn:onf:otcc:yang:",
     "organization":"ONF OTCC (Open Transport Configuration & Control) Project",
-    "contact":"\r\n Project Web: <https://wiki.opennetworking.org/display/OTCC/TAPI>\r\n Project List: <mailto:transport-api@opennetworking.org>\r\n Editor: Karthik Sethuraman\r\n\t\t <mailto:karthik.sethuraman@necam.com>",
+    "contact":"\r\n Project Web: <https://wiki.opennetworking.org/display/OTCC/TAPI>\r\n Project List: <mailto:transport-api@opennetworking.org>\r\n Editor: Karthik Sethuraman\r\n         <mailto:karthik.sethuraman@necam.com>",
     "withSuffix":false,
     "revision": [
+        {
+	      "date":"2018-12-10",
+	      "description":"ONF Transport API version 2.1.1.\r\n  - The TAPI YANG models included in this TAPI release (v2.1.1) are a *normative* part of the TAPI SDK.\r\n  - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]\r\n   <https://github.com/OpenNetworkingFoundation/EagleUmlYang>\r\n   and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]\r\n   <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>\r\n  - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.\r\n   As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.\r\n  - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.\r\n   The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\r\n   YANG models included in this release are not backward compatible with previous TAPI releases.\r\n  - Changes included in this TAPI release (v2.1.1) are listed in\r\n   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>",
+	      "reference":"ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model\n                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>"
+	    },
         {
 	      "date":"2018-10-16",
-	      "description":"ONF Transport API version 2.1.0.\r\n  - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.\r\n  - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]\r\n\t<https://github.com/OpenNetworkingFoundation/EagleUmlYang>\r\n\tand further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]\r\n\t<https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>\r\n  - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.\r\n\tAs described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.\r\n  - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.\r\n\tThe YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\r\n\tYANG models included in this release are not backward compatible with previous TAPI releases.\r\n  - Changes included in this TAPI release (v2.1.0) are listed in\r\n\t<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>",
+	      "description":"ONF Transport API version 2.1.0.\r\n  - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.\r\n  - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]\r\n   <https://github.com/OpenNetworkingFoundation/EagleUmlYang>\r\n   and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]\r\n   <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>\r\n  - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.\r\n   As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.\r\n  - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.\r\n   The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\r\n   YANG models included in this release are not backward compatible with previous TAPI releases.\r\n  - Changes included in this TAPI release (v2.1.0) are listed in\r\n   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>",
 	      "reference":"ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model\n                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>"
 	    },
 	    {
diff --git a/YANG/tapi-common@2018-10-16.tree b/YANG/tapi-common@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-common@2018-10-16.tree
rename to YANG/tapi-common@2018-12-10.tree
diff --git a/YANG/tapi-common@2018-10-16.yang b/YANG/tapi-common@2018-12-10.yang
similarity index 92%
rename from YANG/tapi-common@2018-10-16.yang
rename to YANG/tapi-common@2018-12-10.yang
index d526a7ab..b5fecaa9 100755
--- a/YANG/tapi-common@2018-10-16.yang
+++ b/YANG/tapi-common@2018-12-10.yang
@@ -10,23 +10,29 @@ module tapi-common {
     description "
         This module contains TAPI Common Model definitions.
         Source: TapiCommon.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
-        License: This module is distributed under the Apache License 2.0
-        ";
+        License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-connectivity@2018-10-16.tree b/YANG/tapi-connectivity@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-connectivity@2018-10-16.tree
rename to YANG/tapi-connectivity@2018-12-10.tree
diff --git a/YANG/tapi-connectivity@2018-10-16.yang b/YANG/tapi-connectivity@2018-12-10.yang
similarity index 92%
rename from YANG/tapi-connectivity@2018-10-16.yang
rename to YANG/tapi-connectivity@2018-12-10.yang
index 755eb2ef..5b798c7b 100755
--- a/YANG/tapi-connectivity@2018-10-16.yang
+++ b/YANG/tapi-connectivity@2018-12-10.yang
@@ -19,22 +19,29 @@ module tapi-connectivity {
     description "
         This module contains TAPI Connectivity Model definitions.
         Source: TapiConnectivity.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
         License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-dsr@2018-10-16.tree b/YANG/tapi-dsr@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-dsr@2018-10-16.tree
rename to YANG/tapi-dsr@2018-12-10.tree
diff --git a/YANG/tapi-dsr@2018-10-16.yang b/YANG/tapi-dsr@2018-12-10.yang
similarity index 75%
rename from YANG/tapi-dsr@2018-10-16.yang
rename to YANG/tapi-dsr@2018-12-10.yang
index 545f5855..77f5a8b5 100755
--- a/YANG/tapi-dsr@2018-10-16.yang
+++ b/YANG/tapi-dsr@2018-12-10.yang
@@ -10,21 +10,32 @@ module tapi-dsr {
          Project List: <mailto:transport-api@opennetworking.org>
          Editor: Karthik Sethuraman
                  <mailto:karthik.sethuraman@necam.com>";
-    description "none";
+    description "
+        This module contains TAPI DSR Model definitions.
+        Source: TapiDsr.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
+        Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
+        License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-eth@2018-10-16.tree b/YANG/tapi-eth@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-eth@2018-10-16.tree
rename to YANG/tapi-eth@2018-12-10.tree
diff --git a/YANG/tapi-eth@2018-10-16.yang b/YANG/tapi-eth@2018-12-10.yang
similarity index 95%
rename from YANG/tapi-eth@2018-10-16.yang
rename to YANG/tapi-eth@2018-12-10.yang
index 383558eb..953affaf 100755
--- a/YANG/tapi-eth@2018-10-16.yang
+++ b/YANG/tapi-eth@2018-12-10.yang
@@ -21,22 +21,29 @@ module tapi-eth {
                  <mailto:karthik.sethuraman@necam.com>";
     description "This module contains TAPI ETH Model definitions.
         Source: TapiEth.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
         License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-notification@2018-10-16.tree b/YANG/tapi-notification@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-notification@2018-10-16.tree
rename to YANG/tapi-notification@2018-12-10.tree
diff --git a/YANG/tapi-notification@2018-10-16.yang b/YANG/tapi-notification@2018-12-10.yang
similarity index 88%
rename from YANG/tapi-notification@2018-10-16.yang
rename to YANG/tapi-notification@2018-12-10.yang
index 2885abc4..28071af0 100755
--- a/YANG/tapi-notification@2018-10-16.yang
+++ b/YANG/tapi-notification@2018-12-10.yang
@@ -13,22 +13,29 @@ module tapi-notification {
     description "
         This module contains TAPI Notification Model definitions.
         Source: TapiNotification.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
         License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-oam@2018-10-16.tree b/YANG/tapi-oam@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-oam@2018-10-16.tree
rename to YANG/tapi-oam@2018-12-10.tree
diff --git a/YANG/tapi-oam@2018-10-16.yang b/YANG/tapi-oam@2018-12-10.yang
similarity index 90%
rename from YANG/tapi-oam@2018-10-16.yang
rename to YANG/tapi-oam@2018-12-10.yang
index 143b7901..5410ba45 100755
--- a/YANG/tapi-oam@2018-10-16.yang
+++ b/YANG/tapi-oam@2018-12-10.yang
@@ -19,22 +19,29 @@ module tapi-oam {
     description "
         This module contains TAPI OAM Model definitions.
         Source: TapiOam.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
         License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-odu@2018-10-16.tree b/YANG/tapi-odu@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-odu@2018-10-16.tree
rename to YANG/tapi-odu@2018-12-10.tree
diff --git a/YANG/tapi-odu@2018-10-16.yang b/YANG/tapi-odu@2018-12-10.yang
similarity index 92%
rename from YANG/tapi-odu@2018-10-16.yang
rename to YANG/tapi-odu@2018-12-10.yang
index d927fddd..8d104b90 100755
--- a/YANG/tapi-odu@2018-10-16.yang
+++ b/YANG/tapi-odu@2018-12-10.yang
@@ -25,22 +25,29 @@ module tapi-odu {
     description "
         This module contains TAPI Odu Model definitions.
         Source: TapiOdu.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
         License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-path-computation@2018-10-16.tree b/YANG/tapi-path-computation@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-path-computation@2018-10-16.tree
rename to YANG/tapi-path-computation@2018-12-10.tree
diff --git a/YANG/tapi-path-computation@2018-10-16.yang b/YANG/tapi-path-computation@2018-12-10.yang
similarity index 87%
rename from YANG/tapi-path-computation@2018-10-16.yang
rename to YANG/tapi-path-computation@2018-12-10.yang
index ba6173d3..eeae3e27 100755
--- a/YANG/tapi-path-computation@2018-10-16.yang
+++ b/YANG/tapi-path-computation@2018-12-10.yang
@@ -16,22 +16,29 @@ module tapi-path-computation {
     description "
         This module contains TAPI Path Computation Model definitions.
         Source: TapiPathComputation.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
         License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-photonic-media@2018-10-16.tree b/YANG/tapi-photonic-media@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-photonic-media@2018-10-16.tree
rename to YANG/tapi-photonic-media@2018-12-10.tree
diff --git a/YANG/tapi-photonic-media@2018-10-16.yang b/YANG/tapi-photonic-media@2018-12-10.yang
similarity index 93%
rename from YANG/tapi-photonic-media@2018-10-16.yang
rename to YANG/tapi-photonic-media@2018-12-10.yang
index 5ae8fe1c..dc69c768 100755
--- a/YANG/tapi-photonic-media@2018-10-16.yang
+++ b/YANG/tapi-photonic-media@2018-12-10.yang
@@ -19,22 +19,29 @@ module tapi-photonic-media {
     description "
         This module contains TAPI PhotonicMedia Model definitions.
         Source: TapiPhotonicMedia.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
         License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-topology@2018-10-16.tree b/YANG/tapi-topology@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-topology@2018-10-16.tree
rename to YANG/tapi-topology@2018-12-10.tree
diff --git a/YANG/tapi-topology@2018-10-16.yang b/YANG/tapi-topology@2018-12-10.yang
similarity index 92%
rename from YANG/tapi-topology@2018-10-16.yang
rename to YANG/tapi-topology@2018-12-10.yang
index df459aae..0d35d859 100755
--- a/YANG/tapi-topology@2018-10-16.yang
+++ b/YANG/tapi-topology@2018-12-10.yang
@@ -13,22 +13,29 @@ module tapi-topology {
     description "
         This module contains TAPI Topology Model definitions.
         Source: TapiTopology.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
         License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }
diff --git a/YANG/tapi-virtual-network@2018-10-16.tree b/YANG/tapi-virtual-network@2018-12-10.tree
similarity index 100%
rename from YANG/tapi-virtual-network@2018-10-16.tree
rename to YANG/tapi-virtual-network@2018-12-10.tree
diff --git a/YANG/tapi-virtual-network@2018-10-16.yang b/YANG/tapi-virtual-network@2018-12-10.yang
similarity index 83%
rename from YANG/tapi-virtual-network@2018-10-16.yang
rename to YANG/tapi-virtual-network@2018-12-10.yang
index 8ab1bb47..e6ed2446 100755
--- a/YANG/tapi-virtual-network@2018-10-16.yang
+++ b/YANG/tapi-virtual-network@2018-12-10.yang
@@ -16,22 +16,29 @@ module tapi-virtual-network {
     description "
         This module contains TAPI Virtual Network Model definitions.
         Source: TapiVirtualNetwork.uml
+        - The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
+        - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
+          <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
+          and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
+          <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
+        - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
+          As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
+        - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
+          The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
+          YANG models included in this release may not be backward compatible with previous TAPI releases.
         Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
         License: This module is distributed under the Apache License 2.0";
+    revision 2018-12-10 {
+        description "ONF Transport API version 2.1.1.
+                   Changes included in this TAPI release (v2.1.1) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
+        reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+                  <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
+    }
     revision 2018-10-16 {
         description "ONF Transport API version 2.1.0.
-          - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
-          - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
-            <https://github.com/OpenNetworkingFoundation/EagleUmlYang>
-            and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
-            <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
-          - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
-            As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
-          - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
-            The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
-            YANG models included in this release are not backward compatible with previous TAPI releases.
-          - Changes included in this TAPI release (v2.1.0) are listed in
-            <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
+                   Changes included in this TAPI release (v2.1.0) are listed in
+                   <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
         reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
                   <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
     }

From 1ef8a994f2724a4c88bf18e0e9971ab800b5433c Mon Sep 17 00:00:00 2001
From: Karthik Sethuraman <karthik.sethuraman@necam.com>
Date: Mon, 10 Dec 2018 15:26:58 -0500
Subject: [PATCH 3/3] Change-log updates for Release 2.1.1

---
 CHANGE_LOG/change-log.2.1.1.html | 24 ++++++++++++++++++++++++
 CHANGE_LOG/change-log.2.1.1.md   | 12 ++++++++++++
 2 files changed, 36 insertions(+)

diff --git a/CHANGE_LOG/change-log.2.1.1.html b/CHANGE_LOG/change-log.2.1.1.html
index 2be95bda..75ddaa71 100644
--- a/CHANGE_LOG/change-log.2.1.1.html
+++ b/CHANGE_LOG/change-log.2.1.1.html
@@ -34,6 +34,30 @@ <h2>Commit Range: v2.1.0..HEAD</h2>
                   </thead>
                   <tbody>
                   
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-10T15:25:36&nbsp;</span>10-Dec-2018 15:25</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/ac2ccf54b97bdf48afae2108f1f9a48a231c1ef7'>ac2ccf54b97bdf48afae2108f1f9a48a231c1ef7</a>
+			    <br>
+                            Renamed YANG, TREE &amp; OAS files with 2.1.1 revision date @2018-12-10
+                            
+                        </td>
+                    </tr>
+                    
+                    <tr>
+                        
+                        <td nowrap="nowrap"><span style="display:none">2018-12-10T14:30:13&nbsp;</span>10-Dec-2018 14:30</td>
+                        <td>Karthik Sethuraman</td>
+                        <td>
+				<a href='https://github.com/OpenNetworkingFoundation/TAPI/commit/b9caaadaad5a5675acd41d16ddfaf7f084351b22'>b9caaadaad5a5675acd41d16ddfaf7f084351b22</a>
+			    <br>
+                            Change Logs for Release 2.1.1
+                            
+                        </td>
+                    </tr>
+                    
                     <tr>
                         
                         <td nowrap="nowrap"><span style="display:none">2018-12-09T21:13:16&nbsp;</span>09-Dec-2018 21:13</td>
diff --git a/CHANGE_LOG/change-log.2.1.1.md b/CHANGE_LOG/change-log.2.1.1.md
index fbded275..cc3af9d7 100644
--- a/CHANGE_LOG/change-log.2.1.1.md
+++ b/CHANGE_LOG/change-log.2.1.1.md
@@ -2,6 +2,18 @@
 ## Commit Range: v2.1.0..HEAD
 
 
+* __Renamed YANG, TREE &amp; OAS files with 2.1.1 revision date @2018-12-10__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Mon, 10 Dec 2018 15:25:36 -0500
+    [ac2ccf54b97bdf48afae2108f1f9a48a231c1ef7](https://github.com/OpenNetworkingFoundation/TAPI/commit/ac2ccf54b97bdf48afae2108f1f9a48a231c1ef7)
+    
+
+* __Change Logs for Release 2.1.1__
+
+    [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Mon, 10 Dec 2018 14:30:13 -0500
+    [b9caaadaad5a5675acd41d16ddfaf7f084351b22](https://github.com/OpenNetworkingFoundation/TAPI/commit/b9caaadaad5a5675acd41d16ddfaf7f084351b22)
+    
+
 * __README updates and minor cleanup__
 
     [Karthik Sethuraman](mailto:karthik.sethuraman@necam.com) - Sun, 9 Dec 2018 21:13:16 -0500

Date	Author	Commit
2018-12-09T21:13:16 09-Dec-2018 21:13	Karthik Sethuraman	+ 8a98f669567cea1777fbf9719d4bb88161520bee + + README updates and minor cleanup + +
2018-12-08T19:48:08 08-Dec-2018 19:48	Karthik Sethuraman	+ ac011c1b35f01440c3c56174df871c9fa3e0eb8f + + TAPI Python client implementation + +
2018-12-08T19:47:30 08-Dec-2018 19:47	Karthik Sethuraman	+ 6922098f42d82995e431aba070f5f1a90aa228c7 + + cleanup and minor fixes + +
2018-12-07T22:37:57 07-Dec-2018 22:37	Karthik Sethuraman	+ 1025912b1005198fd579cd8d454e6ad3fee4888a + + basic topology api implementations + +
2018-12-07T21:35:58 07-Dec-2018 21:35	Karthik Sethuraman	+ 88a8af56a6376d6ebf4dcd50d731a88fe910caba + + ODU Context topology from earlier TAPI version - need update + +
2018-12-07T21:34:44 07-Dec-2018 21:34	Karthik Sethuraman	+ 99e08b46da21a80c63ee8cf2f55ddac0176b6ac6 + + clean-up commented code + +
2018-12-07T21:34:20 07-Dec-2018 21:34	Karthik Sethuraman	+ e12a45f99a70c0eb3a29c595b86293226a82b902 + + TPD & OLS Contexts topologies + +
2018-12-04T23:17:36 04-Dec-2018 23:17	Ai Hamano	+ c9ed33cdf01fd95b84cbc7f7b01d0f0d2d04eec4 + + Convert tabs into spaces and fix the indentation + +
2018-11-29T16:32:45 29-Nov-2018 16:32	Karthik Sethuraman	+ 4996056d6fa1226bd6f9927b499c579897492502 + + Initial commit of TAPI RI for v2.1.1 - also removed old RI + +
2018-11-29T10:47:39 29-Nov-2018 10:47	karthik-sethuraman	+ 90bce6ac0c84e793615902979605bd651d588fac + + Fix #196/#372: added MC-SIP, MC-CEP & OTSi-CEP augments to RPCs + +
2018-11-29T10:46:06 29-Nov-2018 10:46	karthik-sethuraman	+ 743d49b3f42ed411561882bf60b77ad500c3630f + + Fix #196: Added getConnectionEndPointDetails RPC to tapi-connectivity + +
2018-11-28T17:20:08 28-Nov-2018 17:20	Karthik Sethuraman	+ 84389eb4bf4eff80611d3aa9d902e84d1c8ca400 + + Manual fix for missing ConnectivityService definition + +
2018-11-27T21:59:29 27-Nov-2018 21:59	karthik-sethuraman	+ cdb2163d29bce31ea0af5da8f8a70437a8efb089 + + Fix #372: Generated .tree & .oas files from the updated yang files + +
2018-11-27T21:52:15 27-Nov-2018 21:52	karthik-sethuraman	+ 4fa0699a1c64ff2d12ce72c44869e43bd8e5353d + + Fix #372: Added 'key" to complex data-types used as list attribute + +
2018-11-27T21:12:52 27-Nov-2018 21:12	karthik-sethuraman	+ 3bead76029659d2ab26ff7b7abcecf3dd7edb317 + + Fix #372: Added 'key" to SpectrumBand & CentralFrequency data-types + +
2018-11-27T21:10:53 27-Nov-2018 21:10	karthik-sethuraman	+ 21849dfa1725282276b5c515ed7110ae4caf8120 + + Fix #372: Added 'key' sub-statements to 'list' outputs of RPCs + +
2018-11-27T16:55:24 27-Nov-2018 16:55	karthik-sethuraman	+ cb6d9d4c903fa8a8b6802d1c22b0ec2a9a18181b + + Fix #372: Added 'key' sub-statements to 'list' outputs of RPCs + +
2018-11-27T16:46:55 27-Nov-2018 16:46	karthik-sethuraman	+ 0c566fe3b2c8efe925ddd5a7f9948f2df02a9b83 + + Partial fix #196 - updated photonic-media with RPC augments + +
2018-10-19T12:48:35 19-Oct-2018 12:48	Karthik Sethuraman	+ 433c06a4447182a52308132cf17ea1965d3fd98e + + Replaced Developer guide with Implementation guide + +
2018-10-19T12:14:38 19-Oct-2018 12:14	Karthik Sethuraman	+ 9ad9b6d616ae11490e5a20c11748f771e16717cc + + Updated README based on TST approved TAPI 2.1 release notes + +