Re: [Hipsec] Relaying to non-hip aware servers

Robert Moskowitz <rgm@htt-consult.com> Tue, 27 September 2016 14:15 UTC

Return-Path: <rgm@htt-consult.com>
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 D2F2712B1F2 for <hipsec@ietfa.amsl.com>; Tue, 27 Sep 2016 07:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level:
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_PASS=-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 CBQ2NvErhL39 for <hipsec@ietfa.amsl.com>; Tue, 27 Sep 2016 07:15:31 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (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 E26B612B1E1 for <hipsec@ietf.org>; Tue, 27 Sep 2016 07:15:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 2EDFD621C4; Tue, 27 Sep 2016 10:15:30 -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 fkq-Wzfby8WU; Tue, 27 Sep 2016 10:15:28 -0400 (EDT)
Received: from lx120e.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 492DD621C5; Tue, 27 Sep 2016 10:15:25 -0400 (EDT)
To: Miika Komu <miika.komu@ericsson.com>, hip WG <hipsec@ietf.org>
References: <a1c2517a-1e06-7ae9-284d-79a172d8a3c5@htt-consult.com> <5a42438c-fcb6-d74f-b590-7f310a9d5447@ericsson.com>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <6b8d5b7c-1eff-a858-5a67-153253c18870@htt-consult.com>
Date: Tue, 27 Sep 2016 10:15:24 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <5a42438c-fcb6-d74f-b590-7f310a9d5447@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/HXLyLWjSWgcCWgEazP0Jt8p2Hso>
Subject: Re: [Hipsec] Relaying to non-hip aware servers
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.17
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/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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>
X-List-Received-Date: Tue, 27 Sep 2016 14:15:34 -0000


On 09/27/2016 10:02 AM, Miika Komu wrote:
> Hi Robert,
>
> On 09/27/2016 04:46 PM, Robert Moskowitz wrote:
>> Where did we describe connections from a mobile hip-aware host to a
>> legacy non-HIP 'stable' server.
>>
>> I thought it was HIPBONE (as it is not what HIP nat traversal is about),
>> but I am not seeing this function there.
>>
>> Basically, the Mobile host has its HIP SA with a relay that decapsulates
>> the ESP traffic onto legacy Internet.
>>
>> This can cause some nasty routing scenarios unless the HIP host can
>> treat a group of relays as multihome interfaces or the like and use the
>> best relay for any connection.  Which would drive TCP/UDP crazy though?
>>
>> I recall through the window, darkly, that we had these discussions. But
>> my search foo is weak and I am not finding them.
>
> proxy HIP:

proxy.  like I said weak search foo....

thanks

>
> https://tools.ietf.org/html/draft-melen-hip-proxy-02
> https://tools.ietf.org/html/draft-irtf-hiprg-proxies-05
>