IETF Logo Mail Archive

Re: [tcpm] Request for feedback on WG adoption of draft-scharf-tcpm-yang-tcp-04

Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 07 April 2020 03:46 UTC

Return-Path: <mjethanandani@gmail.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A96E83A14AB; Mon, 6 Apr 2020 20:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 j1Ua4uTJO9rD; Mon, 6 Apr 2020 20:46:34 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 1816C3A14A4; Mon, 6 Apr 2020 20:46:34 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id c5so1076610pgi.7; Mon, 06 Apr 2020 20:46:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=rmyFQMPBJs3hnhtpJhpjNGntLBQK/gpnEdg1ErWXysM=; b=oC0NUYfj4ekqzcC/XfzvxqEFnF2I67Y3PoegYSes5d5XiKdKeUAb/wjRoYbBt1uegA FB1RT7VtwntgsJEXikJoL5PxTMC5UjDwG/Gps1hYO7dPE0k2CgaIMpaSkW8EDjGHhpEk bQjXJXbFSam8SxcXRlFrW+oiAjNGyEBrNcs1we+KP7/lUKxwcMGfihq0cQUqsNjTqEKv UUxcVcrCrS3IduWItTdYivIENrDUDgbHh6V9gao1q76YShbDp8mjEerCTBIWLt9r+rAs bw7otnlZezwNwAc00RXx07C+LA4Gft5f59GIVtuYkqI+g3E+8ToHhCNteKU1kZdORuO6 iT2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=rmyFQMPBJs3hnhtpJhpjNGntLBQK/gpnEdg1ErWXysM=; b=XIz+YZnGiEmaiz7z576HvNAGL/MMsMuSuc+SHDpn6wExOqojx9hWqdhlme0RpXR5yJ 0Q3EK7AFMRgXv6DIkqan9SSt0q2rqcNU/4LDJ26BcotBhWo1f7jbP4sOis3H6uqn1VEo 3fWo4gev/PpwI0atHucDlHjIHkN0BuY8qigt/VyGQbheQ5hYdq5r2QdNF+I5DUwurlHj dXgoJAG84aAq9tZ3Ealu/kb0V3RAMWbRSbazQ0ZbeJ4Rna878cb19e3UEsKRMP72Gzsu UtloY1MGs+P/+J6ouWIitncboD+a1T+1n0HxplNtxGrYqgpifwdex5MpUJe9QxEJ8vsW L3vg==
X-Gm-Message-State: AGi0PuZ2gs6BfAc/PdW/l6KT0B4vtAnjM6mM9Z0gKq9jqkzVzL/3mA29 6h2kJ/un6SaLFk+JhmfEd30=
X-Google-Smtp-Source: APiQypIx/ciWDq7XVDNPyU2m6xqt8CpW1R/fCgbG9JH/ZadeuRlmpAmXXKDolFdSexMtqHlu6ZvhUA==
X-Received: by 2002:a63:330c:: with SMTP id z12mr32603pgz.415.1586231193431; Mon, 06 Apr 2020 20:46:33 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:28f4:f75f:dbc6:cd22? ([2601:647:5600:5020:28f4:f75f:dbc6:cd22]) by smtp.gmail.com with ESMTPSA id f15sm12972019pfq.100.2020.04.06.20.46.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Apr 2020 20:46:32 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <A38B6C49-ED38-4C02-ADCA-62A0085D1782@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AC3A04CB-D128-4FE0-B9EE-5A094B21ECAE"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\))
Date: Mon, 06 Apr 2020 20:46:30 -0700
In-Reply-To: <6EC6417807D9754DA64F3087E2E2E03E2DA3F971@rznt8114.rznt.rzdir.fht-esslingen.de>
Cc: Lars Eggert <lars@eggert.org>, Michael Tuexen <tuexen@fh-muenster.de>, tcpm IETF list <tcpm@ietf.org>, "draft-scharf-tcpm-yang-tcp@ietf.org" <draft-scharf-tcpm-yang-tcp@ietf.org>
To: Michael SCHARF <Michael.Scharf@hs-esslingen.de>
References: <6EC6417807D9754DA64F3087E2E2E03E2DA3F971@rznt8114.rznt.rzdir.fht-esslingen.de>
X-Mailer: Apple Mail (2.3445.9.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/cLHgT41Z0cPNn1pPOEE14BiLdxE>
Subject: Re: [tcpm] Request for feedback on WG adoption of draft-scharf-tcpm-yang-tcp-04
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2020 03:46:36 -0000

I agree with Michael here.

> On Mar 27, 2020, at 7:49 AM, Scharf, Michael <Michael.Scharf@hs-esslingen.de> wrote:
> 
> Regarding MD5, I get told that there is still running code and operational deployment, even if TCP-AO is getting traction. As users seem to ask for it, my proposal would be to add big warning signs that it is deprecated, i.e., TCP-AO should be used instead. On that aspect, the other authors could maybe also chime in.

The requirement to support MD5 stems from existing deployments of BGP that still use MD5 to secure the session. That is why the support for MD5 has been added to the BGP YANG model <https://tools.ietf.org/html/draft-ietf-idr-bgp-model-08>, using groupings defined by the YANG model in draft-scarf-tcpm-yang-tcp.

Cheers.

Mahesh Jethanandani
mjethanandani@gmail.com

v2.23.0 | Report a Bug | By Email