Re: I-D ACTION:draft-ietf-hip-base-03.txt

Bruce Lilly <blilly@erols.com> Fri, 24 June 2005 00:01 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dlbd0-0007kf-3x; Thu, 23 Jun 2005 20:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dlbcw-0007jf-7C for ietf@megatron.ietf.org; Thu, 23 Jun 2005 20:01:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17908 for <ietf@ietf.org>; Thu, 23 Jun 2005 20:00:57 -0400 (EDT)
Received: from ns4a.townisp.com ([216.195.0.138] helo=ns4.townisp.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dlc1L-0005hh-HX for ietf@ietf.org; Thu, 23 Jun 2005 20:26:12 -0400
Received: from mail.blilly.com (dhcp-0-8-a1-c-fa-f7.cpe.townisp.com [216.49.158.220]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "marty.blilly.com", Issuer "Bruce Lilly" (not verified)) by ns4.townisp.com (Postfix) with ESMTP id 0786F29931; Thu, 23 Jun 2005 20:00:53 -0400 (EDT)
Received: from marty.blilly.com (marty.blilly.com [192.168.99.98] (may be forged)) by mail.blilly.com with ESMTP id j5O00pFR015819(8.13.1/8.13.1/mail.blilly.com /etc/sendmail.mc.mail 1.25 2005/06/05 08:09:15) (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) ; Thu, 23 Jun 2005 20:00:51 -0400
Received: from marty.blilly.com (localhost [127.0.0.1]) (authenticated (0 bits)) by marty.blilly.com with ESMTP id j5O00o1g015818(8.13.1/8.13.1/blilly.com submit.mc 1.3 2005/04/08 12:29:31) (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) ; Thu, 23 Jun 2005 20:00:51 -0400
From: Bruce Lilly <blilly@erols.com>
Organization: Bruce Lilly
To: ietf@ietf.org
Date: Thu, 23 Jun 2005 20:00:45 -0400
User-Agent: KMail/1.8.1
References: <E1DlaWH-0007zv-Bo@newodin.ietf.org>
In-Reply-To: <E1DlaWH-0007zv-Bo@newodin.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200506232000.47898.blilly@erols.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: petri.jokela@nomadiclab.com, rgm@icsalabs.com, thomas.r.henderson@boeing.com
Subject: Re: I-D ACTION:draft-ietf-hip-base-03.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Thu June 23 2005 18:50, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Host Identity Protocol Working Group of the IETF.
> 
> 	Title		: Host Identity Protocol
> 	Author(s)	: R. Moskowitz, et al.
> 	Filename	: draft-ietf-hip-base-03.txt
> 	Pages		: 96
> 	Date		: 2005-6-23
> 	
> This memo specifies the details of the Host Identity Protocol (HIP).
>    HIP provides a rapid exchange of Host Identities (public keys)
>    between hosts and uses a Sigma-compliant [REF] Diffie-Hellman key
>    exchange to establish shared secrets between such endpoints.  The
>    protocol is designed to be resistant to Denial-of-Service (DoS) and
>    Man-in-the-middle (MitM) attacks, and when used together with another
>    suitable security protocol, such as Encapsulated Security Payload
>    (ESP) [24], it provides encryption and/or authentication protection
>    for upper layer protocols such as TCP and UDP, while enabling
>    continuity of communications across network layer address changes.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-hip-base-03.txt

Brief comments:

1. The Abstract isn't supposed to contain references.

2. It is helpful to indicate a suggested forum for discussion
   (the Abstract is a good place)

3. Numeric references are deprecated
   http://www.rfc-editor.org/pipermail/rfc-interest/2005-January/000235.html

4. The introduction refers to an architecture document, reference #25:
   [25]  Moskowitz, R., "Host Identity Protocol Architecture",
         draft-moskowitz-hip-arch-03 (work in progress), May 2003.

   Given the date, I strongly suspected expiration; I checked the I-D
   database:
   https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=4950
   which shows a -06 version as the latest, also expired, and therefore no
   link to retrieve the document.  Dead End.

5. Appendices (the draft's contain reference citations) should appear
   before the Normative/Informative references.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf