Re: [Dime] [RFC3588bis-34] - Host-IP-Address AVP

Glen Zorn <glenzorn@gmail.com> Tue, 18 September 2012 11:40 UTC

Return-Path: <glenzorn@gmail.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C70BA21E80C2 for <dime@ietfa.amsl.com>; Tue, 18 Sep 2012 04:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.083
X-Spam-Level:
X-Spam-Status: No, score=-3.083 tagged_above=-999 required=5 tests=[AWL=-0.103, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E+fJwauoPelH for <dime@ietfa.amsl.com>; Tue, 18 Sep 2012 04:40:52 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 51F2921E80A7 for <dime@ietf.org>; Tue, 18 Sep 2012 04:40:52 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so11439693obb.31 for <dime@ietf.org>; Tue, 18 Sep 2012 04:40:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=pMBYg5vn8/PHOraJfv/lom48qPwQVhmnNb4jP21BjYQ=; b=j9tuZyA/9vCvG3jFTjWHBRv5/Sl59A3uJwoir1xLN4+HV6Xy5fKcgi6gGU5h8GHeqS 3Kw1iaQ9w2RhTYoTQOf0hoBT2I+s842u4AcLOw70xMcYaoofMAnBKchqUP09QfFr9ZbK wiTH79FSFgHBQKLnUjwYgcW4nyhQ6BOAxUvvna2OKqS7QU7rkS5HWt4INqyF2L5yF3yG SklbvRLpGPGP+08ArtbOeoMDC4KsKCotfKlXLBqQJ6CjMs/rVeCfn/mwo8kbmjw4VitE oTEyCKk6BQr4xevfUZErs1x9caIhWoO51NXynIiKUjR+c8j9UVVK4WbNrZfcl4AuVn+F NkOw==
Received: by 10.182.111.74 with SMTP id ig10mr7055330obb.14.1347968451947; Tue, 18 Sep 2012 04:40:51 -0700 (PDT)
Received: from [192.168.0.102] (ppp-58-11-235-161.revip2.asianet.co.th. [58.11.235.161]) by mx.google.com with ESMTPS id qd7sm14135920obc.5.2012.09.18.04.40.49 (version=SSLv3 cipher=OTHER); Tue, 18 Sep 2012 04:40:51 -0700 (PDT)
Message-ID: <50585DBF.20502@gmail.com>
Date: Tue, 18 Sep 2012 18:40:47 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120830 Thunderbird/15.0
MIME-Version: 1.0
To: jouni korhonen <jouni.nospam@gmail.com>
References: <5F42DFF905CBA544A7BBB0909003E1A3148F14F7C6@FRMRSSXCHMBSC1.dc-m.alcatel-lucent.com> <50570410.9000708@gmail.com> <5F42DFF905CBA544A7BBB0909003E1A3148F14F987@FRMRSSXCHMBSC1.dc-m.alcatel-lucent.com> <E4A11012-4F89-455F-AC98-57F188456D91@gmail.com>
In-Reply-To: <E4A11012-4F89-455F-AC98-57F188456D91@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] [RFC3588bis-34] - Host-IP-Address AVP
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Sep 2012 11:40:52 -0000

On 09/18/2012 03:06 AM, jouni korhonen wrote:
> Hi,
>
> Few quick comments inline.
>
> On Sep 17, 2012, at 3:09 PM, VITON HORCAJO, Pedro (Pedro) wrote:
>
>> Glen,
>>
>> Thanks for answering.
>> Maybe my original mail was too long, and I  might have not have been clear enough.
>>
>> Let me rephase my questions, in a shorter way:
>>
>> 1.- The current text for Host-IP-Address AVP indicates the value to send when transporting over SCTP.
>> But which value should be sent when transporting over TCP?
> RFC3588bis says:
>
>     The Host-IP-Address AVP (AVP Code 257) is of type Address and is used
>     to inform a Diameter peer of the sender's IP address.
>
> This part is not SCTP specific. So at minimum you include the address the
> very TCP connection comes from. Repetition but acceptable. Also, Diameter
> host's DiameterIdentity may resolve to one or more IP addresses but not
> necessarily to all of those. It is a DNS provisioning matter. The Diameter
> node would know all its addresses it can use, so those additional addresses
> would be included.

This doesn't really make sense to me: I was under the impression that a 
TCP connection was between two unique addresses.  Yes, a box might 
___have_ a whole bunch of addresses it _could_ use, but that seems 
irrelevant in the case of TCP (but not SCTP).

>
>> 2.- What should a Diameter implementation do when receiving the Host-IP-Address AVP?
> In case of TCP.. that is more like FYI (unless someone plans to hack MPTCP into
> Diameter some day). Or in case of transport failure, the peer can select other
> IP for retrying the transport connection.

Surely it makes more sense just to start over, doesn't it?  That 
behavior also seems to be prescribed by the state machine...

...