IETF Logo Mail Archive

Re: Late IPR Disclosure regarding draft-ietf-6man-ipv6-alt-mark

Carsten Bormann <cabo@tzi.org> Fri, 01 July 2022 07:13 UTC

Return-Path: <cabo@tzi.org>
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 74517C14F74E for <ipv6@ietfa.amsl.com>; Fri, 1 Jul 2022 00:13:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable 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 5giAHZRv6HO1 for <ipv6@ietfa.amsl.com>; Fri, 1 Jul 2022 00:13:27 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (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 0914CC14CF0D for <ipv6@ietf.org>; Fri, 1 Jul 2022 00:13:25 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4LZ5yV5yNdzDCbJ; Fri, 1 Jul 2022 09:13:22 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Subject: Re: Late IPR Disclosure regarding draft-ietf-6man-ipv6-alt-mark
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <e3e1d7a904f345ddab2f5f573463bf5f@huawei.com>
Date: Fri, 01 Jul 2022 09:13:22 +0200
Cc: Fernando Gont <fgont@si6networks.com>, Fernando Gont <fernando@gont.com.ar>, Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
X-Mao-Original-Outgoing-Id: 678352402.329132-6f0a805deb25afaf074335ec2f117f0b
Content-Transfer-Encoding: quoted-printable
Message-Id: <F91B03F6-097F-4009-8CAE-926BBF9CFA98@tzi.org>
References: <8E1527F0-5D03-432D-8077-8022801A28E3@gmail.com> <b97b96f0-3fc8-78b4-f434-7a1da0654e35@gont.com.ar> <182b7608c4eb432b839f2654bfa12a62@huawei.com> <86ca671b-36b9-7b04-b244-82bd518a7240@si6networks.com> <e3e1d7a904f345ddab2f5f573463bf5f@huawei.com>
To: Giuseppe Fioccola <giuseppe.fioccola=40huawei.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/DEu-3TBPcRBG0s_AvDXW22YVOn4>
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: Fri, 01 Jul 2022 07:13:31 -0000

On 2022-07-01, at 09:01, Giuseppe Fioccola <giuseppe.fioccola=40huawei.com@dmarc.ietf.org> wrote:
> 
> I think it is correct to mention RFC 8799 as a document to read as it is done in RFC 9197 as well.

RFC 9197 demonstrates an interesting use case for an informative reference:
Terminology from 8799 is used to define terminology in 9197 that is then used in a normative way.
There are probably limits to this kind of up-ratcheting, but it strikes me as entirely appropriate in 9197.
(I normally try to turn terminology references into normative ones, except for informational sources, such as RFC 7228.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email