[IPsec] Re: New Version Notification for draft-hu-ipsecme-pqt-hybrid-auth-04.txt

"Jun Hu (Nokia)" <jun.hu@nokia.com> Fri, 27 February 2026 22:58 UTC

Return-Path: <jun.hu@nokia.com>
X-Original-To: ipsec@mail2.ietf.org
Delivered-To: ipsec@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 972CABFFFAA2 for <ipsec@mail2.ietf.org>; Fri, 27 Feb 2026 14:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=nokia.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WxPmM34BGY3o for <ipsec@mail2.ietf.org>; Fri, 27 Feb 2026 14:58:35 -0800 (PST)
Received: from PH0PR06CU001.outbound.protection.outlook.com (mail-westus3azon11011042.outbound.protection.outlook.com [40.107.208.42]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A962DBFFFA9B for <ipsec@ietf.org>; Fri, 27 Feb 2026 14:58:35 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=OitoRdTbHobzG+84MYPL9kk1hgZsTXSD0vJECuDjmDH2CVqUOqLXNLONqkvx7QOZZ4zsGHlCO3gAusDZg6hfjJBvSs4tpyPLrDwhPhqVTx6zywpG5Oj7QagESAmPfqYoOUOIOpqY53m8WH2XX432ej+xvWcuvbyZ46aB/mJJ3Yqr4d3WBaIXhtd2DtDp80T8td1n8NhtBLj/68892HLn7XH6uJxoqmUqG0Cx4MqxOUOQEAhPFZlF0HFjEcJC3INXNgG/Zbhjd2htII/19mkzW9Iuu8uSOMrf09aZdXY6iS6FvP6bPUDnyVpBQm1yYnXHU+eCeOAknhQjw+6Zl5f7pA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=YJBcCDfI2YUgUZOejXZ58BX+4LeAkIKwGwUEnQ+eh3Q=; b=fIxml+REu9k6s0eTiUUC9iDebPs+nu/L6jYYfFTXZiMW19wUQHQyDyS+UceUJ2Z1bjxvRbxPOqR5Yb6K0FXVURS0fVyDlTWQQovsAcWI8PE6rgNJMb1E6pKZdpBwiGktrKQNyRI8L47xyPR3swZacUpmSTXkxjPwa5/JWA3D1xUgXiRROyrDunmEe1lb+J9vjB4J80ZkML12YvSrU8H9fBHy1MIHmwsXX3ltIC30YbZl3OtNQEicdXNgjywqU0haStFBArp0afCj5ZU6WjhMvsSxxe9kJLOw1ruSnysyQXWC7nyl4T8mMgaV4QIcRL5s5d3lzENVY/l5tAZdPPFznQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=YJBcCDfI2YUgUZOejXZ58BX+4LeAkIKwGwUEnQ+eh3Q=; b=YhiVBmpmK9/F9bqkn01ZYL3KHT2LJrZDFJfFWn/4iX4twcTxFtftXFgD0F2OV0RWq0wBERnZHlakjBPrLBC2OR1gnuKJXzVk5y+ZGtV2NbNQ64QPhbgAAKBD9qtwk0M0aQ0Br8Qytmzzltba7BeRuAmMX80WcDZNyNgpdRvAF+dF1bmo25XJqh8HtlTcf0zJlED1rLO5aOsfQQcm9QiDIH5GwjFTtfCTXlvvRrO2n+pyHFGqrCg676xsGxSr5/8fttjqppm7AwOiCwkgLqdlnvyQVfEXbdNCBF2+ediwM8mjwAwAIu3e7+lZJdKroUPyAcldQ6XBINddS2BAiARByw==
Received: from BYAPR08MB5288.namprd08.prod.outlook.com (2603:10b6:a03:4d::33) by DS0PR08MB9695.namprd08.prod.outlook.com (2603:10b6:8:1a0::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9654.16; Fri, 27 Feb 2026 22:58:20 +0000
Received: from BYAPR08MB5288.namprd08.prod.outlook.com ([fe80::8553:fc80:6a1a:b2bf]) by BYAPR08MB5288.namprd08.prod.outlook.com ([fe80::8553:fc80:6a1a:b2bf%5]) with mapi id 15.20.9632.017; Fri, 27 Feb 2026 22:58:20 +0000
From: "Jun Hu (Nokia)" <jun.hu@nokia.com>
To: "Scott Fluhrer (sfluhrer)" <sfluhrer=40cisco.com@dmarc.ietf.org>, IPsecME WG <ipsec@ietf.org>
Thread-Topic: New Version Notification for draft-hu-ipsecme-pqt-hybrid-auth-04.txt
Thread-Index: AQHcqB4P6Vm8ZtT6tk6zlsvnPglZo7WW/IRggAAILrmAABZcwA==
Date: Fri, 27 Feb 2026 22:58:19 +0000
Message-ID: <BYAPR08MB5288A989B85A8647F71C831A9573A@BYAPR08MB5288.namprd08.prod.outlook.com>
References: <177221998862.2903818.6209802431990106680@dt-datatracker-6ff7c68975-7k42g> <BYAPR08MB5288F49D7ADD193217871ADC9573A@BYAPR08MB5288.namprd08.prod.outlook.com> <PH3PPFA3FE8A23FF6EECBFCBAD114EB2A9AC173A@PH3PPFA3FE8A23F.namprd11.prod.outlook.com>
In-Reply-To: <PH3PPFA3FE8A23FF6EECBFCBAD114EB2A9AC173A@PH3PPFA3FE8A23F.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=nokia.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: BYAPR08MB5288:EE_|DS0PR08MB9695:EE_
x-ms-office365-filtering-correlation-id: b244c20f-e69d-4906-61bf-08de7653b39d
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|1800799024|366016|376014|4022899009|38070700021|8096899003|13003099007|7053199007|7142099003;
x-microsoft-antispam-message-info: VPBgfRY4L78m/Ktz+p4XG9dvjuwgjmcTYAZg46O6vkxI1Z3mujl/3F+YSX2mWcRc7+XPe6iWTFoI+LO6MZjL620x78oTS/G6r3S3K2N/lUXnTqaZB4cpiwM8+w/vFBzawoplT+kmPdoXU+WuzRoZIUCzPsuaHFEoR5Pdg1QEXPOFoT0aRstbTXTQDmZnYU+FVwTRXE7kr4oPnTEEjLZkusUxPl/V/G/JOQ4KDjD2JWNp5ZaOVG/tgZHMPyGg2InJ2tvmZ8X66uyasXAzib/L2VUCe64RIbR3Wq0LpY88xWP5hY7ITMAp3mM5x4/b0a4laNQGvgxmR1bkYRjvvjmUhyxBoGWeQDaEUni3lsUAq6Mza8r0yt5KTwjjTxqb0B2a31Bx9wNlEWNRFzSJ2SSpLMIkvkYm/RGP9hHkGyQQKcEwY6LndQKLsA+JgnwlthqBeEjCYDAGqfYVhd18C8JGIFeYYZxq0WWsLGXUh0NHm6OBdAPEgo1oeWYzD4znJmKYXAyP6vcMueFlTYodSex1PEU8D/m5Tu6KV+AuTj31oIFRJI4BZMC6OKBI6ezEvrUEPhddMTF/okY2sEMJXGFOT3n6gQa7bveDisK7TJu8/vUMXvnF6D/mZVoTUm+hAn5MbIFNd1p+qU00haEhOQceqiJsUhtpel327HgZTDXbNryjsLMX1T+1vsmf7ISV2PbKvqUGxNsXZIAc2oSf6auHyRKbZhzpxafTfBCl//h12x/EdCbB3QCPlqKfgqjk5FqhIXU7Hav4HXDK1UWWOiUy27JBLTfMHQ+ZaAYYF1ATUW0=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:ja;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:BYAPR08MB5288.namprd08.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(1800799024)(366016)(376014)(4022899009)(38070700021)(8096899003)(13003099007)(7053199007)(7142099003);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: vAaUj39pS2oJzNtiDD4ljRen5aKLfsrsneK2glySvRPXYY+ot2BkFg1AUWm9E206555fr/DIuY5tS7z6LhhEf6+10rYmothUXgP/17hJ35DpG21V78ifjP4pUR/9XINIld4KRo/V6mGhOFrbKAKgZ9qCu3N97cFyHgM9vPvuVRAjTLB1NCmt6FvEdDZrsVHxdEgDrLCuoeVin91KJD209vAY5yVVHXLvp9nEgvol2ys3KxNOXu+bjWIvPu4vpdDnNqzqNmvGhyXoHo9gvc4kEJmRMKJUofXprobdQz72ny/elKI6aUZh1Cz1vHooGOrIAyneiCLn20jyP7uawjau1XH75z8N2eDlR5P60es3osZnAdEwL7pV0E9S5zMa+LdZgf3CjvpSApIqwLm1tHelnR9BgPxA51CnOSSfGWKmu7ZzQRhAUlh+It0zpgJGNy8t6JAJFfHK+Yc/70JGiAXcuEB/XIS4gOMbfrweEsVWoRPHATXE7cIJizUcEoz31z7C3uhdHG4677GZ9bEVdzUt7tSsmuhgp41G8C5eRb6pWBdW5pBeZKh8j6Z6ayTrJ65cMVT4Vy3PSp2FlMPhN/u+LlXbPVofyqD6GDzako+awKmsh2NBG0hfO2QGoJzIGO5VuzTVEOn/C2b3Ws9MqXorbmvYlb8ZU366fOhJej/q/huTINZrYvWKUqtMa8NEC2oI/0Lu5DYoUY+wbvAuNNOjqBnZSA8Ujc+mxbueis3ANwcOfWiOb0GHtxsFceiBHfGAUzV47Ev6REtXyiQJIFvylffmuHlIv6DuLYz4NZ6j6Nh24QpZc5ZQV3qaOKDoqogpoNabWE9KY9v7ZjsiC+haqI5zuGJcsCippiUNFM/hqNW/7Lz06dFfls2gx73jBc62yf68daknRNmZ+tZ5Wql+kLL8L5x9xKDq5b8E1TqUp/MUACD4ifeSd4Q7oqiUtV6+kxgR1I6Mv0oX+UF0FDsDnMGsp8zyyKlRbOXC1mC1ot3EbBru0tp++oKgYYbTghLMwx9WEadWqUklSYIyODOwq4WaZXTXUPXC0HW28ph2zJg6BZUeVkRccXTycm89mmddBZY57tzQjLA33xmw9Y+rtCTLD59mlonM90vuVkjl5LcRr58848L4dwsMhUt0AZ1qkhuJlAy9yRk2/cS6P4ii/TYjixDq+eitZ4wTCOZJh41j4xUuo82+KqJYAz63S2MHdjstUJihkMAI3xa+MoL12/qYRKFDQopfCtHmj0vgNzJwkMjyDYG6hJ+kbXln5dpp+6fDaYJ5OxRaqiTTIm7973qMmE+u4tEF1wWm5V4fcGS34wtaK3funpy3rwMmTnjUbyDEzKmUU8TKb2GRYmbTiTAPSY/krY+vHLbge5/dBvhTKBBBLSjGikry92QR99ARyzDx+oswK2WJJkz/E46sW3ecSByYf+IuOodFNJoBUd8/h4nqVt+AnUj/e7CzVIu/J26teoae9l8yDcoUgx4Sme1KDlnjiaoDPJ7u9KS1ajKeT6aCq++95rRADndMCabZLYoousMkJmNHMuUNw2qTQesbBP9roMyWNffT/J63CHPEa70ObGvBaTwbMfvggeW2KrwP9/h25Q8tza/qeH/lMnPw2Jerr4G8Txs4e5wgYYWDOGM1K6SmWkQ8JnOMVxriGc8JvmhKf9GMg2ryy/tCo24lXX+xW1aLzbN/ZAuO0o8KLVw1vtDJrhYA5yHyhU3s
Content-Type: multipart/alternative; boundary="_000_BYAPR08MB5288A989B85A8647F71C831A9573ABYAPR08MB5288namp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR08MB5288.namprd08.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b244c20f-e69d-4906-61bf-08de7653b39d
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2026 22:58:20.0468 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: JJBujZ8MxhUejp/reqEKNhkcBFkjAX8Q+3E2WbSnE6tHJKFG2jVvVKl7PMTXJCKPv+8ROYqWQI70iGCrw1Qx7g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DS0PR08MB9695
Message-ID-Hash: 3WBHBAG7N6NFRDOA6DUVFQ5G6GQ75AFL
X-Message-ID-Hash: 3WBHBAG7N6NFRDOA6DUVFQ5G6GQ75AFL
X-MailFrom: jun.hu@nokia.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipsec.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [IPsec] Re: New Version Notification for draft-hu-ipsecme-pqt-hybrid-auth-04.txt
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/rR5W7Z_JIMVzre-YhI_9NUmOwuE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Owner: <mailto:ipsec-owner@ietf.org>
List-Post: <mailto:ipsec@ietf.org>
List-Subscribe: <mailto:ipsec-join@ietf.org>
List-Unsubscribe: <mailto:ipsec-leave@ietf.org>

Thanks Scott for your comments, see my reply below inline as [HJ]

From: Scott Fluhrer (sfluhrer) <sfluhrer=40cisco.com@dmarc.ietf.org>
Sent: Friday, February 27, 2026 1:11 PM
To: Jun Hu (Nokia) <jun.hu@nokia.com>; IPsecME WG <ipsec@ietf.org>
Subject: Re: New Version Notification for draft-hu-ipsecme-pqt-hybrid-auth-04.txt


CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.


Two comments:


  *   In section 5, "the initiator chooses a combination from the responder's SUPPORTED_AUTH_METHODS"; but no guidance is given about how to make this choice (and similarly for the responder).  Ultimately, the proper choice would depend on the peer's policy, that is, what sets of signatures the peer would insist on as a proper validation, and no mechanism exists for communicating that for multiple certificates (currently, it is implied that any single supported signature algorithm with a valid certificate is sufficient).  When multiple certificates are in play, then a peer might have either of these policies: "I'd prefer an RSA cert and an ML-DSA cert, but I'll accept only an RSA cert" (which the peer might do during a general upgrade), or your policy might be "You must have an RSA cert and an ML-DSA cert, or I won't talk to you" *which might be after you've upgraded all your peers).  Now, I suppose you can say "choose the maximal set of certificates, and if that'd not sufficient, the IKE negotiation would fail" - I believe that a cleaner approach would be to inform the peer of the policy up front (and if we can't abide by that, the error is more apparent).
[HJ] I think this is about the semantic of SUPPORTED_AUTH_METHODS as defined in RFC9593; my understanding is the methods in SUPPORTED_AUTH_METHODS  are the methods sender expects receiver to use to authenticate itself (generate receiver’s AUTH payload); e.g. if peer A include method-1 in its SUPPORTED_AUTH_METHODS to peer B, then it means A expects B to use method-1 to generate the AUTH payload it sends to A; there is no mechanism defined in RFC9593 (or other RFC AFAIK) allows sender to also announce the methods of generating sender’s AUTH payload.
This draft is only extending RFC9593, but not trying to  (and I think it should not)  change this basic semantic of SUPPORTED_AUTH_METHODS.
As with you example "I'd prefer an RSA cert and an ML-DSA cert, but I'll accept only an RSA cert", I assume it means e.g. peer A only authenticate B via RSA but it prefer to use RSA+ML-DSA to authenticate itself. So A need to only include method 1 in its SUPPORTED_AUTH_METHODS  to B, and A will use RSA+ML-DSA cert if B includes RSA+ML-DSA+type-2 in B’s SUPPORTED_AUTH_METHODS
For the other example  "You must have an RSA cert and an ML-DSA cert, or I won't talk to you", then A only includes RSA+ML-DSA +type-2 in A’s SUPPORTED_AUTH_METHODS, and fail the setup if B doesn’t include same in B’s SUPPORTED_AUTH_METHODS


  *   I personally disagree with bolting into the protocol any characterization of a cryptographical algorithm beyond the minimal ("it's a signature algorithm").  Your protocol makes an explicit distinction between "traditional" and "PQC"; in the future, that understanding may change or get more nuanced.  I believe it would be wise if the protocol took a broader and more extensible view.
[HJ] This is due to the driving use case is PQC hybrid authentication, “traditional” and “PQC” are the terms used in such context. But I am open to make it generic.


________________________________
From: Jun Hu (Nokia) <jun.hu=40nokia.com@dmarc.ietf.org<mailto:jun.hu=40nokia.com@dmarc.ietf.org>>
Sent: Friday, February 27, 2026 3:22 PM
To: IPsecME WG <ipsec@ietf.org<mailto:ipsec@ietf.org>>
Subject: [IPsec] FW: New Version Notification for draft-hu-ipsecme-pqt-hybrid-auth-04.txt

Hi,
Here is an update to draft-hu-ipsecme-pqt-hybrid-auth, review and comments are appreciated

What's changed in v04:

   *  align to draft-ietf-lamps-pq-composite-sigs-14
   *  add text to clarify two setup types
   *  add text to describe the example exchange in section 5
   *  clarify using of pre-hash alg
   *  clarify sign operation in type-2
   *  ietf-lamps-cert-binding-for-multi-auth is now RFC9763
   *  ietf-lamps-dilithium-certificates is now RFC9881
   *  editorial changes

-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Sent: Friday, February 27, 2026 11:20 AM
To: Guilin WANG <Wang.Guilin@huawei.com<mailto:Wang.Guilin@huawei.com>>; Guilin Wang <Wang.Guilin@huawei.com<mailto:Wang.Guilin@huawei.com>>; Jun Hu (Nokia) <jun.hu@nokia.com<mailto:jun.hu@nokia.com>>; Yasufumi Morioka (森岡 康史) <yasufumi.morioka.dt@nttdocomo.com<mailto:yasufumi.morioka.dt@nttdocomo.com>>
Subject: New Version Notification for draft-hu-ipsecme-pqt-hybrid-auth-04.txt


CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.



A new version of Internet-Draft draft-hu-ipsecme-pqt-hybrid-auth-04.txt has been successfully submitted by Jun Hu and posted to the IETF repository.

Name:     draft-hu-ipsecme-pqt-hybrid-auth
Revision: 04
Title:    Post-Quantum Traditional (PQ/T) Hybrid PKI Authentication in the Internet Key Exchange Version 2 (IKEv2)
Date:     2026-02-27
Group:    Individual Submission
Pages:    14
URL:      https://www.ietf.org/archive/id/draft-hu-ipsecme-pqt-hybrid-auth-04.txt
Status:   https://datatracker.ietf.org/doc/draft-hu-ipsecme-pqt-hybrid-auth/
HTML:     https://www.ietf.org/archive/id/draft-hu-ipsecme-pqt-hybrid-auth-04.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-hu-ipsecme-pqt-hybrid-auth
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-hu-ipsecme-pqt-hybrid-auth-04

Abstract:

   One IPsec area that would be impacted by Cryptographically Relevant
   Quantum Computer (CRQC) is IKEv2 authentication based on traditional
   asymmetric cryptographic algorithms: e.g RSA, ECDSA, which are widely
   deployed authentication options of IKEv2.  There are new Post-Quantum
   Cryptographic (PQC) algorithms for digital signature like NIST
   [ML-DSA], However, it takes time for new cryptographic algorithms to
   mature, There is security risk to use only the new algorithm before
   it is field proven.  This document describes a hybrid PKI
   authentication scheme for IKEv2 that incorporates both traditional
   and PQC digital signature algorithms, so that authentication is
   secure as long as one algorithm in the hybrid scheme is secure.



The IETF Secretariat


_______________________________________________
IPsec mailing list -- ipsec@ietf.org<mailto:ipsec@ietf.org>
To unsubscribe send an email to ipsec-leave@ietf.org<mailto:ipsec-leave@ietf.org>