IETF Logo Mail Archive

Re: [quicwg/base-drafts] Auth48: Should any drawings be sourcecode? (Issue #4948)

Mike Bishop <notifications@github.com> Thu, 17 February 2022 18:48 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2510E3A0F29 for <quic-issues@ietfa.amsl.com>; Thu, 17 Feb 2022 10:48:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level:
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aI9-IjLK1X1q for <quic-issues@ietfa.amsl.com>; Thu, 17 Feb 2022 10:48:03 -0800 (PST)
Received: from smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 797443A0F05 for <quic-issues@ietf.org>; Thu, 17 Feb 2022 10:48:03 -0800 (PST)
Received: from github-lowworker-a6a2749.va3-iad.github.net (github-lowworker-a6a2749.va3-iad.github.net [10.48.16.62]) by smtp.github.com (Postfix) with ESMTP id 6F4A75607EA for <quic-issues@ietf.org>; Thu, 17 Feb 2022 10:48:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1645123682; bh=vkG24xEUZGp1Oeczrh/+r0/Gv8MYbGHsrzh/PtS1yyA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=joQCNlUNsagg9i4bIQomYeTvPWfD8FHG3BXQTIlz9lT63kh/Bp7L0GB/AFthWRSYe 9dbLXWA1r+/n2h72TPBwNlfAhbYAJmw9KD+nkOjRTuKPa0SSvIWvAbhnO2XnI0AgcY eVTS+88EvUo35cYCPYGYXeDeOS6bB9gCNRBFLvnQ=
Date: Thu, 17 Feb 2022 10:48:02 -0800
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5S6UOECNPLRW4TSFWADJ4WFEVBNHHEHTPL7M@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4948/1043296135@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4948@github.com>
References: <quicwg/base-drafts/issues/4948@github.com>
Subject: Re: [quicwg/base-drafts] Auth48: Should any drawings be sourcecode? (Issue #4948)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_620e98626067c_3c82c6fc1680138"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/XGtpBs9fuwh91fjkzdAkrsUl-jI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2022 18:48:07 -0000

My XML-fixup PR will include the change from `drawing` to `ascii-art`.  Having reviewed the artwork instances, they are all stream headers and frame layouts.  The guidance for sourcecode says:

> For artwork such as character-based art, diagrams of message layouts, and so on, use the [<artwork>](https://authors.ietf.org/rfcxml-vocabulary#artwork) element instead.

Therefore, I'm going to close this issue and say no further change is needed.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4948#issuecomment-1043296135
You are receiving this because you are subscribed to this thread.

Message ID: <quicwg/base-drafts/issues/4948/1043296135@github.com>

v2.8.7 | Report a Bug | By Email