
From vijay@gatech.edu  Mon Jun  1 20:10:21 2009
Return-Path: <vijay@gatech.edu>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BF633A69BD for <rrg@core3.amsl.com>; Mon,  1 Jun 2009 20:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 XrgJWg2L+fEB for <rrg@core3.amsl.com>; Mon,  1 Jun 2009 20:10:21 -0700 (PDT)
Received: from deliverator6.ecc.gatech.edu (deliverator6.ecc.gatech.edu [130.207.185.176]) by core3.amsl.com (Postfix) with ESMTP id D23143A6D24 for <rrg@irtf.org>; Mon,  1 Jun 2009 20:09:20 -0700 (PDT)
Received: from deliverator6.ecc.gatech.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7DC7320C121 for <rrg@irtf.org>; Mon,  1 Jun 2009 23:09:20 -0400 (EDT)
Received: from mail6.gatech.edu (bigip.ecc.gatech.edu [130.207.185.140]) by deliverator6.ecc.gatech.edu (Postfix) with ESMTP id 0EE0320C087 for <rrg@irtf.org>; Mon,  1 Jun 2009 23:09:20 -0400 (EDT)
Received: from mail6.gatech.edu (localhost [127.0.0.1]) by mail6.gatech.edu (Postfix) with ESMTP id 02F5A2259F5 for <rrg@irtf.org>; Mon,  1 Jun 2009 23:09:20 -0400 (EDT)
Date: Mon, 1 Jun 2009 23:09:19 -0400 (EDT)
From: "Balasubramaniyan, Vijay A" <vijay@gatech.edu>
To: rrg@irtf.org
Message-ID: <1441829858.2853671243912159980.JavaMail.root@mail6.gatech.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [130.207.185.163]
X-Mailer: Zimbra 5.0.16_GA_2921.RHEL5_64 (ZimbraWebClient - FF3.0 (Linux)/5.0.16_GA_2921.RHEL5_64)
Subject: [rrg] Final CFP NPSec 2009, Abstract Submission Deadline June 8th, 2009
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2009 03:10:21 -0000

[Apologies if you receive multiple copies of this CFP]

Submission deadline is 1 week away.

                              CALL FOR PAPERS (Final)
                                NPSec 2009
                 5th Workshop on Secure Network Protocols
                      In conjunction with ICNP 2009
                             October 13, 2009
                        Princeton, New Jersey, USA
                   http://www.gtisc.gatech.edu/npsec09/

Scope:
The 5th workshop on Secure Network Protocols (NPSec) is a one-day event
held in conjunction with with the 17th IEEE International Conference on
Network Protocols (ICNP 2009). NPSec focuses on two general areas.  
The first focus is on the development and analysis of secure or hardened
protocols for the operation (establishment and maintenance) of network
infrastructure, including such targets as secure multidomain, ad hoc, sensor
or overlay networks, or other related target areas.  This can include new
protocols, enhancements to existing protocols, protocol analysis, and new
attacks on existing protocols.  The second focus is on employing such secure
network protocols to create or enhance network applications. Examples include
collaborative firewalls, incentive strategies for multiparty networks, and
deployment strategies to enable secure applications.  

NPSec 2009 particularly welcomes new ideas on security in the context of
future Internet design, such as architectural considerations for future
Internet security and new primitives for supporting secure network protocol
and application design.  

Topics of interest include but are not limited to:
1. security in future Internet architectures
 - role of security in future architectures
 - integrating security into future protocols and applications
2. secure and/or resilient network protocols, e.g.:
- internetworking/routing
- MANETs
- LANs and WLANs
- mobile/cellular data networks
- p2p and other overlay networks
- federated trust systems
- sensor networks
3. vulnerabilities of existing protocols and applications (both theoretical and case studies), including attacks
4. key distribution/management
5. intrusion detection and response
6. incentive systems for p2p systems and MANETs routing
7. secure protocol configuration and deployment


Important Dates:
Abstract submission: June 8, 2009
Paper submission: June 15, 2009
Notification of acceptance: July 15, 2009
Camera ready version: August 5, 2009


NPSEC Steering Committee:
Sonia Fahmy, Purdue University (chair)
George Kesidis, Penn State University
Cristina Nita-Rotaru, Purdue University
Gene Tsudik, UC Irvine


Program Co-Chairs:
Jelena Mirkovic, USC/ISI
Xiaowei Yang, Duke University


Web and Proceedings Chair:
Vijay A. Balasubramaniyan, Georgia Tech.


Technical Program Committee:
Daniel Massey, Colorado State University
Jun Li, University of Oregon
Peter Reiher, UCLA
Beichuan Zhang, University of Arizona
Young Cho, USC/ISI
Mukesh Singhal, University of Kentucky
Minseok Kwon, Rochester Institute of Technology
Lan Wang, University of Memphis
Y. Charlie Hu, Purdue University
Minaxi Gupta, Indiana University
Dan Pei, AT\&T Research
Bogdan Carbunar, Motorola Research
Ted Faber, USC/ISI
Jia Wang, AT\&T Research
Landon Cox, Duke University
Jean-Pierre Hubaux, EPFL
Stephan Bohacek, University of Delaware
Reza Curtmola, New Jersey Institute of Technology
Brent Kang, University of North Carolina
Bryan Ford, Max Planck Institute for Software Systems

From irtf@tonistoev.info  Sun Jun  7 18:49:28 2009
Return-Path: <irtf@tonistoev.info>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D79013A688C for <rrg@core3.amsl.com>; Sun,  7 Jun 2009 18:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 vLg1efbzuIeU for <rrg@core3.amsl.com>; Sun,  7 Jun 2009 18:49:28 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 04C1D3A6889 for <rrg@irtf.org>; Sun,  7 Jun 2009 18:49:27 -0700 (PDT)
Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <irtf@tonistoev.info>) id 1MDTzL-0003x8-Mx for rrg@irtf.org; Mon, 08 Jun 2009 04:49:27 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Mon, 8 Jun 2009 04:49:27 +0300
User-Agent: KMail/1.9.9
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200906080449.27707.irtf@tonistoev.info>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - chi.r1servers.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - tonistoev.info
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [rrg] Reminder
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jun 2009 01:49:29 -0000

Dear fellow (re)searchers,

I like to remind you of the following:
Naming node, not interface, with locator and separating inter-domain from intra-domain routing are both together the premises for reaching the design goal of significantly improved routing scalability.

Toni

From jmh@joelhalpern.com  Sun Jun  7 18:57:48 2009
Return-Path: <jmh@joelhalpern.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F12E53A6B5E for <rrg@core3.amsl.com>; Sun,  7 Jun 2009 18:57:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.684
X-Spam-Level: 
X-Spam-Status: No, score=-3.684 tagged_above=-999 required=5 tests=[AWL=-0.085, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 dDii9N6M-1I3 for <rrg@core3.amsl.com>; Sun,  7 Jun 2009 18:57:48 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 593163A6834 for <rrg@irtf.org>; Sun,  7 Jun 2009 18:57:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 588B5430523; Sun,  7 Jun 2009 18:57:53 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-52-172.clppva.btas.verizon.net [71.161.52.172]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id C79DF430519; Sun,  7 Jun 2009 18:57:52 -0700 (PDT)
Message-ID: <4A2C701D.1060000@joelhalpern.com>
Date: Sun, 07 Jun 2009 21:57:49 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Toni Stoev <irtf@tonistoev.info>
References: <200906080449.27707.irtf@tonistoev.info>
In-Reply-To: <200906080449.27707.irtf@tonistoev.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IRTF RRG <rrg@irtf.org>
Subject: Re: [rrg] Reminder
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jun 2009 01:57:49 -0000

No Toni.  Those two ideas are neither "the" nor "premise" for the work 
of the RRG.  They are ideas that we are looking at that, in some peoples 
judgment, for some architectural directions, are likely to be helpful.

Joel

Toni Stoev wrote:
> Dear fellow (re)searchers,
> 
> I like to remind you of the following:
> Naming node, not interface, with locator and separating inter-domain from intra-domain routing are both together the premises for reaching the design goal of significantly improved routing scalability.
> 
> Toni
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
> 

From dino@cisco.com  Mon Jun  8 14:54:25 2009
Return-Path: <dino@cisco.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC2D13A687C for <rrg@core3.amsl.com>; Mon,  8 Jun 2009 14:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.164
X-Spam-Level: 
X-Spam-Status: No, score=-6.164 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
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 4YLLpgZRUpbc for <rrg@core3.amsl.com>; Mon,  8 Jun 2009 14:54:25 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 42B833A63CB for <rrg@irtf.org>; Mon,  8 Jun 2009 14:54:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,326,1241395200"; d="scan'208";a="319300502"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 08 Jun 2009 21:54:30 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n58LsUSa027438 for <rrg@irtf.org>; Mon, 8 Jun 2009 14:54:30 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n58LsUtB003443 for <rrg@irtf.org>; Mon, 8 Jun 2009 21:54:30 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 8 Jun 2009 14:54:29 -0700
Received: from [192.168.1.2] ([10.21.66.70]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 8 Jun 2009 14:54:29 -0700
Message-Id: <6AEBBEF7-0EC7-4970-938A-D36C34F7C1DE@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: RRG RG <rrg@irtf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 8 Jun 2009 14:54:29 -0700
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 08 Jun 2009 21:54:29.0399 (UTC) FILETIME=[B2BEFA70:01C9E883]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=60; t=1244498070; x=1245362070; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Any=20idea=20when=20RRG=20is=20going=20to=20mee t=20in=20Stockholm? |Sender:=20; bh=iSez6vC30JfpZVSUNXK0dyvTW9lmJvE+WVwJSpa57XA=; b=FxEFtIOOK50NtjOEJ3tefz+1Nse+uiu+yTCxU+/94EM0Pn+EnoI4yKwqYy o2rgyxLtIrBie9Q7S71Wh1o0I5cwKaEH/rSOgAhwXUWtR9JpUqV5vMs78s/S fjbiaueEkG;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Subject: [rrg] Any idea when RRG is going to meet in Stockholm?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jun 2009 21:54:26 -0000

Will it be the usual 9:00-5:00 on Friday?

Thanks,
Dino

From tony.li@tony.li  Mon Jun  8 20:24:46 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17B113A682E for <rrg@core3.amsl.com>; Mon,  8 Jun 2009 20:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.729
X-Spam-Level: 
X-Spam-Status: No, score=-1.729 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_MLH_Stock1=0.87]
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 MtVQqr2wuJa3 for <rrg@core3.amsl.com>; Mon,  8 Jun 2009 20:24:45 -0700 (PDT)
Received: from QMTA13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by core3.amsl.com (Postfix) with ESMTP id 3DD833A68A8 for <rrg@irtf.org>; Mon,  8 Jun 2009 20:24:45 -0700 (PDT)
Received: from OMTA05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by QMTA13.emeryville.ca.mail.comcast.net with comcast id 1e4H1c0050vp7WLADfQr9b; Tue, 09 Jun 2009 03:24:51 +0000
Received: from [192.168.0.112] ([24.6.155.154]) by OMTA05.emeryville.ca.mail.comcast.net with comcast id 1fQq1c0093L8a8Q8RfQqhh; Tue, 09 Jun 2009 03:24:51 +0000
Message-ID: <4A2DD5D9.6070506@tony.li>
Date: Mon, 08 Jun 2009 20:24:09 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Dino Farinacci <dino@cisco.com>
References: <6AEBBEF7-0EC7-4970-938A-D36C34F7C1DE@cisco.com>
In-Reply-To: <6AEBBEF7-0EC7-4970-938A-D36C34F7C1DE@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Any idea when RRG is going to meet in Stockholm?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2009 03:24:46 -0000

Dino Farinacci wrote:
> Will it be the usual 9:00-5:00 on Friday?


As usual, that's what we've requested.

Tony


From irtf@tonistoev.info  Wed Jun 10 14:49:56 2009
Return-Path: <irtf@tonistoev.info>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C3C9A3A6CAB for <rrg@core3.amsl.com>; Wed, 10 Jun 2009 14:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.49
X-Spam-Level: 
X-Spam-Status: No, score=-0.49 tagged_above=-999 required=5 tests=[AWL=0.305,  BAYES_05=-1.11, SARE_MILLIONSOF=0.315]
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 2KBagUWfmspo for <rrg@core3.amsl.com>; Wed, 10 Jun 2009 14:49:56 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id ECEBF3A6CA8 for <rrg@irtf.org>; Wed, 10 Jun 2009 14:49:55 -0700 (PDT)
Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <irtf@tonistoev.info>) id 1MEVgD-0000TQ-VS for rrg@irtf.org; Thu, 11 Jun 2009 00:49:57 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Thu, 11 Jun 2009 00:49:57 +0300
User-Agent: KMail/1.9.9
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200906110049.57425.irtf@tonistoev.info>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - chi.r1servers.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - tonistoev.info
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [rrg] The premises
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2009 21:49:56 -0000

Wow, real world beings have released Tony.

Joel,

Naming interface, not node, with (global) unicast addresses and mixing inter-domain with intra-domain routing are ideas that we are looking at that, in some peoples judgment, for some architectural directions, are likely to be helpful, but actually we bear the burden of those two ideas every day together with thousands of ignorant administrators and millions of unsuspecting users.

Toni
 
> Joel M. Halpern wrote:
> No Toni.  Those two ideas are neither "the" nor "premise" for the work 
> of the RRG.  They are ideas that we are looking at that, in some peoples 
> judgment, for some architectural directions, are likely to be helpful.
> 
> Joel
> 
> Toni Stoev wrote:
> > Dear fellow (re)searchers,
> > 
> > I like to remind you of the following:
> > Naming node, not interface, with locator and separating inter-domain from intra-domain routing are both together the premises for reaching the design goal of significantly improved routing scalability.
> > 
> > Toni

From HeinerHummel@aol.com  Sat Jun 13 08:30:03 2009
Return-Path: <HeinerHummel@aol.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83A3B3A6B4D for <rrg@core3.amsl.com>; Sat, 13 Jun 2009 08:30:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.917
X-Spam-Level: 
X-Spam-Status: No, score=0.917 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_83=0.6, SARE_MILLIONSOF=0.315]
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 DzzMiFaJehfi for <rrg@core3.amsl.com>; Sat, 13 Jun 2009 08:30:02 -0700 (PDT)
Received: from imo-m23.mx.aol.com (imo-m23.mx.aol.com [64.12.137.4]) by core3.amsl.com (Postfix) with ESMTP id B9EA03A6A91 for <rrg@irtf.org>; Sat, 13 Jun 2009 08:30:01 -0700 (PDT)
Received: from imo-da04.mx.aol.com (imo-da04.mx.aol.com [205.188.169.202]) by imo-m23.mx.aol.com (v107.10) with ESMTP id RELAYIN3-44a33c5f91e6; Sat, 13 Jun 2009 11:30:01 -0400
Received: from HeinerHummel@aol.com by imo-da04.mx.aol.com  (mail_out_v40_r1.5.) id a.bdb.478352fa (41811);  Sat, 13 Jun 2009 11:29:59 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <bdb.478352fa.37651ff7@aol.com>
Date: Sat, 13 Jun 2009 11:29:59 EDT
To: irtf@tonistoev.info, rrg@irtf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1244906999"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-IP: 205.188.169.202
Subject: Re: [rrg] The premises
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jun 2009 15:30:03 -0000

-------------------------------1244906999
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

 
Given that  a LISP WG has been installed in the meantime, it would be  of=
 
general interest (I believe), to hear whether this has any impact on the=
 RRG  
activities&tasks, e.g. as to
a) observe LISP from the distance only,
b) search for other solutions,
c) extend the view by which to look at the problems:Why are things  
sacrosanct such as
             -  the indeed orthogonality of intra and inter-domain routing=
 
? 
             -  the existing layer-2 / layer-3 separation although 
additional (outer) data is  needed by any solution
                (incl.LISP) ?
             -  the prefix aggregation paradigm although it dosn't work fo=
r 
multicast and  although internet-TV to 
               millions  of receivers might be the really big step in the=
 
future?
 
Heiner
 
In einer eMail vom 10.06.2009 23:50:11 Westeurop=E4ische Normalzeit schrei=
bt  
irtf@tonistoev.info:

Wow,  real world beings have released Tony.

Joel,

Naming interface,  not node, with (global) unicast addresses and mixing 
inter-domain with  intra-domain routing are ideas that we are looking at=
 that, 
in some peoples  judgment, for some architectural directions, are likely=
 to 
be helpful, but  actually we bear the burden of those two ideas every day=
 
together with  thousands of ignorant administrators and millions of 
unsuspecting  users.

Toni

> Joel M. Halpern wrote:
> No Toni.   Those two ideas are neither "the" nor "premise" for the work=
 
> of the  RRG.  They are ideas that we are looking at that, in some people=
s 
 
> judgment, for some architectural directions, are likely to be  helpful.
> 
> Joel
> 
> Toni Stoev wrote:
> >  Dear fellow (re)searchers,
> > 
> > I like to remind you of  the following:
> > Naming node, not interface, with locator and  separating inter-domain=
 
from intra-domain routing are both together the  premises for reaching the=
 
design goal of significantly improved routing  scalability.
> > 
> >  Toni
_______________________________________________
rrg mailing  list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg





-------------------------------1244906999
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1=
">
<META content=3D"MSHTML 6.00.6000.16850" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY=
: Arial" 
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Dr=
ole_document 
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>Given that&nbsp; a LISP WG has been installed in the meantime, it wou=
ld be 
of general interest (I believe), to hear whether this has any impact on th=
e RRG 
activities&amp;tasks, e.g. as to</DIV>
<DIV>a) observe LISP from the distance only,</DIV>
<DIV>b) search for other solutions,</DIV>
<DIV>c) extend the view by which to look at the problems:Why are&nbsp;thin=
gs 
sacrosanct such as</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;- 
the indeed orthogonality of intra and inter-domain routing ? </DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;- 
the existing layer-2 / layer-3 separation although additional (outer) data=
 is 
needed by any solution</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; 
(incl.LISP) ?</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; - 
the prefix aggregation paradigm although it dosn't work for multicast and=
 
although internet-TV to </DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;millions 
of&nbsp;receivers might be the&nbsp;really big step in the future?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>In einer eMail vom 10.06.2009 23:50:11 Westeurop=E4ische Normalzeit=
 schreibt 
irtf@tonistoev.info:</DIV>
<BLOCKQUOTE 
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 siz=
e=3D2>Wow, 
  real world beings have released Tony.<BR><BR>Joel,<BR><BR>Naming interfa=
ce, 
  not node, with (global) unicast addresses and mixing inter-domain with=
 
  intra-domain routing are ideas that we are looking at that, in some peop=
les 
  judgment, for some architectural directions, are likely to be helpful,=
 but 
  actually we bear the burden of those two ideas every day together with=
 
  thousands of ignorant administrators and millions of unsuspecting 
  users.<BR><BR>Toni<BR><BR>&gt; Joel M. Halpern wrote:<BR>&gt; No Toni.&n=
bsp; 
  Those two ideas are neither "the" nor "premise" for the work <BR>&gt; of=
 the 
  RRG.&nbsp; They are ideas that we are looking at that, in some peoples=
 
  <BR>&gt; judgment, for some architectural directions, are likely to be=
 
  helpful.<BR>&gt; <BR>&gt; Joel<BR>&gt; <BR>&gt; Toni Stoev wrote:<BR>&gt=
; &gt; 
  Dear fellow (re)searchers,<BR>&gt; &gt; <BR>&gt; &gt; I like to remind=
 you of 
  the following:<BR>&gt; &gt; Naming node, not interface, with locator and=
 
  separating inter-domain from intra-domain routing are both together the=
 
  premises for reaching the design goal of significantly improved routing=
 
  scalability.<BR>&gt; &gt; <BR>&gt; &gt; 
  Toni<BR>_______________________________________________<BR>rrg mailing=
 
  list<BR>rrg@irtf.org<BR>http://www.irtf.org/mailman/listinfo/rrg<BR></FO=
NT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1244906999--

From lixia@cs.ucla.edu  Sat Jun 20 12:12:07 2009
Return-Path: <lixia@cs.ucla.edu>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B054E3A68C9 for <rrg@core3.amsl.com>; Sat, 20 Jun 2009 12:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, SARE_MLH_Stock1=0.87]
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 a5hIbbWPUpNZ for <rrg@core3.amsl.com>; Sat, 20 Jun 2009 12:12:07 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 117653A6803 for <rrg@irtf.org>; Sat, 20 Jun 2009 12:12:07 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 5AAE639E808D for <rrg@irtf.org>; Sat, 20 Jun 2009 12:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t0kLQE2i5e4Q for <rrg@irtf.org>; Sat, 20 Jun 2009 12:12:17 -0700 (PDT)
Received: from [10.0.1.7] (cpe-98-151-52-146.socal.res.rr.com [98.151.52.146]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 595E839E80C5 for <rrg@irtf.org>; Sat, 20 Jun 2009 12:12:17 -0700 (PDT)
Message-Id: <35BF8B34-CF9F-454F-93B0-06ECD5761B75@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: rrg@irtf.org
In-Reply-To: <4A2DD5D9.6070506@tony.li>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sat, 20 Jun 2009 12:12:16 -0700
References: <6AEBBEF7-0EC7-4970-938A-D36C34F7C1DE@cisco.com> <4A2DD5D9.6070506@tony.li>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [rrg] Any idea when RRG is going to meet in Stockholm?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jun 2009 19:12:07 -0000

On Jun 8, 2009, at 8:24 PM, Tony Li wrote:

> Dino Farinacci wrote:
>> Will it be the usual 9:00-5:00 on Friday?
>
>
> As usual, that's what we've requested.
>
> Tony

in case people have not noticed: IETF75 *draft* agenda is out, RRG is  
on Friday as usual:
    See http://www.ietf.org/meetings/75/75-Draft-Agenda.pdf

FYI.


From christian.vogt@ericsson.com  Fri Jun 26 10:24:55 2009
Return-Path: <christian.vogt@ericsson.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D6143A6B07 for <rrg@core3.amsl.com>; Fri, 26 Jun 2009 10:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 56OPAqjyQYF4 for <rrg@core3.amsl.com>; Fri, 26 Jun 2009 10:24:54 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 3D62D3A6932 for <rrg@irtf.org>; Fri, 26 Jun 2009 10:24:54 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n5QHO3n9028785 for <rrg@irtf.org>; Fri, 26 Jun 2009 12:24:03 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 26 Jun 2009 12:24:03 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 26 Jun 2009 12:24:02 -0500
Message-Id: <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Routing Research Group Mailing List <rrg@irtf.org>
In-Reply-To: <49E559E0.2090302@tony.li>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 26 Jun 2009 10:24:03 -0700
References: <49E559E0.2090302@tony.li>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 26 Jun 2009 17:24:02.0935 (UTC) FILETIME=[E6749070:01C9F682]
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2009 17:24:55 -0000

Dear all -

I am catching up on folks' previous discussion on identifier properties.
This discussion is really useful; I wish I had participated earlier.

One thought that has been brought up is the inevitable coexistence of
multiple types of identifiers.  This makes sense given the variety of
things to be identified.  In fact, the multitudinousness of identifiers
is not new:  Many applications have their own identifiers already today.

But are all these identifier types essential elements of an Internet
architecture?  I would argue most of them are not -- they are useful
within the scope of a particular Internet application, but they are not
essential for the Internet per se to function.  In fact, I see only two
purposes for which the Internet architecture must have identifiers:

(1) service identification, identifying a piece of communication
     software that responds to incoming contact establishment attempts

(2) session identification, identifying the protocol state corresponding
     to a particular session after contact establishment

Individual Internet architecture solutions may use combinations of more
than one identifier for either of these two purposes.  For example,
service identification in the existing Internet is achieved by combining
a host identifier (DNS name, or IP address in its role as a host
identifier) and a host-local service identifier (well-known port
number).  So an Internet architecture may have more than two types of
identifiers.  But again, it seems that all of those identifiers would
serve only the above two purposes, after all.

Given the distinct identifier purposes, the properties of identifiers
may naturally be specific to a particular purpose.  For example, the
property of enabling session referrals clearly applies to only session
identification, but not to service identification.  On the other hand,
stability is a property that is more important for service
identification than for session identification, since two hosts engaged
in a session may be able to handle changes of session identifiers.

Thoughts?

- Christian




From irtf@tonistoev.info  Fri Jun 26 17:29:31 2009
Return-Path: <irtf@tonistoev.info>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE7453A6A09 for <rrg@core3.amsl.com>; Fri, 26 Jun 2009 17:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.545
X-Spam-Level: 
X-Spam-Status: No, score=-1.545 tagged_above=-999 required=5 tests=[AWL=1.054,  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 W0ym2+PGb54v for <rrg@core3.amsl.com>; Fri, 26 Jun 2009 17:29:30 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 82C5E3A681C for <rrg@irtf.org>; Fri, 26 Jun 2009 17:29:30 -0700 (PDT)
Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop-2.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <irtf@tonistoev.info>) id 1MKLnc-0005eB-Ez for rrg@irtf.org; Sat, 27 Jun 2009 03:29:44 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Sat, 27 Jun 2009 03:29:42 +0300
User-Agent: KMail/1.9.9
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
In-Reply-To: <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200906270329.43098.irtf@tonistoev.info>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - chi.r1servers.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - tonistoev.info
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jun 2009 00:29:31 -0000

Christian,

There is one more primary need for identification on the general network. That is the necessity of node identification.
A node has to have identifier in order to be distinguished from other nodes.
Node identification provides for efficient handling of node multihoming, possibly dynamic, and for stable mapping of human readable names.
One basic use of node identification is connection identification, which includes node identification. A complement to that use is the presence of node identification in connection initiation.
Node identification descends from the domain name system and is currently woven into unicast addressing. Extracting it from both is the evolution.

Toni


Christian Vogt wrote:
> Dear all -
> 
> I am catching up on folks' previous discussion on identifier properties.
> This discussion is really useful; I wish I had participated earlier.
> 
> One thought that has been brought up is the inevitable coexistence of
> multiple types of identifiers.  This makes sense given the variety of
> things to be identified.  In fact, the multitudinousness of identifiers
> is not new:  Many applications have their own identifiers already today.
> 
> But are all these identifier types essential elements of an Internet
> architecture?  I would argue most of them are not -- they are useful
> within the scope of a particular Internet application, but they are not
> essential for the Internet per se to function.  In fact, I see only two
> purposes for which the Internet architecture must have identifiers:
> 
> (1) service identification, identifying a piece of communication
>      software that responds to incoming contact establishment attempts
> 
> (2) session identification, identifying the protocol state corresponding
>      to a particular session after contact establishment
> 
> Individual Internet architecture solutions may use combinations of more
> than one identifier for either of these two purposes.  For example,
> service identification in the existing Internet is achieved by combining
> a host identifier (DNS name, or IP address in its role as a host
> identifier) and a host-local service identifier (well-known port
> number).  So an Internet architecture may have more than two types of
> identifiers.  But again, it seems that all of those identifiers would
> serve only the above two purposes, after all.
> 
> Given the distinct identifier purposes, the properties of identifiers
> may naturally be specific to a particular purpose.  For example, the
> property of enabling session referrals clearly applies to only session
> identification, but not to service identification.  On the other hand,
> stability is a property that is more important for service
> identification than for session identification, since two hosts engaged
> in a session may be able to handle changes of session identifiers.
> 
> Thoughts?
> 
> - Christian
> 
> 
> 
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>

From irtf@tonistoev.info  Sat Jun 27 19:14:01 2009
Return-Path: <irtf@tonistoev.info>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA5393A67E7 for <rrg@core3.amsl.com>; Sat, 27 Jun 2009 19:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[AWL=0.703,  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 jqpRhIX3WuD4 for <rrg@core3.amsl.com>; Sat, 27 Jun 2009 19:14:01 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id D14F63A6A3A for <rrg@irtf.org>; Sat, 27 Jun 2009 19:13:55 -0700 (PDT)
Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop-2.local) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <irtf@tonistoev.info>) id 1MKjuD-0005R8-W2 for rrg@irtf.org; Sun, 28 Jun 2009 05:14:10 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Sun, 28 Jun 2009 05:14:07 +0300
User-Agent: KMail/1.9.9
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
In-Reply-To: <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200906280514.08281.irtf@tonistoev.info>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - chi.r1servers.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - tonistoev.info
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jun 2009 02:14:01 -0000

Christian, thanks for waking us up.

Christian Vogt wrote:
> In fact, I see only two 
> purposes for which the Internet architecture must have identifiers:
> 
> (1) service identification, identifying a piece of communication
>      software that responds to incoming contact establishment attempts

Service identification denotes a type of activity that a node would perform for a node. For example, check the time and return a timestamp. The activity is checking and returning, and when it is performed multiple times, those are distinct activities of the same type. Identified is the particular type of activity among all that a node would perform.

> (2) session identification, identifying the protocol state corresponding
>      to a particular session after contact establishment

Do you mean connection identification?

> Individual Internet architecture solutions may use combinations of more
> than one identifier for either of these two purposes.  For example,
> service identification in the existing Internet is achieved by combining
> a host identifier (DNS name, or IP address in its role as a host
> identifier) and a host-local service identifier (well-known port
> number).

Since the port number is well-known, the service identifier is not just host-local, but is meaningful to any host, that is, it is global.
And the combination with host identifier is service localization.

> So an Internet architecture may have more than two types of 
> identifiers.  But again, it seems that all of those identifiers would
> serve only the above two purposes, after all.

There exists node-local identification of connection instances, currently the socket "port". It serves the purpose of connection identification.

Agree?

Toni

From christian.vogt@ericsson.com  Mon Jun 29 13:38:00 2009
Return-Path: <christian.vogt@ericsson.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62D7E28C17F for <rrg@core3.amsl.com>; Mon, 29 Jun 2009 13:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.526
X-Spam-Level: 
X-Spam-Status: No, score=-6.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 IKRaEK1j402W for <rrg@core3.amsl.com>; Mon, 29 Jun 2009 13:37:59 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 80C8228C185 for <rrg@irtf.org>; Mon, 29 Jun 2009 13:37:59 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n5TKcInr007441; Mon, 29 Jun 2009 15:38:19 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 29 Jun 2009 15:38:18 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 29 Jun 2009 15:38:17 -0500
Message-Id: <3EC7226C-FE5B-4DB7-9E2C-CBBFB6BE1095@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Toni Stoev <irtf@tonistoev.info>
In-Reply-To: <200906270329.43098.irtf@tonistoev.info>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 29 Jun 2009 13:38:18 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <200906270329.43098.irtf@tonistoev.info>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 29 Jun 2009 20:38:18.0029 (UTC) FILETIME=[88AC05D0:01C9F8F9]
Cc: IRTF RRG <rrg@irtf.org>
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2009 20:38:00 -0000

Toni -

I don't think that host identification is a necessary element of an
Internet architecture.  It is important which software process you
reach, not which hardware this software process runs on.  Load-balancing
mechanisms such as Akamai exploit just this.  Similarly, after contact
establishment, it is important to reach the protocol state for the
particular session at hand, not which hardware this state is currently
residing on.  Session mobility mechanisms exploit just this.  So host
identification is not a general requirement.

Of course, individual Internet architecture solutions may use host
identifiers as part of service or session identification.  Even the
existing Internet does this, as I mentioned in my previous email.  In
those cases, the host identifiers are used in composition with other,
typically host-local identifiers, so that the composition identifies
either a service or a session.

So again, we need identifiers for only two purposes: for the purpose of
service identification, and for the purpose of session identification.

- Christian



On Jun 26, 2009, Toni Stoev wrote:

> Christian,
>
> There is one more primary need for identification on the general
> network. That is the necessity of node identification. A node has to
> have identifier in order to be distinguished from other nodes. Node
> identification provides for efficient handling of node multihoming,
> possibly dynamic, and for stable mapping of human readable names. One
> basic use of node identification is connection identification, which
> includes node identification. A complement to that use is the presence
> of node identification in connection initiation. Node identification
> descends from the domain name system and is currently woven into  
> unicast
> addressing. Extracting it from both is the evolution.
>
> Toni




From christian.vogt@ericsson.com  Mon Jun 29 13:43:24 2009
Return-Path: <christian.vogt@ericsson.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B81228C2E9 for <rrg@core3.amsl.com>; Mon, 29 Jun 2009 13:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.529
X-Spam-Level: 
X-Spam-Status: No, score=-6.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 PChzFlpEIz6f for <rrg@core3.amsl.com>; Mon, 29 Jun 2009 13:43:23 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 9961028C2CB for <rrg@irtf.org>; Mon, 29 Jun 2009 13:43:23 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n5TKhb1e010274; Mon, 29 Jun 2009 15:43:37 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 29 Jun 2009 15:43:36 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 29 Jun 2009 15:43:36 -0500
Message-Id: <DF69E60C-656E-4C9C-9C8B-939F94047740@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Toni Stoev <irtf@tonistoev.info>
In-Reply-To: <200906280514.08281.irtf@tonistoev.info>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 29 Jun 2009 13:43:36 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <200906280514.08281.irtf@tonistoev.info>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 29 Jun 2009 20:43:36.0508 (UTC) FILETIME=[46800FC0:01C9F8FA]
Cc: IRTF RRG <rrg@irtf.org>
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2009 20:43:24 -0000

Hi Toni -

Regarding your question on whether I mean "connection identification"  
when saying "session identification":  For data exchanges that use  
connection-oriented transport protocols, yes, the two terms are the  
same.  But note that "session" is a more general term because it also  
includes data exchanges that use connection-less transport protocols.

- Christian



On Jun 27, 2009, Toni Stoev wrote:

> Christian, thanks for waking us up.
>
>> In fact, I see only two
>> purposes for which the Internet architecture must have identifiers:
>>
>> (1) service identification, identifying a piece of communication
>>     software that responds to incoming contact establishment attempts
>
> Service identification denotes a type of activity that a node would  
> perform for a node. For example, check the time and return a  
> timestamp. The activity is checking and returning, and when it is  
> performed multiple times, those are distinct activities of the same  
> type. Identified is the particular type of activity among all that a  
> node would perform.
>
>> (2) session identification, identifying the protocol state  
>> corresponding
>>     to a particular session after contact establishment
>
> Do you mean connection identification?
>
>> Individual Internet architecture solutions may use combinations of  
>> more
>> than one identifier for either of these two purposes.  For example,
>> service identification in the existing Internet is achieved by  
>> combining
>> a host identifier (DNS name, or IP address in its role as a host
>> identifier) and a host-local service identifier (well-known port
>> number).
>
> Since the port number is well-known, the service identifier is not  
> just host-local, but is meaningful to any host, that is, it is global.
> And the combination with host identifier is service localization.
>
>> So an Internet architecture may have more than two types of
>> identifiers.  But again, it seems that all of those identifiers would
>> serve only the above two purposes, after all.
>
> There exists node-local identification of connection instances,  
> currently the socket "port". It serves the purpose of connection  
> identification.
>
> Agree?
>
> Toni





From louise.burness@bt.com  Tue Jun 30 02:33:19 2009
Return-Path: <louise.burness@bt.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 071FF3A6CCB for <rrg@core3.amsl.com>; Tue, 30 Jun 2009 02:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.082
X-Spam-Level: 
X-Spam-Status: No, score=-3.082 tagged_above=-999 required=5 tests=[AWL=0.517,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 bigr3idjhv7Q for <rrg@core3.amsl.com>; Tue, 30 Jun 2009 02:33:18 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id E33383A6820 for <rrg@irtf.org>; Tue, 30 Jun 2009 02:33:17 -0700 (PDT)
Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.109]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 30 Jun 2009 10:33:09 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 30 Jun 2009 10:33:09 +0100
Message-ID: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <3EC7226C-FE5B-4DB7-9E2C-CBBFB6BE1095@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Next topic: properties of identifiers
Thread-Index: Acn4+ZBXZIh4vsuKTZeirGe+FpHGnQAbCPEg
From: <louise.burness@bt.com>
To: <christian.vogt@ericsson.com>, <irtf@tonistoev.info>
X-OriginalArrivalTime: 30 Jun 2009 09:33:09.0586 (UTC) FILETIME=[C7CCA320:01C9F965]
Cc: rrg@irtf.org
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2009 09:33:19 -0000

Is host identification most useful for fault finding?=20

> -----Original Message-----
> From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On=20
> Behalf Of Christian Vogt
> Sent: 29 June 2009 21:38
> To: Toni Stoev
> Cc: IRTF RRG
> Subject: Re: [rrg] Next topic: properties of identifiers
>=20
> Toni -
>=20
> I don't think that host identification is a necessary element=20
> of an Internet architecture.  It is important which software=20
> process you reach, not which hardware this software process=20
> runs on.  Load-balancing mechanisms such as Akamai exploit=20
> just this.  Similarly, after contact establishment, it is=20
> important to reach the protocol state for the particular=20
> session at hand, not which hardware this state is currently=20
> residing on.  Session mobility mechanisms exploit just this. =20
> So host identification is not a general requirement.
>=20
> Of course, individual Internet architecture solutions may use=20
> host identifiers as part of service or session=20
> identification.  Even the existing Internet does this, as I=20
> mentioned in my previous email.  In those cases, the host=20
> identifiers are used in composition with other, typically=20
> host-local identifiers, so that the composition identifies=20
> either a service or a session.
>=20
> So again, we need identifiers for only two purposes: for the=20
> purpose of service identification, and for the purpose of=20
> session identification.
>=20
> - Christian
>=20
>=20
>=20
> On Jun 26, 2009, Toni Stoev wrote:
>=20
> > Christian,
> >
> > There is one more primary need for identification on the general=20
> > network. That is the necessity of node identification. A=20
> node has to=20
> > have identifier in order to be distinguished from other nodes. Node=20
> > identification provides for efficient handling of node multihoming,=20
> > possibly dynamic, and for stable mapping of human readable=20
> names. One=20
> > basic use of node identification is connection=20
> identification, which=20
> > includes node identification. A complement to that use is=20
> the presence=20
> > of node identification in connection initiation. Node=20
> identification=20
> > descends from the domain name system and is currently woven into=20
> > unicast addressing. Extracting it from both is the evolution.
> >
> > Toni
>=20
>=20
>=20
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>=20

From pfrejborg@gmail.com  Tue Jun 30 06:19:15 2009
Return-Path: <pfrejborg@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 831E128C3B7 for <rrg@core3.amsl.com>; Tue, 30 Jun 2009 06:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_BIZOP=0.7]
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 U4GFrYOnsehK for <rrg@core3.amsl.com>; Tue, 30 Jun 2009 06:19:14 -0700 (PDT)
Received: from mail-yx0-f179.google.com (mail-yx0-f179.google.com [209.85.210.179]) by core3.amsl.com (Postfix) with ESMTP id 357353A6A38 for <rrg@irtf.org>; Tue, 30 Jun 2009 06:19:04 -0700 (PDT)
Received: by yxe9 with SMTP id 9so76681yxe.15 for <rrg@irtf.org>; Tue, 30 Jun 2009 06:18:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3XQnIwa2M8JZxwfSv8MqIz81wNp+GrHNwCWDoMjT3MM=; b=UfdjYMw3K3aQSvYPNBEU43DiEAb2nZAab351Pb/z3A/1ugxxsTjiX/yMhpL2brm/ii xchxJx6o+1dSltC/0uC7bjp+GjQ8ksXMPK68u98ziCta99dVT6x3qGBDqO6fe7X2vkui o36OU8eDE8SCbof+5Hk+3dH2ri3HvGWGjEqP4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bnBjbzmIqq9tXGLnmyHyvXiHQ9MtSuWZ6/LdfZ+KXTHWU0w3UvXaHnRFkOq+vWVGY9 s8aV5kB5JxyLf9D+u1ru0r8gDMgkX4i0Pdz87qpyYm9SiJR8gDR1k9sRotDZCqpern8m ROxEWEsQeNE+pNaXqdSIN+y/xF7Smapv2ULXQ=
MIME-Version: 1.0
Received: by 10.100.144.14 with SMTP id r14mr11214285and.120.1246367604799;  Tue, 30 Jun 2009 06:13:24 -0700 (PDT)
In-Reply-To: <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
Date: Tue, 30 Jun 2009 16:13:24 +0300
Message-ID: <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com>
From: Patrick Frejborg <pfrejborg@gmail.com>
To: Christian Vogt <christian.vogt@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Routing Research Group Mailing List <rrg@irtf.org>
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2009 13:19:15 -0000

Hi Christian,

I think service identification and session identification is belonging
to the transport layer in the IP reference model  - in the OS model
they are on separate layers. So in the IP model I would collapse them
under one identifier, I think that is what we have today. E.g a TCP
connection is identified by the five tuples; source and destination
addresses, source and destination ports and protocol. But here the
problems starts, a connection/session/association is identified by
elements from the network layer (source and destination addresses) -
thus the border between the network and transport layer gets very
blurred. I believe that this is the reason why we today need to have
global unique IP addresses, with global addresses we can identify
connections on hosts, security and NAT nodes - it is the only method
at the moment, right?

Adding a host identifier to the IP reference model wouldn't add much
value - unless it can decouple the dependency between network and
transport layer. If the host identifier could give an identity for a
connection without deep dependency to the network layer an new world
opens. I.e. a connection could be identified by some other mechanisms
than the network tuples. Then we could migrate from a single-level
address scheme to a multilevel address scheme and create a better
routing architecture without the need to have global unique addresses.
And mobility would be much easier to achieve, i.e. if connections are
identified by something else it doesn't matter when the underlying
network changes - the application will not be aware and doesn't care
about the network parameters.

SCTP goes in this direction but the current mainstream transport
protocol is TCP. Guess people will not move their applications to use
SCTP instead of TCP in order to improve the routing architecture of
Internet, right?
I think the only way is to fool TCP that underlying network is still
the same though it isn't - something is needed between the network and
transport layer that the applications aren't aware of. By having a new
layer we could change the underlying addressing scheme with backwards
compatibly to the current addressing scheme - not all stacks needs to
be upgraded since it is backwards compatible. This will not improve
mobility but mobility will be improved once people are starting to
move their applications to use the host identifier to identify
connections on the transport layer. Would people move their
applications to support mobility? I think it is matter of time, there
are so much mobile devices connected to Internet that enterprises will
see business opportunities to move applications to an infrastructure
that better supports mobility, this is long term vision but guess it
will happen.

So I think the identifier(s) should be designed to decouple the
transport layer from the network layer. Opponents will say that all
hosts must be upgraded, this is not true if the the new stack is made
backwards compatible with fallback mechanisms to the current
architecture.


-- patte


On Fri, Jun 26, 2009 at 8:24 PM, Christian
Vogt<christian.vogt@ericsson.com> wrote:
> Dear all -
>
> I am catching up on folks' previous discussion on identifier properties.
> This discussion is really useful; I wish I had participated earlier.
>
> One thought that has been brought up is the inevitable coexistence of
> multiple types of identifiers. =A0This makes sense given the variety of
> things to be identified. =A0In fact, the multitudinousness of identifiers
> is not new: =A0Many applications have their own identifiers already today=
.
>
> But are all these identifier types essential elements of an Internet
> architecture? =A0I would argue most of them are not -- they are useful
> within the scope of a particular Internet application, but they are not
> essential for the Internet per se to function. =A0In fact, I see only two
> purposes for which the Internet architecture must have identifiers:
>
> (1) service identification, identifying a piece of communication
> =A0 =A0software that responds to incoming contact establishment attempts
>
> (2) session identification, identifying the protocol state corresponding
> =A0 =A0to a particular session after contact establishment
>
> Individual Internet architecture solutions may use combinations of more
> than one identifier for either of these two purposes. =A0For example,
> service identification in the existing Internet is achieved by combining
> a host identifier (DNS name, or IP address in its role as a host
> identifier) and a host-local service identifier (well-known port
> number). =A0So an Internet architecture may have more than two types of
> identifiers. =A0But again, it seems that all of those identifiers would
> serve only the above two purposes, after all.
>
> Given the distinct identifier purposes, the properties of identifiers
> may naturally be specific to a particular purpose. =A0For example, the
> property of enabling session referrals clearly applies to only session
> identification, but not to service identification. =A0On the other hand,
> stability is a property that is more important for service
> identification than for session identification, since two hosts engaged
> in a session may be able to handle changes of session identifiers.
>
> Thoughts?
>
> - Christian
>
>
>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>

From christian.vogt@ericsson.com  Tue Jun 30 12:50:43 2009
Return-Path: <christian.vogt@ericsson.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9B953A6EC5 for <rrg@core3.amsl.com>; Tue, 30 Jun 2009 12:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 UqWrDG9f6bBa for <rrg@core3.amsl.com>; Tue, 30 Jun 2009 12:50:42 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id CC7003A6EBA for <rrg@irtf.org>; Tue, 30 Jun 2009 12:50:42 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n5UJobwO012845; Tue, 30 Jun 2009 14:50:37 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 30 Jun 2009 14:50:36 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 30 Jun 2009 14:50:36 -0500
Message-Id: <8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: "<louise.burness@bt.com>" <louise.burness@bt.com>
In-Reply-To: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 30 Jun 2009 12:50:37 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 30 Jun 2009 19:50:36.0836 (UTC) FILETIME=[09AE5E40:01C9F9BC]
Cc: rrg@irtf.org
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2009 19:50:43 -0000

> Is host identification most useful for fault finding?


Louise -

Absolutely.  In fact, there is a richness of purposes for which one may
need identifiers.  What I claim is that most of those purposes are
application-specific and not essential to an Internet architecture.  For
example, fault finding is the purpose of a debugging application.

An Internet architecture must be versatile enough to enable applications
to use their own identifiers.  But to do this, the Internet architecture
itself must incorporate identifiers for only two purposes:  to  
identify a
peer service for contact establishment, and to identify a session
instantiated during contact establishment.  On top of that, applications
can do what they want, such as providing a means to identify hosts for
fault finding.  Does this make sense?

- Christian



From christian.vogt@ericsson.com  Tue Jun 30 13:14:51 2009
Return-Path: <christian.vogt@ericsson.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6670F3A6A96 for <rrg@core3.amsl.com>; Tue, 30 Jun 2009 13:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.203
X-Spam-Level: 
X-Spam-Status: No, score=-6.203 tagged_above=-999 required=5 tests=[AWL=-0.304, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_BIZOP=0.7]
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 u0TH-s7vwcX2 for <rrg@core3.amsl.com>; Tue, 30 Jun 2009 13:14:50 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 675473A6891 for <rrg@irtf.org>; Tue, 30 Jun 2009 13:14:50 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n5UKDor8011427; Tue, 30 Jun 2009 15:15:11 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 30 Jun 2009 15:14:56 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 30 Jun 2009 15:14:55 -0500
Message-Id: <9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Patrick Frejborg <pfrejborg@gmail.com>
In-Reply-To: <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 30 Jun 2009 13:14:56 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 30 Jun 2009 20:14:55.0505 (UTC) FILETIME=[6F1D9810:01C9F9BF]
Cc: Routing Research Group Mailing List <rrg@irtf.org>
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2009 20:14:51 -0000

Hi Patte -

You are absolutely right that decoupling services and sessions from
their location would be highly useful.  The current conflation of
identification and location certainly has serious disadvantages.  For
example, decoupling would mitigate the routing scalability problem.

But are you saying that using a host identity as part of service or
session identification is necessary to achieve this decoupling?

- Christian



On Jun 30, 2009, at Patrick Frejborg wrote:

> Hi Christian,
>
> I think service identification and session identification is belonging
> to the transport layer in the IP reference model  - in the OS model
> they are on separate layers. So in the IP model I would collapse them
> under one identifier, I think that is what we have today. E.g a TCP
> connection is identified by the five tuples; source and destination
> addresses, source and destination ports and protocol. But here the
> problems starts, a connection/session/association is identified by
> elements from the network layer (source and destination addresses) -
> thus the border between the network and transport layer gets very
> blurred. I believe that this is the reason why we today need to have
> global unique IP addresses, with global addresses we can identify
> connections on hosts, security and NAT nodes - it is the only method
> at the moment, right?
>
> Adding a host identifier to the IP reference model wouldn't add much
> value - unless it can decouple the dependency between network and
> transport layer. If the host identifier could give an identity for a
> connection without deep dependency to the network layer an new world
> opens. I.e. a connection could be identified by some other mechanisms
> than the network tuples. Then we could migrate from a single-level
> address scheme to a multilevel address scheme and create a better
> routing architecture without the need to have global unique addresses.
> And mobility would be much easier to achieve, i.e. if connections are
> identified by something else it doesn't matter when the underlying
> network changes - the application will not be aware and doesn't care
> about the network parameters.
>
> SCTP goes in this direction but the current mainstream transport
> protocol is TCP. Guess people will not move their applications to use
> SCTP instead of TCP in order to improve the routing architecture of
> Internet, right?
> I think the only way is to fool TCP that underlying network is still
> the same though it isn't - something is needed between the network and
> transport layer that the applications aren't aware of. By having a new
> layer we could change the underlying addressing scheme with backwards
> compatibly to the current addressing scheme - not all stacks needs to
> be upgraded since it is backwards compatible. This will not improve
> mobility but mobility will be improved once people are starting to
> move their applications to use the host identifier to identify
> connections on the transport layer. Would people move their
> applications to support mobility? I think it is matter of time, there
> are so much mobile devices connected to Internet that enterprises will
> see business opportunities to move applications to an infrastructure
> that better supports mobility, this is long term vision but guess it
> will happen.
>
> So I think the identifier(s) should be designed to decouple the
> transport layer from the network layer. Opponents will say that all
> hosts must be upgraded, this is not true if the the new stack is made
> backwards compatible with fallback mechanisms to the current
> architecture.
>
>
> -- patte



