Return-Path: X-Original-To: idr@mail2.ietf.org Delivered-To: idr@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D2EBB7B97109 for ; Fri, 24 Oct 2025 04:19:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 S98ACUvp8X6B for ; Fri, 24 Oct 2025 04:19:47 -0700 (PDT) Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by mail2.ietf.org (Postfix) with ESMTP id 1D6E47B97028 for ; Fri, 24 Oct 2025 04:18:41 -0700 (PDT) Received: from smtpclient.apple (99-188-202-8.lightspeed.livnmi.sbcglobal.net [99.188.202.8]) by slice.pfrc.org (Postfix) with ESMTPSA id 4E3CA1E24F; Fri, 24 Oct 2025 07:18:34 -0400 (EDT) From: Jeffrey Haas Content-Type: multipart/alternative; boundary="Apple-Mail=_AAD395C8-FF6D-4BAD-A94D-32629288250C" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.10\)) Date: Fri, 24 Oct 2025 07:18:33 -0400 References: <176124135265.330611.5037996948882383595@dt-datatracker-675c8fd764-bsflw> To: idr Message-Id: X-Mailer: Apple Mail (2.3696.120.41.1.10) Message-ID-Hash: RSELHSSWBJCDPKJGFDWWMVGZLDIWERZR X-Message-ID-Hash: RSELHSSWBJCDPKJGFDWWMVGZLDIWERZR X-MailFrom: jhaas@pfrc.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; 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: =?utf-8?q?=5BIdr=5D_Fwd=3A_IESG_Statement_on_Assignable_Codepoints_for_Examp?= =?utf-8?q?les_in_IETF_Specifications?= List-Id: Inter-Domain Routing Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --Apple-Mail=_AAD395C8-FF6D-4BAD-A94D-32629288250C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Most working group participants are good about using example code points = in their contributions to IDR. This list (see contents of URL) may be = of interest to newer working group participants. -- Jeff > Begin forwarded message: >=20 > From: IESG Secretary > Subject: IESG Statement on Assignable Codepoints for Examples in IETF = Specifications > Date: October 23, 2025 at 1:42:32 PM EDT > To: "IETF Announcement List" > Cc: iesg@ietf.org > Reply-To: iesg@ietf.org >=20 > The IESG has issued a Statement on Assignable Codepoints for Examples = in IETF Specifications. >=20 > 23 October 2025 >=20 > Protocol specifications and other documents intended for RFC = publication may include examples with correctly formatted and = syntactically valid codepoints to illustrate the use of a given = functionality. >=20 > Examples of codepoints are email addresses, domain names, IP = addresses, or port numbers. Codepoint values may already have been = assigned or may become assigned in the future to entities on the = Internet. >=20 > To explicitly distinguish between codepoint assignments that could be = used in production and those solely for examples in documentation (and = not production use), the IETF has reserved values for documentation = purposes and usually recorded them in a relevant IANA registry. This = practice reduces the impact or associated confusion if codepoints = allocated for documentation leak into production use. >=20 > Read the full statement: = https://datatracker.ietf.org/doc/statement-iesg-statement-on-assignable-co= depoints-for-examples-in-ietf-specifications/ >=20 > _______________________________________________ > IETF-Announce mailing list -- ietf-announce@ietf.org > To unsubscribe send an email to ietf-announce-leave@ietf.org --Apple-Mail=_AAD395C8-FF6D-4BAD-A94D-32629288250C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Most = working group participants are good about using example code points in = their contributions to IDR.  This list (see contents of URL) may be = of interest to newer working group participants.

-- Jeff


Begin forwarded message:

From: = IESG Secretary <iesg-secretary@ietf.org>
Subject: = IESG Statement on = Assignable Codepoints for Examples in IETF Specifications
Date: = October 23, 2025 at 1:42:32 PM = EDT
To: = "IETF Announcement List" <ietf-announce@ietf.org>
Cc: iesg@ietf.org
Reply-To: = iesg@ietf.org

The IESG has issued a = Statement on Assignable Codepoints for Examples in IETF = Specifications.

23 October 2025

Protocol specifications and other documents = intended for RFC publication may include examples with correctly = formatted and syntactically valid codepoints to illustrate the use of a = given functionality.

Examples of codepoints = are email addresses, domain names, IP addresses, or port numbers. = Codepoint values may already have been assigned or may become assigned = in the future to entities on the Internet.

To= explicitly distinguish between codepoint assignments that could be used = in production and those solely for examples in documentation (and not = production use), the IETF has reserved values for documentation purposes = and usually recorded them in a relevant IANA registry. This practice = reduces the impact or associated confusion if codepoints allocated for = documentation leak into production use.

Read = the full statement: https://datatracker.ietf.org/doc/statement-iesg-statement-on-as= signable-codepoints-for-examples-in-ietf-specifications/

_______________________________________________
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send = an email to ietf-announce-leave@ietf.org

= --Apple-Mail=_AAD395C8-FF6D-4BAD-A94D-32629288250C--