Re: [IPsec] Is there any drafts or RFCs on solutions to RFC 7018 Auto-Discovery VPN Problem Statement and Requirements?

"vishwas.ietf" <vishwas.ietf@gmail.com> Mon, 18 May 2020 17:31 UTC

Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2B903A0A00 for <ipsec@ietfa.amsl.com>; Mon, 18 May 2020 10:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 oTLebpkQ2KgC for <ipsec@ietfa.amsl.com>; Mon, 18 May 2020 10:31:48 -0700 (PDT)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 1C5D13A09FF for <ipsec@ietf.org>; Mon, 18 May 2020 10:31:48 -0700 (PDT)
Received: by mail-pl1-x631.google.com with SMTP id t7so4517682plr.0 for <ipsec@ietf.org>; Mon, 18 May 2020 10:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:savedfromemail:date:subject:in-reply-to:importance:from :to:mime-version; bh=65HjsV8nRih6gplX6b+oDXgp4/NSu1i9aYgLfv1l6LA=; b=dj3H68dXC8QCX2JaUHQvGY7svkcuDyYELTfdSUN9B/3dYpip5XbPEfltES/QejG4Ay VP2B757/55PPCi/CxThZMdppTDwAopHSDm8vVeW7CKzlcKQ++Xz+GzwlimoponEGND1H aRJelHBgR98FUmPieoNiG24z8MePCtGTlxsrJvBxfqiHfeyfLOgv3fi9OKypuJouMByb Q7ZxbL90KhXK7dl67YIdT+gDXpUlVQm7+Lzc0VQOLjKH893CQap3+UfGwB/WSZ7kfbuL t5iiDu6nzDfNawXhE+BJmdaKfgWaIPkYahWhKrslGic1bPHPUSOFcrIq4a0ox7lOh8av JJKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:savedfromemail:date:subject :in-reply-to:importance:from:to:mime-version; bh=65HjsV8nRih6gplX6b+oDXgp4/NSu1i9aYgLfv1l6LA=; b=dzrU3iwOiivK5+BdypquJYCYnyHtwqyEotpXcKNvZJFd5Th1c0Ogfu4PlgTGcWqySX 8eCB2IM6N4FTUXerA6sSls23c45zO23hJsaNPPmZlfCwzZts+zbn7tccOKbScO56vrNW wNVemWjt/vHWBkzt7l1yNBIcG9CmDJl3OkkgzUKrULgfVZQiyocqKkvWCraM34yrgcie uGWldtPgggDcBVP7NUoa7W1zYBp2toaRiT+amB1nzRSZ+C63CYrG+/1L0msFPn5Nuvkq GcsT1xyC29ipb7RU5afh7xJqrPIVI1fF4axv+bHS0EchNwaIIu6mYpjbAVJ5Cd3x8D2o bPQQ==
X-Gm-Message-State: AOAM533lFd8Nlmx+lTgwEbQqEVSfK1TNcYmxfF1ZBwOzkkw+svAlMPfM RMiLY7PkWIg8YG3JWCxYnhc=
X-Google-Smtp-Source: ABdhPJzY6iDKuHqCO7a79RfDR5ImaPw96dq+ajufbsa4mFXidaIzWIiakb9/FMsE4UaVSd64FqGcNA==
X-Received: by 2002:a17:902:502:: with SMTP id 2mr12230695plf.134.1589823107562; Mon, 18 May 2020 10:31:47 -0700 (PDT)
Received: from ?IPv6:2601:647:5180:4720:557d:60fd:bd14:cf32? ([2601:647:5180:4720:557d:60fd:bd14:cf32]) by smtp.gmail.com with ESMTPSA id l9sm9518791pfd.5.2020.05.18.10.31.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 May 2020 10:31:46 -0700 (PDT)
Message-ID: <5ec2c682.1c69fb81.4aa28.d34b@mx.google.com>
SavedFromEmail: vishwas.ietf@gmail.com
Date: Mon, 18 May 2020 10:31:45 -0700
In-Reply-To: <SN6PR13MB233450103D13365702E14D7A85B80@SN6PR13MB2334.namprd13.prod.outlook.com>
Importance: normal
From: "vishwas.ietf" <vishwas.ietf@gmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>, "ipsec@ietf.org WG" <ipsec@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_45472275879500"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/W3JVCvKzGQSog88JbRpSx4Htgy4>
Subject: Re: [IPsec] Is there any drafts or RFCs on solutions to RFC 7018 Auto-Discovery VPN Problem Statement and Requirements?
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2020 17:31:50 -0000

Linda,There were 4 drafts written based on the existing state of art at that time.We created one as HP and H3C about 6 years back. Cisco had one too and so did others.https://tools.ietf.org/html/draft-mao-ipsecme-ad-vpn-protocol-02-Vishwas
-------- Original message --------From: Linda Dunbar <linda.dunbar@futurewei.com> Date: 5/18/20  10:13 AM  (GMT-08:00) To: "ipsec@ietf.org WG" <ipsec@ietf.org> Subject: [IPsec] Is there any drafts or RFCs on solutions to RFC 7018 Auto-Discovery VPN Problem Statement and Requirements? 

We are experiencing the problems described in RFC 7018 (Auto-Discovery VPN Problem Statement and Requirements), i.e. the  problem of enabling a large number of peers (primarily Gateway) to communicate directly using IPsec to protect the
 traffic between them. 
 
Is there any drafts describing the solutions to the problems identified by RFC7018?

 
Thank you very much, 
 
Linda Dunbar