D109 Security Considerations

From: Jari Arkko
Subject: [Mobike] design draft issue: security considerations
Date: Wed, 21 Dec 2005 12:54:13 +0200

| 7.  Security Considerations


This section seems weak compared to the one in
the protocol draft. Consider simply referring to the
protocol spec unless there is some new information
(e.g. design decisions not covered in the protocol
spec).

From: Tero Kivinen
Subject: [Mobike]  D109 design draft issue: security considerations
Date: Tue, 3 Jan 2006 19:12:49 +0200

Jari Arkko writes:
| | 7.  Security Considerations
| 
| This section seems weak compared to the one in
| the protocol draft. Consider simply referring to the
| protocol spec unless there is some new information
| (e.g. design decisions not covered in the protocol
| spec).

As we do not really define protocol here, there is not that much of
real security considerations. The current security considerations
lists the generic problems against all protocols of this type.

I am not sure adding pointer to the protocol document helps that much,
as I assume people will read the protocol document anyways, but
perhaps adding text "See Security considerations section of <xref
target="I-D.ietf-mobike-protocol"/> for more information about
security considerations of the actual protocol." helps. 

From: Jari Arkko
Subject: Re: [Mobike] D109 design draft issue: security considerations
Date: Thu, 26 Jan 2006 15:52:38 +0200

Yes. Maybe you could also cut the paragraph about
ICMP (since it isn't complete).