Re: Finalizing the TM-RID BoF at IETF-106/Singapore

Robert Moskowitz <[email protected]> Thu, 24 Oct 2019 09:57:20 -0400
Newsgroups	gmane.ietf.hipsec,gmane.ietf.hip
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--===============0882151868816358195==
Content-Type: multipart/alternative;
 boundary="------------4F5EFD216BB0C5AF5E2EECA7"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------4F5EFD216BB0C5AF5E2EECA7
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Eric,

I will update the agenda.  Work in Progress with also reving Dex draft.

Michael Richardson is triple booked on this time slot, so maybe Carsten 
or Henk.  Or Daniel Migault.

I will ask around.

I posted a message here on the basics of why HIP (it starts with the 
HIT).  Stu is working on his UAS draft that will have a section on why 
HIP and will be in his slides.  But I will add this to the charter and 
agenda.

Privacy of PII is clearly called out in the FAA requirements and Stu 
will cover that as well.  But it will be clearer in the charter. 
Actually a couple ballots on the ASTM doc noted that the use of Serial # 
or CAA registration probably violates PII requirements and HITs can well 
protect PII and still provide strong ID.

But I need to update the BOF info.

Bob


On 10/24/19 3:31 AM, Eric Vyncke (evyncke) wrote:
>
> Bob and Stu,
>
> Are we all set for this BoF?
>
> For instance, currently there is a single chair Gonzalo Camarillo 
> while it may be useful to have two.
>
> The agenda should also have a point about privacy (even if, as 
> previously discussed, there is no real privacy on purpose) and why IP 
> and HIP rather than another technique.
>
> Beside the discussion on the charter for a potential WG, it would be 
> safer to reserve 10 minutes at the end to probe the participants about 
> the questions of RFC 5434 that are required in order to form a WG.
>
> Unsure whether you can still update the BoF page on your own, else, 
> send me the changes and I will apply them
>
> Regards
>
> -éric
>
>
> _______________________________________________
> Hipsec mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/hipsec


--------------4F5EFD216BB0C5AF5E2EECA7
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Eric,<br>
    <br>
    I will update the agenda.  Work in Progress with also reving Dex
    draft.<br>
    <br>
    Michael Richardson is triple booked on this time slot, so maybe
    Carsten or Henk.  Or Daniel Migault.<br>
    <br>
    I will ask around.<br>
    <br>
    I posted a message here on the basics of why HIP (it starts with the
    HIT).  Stu is working on his UAS draft that will have a section on
    why HIP and will be in his slides.  But I will add this to the
    charter and agenda.<br>
    <br>
    Privacy of PII is clearly called out in the FAA requirements and Stu
    will cover that as well.  But it will be clearer in the charter. 
    Actually a couple ballots on the ASTM doc noted that the use of
    Serial # or CAA registration probably violates PII requirements and
    HITs can well protect PII and still provide strong ID.<br>
    <br>
    But I need to update the BOF info.<br>
    <br>
    Bob<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 10/24/19 3:31 AM, Eric Vyncke
      (evyncke) wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	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:"Calibri",sans-serif;
	color:windowtext;}
..MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style>
      <div class="WordSection1">
        <p class="MsoNormal"><span style="font-size:11.0pt" lang="FR">Bob
            and Stu,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt" lang="FR"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt">Are we all
            set for this BoF?<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt">For
            instance, currently there is a single chair Gonzalo
            Camarillo while it may be useful to have two.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt">The agenda
            should also have a point about privacy (even if, as
            previously discussed, there is no real privacy on purpose)
            and why IP and HIP rather than another technique.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt">Beside the
            discussion on the charter for a potential WG, it would be
            safer to reserve 10 minutes at the end to probe the
            participants about the questions of RFC 5434 that are
            required in order to form a WG.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt">Unsure
            whether you can still update the BoF page on your own, else,
            send me the changes and I will apply them<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt">Regards<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt">-éric<o:p></o:p></span></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Hipsec mailing list
<a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/hipsec">https://www.ietf.org/mailman/listinfo/hipsec</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------4F5EFD216BB0C5AF5E2EECA7--


--===============0882151868816358195==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hipsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/hipsec

--===============0882151868816358195==--