Re: [pkix] TrustAnchorInfo Media (MIME) Type
"Jim Schaad" <ietf@augustcellars.com> Tue, 24 November 2015 06:12 UTC
Return-Path: <ietf@augustcellars.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35AE81B2E36 for <pkix@ietfa.amsl.com>; Mon, 23 Nov 2015 22:12:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 vicOUo8706DF for <pkix@ietfa.amsl.com>; Mon, 23 Nov 2015 22:12:32 -0800 (PST)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B35491B2E34 for <pkix@ietf.org>; Mon, 23 Nov 2015 22:12:32 -0800 (PST)
Received: from hebrews (c-24-21-96-37.hsd1.or.comcast.net [24.21.96.37]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 2B95738F01; Mon, 23 Nov 2015 22:12:32 -0800 (PST)
From: Jim Schaad <ietf@augustcellars.com>
To: 'Peter Bowen' <pzbowen@gmail.com>, pkix@ietf.org
References: <CAK6vND9y72cX1n8TfAu=NGJoh6H0Vuy6BOQNUjsiL_vArVY4QQ@mail.gmail.com>
In-Reply-To: <CAK6vND9y72cX1n8TfAu=NGJoh6H0Vuy6BOQNUjsiL_vArVY4QQ@mail.gmail.com>
Date: Mon, 23 Nov 2015 22:09:42 -0800
Message-ID: <042101d1267e$b626dcb0$22749610$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJmOuzZ1Fu2EjAn/jBiohNZPmSbOp2Ahu0w
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/uwExWbAL12Cp2Qz6ft_VTOw5aTs>
Subject: Re: [pkix] TrustAnchorInfo Media (MIME) Type
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2015 06:12:34 -0000
I don't know about a file extension, but the media type would be application/cms as defined in RFC 7193. I would guess, but do not know, that it was thought that one would only send a list of one item rather than the TrustAnchorInfo structure on its own. The other thing to consider is if one is going to want to used one of the CMS security wrappers on the type as well. Jim > -----Original Message----- > From: pkix [mailto:pkix-bounces@ietf.org] On Behalf Of Peter Bowen > Sent: Monday, November 23, 2015 9:20 PM > To: <pkix@ietf.org> <pkix@ietf.org> > Subject: [pkix] TrustAnchorInfo Media (MIME) Type > > RFC 5914 defines the TrustAnchorInfo and TrustAnchorList data types and > assigns a CMS content type for TrustAnchorList. It does not request any > assignment of Media (MIME) Types for either the TAI or TAL structures. > > Has there been any discussion or informal consensus of a Media Type or file > extension for either data structure? > > Thanks, > Peter > > _______________________________________________ > pkix mailing list > pkix@ietf.org > https://www.ietf.org/mailman/listinfo/pkix
- Re: [pkix] TrustAnchorInfo Media (MIME) Type Jim Schaad
- [pkix] TrustAnchorInfo Media (MIME) Type Peter Bowen
- Re: [pkix] TrustAnchorInfo Media (MIME) Type Carl Wallace