+The `RangeAssigner` is a `NetworkAssigner` implementation that provides automatic IP address assignment using the `RangeStore` for efficient bitmap-based tracking.
+
+## Overview
+
+The `RangeAssigner` integrates with the network management system to provide:
+
+- Automatic IP range initialization based on network CIDR blocks
+- Sequential IP address assignment within network ranges
+The `RangeAssigner` is fully integrated with the `NetworkStore` lifecycle:
+
+1. **Creation**: Range is automatically initialized when network is created
+2. **Updates**: Range configuration can be updated with network updates
+3. **Deletion**: Consider manually cleaning up ranges when networks are deleted
+
+## Best Practices
+
+### Range Naming
+- Use descriptive, unique names for ranges
+- Consider including network name: `"production-web-tier-range"`
+- Avoid special characters that might cause issues
+
+### IP Management
+- Always check return values from assignment operations
+- Implement proper cleanup when devices are removed
+- Monitor range utilization to prevent exhaustion
+
+### Configuration
+- Set appropriate `pool_size` limits for large networks
+- Use `reserve_gateway` for networks needing gateway addresses
+- Document configuration choices for operational clarity
+
+## Thread Safety
+
+The `RangeAssigner` uses the underlying `RangeStore` which provides thread-safe operations through `sled`'s transactional system. Multiple `RangeAssigner` instances can safely operate on the same range concurrently.
+
+## Performance Considerations
+
+- Assignment operations are O(n) in worst case, where n is the range size
+- Consider smaller subnet allocations for very large networks
+- Range lookups and unassignments are generally fast O(1) operations
+- Bitmap storage is memory-efficient even for large ranges