Re: [Dime] [AAA-DOCTORS] FW: I-D Action:draft-zorn-dime-rfc4005bis-01.txt
"Dave Nelson" <d.b.nelson@comcast.net> Tue, 25 May 2010 11:20 UTC
Return-Path: <d.b.nelson@comcast.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 49C433A6AC0 for <dime@core3.amsl.com>; Tue, 25 May 2010 04:20:40 -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 1HulmX3nekkL for <dime@core3.amsl.com>; Tue, 25 May 2010 04:20:33 -0700 (PDT)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by core3.amsl.com (Postfix) with ESMTP id 020333A6AFA for <dime@ietf.org>; Tue, 25 May 2010 04:20:29 -0700 (PDT)
Received: from omta08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by qmta01.emeryville.ca.mail.comcast.net with comcast id Mmwh1e0020FhH24A1nLPZh; Tue, 25 May 2010 11:20:23 +0000
Received: from NEWTON603 ([24.218.90.45]) by omta08.emeryville.ca.mail.comcast.net with comcast id MnLM1e0050yip6Y8UnLNZ6; Tue, 25 May 2010 11:20:23 +0000
From: Dave Nelson <d.b.nelson@comcast.net>
To: 'Glen Zorn' <gwz@net-zen.net>, dime@ietf.org
References: <003a01cafacd$a5061780$ef124680$@net>
Date: Tue, 25 May 2010 07:20:35 -0400
Message-ID: <AAAA39527F0443C99BD73157F4AA5AF7@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <003a01cafacd$a5061780$ef124680$@net>
thread-index: Acr6yQARBiQDGd5qTZOGEzMy5EJORwAAfQngAEwMWiA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
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: Tue, 25 May 2010 11:20:40 -0000
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.