Re: take the train in Chicago

2007-07-21 Thread Russ Housley
I used the train yesterday, and it worked as advertised.  It took 45 
minutes, and it was cheap.  However, it will be even slower for 
people arriving this weekend.  The train will stop running on a 
portion of the Blue Line Friday at 11PM (last night) until early 
Monday morning.  A shuttle bus will be used to move people around the 
closed portion of track.



*Blue Line Slow Zone Elimination Project*

*Effective 11:00 p.m., Friday, July 20 until 1:00 a.m., 
Monday,  July 23, 2007*


Due to Blue Line construction to eliminate slow zones*, Blue Line rail
service will be temporarily suspended in both direction*s between the
Clark/Lake (accessible) and western/Milwaukee stations. Bus shuttles
will operate as a substitute for rail service, making all stops from
Jackson (accessible) to Western/Milwaukee.

CTA Blue Line trains provide frequent service from _O'Hare Airport_ to
downtown in only 45-50 minutes.

The Blue Line operates 24 hours a day, seven days a week.


Safe travel,
  Russ



___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf


Re: Last Call: draft-duerst-archived-at (The Archived-At Message Header Field) to Proposed Standard

2007-07-21 Thread Stephane Bortzmeyer
On Thu, Jul 12, 2007 at 10:03:00AM -0400,
 The IESG <[EMAIL PROTECTED]> wrote 
 a message of 24 lines which said:

> - 'The Archived-At Message Header Field '
> as a Proposed Standard

I've reviewed the document and I find it OK. I also regard the use
cases presented in section 3.3 as realistic and important so I support
the idea of such a standard.

Two remarks, only details:

1) Section 3.2 suggests, to avoid a DoS if the Message-ID is used to
construct the link, to "offer multiple choices in the response". This
does not really mitigate the DoS. An attacker could send 1000 messages
and the only legitimate one would be quite lost among the 1001
responses. It seems a general case of "you should not let the client
control the URI space if this client is unauthenticated".

2) Section 5.2 suggests to register the old experimental header
X-Archived-At. I am not sure it is compliant with RFC 3864 to register
private-use headers. I notice there is currently not one "X-something"
header in the IANA registry. Is this section really necessary?






signature.asc
Description: Digital signature
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf