[Hipsec] Charter proposal

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Mon, 15 February 2016 15:40 UTC

Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id A84F31B338A for <hipsec@ietfa.amsl.com>; Mon, 15 Feb 2016 07:40:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id C7UPWO2s6385 for <hipsec@ietfa.amsl.com>; Mon, 15 Feb 2016 07:40:20 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D18321B3373 for <hipsec@ietf.org>; Mon, 15 Feb 2016 07:40:19 -0800 (PST)
X-AuditID: c1b4fb25-f794e6d000003d15-b5-56c1f161e3fd
Received: from ESESSHC020.ericsson.se (Unknown_Domain []) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id D3.DA.15637.161F1C65; Mon, 15 Feb 2016 16:40:17 +0100 (CET)
Received: from [] ( by smtp.internal.ericsson.com ( with Microsoft SMTP Server id; Mon, 15 Feb 2016 16:40:14 +0100
To: HIP <hipsec@ietf.org>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <56C1F15E.8000500@ericsson.com>
Date: Mon, 15 Feb 2016 17:40:14 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprALMWRmVeSWpSXmKPExsUyM2K7n27ix4NhBq+2GllMXTSZ2YHRY8mS n0wBjFFcNimpOZllqUX6dglcGU+vzGcqmMNbcfz3d5YGxqdcXYycHBICJhJXH75nhbDFJC7c W8/WxcjFISRwmFHiTddvJghnLaPE5If7mUCqRAQkJXruLmUBsdkELCS23LoPZgsDxY8s6wey OTh4BbQlLnR7gIRZBFQlnrzdBrZAVCBG4mLnEbAxvAKCEidnPgErZxbQlFi/Sx8kzCwgL7H9 7RxmEFsIaMryZy0sExj5ZiHpmIXQMQtJxwJG5lWMosWpxUm56UbGeqlFmcnFxfl5enmpJZsY geF0cMtv1R2Ml984HmIU4GBU4uHdcO5AmBBrYllxZe4hRgkOZiURXovTB8OEeFMSK6tSi/Lj i0pzUosPMUpzsCiJ865xXh8mJJCeWJKanZpakFoEk2Xi4JRqYJywI1Yz0cr4UIzH39J9679H 8OafU9hZ5ccfqtEuXc1zK5njSuWNVZ7vN/Bqf7YpmtoaHes79UzL9djq0oOu0jdniCaWOO5v E96wYU20XniB85s7H9Xd89pO5h799eJZebyopOjBXpt9CYasfX35N0tajoXvl7D0N1Sdf9BE T37VJ+2tOo4rlViKMxINtZiLihMBK4TehCMCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/hipsec/izV5ZM8X9pmKfLNa016z0PBniv8>
Subject: [Hipsec] Charter proposal
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 15 Feb 2016 15:40:21 -0000


please, find below a proposal to revise our charter. Please, send your
comments to this list.



HIP WG Charter

The Host Identity Protocol (HIP) provides a method of separating the
end-point identifier and locator roles of IP addresses. It introduces
a new Host Identity (HI) name space, based on public keys, from which
end-point identifiers are taken. The public keys are typically, but
not necessarily, self generated. HIP uses existing IP addressing and
forwarding for locators and packet delivery.

The architecture and protocol details for these mechanisms were
originally specified in a set of Experimental RFCs, which include the

o HIP Architecture (RFC 4423)
o Host Identity Protocol (RFC 5201)

There are several publicly-known interoperating HIP implementations,
some of which are open source.

The Experimental RFCs originally produced by the HIP WG allowed the
community to experiment with HIP technologies and learn from these
experiments.  The HIP WG then worked on producing standards track
versions of the main HIP RFCs taking as a base the original
Experimental RFCs. Some of the original Experimental RFCs have already
been revised as standard track RFCs.

The HIP WG will finish revising the original Experimental RFCs into
standards track RFCs. In particular, the WG will revise the mobility,
multihoming, NAT traversal, and architecture specifications.

Additionally, the HIP WG will specify a standards track mechanism to
perform a light-weight HIP exchange, which will be suitable to be used
in constrained environments.

After completing the work items above, the HIP WG will be closed.