Re: Informational RFC to be: draft-arkko-map-doi-08.txt
The IESG <iesg-secretary@ietf.org> Fri, 09 April 2004 18:53 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12003 for <ietf-announce-archive@odin.ietf.org>; Fri, 9 Apr 2004 14:53:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC17w-0005oG-IA for ietf-announce-archive@odin.ietf.org; Fri, 09 Apr 2004 14:53:20 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i39IrKjn022293 for ietf-announce-archive@odin.ietf.org; Fri, 9 Apr 2004 14:53:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC13n-0004YI-Eh; Fri, 09 Apr 2004 14:49:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC0Zg-0001xL-1c for ietf-announce@optimus.ietf.org; Fri, 09 Apr 2004 14:17:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10760 for <ietf-announce@ietf.org>; Fri, 9 Apr 2004 14:17:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BC0Zd-0001Zf-00 for ietf-announce@ietf.org; Fri, 09 Apr 2004 14:17:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BC0Ye-0001UW-00 for ietf-announce@ietf.org; Fri, 09 Apr 2004 14:16:52 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BC0Xw-0001Of-00; Fri, 09 Apr 2004 14:16:08 -0400
Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1BC0Xw-0001nx-0H; Fri, 09 Apr 2004 14:16:08 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: RFC Editor <rfc-editor@rfc-editor.org>
Cc: The IESG <iesg@ietf.org>, iana@iana.org
Subject: Re: Informational RFC to be: draft-arkko-map-doi-08.txt
Message-Id: <E1BC0Xw-0001nx-0H@optimus.ietf.org>
Date: Fri, 09 Apr 2004 14:16:08 -0400
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
The IESG has no problem with the publication of 'The Mobile Application Part SECurity (MAPSEC) Domain of Interpretation (DOI) for the Internet Security Association and Key Management Protocol (ISAKMP)' <draft-arkko-map-doi-08.txt> as an Informational RFC. The IESG contact person is Russ Housley. Thank you, The IESG Secretary Technical Summary The Mobile Application Part (MAP) protocol is a signaling protocol for cellular networks. The MAP Security (MAPSEC) protocol provides a secure way to transport MAP messages. To use MAPSEC, however, Security Associations (SAs) are needed. This document defines how such SAs can be created automatically. We use the Internet Security Association and Key Management Protocol (ISAKMP) as a framework for managing SAs and establishing keys. The framework can be specialized to a particular task. Such a specialization is called a Domain of Interpretation (DOI), and this document defines the MAPSEC DOI. This specialization is very similar to the Internet Key Exchange protocol and the ISAKMP specialization for IP Security, except that SAs for use with non-IP protocols are being negotiated. End-run Review This document was reviewed by Russ Housley for the IESG. IESG Note This document is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this document for any purpose, and in particular notes that it has not had IETF review for such things as security, congestion control or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce