[MMUSIC] Further Question to MIKEY embedding with kmgmt-ext.
Fries Steffen <steffen.fries@siemens.com> Tue, 12 April 2005 08:10 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06071 for <mmusic-web-archive@ietf.org>; Tue, 12 Apr 2005 04:10:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLGdP-0000Ai-PD for mmusic-web-archive@ietf.org; Tue, 12 Apr 2005 04:20:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLGRw-0001ZE-75; Tue, 12 Apr 2005 04:08:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLGRs-0001YU-5a for mmusic@megatron.ietf.org; Tue, 12 Apr 2005 04:08:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05904 for <mmusic@ietf.org>; Tue, 12 Apr 2005 04:08:30 -0400 (EDT)
Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLGbF-00006U-PN for mmusic@ietf.org; Tue, 12 Apr 2005 04:18:24 -0400
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id j3C88R1a032137; Tue, 12 Apr 2005 10:08:27 +0200
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99]) by mail2.siemens.de (8.12.6/8.12.6) with ESMTP id j3C88PmY027437; Tue, 12 Apr 2005 10:08:25 +0200
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72) id <2SQ524S6>; Tue, 12 Apr 2005 10:08:25 +0200
Message-ID: <AFE91B59A185A5439840B43AB791904701744B98@mchp997a.mch.sbs.de>
From: Fries Steffen <steffen.fries@siemens.com>
To: Fries Steffen <steffen.fries@siemens.com>, elisabetta.carrara@ericsson.com
Date: Tue, 12 Apr 2005 10:08:24 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: mmusic@ietf.org
Subject: [MMUSIC] Further Question to MIKEY embedding with kmgmt-ext.
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Hi, I've got another question to MIKEY usage. When a SIP dialog has been established and further offer/answer messages are to be sent, does one need to include MIKEY container when no changes to the established MIKEY parameter are there? regards Steffen > -----Original Message----- > From: mmusic-bounces@ietf.org > [mailto:mmusic-bounces@ietf.org] On Behalf Of Fries Steffen > Sent: Monday, April 11, 2005 8:55 AM > To: elisabetta.carrara@ericsson.com > Cc: mmusic@ietf.org > Subject: [MMUSIC] Question to MIKEY embedding with kmgmt-ext. > > Hi Elisabetta, > > recently a question came up in the usage of the key > management extentions for SIP to use MIKEY: > > Section 3.1.2 of draft-ietf-mmusic-kmgmt-ext-14 contains the following > statement: > > "If the key management rejects the offer and the session > needs to be aborted, the answerer SHOULD return a "488 Not > Acceptable Here" message, optionally also including one or > more Warning headers (a 306 "Attribute not understood" when > one of the parameters is not supported, and a 399 > "Miscellaneous warning" with arbitrary information to be > presented to a human user or logged, see Section 20.43 in > [SIP]). Further details about the cause of failure MAY be > described in an included message from the key management > protocol. The session is then aborted (and it is up to local > policy or end user to decide how to continue)." > > Concerning the sentence in bold (The sentence before the last > sentence in quotes), how does it do that in the following scenario?: > A UA receives an INVITE request containing an SDP offer with > a MIKEY I_MESSAGE that is for some reason unacceptable. The > receiving UA will return a 488 response, which does not > contain an SDP answer. Therefore there is no way of embedding > a MIKEY R_MESSAGE to indicate the error. Is there any way to > signla the MIKEY error in this case? > > Regards > Steffen > > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www1.ietf.org/mailman/listinfo/mmusic > _______________________________________________ mmusic mailing list mmusic@ietf.org https://www1.ietf.org/mailman/listinfo/mmusic
- [MMUSIC] Further Question to MIKEY embedding with… Fries Steffen