IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Wed, 24 May 2023 23:49 UTC

Return-Path: <mellon@fugue.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 31BDCC151B19 for <ipv6@ietfa.amsl.com>; Wed, 24 May 2023 16:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20221208.gappssmtp.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 YHhX4_l3j6IF for <ipv6@ietfa.amsl.com>; Wed, 24 May 2023 16:49:42 -0700 (PDT)
Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (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 579E3C151B17 for <ipv6@ietf.org>; Wed, 24 May 2023 16:49:41 -0700 (PDT)
Received: by mail-qv1-xf2e.google.com with SMTP id 6a1803df08f44-625bb54004dso335486d6.1 for <ipv6@ietf.org>; Wed, 24 May 2023 16:49:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20221208.gappssmtp.com; s=20221208; t=1684972180; x=1687564180; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=226Nt88ESycYlgfthFCBWdWBVvAvR9MCJzWLc7bG8pk=; b=h0lMCp0G57ih3RYc+PAF0rLVac+bcO+sxMLBMDesZwNmZGEePJCGMbeEK5NIh9M1GK 2IJ5QeWrxoHjrU/UStEHE/3Xov1gFV3ypPi4hKzhna6MbQVJ2k0KwrmDWnBPhq13oLOo aKD1xZGz5MKBaHQSdSN7iRFMljHKXS0yvgsxoWe0NwWopVCq+b/JCysuxDJmwHaOipQW andt/qGH77e33RgTwQ9L0fyXs/eJRaYhWDiKsKcFXZ5nEHSilv+Brt+kmV4f3zDY5BZH isCqZezeQuAtCipLucP/mxljhimCqCh57JMC0cxydT2Abcfzp/7XLqdiWQaj7HsWgt+r LeFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684972180; x=1687564180; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=226Nt88ESycYlgfthFCBWdWBVvAvR9MCJzWLc7bG8pk=; b=Y9muRG3ePDiUoqQlzaRyRcpPQ/KfCj+OLEpbynn4DLRHsnRFyKyMmJdFKNacSxaZnf 9Xc8O1O418bruo1Cx+ZTBmPXsib+D+cT+CT9/5tJEse1NwrDaOQSK1KVe2z6io9jYSFW rcmlDRcCjAqvMaZumTTm7cg4wZk9jOiS3JG7nTCODU29DdLKAcXbqk9An2SdMknjX1mL dnfx+jeDwUeHT08pzIE+7T7dgIA3qMZIyPSZSfKc678g4XM3YBe6HPzHOAnK70vizcYC iahuyxUWCKZDQt4cMBwDnqQY1LbKL2PNcCHXWVfnlRcynEfkpK8YrL3b9NkurEHPTzT/ dz9g==
X-Gm-Message-State: AC+VfDwaqkMG4bwaqM3iQMw4lwJnnVD6Qw1u2qX4GRZ9UpLY5WZm7nXa xzyg5qnglSL2pp+xm0RKOIt7GPxFGHDRDUD1yJaCjg==
X-Google-Smtp-Source: ACHHUZ6jJ6n5sNisel6JZbUruX4aJ1B43LJ7KrPfGeOQ1wJdstVCSmG0mCNiM5+kryBLVonNF0KaNI1E0AaLdIlDND8=
X-Received: by 2002:ad4:4eaf:0:b0:616:7977:2460 with SMTP id ed15-20020ad44eaf000000b0061679772460mr1237343qvb.24.1684972180509; Wed, 24 May 2023 16:49:40 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR11MB4881C130988C6FF3A11B500AD8419@CO1PR11MB4881.namprd11.prod.outlook.com> <CO3PR13MB5752AE273D328D809BA179A9F4419@CO3PR13MB5752.namprd13.prod.outlook.com>
In-Reply-To: <CO3PR13MB5752AE273D328D809BA179A9F4419@CO3PR13MB5752.namprd13.prod.outlook.com>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 24 May 2023 19:49:04 -0400
Message-ID: <CAPt1N1=xB_UQ4QL7Cpa=Tm-8LUkrzwa4dUb_m5Zw+n_iorwUhA@mail.gmail.com>
To: Michael McBride <michael.mcbride@futurewei.com>
Cc: "pthubert@cisco.com" <pthubert@cisco.com>, "IPv6 WG (ipv6@ietf.org)" <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000046ab6905fc792818"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/AEYUsEk_IW5tYyUvqjSTdFjSC7Q>
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: Wed, 24 May 2023 23:49:46 -0000

Bonjour is Apple's branding of DNS-SD over mDNS.

On Wed, May 24, 2023 at 5:48 PM Michael McBride <
michael.mcbride@futurewei.com> wrote:

> Looks good Pascal. Agree its ready to progress.
>
>
>
> [MCAST PROBLEMS] can be now be replaced with RFC 9119. And you may want to
> consider moving the acronyms up from page 13 to page 3.
>
>
>
> Question on your Bonjour reference. Bonjour uses mDNS. Is that what you
> are referring to with “Excessive use of broadcast by protocols such as
> ND-Classic and Bonjour led network administrators to install multicast rate
> limiting to protect the network.”? We didn’t get into Bonjour in 9119 but
> we did get into mDNS a bit, ie, when many devices are using it. Just want
> to make sure we are saying that same thing.
>
>
>
> Thanks,
>
> mike
>
>
>
> *From:* ipv6 <ipv6-bounces@ietf.org> *On Behalf Of * Pascal Thubert
> (pthubert)
> *Sent:* Tuesday, May 23, 2023 11:52 PM
> *To:* IPv6 WG (ipv6@ietf.org) <ipv6@ietf.org>
> *Subject:* [IPv6] next steps for draft-ietf-6man-ipv6-over-wireless
>
>
>
> Dear WG:
>
>
>
> We adopted that draft to publish it as informational; it is at the same
> time a state of the art, a problem statement, and an applicability
> statement.
>
>
>
> The issues are clear and present, see also
> draft-ietf-v6ops-nd-considerations. We face customer situations where
> clients are not properly served because ND snooping fails to locate them
> all with a painful regularity. This impacts all sorts of situations, from
> wireless to fabrics / EVPN.
>
>
>
> Note that This is indeed very related to the SLAAC operation and IPv4 is
> mostly immune. Meaning that the IPv6 experience is of more broadcasts and
> less reliability.
>
>
>
> In order to progress in solving the issues raised, it makes sense to
> publish soon and move on. The draft has been progressing as an individual
> submission for a long time and it is mostly complete, IMHO. So my intent is
> to ask for WGLC sooner than later. To get there, reviews would be highly
> appreciated.
>
>
>
> Many thanks in advance : )
>
>
>
> Pascal
> --------------------------------------------------------------------
> 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