[rfc-i] The New RFC Editor Website
daedulus at btconnect.com
Fri Oct 16 02:54:27 PDT 2015
----- Original Message -----
From: "Heather Flanagan (RFC Series Editor)" <rse at rfc-editor.org>
To: "t.p." <daedulus at btconnect.com>; "IETF" <ietf at ietf.org>
Sent: Monday, October 12, 2015 4:38 PM
Subject: Re: The New RFC Editor Website
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> On 10/11/15 1:34 AM, t.p. wrote:
> > Will there ever be a web site redesign that does not generate a 404?
> > Probably not.
> Of course not. Murphy's Law is a powerful force.
> > In this case, you get one when you look to see what feedback there
> > has been previously, to see if others are experiencing the same
> > problems as you are and the answer is, 404! Has there been feedback
> > about this already? 404!
> Interesting; that worked before, and we haven't turned off http access
> (if you go to
> https://www.rfc-editor.org/rse/wiki/doku.php?id=webfeedback instead of
> http://www.rfc-editor.org/rse/wiki/doku.php?id=webfeedback, which is
> where that feedback link goes, it works. Well, it works for me. Your
> mileage _shouldn't_ vary...)
And today, my mileage is consistently the same as yours; Murphy strikes
> Thanks for the report.
> - -Heather
> > Tom Petch
> > ----- Original Message ----- From: "IETF Chair" <chair at ietf.org> To:
> > "IETF Announcement List" <ietf-announce at ietf.org> Cc: "Heather
> > Flanagan (RFC Series Editor)" <rse at rfc-editor.org>; "IETF"
> > <ietf at ietf.org> Sent: Wednesday, October 07, 2015 5:15 PM
> > I wanted to introduce people to the new RFC Editor website and send
> > link to Heather’s blog article about the changes:
> > https://www.rfc-editor.org
> > https://www.ietf.org/blog/2015/10/the-new-rfc-editor-website/
> > Jari Arkko, IETF Chair
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2
> Comment: GPGTools - http://gpgtools.org
> -----END PGP SIGNATURE-----
More information about the rfc-interest