[bess] Can we have the IPSEC related drafts discussion before Friday during IETF 105?

Linda Dunbar <linda.dunbar@futurewei.com> Mon, 01 July 2019 16:04 UTC

Return-Path: <linda.dunbar@futurewei.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB86A12024A; Mon, 1 Jul 2019 09:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 sYyYcCGWJkNl; Mon, 1 Jul 2019 09:04:08 -0700 (PDT)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-eopbgr720136.outbound.protection.outlook.com [40.107.72.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A59A61200A3; Mon, 1 Jul 2019 09:04:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0xN+6ofT0Q/tnkuukTYXpZhZ8QOKCTuF0EDMal2tWVw=; b=Sn/Gn90oOMFS9SGU34pOnFn7GMqEMuutF1LgfO/MHiiOtwosuYG8GhEZ6SFfUgziLqzayYkuwhBlG5sAHyicr8nGgxpppGPUXKtjm8Qf+Tc5a4b7h+v/mC5pGu3cKHm59XHKpha3luLKxOkolc2ua9TAvImluWhVV76Tj4dpTtw=
Received: from MN2PR13MB3582.namprd13.prod.outlook.com (10.255.238.139) by MN2PR13MB2781.namprd13.prod.outlook.com (20.178.253.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.12; Mon, 1 Jul 2019 16:04:03 +0000
Received: from MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::a8cd:e9ef:5219:67ea]) by MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::a8cd:e9ef:5219:67ea%6]) with mapi id 15.20.2052.010; Mon, 1 Jul 2019 16:04:03 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>, "bess@ietf.org" <bess@ietf.org>, Paul Wouters <paul@nohats.ca>, Yoav Nir <ynir.ietf@gmail.com>
Thread-Topic: Can we have the IPSEC related drafts discussion before Friday during IETF 105?
Thread-Index: AdUwJlzBgqPG/uWTROC99JM1h8rmCw==
Date: Mon, 1 Jul 2019 16:04:03 +0000
Message-ID: <MN2PR13MB3582020B762959BB57A80CD185F90@MN2PR13MB3582.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=linda.dunbar@futurewei.com;
x-originating-ip: [12.111.81.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: de3c331d-c780-46fa-7fae-08d6fe3dbd1c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB2781;
x-ms-traffictypediagnostic: MN2PR13MB2781:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR13MB278103F255DCEE3B47977E5E85F90@MN2PR13MB2781.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00851CA28B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(39840400004)(396003)(366004)(376002)(346002)(189003)(199004)(9686003)(6306002)(54896002)(55016002)(7696005)(44832011)(66066001)(14454004)(76116006)(102836004)(53936002)(2501003)(6436002)(186003)(6506007)(68736007)(26005)(33656002)(53546011)(5660300002)(3846002)(6116002)(99286004)(7736002)(790700001)(478600001)(64756008)(316002)(110136005)(8676002)(81166006)(66946007)(86362001)(81156014)(66446008)(73956011)(66476007)(66556008)(2201001)(74316002)(71190400001)(8936002)(476003)(486006)(71200400001)(14444005)(256004)(25786009)(52536014)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB2781; H:MN2PR13MB3582.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: efpmZHtn8JqUVnJfcqQ+SC/oDFnaHYlPqP5AqpG/PujsxpdNOu+ogCCcUahiOpxm/aigcOt4euzbVU2vUwC08o4qstRpApKRSLeUASCIfHdUASf1mqULrgwBlLj8E5xgyj9fWrfaDsHbWS4Jv9M+fpAd7s/oEhh2GUkMyWCN/foj8lyFn+DF7sPzYROsWgIwb3YpjyD8kJwQsTt4VZ9TVSMYnCrJHRWoNVDv+BZRReKkYh5tIhCTPiZtDLYFuZElZlofFfmvDF0YQDsbPWFcTIrhtdSKCYuf3BlomxsDRHUlSR8/Aw+ns92X50iy+2yXm+XKLeRiFEl0mKi9cXFw3B/h0dZouUo2EvC7akH1o2Pjm7HKNr3qzJwUwuFcNOeMOTRtMbkdBmR/mq+lveg6P/DK2SKepYSKlqR1sqY5Y/A=
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB3582020B762959BB57A80CD185F90MN2PR13MB3582namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: de3c331d-c780-46fa-7fae-08d6fe3dbd1c
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Jul 2019 16:04:03.3918 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ldunbar@futurewei.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB2781
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/N6PHd5YV4LeEyGnJsTkaQ97WXGk>
Subject: [bess] Can we have the IPSEC related drafts discussion before Friday during IETF 105?
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2019 16:04:11 -0000

Hope we can have a face to face meeting discussing IPSEC related drafts in IETF105.
I have hard conflict for Friday July 26.

Can we have the discussion anytime before Friday during IETF105?

Thank you very much.

Linda Dunbar

From: Idr <idr-bounces@ietf.org> On Behalf Of Susan Hares
Sent: Monday, June 10, 2019 2:14 PM
To: idr@ietf.org; bess@ietf.org
Subject: [Idr] Issue 1: IPSEC related drafts

Greetings:

At IETF 104, we consider BGP VPNs supporting asking for TLVS in draft-ietf-idr-tunnel-encaps.    After hearing all the discussion, the BESS, IDR and I2RS WG chairs discussed what to do with the following

Drafts considered:

  *   draft-sajassi-bess-secure-evpn-01.txt,
  *   draft-hujun-idr-bgp-ipsec-00.txt,
  *   draft-dunbar-idr-sdwan-port-safi-01.txt
relating drafts/ Supporting drafts:

  *   draft-carrell-ipsecme-controller-ike-00.txt
  *   draft-ietf-i2nsf-sdn-ipsec-flow-protection-04.txt
  *   draft-ietf-idr-tunnel-encaps-12.txt
Basic topologies:
                       Ipsec tunnels
     [rtrA] -------------------- [rtrB]
         |     \                           /      |
         |       \ -- RR1 -------/     | ipsec tunnels
         |    / -----| |------\         |
     [rtrC]------------------- [rtrD]


The decision is that

  *   TLVs mechanisms for new TLVS related draft-ietf-idr-tunnel-encaps should be moved to drafts with just the mechanisms.
     *   All three mechanisms could be included in the TLVs or portions.
     *   The use case and the SA mechanisms can stay in BESS or IDR (depending on what is appropriate).
  *   The RTG Chairs are not experts on Security associations, so that we will try to schedule a unique session at IETF 105 where security experts can help the RTG chairs (BESS, IDR) review the Security association mechanisms.
     *   We'd love to have the second co-chair of I2NSF (Yoav NIR) and someone from IPSECME.
     *   We'll invite IPSEC experts.
     *   We encourage the authors of the 3 drafts to attend this session in IETF 105 and present their security-association mechanisms.
  *   The NLRI/SAFI in draft-dunbar-idr-sdwan-port-safi is unique and can be requested as IDR or ISE draft.
This email has two request:

  *   WG or authors please send any questions to Susan Hares,
  *   The IDR WG is encouraged to discuss requirements or needs in preparation for the TLV selection, and
  *   Please help me secure 2 IPSEC experts to attend this session.

Susan Hares