Merge pull request #281 from WilliamDenniss/master

Updated references to the OAuth 2.0 for Native Apps BCP.

Author: WilliamDenniss

README.md

@@ -16,7 +16,7 @@ raw protocol flows, convenience methods are available to assist with common
 tasks like performing an action with fresh tokens.
 
 The library follows the best practices set out in
-[OAuth 2.0 for Native Apps](https://tools.ietf.org/html/draft-ietf-oauth-native-apps),
+[RFC 8252 - OAuth 2.0 for Native Apps](https://tools.ietf.org/html/rfc8252),
 including using
 [Custom Tabs](http://developer.android.com/tools/support-library/features.html#custom-tabs)
 for authorization requests. For this reason,
@@ -46,7 +46,7 @@ Both Custom URI Schemes (all supported versions of Android) and App Links (Andro
 be used with the library.
 
 In general, AppAuth can work with any Authorization Server (AS) that supports
-[native apps](https://tools.ietf.org/html/draft-ietf-oauth-native-apps),
+native apps as documented in [RFC 8252](https://tools.ietf.org/html/rfc8252),
 either through custom URI scheme redirects, or App Links.
 AS's that assume all clients are web-based or require clients to maintain
 confidentiality of the client secrets may not work well.

library/java/net/openid/appauth/package-info.java

@@ -24,7 +24,7 @@
  * fresh tokens.
  *
  * <p>The library follows the best practices set out in
- * <a href="https://tools.ietf.org/html/draft-ietf-oauth-native-apps">OAuth 2.0 for Native Apps</a>
+ * <a href="https://tools.ietf.org/html/rfc8252">RFC 8252 - OAuth 2.0 for Native Apps</a>
  * including using
  * <a href="http://developer.android.com/tools/support-library/features.html#custom-tabs">Custom
  * Tabs</a> for the auth request. For this reason, {@link android.webkit.WebView} is explicitly