20 Jan
2016
20 Jan
'16
11:19 a.m.
On 20/01/16 17:04, Alex Balashov wrote:
On 01/20/2016 11:01 AM, Daniel-Constantin Mierla
wrote:
No need to send on mailing list, traces/sensitive data can be sent
directly - if there is a note on mailing list it was send, I will grab
it for anyone, this is something common done so far.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu
But you reminded me that I should highlight again
that private replies
to mailing discussions are unlikely to be followed, going in the common
folder (no longer filtered by mailing list rules), where I have a lot of
unsolicited emails and I don't check it often -- searching now the
[sr-users] prefix on subject shows couple of hundreds there, so if
anyone replied directly to me to a mailing list discussion without being
advised to do so and wants an answer, better resend to mailing list.
Yeah, I know. And I agree with you one hundred percent on the reasons
for why threads should be kept public consistently.
Sometimes there are packet captures with customer proprietary network
information or other topology information, however, and replacing with
fake values is not always easy. In some situations, the original
values can be integral to the problem. In those cases and in those
cases only, I may send something privately.
If you insist, I can post the CANCEL-200 OK exchange with proprietary
topology redacted.