I'd call this `max_norm`. Also there's no reason for this not to be able to encapsulate both a max and a min constraint at once, but this pull request has dragged on for long enough. 

For now I'd just change this to `max_norm` and get rid of the `is_max_constraint` and associated logic. We can add a `min_norm` argument in a subsequent pull request.