Re: [Hipsec] Stephen Farrell's Discuss on draft-ietf-hip-rfc5203-bis-10: (with DISCUSS and COMMENT)

Julien Laganier <julien.ietf@gmail.com> Thu, 21 July 2016 14:35 UTC

Return-Path: <julien.ietf@gmail.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 524CB12D5C0; Thu, 21 Jul 2016 07:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 G4qjwsrbchnm; Thu, 21 Jul 2016 07:35:39 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F71412B058; Thu, 21 Jul 2016 07:35:38 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id l72so120372786oig.2; Thu, 21 Jul 2016 07:35:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FH/nwrNpF7xmf5zMbgzPu0z7PkkQtYd9SVtRWYvd98U=; b=q8mzD8VcLWtXJfGqvBgc2MOP6iiYHWCyaG/YNri/c68TZ85z8wdtU8dbW9NWg7BD3U o8e6yxoZHxfB1eyPlOrUji8wmF+nZ4JmA0O7c/rq2yMDVPDq/onEo9YTHap2JMgzflc8 EP5sH59EpzHvdOOlFe1q5tFjPWKgn1Xce4Jk1YLilgCR04+d5Bg+HvW5bNddO6l1U3j3 Qsy5cdpa+S/Ft7COi8H3RwMQj0g89ADIESRsPp2OEogtS2kVH6XYqibrzi7Gf2lQ369v AU8nBe8pqsX0KhcdQrRCvluc237lV1cOV0Tx1p5U9mSrhXqkzH8WMjeRWMUFw+gC4bwP 3IAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FH/nwrNpF7xmf5zMbgzPu0z7PkkQtYd9SVtRWYvd98U=; b=K/hmsYmfsYrK6mJGGjWhXZopQjk9jRSOSXeAzcQ/jwN2k5uYz5PgEftWeRdw0zsfma oFbXe+zae/Z8y2sBcuKhGwItJpmFQmx2UVm/jLF7A7BddylwEDuP5vPKOUUJND32zacy 6GDDx+YM2h5xcuNHvT9LOZ7DtSE0jD4AMdzP2km6txNvv/XTQ/qPbbMqTqdT+3owEDaU i7DYU+HfbkEzTb6WsJiyNdKD/XBoQvQu8DOy6LVBz8N587L06ETmVeTy/5TZImYY5ZtW X0TysiGQA/vCn2Y0u9R3IH9XeJzIsxUffqWGHC29yEOU/Zysqv5VbpPHTli67dSR82EY r/zw==
X-Gm-Message-State: ALyK8tJ0ykgaZ/XOyMMgC/vM2gxYMw0DiwnmfSuUI3g+OWBJM5Dy20E/H8SAYCtc5VPBcLm72FY8GonYHxvB9g==
X-Received: by 10.202.84.72 with SMTP id i69mr26092973oib.93.1469111737850; Thu, 21 Jul 2016 07:35:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.47.164 with HTTP; Thu, 21 Jul 2016 07:35:37 -0700 (PDT)
In-Reply-To: <102eb607-f1c5-9dc8-e7bb-fa5fd1daf838@cs.tcd.ie>
References: <20160705140143.22339.24069.idtracker@ietfa.amsl.com> <CAE_dhjtc7VHZaMEu_rHZwbGKPvh1cxpsbV-BvFBYF_vp4zvehQ@mail.gmail.com> <102eb607-f1c5-9dc8-e7bb-fa5fd1daf838@cs.tcd.ie>
From: Julien Laganier <julien.ietf@gmail.com>
Date: Thu, 21 Jul 2016 07:35:37 -0700
Message-ID: <CAE_dhjsBGhnRT1ypTkLnGLrP8y3vFCMbj7Zb6iDTBQgbdOJY6g@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/YFsgHUVOV3Tm8nY_csUoWfMBJ68>
Cc: draft-ietf-hip-rfc5203-bis@ietf.org, HIP <hipsec@ietf.org>, hip-chairs@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [Hipsec] Stephen Farrell's Discuss on draft-ietf-hip-rfc5203-bis-10: (with DISCUSS and COMMENT)
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2016 14:35:45 -0000

Thanks, Stephen.

The HIP WG was CC'd on these emails so participants have seen the
proposal, I will seek their feedback in a separate note.

Best,

--julien

On Thu, Jul 21, 2016 at 4:22 AM, Stephen Farrell
<stephen.farrell@cs.tcd.ie>; wrote:
>
> Hiya,
>
> That'd be fine for clearing my discuss.
>
> I'd encourage you to also get feedback from the WG though as I
> don't think I've ever seen a list of cert handling errors that
> was correct first time around:-)
>
> Cheers,
> S.
>
>
>
> On 20/07/16 16:11, Julien Laganier wrote:
>> Hi Stephen,
>>
>> Thanks for reviewing the document.
>>
>> I think there would be value in making the cause of certificate error
>> explicit. Would the following change be acceptable?
>>
>> OLD:
>>
>>    If the certificate in the parameter is not accepted, the registrar
>>    MUST reject the corresponding registrations with Failure Type [IANA
>>    TBD] (Invalid certificate).
>>
>> NEW:
>>
>>    If the certificate in the parameter is not accepted, the registrar
>>    MUST reject the corresponding registrations with the appropriate
>>    Failure Type:
>>    [IANA TBD] (Bad certificate): The certificate is corrupt, contains
>> invalid signatures, etc.
>>    [IANA TBD] (Unsupported certificate): The certificate is of an
>> unsupported type.
>>    [IANA TBD] (Certificate expired): The certificate is no longer valid.
>>    [IANA TBD] (Certificate other): The certificate could not be
>> validated for some unspecified reason.
>>    [IANA TBD] (Unknown CA): The issuing CA certificate could not be
>> located or is not trusted.
>>
>> Please let us know.
>>
>> Best,
>>
>> --julien
>>
>>
>>
>>
>> On Tue, Jul 5, 2016 at 7:01 AM, Stephen Farrell
>> <stephen.farrell@cs.tcd.ie>; wrote:
>>> Stephen Farrell has entered the following ballot position for
>>> draft-ietf-hip-rfc5203-bis-10: Discuss
>>>
>>> When responding, please keep the subject line intact and reply to all
>>> email addresses included in the To and CC lines. (Feel free to cut this
>>> introductory paragraph, however.)
>>>
>>>
>>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>>> for more information about IESG DISCUSS and COMMENT positions.
>>>
>>>
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5203-bis/
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>>
>>>
>>> 3.3 - This fails to distinguish between an invalid
>>> certificate (e.g. bad signature, unknown signer) and one
>>> that is valid, but is not acceptable for this purpose.  I
>>> don't get why that is ok for HIP, can you explain?  If it
>>> is ok, I think you need to say so. If it is not ok (as I'd
>>> suspect) then you appear to need to change text or one more
>>> new error code.
>>>
>>>
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>>
>>>
>>> Section 7 - I'm fine that this doesn't repeat stuff
>>> from 5203, but a sentence saying to go look there too
>>> would maybe be good. (I'm not sure if that would fix
>>> Alexey's discuss or not. If not, then ignore me and
>>> just talk to him about his discuss.)
>>>
>>>
>