RIPv1 doesn't send the subnet information to the neighbors.
If the recieved network ID fits the address classes (Class A, Class B, or Class C), the default class-based subnet mask is assumed.
If the network ID does not fit the address class, then:
If the recieved network ID and the interface on which it is received belong to same CLASSFULL address, the subnet mask of the interface on which it was received is assumed.
If it doesn't fit the above the network ID is assumed to be a host route with the subnet mask /32.
I never used RIPv1 anywhere, so this was interesting to me to check.
Created a simple netwrok running RIPv1.
R1 <==> R2 (WAN link 10.11.12.0/30)
Originated the following routes from R1
0.0.0.0/0
192.168.0.0/16
10.11.12.0/24
10.11.13.0/24
10.20.13.0/24
11.11.13.0/24
R2's routing table explains the above mentioned rule.
lab@LAB-960-001:R2> show route protocol rip
Aug 09 12:24:39
inet.0: 8 destinations, 9 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
0.0.0.0/0 *[RIP/100] 00:14:59, metric 2, tag 0
> to 10.11.12.1 via xe-9/0/1.70
10.11.12.0/30 [RIP/100] 00:14:59, metric 2, tag 0
> to 10.11.12.1 via xe-9/0/1.70
10.11.13.0/30 *[RIP/100] 00:14:59, metric 2, tag 0
> to 10.11.12.1 via xe-9/0/1.70
10.20.13.0/30 *[RIP/100] 00:00:28, metric 2, tag 0
> to 10.11.12.1 via xe-9/0/1.70
11.11.13.0/32 *[RIP/100] 00:14:59, metric 2, tag 0
> to 10.11.12.1 via xe-9/0/1.70
192.168.0.0/24 *[RIP/100] 00:14:59, metric 2, tag 0
> to 10.11.12.1 via xe-9/0/1.70
224.0.0.9/32 *[RIP/100] 00:00:32, metric 1
MultiRecv
I hope this explains your question.