Re: [Dime] [dime] #39: Definition of Diameter Routing

Steve Donovan <srdonovan@usdonovans.com> Mon, 10 February 2014 16:39 UTC

Return-Path: <srdonovan@usdonovans.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D94B71A0889 for <dime@ietfa.amsl.com>; Mon, 10 Feb 2014 08:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 ODQTPloWK4_4 for <dime@ietfa.amsl.com>; Mon, 10 Feb 2014 08:39:15 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [66.117.0.129]) by ietfa.amsl.com (Postfix) with ESMTP id 429E71A0885 for <dime@ietf.org>; Mon, 10 Feb 2014 08:39:15 -0800 (PST)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:57630 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1WCtrx-0005t1-3H; Mon, 10 Feb 2014 08:38:07 -0800
Message-ID: <52F900AF.6020201@usdonovans.com>
Date: Mon, 10 Feb 2014 10:39:11 -0600
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dime@ietf.org, draft-docdt-dime-ovli@tools.ietf.org, ben@nostrum.com
References: <057.f065e75bab4329d8222a3e0f41765194@trac.tools.ietf.org>
In-Reply-To: <057.f065e75bab4329d8222a3e0f41765194@trac.tools.ietf.org>
Content-Type: multipart/alternative; boundary="------------090304080400090909040708"
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srdonovan@usdonovans.com
Subject: Re: [Dime] [dime] #39: Definition of Diameter Routing
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 10 Feb 2014 16:39:17 -0000

I agree with Ben, I don't see the need to include this definition.

Steve

On 2/7/14 2:41 PM, dime issue tracker wrote:
> #39: Definition of Diameter Routing
>
>  Do we need this definition? Diameter routing should be fully defined by
>  the base specification.
>
>  But if we do, I think the phrase "non-adjacent nodes" in the first
>  sentence is misleading. Destination-Realm is also used to route between
>  adjacent nodes, at least until you reach the node responsible for the
>  ream+application. We should also include Application-Id.
>