IETF Logo Mail Archive

Re: [IPsec] Clarifications and Implementation Guidelines for using TCP Encapsulation in IKEv2 draft

Benjamin Kaduk <kaduk@mit.edu> Sat, 09 May 2020 00:00 UTC

Return-Path: <kaduk@mit.edu>
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 2C8723A011F; Fri, 8 May 2020 17:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 kDzDzaMfQiif; Fri, 8 May 2020 17:00:24 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 CA0313A0406; Fri, 8 May 2020 17:00:23 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 04900CDT022893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 8 May 2020 20:00:14 -0400
Date: Fri, 08 May 2020 17:00:12 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Valery Smyslov <smyslov.ietf@gmail.com>
Cc: 'Yoav Nir' <ynir.ietf@gmail.com>, ipsec@ietf.org, ipsecme-chairs@ietf.org, 'Tommy Pauly' <tpauly@apple.com>
Message-ID: <20200509000012.GX27494@kduck.mit.edu>
References: <0b5201d61d43$0f16dfe0$2d449fa0$@gmail.com> <53F12987-8F6B-46B7-831C-A4185E2B3805@apple.com> <007d01d61e3c$c43a8990$4caf9cb0$@gmail.com> <69538081-E679-4BE4-A818-6AD424ECBCF0@gmail.com> <20200503224914.GG27494@kduck.mit.edu> <004a01d621da$3ebab960$bc302c20$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <004a01d621da$3ebab960$bc302c20$@gmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/8BDWky7_8-C18wNz0FQmW8XnmlM>
Subject: Re: [IPsec] Clarifications and Implementation Guidelines for using TCP Encapsulation in IKEv2 draft
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: Sat, 09 May 2020 00:00:48 -0000

On Mon, May 04, 2020 at 09:07:08AM +0300, Valery Smyslov wrote:
> Hi Ben,
> 
> > On Wed, Apr 29, 2020 at 10:54:26PM +0300, Yoav Nir wrote:
> > > [With chair hat on]
> > >
> > > Yes, the charter says that we are to make a guidance document. If the
> > working group feels that it’s better to put the specification and guidance in a
> > single document, we can work on that and clear it with the ADs.
> > >
> > > Charters can be modified.
> > 
> > FWIW I don't see a particular need to recharter to do an 8229bis.
> 
> Can you please clarify for those of us who (like me) are not native speakers:
> do you think that the current charter allows to do an 8229bis without need to recharter
> or do you think there is no need to do an 8229bis and thus no need to recharter?

Sorry!  I think that the current charter allows us to do an 8229bis without
additional rechartering.

-Ben

v2.23.0 | Report a Bug | By Email