[shim6] [Fwd: [Int-area] Name based sockets]

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 02 August 2010 04:10 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC9933A6A01 for <shim6@core3.amsl.com>; Sun, 1 Aug 2010 21:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.912
X-Spam-Level:
X-Spam-Status: No, score=-2.912 tagged_above=-999 required=5 tests=[AWL=-0.313, BAYES_00=-2.599]
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 cpw9vU4nkCAS for <shim6@core3.amsl.com>; Sun, 1 Aug 2010 21:10:20 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 08FEA3A6A9D for <shim6@ietf.org>; Sun, 1 Aug 2010 21:10:19 -0700 (PDT)
Received: by gyg8 with SMTP id 8so1370033gyg.31 for <shim6@ietf.org>; Sun, 01 Aug 2010 21:10:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:content-type :content-transfer-encoding; bh=SgArkXkF//oJgUYcvc5ndZ4iNzOB70JR6BN+5LKUbqg=; b=nG3kxOzIdsbPzfax0JG97l4vqg7vhjoBttx055f7gN169x59Ta8ToNcQ8GCGMIESil n4TVGjojcL0mbiEg1PVYINmzi0aZEk2PAA2OvMXyMC7hI9A7TYeOBHa3uJbab4SWzJJJ w6tBdtkewD+cyrZAuuekUt6kyT3S07MPk5Z7U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:content-type:content-transfer-encoding; b=Fkthw1+L89ArDSUjGmfdDb18K6N0xtoPnUs0BAUuGxROI0UtMDs48DYLjmUNpPCgN+ kVCzjwXLM/m/L03gxY9RvB0sQqwMq4BzAN+kWGl1u/bSJhabVZ/qyT73a0cL60CXjwWR CAxhVo8z+dPOHSlrsJk6yzdUh/+aNa2yFZXCg=
Received: by 10.151.150.2 with SMTP id c2mr1860817ybo.404.1280722247052; Sun, 01 Aug 2010 21:10:47 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id q3sm4943309ybe.14.2010.08.01.21.10.45 (version=SSLv3 cipher=RC4-MD5); Sun, 01 Aug 2010 21:10:46 -0700 (PDT)
Message-ID: <4C564543.6040509@gmail.com>
Date: Mon, 02 Aug 2010 16:10:43 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: shim6@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [shim6] [Fwd: [Int-area] Name based sockets]
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2010 04:10:22 -0000

Since this proposal includes major changes to SHIM6
and REAP, I wonder if people here have looked at it?

    Brian

-------- Original Message --------
Subject: [Int-area] Name based sockets
Date: Mon, 26 Jul 2010 19:47:08 +0200
From: Javier Ubillos <jav@sics.se>
To: Internet Area Mailing List <int-area@ietf.org>

Name Based Sockets
Draft: http://www.ietf.org/id/draft-ubillos-name-based-sockets-01.txt
Presentation:
http://www.sics.se/~jav/ietf78/namebasedsockets-IETF78-apps.pdf

Consider it a real "request for comments", because I do want comments.

Please note, that we inpractice presented two distinct things.
A. Name based sockets.
B. An improvement to shim6 (which is only possible using names)

I'll try to briefly address some of the questions I remmember:

* There are already solutions for all these problems
Yes, they are, and we want to help to deploy all those cool things.

* We should not require changes to applications
I'm not convinced, however, there are already several solutions that do
do this with surrogate/pseudo IPs.
Actually, nothing says that we couldn't do both.
Name based sockets is just an API to pre-existing cool solutions.

* What is a name?
My spontaneous answer is that a name is eiter just a session identifier,
or that it both that and an identifier for a particular ... something.


That's all I remmember offhand...

// Javier