Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 20 August 2022 19:51 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E576C14F748 for <6lo@ietfa.amsl.com>; Sat, 20 Aug 2022 12:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.706
X-Spam-Level:
X-Spam-Status: No, score=-6.706 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (bad RSA signature)" header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBBuFxTHnrwV for <6lo@ietfa.amsl.com>; Sat, 20 Aug 2022 12:51:26 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B944C15270D for <6lo@ietf.org>; Sat, 20 Aug 2022 12:51:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 1768818E6E; Sat, 20 Aug 2022 16:11:09 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9S57xq8Oqa0R; Sat, 20 Aug 2022 16:11:07 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id BACAB18CF0; Sat, 20 Aug 2022 16:11:07 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1661026267; bh=xpk3xKxkDgylsJo2attgzfnGFF0PpTzIuJvk/n8xjKs=; h=From:To:Subject:In-Reply-To:References:Date:From; b=ToW5D0Ay45jv4XS+btZJDq0c9BDua+s21AISrH5LLKn9vSOEpOObJEQm8L677PzYr jqmyLshL8xvzsqWfIwCtRXQHj8yzR3uBmUj8zMifqZPFaqlHAWC4I0yloXc9Iz5RkO Haf4JAvndNkHqPY3+VjEn8okAJTdwsT7n1dNm0qHkbqRW7y3BEcTjt0H8viVH0aECm vJ3OiIn8v2qCp8kgpx6OpM4McKynEJ7DDlzWGHoHDsyVYavxSRn6fgbTc+TJdR5710 u/M4EmbsjNj7Jhx+iBTmOkHizwxzKahI6ojtpcbULGIr0lFxbvP9q8HcgRdg4Vu2MV PBCNeg4XqGdvg==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8B53A147; Sat, 20 Aug 2022 15:51:19 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Luigi IANNONE <luigi.iannone=40huawei.com@dmarc.ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
In-Reply-To: <6066dc1b32a5406a94b0761a8b5d1251@huawei.com>
References: <91f63618-ebbc-cdc6-b38e-d7b5a3d3e850@gmail.com> <5497C7A1-231D-414E-BCEF-956BB65298C2@gmail.com> <CACQW0Eq3_oFijtuKNcPV9rHrpiwPejBEjyVcktv0xACQGw-oSg@mail.gmail.com> <6066dc1b32a5406a94b0761a8b5d1251@huawei.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 20 Aug 2022 15:51:19 -0400
Message-ID: <11911.1661025079@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/if5NAl_hABruPC7ts7WHWn1U4WA>
Subject: Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2022 19:51:30 -0000

Luigi IANNONE <luigi.iannone=40huawei.com@dmarc.ietf.org> wrote:
    > Hi Alexander,

    > Thanks for your feedback. Please send us the tons of questions you have
    > we will do our best to answer them.

Well, Alexander and a few others including me, have asked for more detailed
and more specific use cases.   The existence of the
https://datatracker.ietf.org/doc/draft-li-nsa-reliability/ draft makes me
doubt whether or not nsa is useable on it's own.  (And please resubmit it
with 6lo in it's name)

I have now seen a slightly reasonable use case, but I remain skeptical about
the overall utility.    I would like to see some running code.


    > In general I think that the concerns that you are expressing can be
    > solved during the normal life cycle of a draft as a WG item.

Sure, as long as you agree that it could be that the objections are fatal,
and that the document might not get published.

The other question is whether or not you have looked at the BIER routing work
that we started in ROLL, as that actually might map even better to your use
case.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide