Re: [Int-area] WGLC for draft-ietf-intarea-rfc7042bis-04

Donald Eastlake <d3e3e3@gmail.com> Wed, 10 May 2023 01:38 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD01EC152567; Tue, 9 May 2023 18:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.845
X-Spam-Level:
X-Spam-Status: No, score=-6.845 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 F8cpyrI0I4qx; Tue, 9 May 2023 18:37:56 -0700 (PDT)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 C7A40C14CE3F; Tue, 9 May 2023 18:37:56 -0700 (PDT)
Received: by mail-ej1-x62a.google.com with SMTP id a640c23a62f3a-965c3f9af2aso973166666b.0; Tue, 09 May 2023 18:37:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683682675; x=1686274675; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=yLPxx1nQ6NLPuvPAdq6vVPBywTftjbMRZ2AGoIc5vYI=; b=HRoGT0+8HFrE4n52eybIR7uSzEfPtnh2quCaod/YilaJsAXZceYkf6EWxOtQYezJRF CL5LA9SXZUb3nu2cu/x5FLMsKjBjXgOcDd4jKhETKI4JazwsL7HtU6qjTKZXycPzohO/ oMzkwXPPdEHpxSmrvLL95zZOXn3VLILeCyizulVnVW2zGxSv5RjMELQzUtySExupBKeJ h/pSRzOalNqh7ME1JOY0H+oBDvGEu93++vs/h+de0c6gKC9tZUPPn/T7n7RCm6eGad0V 8upFn3w65XLcZTXvIlPvjLLViCKGyGN1lvAUyi7sB/0hRAcV0C4BNiC/kg6xuBqBgvVj HmOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683682675; x=1686274675; 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=yLPxx1nQ6NLPuvPAdq6vVPBywTftjbMRZ2AGoIc5vYI=; b=Z9drEPEg4elzfnsX21USMEayCbqfoEB4PAqk95vIofsc6pPLuuL5lQkEOrIVfc6AyH JX4CwPth97uyihHyjQs8nr4uvu2QfRd4H1JZP/y/md/w4fbl/O1D5wD/aeJPsMu9U9v5 SiiltHnK+Ei1rcjOTo0cu6DNylehvwFs+ylS8pzKxAcpcwHZf1Tuh5Pk3lSs6eh/GtQw 0bBM2ydC/LQATzo6VNyi2R/utt6obx84myoZpv615FK+4itakCiA+JzdLvI+PSel72JR M9KQ4XLU2tvRnzGTce6DmulHAZSQ8ANMRWA+3Fxpoq2N/RWxWxsb0iHSusiVK0KK6co2 5CGw==
X-Gm-Message-State: AC+VfDwVX2dLfKtiWmKGckgapEZsJCyhhlJMX00Im4Kt05crA+Eme/xG ztv1+kY3LzPbYjC7nELZ058PnALV0U1zuTbZyEs=
X-Google-Smtp-Source: ACHHUZ6mo3pi/sdvuqmCq1QSr6ywrWSEAd+BMlMsr3zalznc2c64mTZP4faYqLPqc5R5rnvS8KCkMLjUvfA5VmMRaY4=
X-Received: by 2002:a17:907:2d91:b0:969:f3b4:83 with SMTP id gt17-20020a1709072d9100b00969f3b40083mr3811251ejc.71.1683682675107; Tue, 09 May 2023 18:37:55 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR15MB23278DD6E18A9A9729BBEFD899729@BYAPR15MB2327.namprd15.prod.outlook.com> <F78955B7-FB56-4431-9EA7-246F7F2C9BD5@gmail.com>
In-Reply-To: <F78955B7-FB56-4431-9EA7-246F7F2C9BD5@gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 09 May 2023 21:37:43 -0400
Message-ID: <CAF4+nEEtqs1htbOwahicyERRkACciSJOB05iLB2F61JuwR_YkA@mail.gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Cc: Internet Area <int-area@ietf.org>, Wassim Haddad <wassim.haddad=40ericsson.com@dmarc.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c3aafd05fb4cebd6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/dlxlhJyjGpud0nnIKNV4H-Wiu9M>
Subject: Re: [Int-area] WGLC for draft-ietf-intarea-rfc7042bis-04
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 May 2023 01:38:00 -0000

Hi Bob,

On Tue, May 9, 2023 at 11:29 AM Bob Hinden <bob.hinden@gmail.com> wrote:
>
> Hi,
>
> I generally support advancing this document, but I noticed an issue that
should be resolved.
>
> In Section 2.2.1. "IPv6 Use of Modified EUI‑64 Identifiers”.    The
contents is technically correct, but it should also mention that this type
of IPv6 Interface Identifiers are no longer recommended.   See RFC8064
"Recommendation on Stable IPv6 Interface Identifiers”.   I think it would
be better if text was added at the beginning of Section 2.2.1 that this
approach is no longer recommended, include a reference to RFC8064, and say
something that this is included for completeness (or similar wording).

Thanks for this cogent comment.

How about adding the following sentence as a new first paragraph in Section
2.2.1: "The approach described below for constructing IPv6 is now
deprecated and the method specified in [RFC8064] is RECOMMENDED."

Also changing the beginning of the following text as follows
OLD

UI‑64 identifiers are used to form the lower 64 bits of some

NEW

UI‑64 identifiers have been used to form the lower 64 bits of some


Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com


On Tue, May 9, 2023 at 11:29 AM Bob Hinden <bob.hinden@gmail.com> wrote:

> Hi,
>
> I generally support advancing this document, but I noticed an issue that
> should be resolved.
>
> In Section 2.2.1. "IPv6 Use of Modified EUI‑64 Identifiers”.    The
> contents is technically correct, but it should also mention that this type
> of IPv6 Interface Identifiers are no longer recommended.   See RFC8064
> "Recommendation on Stable IPv6 Interface Identifiers”.   I think it would
> be better if text was added at the beginning of Section 2.2.1 that this
> approach is no longer recommended, include a reference to RFC8064, and say
> something that this is included for completeness (or similar wording).
>
> Bob
>
>
> On May 4, 2023, at 11:17 PM, Wassim Haddad <
> wassim.haddad=40ericsson.com@dmarc.ietf.org> wrote:
>
> Dear Intarea WG,
>
> This email starts an Intarea WG Last Call on
> draft-ietf-intarea-rfc7042bis-04 (“IANA Considerations and IETF Protocol
> and Documentation Usage for IEEE 802 Parameters”).
>
> A link to the draft:
> https://datatracker.ietf.org/doc/draft-ietf-intarea-rfc7042bis/
>
> Please respond to this email to support the documents and/or send comments
> by 05/20/2023.
>
>
> Thanks,
> Juan Carlos & Wassim
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>