constrained links.
On 8/13/23 16:32, Stu Card wrote:
Although I have long been intrigues by IKE and MobIKE, what I don't know about
them would fill volumes.
Any of you better-informed folk willing to essay this?
-Original Message-
From: Hipsec On Behalf Of Robert Moskowitz
Sent
Please note that in ipsecme there is work to apply SCHC to EXP:
https://datatracker.ietf.org/doc/draft-mglt-ipsecme-diet-esp/
This is a 32 byte savings.
The additional interesting thing impacting HIP is that addition to IKEv2
to negotiate Diet-ESP:
Message
Subject: New Version Notification for
draft-moskowitz-hip-fast-mobility-04.txt
Date: Fri, 17 Jun 2022 07:26:29 -0700
From: internet-dra...@ietf.org
To: Stuart W. Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart Card
A new version of I-D, draft-moskowitz-hip-fast
tz, Ed., T. Heer, P. Jokela, T. Henderson
Category: PROPOSED STANDARD
Source : Host Identity Protocol
Area: Internet
Stream : IETF
Verifying Party : IESG
--
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:r...
Jokela, T. Henderson
Category: PROPOSED STANDARD
Source : Host Identity Protocol
Area: Internet
Stream : IETF
Verifying Party : IESG
--
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:r...@labs.htt-consult.com
There's no lim
Sorry everyone.
This is the only IETF/ICAO/ASTM email I have sent since early Mar 25.
No work, no billable hours. ;)
And no work on DRIP other than one short phone call. Sigh.
Holiday and family trumped all else.
I WILL be back on the 5th, totally swamped catching up.
Speaking of catching
Eric,
I will respond to this Tuesday. Lots of emails have magically appeared
after reconfiguring my client. :(
Passover is consuming my time today. So Tuesday is the first of the
middle days and the first I can get to this.
HIP will be on the top of my list.
I think it was the
Wiethuechter
, Robert Moskowitz
, Stuart Card
A new version of I-D, draft-moskowitz-hip-new-crypto-09.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name: draft-moskowitz-hip-new-crypto
Revision: 09
Title: New Cryptographic Algorithms for HIP
Document
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
t seems that the conclusion is near ;-)
-éric
*From: *Robert Moskowitz
*Date: *Monday, 18 January 2021 at 17:06
*To: *Eric Vyncke , Robert Moskowitz
, "hipsec@ietf.org" ,
"draft-ietf-hip-...@ietf.org" , Miika
Komu
*Cc: *Roman Danyliw , Eric Rescorla ,
Gonzalo Camarillo ,
"re
with X25519
On Mon, Jan 18, 2021 at 8:35 AM Robert Moskowitz <mailto:r...@htt-consult.com>> wrote:
Ah, found the paper 'free' from:
https://www.researchgate.net/publication/300253314_Efficient_and_Secure_Elliptic_Curve_Cryptography_for_8-bit_AVR_Microcontrollers
Oops hold it on that paywall URL issue. I responded with a different
paper. All else is still ok, but let me dig a big more on that paper
for non-IACR members.
On 1/18/21 11:06 AM, Robert Moskowitz wrote:
On 1/18/21 9:12 AM, Eric Vyncke (evyncke) wrote:
Standard
TD ;LR : more work
here have been a couple of significant changes (I_NONCE,
some deleted ciphers) since the IETF last call (see
https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-dex-23=draft-ietf-hip-dex-21
<https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-dex-23=draft-ietf-hip-dex-21>
), so, another IETF Last
-dra...@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
;
[2] https://www.rfc-editor.org/cluster_info.php?cid=C386
<https://www.rfc-editor.org/cluster_info.php?cid=C386>
[3] and possibly I will set the state of HIP-DEX as ‘dead’ on the
datatracker
--
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:r
...@ietf.org
To: Robert Moskowitz , Stuart Card
, Adam Wiethuechter
, Stuart W. Card
A new version of I-D, draft-moskowitz-hip-new-crypto-05.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name: draft-moskowitz-hip-new-crypto
Revision: 05
Title: New
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
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
-05.txt
Date: Wed, 13 May 2020 08:20:20 -0700
From: internet-dra...@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
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
Jeff,
Thanks for the feedback. After Passover, I will incorporate what I pull
out of this.
Bob
On 4/6/20 1:51 PM, Jeff Ahrenholz wrote:
Bob,
Brief review below...
I have updated the hip-fast-mobility draft.
I welcome review.
It will be used in an upcoming DRIP N-RID secure transport
HIPsters:
Miika and I have been working away to get NAT-traversal and DEX through
the IESG and on to last call. We are close
That being said, hopefully you have noticed what is going on in the DRIP
workgroup.
In My Highly Biased Opinion (IMHBO), and what is an Opinion, but a bias...
10:01 PM, Benjamin Kaduk wrote:
Hi Bob,
Sorry this dropped off my radar for so long -- I got really swamped.
Just a few notes inline, as I'll focus on reading the -18.
On Mon, Mar 09, 2020 at 04:00:33PM -0400, Robert Moskowitz wrote:
On 3/4/20 12:44 PM, Benjamin Kaduk via Datatracker wrote
-mobility-03.txt
Date: Fri, 03 Apr 2020 06:24:02 -0700
From: internet-dra...@ietf.org
To: Stuart W. Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart Card
A new version of I-D, draft-moskowitz-hip-fast-mobility-03.txt
has been successfully submitted by Robert Moskowitz and posted
Roman,
In ver -17, I have added the hex values for CKDF-Extract and CKDF-Expand.
Please let me know where you stand on my various responses.
Bob
On 3/17/20 9:11 AM, Robert Moskowitz wrote:
I am cutting off all I have responded to in v 14 & 15.
I have posted ver 16.
there is one outstan
Ben,
In ver 18 I have replaced "Perfect Forward Secrecy" with "Forward Secrecy".
That seems to be a consensus on saag.
Please let me know where you stand on my various responses.
Thank you
Bob
On 3/18/20 11:50 AM, Robert Moskowitz wrote:
I have pushed out ver 17
I beli
There are two strings used in the KEYMAT process i HIP-DEX:
CKDF-Extract
and
CKDF-Expand
The draft says that they are "an octet string".
Thing is that depending on which google found tool, I get different text
to octet values!
So to those implementors out there:
What is the proper octet
:00 PM, Robert Moskowitz wrote:
On 3/4/20 12:44 PM, Benjamin Kaduk via Datatracker wrote:
Benjamin Kaduk has entered the following ballot position for
draft-ietf-hip-dex-13: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC
raft of explanations in my email responses.
On 3/6/20 9:21 AM, Robert Moskowitz wrote:
On 3/4/20 1:28 PM, Roman Danyliw via Datatracker wrote:
Roman Danyliw has entered the following ballot position for
draft-ietf-hip-dex-13: Discuss
When responding, please keep the subject line intact and reply to
Suresh,
Your text appeared in ver 14. Please check it out.
thank you.
Bob
On 3/5/20 2:00 PM, Suresh Krishnan wrote:
Hi Bob,
This text works for me. I will clear as soon as the new revision hits.
Regards
Suresh
On Mar 5, 2020, at 11:04 AM, Robert Moskowitz wrote:
Here is the text I
I will be pushing out v 15 shortly with some more fixes. This way you
can review them as I go, rather in one go. The items I previously said
'fixed' were in ver 14.
On 3/6/20 9:21 AM, Robert Moskowitz wrote:
On 3/4/20 1:28 PM, Roman Danyliw via Datatracker wrote:
Roman Danyliw has
On 3/4/20 1:28 PM, Roman Danyliw via Datatracker wrote:
Roman Danyliw has entered the following ballot position for
draft-ietf-hip-dex-13: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
Here is the text I put together for revising sec 5.4 (see below).
On 3/3/20 11:47 PM, Suresh Krishnan via Datatracker wrote:
Suresh Krishnan has entered the following ballot position for
draft-ietf-hip-dex-13: Discuss
When responding, please keep the subject line intact and reply to all
email
strained (DoSing) attacker is competing with a constrained
honest initiator to solve puzzles during an attack, it seems like the
honest initiator is going to lose out pretty badly.
Section 4.1.4
There are security considerations for serializing the HIP state to
nonvolatile storage!
--
Standard Robert M
On 3/4/20 10:53 AM, Jeff Ahrenholz wrote:
https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#icmpv6-parameters-codes-5
And nothing there that looks right.
So what is done in HIP BEX implementations? Both v1 and v2?
For our HIPv1 implementation:
IPv4 packets - we
to be sent need a Code field to be set in
addition to the Pointer. What Code should be used in this message? Please
specify this.
--
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:r...@labs.htt-consult.com
There's no limit to what can be accomplished if it does
On 2/12/20 12:20 PM, Jeff Ahrenholz wrote:
I believe this version answers all the IESG issues.
Please review, there are some important additions.
EKR had a number of security concerns. Some I feel don't apply to HIP, like
use an AEAD for HIP packet security.
But there are a number of
On 2/12/20 11:48 AM, Jeff Ahrenholz wrote:
I believe this version answers all the IESG issues.
Please review, there are some important additions.
EKR had a number of security concerns. Some I feel don't apply to HIP, like
use an AEAD for HIP packet security.
But there are a number of
On 2/12/20 12:50 PM, Jeff Ahrenholz wrote:
Looking at Section 6.3 HIP DEX KEYMAT Generation, it discusses
using Diffie-Hellman derived key Kij, but I don't see anything
about using I_NONCE. There is a random #I provided by the
Responder from the PUZZLE parameter, but nothing about a
random
On 2/12/20 12:20 PM, Jeff Ahrenholz wrote:
I believe this version answers all the IESG issues.
Please review, there are some important additions.
EKR had a number of security concerns. Some I feel don't apply to HIP, like
use an AEAD for HIP packet security.
But there are a number of
Forwarded Message
Subject:New Version Notification for draft-ietf-hip-dex-12.txt
Date: Sun, 09 Feb 2020 23:11:55 -0800
From: internet-dra...@ietf.org
To: Robert Moskowitz , Rene Hummen
, Miika Komu
A new version of I-D, draft-ietf-hip-dex-12.txt
has been successfully
to
implement it. I do expect to have something done for a dex-13.txt draft.
-Ekr
Robert Moskowitz
___
Hipsec mailing list
Hipsec@ietf.org
https://www.ietf.org/mailman/listinfo/hipsec
I do not see anything in this comment that is directly actionable, but
will provide some comments here.
On 11/25/19 1:38 AM, Michael Richardson via Datatracker wrote:
Reviewer: Michael Richardson
Review result: Ready
I am the assigned IoT-Directorate reviewer for 1draft-ietf-hip-dex
I
On 1/24/20 1:41 PM, Michael Richardson wrote:
Robert Moskowitz wrote:
> I would actually like to make a presentation at SAAG about KMAC as a KDF
and
> why the IETF should incorporate it.
> SP 800-185 was published back in Dec 2016. This clearly shows how to use
l) steps to complete that work.
Yours,
Daniel
On Thu, Jan 23, 2020 at 10:47 AM Robert Moskowitz
mailto:r...@labs.htt-consult.com>> wrote:
I have added sec 8.2, discussing the security of using KMAC as a
KDF. This is based on a conversation I had with the Keccak team
at the IAC
-moskowitz-hip-hierarchical-hit-03.txt
Date: Mon, 16 Dec 2019 11:22:00 -0800
From: internet-dra...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
A new version of I-D, draft-moskowitz-hip-hierarchical-hit-03.txt
has been successfully submitted by Robert
-0800
From: internet-dra...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
A new version of I-D, draft-moskowitz-hip-new-crypto-03.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name: draft-moskowitz-hip-new
Dec 2019 14:07:16 -0800
From: internet-dra...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
A new version of I-D, draft-moskowitz-orchid-cshake-00.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name: draft
Fellow HIPsters:
The TM-RID BOF went well. The opinion is to charter TM-RID as a new
workgroup. It will be doing a number of addendum to HIP.
Please join the tm-...@ietf.org list to participate.
Bob
___
Hipsec mailing list
Hipsec@ietf.org
Right now I will only reply to the AEAD comment.
I believe this is directed to the HIP_CIPHER parameter and its use in a
number of HIP parameter objects. The ECHO may be encrypted with it and
in DEX we add the PSK.
Since all HIP packets that contain these fields are MACed with HIP_MAC,
it
I have updated the TMRID BOF Charter at:
https://trac.tools.ietf.org/bof/trac/wiki/WikiStart
Here it is. Comments/corrections/additions welcomed:
Governmental agencies worldwide, including the United States Federal
Aviation Administration (FAA), are embarking on rule making processes to
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
The BOF is Tuesday:
1330-1500 Afternoon Session I
VIP A INT tmrid Trustworthy Multipurpose
Remote ID BOF
Hullet IRTF gaia Global Access to the
Internet for All
Padang IRTF maprg Measurement and Analysis for
...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
A new version of I-D, draft-wiethuechter-tmrid-auth-00.txt
has been successfully submitted by Adam Wiethuechter and posted to the
IETF repository.
Name: draft-wiethuechter-tmrid-auth
Revision: 00
Title: TM-RID
Moskowitz
, Stuart W. Card
A new version of I-D, draft-moskowitz-hip-hhit-registries-01.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name: draft-moskowitz-hip-hhit-registries
Revision: 01
Title: Hierarchical HIT Registries
Document date: 2019-10-17
, Robert Moskowitz
, Stuart W. Card
A new version of I-D, draft-moskowitz-hip-hierarchical-hit-02.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name: draft-moskowitz-hip-hierarchical-hit
Revision: 02
Title: Hierarchical HITs for HIPv2
Document date
.txt
Date: Thu, 03 Oct 2019 08:23:18 -0700
From: internet-dra...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
A new version of I-D, draft-moskowitz-hip-new-crypto-02.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF
IESG will be looking for activity here to gauge the interest/activity.
Bob
On 9/20/19 4:45 PM, Robert Moskowitz wrote:
Dear HIPsters,
I am in discussion with Ganzalo and Eric about a HIP session in
Singapore.
The focus is the new work to support "Trustworthy Multipurpose
RemoteID" with t
Keyak.
Forwarded Message
Subject: New Version Notification for
draft-moskowitz-hip-new-crypto-01.txt
Date: Wed, 25 Sep 2019 14:35:36 -0700
From: internet-dra...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
A new version of I-D
Dear HIPsters,
I am in discussion with Ganzalo and Eric about a HIP session in Singapore.
The focus is the new work to support "Trustworthy Multipurpose RemoteID"
with the target user of UAS.
This week I attended the nuair.org UAS Symposium outside of Syracuse NY
and received considerable
I don't have the KEYMAT construction right. I am talking to NIST about
what is needed. Stay tuned.
Close but not quite there.
On 9/15/19 7:30 PM, Robert Moskowitz wrote:
This completes the first set of drafts for tm-rid.
This draft has a couple drafty areas. Particularly in the cipher, I
Message
Subject: New Version Notification for
draft-moskowitz-hip-new-crypto-00.txt
Date: Sun, 15 Sep 2019 16:12:21 -0700
From: internet-dra...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
A new version of I-D, draft-moskowitz-hip-new-crypto-00
On 9/13/19 11:48 AM, Jeff Ahrenholz wrote:
And the new cipher choice is Keyak. For now. How do we get the ESP transform
number assigned? What docs do we need for that?
Probably needs a short RFC, similar to this one?
https://tools.ietf.org/html/rfc4543
Yes, but no AH. Perhaps. I have
Forwarded Message
Subject: New Version Notification for
draft-moskowitz-hip-hhit-registries-00.txt
Date: Fri, 13 Sep 2019 07:13:14 -0700
From: internet-dra...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
A new version of I-D, draft-moskowitz
From: internet-dra...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
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
-dra...@ietf.org
To: Stuart Card , Adam Wiethuechter
, Robert Moskowitz
, Stuart W. Card
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
I am a bit frustrated here on delays on a number of fronts.
I have been working silently to put some final touches on DEX and
discussions on Native NAT.
But more time on Hierarchical HITs, along with advancements in cryptography.
I am looking for a co-author that is familiar with HIP's
I am working on a new set of crypto for HIP. This is to take advantage
of advancements and hopefully make things better in small things.
I have been looking at FIPS 202 and NIST 800-185 for the new hash and
MACing. In particular SHAKE and KMAC.
Right now, NIST only specifies b=1600 for the
I have been working on my Hierarchical HIT drafts. I have been testing
building x.509 certs with them as the SAN. Thing is were do these certs
come from?
So I moved on to when the device uses HIP Registration to register the
HHIT to its Registry, it could present a CSR in the payload and if
This is connected to the Trustworthy Multipurpose Remote IDs
(tm-...@ietf.org)
Right now I am working on what a eddsa pki would be that would back up
the proposed HHITs and various repositories. For this I want to
generate some testing HHITs.
These HHITs will be used in x.509 certs as in
As part of developing the "Trustworthy Multipurpose Remote ID", I am
going to add new crypto algorithms along the lines that I have in
draft-moskowitz-small-crypto.
The "open' question is that of a PAKE. Would HIP benefit with a PAKE.
I really don't see it, but since I am opening up the
to get enough
information before the parties (FAA and ATSM) like real soon. But there
will be time after that if TM-RID is accepted to finish the work properly.
On 7/3/19 5:35 PM, Robert Moskowitz wrote:
Hello all,
I thank all that have been working away on the last few items while I
have been
Hello all,
I thank all that have been working away on the last few items while I
have been struggling along.
Recently, I met Stuart Card and Adam Wiethuechter of Axenterprize. They
have in a number of gov projects where they have deployed HIP based
solutions. All quietly on their own.
ues: N/A
Nits/editorial comments: N/A
--
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:r...@labs.htt-consult.com
There's no limit to what can be accomplished if it doesn't matter who
gets the credit
___
Hipsec mailin
On 02/23/2018 03:23 AM, Qin Wu wrote:
Reviewer: Qin Wu
Review result: Ready
Summary:
This document defines the Host Identity Protocol Diet EXchange (HIP
DEX) protocol for constrained devices. The draft is well written. I believe
it is ready for publication.
Major issue: None
Minor
First, it seems I had problems with my HIP list folder and have not seen
any messages since around May. There here, and I will read them...
Now. Please read:
https://mailarchive.ietf.org/arch/msg/ideas/GbyBs812xGVAN9LFRbpAp3lUuys
And some follow up discussions. Basically IDEAS is targeting
:59 AM, Miika Komu wrote:
Hi Robert,
yes, mobility support is specified in the draft.
*From:*Robert Moskowitz [mailto:r...@htt-consult.com]
*Sent:* Friday, November 25, 2016 6:33 AM
*To:* Miika Komu <miika.k...@ericsson.com>; hipsec@ietf.org
*Subject:* Re: [Hipsec] I-D Action:
draft-ie
Miika,
Does this draft cover the use case where the mobile HIP device moves
from one NATed network to another. Consider you are in Starbucks and
move next door to Dunkin Donuts.
Your device did this augmented BEX exchange in Starbucks. You walk into
DD and your interface decides the
What is 'co called' in this text:
o In ICE, the conflict when two communicating end-points take the
same controlling role is solved using random values (co called
tie-breaker value). In this protocol, the conflict is solved by
the standard HIP base exchange procedure, where
I will start on it Tuesday.
Bob
On 11/20/2016 03:26 AM, Gonzalo Camarillo wrote:
Hi Tom,
thanks. Your comments seem to be the only one we got on this draft
during the WGLC. Authors, could you please revise the draft in order to
address these comments?
Thanks,
Gonzalo
On 20/11/2016 4:32 AM,
... well...
Cheers,
Gonzalo
On 28/10/2016 3:31 AM, Robert Moskowitz wrote:
I just updated a a set of drafts:
These define a Secure Session Layer Service. The last has how to manage
it with HIP and defines some new HIP parameters to negotiate sse and
gpcomp:
https://www.ietf.org/internet-drafts
drafts minimal to put the proposal together.
Bob
A new version of I-D, draft-moskowitz-hip-based-5gpp-ip-mobility-00.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.
Name:draft-moskowitz-hip-based-5gpp-ip-mobility
Revision:00
Title:HIP
On 09/27/2016 04:58 AM, Miika Komu wrote:
Hi,
On 09/27/2016 03:56 AM, Robert Moskowitz wrote:
On 09/26/2016 09:08 AM, Miika Komu wrote:
Hi,
On 09/16/2016 02:45 PM, Robert Moskowitz wrote:
On 09/16/2016 06:57 AM, Tom Henderson wrote:
On Thu, 15 Sep 2016, Robert Moskowitz wrote
On 09/26/2016 09:08 AM, Miika Komu wrote:
Hi,
On 09/16/2016 02:45 PM, Robert Moskowitz wrote:
On 09/16/2016 06:57 AM, Tom Henderson wrote:
On Thu, 15 Sep 2016, Robert Moskowitz wrote:
5206-bis specifies how to user RVS for the 'double-jump' mobility
problem.
3.2.3 1) says:
1
On 09/19/2016 06:19 AM, Tom Henderson wrote:
Bob, sorry for the delay in replying (inline below)
On 09/13/2016 02:14 AM, Robert Moskowitz wrote:
I have one question on sec 5.4 before I enter a comment...
On 09/12/2016 03:28 PM, Mirja Kuehlewind wrote:
5) section 5.4: How long
I cannot remember why we mandated HIP_SIGNATURE in UPDATE packet,
particularly when we have the HIP_MAC. Sec 5.3.5 in 7401.
I am sure we had a good reason, but I am not finding it
thanks
Bob
___
Hipsec mailing list
Hipsec@ietf.org
5206-bis specifies how to user RVS for the 'double-jump' mobility problem.
3.2.3 1) says:
1. The mobile host sending an UPDATE to the peer, and not receiving an
ACK, MAY resend the UPDATE to a rendezvous server (RVS) of the peer, if
such a server is known.
But it DOES know there is an RVS
I have one question on sec 5.4 before I enter a comment...
On 09/12/2016 03:28 PM, Mirja Kuehlewind wrote:
5) section 5.4: How long will an address be in UNVERIFIED state in case
the verification is not successful (no reply). Is there a timer? How
often will the peer retry the verification
On 09/11/2016 04:06 PM, René Hummen wrote:
Hello Miika,
going through your email again, I saw a total of four suggestions.
Three of them refer to imprecisions in the text of RFC 7401 (which I
copy/pasted for HIP DEX). There, I understood that consistency with
RFC 7401 has a higher priority
-hierarchical-hip-00.txt
Date: Wed, 03 Aug 2016 20:37:24 -0700
From: internet-dra...@ietf.org
To: Xiaohu Xu <xuxia...@huawei.com>, Robert Moskowitz
<r...@htt-consult.com>
A new version of I-D, draft-moskowitz-hierarchical-hip-00.txt
has been successfully submitted by Robe
at?
On 07/27/2016 06:19 AM, Robert Moskowitz wrote:
I am looking at a HIT enrollment function using 5403-bis. But why
should the Registrar accept the Register. This is our basic need of
an Out-off-Band process to trust an enrollment.
So assume that some process establishes a PSK between
Identity Protocol of the IETF.
Title : HIP Diet EXchange (DEX)
Authors : Robert Moskowitz
Rene Hummen
Filename: draft-ietf-hip-dex-02.txt
Pages : 47
Date: 2016-03-21
Abstract
I invite you all to look at work Sue Hares, I, and a few others have
been doing in developing a Session Layer Service that includes security
at the session layer. FOr IETF reasons, Sue did the top-level draft
within I2NSF:
https://www.ietf.org/internet-drafts/draft-hares-i2nsf-ssls-00.txt
-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Host Identity Protocol of the IETF.
Title : HIP Diet EXchange (DEX)
Authors : Robert Moskowitz
Rene Hummen
Filename: draft
to take your outer envelope that contains your XML and compress the
whole thing.
On 03/10/2016 02:10 PM, Derek Fawcus wrote:
On Thu, Mar 10, 2016 at 08:29:15AM -0500, Robert Moskowitz wrote:
I have found comp in TLS, RFC 3749, so HIP's ESP is the only one missing
compression. How did I miss
. Plus with DEX on constrained networks, compression is
even more valuable.
But can you point me to a paper on the TLS compression attack?
On 03/10/2016 02:10 PM, Derek Fawcus wrote:
On Thu, Mar 10, 2016 at 08:29:15AM -0500, Robert Moskowitz wrote:
I have found comp in TLS, RFC 3749, so HIP's ESP
algorithm, or a value of ZERO if none.
R2 would have the confirmed value.
NOTIFY could be used to set up IPCOMP (or change it) at a later time.
Comments?
On 03/09/2016 10:20 AM, Robert Moskowitz wrote:
Why did we not create a parameter to negotiate IPCOMP (currently RFC
3173)?
In IKEv2
Why did we not create a parameter to negotiate IPCOMP (currently RFC 3173)?
In IKEv2 it is negotiated in NOTIFY messages, not the basic exchange and
becomes part of the daughter SA(s).
On contrained networks, IPCOMP could well be of value. Also if HIP is
used to establish the SAs for SSE
iEEE 802.15.9 is Key Management Transport for 802.15.4. It calls out
support for a number of KMPs defined here in the IETF, including both
HIP BEX and DEX. This is one of the many reasons why I want to get HIP
DEX published as an RFC, as only RFCs can be referenced in a published
IEEE
I have uploaded the current draft with the name change.
I will look at what it will take to add Curve25519 (RFC 7748).
On 03/01/2016 02:58 AM, Gonzalo Camarillo wrote:
Authors of draft-moskowitz-hip-rg-dex,
could you please revise the draft as a WG item? Please, use the
following file name in
1 - 100 of 130 matches
Mail list logo
