From nobody Thu Dec 7 16:47:43 2017 Return-Path: X-Original-To: rfc-markdown@ietfa.amsl.com Delivered-To: rfc-markdown@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5CBB126C26 for ; Thu, 7 Dec 2017 16:47:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 cm-K1FTM1VOE for ; Thu, 7 Dec 2017 16:47:37 -0800 (PST) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F2B112762F for ; Thu, 7 Dec 2017 16:47:37 -0800 (PST) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id vB80lVbs004465; Fri, 8 Dec 2017 01:47:31 +0100 (CET) Received: from [192.168.217.124] (p5DC7E827.dip0.t-ipconnect.de [93.199.232.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3ytDGC5L9SzDXbW; Fri, 8 Dec 2017 01:47:31 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Carsten Bormann In-Reply-To: Date: Fri, 8 Dec 2017 01:47:30 +0100 Cc: RFC Interest , RFC Markdown X-Mao-Original-Outgoing-Id: 534386850.340844-5cff76d6ad65f0c0298feaa091e7f4e3 Content-Transfer-Encoding: quoted-printable Message-Id: <9FC5EDD7-BCC4-4DF9-9671-3BBDDDD581D3@tzi.org> References: To: Jeffrey Yasskin X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Rfc-markdown] [rfc-i] How do drafts get section links? X-BeenThere: rfc-markdown@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2017 00:47:42 -0000 Hi Jeffrey, On Dec 8, 2017, at 01:11, Jeffrey Yasskin wrote: >=20 > What's the right way to get deep links to sections from = kramdown-rfc2629 source? (Sections of other documents, that is.) RFCXML version 2 has no way to do this, so kramdown-rfc doesn=E2=80=99t = support it. So why are you seeing links on tools.ietf.org (and only there) where = there aren=E2=80=99t any? The .txt to .html converter at tools.ietf.org has some heuristics that = allow it to identify references to sections of other RFCs. These = heuristics sometimes fail to notice (and famously sometimes point to the = wrong document, leading to spurious errata about problems that aren=E2=80=99= t even in the RFC), but they are better than nothing. Now how is the syntax for deep links into documents going to look like = in kramdown-rfc when we add RFCXML v3 support? I don=E2=80=99t know yet. But I note that essentially the same = heuristics that work on .txt files on tools.ietf.org might work in a = markdown source document (and, if they don=E2=80=99t, the author can = still set a manual xref [er, relref, if that thing stays in v3]). (CCing rfc-markdown, as the question is of interest there, too; please = trim the CC list if you just want to vent about relref, as you probably = should at this point.) Gr=C3=BC=C3=9Fe, Carsten From nobody Thu Dec 7 20:45:41 2017 Return-Path: X-Original-To: rfc-markdown@ietfa.amsl.com Delivered-To: rfc-markdown@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83D3A129508 for ; Thu, 7 Dec 2017 20:45:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=chromium.org 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 EbuexV1fuHoV for ; Thu, 7 Dec 2017 20:45:37 -0800 (PST) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (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 3C62C129503 for ; Thu, 7 Dec 2017 20:45:37 -0800 (PST) Received: by mail-it0-x22d.google.com with SMTP id z6so2318639iti.4 for ; Thu, 07 Dec 2017 20:45:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CNhX6j+p3MMPEvy4vIylgZi0b134Ge9AIuwYxovZPVo=; b=HkKPmgTwGq2jvij+iCQa7unwV41CnRaaVASSPfUDrYgAj3C0S3m9hA9Gsz3DGBVj7i UL/J4/a6efbONhGO9b2tQNYEpOyEv58NBPoqceqNV/n7xVTC5SbY7hBAtkChd32wW7fF /nMOMwzKF6fP8MC4PXv+oc8YXkWB/+o9wXeh4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CNhX6j+p3MMPEvy4vIylgZi0b134Ge9AIuwYxovZPVo=; b=aq5iH6Ajq0M5m3hQL8PSvJHwqOoVOm1ioX4vNSEvyjRVokzmvUrs6mGSnALQ9h2sDR NxeJF7boRX0irHkNU3t5htsOK0oqFUQyX1EiJlsx+/UpCPtZZVQv9PdGzLOenCXn9BQ6 CxXDj0ON2ZIweRmsUQozDFi1nwhfDIlKgIXVJCarZGkvRk2416tM7DUS935fS1BzaWHK zGs1q9rwW+aKLxDbxk6A7PYrjeakQcPJMTycBj+t6vMagochuy4iMjrwTEAj2Uvw/uF/ fbrIcsqrXRa3bwxdALJNlv9qvb8RS6aCVa17D5mc3eWrEJWLGjTDo5g8kHvkieypi4ud 4crQ== X-Gm-Message-State: AJaThX5kWy1+kZfEi/VqVFrjJzO1hglidllDMGNKxGbU4sIUFHaIwAHN MG44zD4Pp59yrOVrndeimmy7+mAoQXhCgsHk0Ruv/Q== X-Google-Smtp-Source: AGs4zMYQc8osxT2SNlGocGb+FCn+tJbIuhZDKY+XTqtd2q+dN35OoxZmpzpkoV6sk2EzS+4q+Gx5TdZKsMzYJrN3hq8= X-Received: by 10.107.205.69 with SMTP id d66mr43684920iog.254.1512708335972; Thu, 07 Dec 2017 20:45:35 -0800 (PST) MIME-Version: 1.0 References: <9FC5EDD7-BCC4-4DF9-9671-3BBDDDD581D3@tzi.org> In-Reply-To: <9FC5EDD7-BCC4-4DF9-9671-3BBDDDD581D3@tzi.org> From: Jeffrey Yasskin Date: Fri, 08 Dec 2017 04:45:25 +0000 Message-ID: To: Carsten Bormann Cc: Jeffrey Yasskin , rfc-interest@rfc-editor.org, rfc-markdown@ietf.org Content-Type: multipart/alternative; boundary="94eb2c188716045531055fccdb44" Archived-At: Subject: Re: [Rfc-markdown] [rfc-i] How do drafts get section links? X-BeenThere: rfc-markdown@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2017 04:45:39 -0000 --94eb2c188716045531055fccdb44 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Dec 7, 2017 at 4:47 PM Carsten Bormann wrote: > Hi Jeffrey, > > On Dec 8, 2017, at 01:11, Jeffrey Yasskin wrote: > > > > What's the right way to get deep links to sections from kramdown-rfc262= 9 > source? > > (Sections of other documents, that is.) > > RFCXML version 2 has no way to do this, so kramdown-rfc doesn=E2=80=99t s= upport it. > Yeah, I mostly mentioned kramdown-rfc to make sure any answers like "use https://www.greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#ext-rfc2= 629.xref" included instructions for how to get the right attributes into the XML from .md source. So why are you seeing links on tools.ietf.org (and only there) where there > aren=E2=80=99t any? > The .txt to .html converter at tools.ietf.org has some heuristics that > allow it to identify references to sections of other RFCs. These > heuristics sometimes fail to notice (and famously sometimes point to the > wrong document, leading to spurious errata about problems that aren=E2=80= =99t even > in the RFC), but they are better than nothing. > Ah, I see: https://tools.ietf.org/tools/rfcmarkup/ does this for URLs under https://tools.ietf.org/html/, but the id/ URLs only use xml2rfc or rfc2629.xslt and so don't get the benefit. That answers my question of how to test that my source gives the right section links, and in fact https://tools.ietf.org/html/draft-yasskin-http-origin-signed-responses-01#s= ection-2 has decent deep links, while https://tools.ietf.org/id/draft-ietf-httpbis-origin-frame-04.html#rfc.secti= on.1 doesn't. I'm happy to conclude that my mistake was in sending out the wrong links, and that this list doesn't need to do anything until RFCXML v3 support comes along. Now how is the syntax for deep links into documents going to look like in > kramdown-rfc when we add RFCXML v3 support? > I don=E2=80=99t know yet. But I note that essentially the same heuristic= s that > work on .txt files on tools.ietf.org might work in a markdown source > document (and, if they don=E2=80=99t, the author can still set a manual x= ref [er, > relref, if that thing stays in v3]). > (https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/26) (CCing rfc-markdown, as the question is of interest there, too; please trim > the CC list if you just want to vent about relref, as you probably should > at this point.) Thanks, Jeffrey --94eb2c188716045531055fccdb44 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Dec 7,= 2017 at 4:47 PM Carsten Bormann <cabo@tzi.org> wrote:
Hi Jeffrey,

On Dec 8, 2017, at 01:11, Jeffrey Yasskin <jyasskin@chromium.org> wrote:
>
> What's the right way to get deep links to sections from kramdown-r= fc2629 source?

(Sections of other documents, that is.)

RFCXML version 2 has no way to do this, so kramdown-rfc doesn=E2=80=99t sup= port it.

Yeah, I mostly mentioned kramd= own-rfc=C2=A0to make sure any answers like "use https://www.greenbytes.de/tech/webdav/rfc2629xslt/rfc2629x= slt.html#ext-rfc2629.xref" included instructions for how to get th= e right attributes into the XML from .md source.

So why are you seeing links on tools.ietf.org (and only there) where there = aren=E2=80=99t any?
The .txt to .html converter at tools.ietf.org has some heuristics that allo= w it to identify references to sections of other RFCs.=C2=A0 These heuristi= cs sometimes fail to notice (and famously sometimes point to the wrong docu= ment, leading to spurious errata about problems that aren=E2=80=99t even in= the RFC), but they are better than nothing.

Ah, I see:=C2=A0https://tools.ietf.org/tools/rfcmarkup/ does this for = URLs under https= ://tools.ietf.org/html/, but the id/ URLs only use xml2rfc or rfc2629.x= slt=C2=A0and so don't get the benefit. That answers my question of how = to test that my source gives the right section links, and in fact https://tools.ietf.org/html/draft-yasskin-h= ttp-origin-signed-responses-01#section-2 has decent deep links, while <= a href=3D"https://tools.ietf.org/id/draft-ietf-httpbis-origin-frame-04.html= #rfc.section.1" target=3D"_blank">https://tools.ietf.org/id/draft-ietf-http= bis-origin-frame-04.html#rfc.section.1 doesn't.

I'm happy to conclude that my mistake was in sending out the wron= g links, and that this list doesn't need to do anything until RFCXML v3= support comes along.

Now how is the syntax for deep links into documents going to look like in k= ramdown-rfc when we add RFCXML v3 support?
I don=E2=80=99t know yet.=C2=A0 But I note that essentially the same heuris= tics that work on .txt files on tools.ietf.org might work in a markdown sou= rce document (and, if they don=E2=80=99t, the author can still set a manual= xref [er, relref, if that thing stays in v3]).


(CCing rfc-markdown, a= s the question is of interest there, too; please trim the CC list if you ju= st want to vent about relref, as you probably should at this point.)=

Thanks,
Jeffrey
--94eb2c188716045531055fccdb44-- From nobody Thu Dec 7 21:46:56 2017 Return-Path: X-Original-To: rfc-markdown@ietfa.amsl.com Delivered-To: rfc-markdown@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28AC3128891 for ; Thu, 7 Dec 2017 21:46:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.4 X-Spam-Level: X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 y7kpvxCWwrcx for ; Thu, 7 Dec 2017 21:46:53 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 CCEBC124205 for ; Thu, 7 Dec 2017 21:46:52 -0800 (PST) Received: from [192.168.178.20] ([93.217.125.18]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MWkep-1eXxve45AR-00Xqth; Fri, 08 Dec 2017 06:46:42 +0100 To: Carsten Bormann , Jeffrey Yasskin Cc: RFC Markdown , RFC Interest References: <9FC5EDD7-BCC4-4DF9-9671-3BBDDDD581D3@tzi.org> From: Julian Reschke Message-ID: Date: Fri, 8 Dec 2017 06:46:41 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <9FC5EDD7-BCC4-4DF9-9671-3BBDDDD581D3@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:vobPSCEFDunYTrLgZ+zW3KNlzpImfzDejV1EczPRHptOc0p0DyX tc83GqYPCl6ssonUm+Z04waa9g4AJiA05dZWHKiHcjGx6j+oSzR2T/9eHaf59tz12dgsbyS gDkgYqI0HFtDfsANDuZMiJaVxtcQsbJYunSYp8YOMcC1kk+bl9v+7uM5dUsfBrSrch2pFOC j7uQHFY/HgBUB1vI1x7YQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:gZrqGQYBsyU=:67ms6Ly2Rnj9SC/JQFCzw6 pmNnG0Expa+DDL9mWj1wMken5Cf7LvQp0aPpJtUwuokj5pYz/3auJgXtEPLBzRz1oGFH8FGpg fbMmKNMaadDWny7WOM3oKZFjwbBrautCBA/c73aiPVC6BlTOEE6j7dog6ueP+qfxW8r1HCBqB DbKdSExm6iqQKjaoOBvyvsVgWl396Ia5MkNldrT4aToiC9/5XTlf+U8LENesa2iUhPvVOQsDC iOOc7q97NmV5abnJAZWS6QxRSPyj2VRr6uKemcmqqjENLZEzlENm6bhcq/dwDwOAwuNeUYZoZ Heuw2rXdYHksGZ68DDEUm7dpyAo0TM5L+wdPWhe7N6Idu7+M+DBjFM/Eh2+omg67aaAf2IXZO H63pIoBYLdM/1w4EHDP4m5dHHeFZPbJnS2GB2G5E7SCpki7nxT666reYP3P1Euavt+/8nfQBW L8ZhiQhzM66zobmQ270YCG2ZOhGxlvay6OwVbHSppF2v4aRjXrr62/e9DSd4LrkDn320E/1oA 6tFPVxU2pp4uUWXfW/y6LSKkUZBG8dju83CT1SGer2zhcPgPWZFwJwwZg2E2lgNJAyv8umEky /Oi5SBJsXpagv7pc94wNCCfvijJ/h6XFAWpCvFVmlKdKitwJ/rIIvbUDdrbYTePiUgypNccTE wueqoaMs/GEiwsnEdW0us5Oq/o+hET+lHy6W2d3QC/Hk1pUwyDv86MbeDeMvR/Wb4E2C3ppmN byXBaHGKBSbSyA2sgqbV3vXRwXimVEn8aoXpBWTieV9fNRZ7I0PO4G7cwFjFYk6HkxFDRHJWK re2O86fBL35NaZO2lI4RHrapbvI8xMUuT2UewhJwanUckPhMmo= Archived-At: Subject: Re: [Rfc-markdown] [rfc-i] How do drafts get section links? X-BeenThere: rfc-markdown@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2017 05:46:55 -0000 On 2017-12-08 01:47, Carsten Bormann wrote: > Hi Jeffrey, > > On Dec 8, 2017, at 01:11, Jeffrey Yasskin wrote: >> >> What's the right way to get deep links to sections from kramdown-rfc2629 source? > > (Sections of other documents, that is.) > > RFCXML version 2 has no way to do this, so kramdown-rfc doesn’t support it. FWFW, rfc2629.xslt does, see , so kramdown-rfc in theory could support it for that backend. > So why are you seeing links on tools.ietf.org (and only there) where there aren’t any? > The .txt to .html converter at tools.ietf.org has some heuristics that allow it to identify references to sections of other RFCs. These heuristics sometimes fail to notice (and famously sometimes point to the wrong document, leading to spurious errata about problems that aren’t even in the RFC), but they are better than nothing. Right. > Now how is the syntax for deep links into documents going to look like in kramdown-rfc when we add RFCXML v3 support? > I don’t know yet. But I note that essentially the same heuristics that work on .txt files on tools.ietf.org might work in a markdown source document (and, if they don’t, the author can still set a manual xref [er, relref, if that thing stays in v3]). > > (CCing rfc-markdown, as the question is of interest there, too; please trim the CC list if you just want to vent about relref, as you probably should at this point.) I did some experiments with the output of kramdown-rfc as used in HTTP and QUIC WG documents (for instance: ), and heuristics work a bit better if you do not have to worry about line breaks. But it's still only heuristics. Best regards, Julian