Re: [Hipsec] Suresh Krishnan's Discuss on draft-ietf-hip-dex-13: (with DISCUSS)

Robert Moskowitz <rgm@labs.htt-consult.com> Wed, 04 March 2020 13:19 UTC

Return-Path: <rgm@labs.htt-consult.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 B4AED3A0EB2; Wed, 4 Mar 2020 05:19:31 -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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 fKmaCrtsDS6F; Wed, 4 Mar 2020 05:19:29 -0800 (PST)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13B563A0EB7; Wed, 4 Mar 2020 05:19:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id A3CA86220F; Wed, 4 Mar 2020 08:19:26 -0500 (EST)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id iqm8-HmFOhSH; Wed, 4 Mar 2020 08:19:20 -0500 (EST)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id D09F8621FB; Wed, 4 Mar 2020 08:19:18 -0500 (EST)
To: Suresh Krishnan <suresh@kaloom.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-hip-dex@ietf.org, hip-chairs@ietf.org, hipsec@ietf.org, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
References: <158329724383.7687.5696211532188484676@ietfa.amsl.com>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
Message-ID: <a0ef66bb-ea77-c5b6-3a63-74d85dba2240@labs.htt-consult.com>
Date: Wed, 4 Mar 2020 08:19:09 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <158329724383.7687.5696211532188484676@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------EA7300C6F4E59892A02924E0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/vsiZIYFdda_KFMcZkYAb4-HPQqQ>
Subject: Re: [Hipsec] Suresh Krishnan's Discuss on draft-ietf-hip-dex-13: (with DISCUSS)
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 04 Mar 2020 13:19:32 -0000

This looks more like an RFC 7401 problem than a HIP-DEX problem; as DEX 
inherits this from 7401.  In fact it is an RFC 5201 problem!

It looks like Suresh is correct that a code is needed and in sec 3.4 of 
RFC 2463 a code is need..

I looked at:

https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#icmpv6-parameters-codes-5

And nothing there that looks right.

So what is done in HIP BEX implementations?  Both v1 and v2?

And should this be fixed in DEX or an errata for 5201 and 7401?  And if 
we do an errata, do we still specify the code in DEX?

Nothing is ever "straightforward to resolve" ...

On 3/3/20 11:47 PM, Suresh Krishnan via Datatracker wrote:
> Suresh Krishnan has entered the following ballot position for
> draft-ietf-hip-dex-13: 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-dex/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> This should be pretty straightforward to resolve.
>
> * Section 5.4.:
>
> The ICMPv6 Parameter Problem messages to be sent need a Code field to be set in
> addition to the Pointer. What Code should be used in this message? Please
> specify this.
>
>
>
>
>

-- 
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:rgm@labs.htt-consult.com

There's no limit to what can be accomplished if it doesn't matter who 
gets the credit