Re: [v6ops] new draft: draft-colitti-v6ops-host-addr-availability

"Hemant Singh (shemant)" <> Tue, 07 July 2015 21:12 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id CAC751ACDF2 for <>; Tue, 7 Jul 2015 14:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UwMO1CR820lV for <>; Tue, 7 Jul 2015 14:12:28 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2E0A11ACDEF for <>; Tue, 7 Jul 2015 14:12:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1676; q=dns/txt; s=iport; t=1436303548; x=1437513148; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=y54QFY/rod5wayUz+msYfK44Wn57FwvzqX8CG/pXpq8=; b=bgZCjYBBycCif1foLtCNEiPyPQ8DijBl3UGxXe60ZiMRJLvC5uBr/98e VFg9125urP8C+6Tg+XNfQ/LyYvDUwr4vPHVYt3ZYNt8vgvi4pCMOdcNvo Qug5erT2vHeMgQy6kHT3ypcUgtbxfXUYsVTwhoiBauME1j+UTGw/+dvju s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.15,426,1432598400"; d="scan'208";a="9695747"
Received: from ([]) by with ESMTP; 07 Jul 2015 21:12:27 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t67LCRIr010080 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 7 Jul 2015 21:12:27 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Tue, 7 Jul 2015 16:12:26 -0500
From: "Hemant Singh (shemant)" <>
To: Brian E Carpenter <>, "Fred Baker (fred)" <>, Andrew Yourtchenko <>
Thread-Topic: [v6ops] new draft: draft-colitti-v6ops-host-addr-availability
Thread-Index: AQHQt+GUs8uYiRy2iUusolpZfA8qWp3PTI+AgAAnzoCAALsP8IAAnweA//+v2rA=
Date: Tue, 7 Jul 2015 21:12:26 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>, "" <>
Subject: Re: [v6ops] new draft: draft-colitti-v6ops-host-addr-availability
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 07 Jul 2015 21:12:30 -0000

-----Original Message-----
From: Brian E Carpenter [] 
Sent: Tuesday, July 07, 2015 4:41 PM
To: Hemant Singh (shemant); Fred Baker (fred); Andrew Yourtchenko
Subject: Re: [v6ops] new draft: draft-colitti-v6ops-host-addr-availability

>It does? I don't see anything in 4862 that prevents a host from generating N separate IIDs and performing SLAAC N times for the same prefix. Now we are getting rid of Modified >EUI-64 as the default IID, that becomes an obvious thing to do.

RFC4862 has no guidance for what specific IID to use.  However, RFC4862 does reference RFC4291 in the context of IID and RFC4291 does include the Modified EUI-42 IID format which uses the host's mac-address.   Thanks, Fred, for replying as well.  

I am only discussing RFC4862 with its Modified EUI-64 format for generating a global IPv6 address.  The reason is because section 7 of the colitti document, in the first bullet, speaks of RFC4862.  

Sure, if one deprecates the Modified EUI-64 format and uses, say, privacy extensions, then one prefix can be used by the host to generate multiple IPv6 globals.