Hi Brian:
Brian E Carpenter wrote:
On 2007-12-04 08:05, Miguel Garcia wrote:
...
Comments:
Section 4 (but this also affects other sections):
... URI-list servers can use URIs
tagged with the 'anonymize' attribute for routing SIP requests, but
MUST convert them to an anonymized URI (such as
sip:[EMAIL PROTECTED]) in recipient-history lists. I
think that to be watertight, the anonymous URI should be
well-defined, i.e. not 'such as' but simply 'MUST be
sip:[EMAIL PROTECTED]'.
Essentially, RFC 3261 allows to have any .invalid TLD as an anonymous
URI, so, I don't think we need to have further restrictions on that.
However, by leaving it open you make the job of a person writing code
to interpret this URI very much harder. If you specify the exact string,
it becomes trivial to check for it. I think it should be specified.
Point taken. I'll add it to the next version of the draft.
/Miguel
--
Miguel A. Garcia tel:+358-50-4804586
Nokia Siemens Networks Espoo, Finland
_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art
