Re: [lisp] draft-ietf-lisp-rfc6833bis-14 8.4.1 Anycast Map-Resolver Operation

Dino Farinacci <farinacci@gmail.com> Sun, 16 September 2018 23:30 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF01F126BED for <lisp@ietfa.amsl.com>; Sun, 16 Sep 2018 16:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eN8i-GqwIaWx for <lisp@ietfa.amsl.com>; Sun, 16 Sep 2018 16:30:39 -0700 (PDT)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9563C130DFD for <lisp@ietf.org>; Sun, 16 Sep 2018 16:30:39 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id s13-v6so6664241pfi.7 for <lisp@ietf.org>; Sun, 16 Sep 2018 16:30:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2ILFAiQETtUHIfpRExxilAkx3x/XODDZ5BkdPr2JG9I=; b=toANHr3bKjHutcE390sDMBcHlOHZhBW+ka/d4kWPSzIqkFZn0R7Z0s7VXNTVzgB0gz SpxLJ6P7Cksan2+UPfQ8SMqKEUBWyD0HFvzsA92bIWODyCsE3gWCidcTmkY8Wjy1dXdz /ppg8aGUlz+qwQ5TRxKSW7Xqmk7DWTyBJIVAdKNKyRTdG1JfaOzxlagTv3BQegxOkbuF d6LXHgIefAI8PUx+C1QH92WqfBf0uivVySdR76Dd780tEk/QYDuYgpr112Ke7duiUNPZ EnyNYlp0vhXdNxUAsIAko6jjEb1iqlNBg1kngKSQ/lEzcMu7gYhKK8A39LN5V/AI6np7 DupA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2ILFAiQETtUHIfpRExxilAkx3x/XODDZ5BkdPr2JG9I=; b=Gn+QoKTQxmI6EiUY2Cou72JASLmmWpb3S8RGAjeHgD9qdRhhZXckRzHFnyaQs6go7L TlhiPJsqSPZRnP3mBAiioEfUy1juQZRojJfntGtuEZywsxASlrGXPX/OliIj76GVBbnP 5ul//f4OfLZHpDbuvskVkqAppjHYp64pX5PIPgr9rSvD0pSRqq6nx6V6BIoq5X8qtOiv aA6HQhcjIdgmcpMfL3x5uffV+n81/OqyYPIYZ4C1R7W/urULNWbKiQ6MdUXGyXZz1UqT fUSHBJnl2IqSS4u3q38BgngNfDwQELhKadG/pVfbZTqRZWrcqby+Qr+scF6GZarlGYYp 2IqQ==
X-Gm-Message-State: APzg51AXiz6fiYwDDkMxvT2NgxLRejhtKDPH00P69NG47U50woqXC+iw rRhrVGEBkAOJO8tIRz/2QsSitC6H
X-Google-Smtp-Source: ANB0Vdb6TO615n46MKG+vsa1G2byOnDeYXqO2EiBpL2aPhzKvoP145jo5kt9Jow0dKnjOq5bhM/cYw==
X-Received: by 2002:a63:9619:: with SMTP id c25-v6mr21416752pge.23.1537140638940; Sun, 16 Sep 2018 16:30:38 -0700 (PDT)
Received: from ?IPv6:2603:3024:151c:55f0:2c93:666e:6b5d:9ef5? ([2603:3024:151c:55f0:2c93:666e:6b5d:9ef5]) by smtp.gmail.com with ESMTPSA id k64-v6sm19293772pfg.141.2018.09.16.16.30.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Sep 2018 16:30:38 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <3DDE70BC-D951-4110-B7F8-1C45BFC7CA0C@cisco.com>
Date: Sun, 16 Sep 2018 16:30:37 -0700
Cc: "Rene 'Renne' Bartsch, B.Sc. Informatics" <ietf=40bartschnet.de@dmarc.ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, Dino Farinacci <farinacci@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E22595A-D702-4826-9E6F-A005A65A45DD@gmail.com>
References: <d50da9ac-82f7-5aa2-5a34-5c6b3f9a2882@bartschnet.de> <3DDE70BC-D951-4110-B7F8-1C45BFC7CA0C@cisco.com>
To: "Darrel Lewis (darlewis)" <darlewis=40cisco.com@dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/dOXsoh8BmZyE9pUrpmk2HWhhIt8>
Subject: Re: [lisp] draft-ietf-lisp-rfc6833bis-14 8.4.1 Anycast Map-Resolver Operation
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Sep 2018 23:30:42 -0000

Well I would say so much has changed since that paragraph was written where we have xTR-IDs  used for the association and registration between an ETR and a map-server and with newer ways of authentication (like using different keys per ETR with same anycast address as well as signature-IDs) we should lighten from SHOULD NOT to MAY. 

I’m willing to change it if there are no objections. 

Dino

> On Sep 16, 2018, at 3:05 PM, Darrel Lewis (darlewis) <darlewis=40cisco.com@dmarc.ietf.org> wrote:
> 
> Hi,
> 
> This turns out to be not the case Renne.  The idea of map-server resiliency is attractive.  But any-cast works best for non-stateful cases, and the relationship between an ETR and a MS is by definition, stateful.
> 
> -Darrel
> 
>> On Sep 16, 2018, at 3:17 AM, Rene 'Renne' Bartsch, B.Sc. Informatics <ietf=40bartschnet.de@dmarc.ietf.org> wrote:
>> 
>> Hi,
>> 
>> "draft-ietf-lisp-rfc6833bis-14" section "8.4.1 Anycast Map-Resolver Operation" says
>> 
>> "Note that Map-Server associations with ETRs SHOULD NOT use anycast
>> addresses, as registrations need to be established between an ETR and
>> a specific set of Map-Servers, each identified by a specific
>> registration association."
>> 
>> In my opinion it is sensible to use anycast addresses for map servers of a distributed database for fail-over/load balancing cases and the "SHOULD NOT" is to limiting.
>> 
>> Instead I suggest to encourage operators to specifially consider possible pitfalls of anycast operation.
>> 
>> 
>> Regards,
>> 
>> 
>> Renne
>> 
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp