Re: [sipcore] Comments on draft-ietf-sipcore-status-unwanted-01 - related draft - https://tools.ietf.org/html/draft-avasarala-sipping-reason-header-dynamic-icb-00

Hi
Sometime I had submitted an I-D based on a similar idea - to block a
particular caller either temporarily or permanently -
https://tools.ietf.org/html/draft-avasarala-sipping-reason-header-dynamic-icb-00

Here the SIP Reason header would be appended to the BYE request.

Now using 666 response code - is the block permanent or time based?

Regards
Ranjit

On Wed, Jan 4, 2017 at 4:35 PM, <marianne.mohali@orange.com> wrote:

> Hi,
>
> I have the following comments on v01:
>
> -Section 4 - 4rd paragraph:
>         The actions described here do not depend on the nature of the SIP
>         URI, e.g., whether it describes a telephone number or not
> but in the rest of the document only telephone numbers are mentioned. It
> would be good to reflect this by using "telephone number or address"?
>
> -Section 4 - last paragraph:
>         We define a SIP feature-capability [RFC6809], sip.666, that allows
>         the registrar to indicate that the corresponding proxy supports
> this
>         particular response code.
> I would suggest: "This document defines a new SIP feature-capability
> indicator [RFC6809] value, sip.666, that ...
>
> -Section 4 general:
> IMO, it would be good to have a paragraph addressing the question of the
> "calling party number" (mentioned several time in the document): indeed,
> this calling party number can be identified by the telephone number/address
> in the From header or the one in the P-Asserted-Identity header that may be
> different. Depending on the one displayed to the called UA, the 666 could
> concern only one or both addresses depending on service provider choices.
> If we take the example of a call-center or an IPBX having the head number
> and a range of private numbers, the service provider could interpret the
> 666 from the called user only for the private number (in the From header)
> or for the whole pool (P-Asserted-Identity). I suggest to have a paragraph
> to highlight this point.
>
> -Section 6:
> calling party number / calling party address
>
>
> Best regards,
> Marianne
>
>
> ____________________________________________________________
> _____________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>