Re: [lisp] #5: LISP protocol version is alive and kicking

jnc@mercury.lcs.mit.edu (Noel Chiappa) Mon, 21 September 2009 17:48 UTC

Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: lisp@core3.amsl.com
Delivered-To: lisp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0F0B3A6947 for <lisp@core3.amsl.com>; Mon, 21 Sep 2009 10:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xstzN3hs+jsu for <lisp@core3.amsl.com>; Mon, 21 Sep 2009 10:48:23 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id CAD0528C160 for <lisp@ietf.org>; Mon, 21 Sep 2009 10:48:22 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id CC40B6BE54F; Mon, 21 Sep 2009 13:49:23 -0400 (EDT)
To: lisp@ietf.org
Message-Id: <20090921174923.CC40B6BE54F@mercury.lcs.mit.edu>
Date: Mon, 21 Sep 2009 13:49:23 -0400
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [lisp] #5: LISP protocol version is alive and kicking
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 21 Sep 2009 17:48:23 -0000

    > From: Sam Hartman <hartmans-ietf@mit.edu>

    > If no version information is included in the packet, then the site
    > may not know what version to use in its responses. ...
    > in the case where the site is going to use gleaned map cache
    > information, it may not have anything other than that first packet
    > to find out what version to use.

Light dawns over famous Massachussetts fishing harbour... :-) Sorry I was
a bit slow to catch on.

Yeah, that's a problem. (Puts on thinking cap, goes away to ponder for a
few days...)

    > You might argue that the map request could have carried your version
    > information. However, because of square routing and other concerns,
    > the map request and data packet may go to different places.

That's a general problem with square routing (i.e. packets from site A to
B flow from ITR a1 to ETR b1, packets back from B to A flow via ITR b2 and
ETR a2), and not just with the version information - the b2 ITR doesn't
have the mapping, either.

I've had it kicking around the back of my brain for a while now, but no
great hack has appeared. I suspect the only answers are painful (e.g.
better co-ordination between all the xTRs at a site - which we might need
anyway, for other reasons).

	Noel