Re: [Sip] draft-jennings-sip-hashcash-01

On 3/2/05 2:15 AM, "Jonathan Rosenberg" <jdrosen@cisco.com> wrote:

> 1. The mechanism interacts badly with forking at the moment. One problem
> is HERFP. If I have a mix of endpoints, some of which support this (and
> thus send a 419), and others that don't (and thus ring the phone), then
> you'll end up always completing the call on the endpoints that don't
> support the extension.

Good point. I think will mention this in the draft but clearly I won't
attempt to solve the well studied HERFP problem. As a separate issues, some
day the WG should discuss the limitations of the "If it hurts don't do it"
solution to the HERFP problem.

> 
> 2. THe mechanism doesn't provide a way for a proxy to aggregate multiple
> Puzzle headers from forked branches. It needs to do something like
> WWW-Authenticate where a proxy collects these from the various 419 and
> places all of them in the 419 forwarded upstream. That will also require
> something akin to realm, that allows a UA/proxy to pull out its own puzzle.

Oops. Excellent point. Thanks, will fix this. 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip