Re: [nvo3] New Version Notification for draft-mglt-nvo3-geneve-security-requirements-06.txt

Daniel Migault <daniel.migault@ericsson.com> Mon, 11 March 2019 06:42 UTC

Return-Path: <mglt.ietf@gmail.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 3FA7413108C for <nvo3@ietfa.amsl.com>; Sun, 10 Mar 2019 23:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 DyPE4rTFmuPT for <nvo3@ietfa.amsl.com>; Sun, 10 Mar 2019 23:42:16 -0700 (PDT)
Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) (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 93074131078 for <nvo3@ietf.org>; Sun, 10 Mar 2019 23:42:15 -0700 (PDT)
Received: by mail-lj1-f177.google.com with SMTP id d24so2947002ljc.12 for <nvo3@ietf.org>; Sun, 10 Mar 2019 23:42:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wu08rr9xVBQuUKpTHzwQmWYk+refG9QgYPNFdw9EdUU=; b=CfXHXvD4WcyXHTBPiAlp/iwODTZNPplHPNpTPfaCr9uBZPAxxT/WDBicel2431uAi1 8N7dVrrth8p04Ykp8D6k32y4mWIjibN2GBN+hnXrTisKQAtHOkF7XRoyXUl/YdplyjOH VIPNYZROF8LfbrDZgZfS6bjrw3ci0spmHFxKyg/X0gZLUwqc8IzrBWD4EvqqWCDIJ4Xs 65UY5yIYockK+xcGrd3bxnWZoNGO0m9Y47pGlnuB85qiZHKnx2zX8364u9DOMdZSfHEA gXfSoMxoyaELFBmrRVC2xBTDfW42AFPY5rGrmheXAuEFOB6WQ2xYdG0FUPhslFwZA0M2 takg==
X-Gm-Message-State: APjAAAU0jzlBNhHZH2406sZMMBj4hkR9gR5h8ikNmed1EUi5MSxPYRmI PFxF9qFx925nOhnuKPFa5uaBdYQ96RKijvewapE=
X-Google-Smtp-Source: APXvYqy316YKWw13lko7LbD5Cn45jROEBB6zlks3ceEmnhSscrLsi0ZsDJ5HzUKGVG1rXNDOmqBmVz5dT6+CTPIH9VA=
X-Received: by 2002:a2e:91d4:: with SMTP id u20mr8909357ljg.54.1552286533590; Sun, 10 Mar 2019 23:42:13 -0700 (PDT)
MIME-Version: 1.0
References: <155140820316.28736.16220301811782333020.idtracker@ietfa.amsl.com> <DM6PR15MB3098714F78AD24077DC4254AE3760@DM6PR15MB3098.namprd15.prod.outlook.com> <C5A274B25007804B800CB5B289727E35904EDDE5@ORSMSX111.amr.corp.intel.com>
In-Reply-To: <C5A274B25007804B800CB5B289727E35904EDDE5@ORSMSX111.amr.corp.intel.com>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Mon, 11 Mar 2019 02:42:01 -0400
Message-ID: <CADZyTk=s73qqFbhNm5JVOj2rdf-W-VpBObNyz7h1Jo4MWczvzg@mail.gmail.com>
To: "Ganga, Ilango S" <ilango.s.ganga@intel.com>
Cc: "nvo3@ietf.org" <nvo3@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006ca2590583cbdff9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/00n_96CS0qatTxpZS8co17xZBqU>
Subject: Re: [nvo3] New Version Notification for draft-mglt-nvo3-geneve-security-requirements-06.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 06:42:18 -0000

Hi Illango,

Though we would appreciate your comment on the new version. We would also
appreciate you go through the issues [1] we opened and answered based on
your previous comments. More specifically, in case the issue has not been
addressed, we would be able to keep the discussion based on the provided
responses rather than re-opening parallel issues. We believe that would be
beneficial to reach consensus.

Yours,
Daniel


[1] https://github.com/mglt/draft-mglt-nvo3-geneve-security-requirements
/issues


On Sat, Mar 2, 2019 at 10:29 PM Ganga, Ilango S <ilango.s.ganga@intel.com>
wrote:

> Hi Daniel,
>
> I quickly glanced through the document, the draft still makes assumptions
> and imposes requirements that is unsupported by Geneve architecture. We had
> provided this input on the previous draft version. However this is still
> maintained in this version. The new draft was posted 2 days ago, I will
> review the document in detail and provide my feedback.
>
> Regards,
> Ilango
>
>
>
> -----Original Message-----
> From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Daniel Migault
> Sent: Thursday, February 28, 2019 6:48 PM
> To: nvo3@ietf.org
> Subject: [nvo3] FW: New Version Notification for
> draft-mglt-nvo3-geneve-security-requirements-06.txt
>
> Hi,
>
> Please find an update of the draft. We considered the feed back received
> during the meeting in Bangkok as well as the comments from Magnus.
>
> So far no issue has been raised that could prevent the draft from being
> adopted, and we believe the draft can be adopted.
>
> Yours,
> Daniel
>
> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> Sent: Thursday, February 28, 2019 9:43 PM
> To: Sami Boutros <boutros@vmware.com>; Dan Wings <dwing@vmware.com>; Dan
> Wing <dwing@vmware.com>; Daniel Migault <daniel.migault@ericsson.com>;
> Suresh Krishnan <suresh@kaloom.com>
> Subject: New Version Notification for
> draft-mglt-nvo3-geneve-security-requirements-06.txt
>
>
> A new version of I-D, draft-mglt-nvo3-geneve-security-requirements-06.txt
> has been successfully submitted by Daniel Migault and posted to the IETF
> repository.
>
> Name:           draft-mglt-nvo3-geneve-security-requirements
> Revision:       06
> Title:          Geneve Security Requirements
> Document date:  2019-02-28
> Group:          Individual Submission
> Pages:          26
> URL:
> https://www.ietf.org/internet-drafts/draft-mglt-nvo3-geneve-security-requirements-06.txt
> Status:
> https://datatracker.ietf.org/doc/draft-mglt-nvo3-geneve-security-requirements/
> Htmlized:
> https://tools.ietf.org/html/draft-mglt-nvo3-geneve-security-requirements-06
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-mglt-nvo3-geneve-security-requirements
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-mglt-nvo3-geneve-security-requirements-06
>
> Abstract:
>    The document defines the security requirements to protect tenants
>    overlay traffic against security threats from the NVO3 network
>    components that are interconnected with tunnels implemented using
>    Generic Network Virtualization Encapsulation (Geneve).
>
>    The document provides two sets of security requirements: 1.
>    requirements to evaluate the data plane security of a given
>    deployment of Geneve overlay.  Such requirements are intended to
>    Geneve overlay provider to evaluate a given deployment.
>    2. requirement a security mechanism need to fulfill to secure any
>    deployment of Geneve overlay deployment
>
>
>
>
> 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
>