Re: Fwd: New Version Notification for draft-moskowitz-hip-hierarchical-hit-00.txt
Robert Moskowitz <[email protected]> Thu, 12 Sep 2019 14:31:53 -0400
| Newsgroups | gmane.ietf.hipsec,gmane.ietf.hip |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============6351324505775395698== Content-Type: multipart/alternative; boundary="------------C03A606804748F5770DF7070" Content-Language: en-US This is a multi-part message in MIME format. --------------C03A606804748F5770DF7070 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Some points about Hierarchical HITs. The idea is not new. See draft-moskowitz-hip-04 from 7/01. One bit was used to identity Hierarchical HITs (HHITs) over flat HITs. Since this concept was removed I am now faced with how to tell the difference in the HIT encoding? HHITs use a different ORCHID construction. Kind of violation the ORCHID rules. Remains to be seen if it will take a direct addendum to ORCHID for this. The HID is included with the HI in computing the ORCHID. I often wondered if the HIT Suite should have been included. Since it wasn't we do have to be careful in specifying HIT Suites so it is not possible to have identical BIT-level HIs for different HIT Suites. I am not attempting to change this part; maybe I should. So given a HIT in the wild (I1, or UAS RID broadcast), how do you know if it is a HHIT. Instead of burning through HIT suites as I first thought in draft-moskowitz-hierarchical-hip, I am specifying a unique HIT prefix for HHITs. If anyone can see any other way, please speak up. Again, the ORCHID prefix is specified in the ORCHID RFC. Will we best do an update to ORCHID? Please chime in. Bob On 9/12/19 12:54 PM, Robert Moskowitz wrote: > Hello all. > > Finally we are now funded to work on this project. I am very unhappy > at what it took to get to this point. Fortunately, I have been using > the time to put together some notes that I am quickly turning into drafts. > > So work on tm-rid is now open. Two more drafts will be posted in the > next couple days. I welcome reviews and comments. > > Also I will be working with the AD for time at IETF106. > > Bob > > > -------- Forwarded Message -------- > Subject: New Version Notification for > draft-moskowitz-hip-hierarchical-hit-00.txt > Date: Thu, 12 Sep 2019 09:49:01 -0700 > From: [email protected] > To: Stuart Card <[email protected]>, Adam Wiethuechter > <[email protected]>, Robert Moskowitz > <[email protected]>, Stuart W. Card <[email protected]> > > > > > A new version of I-D, draft-moskowitz-hip-hierarchical-hit-00.txt > has been successfully submitted by Robert Moskowitz and posted to the > IETF repository. > > Name: draft-moskowitz-hip-hierarchical-hit > Revision: 00 > Title: Hierarchical HITs for HIPv2 > Document date: 2019-09-12 > Group: Individual Submission > Pages: 9 > URL: > https://www.ietf.org/internet-drafts/draft-moskowitz-hip-hierarchical-hit-00.txt > Status: > https://datatracker.ietf.org/doc/draft-moskowitz-hip-hierarchical-hit/ > Htmlized: > https://tools.ietf.org/html/draft-moskowitz-hip-hierarchical-hit-00 > Htmlized: > https://datatracker.ietf.org/doc/html/draft-moskowitz-hip-hierarchical-hit > > > Abstract: > This document describes using a hierarchical HIT to facilitate large > deployments of managed devices. Hierarchical HITs differ from HIPv2 > flat HITs by only using 64 bits for mapping the Host Identity, > freeing 32 bits to bind in a hierarchy of Registering Entities that > provide services to the consumers of hierarchical HITs. > > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > > _______________________________________________ > Hipsec mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/hipsec --------------C03A606804748F5770DF7070 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 text="#000000" bgcolor="#FFFFFF"> Some points about Hierarchical HITs.<br> <br> The idea is not new. See draft-moskowitz-hip-04 from 7/01. One bit was used to identity Hierarchical HITs (HHITs) over flat HITs.<br> <br> Since this concept was removed I am now faced with how to tell the difference in the HIT encoding?<br> <br> HHITs use a different ORCHID construction. Kind of violation the ORCHID rules. Remains to be seen if it will take a direct addendum to ORCHID for this. The HID is included with the HI in computing the ORCHID. I often wondered if the HIT Suite should have been included. Since it wasn't we do have to be careful in specifying HIT Suites so it is not possible to have identical BIT-level HIs for different HIT Suites. I am not attempting to change this part; maybe I should.<br> <br> So given a HIT in the wild (I1, or UAS RID broadcast), how do you know if it is a HHIT. Instead of burning through HIT suites as I first thought in draft-moskowitz-hierarchical-hip, I am specifying a unique HIT prefix for HHITs.<br> <br> If anyone can see any other way, please speak up. Again, the ORCHID prefix is specified in the ORCHID RFC. Will we best do an update to ORCHID?<br> <br> Please chime in.<br> <br> Bob<br> <br> <div class="moz-cite-prefix">On 9/12/19 12:54 PM, Robert Moskowitz wrote:<br> </div> <blockquote type="cite" cite="mid:[email protected]"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> Hello all.<br> <br> Finally we are now funded to work on this project. I am very unhappy at what it took to get to this point. Fortunately, I have been using the time to put together some notes that I am quickly turning into drafts.<br> <br> So work on tm-rid is now open. Two more drafts will be posted in the next couple days. I welcome reviews and comments.<br> <br> Also I will be working with the AD for time at IETF106.<br> <br> Bob<br> <div class="moz-forward-container"><br> <br> -------- Forwarded Message -------- <table class="moz-email-headers-table" cellspacing="0" cellpadding="0" border="0"> <tbody> <tr> <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject: </th> <td>New Version Notification for draft-moskowitz-hip-hierarchical-hit-00.txt</td> </tr> <tr> <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th> <td>Thu, 12 Sep 2019 09:49:01 -0700</td> </tr> <tr> <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th> <td><a class="moz-txt-link-abbreviated" href="mailto:[email protected]" moz-do-not-send="true">[email protected]</a></td> </tr> <tr> <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th> <td>Stuart Card <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]" moz-do-not-send="true"><[email protected]></a>, Adam Wiethuechter <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]" moz-do-not-send="true"><[email protected]></a>, Robert Moskowitz <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]" moz-do-not-send="true"><[email protected]></a>, Stuart W. Card <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]" moz-do-not-send="true"><[email protected]></a></td> </tr> </tbody> </table> <br> <br> <br> A new version of I-D, draft-moskowitz-hip-hierarchical-hit-00.txt<br> has been successfully submitted by Robert Moskowitz and posted to the<br> IETF repository.<br> <br> Name: draft-moskowitz-hip-hierarchical-hit<br> Revision: 00<br> Title: Hierarchical HITs for HIPv2<br> Document date: 2019-09-12<br> Group: Individual Submission<br> Pages: 9<br> URL: <a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-moskowitz-hip-hierarchical-hit-00.txt" moz-do-not-send="true">https://www.ietf.org/internet-drafts/draft-moskowitz-hip-hierarchical-hit-00.txt</a><br> Status: <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-moskowitz-hip-hierarchical-hit/" moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-moskowitz-hip-hierarchical-hit/</a><br> Htmlized: <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-moskowitz-hip-hierarchical-hit-00" moz-do-not-send="true">https://tools.ietf.org/html/draft-moskowitz-hip-hierarchical-hit-00</a><br> Htmlized: <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-moskowitz-hip-hierarchical-hit" moz-do-not-send="true">https://datatracker.ietf.org/doc/html/draft-moskowitz-hip-hierarchical-hit</a><br> <br> <br> Abstract:<br> This document describes using a hierarchical HIT to facilitate large<br> deployments of managed devices. Hierarchical HITs differ from HIPv2<br> flat HITs by only using 64 bits for mapping the Host Identity,<br> freeing 32 bits to bind in a hierarchy of Registering Entities that<br> provide services to the consumers of hierarchical HITs.<br> <br> <br> <br> Please note that it may take a couple of minutes from the time of submission<br> until the htmlized version and diff are available at tools.ietf.org.<br> <br> The IETF Secretariat<br> <br> </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> --------------C03A606804748F5770DF7070-- --===============6351324505775395698== 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 --===============6351324505775395698==--