Subject: [Hipsec-rg] hipl release 1.0.1
From: miika at iki.fi (Miika Komu)
Date: Thu, 21 Dec 2006 22:55:16 +0200 (EET)

HIPL binary release 1.0.1 is available from this URL:

http://infrahip.hiit.fi/hipl/release/1.0.1

Merry Christmas and New Year!

-- 
Miika Komu                                       http://www.iki.fi/miika/

From: thomas.r.henderson at boeing.com (Henderson, Thomas R)
Date: Tue, 5 Dec 2006 09:03:10 -0800
Subject: [Hipsec-rg] FW: I-D ACTION:draft-ahrenholz-hiprg-dht-00.txt
In-Reply-To: <[email-masked]>
Message-ID: <[email-masked]>

> -----Original Message-----
> From: Andrei Gurtov [mailto:gurtov at cs.helsinki.fi] 
> Sent: Tuesday, December 05, 2006 5:10 AM
> To: Ahrenholz, Jeffrey M
> Cc: hipsec-rg at listserv.cybertrust.com
> Subject: Re: [Hipsec-rg] FW: I-D 
> ACTION:draft-ahrenholz-hiprg-dht-00.txt
> 
> 
> Great, perhaps the future draft version(s) should also include reverse
> mapping from IP address to HIT and HIT to FQDN.
> This could perhaps reduce probability of MitM attacks or 
> serve debugging
> purposes (like reverse DNS today).

I am not disagreeing, but I think that these additional mappings require
some more thought, because of security issues and the relation that they
should have to DNS.

Tom

From: gurtov at cs.helsinki.fi (Andrei Gurtov)
Date: Tue, 05 Dec 2006 15:10:18 +0200
Subject: [Hipsec-rg] FW: I-D ACTION:draft-ahrenholz-hiprg-dht-00.txt
In-Reply-To: <[email-masked]>
References: <[email-masked]>
Message-ID: <[email-masked]>

Great, perhaps the future draft version(s) should also include reverse
mapping from IP address to HIT and HIT to FQDN.
This could perhaps reduce probability of MitM attacks or serve debugging
purposes (like reverse DNS today).

Andrei

Ahrenholz, Jeffrey M wrote:
> Andrei and others,
> I'm planning to revise and submit an -01 version of the draft, with the
> following changes:
> - removing LSI-HIT mapping, focus on HIT-IP resolution
> - add support for new OpenDHT remove
> - modified OpenDHT server for verifying signed put/remove (based on Host
> Identity signature)
>
> I'll send around a preview for discussion, for those at InfraHIP, etc.
> with whom we were discussing in October. 
>
> -Jeff
>
>
>   
>> -----Original Message-----
>> From: Andrei Gurtov [mailto:gurtov at cs.helsinki.fi] 
>> Sent: Monday, December 04, 2006 6:11 AM
>> To: Henderson, Thomas R
>> Cc: hipsec-rg at honor.trusecure.com; samu.varjonen at hiit.fi
>> Subject: Re: [Hipsec-rg] FW: I-D 
>> ACTION:draft-ahrenholz-hiprg-dht-00.txt
>>
>>
>>
>> Pretty good draft, someone should submit a new revision.
>>
>> Currently it's not clear why one would need to store LSI-HIT 
>> mappings in 
>> a DHT, since LSI have only local meaning. Reducing local 
>> configuration 
>> state doesn't sound a compelling reason to introduce 
>> additional delay in 
>> resolution. I would vote for removing this part.
>>
>> Instead, ability to map human-readable names to HITs would be quite 
>> valuable. If I could try to connect to "Tom Henderson's 
>> Boeing laptop" 
>> by looking up a mapping from DHT it would be nice. Names could be 
>> reserved from DHT in a first-come/first-served fashion 
>> perhaps with some 
>> features from Unmanaged Internet Architecture. Some people would just 
>> want to store their FQDN->HIT mapping to DNS  using this mechanism 
>> simply because they cannot modify organization's DNS server.
>>
>> If you want to add some interface examples here are captures using 
>> ethereal (thanks to Samu Varjonen for teststub):
>>
>> Put:
>>
>> POST /RPC2 HTTP/1.0
>> User-Agent: hipl
>> Host: 127.0.0.1:5851
>> Content-Type: text/xml
>> Content-length: 326
>>
>> <?xml version="1.0"?>
>> <methodCall><methodName>put</methodName>
>> <params><param><value><base64>IAEAcXyXpbRscxsbCB4SbQ==</base64>
>> </value></param>
>> <param><value><base64>MTI4LjE5Ni4xLjEwMA==</base64></value></param>
>> <param><value><int>120</int></value></param>
>> <param><value><string>HIPL</string></value>
>> </param></params></methodCall>
>>
>>
>> HTTP/1.0 200 OK
>> Date: Wed, 19 Nov 2003 01:49:00 GMT
>> Server: bamboo
>> Connection: close
>> Content-Type: text/xml
>> Content-Length: 135
>>
>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> <methodResponse><params><param><value>
>> <int>0</int></value></param></params>
>> </methodResponse>
>>
>> Example of XML-RPC put operation for HIT and server's response.
>> HIT (2001:0071:7c97:a5b4:6c73:1b1b:081e:126d) (HIT) serves as 
>> a key for
>> an IP address (128.196.1.100).
>>
>>
>> Get:
>>
>> POST /RPC2 HTTP/1.0
>> User-Agent: hipl
>> Host: 127.0.0.1:5851
>> Content-Type: text/xml
>> Content-length: 305
>>
>> <?xml version="1.0"?>
>> <methodCall><methodName>get</methodName>
>> <params>
>> <param><value><base64>IAEAcXyXpbRscxsbCB4SbQ==</base64></value
>>     
>>> </param>
>>>       
>> <param><value><int>10</int></value></param>
>> <param><value><base64></base64></value></param>
>> <param><value><string>HIPL</string></value></param>
>> </params></methodCall>
>>
>>
>>
>> HTTP/1.0 200 OK
>> Date: Wed, 19 Nov 2003 01:49:00 GMT
>> Server: bamboo
>> Connection: close
>> Content-Type: text/xml
>> Content-Length: 279
>>
>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> <methodResponse><params>
>> <param><value><array><data><value><array><data>
>> <value><base64>MTI4LjE5Ni4xLjEwMA==</base64></value></data></a
>> rray></value>
>> <value><base64></base64></value></data></array></value></param>
>> </params></methodResponse>
>>
>>
>> Andrei
>>
>>
>> Henderson, Thomas R wrote:
>>     
>>> FYI, this draft has made it to the repository
>>>
>>> -----Original Message-----
>>> From: Internet-Drafts at ietf.org [mailto:Internet-Drafts at ietf.org] 
>>> Sent: Friday, August 26, 2005 12:50 PM
>>> To: i-d-announce at ietf.org
>>> Subject: I-D ACTION:draft-ahrenholz-hiprg-dht-00.txt 
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>>
>>>
>>> 	Title		: HIP DHT Interface
>>> 	Author(s)	: J. Ahrenholz
>>> 	Filename	: draft-ahrenholz-hiprg-dht-00.txt
>>> 	Pages		: 16
>>> 	Date		: 2005-8-26
>>> 	
>>>    This document specifies a common interface for using HIP 
>>>       
>> with a DHT
>>     
>>>    to provide lookup services.
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ahrenholz-hiprg-dht-00.txt
>>>
>>> _______________________________________________
>>> Hipsec-rg mailing list
>>> Hipsec-rg at honor.trusecure.com
>>> http://honor.trusecure.com/mailman/listinfo/hipsec-rg
>>>   
>>>       
>>     

-- 
Andrei Gurtov  gurtov at hiit.fi  http://www.hiit.fi/andrei.gurtov
Adjunct Professor, TKK
PhD, Senior Research Scientist
Helsinki Institute for Information Technology (HIIT)
High Tech Center, Helsinki, Finland

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3397 bytes
Desc: S/MIME Cryptographic Signature
Url : https://listserv.cybertrust.com/pipermail/hipsec-rg/attachments/20061205/e21a2e3c/attachment.bin 

From: jeffrey.m.ahrenholz at boeing.com (Ahrenholz, Jeffrey M)
Date: Mon, 4 Dec 2006 15:47:37 -0800
Subject: [Hipsec-rg] FW: I-D ACTION:draft-ahrenholz-hiprg-dht-00.txt
In-Reply-To: <[email-masked]>
Message-ID: <[email-masked]>

Andrei and others,
I'm planning to revise and submit an -01 version of the draft, with the
following changes:
- removing LSI-HIT mapping, focus on HIT-IP resolution
- add support for new OpenDHT remove
- modified OpenDHT server for verifying signed put/remove (based on Host
Identity signature)

I'll send around a preview for discussion, for those at InfraHIP, etc.
with whom we were discussing in October. 

-Jeff

> -----Original Message-----
> From: Andrei Gurtov [mailto:gurtov at cs.helsinki.fi] 
> Sent: Monday, December 04, 2006 6:11 AM
> To: Henderson, Thomas R
> Cc: hipsec-rg at honor.trusecure.com; samu.varjonen at hiit.fi
> Subject: Re: [Hipsec-rg] FW: I-D 
> ACTION:draft-ahrenholz-hiprg-dht-00.txt
> 
> 
> 
> Pretty good draft, someone should submit a new revision.
> 
> Currently it's not clear why one would need to store LSI-HIT 
> mappings in 
> a DHT, since LSI have only local meaning. Reducing local 
> configuration 
> state doesn't sound a compelling reason to introduce 
> additional delay in 
> resolution. I would vote for removing this part.
> 
> Instead, ability to map human-readable names to HITs would be quite 
> valuable. If I could try to connect to "Tom Henderson's 
> Boeing laptop" 
> by looking up a mapping from DHT it would be nice. Names could be 
> reserved from DHT in a first-come/first-served fashion 
> perhaps with some 
> features from Unmanaged Internet Architecture. Some people would just 
> want to store their FQDN->HIT mapping to DNS  using this mechanism 
> simply because they cannot modify organization's DNS server.
> 
> If you want to add some interface examples here are captures using 
> ethereal (thanks to Samu Varjonen for teststub):
> 
> Put:
> 
> POST /RPC2 HTTP/1.0
> User-Agent: hipl
> Host: 127.0.0.1:5851
> Content-Type: text/xml
> Content-length: 326
> 
> <?xml version="1.0"?>
> <methodCall><methodName>put</methodName>
> <params><param><value><base64>IAEAcXyXpbRscxsbCB4SbQ==</base64>
> </value></param>
> <param><value><base64>MTI4LjE5Ni4xLjEwMA==</base64></value></param>
> <param><value><int>120</int></value></param>
> <param><value><string>HIPL</string></value>
> </param></params></methodCall>
> 
> 
> HTTP/1.0 200 OK
> Date: Wed, 19 Nov 2003 01:49:00 GMT
> Server: bamboo
> Connection: close
> Content-Type: text/xml
> Content-Length: 135
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <methodResponse><params><param><value>
> <int>0</int></value></param></params>
> </methodResponse>
> 
> Example of XML-RPC put operation for HIT and server's response.
> HIT (2001:0071:7c97:a5b4:6c73:1b1b:081e:126d) (HIT) serves as 
> a key for
> an IP address (128.196.1.100).
> 
> 
> Get:
> 
> POST /RPC2 HTTP/1.0
> User-Agent: hipl
> Host: 127.0.0.1:5851
> Content-Type: text/xml
> Content-length: 305
> 
> <?xml version="1.0"?>
> <methodCall><methodName>get</methodName>
> <params>
> <param><value><base64>IAEAcXyXpbRscxsbCB4SbQ==</base64></value
> ></param>
> <param><value><int>10</int></value></param>
> <param><value><base64></base64></value></param>
> <param><value><string>HIPL</string></value></param>
> </params></methodCall>
> 
> 
> 
> HTTP/1.0 200 OK
> Date: Wed, 19 Nov 2003 01:49:00 GMT
> Server: bamboo
> Connection: close
> Content-Type: text/xml
> Content-Length: 279
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <methodResponse><params>
> <param><value><array><data><value><array><data>
> <value><base64>MTI4LjE5Ni4xLjEwMA==</base64></value></data></a
> rray></value>
> <value><base64></base64></value></data></array></value></param>
> </params></methodResponse>
> 
> 
> Andrei
> 
> 
> Henderson, Thomas R wrote:
> > FYI, this draft has made it to the repository
> >
> > -----Original Message-----
> > From: Internet-Drafts at ietf.org [mailto:Internet-Drafts at ietf.org] 
> > Sent: Friday, August 26, 2005 12:50 PM
> > To: i-d-announce at ietf.org
> > Subject: I-D ACTION:draft-ahrenholz-hiprg-dht-00.txt 
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> >
> > 	Title		: HIP DHT Interface
> > 	Author(s)	: J. Ahrenholz
> > 	Filename	: draft-ahrenholz-hiprg-dht-00.txt
> > 	Pages		: 16
> > 	Date		: 2005-8-26
> > 	
> >    This document specifies a common interface for using HIP 
> with a DHT
> >    to provide lookup services.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ahrenholz-hiprg-dht-00.txt
> >
> > _______________________________________________
> > Hipsec-rg mailing list
> > Hipsec-rg at honor.trusecure.com
> > http://honor.trusecure.com/mailman/listinfo/hipsec-rg
> >   
> 
> 

From: gurtov at cs.helsinki.fi (Andrei Gurtov)
Date: Mon, 04 Dec 2006 16:10:39 +0200
Subject: [Hipsec-rg] FW: I-D ACTION:draft-ahrenholz-hiprg-dht-00.txt
In-Reply-To: <[email-masked]>
References: <[email-masked]>
Message-ID: <[email-masked]>

Pretty good draft, someone should submit a new revision.

Currently it's not clear why one would need to store LSI-HIT mappings in 
a DHT, since LSI have only local meaning. Reducing local configuration 
state doesn't sound a compelling reason to introduce additional delay in 
resolution. I would vote for removing this part.

Instead, ability to map human-readable names to HITs would be quite 
valuable. If I could try to connect to "Tom Henderson's Boeing laptop" 
by looking up a mapping from DHT it would be nice. Names could be 
reserved from DHT in a first-come/first-served fashion perhaps with some 
features from Unmanaged Internet Architecture. Some people would just 
want to store their FQDN->HIT mapping to DNS  using this mechanism 
simply because they cannot modify organization's DNS server.

If you want to add some interface examples here are captures using 
ethereal (thanks to Samu Varjonen for teststub):

Put:

POST /RPC2 HTTP/1.0
User-Agent: hipl
Host: 127.0.0.1:5851
Content-Type: text/xml
Content-length: 326

<?xml version="1.0"?>
<methodCall><methodName>put</methodName>
<params><param><value><base64>IAEAcXyXpbRscxsbCB4SbQ==</base64>
</value></param>
<param><value><base64>MTI4LjE5Ni4xLjEwMA==</base64></value></param>
<param><value><int>120</int></value></param>
<param><value><string>HIPL</string></value>
</param></params></methodCall>

HTTP/1.0 200 OK
Date: Wed, 19 Nov 2003 01:49:00 GMT
Server: bamboo
Connection: close
Content-Type: text/xml
Content-Length: 135

<?xml version="1.0" encoding="ISO-8859-1"?>
<methodResponse><params><param><value>
<int>0</int></value></param></params>
</methodResponse>

Example of XML-RPC put operation for HIT and server's response.
HIT (2001:0071:7c97:a5b4:6c73:1b1b:081e:126d) (HIT) serves as a key for
an IP address (128.196.1.100).

Get:

POST /RPC2 HTTP/1.0
User-Agent: hipl
Host: 127.0.0.1:5851
Content-Type: text/xml
Content-length: 305

<?xml version="1.0"?>
<methodCall><methodName>get</methodName>
<params>
<param><value><base64>IAEAcXyXpbRscxsbCB4SbQ==</base64></value></param>
<param><value><int>10</int></value></param>
<param><value><base64></base64></value></param>
<param><value><string>HIPL</string></value></param>
</params></methodCall>

HTTP/1.0 200 OK
Date: Wed, 19 Nov 2003 01:49:00 GMT
Server: bamboo
Connection: close
Content-Type: text/xml
Content-Length: 279

<?xml version="1.0" encoding="ISO-8859-1"?>
<methodResponse><params>
<param><value><array><data><value><array><data>
<value><base64>MTI4LjE5Ni4xLjEwMA==</base64></value></data></array></value>
<value><base64></base64></value></data></array></value></param>
</params></methodResponse>

Andrei

Henderson, Thomas R wrote:
> FYI, this draft has made it to the repository
>
> -----Original Message-----
> From: Internet-Drafts at ietf.org [mailto:Internet-Drafts at ietf.org] 
> Sent: Friday, August 26, 2005 12:50 PM
> To: i-d-announce at ietf.org
> Subject: I-D ACTION:draft-ahrenholz-hiprg-dht-00.txt 
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: HIP DHT Interface
> 	Author(s)	: J. Ahrenholz
> 	Filename	: draft-ahrenholz-hiprg-dht-00.txt
> 	Pages		: 16
> 	Date		: 2005-8-26
> 	
>    This document specifies a common interface for using HIP with a DHT
>    to provide lookup services.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ahrenholz-hiprg-dht-00.txt
>
> _______________________________________________
> Hipsec-rg mailing list
> Hipsec-rg at honor.trusecure.com
> http://honor.trusecure.com/mailman/listinfo/hipsec-rg
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3397 bytes
Desc: S/MIME Cryptographic Signature
Url : https://listserv.cybertrust.com/pipermail/hipsec-rg/attachments/20061204/02ec4e71/attachment.bin