Re: [v6ops] I-D: draft-rafiee-v6ops-iid-lifetime-00.txt

"Fred Baker (fred)" <fred@cisco.com> Wed, 23 October 2013 05:52 UTC

Return-Path: <fred@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C336011E82F1 for <v6ops@ietfa.amsl.com>; Tue, 22 Oct 2013 22:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.299
X-Spam-Level:
X-Spam-Status: No, score=-110.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ss4ugGn2D9ns for <v6ops@ietfa.amsl.com>; Tue, 22 Oct 2013 22:52:55 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id A289511E82ED for <v6ops@ietf.org>; Tue, 22 Oct 2013 22:52:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4001; q=dns/txt; s=iport; t=1382507571; x=1383717171; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Bg2fJj9aetTlb3UgYBjfT/IES+LRNfg/KuO0zvpW/5w=; b=X3vZFtFb3JkZzkDSIKmj5n1s/GR7FtiQ2Y2L6gkD0lqtBMTAGzsA9vQo BjGYNysK/Yrrqwmhk3XQdYoGyy9dEl/AXGuWjTm4nzFMd8+AJfZKpuhBT N8uFKLj7e2LldGa208hOp4LlMu3nApDhaYM79stMJ9o6XmAHBMNqsC4wG s=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAN5iZ1KtJXG//2dsb2JhbABZgwc4VL5SgS0WdIIlAQEBAwEBAQFrCwULAgEIDgQQJCcLFw4CBAENBQgBBYdyBg26Yo8dMQeDH4EKA5AtgTCHW5BYgySCKg
X-IronPort-AV: E=Sophos; i="4.93,553,1378857600"; d="asc'?scan'208"; a="275468122"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-8.cisco.com with ESMTP; 23 Oct 2013 05:52:51 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9N5qpkP014417 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 23 Oct 2013 05:52:51 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Wed, 23 Oct 2013 00:52:50 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Hosnieh Rafiee <ietf@rozanak.com>, Erik Nordmark <nordmark@sonic.net>
Thread-Topic: [v6ops] I-D: draft-rafiee-v6ops-iid-lifetime-00.txt
Thread-Index: AQHOz7Qb7tczfBfL102ng3enJ0ivMw==
Date: Wed, 23 Oct 2013 05:52:50 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA74263@xmb-rcd-x09.cisco.com>
References: <021e01ceceb4$88158570$98409050$@rozanak.com>
In-Reply-To: <021e01ceceb4$88158570$98409050$@rozanak.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.212.192]
Content-Type: multipart/signed; boundary="Apple-Mail=_AF99458F-E073-4762-A391-3D5A1401314E"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] I-D: draft-rafiee-v6ops-iid-lifetime-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2013 05:52:59 -0000

</chair>

This, along with RFC 4941's observation that there may be utility in an IID that is not tied to hardware identifiers, would appear consistent with the thought and recommendations of 

https://tools.ietf.org/html/rfc1498
1498 On the Naming and Binding of Network Destinations. J. Saltzer.
     August 1993. (Format: TXT=24698 bytes) (Status: INFORMATIONAL)

and the definition of an Endpoint ID in 

https://tools.ietf.org/html/rfc1992
1992 The Nimrod Routing Architecture. I. Castineyra, N. Chiappa, M.
     Steenstrup. August 1996. (Format: TXT=59848 bytes) (Status:
     INFORMATIONAL)

The latter is the origin of the question of a locator/id split; a locator identifies the location of a network point of attachment, and an identifier in essence identifies what we might call a "socket". Imagine - although I can't say I know *why* someone would want to do this <sarcasm> - one wanted to move an application from one physical or virtual machine to another. If the identifier could move with the application, that would simplify such motion.

Note that the NIMROD architecture and Saltzer's document are not fundamentally about security. They are about scalable management of applications interconnected by a network and routing in that network.

On Oct 22, 2013, at 3:23 AM, Hosnieh Rafiee <ietf@rozanak.com> wrote:

> We submitted a new draft which compares the current mechanisms to maintain the lifetime of IIDs and then introduces a framework to enable applications maintaining their privacy by making it difficult to correlate a user's activities by using different IIDs for different applications, without negatively impacting the robustness of the applications.
> 
> We're looking forward to receiving your comments.
> 
> 
> Filename:	 draft-rafiee-v6ops-iid-lifetime
> Revision:	 00
> Title:		 Interface ID lifetime Algorithms
> Creation date:	 2013-10-21
> Group:		 Individual Submission
> Number of pages: 11
> URL:             http://www.ietf.org/internet-drafts/draft-rafiee-v6ops-iid-lifetime-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-rafiee-v6ops-iid-lifetime
> Htmlized:        http://tools.ietf.org/html/draft-rafiee-v6ops-iid-lifetime-00
> 
> 
> Abstract:
>   This document introduces a framework, i.e., an application layer
>   based lifetime [applicationiid] to enable applications maintaining
>   their users' privacy as well as controlling the number of Interface
>   IDs (IIDs) per network adapter. It will also explain different
>   approaches that can be used for maintaining the lifetime of an IID.
>   We also compare this framework to the other available mechanisms.
>   This document also explains when to remove deprecated IP addresses
>   from the a network interface.
> 
> 
> -----------smile----------
> Hosnieh
> … success is a journey, not a destination….
> You cannot change your destination overnight, but you can change your direction ... Focus on the journey
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

If at first the idea is not absurd, then there is no hope for it.  
Albert Einstein