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

jouni korhonen <jouni.nospam@gmail.com> Tue, 18 September 2012 12:07 UTC

Return-Path: <jouni.nospam@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 961A221F8629 for <dime@ietfa.amsl.com>; Tue, 18 Sep 2012 05:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 iNe5hPlyAo8j for <dime@ietfa.amsl.com>; Tue, 18 Sep 2012 05:07:01 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id B525A21F876D for <dime@ietf.org>; Tue, 18 Sep 2012 05:07:00 -0700 (PDT)
Received: by bkty12 with SMTP id y12so2965292bkt.31 for <dime@ietf.org>; Tue, 18 Sep 2012 05:06:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=6ETBfWnAAZLbh9GLlh2tjayFxjysU624zW1oQP4MiEk=; b=YDps8RZr7Idb/d2+FHM1bfLUymbuJ2DyZJqInj+Cw0holNGl/UmclB20B+frzkpcBL kma+FcmIEtKbgVdENkoJX6Fla27S5gA35yYTR2xMsML66+Ft8CUToRA1+2LvpQNMAO9C QvZeuiKoR64ZNcT8x39URDtJJQooYoxesK3VOsEBPihltm6zW7mci6NUw59l87eWnwey 95q29IRIGkuqjh/n8c6DOcqxhnDATqYVerDCFtpgC6vancoRyb/RJNtpON4of+PMUwav SrPnzgRg2WgSZ5qRIwbn9l3m7EJIyQaACtjdPy5i/AwRr1Z+wAF5pU3NFCnDJsGMbHAw TYPw==
Received: by 10.204.152.216 with SMTP id h24mr5614938bkw.42.1347970019784; Tue, 18 Sep 2012 05:06:59 -0700 (PDT)
Received: from ?IPv6:2001:6e8:2100:100:223:32ff:fec9:7938? ([2001:6e8:2100:100:223:32ff:fec9:7938]) by mx.google.com with ESMTPS id t23sm7657708bks.4.2012.09.18.05.06.44 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Sep 2012 05:06:46 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <50585DBF.20502@gmail.com>
Date: Tue, 18 Sep 2012 15:06:42 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <593C8CD1-DAAC-4E39-BE6F-0FA754C706B1@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> <50585DBF.20502@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
X-Mailer: Apple Mail (2.1084)
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 12:07:01 -0000

On Sep 18, 2012, at 2:40 PM, Glen Zorn wrote:
>>> 
>>> 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).

Sure TCP is between just two IPs. I never claimed otherwise. What I mean
that say a Diameter node has IP1 to IP5. Only IP1 has a A/AAAA record or
given out to other parties for static configuration. During the CER/CEA
(and the TCP connection established to IP1) it tell in CEA that
"I btw also have IP2 to IP5". A clever implementation can make use of
this e.g. for the transport failure case I described.

- Jouni