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

"Darrel Lewis (darlewis)" <darlewis@cisco.com> Sun, 16 September 2018 22:05 UTC

Return-Path: <darlewis@cisco.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 BB92B130DC4 for <lisp@ietfa.amsl.com>; Sun, 16 Sep 2018 15:05:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 9nW67F449_Ff for <lisp@ietfa.amsl.com>; Sun, 16 Sep 2018 15:05:07 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 685D5128B14 for <lisp@ietf.org>; Sun, 16 Sep 2018 15:05:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1201; q=dns/txt; s=iport; t=1537135507; x=1538345107; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=9f2Hj5y7Vced637+8xQefobOn436UdqDRQBOFRhwgCs=; b=KW+YokntwWlAUHqfo485U4Ue3Qc4xyEAxF88fAxZ9ydt2js3j7kYdH0a X0KdIcKO/cB9zQyLbN3q0Dc9RpXgPExuoip+vpMeZr+5biKw83MnJP42f cX2cBj0d2bqEeXi6W6dGQyABHm9F2ZelXpQXNxiZAIf5B55z1pbieweY8 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A3AABH0p5b/4oNJK1aGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYFQgghlfygKi32MKIFoJZZLgXoLGAuESQKDXiE0GAEDAQE?= =?us-ascii?q?CAQECbRwMhTgBAQEBAgEBATg0BAcFCwIBCBgeECcLJQIEDgWDIQGBeQgPpRS?= =?us-ascii?q?Ec4UNim0XgUE/gTkME4JMgxsBAQKBSRaDMoImApxECQKQExePDZQoAhEUgSU?= =?us-ascii?q?dOCcagRRwFTsqAYJBCYsMgR+EH28BjRKBHgEB?=
X-IronPort-AV: E=Sophos;i="5.53,382,1531785600"; d="scan'208";a="452915166"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Sep 2018 22:05:06 +0000
Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id w8GM56op008776 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 16 Sep 2018 22:05:06 GMT
Received: from xch-rcd-018.cisco.com (173.37.102.28) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 16 Sep 2018 17:05:05 -0500
Received: from xch-rcd-018.cisco.com ([173.37.102.28]) by XCH-RCD-018.cisco.com ([173.37.102.28]) with mapi id 15.00.1395.000; Sun, 16 Sep 2018 17:05:05 -0500
From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
To: "Rene 'Renne' Bartsch, B.Sc. Informatics" <ietf=40bartschnet.de@dmarc.ietf.org>
CC: "Darrel Lewis (darlewis)" <darlewis@cisco.com>, "lisp@ietf.org" <lisp@ietf.org>
Thread-Topic: [lisp] draft-ietf-lisp-rfc6833bis-14 8.4.1 Anycast Map-Resolver Operation
Thread-Index: AQHUTglSwyMwslNltEKsj8FgSn3zSA==
Date: Sun, 16 Sep 2018 22:05:05 +0000
Message-ID: <3DDE70BC-D951-4110-B7F8-1C45BFC7CA0C@cisco.com>
References: <d50da9ac-82f7-5aa2-5a34-5c6b3f9a2882@bartschnet.de>
In-Reply-To: <d50da9ac-82f7-5aa2-5a34-5c6b3f9a2882@bartschnet.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.253.181]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A5307DD9A82FC749B9AD7BCCF92DA8AF@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.28, xch-aln-018.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/wLZOc8m2TA0SOhpmP-ggHMPBt_U>
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 22:05:10 -0000

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