[nvo3-dt-encap] Question on NVO3 header security/integrity
Pankaj Garg <ipankajg@gmail.com> Wed, 11 January 2017 15:29 UTC
Return-Path: <ipankajg@gmail.com>
X-Original-To: nvo3-dt-encap@ietfa.amsl.com
Delivered-To: nvo3-dt-encap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ACDB1294C5 for <nvo3-dt-encap@ietfa.amsl.com>; Wed, 11 Jan 2017 07:29:28 -0800 (PST)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 te9tNwYtAFKp for <nvo3-dt-encap@ietfa.amsl.com>; Wed, 11 Jan 2017 07:29:26 -0800 (PST)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 DE206128BA2 for <nvo3-dt-encap@ietf.org>; Wed, 11 Jan 2017 07:29:25 -0800 (PST)
Received: by mail-oi0-x22b.google.com with SMTP id w204so92450055oiw.0 for <nvo3-dt-encap@ietf.org>; Wed, 11 Jan 2017 07:29:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=pwI/BQ/slcK4wdU8DMXMvRo74y5gDAbckz92hknz6Ng=; b=jD6ZMkH+jZM4v8mBOrFEZV89+O+Ly01vruSo03ZFVgWi7D+EgyR+sa490rEyojEf/a bZP/ahu8p/lBrXqjcnzzwhe7iDEZUlbNjhKKjhXU4x83a3j7EwhzP9uxvf2uEEuxcBc9 z/WtBmr6ml3aEtps7Sg+1QXa9uPUpVX5huftNePremqCMJi8RvefrX8SsR883levd6FL 3FecGhxDlgfWZPYXUF7RfkWxopS9Vv/Zbg2re2qnH/tdrGQ8z8UmPHj2+jay7s93UViP cGCOX9MycP4QIuZ72GC3RNYvnojtviCQEGg44w1kOfwGsCA3dKwsIA9Nx/VLFWCRg0f3 Y36A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pwI/BQ/slcK4wdU8DMXMvRo74y5gDAbckz92hknz6Ng=; b=NMA6G9aEI/+wOfisNEvg5bOEUL22i0iflpjBaJ//tQQCdgvwNOXiWRtSNjhpKAEXu5 C205LE8+t7DROHnAIugkXb1D3Fcgmnm+3VImb9zV7ollgtwK6iFOMP+ff/YsirEV58X6 mOct45wDVV594ONLiSPHTt7dXw5ZeMGS/csaM6cPOYV7874OS1ttd9YHDasFhXXKGPQ6 1yn7bo6hUtbySUe8lSgfj/ffK8O0BZdSRKGin/2Jmicjb+mg259mG/qZeSB9uvakxY8I S95HZV/vks3esNLfqrS7p1P6YkJZhai57xXB5MtIS8j2x34PSLj0KgqvqXICfjozzhN/ eVgg==
X-Gm-Message-State: AIkVDXLa9CsQg8nt+bMrIlUgnSdplanYCDKbXtAVWsWtLJceNB2ZSNhvOjrEk1FEkUeGs+xWNME8NhQ+yhrirA==
X-Received: by 10.202.223.11 with SMTP id w11mr4371754oig.69.1484148565346; Wed, 11 Jan 2017 07:29:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.31.66 with HTTP; Wed, 11 Jan 2017 07:29:24 -0800 (PST)
From: Pankaj Garg <ipankajg@gmail.com>
Date: Wed, 11 Jan 2017 07:29:24 -0800
Message-ID: <CAM-NV-rTfDgEn_tidYnX-xsQ1tNOt6nOUEE0tpH31ML4FcNGvw@mail.gmail.com>
To: tom@herbertland.com, nvo3-dt-encap@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3-dt-encap/88CQR7unL4g4LdnTa3XDdN21R94>
Subject: [nvo3-dt-encap] Question on NVO3 header security/integrity
X-BeenThere: nvo3-dt-encap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Private mailing list for internal NVO3 Encapsulation Design Team discussions <nvo3-dt-encap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3-dt-encap>, <mailto:nvo3-dt-encap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3-dt-encap/>
List-Post: <mailto:nvo3-dt-encap@ietf.org>
List-Help: <mailto:nvo3-dt-encap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3-dt-encap>, <mailto:nvo3-dt-encap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2017 15:29:28 -0000
Tom - Recently a design team for NVO3 was formed to propose one encapsulation for standardization by NVO3. As part of this design team, we have been looking for a use case of extensions around NVO3 header security/integrity. In the past, you have brought up this use case. Would you be able to describe this use case for us and how extensions can be used to enable this? We would appreciate this and use this example, along with 1-2 other examples to ensure that proposed encapsulation format meets the requirements of such use cases. Thanks Pankaj
- [nvo3-dt-encap] Question on NVO3 header security/… Pankaj Garg
- Re: [nvo3-dt-encap] Question on NVO3 header secur… Tom Herbert