Re: [Hipsec] Missing HIP control flags registry?

Robert Moskowitz <rgm@htt-consult.com> Thu, 17 June 2010 14:29 UTC

Return-Path: <rgm@htt-consult.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5934F3A68EE for <hipsec@core3.amsl.com>; Thu, 17 Jun 2010 07:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.99
X-Spam-Level:
X-Spam-Status: No, score=-0.99 tagged_above=-999 required=5 tests=[AWL=1.609, 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 r6GRuPv0re2J for <hipsec@core3.amsl.com>; Thu, 17 Jun 2010 07:29:41 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id 760343A687F for <hipsec@ietf.org>; Thu, 17 Jun 2010 07:29:41 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 2B44968B49; Thu, 17 Jun 2010 14:22:07 +0000 (UTC)
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8rZOFpCKFqQX; Thu, 17 Jun 2010 10:21:58 -0400 (EDT)
Received: from nc2400.htt-consult.com (h155.home.htt [208.83.67.155]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 0092968B41; Thu, 17 Jun 2010 10:21:57 -0400 (EDT)
Message-ID: <4C1A314D.80401@htt-consult.com>
Date: Thu, 17 Jun 2010 10:29:33 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Thunderbird/3.0.4
MIME-Version: 1.0
To: Ari Keranen <ari.keranen@nomadiclab.com>
References: <4C1A2A9A.8010703@nomadiclab.com>
In-Reply-To: <4C1A2A9A.8010703@nomadiclab.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: HIP WG <hipsec@ietf.org>
Subject: Re: [Hipsec] Missing HIP control flags registry?
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 17 Jun 2010 14:29:42 -0000

On 06/17/2010 10:00 AM, Ari Keranen wrote:
> Hi all,
>
> It seems that there is no IANA registry for the HIP control flags [1] 
> or even policy defined how to reserve them. Is this correct? That 
> could be something to fix in the bis version.

Tobias and I were discussing Control flags yesterday that should bring 
some focus to this.

Good catch, Ari.

>
>
> Cheers,
> Ari
>
> [1] http://tools.ietf.org/html/rfc5201#section-5.1.2
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
>