Re: [secdir] Security review of draft-shore-icmp-aup-06

[Hilarie Orman <[e-mail]>]

That'll do.

Hilarie

----- Original Message -----
From: Carlos Pignataro (cpignata) <[e-mail]>
To: Melinda Shore <[e-mail]>, Hilarie Orman <[e-mail]>
Cc: <[e-mail]> <[e-mail]>, The IESG <[e-mail]>, [e-mail]
Sent: Wed, 13 Nov 2013 17:42:15 -0700 (MST)
Subject: Re: Security review of draft-shore-icmp-aup-06

Thanks, Hilarie,

How's this updated Security Considerations?

5.  Security considerations

   This document attempts to describe a high-level policy for adding
   ICMP types and codes.  While special attention must be paid to the
   security implications of any particular new ICMP type or code, this
   recommendation presents no new security considerations.

   From a security perspective, ICMP plays a part in the Photuris
   protocol.  But more generally, ICMP is not a secure protocol, and
   does not include features to be used to discover network security
   parameters or to report on network security anomalies in the
   forwarding plane.


Thanks,

-- Carlos.

On Nov 13, 2013, at 3:18 AM, Melinda Shore <[e-mail]> wrote:

> On 11/12/13 10:43 PM, Hilarie Orman wrote:
>> While there are ostensibly no new security considerations, it is
>> worthwhile noting that ICMP plays a part in the Photuris protocol and
>> was also used in SKIP (though that usage is deprecated).  In general,
>> I have some concern about using ICMP to discover network security
>> parameters or to report on network security anomalies in the
>> forwarding plane.
> 
> I hadn't been aware of its use in Photuris.  We'll get some
> text in there mentioning that, as well as some discussion of
> the problems you've mentioned with regard to reporting of
> security parameters/anomalies.  And now that you mention it
> that's actually a more general security problem.
> 
> Melinda
> 
> 
> -- 
> Melinda Shore
> No Mountain Software
> [e-mail]
> 
> "Software longa, hardware brevis."