Re: [P2PSIP] draft-ietf-p2psip-base publication to be requested

Diego Suarez <loopp2psip@gmail.com> Thu, 09 June 2011 14:44 UTC

Return-Path: <loopp2psip@gmail.com>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04AFA21F8482 for <p2psip@ietfa.amsl.com>; Thu, 9 Jun 2011 07:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ta+ewlgmkH7F for <p2psip@ietfa.amsl.com>; Thu, 9 Jun 2011 07:44:24 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 26F1421F847C for <p2psip@ietf.org>; Thu, 9 Jun 2011 07:44:23 -0700 (PDT)
Received: by wyb29 with SMTP id 29so1331523wyb.31 for <p2psip@ietf.org>; Thu, 09 Jun 2011 07:44:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:cc:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=E9RyZYUILTpdFqJFxdqHaPNCID7/uW3KjSwdGIvfJcQ=; b=wpkjiZwBgrheRpIZWlQEsczlXmjPpugxjRS2XoHdMySnOhq9ZFZnUV7n1prevuiWen vjjNUwMTe7l89ZekH4F0hbQfMsrYK7eW6pY/a1dBoZrK93SQ3qWDZGokTglkNCJSYUwI 8ZbIUt1LWVLqCmyo4FD8HXpsK4ialfJ63U9pg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=cQiHtrjYk4SX7P+YCSMiHD6ZN1ZB0qzXDfAjJOVhF4D1eD+R8aPp1SO8EHvHp3jOM3 b9zaUkvhZQ4sirYZYsgvSLbJRhNwBIt7NFMV+tE0+WKj1U1eXhxdT33NgK5aSriVDwho FjGtAV2otrXAEcnHajJ5P3d22M0yQ5tQtXCko=
Received: by 10.227.200.210 with SMTP id ex18mr937286wbb.7.1307630658612; Thu, 09 Jun 2011 07:44:18 -0700 (PDT)
Received: from [163.117.205.20] ([163.117.205.20]) by mx.google.com with ESMTPS id c17sm1278963wbh.12.2011.06.09.07.44.13 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Jun 2011 07:44:14 -0700 (PDT)
From: Diego Suarez <loopp2psip@gmail.com>
To: "David A. Bryan" <dbryan@ethernot.org>
In-Reply-To: <BANLkTikuy8qpZ42Zod1YK2+iYv1ib6=Yag@mail.gmail.com>
References: <BANLkTikuy8qpZ42Zod1YK2+iYv1ib6=Yag@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 09 Jun 2011 16:31:18 +0200
Message-ID: <1307629878.30919.87.camel@toedo>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3
Content-Transfer-Encoding: 8bit
Cc: P2PSIP WG <p2psip@ietf.org>, draft-ietf-p2psip-base@tools.ietf.org
Subject: Re: [P2PSIP] draft-ietf-p2psip-base publication to be requested
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 14:44:25 -0000

Hi, 

I had in mind writing a draft about this, but since I'm running out of
time, I would like to summarize a new certification model for P2PSIP I
have been working on, in case it is of interest for the group.
Further details can be found in paper:

D. Touceda, J. Camara, L. Villalba, and J. Marquez, “Advantages of
identity certificate segregation in P2PSIP systems,” Communications,
IET, vol. 5, pp. 879–889, Apr. 2011.


The idea is to split the certification of users and devices. Devices are
identified by PKCs including a nodeID and the PK of the device, while
users are identified by PKCs including a username and the PK of the
user. Similar models have been used before in other communications
systems, such as GSM where devices and users are separately represented
by the international mobile equipment identity (IMEI) stored in the
phones and the international mobile subscriber identity (IMSI) stored in
the user subscriber identity module (SIM), respectively.

Motivations of this model are:

- Users and devices are different entities performing different
roles within a P2PSIP system. Devices are nodes of the P2P
overlay network (represented by a nodeID) that offer services
(to route messages, to store data, . . .) to the system, while
users (represented by an username) utilize these services,
usually to establish media communications using SIP.

- Support for mobility scenarios where a user may be logged at different
devices at the same time using the same PKC.

- Support several users to be logged in the same device (like a fixed
phone) at the same time.

- Support for user independent hard-coded devices.

- Interoperability with SIP. SIP certificates are not valid in actual
P2PSIP since they don't include a nodeID.

cheers

Diego Suárez


On Wed, 2011-06-08 at 09:48 -0700, David A. Bryan wrote:
> Unless something major comes up, we plan to request the newest version
> of the base draft, draft-ietf-p2psip-base-15, be published. I'll put
> in the request in a week (June 16th or 17th). If there are any further
> comments from the last call a while ago (or further comments on the
> comments since then), please send them to the list ASAP.
> 
> Thanks,
> 
> David (as chair)
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www.ietf.org/mailman/listinfo/p2psip