December 2012 - mpi-forum - mailman3.cels.anl.gov

Re: [Mpi-forum] Errata handling
by Rolf Rabenseifner 05 Dec '12

05 Dec '12

Additionally, I must say that an MPI-3.0.1 would be directly against the final result of the discussion from last meeting. We said that a standard must have a meaningful stability of at least two years. I do not want to reopen this discussion, but based on exactly this result, our center decided to take the risk to print the MPI-3.0 and to sell it at costs as a service for the whole MPI community. We had to print all books for the next two years and to pay them. Print-on-demand has shown that it does not work with 852 pages in hardcover. An MPI-3.0.1 would completely kill this service combined with a significant loss. Result: Errata should never touch the numbering of our standard. I hope that the whole Forum supports our print service and does not continue with this errata numbering discussion. Best regards Rolf Sorry Tony, but in the past we did errata without incrementing anything, and it worked. Errata change the original document because there is a bug that must be fixed. Only this bug is fixed. Errata never change the title page of a document, and MPI-3.0 from Sep 21, 2012 is part of the title page and this is not a bug, therefore not changed by errata. If an implementor did not detect an inconsistency and implemented something that is wrong, then it is a bug in his software and it needs to be fixed, latest when the errata is voted in, better when the inconsistency is reolved by the chapter committee and published in a ticket. The software is always MPI-3.0 compliant, but with some bugs. Please keep it simple! Best regards Rolf ----- Original Message ----- > From: "Anthony Skjellum" <tony(a)cis.uab.edu> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Sent: Wednesday, December 5, 2012 6:42:07 PM > Subject: Re: [Mpi-forum] Errata handling > We need to increment the third digit of the standard each time errata > are accepted in this way. > "3.0 + errata compliant" is too vague. > > > ----- Original Message ----- > From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Sent: Wednesday, December 5, 2012 11:23:56 AM > Subject: [Mpi-forum] Errata handling > > Dear all, > > I detected that there seems to be a discussion. > >From my viewpoint based on experience since MPI-2.0, > the processing should be very simple and clear: > > - only important errata are published, not the typos. > - important is that the interface was definitely inconsistent > or obviously wrong. > - enough review by committee members, i.e., it is clear that > the correction is correct. > - real reading in the forum, because it is about the interface. > - single reading + vote for corrections of inconsistencies. > > Errata should pass always in the next meeting after they > were detected. > > Errata are voted and "3.0 compiant" always means 3.0+errata compliant. > Errata are for obvious bugs and inconsistencies. > > Reason: > - Being compliant to a bug is stupied and must be corrected > as soon as detected. > (Example: It was never intented that you are MPI-2.2 compliant > when having BOOL with 4 bytes in the external32 datarep.) > - Being compliant to an inconsistency is impossible, > because MPI-3.0 says A and not-A; > you can never be compliant to both A and not-A. > > There should be only ONE errata document, which is > updated after each meeting if new errata are added. > The errata should be sorted by page and linenumbers in MPI-3.0. > > By this, there are older versions (visible at the date) > of the errata document, but only the newest is binding. > > If we want to have the history in, we can add for each > erratum the following parantheses: > > "(detected in ticket #nnn on May 1, 2099, voted in on Jun 16, 2099)". > > Because we always should try to circulate errata in a ticket, > all implementors have early access to the information. > It should be voted in in the same meeting as it was read. > That's enough. This should need 30-60 minutes in a forum meeting. > That's fast compared to a lot of emailing or email-voting. > > That's the way we did it in the past for all corrections > in the voted Fortran interface - and it worked. > > My strong recommendation: > - Do it simple and effective! > - And start it now! > - Use the meeting time for content of the MPI standard > and not for complicating the errata process. > > Best regards > Rolf > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Room 1.307) > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Room 1.307) _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

1 0

Re: [Mpi-forum] Errata handling
by Rolf Rabenseifner 05 Dec '12

05 Dec '12

Sorry Tony, but in the past we did errata without incrementing anything, and it worked. Errata change the original document because there is a bug that must be fixed. Only this bug is fixed. Errata never change the title page of a document, and MPI-3.0 from Sep 21, 2012 is part of the title page and this is not a bug, therefore not changed by errata. If an implementor did not detect an inconsistency and implemented something that is wrong, then it is a bug in his software and it needs to be fixed, latest when the errata is voted in, better when the inconsistency is reolved by the chapter committee and published in a ticket. The software is always MPI-3.0 compliant, but with some bugs. Please keep it simple! Best regards Rolf ----- Original Message ----- > From: "Anthony Skjellum" <tony(a)cis.uab.edu> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Sent: Wednesday, December 5, 2012 6:42:07 PM > Subject: Re: [Mpi-forum] Errata handling > We need to increment the third digit of the standard each time errata > are accepted in this way. > "3.0 + errata compliant" is too vague. > > > ----- Original Message ----- > From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Sent: Wednesday, December 5, 2012 11:23:56 AM > Subject: [Mpi-forum] Errata handling > > Dear all, > > I detected that there seems to be a discussion. > >From my viewpoint based on experience since MPI-2.0, > the processing should be very simple and clear: > > - only important errata are published, not the typos. > - important is that the interface was definitely inconsistent > or obviously wrong. > - enough review by committee members, i.e., it is clear that > the correction is correct. > - real reading in the forum, because it is about the interface. > - single reading + vote for corrections of inconsistencies. > > Errata should pass always in the next meeting after they > were detected. > > Errata are voted and "3.0 compiant" always means 3.0+errata compliant. > Errata are for obvious bugs and inconsistencies. > > Reason: > - Being compliant to a bug is stupied and must be corrected > as soon as detected. > (Example: It was never intented that you are MPI-2.2 compliant > when having BOOL with 4 bytes in the external32 datarep.) > - Being compliant to an inconsistency is impossible, > because MPI-3.0 says A and not-A; > you can never be compliant to both A and not-A. > > There should be only ONE errata document, which is > updated after each meeting if new errata are added. > The errata should be sorted by page and linenumbers in MPI-3.0. > > By this, there are older versions (visible at the date) > of the errata document, but only the newest is binding. > > If we want to have the history in, we can add for each > erratum the following parantheses: > > "(detected in ticket #nnn on May 1, 2099, voted in on Jun 16, 2099)". > > Because we always should try to circulate errata in a ticket, > all implementors have early access to the information. > It should be voted in in the same meeting as it was read. > That's enough. This should need 30-60 minutes in a forum meeting. > That's fast compared to a lot of emailing or email-voting. > > That's the way we did it in the past for all corrections > in the voted Fortran interface - and it worked. > > My strong recommendation: > - Do it simple and effective! > - And start it now! > - Use the meeting time for content of the MPI standard > and not for complicating the errata process. > > Best regards > Rolf > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Room 1.307) > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Room 1.307)

1 0

Re: [Mpi-forum] Errata handling
by Anthony Skjellum 05 Dec '12

05 Dec '12

We need to increment the third digit of the standard each time errata are accepted in this way. "3.0 + errata compliant" is too vague. ----- Original Message ----- From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> Sent: Wednesday, December 5, 2012 11:23:56 AM Subject: [Mpi-forum] Errata handling Dear all, I detected that there seems to be a discussion. >From my viewpoint based on experience since MPI-2.0, the processing should be very simple and clear: - only important errata are published, not the typos. - important is that the interface was definitely inconsistent or obviously wrong. - enough review by committee members, i.e., it is clear that the correction is correct. - real reading in the forum, because it is about the interface. - single reading + vote for corrections of inconsistencies. Errata should pass always in the next meeting after they were detected. Errata are voted and "3.0 compiant" always means 3.0+errata compliant. Errata are for obvious bugs and inconsistencies. Reason: - Being compliant to a bug is stupied and must be corrected as soon as detected. (Example: It was never intented that you are MPI-2.2 compliant when having BOOL with 4 bytes in the external32 datarep.) - Being compliant to an inconsistency is impossible, because MPI-3.0 says A and not-A; you can never be compliant to both A and not-A. There should be only ONE errata document, which is updated after each meeting if new errata are added. The errata should be sorted by page and linenumbers in MPI-3.0. By this, there are older versions (visible at the date) of the errata document, but only the newest is binding. If we want to have the history in, we can add for each erratum the following parantheses: "(detected in ticket #nnn on May 1, 2099, voted in on Jun 16, 2099)". Because we always should try to circulate errata in a ticket, all implementors have early access to the information. It should be voted in in the same meeting as it was read. That's enough. This should need 30-60 minutes in a forum meeting. That's fast compared to a lot of emailing or email-voting. That's the way we did it in the past for all corrections in the voted Fortran interface - and it worked. My strong recommendation: - Do it simple and effective! - And start it now! - Use the meeting time for content of the MPI standard and not for complicating the errata process. Best regards Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Room 1.307) _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

1 0

Errata handling
by Rolf Rabenseifner 05 Dec '12

05 Dec '12

Dear all, I detected that there seems to be a discussion. >From my viewpoint based on experience since MPI-2.0, the processing should be very simple and clear: - only important errata are published, not the typos. - important is that the interface was definitely inconsistent or obviously wrong. - enough review by committee members, i.e., it is clear that the correction is correct. - real reading in the forum, because it is about the interface. - single reading + vote for corrections of inconsistencies. Errata should pass always in the next meeting after they were detected. Errata are voted and "3.0 compiant" always means 3.0+errata compliant. Errata are for obvious bugs and inconsistencies. Reason: - Being compliant to a bug is stupied and must be corrected as soon as detected. (Example: It was never intented that you are MPI-2.2 compliant when having BOOL with 4 bytes in the external32 datarep.) - Being compliant to an inconsistency is impossible, because MPI-3.0 says A and not-A; you can never be compliant to both A and not-A. There should be only ONE errata document, which is updated after each meeting if new errata are added. The errata should be sorted by page and linenumbers in MPI-3.0. By this, there are older versions (visible at the date) of the errata document, but only the newest is binding. If we want to have the history in, we can add for each erratum the following parantheses: "(detected in ticket #nnn on May 1, 2099, voted in on Jun 16, 2099)". Because we always should try to circulate errata in a ticket, all implementors have early access to the information. It should be voted in in the same meeting as it was read. That's enough. This should need 30-60 minutes in a forum meeting. That's fast compared to a lot of emailing or email-voting. That's the way we did it in the past for all corrections in the voted Fortran interface - and it worked. My strong recommendation: - Do it simple and effective! - And start it now! - Use the meeting time for content of the MPI standard and not for complicating the errata process. Best regards Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Room 1.307)

1 0

Re: [Mpi-forum] Here's the document we're discussing right now
by Supalov, Alexander 05 Dec '12

05 Dec '12

Cool, thank you. I hope feedback may keep coming, too. This is not a promise, though. -----Original Message----- From: mpi-forum-bounces(a)lists.mpi-forum.org [mailto:[email protected]] On Behalf Of Jeff Squyres Sent: Wednesday, December 05, 2012 2:16 PM To: Main MPI Forum mailing list Subject: Re: [Mpi-forum] Here's the document we're discussing right now Yes, but there was a LOT of discussion about this document in the room, and Brian and I took a lot of good feedback about it (thanks for recording the feedback, Martin!). We'll be coming back to the Forum with an updated proposal next meeting. On Dec 5, 2012, at 12:00 AM, Supalov, Alexander wrote: > ... and outside of the room, too, I hope. J > > From: mpi-forum-bounces(a)lists.mpi-forum.org > [mailto:[email protected]] On Behalf Of Jeff > Squyres > Sent: Tuesday, December 04, 2012 11:23 PM > To: MPI Forum list > Subject: [Mpi-forum] Here's the document we're discussing right now > > For everyone in the room.... > > -- > Jeff Squyres > jsquyres(a)cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: > Feldkirchen bei Muenchen > Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas > Lusk > Registergericht: Muenchen HRB 47456 > Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. > (BLZ 502 109 00) 600119052 > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052

1 0

Re: [Mpi-forum] Here's the document we're discussing right now
by Jeff Squyres 05 Dec '12

05 Dec '12

Yes, but there was a LOT of discussion about this document in the room, and Brian and I took a lot of good feedback about it (thanks for recording the feedback, Martin!). We'll be coming back to the Forum with an updated proposal next meeting. On Dec 5, 2012, at 12:00 AM, Supalov, Alexander wrote: > ï¿½ and outside of the room, too, I hope. J > > From: mpi-forum-bounces(a)lists.mpi-forum.org [mailto:[email protected]] On Behalf Of Jeff Squyres > Sent: Tuesday, December 04, 2012 11:23 PM > To: MPI Forum list > Subject: [Mpi-forum] Here's the document we're discussing right now > > For everyone in the room.... > > -- > Jeff Squyres > jsquyres(a)cisco.com > For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen, Deutschland > Sitz der Gesellschaft: Feldkirchen bei Muenchen > Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk > Registergericht: Muenchen HRB 47456 > Ust.-IdNr./VAT Registration No.: DE129385895 > Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052 > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Re: [Mpi-forum] Here's the document we're discussing right now
by Supalov, Alexander 05 Dec '12

05 Dec '12

... and outside of the room, too, I hope. :) From: mpi-forum-bounces(a)lists.mpi-forum.org [mailto:[email protected]] On Behalf Of Jeff Squyres Sent: Tuesday, December 04, 2012 11:23 PM To: MPI Forum list Subject: [Mpi-forum] Here's the document we're discussing right now For everyone in the room.... -- Jeff Squyres jsquyres(a)cisco.com<mailto:[email protected]> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052

1 0

Here's the document we're discussing right now
by Jeff Squyres 04 Dec '12

04 Dec '12

For everyone in the room.... -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Re: [Mpi-forum] Callin numbers for Forum meetings
by Jeff Squyres 04 Dec '12

04 Dec '12

Webex links for both webex sessions are now up on the agenda page: http://meetings.mpi-forum.org/secretary/2012/12/agenda.php Today, Tue, Dec 4, 2012, 9am Pacific: general FT meeting Tomorrow, Wed, Dec 5, 2012, 9am Pacific: FT/RMA meeting The webex password is "mpi" for both meetings. On Dec 3, 2012, at 6:50 AM, Richard Graham wrote: > I will put them on the agenda, as soon as I get them. > > Rich > > From: Stephen Sachs [mailto:[email protected]] > Sent: Monday, December 03, 2012 05:00 AM > To: Main MPI Forum mailing list <mpi-forum(a)lists.mpi-forum.org> > Subject: Re: [Mpi-forum] Callin numbers for Forum meetings > > Dear Rich, > > I would like to call into those two sessions. Where can I find the phone details? > > Thanks, > Stephen. > > From: mpi-forum-bounces(a)lists.mpi-forum.org [mailto:[email protected]] On Behalf Of Richard Graham > Sent: Wednesday, November 28, 2012 6:36 PM > To: mpi-forum(a)lists.mpi-forum.org > Subject: [Mpi-forum] Callin numbers for Forum meetings > > I have been requested to provide call in capabilities to two session at the upcoming meeting ï¿½ the Tuesday AM FT discussion, and the Wed am FT/RMA discussion (note the time change to accommodate folks from Europe). Are there other sessions that people would want to call into ? If so, please let Jeff and me know, so that Jeff can make the appropriate arrangements. > > Thanks, > Rich > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Webex info for FT meeting this morning
by Jeff Squyres 04 Dec '12

04 Dec '12

See below. The webex link is also on the meeting agenda page. Starting at 9am Pacific. Begin forwarded message: > From: Jeff Squyres <messenger(a)webex.com> > Subject: (Forward to attendees) Meeting invitation: MPI Forum: FT > Date: December 4, 2012 5:29:58 AM PST > To: <jsquyres(a)cisco.com> > Reply-To: <jsquyres(a)cisco.com> > > **** You can forward this email invitation to attendees **** > > Hello , > > Jeff Squyres invites you to attend this online meeting. > > Topic: MPI Forum: FT > Date: Tuesday, December 4, 2012 > Time: 9:00 am, Pacific Standard Time (San Francisco, GMT-08:00) > Meeting Number: 204 116 262 > Meeting Password: mpi > > > ------------------------------------------------------- > To join the online meeting (Now from mobile devices!) > ------------------------------------------------------- > 1. Go to https://cisco.webex.com/ciscosales/j.php?ED=211784057&UID=0&PW=NN2NkZWJhZTA… > 2. Enter your name and email address. > 3. Enter the meeting password: mpi > 4. Click "Join Now". > > To view in other time zones or languages, please click the link: > https://cisco.webex.com/ciscosales/j.php?ED=211784057&UID=0&PW=NN2NkZWJhZTA… > > ---------------------------------------------------------------- > ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes > ---------------------------------------------------------------- > > The affected toll free numbers are: (866) 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the RTP area. > > Please dial the local access number for your area from the list below: > - San Jose/Milpitas (408) area: 525-6800 > - RTP (919) area: 392-3330 > > ------------------------------------------------------- > To join the teleconference only > ------------------------------------------------------- > 1. Dial into Cisco WebEx (view all Global Access Numbers at > http://cisco.com/en/US/about/doing_business/conferencing/index.html > 2. Follow the prompts to enter the Meeting Number (listed above) or Access Code followed by the # sign. > > San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 > > US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 > > India: +91.80.4350.1111 Germany: +49.619.6773.9002 > > Japan: +81.3.5763.9394 China: +86.10.8515.5666 > > ------------------------------------------------------- > For assistance > ------------------------------------------------------- > 1. Go to https://cisco.webex.com/ciscosales/mc > 2. On the left navigation bar, click "Support". > > You can contact me at: > jsquyres(a)cisco.com > 1-408-525 0971 > > To add this meeting to your calendar program (for example Microsoft Outlook), click this link: > https://cisco.webex.com/ciscosales/j.php?ED=211784057&UID=0&ICS=MI&LD=1&RD=… > > The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://cisco.webex.com/ciscosales/systemdiagnosis.php. > > > > > http://www.webex.com > > CCP:+14085256800x204116262# > > IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0