IETF Logo Mail Archive

Re: [lisp] [nvo3] New Version Notification for draft-quinn-vxlan-gpe-00.txt

Dino Farinacci <farinacci@gmail.com> Tue, 10 September 2013 17:19 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2353921F941F; Tue, 10 Sep 2013 10:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KtVlAaSDJdDC; Tue, 10 Sep 2013 10:19:26 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 632A721F84B6; Tue, 10 Sep 2013 10:19:26 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz10so8036156pad.16 for <multiple recipients>; Tue, 10 Sep 2013 10:19:26 -0700 (PDT)
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=So0OUzbuYiRgj5YLUCbrANBOWre8SVzk8y6UqZwAqtc=; b=uifGD3RMDd4MTOCXkYV1ZQOSHrLRUykhy5m70OMc9GmMbpDy7NryQpQu8YSCAP58D7 9Q/o+rKpyjv4nhrm/ScCoR20Xhns4M3U4AhhdftDPI4sr0x0adWSiYCrU7TVkYPb0DOZ FflitVAfxZD8QY8pcNK5Bqh/ZezTb/d4K3prZVtucHoTVOaNGkcNjgouDe8rUA8a84O+ QTGalzoGYmOY8DOiTvusHFRy1qmoy/MuG6NiHszO44wJkP2hlcUvvC0mq2Lvk4dka/gd HGMhbL8PZaNQohTd95yTbWIVlqyG7uS9UZWQAVcxEsabMdAELwRNdF9vCRM95S/s7Obs w/RQ==
X-Received: by 10.66.221.8 with SMTP id qa8mr3142684pac.188.1378833565909; Tue, 10 Sep 2013 10:19:25 -0700 (PDT)
Received: from [10.169.113.83] (71-6-80-11.static-ip.telepacific.net. [71.6.80.11]) by mx.google.com with ESMTPSA id f2sm23281932pbg.44.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Sep 2013 10:19:25 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D452C3627@dfweml509-mbb.china.huawei.com>
Date: Tue, 10 Sep 2013 10:19:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D25752D-8556-4A89-80A3-EC28F94437EF@gmail.com>
References: <20130827170744.22874.97003.idtracker@ietfa.amsl.com> <B4CF12F64861194990FEA0AE39F9B1620EA5E32E@xmb-rcd-x14.cisco.com> <2691CE0099834E4A9C5044EEC662BB9D452B3D74@dfweml509-mbx.china.huawei.com> <B4CF12F64861194990FEA0AE39F9B1620EA61F74@xmb-rcd-x14.cisco.com> <2691CE0099834E4A9C5044EEC662BB9D452C25C3@dfweml509-mbb.china.huawei.com> <1619DC43-A6B8-4DD2-8875-A2FA57A85E82@gmail.com> <2691CE0099834E4A9C5044EEC662BB9D452C360E@dfweml509-mbb.china.huawei.com> <0E854774-B26D-4FEF-A810-A8383CB9A288@gmail.com> <2691CE0099834E4A9C5044EEC662BB9D452C3627@dfweml509-mbb.china.huawei.com>
To: Lucy yong <lucy.yong@huawei.com>
X-Mailer: Apple Mail (2.1508)
Cc: nvo3@ietf.org, "Paul Quinn (paulq)" <paulq@cisco.com>, "lisp@ietf.org list" <lisp@ietf.org>
Subject: Re: [lisp] [nvo3] New Version Notification for draft-quinn-vxlan-gpe-00.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Sep 2013 17:19:27 -0000

Copying the LISP working group mailing list.

>> This implies that both gpe LISP and legacy LISP may be used in the market. Is that true only IP-in-IP application need nonce feature? Mobility is important requirement for cloud applications, so gpe LISP needs to develop other solution for this feature? Sorry, this is a hard sale.
> 
> If you use IP-in-IP you don't need to set the P-bit, making the nonce available for use. Yes, there are applications where the nonce is useful.
> [Lucy] Yes, I agree that the nonce is useful. But gpe LISP router will not support that. Why do we want to remove this in the protocol evolution? 

Lucy, we are not removing anything. Like I said (and I don't want to continually repeat myself) that the features are tradeoffs.

The motivation for the change was to get VXLAN to have protocol demuxing. And in the spirit of keeping the packet formats for VXLAN and LISP as identical as VXLAN will have it, the P-bit is being proposed for LISP.

This is a proposal. The LISP working group must decide if the draft becomes a working group document.

Dino

> 
> Lucy
> 
> Dino
> 
>> 
>> Regards,
>> Lucy
>> 
>> 
>> 
>> -----Original Message-----
>> From: Dino Farinacci [mailto:farinacci@gmail.com] 
>> Sent: Tuesday, September 10, 2013 10:56 AM
>> To: Lucy yong
>> Cc: Paul Quinn (paulq); nvo3@ietf.org
>> Subject: Re: [nvo3] New Version Notification for draft-quinn-vxlan-gpe-00.txt
>> 
>>> Regarding to the protocol evolution, does this mean that nonce/map-version features in LISP will be deprecated? IMO: Having the same field overloaded for many difference purposes is not good way for the protocol evolution, it becomes messy.
>> 
>> No it does not mean that. It means that the features need to be traded off. So the market/user-base will decide what it wants to use that field for.
>> 
>> Dino
>> 
>> _______________________________________________
>> nvo3 mailing list
>> nvo3@ietf.org
>> https://www.ietf.org/mailman/listinfo/nvo3
> 
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3

v2.23.0 | Report a Bug | By Email