Re: [RAM] New LISP draft available ...

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 25 July 2007 19:15 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDmL1-0003JK-MH; Wed, 25 Jul 2007 15:15:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDmL0-0003Io-Ss for ram@iab.org; Wed, 25 Jul 2007 15:15:59 -0400
Received: from wx-out-0506.google.com ([66.249.82.231]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDmL0-0002GO-L0 for ram@iab.org; Wed, 25 Jul 2007 15:15:58 -0400
Received: by wx-out-0506.google.com with SMTP id i28so281443wxd for <ram@iab.org>; Wed, 25 Jul 2007 12:15:58 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=btkLEze7Nk2aTO6CgRMGiLVNIxyOQo+laWu7WOuIm16QxAexT3dDOSHCwcESc4KNyjRE3ea1M1w98PnDvEU945coKI1KebAqQ+aFdKgy167DEaxnLu7HVcuJQdXCn7gwr+xsL3HAaTMA+3hFyUOumxl43Gci90vIgF1pKxhh05k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=YR/Su87w/1b9e6DQAMbcQ4Nurr/JfbDNVjA1SQQVzypskHYkZrWIVODDT8pek+e5DjfkWUl+XtldEmgFbPMm0luayw/Gl6kXF4u2mHjXY9RmopgQbQe8kVVXN3COYM7Mqr34VQHRbsb+3JhIcv4QqOQVSje5rWPrHgz8lScG/5Y=
Received: by 10.90.118.8 with SMTP id q8mr1016437agc.1185390958291; Wed, 25 Jul 2007 12:15:58 -0700 (PDT)
Received: from ?130.129.83.253? ( [130.129.83.253]) by mx.google.com with ESMTPS id 43sm1151116wri.2007.07.25.12.15.57 (version=SSLv3 cipher=RC4-MD5); Wed, 25 Jul 2007 12:15:57 -0700 (PDT)
Message-ID: <46A7A16D.7030803@gmail.com>
Date: Wed, 25 Jul 2007 21:15:57 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Dino Farinacci <dino@cisco.com>
Subject: Re: [RAM] New LISP draft available ...
References: <1DFBAD55-CA28-4D44-9F96-218F5F281047@cisco.com> <46A3CEE9.5080008@gmail.com> <FD40F969-AACC-4182-87F0-109C5556ACD1@cisco.com> <46A78A95.8040500@gmail.com> <10CE716C-FB80-4D54-88AA-FB8262E09076@cisco.com>
In-Reply-To: <10CE716C-FB80-4D54-88AA-FB8262E09076@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: RAM Mailing List <ram@iab.org>
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

All OK except:

>>>> That rule doesn't seem viable or enforcable. The client side may
>>>> simply not desire to take orders on how to load share, and that
>>>> could be a business issue (if the client has ISP preferences
>>>> for example). I think it needs to be "Client SHOULD only use the 
>>>> subset list
>>>>       according to the weighting assigned by the server-side."
>>> Well, we do want client spec-compliant implications. I realize there 
>>> are malicious systems out there but you have to document what the 
>>> intended rules are.
>>
>> Maybe I'm disagreeing with that rule then. Is there a *technical* 
>> argument
>> for why the server side must determine the weights?
> 
> There is a requirement for site-based ETRs to allow to control the data 
> flow to each of the site's locators. This is precisely controlling 
> ingress traffic flow.

Sorry to harp on but why is that a *technical* requirement?

(To be clear, if it's a *business* requirement I still think it
should be a SHOULD.)

     Brian

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram