Re: [IPsec] I-D Action: draft-ietf-ipsecme-rfc8229bis-06.txt

Valery Smyslov <smyslov.ietf@gmail.com> Tue, 17 May 2022 12:07 UTC

Return-Path: <smyslov.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 62BB9C15949C; Tue, 17 May 2022 05:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68E9ZD_JFqBM; Tue, 17 May 2022 05:07:55 -0700 (PDT)
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48E04C159485; Tue, 17 May 2022 05:07:55 -0700 (PDT)
Received: by mail-ej1-x635.google.com with SMTP id ch13so34181808ejb.12; Tue, 17 May 2022 05:07:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=cCmhTdwD8goctaHr3K1nQQZioWeTFxtxRdMOfxRqywY=; b=hPCMjZKnIf5M/5du6LkmdQj8T8snOHioVi6roufl5MOs4DJecOCEjJoE/QrMmtAiG3 axZ0gjAWZTY5Jg9+LMzM+76KLz0fO6lh7yteeooRU5CNbwskCa3f5DOWlCS1epUefAGJ icpMgcL4NoLjiVAqy7OTDAIqBmx+DRxUEG8+ZhYGUPQeg/OtFegwrVH6zhJSZi5zEx2e J6SJs6xsO70SEUCZns2LUcqVEMV6a6nTNtNQIetjF3zb0SA+6QY2/vV6W1bgW1TscMID jeUTU0Wdr4De8vQvXcOlRLUJd2BxLZop79pdyLDymJhLTMkCLa2sXv6/qNVz6qq8uOk6 +Lqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=cCmhTdwD8goctaHr3K1nQQZioWeTFxtxRdMOfxRqywY=; b=07tHE3X0kq160o/xbTbTE6rR0GuJOY62eOURQTxZv6hJCZlA2UXcOEdj/aiLZ7RQDs /bo3aDiZ5bNpL9yVlNw4FZV8F/EhcIJzRqAgBkLtbbeI3MBWxIz0B+c+ZOyD6iwRw8Bp lHM0CAVCKZk59+EVTNFEyld4i1oy8iIwNOycGWopGb4Nd/3lS0Xu/ot9xYt32ZGCCx2F ZXcHtVnRpp7IWAssJmhDw9eg+xnYfR5KGeAPu7r/CziYpMdp78WVv3Kg3tmKvjGG2awf z4rFCqz8191DpC/34lCF+FhwWDDQSymfIaJVDiAVYcyujZglkcrAjlbZ3ObUBd8i44CT YMww==
X-Gm-Message-State: AOAM531UEcr7IWhCvIajxmjCajjZMsKwkJLKiDHHSDT6Vmnh5Scoiz/t bGR2aLlUzBx8vY6OlTy7EcqSuIuHer8=
X-Google-Smtp-Source: ABdhPJwqqXhx4/mtrLu2I/KMk54r+WD3agwUYhtU447Oi+s9J5O9OOU56iLB11S5hwxvUjS6Nuy9Bw==
X-Received: by 2002:a17:906:8301:b0:6e4:896d:59b1 with SMTP id j1-20020a170906830100b006e4896d59b1mr18773224ejx.396.1652789273079; Tue, 17 May 2022 05:07:53 -0700 (PDT)
Received: from buildpc ([93.188.44.204]) by smtp.gmail.com with ESMTPSA id e7-20020a170906844700b006f3ef214e24sm954144ejy.138.2022.05.17.05.07.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 May 2022 05:07:52 -0700 (PDT)
From: Valery Smyslov <smyslov.ietf@gmail.com>
To: ipsec@ietf.org
Cc: tpauly@apple.com, 'Roman Danyliw' <rdd@cert.org>, ipsecme-chairs@ietf.org
References: <165278873555.62264.12308322360275048978@ietfa.amsl.com>
In-Reply-To: <165278873555.62264.12308322360275048978@ietfa.amsl.com>
Date: Tue, 17 May 2022 15:07:50 +0300
Message-ID: <341f01d869e6$bcb76600$36263200$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHgF2gXyuLU503cYhofCsIyNTtYgK0TnGow
Content-Language: ru
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/oeyBMfKf0U6U-EBVq6A9oneMeaY>
Subject: Re: [IPsec] I-D Action: draft-ietf-ipsecme-rfc8229bis-06.txt
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 17 May 2022 12:07:57 -0000

Hi,

a new version of rfc8229bis draft is posted.

This version addresses the issues raised by AD review.

Regards,
Tommy & Valery.

> -----Original Message-----
> From: IPsec [mailto:ipsec-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Tuesday, May 17, 2022 2:59 PM
> To: i-d-announce@ietf.org
> Cc: ipsec@ietf.org
> Subject: [IPsec] I-D Action: draft-ietf-ipsecme-rfc8229bis-06.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IP Security Maintenance and Extensions WG of the IETF.
> 
>         Title           : TCP Encapsulation of IKE and IPsec Packets
>         Authors         : Tommy Pauly
>                           Valery Smyslov
> 	Filename        : draft-ietf-ipsecme-rfc8229bis-06.txt
> 	Pages           : 31
> 	Date            : 2022-05-17
> 
> Abstract:
>    This document describes a method to transport Internet Key Exchange
>    Protocol (IKE) and IPsec packets over a TCP connection for traversing
>    network middleboxes that may block IKE negotiation over UDP.  This
>    method, referred to as "TCP encapsulation", involves sending both IKE
>    packets for Security Association establishment and Encapsulating
>    Security Payload (ESP) packets over a TCP connection.  This method is
>    intended to be used as a fallback option when IKE cannot be
>    negotiated over UDP.
> 
>    TCP encapsulation for IKE and IPsec was defined in RFC 8229.  This
>    document updates the specification for TCP encapsulation by including
>    additional clarifications obtained during implementation and
>    deployment of this method.  This documents obsoletes RFC 8229.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ipsecme-rfc8229bis/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-ipsecme-rfc8229bis-06
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ipsecme-rfc8229bis-06
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec