IETF Logo Mail Archive

Re: [lisp] Lisp for 5G

Sharon <sbarkai@gmail.com> Sat, 27 August 2016 22:56 UTC

Return-Path: <sbarkai@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 E944412D149 for <lisp@ietfa.amsl.com>; Sat, 27 Aug 2016 15:56:38 -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 tnilHeuqxuOI for <lisp@ietfa.amsl.com>; Sat, 27 Aug 2016 15:56:37 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 2E8BF12B016 for <lisp@ietf.org>; Sat, 27 Aug 2016 15:56:37 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id u134so67946177ywg.3 for <lisp@ietf.org>; Sat, 27 Aug 2016 15:56:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=n12eM9T6/eGqK+7JN6VDRPUAfkHx62sxjBfsBORpWxU=; b=EFszF7Rvs8JsNizIsu0kGa7Oj9nBdBHgpIEqPnWAPBSI3qdJ1r9Hi+T25pWQ4ySE/f oc/i2qi4apwdwjK3XnLmwQ8Wv0dHtwJ8rJFq2QUW1PVMlHz8XejvBnkGyfswgyWG2Ivy +sgZALaa7wz5xA2cPHHqQMSvKMCpfq6o1aWNY9P9vk+6CrcambBr+ca0bnjwkeHIiGaW 9nIdqcvrh1uUVjw2HehU1L/TdyY2ztFaEO4nNhFo+NgsHrSo7GIm+L7tjIDFj1ay13mv SzgQ1kjfYYTWXRj0+mAieILS8lWV6A2CDBJUmzLgWato6GSRnO/BG9JdMTYecIQwaAyl cEOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=n12eM9T6/eGqK+7JN6VDRPUAfkHx62sxjBfsBORpWxU=; b=Li8gQT2crvqTK9aOn2k5rVg/gcqpnQLx7UzvLvO833brSgn07FQvrKD+4kwXaXsXdh WpDgKVzbl+PGXEKoKhsLzxLTf2UIn9YMnJ/vecECeFgXi4u4wZ6GWBaAQLC411v+rbA9 +avwTI4MJHaUb4nblj2yuFc1HerNULuMX6IJwmUNh/oQON0l8t1FU8Z2ln2rO4YTqGbs HVRK+EjH2hgiFI9zc61qrR/SVNfEFOiTfqGpY05+9iq+DMd4/x/MutXjbC7YvYtO7G6Y xCK5WR1VruCL9qByCCCD4mH7uiHFXs2R87RN68b/5hKJt255N2VvP7kIVvkQ7Cz2KUX2 zULA==
X-Gm-Message-State: AE9vXwPB6ZAaEGVJHNbPLL8YNegKb4GQA0XsT3AFvyknCnqrujMY4oGGr6XRIHsySHtDLA==
X-Received: by 10.13.217.20 with SMTP id b20mr9573392ywe.44.1472338596480; Sat, 27 Aug 2016 15:56:36 -0700 (PDT)
Received: from ?IPv6:2600:1017:b409:74db:880a:5010:b2d2:a52c? ([2600:1017:b409:74db:880a:5010:b2d2:a52c]) by smtp.gmail.com with ESMTPSA id c13sm13478996ywa.19.2016.08.27.15.56.35 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 27 Aug 2016 15:56:35 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-22464E0A-4106-4D35-BFDB-778A193888BE"
Mime-Version: 1.0 (1.0)
From: Sharon <sbarkai@gmail.com>
X-Mailer: iPhone Mail (13G36)
In-Reply-To: <9CCD7FDA-A935-4245-AD71-ADB1707C3727@gmail.com>
Date: Sat, 27 Aug 2016 18:56:33 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <D6F95AA7-64DF-4418-BB48-B56A512C686F@gmail.com>
References: <099C4B79-7704-46C1-8964-844C5D093E9B@gmail.com> <9CCD7FDA-A935-4245-AD71-ADB1707C3727@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/NG574DywYzFeYIFm4F3jMkPfpf0>
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 22:56:39 -0000

Maybe we should go in a draft through all the mechanisms, multi home, bits, Smr ..
specifically in the context of handover 
Perhaps a heads up message from the mobile device  is needed before fully  moving from ETR to ETR ...

--szb

> On Aug 27, 2016, at 12:34 PM, Dino Farinacci <farinacci@gmail.com> wrote:
> 
> 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