Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?

[Marshall Eubanks <tme at multicasttech.com>]

I know that there is work going on today with the transfer of  
services from NSS
to AMS, and I suspect that these errors may be connected to this.  
(Note that IPv4 and
IPv6 are being done somewhat separately, so what works for one  
version may not for the other.)

I would suggest sending any 404 errors, DNS lookup errors, etc., to  
our IAD.

Regards
Marshall


On Dec 14, 2007, at 9:10 AM, Roy Arends wrote:

> On Dec 14, 2007, at 1:34 PM, Stephane Bortzmeyer wrote:
>
> > On Thu, Dec 13, 2007 at 07:17:15PM -0500,
> > Russ Housley <housley at vigilsec.com> wrote
> > a message of 31 lines which said:
> >
> > > Another possible remedy might be to withdraw the RFC.  This remedy
> > > is not as attractive because there is no procedure to do it.
> >
> > Is it to test the future procedure that RFC 4390 is no longer
> > downloadable? :-)
> >
> > http://www.ietf.org/rfc/rfc4390.txt
> >
> > Forbidden
> >
> > You don't have permission to access /rfc/rfc4390.txt on this server.
> >
> > Additionally, a 403 Forbidden error was encountered while trying  
> > to use an ErrorDocument to handle the request.
> > Apache/2.0.52 (Red Hat) Server at www.ietf.org Port 80
>
> http://www.ietf.org/rfc/rfc4390
>
> _______________________________________________
> Ietf mailing list
> Ietf at ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf