From nobody Mon May 4 14:44:25 2020 Return-Path: X-Original-To: hipsec@ietf.org Delivered-To: hipsec@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB223A0AEE; Mon, 4 May 2020 14:44:19 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: hipsec@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.129.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: hipsec@ietf.org Message-ID: <158862865950.20946.13946913206555887142@ietfa.amsl.com> Date: Mon, 04 May 2020 14:44:19 -0700 Archived-At: Subject: [Hipsec] I-D Action: draft-ietf-hip-dex-19.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.29 List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2020 21:44:20 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol WG of the IETF. Title : HIP Diet EXchange (DEX) Authors : Robert Moskowitz Rene Hummen Miika Komu Filename : draft-ietf-hip-dex-19.txt Pages : 58 Date : 2020-05-04 Abstract: This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. The HIP DEX protocol is primarily designed for computation or memory- constrained sensor/actuator devices. Like HIPv2, it is expected to be used together with a suitable security protocol such as the Encapsulated Security Payload (ESP) for the protection of upper layer protocol data. Unlike HIPv2, HIP DEX does not support Forward Secrecy (FS), and MUST only be used on devices where FS is prohibitively expensive. In addition, HIP DEX can also be used as a keying mechanism for security primitives at the MAC layer, e.g., for IEEE 802.15.4 networks. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-hip-dex/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-hip-dex-19 https://datatracker.ietf.org/doc/html/draft-ietf-hip-dex-19 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-dex-19 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon May 4 14:50:59 2020 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55C2B3A0A73; Mon, 4 May 2020 14:50:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sMlkATlc1Qva; Mon, 4 May 2020 14:50:56 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B86D3A10CE; Mon, 4 May 2020 14:50:54 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 22CA462145; Mon, 4 May 2020 17:50:52 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xTtghi9AkTbO; Mon, 4 May 2020 17:50:43 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 294C46214B; Mon, 4 May 2020 17:50:42 -0400 (EDT) To: hipsec@ietf.org, internet-drafts@ietf.org, i-d-announce@ietf.org References: <158862865950.20946.13946913206555887142@ietfa.amsl.com> From: Robert Moskowitz Message-ID: <048cc95d-b459-ee95-9ea6-dc2a88638777@htt-consult.com> Date: Mon, 4 May 2020 17:50:42 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <158862865950.20946.13946913206555887142@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [Hipsec] I-D Action: draft-ietf-hip-dex-19.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2020 21:50:58 -0000 This is the output of my 1st 'cherry picking' pass through Ben's comments.  Anyone willing to look at the changes (use the diff tool) and give me comments, I greatly welcome. I will attempt to capture the rest of Ben's comments in the next rev. Bob On 5/4/20 5:44 PM, internet-drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Host Identity Protocol WG of the IETF. > > Title : HIP Diet EXchange (DEX) > Authors : Robert Moskowitz > Rene Hummen > Miika Komu > Filename : draft-ietf-hip-dex-19.txt > Pages : 58 > Date : 2020-05-04 > > Abstract: > This document specifies the Host Identity Protocol Diet EXchange (HIP > DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The > HIP DEX protocol design aims at reducing the overhead of the employed > cryptographic primitives by omitting public-key signatures and hash > functions. > > The HIP DEX protocol is primarily designed for computation or memory- > constrained sensor/actuator devices. Like HIPv2, it is expected to > be used together with a suitable security protocol such as the > Encapsulated Security Payload (ESP) for the protection of upper layer > protocol data. Unlike HIPv2, HIP DEX does not support Forward > Secrecy (FS), and MUST only be used on devices where FS is > prohibitively expensive. In addition, HIP DEX can also be used as a > keying mechanism for security primitives at the MAC layer, e.g., for > IEEE 802.15.4 networks. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-hip-dex/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-hip-dex-19 > https://datatracker.ietf.org/doc/html/draft-ietf-hip-dex-19 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-dex-19 > > > 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. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > > _______________________________________________ > Hipsec mailing list > Hipsec@ietf.org > https://www.ietf.org/mailman/listinfo/hipsec From nobody Wed May 13 08:24:10 2020 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7A6C3A0DB4 for ; Wed, 13 May 2020 08:24:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UB3y1yHhbnly for ; Wed, 13 May 2020 08:24:05 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEF4F3A0E03 for ; Wed, 13 May 2020 08:24:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 37906621B2 for ; Wed, 13 May 2020 11:24:04 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kkcas+OHHWsj for ; Wed, 13 May 2020 11:23:57 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 1F74362162 for ; Wed, 13 May 2020 11:23:57 -0400 (EDT) To: HIP From: Robert Moskowitz Message-ID: <85919573-2ef3-63b9-e888-7af112a3d5e0@htt-consult.com> Date: Wed, 13 May 2020 11:23:50 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------35032C94B1FA7DA218B4B279" Content-Language: en-US Archived-At: Subject: [Hipsec] Fwd: New Version Notification for draft-moskowitz-hip-hierarchical-hit-05.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2020 15:24:09 -0000 This is a multi-part message in MIME format. --------------35032C94B1FA7DA218B4B279 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Some text clean up and references to historical HHIT proposals. Big item is changing hierarchy for 14/18 to 16/16 per earlier discussion. We still need discussions on DNS formats. -------- Forwarded Message -------- Subject: New Version Notification for draft-moskowitz-hip-hierarchical-hit-05.txt Date: Wed, 13 May 2020 08:20:20 -0700 From: internet-drafts@ietf.org To: Robert Moskowitz , Stuart Card , Adam Wiethuechter , Stuart W. Card A new version of I-D, draft-moskowitz-hip-hierarchical-hit-05.txt has been successfully submitted by Robert Moskowitz and posted to the IETF repository. Name: draft-moskowitz-hip-hierarchical-hit Revision: 05 Title: Hierarchical HITs for HIPv2 Document date: 2020-05-12 Group: Individual Submission Pages: 11 URL: https://www.ietf.org/internet-drafts/draft-moskowitz-hip-hierarchical-hit-05.txt Status: https://datatracker.ietf.org/doc/draft-moskowitz-hip-hierarchical-hit/ Htmlized: https://tools.ietf.org/html/draft-moskowitz-hip-hierarchical-hit-05 Htmlized: https://datatracker.ietf.org/doc/html/draft-moskowitz-hip-hierarchical-hit Diff: https://www.ietf.org/rfcdiff?url2=draft-moskowitz-hip-hierarchical-hit-05 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 --------------35032C94B1FA7DA218B4B279 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
Some text clean up and references to historical HHIT proposals.

Big item is changing hierarchy for 14/18 to 16/16 per earlier discussion.

We still need discussions on DNS formats.



-------- Forwarded Message --------
Subject: New Version Notification for draft-moskowitz-hip-hierarchical-hit-05.txt
Date: Wed, 13 May 2020 08:20:20 -0700
From: internet-drafts@ietf.org
To: Robert Moskowitz <rgm@labs.htt-consult.com>, Stuart Card <stu.card@axenterprize.com>, Adam Wiethuechter <adam.wiethuechter@axenterprize.com>, Stuart W. Card <stu.card@axenterprize.com>



A new version of I-D, draft-moskowitz-hip-hierarchical-hit-05.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.

Name: draft-moskowitz-hip-hierarchical-hit
Revision: 05
Title: Hierarchical HITs for HIPv2
Document date: 2020-05-12
Group: Individual Submission
Pages: 11
URL: https://www.ietf.org/internet-drafts/draft-moskowitz-hip-hierarchical-hit-05.txt
Status: https://datatracker.ietf.org/doc/draft-moskowitz-hip-hierarchical-hit/
Htmlized: https://tools.ietf.org/html/draft-moskowitz-hip-hierarchical-hit-05
Htmlized: https://datatracker.ietf.org/doc/html/draft-moskowitz-hip-hierarchical-hit
Diff: https://www.ietf.org/rfcdiff?url2=draft-moskowitz-hip-hierarchical-hit-05

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



--------------35032C94B1FA7DA218B4B279-- From nobody Thu May 21 07:24:19 2020 Return-Path: X-Original-To: hipsec@ietf.org Delivered-To: hipsec@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 83AC53A0D13; Thu, 21 May 2020 07:24:12 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: hipsec@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.0.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: hipsec@ietf.org Message-ID: <159007105246.20747.2735344660049014842@ietfa.amsl.com> Date: Thu, 21 May 2020 07:24:12 -0700 Archived-At: Subject: [Hipsec] I-D Action: draft-ietf-hip-dex-20.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.29 List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2020 14:24:13 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol WG of the IETF. Title : HIP Diet EXchange (DEX) Authors : Robert Moskowitz Rene Hummen Miika Komu Filename : draft-ietf-hip-dex-20.txt Pages : 59 Date : 2020-05-21 Abstract: This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. The HIP DEX protocol is primarily designed for computation or memory- constrained sensor/actuator devices. Like HIPv2, it is expected to be used together with a suitable security protocol such as the Encapsulated Security Payload (ESP) for the protection of upper layer protocol data. Unlike HIPv2, HIP DEX does not support Forward Secrecy (FS), and MUST only be used on devices where FS is prohibitively expensive. In addition, HIP DEX can also be used as a keying mechanism for security primitives at the MAC layer, e.g., for IEEE 802.15.4 networks. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-hip-dex/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-hip-dex-20 https://datatracker.ietf.org/doc/html/draft-ietf-hip-dex-20 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-dex-20 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu May 21 07:27:45 2020 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F15143A0D72 for ; Thu, 21 May 2020 07:27:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgOE2TPbgfyM for ; Thu, 21 May 2020 07:27:37 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 428183A0D83 for ; Thu, 21 May 2020 07:27:37 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 1CA68621B8 for ; Thu, 21 May 2020 10:27:36 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id aZgujLUz88IM for ; Thu, 21 May 2020 10:27:33 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id E8D4062196 for ; Thu, 21 May 2020 10:27:32 -0400 (EDT) To: hipsec@ietf.org References: <159007105246.20747.2735344660049014842@ietfa.amsl.com> From: Robert Moskowitz Message-ID: <48022db7-916c-a62a-6aea-6bb3af2d5261@htt-consult.com> Date: Thu, 21 May 2020 10:27:32 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <159007105246.20747.2735344660049014842@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [Hipsec] I-D Action: draft-ietf-hip-dex-20.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2020 14:27:44 -0000 I made it through all of Ben's comments with this version. This should be the home stretch.  So take a read, please. Bob On 5/21/20 10:24 AM, internet-drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Host Identity Protocol WG of the IETF. > > Title : HIP Diet EXchange (DEX) > Authors : Robert Moskowitz > Rene Hummen > Miika Komu > Filename : draft-ietf-hip-dex-20.txt > Pages : 59 > Date : 2020-05-21 > > Abstract: > This document specifies the Host Identity Protocol Diet EXchange (HIP > DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The > HIP DEX protocol design aims at reducing the overhead of the employed > cryptographic primitives by omitting public-key signatures and hash > functions. > > The HIP DEX protocol is primarily designed for computation or memory- > constrained sensor/actuator devices. Like HIPv2, it is expected to > be used together with a suitable security protocol such as the > Encapsulated Security Payload (ESP) for the protection of upper layer > protocol data. Unlike HIPv2, HIP DEX does not support Forward > Secrecy (FS), and MUST only be used on devices where FS is > prohibitively expensive. In addition, HIP DEX can also be used as a > keying mechanism for security primitives at the MAC layer, e.g., for > IEEE 802.15.4 networks. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-hip-dex/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-hip-dex-20 > https://datatracker.ietf.org/doc/html/draft-ietf-hip-dex-20 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-dex-20 > > > 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. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > > _______________________________________________ > Hipsec mailing list > Hipsec@ietf.org > https://www.ietf.org/mailman/listinfo/hipsec From nobody Thu May 21 09:13:02 2020 Return-Path: X-Original-To: hipsec@ietfa.amsl.com Delivered-To: hipsec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2B313A0442 for ; Thu, 21 May 2020 09:13:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G1tOsJ9EF_AO for ; Thu, 21 May 2020 09:12:59 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDE843A0404 for ; Thu, 21 May 2020 09:12:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 6E5A862196 for ; Thu, 21 May 2020 12:12:57 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id uDgZBYGFS-B3 for ; Thu, 21 May 2020 12:12:50 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id BCBD062162 for ; Thu, 21 May 2020 12:12:45 -0400 (EDT) To: HIP From: Robert Moskowitz Message-ID: Date: Thu, 21 May 2020 12:12:44 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------4405879FBB0F8345B2D1A72F" Content-Language: en-US Archived-At: Subject: [Hipsec] Fwd: New Version Notification for draft-moskowitz-orchid-cshake-01.txt X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2020 16:13:01 -0000 This is a multi-part message in MIME format. --------------4405879FBB0F8345B2D1A72F Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Text clean up. ======================= A new version of I-D, draft-moskowitz-orchid-cshake-01.txt has been successfully submitted by Robert Moskowitz and posted to the IETF repository. Name: draft-moskowitz-orchid-cshake Revision: 01 Title: Using cSHAKE in ORCHIDs Document date: 2020-05-21 Group: Individual Submission Pages: 8 URL:https://www.ietf.org/internet-drafts/draft-moskowitz-orchid-cshake-01.txt Status:https://datatracker.ietf.org/doc/draft-moskowitz-orchid-cshake/ Htmlized:https://tools.ietf.org/html/draft-moskowitz-orchid-cshake-01 Htmlized:https://datatracker.ietf.org/doc/html/draft-moskowitz-orchid-cshake Diff:https://www.ietf.org/rfcdiff?url2=draft-moskowitz-orchid-cshake-01 Abstract: This document specifies how to use the cSHAKE hash for ORCHID generation and allows for varying sized hashes in the ORCHID along with additional information within the ORCHID. It is an addendum to ORCHIDv2 [RFC7343]. 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 --------------4405879FBB0F8345B2D1A72F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit 
Text clean up.

=======================
A new version of I-D, draft-moskowitz-orchid-cshake-01.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.

Name:		draft-moskowitz-orchid-cshake
Revision:	01
Title:		Using cSHAKE in ORCHIDs
Document date:	2020-05-21
Group:		Individual Submission
Pages:		8
URL:            https://www.ietf.org/internet-drafts/draft-moskowitz-orchid-cshake-01.txt
Status:         https://datatracker.ietf.org/doc/draft-moskowitz-orchid-cshake/
Htmlized:       https://tools.ietf.org/html/draft-moskowitz-orchid-cshake-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-moskowitz-orchid-cshake
Diff:           https://www.ietf.org/rfcdiff?url2=draft-moskowitz-orchid-cshake-01

Abstract:
   This document specifies how to use the cSHAKE hash for ORCHID
   generation and allows for varying sized hashes in the ORCHID along
   with additional information within the ORCHID.  It is an addendum to
   ORCHIDv2 [RFC7343].

                                                                                  


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
--------------4405879FBB0F8345B2D1A72F--