Re: [lisp] Some basic questions ...

Dino Farinacci <farinacci@gmail.com> Fri, 21 February 2014 01:55 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A77E21A03B4 for <lisp@ietfa.amsl.com>; Thu, 20 Feb 2014 17:55:32 -0800 (PST)
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, SPF_PASS=-0.001] autolearn=ham
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 BejIUXKuGVBd for <lisp@ietfa.amsl.com>; Thu, 20 Feb 2014 17:55:30 -0800 (PST)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id D76F71A03AF for <lisp@ietf.org>; Thu, 20 Feb 2014 17:55:30 -0800 (PST)
Received: by mail-pb0-f50.google.com with SMTP id rq2so2732192pbb.23 for <lisp@ietf.org>; Thu, 20 Feb 2014 17:55:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CABN2Kj7VpVDM9gTE0UtbnSYGW8HqMNT9n/bvDdtAus=; b=MwAWHDVYXX0wovbGIEPm/h+WPgjo92p5foGET6SwtjfgEspEGzffH5gHK9fKt+2bSk GVEOLIH9dPZfMqjyc2KrhjPBSZm/4OCDJqQoqp+UvN+cN8i7F+5vtBKyw2bH2xTIL+jF UTwDpgB+d4nyJY+tOZhuwW9CgpDkbXZdPa68V3okPPlvoQCj0B51wTzYQhyg/qy3avcY BvbO+hBHonfJMx1kqIiOCFPZRu8JQpvIYyemoXFgScIRPVMrP1DuQWHeoY6+xD689H4B TKUMuwjNzBZQjbn6nbknMiNPhcFcI2qROvOf4qbkmJzNsH/ynxXo6cAzxam/a9E/R9/f iW2w==
X-Received: by 10.68.241.198 with SMTP id wk6mr5894054pbc.11.1392947727196; Thu, 20 Feb 2014 17:55:27 -0800 (PST)
Received: from [192.168.1.10] (173-8-188-29-SFBA.hfc.comcastbusiness.net. [173.8.188.29]) by mx.google.com with ESMTPSA id it4sm15657079pbc.39.2014.02.20.17.55.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Feb 2014 17:55:24 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <20140220164147147597.5306c32c@sniff.de>
Date: Thu, 20 Feb 2014 17:55:25 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <80461F03-4633-4705-9F01-E5ACF01E3677@gmail.com>
References: <20140217013051556658.9cfb700c@sniff.de> <85246DF3-B45A-474A-BB5F-B0C9D3EE88DA@gmail.com> <20140220164147147597.5306c32c@sniff.de>
To: Marc Binderberger <marc@sniff.de>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/0-YwwkNnp-NKp5lXmX-eT1UyTHo
Cc: LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] Some basic questions ...
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 21 Feb 2014 01:55:32 -0000

> Hello Dino,
> 
> there was another question I forgot regarding the notifications: so 
> when the map-notification is not used as an ACK for map-register but is 
> actually informing the ETRs about events then how is the delivery 
> guaranteed? The underlying IP/UDP transport may drop.

The Map-Server sends Map-Notify messages to the ETR and the ETR responds with Map-Notify-Ack messages.

> For map-register we periodically send again, so packet loss of 
> map-registers is not a big problem. What is your idea for map-notifies? 
> Some of the notifications may be singular events. Other of course could 
> be periodic (e.g. merge notification triggered by the map-registers?).

These are not perioidic, because only when there are locator-set changes, the Map-Notify messages are sent by Map-Servers.

> Would I need an ACK for the map-notification (and some fast-timer 
> re-send, e.g. every 1sec until ACKed) ?  That would take state/timer, 
> although only until's it's ACKnowledged.

Yes, they are called Map-Notify-Ack messages. They contain the same contents as the Map-Notify but just with a different type value.

Dino