Re: [dispatch] IETF 113 - do you have something for DISPATCH?

worley@ariadne.com Sun, 20 February 2022 14:43 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B0A23A11F1 for <dispatch@ietfa.amsl.com>; Sun, 20 Feb 2022 06:43:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.983
X-Spam-Level:
X-Spam-Status: No, score=-0.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 LCwlE1-5KUWJ for <dispatch@ietfa.amsl.com>; Sun, 20 Feb 2022 06:43:45 -0800 (PST)
Received: from resqmta-c1p-023464.sys.comcast.net (resqmta-c1p-023464.sys.comcast.net [IPv6:2001:558:fd00:56::b]) (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 3DB3A3A11EB for <dispatch@ietf.org>; Sun, 20 Feb 2022 06:43:44 -0800 (PST)
Received: from resomta-c1p-022589.sys.comcast.net ([96.102.18.236]) by resqmta-c1p-023464.sys.comcast.net with ESMTP id LmThnhmyMbn0tLnR4nvUJS; Sun, 20 Feb 2022 14:43:38 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1645368218; bh=f/RgjePpuP//4kBuZR8uCMAfEzuKK0fW4ei0HCjzrX0=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=qD7241mQi6QyC/z8qJUPNvBCY498pcxYCxje/RKbxuKHgklUGqP/yCoIYMpuyfTXB YrCeUAofApWbQ6gdkKAnsDTZi3fFBw8iQ/AzusubkV6v0hQEtLr7+VN/EgGze+tLM2 62DLZjepvzkiRFF0zRtHjyD1v0CdhTr4utYB3qvhGfd4s0qvU+KXcesF2VAsn5f6sv zk12188DAqjU+sBC7RpSkECt/dE916ZIMxUTsSGf1Sxfdc1p3Q+YFiLLhSoc3Vf6oA e3v4VFiEwLyomi+UFmHem1cuhcaQoBONCmS6LmJRbUXIA7bAcBmlg8eK3hLvHD+lqx N0OZTt5NUHt8A==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::2f20]) by resomta-c1p-022589.sys.comcast.net with ESMTPA id LnR2nHqmrGBB2LnR2nCK7x; Sun, 20 Feb 2022 14:43:37 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 21KEhZAu105536 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Sun, 20 Feb 2022 09:43:35 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 21KEhZk6105533; Sun, 20 Feb 2022 09:43:35 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Anton Tveretin <tveretinas@yandex.ru>
Cc: kirsty.ietf@gmail.com, dispatch@ietf.org
In-Reply-To: <189931645313194@mail.yandex.ru> (tveretinas@yandex.ru)
Sender: worley@ariadne.com
Date: Sun, 20 Feb 2022 09:43:35 -0500
Message-ID: <87bkz18up4.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/WppH9jPHCu7-FtK0BXGzx9xi1Zg>
Subject: Re: [dispatch] IETF 113 - do you have something for DISPATCH?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Feb 2022 14:43:50 -0000

Anton Tveretin <tveretinas@yandex.ru> writes:
> I wrote two I-Ds, namely, draft-tveretin-dispatch-l2tp-sdp-02 [...]

For reference:  draft-tveretin-dispatch-l2tp-sdp-02.txt is "This
document registeres new media type (application/l2tp) to be used with
SDP, and clarifies procedure to be used by peers for L2TP tunnels."

As always, the question is "How much support do you have?"  That has a
lot of aspects.  One is, "Are there people interested in working on this
document?"  Another is "Are there people interested in implementing
this?", which is closely related to, "Do people feel a unsatisfied need
that this would satisfy?"

Often the answers aren't well-correlated with, "Would this be a good
idea in principle?"

I'm reminded of when I did some work on "Happy Earballs", working out
how a SIP client should attempt to contact a SIP server in the general
case when the server's hostname resolves into multiple IPv4 and IPv6
addresses of unknown reachability.  The problem had even been raised by
some of the long-term experts in SIP.  But nobody was interested in
actually implementing it, which I strongly suspect is because in
practice SIP is used to replicate traditional telco networks, with
tightly controlled signaling paths in a network that has an overall
architecture -- if a client knows of a server's name, the architecture
ensures the addresses will connect.  (Which is much different from the
typical HTTP case.)

So the first step is what is called "socializing" your proposal, talking
to people in a fairly informal way to determine what interest you can
raise in the work.

Dale