[dnssec-deployment] TIME CHANGE: meeting announcement: 13 April 2005

[James M Galvin]

That's what I get for copy-and-pasting carelessly.  This meeting at 3pm 
Eastern.



--On Monday, April 11, 2005 6:07 PM -0400 James M Galvin 
<galvin at elistx.com> wrote:

> NOTE WELL: The US is now observing daylight savings time but we are
> keeping the meeting at 2pm Eastern.  Thus, the time of this meeting
> will change for many of you.
>
>
> This meeting will be held at the usual time of:
>
>     1200 Los Angeles, San Francisco
>     1300 Phoenix
>     1500 Washington
>     1900 UTC  (** TIME CHANGE **)
>     2100 Netherlands  (** TIME CHANGE **)
>     2200 Israel
>     0400 Tokyo (the next day) (** TIME CHANGE **)
>     0500 Melbourne (the next day) (** TIME CHANGE **)
>
> The usual teleconference logistics are as follows.  These do not
> change. You will hear music until the moderator joins (that would be
> me).
>
>     USA Toll Free Number: +1 888-221-7341
>     USA Toll Number:      +1 973-935-2305
>
>     Passcode: 599786
>     Leader:   James Galvin
> 	      employed by ICANN if speaking to an operator
>
>     Jabber:   dnssec-deployment at conference.jabber.org
> 	      This is a public room.
>
>     If your phone does not have a mute capability you can use "*6" to
>     mute and unmute your connection.
>
>     DIAL OUT:
>         1. ISC SIP Bridge - contact me for SIP identifiers
>
>
> DRAFT AGENDA
>
>
>  -- Meeting during the CENTR meeting
>
>     We may have an opportunity to discuss DNSSEC privacy issues at the
>     CENTR meeting.  Is this something we want to do and can we get
>     organized in time?  Note the CENTR meeting is in Stockholm from
> May     2 to 6.
>
>
>  -- DNS Cache Poisoning
>
>     There is active cache poisoning in progress on the Internet.
> There     are at least two questions for the working group to
> consider:
>
>     * Where and how does DNSSEC help mitigate this problem?
>
>     * Does this change our deployment story, i.e., the urgency and
>       feasibility of deployment?
>
>     Since this issue is getting a fair amount of press coverage now
> is a     good time to be talking about how DNSSEC helps if we can
> accurately     describe its use.  This would also make a nice
> addition to our     collection of DNSSEC use cases.
>
>     The following documentation is required reading in preparation
>     for this discussion:
>
>       http://isc.sans.org/presentations/dnspoisoning.php
>
>
> #############################################################
> This message is sent to you because you are subscribed to
>   the mailing list <dnssec-deployment at shinkuro.com>.
> To unsubscribe, E-mail to: <dnssec-deployment-off at shinkuro.com>
> A public archive is available here:
> <http://mail.shinkuro.com:8100/Lists/dnssec-deployment/>
>