Re: [AAA-DOCTORS] Functionality in draft-ietf-dime-mip6-integrated vs. draft-ietf-mip6-radius

"jouni korhonen" <jouni.nospam@gmail.com> Tue, 02 December 2008 12:14 UTC

Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50FBA3A6888; Tue, 2 Dec 2008 04:14:52 -0800 (PST)
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC60C3A6888 for <aaa-doctors@core3.amsl.com>; Tue, 2 Dec 2008 04:14:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 1khIFBiKNxlu for <aaa-doctors@core3.amsl.com>; Tue, 2 Dec 2008 04:14:51 -0800 (PST)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by core3.amsl.com (Postfix) with ESMTP id 557AA3A67A1 for <aaa-doctors@ietf.org>; Tue, 2 Dec 2008 04:14:50 -0800 (PST)
Received: by ey-out-2122.google.com with SMTP id 9so1244442eyd.31 for <aaa-doctors@ietf.org>; Tue, 02 Dec 2008 04:14:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=ZY/hvQnyuuJl5NJ6oq4vfHO8iPiP2gOOAb/HVp4bA6g=; b=YzLhtXbV5LvCr2pJzzbPLMtpkhA/yUdY899iXyOBbb6IzaSdjiVeKJkYNFPgKQMu+S a/G+AcqObzHGb7z5ltA6sN5XdNiDUYNTmLAwMVbSUdzS/X0XufYur/Jtq2j2UcxhCcUu ARNUK8fdAwzJyPjbITbXM7ZbV2XMeh+TkobtM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=QcOT3cXtV8PuDg2gRptCuARBV2cZC7lp5YJ3jeyvq11vRK9xN2yU7TVgsiNgz5PZDQ Ay0GBaa/ULo8bCxOfj6qY5U1rep1pARcaPFmyS704bn3r4OCDANdVInJQ5gqQ6pwLCQB dPUnQ0Ncuv0qDQnYYyTZec6Sr1ptPkmUHcuxw=
Received: by 10.210.137.14 with SMTP id k14mr9717314ebd.175.1228220084561; Tue, 02 Dec 2008 04:14:44 -0800 (PST)
Received: by 10.210.111.15 with HTTP; Tue, 2 Dec 2008 04:14:44 -0800 (PST)
Message-ID: <3fe59bfe0812020414r30833cf1wfbb8f753bd26fab@mail.gmail.com>
Date: Tue, 02 Dec 2008 14:14:44 +0200
From: jouni korhonen <jouni.nospam@gmail.com>
To: Pasi.Eronen@nokia.com
In-Reply-To: <1696498986EFEC4D9153717DA325CB72027062CF@vaebe104.NOE.Nokia.com>
MIME-Version: 1.0
References: <1696498986EFEC4D9153717DA325CB72027062CF@vaebe104.NOE.Nokia.com>
Cc: kchowdhury@starentnetworks.com, aaa-doctors@ietf.org, jouni.korhonen@nsn.com, julien.bournelle@orange-ftgroup.com, charliep@wichorus.com, marcelo@it.uc3m.es, avi@bridgewatersystems.com, julien.laganier.ietf@googlemail.com
Subject: Re: [AAA-DOCTORS] Functionality in draft-ietf-dime-mip6-integrated vs. draft-ietf-mip6-radius
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0315345912=="
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

On Tue, Dec 2, 2008 at 1:39 PM, <Pasi.Eronen@nokia.com> wrote:

>
> Jouni, Avi, and others,
>

<major-snip>

(BTW -- all this is about the "integrated scenario"; split scenario
> is a topic for a different day...)
>
> If these differences in functionality/semantics are intentional, and
> there's no desire to allow lossless translation in either direction
> (even assuming new code in the RADIUS/Diameter translation agent),
> then using identical AVP formats/numbers isn't that big deal.
>
> So, I'm wondering whether these differences are intentional, or perhaps
> artifacts of not-totally-synchronized work in two WGs?


Hmm.. I am not co-authoring mip6-radius, so maybe other folks know details
on above better than me. I have worked only on the dime-mip6-integrated
based
on my view of stuff, integrated-dhc and comments received from outside IETF.

Cheers,
      Jouni


>
> Best regards,
> Pasi
>
_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors