Benzi

I think the week of 30 March works best, I may have to dovetail the trip to ISR for the WG into a conference in Qatar 3-5 April. So if I could depart Tampa on 29 March and arrive 30 March to work 31 Mar- 1 or 2 Apr that would work best. I think this works for CAOC as well.

I don’t think RADM Paparo will be able to travel with his schedule filling up until he leaves CENTCOM. But, he has no problem signing the document once complete virtually.

Let me know what you think. It was great to see Shahar here last week.

S/F

Brad

From: Benzi Zimerman <Benzi_zimerman@mail.gov.il>
Sent: Wednesday, February 19, 2020 1:20 AM
To: Arndt, Michael C Col USAF CENTCOM CCJ3 (USA) <michael.c.arndt2.mil@mail.mil>; Swigart, Caleb J LCDR USN CENTCOM CCJ3 (USA) <caleb.j.swigart.mil@mail.mil>; Cowley, Bradley Scott Col USMC CENTCOM CCJ3 (USA) <bradley.s.cowley.mil@mail.mil>
Subject: [Non-DoD Source] P2 visit and CSOP WG

All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.

Hey all, hope all is well by you in sunny Florida.

Got great feedback from Shahar's visit last week!

I got the understanding that we want to look at the last week of March for the CSOP WG – is that confirmed?

Would be great to pencil down a date for P2's visit in ISR. If we can have him come in on the same week, and present P2 and H2 the CSOP – that would be fantastic!

v/r,

MAJ Benzi Zimmerman 
Head, International Cooperation Desk

IDF Operations Directorate - Plans, Doctrine & Exercises (J3-5/7)

T: +972-3-740-7723 | M: +972-5-42074487 | E: benzi_zimeraman@mail.gov.il < Caution-mailto:benzi_zimeraman@mail.gov.il > 

The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.