Re: "The IETF has difficulty solving complex problems" or alternatively Why IMS is a big fat ugly incomprehensiable protocol

Pekka Nikander <> Thu, 15 September 2005 07:57 UTC

Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1EFocz-000157-4w; Thu, 15 Sep 2005 03:57:53 -0400
Received: from ([] by with esmtp (Exim 4.32) id 1EFocx-00014v-5F for; Thu, 15 Sep 2005 03:57:51 -0400
Received: from (ietf-mx []) by (8.9.1a/8.9.1a) with ESMTP id DAA25144 for <>; Thu, 15 Sep 2005 03:57:48 -0400 (EDT)
Received: from ([]) by with esmtp (Exim 4.43) id 1EFohg-0008O7-T1 for; Thu, 15 Sep 2005 04:02:46 -0400
Received: from [] (localhost []) by (Postfix) with ESMTP id 50E1A212C46; Thu, 15 Sep 2005 10:57:38 +0300 (EEST)
In-Reply-To: <>
References: <20050804050502.GB6084@sbrim-wxp01> <> <> <> <151701c5b570$052a25a0$> <C0DE65F6343F8BD987425795@B50854F0A9192E8EC6CDA126> <> <> <> <>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <>
Content-Transfer-Encoding: quoted-printable
From: Pekka Nikander <>
Date: Thu, 15 Sep 2005 09:57:37 +0200
To: Iljitsch van Beijnum <>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <>
Subject: Re: "The IETF has difficulty solving complex problems" or alternatively Why IMS is a big fat ugly incomprehensiable protocol
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

>> So, as I state in my little web page, I think we really should  
>> work hard to create a new waist for the architecture.   I, of  
>> course, have my own theory where the new waist should be and how  
>> it should be implemented,
> Well, don't be shy: where can we absorb these insights?

Since you ask:

Unfortunately I don't have any concise summary of my "theory", but  
wading through my academic papers (available through my home page)  
should give a fairly good view.  I would focus on the following three  
papers, roughly in this order:

1. Pekka Nikander, Jukka Ylitalo, and Jorma Wall, "Integrating  
Security, Mobility, and Multi-Homing in a HIP Way," in Proceedings of  
Network and Distributed Systems Security Symposium (NDSS'03),  
February 6-7, 2003, San Diego, CA, pp. 87-99, Internet Society,  
February, 2003.

2. Jukka Ylitalo, Pekka Nikander, "A new Name Space for End-Points:  
Implementing secure Mobility and Multi-homing across the two versions  
of IP," in Proceedings of the Fifth European Wireless Conference,  
Mobile and Wireless Systems beyond 3G (EW2004), pp. 435-441,  
Barcelona, Spain, February 24-27, 2004.

3. Pekka Nikander, Jari Arkko, and Börje Ohlman, Host Identity  
Indirection Infrastructure (Hi3)," in Proceedings of The Second  
Swedish National Computer Networking Workshop 2004 (SNCNW2004),  
Karlstad University, Karlstad, Sweden, Nov 23-24, 2004.

Especially the last one is pretty dense; it takes time to understand  
all that we are trying to say there.

All three (and more) are available at

If you prefer slideware, see our IETF 62 plenary slides:

But, as I wrote, I am trying to take distance from these and trying  
to understand alternative approaches, like "virtualising IP" or  
"domain-based internetworking" that some people are thinking about.   
It is now mostly other people that are continuing the HIP-based work,  
for example, at the CEC funded Ambient Networks project and at the  
IRTF HIP Research Group.

--Pekka Nikander

Ietf mailing list