Re: Interested in wireless ?

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 31 May 2020 23:20 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2B433A07DD for <ipv6@ietfa.amsl.com>; Sun, 31 May 2020 16:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 h6RUMzP2Npe5 for <ipv6@ietfa.amsl.com>; Sun, 31 May 2020 16:20:42 -0700 (PDT)
Received: from mail-pf1-x442.google.com (mail-pf1-x442.google.com [IPv6:2607:f8b0:4864:20::442]) (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 812E73A07DC for <ipv6@ietf.org>; Sun, 31 May 2020 16:20:42 -0700 (PDT)
Received: by mail-pf1-x442.google.com with SMTP id 64so2573250pfg.8 for <ipv6@ietf.org>; Sun, 31 May 2020 16:20:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=BoUuIrelAcyDllmfbPoIOMqDNT0wQ5VeiEX3uZmkA3M=; b=fIyQZRIf9PBhnvTl9Mlysg04ySpy2SLxzRjfURSWE9U1/5bKb3RLJC1pZC4WD9FuxC lCweb7GtXohhBepDOeuocMZkZOiRkTQ9eAvjbH9LJ2RS5EUET6ej526PygC6WkRD+F1v 5QD0hfr1AeUjtP9M24+UiY5eea/pUAnAcKf6anvtWZIBC95BPENkL6Y+JRpy08Dn2NGd WxRMNQOKBFutQIoZj/3Xwgw5jGymMk/zZJQ6YKDu8Ccxlp7OZJPzylA4aL5ldGwy/vlA rn6NxE4ygXtkytdLT9W0pZ2zHb8ERMcrL1Ye29A/w97+q1S7GAkpbPnAoXZC0tH+vI6G yHFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=BoUuIrelAcyDllmfbPoIOMqDNT0wQ5VeiEX3uZmkA3M=; b=Le9Yab3c4XXAFZI/HFHee8HBMrX3f1qQH8sVwodnJ/eBSzFoeEp33tyKbBnUI0XLmS fhymmQ2prvvWR54wmf5GoNrb3GBezs7v3P5tQWg0vpRcQqFM3oum0m6zM22+zwRrViI5 dNm62ziCO6x6f6H1YPNVbx+Ac2f1MvFQyHNVopzYiGacmbIAG+n/dAXAwF7kXEAQi0pZ w6XM1NLs30Uup8bv1+lCQrAx6yJfUmlbtR3mwIQBnQUcDrv77pgpiItCWm95NrROCmQw 4rSM6cW+dKpXIWkrURvsowZaVvZw/RERqcjKo/9h8TaXwsGZx0YWQvZsFBB6PB8O/b7G Zxvg==
X-Gm-Message-State: AOAM530kfK3tF6xaFQ25BrC01ddHpOS6eaNpl8Y/sznGD2yjBgzZ2AHG k9WlHemZdgMvpFUIfG9HgRpnhHfxXlY=
X-Google-Smtp-Source: ABdhPJxToWxsrQGuDqUNLi7l0SnzvYrLTyfbTdZ82usQn0tujlAuQViIy8llYP2mD8uDLbLf5rT94A==
X-Received: by 2002:a63:4563:: with SMTP id u35mr17237587pgk.163.1590967240482; Sun, 31 May 2020 16:20:40 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.12.178]) by smtp.gmail.com with ESMTPSA id n3sm11193531pgq.30.2020.05.31.16.20.38 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 31 May 2020 16:20:39 -0700 (PDT)
Subject: Re: Interested in wireless ?
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: 6man WG <ipv6@ietf.org>
References: <A26FA9F8-72B8-4728-B978-6DDD271EC64D@cisco.com> <d157e481-f5d0-7f54-2f62-7400e0394688@gmail.com> <49E329AB-5060-46A3-BEC9-66EC80056565@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <2c94c310-28ba-01e5-a874-029509e9b653@gmail.com>
Date: Mon, 01 Jun 2020 11:20:36 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <49E329AB-5060-46A3-BEC9-66EC80056565@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/eB6da6mF1G2D2KIzSkE8rl1z1XY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 May 2020 23:20:44 -0000

Pascal,

There is a category of standards track documents foreseen in RFC2026 called "applicability statements", described at https://tools.ietf.org/html/rfc2026#section-3.2

I think that is perhaps where your draft could fit. A little bit stronger than Informational and little bit different than Best *Current* Practice.

Regards
   Brian

On 01-Jun-20 04:40, Pascal Thubert (pthubert) wrote:
> Hello Brian
> 
> We may have to split the doc but for the most part I agree it is an informational. 
> 
> For now I suggest to just change the intended status accordingly and aim at BCP or something.
> 
> Let’s discuss in parallel the coexistence and if there’s a need for an std track somewhere. There’s at least the use of a 6LBR for address looking up in unicast.
> 
> Take care,
> Pascal
> 
>> Le 30 mai 2020 à 22:47, Brian E Carpenter <brian.e.carpenter@gmail.com> a écrit :
>>
>> Hi,
>>
>> I believe that this is an important topic that 6MAN should take up. The draft is a good basis.
>>
>> At the moment I find the draft a bit confusing in one way. It's aimed at standards track, but it mainly doesn't read like a standard. There's a lot of discussion but not much specification. If I was a coder, I wouldn't really know where to start. For example, the end of the Introduction says:
>>
>> "This document discusses the applicability of IPv6 ND
>> over wireless links, as compared with routing-based alternatives such
>> as prefix-per node and multi-link subnets (MLSN), and with Wireless
>> ND (WiND), that is similar to the Wi-Fi association and reduces the
>> need for Network-Layer multicast."
>>
>> If it's a standard, IMHO it shouldn't do that. It should specify what WiND is, with normative references as needed. Section 5 is the important part. It's fine to have a descriptive section about why WiND is needed, but that is almost better as an appendix. The main text should be essentially the instructions for a kernel programmer.
>>
>> Regards
>>   Brian Carpenter
>>
>>> On 30-May-20 23:46, Pascal Thubert (pthubert) wrote:
>>> Dear all
>>>
>>> Since there’s so much energy on the list these days, could we consider the adoption of
>>> https://tools.ietf.org/html/draft-thubert-6man-ipv6-over-wireless-05
>>> ?
>>>
>>> I got only positive feedback, there’s no politics, there no label, it’s all about IPv6 models for wireless. This may appear useful in a world where the vast majority of devices are connected that way.
>>>
>>> Keep safe,
>>>
>>> Pascal
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>>