[Hipsec] HIT to IP in DNS
Oleg Ponomarev <oleg.ponomarev@hiit.fi> Mon, 19 January 2009 23:14 UTC
Return-Path: <hipsec-bounces@ietf.org>
X-Original-To: hip-archive@lists.ietf.org
Delivered-To: ietfarch-hip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7E9E3A6A04; Mon, 19 Jan 2009 15:14:55 -0800 (PST)
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01B3F3A6A04 for <hipsec@core3.amsl.com>; Mon, 19 Jan 2009 15:14:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.058
X-Spam-Level:
X-Spam-Status: No, score=-2.058 tagged_above=-999 required=5 tests=[AWL=0.542, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPTtnLNFvIN7 for <hipsec@core3.amsl.com>; Mon, 19 Jan 2009 15:14:48 -0800 (PST)
Received: from felwood.infrahip.net (felwood.infrahip.net [IPv6:2001:708:140:220::3]) by core3.amsl.com (Postfix) with ESMTP id 96C773A6817 for <hipsec@ietf.org>; Mon, 19 Jan 2009 15:14:46 -0800 (PST)
Received: from stargazer.pc.infrahip.net (stargazer.pc.infrahip.net [IPv6:2001:708:140:220:215:60ff:fe9f:60c4]) by felwood.infrahip.net (8.14.2/8.14.2) with ESMTP id n0JNEPnE013815 for <hipsec@ietf.org>; Tue, 20 Jan 2009 01:14:27 +0200
Date: Tue, 20 Jan 2009 01:14:25 +0200
From: Oleg Ponomarev <oleg.ponomarev@hiit.fi>
X-X-Sender: ponomare@stargazer.pc.infrahip.net
To: hipsec@ietf.org
Message-ID: <alpine.LFD.2.00.0901200059400.17180@stargazer.pc.infrahip.net>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
X-GPG-FINGRPRINT: E94D 632A 70E4 3F92 9A7E B04E 20BF FC6B 983B CA5E
X-GPG-PUBLIC_KEY: http://ponomarev.ru/oleg.asc
MIME-Version: 1.0
Subject: [Hipsec] HIT to IP in DNS
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: hipsec-bounces@ietf.org
Errors-To: hipsec-bounces@ietf.org
Hi! I just submitted an initial version of a draft[1] to specify one of the methods used in HIPL[2] to do the HIT->current IP addresses resolution. This is needed to run legacy applications. Briefly: query A/AAAA 8.7.6.5.4.3.2.1.0.f.e.d.c.b.a.9.8.7.6.5.4.3.2.1.0.1. 0.0.1.0.0.2.hit-to-ip.example.net. and allow their changes from the corresponding HIT. Your comments are appreciated as usual. [1] http://tools.ietf.org/html/draft-ponomarev-hip-hit2ip-00 [2] http://hipl.hiit.fi/ -- Regards, Oleg. _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec
- [Hipsec] HIT to IP in DNS Oleg Ponomarev
- Re: [Hipsec] HIT to IP in DNS Henderson, Thomas R