IETF Logo Mail Archive

[ai-control] [Question] Priority conflict between HTTP Header and Robots.txt in draft-ietf-aipref-attach

happypants <1195600347@qq.com> Fri, 27 February 2026 09:26 UTC

Return-Path: <1195600347@qq.com>
X-Original-To: ai-control@mail2.ietf.org
Delivered-To: ai-control@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 1075DBF6EFE7 for <ai-control@mail2.ietf.org>; Fri, 27 Feb 2026 01:26:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 1.099
X-Spam-Level: *
X-Spam-Status: No, score=1.099 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, FROM_EXCESS_BASE64=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, NO_FM_NAME_IP_HOSTN=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=qq.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C2WksRjH104p for <ai-control@mail2.ietf.org>; Fri, 27 Feb 2026 01:26:08 -0800 (PST)
Received: from out203-205-221-236.mail.qq.com (out203-205-221-236.mail.qq.com [203.205.221.236]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 704F9BF6EFDD for <ai-control@ietf.org>; Fri, 27 Feb 2026 01:26:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qq.com; s=s201512; t=1772184365; bh=1roFfmGhlZLY++2z7P2fbnQR0cAIZ9JSQe/cyvjiYoc=; h=From:To:Subject:Date; b=NLdy/DUyR+HQWJX+gRKgqzB1SqeejEduF4W6wM0cLsoWhtBSq5uPpNJh310zDNsxb omQC27y2x2x7a0jFi4FtKLJD+2RIzQSeZihU0t1zXs5rKoncJUXCsCelE5YSowClPP jby3fzUGPN0Dhzsll46UOtZ1/WmhXCSTZIXqUagY=
X-QQ-XMRINFO: OJlEh3abS6gXFhL1Ch7aJr+meQ2T6qVBAw==
X-QQ-XMAILINFO: OL8zF8Nz2fr0e+AfsOdp1z08T2rGvsTnY7T+jD5RHsGvZgbkbnQefX74ZJ/vbi R22cS7FlK4Jo+p/oLtZzhqOaqe+MW+1Ce7xkWramPkRI3doYmtnRuYUuFSixrLDpYu7l0M08jaVNR 9WnySib1PyawWk0awVWQqVPxMS1Ueeiaa6+wEe/kCWlYuP7tteeTLK8rJjNDbrH1SKqu/QWwIafR6 TFfaFB32sX2deIyF9kq+G3gqo8zS21rOS64CPYu8PMoFOoi8SVLsFmei/VvrYewUKwOFHfPBh9RQs FrRIZf4H/zn9HfZ/O104l/vQALG8acf231Erg72xmD4BRZ7SJ82Cc8H3gKqCczfpVOWwh8q1R22Co lY7OG+LSxVIvAaNnaSSo+sJP2o9cbOL05WNTeFXowDbbFeY5+heVgdcp+vY+k054ktwjTFbXQoVtw fMIOxLvArDhIz3M5Nu/0J/wZsvA5IBMgSaMfACH3KQ2SUHeNojwblrH5gSleBum6BhLz1edTwIu07 8mdgWZ9GzSRZ0SsRbyWX+gLaBXYiKGjM+eAO70HiOyoIQfhRoB2TLUVfl+elpQJXgX5HSRFmp2rr3 bgSVyCjpxoRzz/8S8H5KJQYTgq3d4GjMbYQrxZW1BH2AFvRZV+yeY5pAfdzeQ4ZWEKhzgPvS7B3rl ayvMAYGT9Gl8tvQqokO7cwOWjX4BgNZqretA4AJ9iLU/AjP6BTnVeYTR4Am1GVUyBV6k7+9mXVz9l xhslYy3Uqp8wBk4HG/yP6Mb4LPC3fcNSUiql4SU56ose/8vroxGpWTTZnnSjcy+lWJh2BvmB/CGwD 2pacWxI1BLZkhQPo9zXtHoX5mEje0Bl2JO3GX6SfbrLlVttxdjqUSgeY6RCFCJYDpUwJPxbGFdzn7 xq/IvlyYDFdekCmrP5Ei01w8N3REPOpLm8b9Tn2+GFchMF9JXNJLah9DMRyMSSkQiYO+4TvJ/+Nxr 9MnyKokDqlasbWLKmeYJ29ycCDE6zwEtKiB6q5dNRZTw7G1W36QDJrUoaiY9a57WbSe67TD9mSPRo CLToQ+vq+HUCcyZk+nQKQYpQbZ1QrEAZTmfBBr17Ae3AJErM=
From: happypants <1195600347@qq.com>
To: ai-control <ai-control@ietf.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_69A1632B_F133F500_5AD97B58"
Content-Transfer-Encoding: 8bit
Date: Fri, 27 Feb 2026 17:26:03 +0800
X-Priority: 3
Message-ID: <tencent_BF019236E61CCA0F36BF96B86EC1ECC29506@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
X-QQ-mid: xmsezc43-1t1772184363txw196rhh
Message-ID-Hash: 25UHQEPAPZPGOGCLZTROI6SECHE3XWFH
X-Message-ID-Hash: 25UHQEPAPZPGOGCLZTROI6SECHE3XWFH
X-MailFrom: 1195600347@qq.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [ai-control] [Question] Priority conflict between HTTP Header and Robots.txt in draft-ietf-aipref-attach
List-Id: AI Control <ai-control.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ai-control/v21qsfZmpt-pJciVWBrVxzLBGBI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ai-control>
List-Help: <mailto:ai-control-request@ietf.org?subject=help>
List-Owner: <mailto:ai-control-owner@ietf.org>
List-Post: <mailto:ai-control@ietf.org>
List-Subscribe: <mailto:ai-control-join@ietf.org>
List-Unsubscribe: <mailto:ai-control-leave@ietf.org>

Hi everyone,
I am a new participant from Nanchang univeristy, and I am currently reviewing the draft-ietf-aipref-attach&nbsp;to understand how to associate AI usage preferences with content.
I have a question regarding priority conflicts.
As defined in the draft:

Section 2&nbsp;defines the Content-Usage&nbsp;header field for HTTP responses.

Section 3&nbsp;defines the Content-Usage&nbsp;rule for the Robots Exclusion Protocol (robots.txt).
What should be the expected behavior if these two mechanisms provide conflicting&nbsp;instructions&nbsp;for the same resource?
For example:

The HTTP header says: Content-Usage: train-ai=y&nbsp;(Allow training)

But the robots.txt says: Content-Usage: train-ai=n&nbsp;(Disallow training)
Which one should the automated system (crawler/AI) prioritize? Is there a defined hierarchy, or should both be considered simultaneously?
This is a practical scenario I am curious about, especially for webmasters who might configure these separately.
Thanks for any clarification!
Best regards,
Yudong Sheng




happypants
1195600347@qq.com

v2.45.0 | Report a Bug | By Email | System Status