IETF Logo Mail Archive

Re: [Hipsec] 5201-bis -- HOST_ID format for RSA/DSA Identities

René Hummen <rene.hummen@comsys.rwth-aachen.de> Sun, 21 October 2012 13:19 UTC

Return-Path: <rene.hummen@comsys.rwth-aachen.de>
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 DCFDD21F8596 for <hipsec@ietfa.amsl.com>; Sun, 21 Oct 2012 06:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.948
X-Spam-Level:
X-Spam-Status: No, score=-5.948 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 BjevVoK76bto for <hipsec@ietfa.amsl.com>; Sun, 21 Oct 2012 06:19:17 -0700 (PDT)
Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.rwth-aachen.de [134.130.7.73]) by ietfa.amsl.com (Postfix) with ESMTP id B3F4721F849A for <hipsec@ietf.org>; Sun, 21 Oct 2012 06:19:16 -0700 (PDT)
MIME-version: 1.0
Received: from mx-out-1.rwth-aachen.de ([134.130.5.186]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0MC800NUXVO34430@mta-2.ms.rz.RWTH-Aachen.de> for hipsec@ietf.org; Sun, 21 Oct 2012 15:19:15 +0200 (CEST)
X-IronPort-AV: E=Sophos; i="4.80,625,1344204000"; d="p7s'?scan'208,217"; a="196363759"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by mx-1.rz.rwth-aachen.de with ESMTP; Sun, 21 Oct 2012 15:19:15 +0200
Received: from [192.168.2.12] ([unknown] [77.11.72.229]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0MC800B5TVO21U70@relay-auth-1.ms.rz.rwth-aachen.de> for hipsec@ietf.org; Sun, 21 Oct 2012 15:19:15 +0200 (CEST)
From: René Hummen <rene.hummen@comsys.rwth-aachen.de>
Content-type: multipart/signed; boundary="Apple-Mail=_EE114AD8-40AB-4191-A5F5-2928262AFFA8"; protocol="application/pkcs7-signature"; micalg="sha1"
Message-id: <2A95A711-0A60-4D83-82BC-EB0163FD61B1@comsys.rwth-aachen.de>
Date: Sun, 21 Oct 2012 15:19:13 +0200
References: <50759ACB.7070304@cs.hut.fi> <50814221.1060700@htt-consult.com> <F4955D25-BFDB-4431-8FD9-E516EFFFB0E8@gmail.com> <758141CC3D829043A8C3164DD3D593EA2E4C38C193@XCH-NW-16V.nw.nos.boeing.com> <5082BD8C.4090205@cs.hut.fi> <CALVM8ckEMi3OC_JazQFM979qX4koqgTz=7Vh3Py7mK+pByBuiA@mail.gmail.com>
To: "hipsec@ietf.org WG" <hipsec@ietf.org>
In-reply-to: <CALVM8ckEMi3OC_JazQFM979qX4koqgTz=7Vh3Py7mK+pByBuiA@mail.gmail.com>
X-Mailer: Apple Mail (2.1499)
Subject: Re: [Hipsec] 5201-bis -- HOST_ID format for RSA/DSA Identities
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: Sun, 21 Oct 2012 13:19:18 -0000

On 20.10.2012, at 23:21, Tobias Heer <heer@cs.rwth-aachen.de> wrote:
> Am 20.10.2012 17:04 schrieb "Miika Komu" <mkomu@cs.hut.fi>:
> >
> > Hi,
> >
> >
> > On 10/20/2012 01:28 AM, Henderson, Thomas R wrote:
> >>>
> >>>
> >>> Since parsing and formatting code for both is pretty much ubiquitous
> >>> and the packet space is dominated by the key itself, I see no real
> >>> reason to change.  That DNSKEY is supposed only to be used for DNSSEC
> >>> is a distraction, we have our own RR and reusing the wire format is
> >>> merely a convenience.
> >>
> >>
> >> +1
> >
> >
> > fine by me as well.
> 
> I agree. +1.
> 

I originally brought up the issue because I was not sure if 5201-bis was conflicting with the statement in RFC 4043. Now that things are clarified, it's fine by me.



--
Dipl.-Inform. Rene Hummen, Ph.D. Student
Chair of Communication and Distributed Systems
RWTH Aachen University, Germany
tel: +49 241 80 21429
web: http://www.comsys.rwth-aachen.de/team/rene-hummen/

v2.23.0 | Report a Bug | By Email