Re: Request for well-known URI: est

"Max Pritikin (pritikin)" <pritikin@cisco.com> Wed, 17 April 2013 01:20 UTC

Return-Path: <pritikin@cisco.com>
X-Original-To: wellknown-uri-review@ietfa.amsl.com
Delivered-To: wellknown-uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D59A21F961E for <wellknown-uri-review@ietfa.amsl.com>; Tue, 16 Apr 2013 18:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 g6rxQDkoj-3m for <wellknown-uri-review@ietfa.amsl.com>; Tue, 16 Apr 2013 18:20:03 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 8A5C821F9619 for <wellknown-uri-review@ietf.org>; Tue, 16 Apr 2013 18:20:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2036; q=dns/txt; s=iport; t=1366161603; x=1367371203; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=vUXzBtIUMpa3Zkqh9sdJ0/89YM6Jj/s56MULK5gr0sU=; b=OuoK/WaxEpOy6giX2ny2myoi3ORH3bmbu7PXevBc2QEOnXbQ1/zYAkrA 9A5SvNElAaNcXIo2AyMeheJ2d9pLVUkSyabs+ueopYUUMQf2+gYt9wiBk S8OKPP9rOv0qwckGS+uHCK5VQ7R83bT4zK/LDvhOXKlUdhExDFBpXc3k8 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAL/3bVGtJXHB/2dsb2JhbABQgwY2wQuBDhZ0gh8BAQEDAQEBATcxAwsFCwIBCA4KHhAnCyUCBA4FiA4GDK8HjhGOaDMHgmRhA5cGkRSCfg0
X-IronPort-AV: E=Sophos;i="4.87,488,1363132800"; d="scan'208";a="199579180"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-6.cisco.com with ESMTP; 17 Apr 2013 01:20:03 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r3H1K2sZ007801 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Apr 2013 01:20:02 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.88]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Tue, 16 Apr 2013 20:20:02 -0500
From: "Max Pritikin (pritikin)" <pritikin@cisco.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Request for well-known URI: est
Thread-Topic: Request for well-known URI: est
Thread-Index: AQHOOrZG2HJ3iG8ARUyXQKwBb3sBk5jZ7ToA//+wtyE=
Date: Wed, 17 Apr 2013 01:20:01 +0000
Message-ID: <5BF29361-015A-48D2-9D0A-6FBCD952BFFA@cisco.com>
References: <516D6CC8.6070705@ieca.com>, <F3F69278-D4BA-4A12-9572-A72046186D5F@mnot.net>
In-Reply-To: <F3F69278-D4BA-4A12-9572-A72046186D5F@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "apps-ads@tools.ietf.org" <apps-ads@tools.ietf.org>, Sean Turner <turners@ieca.com>, "wellknown-uri-review@ietf.org" <wellknown-uri-review@ietf.org>, "draft-ietf-pkix-est@tools.ietf.org" <draft-ietf-pkix-est@tools.ietf.org>
X-BeenThere: wellknown-uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Well-Known URI review list <wellknown-uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wellknown-uri-review>
List-Post: <mailto:wellknown-uri-review@ietf.org>
List-Help: <mailto:wellknown-uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Apr 2013 01:20:06 -0000

Making each path element lowercase will not be a problem. 

- max

On Apr 16, 2013, at 6:04 PM, "Mark Nottingham" <mnot@mnot.net> wrote:

> Hi Sean,
> 
> Each well-known controls the name space "below" it, so you can do what you like there (within the constraints of URIs).
> 
> However (and with my expert hat off), many/most Web servers map from filesystems to URIs in a case-sensitive fashion, and pretty much all APIs don't make any accommodation for case normalisation, so making these path components case-insensitive would be seen by many as a counter-intuitive, and even fairly unfriendly thing to do. Personally, I wouldn't recommend it.
> 
> (hat back on) I'll take a look at the draft and get back to you.
> 
> Cheers,
> 
> 
> 
> On 17/04/2013, at 1:22 AM, Sean Turner <turners@ieca.com> wrote:
> 
>> Hi wellknown-uri experts!
>> 
>> I'd like to request a review of registration request for .well-known/est, which is found in https://datatracker.ietf.org/doc/draft-ietf-pkix-est/.
>> 
>> Summary: EST (Enrollment over Secure Transport) is a way for clients to retrieve PKI-related "stuff" from an EST server.  Think posting enrollment requests (i.e., PKCS#10), getting enrollment responses (i.e., PKCS#7 certs-only), re-enrollment, CA certificates, etc.
>> 
>> 
>> A related question, which I'm hoping you might be able to help with: when specifying the URI bit below our soon-to-be wellknown URI do we need to specify whether they are case sensitive or not?  For example, we have:
>> 
>> /.well-known/est/CACerts
>> 
>> but would that only be the same as the following if we state that it's case insensitive:
>> 
>> /.well-known/est/cacerts
>> 
>> spt
>> 
>> _______________________________________________
>> wellknown-uri-review mailing list
>> wellknown-uri-review@ietf.org
>> https://www.ietf.org/mailman/listinfo/wellknown-uri-review
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
>