Re: [lisp] draft-farinacci-lisp-crypto-01 - Call for WG Adoption

Fabio Maino <fmaino@cisco.com> Thu, 04 December 2014 19:08 UTC

Return-Path: <fmaino@cisco.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 E752E1A009E for <lisp@ietfa.amsl.com>; Thu, 4 Dec 2014 11:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 6-nXA0RB30qP for <lisp@ietfa.amsl.com>; Thu, 4 Dec 2014 11:08:37 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A05281A0099 for <lisp@ietf.org>; Thu, 4 Dec 2014 11:08:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2532; q=dns/txt; s=iport; t=1417720118; x=1418929718; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=35XnFZMpidNyQ+YAhVo6grG7YvcUU/WcKuB/syLBHxs=; b=NulqcrLY4l1qBy7dD4qhM3zf1eAxhxquUPgGBdnkYHyq7qbHiczKljdO UuohhIUtYlEWUIJWDnsRCgFZOsM0lsNe4IFkw2wL2grv2tyx1dt9I2TIJ 87BxxKupAHpgdkSJxBmC3uJcUV9yQlfragm8eowc35EusUDJu8Zks/igE o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al4FAO6vgFStJA2B/2dsb2JhbABZgwZSWIMFw0YKhhYCgR8WAQEBAQF9hAMBAQQBAQEaBg8BBTYKEQsYAgIFFgsCAgkDAgECARUwEwYCAQGIOg3ATJZzAQEBBwEBAQEaBIErj0IWgluBUQEEilOJU4Y0gSODLYJNiRKDaYQaHjCCRQEBAQ
X-IronPort-AV: E=Sophos;i="5.07,517,1413244800"; d="scan'208";a="102736989"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-3.cisco.com with ESMTP; 04 Dec 2014 19:08:37 +0000
Received: from [10.24.197.82] ([10.24.197.82]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id sB4J8a55013687 for <lisp@ietf.org>; Thu, 4 Dec 2014 19:08:36 GMT
Message-ID: <5480B13C.4090203@cisco.com>
Date: Thu, 04 Dec 2014 11:08:44 -0800
From: Fabio Maino <fmaino@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: lisp@ietf.org
References: <D35D7CD0-20E5-4210-8025-7C92441DD339@gigix.net>
In-Reply-To: <D35D7CD0-20E5-4210-8025-7C92441DD339@gigix.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/XQw754ADL4E2EazwxqKHgckYhVI
Subject: Re: [lisp] draft-farinacci-lisp-crypto-01 - Call for WG Adoption
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: Thu, 04 Dec 2014 19:08:40 -0000

I don't support adoption of this document.

The document is proposing an extension of the LISP header to support 
data plane security.  However, there has been quite a lot of discussion 
in various WGs, including LISP, about the need for a more flexible 
overlay encapsulation. Besides support for data plane security, the 
requirements include capability to support non IP payloads, and to 
support metadata for various applications including service chaining  
and policy tags.

I believe that rather than just adding incremental support for data 
plane security, the WG should  have a comprehensive look at how to 
extend the LISP header to address the requirements above. 
draft-lewis-lisp-gpe, that was presented to the WG a few times, tries to 
address all of those requirements.

Extending the semantic of the header to support data plane security, at 
least for HW implementations, comes at about the same cost of addressing 
all of the requirements above. I believe the same is true, to a lesser 
extent, even with SW implementations (at least those that deal with the 
encap in the kernel).

Thanks,
Fabio



On 12/4/14, 3:27 AM, Luigi Iannone wrote:
> Hi All,
>
> During the 91st IETF authors of the draft-farinacci-lisp-crypto-01
> [https://tools.ietf.org/html/draft-farinacci-lisp-crypto-01]
> asked for WG adoption. Meeting participants expressed consensus on adoption.
>
> This message begins the two weeks call for WG adoption to confirm the meeting outcome.
> The call ends on  December 19th 2014.
>
> Please respond to the LISP mailing list with any statements of approval or disapproval.
>
> Recall that:
>
> - This is not WG Last Call. The document is not final, and the WG is expected to
>    modify the document’s content until there is WG consensus that the content is solid.
>    Therefore, please don’t oppose adoption just because you want to see changes to its content.
>
> - If you have objections to adoption of the document, please state your reasons why,
>    and explain what it would take to address your concerns.
>
> - If you have issues with the content, by all means raise those issues and we can
>    begin a dialog about how best to address them.
>                        
>                                                                                                          
> Luigi and Joel
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp