o User wants to get some simple action from remote device. Consider
garage door opener: it must authenticate user to open the door,
but it is not necessary for the user to authenticate the door
opener. In this case one-way authentication is sufficient.
In this example there is no harm if garage door opener
fills in its ID Payload - it need not be anonymous.
There is harm. An observer could figure out if it is me that's opening
the door, or my wife or my kids.
If the server (door) does not need it, don't send it.
Sorry, you missed the point. In this example user must sent
his identity and must authenticate to the door opener
(otherwise it will open the door to any stranger).
But door opener (responder) need not authenticate
itself to the user and may use NULL Auth. It is a reverse
situation to the first example in the draft, when
initiator uses NULL Auth.
What is the harm if door opener sends its unauthenticated identity to you?
And what will you do in this case? Reject connection?
But remember, that it was you who initiated this connection,
and moreover, you are already authenticated and
the action you requested (opening the door) has probably
already occured, so rejecting connection in this case
looks like stupid action.
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec
