Re: [MBONED] mboned: UDP port conflict mtrace/traceroute

Warren Kumari <warren@kumari.net> Wed, 11 September 2019 15:28 UTC

Return-Path: <warren@kumari.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACCFF120154 for <mboned@ietfa.amsl.com>; Wed, 11 Sep 2019 08:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=kumari-net.20150623.gappssmtp.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 2cODiSVYdqAr for <mboned@ietfa.amsl.com>; Wed, 11 Sep 2019 08:28:08 -0700 (PDT)
Received: from mail-qt1-x843.google.com (mail-qt1-x843.google.com [IPv6:2607:f8b0:4864:20::843]) (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 38EEE120152 for <mboned@ietf.org>; Wed, 11 Sep 2019 08:28:08 -0700 (PDT)
Received: by mail-qt1-x843.google.com with SMTP id j1so13004156qth.1 for <mboned@ietf.org>; Wed, 11 Sep 2019 08:28:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5EqMXbMBpbr6HrtbEtq02mpT3ZBp6V3smvfd3UyM4+E=; b=cUt5u2x6DzlYTUmxa/6RxyuwmyJJfqu8Vcq3yR5bGS5AC4xljDx494PthyFHONhVpk EctKMfmm4vnn07ZfyQxt7sMGL2Ouv7jy3G9gtiKxDoqRJ0WsZ/MkY/mBqNS9pLpEOnDQ oRAio4seGezNxK9L2jqr1GDnZUW2fNIqcejm/XINOXuMG8a2d/PEKjcRZAeQ0ktPHCnL NVGtmQQrTcrJelYc53YxvnGx4pGNJ5NyAuhpbgW92Tye3R023oc18mFgA7S3zHlhw8zA kFKr3tD9psZllbK7jB3kW8k98oR27ak0FiPH9MHvMjbNqXAEMQnsA6bh2u1gnMZl5kqo 5Y8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5EqMXbMBpbr6HrtbEtq02mpT3ZBp6V3smvfd3UyM4+E=; b=ffsv8u3lrQChFORM8jG/PfsWEOeYpzXXo/RTDS4mwypCO45N5B/tSN+Iljgf0Cn+iX vvSLNTAxtRak+1HkRgbVdah78Lex6f8INRYCCgAvDfr6LXJJGKHkkJYDulKLaXo8NYZ1 OX+H8IihmHW+53b1+DlbumPyqPJQPxwdXzhrIKhFoq0+dAmj3400wH3uCMm784jvofJo 26a7kLaxhNoRW38jEjOjxvVHxPGtfjoGTdjdYlxpyTBUouFK/OQD31d+zMd7AuMKNArY D7uRJH6R/LH8gthZk403MoKT6QumjEorNqkj9xAU5EX+HELKbDPKzbIij8oNweeRJa5+ tW/g==
X-Gm-Message-State: APjAAAW1h3jgIif/crY3iIR2n4JkGGi4ZJwaN5heFaFv31XnClW/sVKj JLK8BmPwapxm1B1e9HKjQQalACcdAVKBQx0YK5gxdg==
X-Google-Smtp-Source: APXvYqyggGILYtj46e8qjsT8vNd2z1m+F84WD1LANWVV+a7agvUhHIOMM93bfEe0N9AREZuJQz8MVsQm89dqvFQNciw=
X-Received: by 2002:a0c:8171:: with SMTP id 104mr23110723qvc.168.1568215686959; Wed, 11 Sep 2019 08:28:06 -0700 (PDT)
MIME-Version: 1.0
References: <CAH8Jh6DSMMyjtzTn5yKqWdsio40nMjkreUMyMkc8mJGAFdYK4Q@mail.gmail.com> <BA0AA020-AE9D-441A-9AF2-DF847F1D9597@strayalpha.com> <CAHw9_iJCk6ym_CoXca8zgSsN7qCx-iAzsTg2-hV+SWHRz2D17g@mail.gmail.com> <2ba7bbf42e6d007b83d024ef11c24070@strayalpha.com>
In-Reply-To: <2ba7bbf42e6d007b83d024ef11c24070@strayalpha.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 11 Sep 2019 11:27:31 -0400
Message-ID: <CAHw9_iJsHGyttCw6UCQYzc2gEy4Rf+v=dTa9OyKOTaoZxEFtPQ@mail.gmail.com>
To: Joe Touch <touch@strayalpha.com>
Cc: "James A. (Jim) Stevens" <james.a.stevens=40collins.com@dmarc.ietf.org>, MBONED WG <mboned@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/K_rh6jj6QO9ctbjR_Xjbx7rZzFI>
Subject: Re: [MBONED] mboned: UDP port conflict mtrace/traceroute
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 15:28:11 -0000

On Mon, Jul 29, 2019 at 1:36 PM Joe Touch <touch@strayalpha.com> wrote:
>
> On 2019-07-29 10:09, Warren Kumari wrote:
>
> ...
>
> Just FYI, I sent email to IANA letting them know that ports 33435 -
> 33534 should probably be listed it as "Known Unauthorized Use".
> From some archaeology, 33434 is apparently 2^15 + 666, and the
> "standard" traceroutes use up to 100 ports.
> I based this on the Van Jacobson (van@ee.lbl.gov) - 1988 which he
> "stole" (credited) from Steve Deering -- easiest location of code is:
> https://github.com/freebsd/freebsd/blob/master/contrib/traceroute/traceroute.c
>
> I don't much like referring to it as "Known Unauthorized Use" but
> that's technically what it is -- the important bit to me seems to be
> that we make in some way so they don't get handed out, exactly what
> they should be called is a less pressing problem.
>
>
> Although that's helpful to those seeing traffic on those ports, it does not prevent IANA from assigning those values when requested.
>
> The only way to do that would be to make them ASSIGNED. That happens by the process indicated in RFCs 6335 and 7605 and notably is not driven by this sort of "squatting".
>
> NOTE: at the time that code was originally developed (1988), that range was OK for such uses without registration, but times changed in 1992.
>
> That code ought to be fixed.

Yes, that is true -- that code ought to be fixed; however, it doesn't
change the fact that mtrace cannot realistically be deployed using
this port -- enabling it on a router breaks traceroutes through that
router, leading to asterisks (I'd thought that we'd agreed on that,
but while looking back through my mail on this topic, it's possible
I'd misunderstood, and you don't actually agree that this port isn't
fit *for this particular purpose*).

Just wanting to make sure we are all on the same page, and they MBONED
will be publishing a -bis, deprecating this RFC and publishing a new
one with a different port...

W
>
> Joe



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf