[ai-control] Re: New draft: draft-kelley-aipref-training-preference-signal-00

Martin Thomson <mt@lowentropy.net> Thu, 12 November 2026 18:10 UTC

Received: from flow-a3-smtp.messagingengine.com (flow-a3-smtp.messagingengine.com [103.168.172.138]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 5C05C46 for <ai-control@ietf.org>; Thu, 12 Nov 2026 18:10:58 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=lowentropy.net header.s=fm1 header.b=BD2hMbEY; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="c cwWRgk"; spf=pass (mx.ietf.org: domain of mt@lowentropy.net designates 103.168.172.138 as permitted sender) smtp.mailfrom=mt@lowentropy.net; dmarc=pass (policy=none) header.from=lowentropy.net
Received: from phl-compute-04.internal (phl-compute-04.internal [10.202.2.44]) by mailflow.phl.internal (Postfix) with ESMTP id 18CE01381B37 for <ai-control@ietf.org>; Thu, 12 Nov 2026 13:10:58 -0500 (EST)
Received: from phl-imap-15 ([10.202.2.104]) by phl-compute-04.internal (MEProxy); Thu, 12 Nov 2026 13:10:58 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm1; t=1794507058; x=1794514258; bh=8PpuNi8rHPptXmMY19ANzjvvYt8W8ZYk As0ly/h0a3w=; b=BD2hMbEYohxHdPYRj0UfN0TsxLnAH8DCYjDV3zL8DJmoJsnV Xo1/IMt98ozUOsL8jjGrjI/vUWHS04dDXnzojeEgGHR7GVmOQTiXRj1/mOjat3vn op93uCoXJzHRGqMcVwRQ9WQzA8d4O/9QqT8/t4dNv1D6YyoJ0mxKltfxVh4QqpHh Gdk1m1tYf6vcU5yJu/bqO+MVHoWmi+fBHkoMmzc3wJc4+k1WIbZXLUVQUEuxRFtH OwlR6MsJIIOWIsPnvKzoPL1ReYmPKe1Piz9KbpJYCM42jG7V7v9/aR/4lYaUPFhu +hWCuBJdF8yfRME5GLRw4VRXsrIOFFnHAZWPtg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1794507058; x= 1794514258; bh=8PpuNi8rHPptXmMY19ANzjvvYt8W8ZYkAs0ly/h0a3w=; b=c cwWRgk53t/BnkmcIGmF4DDNPYSlD2iIlBt2PCnfrT0x4e/fi/W1ZSNeG1SjLvCB5 UOeb12n/1khc+1u+blhJTx3BjgMTvw4eUnJ+YnObLgfjlHpC5pFrSQxxdEvkG8kq iwtbaSCEEI0/n35SNwAx4mqqAIUCexwKwayK/85Z7van/C03M5vchKJE8/1Q3fzm MjcCqgeYU5d1esIcA5eIlP0uEoIMUO2qdG9CvADKQEz4D+XtvlRP0OzoO0Yfipki N3nbyJlurC7aNufWV5bHQfyneqfnOoROco6vf/RHYS+sObiTicsfLVazFJG4Xdx0 fdQlAzJNRdBuczLc0t5Xg==
X-DKIM2-Info: draft=ietf-dkim-dkim2-spec-09; repo=github.com/dkim2wg/interop; date=2026-11-03; sw=lmtpprox; action=sign d=lowentropy.net a=rsa-sha256;
DKIM2-Signature: i=1; m=1; t=1794507058; d=lowentropy.net; mf=PG10QGxvd2VudHJvcHkubmV0Pg==; rt=PGFpLWNvbnRyb2xAaWV0Zi5vcmc+; s=fm1:rsa-sha256:T5/4xFu9/8/HUazHreziDDEo0vk4szZcGi/DCmjWUzHZ1Nd 0Uk9JzzOVQdis1MGzItOaJ9FjSccgi29LN2bsor8Bq4NBo2eRoiAqUmp3PPtvvRe lSc2gtaZirfGqwz38d7qqbuwwaSbpvSyBUDRD9VM7PZMRdGOe0P+VR81ix3m7Bme 6O4zB3RXIiyBbufjbhrUOX9g/2laLMKbKu8SocD9imict9qdudzJNhhXVxNyVKUs RIaApeHrY3TdlmSrhxwfEEVRm+iR0u2kEQtoQDtlb/gwEz0wdxdxkMBp47xufuoy 2/fQjyfYT2uNV8r5V7hmE+D6I/L3MRhHSdiftEw==;
X-DKIM2-Info: draft=ietf-dkim-dkim2-spec-09; repo=github.com/dkim2wg/interop; date=2026-11-03; sw=lmtpprox; action=mi-m=1; hc=12; hn=cc,content-transfer-encoding,content-type,date,feedback-id, from,in-reply-to,message-id,mime-version,references,subject,to;
Message-Instance: m=1; h=sha256:1UI8oc2P1iucXtmn7P8UYiPqvqbb349gZ2+LNO6bEvE=:abfB1C1cvnzZbQD+ANpNH4phCRVHHtBNRTK+ATWxYK4=;
X-ME-Sender: <xms:MQH2aq0df_TCwHqdy0TpW9JfWLNFCY6ahQ90uvhlZN07J2pQJx50Aw> <xme:MQH2an7k04vCGXS7HBvRkb5yn4utqlgWU6Gn9JmtNwtP3Lxe4aI_3sANBE6X4dXJT CS4P86G8Io9JwNgR3Xt4F2MB4D7TgSrw_6GruXsrVOyJzg6wmNdNJ4>
X-ME-Proxy-Cause: dmFkZTFBHBuSQtloBXFlziC3igxC99k7qvFJjkcgbvl+w8Rct1Ucra55olltiVTZWZFLn5 t45uYnwUgo6dh0ogfzxg5dML3GLx6oPpBrIbeskWkUGckNH1nQiQPSe2d5W5mBblcwJDHh 30vPUQwOVuY5Rxnd1eHvrieQ1UBizN5sEe1Hu1iS4ZtSFRMtLRtZBhK54P3AZOuRj4zE1z nqutKDS2kqmlXriwoj9HiEkxc6zFFNpTY9t3HrF+rzquWP7BqFIUFC6QogZxWbgDl/FMEY frPYwlSqInQGKisxnbG6yyMkpDtyqQJlMox9GcfEYwbeLV88SYOOy1BV7Pwo8+bbDxGyme QNVFUX93BK6StgxCV1+VnZ12JSSsrzT7CPf7L5SnZikRjBr2IXLV4eM/sL3Cw4BsweGFkd pi2bupFxsD5dD/ZLmvVxtHF4zJMn6AlPfhFWY+W/RQhqjKA6D2vGfZfzSzi5n0vakJz3LX sTW9u6BjBzLqwK8b37YxKqk7jSVWO9XvsMptKuJGXk7JEI2xCB327SBmuWYpkaNOh24CDh oko7Okzq+sR1XSidLwoHz+4eUl2TLKU2ii2VYLPK7yvgjBDRJ6R1SDVQ2fkD9udd189zCF P6NceIEZuD1bpcdUR9wwlIzmSxdFNoIH15b8N5+xDo0y3LKcTOsXphhqxJBA
X-ME-Proxy: <xmx:MQH2aj1c-A7lg7MT2IMu5a9gPOaQSnuPjIJ4X3KSZrmOGQbJX5jUQg> <xmx:MQH2aoGzbUnPmO2VzF_vxT-EAqkAs2vGfUZHx1ZHcLPGw6QqW9tHpg> <xmx:MQH2ahhKMGBrccKWmif7G2fgiZt89MxeSH_HhZa0J4LmRQLPftr1aw> <xmx:MQH2aj9lG50cLnMdeDrYL1r8QPb4VONu99AeIHqLDox61ZXaYPROfg> <xmx:MgH2alCi1sUmSRWMuc0EC4QMQHOkomnPrvmZmRpWgFxrDTLdi7gkqjpv>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.phl.internal (Postfix, from userid 501) id C86C3780070; Thu, 12 Nov 2026 13:10:57 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
MIME-Version: 1.0
X-ThreadId: Aj3RCxZbecaN
Date: Thu, 12 Nov 2026 10:10:36 -0800
From: Martin Thomson <mt@lowentropy.net>
To: Kevin Kelley <kelleyk-ietf@kelleyk.net>
Message-Id: <353315da-0141-4a0f-b5ef-2366394f3f73@app.fastmail.com>
In-Reply-To: <1d9c01dd72c9$8b63f640$a22be2c0$@epceurope.eu>
References: <CAGfqOAY_t6UmzZw+nYzTfRVhyHuGb7RyEwmcwetwAF01f4ONbA@mail.gmail.com> <CAOC05+J7Zs97jXaAvwU_a1LimYMfTkExULWADY3F=z1Dnip=GA@mail.gmail.com> <CAN99zG35KyYTFVeDYD1UW6fWkUn+ojr3zxRn6aR1DhD07wsURA@mail.gmail.com> <CAGfqOAbd0PmA9VR2OYXVDGFH_iraA94gFm5u+pDg08uFGtR9GQ@mail.gmail.com> <CAGfqOAZwS2bO0_iKaHG7Q42KfZCpb7+ukj_FLZ2m5xHoOHeWDg@mail.gmail.com> <CA++fB=oucjGZiyyhLAUvw-XAJRxxV0hAzzzRhtJLCz7PpQfAVg@mail.gmail.com> <C96DE6CA-006C-4E2E-A8D6-B455A73A136B@skgo.org> <1d9c01dd72c9$8b63f640$a22be2c0$@epceurope.eu>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Spamd-Bar: -------------------
Message-ID-Hash: 7GAFT2OJ4TNOBBTTL666IMXH7F4OCDFD
X-Message-ID-Hash: 7GAFT2OJ4TNOBBTTL666IMXH7F4OCDFD
X-MailFrom: mt@lowentropy.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "ai-control@ietf.org" <ai-control@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [ai-control] Re: New draft: draft-kelley-aipref-training-preference-signal-00
List-Id: AI Control <ai-control.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ai-control/PM_ytXENx5aIn02kwvonMoGDniw>
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>

(I'm not singling out Angela's email in particular...)

This is perhaps a timely reminder of how our processes interact with the notion of "voluntary adoption".  At the same time, the IETF has a long tradition of deployment in parallel with its work. That does not always involve a public discussion of those deployments.  Sometimes, that looks a lot like proprietary solutions being deployed.  How those are viewed is always tricky, as deployment experience is valuable, but it can also front-run ongoing discussions in ways that can encumber them awkwardly.  It's important not to get too bogged down in the details.

(I'm specifically not addressing the acknowledgments issue here. I read that as Kevin showing his appreciation and respect for the people who have engaged in the process, nothing nefarious.  Acknowledgments like this do not imply endorsement in any way; IETF docs reserve "contributors" lists for that.)

On Thu, Nov 12, 2026, at 09:16, angela.mills-wade@epceurope.eu wrote:
> Thanks Kevin for these clarifications but I have two main concerns.
>
> Firstly that the announcements and accompanying publicity came before 
> there had been an opportunity for the wider group to discuss the 
> proposal and its implications. To be blunt it looked as if you had 
> cherry picked only part of the vocab and wrapped your own 
> implementation around it. This left me wondering about its relationship 
> with the collective work already under way, and how it was possible for 
> implementation decisions to be taken outside the main group. 
>
> Secondly, I was just as surprised as Alex Gibson to have been 
> accredited this way as I had only contributed to the vocab work track, 
> and then only occasionally, so do not want my name associated with your 
> announcement. 
>
> For publishers, training is only part of the picture because meaningful 
> distinctions between search and the use of journalism to generate AI 
> answers are particularly important. I appreciate that some definitions 
> require further work, but would welcome reassurance that by taking 
> training forward as you did still leaves a clear route for those wider 
> choices, with publishers involved in shaping them.
>
> In future, an opportunity to discuss these questions together before 
> further public announcements would also help build confidence in the 
> process.
>
> All the best,
>
> Angela
>
> From: Srecko Jovancevic <Srecko.Jovancevic@skgo.org> 
> Sent: 12 November 2026 11:52
> To: Nate Hake <nate@travellemming.com>
> Cc: Kevin Kelley <kelleyk-ietf@kelleyk.net>; Alex Gibson 
> <agibson@newscorp.com>; ai-control@ietf.org
> Subject: [ai-control] Re: New draft: 
> draft-kelley-aipref-training-preference-signal-00
>
> Wondered the same,  No clue
> Sent from my iPhone
>
>
> On 12. 11. 2026., at 12:51, Nate Hake <mailto:nate@travellemming.com> wrote:
> 
> Kevin - 
>
> Do you know why these announcements were all made right around October 
> 30, 2026? Like, why this specific time and not some other time? Did 
> some event prompt the timing here (if you know)? 
>
> Thanks, 
> Nate 
>
>
>
> ***
>
> Nate Hake
> Founder
> https://travellemming.com/
>
>
> On Thu, Nov 12, 2026 at 8:08 AM Kevin Kelley 
> <mailto:kelleyk-ietf@kelleyk.net> wrote:
> Mark, Alissa, Nate,
>
> My draft was intended to be a self-contained description of what I was 
> announcing, and not a wholesale replacement for any of the Working 
> Group’s efforts.
>
> It doesn't contribute anything particularly novel on the vocabulary 
> side, since the "AI training" definition it uses is exactly the one 
> from the Working Group's current draft.
>
> I included that term and not others only because that definition was 
> the first to stabilize.  We’ve done some refactoring, added some 
> clarifying examples, and so on, but there hasn’t been much discussion 
> about whether we’re drawing a line in a useful place or about the meat 
> of the definition in quite a while.  In contrast, we set aside 
> discussion of inference-time use to make progress on training, and my 
> sense is that there are still more philosophical conversations to be 
> had there.
>
> I have a lot of respect for the IETF process and for the work we’ve put 
> into finding common ground in AIPREF.  The multilateral nature of the 
> group is what makes the work we’re doing together practically useful 
> for everyone involved (in contrast to the variety of unilateral 
> attempts at addressing similar problems); and I was concerned that 
> folks would not appreciate it if I announced signals based on less 
> stable definitions.  If I read that incorrectly, and you would have 
> preferred that I had included more of the vocabulary, that would be 
> useful feedback, and I hope you feel comfortable sharing it, either 
> here or in private.
>
> Like I said in my first message in this thread, I’m committed to 
> continuing to participate in the Working Group, and to working with 
> everyone to try to describe, and find mutually workable definitions 
> for, other interesting categories of use.
>
> The draft does contribute on the attachment side, which was necessary 
> because that work has been on hold in the Working Group while we’ve 
> been focused on the vocab.  As much as the history of robots.txt makes 
> working with it delicate (which I hear some people pronounce 
> “frustrating”), I’ve always seen attachment as a much more mechanical 
> part of the problem.  I landed in the place I described in my 
> individual draft while navigating a long list of interoperability 
> issues.  That work *is* something that I wanted to offer to the Working 
> Group, though more because I hope it lets us make progress as we sort 
> out vocabulary issues than because I’m attached to the specifics.
>
> On the concerns around the lack of intentionally extensible syntax: my 
> initial drafts were actually written that way!  I pulled that out of 
> the version that I submitted as -00 based on strong off-list feedback 
> suggesting that it made the draft harder to follow.
>
> I’ve posted a draft that updates RFC 9309 to add namespaced labels, and 
> will submit it once the Datatracker reopens.  You can read that here, 
> though it’s purely focused on how to get robots.txt to carry distinct 
> signals:
>
>   
> https://kelleyk.github.io/draft-kelley-rep-namespaces/draft-kelley-rep-namespaces-00/draft-kelley-rep-namespaces.html
>
> Mark, I’ll also open a PR against the attachment draft that proposes 
> defining a “usage” namespace and mapping the entire vocabulary to 
> labels in it.
> Happy to answer questions here, or you are all welcome to reach out 
> directly or pull me aside in SF if you'd prefer.
>
> Cheers,
>
> -K
>
> On Wed, Nov 11, 2026 at 4:38 PM Kevin Kelley 
> <mailto:kelleyk-ietf@kelleyk.net> wrote:
> Alex,
>
> I see the draft I submitted as describing a checkpoint in the Working 
> Group's work, so it felt important to me to acknowledge everyone who 
> came together to do that work rather than submitting a draft with only 
> my name on it (which felt a little bit too much like taking credit for 
> other people's work).  My intention was never for that list of 
> acknowledgements to imply any sort of endorsement, though re-reading it 
> now that might be a little bit less explicit than I'd thought; for 
> example, I describe the list as people who "shaped the Working Group's 
> discussion".
>
> For example, you joined us at the last in-person interim in London, and 
> appear on the bluesheets for several virtual interims and other IETF 
> meetings.  Max appears on the bluesheets for almost every AIPREF 
> session since the Working Group started, including main IETF meetings 
> (122 Bangkok virtually, 123 Madrid, 124 Montreal, 126 Vienna), most if 
> not all of the virtual interims, the London design team meeting, and 
> the in-person interims in Zurich, Toronto, and London.  That felt worth 
> acknowledging.
>
> I can't submit a new version of the draft right now because the 
> Datatracker is locked, but I'm happy to make changes.  I'll make it 
> more explicit that acknowledgement does not imply endorsement, or 
> participation in my individual draft (versus participation in the 
> Working Group, whose work my draft borrows wholesale).  If you would 
> like me to redact your affiliation, or to remove your name entirely, 
> I'm happy to do that, to; just let me know what you'd prefer.
>
> If Max or anyone else I listed is feeling similarly, then: I apologize 
> in advance; just shoot me a note off-list and let me know what you'd 
> prefer.
>
> -K
>
> On Tue, Nov 10, 2026 at 1:34 PM Alex Gibson 
> <agibson=mailto:40newscorp.com@dmarc.ietf.org> wrote:
> All,
>
> Per the email below, Kevin Kelley of Anthropic has posted an 
> Internet-Draft, "Machine-Readable Training Preference Signal," to the 
> IETF AI Preferences Working Group page. Its Acknowledgements section 
> lists Max Gendler and me, with our News Corp affiliation, thanking us 
> for "substantial contributions to shaping the Working Group's 
> discussion" and for our "partnership."
>
> Neither of us contributed to this draft or worked in partnership with 
> Mr. Kelley or Anthropic. News Corp does not support the proposal.
>
> Please remove our names from the draft. Please also do not use our 
> names, or News Corp's, in any way that suggests we took part in or 
> support it.
>
> -- Alex Gibson, News Corp
>
> From: Kevin Kelley <mailto:kelleyk-ietf@kelleyk.net>
> Date: Sat, 31 Oct 2026 at 2:39 am
> Subject: [ai-control] New draft: 
> draft-kelley-aipref-training-preference-signal-00
> To: <mailto:ai-control@ietf.org>
>
> Howdy everyone,
>
> I've just submitted a new I-D, draft-kelley-aipref-training-preference-signal:
>
>     
> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-kelley-aipref-training-preference-signal/__;!!F0Stn7g!DsFbaCWfaZxD1CdexVxtBKS5hVsyjYUqWPHnUdSpSHGnd2ruvnz_eHCHBMhthuUwBMpLXdDa2HSSlF0$
>
> It describes a way to express AI-training preferences in robots.txt 
> without adding any new grammar. A site operator writes an ordinary rule 
> group whose User-Agent line names a "policy token":
>
>     User-Agent: __usage_ai-training
>     Disallow: /
>     Allow: /press-kit/
>
> This reads as "a preference against AI training for everything except 
> /press-kit/, and a preference in favor of it there." Lookup uses the 
> usual RFC 9309 path matching and longest-match precedence.
>
> This is a preference about use, not a traffic-management signal; the 
> two are intentionally separate, and ordinary rules for a crawler’s own 
> product token still govern fetching (though the draft does ask crawlers 
> not to fetch what they can’t use).
>
> This differs from the attachment draft that we put aside in order to 
> make progress on the vocabulary.  Like I've mentioned, I've spent a lot 
> of time investigating how deployed parsers would interact with a wide 
> variety of ways of expressing preferences in robots.txt files.
>
> The mechanism in my draft uses only existing syntax, so parsers and 
> crawlers that don't implement it but comply with RFC 9309 should 
> gracefully ignore preference expressions and still receive other 
> signals. It also avoids relying on the areas where deployed parsers 
> behave differently (and let me tell you, there are plenty!).
>
> And it builds on prior art: some crawler operators already publish 
> tokens that control how content is used rather than which crawler can 
> fetch it.  The draft introduces the term “policy token” as a 
> vendor-neutral name for that pattern, and calls the existing 
> vendor-specific ones “proprietary policy tokens”.
>
> Wildcard groups never match the new, vendor-neutral policy token, so 
> existing User-Agent: * rules aren’t read as expressing a preference, 
> which was a deliberate design goal. As a result, a robots.txt file that 
> doesn’t use this mechanism, as is true of every one published today, 
> expresses no preference at all.  Rules for crawler product tokens and 
> proprietary policy tokens keep whatever meaning they have today. 
>
> I’m proposing this as input to the WG’s attachment work, and I'm 
> planning to open a PR against the attachment draft to get thoughts from 
> all of you.  I'll try to explain my thinking a little bit more there.  
> (Thank you to everyone who's already weighed in off-list!) 
>
> On the vocabulary front, the policy token takes its meaning directly 
> from the "AI Training" definition in draft-ietf-aipref-vocab-08.
>
> I'm also excited to share that Anthropic has already started 
> implementing support for this draft.  This complements our existing 
> crawler controls rather than replacing them.
>
> It'll take us some time to add support across our services and work 
> through the inevitable complications and edge cases that I'm sure we'll 
> discover.  Also, as standards in this area evolve, how we interpret and 
> apply these signals may change.  I'm looking forward to what we'll 
> learn from having "running code" in the field and how that will inform 
> the work we still have to do together.
>
> I'm very pleased that, over the coming months, all of our hard work 
> will start to become something that website publishers can use.  
> Putting a working signal in people's hands feels like tangible evidence 
> that all of the effort and heart we've put in, and all of the long 
> hours and long flights, are paying off.
>
> We hope that others will join us and make this a single signal that is 
> respected across the Internet.
>
> I'm curious to hear everyone's reactions and happy to answer any questions.
>
> On a personal note:  I'm incredibly grateful to everyone who has 
> invested time and effort in the WG's work and engaged in good faith, 
> from every point of view.  I hope this is just the beginning of what we 
> can ship together, and I look forward to seeing all of you in San 
> Francisco.
>
> Cheers,
>
> -K
> _______________________________________________
> ai-control mailing list -- mailto:ai-control@ietf.org
> To unsubscribe send an email to mailto:ai-control-leave@ietf.org
>
>
>
>
> This message and its attachments may contain legally privileged or 
> confidential information. It is intended solely for the named 
> addressee. If you are not the addressee indicated in this message (or 
> responsible for delivery of the message to the addressee), you may not 
> copy or deliver this message or its attachments to anyone. Rather, you 
> should permanently delete this message and its attachments and kindly 
> notify the sender by reply e-mail. Any content of this message and its 
> attachments that does not relate to the official business of News 
> Corporation or its subsidiaries must be taken not to have been sent or 
> endorsed by any of them. No representation is made that this email or 
> its attachments are without defect.
> _______________________________________________
> ai-control mailing list -- mailto:ai-control@ietf.org
> To unsubscribe send an email to mailto:ai-control-leave@ietf.org
> _______________________________________________
> ai-control mailing list -- mailto:ai-control@ietf.org
> To unsubscribe send an email to mailto:ai-control-leave@ietf.org
> _______________________________________________
> ai-control mailing list -- mailto:ai-control@ietf.org
> To unsubscribe send an email to mailto:ai-control-leave@ietf.org
>
> _______________________________________________
> ai-control mailing list -- ai-control@ietf.org
> To unsubscribe send an email to ai-control-leave@ietf.org