[NSIS] Re: More IESG Review of draft-ietf-nsis-req-08.txt

--On Donnerstag, 26. Juni 2003 21:41 -0700 Allison Mankin <mankin@psg.com> 
wrote:

>
> Steve Bellovin also had comments on the NSIS Requirements draft:
>
>  Section 3 effectively rules out any requirement for security within a
>  domain.  I don't think that's right.
>

That's definitely not right. I assume you refer to point 5 of section 3:

   5. We can see the network at the level of domains/subdomains rather than 

   individual routers (except in the special case that the domain contains
   one link). Domains are assumed to be administrative entities, so 
security
   requirements apply to the signaling between them.

How about the following

   5. We can see the network at the level of domains/subdomains rather than 

   individual routers (except in the special case that the domain contains
   one link). Domains are assumed to be administrative entities. So 
security
   requirements might apply differently for the signaling between them and 

   within them.

>  In 5.7.8, confidentiality SHOULD be supported.  The ability to listen
>  to signaling channels is a major guide to what data channels are
>  interesting.

Is ok for me. The requirement changes then from

OLD:
   5.7.8 Confidentiality of signaling messages

   Based on the signaling information exchanged between nodes participating
   in the signaling protocol an adversary may learn both the identities and
   the content of the signaling messages. To prevent this from happening,
   confidentiality of the signaling message in a hop-by-hop manner MAY be
   provided. Note that the protection can be provided on a hop-by-hop basis
   for most message payloads since it is required that entities which
   actively participating in the signaling protocol must be able to read 
and
   eventually modify the content of the signaling messages.

to NEW:

   5.7.8 Confidentiality of signaling messages

   Based on the signaling information exchanged between nodes participating
   in the signaling protocol an adversary may learn both the identities and
   the content of the signaling messages. Since the ability to listen
   to signaling channels is a major guide to what data channels are
   interesting ones.

   To prevent this from happening, confidentiality of the signaling message
   in a hop-by-hop manner SHOULD be provided. Note that the protection can
   be provided on a hop-by-hop basis for most message payloads since it is
   required that entities which actively participating in the signaling
   protocol must be able to read and eventually modify the content of the
   signaling messages.

Objections?

Marcus

>
>
>
>
>
>

--------------------------------------
Dr. Marcus Brunner
Network Laboratories
NEC Europe Ltd.

E-Mail: brunner@ccrle.nec.de
WWW:    http://www.ccrle.nec.de/
Phone: +49 (0) 6221 905 11 29
Mobile: +49 (0) 163 275 17 43
personal home page: http://www.brubers.org/marcus

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

[NSIS] Re: More IESG Review of draft-ietf-nsis-req-08.txt - Comments 2