IETF Logo Mail Archive

Re: [Hipsec] Fwd: Status of WG items

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Sat, 15 December 2012 07:41 UTC

Return-Path: <thomas.r.henderson@boeing.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 8860821F8A28 for <hipsec@ietfa.amsl.com>; Fri, 14 Dec 2012 23:41:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lw7xtTYUiBxI for <hipsec@ietfa.amsl.com>; Fri, 14 Dec 2012 23:41:00 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id E061F21F8A21 for <hipsec@ietf.org>; Fri, 14 Dec 2012 23:41:00 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id qBF7f006008660 for <hipsec@ietf.org>; Fri, 14 Dec 2012 23:41:00 -0800
Received: from XCH-NWHT-03.nw.nos.boeing.com (xch-nwht-03.nw.nos.boeing.com [130.247.71.23]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id qBF7ewgP008652 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 14 Dec 2012 23:40:59 -0800
Received: from XCH-NW-16V.nw.nos.boeing.com ([130.247.25.238]) by XCH-NWHT-03.nw.nos.boeing.com ([130.247.71.23]) with mapi; Fri, 14 Dec 2012 23:40:58 -0800
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: 'Ari Keranen' <ari.keranen@nomadiclab.com>, "hipsec@ietf.org" <hipsec@ietf.org>
Date: Fri, 14 Dec 2012 23:40:58 -0800
Thread-Topic: [Hipsec] Fwd: Status of WG items
Thread-Index: Ac3Z/QZr4bJf9PfER26auLR1uD7uvQAmiOEg
Message-ID: <758141CC3D829043A8C3164DD3D593EA2E4D5DDEE7@XCH-NW-16V.nw.nos.boeing.com>
References: <4FE96F9F.3090800@ericsson.com> <758141CC3D829043A8C3164DD3D593EA1BD324E110@XCH-NW-16V.nw.nos.boeing.com> <4FEA1876.900@cs.rwth-aachen.de> <CAE_dhjveQ6WVVE3BVKk2txfBxNhfWvjbz+QVU2P919dNZ1WO4A@mail.gmail.com> <5012C05B.6080203@nomadiclab.com> <CAE_dhjufW+ic-VaBtqs787jK=xxy_XxnegpgGEtmpjZHsmJ4nA@mail.gmail.com> <505C213F.6050701@ericsson.com> <CAE_dhjv8LRwurQ9QmCmh6Spa+1UuECk1farGAKf_o9gYVsy_Lg@mail.gmail.com> <CAE_dhjsUXVwY8vXNLCwUjXPV9SxHTDbhk4dCt+ffQuQN=a6CMw@mail.gmail.com> <50615C93.6090300@ericsson.com> <5080010B.7030605@cs.hut.fi> <50CB264A.7030403@nomadiclab.com>
In-Reply-To: <50CB264A.7030403@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
X-TM-AS-MML: No
Subject: Re: [Hipsec] Fwd: Status of WG items
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Sat, 15 Dec 2012 07:41:01 -0000

> -----Original Message-----
> From: hipsec-bounces@ietf.org [mailto:hipsec-bounces@ietf.org] On
> Behalf Of Ari Keranen
> Sent: Friday, December 14, 2012 5:15 AM
> To: hipsec@ietf.org
> Subject: Re: [Hipsec] Fwd: Status of WG items
> 
> Or we can do this.
> 
> However, I would not be too concerned for the CERT draft blocking the
> reg draft given that the CERT draft should not require much (any?)
> changes for STD track. Of course that would need someone driving that
> work too.
> 
> If there's not enough interest for that work (I think it's important
> but don't have the cycles to do it myself), it makes sense to go
> forward as proposed below.

I agree with the above.  I would support carrying them forward as is and trying to publish together, but if the authors prefer to decouple, I would be fine with that approach.

- Tom

v2.23.0 | Report a Bug | By Email