Return-Path: X-Original-To: mpls@ietfa.amsl.com Delivered-To: mpls@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99D95C1519AD; Tue, 1 Oct 2024 09:33:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.103 X-Spam-Level: X-Spam-Status: No, score=-2.103 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=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 Z2MUpadYuQHx; Tue, 1 Oct 2024 09:33:54 -0700 (PDT) Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17721C169421; Tue, 1 Oct 2024 09:33:54 -0700 (PDT) Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-a8d51a7d6f5so755240466b.2; Tue, 01 Oct 2024 09:33:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727800432; x=1728405232; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=9NY86ZbYOm3mJczQC3/Pot8tGdA6dHz88kk3Y1kOKtE=; b=ctjnHHLATNzmiT55QolNvaDHLBlrkugkB1tNKD9TTLtFxvJyE8GTCJkpE0qQsgzmTG 85DyWfXiQPZ/qp7p9j5BW1zKV+CMq2W5So1iH84ZPJ/jYfiYlGSpWhDWobVprsbzZdE7 4oiiJ6s3VW3EpeJaI1t/Z1zw9d9pbxNbVjQR9U04PPIO/V4WccOlJ9pc5bJ4eng+4oCK OkcLWATbkLtAHFDok/mKVs4GYJihZmicOKqfNnLjPA1907VTVhCNjtb0Gykd6xpJUqCB hSP+9Asa07gYimkg8DYYuHtimqoUXrO1c+HzZlJ4afahXVT8vpGKbBKah8HlqtOHl4QO GcFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727800432; x=1728405232; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9NY86ZbYOm3mJczQC3/Pot8tGdA6dHz88kk3Y1kOKtE=; b=uLZEZDuK/HpkSrX12s/ckvDsf2yHKzgYP2KBmf9FYgNRTkNAEzV2Zez344lE8nm59d csfO1bu9HtzQsQ4gBy7tinNzgwD5Ah2sq3phvQRziImULsxfgoaLGOt8TgfOl1uGsWjs UTxEvG6hJ3GSpmnsQNTMS0Fy12PXYICB33xEwdDqaEjQe+BPWqqV22KLhI2+CVeVftLs w+wApuf6D5Lj22izdNRV5co0oXCWML1cGVN8ObzI8rdcx/Z3P5H9Knoh7Lh1oz3Way33 LILV7WnHSGxSBsT46LAmgO5LiO56qJQ+MIoL1yEVggI2S4PxBWambo5wQboh9yxET6ns Gpcg== X-Forwarded-Encrypted: i=1; AJvYcCWxtWwpMYwLfFPzeMDQINUosrIY81/q715kR1JI19f6BkWfclpEQ5fv50noAutm8Dm+PPuZma/Ikt+En/9ryN7bdaUa6udRQ6HL@ietf.org, AJvYcCXRKeHlJssC5Vcrfij1pWhNVKIqOBWjmTlSJnb+/kW17n1jcgFScqwHoZszO8tp/9+JmeCCVNILkPQ7CQw=@ietf.org, AJvYcCXpQLcl7OX7GeStxUCMB8fm+JRjx6k0YIOLPjiLdG+6bMD+C25T49D7iHYLIgkIz7lZQeb50A==@ietf.org X-Gm-Message-State: AOJu0YxzI4NM0oOk/AjmqTEYXUb9XPVkbgencShnMLrLEdKH+LQH5Wsk 1xZQf7PBdSbYgPxir4WmthDkgEnzjayd3mHE0uy6FjyrH6+GxiM9 X-Google-Smtp-Source: AGHT+IGh19gkK00hBfaybkiKFRR+uBeOhxzYmpwhvdREHETvn6PsFXkfs7n9SJ2bR3cog9NSLqkhnw== X-Received: by 2002:a17:906:7311:b0:a7a:9a78:4b5a with SMTP id a640c23a62f3a-a98f837bcf8mr14720866b.52.1727800432267; Tue, 01 Oct 2024 09:33:52 -0700 (PDT) Received: from smtpclient.apple ([148.252.132.241]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a93c27ecd10sm734572766b.96.2024.10.01.09.33.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Oct 2024 09:33:51 -0700 (PDT) From: Stewart Bryant Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_49D53218-9CFF-4B44-A0A3-D8D38E859828" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Date: Tue, 1 Oct 2024 17:33:39 +0100 In-Reply-To: To: Nicolai Leymann References: X-Mailer: Apple Mail (2.3776.700.51) Message-ID-Hash: 5ANTC2ETBHGTGEEEJHC6TSHQYX5WSXYC X-Message-ID-Hash: 5ANTC2ETBHGTGEEEJHC6TSHQYX5WSXYC X-MailFrom: stewart.bryant@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: mpls , mpls-chairs@ietf.org, draft-li-mpls-mna-entropy@ietf.org X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5Bmpls=5D_Re=3A_IPR_poll_on_draft-li-mpls-mna-entropy?= List-Id: Multi-Protocol Label Switching WG Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --Apple-Mail=_49D53218-9CFF-4B44-A0A3-D8D38E859828 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Are we sure that the IPR filed against RFC6790 is not of such generality = that it also applies to this work? The patent claim text certainly seems = quite general. I know that the WG is sensitive to IPR on MNA as it previously rejected = a solution based on it being encumbered by IPR, making this is an = important point to consider. Best regards Stewart > On 30 Sep 2024, at 13:49, N.Leymann@telekom.de wrote: >=20 > Hi Working Group and authors, > =20 > This email initiates an IPR poll draft-li-mpls-mna-entropy in = anticipation of its Working Group adoption poll. > =20 > Are you aware of any IPR that applies to the draft identified above? > Please state either: > "No, I'm not aware of any IPR that applies to this draft" > or > "Yes, I'm aware of IPR that applies to this draft" > =20 > If your answer is yes, has this IPR been disclosed in compliance with = IETF IPR rules (see RFCs 3669, 5378 and 8179 for more details)? > Please state either: > "Yes, the IPR has been disclosed in compliance with IETF IPR rules" > or > "No, the IPR has not been disclosed" > =20 > If your answer no, please provide any additional details you think = appropriate. > If you are listed as a document author or contributor please answer = the above by responding to this email regardless of whether or not you = are aware of any relevant IPR. > =20 > **The response needs to be sent to the MPLS WG mailing list.** > =20 > This document will not advance to the next stage until a response has = been received from each author. > Note, currently there is no IPR disclosure listed against this = document. > =20 > If you are on the WG email list or attend WG meetings but are not = listed as an author or contributor, we remind you of your obligations = under the IETF IPR rules which encourages you to notify the IETF if you = are aware of IPR of others on an IETF contribution, or to refrain from = participating in any contribution or discussion related to your = undisclosed IPR. For more information, please see the RFCs listed above = and = http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty. > =20 > The authors/contributors that we expect responses from are: > Tony Li > John Drake > =20 > Regards > =20 > Nic (for the MPLS chairs) > =20 > _______________________________________________ > mpls mailing list -- mpls@ietf.org > To unsubscribe send an email to mpls-leave@ietf.org = --Apple-Mail=_49D53218-9CFF-4B44-A0A3-D8D38E859828 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Are we sure = that the IPR filed against RFC6790 is not of such generality that it = also applies to this work? The patent claim text certainly seems quite = general.

I know that the WG is sensitive to IPR on = MNA as it previously rejected a solution based on it being encumbered by = IPR, making this is an important point to = consider.

Best = regards

Stewart

On 30 Sep 2024, at 13:49, N.Leymann@telekom.de = wrote:

Hi Working = Group and authors,
 
This email = initiates an IPR poll draft-li-mpls-mna-entropy in anticipation of its = Working Group adoption poll.
 
Are you aware of any IPR that applies to the = draft identified above?
Please state either:
"No, I'm not aware of any IPR that applies to = this draft"
or
"Yes, I'm = aware of IPR that applies to this draft"
 
If your answer is yes, has this IPR been = disclosed in compliance with IETF IPR rules (see RFCs 3669, 5378 and = 8179 for more details)?
Please state either:
"Yes, the IPR has been disclosed in = compliance with IETF IPR rules"
or
"No, the IPR has not been = disclosed"
 
If your = answer no, please provide any additional details you think = appropriate.
If you are = listed as a document author or contributor please answer the above by = responding to this email regardless of whether or not you are aware of = any relevant IPR.
 
**The = response needs to be sent to the MPLS WG mailing list.**
 
This document will not advance to the next = stage until a response has been received from each author.
Note, currently there is no IPR disclosure = listed against this document.
 
If you are on the WG email list or attend WG = meetings but are not listed as an author or contributor, we remind you = of your obligations under the IETF IPR rules which encourages you to = notify the IETF if you are aware of IPR of others on an IETF = contribution, or to refrain from participating in any contribution or = discussion related to your undisclosed IPR. For more information, please = see the RFCs listed above and http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualPr= operty.
 
The authors/contributors that we expect = responses from are:
  • Tony Li
  • John Drake
 
Regards
 
Nic (for the MPLS chairs)
 
_______________________________________________
mpls mailing list -- mpls@ietf.org
To unsubscribe send an email to mpls-leave@ietf.org

= --Apple-Mail=_49D53218-9CFF-4B44-A0A3-D8D38E859828--