diff --git a/gtfs-realtime/proto/gtfs-realtime.proto b/gtfs-realtime/proto/gtfs-realtime.proto
index d9e9ade4..01edabda 100644
--- a/gtfs-realtime/proto/gtfs-realtime.proto
+++ b/gtfs-realtime/proto/gtfs-realtime.proto
@@ -1198,10 +1198,6 @@ message ReplacementStop {
   // The replacement stop ID which will now be visited by the trip. May refer to a new stop added using a GTFS-RT Stop message, or to an existing stop defined in the GTFS-Static feed’s stops.txt. The stop MUST have location_type=0 (routable stops).
   optional string stop_id = 2;
 
-  // The amount of time difference between the scheduled arrival time and departure time. If not specified, the dwell time is assumed to be 0, and the arrival time and departure time will be the same.
-  // If specified, the arrival time of the replacement stop is defined as `reference_stop.departure_time + travel_time_to_stop` and departure time is defined as `reference_stop.departure_time + travel_time_to_stop + dwell_time`
-  optional uint32 dwell_time = 3;
-
   // The extensions namespace allows 3rd-party developers to extend the
   // GTFS Realtime Specification in order to add and evaluate new features and
   // modifications to the spec.
diff --git a/gtfs-realtime/spec/en/trip-modifications.md b/gtfs-realtime/spec/en/trip-modifications.md
index cf98227a..0f7fcd00 100644
--- a/gtfs-realtime/spec/en/trip-modifications.md
+++ b/gtfs-realtime/spec/en/trip-modifications.md
@@ -36,8 +36,6 @@ A `Modification` message describes changes to each affected trip starting at `st
 
 The sequence of `replacement_stops` may be of arbitrary length. For example, 3 stops could be replaced by 2, 4, or 0 stops as the situation may require. 
 
-It's allowed to replace a stop with a `ReplacementStop` that is the same as in the schedule if some other value are changing (like `dwell_time` `travel_time_to_stop`). 
-
 ![](images/trip_modification.png)
 
 _An example showing the effect of a modification on a particular trip. This modification may also be applied to several other trips._
@@ -52,7 +50,7 @@ Each `ReplacementStop` message defines a stop that will now be visited by the tr
 
 When `travel_time_to_stop` is specified, the `arrival_time` is calculated from a reference stop in the original trip, plus the offset in `travel_time_to_stop`. Otherwise, the `arrival_time` can be be interpolated based on the total duration of the modification in the original trip.
 
-The dwell time can be defined with the `dwell_time` field, and by default it's 0.
+The `departure_time` always equals the `arrival_time`.
 
 The optional fields of [`stop_times.txt`](https://github.com/google/transit/blob/master/gtfs/spec/en/reference.md#stop_timestxt) in the (CSV) GTFS specification are all set to their default values.