[Certsanddns] Introductory remarks

[James M Galvin]

You don't call this out but then perhaps it is obvious.

You're obviously going to introduce each of the speakers in turn. 
After that, I think you should re-introduce Phil and myself and our 
roles for the open discussion.

I suggest that order because then you can hand off to me and I'll say a 
few words about how I'm going to manage the queue so we can keep things 
moving.

Logistically, I'm assuming Phil and I will be in the front of the room. 
If there's a podium Phil can stand there and I'll sit nearby.  If 
there's no separate table I'll just take a seat at the corner of the 
"U" closest to the podium.

Thanks,

Jim




-- On January 20, 2011 10:20:00 AM -0500 Tim Moses 
<tim.moses at entrust.com> wrote regarding [Certsanddns] Introductory 
remarks --

>
>
> FYI.  This is what I’ll cover in the introductory remarks.  Let me
> know if I forgot anything.  Thanks a lot.  All the best.  Tim.
>
>
>
> Introduction and logistics
>
> Introduce our host, Andy.  Introduce our dinner host, Ryan.  How to
> access the wi-fi.  Arrangements for getting in and out of the
> building.  Where the washrooms are.
>
> Topic: “Trust in DNSSEC” – Focus on governance framework for
> DNS itself and for applications that rely on DNS, not on technical
> mechanisms
>
> Outline for the afternoon – Short background presentation, then two
> short presentations to establish common terminology and frame the
> problem, followed by open discussion and conclusions/next steps.
> There will be a short break mid-afternoon.   Close at 17:00.
>
> Write your name on the card and state your name and affiliation the
> first time you talk
>
> Check your name and email address on the list being circulated
>
> Turn your name card “on end” when you have something you want to
> say
>
> Audio recording for the purposes of compiling a record of the meeting
>
> People may join by phone, so speak clearly and sufficiently loudly
>
> Meeting notes will be sent to you once they have been prepared
>
>
>
>
>
> Tom Albertson
>
> tomalb at microsoft.com
>
>
>
> Robin Alden
>
> robin at comodo.com
>
>
>
> Takuji Akiyama
>
> akiyama at CrossTrust.co.jp
>
>
>
> Anand, Reema
>
> reemaanand at kpmg.com
>
>
>
> Inigo Barreira
>
> i-barreira at izenpe.net
>
>
>
> Matthew Campagna
>
> mcampagna at certicom.com
>
>
>
> Stephen Davidson
>
> S.Davidson at quovadisglobal.com
>
>
>
> James M Galvin
>
> jgalvin at afilias.info
>
>
>
> Joseph Gersch
>
> joe.gersch at secure64.com
>
>
>
> Phillip Hallem-Baker
>
> philliph at comodo.com
>
>
>
> Wes Hardaker
>
> Wes.Hardaker at cobham.com
>
>
>
> Hiraiwa Yoshimasa
>
> hiraiwa at verisign.co.jp
>
>
>
> Paul Hoffman
>
> paul.hoffman at vpnc.org
>
>
>
> Atsushi Inaba
>
> atsushi.inaba at globalsign.co.jp
>
>
>
> Dan Kaminsky
>
> dan at doxpara.com
>
>
>
> Chris Klein
>
> cklein at verisign.com
>
>
>
> Ryan Koski
>
> rkoski at godaddy.com
>
>
>
> Adam Langley
>
> agl at google.com
>
>
>
> John McFadden
>
> John.McFadden at markmonitor.com
>
>
>
> Richard Merdinger
>
> rmerdinger at godaddy.com
>
>
>
> Bruce Morton
>
> bruce.morton at entrust.com
>
>
>
> Tim Moses
>
> tim.moses at entrust.com
>
>
>
> Eric Osterweil
>
> eosterweil at verisign.com
>
>
>
> Doug Pelton
>
> peltond at wellsfargo.com
>
>
>
> Nicholas Percoco
>
> npercoco at trustwave.com
>
>
>
> Yngve N. Pettersen
>
> yngve at opera.com
>
>
>
> Scott Rose
>
> scott.rose at nist.gov
>
>
>
> Jay Schiavo
>
> jschiavo at verisign.com
>
>
>
> Jakob Schlyter
>
> jakob at kirei.se
>
>
>
> Brian Smith
>
> bsmith at mozilla.com
>
>
>
> Andy Steingruebl
>
> asteingruebl at paypal-inc.com
>
>
>
> Johan Sys
>
> johan.sys at globalsign.com
>
>
>
> Paul Tiemann
>
> paul at digicert.com
>
>
>
> Alexander Truskovsky
>
> atruskovsky at rim.com
>
>
>
> Sandy Wilbourn
>
> Sandy.Wilbourn at nominum.com
>
>
>
> Richard Wilhelm
>
> Richard.Wilhelm at networksolutions.com
>
>
>
> Ben Wilson
>
> ben at digicert.com
>
>
>
> Yoshiro YONEYA
>
> yoshiro.yoneya at jprs.co.jp
>
>
>
>
>
>
>
>
>
>
>
> Tim Moses
>
> +1 613 270 3183
>
>