From: Christoph Hellwig <hch@infradead.org>
To: David Vernet <void@manifault.com>
Cc: Will Hawkins <hawkinsw@obs.cr>, bpf@ietf.org, bpf@vger.kernel.org
Subject: Re: [Bpf] [PATCH] bpf, docs: Add additional ABI working draft base text
Date: Mon, 23 Oct 2023 21:02:49 -0700 [thread overview]
Message-ID: <ZTdB6dJSum4p63oR@infradead.org> (raw)
In-Reply-To: <20231024005528.GA33696@maniforge>
On Mon, Oct 23, 2023 at 07:55:28PM -0500, David Vernet wrote:
> > You make an excellent point. Although v2 does not make this change, do
> > you think that a reasonable adjustment would be to simply move this
> > section to the end of the document?
>
> My initial expectation is that it's not a great idea to reference
> external documents that could change, no longer be valid links, etc, but
> I'd like to hear what others think. Dave -- is this typical for an IETF
> informational document? It seems like if we did this we'd basically be
> taking implicit dependencies on documents we can't actually control
> (because they're not IETF), but I have no idea if this is normal or not.
IETF prefers IETF references, and if not stable standards-like
documents. Even those will get careful review (talking as someone
with a draft that has normative SCSI and NVMe references right now).
For non-normative references this is a bit relaxed, but a random url
that can change is never acceptable.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: David Vernet <void@manifault.com>
Cc: Will Hawkins <hawkinsw@obs.cr>, bpf@ietf.org, bpf@vger.kernel.org
Subject: Re: [Bpf] [PATCH] bpf, docs: Add additional ABI working draft base text
Date: Mon, 23 Oct 2023 21:02:49 -0700 [thread overview]
Message-ID: <ZTdB6dJSum4p63oR@infradead.org> (raw)
Message-ID: <20231024040249.D-p4poKr-R3FnaX4KOcTxRQr2_zbnuMB6my-SngbEnY@z> (raw)
In-Reply-To: <20231024005528.GA33696@maniforge>
On Mon, Oct 23, 2023 at 07:55:28PM -0500, David Vernet wrote:
> > You make an excellent point. Although v2 does not make this change, do
> > you think that a reasonable adjustment would be to simply move this
> > section to the end of the document?
>
> My initial expectation is that it's not a great idea to reference
> external documents that could change, no longer be valid links, etc, but
> I'd like to hear what others think. Dave -- is this typical for an IETF
> informational document? It seems like if we did this we'd basically be
> taking implicit dependencies on documents we can't actually control
> (because they're not IETF), but I have no idea if this is normal or not.
IETF prefers IETF references, and if not stable standards-like
documents. Even those will get careful review (talking as someone
with a draft that has normative SCSI and NVMe references right now).
For non-normative references this is a bit relaxed, but a random url
that can change is never acceptable.
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2023-10-24 4:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 14:19 [PATCH] bpf, docs: Add additional ABI working draft base text Will Hawkins
2023-10-02 14:19 ` [Bpf] " Will Hawkins
2023-10-03 18:26 ` David Vernet
2023-10-03 18:26 ` [Bpf] " David Vernet
2023-10-21 23:13 ` Will Hawkins
2023-10-21 23:13 ` [Bpf] " Will Hawkins
2023-10-21 23:26 ` [PATCH v2] " Will Hawkins
2023-10-21 23:26 ` [Bpf] " Will Hawkins
2023-10-24 0:55 ` [PATCH] " David Vernet
2023-10-24 0:55 ` [Bpf] " David Vernet
2023-10-24 4:02 ` Christoph Hellwig [this message]
2023-10-24 4:02 ` Christoph Hellwig
2023-11-03 21:14 ` Will Hawkins
2023-11-03 21:14 ` Will Hawkins
2023-11-03 21:20 ` [PATCH v3] " Will Hawkins
2023-11-03 21:20 ` [Bpf] " Will Hawkins
2023-11-05 9:51 ` Alexei Starovoitov
2023-11-05 9:51 ` Alexei Starovoitov
2023-11-06 0:17 ` Will Hawkins
2023-11-06 0:17 ` Will Hawkins
2023-11-06 8:38 ` Alexei Starovoitov
2023-11-06 8:38 ` Alexei Starovoitov
2023-11-07 19:56 ` Will Hawkins
2023-11-07 19:56 ` Will Hawkins
2023-11-08 1:17 ` Alexei Starovoitov
2023-11-08 1:17 ` Alexei Starovoitov
2023-11-08 10:13 ` Will Hawkins
2023-11-08 10:13 ` Will Hawkins
2023-11-08 19:51 ` Alexei Starovoitov
2023-11-08 19:51 ` Alexei Starovoitov
2023-11-08 23:57 ` Will Hawkins
2023-11-08 23:57 ` Will Hawkins
2023-11-09 18:31 ` Alexei Starovoitov
2023-11-09 18:31 ` Alexei Starovoitov
2023-11-10 0:56 ` Will Hawkins
2023-11-10 0:56 ` Will Hawkins
2023-11-10 1:35 ` Will Hawkins
2023-11-10 1:35 ` Will Hawkins
2023-10-19 6:01 ` [Bpf] [PATCH] " Christoph Hellwig
2023-10-19 6:01 ` Christoph Hellwig
2023-10-20 2:42 ` Will Hawkins
2023-10-20 2:42 ` Will Hawkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZTdB6dJSum4p63oR@infradead.org \
--to=hch@infradead.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=hawkinsw@obs.cr \
--cc=void@manifault.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.