
From louise.burness@bt.com  Wed Jul  1 01:04:45 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 521513A6AE6 for <rrg@core3.amsl.com>; Wed,  1 Jul 2009 01:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.856
X-Spam-Level: 
X-Spam-Status: No, score=-2.856 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, J_CHICKENPOX_42=0.6, 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 kbTLOzfTl+iw for <rrg@core3.amsl.com>; Wed,  1 Jul 2009 01:04:44 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by core3.amsl.com (Postfix) with ESMTP id 2A04F3A68D3 for <rrg@irtf.org>; Wed,  1 Jul 2009 01:04:42 -0700 (PDT)
Received: from E03MVB2-UKBR.domain1.systemhost.net ([193.113.197.109]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 1 Jul 2009 09:05:02 +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: Wed, 1 Jul 2009 09:05:01 +0100
Message-ID: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Next topic: properties of identifiers
Thread-Index: Acn5vA06aOd8qnMgQIuxGoFTRLGh+gAZfqHA
From: <louise.burness@bt.com>
To: <christian.vogt@ericsson.com>
X-OriginalArrivalTime: 01 Jul 2009 08:05:02.0951 (UTC) FILETIME=[A321E770:01C9FA22]
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: Wed, 01 Jul 2009 08:04:45 -0000

=20

> -----Original Message-----
> From: Christian Vogt [mailto:christian.vogt@ericsson.com]=20
> Sent: 30 June 2009 20:51
> To: Krug,AL,Louise,CXR9 R
> Cc: irtf@tonistoev.info; rrg@irtf.org
> Subject: Re: [rrg] Next topic: properties of identifiers
>=20
> > Is host identification most useful for fault finding?
>=20
>=20
> Louise -
>=20
> Absolutely.  In fact, there is a richness of purposes for=20
> which one may need identifiers.  What I claim is that most of=20
> those purposes are application-specific and not essential to=20
> an Internet architecture.  For example, fault finding is the=20
> purpose of a debugging application.
>=20
> An Internet architecture must be versatile enough to enable=20
> applications to use their own identifiers.  But to do this,=20
> the Internet architecture itself must incorporate identifiers=20
> for only two purposes:  to identify a peer service for=20
> contact establishment, and to identify a session instantiated=20
> during contact establishment.  On top of that, applications=20
> can do what they want, such as providing a means to identify=20
> hosts for fault finding.  Does this make sense?
>=20
> - Christian
>=20
>=20
>=20
It makes sense in the abstract, but I am still mulling the question "if
a lot of applications would need something such as a host ID, and the
network does not provide it will we end up with a lot of different ways
of providing it, and possibly some very nasty ways (like IP addresses
got overused). I guess then you might say that you have the core
architecture and a set of extras that need to be standardised but you
should not expect them to be gloablly available?

Do you think the session need to have a globally unique identifier or
locally agreed between the endpoints during the contact establishment?

Louise

From jmh@joelhalpern.com  Wed Jul  1 07:04:26 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 C3CB828C561 for <rrg@core3.amsl.com>; Wed,  1 Jul 2009 07:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.222
X-Spam-Level: 
X-Spam-Status: No, score=-3.222 tagged_above=-999 required=5 tests=[AWL=-0.223, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, 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 5gVkHhkmOUKB for <rrg@core3.amsl.com>; Wed,  1 Jul 2009 07:04:25 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 706B83A6F3A for <rrg@irtf.org>; Wed,  1 Jul 2009 07:04:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id AD26E430229 for <rrg@irtf.org>; Wed,  1 Jul 2009 07:03:23 -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 007FB430218 for <rrg@irtf.org>; Wed,  1 Jul 2009 07:03:22 -0700 (PDT)
Message-ID: <4A4B6CA7.7080208@joelhalpern.com>
Date: Wed, 01 Jul 2009 10:03:19 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: rrg@irtf.org
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>
In-Reply-To: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Wed, 01 Jul 2009 14:04:26 -0000

While there is an architectural argument that we should have nothing 
more than is absolutely necessary in the architecture, taken too far 
this view encourages entangling components and misusing information. 
(~We could use that piece over there, instead of having the right piece 
with the right meaning, sicne it would save a part.~)

While it is sometimes (particularly for management purposes) useful to 
be able to name a physical node, when I look at this the piece I tend to 
want to name is the communicating entity.  Having a name for this thing 
is useful for session establishment, referral, and security purposes. 
This is distinct from, but may be a component of, the identifier used 
for a specific communication session.  (Some folks like to simply mint 
session IDs in a way that is sufficiently unique, some like to 
implicitly tie session IDs to the entity IDs, and some folks use designs 
where the tie-in is explicit.)

The reason I started with the comment about necessity is taht some folks 
argue that a communicating entity ID is not necessary as it can be 
represented by the collected network layer locators.  (And that once one 
has established communication using any locators, the protocol can 
exchange the rest.)  This is true as far as it goes.
It seems to me however that it is useful to be able to explicitly tell 
which locators go with the same communicating entity, as distinct from 
the larger set of locators which might go with the same service 
(whatever that means.)

To save myself typing, and because it tends to be similar to what other 
folks have meant when they use the term, I tend to prefer to think of 
this ID as a stack-ID.  And yes, I know that is vague.  Exactly what is 
the stack.  Does it include TCP, UDP, SCTP, and DCCP, or is it just one 
of them?  Etc.
I have considered writing a draft trying to clarify this, but the 
question of identifiers has not seemed to be the actual top problem, so 
I have not seen enough reason to do so.

Yours,
Joel

louise.burness@bt.com wrote:
>  
> 
>> -----Original Message-----
>> From: Christian Vogt [mailto:christian.vogt@ericsson.com] 
>> Sent: 30 June 2009 20:51
>> To: Krug,AL,Louise,CXR9 R
>> Cc: irtf@tonistoev.info; rrg@irtf.org
>> Subject: Re: [rrg] Next topic: properties of identifiers
>>
>>> 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
>>
>>
>>
> It makes sense in the abstract, but I am still mulling the question "if
> a lot of applications would need something such as a host ID, and the
> network does not provide it will we end up with a lot of different ways
> of providing it, and possibly some very nasty ways (like IP addresses
> got overused). I guess then you might say that you have the core
> architecture and a set of extras that need to be standardised but you
> should not expect them to be gloablly available?
> 
> Do you think the session need to have a globally unique identifier or
> locally agreed between the endpoints during the contact establishment?
> 
> Louise
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
> 

From pfrejborg@gmail.com  Wed Jul  1 13:51:17 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 C44F53A6A73 for <rrg@core3.amsl.com>; Wed,  1 Jul 2009 13:51:17 -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 FkhrlGBdqU41 for <rrg@core3.amsl.com>; Wed,  1 Jul 2009 13:51:16 -0700 (PDT)
Received: from mail-yx0-f187.google.com (mail-yx0-f187.google.com [209.85.210.187]) by core3.amsl.com (Postfix) with ESMTP id A46853A6AB8 for <rrg@irtf.org>; Wed,  1 Jul 2009 13:49:16 -0700 (PDT)
Received: by yxe17 with SMTP id 17so390560yxe.15 for <rrg@irtf.org>; Wed, 01 Jul 2009 13:47:07 -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=8i4s3tW1vx+VSgG2NhDfPJlp73uFAVX3NtpuM1m2YGM=; b=OM+YP9B3v+Nfam0wb64GFj+bmItu8LYcSRSyG4k93kk0i5jp/Munt0cnyOat7/jtBn F9TgWfT792UNuz0hV5QYQm8iPL793tUuMbmKpVjoaRs0Yy13x5DSrqxpYdNNPn5466qE A6pLmI2C5W2GwNptV42i6fxWirfWwyxNYt4ao=
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=ElSI3hr7MY0ll8N697hUOWg2w4U01cRr046XpXXz0SM2RBIXWNSh59OsCvW9DZia0x OcXUkOcokIlcaBKTY5BoQ8DVa3K4AFBXT5erQuhR8gk1ObGOTG4znZrKHPIeOciJI66n 83Tx0gDUqILO/hrmeh1SO4IUGOjBp9lIVRNMU=
MIME-Version: 1.0
Received: by 10.100.241.8 with SMTP id o8mr14018937anh.102.1246481227094; Wed,  01 Jul 2009 13:47:07 -0700 (PDT)
In-Reply-To: <9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com>
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com> <9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com>
Date: Wed, 1 Jul 2009 23:47:07 +0300
Message-ID: <5bc37fd40907011347p29101477m1441fcd1b05e61e7@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: Wed, 01 Jul 2009 20:51:17 -0000

Hi Christian,

I think host identity together with a generic session identification
mechanism would make it easier to promote the decoupling, there would
be more good reasons to upgrade the stack - e.g. server load balancing
and troubleshooting in the "middleboxed" Internet would be a lot more
easier to carry out.

HTTP deploys cookies to identify sessions and a Server Load Balancer
uses the cookies to do load balancing, especially if the clients are
behind a NAT device. Using cookies as the session identifier is the
only mechanism to ensure that the client is communicating to the
correct real server, also to achieve good load balancing if there are
many clients behind one NAT device.

Also SIP people are building their own mechanism to identify sessions
http://tools.ietf.org/html/draft-kaplan-sip-session-id-02

1.2. The use-case for Session-ID


   The need for a unique identifier is driven by the need to
   troubleshoot SIP sessions as they cross SIP nodes.  Troubleshooting
   is more complicated if multiple legs of the session are on different
   sides of B2BUA's, due to the lack of a common identifier to tie the
   legs together.  Currently proprietary mechanisms are used to achieve
   this.

It seems that application people are already developing their own
specific solutions to have an end-to-end session identifier mechanism.
HTTP uses cookies, SIP is developing their own mechanism and perhaps
there are more applications having similar solutions developed or
under construction - could this get out of control, if every
application develops their own method to identify an end-to-end
host/session???

It would be great if the transport layer (or something between the
transport and network layer) have a standardized host identifier (not
relying on the network locators) with a session identifier that all
applications could access - if the application developers find it
useful. And the middleboxes should not be allowed to touch the
host/session identifier - the main purpose of the identifier is to
provide a troubleshooting tool that provides visibility behind
NAT/middleboxes, a mobility enabler (with a session identifier you
might restart a TCP connection, security issues arises and now I'm on
thin ice) and a new routing architecture enabler.
A host/session identifier could be e.g. the following: the host part
derived from the MAC address from one attached NIC and the session
identifier could be just a random counter that changes every time the
application layer initiates a new session. So one part is globally
unique and the other part is session unique - just as an example.
Ports are used to identify services and I don't see a reason to change
that mechanism.....or??

-- patte


On Tue, Jun 30, 2009 at 11:14 PM, Christian
Vogt<christian.vogt@ericsson.com> wrote:
> Hi Patte -
>
> You are absolutely right that decoupling services and sessions from
> their location would be highly useful. =A0The current conflation of
> identification and location certainly has serious disadvantages. =A0For
> 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 =A0- 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
>
>
>
>

From pfrejborg@gmail.com  Thu Jul  2 00:41:04 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 4344728C0D7 for <rrg@core3.amsl.com>; Thu,  2 Jul 2009 00:41:04 -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 73R-JNQADBjE for <rrg@core3.amsl.com>; Thu,  2 Jul 2009 00:41:03 -0700 (PDT)
Received: from mail-yx0-f187.google.com (mail-yx0-f187.google.com [209.85.210.187]) by core3.amsl.com (Postfix) with ESMTP id 18C8C3A6B5E for <rrg@irtf.org>; Thu,  2 Jul 2009 00:41:03 -0700 (PDT)
Received: by yxe17 with SMTP id 17so800696yxe.15 for <rrg@irtf.org>; Thu, 02 Jul 2009 00:41:22 -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=uS9d0w5VrVavHCOvAtGFMC3idu75R09Lq434z5TqNCg=; b=SmgX4MseDYzpqYvr108EiwNMGNY8y4dMXNpSMkpch6Hy8KxEoWHgw4cDUJ196C2Ck8 AyPbkz4GKNIwxSacjitJY8apGmoHQCcmLenAAURczPj5sYYQO/CAMjdVx+E3cQsWkwh5 94sH8ArxQCXhVOAaHfPdu5APMIbEu1EQ2S5TU=
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=n0GwCmRRsTocUirbUFeIgQw+ZG324eS385x1wJl7h+TGL6RxbJMTbbn4VZjcsz1zGE WBjxmdKx9rRyG08dXxD0OUZnaUcsCDxq3nP7Er3yNLCAm1oGsjZ+LfmoK0z09Rf+0+jM MZS14siUverUmzipt0C1hJpdnwoGK76b3Rj4I=
MIME-Version: 1.0
Received: by 10.100.105.4 with SMTP id d4mr15181691anc.39.1246520482518; Thu,  02 Jul 2009 00:41:22 -0700 (PDT)
In-Reply-To: <9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com>
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com> <9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com>
Date: Thu, 2 Jul 2009 10:41:22 +0300
Message-ID: <5bc37fd40907020041w6daf6179g267cf9a391872802@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: Thu, 02 Jul 2009 07:41:04 -0000

Hi Christian,

trying to come up with more arguments and here is an early simple
idea, more or less a brain dump that you (all of you) should try to
shoot down.

NAPT devices have to keep track of both IP addresses and ports, the
binding can become quite complex. But if the connection also have host
identifiers in the header of the datagrams the NAPT box doesn't need
to keep track of the ports - the connection can be tracked with the
help of the host identifier.

Not so interesting but it gets better if the host identifier is added
to the DNS record. By adding a host identifier to the DNS record the
NAPT box could accept traffic from the Internet and redirect it to the
correct host in the private network. This can be achieved by having
the DNS entry as the IP address with the public IP address of the NAPT
box and the host identifier with the global unique identifier of the
internal server. Then you create a static binding at the middlebox - a
host identifier is binded to the internal IP address of the server.
Now the middlebox can handle both inbound and outbound connections,
with one public PA IP address, and still provide end-to-end visibility
in case you need to troubleshoot sessions. Also the meaning of DNS
changes slightly, a DNS look up tells us today "what is the local IP
address of the server". With the host identifier added the DNS look up
would tell us "via this attachment point at the border of Internet the
internal host can be reached".

How then to achieve multi-homing? Well, add a second middlebox to the
organization's network - the second middlebox should have a PA-address
from another service provider and then two DNS records are needed,
same host identifier record with two different A-records, each with
weights so one of them is the preferred path (just as an example). If
the primary path goes down the clients should after a while try to use
the secondary path. And here is the session identifier needed - since
the network path changes TCP connections needs to be restarted, this
can be achieved if there is a session identifier coupled to the host
identifier. But this will also open up for man-in-the-middle attacks -
should we try to solve this on the network or transport layer?  I
don't think so, instead the transport layer should inform the
application layer that the network parameters has changed (could be an
attack) and then it is up to the application layer - should the
credentials for this session be re-verified or not - it depends on the
content of the application (the lower layers should not get involved
with the content).

If this is really doable the outcome is that PI-addresses are no
longer attractive, you can publish services towards Internet with your
internal addressing scheme - the routing architecture of an
organization is an internal affair and Internet doesn't need to know
about how it is constructed. But still external customers, partners
etc. can reach your published services with the help of the host
identifier.

It seems that adding a host identifier to the Internet architecture
will provide better visibility of end-to-end connectivity and at the
same time hide more the routing architecture, interesting...

Or do I miss something, this is an early idea and there might be some
severe flaw in my thinking.

-- patte

On Tue, Jun 30, 2009 at 11:14 PM, Christian
Vogt<christian.vogt@ericsson.com> wrote:
> Hi Patte -
>
> You are absolutely right that decoupling services and sessions from
> their location would be highly useful. =A0The current conflation of
> identification and location certainly has serious disadvantages. =A0For
> 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 =A0- 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
>
>
>
>

From pekka.nikander@nomadiclab.com  Thu Jul  2 02:25:33 2009
Return-Path: <pekka.nikander@nomadiclab.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 04DFA28C165 for <rrg@core3.amsl.com>; Thu,  2 Jul 2009 02:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 GpcT5+9p9QUq for <rrg@core3.amsl.com>; Thu,  2 Jul 2009 02:25:30 -0700 (PDT)
Received: from n2.nomadiclab.com (n2.nomadiclab.com [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 58FA13A6A9E for <rrg@irtf.org>; Thu,  2 Jul 2009 02:25:29 -0700 (PDT)
Received: from n2.nomadiclab.com (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id C59511EF208; Thu,  2 Jul 2009 12:25:44 +0300 (EEST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by n2.nomadiclab.com (Postfix) with ESMTP id 5ADAC1EF12E; Thu,  2 Jul 2009 12:25:44 +0300 (EEST)
Message-Id: <881A869F-4E9E-4D98-B3C0-82526B298B55@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: Routing Research Group Mailing List <rrg@irtf.org>
In-Reply-To: <5bc37fd40907020041w6daf6179g267cf9a391872802@mail.gmail.com>
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: Thu, 2 Jul 2009 12:25:44 +0300
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com> <9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com> <5bc37fd40907020041w6daf6179g267cf9a391872802@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: Christian Vogt <christian.vogt@ericsson.com>
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: Thu, 02 Jul 2009 09:25:33 -0000

Sorry for sounding like a broken record player, but I have a strong  
deja vu.

> Not so interesting but it gets better if the host identifier is  
> added to the DNS record.

RFC5205

> By adding a host identifier to the DNS record the NAPT box could  
> accept traffic from the Internet and redirect it to the correct host  
> in the private network.

See draft-ietf-hip-nat-traversal-08.txt and draft-melen-spinat-01.txt  
for two different ways.

> How then to achieve multi-homing?

RFC5206

> If this is really doable the outcome is that PI-addresses are no
> longer attractive, you can publish services towards Internet with your
> internal addressing scheme - the routing architecture of an
> organization is an internal affair and Internet doesn't need to know
> about how it is constructed. But still external customers, partners
> etc. can reach your published services with the help of the host
> identifier.

I completely agree. Those were some of our goals.

> It seems that adding a host identifier to the Internet architecture
> will provide better visibility of end-to-end connectivity and at the
> same time hide more the routing architecture, interesting...

I think we wrote something about those already in RFC4423.  (And  
others before that, see e.g. NIMROD...)

-------

[Then I hear all the usual objections on HIP from the list.  To them:   
Yes, you can use HIP without ESP (but we still need someone to define  
exact how).  Yes, we can use HIP without public key crypto, see draft- 
heer-hip-lhip-00.txt.  No, architecturally HIP does not necessarily  
add packet size as it can use any flow identifier as a proxy for host  
identifier.  No, HIP does not necessarily add delay when opening TCP  
with legacy hosts, draft-lindqvist-hip-tcp-piggybacking-00.txt.

Ducking back wondering why people want to invent the same again and  
again...]

--Pekka Nikander


From christian.vogt@ericsson.com  Fri Jul  3 16:05:50 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 7B6EE3A6EBA for <rrg@core3.amsl.com>; Fri,  3 Jul 2009 16:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.555
X-Spam-Level: 
X-Spam-Status: No, score=-6.555 tagged_above=-999 required=5 tests=[AWL=0.044,  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 kxddq-GG1YRI for <rrg@core3.amsl.com>; Fri,  3 Jul 2009 16:05:49 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 48D6628C354 for <rrg@irtf.org>; Fri,  3 Jul 2009 16:05:00 -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 n63N5KMG029436; Fri, 3 Jul 2009 18:05:23 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 3 Jul 2009 18:05:04 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 3 Jul 2009 18:05:03 -0500
Message-Id: <32802D78-63CE-4471-A107-4322A93D683A@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Patrick Frejborg <pfrejborg@gmail.com>
In-Reply-To: <5bc37fd40907011347p29101477m1441fcd1b05e61e7@mail.gmail.com>
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: Fri, 3 Jul 2009 16:05:03 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com> <9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com> <5bc37fd40907011347p29101477m1441fcd1b05e61e7@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 03 Jul 2009 23:05:04.0010 (UTC) FILETIME=[B31916A0:01C9FC32]
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: Fri, 03 Jul 2009 23:05:50 -0000

On Jul 1, 2009, Patrick Frejborg wrote:

> I think host identity together with a generic session identification
> mechanism would make it easier to promote the decoupling, there  
> would be
> more good reasons to upgrade the stack - e.g. server load balancing  
> and
> troubleshooting in the "middleboxed" Internet would be a lot more  
> easier
> to carry out.

Patte -

So you are saying that it would be useful if (part of) a session
identifier identified the host that is keeping the session state.
Perhaps.  Or, more specifically, session identifiers should also
identify the /stack/ that is keeping the session state.

But I am still unconvinced that session identifiers really should
identify anything else but a session.  There are two reasons:  First, if
they did, session mobility would be constrained, because a session would
by definition be bound to something else, such as a host or a stack.
Second, given a pure session identifier and the session's address, I
don't yet see a general benefit of having a host (or stack) identifier
in addition.

The emphasis here is on "general", since there will certainly be
applications that need host or stack identifiers.  But again, those host
and stack identifiers will be application-level components, and don't
have to be defined as part of Internet architecture in my personal
opinion.

- Christian



From christian.vogt@ericsson.com  Fri Jul  3 16:24: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 D505E3A67AA for <rrg@core3.amsl.com>; Fri,  3 Jul 2009 16:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level: 
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043,  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 TLZnRIAn4HPW for <rrg@core3.amsl.com>; Fri,  3 Jul 2009 16:24:43 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id E70043A68E1 for <rrg@irtf.org>; Fri,  3 Jul 2009 16:23:52 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n63NOBKK003372; Fri, 3 Jul 2009 18:24:12 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 3 Jul 2009 18:23:19 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 3 Jul 2009 18:23:18 -0500
Message-Id: <4C542F5F-67EA-4E87-B0D0-577F361697A1@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Louise Burness <louise.burness@bt.com>
In-Reply-To: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@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: Fri, 3 Jul 2009 16:23:18 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 03 Jul 2009 23:23:18.0973 (UTC) FILETIME=[3FBF2ED0:01C9FC35]
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: Fri, 03 Jul 2009 23:24:44 -0000

On Jul 1, 2009, Louise Burness wrote:

> It makes sense in the abstract, but I am still mulling the question  
> "if
> a lot of applications would need something such as a host ID, and the
> network does not provide it will we end up with a lot of different  
> ways
> of providing it, and possibly some very nasty ways (like IP addresses
> got overused). [...]

Very likely we will.  But we may in any case, even if there was a
default means to identify a host.

Applications often have their very specific requirements, which makes it
hard to provide a default that is sufficient for all applications.  The
consequence is that applications incorporate their own mechanisms.

- Christian




From christian.vogt@ericsson.com  Fri Jul  3 18:52:50 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 35CB33A6B2E for <rrg@core3.amsl.com>; Fri,  3 Jul 2009 18:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.557
X-Spam-Level: 
X-Spam-Status: No, score=-6.557 tagged_above=-999 required=5 tests=[AWL=0.042,  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 Rbq0O6hbdlya for <rrg@core3.amsl.com>; Fri,  3 Jul 2009 18:52:49 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 558843A682A for <rrg@irtf.org>; Fri,  3 Jul 2009 18:52:49 -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 n63NwgHi006018; Fri, 3 Jul 2009 18:58:43 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 3 Jul 2009 18:58:12 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 3 Jul 2009 18:58:12 -0500
Message-Id: <8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <4A4B6CA7.7080208@joelhalpern.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 3 Jul 2009 16:58:12 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <4A4B6CA7.7080208@joelhalpern.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 03 Jul 2009 23:58:12.0652 (UTC) FILETIME=[1FAD3EC0:01C9FC3A]
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: Sat, 04 Jul 2009 01:52:50 -0000

On Jul 1, 2009, Joel M. Halpern wrote:

> It seems to me however that it is useful to be able to explicitly tell
> which locators go with the same communicating entity, as distinct from
> the larger set of locators which might go with the same service [...]

Joel -

Yes, we absolutely need this.  But why does this imply the need for a
host or stack identifier?  Session identifiers already map to the set of
locators that go to the same communicating entity.  This is why we need
to distinguish them from service identifiers, which in turn may map to
locators of different communicating entities.

- Christian




From jmh@joelhalpern.com  Fri Jul  3 19:36:25 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 225BB3A6814 for <rrg@core3.amsl.com>; Fri,  3 Jul 2009 19:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.533
X-Spam-Level: 
X-Spam-Status: No, score=-3.533 tagged_above=-999 required=5 tests=[AWL=0.066,  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 sdxIeNIFlMCX for <rrg@core3.amsl.com>; Fri,  3 Jul 2009 19:36:24 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 62DD33A65A6 for <rrg@irtf.org>; Fri,  3 Jul 2009 19:36:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id E617E4302D6; Fri,  3 Jul 2009 19:36:45 -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 4958A4302D4; Fri,  3 Jul 2009 19:36:45 -0700 (PDT)
Message-ID: <4A4EC03C.3000604@joelhalpern.com>
Date: Fri, 03 Jul 2009 22:36:44 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Christian Vogt <christian.vogt@ericsson.com>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <4A4B6CA7.7080208@joelhalpern.com> <8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com>
In-Reply-To: <8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 04 Jul 2009 02:36:25 -0000

The reason this (naming the set of locators that lead to the same 
entity) leads to a stack ID (or node, host, something) is that I want 
that collective property available before I start communicating.
Referrals are the easy case.  I am trying to refer someone to a specific 
entity.  They do not have a session with that entity.  So a session ID 
is clearly totally useless for a referral.

I believe that similar constraints apply at the time of initial 
communication establishment, in that there is a semantic difference 
between using multiple locators for a target to establish communication 
and trying to establish communicaiton with multiple "equivalent but 
distinct" targets.  I consider it helpful to udnerstand that distinction.

It seems clear to me that one of the important properties of a 
communication session is the pair (or worse, if one likes multiparty 
sessions) of entities that are talking.  But session identification is 
much more specific than just naming the communicating parties, or even 
the available interfaces.  At this stage of the game I do not care 
whether session IDs are minted using the stack IDs, or minted out of 
whole cloth using bilateral state.  Either can work.  I am not arguing 
that session IDs inherently require stack IDs.  They don't.  I am 
arguing that stack IDs are useful separate from session IDs.

Yours,
Joel

Christian Vogt wrote:
> On Jul 1, 2009, Joel M. Halpern wrote:
> 
>> It seems to me however that it is useful to be able to explicitly tell
>> which locators go with the same communicating entity, as distinct from
>> the larger set of locators which might go with the same service [...]
> 
> Joel -
> 
> Yes, we absolutely need this.  But why does this imply the need for a
> host or stack identifier?  Session identifiers already map to the set of
> locators that go to the same communicating entity.  This is why we need
> to distinguish them from service identifiers, which in turn may map to
> locators of different communicating entities.
> 
> - Christian
> 
> 
> 
> 

From irtf@tonistoev.info  Sat Jul  4 11:44:13 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 6FF5428C14C for <rrg@core3.amsl.com>; Sat,  4 Jul 2009 11:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.865
X-Spam-Level: 
X-Spam-Status: No, score=-0.865 tagged_above=-999 required=5 tests=[AWL=-0.680, 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 6cP3esi9WJim for <rrg@core3.amsl.com>; Sat,  4 Jul 2009 11:44:12 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 53EAD3A69B7 for <rrg@irtf.org>; Sat,  4 Jul 2009 11:44:03 -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 1MNADn-00059D-Ro for rrg@irtf.org; Sat, 04 Jul 2009 21:44:23 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Sat, 4 Jul 2009 21:44:22 +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: <200907042144.23098.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] Common understanding
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, 04 Jul 2009 18:44:13 -0000

Dear fellow (re)searchers,

Some of the opinions expressed on the list, with positions that I share, include the concept of protocol layering.
There is an alternative to that concept. It is the role-based architecture (RBA). It gives much freedom with consistency.
I would like to communicate here, knowing that at least some of you know what role-based architecture is.
Please, anyone interested, find the documentation of RBA and read it.
Or maybe you already know RBA.
Either case, please, let me know.

Toni

From christian.vogt@ericsson.com  Sun Jul  5 15:14: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 AB4F728C161 for <rrg@core3.amsl.com>; Sun,  5 Jul 2009 15:14:55 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sexiNLbPZRuk for <rrg@core3.amsl.com>; Sun,  5 Jul 2009 15:14:54 -0700 (PDT)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by core3.amsl.com (Postfix) with ESMTP id CDCE728C146 for <rrg@irtf.org>; Sun,  5 Jul 2009 15:14:54 -0700 (PDT)
Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 25ACC3ACFD9; Sun,  5 Jul 2009 18:15:19 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 05 Jul 2009 18:15:19 -0400
X-Sasl-enc: SnIgMZISEeHeuPxmdv3rdJsgFZgXD8aAZxPsgqZN+Olp 1246832118
Received: from [10.0.1.2] (99-28-160-42.lightspeed.miamfl.sbcglobal.net [99.28.160.42]) by mail.messagingengine.com (Postfix) with ESMTPSA id 69B1E49F90; Sun,  5 Jul 2009 18:15:18 -0400 (EDT)
Message-Id: <AB393FE6-4D0F-49DE-891D-12BBEA6F7C15@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
In-Reply-To: <4A4EC03C.3000604@joelhalpern.com>
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: Sun, 5 Jul 2009 15:15:16 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <4A4B6CA7.7080208@joelhalpern.com> <8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com> <4A4EC03C.3000604@joelhalpern.com>
X-Mailer: Apple Mail (2.935.3)
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: Sun, 05 Jul 2009 22:14:55 -0000

Joel -

You are saying that there ought to be a third identifier type, besides
service and session identifiers, which is used to map a service of
interest to a particular stack on which an instance of this service is
running.  This would enable a host to refer a third party to this
particular service instance.

I agree with you that such "service instance referrals" must be
possible.  Where our opinions diverge is on whether we need a third
identifier type for it.

In my opinion, we don't need a third identifier type for service
instance referrals.  The service identifiers, which we need in any case,
are already sufficient for this purpose:  At the point where an
application wants to refer a third party to a particular service
instance, it is defining a new service that only said service instance
can provide.  This new service can naturally have its own service
identifier.  This service identifier, in turn, will map to the locators
of only the stack on which the referenced service instance in running.

Oh, and regarding session identifiers:  Those are irrelevant for all of
the above. I agree with this. It is the service identifiers that matter.

- Christian



On Jul 3, 2009, Joel M. Halpern wrote:

> The reason this (naming the set of locators that lead to the same
> entity) leads to a stack ID (or node, host, something) is that I want
> that collective property available before I start communicating.
> Referrals are the easy case.  I am trying to refer someone to a  
> specific
> entity.  They do not have a session with that entity.  So a session ID
> is clearly totally useless for a referral.
>
> I believe that similar constraints apply at the time of initial
> communication establishment, in that there is a semantic difference
> between using multiple locators for a target to establish  
> communication
> and trying to establish communicaiton with multiple "equivalent but
> distinct" targets.  I consider it helpful to udnerstand that
> distinction.
>
> It seems clear to me that one of the important properties of a
> communication session is the pair (or worse, if one likes multiparty
> sessions) of entities that are talking.  But session identification is
> much more specific than just naming the communicating parties, or even
> the available interfaces.  At this stage of the game I do not care
> whether session IDs are minted using the stack IDs, or minted out of
> whole cloth using bilateral state.  Either can work.  I am not arguing
> that session IDs inherently require stack IDs.  They don't.  I am
> arguing that stack IDs are useful separate from session IDs.
>
> Yours, Joel




From lixia@cs.ucla.edu  Tue Jul  7 04:29:32 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 3448A28C349 for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 04:29:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 kArrcHiXQ5FQ for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 04:29:31 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 87C6A28C305 for <rrg@irtf.org>; Tue,  7 Jul 2009 04:29:31 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 5CCAA39E80DA; Tue,  7 Jul 2009 04:28:42 -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 nJ1B6WCAwzOI; Tue,  7 Jul 2009 04:28:37 -0700 (PDT)
Received: from [10.113.178.251] (unknown [88.128.80.187]) by smtp.cs.ucla.edu (Postfix) with ESMTP id EE63139E80CF; Tue,  7 Jul 2009 04:28:36 -0700 (PDT)
Message-Id: <5D502750-5F80-4C4B-A80E-20C19EC7760D@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Toni Stoev <irtf@tonistoev.info>
In-Reply-To: <200907042144.23098.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: Tue, 7 Jul 2009 04:28:32 -0700
References: <200907042144.23098.irtf@tonistoev.info>
X-Mailer: Apple Mail (2.935.3)
Cc: IRTF RRG <rrg@irtf.org>
Subject: Re: [rrg] Common understanding
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, 07 Jul 2009 11:29:32 -0000

On Jul 4, 2009, at 11:44 AM, Toni Stoev wrote:

> Dear fellow (re)searchers,
>
> Some of the opinions expressed on the list, with positions that I  
> share, include the concept of protocol layering.
> There is an alternative to that concept. It is the role-based  
> architecture (RBA). It gives much freedom with consistency.
> I would like to communicate here, knowing that at least some of you  
> know what role-based architecture is.
> Please, anyone interested, find the documentation of RBA and read it.
> Or maybe you already know RBA.
> Either case, please, let me know.

Hi Toni,

Thanks for the msg, RBA can indeed be an interesting topic.
On the other hand, my understanding of the goal of this RG at this  
time is to address routing scalability issue without requiring the  
whole Internet moving to an entirely different architecture.

Lixia

From pfrejborg@gmail.com  Tue Jul  7 09:13:35 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 27D9F3A6ABE for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 09:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.350,  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 6zFz2uEQXogz for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 09:13:34 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248]) by core3.amsl.com (Postfix) with ESMTP id 18CE03A690F for <rrg@irtf.org>; Tue,  7 Jul 2009 09:13:34 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c38so1972595ana.37 for <rrg@irtf.org>; Tue, 07 Jul 2009 09:13:18 -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=uGjZeXTvTF3rH6HL23BXeMRR5XdqBhuymv9wvPcOFUo=; b=BcyNQJyKx8Eso1kkEMCghrQaQJePmLSzXwfSRANHymNdBPEQal2iDQdk+NdDl4AxCV eBGWjo0Ztz+UUA74MCvNxWCaZOW+9sYAZMYA5weOWOuVNoTIgeMlQLqeF6G5/pehGF7d Ip2OEHUajJuE3a2I6vlQjtHMKOD06rDJSCuh0=
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=KMSkFE+80GeL35nWCDiFYlkzXn2GB3b3YpYB7EHBbLImuEIuvukUKGOzs66h30EKQ/ EzdK0gpOo0HXJprKmIONaKAzzmLjXQxNSGXL+5W9kEZajR9hT/WKpxasuGRm0N+L5ctV aMjYsxudmxSMAd9deUuqIPvTwgXOiWIRGmUxA=
MIME-Version: 1.0
Received: by 10.100.32.6 with SMTP id f6mr10737268anf.143.1246983198429; Tue,  07 Jul 2009 09:13:18 -0700 (PDT)
In-Reply-To: <881A869F-4E9E-4D98-B3C0-82526B298B55@nomadiclab.com>
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com> <9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com> <5bc37fd40907020041w6daf6179g267cf9a391872802@mail.gmail.com> <881A869F-4E9E-4D98-B3C0-82526B298B55@nomadiclab.com>
Date: Tue, 7 Jul 2009 19:13:18 +0300
Message-ID: <5bc37fd40907070913y3e2fa371h584f0623d66679ab@mail.gmail.com>
From: Patrick Frejborg <pfrejborg@gmail.com>
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Routing Research Group Mailing List <rrg@irtf.org>, Christian Vogt <christian.vogt@ericsson.com>
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, 07 Jul 2009 16:13:35 -0000

Pekka,

thanks for playing that record again, I got familiar with LHIP - which
is a very interesting draft, indeed.

-- patte

On Thu, Jul 2, 2009 at 12:25 PM, Pekka
Nikander<pekka.nikander@nomadiclab.com> wrote:
> Sorry for sounding like a broken record player, but I have a strong deja =
vu.
>
>> Not so interesting but it gets better if the host identifier is added to
>> the DNS record.
>
> RFC5205
>
>> By adding a host identifier to the DNS record the NAPT box could accept
>> traffic from the Internet and redirect it to the correct host in the pri=
vate
>> network.
>
> See draft-ietf-hip-nat-traversal-08.txt and draft-melen-spinat-01.txt for
> two different ways.
>
>> How then to achieve multi-homing?
>
> RFC5206
>
>> If this is really doable the outcome is that PI-addresses are no
>> longer attractive, you can publish services towards Internet with your
>> internal addressing scheme - the routing architecture of an
>> organization is an internal affair and Internet doesn't need to know
>> about how it is constructed. But still external customers, partners
>> etc. can reach your published services with the help of the host
>> identifier.
>
> I completely agree. Those were some of our goals.
>
>> It seems that adding a host identifier to the Internet architecture
>> will provide better visibility of end-to-end connectivity and at the
>> same time hide more the routing architecture, interesting...
>
> I think we wrote something about those already in RFC4423. =A0(And others
> before that, see e.g. NIMROD...)
>
> -------
>
> [Then I hear all the usual objections on HIP from the list. =A0To them: =
=A0Yes,
> you can use HIP without ESP (but we still need someone to define exact ho=
w).
> =A0Yes, we can use HIP without public key crypto, see
> draft-heer-hip-lhip-00.txt. =A0No, architecturally HIP does not necessari=
ly
> add packet size as it can use any flow identifier as a proxy for host
> identifier. =A0No, HIP does not necessarily add delay when opening TCP wi=
th
> legacy hosts, draft-lindqvist-hip-tcp-piggybacking-00.txt.
>
> Ducking back wondering why people want to invent the same again and
> again...]
>
> --Pekka Nikander
>
>

From pfrejborg@gmail.com  Tue Jul  7 09:39:58 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 D515428C2F9 for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 09:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[AWL=0.263,  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 GJgzrY3F3UXw for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 09:39:57 -0700 (PDT)
Received: from mail-gx0-f206.google.com (mail-gx0-f206.google.com [209.85.217.206]) by core3.amsl.com (Postfix) with ESMTP id 96F2A3A6E72 for <rrg@irtf.org>; Tue,  7 Jul 2009 09:39:57 -0700 (PDT)
Received: by gxk2 with SMTP id 2so5084542gxk.7 for <rrg@irtf.org>; Tue, 07 Jul 2009 09:40:12 -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=JxtMyIuw0c8wfrPYsAgf0YlbpbX2t6AwEKe8ItO2H7c=; b=G7JHJKXST9Yd6VMKLOWSWbc5JfCkynGpN61ghH3KCLKuUsEoZu8n5MtPKGRuImZjjt UDt13wIkRosSRjaVXf0iNNCx4vTdivlhpMBUvOzYEhxvabecCZO5jlRNm8ZGBNFOjeEz 3qEIHXkWmxrnMWpIkrBOhIszePd2hMxfh8icE=
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=CwDmM330E78x8z6IXJiOaiq6b4f5iz1WFp9PiM7JFYY8i2Ls6Zwp1IOu92gYsr2J1L dj55YhW+SAUllOkHIZindVzYrPLb1guVQNc50z5c1FgvS+NkVYl4Yr+9G6GeeZvamunZ 9AL/ahXkOgOJy1Hc5iL/m59tH28amuq6cgVQU=
MIME-Version: 1.0
Received: by 10.100.32.6 with SMTP id f6mr10777903anf.143.1246984812569; Tue,  07 Jul 2009 09:40:12 -0700 (PDT)
In-Reply-To: <4A4EC03C.3000604@joelhalpern.com>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <4A4B6CA7.7080208@joelhalpern.com> <8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com> <4A4EC03C.3000604@joelhalpern.com>
Date: Tue, 7 Jul 2009 19:40:12 +0300
Message-ID: <5bc37fd40907070940v694f3022r68e7579442486210@mail.gmail.com>
From: Patrick Frejborg <pfrejborg@gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rrg@irtf.org, Christian Vogt <christian.vogt@ericsson.com>
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, 07 Jul 2009 16:39:58 -0000

Joel,

I think you are right here and I got it all wrong when claiming that
host-ID, hereafter stack-ID, should be coupled together with a
session-ID.
Now I agree that they should be separated - when separated only the
server need to have a stack-ID, the client doesn't need to have one.
Then we are close to a HTTP session token solution, aren't we?

http://en.wikipedia.org/wiki/Session_(computer_science)

-- patte

On Sat, Jul 4, 2009 at 5:36 AM, Joel M. Halpern<jmh@joelhalpern.com> wrote:
> The reason this (naming the set of locators that lead to the same entity)
> leads to a stack ID (or node, host, something) is that I want that
> collective property available before I start communicating.
> Referrals are the easy case. =A0I am trying to refer someone to a specifi=
c
> entity. =A0They do not have a session with that entity. =A0So a session I=
D is
> clearly totally useless for a referral.
>
> I believe that similar constraints apply at the time of initial
> communication establishment, in that there is a semantic difference betwe=
en
> using multiple locators for a target to establish communication and tryin=
g
> to establish communicaiton with multiple "equivalent but distinct" target=
s.
> =A0I consider it helpful to udnerstand that distinction.
>
> It seems clear to me that one of the important properties of a communicat=
ion
> session is the pair (or worse, if one likes multiparty sessions) of entit=
ies
> that are talking. =A0But session identification is much more specific tha=
n
> just naming the communicating parties, or even the available interfaces. =
=A0At
> this stage of the game I do not care whether session IDs are minted using
> the stack IDs, or minted out of whole cloth using bilateral state. =A0Eit=
her
> can work. =A0I am not arguing that session IDs inherently require stack I=
Ds.
> =A0They don't. =A0I am arguing that stack IDs are useful separate from se=
ssion
> IDs.
>
> Yours,
> Joel
>
> Christian Vogt wrote:
>>
>> On Jul 1, 2009, Joel M. Halpern wrote:
>>
>>> It seems to me however that it is useful to be able to explicitly tell
>>> which locators go with the same communicating entity, as distinct from
>>> the larger set of locators which might go with the same service [...]
>>
>> Joel -
>>
>> Yes, we absolutely need this. =A0But why does this imply the need for a
>> host or stack identifier? =A0Session identifiers already map to the set =
of
>> locators that go to the same communicating entity. =A0This is why we nee=
d
>> to distinguish them from service identifiers, which in turn may map to
>> locators of different communicating entities.
>>
>> - Christian
>>
>>
>>
>>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>

From jmh@joelhalpern.com  Tue Jul  7 12:56:25 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 6D0F13A6AAC for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 12:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level: 
X-Spam-Status: No, score=-2.812 tagged_above=-999 required=5 tests=[AWL=-0.547, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 Pn5P56pZ35By for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 12:56:24 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by core3.amsl.com (Postfix) with ESMTP id 3C80B3A67F0 for <rrg@irtf.org>; Tue,  7 Jul 2009 12:56:24 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by morbo.tigertech.net (Postfix) with ESMTP id 3244BA39F5 for <rrg@irtf.org>; Tue,  7 Jul 2009 12:55:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id BEE1043031B; Tue,  7 Jul 2009 12:55:13 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [192.168.2.250] (wsip-24-249-19-66.hr.hr.cox.net [24.249.19.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 3E62B4302B5; Tue,  7 Jul 2009 12:55:13 -0700 (PDT)
Message-ID: <4A53A81E.8090405@joelhalpern.com>
Date: Tue, 07 Jul 2009 15:55:10 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Patrick Frejborg <pfrejborg@gmail.com>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	 <4A4B6CA7.7080208@joelhalpern.com>	 <8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com>	 <4A4EC03C.3000604@joelhalpern.com> <5bc37fd40907070940v694f3022r68e7579442486210@mail.gmail.com>
In-Reply-To: <5bc37fd40907070940v694f3022r68e7579442486210@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 07 Jul 2009 19:56:25 -0000

It is probably true that for a client-server protocol, the client does 
not need to have a stack-ID.

 From an architectural perspective, I tend to see that any machine may 
sometimes be a server, and therefore I prefer to approach things by 
giving every stack an ID.

Thank you,
Joel

Patrick Frejborg wrote:
> Joel,
> 
> I think you are right here and I got it all wrong when claiming that
> host-ID, hereafter stack-ID, should be coupled together with a
> session-ID.
> Now I agree that they should be separated - when separated only the
> server need to have a stack-ID, the client doesn't need to have one.
> Then we are close to a HTTP session token solution, aren't we?
> 
> http://en.wikipedia.org/wiki/Session_(computer_science)
> 
> -- patte
> 
> On Sat, Jul 4, 2009 at 5:36 AM, Joel M. Halpern<jmh@joelhalpern.com> wrote:
>> The reason this (naming the set of locators that lead to the same entity)
>> leads to a stack ID (or node, host, something) is that I want that
>> collective property available before I start communicating.
>> Referrals are the easy case.  I am trying to refer someone to a specific
>> entity.  They do not have a session with that entity.  So a session ID is
>> clearly totally useless for a referral.
>>
>> I believe that similar constraints apply at the time of initial
>> communication establishment, in that there is a semantic difference between
>> using multiple locators for a target to establish communication and trying
>> to establish communicaiton with multiple "equivalent but distinct" targets.
>>  I consider it helpful to udnerstand that distinction.
>>
>> It seems clear to me that one of the important properties of a communication
>> session is the pair (or worse, if one likes multiparty sessions) of entities
>> that are talking.  But session identification is much more specific than
>> just naming the communicating parties, or even the available interfaces.  At
>> this stage of the game I do not care whether session IDs are minted using
>> the stack IDs, or minted out of whole cloth using bilateral state.  Either
>> can work.  I am not arguing that session IDs inherently require stack IDs.
>>  They don't.  I am arguing that stack IDs are useful separate from session
>> IDs.
>>
>> Yours,
>> Joel
>>
>> Christian Vogt wrote:
>>> On Jul 1, 2009, Joel M. Halpern wrote:
>>>
>>>> It seems to me however that it is useful to be able to explicitly tell
>>>> which locators go with the same communicating entity, as distinct from
>>>> the larger set of locators which might go with the same service [...]
>>> Joel -
>>>
>>> Yes, we absolutely need this.  But why does this imply the need for a
>>> host or stack identifier?  Session identifiers already map to the set of
>>> locators that go to the same communicating entity.  This is why we need
>>> to distinguish them from service identifiers, which in turn may map to
>>> locators of different communicating entities.
>>>
>>> - Christian
>>>
>>>
>>>
>>>
>> _______________________________________________
>> rrg mailing list
>> rrg@irtf.org
>> http://www.irtf.org/mailman/listinfo/rrg
>>
> 

From lixia@CS.UCLA.EDU  Tue Jul  7 13:15:55 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 55C703A6867 for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 13:15:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 2Tz3+hZUqWO2 for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 13:15:54 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 7283F3A683B for <rrg@irtf.org>; Tue,  7 Jul 2009 13:15:54 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id C231C39E80CF; Tue,  7 Jul 2009 13:15:27 -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 u6-hIjbZxnQe; Tue,  7 Jul 2009 13:15:23 -0700 (PDT)
Received: from [192.168.1.12] (unknown [80.187.147.250]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 60EC139E80C5; Tue,  7 Jul 2009 13:15:21 -0700 (PDT)
Message-Id: <60273303-E2CA-4F25-B683-FAC9CCE54579@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Christian Vogt <christian.vogt@ericsson.com>
In-Reply-To: <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
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, 7 Jul 2009 13:00:27 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
X-Mailer: Apple Mail (2.935.3)
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, 07 Jul 2009 20:15:55 -0000

On Jun 26, 2009, at 10:24 AM, Christian Vogt wrote:

> Dear all -
>
> I am catching up on folks' previous discussion on identifier  
> properties.

I'm doing the same, albert 10 days after Christian, in preparation for  
next IETF. Just finished all the msgs on this thread.

> This discussion is really useful; I wish I had participated earlier.

same here!!!

I'll save the detailed comments for a face-face chat as next IETF is  
really coming soon.
For a quick comment here: I'd just say that I would like to second the  
view some other people have expressed earlier, that is whether a good  
architecture should have nothing more than necessary --- this is  
quoted from one of Joel's msgs but I removed the adjective "absolutely".
I view a good architecture as a good engineering design, the necessity  
should be measured by whether it is the best engineering tradeoff;  
pushing a design to the extreme point may or may not represent the  
best tradeoff.

Lixia

> 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 lixia@CS.UCLA.EDU  Tue Jul  7 13:46:42 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 3F4073A696D for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 13:46:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=-0.350, 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 uLTpPB-C4lFr for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 13:46:41 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 7EC2D3A6967 for <rrg@irtf.org>; Tue,  7 Jul 2009 13:46:41 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 32C4139E80DA for <rrg@irtf.org>; Tue,  7 Jul 2009 13:45:48 -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 zINAyIR6mlLf for <rrg@irtf.org>; Tue,  7 Jul 2009 13:45:43 -0700 (PDT)
Received: from [192.168.1.12] (unknown [80.187.147.250]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 0C8E839E80CF for <rrg@irtf.org>; Tue,  7 Jul 2009 13:45:40 -0700 (PDT)
Message-Id: <081E8BA4-2222-426A-B5CE-B6712FBF1A64@CS.UCLA.EDU>
From: Lixia Zhang <lixia@CS.UCLA.EDU>
To: rrg@irtf.org
In-Reply-To: <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com>
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, 7 Jul 2009 13:45:02 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
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, 07 Jul 2009 20:46:42 -0000

On Jun 30, 2009, at 6:13 AM, Patrick Frejborg wrote:

> ......
> 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 so.

> 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.

Patte, the above are all great comments.
To my view, the work by multipath-TCP people seems to match what you  
described above: don't try to change TCP, but make use of it by adding  
some sort of sub-layer, in their case it is a sub-layer that makes use  
of multiple simultaneous TCP connections, and backward compatible (and  
might  handling mobility as well).
In case not everyone has heard: a MPTCP BOF has been scheduled on Wed  
morning of IETF week.

> 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
>


From irtf@tonistoev.info  Tue Jul  7 20:06:36 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 375023A6A1F for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 20:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.786
X-Spam-Level: 
X-Spam-Status: No, score=-0.786 tagged_above=-999 required=5 tests=[AWL=-0.487, BAYES_00=-2.599, MANGLED_RVLUTN=2.3]
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 BHdSH-fQCFZ2 for <rrg@core3.amsl.com>; Tue,  7 Jul 2009 20:06:35 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 67EF83A6452 for <rrg@irtf.org>; Tue,  7 Jul 2009 20:06:34 -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 1MONUf-0007kv-6v; Wed, 08 Jul 2009 06:06:49 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Wed, 8 Jul 2009 06:06:47 +0300
User-Agent: KMail/1.9.9
References: <200907042144.23098.irtf@tonistoev.info> <5D502750-5F80-4C4B-A80E-20C19EC7760D@cs.ucla.edu>
In-Reply-To: <5D502750-5F80-4C4B-A80E-20C19EC7760D@cs.ucla.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907080606.48308.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] Common understanding
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, 08 Jul 2009 03:06:36 -0000

On Tuesday 7 July 2009 at 14:28:32 Lixia Zhang sent:
> 
> On Jul 4, 2009, at 11:44 AM, Toni Stoev wrote:
> 
> > Dear fellow (re)searchers,
> >
> > Some of the opinions expressed on the list, with positions that I  
> > share, include the concept of protocol layering.
> > There is an alternative to that concept. It is the role-based  
> > architecture (RBA). It gives much freedom with consistency.
> > I would like to communicate here, knowing that at least some of you  
> > know what role-based architecture is.
> > Please, anyone interested, find the documentation of RBA and read it.
> > Or maybe you already know RBA.
> > Either case, please, let me know.
> 
> Hi Toni,
> 
> Thanks for the msg, RBA can indeed be an interesting topic.
> On the other hand, my understanding of the goal of this RG at this  
> time is to address routing scalability issue without requiring the  
> whole Internet moving to an entirely different architecture.
> 
> Lixia
> 

Hi Lixia,

Surely this research group is not chartered to change the packet header processing model of the Internet.
But folks are using here protocol layering concepts as routing solution arguments. Meanwhile there modestly exists a role-based approach.
Are we stuck with the layering approach, or are we free to choose roling.
Let us free ourselves of this unclarity and face the real routing choices.

Besides routing, there is actually the need for a significantly different architecture. The RBA is a fundament for such a change. A few more (r)evolution aspiring concepts are needed for the change.

So, Lixia, thanks for knowing RBA.

Toni

From lixia@cs.ucla.edu  Wed Jul  8 00:56:08 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 9B3E03A6E16 for <rrg@core3.amsl.com>; Wed,  8 Jul 2009 00:56:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_RVLUTN=2.3]
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 rTJQ-zWE6EJP for <rrg@core3.amsl.com>; Wed,  8 Jul 2009 00:56: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 DFC813A6AE1 for <rrg@irtf.org>; Wed,  8 Jul 2009 00:56:07 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 20DF939E80DF; Wed,  8 Jul 2009 00:56:22 -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 8FUr-zolFR4b; Wed,  8 Jul 2009 00:56:18 -0700 (PDT)
Received: from [192.168.1.28] (unknown [88.128.85.149]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 5D3B839E80DC; Wed,  8 Jul 2009 00:56:15 -0700 (PDT)
Message-Id: <3EE20780-DB40-488D-862D-614FC5E8B986@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Toni Stoev <irtf@tonistoev.info>
In-Reply-To: <200907080606.48308.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: Wed, 8 Jul 2009 00:56:09 -0700
References: <200907042144.23098.irtf@tonistoev.info> <5D502750-5F80-4C4B-A80E-20C19EC7760D@cs.ucla.edu> <200907080606.48308.irtf@tonistoev.info>
X-Mailer: Apple Mail (2.935.3)
Cc: IRTF RRG <rrg@irtf.org>
Subject: Re: [rrg] Common understanding
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, 08 Jul 2009 07:56:08 -0000

On Jul 7, 2009, at 8:06 PM, Toni Stoev wrote:

> On Tuesday 7 July 2009 at 14:28:32 Lixia Zhang sent:
>>
>> On Jul 4, 2009, at 11:44 AM, Toni Stoev wrote:
>>
>>> Dear fellow (re)searchers,
>>>
>>> Some of the opinions expressed on the list, with positions that I
>>> share, include the concept of protocol layering.
>>> There is an alternative to that concept. It is the role-based
>>> architecture (RBA). It gives much freedom with consistency.
>>> I would like to communicate here, knowing that at least some of you
>>> know what role-based architecture is.
>>> Please, anyone interested, find the documentation of RBA and read  
>>> it.
>>> Or maybe you already know RBA.
>>> Either case, please, let me know.
>>
>> Hi Toni,
>>
>> Thanks for the msg, RBA can indeed be an interesting topic.
>> On the other hand, my understanding of the goal of this RG at this
>> time is to address routing scalability issue without requiring the
>> whole Internet moving to an entirely different architecture.
>>
>> Lixia
>
> Hi Lixia,
>
> Surely this research group is not chartered to change the packet  
> header processing model of the Internet.
> But folks are using here protocol layering concepts as routing  
> solution arguments. Meanwhile there modestly exists a role-based  
> approach.
> Are we stuck with the layering approach, or are we free to choose  
> roling.
> Let us free ourselves of this unclarity and face the real routing  
> choices.
>
> Besides routing, there is actually the need for a significantly  
> different architecture. The RBA is a fundament for such a change. A  
> few more (r)evolution aspiring concepts are needed for the change.

IAB set up a mailing list a few years back specifically for  
architecture-related discussion:
   architecture-discuss@ietf.org
   https://www.ietf.org/mailman/listinfo/architecture-discuss

FYI,
Lixia

From irtf@tonistoev.info  Wed Jul  8 13:24: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 8C3FC3A6B34 for <rrg@core3.amsl.com>; Wed,  8 Jul 2009 13:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.744,  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 ob-iLA2eYR8L for <rrg@core3.amsl.com>; Wed,  8 Jul 2009 13:24:30 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id A5E853A6846 for <rrg@irtf.org>; Wed,  8 Jul 2009 13:24: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 1MOdgd-0005rK-Vh; Wed, 08 Jul 2009 23:24:15 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: Lixia Zhang <lixia@cs.ucla.edu>
Date: Wed, 8 Jul 2009 23:24:14 +0300
User-Agent: KMail/1.9.9
References: <200907042144.23098.irtf@tonistoev.info> <200907080606.48308.irtf@tonistoev.info> <3EE20780-DB40-488D-862D-614FC5E8B986@cs.ucla.edu>
In-Reply-To: <3EE20780-DB40-488D-862D-614FC5E8B986@cs.ucla.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907082324.15263.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: 
Cc: IRTF RRG <rrg@irtf.org>
Subject: Re: [rrg] Common understanding
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, 08 Jul 2009 20:24:31 -0000

> IAB set up a mailing list a few years back specifically for  
> architecture-related discussion:
>    architecture-discuss@ietf.org
>    https://www.ietf.org/mailman/listinfo/architecture-discuss
> 
> FYI,
> Lixia
> 

Thank you very much, Lixia.

From lixia@cs.ucla.edu  Wed Jul  8 15:58:20 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 A2BC828C0DC for <rrg@core3.amsl.com>; Wed,  8 Jul 2009 15:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level: 
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=0.175,  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 gyEH-2luRxCP for <rrg@core3.amsl.com>; Wed,  8 Jul 2009 15:58:19 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id C3B7528B23E for <rrg@irtf.org>; Wed,  8 Jul 2009 15:58:19 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 3157A39E80DF; Wed,  8 Jul 2009 15:58:47 -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 3JNnyRHqcAuZ; Wed,  8 Jul 2009 15:58:43 -0700 (PDT)
Received: from [10.113.178.183] (unknown [80.187.148.112]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 7586139E80C5; Wed,  8 Jul 2009 15:58:40 -0700 (PDT)
Message-Id: <97DEA687-A2EB-4392-AF91-980B503B38A5@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Christian Vogt <christian.vogt@ericsson.com>
In-Reply-To: <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
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: Wed, 8 Jul 2009 15:58:35 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
X-Mailer: Apple Mail (2.935.3)
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: Wed, 08 Jul 2009 22:58:20 -0000

top posting:
- it is a generally accepted notion that some sort of identifier(s)  
needs to be added to the existing architecture (I'm writing up a short  
notes on my own understanding of why now, and why *not* day one)

- since god did not write us a bible on how to design networks, we  
have to learn as we go.  And one of the things I have learned from  
last 30 years: never be too sure about the future's need.  A winning  
strategy seems including the following ingredients:
   + start simple, and
   + stay flexible, keep the mind open.

Along that line of thought: we need to understand the interplay  
between address (used for routing) and this forthcoming identifier  
thing, but I would keep the focus on address/routing, not nailing down  
the exactly numbers and definitions of identifiers.

Lixia

On Jun 26, 2009, at 10:24 AM, 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 christian.vogt@ericsson.com  Wed Jul  8 19:53:06 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 1F8D73A6F64 for <rrg@core3.amsl.com>; Wed,  8 Jul 2009 19:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.561
X-Spam-Level: 
X-Spam-Status: No, score=-6.561 tagged_above=-999 required=5 tests=[AWL=0.038,  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 PO-WXx13C8ni for <rrg@core3.amsl.com>; Wed,  8 Jul 2009 19:53:05 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 4DD843A684A for <rrg@irtf.org>; Wed,  8 Jul 2009 19:53:05 -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 n692rSke022245; Wed, 8 Jul 2009 21:53:30 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 8 Jul 2009 21:53:15 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 8 Jul 2009 21:53:14 -0500
Message-Id: <6EBBB160-2DB3-466F-85D9-DAD36D8A01F9@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <97DEA687-A2EB-4392-AF91-980B503B38A5@cs.ucla.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 8 Jul 2009 19:53:13 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <97DEA687-A2EB-4392-AF91-980B503B38A5@cs.ucla.edu>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 09 Jul 2009 02:53:14.0756 (UTC) FILETIME=[677BE440:01CA0040]
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: Thu, 09 Jul 2009 02:53:06 -0000

Hi Lixia -

I certainly agree with your winning strategy.  And if you prefer not to
discuss identifiers on this mailing list, so be it.

I still would like to observe, though, that a good understanding of what
needs to be identified may prove helpful in devising the locators that
must lead to the things being identified.

This said, I do understand your impatience to bring the discussion to
the core topic of this research group.  This, in fact, reminds me of a
result from the Dagstuhl workshop in March, which the research group
didn't yet evaluate -- namely, the following set of locator properties:

- topologically sensitive

- multihoming=E2=80=90capable

- local and constant cost for topological changes

Would a discussion of these locator properties be in scope?

- Christian



On Jul 8, 2009, Lixia Zhang wrote:

> top posting:
>
> - it is a generally accepted notion that some sort of identifier(s)
>   needs to be added to the existing architecture (I'm writing up a
>   short notes on my own understanding of why now, and why *not* day
>   one)
>
> - since god did not write us a bible on how to design networks, we =20
> have
>   to learn as we go.  And one of the things I have learned from last
>   30 years: never be too sure about the future's need.  A winning
>   strategy seems including the following ingredients: + start simple,
>   and + stay flexible, keep the mind open.
>
> Along that line of thought: we need to understand the interplay =20
> between
> address (used for routing) and this forthcoming identifier thing, =20
> but I
> would keep the focus on address/routing, not nailing down the exactly
> numbers and definitions of identifiers.
>
> Lixia




From lixia@cs.ucla.edu  Thu Jul  9 05:56:45 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 808373A6C09 for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 05:56:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.024
X-Spam-Level: 
X-Spam-Status: No, score=-2.024 tagged_above=-999 required=5 tests=[AWL=0.575,  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 NThT24i6nkci for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 05:56:44 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id AED8F3A6963 for <rrg@irtf.org>; Thu,  9 Jul 2009 05:56:44 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 0D6B039E80DC; Thu,  9 Jul 2009 05:57:12 -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 FDtufenRPtb2; Thu,  9 Jul 2009 05:57:07 -0700 (PDT)
Received: from [10.113.178.133] (unknown [88.128.86.235]) by smtp.cs.ucla.edu (Postfix) with ESMTP id C65F039E80C5; Thu,  9 Jul 2009 05:57:03 -0700 (PDT)
Message-Id: <FEA19257-4947-4F39-A016-7344CD34B924@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Christian Vogt <christian.vogt@ericsson.com>
In-Reply-To: <6EBBB160-2DB3-466F-85D9-DAD36D8A01F9@ericsson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 9 Jul 2009 05:56:55 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <97DEA687-A2EB-4392-AF91-980B503B38A5@cs.ucla.edu> <6EBBB160-2DB3-466F-85D9-DAD36D8A01F9@ericsson.com>
X-Mailer: Apple Mail (2.935.3)
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: Thu, 09 Jul 2009 12:56:45 -0000

On Jul 8, 2009, at 7:53 PM, Christian Vogt wrote:

> Hi Lixia -
>
> I certainly agree with your winning strategy.  And if you prefer not =20=

> to
> discuss identifiers on this mailing list, so be it.

it is not an issue of any individual's preference.
Rather,
- this list got its own mission to accomplish;
and perhaps more importantly,
- it is unclear whether people who know more about the higher level =20
requirements on identifiers are watching this list.

agree?

> I still would like to observe, though, that a good understanding of =20=

> what
> needs to be identified may prove helpful in devising the locators that
> must lead to the things being identified.

agree on the good understanding part.
I avoid the word "locator", as what we have in hand is simply IP =20
addresses, whose basic function is to identify the attachment point of =20=

destinations to which IP packets are delivered, independent from which =20=

identifier resolved to that delivery address.

make sense?

> This said, I do understand your impatience to bring the discussion to
> the core topic of this research group.

impatience?  not sure what led to that...  maybe my poor English =20
expressions. but honest, I have all the patience:-)

my goal is trying to focus the attention on our own mission (I assume =20=

everyone still remembers that we have this March deadline for a =20
routing scalability recommendation:)

>  This, in fact, reminds me of a
> result from the Dagstuhl workshop in March, which the research group
> didn't yet evaluate -- namely, the following set of locator =20
> properties:
>
> - topologically sensitive
>
> - multihoming=E2=80=90capable
>
> - local and constant cost for topological changes
>
> Would a discussion of these locator properties be in scope?

of course.

Lixia

> On Jul 8, 2009, Lixia Zhang wrote:
>
>> top posting:
>>
>> - it is a generally accepted notion that some sort of identifier(s)
>>  needs to be added to the existing architecture (I'm writing up a
>>  short notes on my own understanding of why now, and why *not* day
>>  one)
>>
>> - since god did not write us a bible on how to design networks, we =20=

>> have
>>  to learn as we go.  And one of the things I have learned from last
>>  30 years: never be too sure about the future's need.  A winning
>>  strategy seems including the following ingredients: + start simple,
>>  and + stay flexible, keep the mind open.
>>
>> Along that line of thought: we need to understand the interplay =20
>> between
>> address (used for routing) and this forthcoming identifier thing, =20
>> but I
>> would keep the focus on address/routing, not nailing down the exactly
>> numbers and definitions of identifiers.
>>
>> Lixia
>
>
>


From lixia@cs.ucla.edu  Thu Jul  9 09:27:34 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 E909928C22F for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 09:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.078
X-Spam-Level: 
X-Spam-Status: No, score=-1.078 tagged_above=-999 required=5 tests=[AWL=-0.754, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, 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 yw3oq+UDtFS9 for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 09:27:33 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id B118F28C225 for <rrg@irtf.org>; Thu,  9 Jul 2009 09:27:33 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id AD34739E80DC; Thu,  9 Jul 2009 09:28:01 -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 lytegyyrtMyK; Thu,  9 Jul 2009 09:27:57 -0700 (PDT)
Received: from [10.113.178.133] (unknown [88.128.87.248]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 0F8CB39E80E0; Thu,  9 Jul 2009 09:27:55 -0700 (PDT)
Message-Id: <DFBCCE25-C20B-42D5-A633-9F30EF761BBF@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Patrick Frejborg <pfrejborg@gmail.com>
In-Reply-To: <5bc37fd40907020041w6daf6179g267cf9a391872802@mail.gmail.com>
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: Thu, 9 Jul 2009 09:27:52 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com> <9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com> <5bc37fd40907020041w6daf6179g267cf9a391872802@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
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: Thu, 09 Jul 2009 16:27:35 -0000

On Jul 2, 2009, at 12:41 AM, Patrick Frejborg wrote:

> Hi Christian,
>
> trying to come up with more arguments and here is an early simple
> idea, more or less a brain dump that you (all of you) should try to
> shoot down.
>
> NAPT devices have to keep track of both IP addresses and ports, the
> binding can become quite complex. But if the connection also have host
> identifiers in the header of the datagrams the NAPT box doesn't need
> to keep track of the ports - the connection can be tracked with the
> help of the host identifier.
>
> Not so interesting but it gets better if the host identifier is added
> to the DNS record. By adding a host identifier to the DNS record the
> NAPT box could accept traffic from the Internet and redirect it to the
> correct host in the private network. This can be achieved by having
> the DNS entry as the IP address with the public IP address of the NAPT
> box and the host identifier with the global unique identifier of the
> internal server. Then you create a static binding at the middlebox - a
> host identifier is binded to the internal IP address of the server.
> Now the middlebox can handle both inbound and outbound connections,
> with one public PA IP address, and still provide end-to-end visibility
> in case you need to troubleshoot sessions. Also the meaning of DNS
> changes slightly, a DNS look up tells us today "what is the local IP
> address of the server". With the host identifier added the DNS look up
> would tell us "via this attachment point at the border of Internet the
> internal host can be reached".

Patte,

Just FYI: your above description actually matches to an existing  
implementation pretty closely: Apple's Mobile.Me/BTMM (Back To My Mac).

I gave a short talk on this implementation back in February at the  
Dagstuhl Seminar on naming and addressing:
  "What to Use as Host Identifier: there is theory, and there is  
practice"
  http://www.dagstuhl.de/Materials/Files/09/09102/09102.ZhangLixia1.Slides1.pdf

- This is really Apple/Stuart Cheshire's work; I failed to get Stuart to
   attend the seminar, so I gave the talk.
- I wanted to make this work known to the community because it  
represents a
   *very* pragmatic way of adding the identifier into the pictur--it is
   running today (the claim is that BTMM got millions of users)

It may be far from perfect (I've been collecting a list of things that  
need to be improved), but seems to me a good/pragmatic starting point.

> How then to achieve multi-homing?

I'd like to clarify a bit here: there are multiple levels of  
multihoming, for example,
- site multihoming: UCLA is multihomed to multiple providers
- host multihoming: an iphone has multiple interfaces that even
   goes to different providers.
(of course there is also subnet multihoming, handled by IGP routing).

this naturally leads to the question of whether one would attempt one  
solution for all levels of multihoming, or have a separate solution  
for host multihoming, and handle site multihoming in a different way.


> If this is really doable the outcome is that PI-addresses are no
> longer attractive, you can publish services towards Internet with your
> internal addressing scheme - the routing architecture of an
> organization is an internal affair and Internet doesn't need to know
> about how it is constructed. But still external customers, partners
> etc. can reach your published services with the help of the host
> identifier.

this can be one possibility, but not the only one.
There are people out that who want PI blocks, or want to hold on their  
PI blocks.
It is because PI blocks make some part of their jobs easier.
It is not because there is something that can be theoretically proven  
impossible without PI blocks (even the need for identifier can't be  
proven this way). As I mentioned in an earlier reply, networking (both  
designs and operations) is about making a best engineering tradeoffs  
(and the criteria for "best" vary for different parties).
Isn't networking fun? :-)

Lixia






From scott.brim@gmail.com  Thu Jul  9 10:30:30 2009
Return-Path: <scott.brim@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 770383A6CBA for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 10:30:30 -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=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2]
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 aw4yKF07-E7j for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 10:30:29 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by core3.amsl.com (Postfix) with ESMTP id 49E583A6C96 for <rrg@irtf.org>; Thu,  9 Jul 2009 10:30:29 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id j4so39730wah.23 for <rrg@irtf.org>; Thu, 09 Jul 2009 10:30:56 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=FbOkHQQWZq6O08G+PLOXH2VAxyT6V84SOBGA5QCdIB0=; b=G/C5Jh4VH02auIICNkxv4tDdq2S81/4xPboyHkqqGOuyoNo7lTfU8m7FxHrdTJ/BA6 itjqAEOqHVnk9bzBEO4C0PESnkD7a74wuwgY3Ddf4FMusUWyhVVC/D78vxRjh9FAI74L LiJXATSjwdbSBusJBvD/JD60nd/TyOhxUmamM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=a1TTXGgfBTjI/KrziKMnru/OUFhn0CaL18acIJoS+thS6HNti4YWa5GqHlvS38292V fwEt3CBxpHfd/ucypz3NpVMscKgM68hQc08YG2Pi2uZ/PNX0li3dNbunKiNQ4S/EZgzV DDHXZcZ4DpHHHN92hULkIx7rWZGs+T8GVkhH8=
Received: by 10.115.108.20 with SMTP id k20mr625317wam.4.1247160656868; Thu, 09 Jul 2009 10:30:56 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id m30sm102492wag.34.2009.07.09.10.30.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 09 Jul 2009 10:30:54 -0700 (PDT)
Message-ID: <4A562945.3070408@gmail.com>
Date: Thu, 09 Jul 2009 13:30:45 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Christian Vogt <christian.vogt@ericsson.com>
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
In-Reply-To: <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 09 Jul 2009 17:30:30 -0000

It's my turn to catch up :-)

Christian Vogt allegedly wrote on 06/26/2009 1:24 PM:
> 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

First, let's avoid thinking of the Internet in client/server concepts.
"Service" has connotations of a destination that is frequently accessed,
well-known, and perhaps globally addressed.  We need to leave room for
simple personal communications.  Let's just talk about destinations.

I repeat the litany of five identifier functions :-) ...

  * for access, to use a visited network at all.

  * for initially finding something you want to talk to.  Examples would
    be domain names and SIP URIs.  These might correspond to your
    "service identification".

  * for initial contact, in order to establish sessions.  These include
    authentication and authorization identifiers.

  * for session control: initial authentication and association of
    locators with sessions, as well as re-authentication when locators
    change.

  * for referrals, whereby one endpoint tells another about yet a third.

Which of these are "essential for the Internet to function"?  I don't
see how we could get rid of any of access, search, authentication,
session control and referral.  However,

  * You might be able to use the same identifiers for different
    functions.  That is, you may be able to use the same identifier as
    input to multiple identification functions.

  * Also, a single identification function can take multiple
    identifiers.

  * Finally, different layers will repeat the same functions.  For
    example, you may have multiple authentication functions, or
    "session" control at multiple layers.

We haven't resolved the practical aspects of what might be the most
convenient way to reduce identifier count because we don't have enough
experience, so we're projecting and speculating.


Toni Stoev allegedly wrote on 06/26/2009 8:29 PM:
> Node identification provides for efficient handling of node
> multihoming, possibly dynamic, and for stable mapping of human
> readable names.

If I move a session from one device to another, or from one interface to
another, a node identifier is not enough to support session continuity.
 If I have a way to identify sessions that does support session
continuity, then a node identifier is not necessary in addition for that
purpose.  As others have said, one might want a node identifier for
management, but what we really want is a way to talk to a management
entity that claims to be responsible for the node.


Joel M. Halpern allegedly wrote on 07/03/2009 10:36 PM:
> The reason this (naming the set of locators that lead to the same 
> entity) leads to a stack ID (or node, host, something) is that I want
> that collective property available before I start communicating. 
> Referrals are the easy case. I am trying to refer someone to a
> specific entity. They do not have a session with that entity. So a
> session ID is clearly totally useless for a referral.

http://tools.ietf.org/html/draft-carpenter-behave-referral-object-00
(which we should get back to, Joel).

> I believe that similar constraints apply at the time of initial 
> communication establishment, in that there is a semantic difference 
> between using multiple locators for a target to establish
> communication and trying to establish communicaiton with multiple
> "equivalent but distinct" targets. I consider it helpful to
> udnerstand that distinction.

Of course there is but I don't see the point you're trying to make.  If
you address a letter to {my country, my town, my street, my house, me},
you are using multiple locators for a target, but are you trying to
establish communication with "equivalent but distinct" targets?
Identifiers do not all have to name the endpoints of communication; they
can also name the scope in which other (associated) identifiers are to
be interpreted.

I'm not going to say much more about whether we want a "stack ID" or
whether doing the same thing with a set of identifiers with multiple
purposes is better.  We can leave that to the market.

Stopping here for now.

... Scott


From scott.brim@gmail.com  Thu Jul  9 10:36:58 2009
Return-Path: <scott.brim@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 9687328C1F4 for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 10:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.766
X-Spam-Level: 
X-Spam-Status: No, score=-2.766 tagged_above=-999 required=5 tests=[AWL=-0.167, 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 tglvLbYOWtCi for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 10:36:57 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by core3.amsl.com (Postfix) with ESMTP id DB88D28C1E9 for <rrg@irtf.org>; Thu,  9 Jul 2009 10:36:57 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id j4so40174wah.23 for <rrg@irtf.org>; Thu, 09 Jul 2009 10:37:25 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=GeJamy6Oh+PebPxdfhnt1sgGr4QdemrUB5sNFMlVhfo=; b=vXqfYxR317JAbQvNIH/aTyZ1zj4l3gig3AbEOSzyeM3AueejG+2WGvlE1BhNYzyTK2 ghdfJdrMEziiqFX9SFJPomMzDj2NXi4tANxaIcZ5rMyzcWTSJM+Kd1C/pK8YYy5biSBZ E61+tSm/YX0Y2gm047a3+kXgGJIe7//O03bME=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Da65Wu5Qw0JwsmdxE4LRqjOjsdHgj9dgYzHpwM2uxV7Un5qR8bAkgXmHFvoIjzt/at YPinLH3AZK1FOm9J3GLTIMZ7JmPOELb7sG+WjHYWcBO0GVG5swTONjHNDtH3NghwXHyD A6aMKxBuV0VwvyvBY1FBrqRkMQ6rW5AGUhbYA=
Received: by 10.114.192.10 with SMTP id p10mr1570452waf.145.1247161045828; Thu, 09 Jul 2009 10:37:25 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id m25sm124384waf.9.2009.07.09.10.37.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 09 Jul 2009 10:37:22 -0700 (PDT)
Message-ID: <4A562ACE.3020800@gmail.com>
Date: Thu, 09 Jul 2009 13:37:18 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Patrick Frejborg <pfrejborg@gmail.com>
References: <49E559E0.2090302@tony.li>	<89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>	<5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com>	<9399349C-1EFC-4E60-B5F5-E9CCA529A738@ericsson.com> <5bc37fd40907020041w6daf6179g267cf9a391872802@mail.gmail.com>
In-Reply-To: <5bc37fd40907020041w6daf6179g267cf9a391872802@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Routing Research Group Mailing List <rrg@irtf.org>, Christian Vogt <christian.vogt@ericsson.com>
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: Thu, 09 Jul 2009 17:36:58 -0000

Patrick Frejborg allegedly wrote on 07/02/2009 3:41 AM:
> NAPT devices have to keep track of both IP addresses and ports, the
> binding can become quite complex. But if the connection also have host
> identifiers in the header of the datagrams the NAPT box doesn't need
> to keep track of the ports - the connection can be tracked with the
> help of the host identifier.

There are privacy concerns with host identifiers.  If an identifier
associated with an endpoint is persistent over a long time, regardless
of where the node might be, its behavior is easier to track and analyze.
  Session identifiers of various sorts are transient.  Even security
associations are rekeyed periodically.




From scott.brim@gmail.com  Thu Jul  9 10:38:05 2009
Return-Path: <scott.brim@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 4623328C22F for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 10:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.742
X-Spam-Level: 
X-Spam-Status: No, score=-2.742 tagged_above=-999 required=5 tests=[AWL=-0.143, 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 tn+nuFyO7t0s for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 10:38:04 -0700 (PDT)
Received: from mail-px0-f189.google.com (mail-px0-f189.google.com [209.85.216.189]) by core3.amsl.com (Postfix) with ESMTP id 96A4128C22B for <rrg@irtf.org>; Thu,  9 Jul 2009 10:38:04 -0700 (PDT)
Received: by pxi27 with SMTP id 27so191438pxi.15 for <rrg@irtf.org>; Thu, 09 Jul 2009 10:38:32 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=HZjVvjYXsg9rnINdg0GGE3yaIFG7WG7oK01E7ITii4Q=; b=sSB0pd00fr9E8d1VA8kbiyqK8pJE/1uCA3q1dXhBY8jJTe9PPI0gJcJgb6o36A4OL2 xvJwmLMvbQHqiBj2vr/3c8ikmeGscZ94sFR+Se8KTyY2pg+vHEFaoUhd/i2FNS/OpMld 9w2BMNdBjKrMAexOivNwqCfLO3Ikur8H2+Vkg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=KjqR5sNTSZJZXDiSPcUGY5+c6jcBv20udkVz1iorna77URaIuYlwdT4lcG/aVpdeEt +TxIGwNW/IWDXnICRsa0obG1haI7yMccqV4XvPBgrwcsHV4aVtfyE+2D4mSeXIxjX8G3 yfQuw+SGsBCCSw+l1N4oyJ9Rn21JU+Hk4WOgw=
Received: by 10.114.108.10 with SMTP id g10mr1590857wac.78.1247161111961; Thu, 09 Jul 2009 10:38:31 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id l28sm107065waf.54.2009.07.09.10.38.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 09 Jul 2009 10:38:30 -0700 (PDT)
Message-ID: <4A562B14.1020705@gmail.com>
Date: Thu, 09 Jul 2009 13:38:28 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Lixia Zhang <lixia@CS.UCLA.EDU>
References: <49E559E0.2090302@tony.li>	<89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>	<5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com> <081E8BA4-2222-426A-B5CE-B6712FBF1A64@CS.UCLA.EDU>
In-Reply-To: <081E8BA4-2222-426A-B5CE-B6712FBF1A64@CS.UCLA.EDU>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 09 Jul 2009 17:38:05 -0000

Lixia Zhang allegedly wrote on 07/07/2009 4:45 PM:
> In case not everyone has heard: a MPTCP BOF has been scheduled on Wed
> morning of IETF week.

It has almost certainly moved to Thursday to avoid conflict with ICCRG.

Scott

From tme@americafree.tv  Thu Jul  9 10:49:50 2009
Return-Path: <tme@americafree.tv>
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 9A94F3A6C87 for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 10:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.622
X-Spam-Level: 
X-Spam-Status: No, score=-2.622 tagged_above=-999 required=5 tests=[AWL=-0.023, 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 Of0S8rcxmGhL for <rrg@core3.amsl.com>; Thu,  9 Jul 2009 10:49:49 -0700 (PDT)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 847933A6B76 for <rrg@irtf.org>; Thu,  9 Jul 2009 10:49:49 -0700 (PDT)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 4A8E44323643; Thu,  9 Jul 2009 13:50:17 -0400 (EDT)
Message-Id: <2CD75854-6DFF-4B28-A4A9-B567D8967230@americafree.tv>
From: Marshall Eubanks <tme@americafree.tv>
To: Scott Brim <scott.brim@gmail.com>
In-Reply-To: <4A562B14.1020705@gmail.com>
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: Thu, 9 Jul 2009 13:50:16 -0400
References: <49E559E0.2090302@tony.li>	<89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com>	<5bc37fd40906300613tb522d67k27f1d0714907b201@mail.gmail.com> <081E8BA4-2222-426A-B5CE-B6712FBF1A64@CS.UCLA.EDU> <4A562B14.1020705@gmail.com>
X-Mailer: Apple Mail (2.935.3)
Cc: rrg@irtf.org, Lixia Zhang <lixia@CS.UCLA.EDU>
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: Thu, 09 Jul 2009 17:49:50 -0000

On Jul 9, 2009, at 1:38 PM, Scott Brim wrote:

> Lixia Zhang allegedly wrote on 07/07/2009 4:45 PM:
>> In case not everyone has heard: a MPTCP BOF has been scheduled on Wed
>> morning of IETF week.
>
> It has almost certainly moved to Thursday to avoid conflict with  
> ICCRG.
>

Thursday morning, according to the "Final" schedule
THURSDAY, July 30,
0900-1130 Morning Session I
Congresshall B INT l2vpn Layer 2 Virtual Private Networks WG
Cabaret INT savi Source Address Validation Improvements WG
Room 300 OPS capwap Control And Provisioning of Wireless Access Points  
WG
Room 307 RAI mediactrl Media Server Control WG
Congresshall C RAI mmusic Multiparty Multimedia Session Control WG
Small Stage RTG sidr Secure Inter-Domain Routing WG
Large Stage SEC keyprov Provisioning of Symmetric Keys WG
Congresshall A TSV mptcp Multipath TCP BOF

Marshall

> Scott
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>

Regards
Marshall Eubanks
email   : tme@americafree.tv
twitter : @TMEubanks
Cut the Cord with AmericaFree.TV






From christian.vogt@ericsson.com  Fri Jul 10 11:12:26 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 1C99E28C330 for <rrg@core3.amsl.com>; Fri, 10 Jul 2009 11:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.56
X-Spam-Level: 
X-Spam-Status: No, score=-6.56 tagged_above=-999 required=5 tests=[AWL=0.039,  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 Hit3gTGy3b+7 for <rrg@core3.amsl.com>; Fri, 10 Jul 2009 11:12:25 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 51F4728C361 for <rrg@irtf.org>; Fri, 10 Jul 2009 11:12:25 -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 n6AICoa4012450; Fri, 10 Jul 2009 13:12:50 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 10 Jul 2009 13:12:16 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 10 Jul 2009 13:12:15 -0500
Message-Id: <1C36331D-EA36-4CC5-A51A-6391CDC18D4A@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <FEA19257-4947-4F39-A016-7344CD34B924@cs.ucla.edu>
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: Fri, 10 Jul 2009 11:12:15 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <97DEA687-A2EB-4392-AF91-980B503B38A5@cs.ucla.edu> <6EBBB160-2DB3-466F-85D9-DAD36D8A01F9@ericsson.com> <FEA19257-4947-4F39-A016-7344CD34B924@cs.ucla.edu>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 10 Jul 2009 18:12:15.0627 (UTC) FILETIME=[F46AD5B0:01CA0189]
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: Fri, 10 Jul 2009 18:12:26 -0000

Lixia -

>> I certainly agree with your winning strategy.  And if you prefer  
>> not to
>> discuss identifiers on this mailing list, so be it.
>
> it is not an issue of any individual's preference. Rather,
> - this list got its own mission to accomplish;

Of course.  But keep in mind that there is a group of people in RRG who
believe that identifier-locator separation can accomplish our mission.
Devising a suitable identifier-locator separation solution, in turn,
requires some discussion of the type we were having.

> and perhaps more importantly,
> - it is unclear whether people who know more about the higher level
> requirements on identifiers are watching this list.

This may indeed be an issue, I agree.  But the conclusion from this
should be different, in my opinion.  We should motivate more good people
to participate in this discussion, not give up the discussion.

>> I still would like to observe, though, that a good understanding of  
>> what
>> needs to be identified may prove helpful in devising the locators  
>> that
>> must lead to the things being identified.
>
> agree on the good understanding part. I avoid the word "locator", as
> what we have in hand is simply IP addresses, whose basic function is  
> to
> identify the attachment point of destinations to which IP packets are
> delivered, independent from which identifier resolved to that delivery
> address.

This makes sense.  Any viable solution to the routing scalability
problem will have to use IP addresses as locators, since this is a
prerequisite for incremental deployability.

- Christian




From irtf@tonistoev.info  Fri Jul 10 22:21: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 BC9D33A672F for <rrg@core3.amsl.com>; Fri, 10 Jul 2009 22:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.961
X-Spam-Level: 
X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[AWL=0.638,  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 thHoqlJvbSUe for <rrg@core3.amsl.com>; Fri, 10 Jul 2009 22:21:24 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id D7EBC3A692B for <rrg@irtf.org>; Fri, 10 Jul 2009 22:21:23 -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 1MPV1w-0004el-2P for rrg@irtf.org; Sat, 11 Jul 2009 08:21:48 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Sat, 11 Jul 2009 08:21:46 +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: <200907110821.47414.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, 11 Jul 2009 05:21:29 -0000

Please, anyone who writes on identifiers topic, identify your empathy to:
Design Goals for Scalable Internet Routing, 3.6. Decoupling location and identification

I do care about that goal.

We have interface (node) identification with IP addresses.
It is used for node-local session identification as part of the socket.
There the IP address is an identifier of the endpoint of the inter-node communication process.
Let us extract this identification from IP addresses and have it separately.
But let us keep using the hierarchical structure for the function of authentication of identity.

End of part one
Toni

From irtf@tonistoev.info  Fri Jul 10 23:16:02 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 F035A3A6A99 for <rrg@core3.amsl.com>; Fri, 10 Jul 2009 23:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level: 
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[AWL=0.558,  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 U8VdMv+6y8G1 for <rrg@core3.amsl.com>; Fri, 10 Jul 2009 23:16:02 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 281223A6A72 for <rrg@irtf.org>; Fri, 10 Jul 2009 23:16:02 -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 1MPVsr-0002Hm-Cr for rrg@irtf.org; Sat, 11 Jul 2009 09:16:29 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Sat, 11 Jul 2009 09:16:27 +0300
User-Agent: KMail/1.9.9
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <4A562945.3070408@gmail.com>
In-Reply-To: <4A562945.3070408@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907110916.27253.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, 11 Jul 2009 06:16:03 -0000

Scott Brim wrote:
> If I move a session from one device to another, or from one interface to
> another,

Scott, a session is established with a node. You can move communication among interfaces but you keep talking to the same node.

> a node identifier is not enough to support session continuity.

A node locator, a node identifier and a node-local session instance number would do the job.

>  If I have a way to identify sessions that does support session
> continuity, then a node identifier is not necessary in addition for that
> purpose.

A node locator and a node-local session instance number are sufficient to have a session.
A node identifier is needed to move the session from one node to another.

Caught up.
Toni

From HeinerHummel@aol.com  Sat Jul 11 00:14:34 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 F2E8D3A69B9 for <rrg@core3.amsl.com>; Sat, 11 Jul 2009 00:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001]
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 DbQp5puIKPyK for <rrg@core3.amsl.com>; Sat, 11 Jul 2009 00:14:33 -0700 (PDT)
Received: from imr-ma03.mx.aol.com (imr-ma03.mx.aol.com [64.12.206.41]) by core3.amsl.com (Postfix) with ESMTP id 08EFB3A63EB for <rrg@irtf.org>; Sat, 11 Jul 2009 00:14:32 -0700 (PDT)
Received: from imo-ma01.mx.aol.com (imo-ma01.mx.aol.com [64.12.78.136]) by imr-ma03.mx.aol.com (8.14.1/8.14.1) with ESMTP id n6B7EjNi004517; Sat, 11 Jul 2009 03:14:46 -0400
Received: from HeinerHummel@aol.com by imo-ma01.mx.aol.com  (mail_out_v40_r1.5.) id t.d27.34b33cef (30740);  Sat, 11 Jul 2009 03:14:40 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <d27.34b33cef.378995e0@aol.com>
Date: Sat, 11 Jul 2009 03:14:40 EDT
To: christian.vogt@ericsson.com, lixia@cs.ucla.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1247296479"
X-Mailer: 9.0 SE for Windows sub 5021
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: Sat, 11 Jul 2009 07:14:34 -0000

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

 
In einer eMail vom 10.07.2009 20:13:18 Westeurop=E4ische Normalzeit schrei=
bt  
christian.vogt@ericsson.com:

This  makes sense.  Any viable solution to the routing scalability
problem  will have to use IP addresses as locators, since this is a
prerequisite for  incremental deployability.

-  Christian






Sorry Christian that I have a different opinion. 
At first, a locator, i.e. a location information, must be routable  
(aggregatable is something completely different) and, of course, it must=
 be  
written somewhere, e.g. into the field for destination IP address,    and/=
or 
destination MAC-address and eventually, for some transitional time, into=
  a new 
additional header. Even LISP authors emphasized that the locator  addresse=
s 
inside the LISP header could potentially make up a new  namespace. However=
 it 
is the LISP supporters' decision to use  non-routable IP addresses instead=
, 
or better said, the same IP-address-based  routing technique which produce=
d 
and produces the scalability problem.
 
Heiner
 
 

-------------------------------1247296479
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>In einer eMail vom 10.07.2009 20:13:18 Westeurop=E4ische Normalzeit=
 schreibt 
christian.vogt@ericsson.com:</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>This 
  makes sense.&nbsp; Any viable solution to the routing scalability<BR>pro=
blem 
  will have to use IP addresses as locators, since this is a<BR>prerequisi=
te for 
  incremental deployability.<BR><BR>- 
Christian<BR><BR><BR><BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>Sorry Christian that I have a different opinion. </DIV>
<DIV>At first, a locator, i.e. a location information, must be routable 
(aggregatable is something completely different) and, of course, it must=
 be 
written somewhere, e.g. into the field for destination IP address,&nbsp;&n=
bsp; 
and/or destination MAC-address and eventually, for some transitional time,=
 into 
a new additional header. Even LISP authors&nbsp;emphasized that the&nbsp;l=
ocator 
addresses inside the LISP header could potentially&nbsp;make up a new 
namespace.&nbsp;However it&nbsp;is the LISP supporters' decision to use 
non-routable IP addresses instead, or better said, the same IP-address-bas=
ed 
routing technique which produced and produces the scalability problem.</DI=
V>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1247296479--

From christian.vogt@ericsson.com  Sat Jul 11 16:40: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 411FF3A6A3D for <rrg@core3.amsl.com>; Sat, 11 Jul 2009 16:40:55 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cp8xvri8SzN8 for <rrg@core3.amsl.com>; Sat, 11 Jul 2009 16:40:54 -0700 (PDT)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by core3.amsl.com (Postfix) with ESMTP id 25BA53A6A26 for <rrg@irtf.org>; Sat, 11 Jul 2009 16:40:53 -0700 (PDT)
Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 498593B0820; Sat, 11 Jul 2009 19:41:21 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Sat, 11 Jul 2009 19:41:20 -0400
X-Sasl-enc: h+Mv9XbSOQRwrlCYjssJ/il/QHIV1NcwDZTWUJRsIfP2 1247355680
Received: from [10.0.1.2] (99-28-160-42.lightspeed.miamfl.sbcglobal.net [99.28.160.42]) by mail.messagingengine.com (Postfix) with ESMTPSA id 8E05D35D81; Sat, 11 Jul 2009 19:41:20 -0400 (EDT)
Message-Id: <82199686-E30C-4429-A1C7-2E0EECA0D3CC@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Scott Brim <Scott.Brim@gmail.com>
In-Reply-To: <4A562945.3070408@gmail.com>
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, 11 Jul 2009 16:41:19 -0700
References: <49E559E0.2090302@tony.li> <89D69449-8F86-4296-B4F8-454D8F137D3E@ericsson.com> <4A562945.3070408@gmail.com>
X-Mailer: Apple Mail (2.935.3)
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: Sat, 11 Jul 2009 23:40:55 -0000

Hi Scott -

>> 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
>
> First, let's avoid thinking of the Internet in client/server concepts.

Yes, thinking in client-server concepts would be too limiting.  And we
are not.  "Service" here is defined as a piece of communication software
that responds to incoming contact establishment attempts.  This includes
both peer-to-peer and client-server applications.  (FWIW, it also  
includes
"applications" further down the stack, such as the ICMP Echo service.)

> I repeat the litany of five identifier functions :-) ...


Many things certainly need to be identified.  But again, most identifier
types are not core elements of Internet architecture because they are
specific to certain services.  An example is host identifiers, which per
se are of use only in management applications.

Further, I would exclude authentication and authorization credentials
from the definition of identifier.  Credentials are useful to prove
ownership of an identifier, but they are not identifiers themselves.

Let me comment more specifically on your proposed five identifier types:

> * for access, to use a visited network at all.


Network access identifiers are certainly needed.  But they are specific
to the access authorization service, and exchanged only within this
service.  Also, network access identifiers are likely to be specific to
certain networks.  Hence I would not consider them core elements of
Internet architecture.

In my personal view, the core elements of Internet architecture are
those which enable you to establish communications in general, such as
with said access authorization service.  And those are service
identifiers for initial contact, and session identifiers afterwards.

> * for initially finding something you want to talk to.  Examples would
>   be domain names and SIP URIs.  These might correspond to your
>   "service identification".

Agree, these are service identifiers.

> * for initial contact, in order to establish sessions.  These include
>   authentication and authorization identifiers.

These are service identifiers as well, plus credentials.

> * for session control: initial authentication and association of
>   locators with sessions, as well as re-authentication when locators
>   change.

These are session identifiers.  Supplementary credentials may be needed
for security reasons.

> * for referrals, whereby one endpoint tells another about yet a third.


Referrals are important.  But you don't need an extra identifier for it.
Service identifiers serve this purpose already.

Reading your email further:

> However,
>
> * You might be able to use the same identifiers for different
>   functions.  That is, you may be able to use the same identifier as
>   input to multiple identification functions.
>
> * Also, a single identification function can take multiple
>   identifiers.
>
> * Finally, different layers will repeat the same functions.  For
>   example, you may have multiple authentication functions, or
>   "session" control at multiple layers.

Absolutely.  The actual identifiers used may end up being more than just
two.  E.g., we may find that the use of host identifiers as a component
in service identification has advantages engineering-wise.  This is why
we are only talking about "identification purposes" at this stage, and
not yet about actual sets of identifier types.

- Christian



From christian.vogt@ericsson.com  Sat Jul 11 16:47:11 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 E79AA3A6C11 for <rrg@core3.amsl.com>; Sat, 11 Jul 2009 16:47:11 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5zlh1XKOHqvM for <rrg@core3.amsl.com>; Sat, 11 Jul 2009 16:47:11 -0700 (PDT)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by core3.amsl.com (Postfix) with ESMTP id 2EB573A6C0E for <rrg@irtf.org>; Sat, 11 Jul 2009 16:47:11 -0700 (PDT)
Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 9A2E43B08C2; Sat, 11 Jul 2009 19:47:40 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 11 Jul 2009 19:47:40 -0400
X-Sasl-enc: zXiqB0RSpi6ghGognNTs9KJ8oIcsiGalQTzgRUCdev6Z 1247356060
Received: from [10.0.1.2] (99-28-160-42.lightspeed.miamfl.sbcglobal.net [99.28.160.42]) by mail.messagingengine.com (Postfix) with ESMTPSA id F286211A1C; Sat, 11 Jul 2009 19:47:39 -0400 (EDT)
Message-Id: <E57B786A-3AB5-42AD-A300-734532490079@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: HeinerHummel@aol.com
In-Reply-To: <d27.34b33cef.378995e0@aol.com>
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, 11 Jul 2009 16:47:23 -0700
References: <d27.34b33cef.378995e0@aol.com>
X-Mailer: Apple Mail (2.935.3)
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: Sat, 11 Jul 2009 23:47:12 -0000

Heiner -

How would map-and-encap schemes be incrementally deployable if they
didn't use IP addresses for both address realms?  Even translation-based
schemes need IP addresses as locators for backwards compatibility.

- Christian



On Jul 11, 2009, HeinerHummel@aol.com wrote:

> Sorry Christian that I have a different opinion. At first, a locator,
> i.e. a location information, must be routable (aggregatable is  
> something
> completely different) and, of course, it must be written somewhere,  
> e.g.
> into the field for destination IP address,   and/or destination
> MAC-address and eventually, for some transitional time, into a new
> additional header. Even LISP authors emphasized that the locator
> addresses inside the LISP header could potentially make up a new
> namespace. However it is the LISP supporters' decision to use
> non-routable IP addresses instead, or better said, the same
> IP-address-based routing technique which produced and produces the
> scalability problem.
>
> Heiner




From HeinerHummel@aol.com  Sun Jul 12 01:14:15 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 1BD833A6897 for <rrg@core3.amsl.com>; Sun, 12 Jul 2009 01:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.669
X-Spam-Level: 
X-Spam-Status: No, score=-1.669 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 QykoZAuQu+Xh for <rrg@core3.amsl.com>; Sun, 12 Jul 2009 01:14:14 -0700 (PDT)
Received: from imr-m08.mx.aol.com (imr-m08.mx.aol.com [64.12.138.210]) by core3.amsl.com (Postfix) with ESMTP id CE9263A67DB for <rrg@irtf.org>; Sun, 12 Jul 2009 01:14:04 -0700 (PDT)
Received: from imo-ma04.mx.aol.com (imo-ma04.mx.aol.com [64.12.78.139]) by imr-m08.mx.aol.com (v107.10) with ESMTP id RELAYIN2-34a599b66375; Sun, 12 Jul 2009 04:14:30 -0400
Received: from HeinerHummel@aol.com by imo-ma04.mx.aol.com  (mail_out_v40_r1.5.) id t.d27.34c74e5d (29678);  Sun, 12 Jul 2009 04:14:28 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <d27.34c74e5d.378af564@aol.com>
Date: Sun, 12 Jul 2009 04:14:28 EDT
To: christian.vogt@ericsson.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1247386468"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-IP: 64.12.78.139
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: Sun, 12 Jul 2009 08:14:15 -0000

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

In einer eMail vom 12.07.2009 01:47:45 Westeurop=E4ische Normalzeit schrei=
bt  
christian.vogt@ericsson.com:

Heiner  -

How would map-and-encap schemes be incrementally deployable if  they
didn't use IP addresses for both address realms?  Even  translation-based
schemes need IP addresses as locators for backwards  compatibility.

- Christian



Let's put it differently: Incremental deployability requires still BGP  to=
 
overcome the main function of BGP which is the non-scalable way to  
disseminate all these hundred thousands of prefixes.
The methods are not new: Remember  BGP-based dissemination of MPLS-VPN  
sites (just lacking the goal to build ONE SINGLE "internet-VPN") : here th=
e  
information are labels, i.e. not IP addresses. Also remember LISP's defaul=
t  
mapper. Issueing a prefix of length 0 might attract traffic destined  for=
 a 
node which doesn't propagate its traditional reachability prefixes anymore=
  
but just new routing info for a new architecture, analogously to the  
MPLS-labels.
 
Heiner



On Jul 11, 2009, HeinerHummel@aol.com wrote:

> Sorry  Christian that I have a different opinion. At first, a locator,
> i.e. a  location information, must be routable (aggregatable is  
>  something
> completely different) and, of course, it must be written  somewhere,  
> e.g.
> into the field for destination IP  address,   and/or destination
> MAC-address and eventually,  for some transitional time, into a new
> additional header. Even LISP  authors emphasized that the locator
> addresses inside the LISP header  could potentially make up a new
> namespace. However it is the LISP  supporters' decision to use
> non-routable IP addresses instead, or  better said, the same
> IP-address-based routing technique which  produced and produces the
> scalability problem.
>
>  Heiner







-------------------------------1247386468
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>In einer eMail vom 12.07.2009 01:47:45 Westeurop=E4ische Normalzeit=
 schreibt 
christian.vogt@ericsson.com:</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>Heiner 
  -<BR><BR>How would map-and-encap schemes be incrementally deployable if=
 
  they<BR>didn't use IP addresses for both address realms?&nbsp; Even 
  translation-based<BR>schemes need IP addresses as locators for backwards=
 
  compatibility.<BR><BR>- Christian<BR><BR></FONT></BLOCKQUOTE>
<DIV>&nbsp;</DIV>
<DIV>Let's put it differently: Incremental deployability requires&nbsp;sti=
ll BGP 
to overcome the main function of BGP which is the non-scalable way to 
disseminate all these hundred thousands of prefixes.</DIV>
<DIV>The methods are not new: Remember &nbsp;BGP-based dissemination of MP=
LS-VPN 
sites (just lacking the goal to build ONE SINGLE "internet-VPN") : here th=
e 
information are labels, i.e. not IP addresses. Also remember LISP's defaul=
t 
mapper.&nbsp;Issueing a prefix of length 0&nbsp;might attract traffic dest=
ined 
for a node which doesn't propagate its traditional reachability prefixes=
 anymore 
but just new routing info for a new architecture, analogously to the 
MPLS-labels.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</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 
  size=3D2><BR><BR>On Jul 11, 2009, HeinerHummel@aol.com wrote:<BR><BR>&gt=
; Sorry 
  Christian that I have a different opinion. At first, a locator,<BR>&gt;=
 i.e. a 
  location information, must be routable (aggregatable is&nbsp; <BR>&gt;=
 
  something<BR>&gt; completely different) and, of course, it must be writt=
en 
  somewhere,&nbsp; <BR>&gt; e.g.<BR>&gt; into the field for destination IP=
 
  address,&nbsp;&nbsp; and/or destination<BR>&gt; MAC-address and eventual=
ly, 
  for some transitional time, into a new<BR>&gt; additional header. Even=
 LISP 
  authors emphasized that the locator<BR>&gt; addresses inside the LISP he=
ader 
  could potentially make up a new<BR>&gt; namespace. However it is the LIS=
P 
  supporters' decision to use<BR>&gt; non-routable IP addresses instead,=
 or 
  better said, the same<BR>&gt; IP-address-based routing technique which=
 
  produced and produces the<BR>&gt; scalability problem.<BR>&gt;<BR>&gt;=
 
  Heiner<BR><BR><BR><BR></FONT></BLOCKQUOTE>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1247386468--

From xuxh@huawei.com  Sun Jul 12 20:10:22 2009
Return-Path: <xuxh@huawei.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 39C0E3A6C37 for <rrg@core3.amsl.com>; Sun, 12 Jul 2009 20:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.25
X-Spam-Level: **
X-Spam-Status: No, score=2.25 tagged_above=-999 required=5 tests=[AWL=2.060, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45]
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 lQ8yajt5-sRD for <rrg@core3.amsl.com>; Sun, 12 Jul 2009 20:10:21 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 55AFB3A6C36 for <rrg@irtf.org>; Sun, 12 Jul 2009 20:10:21 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KMP004HKA5R11@szxga04-in.huawei.com> for rrg@irtf.org; Mon, 13 Jul 2009 11:10:40 +0800 (CST)
Received: from x41208a ([10.111.12.94]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KMP00C45A5ROS@szxga04-in.huawei.com> for rrg@irtf.org; Mon, 13 Jul 2009 11:10:39 +0800 (CST)
Date: Mon, 13 Jul 2009 11:10:36 +0800
From: Xu Xiaohu <xuxh@huawei.com>
To: 'IRTF RRG' <rrg@irtf.org>
Message-id: <009301ca0367$7fe32d70$5e0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Thread-index: AcoDZJCJh0FK5084Tuujy37BHFEMawAASA0g
Subject: Re: [rrg] New Version Notification for draft-xu-rangi-01
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, 13 Jul 2009 03:10:22 -0000

Hi all,

I have just submitted the updated version of draft-xu-rangi which =
describes
an id/locator split based routing and addressing architecture. The major
changes from the -00 version are as follows:

1. Refine the structure of the host identifier.
In order to distinguish identifiers from locators (IPv6 addresses) in =
the
transition mechanisms [RANGI-PROXY], identifiers use a specific prefix,
which is to be allocated from the IPv6 address space by IANA. Hence, =
several
leftmost bits in the AD ID field should be reserved for this purpose.

2. Several editorial modifications.

3. Author-list updated.

Any comments are appreciated.

Xiaohu
   =20

> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> =B7=A2=BC=FE=C8=CB: IETF I-D Submission Tool =
[mailto:idsubmission@ietf.org]=20
> =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA7=D4=C213=C8=D5 10:48
> =CA=D5=BC=FE=C8=CB: xuxh@huawei.com
> =D6=F7=CC=E2: New Version Notification for draft-xu-rangi-01
>=20
>=20
> A new version of I-D, draft-xu-rangi-01.txt has been=20
> successfuly submitted by Xiaohu Xu and posted to the IETF repository.
>=20
> Filename:	 draft-xu-rangi
> Revision:	 01
> Title:		 Routing Architecture for the Next=20
> Generation Internet (RANGI)
> Creation_date:	 2009-07-13
> WG ID:		 Independent Submission
> Number_of_pages: 15
>=20
> Abstract:
> IRTF Routing Research Group (RRG) is exploring a new routing=20
> and addressing architecture to address the issues with the=20
> current Internet, e.g., mobility, multi-homing, traffic=20
> engineering, and especially the routing scalability. This=20
> document describes a new identifier (ID)/locator split based=20
> routing and addressing architecture, called Routing=20
> Architecture for the Next Generation Internet (RANGI), in an=20
> attempt to deal with the above problems.
>                                                              =20
>                    =20
>=20
>=20
> The IETF Secretariat.
>=20
>=20


From xuxh@huawei.com  Sun Jul 12 20:41:06 2009
Return-Path: <xuxh@huawei.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 2A1BD3A6C54 for <rrg@core3.amsl.com>; Sun, 12 Jul 2009 20:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.563
X-Spam-Level: *
X-Spam-Status: No, score=1.563 tagged_above=-999 required=5 tests=[AWL=1.373,  BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45]
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 oJAFQ1hmU+lh for <rrg@core3.amsl.com>; Sun, 12 Jul 2009 20:41:05 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 44F873A6BD7 for <rrg@irtf.org>; Sun, 12 Jul 2009 20:41:05 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KMP004R5BL911@szxga04-in.huawei.com> for rrg@irtf.org; Mon, 13 Jul 2009 11:41:33 +0800 (CST)
Received: from x41208a ([10.111.12.94]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KMP00ML8BL9AF@szxga04-in.huawei.com> for rrg@irtf.org; Mon, 13 Jul 2009 11:41:33 +0800 (CST)
Date: Mon, 13 Jul 2009 11:41:33 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <20090713024805.118F63A69A6@core3.amsl.com>
To: 'IRTF RRG' <rrg@irtf.org>
Message-id: <009401ca036b$d10218c0$5e0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Thread-index: AcoDZGzFOCUVdKrQRDeVykxGPcfwDgAAxoTQ
Subject: Re: [rrg] New Version Notification for draft-xu-rangi-proxy-01
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, 13 Jul 2009 03:41:06 -0000

Hi all,

A updated version of draft-xu-rangi-proxy has just been submitted. This
document describes some transition mechanisms for the RANGI (Routing
Architecture for the Next Generation Internet) . The major changes from =
the
-00 version are as follows:

1. Except of the site proxy mechanism defined in the -00 version,  a =
transit
proxy mechanism is introduced to support communications from legacy IPv6
hosts to RANGI hosts in the scenario where the legacy site network has =
not
yet deployed any site proxy.  With this mechanism, the transit proxies =
are
deployed in the transit networks by ISPs and the identifier-based =
routing is
also supported in the transit netwroks. To some extent, the transit =
proxy is
similar to the APR in the VA
(http://tools.ietf.org/html/draft-ietf-grow-va-00) and the PTR in the =
LISP.

2.  For RANGI hosts to initiate communications with the legacy hosts in =
the
above scenario, the RANGI hosts will establish sessions in the =
traditional
IPv6 fashion once they recognizes that the identifiers of the =
destination
hosts are IPv6 addresses (i.e. locators).

3. Some editorial updates.

Any comments are welcome.

Xiaohu
=20

> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> =B7=A2=BC=FE=C8=CB: IETF I-D Submission Tool =
[mailto:idsubmission@ietf.org]=20
> =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA7=D4=C213=C8=D5 10:48
> =CA=D5=BC=FE=C8=CB: xuxh@huawei.com
> =D6=F7=CC=E2: New Version Notification for draft-xu-rangi-proxy-01
>=20
>=20
> A new version of I-D, draft-xu-rangi-proxy-01.txt has been=20
> successfuly submitted by Xiaohu Xu and posted to the IETF repository.
>=20
> Filename:	 draft-xu-rangi-proxy
> Revision:	 01
> Title:		 Transition Mechanisms for Routing=20
> Architecture for the Next Generation Internet (RANGI)
> Creation_date:	 2009-07-13
> WG ID:		 Independent Submission
> Number_of_pages: 9
>=20
> Abstract:
> The Routing Architecture for the Next Generation Internet=20
> (RANGI) described in [RANGI] is a proposal for solving=20
> routing scalability, mobility, multihoming, traffic=20
> engineering and other issues facing the current Internet.=20
> This document describes some transition mechanisms for the=20
> RANGI. With these mechanisms, legacy IPv4 and IPv6 hosts can=20
> communicate with RANGI hosts, and vice versa.
>                                                              =20
>                    =20
>=20
>=20
> The IETF Secretariat.
>=20
>=20


From xuxh@huawei.com  Sun Jul 12 21:16:08 2009
Return-Path: <xuxh@huawei.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 1020E3A68CB for <rrg@core3.amsl.com>; Sun, 12 Jul 2009 21:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.694
X-Spam-Level: ****
X-Spam-Status: No, score=4.694 tagged_above=-999 required=5 tests=[AWL=-2.445,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339,  FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3,  MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1, SARE_SUB_ENC_GB2312=1.345]
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 fQyPXjIAlT9D for <rrg@core3.amsl.com>; Sun, 12 Jul 2009 21:16:07 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 2392F3A6842 for <rrg@irtf.org>; Sun, 12 Jul 2009 21:16:07 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KMP003R6D7ECF@szxga02-in.huawei.com> for rrg@irtf.org; Mon, 13 Jul 2009 12:16:26 +0800 (CST)
Received: from x41208a ([10.111.12.94]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KMP00E6QD7ESZ@szxga02-in.huawei.com> for rrg@irtf.org; Mon, 13 Jul 2009 12:16:26 +0800 (CST)
Date: Mon, 13 Jul 2009 12:16:25 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <009301ca0367$7fe32d70$5e0c6f0a@china.huawei.com>
To: 'Xu Xiaohu' <xuxh@huawei.com>, 'IRTF RRG' <rrg@irtf.org>
Message-id: <009601ca0370$b05484f0$5e0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Thread-index: AcoDZJCJh0FK5084Tuujy37BHFEMawAASA0gAAK2RCA=
Subject: [rrg] =?gb2312?b?ILTwuLQ6ICBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9y?= =?gb2312?b?IGRyYWZ0LXh1LXJhbmdpLTAx?=
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, 13 Jul 2009 04:16:08 -0000

The link is attached. =
http://www.ietf.org/internet-drafts/draft-xu-rangi-01.
txt=20

Xiaohu

> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> =B7=A2=BC=FE=C8=CB: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] =
=B4=FA=B1=ED Xu Xiaohu
> =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA7=D4=C213=C8=D5 11:11
> =CA=D5=BC=FE=C8=CB: 'IRTF RRG'
> =D6=F7=CC=E2: Re: [rrg] New Version Notification for draft-xu-rangi-01
>=20
> Hi all,
>=20
> I have just submitted the updated version of draft-xu-rangi=20
> which describes an id/locator split based routing and=20
> addressing architecture. The major changes from the -00=20
> version are as follows:
>=20
> 1. Refine the structure of the host identifier.
> In order to distinguish identifiers from locators (IPv6=20
> addresses) in the transition mechanisms [RANGI-PROXY],=20
> identifiers use a specific prefix, which is to be allocated=20
> from the IPv6 address space by IANA. Hence, several leftmost=20
> bits in the AD ID field should be reserved for this purpose.
>=20
> 2. Several editorial modifications.
>=20
> 3. Author-list updated.
>=20
> Any comments are appreciated.
>=20
> Xiaohu
>    =20
>=20
> > -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> > =B7=A2=BC=FE=C8=CB: IETF I-D Submission Tool =
[mailto:idsubmission@ietf.org]
> > =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA7=D4=C213=C8=D5 10:48
> > =CA=D5=BC=FE=C8=CB: xuxh@huawei.com
> > =D6=F7=CC=E2: New Version Notification for draft-xu-rangi-01
> >=20
> >=20
> > A new version of I-D, draft-xu-rangi-01.txt has been successfuly=20
> > submitted by Xiaohu Xu and posted to the IETF repository.
> >=20
> > Filename:	 draft-xu-rangi
> > Revision:	 01
> > Title:		 Routing Architecture for the Next=20
> > Generation Internet (RANGI)
> > Creation_date:	 2009-07-13
> > WG ID:		 Independent Submission
> > Number_of_pages: 15
> >=20
> > Abstract:
> > IRTF Routing Research Group (RRG) is exploring a new routing and=20
> > addressing architecture to address the issues with the current=20
> > Internet, e.g., mobility, multi-homing, traffic engineering, and=20
> > especially the routing scalability. This document describes a new=20
> > identifier (ID)/locator split based routing and addressing=20
> > architecture, called Routing Architecture for the Next Generation=20
> > Internet (RANGI), in an attempt to deal with the above problems.
> >                                                              =20
> >                    =20
> >=20
> >=20
> > The IETF Secretariat.
> >=20
> >=20
>=20
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>=20


From scott.brim@gmail.com  Mon Jul 13 11:02:19 2009
Return-Path: <scott.brim@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 9903A3A6858 for <rrg@core3.amsl.com>; Mon, 13 Jul 2009 11:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level: 
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=0.117,  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 Kb50ot7uv4yT for <rrg@core3.amsl.com>; Mon, 13 Jul 2009 11:02:18 -0700 (PDT)
Received: from mail-pz0-f195.google.com (mail-pz0-f195.google.com [209.85.222.195]) by core3.amsl.com (Postfix) with ESMTP id 005F928C0FF for <rrg@irtf.org>; Mon, 13 Jul 2009 11:01:41 -0700 (PDT)
Received: by pzk33 with SMTP id 33so1836524pzk.15 for <rrg@irtf.org>; Mon, 13 Jul 2009 11:02:12 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=7iWuzOUJav+WPTSQeg5OrDPo5nZ6PauzDJ8/9pOwiP0=; b=icBB/adS8cpPE4P26vxceJZ3AE8tdwwzOaoWb3AxYZNHdhCft3R1YyV9OEuEKixm/m 9H6trSS+mN4iMJ2Se//0SkaQpgtizbwyN9Asch9yg/1ih05pd3q5/Ge/iGAXoyn9Ib1j KuZWmav+PbfK3tRXIslnNN/EMcFUHzDke631A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=jZbCEHhDHcs+UJkdj8HRr6HxZJOhPvRCOqDbpbweYk9SwiBbI0Dzo1mhmUQOuWjvI4 UmCKk6G4w1M3fAHrCbELoS7a98UNDAC0qyMRU019dwMMkEP0QX/uFGtRDlybQw2We/S4 WAmUhfbZkUQYhfM8TYWLhViTzPnYVIPUiI1fs=
Received: by 10.115.58.1 with SMTP id l1mr9348679wak.106.1247508132151; Mon, 13 Jul 2009 11:02:12 -0700 (PDT)
Received: from sbrim-mbp.local (cpe-67-241-43-66.twcny.res.rr.com [67.241.43.66]) by mx.google.com with ESMTPS id j31sm9163303waf.68.2009.07.13.11.02.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 13 Jul 2009 11:02:10 -0700 (PDT)
Message-ID: <4A5B76A0.8090200@gmail.com>
Date: Mon, 13 Jul 2009 14:02:08 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Toni Stoev <irtf@tonistoev.info>
References: <200907110821.47414.irtf@tonistoev.info>
In-Reply-To: <200907110821.47414.irtf@tonistoev.info>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 13 Jul 2009 18:02:19 -0000

Toni Stoev allegedly wrote on 07/11/2009 1:21 AM:
> Please, anyone who writes on identifiers topic, identify your empathy to:
> Design Goals for Scalable Internet Routing, 3.6. Decoupling location and identification
> 
> I do care about that goal.

Of course.

> We have interface (node) identification with IP addresses.
> It is used for node-local session identification as part of the socket.
> There the IP address is an identifier of the endpoint of the inter-node communication process.

Please let me know if I am paraphrasing you correctly:

  - an IP address identifies an interface
  - identifying an interface is the same as identifying a node
  - an IP address is part of the identification of a session endpoint

IMHO an IP address can be part of the set of identifiers you use for
_initial_ contact, to establish a session in the first place (this is
the "stack ID" discussion).  However, you want a session to be able to
run over more than one interface, so you quickly want to decouple
identifiers used for session continuity from any interface identifiers.

> Let us extract this identification from IP addresses and have it separately.
> But let us keep using the hierarchical structure for the function of authentication of identity.

If I understand correctly, you are saying that the set of {IP address,
port, protocol} can be used as input to authentication.  For
authentication you generally need a trusted third party and identifiers
that third party understands.


Toni Stoev allegedly wrote on 07/11/2009 2:16 AM:
> Scott Brim wrote:
>> If I move a session from one device to another, or from one
>> interface to another,
> 
> Scott, a session is established with a node. You can move
> communication among interfaces but you keep talking to the same node.

A session is established between communicating entities; those entities
may move from node to node.  Don't forget about virtualization.

>> a node identifier is not enough to support session continuity.
> 
> A node locator, a node identifier and a node-local session instance
> number would do the job.

You don't want identifiers used for session continuity to be required to
change just because a node changes its identifiers.  The local session
instance identifier is the only one of these that may work for you.

>> If I have a way to identify sessions that does support session 
>> continuity, then a node identifier is not necessary in addition for
>> that purpose.
> 
> A node locator and a node-local session instance number are
> sufficient to have a session. A node identifier is needed to move the
> session from one node to another.

Now I'm confused.

From christian.vogt@ericsson.com  Tue Jul 14 10:48:13 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 35EBA28C1A0 for <rrg@core3.amsl.com>; Tue, 14 Jul 2009 10:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level: 
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038,  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 0YiB7wGBEPQP for <rrg@core3.amsl.com>; Tue, 14 Jul 2009 10:48:12 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 6D03128C324 for <rrg@irtf.org>; Tue, 14 Jul 2009 10:48:12 -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 n6EHkxKT025935; Tue, 14 Jul 2009 12:47:01 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 14 Jul 2009 12:45:50 -0500
Received: from [155.53.229.43] ([155.53.229.43]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 14 Jul 2009 12:45:50 -0500
Message-Id: <5BE2926C-5979-45C1-BB66-011D86AEBC4B@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: HeinerHummel@aol.com
In-Reply-To: <d27.34c74e5d.378af564@aol.com>
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, 14 Jul 2009 10:45:49 -0700
References: <d27.34c74e5d.378af564@aol.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 14 Jul 2009 17:45:50.0144 (UTC) FILETIME=[ED0C5400:01CA04AA]
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, 14 Jul 2009 17:48:13 -0000

On Jul 12, 2009, HeinerHummel@aol.com wrote:

> Let's put it differently: Incremental deployability requires still BGP
> to overcome the main function of BGP which is the non-scalable way to
> disseminate all these hundred thousands of prefixes. The methods are  
> not
> new: Remember  BGP-based dissemination of MPLS-VPN sites (just lacking
> the goal to build ONE SINGLE "internet-VPN") : here the information  
> are
> labels, i.e. not IP addresses. Also remember LISP's default mapper.
> Issueing a prefix of length 0 might attract traffic destined for a  
> node
> which doesn't propagate its traditional reachability prefixes anymore
> but just new routing info for a new architecture, analogously to the
> MPLS-labels.


Heiner -

I agree with the argument that IP addresses could theoretically be
replaced in their role of locators.  Although I would add that the
feasibility of this heavily depends on the deployment model:

LISP proxies are not a good example because they require IP addresses
as locators to route packets towards a proxy.  On the other hand, APT's
deployment model -- which calls for initial local deployment and
subsequent expansion -- could facilitate the introduction of new
locators.  Of course, those new locators would have to be suitable for
use across administratively discontinuous providers, like IP addresses.

- Christian



From HeinerHummel@aol.com  Tue Jul 14 13:25:46 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 C6D093A6826 for <rrg@core3.amsl.com>; Tue, 14 Jul 2009 13:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.841
X-Spam-Level: 
X-Spam-Status: No, score=-0.841 tagged_above=-999 required=5 tests=[AWL=1.757,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 DAbDq67KWnbz for <rrg@core3.amsl.com>; Tue, 14 Jul 2009 13:25:45 -0700 (PDT)
Received: from imr-m06.mx.aol.com (imr-m06.mx.aol.com [64.12.138.200]) by core3.amsl.com (Postfix) with ESMTP id 4E02A3A67D3 for <rrg@irtf.org>; Tue, 14 Jul 2009 13:25:44 -0700 (PDT)
Received: from imo-da01.mx.aol.com (imo-da01.mx.aol.com [205.188.169.199]) by imr-m06.mx.aol.com (v107.10) with ESMTP id RELAYIN3-44a5ce9872ed; Tue, 14 Jul 2009 16:24:39 -0400
Received: from HeinerHummel@aol.com by imo-da01.mx.aol.com  (mail_out_v40_r1.5.) id t.c0f.534d1450 (39955);  Tue, 14 Jul 2009 16:25:01 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <c0f.534d1450.378e439d@aol.com>
Date: Tue, 14 Jul 2009 16:25:01 EDT
To: christian.vogt@ericsson.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1247603101"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-IP: 205.188.169.199
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, 14 Jul 2009 20:25:46 -0000

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

In einer eMail vom 14.07.2009 19:47:16 Westeurop=E4ische Normalzeit schrei=
bt  
christian.vogt@ericsson.com:

On Jul  12, 2009, HeinerHummel@aol.com wrote:

> Let's put it differently:  Incremental deployability requires still BGP
> to overcome the main  function of BGP which is the non-scalable way to
> disseminate all these  hundred thousands of prefixes. The methods are =
 
> not
> new:  Remember  BGP-based dissemination of MPLS-VPN sites (just lacking
>  the goal to build ONE SINGLE "internet-VPN") : here the information  =
 
> are
> labels, i.e. not IP addresses. Also remember LISP's  default mapper.
> Issueing a prefix of length 0 might attract traffic  destined for a  
> node
> which doesn't propagate its  traditional reachability prefixes anymore
> but just new routing info  for a new architecture, analogously to the
>  MPLS-labels.


Heiner -

I agree with the argument that IP  addresses could theoretically be
replaced in their role of locators.   Although I would add that the
feasibility of this heavily depends on the  deployment model:
Absolutely. The model must a) work, b) be incrementally deployable and c)=
  
solve all the problems that are due to the state-of-art though bad 
architecture:  abolish the scalability problem (even if the internet were=
 a millions 
times  bigger),overcome the IPv4 address depletion issue, cater for 
multihoming,  make Moore's law  become applicable and finally  enable much=
 better TE 
 by also providing the view to the rear ( who else would use THIS router=
 
for  transit to get to some destination down in the forward direction.)
I wouldn't emphasize all these  objectives if my model didn't  enable them=
 
:-)

LISP proxies are not a good example because they require IP  addresses
as locators to route packets towards a proxy.  On the other  hand, APT's
deployment model -- which calls for initial local deployment  and
subsequent expansion -- could facilitate the introduction of  new
locators.  Of course, those new locators would have to be suitable  for
use across administratively discontinuous providers, like IP  addresses.
 
LISP is an attempt to rescue the existing model and the existing  
paradigms.(called jack-up model)
While most people praise the existing paradigms and e.g. think that  
caching is a nice enhancement thereof  I rather believe that caching is a=
  
built-in repair system of an old/bad architecture from the start.
 
Heiner
 


- Christian






-------------------------------1247603101
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 content=3D"text/html; charset=3DISO-8859-1" http-equiv=3DContent-Typ=
e>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18783"></HEAD>
<BODY style=3D"FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=3Dr=
ole_body 
bottomMargin=3D7 leftMargin=3D7 rightMargin=3D7 topMargin=3D7><FONT id=3Dr=
ole_document 
color=3D#000000 size=3D2 face=3DArial>
<DIV>In einer eMail vom 14.07.2009 19:47:16 Westeurop=E4ische Normalzeit=
 schreibt 
christian.vogt@ericsson.com:</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=3D=
Arial>On Jul 
  12, 2009, HeinerHummel@aol.com wrote:<BR><BR>&gt; Let's put it different=
ly: 
  Incremental deployability requires still BGP<BR>&gt; to overcome the mai=
n 
  function of BGP which is the non-scalable way to<BR>&gt; disseminate all=
 these 
  hundred thousands of prefixes. The methods are&nbsp; <BR>&gt; not<BR>&gt=
; new: 
  Remember&nbsp; BGP-based dissemination of MPLS-VPN sites (just lacking<B=
R>&gt; 
  the goal to build ONE SINGLE "internet-VPN") : here the information&nbsp=
; 
  <BR>&gt; are<BR>&gt; labels, i.e. not IP addresses. Also remember LISP's=
 
  default mapper.<BR>&gt; Issueing a prefix of length 0 might attract traf=
fic 
  destined for a&nbsp; <BR>&gt; node<BR>&gt; which doesn't propagate its=
 
  traditional reachability prefixes anymore<BR>&gt; but just new routing=
 info 
  for a new architecture, analogously to the<BR>&gt; 
  MPLS-labels.<BR><BR><BR>Heiner -<BR><BR>I agree with the argument that=
 IP 
  addresses could theoretically be<BR>replaced in their role of locators.&=
nbsp; 
  Although I would add that the<BR>feasibility of this heavily depends on=
 the 
  deployment model:</FONT></BLOCKQUOTE>
<DIV>Absolutely. The model must a) work, b) be incrementally deployable an=
d c) 
solve all the problems that are due to the state-of-art though bad archite=
cture: 
abolish the scalability problem (even if the internet were a millions time=
s 
bigger),overcome the IPv4 address depletion issue,&nbsp;cater for multihom=
ing, 
make Moore's law&nbsp; become applicable and finally&nbsp; enable much bet=
ter TE 
by also providing the view to the rear ( who else would use THIS router fo=
r 
transit to get to some destination down in the forward direction.)</DIV>
<DIV>I wouldn't emphasize all these&nbsp;&nbsp;objectives if my model didn=
't 
enable them :-)<FONT style=3D"BACKGROUND-COLOR: transparent" color=3D#0000=
00 size=3D2 
face=3DArial><BR><BR>LISP proxies are not a good example because they requ=
ire IP 
addresses<BR>as locators to route packets towards a proxy.&nbsp; On the ot=
her 
hand, APT's<BR>deployment model -- which calls for initial local deploymen=
t 
and<BR>subsequent expansion -- could facilitate the introduction of 
new<BR>locators.&nbsp; Of course, those new locators would have to be suit=
able 
for<BR>use across administratively discontinuous providers, like IP 
addresses.</FONT></DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D=
2 
face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D=
2 
face=3DArial>LISP is an attempt to rescue the existing model and the exist=
ing 
paradigms.(called jack-up model)</FONT></DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D=
2 
face=3DArial>While most people praise the existing paradigms and e.g. thin=
k that 
caching is a nice enhancement thereof &nbsp;I rather believe that caching=
 is a 
built-in repair system of an old/bad architecture from the start.</FONT></=
DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D=
2 
face=3DArial>&nbsp;</DIV>
<DIV><BR><BR>- Christian<BR><BR><BR></DIV></FONT>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1247603101--

From phdgang@gmail.com  Tue Jul 14 20:21:44 2009
Return-Path: <phdgang@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 AD0DA3A6945 for <rrg@core3.amsl.com>; Tue, 14 Jul 2009 20:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.407
X-Spam-Level: 
X-Spam-Status: No, score=-1.407 tagged_above=-999 required=5 tests=[AWL=1.191,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 1M4wkxdXXdEI for <rrg@core3.amsl.com>; Tue, 14 Jul 2009 20:21:43 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by core3.amsl.com (Postfix) with ESMTP id B8C903A69A7 for <rrg@irtf.org>; Tue, 14 Jul 2009 20:21:43 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 24so1118636wfg.7 for <rrg@irtf.org>; Tue, 14 Jul 2009 20:20:58 -0700 (PDT)
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=RkED7Ip/ourmqskOHF5dGBOz6zD/iNXP+Xgr2DhuJas=; b=oktgETEqnIIzupu1+cq12Vm6X5yji2Lp3CrFvc0ZLnhGt1s/GhqGLEgQ00vE/pWgmc mR5spRvBOT0+49cy+D2HfdT1QWhPWnfFgKx1xJDLSH1svRPK2GbsEeA9cXuBKr26dHlU IaskpINkW4MTgwqc14kqz1cPXUkfesEwkO5Q4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=GI5NnCQll4Ej1ra2q4h0xcYuRbr7HKHqIMTvzOvGgAy88HH60h8pcqETtfA1dqUrPs sfqisf71qpi93gNHDoO7mGaYSnT95G4l/rE6EtGpjQyI4NP+muRFP99AdeJ6Bzlw9BsD M6qH3DJbVDo+mvs3wHGhvdBtnqqWMuNJF2PZs=
MIME-Version: 1.0
Received: by 10.142.13.13 with SMTP id 13mr1718434wfm.276.1247628058482; Tue,  14 Jul 2009 20:20:58 -0700 (PDT)
Date: Wed, 15 Jul 2009 11:20:58 +0800
Message-ID: <36ba02b00907142020p91c7200xe42e1f150524c146@mail.gmail.com>
From: Chen Gang <phdgang@gmail.com>
To: rrg@irtf.org
Content-Type: multipart/alternative; boundary=000e0cd5097a3cda14046eb60bb0
Subject: [rrg] An Incremental Deployable Mapping Service Draft
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, 15 Jul 2009 03:21:44 -0000

--000e0cd5097a3cda14046eb60bb0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hello all,

We have posted a new draft which has proposed an incremental deplyable
mapping service based DHT overlay network.
Please kindly review it.
Any comment is welcome.

Thanks

-Gang

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
       Title           : An Incremental Deployable Mapping Service for
Scalable Routing Architecture
       Author(s)       : G. Chen, et al.
       Filename        : draft-chen-lisp-er-mo-01.txt
       Pages           : 20
       Date            : 2009-07-12
This document describes a mechanism of providing mapping service for
LISP-like architecture.  The mapping service comprises of EID Router
(ER) mechanism and supplementary DHT Mapping Overlay (MO), in which
ER mechanism is for reducing forwarding entries in routers while
driving the packets to the destination through tunnels, and the DHT
MO serves as a supplement that provides specific mappings to reduce
the number of tunnels.  The mechanism is flexibly deployable for ISPs
since it costs little and is easy to progress.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-chen-lisp-er-mo-01.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

<div>Hello all,<br>=A0<br>We have posted a new draft which has proposed an =
incremental deplyable mapping service based DHT overlay network.<br>Please =
kindly review it.<br>Any comment is welcome.<br>=A0<br>Thanks<br>=A0<br>-Ga=
ng</div>

<div>=A0</div>
<div>A New Internet-Draft is available from the on-line Internet-Drafts dir=
ectories.</div>
<div>=A0=A0=A0=A0=A0=A0 Title=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 : An Incrementa=
l Deployable Mapping Service for Scalable Routing Architecture<br>=A0=A0=A0=
=A0=A0=A0 Author(s)=A0=A0=A0=A0=A0=A0 : G. Chen, et al.<br>=A0=A0=A0=A0=A0=
=A0 Filename=A0=A0=A0=A0=A0=A0=A0 : draft-chen-lisp-er-mo-01.txt<br>=A0=A0=
=A0=A0=A0=A0 Pages=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 : 20<br>
=A0=A0=A0=A0=A0=A0 Date=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 : 2009-07-12</div>
<div>This document describes a mechanism of providing mapping service for<b=
r>LISP-like architecture.=A0 The mapping service comprises of EID Router<br=
>(ER) mechanism and supplementary DHT Mapping Overlay (MO), in which<br>
ER mechanism is for reducing forwarding entries in routers while<br>driving=
 the packets to the destination through tunnels, and the DHT<br>MO serves a=
s a supplement that provides specific mappings to reduce<br>the number of t=
unnels.=A0 The mechanism is flexibly deployable for ISPs<br>
since it costs little and is easy to progress.</div>
<div>A URL for this Internet-Draft is:<br><a href=3D"http://www.ietf.org/in=
ternet-drafts/draft-chen-lisp-er-mo-01.txt">http://www.ietf.org/internet-dr=
afts/draft-chen-lisp-er-mo-01.txt</a></div>
<div>Internet-Drafts are also available by anonymous FTP at:<br><a href=3D"=
ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a=
></div>

--000e0cd5097a3cda14046eb60bb0--

From lixia@cs.ucla.edu  Wed Jul 15 10:43:29 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 38FBB28C1A3 for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 10:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.212
X-Spam-Level: 
X-Spam-Status: No, score=-2.212 tagged_above=-999 required=5 tests=[AWL=-0.213, BAYES_00=-2.599, J_CHICKENPOX_42=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 EK0tK4+FdFHC for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 10:43:28 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 7985728C13C for <rrg@irtf.org>; Wed, 15 Jul 2009 10:43:28 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 4F21139E80FA; Wed, 15 Jul 2009 10:43:01 -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 u5DDjI4cs44Q; Wed, 15 Jul 2009 10:42:56 -0700 (PDT)
Received: from [10.0.1.5] (cpe-98-151-52-146.socal.res.rr.com [98.151.52.146]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 7B95B39E80DA; Wed, 15 Jul 2009 10:42:56 -0700 (PDT)
Message-Id: <7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Louise Burness <louise.burness@bt.com>
In-Reply-To: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@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: Wed, 15 Jul 2009 10:42:55 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>
X-Mailer: Apple Mail (2.935.3)
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: Wed, 15 Jul 2009 17:43:29 -0000

Apology for this belated response.  In an effort to get ready for our  
next meeting, I've been going through the mail again....

> -----Original Message-----
>> From: Christian Vogt [mailto:christian.vogt@ericsson.com]
>> Sent: 30 June 2009 20:51
>> To: Krug,AL,Louise,CXR9 R
>> Cc: irtf@tonistoev.info; rrg@irtf.org
>> Subject: Re: [rrg] Next topic: properties of identifiers
>>
>>> 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
>>
>
> It makes sense in the abstract, but I am still mulling the question  
> "if
> a lot of applications would need something such as a host ID, and the
> network does not provide it will we end up with a lot of different  
> ways
> of providing it, and possibly some very nasty ways (like IP addresses
> got overused). I guess then you might say that you have the core
> architecture and a set of extras that need to be standardised but you
> should not expect them to be gloablly available?

we are facing complex design issues.  I feel that one way to make us  
see the picture clearly is to clarify any vague notion, so here is  
one: the above says

    "if a lot of applications would need something such as
     a host ID, and the network does not provide it will we
     end up with a lot of different ways of providing it..."

What is this "network" referred to in the above?
The data delivery network?
or the overall Internet architecture?

I assume the answer is the latter?

> Do you think the session need to have a globally unique identifier or
> locally agreed between the endpoints during the contact establishment?

I've seen multiple mentioning about "sessions", but yet to see a clear  
definition of it.

Lixia


From scott.brim@gmail.com  Wed Jul 15 10:53:36 2009
Return-Path: <scott.brim@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 9364F3A6BC7 for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 10:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.682
X-Spam-Level: 
X-Spam-Status: No, score=-2.682 tagged_above=-999 required=5 tests=[AWL=-0.083, 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 GDMKGQ3Q7s1s for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 10:53:35 -0700 (PDT)
Received: from mail-pz0-f195.google.com (mail-pz0-f195.google.com [209.85.222.195]) by core3.amsl.com (Postfix) with ESMTP id DE0853A6A45 for <rrg@irtf.org>; Wed, 15 Jul 2009 10:53:35 -0700 (PDT)
Received: by pzk33 with SMTP id 33so2945297pzk.15 for <rrg@irtf.org>; Wed, 15 Jul 2009 10:52: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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=oFNwPUEnotAI6aDfF9fZKvOtLNuE4kr+lJf6CKGTlKY=; b=X4Df0ejUpj2xliPeG5J2Ym7jtePgXvdYcJKfiUK+Xvq3/h8WjEo6sQpznLp0CkyxPG WAeZ9zJNyaegWx/BZoyekx2kOeuv2UJ5X0lXf+fp3xwzELKU5/X+m15E2wgxlJLDKpfm q+DdfUltDu4eAcEKVl/TNmKf7pmwLWK6i++2M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=jEcry1IaMry+3OCFzSG18yjmRpfV4Bq2RI8sZq9CotJfq4FPE+JyxPBrSJkXYXFJ8n nkeGpwAt/BFIGJzrPW5q0KComOwZvKhi0SWhx0m544dovSvvlnbzX7eUs4/iV6LBUqgN /hi0gGSlzNaQ9lJnQpIKZP6Y8OAwJ2rcG+tqc=
Received: by 10.115.94.1 with SMTP id w1mr12912077wal.177.1247680367725; Wed, 15 Jul 2009 10:52:47 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id n40sm14218573wag.30.2009.07.15.10.52.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 15 Jul 2009 10:52:46 -0700 (PDT)
Message-ID: <4A5E176B.5060302@gmail.com>
Date: Wed, 15 Jul 2009 13:52:43 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Lixia Zhang <lixia@cs.ucla.edu>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu>
In-Reply-To: <7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Wed, 15 Jul 2009 17:53:36 -0000

Lixia Zhang allegedly wrote on 07/15/2009 1:42 PM:
>> Do you think the session need to have a globally unique identifier or
>> locally agreed between the endpoints during the contact establishment?
> 
> I've seen multiple mentioning about "sessions", but yet to see a clear
> definition of it.

Lixia,

First informally: You know what it is.  Why do you need it rigorously
defined?

Attempting formality, something like: An exchange of messages between
two or more high level (i.e. top of stack, ultimate consumer of packet)
entities that involves synchronized state information.  A session is
distinguishable from a transaction (no synchronized state) and a one-way
stream (not an "exchange").

Scott

From lixia@cs.ucla.edu  Wed Jul 15 10:54:52 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 057513A683A for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 10:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.123,  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 9jXcmgRYPEUu for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 10:54:51 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 3D2803A6C3A for <rrg@irtf.org>; Wed, 15 Jul 2009 10:53:45 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 0AB2C39E80DA for <rrg@irtf.org>; Wed, 15 Jul 2009 10:52:55 -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 B3ayoRBS3d1H for <rrg@irtf.org>; Wed, 15 Jul 2009 10:52:50 -0700 (PDT)
Received: from [10.0.1.5] (cpe-98-151-52-146.socal.res.rr.com [98.151.52.146]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 3BE0539E80F2 for <rrg@irtf.org>; Wed, 15 Jul 2009 10:52:50 -0700 (PDT)
Message-Id: <36975B15-B7FA-4E7B-80EC-A2BD43701744@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: rrg@irtf.org
In-Reply-To: <8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com>
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: Wed, 15 Jul 2009 10:52:49 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <4A4B6CA7.7080208@joelhalpern.com> <8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com>
X-Mailer: Apple Mail (2.935.3)
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: Wed, 15 Jul 2009 17:54:52 -0000

On Jul 3, 2009, at 4:58 PM, Christian Vogt wrote:

> On Jul 1, 2009, Joel M. Halpern wrote:
>
>> It seems to me however that it is useful to be able to explicitly  
>> tell
>> which locators go with the same communicating entity, as distinct  
>> from
>> the larger set of locators which might go with the same service [...]
>
> Joel -
>
> Yes, we absolutely need this.  But why does this imply the need for a
> host or stack identifier?  Session identifiers already map to the  
> set of
> locators that go to the same communicating entity.  This is why we  
> need
> to distinguish them from service identifiers, which in turn may map to
> locators of different communicating entities.


the above comment seems brining more implicit assumptions regarding  
"session identifiers", e.g. "Session identifiers already map to the  
set of locators that go to the same communicating entity..."

as I mentioned in the prev msg, I've yet to see a simple and clear  
definition of "Session" first.  As Joel questioned in next msg,

    I am trying to refer someone to a specific entity. They
    do not have a session with that entity.  So a session ID
    is clearly totally useless for a referral.

Maybe I would not go as far as saying session ID is totally useless  
because I do not even know what it identifies:)

Lixia


From scott.brim@gmail.com  Wed Jul 15 11:06:08 2009
Return-Path: <scott.brim@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 AEA9C3A6A6C for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 11:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=-0.071,  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 t3+2pFdZdM5r for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 11:06:07 -0700 (PDT)
Received: from mail-pz0-f195.google.com (mail-pz0-f195.google.com [209.85.222.195]) by core3.amsl.com (Postfix) with ESMTP id C0A323A6B57 for <rrg@irtf.org>; Wed, 15 Jul 2009 11:06:07 -0700 (PDT)
Received: by pzk33 with SMTP id 33so2950286pzk.15 for <rrg@irtf.org>; Wed, 15 Jul 2009 11:05:56 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Fh8ofNE/8VTNF9FUKa71TfwufXr0hEKCIVSh5JM2h5A=; b=KMAhKBj160cZWfZEjZIh8a46BNdtQQwBPQKmtOtYD2y39fmC7iOWle0NG16dnRpJyC Pd32JijvXnzjaMTU3U17s7SCjumFcczd/bySzrWONTFc5KkNtFGLi3ITkkQICVAxSRje Pg+97pQu2utx24QTG3hX/qjRAiLByDmgE/i3w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=WFOhtPeOvEpSctjPj+fMyczFXumS28A/vLye58emqWzPigCzUcUHngLDN5IAV7rsW2 XP4h+yMSflAjjmkuPmdVL8wkSu1hjPEmiFEGCoXIk3ubuvtXNgstl6BzpShII53DWNd2 JW7VFR1WyE2TEdZ94p72e/xTUhjtQzCHlp4ww=
Received: by 10.114.58.15 with SMTP id g15mr12030544waa.38.1247681156096; Wed, 15 Jul 2009 11:05:56 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id g25sm14329385wag.8.2009.07.15.11.05.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 15 Jul 2009 11:05:54 -0700 (PDT)
Message-ID: <4A5E1A7F.8070108@gmail.com>
Date: Wed, 15 Jul 2009 14:05:51 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Lixia Zhang <lixia@cs.ucla.edu>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	<4A4B6CA7.7080208@joelhalpern.com>	<8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com> <36975B15-B7FA-4E7B-80EC-A2BD43701744@cs.ucla.edu>
In-Reply-To: <36975B15-B7FA-4E7B-80EC-A2BD43701744@cs.ucla.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Wed, 15 Jul 2009 18:06:08 -0000

Lixia Zhang allegedly wrote on 07/15/2009 1:52 PM:
>> Yes, we absolutely need this.  But why does this imply the need for a
>> host or stack identifier?  Session identifiers already map to the set of
>> locators that go to the same communicating entity.  This is why we need
>> to distinguish them from service identifiers, which in turn may map to
>> locators of different communicating entities.
> 
> the above comment seems brining more implicit assumptions regarding
> "session identifiers", e.g. "Session identifiers already map to the set
> of locators that go to the same communicating entity..."

This mapping of session identifier -> locators is transient and not for
general use.  That is, you couldn't put a session identifier in DNS and
expect to use it as a "where is this node" locator.  However, while a
session exists, participants in that session can use a session
identifier internally.

> as I mentioned in the prev msg, I've yet to see a simple and clear
> definition of "Session" first.  As Joel questioned in next msg,

See previous reply.

>    I am trying to refer someone to a specific entity. They
>    do not have a session with that entity.  So a session ID
>    is clearly totally useless for a referral.

That's a different purpose and the statement is correct.  A session ID
is meaningless if there is no session.

From irtf@tonistoev.info  Wed Jul 15 20:18:23 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 B257F3A6C7A for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 20:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level: 
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[AWL=0.496,  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 t79ZfxQS1new for <rrg@core3.amsl.com>; Wed, 15 Jul 2009 20:18:22 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 685733A6A5D for <rrg@irtf.org>; Wed, 15 Jul 2009 20:18:22 -0700 (PDT)
Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <irtf@tonistoev.info>) id 1MRHUZ-00065x-GZ for rrg@irtf.org; Thu, 16 Jul 2009 06:18:43 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Thu, 16 Jul 2009 06:18:42 +0300
User-Agent: KMail/1.9.9
References: <200907110821.47414.irtf@tonistoev.info> <4A5B76A0.8090200@gmail.com>
In-Reply-To: <4A5B76A0.8090200@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907160618.43242.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: Thu, 16 Jul 2009 03:18:23 -0000

Scott,

Why "stack" instead of "node"?
We need node identifiers and node locators, identifiers mapping to locators.


On Monday 13 July 2009 21:02:08 Scott Brim wrote:
> Toni Stoev allegedly wrote on 07/11/2009 1:21 AM:
> > Please, anyone who writes on identifiers topic, identify your empathy to:
> > Design Goals for Scalable Internet Routing, 3.6. Decoupling location and identification
> > 
> > I do care about that goal.
> 
> Of course.
> 
> > We have interface (node) identification with IP addresses.
> > It is used for node-local session identification as part of the socket.
> > There the IP address is an identifier of the endpoint of the inter-node communication process.
> 
> Please let me know if I am paraphrasing you correctly:
> 
>   - an IP address identifies an interface
>   - identifying an interface is the same as identifying a node
>   - an IP address is part of the identification of a session endpoint

An IP address identifies an interface and thus generally the node that it belongs to.
This is the IP identification of a node.

> IMHO an IP address can be part of the set of identifiers you use for
> _initial_ contact, to establish a session in the first place (this is
> the "stack ID" discussion).  However, you want a session to be able to
> run over more than one interface, so you quickly want to decouple
> identifiers used for session continuity from any interface identifiers.
> 
> > Let us extract this identification from IP addresses and have it separately.
> > But let us keep using the hierarchical structure for the function of authentication of identity.
> 
> If I understand correctly, you are saying that the set of {IP address,
> port, protocol} can be used as input to authentication.  For
> authentication you generally need a trusted third party and identifiers
> that third party understands.

And identifier structure that points third/intermediate parties.

> Toni Stoev allegedly wrote on 07/11/2009 2:16 AM:
> > Scott Brim wrote:
> >> If I move a session from one device to another, or from one
> >> interface to another,
> > 
> > Scott, a session is established with a node. You can move
> > communication among interfaces but you keep talking to the same node.
> 
> A session is established between communicating entities; those entities
> may move from node to node.  Don't forget about virtualization.

Are those entities application instances or do you mean virtual nodes?

> >> a node identifier is not enough to support session continuity.
> > 
> > A node locator, a node identifier and a node-local session instance
> > number would do the job.
> 
> You don't want identifiers used for session continuity to be required to
> change just because a node changes its identifiers.  The local session
> instance identifier is the only one of these that may work for you.

Again, what are the session endpoint entities that communicate?

> >> If I have a way to identify sessions that does support session 
> >> continuity, then a node identifier is not necessary in addition for
> >> that purpose.
> > 
> > A node locator and a node-local session instance number are
> > sufficient to have a session. A node identifier is needed to move the
> > session from one node to another.
> 
> Now I'm confused.

Sorry about that.
A node identifier is needed to move the session from one node location to another.


Toni

From lixia@cs.ucla.edu  Fri Jul 17 23:43:49 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 D34183A6EF1 for <rrg@core3.amsl.com>; Fri, 17 Jul 2009 23:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 IPO1vP2SMl8r for <rrg@core3.amsl.com>; Fri, 17 Jul 2009 23:43:49 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 1B0CD3A67D3 for <rrg@irtf.org>; Fri, 17 Jul 2009 23:43:39 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id A5C6039E8101; Fri, 17 Jul 2009 23:43:38 -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 T52SaWf6dRb3; Fri, 17 Jul 2009 23:43:34 -0700 (PDT)
Received: from [10.0.1.5] (cpe-98-151-52-146.socal.res.rr.com [98.151.52.146]) by smtp.cs.ucla.edu (Postfix) with ESMTP id CC79C39E80FF; Fri, 17 Jul 2009 23:43:33 -0700 (PDT)
Message-Id: <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Scott Brim <scott.brim@gmail.com>
In-Reply-To: <4A5E176B.5060302@gmail.com>
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: Fri, 17 Jul 2009 23:43:33 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu> <4A5E176B.5060302@gmail.com>
X-Mailer: Apple Mail (2.935.3)
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: Sat, 18 Jul 2009 06:43:50 -0000

On Jul 15, 2009, at 10:52 AM, Scott Brim wrote:

> Lixia Zhang allegedly wrote on 07/15/2009 1:42 PM:
>>> Do you think the session need to have a globally unique identifier  
>>> or
>>> locally agreed between the endpoints during the contact  
>>> establishment?
>>
>> I've seen multiple mentioning about "sessions", but yet to see a  
>> clear
>> definition of it.
>
> Lixia,
>
> First informally: You know what it is.  Why do you need it rigorously
> defined?

1/ I honestly do not know.  Citing Joel's comment here: does a session  
mean the combination of two ends?  do we care unicast/multicast  
sessions?  how lasting/transient is a session (hence the life time of  
its ID)?  etc etc.

2/ more fundamentally: when I program, maybe I could say "I know what  
each part does" and dont define rigorous interface (but still, that is  
NOT good practice)
But here we are talking about a big architecture. As I've seen, even a  
term with a definition often gets different interpretation by  
different people, let alone a term without a clear definition!

But I would like to step up a level and repeat what I said earlier:
1/ I do not think it is in our charter to define how many identifiers  
we ought to have, or what they ought to be.
2/ Our job is to figureout scalable routing architecture.
3/ We need to have a good understanding about the interplay between  
addresses and identifiers, no less and also no more.

Related to the last point: I had planned to get a short draft out on  
the terminology discussion we had at SF IETF before the draft 00  
deadline but you all know by now that I did not get there.  I am still  
trying to finish it in coming days, to get it ready for discussion at  
Stockholm.

Lixia

From jmh@joelhalpern.com  Sat Jul 18 07:23:15 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 C52D63A6945 for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 07:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 AEXfG94zxxJz for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 07:23:15 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 262693A68BC for <rrg@irtf.org>; Sat, 18 Jul 2009 07:23:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 1112E437E4A; Sat, 18 Jul 2009 07:23:15 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-52-248.clppva.btas.verizon.net [71.161.52.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 74831434029; Sat, 18 Jul 2009 07:23:14 -0700 (PDT)
Message-ID: <4A61DAD1.4070309@joelhalpern.com>
Date: Sat, 18 Jul 2009 10:23:13 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Lixia Zhang <lixia@cs.ucla.edu>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	<7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu>	<4A5E176B.5060302@gmail.com> <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu>
In-Reply-To: <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 18 Jul 2009 14:23:15 -0000

I think that this is at least misleading.
 From a pure routing architecture perspective, the statement that IPv6 
started with (thou shalt always use provider address) is sufficient.
However, once we acknowledge that issues like renumbering and the 
realities of building networks are relevant, we have to look beyond just 
our playpen and pay attention to adjacent activities and our affects on 
them.  Similarly, when evaluating map-and-encaps ideas, we should be 
aware of the interaction of those ideas and other activities like 
multi-path TCP, even though multi-TCP is clearly not "routing".

If we claim to have solved something with too small a focus, we won't 
have anything usable.

Yours,
Joel

Lixia Zhang wrote:
...
> But I would like to step up a level and repeat what I said earlier:
> 1/ I do not think it is in our charter to define how many identifiers we 
> ought to have, or what they ought to be.
> 2/ Our job is to figureout scalable routing architecture.
> 3/ We need to have a good understanding about the interplay between 
> addresses and identifiers, no less and also no more.
...

From luigi@net.t-labs.tu-berlin.de  Sat Jul 18 07:41:17 2009
Return-Path: <luigi@net.t-labs.tu-berlin.de>
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 173CE3A68AB for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 07:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.759
X-Spam-Level: 
X-Spam-Status: No, score=-0.759 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001]
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 AZfqokIhYoaB for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 07:41:16 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [130.149.220.252]) by core3.amsl.com (Postfix) with ESMTP id DC2B73A68BC for <rrg@irtf.org>; Sat, 18 Jul 2009 07:41:15 -0700 (PDT)
Received: from dyn113.net.t-labs.tu-berlin.de (dyn113.net.t-labs.tu-berlin.de [130.149.220.113]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTP id 40D2F701BA82; Sat, 18 Jul 2009 16:41:14 +0200 (CEST)
Message-Id: <572150EB-774C-4913-BCBF-8CE08D3BAE6B@net.t-labs.tu-berlin.de>
From: Luigi Iannone <luigi@net.t-labs.tu-berlin.de>
To: Lixia Zhang <lixia@CS.UCLA.EDU>
In-Reply-To: <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu>
Content-Type: multipart/alternative; boundary=Apple-Mail-21--962065886
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sat, 18 Jul 2009 16:41:13 +0200
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu> <4A5E176B.5060302@gmail.com> <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu>
X-Mailer: Apple Mail (2.935.3)
Cc: rrg@irtf.org, Scott Brim <scott.brim@gmail.com>
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, 18 Jul 2009 14:41:17 -0000

--Apple-Mail-21--962065886
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Jul 18, 2009, at 8:43 , Lixia Zhang wrote:
>
>
> But I would like to step up a level and repeat what I said earlier:
> 1/ I do not think it is in our charter to define how many  
> identifiers we ought to have, or what they ought to be.
> 2/ Our job is to figureout scalable routing architecture.

I am confused here. Isn't 1 a part 2? i.e., by defining a new routing  
architecture shall we not define exactly what is an identifier  
(including how many different identifiers)?


Luigi


> 3/ We need to have a good understanding about the interplay between  
> addresses and identifiers, no less and also no more.
>
> Related to the last point: I had planned to get a short draft out on  
> the terminology discussion we had at SF IETF before the draft 00  
> deadline but you all know by now that I did not get there.  I am  
> still trying to finish it in coming days, to get it ready for  
> discussion at Stockholm.
>
> Lixia
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg


--Apple-Mail-21--962065886
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Jul 18, 2009, =
at 8:43 , Lixia Zhang wrote:</div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" color=3D"#000000"><br></font><br>But I would =
like to step up a level and repeat what I said earlier:<br>1/ I do not =
think it is in our charter to define how many identifiers we ought to =
have, or what they ought to be.<br>2/ Our job is to figureout scalable =
routing architecture.<br></div></blockquote><div><br></div><div>I am =
confused here. Isn't 1 a part 2? i.e., by defining a new routing =
architecture shall we not define exactly what is an identifier =
(including how many different =
identifiers)?&nbsp;</div><div><br></div><div><br></div><div>Luigi</div><di=
v><br></div><br><blockquote type=3D"cite"><div>3/ We need to have a good =
understanding about the interplay between addresses and identifiers, no =
less and also no more.<br><br>Related to the last point: I had planned =
to get a short draft out on the terminology discussion we had at SF IETF =
before the draft 00 deadline but you all know by now that I did not get =
there. &nbsp;I am still trying to finish it in coming days, to get it =
ready for discussion at =
Stockholm.<br><br>Lixia<br>_______________________________________________=
<br>rrg mailing list<br><a =
href=3D"mailto:rrg@irtf.org">rrg@irtf.org</a><br>http://www.irtf.org/mailm=
an/listinfo/rrg<br></div></blockquote></div><br></body></html>=

--Apple-Mail-21--962065886--

From lixia@CS.UCLA.EDU  Sat Jul 18 08:07:30 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 A38703A6A49 for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 08:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 KuSWXVIK7U-R for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 08:07:29 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id CB2793A6A67 for <rrg@irtf.org>; Sat, 18 Jul 2009 08:05:07 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id AE48639E80DA; Sat, 18 Jul 2009 08:05:07 -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 j3couoyD6+PK; Sat, 18 Jul 2009 08:05:03 -0700 (PDT)
Received: from [10.0.1.5] (cpe-98-151-52-146.socal.res.rr.com [98.151.52.146]) by smtp.cs.ucla.edu (Postfix) with ESMTP id A4FA039E80CF; Sat, 18 Jul 2009 08:05:03 -0700 (PDT)
Message-Id: <C939DED3-77CF-4F9A-B72B-85C363D69E82@CS.UCLA.EDU>
From: Lixia Zhang <lixia@CS.UCLA.EDU>
To: Luigi Iannone <luigi@net.t-labs.tu-berlin.de>
In-Reply-To: <572150EB-774C-4913-BCBF-8CE08D3BAE6B@net.t-labs.tu-berlin.de>
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, 18 Jul 2009 08:05:03 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu> <4A5E176B.5060302@gmail.com> <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu> <572150EB-774C-4913-BCBF-8CE08D3BAE6B@net.t-labs.tu-berlin.de>
X-Mailer: Apple Mail (2.935.3)
Cc: rrg@irtf.org, Scott Brim <scott.brim@gmail.com>
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, 18 Jul 2009 15:07:30 -0000

On Jul 18, 2009, at 7:41 AM, Luigi Iannone wrote:

>
> On Jul 18, 2009, at 8:43 , Lixia Zhang wrote:
>>
>>
>> But I would like to step up a level and repeat what I said earlier:
>> 1/ I do not think it is in our charter to define how many  
>> identifiers we ought to have, or what they ought to be.
>> 2/ Our job is to figureout scalable routing architecture.
>
> I am confused here. Isn't 1 a part 2? i.e., by defining a new  
> routing architecture shall we not define exactly what is an  
> identifier (including how many different identifiers)?
>
> Luigi


I fully agree with defining exactly what properties an identifier  
ought to have with regard to routing, as we have discussed at SF IETF.

I do not believe this group is the right body to tell how many  
identifiers the applications may ever want. I take the liberty to  
quote a paragraph from a msg Scott Brim sent earlier in reply to  
Christian (July 9, 2009 10:30:45 AM PDT):

    First, let's avoid thinking of the Internet in client/server
    concepts. "Service" has connotations of a destination that is
    frequently accessed, well-known, and perhaps globally addressed.
    We need to leave room for simple personal communications.

We need to leave room for future new applications, which we dont know  
what they may be but we know for sure they will come.

I saw my earlier statement was not exactly clear; I should have said:

    I do not think it is in our charter to define exactly how many
    identifiers all the upper layers ought to have.

together with my 3rd statement:

> 3/ We need to have a good understanding about the interplay between  
> addresses and identifiers, no less and also no more.

does this sound right now?

>> Related to the last point: I had planned to get a short draft out  
>> on the terminology discussion we had at SF IETF before the draft 00  
>> deadline but you all know by now that I did not get there.  I am  
>> still trying to finish it in coming days, to get it ready for  
>> discussion at Stockholm.
>>
>> Lixia
>> _______________________________________________
>> rrg mailing list
>> rrg@irtf.org
>> http://www.irtf.org/mailman/listinfo/rrg
>


From lixia@cs.ucla.edu  Sat Jul 18 08:09:30 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 021223A6831 for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 08:09:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  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 9hwpbt4v-VkV for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 08:09:29 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 96D5F3A6AB4 for <rrg@irtf.org>; Sat, 18 Jul 2009 08:09:02 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 9D54C39E80DA; Sat, 18 Jul 2009 08:09:02 -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 XiUrTkVZJbaJ; Sat, 18 Jul 2009 08:08:57 -0700 (PDT)
Received: from [10.0.1.5] (cpe-98-151-52-146.socal.res.rr.com [98.151.52.146]) by smtp.cs.ucla.edu (Postfix) with ESMTP id C9ADC39E80CF; Sat, 18 Jul 2009 08:08:57 -0700 (PDT)
Message-Id: <323D65F3-4AD8-4F01-A16A-601834309029@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Joel M. Halpern <jmh@joelhalpern.com>
In-Reply-To: <4A61DAD1.4070309@joelhalpern.com>
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, 18 Jul 2009 08:08:57 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	<7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu>	<4A5E176B.5060302@gmail.com> <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu> <4A61DAD1.4070309@joelhalpern.com>
X-Mailer: Apple Mail (2.935.3)
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: Sat, 18 Jul 2009 15:09:30 -0000

On Jul 18, 2009, at 7:23 AM, Joel M. Halpern wrote:

> I think that this is at least misleading.
> From a pure routing architecture perspective, the statement that  
> IPv6 started with (thou shalt always use provider address) is  
> sufficient.
> However, once we acknowledge that issues like renumbering and the  
> realities of building networks are relevant, we have to look beyond  
> just our playpen and pay attention to adjacent activities and our  
> affects on them.  Similarly, when evaluating map-and-encaps ideas,  
> we should be aware of the interaction of those ideas and other  
> activities like multi-path TCP, even though multi-TCP is clearly not  
> "routing".

Joel, I fully agree with the above statements (except the one about  
misleading:)

e.g. taking multipath-tcp as an example: I thought this is covered  
under my 3rd statement below:

    We need to have a good understanding about the interplay
    between addresses and identifiers

> If we claim to have solved something with too small a focus, we  
> won't have anything usable.

agree.

>
> Yours,
> Joel
>
> Lixia Zhang wrote:
> ...
>> But I would like to step up a level and repeat what I said earlier:
>> 1/ I do not think it is in our charter to define how many  
>> identifiers we ought to have, or what they ought to be.
>> 2/ Our job is to figureout scalable routing architecture.
>> 3/ We need to have a good understanding about the interplay between  
>> addresses and identifiers, no less and also no more.
> ...


From jmh@joelhalpern.com  Sat Jul 18 08:15:23 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 E1D543A6831 for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 08:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 X3Ypz+Du1KPh for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 08:15:23 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 3D2493A6965 for <rrg@irtf.org>; Sat, 18 Jul 2009 08:15:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 0AD34437E4A; Sat, 18 Jul 2009 08:15:20 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-52-248.clppva.btas.verizon.net [71.161.52.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 626A3434029; Sat, 18 Jul 2009 08:15:19 -0700 (PDT)
Message-ID: <4A61E706.4010703@joelhalpern.com>
Date: Sat, 18 Jul 2009 11:15:18 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Lixia Zhang <lixia@cs.ucla.edu>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	<7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu>	<4A5E176B.5060302@gmail.com> <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu> <4A61DAD1.4070309@joelhalpern.com> <323D65F3-4AD8-4F01-A16A-601834309029@cs.ucla.edu>
In-Reply-To: <323D65F3-4AD8-4F01-A16A-601834309029@cs.ucla.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 18 Jul 2009 15:15:24 -0000

Fair enough.  If what you intended and what I was trying to ask for are 
similar enough, then at least the two of us (and I think quite a few 
others) are on the same page.
Thanks,
Joel


Lixia Zhang wrote:
> 
> On Jul 18, 2009, at 7:23 AM, Joel M. Halpern wrote:
> 
>> I think that this is at least misleading.
>> From a pure routing architecture perspective, the statement that IPv6 
>> started with (thou shalt always use provider address) is sufficient.
>> However, once we acknowledge that issues like renumbering and the 
>> realities of building networks are relevant, we have to look beyond 
>> just our playpen and pay attention to adjacent activities and our 
>> affects on them.  Similarly, when evaluating map-and-encaps ideas, we 
>> should be aware of the interaction of those ideas and other activities 
>> like multi-path TCP, even though multi-TCP is clearly not "routing".
> 
> Joel, I fully agree with the above statements (except the one about 
> misleading:)
> 
> e.g. taking multipath-tcp as an example: I thought this is covered under 
> my 3rd statement below:
> 
>    We need to have a good understanding about the interplay
>    between addresses and identifiers
> 
>> If we claim to have solved something with too small a focus, we won't 
>> have anything usable.
> 
> agree.
> 
>>
>> Yours,
>> Joel
>>
>> Lixia Zhang wrote:
>> ...
>>> But I would like to step up a level and repeat what I said earlier:
>>> 1/ I do not think it is in our charter to define how many identifiers 
>>> we ought to have, or what they ought to be.
>>> 2/ Our job is to figureout scalable routing architecture.
>>> 3/ We need to have a good understanding about the interplay between 
>>> addresses and identifiers, no less and also no more.
>> ...
> 
> 

From luigi@net.t-labs.tu-berlin.de  Sat Jul 18 08:28:06 2009
Return-Path: <luigi@net.t-labs.tu-berlin.de>
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 21E033A693F for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 08:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.504
X-Spam-Level: 
X-Spam-Status: No, score=-1.504 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 6UN2AP7Dl0GA for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 08:27:59 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [130.149.220.252]) by core3.amsl.com (Postfix) with ESMTP id 699463A68AB for <rrg@irtf.org>; Sat, 18 Jul 2009 08:27:59 -0700 (PDT)
Received: from dyn113.net.t-labs.tu-berlin.de (dyn113.net.t-labs.tu-berlin.de [130.149.220.113]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTP id 85BB5701BA82; Sat, 18 Jul 2009 17:27:57 +0200 (CEST)
Message-Id: <9F48BAD3-01D2-46B2-BA25-0E064D6F0BAA@net.t-labs.tu-berlin.de>
From: Luigi Iannone <luigi@net.t-labs.tu-berlin.de>
To: Lixia Zhang <lixia@CS.UCLA.EDU>
In-Reply-To: <C939DED3-77CF-4F9A-B72B-85C363D69E82@CS.UCLA.EDU>
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, 18 Jul 2009 17:27:56 +0200
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu> <4A5E176B.5060302@gmail.com> <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu> <572150EB-774C-4913-BCBF-8CE08D3BAE6B@net.t-labs.tu-berlin.de> <C939DED3-77CF-4F9A-B72B-85C363D69E82@CS.UCLA.EDU>
X-Mailer: Apple Mail (2.935.3)
Cc: rrg@irtf.org, Scott Brim <scott.brim@gmail.com>
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, 18 Jul 2009 15:28:06 -0000

On Jul 18, 2009, at 17:05 , Lixia Zhang wrote:

>
> On Jul 18, 2009, at 7:41 AM, Luigi Iannone wrote:
>
>>
>> On Jul 18, 2009, at 8:43 , Lixia Zhang wrote:
>>>
>>>
>>> But I would like to step up a level and repeat what I said earlier:
>>> 1/ I do not think it is in our charter to define how many  
>>> identifiers we ought to have, or what they ought to be.
>>> 2/ Our job is to figureout scalable routing architecture.
>>
>> I am confused here. Isn't 1 a part 2? i.e., by defining a new  
>> routing architecture shall we not define exactly what is an  
>> identifier (including how many different identifiers)?
>>
>> Luigi
>
>
> I fully agree with defining exactly what properties an identifier  
> ought to have with regard to routing, as we have discussed at SF IETF.
>
> I do not believe this group is the right body to tell how many  
> identifiers the applications may ever want. I take the liberty to  
> quote a paragraph from a msg Scott Brim sent earlier in reply to  
> Christian (July 9, 2009 10:30:45 AM PDT):
>
>   First, let's avoid thinking of the Internet in client/server
>   concepts. "Service" has connotations of a destination that is
>   frequently accessed, well-known, and perhaps globally addressed.
>   We need to leave room for simple personal communications.
>
> We need to leave room for future new applications, which we dont  
> know what they may be but we know for sure they will come.
>
> I saw my earlier statement was not exactly clear; I should have said:
>
>   I do not think it is in our charter to define exactly how many
>   identifiers all the upper layers ought to have.
>

Totally agree.

> together with my 3rd statement:
>
>> 3/ We need to have a good understanding about the interplay between  
>> addresses and identifiers, no less and also no more.
>
> does this sound right now?

Yes

thanks

L.

>
>>> Related to the last point: I had planned to get a short draft out  
>>> on the terminology discussion we had at SF IETF before the draft  
>>> 00 deadline but you all know by now that I did not get there.  I  
>>> am still trying to finish it in coming days, to get it ready for  
>>> discussion at Stockholm.
>>>
>>> Lixia
>>> _______________________________________________
>>> rrg mailing list
>>> rrg@irtf.org
>>> http://www.irtf.org/mailman/listinfo/rrg
>>
>


From scott.brim@gmail.com  Sat Jul 18 09:17:41 2009
Return-Path: <scott.brim@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 62E423A6B8A for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 09:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 JIDLAvAEASpl for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 09:17:40 -0700 (PDT)
Received: from mail-px0-f202.google.com (mail-px0-f202.google.com [209.85.216.202]) by core3.amsl.com (Postfix) with ESMTP id 9D6F23A69B3 for <rrg@irtf.org>; Sat, 18 Jul 2009 09:17:17 -0700 (PDT)
Received: by pxi40 with SMTP id 40so1036804pxi.15 for <rrg@irtf.org>; Sat, 18 Jul 2009 09:16:45 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=cP9GCJNh/sukUHOcO+EdZH5Sl7l7N8dyIJXFI869GbY=; b=aARD5uC7jhU45n2IGjku5z0+UgfmbPLbbA9E30T2BjhlkZVF83GCCBdAYnOJeBAZPI r0b8plF6Ce+P5oeBWtBEYW0mqeHCCmwAN5uoXTz1npJ6yI5enlo6E4eBwXkap3M4BLg/ pRNJoDvKnJxRlFn2GUSJQDfjAuQfkr4Wvu6EE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=G5tdx/Y0p/bDTgY+cEGGGX18SKyu9mhntLT8gxRjNhB0HuU6kKh9rZb+iDc/UMbA0N WWHp1Yl7VnqW1cu25K712OWiTGuvjY9LsIIO5h0VZbDePcELlYuRU2frxTNcifk0WwWW guvLDSZ/ceRCGqjUFQr3mZk24Dn2CRWqtqZE4=
Received: by 10.143.29.17 with SMTP id g17mr526678wfj.218.1247933805941; Sat, 18 Jul 2009 09:16:45 -0700 (PDT)
Received: from sbrim-mbp.local (cpe-67-241-43-66.twcny.res.rr.com [67.241.43.66]) by mx.google.com with ESMTPS id 31sm7086908wff.38.2009.07.18.09.16.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 18 Jul 2009 09:16:45 -0700 (PDT)
Message-ID: <4A61F56A.2050009@gmail.com>
Date: Sat, 18 Jul 2009 12:16:42 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Lixia Zhang <lixia@CS.UCLA.EDU>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net> <7AEE32D3-C746-45C4-81AC-F99FB4F24D90@cs.ucla.edu> <4A5E176B.5060302@gmail.com> <4FE9EA3A-7212-4333-BC87-CD09663F5844@cs.ucla.edu> <572150EB-774C-4913-BCBF-8CE08D3BAE6B@net.t-labs.tu-berlin.de> <C939DED3-77CF-4F9A-B72B-85C363D69E82@CS.UCLA.EDU>
In-Reply-To: <C939DED3-77CF-4F9A-B72B-85C363D69E82@CS.UCLA.EDU>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Sat, 18 Jul 2009 16:17:41 -0000

Routing per se only uses locators and forwarding indications, and
doesn't care what properties any identifiers might have (it doesn't use
them). From the point of view of routing and addressing, the motivation
for locator/identifier separation is to REMOVE constraints on routing
architecture, to make it possible to solve the routing architecture
problems (scaling, robustness, adaptability etc.).  The list of RRG
requirements with respect to identifiers is negative, not positive.  For
example, something like: "A locator MUST NOT be constrained to a
long-term association with an object.  Locators name network attachment
points, not endpoint interfaces.".

However, for any routing/addressing/forwarding architecture, RRG should
write up the implications has on identification functions.  In order to
do that, we do need to understand what identification functions are
essential for Internet operations.  We have to be sure we understand the
implications of what we recommend before we can do so responsibly.

I believe we are at the point where we have a good sense of what
identification functions are needed, and now we can keep that list in
our back pocket, as a checklist, and narrow the scope of activity back
down.

Scott




From HeinerHummel@aol.com  Sat Jul 18 14:33:19 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 440193A6B65 for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 14:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level: 
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001]
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 TVgPVGarDKgX for <rrg@core3.amsl.com>; Sat, 18 Jul 2009 14:33:18 -0700 (PDT)
Received: from imr-da03.mx.aol.com (imr-da03.mx.aol.com [205.188.105.145]) by core3.amsl.com (Postfix) with ESMTP id EE0333A6B30 for <rrg@irtf.org>; Sat, 18 Jul 2009 14:33:17 -0700 (PDT)
Received: from imo-da04.mx.aol.com (imo-da04.mx.aol.com [205.188.169.202]) by imr-da03.mx.aol.com (8.14.1/8.14.1) with ESMTP id n6IKVjUt009536; Sat, 18 Jul 2009 16:31:45 -0400
Received: from HeinerHummel@aol.com by imo-da04.mx.aol.com  (mail_out_v40_r1.5.) id f.c78.596f990d (39330);  Sat, 18 Jul 2009 16:31:44 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <c78.596f990d.37938b30@aol.com>
Date: Sat, 18 Jul 2009 16:31:44 EDT
To: lixia@cs.ucla.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1247949104"
X-Mailer: 9.0 SE for Windows sub 5021
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: Sat, 18 Jul 2009 21:33:19 -0000

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

 
In einer eMail vom 18.07.2009 17:10:05 Westeurop=E4ische Normalzeit schrei=
bt  
lixia@cs.ucla.edu:

>  Lixia Zhang wrote:
> ...
>> But I would like to step up a level  and repeat what I said earlier:
>> 1/ I do not think it is in our  charter to define how many  
>> identifiers we ought to have, or  what they ought to be.
>> 2/ Our job is to figureout scalable routing  architecture.
>> 3/ We need to have a good understanding about the  interplay between =
 
>> addresses and identifiers, no less and  also no more.



IMHO, at first it takes a clear idea about an architecture, i.e. about  
network components and how they interrelate. These network components need=
  to 
be identified, of course. However I don't think that it is helpful to  
define identifiers in the first place and then look for an architecture wh=
ich  
complies with these identifiers.
 
With MAC + IPv4 address we have 10 octets. Are they used best ? Why is  
there no co-working with IEEE such that the best exploitation can be  made=
 from 
having 10 octets altogether ? 
LISP needs an aditional header. I can anticipate that on day soon  a secon=
d 
LISP-header is prepended to the LISP-header.
My experience: if there is no discipline and no strive for optimal  
utilization, but egoistic behavior instead, then
even more available octets won't help (like MAC+IPv6 =3D22 octets).
 
Some email mentioned that the architecture should not just solve one  
particular problem (scalability) but should enable more flexible and bette=
r  
routing. Is everyone happy with the existing Multicast solutions ???
Is everyone satisfied by having no rear mirrow for recognizing all those=
  
routers which would use the current one for transit? Is everyone convinced=
 
that  the orthogonality of intra and inter-domain routing is the best ever=
 
after  ?
 
Heiner
 
 
 
 
 
 
 

-------------------------------1247949104
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 content=3D"text/html; charset=3DISO-8859-1" http-equiv=3DContent-Typ=
e>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18783"></HEAD>
<BODY style=3D"FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=3Dr=
ole_body 
bottomMargin=3D7 leftMargin=3D7 rightMargin=3D7 topMargin=3D7><FONT id=3Dr=
ole_document 
color=3D#000000 size=3D2 face=3DArial>
<DIV>
<DIV>In einer eMail vom 18.07.2009 17:10:05 Westeurop=E4ische Normalzeit=
 schreibt 
lixia@cs.ucla.edu:</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=3D=
Arial>&gt; 
  Lixia Zhang wrote:<BR>&gt; ...<BR>&gt;&gt; But I would like to step up=
 a level 
  and repeat what I said earlier:<BR>&gt;&gt; 1/ I do not think it is in=
 our 
  charter to define how many&nbsp; <BR>&gt;&gt; identifiers we ought to ha=
ve, or 
  what they ought to be.<BR>&gt;&gt; 2/ Our job is to figureout scalable=
 routing 
  architecture.<BR>&gt;&gt; 3/ We need to have a good understanding about=
 the 
  interplay between&nbsp; <BR>&gt;&gt; addresses and identifiers, no less=
 and 
  also no more.<BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>IMHO, at first it takes a clear idea about an architecture, i.e. abou=
t 
network components and how they interrelate. These network components need=
 
&nbsp;to be identified, of course. However I don't think that it is helpfu=
l to 
define identifiers in the first place and then look for an architecture wh=
ich 
complies with these identifiers.</DIV>
<DIV>&nbsp;</DIV>
<DIV>With MAC + IPv4 address we have 10 octets. Are they used best ? Why=
 is 
there no co-working with IEEE such that the best&nbsp;exploitation can be=
 
made&nbsp;from having 10 octets altogether ? </DIV>
<DIV>LISP needs an aditional header. I can anticipate that on day soon 
a&nbsp;second LISP-header is prepended to the LISP-header.</DIV>
<DIV>My experience: if there is no discipline and no strive for optimal 
utilization, but egoistic behavior instead, then</DIV>
<DIV>even more available octets won't help (like MAC+IPv6 =3D22 octets).</=
DIV>
<DIV>&nbsp;</DIV>
<DIV>Some&nbsp;email mentioned that the architecture should not just solve=
 one 
particular problem (scalability) but should enable more flexible&nbsp;and=
 better 
routing. Is everyone happy with the existing Multicast solutions ???</DIV>
<DIV>Is everyone satisfied by having no rear mirrow for recognizing all th=
ose 
routers which would use the current one for transit? Is everyone convinced=
 that 
the orthogonality&nbsp;of intra and inter-domain routing is the best ever=
 after 
?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1247949104--

From irtf@tonistoev.info  Sun Jul 19 00:16:39 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 7491D3A6929 for <rrg@core3.amsl.com>; Sun, 19 Jul 2009 00:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 F9Q9OArqEr90 for <rrg@core3.amsl.com>; Sun, 19 Jul 2009 00:16:38 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id A8E1F3A6825 for <rrg@irtf.org>; Sun, 19 Jul 2009 00:16:38 -0700 (PDT)
Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <irtf@tonistoev.info>) id 1MSQdO-0004zy-Ul for rrg@irtf.org; Sun, 19 Jul 2009 10:16:34 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Sun, 19 Jul 2009 10:16:32 +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: <200907191016.33039.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, 19 Jul 2009 07:16:39 -0000

Nice chatting on the list.

So what are identifiers? Do they have any properties, like hierarchical structure, for example?
And by the way, from a routing point of view, do identifiers identify nodes, or interfaces, or maybe links sometime in the future?
Session identification is important, but is it what we are decoupling from IP addresses? Or is interface/host/node identification?

Toni

From HeinerHummel@aol.com  Sun Jul 19 03:50:05 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 965093A6C0F for <rrg@core3.amsl.com>; Sun, 19 Jul 2009 03:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.391
X-Spam-Level: 
X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[AWL=1.207,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ce+x-xh-Uhhm for <rrg@core3.amsl.com>; Sun, 19 Jul 2009 03:50:04 -0700 (PDT)
Received: from imr-m06.mx.aol.com (imr-m06.mx.aol.com [64.12.138.200]) by core3.amsl.com (Postfix) with ESMTP id 8EEFE3A6C0A for <rrg@irtf.org>; Sun, 19 Jul 2009 03:50:04 -0700 (PDT)
Received: from imo-da02.mx.aol.com (imo-da02.mx.aol.com [205.188.169.200]) by imr-m06.mx.aol.com (v107.10) with ESMTP id RELAYIN3-44a62fa36334; Sun, 19 Jul 2009 06:49:26 -0400
Received: from HeinerHummel@aol.com by imo-da02.mx.aol.com  (mail_out_v40_r1.5.) id f.c57.58fc5c4e (32913);  Sun, 19 Jul 2009 06:49:58 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <c57.58fc5c4e.37945454@aol.com>
Date: Sun, 19 Jul 2009 06:49:56 EDT
To: HeinerHummel@aol.com, lixia@cs.ucla.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1248000596"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-IP: 205.188.169.200
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: Sun, 19 Jul 2009 10:50:05 -0000

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

Resent for dispatching a spelling mistake primarily :-)
In einer eMail vom 18.07.2009 23:33:32 Westeurop=E4ische Normalzeit schrei=
bt  
HeinerHummel@aol.com:

In einer eMail vom 18.07.2009 17:10:05 Westeurop=E4ische Normalzeit  schre=
ibt 
lixia@cs.ucla.edu:

>  Lixia Zhang wrote:
> ...
>> But I would like to step up a  level and repeat what I said earlier:
>> 1/ I do not think it is in  our charter to define how many  
>> identifiers we ought to  have, or what they ought to be.
>> 2/ Our job is to figureout  scalable routing architecture.
>> 3/ We need to have a good  understanding about the interplay between =
 
>> addresses and  identifiers, no less and also no  more.

 
IMHO, at first it takes a clear idea about an architecture, i.e. about  
network components and how they should interrelate. These network  compone=
nts 
need  to be identified, of course. However I don't think that it  is helpf=
ul 
to define identifiers in the first place and then look for an  architectur=
e 
which complies with these identifiers.
 
With MAC + IPv4 address we have 10 octets. Are they used best ? Why is  
there no co-working with IEEE such that the best exploitation can be  made=
 from 
having 10 octets altogether ? 
LISP needs an aditional header. I can anticipate that on day soon  a secon=
d 
LISP-header is prepended to the LISP-header.
My experience: if there is no discipline and no strive for optimal  
utilization, but egoistic behavior instead, then
even more available octets won't help (like MAC+IPv6 =3D22 octets).
 
Some email mentioned that the architecture should not just solve one  
particular problem (scalability) but should enable more flexible and bette=
r  
routing: 
 
- Is everyone happy with the existing Multicast solutions ???
 
- Is everyone satisfied by having no rear mirror for recognizing all those=
  
routers which would use the current one for transit? And by never being 
able to  add one (e.g. for the sake of TE traffic balancing etc.)
 
- Is everyone convinced that the orthogonality of intra and  inter-domain=
 
routing is the best ever after ?
 
Heiner
 


-------------------------------1248000596
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 content=3D"text/html; charset=3DISO-8859-1" http-equiv=3DContent-Typ=
e>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18783"></HEAD>
<BODY style=3D"FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=3Dr=
ole_body 
bottomMargin=3D7 leftMargin=3D7 rightMargin=3D7 topMargin=3D7><FONT id=3Dr=
ole_document 
color=3D#000000 size=3D2 face=3DArial>
<DIV>Resent for dispatching a spelling mistake primarily :-)</DIV>
<DIV>In einer eMail vom 18.07.2009 23:33:32 Westeurop=E4ische Normalzeit=
 schreibt 
HeinerHummel@aol.com:</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=3D=
Arial><FONT 
  color=3D#000000 size=3D2 face=3DArial>
  <DIV>In einer eMail vom 18.07.2009 17:10:05 Westeurop=E4ische Normalzeit=
 
  schreibt lixia@cs.ucla.edu:</DIV>
  <BLOCKQUOTE 
  style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x"><FONT 
    style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=
=3DArial>&gt; 
    Lixia Zhang wrote:<BR>&gt; ...<BR>&gt;&gt; But I would like to step up=
 a 
    level and repeat what I said earlier:<BR>&gt;&gt; 1/ I do not think it=
 is in 
    our charter to define how many&nbsp; <BR>&gt;&gt; identifiers we ought=
 to 
    have, or what they ought to be.<BR>&gt;&gt; 2/ Our job is to figureout=
 
    scalable routing architecture.<BR>&gt;&gt; 3/ We need to have a good=
 
    understanding about the interplay between&nbsp; <BR>&gt;&gt; addresses=
 and 
    identifiers, no less and also no 
more.</FONT></FONT></FONT></BLOCKQUOTE></BLOCKQUOTE>
<DIV>
<DIV>IMHO, at first it takes a clear idea about an architecture, i.e. abou=
t 
network components and how they should&nbsp;interrelate. These network 
components need &nbsp;to be identified, of course. However I don't think=
 that it 
is helpful to define identifiers in the first place and then look for an=
 
architecture which complies with these identifiers.</DIV>
<DIV>&nbsp;</DIV>
<DIV>With MAC + IPv4 address we have 10 octets. Are they used best ? Why=
 is 
there no co-working with IEEE such that the best&nbsp;exploitation can be=
 
made&nbsp;from having 10 octets altogether ? </DIV>
<DIV>LISP needs an aditional header. I can anticipate that on day soon 
a&nbsp;second LISP-header is prepended to the LISP-header.</DIV>
<DIV>My experience: if there is no discipline and no strive for optimal 
utilization, but egoistic behavior instead, then</DIV>
<DIV>even more available octets won't help (like MAC+IPv6 =3D22 octets).</=
DIV>
<DIV>&nbsp;</DIV>
<DIV>Some&nbsp;email mentioned that the architecture should not just solve=
 one 
particular problem (scalability) but should enable more flexible&nbsp;and=
 better 
routing: </DIV>
<DIV>&nbsp;</DIV>
<DIV>- Is everyone happy with the existing Multicast solutions ???</DIV>
<DIV>&nbsp;</DIV>
<DIV>- Is everyone satisfied by having no rear mirror for recognizing all=
 those 
routers which would use the current one for transit? And by never being ab=
le to 
add one (e.g. for the sake of TE traffic balancing etc.)</DIV>
<DIV>&nbsp;</DIV>
<DIV>- Is everyone convinced that the orthogonality&nbsp;of intra and 
inter-domain routing is the best ever after ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV></DIV></FONT></BODY></HTML>

-------------------------------1248000596--

From scott.brim@gmail.com  Sun Jul 19 04:15:39 2009
Return-Path: <scott.brim@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 E6E163A682D for <rrg@core3.amsl.com>; Sun, 19 Jul 2009 04:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 KTygGIRgBduP for <rrg@core3.amsl.com>; Sun, 19 Jul 2009 04:15:39 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by core3.amsl.com (Postfix) with ESMTP id 1D7B13A67EB for <rrg@irtf.org>; Sun, 19 Jul 2009 04:15:38 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 3so552705qwe.7 for <rrg@irtf.org>; Sun, 19 Jul 2009 04:15:36 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=1tVvqV9R8+rpCq8r72I/Et1vpYKJVsQF559WfA5TYfQ=; b=eSkz6x0IqKRpCPome0YsD443Z/+Tc6u7Tyb19cLmDRduKpq+VMfHqiIl798Jx7flJL UgLrwqKf+Cfjb9eE+LeJlDauNC5ywZeVkqDcO3vJPMg8OLKeDDTH4L5bkz6o17ngstfX oCMzCmrgrL71vfW4dgLGKk8E93g3L+D6GNCH0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=LfgNv3P2I37+xYXowQIGBk4jUeDucnI61H0rKD6UGE17izcof/pkMX65q1oRsplMQJ RkD7dUyVZG3JbSE28hoQlP7d8Ln0PjWf3D7Oc9kG6P1iS/BPv4DbM6XkaqbDn3CPpLjU koFCI/BzcXtPebEuMyOzp2yB+ol8n3vCAG8BI=
Received: by 10.224.73.206 with SMTP id r14mr1982036qaj.285.1248002136622; Sun, 19 Jul 2009 04:15:36 -0700 (PDT)
Received: from sbrim-mbp.local (cpe-67-241-43-66.twcny.res.rr.com [67.241.43.66]) by mx.google.com with ESMTPS id 8sm5126169qwj.6.2009.07.19.04.15.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 19 Jul 2009 04:15:36 -0700 (PDT)
Message-ID: <4A630057.70204@gmail.com>
Date: Sun, 19 Jul 2009 07:15:35 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Toni Stoev <irtf@tonistoev.info>
References: <200907191016.33039.irtf@tonistoev.info>
In-Reply-To: <200907191016.33039.irtf@tonistoev.info>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Sun, 19 Jul 2009 11:15:40 -0000

Toni Stoev allegedly wrote on 07/19/2009 3:16 AM:
> Nice chatting on the list.
> 
> So what are identifiers? 

http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGTerminology

> Do they have any properties, like hierarchical structure, for example?

Hierarchy is often discussed in fora for the specific identifiers under
question.  From the point of view of Routing, the question doesn't matter.

> And by the way, from a routing point of view, do identifiers identify
> nodes, or interfaces, or maybe links sometime in the future?

All.

> Session identification is important, but is it what we are decoupling
> from IP addresses? Or is interface/host/node identification?

The main problem is "addresses", which are used in both
routing/forwarding and identification functions.  We needed to get
identification functions to stop using information that is
topology-dependent (at least at some level).

From eric.fleischman@boeing.com  Tue Jul 21 09:08:50 2009
Return-Path: <eric.fleischman@boeing.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 960A83A684C for <rrg@core3.amsl.com>; Tue, 21 Jul 2009 09:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 UUSLTrSsDyiY for <rrg@core3.amsl.com>; Tue, 21 Jul 2009 09:08:49 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id AC5E33A6E6D for <rrg@irtf.org>; Tue, 21 Jul 2009 09:08:49 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n6LG8GAS020043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Jul 2009 11:08:17 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n6LG8GXR025994; Tue, 21 Jul 2009 09:08:16 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n6LG8Cmf025857; Tue, 21 Jul 2009 09:08:15 -0700 (PDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 21 Jul 2009 09:08:13 -0700
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, 21 Jul 2009 09:07:29 -0700
Message-ID: <474EEBD229DF754FB83D256004D021080C309E64@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <4A5E1A7F.8070108@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Next topic: properties of identifiers
Thread-Index: AcoFdynWE5QXTFYjQdWPPBMEVRaLAQEpSeqw
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	<4A4B6CA7.7080208@joelhalpern.com>	<8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com><36975B15-B7FA-4E7B-80EC-A2BD43701744@cs.ucla.edu> <4A5E1A7F.8070108@gmail.com>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "Scott Brim" <scott.brim@gmail.com>, "Lixia Zhang" <lixia@cs.ucla.edu>
X-OriginalArrivalTime: 21 Jul 2009 16:08:13.0226 (UTC) FILETIME=[72F1D0A0:01CA0A1D]
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, 21 Jul 2009 16:08:50 -0000

I apologize for the delayed response: I'm trying to catch up with my
email.

The thing that bothers me about this otherwise excellent discussion is
that I interpret these emails as implying that all identifiers must be
known at the IP layer. A session ID is a transport layer or above
concept. It is desirable (e.g., for management and security) to be able
to correlate session IDs with locators and also with physical locations,
but this doesn't mean that it is desirable to map these identifiers
together within the same layer. Put another way, it is fine for locators
to be in the IP layer and identified at that layer and session IDs to be
at a transport and above layer and identified there. Should a function
need to correlate the two then their existence within their appropriate
layers would permit that in the general case.

-----Original Message-----
From: Scott Brim [mailto:scott.brim@gmail.com]=20
Sent: Wednesday, July 15, 2009 11:06 AM
To: Lixia Zhang
Cc: rrg@irtf.org
Subject: Re: [rrg] Next topic: properties of identifiers

Lixia Zhang allegedly wrote on 07/15/2009 1:52 PM:
>> Yes, we absolutely need this.  But why does this imply the need for a

>> host or stack identifier?  Session identifiers already map to the set

>> of locators that go to the same communicating entity.  This is why we

>> need to distinguish them from service identifiers, which in turn may=20
>> map to locators of different communicating entities.
>=20
> the above comment seems brining more implicit assumptions regarding=20
> "session identifiers", e.g. "Session identifiers already map to the=20
> set of locators that go to the same communicating entity..."

This mapping of session identifier -> locators is transient and not for
general use.  That is, you couldn't put a session identifier in DNS and
expect to use it as a "where is this node" locator.  However, while a
session exists, participants in that session can use a session
identifier internally.

> as I mentioned in the prev msg, I've yet to see a simple and clear=20
> definition of "Session" first.  As Joel questioned in next msg,

See previous reply.

>    I am trying to refer someone to a specific entity. They
>    do not have a session with that entity.  So a session ID
>    is clearly totally useless for a referral.

That's a different purpose and the statement is correct.  A session ID
is meaningless if there is no session.
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From lixia@cs.ucla.edu  Thu Jul 23 00:03:04 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 7B8733A6843 for <rrg@core3.amsl.com>; Thu, 23 Jul 2009 00:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  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 zEI2k46VGql7 for <rrg@core3.amsl.com>; Thu, 23 Jul 2009 00:03:03 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id AFA963A6765 for <rrg@irtf.org>; Thu, 23 Jul 2009 00:03:03 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id DCB3939E80DC; Wed, 22 Jul 2009 23:52:32 -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 80oynJLhAZoa; Wed, 22 Jul 2009 23:52:29 -0700 (PDT)
Received: from [10.0.1.5] (cpe-98-151-52-146.socal.res.rr.com [98.151.52.146]) by smtp.cs.ucla.edu (Postfix) with ESMTP id C960239E80CF; Wed, 22 Jul 2009 23:52:28 -0700 (PDT)
Message-Id: <7B045821-8BBE-4946-A6A8-6FE1B596855A@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080C309E64@XCH-NW-6V1.nw.nos.boeing.com>
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: Wed, 22 Jul 2009 23:52:28 -0700
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	<4A4B6CA7.7080208@joelhalpern.com>	<8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com><36975B15-B7FA-4E7B-80EC-A2BD43701744@cs.ucla.edu> <4A5E1A7F.8070108@gmail.com> <474EEBD229DF754FB83D256004D021080C309E64@XCH-NW-6V1.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.935.3)
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: Thu, 23 Jul 2009 07:03:04 -0000

On Jul 21, 2009, at 9:07 AM, Fleischman, Eric wrote:

> I apologize for the delayed response: I'm trying to catch up with my
> email.

like everyone else:)

> The thing that bothers me about this otherwise excellent discussion is
> that I interpret these emails as implying that all identifiers must be
> known at the IP layer.

Hi Eric, I do not see the implication here.

> A session ID is a transport layer or above
> concept. It is desirable (e.g., for management and security) to be  
> able
> to correlate session IDs with locators and also with physical  
> locations,
> but this doesn't mean that it is desirable to map these identifiers
> together within the same layer. Put another way, it is fine for  
> locators
> to be in the IP layer and identified at that layer and session IDs  
> to be
> at a transport and above layer and identified there. Should a function
> need to correlate the two then their existence within their  
> appropriate
> layers would permit that in the general case.

no disagreement here.

Lixia

>
> -----Original Message-----
> From: Scott Brim [mailto:scott.brim@gmail.com]
> Sent: Wednesday, July 15, 2009 11:06 AM
> To: Lixia Zhang
> Cc: rrg@irtf.org
> Subject: Re: [rrg] Next topic: properties of identifiers
>
> Lixia Zhang allegedly wrote on 07/15/2009 1:52 PM:
>>> Yes, we absolutely need this.  But why does this imply the need  
>>> for a
>
>>> host or stack identifier?  Session identifiers already map to the  
>>> set
>
>>> of locators that go to the same communicating entity.  This is why  
>>> we
>
>>> need to distinguish them from service identifiers, which in turn may
>>> map to locators of different communicating entities.
>>
>> the above comment seems brining more implicit assumptions regarding
>> "session identifiers", e.g. "Session identifiers already map to the
>> set of locators that go to the same communicating entity..."
>
> This mapping of session identifier -> locators is transient and not  
> for
> general use.  That is, you couldn't put a session identifier in DNS  
> and
> expect to use it as a "where is this node" locator.  However, while a
> session exists, participants in that session can use a session
> identifier internally.
>
>> as I mentioned in the prev msg, I've yet to see a simple and clear
>> definition of "Session" first.  As Joel questioned in next msg,
>
> See previous reply.
>
>>   I am trying to refer someone to a specific entity. They
>>   do not have a session with that entity.  So a session ID
>>   is clearly totally useless for a referral.
>
> That's a different purpose and the statement is correct.  A session ID
> is meaningless if there is no session.
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg


From eric.fleischman@boeing.com  Thu Jul 23 09:12:38 2009
Return-Path: <eric.fleischman@boeing.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 CDBAF3A6B44 for <rrg@core3.amsl.com>; Thu, 23 Jul 2009 09:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 ULh0-MBvnijT for <rrg@core3.amsl.com>; Thu, 23 Jul 2009 09:12:37 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id E1D6B3A6AD3 for <rrg@irtf.org>; Thu, 23 Jul 2009 09:12:37 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n6NGC5Kr008087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 23 Jul 2009 09:12:05 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n6NGC5SK016746; Thu, 23 Jul 2009 09:12:05 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n6NGC4Du016692; Thu, 23 Jul 2009 09:12:05 -0700 (PDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 23 Jul 2009 09:12:00 -0700
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: Thu, 23 Jul 2009 09:12:02 -0700
Message-ID: <474EEBD229DF754FB83D256004D021080C34A85F@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <7B045821-8BBE-4946-A6A8-6FE1B596855A@cs.ucla.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Next topic: properties of identifiers
Thread-Index: AcoLYilZXOorhQSBRfGmPJccMaUAXgASWj4w
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	<4A4B6CA7.7080208@joelhalpern.com>	<8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com><36975B15-B7FA-4E7B-80EC-A2BD43701744@cs.ucla.edu> <4A5E1A7F.8070108@gmail.com> <474EEBD229DF754FB83D256004D021080C309E64@XCH-NW-6V1.nw.nos.boeing.com> <7B045821-8BBE-4946-A6A8-6FE1B596855A@cs.ucla.edu>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "Lixia Zhang" <lixia@cs.ucla.edu>
X-OriginalArrivalTime: 23 Jul 2009 16:12:00.0662 (UTC) FILETIME=[4F554B60:01CA0BB0]
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: Thu, 23 Jul 2009 16:12:38 -0000

Hi, Lixia!

Concerning my unclear statement (i.e., your "I do not see the
implication here." comment), what I was trying to convey is the
following logic flow:
1) not all identifiers should be at the IP layer -- some logically occur
at other layers
2) just because identifiers are at several layers, one can still
correlate between them (e.g., for network management or security) as
long as that layer isn't encrypted.

The reason I made this statement is that some postings seemed to imply
(or, at least, this is how I read them) that routing identifiers have to
solve all problems. I disagree: routing identifiers need to solve
routing problems but other problems can be solved by identifiers at
other layers.

This observation is hopefully obvious but what excites me is what it
means to ancillary requirements such as security and network management.
As you may know, I've been keen for about a decade on the concept of
"security zones" in which one can have unique policies for parts of a
routing infrastructure to handle unique requirements of a community of
interest. I therefore consider the various insights of the RRG postings
to see their implications to this type of goal, which is why I felt the
need to mention something which to others is hopefully obvious.
Specifically, security zones theoretically can be made by routing policy
at the IP layer (e.g., policy-based routing) but I am currently
discouraged at how this works, except for VPNs and map-and-encaps, which
really are parallel (complementary) routing systems. Therefore, I am
currently trying to do this at the "IPsec layer" or above. I am curious
whether LISP, for example, could be used to support security zones but I
haven't pursued that idea myself. I wonder if others have?

I am also naturally interested if others have had more success doing
security zones solely at the IP layer, but that is probably out-of-scope
for the RRG and so I didn't want to go there in postings to this WG.

-----Original Message-----
From: Lixia Zhang [mailto:lixia@cs.ucla.edu]=20
Sent: Wednesday, July 22, 2009 11:52 PM
To: Fleischman, Eric
Cc: rrg@irtf.org
Subject: Re: [rrg] Next topic: properties of identifiers

<snip>

> The thing that bothers me about this otherwise excellent discussion is

> that I interpret these emails as implying that all identifiers must be

> known at the IP layer.

Hi Eric, I do not see the implication here.

<snip>


From scott.brim@gmail.com  Thu Jul 23 10:57:32 2009
Return-Path: <scott.brim@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 1FF5128C13B for <rrg@core3.amsl.com>; Thu, 23 Jul 2009 10:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level: 
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.145,  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 78Zs9cQm3tcg for <rrg@core3.amsl.com>; Thu, 23 Jul 2009 10:57:31 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by core3.amsl.com (Postfix) with ESMTP id 06A2F3A6B0C for <rrg@irtf.org>; Thu, 23 Jul 2009 10:57:30 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 3so565538qwe.7 for <rrg@irtf.org>; Thu, 23 Jul 2009 10:56:55 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=1dvHKLiewFCOLLb/LbTgPeGSSlQAPqnEHNDINfmsk5I=; b=OWBCdFyQKoEwxCCNdto/r3UYxQeK85gJdMJ/EzZ0jWrLO7+jzWmpxWurxtTphLUMY5 VGy82TTKpEXCTjnhXfvsdOjBrdxd+gXW+DWjxPArrWcWEogThwcU/GeKZ/suT4oN85+f jQci/TgoIE/ri/hebaST4fxppT1a6Xu5isrXs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=i8APULA+hMJFuqjnmLyNH8ESWu68SAMuq0DARSzuxD6bfDZ4kCmSPA2yYBXNg+YX2m yCRdREFUTF2kYmrXj1wxk9SHTZtvAqxXYk4m9fn5++BDS45WqsQVKNtoKI5Ud3MqHE6C +V+SUxJ+KUjRY54qB9AMyKiNB7IRSPoL0slkI=
Received: by 10.224.19.202 with SMTP id c10mr2376635qab.101.1248371472079; Thu, 23 Jul 2009 10:51:12 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 5sm2947171qwg.55.2009.07.23.10.51.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 23 Jul 2009 10:51:10 -0700 (PDT)
Message-ID: <4A68A30B.7090100@gmail.com>
Date: Thu, 23 Jul 2009 19:51:07 +0200
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	<4A4B6CA7.7080208@joelhalpern.com>	<8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com><36975B15-B7FA-4E7B-80EC-A2BD43701744@cs.ucla.edu>	<4A5E1A7F.8070108@gmail.com>	<474EEBD229DF754FB83D256004D021080C309E64@XCH-NW-6V1.nw.nos.boeing.com>	<7B045821-8BBE-4946-A6A8-6FE1B596855A@cs.ucla.edu> <474EEBD229DF754FB83D256004D021080C34A85F@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080C34A85F@XCH-NW-6V1.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 23 Jul 2009 17:57:32 -0000

Fleischman, Eric allegedly wrote on 07/23/2009 6:12 PM:
> This observation is hopefully obvious but what excites me is what it
> means to ancillary requirements such as security and network management.
> As you may know, I've been keen for about a decade on the concept of
> "security zones" in which one can have unique policies for parts of a
> routing infrastructure to handle unique requirements of a community of
> interest. I therefore consider the various insights of the RRG postings
> to see their implications to this type of goal, which is why I felt the
> need to mention something which to others is hopefully obvious.
> Specifically, security zones theoretically can be made by routing policy
> at the IP layer (e.g., policy-based routing) but I am currently
> discouraged at how this works, except for VPNs and map-and-encaps, which
> really are parallel (complementary) routing systems. Therefore, I am
> currently trying to do this at the "IPsec layer" or above. 

It would seem to me that this depends on the what you need to secure. If
you don't want the world to know your IP addresses then you hide them.
If topology, hide routing and addressing. If you don't care about those
but just higher layer objects, you hide them instead, and so on.

> I am curious
> whether LISP, for example, could be used to support security zones but I
> haven't pursued that idea myself. I wonder if others have?

Sure.

Scott


From brian.e.carpenter@gmail.com  Thu Jul 23 14:38:26 2009
Return-Path: <brian.e.carpenter@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 0BCA03A6B6E for <rrg@core3.amsl.com>; Thu, 23 Jul 2009 14:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.228
X-Spam-Level: 
X-Spam-Status: No, score=-2.228 tagged_above=-999 required=5 tests=[AWL=0.371,  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 oKpWLFVHGtrI for <rrg@core3.amsl.com>; Thu, 23 Jul 2009 14:38:25 -0700 (PDT)
Received: from mail-pz0-f195.google.com (mail-pz0-f195.google.com [209.85.222.195]) by core3.amsl.com (Postfix) with ESMTP id 0B1633A68D1 for <rrg@irtf.org>; Thu, 23 Jul 2009 14:38:24 -0700 (PDT)
Received: by pzk33 with SMTP id 33so820351pzk.15 for <rrg@irtf.org>; Thu, 23 Jul 2009 14:38:25 -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:references :in-reply-to:content-type:content-transfer-encoding; bh=MIVdLU4ahWjXa1XqOECJul/XlpNv/0GZSs1SUeSmDug=; b=mpexog1LtDcz8D+eFyO0kCT/Gn8sfokKzVO2ihtYllb9pt53Gl6lQrQI+Wyb1f5V74 RghPczA8qcYou5ibVQmLEmTYPK+9NTeXqcMpKjkqw3LC9yOG7H9tVmtHOJ3BksLh4cHW UuZfl6AFvKb80KGl3cuRiT0RXKiYqhkzszJnw=
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:references:in-reply-to:content-type :content-transfer-encoding; b=HXmpTApqcaww3nCFcjJFYAVc4uMGLmq1n1+WNm5u1KLufPpOXZdDaCHUl9VJPucuhA 9W+JIaoxQNrExI9Cwwe4kvrFMI4e8R6T12S8n/hnw4RcR5sWbUU/32uT0q5TQrjLCEy+ 3WLGViMdYO4MGpgCCs5Q7yIiF8s2Avf0S1fjA=
Received: by 10.115.18.7 with SMTP id v7mr3132882wai.185.1248385105102; Thu, 23 Jul 2009 14:38:25 -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 c26sm4695411waa.50.2009.07.23.14.38.22 (version=SSLv3 cipher=RC4-MD5); Thu, 23 Jul 2009 14:38:24 -0700 (PDT)
Message-ID: <4A68D82D.6000709@gmail.com>
Date: Fri, 24 Jul 2009 09:37:49 +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: "Fleischman, Eric" <eric.fleischman@boeing.com>
References: <DB3E5D6F36600847BC70D451534EBCD504EF80B7@E03MVB2-UKBR.domain1.systemhost.net>	<4A4B6CA7.7080208@joelhalpern.com>	<8A532E12-1CC1-40EB-B604-8F5EA3BADAFB@ericsson.com><36975B15-B7FA-4E7B-80EC-A2BD43701744@cs.ucla.edu>	<4A5E1A7F.8070108@gmail.com>	<474EEBD229DF754FB83D256004D021080C309E64@XCH-NW-6V1.nw.nos.boeing.com>	<7B045821-8BBE-4946-A6A8-6FE1B596855A@cs.ucla.edu> <474EEBD229DF754FB83D256004D021080C34A85F@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080C34A85F@XCH-NW-6V1.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Thu, 23 Jul 2009 21:38:26 -0000

On 2009-07-24 04:12, Fleischman, Eric wrote:
> Hi, Lixia!
> 
> Concerning my unclear statement (i.e., your "I do not see the
> implication here." comment), what I was trying to convey is the
> following logic flow:
> 1) not all identifiers should be at the IP layer -- some logically occur
> at other layers
> 2) just because identifiers are at several layers, one can still
> correlate between them (e.g., for network management or security) as
> long as that layer isn't encrypted.

Agreed on both counts. Slightly orthogonally, there's
draft-carpenter-behave-referral-object-00.txt, which aims at how
the applications layer might achieve 2), among other things.
But in writing that, we found ourselves pretty much forced to
tackle the problem of identifiers for addressing scopes,
i.e. a form of meta-identifier at layer 3.

   Brian

> 
> The reason I made this statement is that some postings seemed to imply
> (or, at least, this is how I read them) that routing identifiers have to
> solve all problems. I disagree: routing identifiers need to solve
> routing problems but other problems can be solved by identifiers at
> other layers.
> 
> This observation is hopefully obvious but what excites me is what it
> means to ancillary requirements such as security and network management.
> As you may know, I've been keen for about a decade on the concept of
> "security zones" in which one can have unique policies for parts of a
> routing infrastructure to handle unique requirements of a community of
> interest. I therefore consider the various insights of the RRG postings
> to see their implications to this type of goal, which is why I felt the
> need to mention something which to others is hopefully obvious.
> Specifically, security zones theoretically can be made by routing policy
> at the IP layer (e.g., policy-based routing) but I am currently
> discouraged at how this works, except for VPNs and map-and-encaps, which
> really are parallel (complementary) routing systems. Therefore, I am
> currently trying to do this at the "IPsec layer" or above. I am curious
> whether LISP, for example, could be used to support security zones but I
> haven't pursued that idea myself. I wonder if others have?
> 
> I am also naturally interested if others have had more success doing
> security zones solely at the IP layer, but that is probably out-of-scope
> for the RRG and so I didn't want to go there in postings to this WG.
> 
> -----Original Message-----
> From: Lixia Zhang [mailto:lixia@cs.ucla.edu] 
> Sent: Wednesday, July 22, 2009 11:52 PM
> To: Fleischman, Eric
> Cc: rrg@irtf.org
> Subject: Re: [rrg] Next topic: properties of identifiers
> 
> <snip>
> 
>> The thing that bothers me about this otherwise excellent discussion is
> 
>> that I interpret these emails as implying that all identifiers must be
> 
>> known at the IP layer.
> 
> Hi Eric, I do not see the implication here.
> 
> <snip>
> 
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
> 

From surfer@mauigateway.com  Fri Jul 24 13:08:59 2009
Return-Path: <surfer@mauigateway.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 5CE563A6A93 for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 13:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.762
X-Spam-Level: **
X-Spam-Status: No, score=2.762 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, URI_HEX=0.368]
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 IPygfmyS9qQJ for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 13:08:58 -0700 (PDT)
Received: from omta0109.mta.everyone.net (imta-38.everyone.net [216.200.145.38]) by core3.amsl.com (Postfix) with ESMTP id 39ACD3A6852 for <rrg@irtf.org>; Fri, 24 Jul 2009 13:08:37 -0700 (PDT)
Received: from dm24.mta.everyone.net (sj1-slb03-gw2 [172.16.1.96]) by omta0109.mta.everyone.net (Postfix) with ESMTP id 465EA2881E8 for <rrg@irtf.org>; Fri, 24 Jul 2009 13:08:17 -0700 (PDT)
X-Eon-Dm: dm24
Received: by resin18.mta.everyone.net (EON-PICKUP) id resin18.4a69e98a.9af6; Fri, 24 Jul 2009 13:08:16 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20090724130816.ADB80B65@resin18.mta.everyone.net>
Date: Fri, 24 Jul 2009 13:08:16 -0700
From: "Scott Weeks" <surfer@mauigateway.com>
To: <rrg@irtf.org>
X-Eon-Sig: AQLAznNKahSwMAhyQwEAAAAB,efba14c19acd208ab8f15e4981b70f99
X-Originating-Ip: [72.253.67.95]
Subject: [rrg] A Challenge for Researchers by John Day
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: surfer@mauigateway.com
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, 24 Jul 2009 20:08:59 -0000

I hope this is acceptable to post here...  

I just finished the book "Patterns in Network Architecture: A Return to Fundamentals" by John Day and was going through the 'Documents and Publications' section of pouzinsociety.org where I found this:  "A Challenge for Researchers" - http://02d7097.netsolhost.com/images/A_Challenge_for_Researchers.pdf

Knowing there is a researcher or two on this list ;-) I wanted to forward it onto the group.  To me (an operator interested in the architecture of the internet and its future, not a researcher) it's a very interesting idea!

scott






































-------------------
--------------------
--------------------


From wherrin@gmail.com  Fri Jul 24 14:09:13 2009
Return-Path: <wherrin@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 CA8393A689A for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 14:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.609
X-Spam-Level: 
X-Spam-Status: No, score=-1.609 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, URI_HEX=0.368]
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 k2AWi0qhe7Qd for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 14:09:12 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by core3.amsl.com (Postfix) with ESMTP id B2CC23A67FD for <rrg@irtf.org>; Fri, 24 Jul 2009 14:09:12 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c38so961775ana.37 for <rrg@irtf.org>; Fri, 24 Jul 2009 14:09:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=1pitzdAfRkHOslvADuW4E9WX6kr1uZ6WKp+ksN+/2ew=; b=Ku9mwRmv+uQgxpXHyGRFDv7CI3W6U+/mqPk6EbDyAP8f9VpA1c7ElfUslSjRfLMHzh Fe8rOoViGTs3IC2O4XdRj+b8fd+em1ycvdUJFy0qakPrRf2i93NaBPGmuHdLmcNiDnJ4 gPQ4C1FymS5hpJJ6+qUzOsBhZK8qep0vyuO9s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=MOLOwZzl0KpcJpANcUKR9dncyYaq+h83ya5OSgJ93EDITx9mpG4udszTphGIpp15a5 ay5kfjI26uU+9zq6VkQHQVtAM0PvOr7COA7pPERcKA8PONja1Vkql42HGLODlrY/Gt0i 6vHiRxKPm+XiK9tsbpxhAbFu/Ctb2woXRg4t4=
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.100.163.15 with SMTP id l15mr5151520ane.22.1248469752717; Fri,  24 Jul 2009 14:09:12 -0700 (PDT)
In-Reply-To: <20090724130816.ADB80B65@resin18.mta.everyone.net>
References: <20090724130816.ADB80B65@resin18.mta.everyone.net>
Date: Fri, 24 Jul 2009 17:09:12 -0400
X-Google-Sender-Auth: 3a6c773ad9632919
Message-ID: <3c3e3fca0907241409g577888b9v64bce7ccba5c9292@mail.gmail.com>
From: William Herrin <bill@herrin.us>
To: surfer@mauigateway.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rrg@irtf.org
Subject: Re: [rrg] A Challenge for Researchers by John Day
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, 24 Jul 2009 21:09:13 -0000

On Fri, Jul 24, 2009 at 4:08 PM, Scott Weeks<surfer@mauigateway.com> wrote:
> I hope this is acceptable to post here...
>
> I just finished the book "Patterns in Network Architecture: A Return to F=
undamentals" by John Day and was going through the 'Documents and Publicati=
ons' section of pouzinsociety.org where I found this: =A0"A Challenge for R=
esearchers" - http://02d7097.netsolhost.com/images/A_Challenge_for_Research=
ers.pdf
>
> Knowing there is a researcher or two on this list ;-) I wanted to forward=
 it onto the group. =A0To me (an operator interested in the architecture of=
 the internet and its future, not a researcher) it's a very interesting ide=
a!


Hi Scott,

This came around back in April and I asked:

http://www.irtf.org/mail-archive/web/rrg/current/msg04922.html

If anyone offers an answer, I'll take another look. Until then, John
has a vaguely interesting idea but we have no shortage of vaguely
interesting ideas here and it's not our role to show whether or why an
incomplete concept can't be completed.

Regards,
Bill Herrin


--=20
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004

From scott.brim@gmail.com  Fri Jul 24 14:54:02 2009
Return-Path: <scott.brim@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 02C003A6930 for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 14:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.48
X-Spam-Level: 
X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119,  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 cQ5gLWeHPOr2 for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 14:54:01 -0700 (PDT)
Received: from mail-qy0-f194.google.com (mail-qy0-f194.google.com [209.85.221.194]) by core3.amsl.com (Postfix) with ESMTP id 388D83A68D9 for <rrg@irtf.org>; Fri, 24 Jul 2009 14:54:01 -0700 (PDT)
Received: by qyk32 with SMTP id 32so2366941qyk.15 for <rrg@irtf.org>; Fri, 24 Jul 2009 14:54:00 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=rgnPCyJcoF0Y6q3nU3OdA/Lo8rBuCfEDwsY5GbRsfmY=; b=RgF2qdU+GUj8snoPljS+CZwT27FOs88pKlEeNs8VQRYXGn88xd4qp3hDEuLivrJUwz G6lBwyuhWqc32wnVF7q3SIKvGtIV9oOtiTDV2StkTYx4jaXImcUeoJifVSs/r4HtloaZ FcK1VuDWIl19Nh+rmdDtquYLuKTSh1he5sw88=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=oI7u7akSAY8VKgpFDeqpuehF31OFF2907PoV5InuZMrd/ggGP0CYMxIuTPVj4s7sC+ qfgVrAJqEfhSnjo3yNq4VAzt49VDeDOszKJ4DWmwfAjYWQCEJBNWITlZruaeeXsxXg+l UtX4iGrzxOwdgxRyJkq0bLP+1jZh7qSsAss1U=
Received: by 10.224.67.204 with SMTP id s12mr3835118qai.293.1248472440252; Fri, 24 Jul 2009 14:54:00 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 6sm5626538qwd.42.2009.07.24.14.53.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 24 Jul 2009 14:53:59 -0700 (PDT)
Message-ID: <4A6A2D75.9070407@gmail.com>
Date: Fri, 24 Jul 2009 23:53:57 +0200
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: surfer@mauigateway.com
References: <20090724130816.ADB80B65@resin18.mta.everyone.net>
In-Reply-To: <20090724130816.ADB80B65@resin18.mta.everyone.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: rrg@irtf.org
Subject: Re: [rrg] A Challenge for Researchers by John Day
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, 24 Jul 2009 21:54:02 -0000

In the meantime look for the pna-discuss group in Google Groups.

From wherrin@gmail.com  Fri Jul 24 15:07:39 2009
Return-Path: <wherrin@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 75E163A6BDE for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 15:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.793
X-Spam-Level: 
X-Spam-Status: No, score=-1.793 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 MSifWSkr1Rql for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 15:07:38 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by core3.amsl.com (Postfix) with ESMTP id 738AB3A6B98 for <rrg@irtf.org>; Fri, 24 Jul 2009 15:07:38 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c38so978402ana.37 for <rrg@irtf.org>; Fri, 24 Jul 2009 15:07:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=cL5zlJyJJh592s+zpfOl1E0cwrs6zI13Ebmw27Rz4MA=; b=l7FINNVQZ9tiXi0LDwp4UgNK07+DAUV3wFWLJNhKCjRIlj13QOEHh4shxSdpIH60VU +A+bmaFgeDOItoqwxs9YP0+r5IWy1sUacLfU401uaLqKFmpRuLwF8tjno5iMEQkYOiSF AYhqyIZtdN67qjWBvl1d/AA7y57Se+S4YQfIU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=vepkZzN1ChJHbQ4N0UGvfx77dsj0klNjouNSsmOUZ3MregxxxSzyKc15cLm5R+SEtf Vo0B5XnjcDqWab6tbo0JbYECZC1ugTBcZIgLObwlZyWCCuP7uSMDOYwekCdtHkpINZgJ LfdDseoXGD/bNxIlkfgXFioctk0DUlCea3OdM=
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.100.107.8 with SMTP id f8mr4910762anc.197.1248472791149; Fri,  24 Jul 2009 14:59:51 -0700 (PDT)
In-Reply-To: <C304DB494AC0C04C87C6A6E2FF5603DB2283082F12@NDJSSCC01.ndc.nasa.gov>
References: <20090724130816.ADB80B65@resin18.mta.everyone.net> <3c3e3fca0907241409g577888b9v64bce7ccba5c9292@mail.gmail.com> <C304DB494AC0C04C87C6A6E2FF5603DB2283082F12@NDJSSCC01.ndc.nasa.gov>
Date: Fri, 24 Jul 2009 17:59:51 -0400
X-Google-Sender-Auth: 8d40b9c6115fb6ae
Message-ID: <3c3e3fca0907241459j9dc0b09k7cea24e97656c1be@mail.gmail.com>
From: William Herrin <bill@herrin.us>
To: "Eddy, Wesley M. (GRC-MS00)[Verizon]" <wesley.m.eddy@nasa.gov>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "rrg@irtf.org" <rrg@irtf.org>
Subject: Re: [rrg] A Challenge for Researchers by John Day
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, 24 Jul 2009 22:07:39 -0000

On Fri, Jul 24, 2009 at 5:25 PM, Eddy, Wesley M.
(GRC-MS00)[Verizon]<wesley.m.eddy@nasa.gov> wrote:
> Day's PNA is more than "vaguely interesting" as it (correctly)
> factors networking functions into the common primitives that
> recurse throughout all of the existing stacks in use, and
> differences between layers as policy rather than protocol. =A0It
> further develops naming & resolution of processes within a
> Distributed IPC Facility (DIF) / layer, and describes just what
> you asked for in intimate detail.

Wes,

At the risk of revealing myself to be a cheap bastard, who will refund
my fifty bucks if it doesn't? Certainly nothing I found on
pouzinsociety.org hinted at the answer to my question though I'd be
happy to have you point out what I missed.

Seriously: if you think the idea has merit, lets dive in to the
nitty-gritty of how it might work. That is, after all, what this
research group is for.

Convince me there's more here than a half-formed abstraction and I
-will- go buy the book. If not, I'll wait for the movie.

Regards,
Bill



--=20
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004

From lixia@cs.ucla.edu  Sat Jul 25 00:05:40 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 83B043A6853 for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 00:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level: 
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599, URI_HEX=0.368]
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 mg6T1LOKU2Q3 for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 00:05:39 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id B47B23A691D for <rrg@irtf.org>; Sat, 25 Jul 2009 00:05:39 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id BFCDC39E80F0; Sat, 25 Jul 2009 00:05:40 -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 CktPl8xwc1sg; Sat, 25 Jul 2009 00:05:37 -0700 (PDT)
Received: from [10.0.1.2] (cpe-98-151-51-242.socal.res.rr.com [98.151.51.242]) by smtp.cs.ucla.edu (Postfix) with ESMTP id F399839E80D9; Sat, 25 Jul 2009 00:05:36 -0700 (PDT)
Message-Id: <E2ECBE4D-EFDB-411B-9D9B-64EB091ECB80@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: William Herrin <bill@herrin.us>
In-Reply-To: <3c3e3fca0907241409g577888b9v64bce7ccba5c9292@mail.gmail.com>
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, 25 Jul 2009 00:05:36 -0700
References: <20090724130816.ADB80B65@resin18.mta.everyone.net> <3c3e3fca0907241409g577888b9v64bce7ccba5c9292@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
Cc: rrg@irtf.org
Subject: Re: [rrg] A Challenge for Researchers by John Day
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, 25 Jul 2009 07:05:40 -0000

On Jul 24, 2009, at 2:09 PM, William Herrin wrote:

> On Fri, Jul 24, 2009 at 4:08 PM, Scott Weeks<surfer@mauigateway.com>  
> wrote:
>> I hope this is acceptable to post here...
>>
>> I just finished the book "Patterns in Network Architecture: A  
>> Return to Fundamentals" by John Day and was going through the  
>> 'Documents and Publications' section of pouzinsociety.org where I  
>> found this:  "A Challenge for Researchers" - http://02d7097.netsolhost.com/images/A_Challenge_for_Researchers.pdf
>>
>> Knowing there is a researcher or two on this list ;-) I wanted to  
>> forward it onto the group.  To me (an operator interested in the  
>> architecture of the internet and its future, not a researcher) it's  
>> a very interesting idea!
>
>
> Hi Scott,
>
> This came around back in April and I asked:
>
> http://www.irtf.org/mail-archive/web/rrg/current/msg04922.html
>
> If anyone offers an answer, I'll take another look. Until then, John
> has a vaguely interesting idea but we have no shortage of vaguely
> interesting ideas here

I would agree with that statement :-)

> and it's not our role to show whether or why an
> incomplete concept can't be completed.

I just replied Steve privately suggesting that the architecture list  
may be a good place to send this pointer to.
My reason: the starting point and the basic reasoning of that short  
(and very interesting) article is not IPC, but a basic understanding  
of how to do system research (great subject for a broader discussion).

Lixia


From tony.li@tony.li  Sat Jul 25 11:23:52 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 81ED73A68D3 for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 11:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 qIh1cEGQRQsr for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 11:23:51 -0700 (PDT)
Received: from QMTA09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by core3.amsl.com (Postfix) with ESMTP id 3C72C3A6877 for <rrg@irtf.org>; Sat, 25 Jul 2009 11:23:48 -0700 (PDT)
Received: from OMTA08.westchester.pa.mail.comcast.net ([76.96.62.12]) by QMTA09.westchester.pa.mail.comcast.net with comcast id LHhs1c0020Fqzac59JPpio; Sat, 25 Jul 2009 18:23:49 +0000
Received: from [10.43.1.99] ([77.241.97.116]) by OMTA08.westchester.pa.mail.comcast.net with comcast id LJPc1c00K2WfiAM3UJPfkB; Sat, 25 Jul 2009 18:23:47 +0000
Message-ID: <4A6B3193.9060704@tony.li>
Date: Sat, 25 Jul 2009 09:23:47 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Christian Vogt <christian.vogt@ericsson.com>
References: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net> <8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com>
In-Reply-To: <8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 25 Jul 2009 18:23:52 -0000

[Catching up...]

Christian Vogt wrote:
> 
> 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?


Well, to me, central to the notion of the Internet architecture and more 
specifically to a routing architecture is the notion of topology.  It 
would seem somewhat challenging to be able to describe topology without 
being able to describe a graph.  And if we want to be able to describe a 
graph, we need to be able to articulate the nodes and edges in that 
graph.  I don't see how to do this with just service identifiers.

Regards,
Tony



From scott.brim@gmail.com  Sat Jul 25 13:04:10 2009
Return-Path: <scott.brim@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 4B2493A68B3 for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 13:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 b07gGjR-zVyS for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 13:04:09 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by core3.amsl.com (Postfix) with ESMTP id 4DF7B3A692C for <rrg@irtf.org>; Sat, 25 Jul 2009 13:04:09 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 9so520073eyd.7 for <rrg@irtf.org>; Sat, 25 Jul 2009 13:04:07 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=J0nQ1ie881hUjpsW4irRcNsPEFnVpiJUa/ky6YyWlK4=; b=a84EE8X0xhH3WSyl60X/pU++o/JXI15e5YKYC6gVr23IJR3TSalq2tIRnntB1HiYN4 h+rM2WgRPjTSU562sxoMYR5DCWgTgfNJZjMAw3FX9+rYAHC3AWKgz3FLjoT23ICro0Wr D4TQryka3ZN9xQBlz7jcKKMvlpn+SH08ymTDA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=TRJNzzqadryqqYf3NyDRuk7mr2mdgqkfHlBIkKo1nX0jGuaWcsrLCWVG5enAQFiXpJ 5kJRSvE28S7etBQAovfBnNnjYRwAyTnnjK2VtrHr19hmbg50GM/HQDLJNzELaBnCGoo5 9CfaG6gc1RZkN4DMhsIKVEydPbJPcVMUGtOUE=
Received: by 10.211.194.4 with SMTP id w4mr6055770ebp.46.1248552247161; Sat, 25 Jul 2009 13:04:07 -0700 (PDT)
Received: from sbrim-mbp.local ([77.241.97.148]) by mx.google.com with ESMTPS id 7sm4309948eyg.26.2009.07.25.13.04.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 25 Jul 2009 13:04:06 -0700 (PDT)
Message-ID: <4A6B6534.7000606@gmail.com>
Date: Sat, 25 Jul 2009 22:04:04 +0200
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net>	<8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com> <4A6B3193.9060704@tony.li>
In-Reply-To: <4A6B3193.9060704@tony.li>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: rrg@irtf.org, Christian Vogt <christian.vogt@ericsson.com>
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, 25 Jul 2009 20:04:10 -0000

Tony Li allegedly wrote on 07/25/2009 6:23 PM:
> Well, to me, central to the notion of the Internet architecture and more
> specifically to a routing architecture is the notion of topology.  It
> would seem somewhat challenging to be able to describe topology without
> being able to describe a graph.  And if we want to be able to describe a
> graph, we need to be able to articulate the nodes and edges in that
> graph.  I don't see how to do this with just service identifiers.
> 
> Regards,
> Tony

An excellent thought-provoking post, although in the end I somewhat
disagree.  From the point of view of the network, the nodes in the graph
are attachment points, not hosts.  Attachment points are where the
network stops.  We do have names for those points without invoking node
identifiers -- according to
<http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGTerminology> they
are called locators.  Of course forwarding functions will use whatever
they want as input, including things that some people call
"identifiers", but that extra information is not necessary to describe
topology.

See you ... Scott


From tony.li@tony.li  Sat Jul 25 21:54:02 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 5BD2128C0E1 for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 21:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Elpkejx1eKOB for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 21:54:01 -0700 (PDT)
Received: from QMTA05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by core3.amsl.com (Postfix) with ESMTP id C71763A6B90 for <rrg@irtf.org>; Sat, 25 Jul 2009 21:53:59 -0700 (PDT)
Received: from OMTA10.emeryville.ca.mail.comcast.net ([76.96.30.28]) by QMTA05.emeryville.ca.mail.comcast.net with comcast id LUcZ1c0030cQ2SLA5Uu16y; Sun, 26 Jul 2009 04:54:01 +0000
Received: from [10.43.1.99] ([77.241.97.116]) by OMTA10.emeryville.ca.mail.comcast.net with comcast id LUtm1c0042WfiAM8WUtptM; Sun, 26 Jul 2009 04:53:59 +0000
Message-ID: <4A6BE12F.9070809@tony.li>
Date: Sun, 26 Jul 2009 06:53:03 +0200
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
References: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net>	<8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com> <4A6B3193.9060704@tony.li> <4A6B6534.7000606@gmail.com>
In-Reply-To: <4A6B6534.7000606@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: rrg@irtf.org, Christian Vogt <christian.vogt@ericsson.com>
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, 26 Jul 2009 04:54:02 -0000

Scott Brim wrote:

> An excellent thought-provoking post, although in the end I somewhat
> disagree.  From the point of view of the network, the nodes in the graph
> are attachment points, not hosts.  Attachment points are where the
> network stops.  We do have names for those points without invoking node
> identifiers -- according to
> <http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGTerminology> they
> are called locators.  Of course forwarding functions will use whatever
> they want as input, including things that some people call
> "identifiers", but that extra information is not necessary to describe
> topology.


Well, for the most part we seem to be using locators to name the edges 
of the graph, not the nodes.  If we only have locators, it makes it very 
challenging to describe topology.  How do you deal with the case where 
there are two nodes that are both connected to two edges?

Tony

From menth@informatik.uni-wuerzburg.de  Sat Jul 25 22:48:28 2009
Return-Path: <menth@informatik.uni-wuerzburg.de>
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 3BA723A6A26 for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 22:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 4XoHioUFDsFj for <rrg@core3.amsl.com>; Sat, 25 Jul 2009 22:48:27 -0700 (PDT)
Received: from mailrelay.rz.uni-wuerzburg.de (mailrelay.rz.uni-wuerzburg.de [132.187.3.28]) by core3.amsl.com (Postfix) with ESMTP id D953C3A699F for <rrg@irtf.org>; Sat, 25 Jul 2009 22:48:26 -0700 (PDT)
Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id 509E7A0869; Sun, 26 Jul 2009 07:48:25 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id 43A4BA085A; Sun, 26 Jul 2009 07:48:25 +0200 (CEST)
Received: from [192.168.1.2] (g227039017.adsl.alicedsl.de [92.227.39.17]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id E5B9B19918A; Sun, 26 Jul 2009 07:48:24 +0200 (CEST)
Message-ID: <4A6BEE28.10809@informatik.uni-wuerzburg.de>
Date: Sun, 26 Jul 2009 07:48:24 +0200
From: Michael Menth <menth@informatik.uni-wuerzburg.de>
Organization: University of Wuerzburg
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net>	<8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com>	<4A6B3193.9060704@tony.li> <4A6B6534.7000606@gmail.com> <4A6BE12F.9070809@tony.li>
In-Reply-To: <4A6BE12F.9070809@tony.li>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de
Cc: rrg@irtf.org, Scott Brim <scott.brim@gmail.com>, Christian Vogt <christian.vogt@ericsson.com>
Subject: Re: [rrg] Next topic: properties of identifiers
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: menth@informatik.uni-wuerzburg.de
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, 26 Jul 2009 05:48:28 -0000

Tony Li schrieb:
> Scott Brim wrote:
>
>> An excellent thought-provoking post, although in the end I somewhat
>> disagree.  From the point of view of the network, the nodes in the graph
>> are attachment points, not hosts.  Attachment points are where the
>> network stops.  We do have names for those points without invoking node
>> identifiers -- according to
>> <http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGTerminology> they
>> are called locators.  Of course forwarding functions will use whatever
>> they want as input, including things that some people call
>> "identifiers", but that extra information is not necessary to describe
>> topology.
>
>
> Well, for the most part we seem to be using locators to name the edges 
> of the graph, not the nodes.  If we only have locators, it makes it 
> very challenging to describe topology.  How do you deal with the case 
> where there are two nodes that are both connected to two edges?
>
> Tony
The edges have two different names then? Sticking to one of them would 
imply that when used for hierarchical routing, multihoming becomes more 
difficult again? Or is this view too much constrained by current Loc/ID 
background?

Michael

-- 
Dr. Michael Menth, Assistant Professor
University of Wuerzburg, Institute of Computer Science
Am Hubland, D-97074 Wuerzburg, Germany, room B206
phone: (+49)-931/31-86644 (new), fax: (+49)-931/888-6632
mailto:menth@informatik.uni-wuerzburg.de
http://www3.informatik.uni-wuerzburg.de/research/ngn


From HeinerHummel@aol.com  Sun Jul 26 01:22:23 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 32C403A6BB7 for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 01:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
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 d6KVlFgklWFS for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 01:22:22 -0700 (PDT)
Received: from imo-m27.mx.aol.com (imo-m27.mx.aol.com [64.12.137.8]) by core3.amsl.com (Postfix) with ESMTP id 32CBE3A67D0 for <rrg@irtf.org>; Sun, 26 Jul 2009 01:22:22 -0700 (PDT)
Received: from imo-ma03.mx.aol.com (imo-ma03.mx.aol.com [64.12.78.138]) by imo-m27.mx.aol.com (v107.10) with ESMTP id RELAYIN1-24a6c12379e; Sun, 26 Jul 2009 04:22:15 -0400
Received: from HeinerHummel@aol.com by imo-ma03.mx.aol.com  (mail_out_v40_r1.5.) id i.cd4.5226f54e (32914);  Sun, 26 Jul 2009 04:22:11 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <cd4.5226f54e.379d6c33@aol.com>
Date: Sun, 26 Jul 2009 04:22:11 EDT
To: tony.li@tony.li, christian.vogt@ericsson.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1248596531"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-IP: 64.12.78.138
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: Sun, 26 Jul 2009 08:22:23 -0000

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

 
In einer eMail vom 25.07.2009 20:24:19 Westeurop=E4ische Normalzeit schrei=
bt  
tony.li@tony.li:

Well, to  me, central to the notion of the Internet architecture and more=
  
specifically to a routing architecture is the notion of topology.  It  
would seem somewhat challenging to be able to describe topology without =
 
being able to describe a graph.  And if we want to be able to  describe a=
 
graph, we need to be able to articulate the nodes and edges in  that 
graph.  I don't see how to do this with just service  identifiers.

Regards,
Tony



Right.For the same reason I don't understand either to have a service  
identifier discussion here.
Routing is about recognizing and utilizing topology.By knowing the topolog=
y 
 you can see all paths in forward direction wrt a given destination as wel=
l 
as  which network part would use you for transit (the rear mirror).
You have much less by assembling hundred thousands of routes instead.
 
Heiner

-------------------------------1248596531
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 content=3D"text/html; charset=3DISO-8859-1" http-equiv=3DContent-Typ=
e>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18783"></HEAD>
<BODY style=3D"FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=3Dr=
ole_body 
bottomMargin=3D7 leftMargin=3D7 rightMargin=3D7 topMargin=3D7><FONT id=3Dr=
ole_document 
color=3D#000000 size=3D2 face=3DArial>
<DIV>
<DIV>In einer eMail vom 25.07.2009 20:24:19 Westeurop=E4ische Normalzeit=
 schreibt 
tony.li@tony.li:</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=3D=
Arial>Well, to 
  me, central to the notion of the Internet architecture and more 
  <BR>specifically to a routing architecture is the notion of topology.&nb=
sp; It 
  <BR>would seem somewhat challenging to be able to describe topology with=
out 
  <BR>being able to describe a graph.&nbsp; And if we want to be able to=
 
  describe a <BR>graph, we need to be able to articulate the nodes and edg=
es in 
  that <BR>graph.&nbsp; I don't see how to do this with just service 
  identifiers.<BR><BR>Regards,<BR>Tony<BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>Right.For the same reason I don't understand either to have a service=
 
identifier discussion here.</DIV>
<DIV>Routing is about recognizing and utilizing topology.By knowing the to=
pology 
you can see all paths in forward direction wrt a given destination as well=
 as 
which network part would use you for transit (the rear mirror).</DIV>
<DIV>You have much less by assembling hundred thousands of routes instead.=
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>

-------------------------------1248596531--

From jnc@mercury.lcs.mit.edu  Sun Jul 26 06:33:17 2009
Return-Path: <jnc@mercury.lcs.mit.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 8A9F73A697F for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 06:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 2-e5nETJXp3o for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 06:33:16 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 990663A6887 for <rrg@irtf.org>; Sun, 26 Jul 2009 06:33:16 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id A081A6BE567; Sun, 26 Jul 2009 09:33:16 -0400 (EDT)
To: rrg@irtf.org
Message-Id: <20090726133316.A081A6BE567@mercury.lcs.mit.edu>
Date: Sun, 26 Jul 2009 09:33:16 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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, 26 Jul 2009 13:33:17 -0000

    > From: Tony Li <tony.li@tony.li>

    > Well, to me, central to the notion of the Internet architecture and
    > qmore specifically to a routing architecture is the notion of topology.
    > It would seem somewhat challenging to be able to describe topology
    > without being able to describe a graph.

I agree pretty much 100% with all you've said, but one minor caveat (and the
credit for this observation goes to someone else, but I can't remember who,
or what mailing list - sorry): using a graph as a model of the network
connectivity (probably a more accurate term than 'topology', but I think
we're stuck with the latter now) usually works very well, but... it is not
necessarily the be-all and end-all. For some networks (e.g. wireless) it may
not work so well. Graphs do have issues in other cases too, e.g. this one:

  http://mercury.lcs.mit.edu/~jnc/tech/abstraction_flame.html

Having said that, I don't have what I consider a superior alternative, for
the mathematical model of network connectivity, here in my hip-pocket, ready
to offer. Like a like of things in routing, there are trade-offs: accuracy
versus amount of information needed to describe a particular connectivity
pattern is one, and for _most_ networks, using a graph to model the
connectivity does really, really well on this.

I don't know how difficult it would be to come up with a routing architecture
that could support multiple models simultaneously (e.g. a graph for most of
the network, but other stuff for local regions, e.g. perhaps something
geographic for a wirless network, etc, etc). My intuition says it would
probably be hard (impossible) to design an architecture where one could
incrementally deploy new models in an interoperable way.

But all that is pretty advanced - we're still a long way from an architecture
which would allow even simpler stuff, like multiple path-selection algorithms
with incremental deployment of new ones, local control of abstraction, etc. (I
mean a long way in deployment terms - a vaguely plausible design was done a
long time ago.)

	Noel

From jnc@mercury.lcs.mit.edu  Sun Jul 26 06:56:34 2009
Return-Path: <jnc@mercury.lcs.mit.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 AE69D3A6A90 for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 06:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 c1zOPs4X5OTf for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 06:56:33 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id A04453A6A2C for <rrg@irtf.org>; Sun, 26 Jul 2009 06:56:33 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 3059C6BE569; Sun, 26 Jul 2009 09:56:34 -0400 (EDT)
To: rrg@irtf.org
Message-Id: <20090726135634.3059C6BE569@mercury.lcs.mit.edu>
Date: Sun, 26 Jul 2009 09:56:34 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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, 26 Jul 2009 13:56:34 -0000

    > From: Tony Li <tony.li@tony.li>

    > for the most part we seem to be using locators to name the edges of the
    > graph, not the nodes.

All depends on how you model the network! Are the graph-nodes interfaces, and
the networks the arcs (this requires multi-drop arcs, of course), or are the
networks the nodes, and interfaces the arcs?

The latter is what it-whose-name-I-don't-like-to-utter originally did, but
that meant we had to have attributes on the arcs, which after some thought I
decided was excess hair. That's because it turned out that when you started
thinking about what data you needed, arcs started to look a lot like nodes,
at least in terms of the data structures. So that led to the next step - make
everything (networks, interfaces, etc) a graph-node; you wound up with a
graph with attribute-less arcs, which only indicated connectivity. (I.e. the
data structure for node X says "I am connected to nodes A, B and C", etc -
there are no actual arc data-structures.)

I argued with the BBN guys (and gal - hi Martha!) and proposed that we have
only attribute-less arcs, and while at first everyone thought I was kind of
crazy (what an unusual happening in my life :-), after some discussion
everyone took my point that although it was a little odd, it made the
implementation, etc simpler.

So we wound up with graphs with a number of different kinds of nodes: network
nodes, interface nodes, router nodes, and abstraction nodes. (We may have had
host nodes too, I don't recall any more.)


    > If we only have locators, it makes it very challenging to describe
    > topology.

No, not at all. A description of the connectivity has to say 'this {thing} is
connected to that {thing}', and locators are the names for the {thing}s (and
maybe for the connection between them, too). Locators are not the
connectivity model, they are just names for elements in the connectivity
model, which you use to pass the connectivity model (or parts of it) to
another entity.

In the model above, locators are simply the names of graph nodes; more
properly, they are attributes of a graph node, and a given graph node can
have more than one (e.g. if two naming abstractions overlap on the graph).


    > How do you deal with the case where there are two nodes that are both
    > connected to two edges?

It all depends on how your model maps to a real network. In the model above,
your question is non-sensical, because there cannot be two arcs between a
pair of nodes. (A pair of nodes are either connected, or they aren't. That's
alll, fffolks.)

So I'm assuming you're using a model where a node is a network, and an
interface is an arc, or something like that? There, you will be able to have
more than one arc between a pair of nodes - and you will therefore need to be
able to name both nodes _and_ arcs - because otherwise you won't be able to
distinguish between the two arcs.

"Elementary,  my dear Dr. Watson!" :-)

	Noel

From jnc@mercury.lcs.mit.edu  Sun Jul 26 07:08:08 2009
Return-Path: <jnc@mercury.lcs.mit.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 079BA3A6A90 for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 07:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 3hBLGK7LtX2y for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 07:08:07 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 4FA583A683B for <rrg@irtf.org>; Sun, 26 Jul 2009 07:08:07 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7C05B6BE569; Sun, 26 Jul 2009 10:08:07 -0400 (EDT)
To: rrg@irtf.org
Message-Id: <20090726140807.7C05B6BE569@mercury.lcs.mit.edu>
Date: Sun, 26 Jul 2009 10:08:07 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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, 26 Jul 2009 14:08:08 -0000

    > From: HeinerHummel@aol.com

    > By knowing the topology you can see all paths in forward direction wrt
    > a given destination as well as which network part would use you for
    > transit (the rear mirror). You have much less by assembling hundred
    > thousands of routes instead.

True - but can we expect routers to have a _complete_ map of the network, or
not? Even leaving aside technical issues such as the amount of information,
some sites may wish to 'hide' information about the internals of their
network.

So then you have to work out how to make the routing work when entities do
not have complete maps...

	Noel

From wesley.m.eddy@nasa.gov  Fri Jul 24 14:25:55 2009
Return-Path: <wesley.m.eddy@nasa.gov>
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 9FD3A3A69C1 for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 14:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.22
X-Spam-Level: 
X-Spam-Status: No, score=-6.22 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, URI_HEX=0.368]
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 tFAMjHEGqCYK for <rrg@core3.amsl.com>; Fri, 24 Jul 2009 14:25:54 -0700 (PDT)
Received: from ndmsnpf03.ndc.nasa.gov (ndmsnpf03.ndc.nasa.gov [198.117.0.123]) by core3.amsl.com (Postfix) with ESMTP id 6A05A3A69E4 for <rrg@irtf.org>; Fri, 24 Jul 2009 14:25:54 -0700 (PDT)
Received: from ndjsppt03.ndc.nasa.gov (ndjsppt03.ndc.nasa.gov [198.117.1.102]) by ndmsnpf03.ndc.nasa.gov (Postfix) with ESMTP id 539FC2D807C; Fri, 24 Jul 2009 16:25:54 -0500 (CDT)
Received: from ndjshub05.ndc.nasa.gov (ndjshub05.ndc.nasa.gov [198.117.4.164]) by ndjsppt03.ndc.nasa.gov (8.14.3/8.14.3) with ESMTP id n6OLPg1v019110; Fri, 24 Jul 2009 16:25:54 -0500
Received: from NDJSSCC01.ndc.nasa.gov ([198.117.4.166]) by ndjshub05.ndc.nasa.gov ([198.117.4.164]) with mapi; Fri, 24 Jul 2009 16:25:43 -0500
From: "Eddy, Wesley M. (GRC-MS00)[Verizon]" <wesley.m.eddy@nasa.gov>
To: William Herrin <bill@herrin.us>, "surfer@mauigateway.com" <surfer@mauigateway.com>
Date: Fri, 24 Jul 2009 16:25:42 -0500
Thread-Topic: [rrg] A Challenge for Researchers by John Day
Thread-Index: AcoMoytWnoVJ+KrRQZmR6EHGW1T5LAAADpQQ
Message-ID: <C304DB494AC0C04C87C6A6E2FF5603DB2283082F12@NDJSSCC01.ndc.nasa.gov>
References: <20090724130816.ADB80B65@resin18.mta.everyone.net> <3c3e3fca0907241409g577888b9v64bce7ccba5c9292@mail.gmail.com>
In-Reply-To: <3c3e3fca0907241409g577888b9v64bce7ccba5c9292@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.7400:2.4.4, 1.2.40, 4.0.166 definitions=2009-07-24_08:2009-07-24, 2009-07-24, 2009-07-24 signatures=0
X-Mailman-Approved-At: Sun, 26 Jul 2009 08:21:54 -0700
Cc: "rrg@irtf.org" <rrg@irtf.org>
Subject: Re: [rrg] A Challenge for Researchers by John Day
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, 24 Jul 2009 21:25:55 -0000

>-----Original Message-----
>From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On Behalf Of
>William Herrin
>Sent: Friday, July 24, 2009 5:09 PM
>
>On Fri, Jul 24, 2009 at 4:08 PM, Scott Weeks<surfer@mauigateway.com>
>wrote:
>> I hope this is acceptable to post here...
>>
>> I just finished the book "Patterns in Network Architecture: A Return
>to Fundamentals" by John Day and was going through the 'Documents and
>Publications' section of pouzinsociety.org where I found this: =A0"A
>Challenge for Researchers" -
>http://02d7097.netsolhost.com/images/A_Challenge_for_Researchers.pdf
>>
>> Knowing there is a researcher or two on this list ;-) I wanted to
>forward it onto the group. =A0To me (an operator interested in the
>architecture of the internet and its future, not a researcher) it's a
>very interesting idea!
>
>
>Hi Scott,
>
>This came around back in April and I asked:
>
>http://www.irtf.org/mail-archive/web/rrg/current/msg04922.html
>
>If anyone offers an answer, I'll take another look. Until then, John
>has a vaguely interesting idea but we have no shortage of vaguely
>interesting ideas here and it's not our role to show whether or why an
>incomplete concept can't be completed.
>


I read the book several months ago, and immediately convinced
several colleagues to as well.  Most have found it very
enlightening as it explains fundamentally what networking is,
and only holds IP or CLNP up as examples compared to that.

Day's PNA is more than "vaguely interesting" as it (correctly)
factors networking functions into the common primitives that
recurse throughout all of the existing stacks in use, and
differences between layers as policy rather than protocol.  It
further develops naming & resolution of processes within a
Distributed IPC Facility (DIF) / layer, and describes just what
you asked for in intimate detail.

If you read the book, your question is clearly answered both in
text and in the diagrams that show nesting and layering of DIFs,
however, I doubt anyone is going to take the time to transcribe
the book into email for your benefit ...

---------------------------
Wes Eddy
Network & Systems Architect
Verizon FNS / NASA GRC
Office: (216) 433-6682
---------------------------

From HeinerHummel@aol.com  Sun Jul 26 10:22:33 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 5B3493A6A98 for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 10:22:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 XNDObDKD1ywi for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 10:22:32 -0700 (PDT)
Received: from imr-da01.mx.aol.com (imr-da01.mx.aol.com [205.188.105.143]) by core3.amsl.com (Postfix) with ESMTP id 5BCB93A67A4 for <rrg@irtf.org>; Sun, 26 Jul 2009 10:22:32 -0700 (PDT)
Received: from imo-ma01.mx.aol.com (imo-ma01.mx.aol.com [64.12.78.136]) by imr-da01.mx.aol.com (8.14.1/8.14.1) with ESMTP id n6QHMKsp007286; Sun, 26 Jul 2009 13:22:20 -0400
Received: from HeinerHummel@aol.com by imo-ma01.mx.aol.com  (mail_out_v40_r1.5.) id 9.c95.47dbb7e0 (30737);  Sun, 26 Jul 2009 13:22:16 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <c95.47dbb7e0.379deac8@aol.com>
Date: Sun, 26 Jul 2009 13:22:16 EDT
To: jnc@mercury.lcs.mit.edu, rrg@irtf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1248628936"
X-Mailer: 9.0 SE for Windows sub 5021
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, 26 Jul 2009 17:22:33 -0000

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

In einer eMail vom 26.07.2009 16:08:29 Westeurop=E4ische Normalzeit schrei=
bt  
jnc@mercury.lcs.mit.edu:

> From: HeinerHummel@aol.com

> By knowing the  topology you can see all paths in forward direction wrt
>  a given destination as well as which network part would use you for
> transit (the rear mirror). You have much less by assembling  hundred
> thousands of routes instead.

True - but  can we expect routers to have a _complete_ map of the network,=
 
or
not?  
Of course not (this is not even required in a multi-area ospf  
network).Instead Hierarchy is the clue for coping with scalability. But =
 there have been 
many many (failing) attempts so far : Nimrod,  PNNI,  ISLAY, Brian's, 
Rangi, CLNP, HAIR, LISP (2-staged), and now  (N)-DIF. Also E.164.Non of th=
ese 
caters for a "sliding" hierarchy such that  every node is (well, almost)=
 in the 
middle of its nearest surrounding topology  at lowest level, followed by=
 
more and more sparsed topologies at higher levels,  the more they are remo=
te. 
Instead they all are static, loaded with political  and/or ISP-sensitive=
 
dependencies.
 

Even  leaving aside technical issues such as the amount of information,
some  sites may wish to 'hide' information about the internals of  their
network.

Sure, and also while some other internals might be solicited to the  
outside. But these are well-known challenges. There are more in addition:=
 How to  
enable such a sliding hierarchy. How to implement a hierarchy where strict=
 
links  do not only show up inside the immediate neighborhood but 
interconnect,  eventually, routers which are 20 000 km away from each othe=
r.
 
 
>So then you have to work out how to make the routing work when  entities=
 do
>not have complete maps...
 
... yes, and where there are also entities around which aren't aware of =
 
such a new technology at all.



Noel


Heiner

-------------------------------1248628936
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 content=3D"text/html; charset=3DISO-8859-1" http-equiv=3DContent-Typ=
e>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18783"></HEAD>
<BODY style=3D"FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=3Dr=
ole_body 
bottomMargin=3D7 leftMargin=3D7 rightMargin=3D7 topMargin=3D7><FONT id=3Dr=
ole_document 
color=3D#000000 size=3D2 face=3DArial>
<DIV>In einer eMail vom 26.07.2009 16:08:29 Westeurop=E4ische Normalzeit=
 schreibt 
jnc@mercury.lcs.mit.edu:</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=3D=
Arial>&nbsp; 
  &gt; From: HeinerHummel@aol.com<BR><BR>&nbsp; &nbsp; &gt; By knowing the=
 
  topology you can see all paths in forward direction wrt<BR>&nbsp; &nbsp;=
 &gt; 
  a given destination as well as which network part would use you for<BR>&=
nbsp; 
  &nbsp; &gt; transit (the rear mirror). You have much less by assembling=
 
  hundred<BR>&nbsp; &nbsp; &gt; thousands of routes instead.<BR><BR>True=
 - but 
  can we expect routers to have a _complete_ map of the network, or<BR>not=
? 
  </FONT></BLOCKQUOTE>
<DIV>Of course not (this is not even required in a multi-area ospf 
network).Instead Hierarchy is the clue&nbsp;for coping with scalability.=
 But 
there have been many many (failing) attempts so far : Nimrod, 
PNNI,&nbsp;&nbsp;ISLAY, Brian's, Rangi, CLNP, HAIR, LISP (2-staged), and=
 now 
(N)-DIF. Also E.164.Non of these caters for a "sliding" hierarchy such tha=
t 
every node is (well, almost) in the middle of its nearest surrounding topo=
logy 
at lowest level, followed by more and more sparsed topologies at higher le=
vels, 
the more they are remote. Instead they all are static, loaded with politic=
al 
and/or ISP-sensitive dependencies.</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=3D=
Arial>Even 
  leaving aside technical issues such as the amount of information,<BR>som=
e 
  sites may wish to 'hide' information about the internals of 
  their<BR>network.<BR></FONT></BLOCKQUOTE>
<DIV>Sure, and also while some other internals might be solicited to the=
 
outside. But these are well-known challenges. There are more in addition:=
 How to 
enable such a sliding hierarchy. How to implement a hierarchy where strict=
 links 
do not only show up inside the immediate neighborhood but interconnect, 
eventually, routers which are 20 000 km away from each other.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D=
2 
face=3DArial>&gt;So then you have to work out how to make the routing work=
 when 
entities do<BR>&gt;not have complete maps...</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>... yes, and where there are also entities around which aren't aware=
 of 
such a new technology at all.</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 
  face=3DArial><BR><BR>&nbsp; &nbsp; Noel<BR></FONT></BLOCKQUOTE>
<DIV></DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>

-------------------------------1248628936--

From irtf@tonistoev.info  Sun Jul 26 13:26:30 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 BED163A6BB2 for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 13:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.092
X-Spam-Level: 
X-Spam-Status: No, score=-0.092 tagged_above=-999 required=5 tests=[AWL=0.093,  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 M0GsibzbUZiI for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 13:26:30 -0700 (PDT)
Received: from chi.r1servers.com (chi.r1servers.com [82.119.92.20]) by core3.amsl.com (Postfix) with ESMTP id 052653A6BAD for <rrg@irtf.org>; Sun, 26 Jul 2009 13:26:30 -0700 (PDT)
Received: from 85-91-132-61.spectrumnet.bg ([85.91.132.61] helo=laptop-work) by chi.r1servers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <irtf@tonistoev.info>) id 1MVAIe-0006jU-4I for rrg@irtf.org; Sun, 26 Jul 2009 23:26:28 +0300
From: Toni Stoev <irtf@tonistoev.info>
To: IRTF RRG <rrg@irtf.org>
Date: Sun, 26 Jul 2009 23:26:26 +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: <200907262326.26319.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] Grad
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, 26 Jul 2009 20:26:30 -0000

A graph where edges may be shared.

From christian.vogt@ericsson.com  Sun Jul 26 19:26:02 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 AE68F3A69E8 for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 19:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 OeQXrRtx99Q6 for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 19:26:02 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id DD8633A63D3 for <rrg@irtf.org>; Sun, 26 Jul 2009 19:26:01 -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 n6R2PxLC004310; Sun, 26 Jul 2009 21:25:59 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 26 Jul 2009 21:25:40 -0500
Received: from [10.16.1.9] ([164.48.124.45]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 26 Jul 2009 21:25:38 -0500
Message-Id: <F8FBC7A5-DD35-4710-A8E4-58E1A1FEA3B7@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Tony Li <tony.li@tony.li>
In-Reply-To: <4A6B3193.9060704@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: Mon, 27 Jul 2009 04:25:34 +0200
References: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net> <8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com> <4A6B3193.9060704@tony.li>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 27 Jul 2009 02:25:39.0546 (UTC) FILETIME=[885663A0:01CA0E61]
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: Mon, 27 Jul 2009 02:26:02 -0000

On Jul 25, 2009, Tony Li wrote:

>> 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?
>

> Well, to me, central to the notion of the Internet architecture and  
> more
> specifically to a routing architecture is the notion of topology.  It
> would seem somewhat challenging to be able to describe topology  
> without
> being able to describe a graph.  And if we want to be able to  
> describe a
> graph, we need to be able to articulate the nodes and edges in that
> graph.  I don't see how to do this with just service identifiers.


Tony -

This is about identification, not about routing.

For routing, I agree that it would be useful to have locators which
route to a given host -- or better: to a given stack, since this is the
entity through which one must pass to reach a given service or session.

- Christian



From tony.li@tony.li  Sun Jul 26 20:16:43 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 545613A6B11 for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 20:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 37aevIDLQTOp for <rrg@core3.amsl.com>; Sun, 26 Jul 2009 20:16:42 -0700 (PDT)
Received: from QMTA10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by core3.amsl.com (Postfix) with ESMTP id 9CE083A6B0B for <rrg@irtf.org>; Sun, 26 Jul 2009 20:16:42 -0700 (PDT)
Received: from OMTA17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by QMTA10.emeryville.ca.mail.comcast.net with comcast id LrCJ1c0011afHeLAArGk5f; Mon, 27 Jul 2009 03:16:44 +0000
Received: from [10.43.1.57] ([77.241.97.116]) by OMTA17.emeryville.ca.mail.comcast.net with comcast id LrGV1c0082WfiAM8drGYpZ; Mon, 27 Jul 2009 03:16:42 +0000
Message-ID: <4A6D1BE7.5040702@tony.li>
Date: Mon, 27 Jul 2009 05:15:51 +0200
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Christian Vogt <christian.vogt@ericsson.com>
References: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net> <8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com> <4A6B3193.9060704@tony.li> <F8FBC7A5-DD35-4710-A8E4-58E1A1FEA3B7@ericsson.com>
In-Reply-To: <F8FBC7A5-DD35-4710-A8E4-58E1A1FEA3B7@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Mon, 27 Jul 2009 03:16:43 -0000

Christian,

> This is about identification, not about routing.

This is RRG.  It's all about routing.  Identification is a necessary 
side-effect.

> For routing, I agree that it would be useful to have locators which
> route to a given host -- or better: to a given stack, since this is the
> entity through which one must pass to reach a given service or session.

Excellent, glad you're on board.

Tony


From jnc@mercury.lcs.mit.edu  Mon Jul 27 06:20:48 2009
Return-Path: <jnc@mercury.lcs.mit.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 E84E828C203 for <rrg@core3.amsl.com>; Mon, 27 Jul 2009 06:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 MS3crt1umrFB for <rrg@core3.amsl.com>; Mon, 27 Jul 2009 06:20:48 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 2F64928C19C for <rrg@irtf.org>; Mon, 27 Jul 2009 06:20:48 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id B86A86BE58E; Mon, 27 Jul 2009 09:20:48 -0400 (EDT)
To: rrg@irtf.org
Message-Id: <20090727132048.B86A86BE58E@mercury.lcs.mit.edu>
Date: Mon, 27 Jul 2009 09:20:48 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
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, 27 Jul 2009 13:20:49 -0000

    > From: Christian Vogt <christian.vogt@ericsson.com>

    > I agree that it would be useful to have locators which route to a given
    > host -- or better: to a given stack, since this is the entity through
    > which one must pass to reach a given service or session.

I've always had this degree of ambivalent feelings about this concept, that
locators can identify 'things' inside a host.

I've always felt like 'the job of the routing is to deliver the packets to
the right network interface, and once that's done, its job is over'. From
then on, it should be the next layer up's job to do demultiplexing - perhaps
with what I have called a Endpoint Selectors (ESEL - a short identifier, with
scope limited to a single interface, which can get a packet to whichever of
several endpoints is sharing a particular interface).

I guess the best counter-argument I've heard is that if you have a 'virtual
machine' setup, each virtual machine thinks it has a virtual network
interface, and that virtual interface needs its interface name. (You can just
do it with ESELs, since each VM would think it's managing the ESEL namespace,
and you could get clashes.) So that would mean that inside the VM system,
packets would have to be 'routed' to the correct VM.

Do note that if we want to support that model (locators for VIs on VMs), that
probably does imply variable length locators... (ducks :-)

	Noel

PS: Nobody has any reaction to my comments about models for connectivity?

From eric.fleischman@boeing.com  Mon Jul 27 08:42:14 2009
Return-Path: <eric.fleischman@boeing.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 EF66D28C289 for <rrg@core3.amsl.com>; Mon, 27 Jul 2009 08:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 RceD+GiSnVz6 for <rrg@core3.amsl.com>; Mon, 27 Jul 2009 08:42:13 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id A24A128C26A for <rrg@irtf.org>; Mon, 27 Jul 2009 08:42:13 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n6RFgBP1027353 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jul 2009 10:42:12 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n6RFgBIU001602; Mon, 27 Jul 2009 08:42:11 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n6RFgAcj001534; Mon, 27 Jul 2009 08:42:11 -0700 (PDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 08:42:10 -0700
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: Mon, 27 Jul 2009 08:42:07 -0700
Message-ID: <474EEBD229DF754FB83D256004D021080C38F4BF@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <20090726135634.3059C6BE569@mercury.lcs.mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Next topic: properties of identifiers
Thread-Index: AcoN+OYMAc1JS2V4SlmRNNNtrdbHLgA1f/Ag
References: <20090726135634.3059C6BE569@mercury.lcs.mit.edu>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>, <rrg@irtf.org>
X-OriginalArrivalTime: 27 Jul 2009 15:42:10.0777 (UTC) FILETIME=[CE218490:01CA0ED0]
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, 27 Jul 2009 15:42:15 -0000

It would be nice if topologies could be mapped to graphs -- and it may
well be possible, even though I personally don't know how to do it.
(Alternatively, I suggested to our mathematicians many years ago that I
suspected that Matrices may be a more appropriate representation for
MANET networks than graphs, but they were not interested enough in this
suggestion to see whether it had any merit or not.)

However, I'd like to point out that for any large network the topology
(or graph) is not fully known from any arbitrary point within the
structure. For large networks, we need abstraction to enable scaling.
Also, those of us who work with MANET technologies are quick to point
out that topology is also a function of time in that topology (and
therefore its graph, if we could draw it) is also a partial function of
the 4 dimensional geographic system (x, y, z, time) in which it exists.=20

I suspect that this is why arcs proved useful in the discussions which
Noel alluded to below -- arcs provide a mechanism to represent
abstraction.

-----Original Message-----
From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]=20
    > From: Tony Li <tony.li@tony.li>

    > for the most part we seem to be using locators to name the edges
of the
    > graph, not the nodes.

All depends on how you model the network! Are the graph-nodes
interfaces, and the networks the arcs (this requires multi-drop arcs, of
course), or are the networks the nodes, and interfaces the arcs?

The latter is what it-whose-name-I-don't-like-to-utter originally did,
but that meant we had to have attributes on the arcs, which after some
thought I decided was excess hair. That's because it turned out that
when you started thinking about what data you needed, arcs started to
look a lot like nodes, at least in terms of the data structures. So that
led to the next step - make everything (networks, interfaces, etc) a
graph-node; you wound up with a graph with attribute-less arcs, which
only indicated connectivity. (I.e. the data structure for node X says "I
am connected to nodes A, B and C", etc - there are no actual arc
data-structures.)

<snip>

From fu@cs.uni-goettingen.de  Mon Jul 27 15:27:49 2009
Return-Path: <fu@cs.uni-goettingen.de>
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 DB66B3A6C3B; Mon, 27 Jul 2009 15:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level: 
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, GB_I_LETTER=-2, HELO_EQ_DE=0.35]
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 z21zHmwgx1UP; Mon, 27 Jul 2009 15:27:49 -0700 (PDT)
Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by core3.amsl.com (Postfix) with ESMTP id B78193A6841; Mon, 27 Jul 2009 15:27:48 -0700 (PDT)
Received: from [77.241.97.115] (helo=[10.43.1.21]) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <fu@cs.uni-goettingen.de>) id 1MVYfa-0007pT-EE; Tue, 28 Jul 2009 00:27:46 +0200
Message-ID: <4A6E29E0.7090203@cs.uni-goettingen.de>
Date: Tue, 28 Jul 2009 00:27:44 +0200
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
Organization: University of Goettingen, Germany
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: rrg@irtf.org, iccrg@cs.ucl.ac.uk, hipsec-rg@listserv.cybertrust.com,  dtn-interest@mailman.dtnrg.org, "sam@irtf.org >> sam" <sam@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated: Id:xfu
X-Virus-Scanned: (clean) by exiscan+sophie
Subject: [rrg] ICNP 2009 Call for Posters
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, 27 Jul 2009 22:27:49 -0000

Our apologies for cross-posting...
----
Dear colleagues,

Please kindly consider a poster contribution to ICNP'09 and/or forward
the following call for posters to interested people/students.

Thank you!
Xiaoming Fu (ICNP'09 Publicity Chair)


ICNP'09 Call for Posters:
========================
ICNP 2009 will hold a poster session to showcase "work-in-progress".
This has been a successful regular event at ICNP in past years and has
attracted many bright ideas that have developed into mature conference
and journal papers over time. The poster session will provide a great
chance for students to obtain feedback on their ongoing research from
knowledgeable conference attendees. In the past, these sessions have
been very well attended. While posters are welcome from everyone, we
particularly encourage on-going work in which the primary contributor
(i.e., first author) is a student. Extended (2-page) abstracts of the
posters will be reviewed by members of the Poster Session Committee. At
the conference, posters must be presented by one of the co-authors.

Posters submitted to this call for papers should contain unpublished
original ideas and not be abbreviations of published papers. The poster
extended abstract (2 pages) will be published in the conference
proceedings and CD, and put on the ICNP website.

Note that acceptance and presentation of a poster at ICNP 2009 will not
prevent authors from publishing a more complete version of their ideas
in future conferences and journals.

Important dates:
---------------
Submission deadline:          August 7, 2009, (Fri 23:59 PDT)
Notification of decisions:    August 28, 2009
Final version of abstracts:   September 4, 2009

Where to submit?
----------------
By email to: icnp09posters@nile.cise.ufl.edu
Use Subject Line: ICNP 2009 poster submission Registration

At least one person must be registered for the conference to present the
poster. Students may register for the conference at the student rate for
presenting posters (if they are not presenting a full paper in the
conference which requires a full registration).
What the final poster should look like?

We define a poster to be 12 pages 8.5in x11in (letter size) on which you
can affix visually appealing material that describes your research.
Alternatively you can use the space as a continuum. You can arrange the
space and orient the poster either horizontally or vertically. You
should prepare the best material (visually appealing and succinct) that
effectively communicates your research problem, techniques, results, and
what is novel and important about your work. You are responsible for
printing your poster and bringing it to the conference site. We will
provide stands for you to mount your poster materials on.

Posters Review Committee
------------------------
Ahmed Helmy        University of Florida (Chair)
Sonia Fahmy        Purdue University
Romit Choudhury    Duke University

For questions: Email icnp09posters@nile.cise.ufl.edu


From fu@cs.uni-goettingen.de  Mon Jul 27 15:40:06 2009
Return-Path: <fu@cs.uni-goettingen.de>
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 2814C3A6AF9 for <rrg@core3.amsl.com>; Mon, 27 Jul 2009 15:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level: 
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 0StC1BhoEEE6 for <rrg@core3.amsl.com>; Mon, 27 Jul 2009 15:40:05 -0700 (PDT)
Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by core3.amsl.com (Postfix) with ESMTP id 3789F3A69F2 for <rrg@irtf.org>; Mon, 27 Jul 2009 15:40:01 -0700 (PDT)
Received: from [77.241.97.115] (helo=[10.43.1.21]) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <fu@cs.uni-goettingen.de>) id 1MVYrP-00044R-UO; Tue, 28 Jul 2009 00:40:00 +0200
Message-ID: <4A6E2CBD.9070304@cs.uni-goettingen.de>
Date: Tue, 28 Jul 2009 00:39:57 +0200
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
Organization: University of Goettingen, Germany
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: rrg@irtf.org, iccrg@cs.ucl.ac.uk, hipsec-rg@listserv.cybertrust.com,  dtn-interest@mailman.dtnrg.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated: Id:xfu
X-Virus-Scanned: (clean) by exiscan+sophie
Subject: [rrg] ICNP 2009 Call for Demos
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, 27 Jul 2009 22:40:06 -0000

Our apologies for cross-posting...
----
Dear colleagues,

Please kindly forward to your colleagues and students for consideration
of a demo contribution to ICNP'09 - Please note there will be a best
demo prize (at the courtesy of Microsoft)!

The deadline for submitting a demo abstract (as well as posters) to
ICNP'09 is August 7, 2009 (Fri 23:59 PDT).

Thanks and best regards,
Xiaoming Fu (ICNP 2009 Publicity Chair)

ICNP'09 Call for Demos:
======================
IEEE ICNP 2009 will include a demo session. Proposals for research
demonstrations and exhibits are strongly solicited. Research
demonstrations should be innovative research prototypes that show new
research related to the topics included in the ICNP call for papers. The
best demo will receive a cash prize of USD 500, courtesy of Microsoft
Research.

Submission Instructions:
-----------------------
Submit demo proposal at: http://edas.info/N7882.

The proposals should include a two-page (10 pt) abstract describing the
goals of the demo and the basic idea it supports. Submissions are single
blind, so please include authors' names and affiliation.

In addition, include a list of equipment the demo will use, as well as
space and power requirements. Note that the organizers can provide only
space and power. We may be able to provide Internet access for the demos
as well, but this is not guaranteed. Let us also know if you will need a
large amount of setup time.

All demo proposals will be reviewed by the ICNP 2009 Poster and Demo
committee. Selected demo abstracts will be published in the ICNP
proceedings.

Important Dates:
---------------
Submission deadline (on EDAS)     August 7, 2009, (Fri 23:59 PDT)
Notification of acceptance        August 28, 2009
Camera ready deadline             September 4, 2009

Organizing Committee:
--------------------
Jitendra Padhye (Chair)  Microsoft Research, USA
Srikanth Krishnamurthy   UC Riverside, USA
Henning Schulzrinne      Columbia University, USA
K. K. Ramakrishnan       AT&T labs, USA



From christian.vogt@ericsson.com  Mon Jul 27 16:38:22 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 311A43A6B9D for <rrg@core3.amsl.com>; Mon, 27 Jul 2009 16:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.243
X-Spam-Level: 
X-Spam-Status: No, score=-3.243 tagged_above=-999 required=5 tests=[AWL=0.356,  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 1QSH25fHOW6l for <rrg@core3.amsl.com>; Mon, 27 Jul 2009 16:38:21 -0700 (PDT)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by core3.amsl.com (Postfix) with ESMTP id 75DDC3A6B69 for <rrg@irtf.org>; Mon, 27 Jul 2009 16:38:21 -0700 (PDT)
Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 5C6873BD956; Mon, 27 Jul 2009 19:38:22 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 27 Jul 2009 19:38:22 -0400
X-Sasl-enc: IwKtvIZAZxvExCUqX8ewCsQCkQjxDoR5WOQy+Xu+a1a3 1248737895
Received: from host-78-64-88-72.homerun.telia.com (host-78-64-88-72.homerun.telia.com [78.64.88.72]) by mail.messagingengine.com (Postfix) with ESMTPSA id 2256939856; Mon, 27 Jul 2009 19:38:15 -0400 (EDT)
Message-Id: <A6A2EA60-2304-4F5A-8A5E-A8CAA5838177@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Tony Li <tony.li@tony.li>
In-Reply-To: <4A6D1BE7.5040702@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: Tue, 28 Jul 2009 01:38:19 +0200
References: <DB3E5D6F36600847BC70D451534EBCD504EA2ECE@E03MVB2-UKBR.domain1.systemhost.net> <8C04EC27-D09B-45FE-A6A0-85E27FD9558D@ericsson.com> <4A6B3193.9060704@tony.li> <F8FBC7A5-DD35-4710-A8E4-58E1A1FEA3B7@ericsson.com> <4A6D1BE7.5040702@tony.li>
X-Mailer: Apple Mail (2.935.3)
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: Mon, 27 Jul 2009 23:38:22 -0000

On Jul 27, 2009, Tony Li wrote:

> This is RRG.  It's all about routing.  Identification is a necessary
> side-effect.

... although it was you who started this thread. ;-)

Also, as I earlier mentioned to Lixia, I do believe this discussion is
useful also for RRG.  Keep in mind that there is a group of people in
RRG who believe that identifier-locator separation can accomplish our
mission.  Devising a suitable identifier-locator separation solution, in
turn, requires some discussion of the type we were having.

>> For routing, I agree that it would be useful to have locators which
>> route to a given host -- or better: to a given stack, since this is  
>> the
>> entity through which one must pass to reach a given service or  
>> session.
>
> Excellent, glad you're on board.

Yep, cool.

- Christian



From lars.eggert@nokia.com  Tue Jul 28 00:31:49 2009
Return-Path: <lars.eggert@nokia.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 65F293A687A for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  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 TkN0EBxdS+68 for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:31:48 -0700 (PDT)
Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by core3.amsl.com (Postfix) with ESMTP id 791E73A6CEF for <rrg@irtf.org>; Tue, 28 Jul 2009 00:31:48 -0700 (PDT)
Received: from dhcp-52bd.meeting.ietf.org (dhcp-52bd.meeting.ietf.org [130.129.82.189] (may be forged)) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id n6S7VfAv070745 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <rrg@irtf.org>; Tue, 28 Jul 2009 10:31:41 +0300 (EEST) (envelope-from lars.eggert@nokia.com)
Message-Id: <210810E2-AA86-4EAD-B6D7-88504E755982@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: rrg@irtf.org
Content-Type: multipart/signed; boundary=Apple-Mail-121--123838047; micalg=sha1; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 28 Jul 2009 09:31:41 +0200
X-Mailer: Apple Mail (2.935.3)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (mail.fit.nokia.com [212.213.221.39]); Tue, 28 Jul 2009 10:31:42 +0300 (EEST)
Subject: [rrg] no agenda = no meeting?
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, 28 Jul 2009 07:31:49 -0000

--Apple-Mail-121--123838047
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Hi,

given that there still isn't an agenda for Friday, I assume the  
meeting will be cancelled?

Lars
--Apple-Mail-121--123838047
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEEi7WbMMKa2GLKFpQDaOBQEwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA4MDgyMzE3NDMzOVoXDTA5MDgyMzE3NDMz
OVowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAlwQVktJZCY89iU6jcW1XnZQN+aMgF2utCUT3H3ZKB5Jbet1SDWt0md/W
571bHjxtn9CfEJdochNL3l9f1WiJNdVbJ182557Ltx9SojqthpqtA0jKEqo2gqrf+raUj1demmo0
6ocsLqv046CrwidOp6k0RAfvkKPLhD4PD9Nk3oaZuxqBz1wY4u8Q83iWMArDeXiQxfNZnOBz5cDs
VvVjTjitm3VANkbD02tNkwl5AHw7htde4yH8hIwlfzqsAtHBEah3HyOvs9b+gHg2pFz9eS+HuotY
ZKycCweRs8NKXoCg+zAkVYi3zvZEH2VOuPlpMQMrB9+fLWg2UBsTeZ864wIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQBMdV2U+ryV5t3nuBFH19XKflodN6Bc60GBYHHY/Z0+Cl08Q75qzTt02IILBg+/YVh/fygb
6pFrOm1sFtLN7fENBfbO2VtpFjP2lGUgbXTVT5xGM6+MtqZiBI6LqexAeY6gsd/taoUfy9fZG42d
ciBA9gSGlQjjWQyG8mb5HR8L9jCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
SLtZswwprYYsoWlANo4FATAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wOTA3MjgwNzMxNDFaMCMGCSqGSIb3DQEJBDEWBBQYht+PsmWQUqhB
gZRldtkcX4J/DDCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEEi7WbMMKa2GLKFpQDaOBQEwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEEi7WbMMKa2GLKFpQDaOBQEw
DQYJKoZIhvcNAQEBBQAEggEAARrR26EFJZ1Vx7Y01iCeTNzy7l0Y5P7hayFwx6t10Aj994Qp6bqz
6Ty+emgHq5O4jtFC8Mk8vLYDfnq+apFLghVxFaX+8GyIV8W6kRlEAqzjnlViw6FqvEEQjmdyW6Qy
Oz3dqr40PEXlY0YjBmBrZdTm8ZE8Wilzhv3usQO/Vp6t0CKbXS6e9B53y3zDcFWZ26G2KJe7YWYa
r9ab44rw/ziMBAtoAJeRkOKz7pNQ76OnHQpNBfZN5QfGM5WQm2EErtVq91j6Qe8DJZERZsCYPBLu
IE+LbCjh1J6K4TEnlTtQ4Xy6qNwlCJigtuGe0PuM78qLB64Ai10Vq/k96YIi/wAAAAAAAA==

--Apple-Mail-121--123838047--

From lixia@cs.ucla.edu  Tue Jul 28 00:41:56 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 16AEF3A696E for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:41:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Jf91Jof6G5N9 for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:41:55 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 3D8FE3A691A for <rrg@irtf.org>; Tue, 28 Jul 2009 00:41:55 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 7E05939E80B1; Tue, 28 Jul 2009 00:41:53 -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 EsKYzSmdRjdx; Tue, 28 Jul 2009 00:41:49 -0700 (PDT)
Received: from dhcp-11db.meeting.ietf.org (dhcp-11db.meeting.ietf.org [130.129.17.219]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 03A6539E8082; Tue, 28 Jul 2009 00:41:48 -0700 (PDT)
Message-Id: <73455000-6ED1-4B0E-905E-5326705551E3@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <210810E2-AA86-4EAD-B6D7-88504E755982@nokia.com>
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, 28 Jul 2009 00:41:46 -0700
References: <210810E2-AA86-4EAD-B6D7-88504E755982@nokia.com>
X-Mailer: Apple Mail (2.935.3)
Cc: rrg@irtf.org
Subject: Re: [rrg] no agenda = no meeting?
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, 28 Jul 2009 07:41:56 -0000

On Jul 28, 2009, at 12:31 AM, Lars Eggert wrote:

> Hi,
>
> given that there still isn't an agenda for Friday, I assume the  
> meeting will be cancelled?

maybe you did not look at the right place? :-)

http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGagendaStockholm

or maybe it is the chairs fault for not having updated right place

Tony and Lixia


From lars.eggert@nokia.com  Tue Jul 28 00:44:41 2009
Return-Path: <lars.eggert@nokia.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 871083A6ABC for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level: 
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.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 LyMG7NEQmgxK for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:44:40 -0700 (PDT)
Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by core3.amsl.com (Postfix) with ESMTP id 79D1A3A67BD for <rrg@irtf.org>; Tue, 28 Jul 2009 00:44:40 -0700 (PDT)
Received: from dhcp-52bd.meeting.ietf.org (dhcp-52bd.meeting.ietf.org [130.129.82.189] (may be forged)) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id n6S7iUkR071003 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 28 Jul 2009 10:44:30 +0300 (EEST) (envelope-from lars.eggert@nokia.com)
Message-Id: <6B77766B-73BC-4963-A1C2-7616F7741AE0@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <73455000-6ED1-4B0E-905E-5326705551E3@cs.ucla.edu>
Content-Type: multipart/signed; boundary=Apple-Mail-122--123069425; micalg=sha1; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 28 Jul 2009 09:44:30 +0200
References: <210810E2-AA86-4EAD-B6D7-88504E755982@nokia.com> <73455000-6ED1-4B0E-905E-5326705551E3@cs.ucla.edu>
X-Mailer: Apple Mail (2.935.3)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (mail.fit.nokia.com [212.213.221.39]); Tue, 28 Jul 2009 10:44:30 +0300 (EEST)
Cc: "rrg@irtf.org" <rrg@irtf.org>
Subject: Re: [rrg] no agenda = no meeting?
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, 28 Jul 2009 07:44:41 -0000

--Apple-Mail-122--123069425
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

On 2009-7-28, at 9:41, Lixia Zhang wrote:
> maybe you did not look at the right place? :-)
> http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGagendaStockholm

I looked at the agenda page, which is blank.

http://tools.ietf.org/agenda/75/rrg.html
vs., for example
http://tools.ietf.org/agenda/75/iccrg.html

Lars
--Apple-Mail-122--123069425
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEEi7WbMMKa2GLKFpQDaOBQEwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA4MDgyMzE3NDMzOVoXDTA5MDgyMzE3NDMz
OVowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAlwQVktJZCY89iU6jcW1XnZQN+aMgF2utCUT3H3ZKB5Jbet1SDWt0md/W
571bHjxtn9CfEJdochNL3l9f1WiJNdVbJ182557Ltx9SojqthpqtA0jKEqo2gqrf+raUj1demmo0
6ocsLqv046CrwidOp6k0RAfvkKPLhD4PD9Nk3oaZuxqBz1wY4u8Q83iWMArDeXiQxfNZnOBz5cDs
VvVjTjitm3VANkbD02tNkwl5AHw7htde4yH8hIwlfzqsAtHBEah3HyOvs9b+gHg2pFz9eS+HuotY
ZKycCweRs8NKXoCg+zAkVYi3zvZEH2VOuPlpMQMrB9+fLWg2UBsTeZ864wIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQBMdV2U+ryV5t3nuBFH19XKflodN6Bc60GBYHHY/Z0+Cl08Q75qzTt02IILBg+/YVh/fygb
6pFrOm1sFtLN7fENBfbO2VtpFjP2lGUgbXTVT5xGM6+MtqZiBI6LqexAeY6gsd/taoUfy9fZG42d
ciBA9gSGlQjjWQyG8mb5HR8L9jCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
SLtZswwprYYsoWlANo4FATAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wOTA3MjgwNzQ0MzBaMCMGCSqGSIb3DQEJBDEWBBTivyRCfb/ydbqT
kwOUJFAcmT/WojCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEEi7WbMMKa2GLKFpQDaOBQEwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEEi7WbMMKa2GLKFpQDaOBQEw
DQYJKoZIhvcNAQEBBQAEggEAVwBzwoiSCY6rhIcU/jolZElnVRd/E6AQVkusjIatUwrxbi1fXVqi
NdSqD+hNYVOT4GWRd1R0KR5VfcFHqzK0aJq702weIzk61IQ41wCEojwXPBOcTkPwXFscuaoMy8qa
SaPPdIsjeePodzFeyn97IXFVZFfUN6kk8PVhkWYTE7lkB+WPXUqC3MWZnI9GKQixwJkf2+CjeHsW
6Dl5pgkZBa75W/3rFSsSuNxPxsCKwxQAUe8yiQoSxF14ehh3wMPlQQMAglwJgQdjRzNuGqmJF083
NcmIR9AivMGCFk8J0ZGtIGbqTNPl5OzN+R5vVPyCksg2cavYqZltxOs4t21pXgAAAAAAAA==

--Apple-Mail-122--123069425--

From jmh@joelhalpern.com  Tue Jul 28 00:45:30 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 7C9DA3A6997 for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:45:30 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7xCb7m4EaH1l for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:45:29 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id A432F3A696E for <rrg@irtf.org>; Tue, 28 Jul 2009 00:45:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 2C968438016; Tue, 28 Jul 2009 00:45:20 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [130.129.17.160] (dhcp-11a0.meeting.ietf.org [130.129.17.160]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 2E03D437E53; Tue, 28 Jul 2009 00:45:18 -0700 (PDT)
Message-ID: <4A6EAC8E.5050302@joelhalpern.com>
Date: Tue, 28 Jul 2009 03:45:18 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20090727132048.B86A86BE58E@mercury.lcs.mit.edu>
In-Reply-To: <20090727132048.B86A86BE58E@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 28 Jul 2009 07:45:30 -0000

There are at least two ways of looking at the problem of getting the 
packet to the right stack.
And, to put the answer before the quesiton, I think the level of 
distinction is irrelevant at this stage of the game.

Let us presume that we started with an identifier for something.  And we 
are going to end up with enough information to delvier the packet.
That information has to include
enough content that the network can delvier the packet to the right 
network interface
enough content that the packet will get from the network interface to 
the right processing stack.

Now, whether those two steps are represented by two pieces of 
information (a locator plus an ESEL),
one piece of information (a locator that is usable by machine packet 
dispatch logic)
or three pieces of information (a subnet locator, an identifier usable 
for packet delivery in the subnet, and a potentially separate field 
usable for intra-machine handling)
Or a variation on three where the identifier covers the last two pieces, 
and we are back to two,
and whether these pieces of information are all part of one fixed length 
field, one variable length field, or separate explicit fields,

we still have to get the packet there.
Different solutions will parse this differently.
I think what is important for the solutions to be clear about what the 
information names / locates, and in what scope.
I do not think it is important that we mandate a very specific meaning 
for the term across those solutions.  I don't think this particular 
ambiguity introduces major confusion, as long as we make sure we know 
what the solution we are examining does, and how it enables this.

(This relates to my hypothesis that we need stack identifiers in the 
abstract, but not all solutions need to have those identifiers exchanged 
on the wire.)

Yours,
Joel

Noel Chiappa wrote:
>     > From: Christian Vogt <christian.vogt@ericsson.com>
> 
>     > I agree that it would be useful to have locators which route to a given
>     > host -- or better: to a given stack, since this is the entity through
>     > which one must pass to reach a given service or session.
> 
> I've always had this degree of ambivalent feelings about this concept, that
> locators can identify 'things' inside a host.
> 
> I've always felt like 'the job of the routing is to deliver the packets to
> the right network interface, and once that's done, its job is over'. From
> then on, it should be the next layer up's job to do demultiplexing - perhaps
> with what I have called a Endpoint Selectors (ESEL - a short identifier, with
> scope limited to a single interface, which can get a packet to whichever of
> several endpoints is sharing a particular interface).
> 
> I guess the best counter-argument I've heard is that if you have a 'virtual
> machine' setup, each virtual machine thinks it has a virtual network
> interface, and that virtual interface needs its interface name. (You can just
> do it with ESELs, since each VM would think it's managing the ESEL namespace,
> and you could get clashes.) So that would mean that inside the VM system,
> packets would have to be 'routed' to the correct VM.
> 
> Do note that if we want to support that model (locators for VIs on VMs), that
> probably does imply variable length locators... (ducks :-)
> 
> 	Noel
> 
> PS: Nobody has any reaction to my comments about models for connectivity?
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
> 

From lixia@cs.ucla.edu  Tue Jul 28 00:47:33 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 EF2983A6CE6 for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 7YC6TJkZ14J3 for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 00:47:33 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 55CE13A6B7A for <rrg@irtf.org>; Tue, 28 Jul 2009 00:47:33 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 5254039E80B1 for <rrg@irtf.org>; Tue, 28 Jul 2009 00:47:16 -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 tSokvbRWOn2b for <rrg@irtf.org>; Tue, 28 Jul 2009 00:47:12 -0700 (PDT)
Received: from dhcp-11db.meeting.ietf.org (dhcp-11db.meeting.ietf.org [130.129.17.219]) by smtp.cs.ucla.edu (Postfix) with ESMTP id E18E239E8082 for <rrg@irtf.org>; Tue, 28 Jul 2009 00:47:11 -0700 (PDT)
Message-Id: <EB2F5DAA-5AB3-4023-AAFB-704C4341615E@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: rrg@irtf.org
In-Reply-To: <73455000-6ED1-4B0E-905E-5326705551E3@cs.ucla.edu>
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, 28 Jul 2009 00:47:09 -0700
References: <210810E2-AA86-4EAD-B6D7-88504E755982@nokia.com> <73455000-6ED1-4B0E-905E-5326705551E3@cs.ucla.edu>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [rrg] no agenda = no meeting?
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, 28 Jul 2009 07:47:34 -0000

On Jul 28, 2009, at 12:41 AM, Lixia Zhang wrote:

>
> On Jul 28, 2009, at 12:31 AM, Lars Eggert wrote:
>
>> Hi,
>>
>> given that there still isn't an agenda for Friday, I assume the  
>> meeting will be cancelled?
>
> maybe you did not look at the right place? :-)
>
> http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGagendaStockholm
>
> or maybe it is the chairs fault for not having updated right place
>
> Tony and Lixia

I feel a need to add a bit explanation for our agenda decision here:
1/ RRG is due for a recommendation by March, Tony and I feel that is  
the goal we need to focus the group's attention on.

2/ So we picked two proposals to discuss in depth on Friday morning.

Lixia


From tony.li@tony.li  Tue Jul 28 04:12:22 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 E1B523A6A8B for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 04:12:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 aqvKc1V9EqDW for <rrg@core3.amsl.com>; Tue, 28 Jul 2009 04:12:22 -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 DAFC93A68FC for <rrg@irtf.org>; Tue, 28 Jul 2009 04:12:21 -0700 (PDT)
Received: from OMTA14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by QMTA13.emeryville.ca.mail.comcast.net with comcast id MPCJ1c0031HpZEsADPCQNY; Tue, 28 Jul 2009 11:12:24 +0000
Received: from [130.129.83.225] ([130.129.83.225]) by OMTA14.emeryville.ca.mail.comcast.net with comcast id MPC91c0014rhcAi8aPCCtv; Tue, 28 Jul 2009 11:12:22 +0000
Message-ID: <4A6EDCF9.7010309@tony.li>
Date: Tue, 28 Jul 2009 13:11:53 +0200
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <210810E2-AA86-4EAD-B6D7-88504E755982@nokia.com>	<73455000-6ED1-4B0E-905E-5326705551E3@cs.ucla.edu> <6B77766B-73BC-4963-A1C2-7616F7741AE0@nokia.com>
In-Reply-To: <6B77766B-73BC-4963-A1C2-7616F7741AE0@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "rrg@irtf.org" <rrg@irtf.org>
Subject: Re: [rrg] no agenda = no meeting?
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, 28 Jul 2009 11:12:23 -0000

Lars Eggert wrote:
> On 2009-7-28, at 9:41, Lixia Zhang wrote:
>> maybe you did not look at the right place? :-)
>> http://trac.tools.ietf.org/group/irtf/trac/wiki/RRGagendaStockholm
> 
> I looked at the agenda page, which is blank.
> 
> http://tools.ietf.org/agenda/75/rrg.html
> vs., for example
> http://tools.ietf.org/agenda/75/iccrg.html


The official agenda has now been uploaded.

Once again, with feeling: while under development, the agenda lives on 
our Wiki page.  It's uploaded only when it has been frozen.

Tony


From HeinerHummel@aol.com  Wed Jul 29 09:05:25 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 5439C3A70D8 for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 09:05:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.451
X-Spam-Level: 
X-Spam-Status: No, score=-1.451 tagged_above=-999 required=5 tests=[AWL=-0.342, BAYES_05=-1.11, HTML_MESSAGE=0.001]
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 dGNi+5aW16Pd for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 09:05:24 -0700 (PDT)
Received: from imo-m22.mail.aol.com (imo-m22.mx.aol.com [64.12.137.3]) by core3.amsl.com (Postfix) with ESMTP id 1CE573A703A for <rrg@irtf.org>; Wed, 29 Jul 2009 09:05:23 -0700 (PDT)
Received: from imo-da01.mx.aol.com (imo-da01.mx.aol.com [205.188.169.199]) by imo-m22.mail.aol.com (v107.10) with ESMTP id RELAYIN3-44a7073371d9; Wed, 29 Jul 2009 12:05:11 -0400
Received: from HeinerHummel@aol.com by imo-da01.mx.aol.com (mail_out_v40_r1.5.) id 9.bdd.553996af (39332) for <rrg@irtf.org>; Wed, 29 Jul 2009 12:05:09 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <bdd.553996af.37a1cd35@aol.com>
Date: Wed, 29 Jul 2009 12:05:09 EDT
To: rrg@irtf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1248883509"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-IP: 205.188.169.199
Subject: [rrg] RRG Mobility Architecture
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, 29 Jul 2009 16:05:25 -0000

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

In einer eMail vom 26.07.2009 23:05:18 Westeurop=E4ische Normalzeit schrei=
bt  
mrw@lilacglade.org:

I like  the idea of viewing broadband subscribers whose addresses  
change  frequently as a subset of mobile nodes.  This is a particularly =
  
interesting case, because when they "roam" there is no "home  network"  
that can be reached using their former address, so some  existing  
mobility mechanisms wouldn't work in this  case. 
Margaret

Suggestion: The RRG group may also discuss the importance and impact  of=
 IP 
Mobility for a scalable routing architecture on this Friday. Wrt above: =
 
Eventually by also envisioning roaming users who are ALWAYS roaming, i.e.=
  
without any home (agent).
 
Heiner

-------------------------------1248883509
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 content=3D"text/html; charset=3DISO-8859-1" http-equiv=3DContent-Typ=
e>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18783"></HEAD>
<BODY style=3D"FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=3Dr=
ole_body 
bottomMargin=3D7 leftMargin=3D7 rightMargin=3D7 topMargin=3D7><FONT id=3Dr=
ole_document 
color=3D#000000 size=3D2 face=3DArial>
<DIV>In einer eMail vom 26.07.2009 23:05:18 Westeurop=E4ische Normalzeit=
 schreibt 
mrw@lilacglade.org:</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=3D=
Arial>I like 
  the idea of viewing broadband subscribers whose addresses&nbsp; <BR>chan=
ge 
  frequently as a subset of mobile nodes.&nbsp; This is a particularly&nbs=
p; 
  <BR>interesting case, because when they "roam" there is no "home 
  network"&nbsp; <BR>that can be reached using their former address, so so=
me 
  existing&nbsp; <BR>mobility mechanisms wouldn't work in this 
  case.&nbsp;<BR>Margaret<BR></FONT></BLOCKQUOTE>
<DIV><FONT style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D=
2 
face=3DArial>Suggestion: The RRG group may also discuss the importance and=
 impact 
of IP Mobility for a scalable routing architecture on this Friday. Wrt abo=
ve: 
Eventually by also envisioning roaming users who are ALWAYS roaming, i.e.=
 
without any home (agent).</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>

-------------------------------1248883509--

From rja@extremenetworks.com  Wed Jul 29 11:52:34 2009
Return-Path: <rja@extremenetworks.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 711083A6A29 for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 11:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 ASfg79V+yaia for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 11:52:33 -0700 (PDT)
Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by core3.amsl.com (Postfix) with ESMTP id A5BE13A6D87 for <rrg@irtf.org>; Wed, 29 Jul 2009 11:52:33 -0700 (PDT)
Received: from [10.30.20.71] ([70.104.193.39]) by vms173003.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KNK00H6S4EO9B10@vms173003.mailsrvcs.net> for rrg@irtf.org; Wed, 29 Jul 2009 13:52:04 -0500 (CDT)
Message-id: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>
From: RJ Atkinson <rja@extremenetworks.com>
To: "rrg@irtf.org 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: Wed, 29 Jul 2009 14:51:56 -0400
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [rrg] RRG Mobility Architecture
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, 29 Jul 2009 18:52:34 -0000

Earlier, Heiner Hummel wrote:
> Suggestion: The RRG group may also discuss the importance and impact
> of IP Mobility for a scalable routing architecture on this Friday.
>
> Wrt above: Eventually by also envisioning roaming users who are ALWAYS
> roaming, i.e. without any home (agent).


I agree on both counts.

I think the community needs a solution that supports not only site
multi-homing in a scalable way, but that also supports individual
host multi-homing, site mobility, and host mobility -- all integrated
together, with suitable scalability, and including appropriate security
capabilities.

An accidental artifact of IETF processes is that work undertaken
in Working Group A is often undertaken in isolation from work
in Working Group B.  This is not the fault of any person, but
just an IETF process artifact that is sometimes unavoidable.
An occasional result is having IETF standards for both A and B,
but that do not necessarily combine together in a harmonious,
integrated, and scalable way.

As this is the IRTF, and as "architecture" is explicitly within
scope, it would be good if we considered the broader set of issues
as the Routing RG examines different architectural alternatives.

Yours,

Ran


From lear@cisco.com  Wed Jul 29 13:24:05 2009
Return-Path: <lear@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 CC1BC3A6856 for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 13:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.079
X-Spam-Level: 
X-Spam-Status: No, score=-10.079 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 qhR+injiCer9 for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 13:24:04 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id A408D3A6F84 for <rrg@irtf.org>; Wed, 29 Jul 2009 13:24:03 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnQAADhNcEqQ/uCLe2dsb2JhbACBUpg6FiQGoT2IJ5AwBYQR
X-IronPort-AV: E=Sophos;i="4.43,290,1246838400"; d="scan'208";a="46094959"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 29 Jul 2009 20:24:04 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6TKO3Ir006406;  Wed, 29 Jul 2009 22:24:03 +0200
Received: from adsl-247-5-fixip.tiscali.ch (ams3-vpn-dhcp7671.cisco.com [10.61.93.246]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6TKO3CF024085; Wed, 29 Jul 2009 20:24:03 GMT
Message-ID: <4A70AFE3.2050102@cisco.com>
Date: Wed, 29 Jul 2009 22:24:03 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>
In-Reply-To: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>
X-Enigmail-Version: 0.97a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1598; t=1248899043; x=1249763043; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20[rrg]=20RRG=20Mobility=20Architecture |Sender:=20; bh=zi6CetU5DrqfzsnmYdCTkbWThs5uMIEIOPefV9orC8M=; b=AvkzaFP00GBIXGNdfZJYYF0DgHVCC84BSd6BpNb88bjJ0fuViPKzy29zMb he0feECb0dfu9HEuPhKFNdFn8jruqvAVvrReaeVUg05sWQ47SdkzsGj4hc9K 6CxO/UTHHx;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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, 29 Jul 2009 20:24:05 -0000

It's a worthy endeavor to understand how two hosts that both always move
and have no home rendezvous.

Eliot


On 7/29/09 8:51 PM, RJ Atkinson wrote:
>
> Earlier, Heiner Hummel wrote:
>> Suggestion: The RRG group may also discuss the importance and impact
>> of IP Mobility for a scalable routing architecture on this Friday.
>>
>> Wrt above: Eventually by also envisioning roaming users who are ALWAYS
>> roaming, i.e. without any home (agent).
>
>
> I agree on both counts.
>
> I think the community needs a solution that supports not only site
> multi-homing in a scalable way, but that also supports individual
> host multi-homing, site mobility, and host mobility -- all integrated
> together, with suitable scalability, and including appropriate security
> capabilities.
>
> An accidental artifact of IETF processes is that work undertaken
> in Working Group A is often undertaken in isolation from work
> in Working Group B.  This is not the fault of any person, but
> just an IETF process artifact that is sometimes unavoidable.
> An occasional result is having IETF standards for both A and B,
> but that do not necessarily combine together in a harmonious,
> integrated, and scalable way.
>
> As this is the IRTF, and as "architecture" is explicitly within
> scope, it would be good if we considered the broader set of issues
> as the Routing RG examines different architectural alternatives.
>
> Yours,
>
> Ran
>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>


From HeinerHummel@aol.com  Wed Jul 29 14:45:42 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 1D2E83A659A for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 14:45:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.948
X-Spam-Level: 
X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 AiexRh023whW for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 14:45:41 -0700 (PDT)
Received: from imo-m26.mail.aol.com (imo-m26.mx.aol.com [64.12.137.7]) by core3.amsl.com (Postfix) with ESMTP id 2DAA93A6BD9 for <rrg@irtf.org>; Wed, 29 Jul 2009 14:45:41 -0700 (PDT)
Received: from imo-ma02.mx.aol.com (imo-ma02.mx.aol.com [64.12.78.137]) by imo-m26.mail.aol.com (v107.10) with ESMTP id RELAYIN1-24a70c253b8; Wed, 29 Jul 2009 17:42:43 -0400
Received: from HeinerHummel@aol.com by imo-ma02.mx.aol.com  (mail_out_v40_r1.5.) id c.cd8.524e85b0 (39332);  Wed, 29 Jul 2009 17:45:00 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <cd8.524e85b0.37a21cdb@aol.com>
Date: Wed, 29 Jul 2009 17:44:59 EDT
To: lear@cisco.com, rja@extremenetworks.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1248903899"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-IP: 64.12.78.137
Cc: rrg@irtf.org
Subject: Re: [rrg] RRG Mobility Architecture
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, 29 Jul 2009 21:45:42 -0000

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

 
In einer eMail vom 29.07.2009 22:24:24 Westeurop=E4ische Normalzeit schrei=
bt  
lear@cisco.com:

It's a  worthy endeavor to understand how two hosts that both always move
and have  no home rendezvous.

Eliot





:-) I had only in mind a scenario where just one (source) party is homeles=
s 
 i.e. all the time on the go.
May be that the associated service which I remember is not perfectly  
adequate (sorry for that): I remember a telephone feature where  a service=
 man 
had no home station but just a chip card with special  service authorizati=
on 
bits on it which he could plug into other phone sets  while visiting other=
 
people's places .
 
After all I only suggested to also discuss IP Mobility and would be  
interested in the outcome.
As to avoid any misunderstanding: my favorite solution for the scalability=
  
problem is based on associating the geographical coordinates of the  
closest DFZ-routers with the individual users' IP addresses (RFC1712).  He=
reby no 
IP Mobility is involved at all.  
 
But my speculation is this: Maybe further aspects show up in the mobility=
  
discussion for which from geo-coordinates derived identifiers might be  
beneficial too.
 
Heiner

-------------------------------1248903899
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 content=3D"text/html; charset=3DISO-8859-1" http-equiv=3DContent-Typ=
e>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18783"></HEAD>
<BODY style=3D"FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=3Dr=
ole_body 
bottomMargin=3D7 leftMargin=3D7 rightMargin=3D7 topMargin=3D7><FONT id=3Dr=
ole_document 
color=3D#000000 size=3D2 face=3DArial>
<DIV>
<DIV>In einer eMail vom 29.07.2009 22:24:24 Westeurop=E4ische Normalzeit=
 schreibt 
lear@cisco.com:</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=3D=
Arial>It's a 
  worthy endeavor to understand how two hosts that both always move<BR>and=
 have 
  no home rendezvous.<BR><BR>Eliot<BR><BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>&nbsp;</DIV>
<DIV>:-) I had only in mind a scenario where just one (source) party is ho=
meless 
i.e. all the time on the go.</DIV>
<DIV>May be that the associated service which I remember is not&nbsp;perfe=
ctly 
adequate (sorry for that):&nbsp;I remember&nbsp;a telephone feature where=
 
a&nbsp;service man&nbsp;had no home station but just a chip card with spec=
ial 
service authorization bits on it which he could plug into other phone sets=
 
while&nbsp;visiting other people's places&nbsp;.</DIV>
<DIV>&nbsp;</DIV>
<DIV>After all I&nbsp;only suggested to also discuss IP Mobility and would=
 be 
interested in the outcome.</DIV>
<DIV>As to avoid any misunderstanding: my favorite solution for the scalab=
ility 
problem&nbsp;is based on associating the geographical coordinates&nbsp;of=
 the 
closest DFZ-routers&nbsp;with the individual users' IP addresses&nbsp;(RFC=
1712). 
Hereby no IP Mobility is involved at all. &nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>But my speculation is this: Maybe further aspects show up in the mobi=
lity 
discussion for which from geo-coordinates derived identifiers might be 
beneficial too.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>

-------------------------------1248903899--

From rja@extremenetworks.com  Wed Jul 29 15:16:21 2009
Return-Path: <rja@extremenetworks.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 41B5B3A703C for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 15:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 VSvoNtirBVzC for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 15:16:20 -0700 (PDT)
Received: from vms173017pub.verizon.net (vms173017pub.verizon.net [206.46.173.17]) by core3.amsl.com (Postfix) with ESMTP id 7E0283A6BED for <rrg@irtf.org>; Wed, 29 Jul 2009 15:16:20 -0700 (PDT)
Received: from [10.30.20.71] ([70.104.193.39]) by vms173017.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KNK00BJGDUU8720@vms173017.mailsrvcs.net> for rrg@irtf.org; Wed, 29 Jul 2009 17:16:11 -0500 (CDT)
Message-id: <592EFD02-4CA4-47BD-ACBF-1132B854A331@extremenetworks.com>
From: RJ Atkinson <rja@extremenetworks.com>
To: Eliot Lear <lear@cisco.com>
In-reply-to: <4A70AFE3.2050102@cisco.com>
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7bit
MIME-version: 1.0 (Apple Message framework v935.3)
Date: Wed, 29 Jul 2009 18:16:03 -0400
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com> <4A70AFE3.2050102@cisco.com>
X-Mailer: Apple Mail (2.935.3)
Cc: "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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, 29 Jul 2009 22:16:21 -0000

On  29 Jul 2009, at 16:24, Eliot Lear wrote:
> It's a worthy endeavor to understand how two hosts
> that both always move and have no home rendezvous.

That's the hardest case, but not impossible operationally
*in the real world with reality constraints*.

THe main trick is to use DNS (or something like it) as
a fallback rendezvous to rediscover the correspondent's
new location.  (I think the idea of first using DNS for
mobility rendezvous might have been first published in
a paper in the IEEE LCS proceedings about a decade back;
it certainly is not my idea.)

One imagines that a control message ("ICMP Location Update")
can be sent by the host (about to move or just finished moving)
to its correspondents && the host also updates its A/AAAA
(or equivalent) records in the DNS using the widely available
Secure DNS Dynamic Update mechanism (available in BIND, MS Windows,
and for MacOS X [source: "DNS & BIND" book, 5th Edition])

If that ICMP message doesn't reach some correspondent (e.g.
because the correspondent moved at the same instant, unlikely
though that might be), then the correspondent can use the DNS
to find the original host's new address (and the original host
can use the DNS to find the correspondent's new address).

In the limit, if both nodes are constantly changing their
point of network attachment, then both nodes will not
be able to send or receive any packets before a new Layer-3
location change -- at which point both nodes are effectively
disconnected, at least until they stand still for a bit.

In practice, most mobility is handled by layer-2 mechanisms
(e.g. mobile phone stuff; IEEE 802.1 bridging) -- at least
part of the time.  For all of the discussion above, only
changes in the layer-3 point of attachment matter.

[In a previous life, I had some small experience dealing with
IPv4 mobility issues, as my then employer had a few hundred
ships deployed around the globe and some large number of
airplanes.  I find that their real-world operational issues
continue to be relevant.  Solutions that will work there
likely also will work nearly everywhere else.]

Cheers,

Ran


From lear@cisco.com  Wed Jul 29 22:49:08 2009
Return-Path: <lear@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 B656A3A6E32 for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 22:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.166
X-Spam-Level: 
X-Spam-Status: No, score=-8.166 tagged_above=-999 required=5 tests=[AWL=-1.567, 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 6sTE6uOD7GjG for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 22:49:07 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id 6B3273A6995 for <rrg@irtf.org>; Wed, 29 Jul 2009 22:49:06 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHXRcEpAaMF0/2dsb2JhbACBUrgriCeQHQWEEYFO
X-IronPort-AV: E=Sophos;i="4.43,293,1246838400"; d="scan'208";a="58707320"
Received: from syd-dkim-1.cisco.com ([64.104.193.116]) by syd-iport-1.cisco.com with ESMTP; 30 Jul 2009 05:49:06 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by syd-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6U5n4Gw018071;  Thu, 30 Jul 2009 15:49:05 +1000
Received: from adsl-247-5-fixip.tiscali.ch (ams3-vpn-dhcp4690.cisco.com [10.61.82.81]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6U5n4N9005921; Thu, 30 Jul 2009 05:49:04 GMT
Message-ID: <4A71344F.1030107@cisco.com>
Date: Thu, 30 Jul 2009 07:49:03 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com> <4A70AFE3.2050102@cisco.com> <592EFD02-4CA4-47BD-ACBF-1132B854A331@extremenetworks.com>
In-Reply-To: <592EFD02-4CA4-47BD-ACBF-1132B854A331@extremenetworks.com>
X-Enigmail-Version: 0.97a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3454; t=1248932946; x=1249796946; c=relaxed/simple; s=syddkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20[rrg]=20RRG=20Mobility=20Architecture |Sender:=20; bh=WWiHbuOypTVkRfh5Gd6gJKFa/jKUmWY+3OY/A4NCpzY=; b=YpoGRhDPoA8t9cO3fxEJZE3A7iCTGp6Ru3mwlqhDYr1JKD6Btj+/I23iF/ 1qhVle9Fq5QYfaIztf0OmUgBKfQhpS8x19JBDADw8esfxpyySwu4MFG1jtVm 1jhr4zf7VXKKN9PvZ69SpNt/kFWsi8lJvWTzcHBmwA+M2moAMqF/E=;
Authentication-Results: syd-dkim-1; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/syddkim1002 verified; ); 
Cc: "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 05:49:08 -0000

Ran,

Before we get into method perhaps it's worth understanding (a) which use
cases one wants to solve for, and (b) the idea that perhaps – perhaps –
one size does not fit all.  Also, it seems to me that another reasonable
question to ask in the context of mobility is what signaling is required
between layers?  Both above and below IP.  One thing that might then
prove useful is a comparison to where most implementations are.

The classic case and point of this would be when one wanted to move from
a cell carrier to 802.11 or back.  Another case would be moving from one
carrier to another.  A third would be moving within a carrier between
regions.

And then there's the question of scaling and general use.  For instance,
perhaps something will for cars but not trainloads of people all
rebinding at once.  Perhaps a solution will scale to that but not fast
moving trains.  Perhaps a solution will scale to that but not fast
moving airplanes.

Finally, there's a whole lot of work in this space.  One question that
should be asked is what would any new solution propose to solve that the
old ones don't?

Eliot

On 7/30/09 12:16 AM, RJ Atkinson wrote:
>
> On  29 Jul 2009, at 16:24, Eliot Lear wrote:
>> It's a worthy endeavor to understand how two hosts
>> that both always move and have no home rendezvous.
>
> That's the hardest case, but not impossible operationally
> *in the real world with reality constraints*.
>
> THe main trick is to use DNS (or something like it) as
> a fallback rendezvous to rediscover the correspondent's
> new location.  (I think the idea of first using DNS for
> mobility rendezvous might have been first published in
> a paper in the IEEE LCS proceedings about a decade back;
> it certainly is not my idea.)
>
> One imagines that a control message ("ICMP Location Update")
> can be sent by the host (about to move or just finished moving)
> to its correspondents && the host also updates its A/AAAA
> (or equivalent) records in the DNS using the widely available
> Secure DNS Dynamic Update mechanism (available in BIND, MS Windows,
> and for MacOS X [source: "DNS & BIND" book, 5th Edition])
>
> If that ICMP message doesn't reach some correspondent (e.g.
> because the correspondent moved at the same instant, unlikely
> though that might be), then the correspondent can use the DNS
> to find the original host's new address (and the original host
> can use the DNS to find the correspondent's new address).
>
> In the limit, if both nodes are constantly changing their
> point of network attachment, then both nodes will not
> be able to send or receive any packets before a new Layer-3
> location change -- at which point both nodes are effectively
> disconnected, at least until they stand still for a bit.
>
> In practice, most mobility is handled by layer-2 mechanisms
> (e.g. mobile phone stuff; IEEE 802.1 bridging) -- at least
> part of the time.  For all of the discussion above, only
> changes in the layer-3 point of attachment matter.
>
> [In a previous life, I had some small experience dealing with
> IPv4 mobility issues, as my then employer had a few hundred
> ships deployed around the globe and some large number of
> airplanes.  I find that their real-world operational issues
> continue to be relevant.  Solutions that will work there
> likely also will work nearly everywhere else.]
>
> Cheers,
>
> Ran
>
>


From tony.li@tony.li  Wed Jul 29 23:22:27 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 DF7833A6AA0 for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 23:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 m9Ce7p5epXON for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 23:22:27 -0700 (PDT)
Received: from QMTA01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id EA22F3A68A3 for <rrg@irtf.org>; Wed, 29 Jul 2009 23:22:26 -0700 (PDT)
Received: from OMTA19.westchester.pa.mail.comcast.net ([76.96.62.98]) by QMTA01.westchester.pa.mail.comcast.net with comcast id N6LE1c00127AodY516NVtY; Thu, 30 Jul 2009 06:22:29 +0000
Received: from [10.43.1.72] ([77.241.97.116]) by OMTA19.westchester.pa.mail.comcast.net with comcast id N6Qj1c0022WfiAM3f6QmZn; Thu, 30 Jul 2009 06:24:55 +0000
Message-ID: <4A713BDD.4090402@tony.li>
Date: Thu, 30 Jul 2009 08:21:17 +0200
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>	<4A70AFE3.2050102@cisco.com>	<592EFD02-4CA4-47BD-ACBF-1132B854A331@extremenetworks.com> <4A71344F.1030107@cisco.com>
In-Reply-To: <4A71344F.1030107@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: RJ Atkinson <rja@extremenetworks.com>, "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 06:22:28 -0000

Eliot Lear wrote:
> Finally, there's a whole lot of work in this space.  One question that
> should be asked is what would any new solution propose to solve that the
> old ones don't?


All of the old ones have great difficulty in changing the L3 point of 
attachment, and end up using the Home Agent concept as the rendezvous 
point.  If location is independent of identity, then it's conceivable 
that one can update peer locations without loosing connections.

Tony

From scott.brim@gmail.com  Wed Jul 29 23:40:33 2009
Return-Path: <scott.brim@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 2A7913A68A3 for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 23:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.678
X-Spam-Level: 
X-Spam-Status: No, score=-2.678 tagged_above=-999 required=5 tests=[AWL=-0.079, 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 fj608N2SDV2z for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 23:40:29 -0700 (PDT)
Received: from mail-bw0-f218.google.com (mail-bw0-f218.google.com [209.85.218.218]) by core3.amsl.com (Postfix) with ESMTP id EC8B73A6BEE for <rrg@irtf.org>; Wed, 29 Jul 2009 23:40:28 -0700 (PDT)
Received: by bwz18 with SMTP id 18so1184696bwz.7 for <rrg@irtf.org>; Wed, 29 Jul 2009 23:40:29 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=EtC38wVy7UMZPhs6iNcfEA9e+h+6/pQ3mqtA9XdErjg=; b=lkkCsf5uJfxYEOkY+cwQnXYPAkTWRQT11IDI9IlkJLAsbqJICtdkioKHtrYTDs2vJl a24YRh8KNGxnGEVDT3oqwjmnYmKGUpqkySLWMQSjpkcxokZXclR2ikuMmQ4gkpC+Y1vU FTfQ44PlHmtdrvsXQtnKJwuOxweybMJOd9Plg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=mISQajs2LGL95eGQBjCSJLuaoREYICOgD/58LpJdsZXk5qq+laTknkmRsFq31FkNyc tdD7zg5VaZ7OxxAyrKJYDr3x0ZnJtJAFu7a1gkdcQIIYnEpzZGvlLwHrvzJOpdOU3u9p 5a5W/gFj0kQjlYcU63slzTwN2QM7JK93su35g=
Received: by 10.103.161.18 with SMTP id n18mr432300muo.48.1248936029766; Wed, 29 Jul 2009 23:40:29 -0700 (PDT)
Received: from dhcp-55fa.meeting.ietf.org ([130.129.85.250]) by mx.google.com with ESMTPS id y2sm10741107mug.12.2009.07.29.23.40.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 29 Jul 2009 23:40:28 -0700 (PDT)
Message-ID: <4A71405A.50301@gmail.com>
Date: Thu, 30 Jul 2009 08:40:26 +0200
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>
In-Reply-To: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 06:40:33 -0000

RJ Atkinson allegedly wrote on 07/29/2009 20:51 GMT+02:00:
> I think the community needs a solution that supports not only site
> multi-homing in a scalable way, but that also supports individual
> host multi-homing, site mobility, and host mobility -- all integrated
> together, with suitable scalability, and including appropriate security
> capabilities.

I just wonder if they all should be solved with the same mechanism.  The 
issues in site mobility are by necessity network-level issues, but 
issues in individual node mobility are not all solvable at the network 
layer.  If some node mobility issues must be dealt with at higher 
layers, then that changes the context in which the ones that _can_ be 
solved at the network layer are considered.

> As this is the IRTF, and as "architecture" is explicitly within
> scope, it would be good if we considered the broader set of issues
> as the Routing RG examines different architectural alternatives.

Agreed, as long as we do it from the perspective of "RRG".


RJ Atkinson allegedly wrote on 07/30/2009 24:16 GMT+02:00:
> In the limit, if both nodes are constantly changing their
> point of network attachment, then both nodes will not
> be able to send or receive any packets before a new Layer-3
> location change -- at which point both nodes are effectively
> disconnected, at least until they stand still for a bit.

... using the mechanisms you are assuming. :-)

Scott

From lear@cisco.com  Wed Jul 29 23:41:22 2009
Return-Path: <lear@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 2EA7C3A6838 for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 23:41:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.942
X-Spam-Level: 
X-Spam-Status: No, score=-9.942 tagged_above=-999 required=5 tests=[AWL=0.657,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 JnarWQigAUk1 for <rrg@core3.amsl.com>; Wed, 29 Jul 2009 23:41:21 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id BF1A03A68E3 for <rrg@irtf.org>; Wed, 29 Jul 2009 23:41:20 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnQAAFrdcEqQ/uCLe2dsb2JhbACBUpg6FiQGnzWIJ5AVBYIygV8
X-IronPort-AV: E=Sophos;i="4.43,293,1246838400"; d="scan'208";a="46111093"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 30 Jul 2009 06:41:21 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6U6fIIN022252;  Thu, 30 Jul 2009 08:41:18 +0200
Received: from adsl-247-5-fixip.tiscali.ch (ams3-vpn-dhcp4690.cisco.com [10.61.82.81]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6U6fKh6015181; Thu, 30 Jul 2009 06:41:20 GMT
Message-ID: <4A714090.7060600@cisco.com>
Date: Thu, 30 Jul 2009 08:41:20 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>	<4A70AFE3.2050102@cisco.com>	<592EFD02-4CA4-47BD-ACBF-1132B854A331@extremenetworks.com> <4A71344F.1030107@cisco.com> <4A713BDD.4090402@tony.li>
In-Reply-To: <4A713BDD.4090402@tony.li>
X-Enigmail-Version: 0.97a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=345; t=1248936078; x=1249800078; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20[rrg]=20RRG=20Mobility=20Architecture |Sender:=20; bh=A/Denu4G1KEZEv0HsFj1hoKYJfzQT5KP0jnZnufP3vA=; b=FwCejzbJ16vtPGB+8R/l0Og6+1/Tl+2zcYLLa2eYzHFGhDjQBpGEeSuuHe 8EO0nifTn/ioE+gS0mjMOLVPJLudHbogZmRQwWFKAWp97tOPSuKsoiB85sLC HzRA2shvZj;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: RJ Atkinson <rja@extremenetworks.com>, "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 06:41:22 -0000

On 7/30/09 8:21 AM, Tony Li wrote:
> All of the old ones have great difficulty in changing the L3 point of
> attachment, and end up using the Home Agent concept as the rendezvous
> point.  If location is independent of identity, then it's conceivable
> that one can update peer locations without loosing connections.

What about HIP?

From tony.li@tony.li  Thu Jul 30 01:15:43 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 EC3D628C1F3 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 01:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 TE4SN4VwwvH0 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 01:15:43 -0700 (PDT)
Received: from QMTA02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by core3.amsl.com (Postfix) with ESMTP id D495928C1F0 for <rrg@irtf.org>; Thu, 30 Jul 2009 01:15:42 -0700 (PDT)
Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59]) by QMTA02.westchester.pa.mail.comcast.net with comcast id N8Fl1c0031GhbT8528Flqe; Thu, 30 Jul 2009 08:15:45 +0000
Received: from [130.129.83.225] ([130.129.83.225]) by OMTA07.westchester.pa.mail.comcast.net with comcast id N8FX1c0014rhcAi3T8FaBX; Thu, 30 Jul 2009 08:15:43 +0000
Message-ID: <4A715694.6030900@tony.li>
Date: Thu, 30 Jul 2009 10:15:16 +0200
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>	<4A70AFE3.2050102@cisco.com>	<592EFD02-4CA4-47BD-ACBF-1132B854A331@extremenetworks.com> <4A71344F.1030107@cisco.com> <4A713BDD.4090402@tony.li> <4A714090.7060600@cisco.com>
In-Reply-To: <4A714090.7060600@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: RJ Atkinson <rja@extremenetworks.com>, "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 08:15:44 -0000

Eliot Lear wrote:
> 
> On 7/30/09 8:21 AM, Tony Li wrote:
>> All of the old ones have great difficulty in changing the L3 point of
>> attachment, and end up using the Home Agent concept as the rendezvous
>> point.  If location is independent of identity, then it's conceivable
>> that one can update peer locations without loosing connections.
> 
> What about HIP?
> 

Yes, ok, if you go to the trouble of CGI's then you can change too. 
Wouldn't it just be simpler and cleaner to have location be separate?

Tony


From darlewis@cisco.com  Thu Jul 30 01:21:16 2009
Return-Path: <darlewis@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 09D6728C202 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 01:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.381
X-Spam-Level: 
X-Spam-Status: No, score=-6.381 tagged_above=-999 required=5 tests=[AWL=0.218,  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 DJUUm2NEGll7 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 01:21:15 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 6ACD328C22A for <rrg@irtf.org>; Thu, 30 Jul 2009 01:19:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,293,1246838400"; d="scan'208";a="191075431"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 30 Jul 2009 08:19:59 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6U8JxEu009322;  Thu, 30 Jul 2009 01:19:59 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n6U8JxLr025458; Thu, 30 Jul 2009 08:19:59 GMT
Received: from xmb-sjc-213.amer.cisco.com ([171.70.151.153]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 30 Jul 2009 01:19:59 -0700
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: Thu, 30 Jul 2009 01:19:57 -0700
Message-ID: <C0ACCB7B60E6F14B9AC46D742C1009A13550CC@xmb-sjc-213.amer.cisco.com>
In-Reply-To: <4A714090.7060600@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] RRG Mobility Architecture
Thread-Index: AcoQ4MOJEq1tHvIVRFy7sWDc0fT7cQADUqcQ
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>	<4A70AFE3.2050102@cisco.com>	<592EFD02-4CA4-47BD-ACBF-1132B854A331@extremenetworks.com><4A71344F.1030107@cisco.com> <4A713BDD.4090402@tony.li> <4A714090.7060600@cisco.com>
From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
To: "Eliot Lear" <lear@cisco.com>, "Tony Li" <tony.li@tony.li>
X-OriginalArrivalTime: 30 Jul 2009 08:19:59.0137 (UTC) FILETIME=[8747C910:01CA10EE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=677; t=1248941999; x=1249805999; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=darlewis@cisco.com; z=From:=20=22Darrel=20Lewis=20(darlewis)=22=20<darlewis@cisc o.com> |Subject:=20RE=3A=20[rrg]=20RRG=20Mobility=20Architecture |Sender:=20; bh=SN+LuYKmW6skzVm1oDdtWgfg86VOd/fNY2cjMwJ3H7I=; b=ivNQ4JoIz+TQTamyMm1Zwf/qdfTYnDPTXVhsSI0PtrER0ReGvhmbapDQPo p6sm1qucNJVQxXCpamGw6L2q8VREHFK16AAHR6rbM7QMNVrKM+PjZ45PQgkg c0/gJIILit;
Authentication-Results: sj-dkim-2; header.From=darlewis@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: RJ Atkinson <rja@extremenetworks.com>, rrg@irtf.org
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 08:21:16 -0000

>=20
>=20
> On 7/30/09 8:21 AM, Tony Li wrote:
> > All of the old ones have great difficulty in changing the=20
> L3 point of
> > attachment, and end up using the Home Agent concept as the=20
> rendezvous
> > point.  If location is independent of identity, then it's=20
> conceivable
> > that one can update peer locations without loosing connections.
>=20
> What about HIP?

With HIP, how do two correspondents (which negotiate a HITs between
them) refer to a 3rd which they don't communicate with at the moment?
Ephemeral IDs are problematic in the real world, since global naming and
referrals today tends to use unique and semi-permanent IDs.

-Darrel

From tony.li@tony.li  Thu Jul 30 04:11:22 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 C5EF33A6C13 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 04:11:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 mRwBIsNsDpKN for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 04:11:22 -0700 (PDT)
Received: from QMTA12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by core3.amsl.com (Postfix) with ESMTP id 17DFA3A6B62 for <rrg@irtf.org>; Thu, 30 Jul 2009 04:11:22 -0700 (PDT)
Received: from OMTA16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by QMTA12.emeryville.ca.mail.comcast.net with comcast id NBBQ1c0061ZMdJ4ACBBQ0y; Thu, 30 Jul 2009 11:11:24 +0000
Received: from [130.129.83.225] ([130.129.83.225]) by OMTA16.emeryville.ca.mail.comcast.net with comcast id NBEL1c0034rhcAi8cBEPSs; Thu, 30 Jul 2009 11:14:28 +0000
Message-ID: <4A717FC2.6090607@tony.li>
Date: Thu, 30 Jul 2009 13:10:58 +0200
From: Tony Li <tony.li@tony.li>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [rrg] Volunteers needed
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: Thu, 30 Jul 2009 11:11:22 -0000

Hi all,

Can I get volunteers for:

- Minute taker
- Jabber scribe


Thanks,
Tony


From scott.brim@gmail.com  Thu Jul 30 04:54:35 2009
Return-Path: <scott.brim@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 DBD803A6908 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 04:54:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.675
X-Spam-Level: 
X-Spam-Status: No, score=-2.675 tagged_above=-999 required=5 tests=[AWL=-0.076, 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 eABYzMP0h45K for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 04:54:35 -0700 (PDT)
Received: from mail-fx0-f228.google.com (mail-fx0-f228.google.com [209.85.220.228]) by core3.amsl.com (Postfix) with ESMTP id 7D94C28C212 for <rrg@irtf.org>; Thu, 30 Jul 2009 04:53:46 -0700 (PDT)
Received: by fxm28 with SMTP id 28so580242fxm.17 for <rrg@irtf.org>; Thu, 30 Jul 2009 04:53:45 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=XEd40fix+HqpqS3fwJxBXeDbidcbeIdH7MeMf/sPn0w=; b=OpLwfWTfM46dL0wGCRW95gmbIoSBmsQmwW5ny+I42U/A0N4mq9Q5boo2xK/+9C1OpJ 1kSbn3zR2qyZDRmpE+7JsEA/JaoPzuGi52iBPpasnJG4Uo3aq/qOTm5gxkvSZemSKfu8 66h1MLc3SGRJDV+lUG/7ty7YpJkG1szIiRxhw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=FwmD1Evk/+qOHnEczdAQJmbvwUB3c8ZK0wnMYaDM4iCKTVcNqbJhjyx+4YgH/DzWgV XLdyVOeq7JCykl8P4NXcJpsCtXc0jsdGROlPJjnkS81RjjoFs/sABTY/0JSErSG0gQWp y+Yw+0mPZAOUxQJyhpRCg3QGRd1cjRCr3xIow=
Received: by 10.103.169.18 with SMTP id w18mr641043muo.69.1248954825100; Thu, 30 Jul 2009 04:53:45 -0700 (PDT)
Received: from dhcp-55fa.meeting.ietf.org ([130.129.85.250]) by mx.google.com with ESMTPS id j10sm2147851mue.15.2009.07.30.04.53.43 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 30 Jul 2009 04:53:44 -0700 (PDT)
Message-ID: <4A7189C6.6090408@gmail.com>
Date: Thu, 30 Jul 2009 13:53:42 +0200
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>	<4A70AFE3.2050102@cisco.com>	<592EFD02-4CA4-47BD-ACBF-1132B854A331@extremenetworks.com>	<4A71344F.1030107@cisco.com> <4A713BDD.4090402@tony.li> <4A714090.7060600@cisco.com>
In-Reply-To: <4A714090.7060600@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: RJ Atkinson <rja@extremenetworks.com>, "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 11:54:36 -0000

Eliot Lear allegedly wrote on 07/30/2009 08:41 GMT+02:00:
> On 7/30/09 8:21 AM, Tony Li wrote:
>> All of the old ones have great difficulty in changing the L3 point of
>> attachment, and end up using the Home Agent concept as the rendezvous
>> point.  If location is independent of identity, then it's conceivable
>> that one can update peer locations without loosing connections.
>
> What about HIP?

HIP doesn't handle both ends moving without at least one rendezvous 
server.  I don't know of anything that doesn't need some kind of stable 
point.


Tony Li allegedly wrote on 07/30/2009 10:15 GMT+02:00:
> Yes, ok, if you go to the trouble of CGI's then you can change too.
> Wouldn't it just be simpler and cleaner to have location be separate?

(1) it's possible to run HIP with only control messages secured, or 
various levels of security on the data packets.  (2) HIP is getting put 
in chips ...

... but (3) I don't understand, how does HIP not separate location?


Darrel Lewis (darlewis) allegedly wrote on 07/30/2009 10:19 GMT+02:00:
> With HIP, how do two correspondents (which negotiate a HITs between
> them) refer to a 3rd which they don't communicate with at the moment?
> Ephemeral IDs are problematic in the real world, since global naming and
> referrals today tends to use unique and semi-permanent IDs.

Referrals are another problem.  In a simple world you just go look up 
the referred HI or address or other stable identifier in a registry, 
like DNS or whatever you used to find the first peer you're talking to. 
  In a complex world, you may need something like 
http://tools.ietf.org/html/draft-carpenter-behave-referral-object (which 
was presented in BEHAVE).

swb

From rja@extremenetworks.com  Thu Jul 30 06:24:23 2009
Return-Path: <rja@extremenetworks.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 6D8CD3A6938 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 06:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 Qfn4B2rq6EmD for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 06:24:22 -0700 (PDT)
Received: from vms173001pub.verizon.net (vms173001pub.verizon.net [206.46.173.1]) by core3.amsl.com (Postfix) with ESMTP id B84283A6802 for <rrg@irtf.org>; Thu, 30 Jul 2009 06:24:22 -0700 (PDT)
Received: from [10.30.20.71] ([70.104.193.39]) by vms173001.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KNL00ALEJW9E350@vms173001.mailsrvcs.net> for rrg@irtf.org; Thu, 30 Jul 2009 08:24:14 -0500 (CDT)
Message-id: <BC6C33E3-EA69-49D2-89D0-AD532AEF331D@extremenetworks.com>
From: RJ Atkinson <rja@extremenetworks.com>
To: "rrg@irtf.org RG" <rrg@irtf.org>
In-reply-to: <4A71405A.50301@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: Thu, 30 Jul 2009 09:24:08 -0400
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com> <4A71405A.50301@gmail.com>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 13:24:23 -0000

On  30 Jul 2009, at 02:40, Scott Brim wrote:
> I just wonder if they all should be solved with the same mechanism.

I suggested that we needed an architecture that supports the
broad range of issues before the RG.  Eliot sought an example,
so I provided *an example*.

Now you and Eliot have both gotten bogged down in the example,
and discussion of architecture seems gone from the thread.

Sigh.

> The issues in site mobility are by necessity network-level issues,

That claim isn't obviously true.

For example, one imagines that an architectural approach that
supports host mobility could also support groups of hosts
being mobile together (i.e. network mobility).

Yours,

Ran
rja@extremenetworks.com



From jnc@mercury.lcs.mit.edu  Thu Jul 30 06:31:58 2009
Return-Path: <jnc@mercury.lcs.mit.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 2530F28C268 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 06:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 1gL9+7z4LbYZ for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 06:31:57 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 6CC2C3A6921 for <rrg@irtf.org>; Thu, 30 Jul 2009 06:31:57 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 438FA6BE5C4; Thu, 30 Jul 2009 09:31:58 -0400 (EDT)
To: rrg@irtf.org
Message-Id: <20090730133158.438FA6BE5C4@mercury.lcs.mit.edu>
Date: Thu, 30 Jul 2009 09:31:58 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 13:31:58 -0000

    > From: RJ Atkinson <rja@extremenetworks.com>

    > Eliot sought an example, so I provided *an example*.
    > 
    > Now you and Eliot have both gotten bogged down in the example, and
    > discussion of architecture seems gone from the thread.

I propose we call this behavioural pattern "IETF disorder", since it's so
common in the IETF! (Ducks! :-)

	Noel

From lear@cisco.com  Thu Jul 30 06:54:53 2009
Return-Path: <lear@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 637FB28C1E1 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 06:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.024
X-Spam-Level: 
X-Spam-Status: No, score=-10.024 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 2X9waDEoSMVt for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 06:54:52 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 41BE128C1C4 for <rrg@irtf.org>; Thu, 30 Jul 2009 06:54:52 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnQAAE9DcUqQ/uCKe2dsb2JhbACBUpg6FiQGn3uIJ5AhBYQR
X-IronPort-AV: E=Sophos;i="4.43,295,1246838400"; d="scan'208";a="46148643"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 30 Jul 2009 13:54:53 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6UDsqHN023929;  Thu, 30 Jul 2009 15:54:52 +0200
Received: from adsl-247-4-fixip.tiscali.ch (dhcp-10-61-103-169.cisco.com [10.61.103.169]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6UDsqSZ012812; Thu, 30 Jul 2009 13:54:52 GMT
Message-ID: <4A71A62C.1010608@cisco.com>
Date: Thu, 30 Jul 2009 15:54:52 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>	<4A71405A.50301@gmail.com> <BC6C33E3-EA69-49D2-89D0-AD532AEF331D@extremenetworks.com>
In-Reply-To: <BC6C33E3-EA69-49D2-89D0-AD532AEF331D@extremenetworks.com>
X-Enigmail-Version: 0.97a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=719; t=1248962092; x=1249826092; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20[rrg]=20RRG=20Mobility=20Architecture |Sender:=20; bh=rpJVbCragXqk3x8k60ae94PPK4p8lRQdshJ4KWYY/84=; b=QTx12zhgaL6pRAAglkrHU8Ils43T4bc8tzWGm5YKlCrPaVMsn3O4jYsW26 K7QXGFHL54QQ854KcPPp3Sn8I078abunP7ry0yVPmQ5U86l+Uo88taEecaBt LC3SwpCIyr;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); 
Cc: "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 13:54:53 -0000

On 7/30/09 3:24 PM, RJ Atkinson wrote:
>
> On  30 Jul 2009, at 02:40, Scott Brim wrote:
>> I just wonder if they all should be solved with the same mechanism.
>
> I suggested that we needed an architecture that supports the
> broad range of issues before the RG.  Eliot sought an example,
> so I provided *an example*.
>
> Now you and Eliot have both gotten bogged down in the example,
> and discussion of architecture seems gone from the thread.

I raised engineering constraints that we need to consider when designing
a system, and by no means all of them.  Determining the point at which
that crosses to architecture should occur directly after we've counted
the number of angels on a pin.

Eliot


From rja@extremenetworks.com  Thu Jul 30 07:34:57 2009
Return-Path: <rja@extremenetworks.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 D6F2B3A6C30 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 07:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 OfJITRI7iynq for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 07:34:57 -0700 (PDT)
Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by core3.amsl.com (Postfix) with ESMTP id 5DF293A71A4 for <rrg@irtf.org>; Thu, 30 Jul 2009 07:34:42 -0700 (PDT)
Received: from [10.30.20.71] ([70.104.193.39]) by vms173003.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KNL00HNKN5G9D60@vms173003.mailsrvcs.net> for rrg@irtf.org; Thu, 30 Jul 2009 09:34:33 -0500 (CDT)
Message-id: <7073E5AD-3126-4869-B599-EE305F1B1582@extremenetworks.com>
From: RJ Atkinson <rja@extremenetworks.com>
To: Eliot Lear <lear@cisco.com>
In-reply-to: <4A71A62C.1010608@cisco.com>
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: Thu, 30 Jul 2009 10:34:28 -0400
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com> <4A71405A.50301@gmail.com> <BC6C33E3-EA69-49D2-89D0-AD532AEF331D@extremenetworks.com> <4A71A62C.1010608@cisco.com>
X-Mailer: Apple Mail (2.935.3)
Cc: "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 14:34:57 -0000

On  30 Jul 2009, at 09:54, Eliot Lear wrote:
> On 7/30/09 3:24 PM, RJ Atkinson wrote:
>>
>> On  30 Jul 2009, at 02:40, Scott Brim wrote:
>>> I just wonder if they all should be solved with the same mechanism.
>>
>> I suggested that we needed an architecture that supports the
>> broad range of issues before the RG.  Eliot sought an example,
>> so I provided *an example*.
>>
>> Now you and Eliot have both gotten bogged down in the example,
>> and discussion of architecture seems gone from the thread.
>
> I raised engineering constraints that we need to consider when  
> designing
> a system, and by no means all of them.  Determining the point at which
> that crosses to architecture should occur directly after we've counted
> the number of angels on a pin.

No.  You saw it yourself.  As soon as the phrase "engineering
constraints" appears, one has left architecture behind and crossed over
into engineering.

Mind, it is very important to get the engineering right.  The Internet
community keeps learning the hard way that it is also very important
to sort out the architecture BEFORE crossing over into engineering.

This is the kind of thing that jnc and some others of us have been
saying for a few years now on this list, so it is neither a new thought
nor uniquely mine.

Yours,

Ran


From lear@cisco.com  Thu Jul 30 07:36:04 2009
Return-Path: <lear@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 E0A3C3A71B4 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 07:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[AWL=-1.400, 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 IuhYF0JPHKfQ for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 07:36:04 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 2CD5C3A71AE for <rrg@irtf.org>; Thu, 30 Jul 2009 07:36:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHNMcUqQ/uCL/2dsb2JhbACBUrh/iCeQIwWEEQ
X-IronPort-AV: E=Sophos;i="4.43,295,1246838400"; d="scan'208";a="191189066"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by sj-iport-2.cisco.com with ESMTP; 30 Jul 2009 14:35:57 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6UEZt80011328;  Thu, 30 Jul 2009 16:35:55 +0200
Received: from adsl-247-4-fixip.tiscali.ch (dhcp-10-61-103-169.cisco.com [10.61.103.169]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6UEZtf5022848; Thu, 30 Jul 2009 14:35:55 GMT
Message-ID: <4A71AFCC.5080701@cisco.com>
Date: Thu, 30 Jul 2009 16:35:56 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com> <4A71405A.50301@gmail.com> <BC6C33E3-EA69-49D2-89D0-AD532AEF331D@extremenetworks.com> <4A71A62C.1010608@cisco.com> <7073E5AD-3126-4869-B599-EE305F1B1582@extremenetworks.com>
In-Reply-To: <7073E5AD-3126-4869-B599-EE305F1B1582@extremenetworks.com>
X-Enigmail-Version: 0.97a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1489; t=1248964555; x=1249828555; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20[rrg]=20RRG=20Mobility=20Architecture |Sender:=20; bh=NbBwi5qQLkw/W4AQ/GMp4LYoBRxLqqFtPWdygt2NVew=; b=JEtk3IWUoHe/9yhSdV/Toer3gbXzJf4+ilUJGrug9+xPProzFl9LCSZvXF WWj0J538QwMIGy9ZIKBqn7LVCSaYzPoNA+fhiZF0+bQXhMLFt3FGfnR8MylQ m06OpIkuG0;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: "rrg@irtf.org RG" <rrg@irtf.org>
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 14:36:05 -0000

And so the counting of angels has begun (or continued).

Eliot

On 7/30/09 4:34 PM, RJ Atkinson wrote:
>
> On  30 Jul 2009, at 09:54, Eliot Lear wrote:
>> On 7/30/09 3:24 PM, RJ Atkinson wrote:
>>>
>>> On  30 Jul 2009, at 02:40, Scott Brim wrote:
>>>> I just wonder if they all should be solved with the same mechanism.
>>>
>>> I suggested that we needed an architecture that supports the
>>> broad range of issues before the RG.  Eliot sought an example,
>>> so I provided *an example*.
>>>
>>> Now you and Eliot have both gotten bogged down in the example,
>>> and discussion of architecture seems gone from the thread.
>>
>> I raised engineering constraints that we need to consider when designing
>> a system, and by no means all of them.  Determining the point at which
>> that crosses to architecture should occur directly after we've counted
>> the number of angels on a pin.
>
> No.  You saw it yourself.  As soon as the phrase "engineering
> constraints" appears, one has left architecture behind and crossed over
> into engineering.
>
> Mind, it is very important to get the engineering right.  The Internet
> community keeps learning the hard way that it is also very important
> to sort out the architecture BEFORE crossing over into engineering.
>
> This is the kind of thing that jnc and some others of us have been
> saying for a few years now on this list, so it is neither a new thought
> nor uniquely mine.
>
> Yours,
>
> Ran
>
>


From eric.fleischman@boeing.com  Thu Jul 30 08:09:32 2009
Return-Path: <eric.fleischman@boeing.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 D274E28C11F for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 08:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 yFxMEOG90hgB for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 08:09:32 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id EF4223A6BA7 for <rrg@irtf.org>; Thu, 30 Jul 2009 08:09:31 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n6UF9Rjj005017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Jul 2009 08:09:27 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n6UF9Rt3010227; Thu, 30 Jul 2009 08:09:27 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n6UF9OK6010029; Thu, 30 Jul 2009 08:09:27 -0700 (PDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 30 Jul 2009 08:09:25 -0700
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: Thu, 30 Jul 2009 08:09:22 -0700
Message-ID: <474EEBD229DF754FB83D256004D021080C424EFD@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <4A715694.6030900@tony.li>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] RRG Mobility Architecture
Thread-Index: AcoQ7fMNOSD4lHmmSCeBhnV55illWAAOEfug
References: <166A8BB9-EE00-400F-9297-56B291682F7A@extremenetworks.com>	<4A70AFE3.2050102@cisco.com>	<592EFD02-4CA4-47BD-ACBF-1132B854A331@extremenetworks.com><4A71344F.1030107@cisco.com> <4A713BDD.4090402@tony.li><4A714090.7060600@cisco.com> <4A715694.6030900@tony.li>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "Tony Li" <tony.li@tony.li>, "Eliot Lear" <lear@cisco.com>
X-OriginalArrivalTime: 30 Jul 2009 15:09:25.0451 (UTC) FILETIME=[B9F1D1B0:01CA1127]
Cc: RJ Atkinson <rja@extremenetworks.com>, rrg@irtf.org
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 15:09:32 -0000

Beating an already dead horse: The MANET deployments I have been
involved with handle mobility within the L3 routing system and, of
course, have no difficulty in readily changing L3 attachment points. The
network attachment points may or may not be re-numbered, based upon the
nature of the movement (e.g., intra-subnetwork moves are transparent)
and scaling issues.=20

Concerning HIP, we have extensive demos that show how HIP protects
communicating end systems from the effects of mobility and multihoming
in MANET environments.=20

Our Secure Mobile Architecture (SMA), which is now available from The
Open Group, also shows that one can even replace entire underlying
network systems in real time without impacting the existing sessions of
communicating hosts that use HIP.

-----Original Message-----
From: Tony Li [mailto:tony.li@tony.li]=20
Sent: Thursday, July 30, 2009 1:15 AM
To: Eliot Lear
Cc: RJ Atkinson; rrg@irtf.org RG
Subject: Re: [rrg] RRG Mobility Architecture

Eliot Lear wrote:
>=20
> On 7/30/09 8:21 AM, Tony Li wrote:
>> All of the old ones have great difficulty in changing the L3 point of

>> attachment, and end up using the Home Agent concept as the rendezvous

>> point.  If location is independent of identity, then it's conceivable

>> that one can update peer locations without loosing connections.
>=20
> What about HIP?
>=20

Yes, ok, if you go to the trouble of CGI's then you can change too.=20
Wouldn't it just be simpler and cleaner to have location be separate?

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From HeinerHummel@aol.com  Thu Jul 30 11:14:40 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 E70533A67F5 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 11:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.165
X-Spam-Level: 
X-Spam-Status: No, score=-2.165 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 NI4LCDpUjVkd for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 11:14:39 -0700 (PDT)
Received: from imr-ma03.mx.aol.com (imr-ma03.mx.aol.com [64.12.206.41]) by core3.amsl.com (Postfix) with ESMTP id 7F57728C245 for <rrg@irtf.org>; Thu, 30 Jul 2009 11:14:00 -0700 (PDT)
Received: from imo-ma01.mx.aol.com (imo-ma01.mx.aol.com [64.12.78.136]) by imr-ma03.mx.aol.com (8.14.1/8.14.1) with ESMTP id n6UIDt4u032334; Thu, 30 Jul 2009 14:13:55 -0400
Received: from HeinerHummel@aol.com by imo-ma01.mx.aol.com  (mail_out_v40_r1.5.) id j.c89.4bd85771 (14501);  Thu, 30 Jul 2009 14:13:53 -0400 (EDT)
From: HeinerHummel@aol.com
Message-ID: <c89.4bd85771.37a33ce1@aol.com>
Date: Thu, 30 Jul 2009 14:13:53 EDT
To: rja@extremenetworks.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1248977633"
X-Mailer: 9.0 SE for Windows sub 5021
Cc: rrg@irtf.org
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 18:14:41 -0000

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

 
In einer eMail vom 30.07.2009 16:35:24 Westeurop=E4ische Normalzeit schrei=
bt  
rja@extremenetworks.com:

On   30 Jul 2009, at 09:54, Eliot Lear wrote:
> On 7/30/09 3:24 PM, RJ  Atkinson wrote:
>>
>> On  30 Jul 2009, at 02:40, Scott  Brim wrote:
>>> I just wonder if they all should be solved with  the same mechanism.
>>
>> I suggested that we needed an  architecture that supports the
>> broad range of issues before the  RG.  Eliot sought an example,
>> so I provided *an  example*.
>>
>> Now you and Eliot have both gotten bogged  down in the example,
>> and discussion of architecture seems gone  from the thread.
>
> I raised engineering constraints that we need  to consider when  
> designing
> a system, and by no means  all of them.  Determining the point at which
> that crosses to  architecture should occur directly after we've counted
> the number of  angels on a pin.

No.  You saw it yourself.  As soon as the  phrase "engineering
constraints" appears, one has left architecture behind  and crossed over
into engineering.

Mind, it is very important to get  the engineering right.  The Internet
community keeps learning the hard  way that it is also very important
to sort out the architecture BEFORE  crossing over into engineering.

This is the kind of thing that jnc and  some others of us have been
saying for a few years now on this list, so it  is neither a new thought
nor uniquely  mine.

Yours,

Ran



IMHO, the problem with the RRG is that it is completely backward  oriented=
. 
Today each handphone is able to take advantage of the geographical  
coordinates/GPS. But routers of even a future routing architecture still=
 must  not.
 
Ran pointed out that scaling is not all. Indeed, I have also stressed many=
  
times the many advantages by viewing the internet topology. 1-2 years ago=
 I 
 asked the rtgwg-folks whether their first accomplishment was the end or=
 
the  beginning. The answer I got: the beginning. But since then nothing 
occurred.  Multipath forwarding can be substantially extended, not just EC=
MP and 
not just  what the rtgwg did, but as well detours  which even start out wi=
th  
crankback, entirely connection-less,  - yes, intra-domain  wise  But in 
inter-domain routing there is not even a rear mirror.  Hence neither a COM=
PLETE 
Multipath forwarding nor adequate TE (as to deal with  traffic congestion)=
 
can be done. Will say: intra-domain routing could be  improved 
substantially, but in the same sense inter-domain routing, too. I could =
 repeat the 
entire list again and again what is prevented so far....
 
Since quite a while I realized that it  will take some years till  the LIS=
P 
worship is over. So I keep being patient but allow me to speak up  wheneve=
r 
this group gets stuck again with the same old problems.
I remember the July meeting 2000 in London. It was said: well we have this=
  
problem, but no rush, we have a ten years time frame. Now we have July  
2009.
 
A second reply wrt to the "users without home agent" point. At first, it=
 is 
 only relevant that just one, i.e. the destination is without home agent.=
 
And  yes, a reasonable service could be to search for this user, in the ca=
se 
where  the source has only an idea inside which geo-patch the destination=
 
might  currently be located.
 
Heiner

-------------------------------1248977633
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 content=3D"text/html; charset=3DISO-8859-1" http-equiv=3DContent-Typ=
e>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18812"></HEAD>
<BODY style=3D"FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=3Dr=
ole_body 
bottomMargin=3D7 leftMargin=3D7 rightMargin=3D7 topMargin=3D7><FONT id=3Dr=
ole_document 
color=3D#000000 size=3D2 face=3DArial>
<DIV>
<DIV>In einer eMail vom 30.07.2009 16:35:24 Westeurop=E4ische Normalzeit=
 schreibt 
rja@extremenetworks.com:</DIV>
<BLOCKQUOTE 
style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"=
><FONT 
  style=3D"BACKGROUND-COLOR: transparent" color=3D#000000 size=3D2 face=3D=
Arial>On&nbsp; 
  30 Jul 2009, at 09:54, Eliot Lear wrote:<BR>&gt; On 7/30/09 3:24 PM, RJ=
 
  Atkinson wrote:<BR>&gt;&gt;<BR>&gt;&gt; On&nbsp; 30 Jul 2009, at 02:40,=
 Scott 
  Brim wrote:<BR>&gt;&gt;&gt; I just wonder if they all should be solved=
 with 
  the same mechanism.<BR>&gt;&gt;<BR>&gt;&gt; I suggested that we needed=
 an 
  architecture that supports the<BR>&gt;&gt; broad range of issues before=
 the 
  RG.&nbsp; Eliot sought an example,<BR>&gt;&gt; so I provided *an 
  example*.<BR>&gt;&gt;<BR>&gt;&gt; Now you and Eliot have both gotten bog=
ged 
  down in the example,<BR>&gt;&gt; and discussion of architecture seems go=
ne 
  from the thread.<BR>&gt;<BR>&gt; I raised engineering constraints that=
 we need 
  to consider when&nbsp; <BR>&gt; designing<BR>&gt; a system, and by no me=
ans 
  all of them.&nbsp; Determining the point at which<BR>&gt; that crosses=
 to 
  architecture should occur directly after we've counted<BR>&gt; the numbe=
r of 
  angels on a pin.<BR><BR>No.&nbsp; You saw it yourself.&nbsp; As soon as=
 the 
  phrase "engineering<BR>constraints" appears, one has left architecture=
 behind 
  and crossed over<BR>into engineering.<BR><BR>Mind, it is very important=
 to get 
  the engineering right.&nbsp; The Internet<BR>community keeps learning th=
e hard 
  way that it is also very important<BR>to sort out the architecture BEFOR=
E 
  crossing over into engineering.<BR><BR>This is the kind of thing that jn=
c and 
  some others of us have been<BR>saying for a few years now on this list,=
 so it 
  is neither a new thought<BR>nor uniquely 
  mine.<BR><BR>Yours,<BR><BR>Ran<BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>IMHO, the problem with the&nbsp;RRG is that it is completely backward=
 
oriented. Today each handphone is able to take advantage of the geographic=
al 
coordinates/GPS. But routers of even a future routing architecture still=
 must 
not.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Ran pointed out that scaling is not all. Indeed, I have also stressed=
 many 
times the many advantages by viewing the internet topology. 1-2 years ago=
 I 
asked the rtgwg-folks whether their first accomplishment was the end or th=
e 
beginning. The answer I got: the beginning. But since then nothing occurre=
d. 
Multipath forwarding can be substantially extended, not just ECMP and not=
 just 
what the rtgwg did, but as well detours&nbsp; which even start out with 
crankback,&nbsp;entirely connection-less,&nbsp; - yes, intra-domain 
wise&nbsp;&nbsp;But in inter-domain routing there is not even a rear mirro=
r. 
Hence neither a COMPLETE Multipath forwarding nor adequate TE (as to deal=
 with 
traffic congestion) can be done. Will say: intra-domain routing could be=
 
improved substantially, but in the same sense inter-domain routing, too.=
 I could 
repeat the entire list again and again what is prevented so far....</DIV>
<DIV>&nbsp;</DIV>
<DIV>Since quite a while I realized that&nbsp;it &nbsp;will take some year=
s till 
the LISP worship is over. So I keep being patient but allow me to speak up=
 
whenever this group gets stuck again with the same old problems.</DIV>
<DIV>I remember the July meeting 2000 in London. It was said: well we have=
 this 
problem, but no rush, we have a ten years time frame. Now we have July 
2009.</DIV>
<DIV>&nbsp;</DIV>
<DIV>A second reply wrt to the "users without home agent" point. At first,=
 it is 
only relevant that just one, i.e. the destination is without home agent.=
 And 
yes, a reasonable service could be to search for this user, in the case wh=
ere 
the source has only an idea inside which geo-patch the destination might=
 
currently be located.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>

-------------------------------1248977633--

From lear@cisco.com  Thu Jul 30 11:55:37 2009
Return-Path: <lear@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 4C7DA3A6C9B for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 11:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.937
X-Spam-Level: 
X-Spam-Status: No, score=-9.937 tagged_above=-999 required=5 tests=[AWL=0.661,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 n2crqTro811A for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 11:55:36 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id D55A93A682F for <rrg@irtf.org>; Thu, 30 Jul 2009 11:55:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsAAAJ+JcUqQ/uCKe2dsb2JhbACBUlEylz4BARYkBqFEiCeQNwWEF4FO
X-IronPort-AV: E=Sophos;i="4.43,296,1246838400"; d="scan'208,217";a="46164150"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 30 Jul 2009 18:55:32 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6UItWrJ016622 for <rrg@irtf.org>; Thu, 30 Jul 2009 20:55:32 +0200
Received: from adsl-247-4-fixip.tiscali.ch (dhcp-10-61-103-169.cisco.com [10.61.103.169]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6UItVw8011350 for <rrg@irtf.org>; Thu, 30 Jul 2009 18:55:31 GMT
Message-ID: <4A71ECA3.1050000@cisco.com>
Date: Thu, 30 Jul 2009 20:55:31 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
X-Enigmail-Version: 0.97a
Content-Type: multipart/alternative; boundary="------------060302070205070809090304"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7009; t=1248980132; x=1249844132; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20[rrg]=20RRG=20Mobility=20Architecture |Sender:=20; bh=S3GajARvrh8+wJqLDC7qo9SrUliCDap8VyAKY2cb+Bk=; b=qfXIsLMbcf0DwgSGh+hbwdY05pbF/spJNYSeinXRs/t7IlX6QSnG+Bsi2M +TIQqQPr+yKKwWJ/Cru9mrBC/yhSJNKd7ClXHSC4LZb7tIjppcYBXzYkcYLa QzfByMpWbv;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); 
Subject: Re: [rrg] RRG Mobility Architecture
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: Thu, 30 Jul 2009 18:55:37 -0000

This is a multi-part message in MIME format.
--------------060302070205070809090304
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

[resending, with two edits]

I'm sorry, Ran.  I shouldn't have been quite so flippant.  BUT.

The architecture v. engineering debate is a red herring that gets thrown
around too easily.  Every PhD student has to do a literature survey to
understand what has been done, in order to demonstrate that there is at
least something new to do that will improve society.  That is what is
needed here.  Nothing more, and certainly nothing less, and it has been
woefully lacking in the past.  N.B., I am not asking that we get stuck
in history– that is a favorite pastime of this organization, but there
is a balance between the two extremes.

If we are going to create a new mobility architecture we should
understand how the existing ones work and don't work, and recognize what
is worthy of our time and what is not.  We've all done the numbers. 
What I stated were common pitfalls the conversation usually follows like:

    * trying to solve the problem exclusively at L3, a favorite within
      the IETF.  You and I know that not considering these problems from
      the transceiver to the application means poor deployment (more on
      this later).
    * not using the right tool for the right purpose.  I'll spare the
      guilty parties, but you know who you are.
    * simply not understanding what problem they are solving, and what
      problems to leave for others.  How many efforts (and perhaps
      entire companies) have failed because of scope?  The IETF perhaps
      goes to the other extreme now, but we'll leave that alone.
    * attempting to shoehorn every last problem into a solution.  I
      believe in the need for locator/id separation, but it is *not* a
      panacea.  For instance, use of different *locators* may have
      involve different costs, that may need to be exposed all the way
      to the application layer.  The iPhone demonstrates this best of
      all with some of its apps.  And so the app can't simply cope with
      an identifier, as many would like.  It has to have additional
      information (although it may not need the locators themselves).

But back to that literature survey thing.  People are often quite hard
on MIPv6, and often for the wrong reasons.  While MIPv6 bind times have
often been viewed as atrocious, often ranging from 20-60 seconds, in
many instances that has been due to poor signaling in the layers below. 
The real problems with MIPv6 (putting aside triangular routing in MIP)
is the need for v6, firewall impedance mismatch, and poor interaction of
the layers above and below L3.  There are assuredly other problems I'm
not mentioning, like the complexity of dealing with private address
spaces.  HIP implementations have some of these problems.  But that is
often times it- we may in fact have the right *Internet* *standards* but
need work elsewhere.  And some of this, such as FW traversal may be just
poor incentive alignment, or scope creep, depending on how you view the
problem.  How do you view the problem?

To restate my main point: if we're going to design a new system, we had
darn well better understand the old systems, and what their limits are.

Eliot

--------------060302070205070809090304
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>

<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#ffffff" text="#000000">
<div class="moz-text-html" lang="x-unicode">[resending, with two edits]<br>
<br>
I'm sorry, Ran.  I shouldn't have been quite so flippant.  BUT.<br>
<br>
The architecture v. engineering debate is a red herring that gets
thrown around too easily.  Every PhD student has to do a literature
survey to understand what has been done, in order to demonstrate that
there is at least something new to do that will improve society.  That
is what is needed here.  Nothing more, and certainly nothing less, and
it has been woefully lacking in the past. 
N.B., I am not asking that we get stuck in history– that is a favorite
pastime of this organization, but there is a balance between the two
extremes.<br>
<br>
If we are going to create a new mobility architecture we should
understand how the existing ones work and don't work, and recognize
what is worthy of our time and what is not.  We've all done the
numbers.  What I stated were common pitfalls the conversation usually
follows like:<br>
<ul>
  <li>trying to solve the problem exclusively at L3, a favorite within
the IETF.  You and I know that not considering these problems from the
transceiver to the application means poor deployment (more on this
later).</li>
  <li>not using the right tool for the right purpose.  I'll spare the
guilty parties, but you know who you are.<br>
  </li>
  <li>simply not understanding what problem they are solving, and what
problems to leave for others.  How many efforts (and perhaps entire
companies) have failed because of scope?  The IETF perhaps goes to the
other extreme now, but we'll leave that alone.<br>
  </li>
  <li>attempting to shoehorn every last problem into a solution.  I
believe in the need for locator/id separation, but it is <b>not</b> a
panacea.  For instance, use of different <b>locators</b> may have
involve different costs, that may need to be exposed all the way to the
application layer.  The iPhone demonstrates this best of all with some
of its apps.  And so the app can't simply cope with an identifier, as
many would like.  It has to have additional information (although it
may not need the locators themselves).<br>
  </li>
</ul>
But back to that literature survey thing.  People are often quite hard
on MIPv6, and often for the wrong reasons.  While MIPv6 bind times have
often been viewed as atrocious, often ranging from 20-60 seconds, in
many instances that has been due to poor signaling in the layers
below.  The real problems with MIPv6 (putting aside triangular routing
in MIP) is the need for v6, firewall impedance mismatch, and poor
interaction of the layers above and below L3.  There are assuredly
other problems I'm not mentioning, like the complexity of dealing with
private address spaces.  HIP implementations have some of these
problems.  But that is often times it- we may in fact have the right <b>Internet</b>
<b>standards</b> but need work elsewhere.  And some of this, such as FW
traversal may be just poor incentive alignment, or scope creep,
depending on how you view the problem.  How do you view the problem?<br>
<br>
To restate my main point: if we're going to design a new system, we had
darn well better understand the old systems, and what their limits are.<br>
<br>
Eliot<br>
</div>
</body>
</html>

--------------060302070205070809090304--

From christian.vogt@ericsson.com  Thu Jul 30 18:21:58 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 C432F3A68BC for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 18:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.384
X-Spam-Level: 
X-Spam-Status: No, score=-6.384 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 rznzZofQ2uKx for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 18:21:57 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 81E413A6A08 for <rrg@irtf.org>; Thu, 30 Jul 2009 18:21:57 -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 n6V01ItS005773 for <rrg@irtf.org>; Thu, 30 Jul 2009 19:01:19 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 30 Jul 2009 19:01:03 -0500
Received: from [10.16.1.9] ([164.48.124.45]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 30 Jul 2009 19:01:03 -0500
Message-Id: <D85AE3AF-CE61-4937-9448-35DB18E859D0@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Routing Research Group Mailing List <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: Fri, 31 Jul 2009 02:01:02 +0200
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 31 Jul 2009 00:01:03.0477 (UTC) FILETIME=[FEA65250:01CA1171]
Subject: [rrg] CFP - Special Issue on Internet Routing Scalability in IEEE JSAC
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, 31 Jul 2009 01:21:58 -0000

Dear all -

FYI and for further distribution:  Below is a call for papers for a
special issue on Internet routing scalability in the IEEE Journal on
Selected Areas in Communications.

- Christian


------------------------------------------------------------------------


                           CALL FOR PAPERS
       IEEE Journal on Selected Areas in Communications (JSAC)
                    INTERNET ROUTING SCALABILITY

The Internet routing infrastructure provides connectivity among millions
of computers around the globe. As the Internet went through a phenomenal
growth over the last three decades, its routing system has encountered
multitude of challenges brought forth by the unprecedented scale of the
system.  In addition to the rapid growth in the number of customer
networks, there have been increasing trends of customer network
multihoming to facilitate load balancing and fail-over between multiple
providers, desiring provider-independent IP address assignments over
provider-allocated addresses to avoid internal renumbering when changing
providers, and Virtual Private Networks (VPNs) deployment to support
business and enterprise users. Unfortunately, the rapid user growth
compounded with multihoming, provider-independent addressing, and VPN
provisioning has led to a fast growth of the global routing systems. At
the same time, Internet service providers (ISPs) face economical
constraints that may prevent them from prompt upgrade to the latest
technologies to meet the demands.

More recently, the Internet routing architecture also confronted two new
challenges: the imminent exhaustion of IPv4 address space and hence
foreseeable wide deployment of IPv6, and the emerging mobile access to
Internet from billions of hand-held devices. The latter further drives
the demands for IPv6 roll out, yet the sheer size of the IPv6 address
space presents a great scaling concern to the routing system, and the
impact of various global-scale mobility solutions on the routing system
remains to be fully understood. The ever increasing size of the global
routing system also directly impacts its security and management. It is
imperative to solve the routing scalability problems in order to enable
continued growth of the Internet while allowing ISPs to operate with
feasible upgrade intervals.  This need has sparked a plethora of recent
research efforts, with proposed solutions ranging from
backwards-compatible, evolutionary techniques, to revolutionary
clean-slate approaches.

This special issue will focus on the latest research on Internet routing
scalability.  Prospective authors are expected to submit original
unpublished contributions to further analyze the problem space, to
compare and evaluate existing solution proposals, or to present new
solutions.  Topics of interest include, but are not limited to, the
following:

- addressing schemes that facilitate scalable routing designs,
- scalable solutions to network multihoming, traffic engineering, and
  VPN support
- impact of mobility on routing scalability
- routing threat analyses and security methods
- economical considerations
- analytical or comparative studies

All submissions must be prepared in accordance with the format described
at http://www.jsac.ucsd.edu/Guidelines/info.html, and be sent via email
to jsac-routing@lists.cs.ucla.edu according to the following timetable:

Manuscript submission:       October 30, 2009
Acceptance notification:     February 15, 2010
Final Manuscript due:        May 15, 2010
Publication:                 3rd quarter, 2010

Guest Editors:
- Tim Griffin, University of Cambridge UK (Timothy.Griffin@cl.cam.ac.uk)
- Tony Li, Ericsson USA (tony.li@tony.li)
- Dan Massey, Colorado State University, USA (massey@cs.colostate.edu)
- Christian Vogt, Ericsson USA (christian.vogt@ericsson.com)
- Jia Wang, AT&T Labs, Inc. - Research, USA (jiawang@research.att.com)
- Lixia Zhang, University of California, USA (lixia@cs.ucla.edu)

http://www.jsac.ucsd.edu/Calls/internetroutingscalabilityCFP.pdf



From christian.vogt@ericsson.com  Thu Jul 30 18:21:58 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 D56203A6A08 for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 18:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.373
X-Spam-Level: 
X-Spam-Status: No, score=-6.373 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 SVEwJ0Hbw+bO for <rrg@core3.amsl.com>; Thu, 30 Jul 2009 18:21:57 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id CE9B63A6A49 for <rrg@irtf.org>; Thu, 30 Jul 2009 18:21:57 -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 n6V01IxM005771 for <rrg@irtf.org>; Thu, 30 Jul 2009 19:01:19 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 30 Jul 2009 19:01:01 -0500
Received: from [10.16.1.9] ([164.48.124.45]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 30 Jul 2009 19:01:00 -0500
Message-Id: <7C4EF97C-5187-40B0-8C19-A55C9400D9D5@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Routing Research Group Mailing List <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: Fri, 31 Jul 2009 01:59:42 +0200
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 31 Jul 2009 00:01:00.0743 (UTC) FILETIME=[FD052570:01CA1171]
Subject: [rrg] CFP - Special Issue on Internet Routing Scalability in IEEE JSAC
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, 31 Jul 2009 01:21:58 -0000

Dear all -

FYI and for further distribution:  Below is a call for papers for a
special issue on Internet routing scalability in the IEEE Journal on
Selected Areas in Communications.

- Christian


------------------------------------------------------------------------


                            CALL FOR PAPERS
        IEEE Journal on Selected Areas in Communications (JSAC)
                     INTERNET ROUTING SCALABILITY

The Internet routing infrastructure provides connectivity among millions
of computers around the globe. As the Internet went through a phenomenal
growth over the last three decades, its routing system has encountered
multitude of challenges brought forth by the unprecedented scale of the
system.  In addition to the rapid growth in the number of customer
networks, there have been increasing trends of customer network
multihoming to facilitate load balancing and fail-over between multiple
providers, desiring provider-independent IP address assignments over
provider-allocated addresses to avoid internal renumbering when changing
providers, and Virtual Private Networks (VPNs) deployment to support
business and enterprise users. Unfortunately, the rapid user growth
compounded with multihoming, provider-independent addressing, and VPN
provisioning has led to a fast growth of the global routing systems. At
the same time, Internet service providers (ISPs) face economical
constraints that may prevent them from prompt upgrade to the latest
technologies to meet the demands.

More recently, the Internet routing architecture also confronted two new
challenges: the imminent exhaustion of IPv4 address space and hence
foreseeable wide deployment of IPv6, and the emerging mobile access to
Internet from billions of hand-held devices. The latter further drives
the demands for IPv6 roll out, yet the sheer size of the IPv6 address
space presents a great scaling concern to the routing system, and the
impact of various global-scale mobility solutions on the routing system
remains to be fully understood. The ever increasing size of the global
routing system also directly impacts its security and management. It is
imperative to solve the routing scalability problems in order to enable
continued growth of the Internet while allowing ISPs to operate with
feasible upgrade intervals.  This need has sparked a plethora of recent
research efforts, with proposed solutions ranging from
backwards-compatible, evolutionary techniques, to revolutionary
clean-slate approaches.

This special issue will focus on the latest research on Internet routing
scalability.  Prospective authors are expected to submit original
unpublished contributions to further analyze the problem space, to
compare and evaluate existing solution proposals, or to present new
solutions.  Topics of interest include, but are not limited to, the
following:

- addressing schemes that facilitate scalable routing designs,
- scalable solutions to network multihoming, traffic engineering, and
   VPN support
- impact of mobility on routing scalability
- routing threat analyses and security methods
- economical considerations
- analytical or comparative studies

All submissions must be prepared in accordance with the format described
at http://www.jsac.ucsd.edu/Guidelines/info.html, and be sent via email
to jsac-routing@lists.cs.ucla.edu according to the following timetable:

Manuscript submission:       October 30, 2009
Acceptance notification:     February 15, 2010
Final Manuscript due:        May 15, 2010
Publication:                 3rd quarter, 2010

Guest Editors:
- Tim Griffin, University of Cambridge UK (Timothy.Griffin@cl.cam.ac.uk)
- Tony Li, Ericsson USA (tony.li@tony.li)
- Dan Massey, Colorado State University, USA (massey@cs.colostate.edu)
- Christian Vogt, Ericsson USA (christian.vogt@ericsson.com)
- Jia Wang, AT&T Labs, Inc. - Research, USA (jiawang@research.att.com)
- Lixia Zhang, University of California, USA (lixia@cs.ucla.edu)

http://www.jsac.ucsd.edu/Calls/internetroutingscalabilityCFP.pdf



From xuxh@huawei.com  Fri Jul 31 01:23:26 2009
Return-Path: <xuxh@huawei.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 B45A728C2F2 for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 01:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.28
X-Spam-Level: 
X-Spam-Status: No, score=0.28 tagged_above=-999 required=5 tests=[AWL=-0.024,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1, SARE_SUB_RAND_LETTRS4=0.799]
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 lTs73ep8cor6 for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 01:23:26 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 3527228C28A for <rrg@irtf.org>; Fri, 31 Jul 2009 01:23:25 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KNN000000JW8R@szxga03-in.huawei.com> for rrg@irtf.org; Fri, 31 Jul 2009 16:21:32 +0800 (CST)
Received: from x41208a ([10.111.12.94]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KNN00N0I0JV3C@szxga03-in.huawei.com> for rrg@irtf.org; Fri, 31 Jul 2009 16:21:32 +0800 (CST)
Date: Fri, 31 Jul 2009 16:21:31 +0800
From: Xu Xiaohu <xuxh@huawei.com>
To: rja@extremenetworks.com
Message-id: <004201ca11b7$e8f30b10$5e0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: quoted-printable
Thread-index: AcoRt+iHrYYXRMbrTlaM9enzktGB3Q==
Cc: 'IRTF RRG' <rrg@irtf.org>
Subject: [rrg] Some concerns about ILNP
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, 31 Jul 2009 08:23:26 -0000

Hi Ran,

If I understand your ILNP correctly, it is much silimar with the GSE.  =
If so, I'm wondering whether the issues with the GSE described in =
draft-ietf-ipngwg-esd-analysis  have been successfully solved by the =
ILNP, e.g., identifier authentication issue. It seems that  the answers =
to these hard issues have not been mentioned in your slides.

I noticed the following statement in your slides, do you believe that =
62-bit field is long enough to prevent the security of the binding of =
the 62-bit hash value and the public key from being easily compromised =
once you use the HIP/CGA like ideas to deal with the identifier =
authentication issue?

*********************************
If scope bit is local, have 62 bits that can be anything:
=E2=80=A3 Cryptographically Generated Identifier (a la CGA proposals)
=E2=80=A3 Hash of a public-key (a la HIP)
=E2=80=A3 Pseudo-randomly generated (a la IPv6 Privacy AutoConf)
**********************************

Best regard,

Xiaohu


From xuxh@huawei.com  Fri Jul 31 01:37:33 2009
Return-Path: <xuxh@huawei.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 D50913A6C2C for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 01:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.769
X-Spam-Level: 
X-Spam-Status: No, score=-0.769 tagged_above=-999 required=5 tests=[AWL=1.031,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 qLAtijS4TUEc for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 01:37:33 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id D44E43A6BC5 for <rrg@irtf.org>; Fri, 31 Jul 2009 01:37:32 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KNN008TE19RHI@szxga04-in.huawei.com> for rrg@irtf.org; Fri, 31 Jul 2009 16:37:03 +0800 (CST)
Received: from x41208a ([10.111.12.94]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KNN00A4F19RXB@szxga04-in.huawei.com> for rrg@irtf.org; Fri, 31 Jul 2009 16:37:03 +0800 (CST)
Date: Fri, 31 Jul 2009 16:37:02 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <004201ca11b7$e8f30b10$5e0c6f0a@china.huawei.com>
To: rja@extremenetworks.com
Message-id: <004c01ca11ba$14274e70$5e0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: quoted-printable
Thread-index: AcoRt+iHrYYXRMbrTlaM9enzktGB3QAAUJvw
Cc: 'IRTF RRG' <rrg@irtf.org>
Subject: Re: [rrg] Some concerns about ILNP
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, 31 Jul 2009 08:37:33 -0000

Hi,

The following is some comment from Tom (HIPRG co-chair) with regard to =
the flat HIT vs hierarchial HIT. The corresponding discussion thread is =
https://listserv.cybertrust.com/pipermail/hipsec-rg/2008-July/000511.html=


*************************************************************************=
*********
Regarding flat HIT vs. hierarchical HIT, this by itself is IMO a good
topic for discussion for this research group, because a hierarchical HIT
offers some improved resolution properties.

I think it is challenging to squeeze hierarchy/administrative bits into
the existing 128-bit field, because if we are constrained to use an
ORCHID prefix, then to get on the order of 32 bits of hierarchy we will
be down to roughly 70 bits of hash which compromises the ability to
survive the second preimage attack.  To me, this is problematic because
one of the key attributes of HIP is that the security of the binding
update is not easily compromised.

Another problem is to decide who owns and gets to allocate the bits
corresponding to the administrative domains.  Presumably, there would
need to be some security architecture to authenticate ownership of
certain bit patterns in that field, and would introduce some kind of
third party gatekeeper of the bits.=20

However, if the bit constraints were reduced by going to larger HITs
(such as 256 bits) then I think that having some bits to identify the
overlay where the HIT may be resolved becomes more attractive, and if
there are a lot of administrative bits available, then the political
problems of administering them are somewhat reduced since they are not
so scarce.

- Tom
*************************************************************************=
********=20

BR,
Xiaohu

> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> =E5=8F=91=E4=BB=B6=E4=BA=BA: rrg-bounces@irtf.org =
[mailto:rrg-bounces@irtf.org] =E4=BB=A3=E8=A1=A8 Xu Xiaohu
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2009=E5=B9=B47=E6=9C=8831=E6=97=A5 16:22
> =E6=94=B6=E4=BB=B6=E4=BA=BA: rja@extremenetworks.com
> =E6=8A=84=E9=80=81: 'IRTF RRG'
> =E4=B8=BB=E9=A2=98: [rrg] Some concerns about ILNP
>=20
> Hi Ran,
>=20
> If I understand your ILNP correctly, it is much silimar with=20
> the GSE.  If so, I'm wondering whether the issues with the=20
> GSE described in draft-ietf-ipngwg-esd-analysis  have been=20
> successfully solved by the ILNP, e.g., identifier=20
> authentication issue. It seems that  the answers to these=20
> hard issues have not been mentioned in your slides.
>=20
> I noticed the following statement in your slides, do you=20
> believe that 62-bit field is long enough to prevent the=20
> security of the binding of the 62-bit hash value and the=20
> public key from being easily compromised once you use the=20
> HIP/CGA like ideas to deal with the identifier authentication issue?
>=20
> *********************************
> If scope bit is local, have 62 bits that can be anything:
> =E2=80=A3 Cryptographically Generated Identifier (a la CGA proposals)=20
> =E2=80=A3 Hash of a public-key (a la HIP) =E2=80=A3 Pseudo-randomly =
generated=20
> (a la IPv6 Privacy AutoConf)
> **********************************
>=20
> Best regard,
>=20
> Xiaohu
>=20
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>=20


From rja@extremenetworks.com  Fri Jul 31 06:05:34 2009
Return-Path: <rja@extremenetworks.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 16CE13A677C for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 06:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=-0.399,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 mIhH4wM1bwWy for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 06:05:32 -0700 (PDT)
Received: from vms173015pub.verizon.net (vms173015pub.verizon.net [206.46.173.15]) by core3.amsl.com (Postfix) with ESMTP id B77A93A698E for <rrg@irtf.org>; Fri, 31 Jul 2009 06:05:32 -0700 (PDT)
Received: from [10.30.20.71] ([70.104.193.39]) by vms173015.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KNN00D61DOF0T50@vms173015.mailsrvcs.net> for rrg@irtf.org; Fri, 31 Jul 2009 08:05:08 -0500 (CDT)
Message-id: <5EA356F2-DBFA-4D28-B4F1-9144DF358F83@extremenetworks.com>
From: RJ Atkinson <rja@extremenetworks.com>
To: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <004201ca11b7$e8f30b10$5e0c6f0a@china.huawei.com>
Content-type: text/plain; charset=UTF-8; format=flowed; delsp=yes
Content-transfer-encoding: quoted-printable
MIME-version: 1.0 (Apple Message framework v935.3)
Date: Fri, 31 Jul 2009 09:04:59 -0400
References: <004201ca11b7$e8f30b10$5e0c6f0a@china.huawei.com>
X-Mailer: Apple Mail (2.935.3)
Cc: 'IRTF RRG' <rrg@irtf.org>
Subject: Re: [rrg] Some concerns about ILNP
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, 31 Jul 2009 13:05:34 -0000

On  31 Jul 2009, at 04:21, Xu Xiaohu wrote:
> If I understand your ILNP correctly, it is much silimar with the =20
> GSE.  If so, I'm wondering whether the issues with the GSE described =20=

> in draft-ietf-ipngwg-esd-analysis  have been successfully solved by =20=

> the ILNP, e.g., identifier authentication issue. It seems that  the =20=

> answers to these hard issues have not been mentioned in your slides.

1) GSE !=3D ILNP.
    There are a range of differences between the specifications.
    The I-D you cite does NOT apply to ILNP.  Please do not confuse
    the two different protocol specifications.  There are similarities,
    and I believe in full credit for earlier related work, which is
    perhaps a bit odd for the modern IETF, but GSE and ILNP are =20
different
    protocols in a variety of ways.

2) There are no open authentication issues with ILNP.
    Nearly all of the work on IGP authentication was done by me (that's
    why I'm mentioned in the OSPFv2 spec, for example).  I also did the
    original work on AH/ESP, for example see RFC-1825 through RFC-1827.
    So I've done a fair bit of authentication work within IETF standards
    over the past decades.  There aren't ANY open security issues with =20=

ILNP.
    ILNP provides security properties entirely equivalent to what IPv6 =20=

has.

3) Separately, the "security issues" in the draft that you cite are =20
widely
    agreed within the IETF Security community to be the result of an =20
invalid
    analysis.  These errors were pointed out in detail (e.g. by Steve =20=

Bellovin
    and others) about a decade ago to the authors, the IESG, and the =20
IAB.
    The authors' choice not to correct known errors in the security =20
analysis
    is a large part of why that particular I-D was never published as =20=

an RFC.

I find it quite curious that ILNP, which fully addresses security in
an open and documented way, would have these questions arise from you,
yet I haven't seen you ask similar questions of the subset of RRG
proposals that don't address security in any meaningful way at all.
(NB: Clearly there are RRG proposals other than ILNP that do address
security issues, but not all RRG proposals do so.)

> I noticed the following statement in your slides, do you believe =20
> that 62-bit field is long enough to prevent the security of the =20
> binding of the 62-bit hash value and the public key from being =20
> easily compromised once you use the HIP/CGA like ideas to deal with =20=

> the identifier authentication issue?
>
> *********************************
> If scope bit is local, have 62 bits that can be anything:
> =E2=80=A3 Cryptographically Generated Identifier (a la CGA proposals)
> =E2=80=A3 Hash of a public-key (a la HIP)
> =E2=80=A3 Pseudo-randomly generated (a la IPv6 Privacy AutoConf)
> **********************************

I gather you aren't familiar with the CGA specification in RFC-3972.

A CGA uses what amounts to a 62-bit hash, because it sets the scope bit
("u") and multicast bit ("g") of the EUI-64 both to zero, precisely as
ILNP does.  See, for example, paragraphs numbered 6 & 7 on page 7 of
RFC-3972.  The IETF CGA community believes the resulting 62-bits of hash
are sufficient, evidence RFC-3972, so ILNP meets their stated =20
requirements.

Your (separate) quote from Tom Henderson about how HITs are used in HIP,
is very interesting but doesn't apply.  The ILNP slides did not talk =20
about
HITs anywhere.  A full specification of how HIP and ILNP might =20
interact is
well beyond the presentation given, and probably deserves an I-D of =20
its own.
I do think that ILNP and HIP can be combined/used together in a very
synergistic way, but again that is a topic well beyond today's talk.

ILNP is very careful to use the EUI-64 construct in a manner identical
to how existing IPv6 uses the EUI-64 construct, precisely so that =20
various
methods used today for forming IPv6 IIDs could be used going forwards to
form ILNP Node IDs.

Yours,

Ran





From rja@extremenetworks.com  Fri Jul 31 08:50:15 2009
Return-Path: <rja@extremenetworks.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 B0BA23A686D for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 08:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.133
X-Spam-Level: 
X-Spam-Status: No, score=-2.133 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 zc8pXFwzZm3y for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 08:50:15 -0700 (PDT)
Received: from vms173011pub.verizon.net (vms173011pub.verizon.net [206.46.173.11]) by core3.amsl.com (Postfix) with ESMTP id 0047F3A69F9 for <rrg@irtf.org>; Fri, 31 Jul 2009 08:50:14 -0700 (PDT)
Received: from [10.30.20.71] ([70.104.193.39]) by vms173011.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KNN00H1CLBDPL00@vms173011.mailsrvcs.net> for rrg@irtf.org; Fri, 31 Jul 2009 10:50:06 -0500 (CDT)
Message-id: <D616AEAE-26F0-4D33-BD0B-1E1CDAB6CC24@extremenetworks.com>
From: RJ Atkinson <rja@extremenetworks.com>
To: IRTF RRG <rrg@irtf.org>
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: Fri, 31 Jul 2009 11:50:01 -0400
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [rrg] Some concerns about ILNP
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, 31 Jul 2009 15:50:15 -0000

At the suggestion of one of the RRG Chairs, kindly let me reiterate
the explanations on this topic, with specific reference to the slides
presented at RRG in Stockholm today.

Looking specifically at Slide 22:

1) Off-path Attacks
    Ordinary IPv6 without IPsec has broad vulnerability to on-path  
attacks,
    as noted in Slide 22, round bullet 2, triangle sub-bullet 2, first
    dash sub-sub-bullet.

    This means that to provide equivalent security ILNP without IPsec
    only needs to protect against off-path attacks.

    ILNP includes a Nonce to protect traffic from off-path attacks,
    as described in Slide 22, 2nd round bullet (and its subsidiary  
items).

    This means that ILNP without IPsec has the same security properties
    as IPv6 without IPsec.  This is also described in draft-rja-ilnp- 
nonce-*
    and in the other draft-rja-ilnp-* drafts -- in more detail than fits
    on 1 slide in a ~30 minute overview talk.  This is also described
    in the 2nd circular bullet on Slide 22.

2) On-path Attacks
    For ordinary IPv6, the only solution to on-path attacks is to use
    IPsec (most obviously AH, but some forms of ESP could also suffice).

    For ILNP, the existing solution of IPsec continues to work fine, and
    actually works *better* because IPsec for ILNP works even if Locator
    Translation ("NAT") is deployed along the path -- without requiring
    any special UDP encapsulation for "IPsec NAT Traversal".  This is
    described in the first round bullet of Slide 22 (and its subsidiary
    items on that same slide).

Yours,

Ran

