[Sip] Inquiry: Authentication in Reciever's Domain

Couret Tabt <courettabt@gmail.com> Sun, 17 January 2010 09:23 UTC

Return-Path: <courettabt@gmail.com>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC6863A6834 for <sip@core3.amsl.com>; Sun, 17 Jan 2010 01:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.955
X-Spam-Level:
X-Spam-Status: No, score=-0.955 tagged_above=-999 required=5 tests=[AWL=-1.644, BAYES_05=-1.11, J_CHICKENPOX_23=0.6, J_CHICKENPOX_32=0.6, J_CHICKENPOX_52=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JCL3XHm9rdTx for <sip@core3.amsl.com>; Sun, 17 Jan 2010 01:23:50 -0800 (PST)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id ED9443A680A for <Sip@ietf.org>; Sun, 17 Jan 2010 01:23:46 -0800 (PST)
Received: by fxm5 with SMTP id 5so1399030fxm.29 for <Sip@ietf.org>; Sun, 17 Jan 2010 01:23:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=xyq6eWYULAw2bb5RC6xOeZ9dj5UxfvF+a7+6mjrm1wI=; b=qnZpQ2VKPdO3MCQcQyGwSuE9Xb50r8yyI5JuvMtzIwAPdLUvGhzgAym9x7yOWPlkLV oAoXMB51E1+1VAr6E/2neHtbTAO91mpMGO4dlqMxggC2nZ8jX+LxLrtawPxXwmRiqjhg kX/vwXAqWP0Z3dLsi2FYDiG04iqhAc+oFEHBI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=RvAb7UhWmOCyGgwtfw2kPczNiQyH3etda7rV/eSxKKbMhcA0LHDj//lzu5oHHbLEQA RrFldK7gsvEG4yLiP/Yta+8c0i2VlAjJD9XpvUdp2sHcnsJ7QluJvtRkpeKxOSnREpJK PWd8Dyu+l/494Vv0/oCaXfi7rT0g4Ur87NhA0=
MIME-Version: 1.0
Received: by 10.239.169.145 with SMTP id o17mr521345hbe.50.1263720217615; Sun, 17 Jan 2010 01:23:37 -0800 (PST)
Date: Sun, 17 Jan 2010 18:23:37 +0900
Message-ID: <13bdfb281001170123p4883eb2bkb8955d52ceefc525@mail.gmail.com>
From: Couret Tabt <courettabt@gmail.com>
To: Sip@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Sip] Inquiry: Authentication in Reciever's Domain
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jan 2010 09:23:51 -0000

Dear folks,

I have a question about SIP Authentication Mechanism below:

In inter-domain (e.g.proxy-proxy) we can use RFC4474(SIP Identity)
 for user authentication, but, inside domain, how can a receiver
or a proxy in receiver side authenticate each other?

This means the followings:

CASE 1) Spoofing of Receiver:
After a Receiver's UA registered, without re-register
other user use the address that the former user registered.
(Then the former user is NOT unregistered by the proxy.)

Invite: Alice(in Atlanta) to Bob(in Biloxi)

Alice --->Atlanta--(RFC4474 Authentication)------>Biloxi---->Bob

             *But actually,

   this is spoofing user

               (NOT Bob)

CASE 2)Spoofing of Proxy:
In attacks like Man-in-the-Middle, barge-in user spoof Receiver side Proxy.

Alice --->Atlanta--(RFC4474 Authentication)------>Biloxi---->Bob

*But actually,

this is spoofing proxy

 (NOT Biloxi)


If you know it(how to authenticate), please let me know.

*I have studied about SIP more.
Is it appreciate that in this mailing list I have any above discussions?
Please let me know, too.

Thanks,
Tabt