Re: [Hipsec] Ben Campbell's No Objection on draft-ietf-hip-rfc4423-bis-19: (with COMMENT)

Ben Campbell <ben@nostrum.com> Tue, 08 January 2019 21:36 UTC

Return-Path: <ben@nostrum.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 E03F6131184; Tue, 8 Jan 2019 13:36:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 SAu0GesDojUf; Tue, 8 Jan 2019 13:36:50 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 B4BB7130F96; Tue, 8 Jan 2019 13:36:50 -0800 (PST)
Received: from [10.0.1.45] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x08LajTX042040 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 8 Jan 2019 15:36:46 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1546983407; bh=ZMx3cf1I/KDCoZL5Xe2kAHMaAE1QwUbM2Nbrf8VrAHQ=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=bnDXnHAEL9NGtxTU6IejD5OthpWHUqKpOZivCvCHLR/ULqRlHi8eQnBnPBMEoUM+o YZyj1sODyNKDxk/T7rhZsk/zg9WdEeI7eXT5IUn6odwvXkwFAoL7tVOONgZxuen+9r zyZ+E50FfEZXOIzTtMllu09Frd6ftCbENj6V4IVo=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.45]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <8D08F48A-F9A9-4E9A-A588-AB338650ACB8@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7400284A-3110-4159-B859-87A7BCD0A9F3"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 08 Jan 2019 15:36:44 -0600
In-Reply-To: <c64f520e-3450-f570-9a9d-0f291f7d4532@ericsson.com>
Cc: The IESG <iesg@ietf.org>, "hipsec@ietf.org" <hipsec@ietf.org>, "hip-chairs@ietf.org" <hip-chairs@ietf.org>, "draft-ietf-hip-rfc4423-bis@ietf.org" <draft-ietf-hip-rfc4423-bis@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
To: Miika Komu <miika.komu@ericsson.com>
References: <152592082640.10421.10127781203317885108.idtracker@ietfa.amsl.com> <c64f520e-3450-f570-9a9d-0f291f7d4532@ericsson.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/BurSDWqgcYBPBuYRlW10L3z1NRw>
Subject: Re: [Hipsec] Ben Campbell's No Objection on draft-ietf-hip-rfc4423-bis-19: (with COMMENT)
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: Tue, 08 Jan 2019 21:36:52 -0000


> On Jan 6, 2019, at 2:40 PM, Miika Komu <miika.komu@ericsson.com> wrote:
> 
>> 
>> Abstract: The abstract manages to completely avoid saying what this namespace
>> is _for_. (Yes, I realize that is old text :-) )
> 
> I changed the first sentence to:
> 
>    This memo describes the Host Identity (HI) namespace, that provides a
>    cryptographic namespace to applications, and the associated protocol
>    layer, the Host Identity Protocol, located between the
>    internetworking and transport layers, that supports end-host
>    mobility, multihoming and NAT traversal.
> 
> Is this ok for you?

Yes, thanks!

Ben.