IETF Logo Mail Archive

Re: [dispatch] please dispatch draft-bhjl-x509-srv-02.xml

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Sat, 20 August 2016 15:26 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 200B912D87F for <dispatch@ietfa.amsl.com>; Sat, 20 Aug 2016 08:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.768
X-Spam-Level:
X-Spam-Status: No, score=-115.768 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 5k7mUHxOl6bP for <dispatch@ietfa.amsl.com>; Sat, 20 Aug 2016 08:26:43 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C48E12D1AC for <dispatch@ietf.org>; Sat, 20 Aug 2016 08:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1540; q=dns/txt; s=iport; t=1471706803; x=1472916403; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=A0qKhBHm5eU3E9EYIS/rfoO/UCOYfnPPVerEgPmDmWM=; b=AliWUX3gJMTMqjidSGM1mIhAnD9Km5ngg/IMyFgt8FnCcZGHDIsCaE1W JG+2ZeKU0l8wCAEBuJtJG4TwAV1kCqswsW6nf02BO7PD8awhM4koS02Bi BP0aZzC9izx+tQnLNXYndph5R+QXdL4eHiSBqnkAq48CafBic6BvQGtHw 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AtAgBldbhX/4MNJK1eg0RWfAe3bIF9JIUvSgKBOzgUAgEBAQEBAQFeJ4ReAQEEAQEBODQLBQsCAQgYHhAnCyUCBA4FiCkIDrsSAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWIIwiCTYQSEQEcgyyCLwWOH4spAY8egW2EXIkHjD+DdwEeNoN6cIVFN38BAQE
X-IronPort-AV: E=Sophos;i="5.28,550,1464652800"; d="scan'208";a="313154157"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Aug 2016 15:26:42 +0000
Received: from XCH-RTP-004.cisco.com (xch-rtp-004.cisco.com [64.101.220.144]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u7KFQgKF027988 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 20 Aug 2016 15:26:42 GMT
Received: from xch-rtp-004.cisco.com (64.101.220.144) by XCH-RTP-004.cisco.com (64.101.220.144) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 20 Aug 2016 11:26:41 -0400
Received: from xch-rtp-004.cisco.com ([64.101.220.144]) by XCH-RTP-004.cisco.com ([64.101.220.144]) with mapi id 15.00.1210.000; Sat, 20 Aug 2016 11:26:41 -0400
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: John R Levine <johnl@taugh.com>
Thread-Topic: [dispatch] please dispatch draft-bhjl-x509-srv-02.xml
Thread-Index: AQHR+vdAk+j6og5nDk2ppXLcWQ3uYg==
Date: Sat, 20 Aug 2016 15:26:41 +0000
Message-ID: <922EDA7D-2269-4E9D-A72A-87327DE60410@cisco.com>
References: <alpine.OSX.2.11.1607221253020.13624@dhcp-b1bb.meeting.ietf.org>
In-Reply-To: <alpine.OSX.2.11.1607221253020.13624@dhcp-b1bb.meeting.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.249.165]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AF5C641D42B53F4D9C0C8225969A8C4E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Q7eIo9V854nxWafejgFfUp6fVN4>
Cc: Dispatch WG <dispatch@ietf.org>
Subject: Re: [dispatch] please dispatch draft-bhjl-x509-srv-02.xml
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2016 15:26:45 -0000

I find this interesting and would like to see something along these lines get published but I think there are a some area that probably need some dissolution....

Security model ... I'm a big confused by the use of HTTPS and DNSSEC. They both seem unneeded if the idea is a certificate is more or less self securing and public

The API. I'd like to see it clearly work for all types of URIs including email. It also seems that perhaps a parameter that directly indicated the returned type like x509, pgp, etc would be a better API design that using uri vs email to indicate if it was x509 or pgp. 

I don't get why the Name Matching parts happens. 

I think what you are really talking about here designing a HTTP REST based API for retrieval of certificates (and it happens to have an SRV entry). That seems to be an idea worth discussing. 

Cullen (in my individual contributor role)


> On Jul 22, 2016, at 4:54 AM, John R Levine <johnl@taugh.com> wrote:
> 
> The WG seemed OK with it.  After talking to people who plan to implement it I updated the draft with some editing fixes and a longer security section.
> 
> This also seems appropriate for AD sponsored, please.
> 
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail.
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

v2.23.0 | Report a Bug | By Email