IETF Logo Mail Archive

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

"Georgios Karagiannis" <karagian@cs.utwente.nl> Tue, 17 June 2003 11:17 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 HAA07036 for <nsis-archive@odin.ietf.org>; Tue, 17 Jun 2003 07:17:11 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5HBGgx18514 for nsis-archive@odin.ietf.org; Tue, 17 Jun 2003 07:16:42 -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 h5H8J2a04913; Tue, 17 Jun 2003 04:19:02 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H8Ivm04902 for <nsis@optimus.ietf.org>; Tue, 17 Jun 2003 04:18: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 EAA03538 for <nsis@ietf.org>; Tue, 17 Jun 2003 04:18:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SBdw-00042y-00 for nsis@ietf.org; Tue, 17 Jun 2003 04:16:40 -0400
Received: from utrhcs.cs.utwente.nl ([130.89.10.247]) by ietf-mx with esmtp (Exim 4.12) id 19SBdv-00042v-00 for nsis@ietf.org; Tue, 17 Jun 2003 04:16:39 -0400
Received: from utip105 (utip105.cs.utwente.nl [130.89.13.76]) by utrhcs.cs.utwente.nl (8.12.9/8.12.9) with SMTP id h5H8ImCf009806; Tue, 17 Jun 2003 10:18:48 +0200 (MET DST)
Message-ID: <002e01c334a9$14c5f1a0$4c0d5982@dynamic.cs.utwente.nl>
From: Georgios Karagiannis <karagian@cs.utwente.nl>
To: Melinda Shore <mshore@cisco.com>
Cc: nsis@ietf.org, "Attila Bader (ETH)" <Attila.Bader@eth.ericsson.se>
References: <200306162131.AIL17276@mira-sjc5-c.cisco.com>
Subject: Re: [NSIS] AD Review comments on draft-ietf-nsis-req-07.txt
Date: Tue, 17 Jun 2003 10:18:49 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
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: 7bit

Hi Melinda

> For practical purposes, if hop-by-hop security is a
> must-implement, then failing to do so results in a
> non-interoperable implementation.  If hop-by-hop security is
> a should-implement, then failing to do so does not result in
> a non-interoperable implementation.

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.

Best Regards,
Georgios



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

v2.23.0 | Report a Bug | By Email