IETF Logo Mail Archive

Re: [Dime] WG adoption call for draft-zorn-dime-rfc4005bis-01

Sebastien Decugis <sdecugis@nict.go.jp> Thu, 05 August 2010 07:52 UTC

Return-Path: <sdecugis@nict.go.jp>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A70EF3A67AC for <dime@core3.amsl.com>; Thu, 5 Aug 2010 00:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mxrFfTcqIrmi for <dime@core3.amsl.com>; Thu, 5 Aug 2010 00:51:59 -0700 (PDT)
Received: from sd-11965.dedibox.fr (sd-11965.dedibox.fr [88.191.67.190]) by core3.amsl.com (Postfix) with ESMTP id 15D183A6801 for <dime@ietf.org>; Thu, 5 Aug 2010 00:51:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sd-11965.dedibox.fr (Postfix) with ESMTP id DD65627D86; Thu, 5 Aug 2010 09:52:28 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at sd-11965.dedibox.fr
Received: from sd-11965.dedibox.fr ([127.0.0.1]) by localhost (sd-11965.dedibox.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nrujkvw5BVeJ; Thu, 5 Aug 2010 09:52:25 +0200 (CEST)
Received: from [202.249.37.5] (morbier.koganei.wide.ad.jp [202.249.37.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sd-11965.dedibox.fr (Postfix) with ESMTPSA id EB13427DD0; Thu, 5 Aug 2010 09:52:23 +0200 (CEST)
Message-ID: <4C5A6DA9.30309@nict.go.jp>
Date: Thu, 05 Aug 2010 16:52:09 +0900
From: Sebastien Decugis <sdecugis@nict.go.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1
MIME-Version: 1.0
To: Glen Zorn <gwz@net-zen.net>
References: <A0A5F8D2-62B7-40BF-A9C2-8ED231D6323E@gmail.com> <4C5A5F2D.20508@nict.go.jp> <001c01cb346e$d7f9a460$87eced20$@net>
In-Reply-To: <001c01cb346e$d7f9a460$87eced20$@net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: dime@ietf.org
Subject: Re: [Dime] WG adoption call for draft-zorn-dime-rfc4005bis-01
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 05 Aug 2010 07:52:01 -0000

 Hello again,

> Would you then consider
> http://www.ietf.org/id/draft-zorn-dime-radia-gate-01.txt to be unsuitable?
Yes. That document describes how to use Diameter as a tunneling protocol
(I don't understand the purpose of this, but anyway), it does not
address the translation of the RADIUS messages to Diameter.

> Be that as it may, however, the point is that it's very unclear whether such
> functionality is actually useful...
First of all, not being useful is a good enough rationale to revise a RFC?

Secondly, I believe that yes, this mechanism is actually useful, to help
transition to Diameter. It provides a way to interconnect several realms
where some use RADIUS while others already moved to Diameter (example:
take a consortium like EDUROAM. How would you migrate someday to
something else that RADIUS, without a translation mechanism?)

Best regards,
Sebastien.

-- 
Sebastien Decugis
Research fellow
Network Architecture Group
NICT (nict.go.jp)

v2.23.0 | Report a Bug | By Email