RE: [NSIS] AD Review comments on draft-ietf-nsis-req-07.txt

john.loughney@nokia.com Tue, 17 June 2003 17:53 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28241 for <nsis-archive@odin.ietf.org>; Tue, 17 Jun 2003 13:53:48 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5HHrKp05306 for nsis-archive@odin.ietf.org; Tue, 17 Jun 2003 13:53:20 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5HBw8a20968; Tue, 17 Jun 2003 07:58:08 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5HBvvm20915 for <nsis@optimus.ietf.org>; Tue, 17 Jun 2003 07:57:57 -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 HAA08595 for <nsis@ietf.org>; Tue, 17 Jun 2003 07:57:56 -0400 (EDT)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SF3s-0005Al-00 for nsis@ietf.org; Tue, 17 Jun 2003 07:55:40 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 19SF3r-0005Ai-00 for nsis@ietf.org; Tue, 17 Jun 2003 07:55:39 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37]) by mgw-x1.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h5HBvra04993 for <nsis@ietf.org>; Tue, 17 Jun 2003 14:57:53 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T62e2ae5d3bac158f25813@esvir05nok.ntc.nokia.com>; Tue, 17 Jun 2003 14:57:52 +0300
Received: from esebe016.NOE.Nokia.com ([172.21.138.55]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 17 Jun 2003 14:57:51 +0300
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebe016.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Tue, 17 Jun 2003 14:57:51 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [NSIS] AD Review comments on draft-ietf-nsis-req-07.txt
Date: Tue, 17 Jun 2003 14:57:50 +0300
Message-ID: <DADF50F5EC506B41A0F375ABEB32063658EEC1@esebe023.ntc.nokia.com>
Thread-Topic: [NSIS] AD Review comments on draft-ietf-nsis-req-07.txt
Thread-Index: AcM0xUAMoWiZNu2KSMWoRlS5nClNvQAAa4DQ
To: karagian@cs.utwente.nl, Attila.Bader@eth.ericsson.se, mankin@psg.com
Cc: nsis@ietf.org
X-OriginalArrivalTime: 17 Jun 2003 11:57:51.0221 (UTC) FILETIME=[AD9A4250:01C334C7]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5HBvvm20917
Sender: nsis-admin@ietf.org
Errors-To: nsis-admin@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi Georgios,

> > We are designing this for the Internet (see the 'I' in the
> > IETF).  This being so, security is extremely important and
> > is needed to ensure a robust protocol that is resistant
> > to DoS attacks; protects infrastructure, etc.  In this
> > way:
> 
> You are right, but there are situations where security can be 
> provided, without adding additional functionality into the protocol.
> 
> For example, the security threats within a trusted administrative domain are
> different then the security threats in a inter-domain communication. Therefore, the
> security features required in these two situations are different.

Currently, the suggested text is:

	"Channel security between signaling entities MUST be implemented."

As one cannot implement or mandate use in a trusted admin domain,
I am not sure how to capture your concern.

If there exists certain deployment scenarios where interior nodes don't
have security associations, that is life.  However, I doubt the security
area will let us have a SHOULD for this requirement, as they have not
let other working groups do that.

John
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis