Re: [weirds] Issue 4: http media types in RDAP replies
Tony Hansen <tony@att.com> Wed, 20 March 2013 16:59 UTC
Return-Path: <tony@att.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7814421F88F7 for <weirds@ietfa.amsl.com>; Wed, 20 Mar 2013 09:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KFAOlliDTza4 for <weirds@ietfa.amsl.com>; Wed, 20 Mar 2013 09:59:49 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id A82AD21F88CF for <weirds@ietf.org>; Wed, 20 Mar 2013 09:59:48 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 40be9415.0.198003.00-423.555249.nbfkord-smmo05.seg.att.com (envelope-from <tony@att.com>); Wed, 20 Mar 2013 16:59:48 +0000 (UTC)
X-MXL-Hash: 5149eb044107ab4d-734ecec74cf980d1174ca88d390cbb7cd484567a
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r2KGxmKn002411 for <weirds@ietf.org>; Wed, 20 Mar 2013 12:59:48 -0400
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r2KGxfpV002362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <weirds@ietf.org>; Wed, 20 Mar 2013 12:59:42 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi132.aldc.att.com (RSA Interceptor) for <weirds@ietf.org>; Wed, 20 Mar 2013 16:59:28 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r2KGxSM9015419 for <weirds@ietf.org>; Wed, 20 Mar 2013 12:59:28 -0400
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r2KGxN0u015266 for <weirds@ietf.org>; Wed, 20 Mar 2013 12:59:24 -0400
Received: from [135.70.58.174] (vpn-135-70-58-174.vpn.west.att.com[135.70.58.174]) by maillennium.att.com (mailgw1) with ESMTP id <20130320165750gw1000m55ue> (Authid: tony); Wed, 20 Mar 2013 16:57:51 +0000
X-Originating-IP: [135.70.58.174]
Message-ID: <5149EAE9.4090903@att.com>
Date: Wed, 20 Mar 2013 12:59:21 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "weirds@ietf.org" <weirds@ietf.org>
References: <62D9228640AC7F49B2DD9ED0C9CE60E58BBF48EE@CHAXCH01.corp.arin.net>
In-Reply-To: <62D9228640AC7F49B2DD9ED0C9CE60E58BBF48EE@CHAXCH01.corp.arin.net>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative; boundary="------------070400000105000704010804"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=2.0 cv=Pr4kmXw3 c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=XQF0PgYYJo4A:10 a=z55uD49gxukA:10 a=p5DJb0AXvPkA:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=guoZXqJl]
X-AnalysisOut: [uEUA:10 a=IIXG7RsUC-_FV_2grb8A:9 a=wPNLvfGTeEIA:10 a=Hz7Ir]
X-AnalysisOut: [DYlS0cA:10 a=IepdWeDwkfhy7EAh:21 a=avzuPbBiUyGjzGK-:21 a=w]
X-AnalysisOut: [iYxLJy5AAAA:8 a=r2CbOPE9Jrqaq3tObs8A:9 a=_W_S_7VecoQA:10 a]
X-AnalysisOut: [=LyUn2sZr3PNXH4Er:21]
Subject: Re: [weirds] Issue 4: http media types in RDAP replies
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 16:59:49 -0000
The draft mentioned below was recently published as RFC 6838:
Media Type Specifications and Registration Procedures. N. Freed, J.
Klensin, T. Hansen. January 2013.
The actual registration of +json can be found in RFC 6839:
Additional Media Type Structured Syntax Suffixes. T. Hansen, A.
Melnikov. January 2013.
Tony Hansen
tony@att.com
On 3/20/2013 12:22 PM, Andy Newton wrote:
> We already do that in json-response, but I'm happy to move it to
> using-http.
>
> Also, we originally had the +json suffix and took it out. But since you've
> found some guidance on the use of the suffix, it is probably wise to add
> it back in.
>
> -andy
>
> On 3/20/13 11:54 AM, "Jean-Philippe Dionne"
> <jean-philippe.dionne@viagenie.ca> wrote:
>
>> What about the +json suffix?
>> From draft-ietf-appsawg-media-type-regs-14#section-3, we can read:
>> "Media types that make use of a named structured syntax SHOULD use the
>> appropriate registered "+suffix" for that structured syntax when they
>> are registered. "
- [weirds] Issue 4: http media types in RDAP replies John Levine
- Re: [weirds] Issue 4: http media types in RDAP re… Jean-Philippe Dionne
- Re: [weirds] Issue 4: http media types in RDAP re… Andy Newton
- Re: [weirds] Issue 4: http media types in RDAP re… Tony Hansen