Re: [Ipsec] draft-solinas-ui-suites-00.txt
Paul Hoffman <paul.hoffman@vpnc.org> Sun, 17 December 2006 16:59 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GvzMg-00016Y-II; Sun, 17 Dec 2006 11:59:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GvzMf-00016S-7F for ipsec@ietf.org; Sun, 17 Dec 2006 11:59:53 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GvzMd-00015O-RZ for ipsec@ietf.org; Sun, 17 Dec 2006 11:59:53 -0500
Received: from [10.20.30.101] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id kBHGxgra076370; Sun, 17 Dec 2006 09:59:43 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624088cc1ab2734b944@[10.20.30.101]>
In-Reply-To: <1479D5BA-A0B1-4321-89E1-92CE778B8D9C@checkpoint.com>
References: <7.0.0.16.2.20061208152939.0794cbd8@vigilsec.com> <1479D5BA-A0B1-4321-89E1-92CE778B8D9C@checkpoint.com>
Date: Sun, 17 Dec 2006 08:59:31 -0800
To: Yoav Nir <ynir@checkpoint.com>, Russ Housley <housley@vigilsec.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [Ipsec] draft-solinas-ui-suites-00.txt
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: ipsec@ietf.org
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Security <ipsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
Errors-To: ipsec-bounces@ietf.org
At 10:32 AM +0200 12/17/06, Yoav Nir wrote: >I think that in RFC 4308 they intentionally used names that do not >name specific algorithms. This is for having a uniform name across >VPN devices and to allow users with no background in cryptography >(and those who don't read the IPsec list) to configure VPN devices >without confusing terms. That's why the names defined there are >VPN-A and VPN-B. > >I suggest that "Suite-B-GCM-128" goes against that. I think better >names would be VPN-C, VPN-D etc. I disagree here. The names are not important as long as there is no obvious clash. As the draft shows, the name "Suite B" is already in widespread use within the community of interest, as well as with IPsec vendors who want to participate in that community in the future. >If it's really important to include the SuiteB name, I'd still go >with SuiteB-1, SuiteB-2 etc. I disagree again. It is up to the community to decide how much or little specificity should be included in the names. When we came up with VPN-A and VPN-B, that's what the general IPsec population of the time wanted, although we could have chosen VPN-TripleDES and VPN-AES12 or somesuch. --Paul Hoffman, Director --VPN Consortium _______________________________________________ Ipsec mailing list Ipsec@ietf.org https://www1.ietf.org/mailman/listinfo/ipsec
- [Ipsec] draft-solinas-ui-suites-00.txt Russ Housley
- Re: [Ipsec] draft-solinas-ui-suites-00.txt Yoav Nir
- Re: [Ipsec] draft-solinas-ui-suites-00.txt Paul Hoffman
- Re: [Ipsec] draft-solinas-ui-suites-00.txt Yoav Nir
- Re: [Ipsec] draft-solinas-ui-suites-00.txt Tero Kivinen
- Re: [Ipsec] draft-solinas-ui-suites-00.txt Paul Hoffman
- Re: [Ipsec] draft-solinas-ui-suites-00.txt Yoav Nir