IETF Logo Mail Archive

Re: [certid] Moving RFC 2818 to Historic (was Comments on draft-saintandre-tls-server-id-check-04)

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 08 June 2010 15:45 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: certid@core3.amsl.com
Delivered-To: certid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F82A3A6805 for <certid@core3.amsl.com>; Tue, 8 Jun 2010 08:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level:
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KV+hV4HN94WT for <certid@core3.amsl.com>; Tue, 8 Jun 2010 08:45:49 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 5B7B43A679F for <certid@ietf.org>; Tue, 8 Jun 2010 08:45:49 -0700 (PDT)
Received: from [172.16.2.123] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TA5lrABeGWGJ@rufus.isode.com>; Tue, 8 Jun 2010 16:45:49 +0100
Message-ID: <4C0E658E.6010006@isode.com>
Date: Tue, 08 Jun 2010 16:45:18 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Sean Turner <turners@ieca.com>
References: <4BEB3870.10904@KingsMountain.com> <4BED0E6E.1090303@edelweb.fr> <4C003D15.4060408@stpeter.im> <4C00FEC0.3080808@edelweb.fr> <4C082431.3050900@stpeter.im> <4C0825AD.1020309@ieca.com> <4C0E6163.2080509@isode.com> <4C0E6565.7040807@ieca.com>
In-Reply-To: <4C0E6565.7040807@ieca.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: certid@ietf.org
Subject: Re: [certid] Moving RFC 2818 to Historic (was Comments on draft-saintandre-tls-server-id-check-04)
X-BeenThere: certid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Representation and verification of identity in certificates <certid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/certid>
List-Post: <mailto:certid@ietf.org>
List-Help: <mailto:certid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 15:45:50 -0000

Sean Turner wrote:

> Alexey Melnikov wrote:
>
>> Hi Sean,
>>
>> Sean Turner wrote:
>>
>>>>> As I said, here you have room for clarification. You essentially
>>>>> rewrite 2818 
>>>>
>>>> This proposed BCP is not limited to HTTP so it does not (only) rewrite
>>>> RFC 2818, but yes it is intended (in part) to provide more up-to-date
>>>> guidelines.
>>>
>>> Should we add a section that moves 2818 to historic? (sorry if this 
>>> has been asked before)
>>
>> RFC 2818 contains more information than just the TLS server identity 
>> verification procedure for https. Besides RFC 2818 is widely used and 
>> I think moving it to historic would be a disservice to the community. 
>> Maybe you meant to suggest "obsoleting" it?
>
> Maybe we should be updating the pertinent sections?  That would mean 
> adding "Updates: 2818 (once approved) to the header of this document? 
>  Also clearly state it doesn't just apply to HTTP.

Yes, we could do that.

v2.8.7 | Report a Bug | By Email