Re: [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
Tom Herbert <therbert@google.com> Fri, 11 April 2014 15:34 UTC
Return-Path: <therbert@google.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC2081A06E7 for <nvo3@ietfa.amsl.com>; Fri, 11 Apr 2014 08:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=no
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 pTfXehFA5PBa for <nvo3@ietfa.amsl.com>; Fri, 11 Apr 2014 08:34:33 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id 58BA01A06F3 for <nvo3@ietf.org>; Fri, 11 Apr 2014 08:34:33 -0700 (PDT)
Received: by mail-ig0-f180.google.com with SMTP id c1so955754igq.13 for <nvo3@ietf.org>; Fri, 11 Apr 2014 08:34:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=h6tPqLnKuiOzZegnGFoj34W8Jh8FXxAySySAA9s+P6Y=; b=ark7OZJrsMmMQWJrgHyFbzdEim8UUQ1ZXUGJiXNkubXCXIR0SoT9rdYnosrez/Hx+1 18k6+WAoeDMmvENEZa8K37aMFXHFu3j7tPvw40mQXNivtAda67lsY2PLZKoScK3CgYWC WwZ95s6OApvoVEPdWVm/+PgF0rqiKmk5pP5aJTwuwhSEWWNj2KwteiKD6FEtWQjgRAkL yVk3o6/GP9QCd5WSRCm1B39qrwG8YaWXUDRd3cZBQo39i3RMWIO2IILya+Ta8Ilsl1HQ 51kNQrdI33KTJ/9ZbpxjTuhuCU3RTg4WbjDlVVEAquv/7wwHHmuzEgXFgFkZIhyIbVwT lUcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=h6tPqLnKuiOzZegnGFoj34W8Jh8FXxAySySAA9s+P6Y=; b=QfA9SCNAdOyh6St/t4s+5GhU/GWTUJ/onSCMdmIoKuIG7areP25FgULzlNNWDQ8aC1 cythp5MbwzMfw+wI18L9soTrxIt7UPALRpMuduB6aDtLJTQcMN3mLO7vKZZyoLSSnE7I WS4QrisJY7jpMkBV6fg43IU9ClHeiaNxlUrKqAHWpFu/s+tWZVNSb1goIFrP91v/n159 vA3aviWgLzyOQQsoG3LWe25LRXA3UkRG8bj4T442wlG/PWQC4vl3EqGI94siwpHh3cpf yJ29gwcOHmpJoPJl7+6SX3o2RXKx4qpUx08kR4pC9KB2cfYYAaRWIYg4MNvRPKTFGlVN YDnw==
X-Gm-Message-State: ALoCoQmnpixcP+675+xVuKYsoAtFbs01xHU0r+oOcZe3fewtxrWZx0RutIobn3CcZrggCQCyfKHk5snwlX1+6QPXDLVWtNhdXdFLI5q8aDMpy+/qQCxUUxXgCfD/N9J8GIh1Juoqp/crjty505ULttr1WlFMu/7TNyiBbjF17t1Ti+5DSAaa0a9k5P5isZ0yCZ1XzIFmEAdx
MIME-Version: 1.0
X-Received: by 10.50.43.225 with SMTP id z1mr4559523igl.29.1397230471910; Fri, 11 Apr 2014 08:34:31 -0700 (PDT)
Received: by 10.64.148.98 with HTTP; Fri, 11 Apr 2014 08:34:31 -0700 (PDT)
In-Reply-To: <5347C7FF.8010606@cisco.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com> <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com> <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E2C07@SZXEMA502-MBS.china.huawei.com> <5347C7FF.8010606@cisco.com>
Date: Fri, 11 Apr 2014 08:34:31 -0700
Message-ID: <CA+mtBx_8TvPoiaUdJu2UegNOfMr4Cte2Y7DPhwk=-+LtgK9_cw@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: "Anton Ivanov (antivano)" <antivano@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/dFtKKRq-KbJCglF1yfmhw6oFdjI
Cc: "nvo3@ietf.org" <nvo3@ietf.org>
Subject: Re: [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 15:34:35 -0000
> You do not need to specify anything here. You can just offset yourself and > stick the extra fields between a _STANDARD_ L2TPv3 header and the payload. > Due to L2TPv3 not specifying an Ethertype in the header you can offset the > data by as much as you wish and stick in there whatever you wish. It will > still be fully compatible and will be supported at some backward > compatibility level by any implementation which has an offset parameter. > That is pretty much all of them nowdays. > "stick in there whatever you wish" is not a plan to produce an interoperable and robust protocol. It seems like L2TP would generally benefit from including an EtherType, why not propose that as a new optional L2TP field? > In any case, as we already have a reference implementation for use of L2TPv3 > as a virtualization protocol enqueued for inclusion in kvm-qemu 2.1, > containers in Linux above 3.3 and UML (TBA, current versions are 3.3+) > please specify how you interoperate versus existing code which in the > process of being deployed. > > Hint - you do not. > > > A. > > > > Thanks, > > > > Carlos. > > > > - Even with Type field, this still suffers from the same problem L2TP > has that network devices won't be able to parse the packet beyond the > L2TP header (the cookie field makes the header variable length). This > eliminates the ability to implement the protocol with LRO for > instance. I suggest you take four or five bits from reserved section > for header length to resolve this (see example in GUE). > > [Frank] : good comments. Will consider it~~ > > > - Cookie mechanism is an advantage over VXLAN and nvgre I believe, but > why limit it to 32 bits? 64 bits is much stronger, and at some point > we might even want 128 bits to do strong authentication. > > Some more general questions applicable to this and some other proposals. > > - "TNI field"-- this seems to use the same 24 bit left shifted format > of nvgre and VXLAN. I still don't see the rationale for this! Why > can't the full 32 bit field be allocated for vni? A large deployment > will be using various levels of hierarchical allocation and possibly > obfuscation of vni (TNI). The nvo3 requirements on this are vague > ("100's of thousands of virtual networks"), but they clearly don't > expect this the VNI to be a simple flat space either. > > [Frank] : It’s an issue existing a long time. I have no personal preference > on it. It totally depends on real requirement. > > > > > > > - "Outer Ethernet Header"-- showing the outer Ethernet header in L3 > encapsulations examples is not necessary, use of Ethernet is not a > requirement, and this is potentially very misleading. For instance, > the outer Ethernet FCS does *not* protect the packet end to end in an > L3 routed network. Personally, I think it would be more illustrative > to show the IP packet in the inner Ethernet frame instead to see how > its alignment is affected. > > [Frank] : Actually, It’s only a encapsulation example. But your comment is > right. We will correct in the next version. Thanks! > > > > Thanks, > Tom > > > B.R. > Frank > > > -----Original Message----- > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > Sent: Thursday, April 10, 2014 11:22 AM > To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon > Kim; Fanduoliang; Xialiang (Frank) > Subject: New Version Notification for draft-fan-l2tp-vp-01.txt > > > A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully > submitted > by Liang Xia and posted to the IETF repository. > > Name: draft-fan-l2tp-vp > Revision: 01 > Title: L2TP-VP: Layer Two Tunneling Protocol - Virtualization > Profile > Document date: 2014-04-10 > Group: Individual Submission > Pages: 9 > URL: > http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt > Status: https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/ > Htmlized: http://tools.ietf.org/html/draft-fan-l2tp-vp-01 > Diff: http://www.ietf.org/rfcdiff?url2=draft-fan-l2tp-vp-01 > > Abstract: > This document describes Layer Two Tunneling Protocol (L2TP)'s > virtualization profile (L2TP-VP), which reuses session header of L2TP > data message to securely support overlay networks for multiple > tenants, and simplifies tunnel setup by disabling all kinds of L2TP > control messages. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > > _______________________________________________ > 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 > > > > > > _______________________________________________ > 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 >
- Re: [nvo3] New Version Notification for draft-fan… Xialiang (Frank)
- Re: [nvo3] New Version Notification for draft-fan… Tom Herbert
- Re: [nvo3] New Version Notification for draft-fan… Carlos Pignataro (cpignata)
- Re: [nvo3] New Version Notification for draft-fan… Tom Herbert
- Re: [nvo3] [L2tpext] New Version Notification for… Carlos Pignataro (cpignata)
- Re: [nvo3] [L2tpext] New Version Notification for… Tom Herbert
- Re: [nvo3] New Version Notification for draft-fan… Xialiang (Frank)
- Re: [nvo3] New Version Notification for draft-fan… Xialiang (Frank)
- Re: [nvo3] New Version Notification for draft-fan… Anton Ivanov (antivano)
- Re: [nvo3] [L2tpext] New Version Notification for… Carlos Pignataro (cpignata)
- Re: [nvo3] New Version Notification for draft-fan… Tom Herbert
- Re: [nvo3] New Version Notification for draft-fan… Anton Ivanov (antivano)