Re: [rrg] London

heinerhummel@aol.com Fri, 17 January 2014 08:06 UTC

Return-Path: <heinerhummel@aol.com>
X-Original-To: rrg@ietfa.amsl.com
Delivered-To: rrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBBC31ADFB5 for <rrg@ietfa.amsl.com>; Fri, 17 Jan 2014 00:06:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.263
X-Spam-Level:
X-Spam-Status: No, score=0.263 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p_WT8kmdnIuy for <rrg@ietfa.amsl.com>; Fri, 17 Jan 2014 00:06:06 -0800 (PST)
Received: from omr-d03.mx.aol.com (omr-d03.mx.aol.com [205.188.109.200]) by ietfa.amsl.com (Postfix) with ESMTP id 951FD1ADFAA for <rrg@irtf.org>; Fri, 17 Jan 2014 00:06:06 -0800 (PST)
Received: from mtaomg-mbe01.mx.aol.com (mtaomg-mbe01.mx.aol.com [172.26.254.175]) by omr-d03.mx.aol.com (Outbound Mail Relay) with ESMTP id 1AB6C701BD6CF; Fri, 17 Jan 2014 03:05:54 -0500 (EST)
Received: from core-dqa005a.r1000.mail.aol.com (core-dqa005.r1000.mail.aol.com [172.29.211.209]) by mtaomg-mbe01.mx.aol.com (OMAG/Core Interface) with ESMTP id A30B73800008C; Fri, 17 Jan 2014 03:05:53 -0500 (EST)
References: <E371C7FE-F5F1-459A-93E6-6C0A5C008630@tony.li> <69AE8596-8E77-4CC9-B7DA-5F0105D8E6E9@aol.com> <5E3D4B6F-C98C-46D3-AD73-B763C4E0CEB9@cs.ucla.edu>
To: lixia@cs.ucla.edu
In-Reply-To: <5E3D4B6F-C98C-46D3-AD73-B763C4E0CEB9@cs.ucla.edu>
X-MB-Message-Source: WebUI
Received: from 178.26.195.50 by webmail-d263.sysops.aol.com (205.188.16.103) with HTTP (WebMailUI); Fri, 17 Jan 2014 03:05:53 -0500
MIME-Version: 1.0
From: heinerhummel@aol.com
X-MB-Message-Type: User
Content-Type: multipart/alternative; boundary="--------MB_8D0E17213BD5DA5_1ABC_18317_webmail-d263.sysops.aol.com"
X-Mailer: AOL Webmail 38252-STANDARD
Message-Id: <8D0E17213B176C5-1ABC-602E@webmail-d263.sysops.aol.com>
X-Originating-IP: [178.26.195.50]
Date: Fri, 17 Jan 2014 03:05:53 -0500 (EST)
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1389945954; bh=MDXKxS1PT1k0ralsrOlMrgxGHxzI7Tq3VoSt/rMqB7k=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=UiPpTaU+odXYAm80j/5IPETO6B3ZZFjg24KDC5RGQs3U1YGxktZr+pyufZNNhBjlc TCPo7ZfSIoRX6VMxPVMPAAN3gnkMZ7q+gZNlsIn5sduuZY0hgI5sWzr1pTSunhrx9y Ywuh4dGhnGB1V/+YUZlRLqG9rjuB0XyuUesnFtXk=
x-aol-sid: 3039ac1afeaf52d8e4610d2a
Cc: rrg@irtf.org
Subject: Re: [rrg] London
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/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, 17 Jan 2014 08:06:13 -0000

Lixia,


It was at the London 2002 IETF meeting when the request was raised to develop a new routing architecture. Concurrently it was added " there is no reason to rush, we will have a 10 years time frame for doing it". Well, meanwhile 12 years have passed and all we 've got is LISP which boast to enable 52x10^27 EIDs per person but doesn't enhance the IPv4 address space not by one single address. A concept which  employs (bottle neck) servers which are vulnerable wrt. DoSA and perhaps even due to normal overload of queries and which impose a threat to their not-owning clients which dependent on them.  


IPv6 was certainly not meant by that request in London because it existed already at that time. And RFC 4984 §3 even warns that it would multifold the number of prefixes. And integrating AS-numbers seems not good wrt prefix building either. Also: 16 octets are provided and yet a E164 mobile user phone number is still needed outside of these 16 octets:-(.


In the past I have  asked many times to discuss the existing paradigms, and to question them ! Research is questioning the obvious! The too obvious! Like: Why are there two different routing concepts wrt intra versus inter-domain routing? I really would like to know why is Dijkstra bad for inter-domain ? Why isn't Distance Vector used in intra-domain routing?
Why is there no Multicast-FIB ? Is it because it can't hardly be like the existing Unicast-FIB on the one hand side while on the other side a FIB must not be any different than the existing one?
Lixia, why would you not necessarily agree with my technical specific of having a Multicast-FIB ?
And also: What is the value of depending on prefix building in unicast forwarding? After all, it doesn't work wrt Multicast nor to Anycast (nor see above with AS#s)




Another very fundamental point is what we expect a network layer to be/to look like/to handle/ to solve:


It is not only me, it is the entire ITU-T which thinks that the network layer deals with the WHERE. With E164 routing and addressing are or at least have been identical: the next-hop trunk was selected electro-mechanically due to the next dialed digit. A routing protocol wasn't even needed. 




It is worth to have a look to the past. I am convinced, If there were not MPOA (but Cisco's Peer model instead) MPLS wouldn't have been developed. Without MPLS, being a strong push of IntServ, there wouldn't have been the counter movement DiffServ whose mantra is "do what Traffic Engineering wanted to contribute to SVCs/LSPs without knowing the network nor its current traffic load external to the waiting queue of incoming packets at any router And - imho - this mantra prevents any reasonable handling of genuine network layer objectives: like handling traffic congestions (avoiding them if possible in the first place dissolving them where needed). A network layer technology which has no idea, how to direct flows such that some would bypass the congested area to the left while some others to the right is not future prone. It is stupid and unknowledgeable!!!


Heiner






-----Ursprüngliche Mitteilung----- 
Von: Lixia Zhang <lixia@cs.ucla.edu>;
An: Heiner Hummel <heinerhummel@aol.com>;
Cc: Tony Li <tony.li@tony.li>;; rrg <rrg@irtf.org>;
Verschickt: So, 12 Jan 2014 7:12 pm
Betreff: Re: [rrg] London


I may not necessarily agree with the technical specifics of Heiner's msg, but I 
do think the msg made a good point: to provide useful input into RRG London 
agenda, we need to first have a clear goal(s) for that meeting.
Just volunteering a talk for whatever latest results multiple individuals have 
achieved may or may not help RRG to move forward.

So what do we as a group want to achieve?
Reactivating RRG would be the results of identifying that goal (the group would 
march towards that clearly articulated goal).

Or maybe the goal of London meeting could be to identify/clarify the goal?

(in that case, Heiner's msg did make one position statement as an input, for the 
group to consider)

Lixia
PS: I must admit that I have NOT had time to go thru the 40 or so RRG msgs since 
Vancouver IETF, ignore my comments if the goal had been clarified earlier (other 
than "reactivating RRG").

On Jan 11, 2014, at 12:24 PM, Heiner Hummel <heinerhummel@aol.com>; wrote:

> Tony,
> Given that the IESG doesn't care about IPv4 anymore, what kind of papers are 
you looking for? IPv6 papers ? IPv7 papers, based on WHAT ?
> 
> For anyone it would be easier to outline a routing architecture while 16 
octets are available instead of 4. But IPv6 is grounded from the start. Not even 
the fact that  IPv4 runs out of addresses will help to unleash IPv6.
> Combined with NAT,  IPv4 won't effectively have a deletion problem. Not for 
the next thousand years.
> Technologically NAT is a sin  fall, it hampers internet services  enormously. 
But this is true with IPv6 as well. So what!
> 
> Backward compatibility and incremental deployability should be the two MUSTs 
for any architecture, no matter who proposes it. IPv6 isn't backward compatible 
due to the dual stack issue - right? or is there any way around?
> What is expected from any new architecture? To be backward compatible with 
IPv4 ( I would think so), to be backward compatible with IPv6 (I wouldn't think 
so)? So what is expected?
> 
> And of course what do you expect to be solved, respectively to be enabled at 
least ?
> ----
> Another Proposal:  This group should come up with ideas about what a 
networking layer should do/support/enable WITHOUT being restricted by any 
existing technical solution.
> Two examples: 1): Prefix building per se is not a service. It is only a subdue 
instrument to cope with problems of a minor design.
> 2): State-less multicast would enable an enormous progress ( Imagine 
TV-broadcast to billions of spectators). But this is disabled due to the crazy 
belief that there is only one way  a FIB can be designed (namely as the existing 
FIB looks like)
> and because a Multicast-FIB cannot reasonable be cast like the existing 
Unicast-FIB there cannot/must not be state-less multicast. Period.
> 
> Heiner
> 
> Am 09.01.2014 um 10:12 schrieb Tony Li <tony.li@tony.li>;:
> 
>> 
>> Hi all,
>> 
>> We are still looking for excellent papers for our workshop in London.  We 
really need your help in collecting these.  If you know of interesting research, 
could you please contact the authors and ask if they would be willing to present 
in London?  It's coming very soon…
>> 
>> Thanks,
>> Tony
>> 
>> _______________________________________________
>> rrg mailing list
>> rrg@irtf.org
>> http://www.irtf.org/mailman/listinfo/rrg
> 
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg