IETF Logo Mail Archive

Re: [lisp] Lisp for 5G

Dino Farinacci <farinacci@gmail.com> Sat, 27 August 2016 17:17 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 9D64912B032 for <lisp@ietfa.amsl.com>; Sat, 27 Aug 2016 10:17:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 QuFbXamlNSCF for <lisp@ietfa.amsl.com>; Sat, 27 Aug 2016 10:17:15 -0700 (PDT)
Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (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 4759712B008 for <lisp@ietf.org>; Sat, 27 Aug 2016 10:17:15 -0700 (PDT)
Received: by mail-qk0-x244.google.com with SMTP id v123so7763497qkh.3 for <lisp@ietf.org>; Sat, 27 Aug 2016 10:17:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=+JgrE5++GDXfiXHlS8PAwtLjSxWM4utfIsHkPA6kzoc=; b=hOfpbNcLk00vBvPQsGs+4pg21B5uUCnA3qPwqCN08kLlJrIgbcqq5Hkj24JkZbjjkJ 959Rmry26Elcudr+X9jK6w0P/uQEBf1OHVBqGKpkDVZYimCiOA8pLxoi1Hb2BRUMFPCs n0dUr4p7tFKTS43KffNzCjXycPtQ0fx8A7BjjBQ2TLtF8mx1c+YAKZ7OARGViGFP/nm7 fPpNWnS4LWG369PNDzUr3bvYaWlbMD9V3ChQsZTuoCqVHZkush1Pq1yFh/z50w7Jt7AY dpcxOjv6owLf2cVM2KgxwcgeJ+Jw6Pv4ar58IfV5MPZpV6U6CXG3LIUVqO1Y6m0jx6Ky CGlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=+JgrE5++GDXfiXHlS8PAwtLjSxWM4utfIsHkPA6kzoc=; b=gw32ir/83iVCz70med1TUAmrgLCXaNzN0qwkqBhYtF5jaaaY6Zz26UpJJfOLV3PVrN J9aIvCTBphbF6m9jSMwq8K0JLx6AvZWm4ru8F3+/Y5TbB/ca+TjJdTuXhXC0TYKzbzAt 24dU8RoFLasdnX1kPECJdS6Zd/n6uLuJE/2lZU4ZWf32hthj+wksmvdivdzugvkMDUOY pKjzpHAl5IbQ+KiOsZPdpPPE0WHCHArnRqccwB5TM6DXxsQOB+9Jojn4NdponT5M0auZ RFpvCAu9Q8APTnEC6jHUtLrk4UQktth6pE6I1jbKs9K/QX4E6kcwWUT1gYzyXdbcvHlk KWMw==
X-Gm-Message-State: AE9vXwNJNkr1/GiTBjywIGnbdR0WdDPs8wIZJL8FK6fxbiPz/YvysGHcK5zhZkT/mxckNQ==
X-Received: by 10.55.217.132 with SMTP id q4mr9568624qkl.221.1472318234464; Sat, 27 Aug 2016 10:17:14 -0700 (PDT)
Received: from [10.220.145.246] ([166.170.30.12]) by smtp.gmail.com with ESMTPSA id i65sm13461943qtb.18.2016.08.27.10.17.12 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 27 Aug 2016 10:17:12 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-298EFFD6-F361-445F-BC75-58F90ADA1048"
Content-Transfer-Encoding: 7bit
From: Dino Farinacci <farinacci@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Sat, 27 Aug 2016 12:34:03 -0400
Message-Id: <9CCD7FDA-A935-4245-AD71-ADB1707C3727@gmail.com>
References: <099C4B79-7704-46C1-8964-844C5D093E9B@gmail.com>
In-Reply-To: <099C4B79-7704-46C1-8964-844C5D093E9B@gmail.com>
To: Sharon <sbarkai@gmail.com>
X-Mailer: iPhone Mail (14A5345a)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/DATUZ_T_u_L3yfpPPTltdzzarEo>
Cc: lisp@ietf.org
Subject: Re: [lisp] Lisp for 5G
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 27 Aug 2016 17:17:16 -0000

> Did anyone look at a weighted/probability based ID-Location schema where ITR chooses ETR by applying a "fuzzy" selection logic for moving identities? (movable && moving things)

In draft-meyer-lisp-mn we created a requirement and spec'ed out the M-bit in the Map-Register message. 

The intent was to allow an ITR or PITR to know that an ETR was acting in behalf of an EID that moved often. Thereby allowing the ITR/PITR to flush its cache often as an alternative to waiting for SMR messages from the ETR or Map-Notify messages from map-servers. 

Do you think this mechanism is sufficient for your requirement?

And yes, the priority and weights can be manipulated so the encapsulator has choice to choose another ETR. 

Dino

v2.23.0 | Report a Bug | By Email