[radext] #186 (dynamic-discovery): Routing error

"radext issue tracker" <trac+radext@trac.tools.ietf.org> Tue, 19 August 2014 20:40 UTC

Return-Path: <trac+radext@trac.tools.ietf.org>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A38C1A6F0B for <radext@ietfa.amsl.com>; Tue, 19 Aug 2014 13:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level:
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.668] 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 kg6p6OtInWAZ for <radext@ietfa.amsl.com>; Tue, 19 Aug 2014 13:40:18 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 EF6CA1A6F04 for <radext@ietf.org>; Tue, 19 Aug 2014 13:40:17 -0700 (PDT)
Received: from localhost ([::1]:53232 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+radext@trac.tools.ietf.org>) id 1XJqCX-0006Ut-J8; Tue, 19 Aug 2014 13:40:17 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "radext issue tracker" <trac+radext@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: jouni.nospam@gmail.com
X-Trac-Project: radext
Date: Tue, 19 Aug 2014 20:40:17 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/186
Message-ID: <063.5f284cb003bf060a7627b3180720803e@trac.tools.ietf.org>
X-Trac-Ticket-ID: 186
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: jouni.nospam@gmail.com, radext@ietf.org
X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/El_Hqay9Z8bCVM7WmSGCr0d5-sc
Cc: radext@ietf.org
Subject: [radext] #186 (dynamic-discovery): Routing error
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: radext@ietf.org
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Aug 2014 20:40:19 -0000

#186: Routing error

 As a pert of the document shepherd proto write-up I read the I-D.

 In Section 1.3. it is claimed:

    o  a partially correct routing error detection (not considered for
       Diameter)

 What is considered missing in Diameter here? Diameter does detect routing
 loops without it being part of the dynamic discovery. The discovery
 mechanism in RFC6733 and 6408 does not protect against a loop in DNS query
 though (that is implementation specific).

-- 
------------------------------------+------------------------------------
 Reporter:  jouni.nospam@gmail.com  |      Owner:  jouni.nospam@gmail.com
     Type:  defect                  |     Status:  new
 Priority:  major                   |  Milestone:
Component:  dynamic-discovery       |    Version:
 Severity:  -                       |   Keywords:
------------------------------------+------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/186>
radext <http://tools.ietf.org/radext/>