Re: [rrg] RRG to hibernation Tue, 04 December 2012 09:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0327521F8720 for <>; Tue, 4 Dec 2012 01:52:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1GwRTW2ew7sf for <>; Tue, 4 Dec 2012 01:52:49 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id EEFFF21F8717 for <>; Tue, 4 Dec 2012 01:52:48 -0800 (PST)
Received: from ( []) by (Outbound Mail Relay) with ESMTP id 6C1C738000372 for <>; Tue, 4 Dec 2012 04:52:48 -0500 (EST)
Received: from ( []) by (OMAG/Core Interface) with ESMTP id 220E7E000087 for <>; Tue, 4 Dec 2012 04:52:48 -0500 (EST)
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
X-MB-Message-Source: WebUI
MIME-Version: 1.0
X-MB-Message-Type: User
Content-Type: multipart/alternative; boundary=""
X-Mailer: AOL Webmail 37208-STANDARD
Received: from by ( with HTTP (WebMailUI); Tue, 04 Dec 2012 04:52:47 -0500
Message-Id: <>
X-Originating-IP: []
Date: Tue, 4 Dec 2012 04:52:48 -0500 (EST)
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20121107; t=1354614768; bh=DJ/IvsmUxRaI72DiyC7aPDxstwRKedUx9NMQ0ZOQfYA=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=W9thl0yIx2q7mq4i/9YEK5PfGcJUEVBv9gdRXJAc8aTg2zih8KpLxXIfYvnnibpR/ Eqn4CtRP2r8qptEnbr7Xsz9zuHjJRssn/aNkZNeIFE7ceFeCVZXhd5DZrWowaQDTRy uw2gbQAOtoJ3idcppE4A38dQNGDTP4EZxtZE+xg4=
X-AOL-SCOLL-SCORE: 0:2:455968224:93952408
x-aol-sid: 3039ac1d33c950bdc7f02607
Subject: Re: [rrg] RRG to hibernation
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF Routing Research Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Dec 2012 09:52:50 -0000

The recent storm in a glass of water has calmed down again. Silence has returned.
I think the outcome of the RRG doesn't satisfy most of the participants (besides few exceptions) and should not thrill the IAB at all.Precious time by the years has been wasted. The problem due to the IPv4 address depletion turns out to be much worse than the scalability problem. 
LISP appears to be a pull-variant replacing the legacy push-model. Loc-id-split is something else: E.g. my TARA model which  doesn't do EID-to-RLOC mapping nor  disseminate such info (neither by pull nor by push) to make sure that the packet is sent to the right ETR. It simple complies with Elvis Presley's "Return to sender, address unknown, noch such number, no such phone..." if it were sent to the wrong/ not anymore up-to-date  ETR -  
or would append a broadcast search inside the surrounding geopatch.
There is more missing: how to use TTL, peeping into the inner header ?:-( How to form and use a Multicast-Locator, or an Anycast-Locator ? How would it  handle a roaming Multicast-sender? 
Above all however there is no working strategy to deal with the situation where ipv4 is not globally unique anymore. Neither LISP nor ILNP have so far    presented a solution. And the RRG has never discussed the theoretical basics !!! In principle the 4 octet sized ipv4 address must be extended.My proposal: by two additional leading octets - in mind. This doesn't mean that they have to be placed directly in front of the 4 octets.  Particularly, the value = 0000H might be equivalent to "the two octets  aren't placed anywhere at all". But other values might be placed somewhere  (e.g. being part of the locator). 
In the (current) TARA concept it would be the geopatch number in the range 1:64800, resp. the number 64801 for well-known Anycast, and 64802 for well-known Multicast.
There are problems by the numbers. Enough for just the networking layer (TCP should take care by itself when ipv4 looses its globally uniqueness )!
I am not a friend of ipv6 either. Just to share my worries: Imagine a multicast instance where sender and receivers are roaming, where sender and receivers are a mix of ipv4 and ipv6 users, in a world where ipv4 has lost globally uniqueness. Brrrrh.
Hibernation is not the right answer.

rrg mailing list