IETF Logo Mail Archive

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

"Rushforth, Peter (NRCan/RNCan)" <peter.rushforth@canada.ca> Wed, 20 January 2016 20:44 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 A5C431ACE58 for <apps-discuss@ietfa.amsl.com>; Wed, 20 Jan 2016 12:44:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 U1iNMp2psKgT for <apps-discuss@ietfa.amsl.com>; Wed, 20 Jan 2016 12:44:23 -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 946A41ACE57 for <apps-discuss@ietf.org>; Wed, 20 Jan 2016 12:44:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=canada.ca; i=@canada.ca; q=dns/txt; s=mx1; t=1453322663; x=1484858663; h=from:to:subject:date:content-transfer-encoding: mime-version; bh=PD8BQEJmvJ/SwdwVqQlYxxVtRO8xvXZOTuYo/PHNpXk=; b=RFjO+RhUpaUrlF/JUq9ne4tk3kxszPoHHbfJCNNRv4eZJeoyVxbbvbuB unEvcDCMbV3tIUqXnc8yLbj6mojaR6E/dD1eq7mJ21N+C7UiESLUCSHmd u4sq6RkBIZ78hVWNgsSn9uonzi0fCsjDvI/li4WuSD6/K2nsNLDz5htci taytg3KqidUF4N2CsCyrbMpmoNCaWwx4MUWdPEnO5RLsom5wD93nfdQLq chRrPW7G7ZVANGkHveghnigB8HELoH26iS5t0Inws4r4XTvHodXxCM+gh q2YMB1uajSijy/zwvNKN8CZ5yKKujsz3a8AGlzhZ31BUz5m1dmaNGXO8w g==;
X-Time-IN: 20 Jan 2016 20:44:22 -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: AdFTwchQ+WE1ZoUgRHCFRtWZVlaoug==
Date: Wed, 20 Jan 2016 20:44:21 +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: <20160120204423.946A41ACE57@ietfa.amsl.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/-nYU1m__tp_MMp3hMwMXsE1zQpY>
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:44:24 -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

v2.23.0 | Report a Bug | By Email