Re: [Sip] WGLC: draft-ietf-sip-consent-framework-00

[Dean Willis <dean.willis at softarmor.com>]

jbemmel at zonnet.nl wrote:
> Major technical comment on section 5.8: the proposed Trigger-Consent 
> mechanism looks like one big hack to me. It does not comply with 
> RFC3515, and appears to be an inappropriate use of REFER. Suggestion: 
> use SUBSCRIBE / NOTIFY
>
> Technical comment on Trigger-Consent: the ABNF in section 5.11 allows 
> multiple instances of this header. Is this desired? If so, a note on 
> what should be done when multiple instances are present is needed. If 
> not, the ABNF should be adapted ( I suspect the latter is the 
> appropriate choice )
>
> Minor technical comment on Figure 5 and the example in 5.11: the 
> escaping of the Refer-To URI is invalid, '<' and '>' should be %-encoded 
> too (but: see first comment, suggest to remove this Refer-To header 
> entirely)

Ok, good comments. Anybody else read this draft?

I'm worried that we're not really getting the needed level of review 
here. Suggestions?

--
Dean

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