IETF Logo Mail Archive

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

Melinda Shore <mshore@cisco.com> Tue, 17 June 2003 13:41 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 JAA15449 for <nsis-archive@odin.ietf.org>; Tue, 17 Jun 2003 09:41:26 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5HDexw29455 for nsis-archive@odin.ietf.org; Tue, 17 Jun 2003 09:40:59 -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 h5HBf3a20307; Tue, 17 Jun 2003 07:41:03 -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 h5HBeWm20295 for <nsis@optimus.ietf.org>; Tue, 17 Jun 2003 07:40:32 -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 HAA07760 for <nsis@ietf.org>; Tue, 17 Jun 2003 07:40:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SEn0-00056J-00 for nsis@ietf.org; Tue, 17 Jun 2003 07:38:14 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138]) by ietf-mx with esmtp (Exim 4.12) id 19SEmz-000561-00 for nsis@ietf.org; Tue, 17 Jun 2003 07:38:13 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h5HBdU6p029502; Tue, 17 Jun 2003 04:39:31 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR) with ESMTP id AIL78197; Tue, 17 Jun 2003 04:39:30 -0700 (PDT)
Message-Id: <200306171139.AIL78197@mira-sjc5-c.cisco.com>
To: Georgios Karagiannis <karagian@cs.utwente.nl>
cc: nsis@ietf.org, "Attila Bader (ETH)" <Attila.Bader@eth.ericsson.se>
From: Melinda Shore <mshore@cisco.com>
Subject: Re: [NSIS] AD Review comments on draft-ietf-nsis-req-07.txt
In-Reply-To: Message from karagian@cs.utwente.nl of "Tue, 17 Jun 2003 10:18:49 +0200." <002e01c334a9$14c5f1a0$4c0d5982@dynamic.cs.utwente.nl>
Date: Tue, 17 Jun 2003 07:39:29 -0400
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>

> It depends where the hop-by hop security is implemented.
> For example in one administrative domain (with trust
> relashionships between NSIS peers) hop-by-hop security
> must be implemented on the NSIS edge nodes, without
> requiring that hop-by-hop security is implemented in the
> NSIS interior nodes.

That's optional-to-use, not optional-to-implement.

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

v2.23.0 | Report a Bug | By Email