Re: [addr-select-dt] Proposed default policy table

Mohacsi Janos <mohacsi@niif.hu> Mon, 12 July 2010 08:53 UTC

Return-Path: <mohacsi@niif.hu>
X-Original-To: addr-select-dt@core3.amsl.com
Delivered-To: addr-select-dt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C2283A6902 for <addr-select-dt@core3.amsl.com>; Mon, 12 Jul 2010 01:53:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.004
X-Spam-Level:
X-Spam-Status: No, score=-0.004 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
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 eAkzD4lncMaV for <addr-select-dt@core3.amsl.com>; Mon, 12 Jul 2010 01:53:41 -0700 (PDT)
Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by core3.amsl.com (Postfix) with ESMTP id 0A9023A6A6F for <addr-select-dt@ietf.org>; Mon, 12 Jul 2010 01:53:40 -0700 (PDT)
Received: from bolha.lvs.iif.hu (bolha.lvs.iif.hu [193.225.14.181]) by mail.ki.iif.hu (Postfix) with ESMTP id 2ADEC851CE; Mon, 12 Jul 2010 10:53:47 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at bolha.lvs.iif.hu
Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by bolha.lvs.iif.hu (bolha.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id 8fidmv-4Dky5; Mon, 12 Jul 2010 10:53:44 +0200 (CEST)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id 65CA2851FB; Mon, 12 Jul 2010 10:53:44 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id 5FAFD851F9; Mon, 12 Jul 2010 10:53:44 +0200 (CEST)
Date: Mon, 12 Jul 2010 10:53:44 +0200
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@mignon.ki.iif.hu
To: Aleksi Suhonen <Aleksi.Suhonen@tut.fi>
In-Reply-To: <4C3AD3AC.5050405@tut.fi>
Message-ID: <alpine.BSF.2.00.1007121041110.21959@mignon.ki.iif.hu>
References: <0f4301cb1ec0$297b4650$7c71d2f0$@com> <4C3A5931.40709@tut.fi> <6750C85E-1FE7-4C80-A4DE-C1195115FA0B@ecs.soton.ac.uk> <EMEW3|f7226135d6b882ba63bf54b974a62f41m6B8Eo03tjc|ecs.soton.ac.uk|6750C85E-1FE7-4C80-A4DE-C1195115FA0B@ecs.soton.ac.uk> <910AF3E6-1632-480B-9482-FB9572355576@nttv6.net> <4C3AD3AC.5050405@tut.fi>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: addr-select-dt@ietf.org
Subject: Re: [addr-select-dt] Proposed default policy table
X-BeenThere: addr-select-dt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPv6 Address Selection Design Team <addr-select-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/addr-select-dt>, <mailto:addr-select-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/addr-select-dt>
List-Post: <mailto:addr-select-dt@ietf.org>
List-Help: <mailto:addr-select-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/addr-select-dt>, <mailto:addr-select-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2010 08:53:42 -0000

On Mon, 12 Jul 2010, Aleksi Suhonen wrote:

> On 07/12/10 07:38, Arifumi Matsumoto wrote:
>>> I have one other topic to add which I can't remember whether I posted 
>>> about recently or not, so apologies if I'm repeating myself.
>>> 
>>> In undertaking some work recently on router-based hints for address 
>>> selection, we found that we could improve address selection behaviour for 
>>> hosts by using a new ICMP-based message to query a router or route server 
>>> for an ordered list of address pairs to use for given candidate addresses. 
>>> The issue that came up was that if the host were to cache the result, and 
>>> we chose to cache it within the RFC3484 policy tables, can we 
>>> change/augment the current syntax/format to accommodate that?
>> 
>> That approach also should have an issue of policy merge/conflict.
>> 
>> When we think about merging process, we may have to think about this
>> kind of approach, if we think it looks like some advantages in merging.
>
> The Linux Way of recent days seems to be to replace /etc/<software>.conf with 
> /etc/<software>.d/*.conf so in Linux specifically you could implement it like 
> this:
>
> /etc/gai.conf:
> 1. default rules that can be overriden
> 2. include instruction for /etc/gai.d/*.conf
> 3. system wide rules that can't be overriden
>
> And then your address selection policy update daemon(s) would update their 
> own file(s) in /etc/gai.d/ safely.
>
> I don't have a good understanding on how other operating systems have 
> implemented RFC3484 so I can't comment how universal this would be.

I think it much more complicated:
- You have default ruleset initialised by the operating system.
- You can  have host specific ruleset configured by the particular node 
configuration files - usually loaded by the startup process like 
from /etc/<software>.conf (or /etc/<software>.d/*.conf) into the kernel

- You might opt from loading something into the kernel from the previous 
cache. I don't think it is reliable. OS should send out something like 
confirmation, whether it is still valid or ICMPv6/DHCP policy table 
solicitation/request.

  - You can have a daemon process, that actually initate this policy table 
solicitation/request and process the incoming policy table and insert the 
ruleset into the kernel.


I don't believe that overriding a particular rule either from 
configuration file or any  policy table distibution method would be 
possible. Every operating system or local setup migth be different 
therefore complete table override is possible, but modifying one rule 
not....

Best Regards,
 		Janos Mohacsi


-


>
> --
> 	Aleksi Suhonen
> 	Department of Communications Engineering
> 	Tampere University of Technology
> _______________________________________________
> addr-select-dt mailing list
> addr-select-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/addr-select-dt
>