Re: [OAUTH-WG] broken links in draft-ietf-oauth-introspection-11
Brian Campbell <bcampbell@pingidentity.com> Sun, 19 July 2015 14:51 UTC
Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 922271AD351 for <oauth@ietfa.amsl.com>; Sun, 19 Jul 2015 07:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3McEXtG9nf7B for <oauth@ietfa.amsl.com>; Sun, 19 Jul 2015 07:51:29 -0700 (PDT)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E26381AD350 for <oauth@ietf.org>; Sun, 19 Jul 2015 07:51:28 -0700 (PDT)
Received: by iehx8 with SMTP id x8so23291543ieh.3 for <oauth@ietf.org>; Sun, 19 Jul 2015 07:51:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=LAmJoZ3WRC5xJwIwZGwCECLP7OV5DcbqcTqBXzEeLgY=; b=V69c3dXKMGyrsXdG9k9n2dfTW2xcVBVCkVGu/uhSgS+5B36AdQC4+YDUIANHOl/S7J p3xR+qeWW2L076Z3ir+NSjuqrBaTK+X8RRd4QCC8t0kgMjLC8bLOyVCrCDQCIVBfuh1W fOiqqA7fR/76H0AApaBBC/I5u3SaRsNFB1csU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=LAmJoZ3WRC5xJwIwZGwCECLP7OV5DcbqcTqBXzEeLgY=; b=aMxHC5F2tCA9pXnx8QeE/0Cg2KD+GhG447fdk/6GDkOw/Es0Pthpt2hLUot3w/JwUF uCSmNsDrNJrORfSNaQ7LE9gRSiA2sx5BxmmxcCoxEwmAg4EieqlllGl2pabyxtscatuH uoDHaqyHvWmNa1xxqY+y7Ll6PaeeiHh/X+IYsGmFjxWUS1kuW0eX2cbPEliImc0EZb6N lGs43uF8kszSivS+/xyLt5Gic+UzfTOdX8UJIb4s/hMb71t03jf4RQfZpXrLlMR/LgpW gYFrZb/VC8ccn6I7K8yftMtwXeIrdxj5tNpEKZ3FK9/uWd8O3ywxUwwoaFEaWEGSKaGn vjIA==
X-Gm-Message-State: ALoCoQnVGQ+PHFDzNgn6khm7IvsIfJMc7MVu3vapZUMoKy1UIc5IvcgQCh41zVSxJ0Hdf36q5PpR
X-Received: by 10.50.30.226 with SMTP id v2mr7713559igh.3.1437317488299; Sun, 19 Jul 2015 07:51:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.96.199 with HTTP; Sun, 19 Jul 2015 07:50:58 -0700 (PDT)
In-Reply-To: <D9FBA222-6ECA-4261-A42F-A902775D9E4B@ve7jtb.com>
References: <CAGBSGjprEOdZ4yXMuQ8ofEmNHy4X4bhjH_z7k3eUVZzBTSZR6Q@mail.gmail.com> <AAD0E675-F885-4ACE-8438-3AD045364A33@mit.edu> <D9FBA222-6ECA-4261-A42F-A902775D9E4B@ve7jtb.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Sun, 19 Jul 2015 16:50:58 +0200
Message-ID: <CA+k3eCQK3FFA8igN1oDeiGvzxXxk1rU8UXrtD5fnHMRGJ3iv=A@mail.gmail.com>
To: John Bradley <ve7jtb@ve7jtb.com>, Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary="047d7b86d50251f6dc051b3b8e41"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/LFC70YWV4Lg_HclSNXEWe4fBTG0>
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] broken links in draft-ietf-oauth-introspection-11
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Jul 2015 14:51:30 -0000
Barry explained the tools issue that causes this and how to work around it a while back on the JOSE list: http://www.ietf.org/mail-archive/web/jose/current/msg04571.html On Sun, Jul 19, 2015 at 2:09 PM, John Bradley <ve7jtb@ve7jtb.com> wrote: > Remember tools is not using the XML to render the HTML directly, it is > marking up the text version. This bites me all the time as well. > > The text version needs to render to “Section 3.3 of RFC 6749” to get Rfcmarkup > tool <http://tools.ietf.org/tools/rfcmarkup/index> to render it > correctly. > > The trailing of OAuth 2.0 messes up Rfcmarkup. > > I am looking at fixing PIXE for the RFC editor so this happens to be a > current issue for me, as I did the same thing because that is what produces > the best HTML output from XML2RFC. > > What I have learned is to NOT format looking at the html output from > XML2RFC as it leads you in the wrong direction, output as text then run > through Rfcmarkup to see what the version on the document tracker will look > like. > > Hope this saves you some time. > > John B. > > > On Jul 19, 2015, at 7:05 AM, Justin Richer <jricher@mit.edu> wrote: > > Thanks, those are artifacts in the rendered XML, I’ll look into fixing > them. > > — Justin > > On Jul 19, 2015, at 3:24 AM, Aaron Parecki <aaron@parecki.com> wrote: > > In section 2.2, > https://tools.ietf.org/html/draft-ietf-oauth-introspection-11#section-2.2 > the "scope" description references section 3.3 of RFC6749, but the > hyperlink contains just the fragment #section-3.3 which then points to the > current page. The same problem exists with the "token_type" parameter. > Additionally, I believe the token type link should point to section 7.1 ( > https://tools.ietf.org/html/rfc6749#section-7.1) which is where token > types are defined. Thanks! > > ---- > Aaron Parecki > aaronparecki.com > @aaronpk <http://twitter.com/aaronpk> > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > >
- [OAUTH-WG] broken links in draft-ietf-oauth-intro… Aaron Parecki
- Re: [OAUTH-WG] broken links in draft-ietf-oauth-i… Justin Richer
- Re: [OAUTH-WG] broken links in draft-ietf-oauth-i… John Bradley
- Re: [OAUTH-WG] broken links in draft-ietf-oauth-i… Brian Campbell
- Re: [OAUTH-WG] broken links in draft-ietf-oauth-i… Justin Richer