[Dime] Association between origin-host and source IP address

Ajinkya Joshi <ajoshi@definitionnetworks.com> Fri, 08 September 2017 14:17 UTC

Return-Path: <ajoshi@definitionnetworks.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 B316813202D for <dime@ietfa.amsl.com>; Fri, 8 Sep 2017 07:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=definitionnetworks-com.20150623.gappssmtp.com
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 sGGTD19O0knZ for <dime@ietfa.amsl.com>; Fri, 8 Sep 2017 07:17:33 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E8D7132153 for <dime@ietf.org>; Fri, 8 Sep 2017 07:17:33 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id x190so15393975oix.3 for <dime@ietf.org>; Fri, 08 Sep 2017 07:17:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=definitionnetworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=wERersuAawdh2/swy726k+kMv1by5NkrZMm2IXBXy5U=; b=nQNOiCGoYaVDC+LV8nLZfKz30QGfu8ohtuk0rgwvT28rngPxj0qbQCFF/dFHhYYmXY 3XSWaICENO8wmpcosh/cPBxCE05ERvCyw2ID5XU7+h35hJrTUsp+wjJWfuGFowvboJVJ xuNM3KrqH+F1UMmBR9Yq+y6QUQuN2nGmOpQDvmNfxotQiy1I0WKBwpsy00DHYFUjbzS6 3Lwtem7u/4Yv3Iu6jSpMZw7PXuHRnC7BBF+gxJoS6f1F8p3XrPR8CZkUQOJZRdpKuk73 x02szhMgz7zCP4cxO9R7JIUMY2tJ0DwuHdLzuqVxX4VXs4+DPFJGhJdoRKhzPLIvHBZf FXnA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wERersuAawdh2/swy726k+kMv1by5NkrZMm2IXBXy5U=; b=Uri5vOpQgqtIIkGh5Yv4kHMUUtqslELZZrZ5jcpqJmRc1CSBb/qrO76VkX9TLrngSw 62ZM+xbhhoFvkg6aAYUCRnkSJFjSgydfjguMeL7fEzBRIC6L14JN5nI+A4NPiqOxZh12 me50atInQwXaD4v76cpZJSLYzMxI5oKk3xB5hZDAtyQxblpoGjbKYGVCCUvDEDryvSIm S9o1M3hrLKovmRGJ1JG2MVHnt6AlD+BFSKKgYzPq9JYrG4ySsZ+L0QyH0wzkgdkZFzlo zzC1UIsoufx9nLGLd+udWziLGgTBZc4rLm6U3HTejruWhOybuenYkjxyBDqpucTi+gLe A6Uw==
X-Gm-Message-State: AHPjjUgympUm9svRj3Anc8Ljgpjtb3XGOaQI7UwNjO6NrnkT1STzATcK XEbNoMTArjjmIbj8A8nl8hUDLTt8yLAx
X-Google-Smtp-Source: AOwi7QDgE2KZkwafBvPUpbiDSGjrHuqfN0PqPImndo4VKloQKcQJGk4MDee3Om0WHLpwwJ+V49KQCovDPpyBqq6fjSY=
X-Received: by 10.202.77.140 with SMTP id a134mr2914118oib.155.1504880252681; Fri, 08 Sep 2017 07:17:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.38.157 with HTTP; Fri, 8 Sep 2017 07:17:32 -0700 (PDT)
From: Ajinkya Joshi <ajoshi@definitionnetworks.com>
Date: Fri, 08 Sep 2017 19:47:32 +0530
Message-ID: <CAFUT_s33RDETqXGsObCWRHAjDpnnniVkKsbwHjCCwFKJe6k2SA@mail.gmail.com>
To: dime@ietf.org
Content-Type: multipart/alternative; boundary="001a11c17daae416f60558ae3ca1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/Zm7gyNpKZQpxpv9dWc5BrSUGAZ0>
Subject: [Dime] Association between origin-host and source IP address
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 08 Sep 2017 14:17:34 -0000

Hello,

It is clear from the RFC that, each diameter implementation maintains a
peer table, which is keyed on origin-host of the peer.
But, it's not clear that on receiving incoming diameter request (non
capability exchange), is diameter node suppose to match source IP address
of incoming request with the source IP address of original transport
association between these nodes?
e.g. Consider that there two transport connection established between A1
<-> B1 and A2 <-> B1, Where A1,A2, and B1 are diameter hosts. Suppose, A2
sends a diameter request to B1, with origin-host as "A1", is B1 suppose to
reject such requests?

-- 
Regards,
Ajinkya Joshi