Re: [media-types] image/svg+xml+gzip
S Moonesamy <sm+ietf@elandsys.com> Fri, 05 April 2024 15:31 UTC
Return-Path: <sm@elandsys.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBD4FC1516F8 for <media-types@ietfa.amsl.com>; Fri, 5 Apr 2024 08:31:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 OrDQUB9FT7xh for <media-types@ietfa.amsl.com>; Fri, 5 Apr 2024 08:31:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 23075C1516F3 for <media-types@ietf.org>; Fri, 5 Apr 2024 08:31:16 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.79.19]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 435FUtcD002679 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Apr 2024 08:31:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1712331067; x=1712417467; i=@elandsys.com; bh=DC0caL4cn3uQtOR5GBKt2EmQ/GmyTcJqtIns01h3epI=; h=Date:To:From:Subject:In-Reply-To:References; b=snySeVrL8fFfIWUl5ITfLMAYwshZ1erNRwzvXqjnf4y/3/Wd93FBd7SMy3U+p6s/r VWt1/aURg3gu51MJgXiRXEJy4+APMeGjqsD2rD+kB8Hc2pYbQMO4CcCuwQBIhx+6Id YGwugFRtt293FVvbm+5QNZVXdU6bMoiUPC8IssJU=
Message-Id: <6.2.5.6.2.20240405070749.0dd8ed20@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 05 Apr 2024 08:30:30 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>, media-types@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CAL0qLwbUUquHHMWFMOmR1usBmQP63U6KTqHYg2dfmpPULsHyeA@mail.g mail.com>
References: <CAL0qLwZw5gsOTGtPHY9hKGL9dCzfAsEh3=zzeLW3rQJwiZrMHQ@mail.gmail.com> <6.2.5.6.2.20240403130637.12bcd340@elandnews.com> <CAL0qLwbUUquHHMWFMOmR1usBmQP63U6KTqHYg2dfmpPULsHyeA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/3jXq1ur-IQBWjcyj8KMw-v5K27o>
Subject: Re: [media-types] image/svg+xml+gzip
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2024 15:31:20 -0000
Hi Murray, At 06:04 PM 03-04-2024, Murray S. Kucherawy wrote: >It did, but an oversight means it didn't follow the BCP for how one >registers, and gets reviewed, a new media type. I don't believe >IETF consensus exists to bypass the relevant BCP, and I'm quite sure >a processing error should not be able to bypass a BCP. I would suggest following the registration policy for the media type. The Document Shepherd did not list any concerns about media type. The IESG and other reviewers went through the specification. Publication was approved. Ten months later, there is a discussion about the registration of one of the media types used in the Proposed Standard. >Yes, that's an option. I agree that we have discretion to >grandfather this in, but that would be under a set of rules not >currently defined and with uncertain forward-looking effects, both >of which MEDIAMAN was chartered to address. I wanted to check with >the community before we make such a decision. I am looking at the two (please see quoted paragraphs) topics separately. The working group (which is not this mailing list) could make recommendations which, for example, prohibit a request such as the one under discussion. Regards, S. Moonesamy
- [media-types] image/svg+xml+gzip Murray S. Kucherawy
- Re: [media-types] image/svg+xml+gzip S Moonesamy
- Re: [media-types] image/svg+xml+gzip Murray S. Kucherawy
- Re: [media-types] image/svg+xml+gzip Mark Nottingham
- Re: [media-types] image/svg+xml+gzip S Moonesamy
- Re: [media-types] image/svg+xml+gzip Mark Nottingham