text: Title: Is JWT in Authorization header a standard? 
  Body: Hi there,
  
  Great work on django-rest-framework-jwt so far. It is a perfect fit with DRF.
  I noticed that you are using JWT in your Authorization header, as in your example: 
  
  $ curl -H "Authorization: JWT <your_token>" http://localhost:8000/protected-url/
  
  Is it the recommended way in the current JWT draft? Other server side token framework often accept Bearer instead of JWT, which I think is very common. The reason I am asking because satellizer (an oauth2 token based javascript library for angularjs) does not work with your django-rest-framework-jwt.
  I suspect because of the JWT text in the Authorization header. Could you please have a look? 
  