[lisp] Some basic questions ...

Marc Binderberger <marc@sniff.de> Mon, 17 February 2014 09:30 UTC

Return-Path: <marc@sniff.de>
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 D25521A0394 for <lisp@ietfa.amsl.com>; Mon, 17 Feb 2014 01:30:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.548] 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 yvLfeC5f9jAd for <lisp@ietfa.amsl.com>; Mon, 17 Feb 2014 01:30:56 -0800 (PST)
Received: from door.sniff.de (door.sniff.de [IPv6:2001:6f8:94f:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 66D251A008E for <lisp@ietf.org>; Mon, 17 Feb 2014 01:30:56 -0800 (PST)
Received: from [IPv6:::1] (localhost.sniff.de [127.0.0.1]) by door.sniff.de (Postfix) with ESMTP id 986F12AA0F for <lisp@ietf.org>; Mon, 17 Feb 2014 09:30:52 +0000 (GMT)
Date: Mon, 17 Feb 2014 01:30:51 -0800
From: Marc Binderberger <marc@sniff.de>
To: lisp@ietf.org
Message-ID: <20140217013051556658.9cfb700c@sniff.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: GyazMail version 1.5.15
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/FuVc86D0yDEooNqMBjncvbPNo4w
Subject: [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: Mon, 17 Feb 2014 09:31:00 -0000

Hello LISP experts,

have two questions, mainly to understand the context a bit better.

Q1: map-notify message.

maybe it's the name but I always expected this message is for the Map 
Server to inform ETRs. Kind of a "push" method. But reading RFCs 6830 
and 6833 again it seems that the Map-Notify is simply an ACK for a 
received and processed Map-Register message. Take the Map-Register 
message, set the type to Map-Notify and send back.

Now, the use as ACK is not a contradiction to the broader use as a push 
message. So my question to the LISP experts and inventors is: is 
Map-Notify restricted to be just an ACK? (having an extra type for it 
seems generous)



Q2: Locator-Status-Bits (LSBs).

RFC 6830 says in section 6.3:

   When an ETR decapsulates a packet, it will check for any change in
   the 'Locator-Status-Bits' field.

I interpret this that if an ITR sets the Locator-Status-Bits then it 
would do so permanently. In other words the LSBs are not set used in an 
"alert style" (means: only set when an RLOC change happened) ?

Wondering what requirements this imposes on the data plane. It may not 
be possible for the "hardware" (NP, ASIC, FPGA) to check the incoming 
LSBs. So if LSBs are sent permanently this would likely require to punt 
every Nth packet to the control plane?



Q3: the lexicographic order of RLOCs.

Maybe stupid question but the lexicographic order is computed over what 
byte sequence exactly?  Loc-AFI + Locator? (both in network order, 
Loc-AFI first)



Thanks & Regards,
Marc