IETF Logo Mail Archive

Re: draft-ietf-6man-slaac-renum: Conveying Information in Router Advertisement (RA) Messages

Fernando Gont <fgont@si6networks.com> Thu, 09 June 2022 15:09 UTC

Return-Path: <fgont@si6networks.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 2A663C15AE38; Thu, 9 Jun 2022 08:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.774
X-Spam-Level:
X-Spam-Status: No, score=-3.774 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 uv3V69UnacI3; Thu, 9 Jun 2022 08:09:15 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (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 0D851C15AE2E; Thu, 9 Jun 2022 08:09:15 -0700 (PDT)
Received: from [10.0.0.137] (unknown [186.19.8.47]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 5280C282A21; Thu, 9 Jun 2022 15:09:12 +0000 (UTC)
Message-ID: <b96ebc86-2d1a-ab2f-327a-258bbcf3fd19@si6networks.com>
Date: Thu, 09 Jun 2022 12:09:09 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
Subject: Re: draft-ietf-6man-slaac-renum: Conveying Information in Router Advertisement (RA) Messages
Content-Language: en-US
To: Ted Lemon <mellon@fugue.com>, Fernando Gont <fgont@si6networks.com>
Cc: ipv6@ietf.org, draft-ietf-6man-slaac-renum@ietf.org
References: <971cee77-6cf5-513f-c72b-458b1f0b581c@si6networks.com> <CAPt1N1nNo0kaQQetM_USUUNXUzq-2Ed1fMwZfYxPw3FNjnQH=A@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
In-Reply-To: <CAPt1N1nNo0kaQQetM_USUUNXUzq-2Ed1fMwZfYxPw3FNjnQH=A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/d0c9VjRJwiQQYZ4andTvBxcghYo>
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: Thu, 09 Jun 2022 15:09:16 -0000

Hi, Ted,

On 9/6/22 11:22, Ted Lemon wrote:
> This text seems correct to me. I suspect that implementations generally 
> already do this, but advising them to do it is not a bad idea.

Thanks for the input!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email