Re: [MEXT] Prefix delegation & Diameter Interaction

"T.J. Kniveton" <tj@kniveton.com> Wed, 28 November 2007 00:37 UTC

Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxAvg-0008Rw-6H; Tue, 27 Nov 2007 19:37:28 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxAve-0008QY-Cw for mext@ietf.org; Tue, 27 Nov 2007 19:37:26 -0500
Received: from deimos.multihop.net ([74.0.36.190] helo=multihop.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IxAvZ-0001t5-Fw for mext@ietf.org; Tue, 27 Nov 2007 19:37:22 -0500
Received: by deimos.multihop.net (Postfix, from userid 1013) id 9BA40A05F26; Tue, 27 Nov 2007 16:37:20 -0800 (PST)
X-Spam-Score: -4.4
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on deimos.multihop.net
X-Spam-Level:
X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3
Received: from [192.168.4.25] (ibmx31.tehama.multihop.net [192.168.4.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by deimos.multihop.net (Postfix) with ESMTP id 8039DA05086; Tue, 27 Nov 2007 16:37:15 -0800 (PST)
Message-ID: <474CB83B.1020802@kniveton.com>
Date: Tue, 27 Nov 2007 16:37:15 -0800
From: "T.J. Kniveton" <tj@kniveton.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [MEXT] Prefix delegation & Diameter Interaction
References: <0MKp8S-1IwdRx2OQq-0008Gc@mrelay.perfora.net> <474B12F7.8000700@azairenet.com> <474B2270.8080405@gmx.net> <474CA7BB.9000007@azairenet.com>
In-Reply-To: <474CA7BB.9000007@azairenet.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, mext@ietf.org
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

FYI, if it helps in your search.. I have all of the MIP, MIP6, MIP4, 
NEMO, MIPSHOP,.. working group messages archived on my email server for 
a number of years. It also has anonymous IMAP and a webmail interface so 
you can search using your mail client (IMAP/POP) or the web.

If you want to use that just let me know and I'll give you instructions. 
It can make searching significantly faster.

TJ

Vijay Devarapalli wrote:
> Hi Hannes,
>
> Here are some pointers to previous discussions. Took me some time
> to find this. IETF archives are not designed for searching.
>
> - http://www1.ietf.org/mail-archive/web/mip6/current/msg06023.html
>
> This thread was about DHCP should be used to assign home address
> from the NAS (access router). RADIUS/Diameter is used to deliver
> the home address from the AAA to the NAS.
>
> - http://www1.ietf.org/mail-archive/web/mip6/current/msg06554.html
>
> This thread talks about AAA or the HA assigning a home address.
>
> - http://www1.ietf.org/mail-archive/web/netlmm/current/msg02515.html
>
> This thread was on the NETLMM mailing list. It was about AAA managing
> prefixes for PMIPv6 instead of the LMA and the AAA delivering the
> prefixes to the MAG.
>
> There was quite bit of discussion on this during the Prague meeting.
> Mostly hallway discussions. Don't have pointers to that. This was
> just after the WG last call for draft-ietf-mip6-hiopt.
>
> There might have been more, but can't spend any more time on this.
> Sorry. Anyway, AFAIK, we have always concluded that the home agent
> or some other entity on the home link (DHCP server) manages the
> home addresses and the home prefixes.
>
> George, Sri, you guys had also sent emails asking for pointers.
> Patience please. It takes quite a bit of time to search through
> the archives.
>
> Vijay
>
> Hannes Tschofenig wrote:
>> Hi Vijay,
>>
>> maybe you can provide some pointers to past discussions and 
>> conclusions. You cannot expect that everyone follows all mailing 
>> lists and now this work is being proposed for DIME.
>>
>> Ciao
>> Hannes
>>
>> PS: I once had comments for a QoS document and I got the following 
>> response "I don't have time to give you a tutorial on this QoS issue. 
>> We discussed this at length in face-to-face meeting at the IETF XYZ 
>> meeting."
>>
>> The document got delayed for more than a year when the same questions 
>> showed  up later again....
>>
>> Vijay Devarapalli wrote:
>>> Alper Yegin wrote:
>>>> Vijay,
>>>>
>>>> Can you explain why you do not recommend AAA-assignment of prefixes?
>>>
>>> We have been through this many times on the MIP6 mailing list.
>>> The earlier discussions were based on AAA assigning the home
>>> address. We have always concluded otherwise. I don't see much
>>> different between AAA managing home prefixes and home addresses.
>>> I am not planning to rehash those discussions.
>>>
>>> Vijay
>>>
>>>
>>>>
>>>> Alper
>>>>
>>>>> -----Original Message-----
>>>>> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
>>>>> Sent: Sunday, November 25, 2007 7:17 PM
>>>>> To: Hannes Tschofenig
>>>>> Cc: mext@ietf.org
>>>>> Subject: Re: [MEXT] Prefix delegation & Diameter Interaction
>>>>>
>>>>> Well, this document seems to assume (or make a case) that the AAA
>>>>> manages the prefixes. We *do not* recommend that model. It is
>>>>> typically either the home agent or a DHCP server co-located with
>>>>> the home agent that manages the prefixes.
>>>>>
>>>>> Vijay
>>>>>
>>>>> Hannes Tschofenig wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> in the DIME working group we have a document that provides the 
>>>>>> Diameter
>>>>>> interworking for prefix delegation.
>>>>>> Here is the document:
>>>>>> http://tools.ietf.org/wg/dime/draft-sarikaya-dime-prefix-delegation-ps- 
>>>>>>
>>>>> 00.txt
>>>>>>
>>>>>> It would help us in DIME if members of this group could give us some
>>>>>> feedback.
>>>>>>
>>>>>> Ciao
>>>>>> Hannes
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> MEXT mailing list
>>>>>> MEXT@ietf.org
>>>>>> https://www1.ietf.org/mailman/listinfo/mext
>>>>>
>>>>> _______________________________________________
>>>>> MEXT mailing list
>>>>> MEXT@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/mext
>>>>
>>
>
>
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www1.ietf.org/mailman/listinfo/mext
>


_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext