IETF Logo Mail Archive

[sipcore] Comment on https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-spam/?include_text=1

Samir Srivastava <srivastava_samir@hush.com> Thu, 21 May 2020 17:11 UTC

Return-Path: <srivastava_samir@hush.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400F03A0A19 for <sipcore@ietfa.amsl.com>; Thu, 21 May 2020 10:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hush.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WaViLjyKAWJI for <sipcore@ietfa.amsl.com>; Thu, 21 May 2020 10:11:45 -0700 (PDT)
Received: from smtp1.hushmail.com (smtp1.hushmail.com [65.39.178.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 230B33A09DB for <sipcore@ietf.org>; Thu, 21 May 2020 10:11:44 -0700 (PDT)
Received: from smtp1.hushmail.com (localhost [127.0.0.1]) by smtp1.hushmail.com (Postfix) with SMTP id 7A8E2404F8 for <sipcore@ietf.org>; Thu, 21 May 2020 17:11:44 +0000 (UTC)
X-hush-tls-connected: 1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=hush.com; h=date:to:subject:from; s=hush; bh=FRN6m8wJNRaCHRDvlXGhpZDPNHA7PT0962W5ICvnKSM=; b=Y1dcsH90rwUTM9pmr5x4kRxVjG50ySC1HtigjKhHJv5gN8di57MciEKXjAPoh9DBJeFVdoTdPPDdfO8COGulvTJHZ3VBK0oSDtWCmI9+BOPkg2UU0ZzXISRNhMfI75/gmu/SudeP2p57tugV4dls+r2+t7qGObl+wuU9zc96YaaLUl40FOQKPTQ0HiTQE2GGNEMLV21LizLNqJeEkA4rdcvw2qu8qrSAzNmRO7qzY1qh7K1AEus/+lpKH6DV3jmfibzqndRW8sLBMD5Biuhij/3kScwaRr+1bCg4HcmwhWMuNvVUqhm6iofl8x79Byp6LSML9pyEKanbhv82u412fw==
Received: from smtp.hushmail.com (w2.hushmail.com [65.39.178.46]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp1.hushmail.com (Postfix) with ESMTPS; Thu, 21 May 2020 17:11:43 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99) id AF1F9E0793; Thu, 21 May 2020 17:11:43 +0000 (UTC)
MIME-Version: 1.0
Date: Thu, 21 May 2020 23:11:43 +0600
To: sipcore@ietf.org, hgs@cs.columbia.edu
From: Samir Srivastava <srivastava_samir@hush.com>
References: <20200510131235.8E2A6C0171@smtp.hushmail.com> <854d7cef-03eb-8974-9159-c493df015996@alum.mit.edu> <8414733e-a5d9-2502-6a89-d6460d931be9@ntlworld.com> <20200511153943.792F620111@smtp.hushmail.com> <32547453-1350-b8a2-d7a5-fc253cf3eaf4@ntlworld.com> <20200512105430.7F9542011C@smtp.hushmail.com> <c12508c3-11c2-aa14-28c6-ecfea4b73bd5@ntlworld.com>
Content-Type: multipart/alternative; boundary="=_03acecc46ae6a3861220ebef60ffc86b"
Message-Id: <20200521171143.AF1F9E0793@smtp.hushmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/mIKbYJTE79SX2c66e9roZjgDErA>
Subject: [sipcore] Comment on https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-spam/?include_text=1
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 May 2020 17:11:47 -0000

Hi,
  Chapter 9, Para 3 states
	   Thus, a UAS SHOULD NOT trust the information in the "Call-Info"   
header field unless the SIP session between the entity inserting the  
 header field and the UAS is protected by TLS [RFC8446].
  What about protection from DTLS? There may be hops which may be
protected by IPSEC tunnel.
  BTW how many deployments of SIPS, we have??  We need to modify the
statement.
ThanksSamir Srivastava
https://samirsrivastava.typepad.com       -    End of Unfairness

v2.23.0 | Report a Bug | By Email