IETF Logo Mail Archive

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

"Rushforth, Peter (NRCan/RNCan)" <peter.rushforth@canada.ca> Fri, 22 January 2016 16:40 UTC

Return-Path: <prvs=822818b3b=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 1BB3B1B29C8 for <apps-discuss@ietfa.amsl.com>; Fri, 22 Jan 2016 08:40:43 -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 zdvL_oLwEVKF for <apps-discuss@ietfa.amsl.com>; Fri, 22 Jan 2016 08:40: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 6419D1A6FDB for <apps-discuss@ietf.org>; Fri, 22 Jan 2016 08:40: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=1453480841; x=1485016841; h=from:to:subject:date:references:in-reply-to: content-transfer-encoding:mime-version; bh=THVz0ZfYmsPZ6zg3nKwpb+J+UhKjmhaf5v0T+9RWnvA=; b=Meo6J9/MczxyKo3JprU/uHKYBxQneBVfJDs9bDNP9tBkpm/P7CIOydBr rtffxeOg+ng06y3fMN7gmMPCjtzED4NWwvENArosjGhZppCYK279Yw2pC 6MMmi8BV6zcpbXdJoRMdnC3ob2XRE8adRZe7xeAoWYuOAE2E06PDG8As2 ZO0nR3XC2ShbIXFEMs59XoYrTnaH5zKgHti7EpJKlpiEta0lmvAucomOb CkfE6bF0dZS2VRHeLZrjklpuEDnXd8+m/r9D1QR5zLDx7sS8rOeAU5p/+ Hpvrm6eXvlrBQzspedLqn/pKtPrkQUyYqSRyfCLnjysd9egQqNeazE5XZ w==;
X-Time-IN: 22 Jan 2016 16:40:39 -0000
From: "Rushforth, Peter (NRCan/RNCan)" <peter.rushforth@canada.ca>
To: Julian Reschke <julian.reschke@gmx.de>, IETF Apps Discuss <apps-discuss@ietf.org>
Thread-Topic: [apps-discuss] RFC 6839 structured suffix support in actual software
Thread-Index: AdFTwchQ+WE1ZoUgRHCFRtWZVlaougBUUByAAAgbviA=
Date: Fri, 22 Jan 2016 16:40:36 +0000
References: <20160120204423.946A41ACE57@ietfa.amsl.com> <56A1DE89.9040501@gmx.de>
In-Reply-To: <56A1DE89.9040501@gmx.de>
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: <20160122164040.6419D1A6FDB@ietfa.amsl.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/vqu22XC29O1Pp3WfZb_VP0h7fQI>
Subject: Re: [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: Fri, 22 Jan 2016 16:40:43 -0000

Hi Julian,

Thanks for your response.  Indeed, I tested it in Chrome and it does appear to work like that.

Regards,
Peter Rushforth

> -----Original Message-----
> From: Julian Reschke [mailto:julian.reschke@gmx.de]
> Sent: January 22, 2016 02:47
> To: Rushforth, Peter (NRCan/RNCan); IETF Apps Discuss
> Subject: Re: [apps-discuss] RFC 6839 structured suffix support in actual
> software
> 
> On 2016-01-20 21:44, Rushforth, Peter (NRCan/RNCan) wrote:
> > 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
> 
> AFAIK, XMLHttpRequest triggers special behavior based on the "+xml"
> suffix; see <https://www.w3.org/TR/XMLHttpRequest/#response-entity-
> body-0>.
> 
> Best regards, Julian

v2.23.0 | Report a Bug | By Email