Re: [nvo3] FW: New Version Notification for draft-spallagatti-bfd-vxlan-03.txt
Shahram Davari <shahram.davari@broadcom.com> Mon, 23 May 2016 21:36 UTC
Return-Path: <shahram.davari@broadcom.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B396212D52A for <nvo3@ietfa.amsl.com>; Mon, 23 May 2016 14:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
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 Nt0Xj2CGyq3m for <nvo3@ietfa.amsl.com>; Mon, 23 May 2016 14:36:14 -0700 (PDT)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBFC112D59B for <nvo3@ietf.org>; Mon, 23 May 2016 14:36:13 -0700 (PDT)
Received: by mail-vk0-x22d.google.com with SMTP id r140so62782699vkf.0 for <nvo3@ietf.org>; Mon, 23 May 2016 14:36:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc; bh=/rVuy69PEfLhucizZGEJe+rq8r+DZ+SKfZOCcBy0swc=; b=LkpR5NX/9akfeEL6MvscuLIU82Tnj75uXrAybjmFO5oYWpOpZzycMoAhnGrg+Mvlax OJgeYCEmWlqFplBhDrNQX9/YtRrOMUwdHv8ZMupoSVoy5TMSTfmKvTcN7hidU9H87lPB kVYCIjU6r9kexPJPPAxdGkF8gsthW3pdcaSt4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc; bh=/rVuy69PEfLhucizZGEJe+rq8r+DZ+SKfZOCcBy0swc=; b=ZtCE6cUJVo43km+V80+p3LpE9sNrfD2jvlEom3fbJBIYOAQZAWzcivx+s4zoRaBbth Xn7JvEulMvstQMIy/hiSItDGQkJE3bqVIa4tj1xXk6qnbq8hEBqJxxPi0adhll97Mxbk mEQ2l3W9UfJu3tfDwpHsvfVJoLmPumz5CtO5iKM6ppDIq3r7ru/4/zyrs4qP8O3wIfR/ vYfWwJ/1SM3a1SK2J0zO5SeTvquFJlJTfAYguHnZHvNAE2kMI2Qvdo8f0kbYRYmMEEqO jUy1HAAkInp1MOi50C3yCoaYWrfJ1Ja09gFQjvrKTCabGt9TV4BjzLqTI/AtwX79TcFm tTwg==
X-Gm-Message-State: ALyK8tI6DvvrZSGd17QvfKhBnrotQQZKRBZC47TXXuaTU9co3BjX2sMzcVM0RmxBHmvgIIvhB+09cdPoa//EpCcc
X-Received: by 10.159.41.71 with SMTP id t65mr672523uat.22.1464039372696; Mon, 23 May 2016 14:36:12 -0700 (PDT)
From: Shahram Davari <shahram.davari@broadcom.com>
References: <20160416060248.17419.11591.idtracker@ietfa.amsl.com> <8f73ecae119843dcba447c54084c80f8@XCH-RCD-020.cisco.com> <D368DCC6.9B912%matthew.bocci@nokia.com> <CA+-tSzyJDPL=cUC7+vCC4zNeZ32CoaCi8Z3nwXgjJTt5oX+F8g@mail.gmail.com> <CA+RyBmW15=YevVtASA21m0cHnBkTxebbrWfE3945eurp-TdzQA@mail.gmail.com> <CA+-tSzyszEcQ9GbqXVJxx3puFkQUU0292uNaKZi39K-aq5QX=g@mail.gmail.com>
In-Reply-To: <CA+-tSzyszEcQ9GbqXVJxx3puFkQUU0292uNaKZi39K-aq5QX=g@mail.gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIMrdB/5G2mlwEeqn9cfT8TbquBagFzuiT1AuMuV+UChXSj3AGFqJCxApxeQaSe+Sdt0A==
Date: Mon, 23 May 2016 14:36:10 -0700
Message-ID: <00ac6551aee9714b93b8f94079b57cbf@mail.gmail.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>, Greg Mirsky <gregimirsky@gmail.com>
Content-Type: multipart/alternative; boundary="001a114b1c8ac00d4e0533893a2f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/nvo3/Er84SbRthnnwLaW-DrctlPoF6UI>
Cc: rtgwg-ooam-dt@ietf.org, rtg-bfd@ietf.org, nvo3@ietf.org
Subject: Re: [nvo3] FW: New Version Notification for draft-spallagatti-bfd-vxlan-03.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 23 May 2016 21:36:16 -0000
Anoop is correct. Thx SD *From:* nvo3 [mailto:nvo3-bounces@ietf.org] *On Behalf Of *Anoop Ghanwani *Sent:* Monday, May 23, 2016 2:35 PM *To:* Greg Mirsky *Cc:* rtgwg-ooam-dt@ietf.org; rtg-bfd@ietf.org; nvo3@ietf.org *Subject:* Re: [nvo3] FW: New Version Notification for draft-spallagatti-bfd-vxlan-03.txt Hi Greg, I think Larry has covered the points I was trying to bring up...if there's a MAC header present, then the VXLAN GPE next header has to indicate "Ethernet" rather than "IPv4" or "IPv6". Thanks, Anoop On Mon, May 23, 2016 at 12:47 PM, Greg Mirsky <gregimirsky@gmail.com> wrote: +BFD WG and RTGWG OOAM DT Hi Anoop, thank you for your review and the question. The scope of this draft is only for the VXLAN. The Overlay OAM Desing Team is working on the Requirements, Gap Analysis and, if there will be required, enhancements and/or new OAM protocols for BIER, NSH, VXLAN-GPE, GENEVE, and GUE, as defined in its charter. Would appreciate you review and comments of the two documents the OOAM-DT already presented in BA meeting: - OOAM Requirements - OAM for Overlay Networks: Gap analysis In the latter you'll find the example to demonstrate applicability of BFD Async mode in BIER domain. As we've discussed, other BFD may be applied to other overlay networks that I've listed above even though their method of indication OAM payload may be different from BIER. Would you agree, or suggest to have another example of BFD? Regards, Greg On Mon, May 23, 2016 at 12:26 PM, Anoop Ghanwani <anoop@alumni.duke.edu> wrote: Authors, In section 4.1, you have this: >>> Next Protocol Field in GPE header MUST be set to IPv4 or IPv6. ... The BFD packet MUST be carried inside the inner MAC frame of the VxLAN packet. The inner MAC frame carrying the BFD payload has the following format: >>> These two statements seem to contradict each other. If the GPE header indicates IPv4 or IPv6, then how can the BFD packet be encapsulated within a MAC frame? Can you please clarify? Thanks, Anoop On Mon, May 23, 2016 at 8:15 AM, Bocci, Matthew (Nokia - GB) < matthew.bocci@nokia.com> wrote: Folks Please could you direct any discussion on this draft to the NVO3 working group list. Regards Matthew On 18/04/2016, 07:54, "nvo3 on behalf of Vengada Prasad Govindan (venggovi)" <nvo3-bounces@ietf.org on behalf of venggovi@cisco.com> wrote: >Hello all, > The authors request comments on the draft below. >Thanks >Prasad > >-----Original Message----- >From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] >Sent: Saturday, April 16, 2016 11:33 AM >To: MALLIK MUDIGONDA (mmudigon) <mmudigon@cisco.com>; Basil Saji ><sbasil@juniper.net>; Greg Mirsky <gregory.mirsky@ericsson.com>; Vengada >Prasad Govindan (venggovi) <venggovi@cisco.com>; Juniper Networks ><santoshpk@juniper.net>; Sudarsan Paragiri <sparagiri@juniper.net>; >Santosh Pallagatti <santoshpk@juniper.net>; sajibasil@gmail.com ><sbasil@juniper.net> >Subject: New Version Notification for draft-spallagatti-bfd-vxlan-03.txt > > >A new version of I-D, draft-spallagatti-bfd-vxlan-03.txt >has been successfully submitted by Vengada Prasad Govindan and posted to >the IETF repository. > >Name: draft-spallagatti-bfd-vxlan >Revision: 03 >Title: BFD for VXLAN >Document date: 2016-04-15 >Group: Individual Submission >Pages: 9 >URL: >https://www.ietf.org/internet-drafts/draft-spallagatti-bfd-vxlan-03.txt >Status: >https://datatracker.ietf.org/doc/draft-spallagatti-bfd-vxlan/ >Htmlized: https://tools.ietf.org/html/draft-spallagatti-bfd-vxlan-03 >Diff: >https://www.ietf.org/rfcdiff?url2=draft-spallagatti-bfd-vxlan-03 > >Abstract: > This document describes use of Bidirectional Forwarding Detection > (BFD) protocol for VXLAN . > > > > > > >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] FW: New Version Notification for draft-spa… Vengada Prasad Govindan (venggovi)
- Re: [nvo3] FW: New Version Notification for draft… Bocci, Matthew (Nokia - GB)
- Re: [nvo3] FW: New Version Notification for draft… Anoop Ghanwani
- Re: [nvo3] FW: New Version Notification for draft… Greg Mirsky
- Re: [nvo3] FW: New Version Notification for draft… Greg Mirsky
- Re: [nvo3] FW: New Version Notification for draft… Shahram Davari
- Re: [nvo3] FW: New Version Notification for draft… Gregory Mirsky
- Re: [nvo3] FW: New Version Notification for draft… Larry Kreeger (kreeger)
- Re: [nvo3] FW: New Version Notification for draft… Shahram Davari
- Re: [nvo3] FW: New Version Notification for draft… Shahram Davari
- Re: [nvo3] FW: New Version Notification for draft… Anoop Ghanwani
- Re: [nvo3] FW: New Version Notification for draft… Shahram Davari
- Re: [nvo3] FW: New Version Notification for draft… Gregory Mirsky
- Re: [nvo3] FW: New Version Notification for draft… Anoop Ghanwani
- Re: [nvo3] FW: New Version Notification for draft… Gregory Mirsky