Update doc

doc/programmers-guide.rst

@@ -110,9 +110,9 @@ HTTP Messaging
 
 By default, nghttp2 library checks HTTP messaging rules described in
 `HTTP/2 specification, section 8
-<https://tools.ietf.org/html/draft-ietf-httpbis-http2-17#section-8>`_.
-Everything described in that section is not validated however.  We
-briefly describe what the library does in this area.  In the following
+<https://tools.ietf.org/html/rfc7540#section-8>`_.  Everything
+described in that section is not validated however.  We briefly
+describe what the library does in this area.  In the following
 description, without loss of generality we omit CONTINUATION frame
 since they must follow HEADERS frame and are processed atomically.  In
 other words, they are just one big HEADERS frame.  To disable these
@@ -249,7 +249,7 @@ set to :type:`nghttp2_session_callbacks` using
 `nghttp2_session_callbacks_set_pack_extension_callback()`.
 
 For example, we will illustrate how to send `ALTSVC
-<https://tools.ietf.org/html/draft-ietf-httpbis-alt-svc-14>`_ frame.
+<https://tools.ietf.org/html/rfc7838>`_ frame.
 
 .. code-block:: c
 

doc/sources/nghttpx-howto.rst

@@ -483,9 +483,9 @@ not wait for handshake to complete before forwarding request included
 in 0-RTT to get full potential of 0-RTT data.  In this case, nghttpx
 adds ``Early-Data: 1`` header field when forwarding a request to a
 backend server.  All backend servers should recognize this header
-field and understand that there is a risk for replay attack.  See
-https://tools.ietf.org/html/draft-ietf-httpbis-replay-04 for
-``Early-Data`` header field.
+field and understand that there is a risk for replay attack.  See `RFC
+8470 <https://tools.ietf.org/html/rfc8470>`_ for ``Early-Data`` header
+field.
 
 nghttpx disables anti replay protection provided by OpenSSL.  The anti
 replay protection of OpenSSL requires that a resumed request must hit