Fix links to prevent redirects

IETF has retired tools, use rfc-editor/datatracker instead.

Change-Id: I1e033045b7e9dd61e02831dd4e2ebf793459fc93
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>

diff --git a/docs/dev-guide.rst b/docs/dev-guide.rst
index a5e0e3fc58b9cd6498320b04f239a78c4e922a1a..686cfefcde3dd6bc82db98bfd683e2738ef5ff9e 100644 (file)
--- a/docs/dev-guide.rst
+++ b/docs/dev-guide.rst
@@ -880,9 +880,9 @@ RESTCONF operations overview
 RESTCONF supports **OPTIONS**, **GET**, **PUT**, **POST**, and
 **DELETE** operations. Request and response data can either be in the
 XML or JSON format. XML structures according to yang are defined at:
 RESTCONF supports **OPTIONS**, **GET**, **PUT**, **POST**, and
 **DELETE** operations. Request and response data can either be in the
 XML or JSON format. XML structures according to yang are defined at:

-`XML-YANG <http://tools.ietf.org/html/rfc6020>`__. JSON structures are
+`XML-YANG <https://www.rfc-editor.org/rfc/rfc6020>`__. JSON structures are

 defined at:
 defined at:

-`JSON-YANG <http://tools.ietf.org/html/draft-lhotka-netmod-yang-json-02>`__.
+`JSON-YANG <https://datatracker.ietf.org/doc/html/draft-lhotka-netmod-yang-json-02>`__.

 Data in the request must have a correctly set **Content-Type** field in
 the http header with the allowed value of the media type. The media type
 of the requested data has to be set in the **Accept** field. Get the
 Data in the request must have a correctly set **Content-Type** field in
 the http header with the allowed value of the media type. The media type
 of the requested data has to be set in the **Accept** field. Get the


@@ -910,7 +910,7 @@ Identifier <https://wiki-archive.opendaylight.org/view/OpenDaylight_Controller:M
      be known which node is X (for example: C:X). For more details about
      encoding, see: `RESTCONF 02 - Encoding YANG Instance Identifiers in
      the Request
      be known which node is X (for example: C:X). For more details about
      encoding, see: `RESTCONF 02 - Encoding YANG Instance Identifiers in
      the Request

-     URI. <http://tools.ietf.org/html/draft-bierman-netconf-restconf-02#section-5.3.1>`__
+     URI. <https://datatracker.ietf.org/doc/html/draft-bierman-netconf-restconf-02#section-5.3.1>`__

 
 Mount point
 ~~~~~~~~~~~
 
 Mount point
 ~~~~~~~~~~~


@@ -1086,7 +1086,7 @@ DELETE /restconf/config/<identifier>
 -  <identifier> points to a data node which must be removed.
 
 More information is available in the `RESTCONF
 -  <identifier> points to a data node which must be removed.
 
 More information is available in the `RESTCONF

-RFC <http://tools.ietf.org/html/draft-bierman-netconf-restconf-02>`__.
+RFC <https://datatracker.ietf.org/doc/html/draft-bierman-netconf-restconf-02>`__.

 
 How RESTCONF works
 ~~~~~~~~~~~~~~~~~~
 
 How RESTCONF works
 ~~~~~~~~~~~~~~~~~~