IETF Logo Mail Archive

Re: [lisp] Proposing "Encapsulation Format" LCAF type

Florin Coras <fcoras@ac.upc.edu> Tue, 02 December 2014 20:01 UTC

Return-Path: <fcoras@ac.upc.edu>
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 2B4C31A701D for <lisp@ietfa.amsl.com>; Tue, 2 Dec 2014 12:01:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-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 Xuksvw0znbBA for <lisp@ietfa.amsl.com>; Tue, 2 Dec 2014 12:01:13 -0800 (PST)
Received: from roura.ac.upc.es (roura.ac.upc.es [147.83.33.10]) by ietfa.amsl.com (Postfix) with ESMTP id DF4B81A7016 for <lisp@ietf.org>; Tue, 2 Dec 2014 12:00:57 -0800 (PST)
Received: from gw-2.ac.upc.es (gw-2.ac.upc.es [147.83.30.8]) by roura.ac.upc.es (8.13.8/8.13.8) with ESMTP id sB2K0uQZ002257; Tue, 2 Dec 2014 21:00:56 +0100
Received: from [10.154.176.215] (128-107-239-233.cisco.com [128.107.239.233]) by gw-2.ac.upc.es (Postfix) with ESMTPSA id 94C77C5; Tue, 2 Dec 2014 21:00:55 +0100 (CET)
Message-ID: <547E1A76.2000207@ac.upc.edu>
Date: Tue, 02 Dec 2014 12:00:54 -0800
From: Florin Coras <fcoras@ac.upc.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: lisp@ietf.org
References: <BD206B2B-8788-4595-8349-18404BE0A592@gmail.com> <AA3EDE9A-F22B-4DB7-8414-003F0875E11B@gmail.com> <DA93E662-48DF-428A-87A9-F8D8EDB08A99@gigix.net> <44E9A1FF-4F0A-4DCC-AE76-E717404CF9FA@cisco.com> <944C1F27-34E0-4ACF-BA88-05FE48C1BAEB@gmail.com>
In-Reply-To: <944C1F27-34E0-4ACF-BA88-05FE48C1BAEB@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/ydu2hRVlgVor8rRI_mCVNcmo6E4
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: Tue, 02 Dec 2014 20:01:19 -0000

+1

Florin

On 12/2/14 11:01 AM, Dino Farinacci wrote:
> So let's have one.
>
> Dino
>
>> On Dec 2, 2014, at 9:54 AM, Darrel Lewis (darlewis) <darlewis@cisco.com> wrote:
>>
>>
>> On Nov 27, 2014, at 7:34 AM, Luigi Iannone <ggx@gigix.net> wrote:
>>
>>> About point (1) of Dino’s mail:
>>>
>>> The proposed encoding is based on a bitwise approach that today reserves specific bits to encapsulation formats that at this time are not WG documents anywhere in the IETF. The WG should be aware that the dependencies introduced in the document may slow down its progress.
>> In general, I believe this points out that we need a Registry for LCAF types that is independent of this document status.  Certainly we want to encourage future types to be developed independent of the LCAF draft’s status.  That is, I would like to see LCAF go to publication independent of any particular AF extension’s progress/use.  I believe Joel said something similar at the mic a few meetings ago.
>>
>> -DArrel
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

v2.28.0 | Report a Bug | By Email | System Status