[apps-discuss] RFC 6839 structured suffix support in actual software

"Rushforth, Peter (NRCan/RNCan)" <peter.rushforth@canada.ca> Wed, 20 January 2016 20:20 UTC

Return-Path: <prvs=820790f80=peter.rushforth@canada.ca>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCEBD1ACDCE for <apps-discuss@ietfa.amsl.com>; Wed, 20 Jan 2016 12:20:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.103
X-Spam-Level:
X-Spam-Status: No, score=-0.103 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
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 xp5AOd_q1dNP for <apps-discuss@ietfa.amsl.com>; Wed, 20 Jan 2016 12:20:40 -0800 (PST)
Received: from mx1.canada.ca (mx1.canada.ca [205.193.214.140]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42D8C1ACDCB for <apps-discuss@ietf.org>; Wed, 20 Jan 2016 12:20:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=canada.ca; i=@canada.ca; q=dns/txt; s=mx1; t=1453321240; x=1484857240; h=from:to:subject:date:content-transfer-encoding: mime-version; bh=/mk62Gw/gCSbjpHi6LttDLsT+D82RYeKT3fDhIuWIiM=; b=sMgCr4QX/d57skUE4CQw4sqjU/1AGg0EZ3z/j43uHBHVp2P90kWRuGz4 pyp4HWRWIOFgaSizgZyBY1tQsJRczbVI7ZVTADfs0qCytVp+E7+2Zewkv 083XtNI1uXJceORA1SEJDDNrD1KpYWSxRTFRl1WLAc37/vI8zqUdejx3s 6TSMte4Ha1Me2txJ/MU8KUDmYZTfAwhzVVsrd9k2WSF/C3raawe+HPNMu n9mEKfQAwAT2VsqWMYNwo75Hoz0+Cw0QDhVkiDIAYJNoLWSnRlBNvxYAG jAByRF+PO+R8qP2l059AeRSUyA5Ff0MOV4zTacJsZvSVWmB9Rv3qv5VmH g==;
X-Time-IN: 20 Jan 2016 20:20:36 -0000
From: "Rushforth, Peter (NRCan/RNCan)" <peter.rushforth@canada.ca>
To: IETF Apps Discuss <apps-discuss@ietf.org>
Thread-Topic: RFC 6839 structured suffix support in actual software
Thread-Index: AdFTv1nOa/aRF41XRp6GoKCk9ui/KA==
Date: Wed, 20 Jan 2016 20:20:28 +0000
Accept-Language: en-CA, en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Message-Id: <20160120202040.42D8C1ACDCB@ietfa.amsl.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/FTQAxgTPjU9yJvBQeHs-zCXRtp8>
X-Mailman-Approved-At: Thu, 21 Jan 2016 23:41:37 -0800
Subject: [apps-discuss] RFC 6839 structured suffix support in actual software
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2016 20:22:38 -0000

Hi,

Can anyone please identify some available software which implements the behaviour described in
section 2 of RFC 6839,  specifically, generic processing of a media type based on its 
structured suffix?

Any structured suffix will do.

Thank you.

Peter Rushforth