IETF Logo Mail Archive

Re: [IPv6] next steps for draft-ietf-6man-ipv6-over-wireless

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 11 June 2023 05:14 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 56C38C151557 for <ipv6@ietfa.amsl.com>; Sat, 10 Jun 2023 22:14:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=pass (2048-bit key) header.d=gmail.com
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 Qq_TPdPFDWas for <ipv6@ietfa.amsl.com>; Sat, 10 Jun 2023 22:14:25 -0700 (PDT)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 A6F6AC15155B for <ipv6@ietf.org>; Sat, 10 Jun 2023 22:14:25 -0700 (PDT)
Received: by mail-pg1-x535.google.com with SMTP id 41be03b00d2f7-5440e98616cso1562377a12.0 for <ipv6@ietf.org>; Sat, 10 Jun 2023 22:14:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686460465; x=1689052465; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=CjRTZWh6cdxI3/tuFmUn3nvmtSvW29nsZgtB87y1VZA=; b=mdA/hPoIDOsA9Y+OA7xuHMy5J+iWwDfu3C5nFL78tuV6IAA/sl1HtiWgM7/bZq/S/G 6Rhv51CUecCLB5RqhkdtpzpF+QSLrhJHtG0K9h/4UflzO8mnzUfWETLN3svfkCyrwEqS zGt68buH5XoRGL0oiUTBTE0x2xXXJWWoV01G0IdUDEEXzXJgBVxoyuLhHZqW3x0keKmz u67qDkOHknQdJHw4JrMMPG94VNHe3UYw7++P0joD7SsxRYc8/GHBq2u96vr5pALeFj8Z re0/Iaakjb4Da5lRkt7z5iRyBjIiq4o6EeBELrSMg0/bw+bsqrF8wpIJvJiXnTboS9uz NweA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686460465; x=1689052465; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=CjRTZWh6cdxI3/tuFmUn3nvmtSvW29nsZgtB87y1VZA=; b=O80/0Oa4jhuIP5Z0KaA83/dTcnAgR9l9CIagzJjK/GVgp+5t36iSHmPmRWouLpPNcq A0waXke4ukEdsPeod4CkLQPgxPdhNxVGiFFcDIPiC4L82WCbt1aV3xSBo99c3jXkALfg 9wPK+lHWLIJ+NDR8J0Ort1bliyhXSMOORzIW24FoOSieGYGTGLoKEm/q76nLjfqvU8w9 DNO06lqgrBXOsK32K0E3Yjk86u+uwyRyVPu9IgN1i5rPgzGB4sTifl7iudVUeeZGALgO OaSK/gHw0HR5oXwfASAvWtmGSfA6K1ciff56YkocVJqq0VL1kSo7AEL7U+Ys5oDEFLP/ zEBg==
X-Gm-Message-State: AC+VfDzr63HFEytux+K4somU4fSy5ld/01ZjrOyv+6933e2H1/KVyaVY X5MLRQOBeY98fdHO7vkXSW8=
X-Google-Smtp-Source: ACHHUZ4tYuefbE3kQiNndgue1wVRZjETkZ8NVG1lPnp4Bqed10W25hT0lYUVK+fDJ0aRdSyahJ3RfA==
X-Received: by 2002:a17:90a:5c:b0:259:12b2:84ef with SMTP id 28-20020a17090a005c00b0025912b284efmr7172057pjb.13.1686460464726; Sat, 10 Jun 2023 22:14:24 -0700 (PDT)
Received: from ?IPV6:2406:e003:1184:f001:9991:d1ad:8c20:42bd? ([2406:e003:1184:f001:9991:d1ad:8c20:42bd]) by smtp.gmail.com with ESMTPSA id c7-20020a170902b68700b001b05e97ee09sm5737805pls.283.2023.06.10.22.14.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 10 Jun 2023 22:14:24 -0700 (PDT)
Message-ID: <7512f78f-b512-4aff-3f3d-988eb630b623@gmail.com>
Date: Sun, 11 Jun 2023 17:14:19 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Cc: IPv6 List <ipv6@ietf.org>
References: <CO1PR11MB4881C130988C6FF3A11B500AD8419@CO1PR11MB4881.namprd11.prod.outlook.com> <CAKD1Yr2Q7tag5PV_QoPAuxhYa4GAJz5pxs9aS7akr0_z_emePw@mail.gmail.com> <CO1PR11MB488126AB23F21EFABFEA5F97D8489@CO1PR11MB4881.namprd11.prod.outlook.com> <F1FED126-517F-466F-8FF5-990E9DE6BC14@gmail.com> <CO1PR11MB4881DE6803EE81A0E78C3237D851A@CO1PR11MB4881.namprd11.prod.outlook.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CO1PR11MB4881DE6803EE81A0E78C3237D851A@CO1PR11MB4881.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gFmimMT1v6dx9wcKjp0P_CEEr30>
Subject: Re: [IPv6] next steps for draft-ietf-6man-ipv6-over-wireless
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
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, 11 Jun 2023 05:14:29 -0000

On 09-Jun-23 20:03, Pascal Thubert (pthubert) wrote:
> Dear all:
> 
> I republished applying the below.
> 
> Since WiND (RFC 8505, 8928, 8929, more coming with xcast and prefix registration) are part of ND I might have created inconsistencies in the process. Please let me know if the reader can get confused.
> 
> And then, I’m still after a way to call things with the WiND extensions.
> 
>  1. Do we keep the term WiND?

It's nice, but it embeds "Wireless" and that sounds like an unintended restriction.
  
> 2)   If not, what else?
> 
> a) ND for NBMA?
> 
> b) Stateful ND?
> 
> c) ND registration?
> 
> d) other?
> 
> Suggestions welcome,

Firstly, let me say that "SGP" seems to me the most important acronym and concept in the model. We've really needed that ever since "NBMA" was coined.

So I quite like "SND" but interpreted as "Subnet Neighbor Discovery".

    Brian

> Pascal
> 
> *From:* ipv6 <ipv6-bounces@ietf.org> *On Behalf Of *Bob Hinden
> *Sent:* Wednesday, May 31, 2023 7:53 PM
> *To:* Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org>
> *Cc:* Bob Hinden <bob.hinden@gmail.com>; Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>; IPv6 List <ipv6@ietf.org>
> *Subject:* Re: [IPv6] next steps for draft-ietf-6man-ipv6-over-wireless
> 
> Pascal,
> 
> 
> 
>     >  Also, please replace "ND classic" with "Neighbor Discovery" everywhere. There is no such thing as "ND classic". There  is only ND.
> 
>     There’s RFC 4861-4862 on the one hand and RFC 6775-8505 on the other. They are all ND. This document needs a term that points on the former group, and one that points of the registration extensions. So the document defines ND-Classic for the purpose of naming the former. The alternate would be to change ND classic to RFC 4861-RFC 4862 throughout. What’s best for the reader?
> 
> My personal view is that it would better to say “Neighbor Discovery” to describe base protocol (RFC 4861-4862) and find a different term for extensions that have been done for other environments.   Saying “ND Classic” is a bit pejorative.
> 
> Bob
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email