<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Aptos;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:Aptos;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#96607D;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Aptos;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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="#467886" vlink="#96607D">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Hi Keith, all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">It turned out that IETF DTN had to provide candidate dates for their meeting in Dublin earlier than us, so that very likely there will be a collision. The proposal from Rick (see the email
below) is that once the date is fixed for the IETF DTN and TVR meetings (according to the IETF website this should be about October 4<sup>th</sup>) we iterate a little bit with our and their agenda to possibly allow CCSDS interested people to join the IETF
meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><br>
Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"> Rick Taylor <rick@tropicalstormsoftware.com>
<br>
<b>Sent:</b> Dienstag, 24. September 2024 11:01<br>
<b>To:</b> de Cola, Tomaso <Tomaso.deCola@dlr.de>; Edward.Birrane@jhuapl.edu<br>
<b>Cc:</b> ek.ietf@gmail.com<br>
<b>Subject:</b> RE: PLEASE REVIEW - CCSDS Fall 2024 Draft Meeting Schedule & Registration<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">Hi Tomaso,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">I wonder if we can be smart about this, this time: Once we have a clear idea when the IETF DTN session (and perhaps the TVR session as well), could we ensure that
those 2 hour slots are free or an “engage with IETF” session is put in the CCSDS-DTN agenda, allowing CSSDS attendee to dial in?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">I would really like to maximize engagement from the regular CCSDS attendees in the IETF sessions, as I get the feeling that we don’t join up our thinking enough sometimes.
I’m thinking the updated Custody Transfer, LTPv2, and QoS work in particular.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">Rick<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-ligatures:none">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-ligatures:none">
<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a> [<a href="mailto:Tomaso.deCola@dlr.de">mailto:Tomaso.deCola@dlr.de</a>]
<br>
<b>Sent:</b> 24 September 2024 07:57<br>
<b>To:</b> Rick Taylor; <a href="mailto:Edward.Birrane@jhuapl.edu">Edward.Birrane@jhuapl.edu</a><br>
<b>Cc:</b> <a href="mailto:ek.ietf@gmail.com">ek.ietf@gmail.com</a><br>
<b>Subject:</b> RE: PLEASE REVIEW - CCSDS Fall 2024 Draft Meeting Schedule & Registration<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Hi Rick,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">No problem, this year (don’t ask me why) the CCSDS secretariat has been very late and slow in requesting time allocation to all area directors and then coming up with a schedule. In any case
the overlap was also difficult to minimize, so let’s see if we manage to have a good participation to both meetings. I’ll once again remind people here in CCSDS to avoid next time any overlap with IETF.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"> Rick Taylor <<a href="mailto:rick@tropicalstormsoftware.com">rick@tropicalstormsoftware.com</a>>
<br>
<b>Sent:</b> Montag, 23. September 2024 16:12<br>
<b>To:</b> de Cola, Tomaso <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>;
<a href="mailto:Edward.Birrane@jhuapl.edu">Edward.Birrane@jhuapl.edu</a><br>
<b>Cc:</b> <a href="mailto:ek.ietf@gmail.com">ek.ietf@gmail.com</a><br>
<b>Subject:</b> RE: PLEASE REVIEW - CCSDS Fall 2024 Draft Meeting Schedule & Registration<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">Hi Tomaso,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">Thank you for the information. Unfortunately we had to submit our session request already, and the chance to add extra conditions has passed, so we may well clash
sessions.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">Avoiding clashes in the future is definitely something to consider for the CCSDS and IETF meetings as a whole next year.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D">Rick<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-ligatures:none">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-ligatures:none">
<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a> [<a href="mailto:Tomaso.deCola@dlr.de">mailto:Tomaso.deCola@dlr.de</a>]
<br>
<b>Sent:</b> 23 September 2024 12:43<br>
<b>To:</b> Rick Taylor; <a href="mailto:Edward.Birrane@jhuapl.edu">Edward.Birrane@jhuapl.edu</a><br>
<b>Cc:</b> <a href="mailto:ek.ietf@gmail.com">ek.ietf@gmail.com</a><br>
<b>Subject:</b> FW: PLEASE REVIEW - CCSDS Fall 2024 Draft Meeting Schedule & Registration<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Hi Rick, Ed,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">As agreed in previous CCSDS/IETF alignment telcos, I can share with you the schedule for the forthcoming CCSDS meeting. As you can see (second page), DTN is happening Tuesday through Friday.
To avoid any collision with DTN IETF, if possible it would better to have the IETF on Monday. From my point of view also Friday should work since typically Friday is a more relaxed day since it’s the end of the CCSDS week and the big things should have happened
the days before. It not too late we can discuss again at the next telco on October 2<sup>nd</sup>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">The agenda of the meeting is instead not yet defined and this I guess may happen only in the next couple of weeks.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"> CESG-All <<a href="mailto:cesg-all-bounces@mailman.ccsds.org">cesg-all-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Oliver, Brian H via CESG-All<br>
<b>Sent:</b> Mittwoch, 18. September 2024 20:10<br>
<b>To:</b> <a href="mailto:CESG-all@mailman.ccsds.org">CESG-all@mailman.ccsds.org</a><br>
<b>Cc:</b> <a href="mailto:techsupport@mailman.ccsds.org">techsupport@mailman.ccsds.org</a><br>
<b>Subject:</b> [Cesg-all] PLEASE REVIEW - CCSDS Fall 2024 Draft Meeting Schedule & Registration<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear CESG-All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We kindly request that you take the next 24 hours to review the draft meeting schedule and registration system for the Fall 2024 Technical Meetings.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Draft Schedule:</b> (see PDF Attachment)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Draft Meeting Registration:<o:p></o:p></b></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/fm/ProfileSDL/My%20Profile.aspx">https://cwe.ccsds.org/fm/ProfileSDL/My%20Profile.aspx</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please inform us at <a href="mailto:techsupport@mailman.ccsds.org">
techsupport@mailman.ccsds.org</a> if you need to make any changes to the meetings. We can easily accommodate changes. Additionally, we have 17 meetings scheduled for Tuesday, November 5th. If anyone would like to cancel/move a meeting on that day, please inform
us. This will help the hosting provider and Secretariat with room allocation.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Brian<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray;mso-ligatures:none"><br>
The preceding message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for the person or entity to which it is addressed, and may contain information that is confidential, protected
by attorney-client or other privilege, or otherwise protected from disclosure by law. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please
reply to the sender that you have received the message in error and destroy the original message and all copies.</span><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>