<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">So 2023c will reflect DST (GMT+3) beginning on March 30 at 12AM GMT+2? Just trying to be extra clear so that vendors who have already updated to 2023b understand what they will have to do to update to 2023c, and they can hopefully get out
ahead of the Wednesday night / Thursday morning deadline.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any idea when we can expect 2023c to be released? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Jad Baz <jadbaz@gmail.com> <br>
<b>Sent:</b> Monday, March 27, 2023 7:18 AM<br>
<b>To:</b> Rany Hany <rany_hany@riseup.net><br>
<b>Cc:</b> tz@iana.org<br>
<b>Subject:</b> Re: [tz] Lebanon DST change reverted<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Yes, the 48h window was officially decided by the cabinet and should probably be adopted for historical purposes<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Middle East airlines already changed local times back to Winter time so I don't expect that they would change them again for Monday->Wednesday flights only<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Unless they do, this is another reason why historical time should be Winter time for midnight Sunday -> midnight Thursday<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">That being said, while 2023c should be released as soon as possible to stop the bleeding from 2023b and future scheduling conundrums, perhaps it's best to advise vendors to stay on 2023a until at least Thursday morning and then jump to
2023c to avoid further confusion in the interrim period<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">This is especially true as people in Lebanon are still calling DST "International Time" vs Winter "Local Time". I think very few people are aware of the IANA db and that a change was already committed and released<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">In other words, any sudden updates to their device times will completely throw them off<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Mar 27, 2023, 15:11 Rany Hany via tz <<a href="mailto:tz@iana.org" target="_blank">tz@iana.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p>Hello,<o:p></o:p></p>
<p>Yes it should switch to DST (GMT+3) on March 30 at 12AM GMT+2. The government statement seems clear to me after more complete media reports came out.<o:p></o:p></p>
<p>Here is a government media source if it is needed to revert this change: <a href="https://urldefense.com/v3/__https:/www.nna-leb.gov.lb/ar/**I/604360/**K-**G-**K-**E-**M-**K-**E-48-**G__;2LPZitin2LPYqdmF2YrZgtin2KrZitij2LnZhNmG2KfZhNi52YjYr9ip2KXZhNmJ2KfZhNiq2YjZgtmK2KrYp9mE2LXZitmB2YrYqNi52K_Ys9in2LnYqQ!!BJMh1g!7m54QAZirrGnjq2OKelaXiMHD6r0cXVPYHNQ4t_CsxZeontiqhHYC0jAAGiN0umhrkHTTZzS2q2ADspY$" target="_blank">
https://www.nna-leb.gov.lb/ar/%D8%B3%D9%8A%D8%A7%D8%B3%D8%A9/604360/%D9%85%D9%8A%D9%82%D8%A7%D8%AA%D9%8A-%D8%A3%D8%B9%D9%84%D9%86-%D8%A7%D9%84%D8%B9%D9%88%D8%AF%D8%A9-%D8%A5%D9%84%D9%89-%D8%A7%D9%84%D8%AA%D9%88%D9%82%D9%8A%D8%AA-%D8%A7%D9%84%D8%B5%D9%8A%D9%81%D9%8A-%D8%A8%D8%B9%D8%AF-48-%D8%B3%D8%A7%D8%B9%D8%A9</a><o:p></o:p></p>
<div>
<p class="MsoNormal">On 3/27/23 15:03, Andrea Singletary via tz wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal">Will 2023c have Asia/Beirut starting DST this year on March 30?
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">What does this mean for future years? Wish the cabinet would've clarified that while they were on the subject, as Spring Forward intersects with Ramadan for the next few years...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="m_-8000217861628804182m_2761341102680316308ms-outlook-mobile-signature">
<div>
<div>
<p class="MsoNormal"><i>——</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-size:12.0pt">Sent from my pocket-sized infinite improbability generator</span></i><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</body>
</html>