Re: [netconf] x509c2n:cert-to-name problem
Kent Watsen <kent+ietf@watsen.net> Mon, 04 November 2019 10:01 UTC
Return-Path: <0100016e35dcd47e-5729ff45-cb28-4a7a-a5a4-2e43a0ea41a5-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE08120100 for <netconf@ietfa.amsl.com>; Mon, 4 Nov 2019 02:01:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 Nfuan-gZvThm for <netconf@ietfa.amsl.com>; Mon, 4 Nov 2019 02:01:36 -0800 (PST)
Received: from a8-64.smtp-out.amazonses.com (a8-64.smtp-out.amazonses.com [54.240.8.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98E5E1200FF for <netconf@ietf.org>; Mon, 4 Nov 2019 02:01:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1572861695; h=Content-Type:Content-Transfer-Encoding:From:Mime-Version:Subject:Date:Message-Id:References:Cc:In-Reply-To:To:Feedback-ID; bh=jYoBihAIUlts1Z2WcCGrc3TdA56IY9cya8ZeHOvJn40=; b=VAsyQ7QOn7eagjM9S1N4LHcTQZYlfjXDgdlZi819TT9Jp3AKYci2Q2oBJF557PXO R6BGNgwKIhgnpwK4yKJxXvu1Obhlhm0crSrhEJaa4YcbZrqPZCXc65xytWSbuXW1b9G /pu4JzcwTMrRFaPD1SjXggehW1jDSaTzzASvbkUE=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From: Kent Watsen <kent+ietf@watsen.net>
Mime-Version: 1.0 (1.0)
Date: Mon, 04 Nov 2019 10:01:35 +0000
Message-ID: <0100016e35dcd47e-5729ff45-cb28-4a7a-a5a4-2e43a0ea41a5-000000@email.amazonses.com>
References: <20191104.091119.1760037446043812190.mbj@tail-f.com>
Cc: netconf@ietf.org
In-Reply-To: <20191104.091119.1760037446043812190.mbj@tail-f.com>
To: Martin Bjorklund <mbj@tail-f.com>
X-Mailer: iPhone Mail (17A878)
X-SES-Outgoing: 2019.11.04-54.240.8.64
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/4qfhvf_wtndbiSggVNU4bmqLrKY>
Subject: Re: [netconf] x509c2n:cert-to-name problem
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 10:01:38 -0000
> Did you see my email "client identification in ietf-netconf-server"? No, could you send again? I see it in the archive, so send to just me? K. > I don't think this refinement is the correct solution. > > > /martin
- [netconf] x509c2n:cert-to-name problem (was [netm… Kent Watsen
- Re: [netconf] x509c2n:cert-to-name problem Martin Bjorklund
- Re: [netconf] x509c2n:cert-to-name problem Kent Watsen
- Re: [netconf] x509c2n:cert-to-name problem Kent Watsen