Re: [media-types] image/svg+xml+gzip

S Moonesamy <sm+ietf@elandsys.com> Wed, 03 April 2024 20:21 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 BE0A2C14F61D for <media-types@ietfa.amsl.com>; Wed, 3 Apr 2024 13:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.685
X-Spam-Level:
X-Spam-Status: No, score=-6.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 bC7b8IryhCeS for <media-types@ietfa.amsl.com>; Wed, 3 Apr 2024 13:21:11 -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 3BA97C14F61B for <media-types@ietf.org>; Wed, 3 Apr 2024 13:21:11 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.91.236]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 433KKslC004948 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Apr 2024 13:21:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1712175666; x=1712262066; i=@elandsys.com; bh=2Y9YuN0+ZI8CcZK0Qlapm1sahyypkTznWffLg1SsX54=; h=Date:To:From:Subject:In-Reply-To:References; b=218dIgJZZHlIaKAgc/c0SK7rqaPmc8m4IzuuGJTLhiek+NrXzoaRDCIhlq3YAxQXc antgpaJVmakegX+whF4qeJ1nR3lN1dOUcCOg/gwq6MtSG3qxKZGc1wa4U0xUX+VlpZ XtR3JAp1cGUDnP27k8CLIhM65kOsAL5vSBJy6o0o=
Message-Id: <6.2.5.6.2.20240403130637.12bcd340@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 03 Apr 2024 13:18:47 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>, media-types@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CAL0qLwZw5gsOTGtPHY9hKGL9dCzfAsEh3=zzeLW3rQJwiZrMHQ@mail.g mail.com>
References: <CAL0qLwZw5gsOTGtPHY9hKGL9dCzfAsEh3=zzeLW3rQJwiZrMHQ@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/x-FW_leH_oBPpOwZIeQ7MQaKbXc>
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: Wed, 03 Apr 2024 20:21:16 -0000

Hi Murray,
At 11:36 AM 03-04-2024, Murray S. Kucherawy wrote:
>A situation has been brought to the IESG's attention for assistance, 
>and it falls squarely into the media type suffixes problem space.
>
>The above-named media type has been referenced in RFC 9399.  It was, 
>however, never registered, and this document neglected to notice 
>this and include the registration.  So now we basically have a 
>proposed standard squatting on a code point.  Even better, the 
>registration includes multiple suffixes, and we don't know exactly 
>what that means, which is one of the things MEDIAMAN was chartered 
>to specify.  We've been asked to sort this out as the type is 
>apparently starting to get used.

The formats were referenced in a Proposed Standard.  That document 
must have met the bar for IETF Consensus.

>So this adds a dash of urgency to the question we discussed at the 
>mic at 119 and continued discussing when Meetecho came to tear down 
>the A/V setup, resulting in the most recent threads.  The IESG was 
>asked to proceed with the registration on the basis I described 
>above, but I'm inclined not to do so until this WG has published (or 
>at least the IESG has approved) the suffixes BCP; it doesn't make 
>sense to me to potentially derail a piece of chartered work 
>especially when it seems like we're converging on a solution.

Someone could file the registration request and include a note to RFC 
9399.  The chartered work cannot have retroactive effect.

Regards,
S. Moonesamy