Re: [homenet] DNCP/HNCP Revisited

Ted Lemon <mellon@fugue.com> Thu, 19 September 2019 13:11 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 611AA120858 for <homenet@ietfa.amsl.com>; Thu, 19 Sep 2019 06:11:52 -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=fugue-com.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 KG_T7FqE5I-x for <homenet@ietfa.amsl.com>; Thu, 19 Sep 2019 06:11:50 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 8367612081B for <homenet@ietf.org>; Thu, 19 Sep 2019 06:11:50 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id c3so4073333qtv.10 for <homenet@ietf.org>; Thu, 19 Sep 2019 06:11:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=oQu8g364OnJTU1QcUWU6iMGttUfMa0z15OuQNqwXbSc=; b=x/QmLJS/u+RCHKS9I7w0YK92Z+Z4iJqaotsXHTKq5N2TU4qiH7vLvZoy+igIO4Y46h d6XpCcUgL9lO7A5hM69vj2eRAghAjbKf9NgnKbzVuCQ+P91MkRxHtLRWT+7aPQiAiS1t TQnHpS8bd/tKY+KfPGuSi6FgNDLgdRsX4lrO1BBXYeg2VXaJV6unzu+ka9djqjJz4DOJ Jh8o9Re8U5j19ylzELv9qvg0xQMjEgpUpIvd6aBoO0tbj4ahlB7DyHMtrcE7RRAiq4Eq B3Nl/uznQjXoUemZzCQRaYopv5lOMa2ZVrgjsw5G6K+uIFH+wxQhgVPMnCT/W0PgeNq0 sePw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=oQu8g364OnJTU1QcUWU6iMGttUfMa0z15OuQNqwXbSc=; b=e7uCoEI6SxqQq1MiMHYbWW2tC909wFArXlxMuXBqz6OgeN+U6FqASo3eaBxnwqQj3u 3f56fyOSXkcoftE1s88qOYhl1ueFxpidGbfxihaMHz9in+kzNiAGToqkCHqt4cFa9MwK oxfzVNIdukwXCP/g6HKX3EdYR/B1tSb6K+lFHPbTPx5FZoE7eUMXkJ4EilPg9rgNgfxh KqOsrh3Ejal7k62QVQ6Dt+Dtiwkl0VumrCF8ksUJZMRFQCZl7cWMOJftUgRPiCEp8CNE uhhU5kVsuqwXfWdkGBKyOA5EdKKrOZg8uFDc5tFZJmEAY6Gy8MvpvbvzURoSxJvRsh55 jl+g==
X-Gm-Message-State: APjAAAXSb2RiJlumdRQt7cMsA4qzCALhbsMWa7fKE4EPsO3D8d8UzT1K On4Peqf9J8aKpItgdXy6CZyzk5Xdo8gvqA==
X-Google-Smtp-Source: APXvYqzj7APaXmuEvaMktxJ1/nNYAWWRWc5+ypBaslJkJGy5vXdEe1f6wvIdLWdw8mVF27DDTrM8ew==
X-Received: by 2002:ac8:5147:: with SMTP id h7mr3020928qtn.117.1568898709605; Thu, 19 Sep 2019 06:11:49 -0700 (PDT)
Received: from [10.0.100.56] (c-73-186-137-119.hsd1.ma.comcast.net. [73.186.137.119]) by smtp.gmail.com with ESMTPSA id l206sm4487999qke.33.2019.09.19.06.11.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Sep 2019 06:11:48 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 19 Sep 2019 09:11:48 -0400
Message-Id: <8BC1E900-3E7D-44F0-A01D-94D468627BFF@fugue.com>
References: <878sqkwtoc.wl-jch@irif.fr>
Cc: HOMENET <homenet@ietf.org>
In-Reply-To: <878sqkwtoc.wl-jch@irif.fr>
To: Juliusz Chroboczek <jch@irif.fr>
X-Mailer: iPhone Mail (17A837)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/4P2xhwApMG5X6WsZcI0vsloGyiQ>
Subject: Re: [homenet] DNCP/HNCP Revisited
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2019 13:11:53 -0000

Yes, of course. We can never change a standards track protocol. That would be wrong. :)

What I’m trying to understand is how bad a problem this is. 

> On Sep 19, 2019, at 04:56, Juliusz Chroboczek <jch@irif.fr> wrote:
> 
> 
>> 
>> This still doesn’t address the problem that the HNCP packet needs to be
>> fragmented.  Fragmented Multicast doesn’t scale well.
> 
> HNCP doesn't fragment multicast, it only uses fragmentation for (link-local)
> unicast.  This is way less severe than what you incorrectly claim.
> 
> At any rate, the right time to discuss that was 2015, not now.  HNCP is
> a standards track protocol, and there's nobody left who's willing and
> competent to work on a new revision.
> 
> -- Juliusz