Tom -
The page you link to is a page that shows, using html, a lot of
metadata, and (currently) an inlined text display. There is discussion
around replacing the inlined text display with what you see at /doc/html
(essentially merging the views so that the metadata becomes accessible
when you need it. So, yes, "save as" on that page is going to give you
something messy if you were hoping to just get the text file.
There are links (that look like buttons) on that page to the other
formats. If you want the plain-text format, click the link on the
Formats row that says `txt`.
For what it's worth, that link will retrieve the draft from the
id-archive at https://www.ietf.org/archive/id.
RjS
On 7/15/24 5:31 AM, Julian Reschke wrote:
Am 15.07.2024 um 12:03 schrieb tom petch:
...
<tp>
The server is whatever the IETF is using for e.g.
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-sendholdtimer/
This is probably a shadow rather than the real web site which I
suspect cannot be accessed with Windows from my PC because of the way
the IETF works.
I don't get that. What do you mean by "shadow" and "because of the way
the IETF works"?
The user agent is
Firefaox 121.0 (64 bit)
The file format is whatever the IETF is using for the above draft
when I select
Formats HTML - the result contains so much cruft as to render work
impractical e.g. below (the hyphens being separators I have added).
...
And what does this have to do with http(s) as protocol?
It seems you don't like the HTML format of internet drafts and RFCs, but
that's an entirely different issue...
Best regards, Julian
