Re: [Dime] Questions on 3588bis election text

Glen Zorn <glenzorn@gmail.com> Sun, 07 October 2012 03:13 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 51B3E21F83EF for <dime@ietfa.amsl.com>; Sat, 6 Oct 2012 20:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level:
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, 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 5qpsfequOcBQ for <dime@ietfa.amsl.com>; Sat, 6 Oct 2012 20:13:24 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF3921F8484 for <dime@ietf.org>; Sat, 6 Oct 2012 20:13:24 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so971424dan.31 for <dime@ietf.org>; Sat, 06 Oct 2012 20:13:24 -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=ZL1dzDEqnH2v+lhpoF7CFHDsEEfVG0c+BD4DBhSWmB0=; b=MGKX2y9RGkChm4x7ROMpWxiZc688k0BNf075tzL1xCoG6rWziJYgF/m7yAEAujIsc+ vcA+vcQouSMfIpypxb5KbI9J+fyzfjt2QOVMFneHl9tl7UxcYbeRxKGfsDV+SqmSZtdd 3kZm5JCee9lH+bK6kHu0cOoqC/b0Btg70y9O2rx6y4N5G3nntqzi2e+LDYYcph2OtvMh YTfzp0CHQtvtOUZjfntdvS4uYNhoAAHgYuCuJUoB5/W+s+8snEt0vJSgq5WWLXv9GZmS dAquDta14ynIzxCr0CUMXrayZCgO8wCt6TLwX4fVEeWl+ed2gOVhq/CYrYMVJ0ztsB+E /0Lg==
Received: by 10.68.235.71 with SMTP id uk7mr42824072pbc.10.1349579604217; Sat, 06 Oct 2012 20:13:24 -0700 (PDT)
Received: from [192.168.0.102] (ppp-115-87-90-243.revip4.asianet.co.th. [115.87.90.243]) by mx.google.com with ESMTPS id jw14sm8489599pbb.36.2012.10.06.20.13.22 (version=SSLv3 cipher=OTHER); Sat, 06 Oct 2012 20:13:23 -0700 (PDT)
Message-ID: <5070F350.1010000@gmail.com>
Date: Sun, 07 Oct 2012 10:13:20 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120914 Thunderbird/15.0.1
MIME-Version: 1.0
To: Andrew Booth <abooth@pt.com>
References: <OFE769E517.39026F3F-ON85257A8D.00656695-85257A8D.006566A0@pt.com>
In-Reply-To: <OFE769E517.39026F3F-ON85257A8D.00656695-85257A8D.006566A0@pt.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: dime@ietf.org
Subject: Re: [Dime] Questions on 3588bis election text
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: Sun, 07 Oct 2012 03:13:25 -0000

On 10/05/2012 01:27 AM, Andrew Booth wrote:
> Hi,
>
> It seems to me that the election resolution text in section 5.6.4 of 
> draft-ietf-dime-rfc3588bis-34.txt is not backward compatible with 
> RFC3588, is this correct?

No.

> My understanding is that IF a diameter node that implements 3588 is 
> communicating with one that implements 3588bis AND at least one of the 
> Diameter IDs contains capital letters in the wrong places, then the 
> two nodes could have different views on which node wins the election, 
> possibly resulting in 0 or 2 connections between the nodes.
>
> Could this lead to reconnect loops where both sides reconnect after Tc 
> and then both continue to close the connection?
>
> Am I misunderstanding something?  Or is this not an issue for other 
> reasons?

RFC 1035 says "Note that while upper and lower case letters are allowed 
in domain
names, no significance is attached to the case.  That is, two names with 
the same spelling but different case are to be treated as if 
identical."  Since the DiameterIdentity type was defined in RFC 3588 as  
FQDN, case-sensitivity wasn't an issue; the revision is just more 
specific about that than the original.

>
> Thanks for any info,
> Andrew
>
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime