Re: [Dime] [AAA-DOCTORS] FW: I-D Action:draft-zorn-dime-rfc4005bis-01.txt
"Glen Zorn" <gwz@net-zen.net> Wed, 26 May 2010 06:25 UTC
Return-Path: <gwz@net-zen.net>
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 1B1563A6980 for <dime@core3.amsl.com>; Tue, 25 May 2010 23:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 j+In6MnLpTb9 for <dime@core3.amsl.com>; Tue, 25 May 2010 23:25:06 -0700 (PDT)
Received: from smtpauth19.prod.mesa1.secureserver.net (smtpauth19.prod.mesa1.secureserver.net [64.202.165.30]) by core3.amsl.com (Postfix) with SMTP id 1ADEC3A6A8D for <dime@ietf.org>; Tue, 25 May 2010 23:23:28 -0700 (PDT)
Received: (qmail 20086 invoked from network); 26 May 2010 06:23:18 -0000
Received: from unknown (115.67.228.30) by smtpauth19.prod.mesa1.secureserver.net (64.202.165.30) with ESMTP; 26 May 2010 06:23:16 -0000
From: Glen Zorn <gwz@net-zen.net>
To: 'Dave Nelson' <d.b.nelson@comcast.net>, dime@ietf.org
References: <003a01cafacd$a5061780$ef124680$@net> <AAAA39527F0443C99BD73157F4AA5AF7@NEWTON603>
In-Reply-To: <AAAA39527F0443C99BD73157F4AA5AF7@NEWTON603>
Date: Wed, 26 May 2010 13:22:57 +0700
Organization: Network Zen
Message-ID: <002601cafc9b$e70a9000$b51fb000$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acr6yQARBiQDGd5qTZOGEzMy5EJORwAAfQngAEwMWiAAJ40ssA==
Content-Language: en-us
Cc: aaa-doctors@ietf.org
Subject: Re: [Dime] [AAA-DOCTORS] FW: I-D Action:draft-zorn-dime-rfc4005bis-01.txt
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: Wed, 26 May 2010 06:25:07 -0000
Dave Nelson [mailto:d.b.nelson@comcast.net] writes: > Glen Zorn writes... > > > A topic of discussion during the last couple of AAA Doctors meetings > > has been what to do about RFC 4005 in general and RADIUS-Diameter > > interoperability in particular. In Anaheim we decided to just try > > removing the RADIUS->Diameter translation stuff from 4005 (since it > > was unclear that it had ever actually been deployed) ... > > I don't personally know that it was ever implemented; I've never been > involved with a Diameter implementation. > > One question that comes to mind is what we ought to do about the RADIUS > RFCs > that include a Diameter Compatibility section, based on the translation > concepts that you are proposing to deprecate --- err, remove, actually? > Technically, I suppose that rfc4005bis would need to Update those RFCs, > indicating that the Diameter Compatibility section is to be ignored. > That > seems cumbersome, but I don't see any other way to formally tie up all > those > loose ends. If & when the draft becomes an RFC, it might be easier (& less confusing) to publish very short notes updating the relevant RADIUS RFCs. > >