Re: [lisp] Proposing "Encapsulation Format" LCAF type
Dino Farinacci <farinacci@gmail.com> Fri, 14 November 2014 03:03 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 B9D431A00D0 for <lisp@ietfa.amsl.com>; Thu, 13 Nov 2014 19:03:39 -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 9rYSxVNZ41Cg for <lisp@ietfa.amsl.com>; Thu, 13 Nov 2014 19:03:34 -0800 (PST)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F95A1A1B9C for <lisp@ietf.org>; Thu, 13 Nov 2014 19:03:34 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id x13so18478140wgg.33 for <lisp@ietf.org>; Thu, 13 Nov 2014 19:03:33 -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=fN4I0JaCzfamn6bqUqHNdIdoLrjLmJER25XMAQGdGfY=; b=zpf0wzoLertjUorkd/7/lDV7ZUrX3Ahf/ynvk+ZU4Y0kG5SoD7fUv8W14ZqkuO2/JZ swVvUjI2OchOmqRtd2qowweyD3y4ljtNIKMQ9J04XaPXgHj6rLCUV4ILGoYDESqW4pSb KzQFbM2FyklUp5WK0EB4qJNs7QsgmI2As/JfVhqEKkqqtsGzWjQkOVPtSpfucLac20Uj YqI+KFiEQrc6jw2HYlG6fB0y7ahvc0pr1EOVQweVHUf50Nlv7WRoDqrXog7o40Dck94f xbS4aK8GiUeIz97R97WetXiR0ne4Gmx8W/CPHRavn7mpon+Aty89gZPMw4UB3SJIqCOs kVeg==
X-Received: by 10.180.93.37 with SMTP id cr5mr3587392wib.76.1415934212970; Thu, 13 Nov 2014 19:03:32 -0800 (PST)
Received: from t2001067c037001608095f7a535b3256a.wireless.v6.meeting.ietf.org (t2001067c037001608095f7a535b3256a.wireless.v6.meeting.ietf.org. [2001:67c:370:160:8095:f7a5:35b3:256a]) by mx.google.com with ESMTPSA id g16sm26866101wjq.20.2014.11.13.19.03.30 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 13 Nov 2014 19:03:32 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <BA0E4573-5642-485D-94F7-41969D589E82@gmail.com>
Date: Thu, 13 Nov 2014 19:03:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2459AE0E-7288-4A97-B1E8-2B12EA50458C@gmail.com>
References: <BD206B2B-8788-4595-8349-18404BE0A592@gmail.com> <7BBBA272-AE34-4EC4-9CD0-4CEDF40165CB@gmail.com> <77423131-7D11-4814-9D98-52AC39DFB4FB@gmail.com> <BA0E4573-5642-485D-94F7-41969D589E82@gmail.com>
To: Damien Saucez <damien.saucez@gmail.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/OPHgWUnUzG4RP1hbmoQQRS1v4sA
Cc: LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] Proposing "Encapsulation Format" LCAF type
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, 14 Nov 2014 03:03:41 -0000
> My point was that if we permit to specify different encapsulation techniques, > we have also to give the room to specify parameters associated to the > encapsulation scheme (e.g., a port number, a cookie, ) As for the port number, the references are in the description of each bit. And the data-plane protocol spec indicates what port is used. As for parameters, well, right now there aren't any and requirements are vague on parameters. Dino
- [lisp] Proposing "Encapsulation Format" LCAF type Dino Farinacci
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Darrel Lewis (darlewis)
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Dino Farinacci
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Damien Saucez
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Dino Farinacci
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Damien Saucez
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Dino Farinacci
- [lisp] Fwd: Proposing "Encapsulation Format" LCAF… Dino Farinacci
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Luigi Iannone
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Lori Jakab
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Sander Steffann
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Dino Farinacci
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Albert Cabellos
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Damien Saucez
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Darrel Lewis (darlewis)
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Darrel Lewis (darlewis)
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Dino Farinacci
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Florin Coras
- Re: [lisp] Proposing "Encapsulation Format" LCAF … Sander Steffann