Re: [Hipsec] New HIP WG charter proposal

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Tue, 18 May 2010 17:22 UTC

Return-Path: <thomas.r.henderson@boeing.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 064753A6C1D for <hipsec@core3.amsl.com>; Tue, 18 May 2010 10:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.277
X-Spam-Level:
X-Spam-Status: No, score=-4.277 tagged_above=-999 required=5 tests=[AWL=-0.278, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
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 sQWL13dZz1t5 for <hipsec@core3.amsl.com>; Tue, 18 May 2010 10:22:48 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id D735A28C196 for <hipsec@ietf.org>; Tue, 18 May 2010 10:18:03 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o4IHHcV6004922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 18 May 2010 12:17:39 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o4IHHcVB029924; Tue, 18 May 2010 10:17:38 -0700 (PDT)
Received: from XCH-NWHT-04.nw.nos.boeing.com (xch-nwht-04.nw.nos.boeing.com [130.247.64.250]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o4IHHbSR029891 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 18 May 2010 10:17:37 -0700 (PDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-04.nw.nos.boeing.com ([130.247.64.250]) with mapi; Tue, 18 May 2010 10:17:37 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: 'Jan Melen' <jan.melen@nomadiclab.com>, Robert Moskowitz <rgm@htt-consult.com>
Date: Tue, 18 May 2010 10:17:36 -0700
Thread-Topic: [Hipsec] New HIP WG charter proposal
Thread-Index: AcrscCn+m/JNWtaOT1SWw+D7YzjcbAKPWepg
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CE9716193@XCH-NW-10V.nw.nos.boeing.com>
References: <4BDBD41E.5030107@ericsson.com> <4BDFE5B7.3020500@oracle.com><4BE02580.8060808@htt-consult.com> <5E24EE17-E367-4CA9-9453-EF3DFF264DFD@nomadiclab.com>
In-Reply-To: <5E24EE17-E367-4CA9-9453-EF3DFF264DFD@nomadiclab.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] New HIP WG charter proposal
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: Tue, 18 May 2010 17:22:52 -0000

> -----Original Message-----
> From: hipsec-bounces@ietf.org
> [mailto:hipsec-bounces@ietf.org] On Behalf Of Jan Melen
> Sent: Wednesday, May 05, 2010 9:29 AM
> To: Robert Moskowitz
> Cc: HIP
> Subject: Re: [Hipsec] New HIP WG charter proposal
>
> Hi,
>
> To me the new charter looks good. For referrals I don't see
> any big problems as mentioned already by Miika and Bob we
> have gained quite a bit experience on how much of an problem
> the referrals are and according to that experience there is
> only very few cases where they cannot be made to work, in all
> other cases the referrals can be resolved through mechanisms
> described by Bob.
>
> Of course these are issues that need to be documented in
> architecture and DNS documents
>
>    Regards,
>     Jan

I'd also like to support the new charter proposal, and also mention that there is some documentation about referrals in RFC 5338.

Tom