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

Robert Moskowitz <rgm@labs.htt-consult.com> Fri, 13 March 2020 18:43 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 B576C3A08F4; Fri, 13 Mar 2020 11:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 2NO8ZyViO6Ec; Fri, 13 Mar 2020 11:43:42 -0700 (PDT)
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 8F28E3A08F0; Fri, 13 Mar 2020 11:43:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id BF7086212C; Fri, 13 Mar 2020 14:43:39 -0400 (EDT)
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 7SHfuzjye9Wv; Fri, 13 Mar 2020 14:43:34 -0400 (EDT)
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 DFA8862113; Fri, 13 Mar 2020 14:43:33 -0400 (EDT)
To: Suresh Krishnan <Suresh@kaloom.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-hip-dex@ietf.org" <draft-ietf-hip-dex@ietf.org>, "j.ahrenholz@tempered.io" <j.ahrenholz@tempered.io>, "hip-chairs@ietf.org" <hip-chairs@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "hipsec@ietf.org" <hipsec@ietf.org>
References: <158329724383.7687.5696211532188484676@ietfa.amsl.com> <ae384776-b0ba-ce43-5fa9-c279f0b91bd4@labs.htt-consult.com> <9336814E-6390-47B1-AD35-38F09A6147AE@kaloom.com>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
Message-ID: <222afffb-896c-3124-997d-99119166ed82@labs.htt-consult.com>
Date: Fri, 13 Mar 2020 14:43:16 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <9336814E-6390-47B1-AD35-38F09A6147AE@kaloom.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/FidmwIajYRsmcqfligQfBooNDlM>
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: Fri, 13 Mar 2020 18:43:44 -0000

Suresh,

Your text appeared in ver 14.  Please check it out.

thank you.

Bob

On 3/5/20 2:00 PM, Suresh Krishnan wrote:
> Hi Bob,
>    This text works for me. I will clear as soon as the new revision hits.
>
> Regards
> Suresh
>
>> On Mar 5, 2020, at 11:04 AM, Robert Moskowitz <rgm@labs.htt-consult.com> wrote:
>>
>> Here is the text I put together for revising sec 5.4 (see below).
>>
>> 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.
>>>
>>>
>>>
>>>
>>>
>> 5.4.  ICMP Messages
>>
>>     When a HIP implementation detects a problem with an incoming packet,
>>     and it either cannot determine the identity of the sender of the
>>     packet or does not have any existing HIP association with the sender
>>     of the packet, it MAY respond with an ICMP packet.  Any such reply
>>     MUST be rate-limited as described in [RFC4443].  In most cases, the
>>     ICMP packet has the Parameter Problem type (12 for ICMPv4, 4 for
>>     ICMPv6) and Code of 0.  The Pointer field pointing to the field that
>>     caused the ICMP message to be generated, for example to the first 8
>>     bytes of a UDP payload for "SPI is Unknown".  The problem cases
>>     specified in Section 5.4. of [RFC7401] also apply to HIP DEX.
>>