IETF Logo Mail Archive

Re: [Rtg-dt-encap-considerations] overlay encapsulation group

"Fred Baker (fred)" <fred@cisco.com> Fri, 24 April 2015 03:43 UTC

Return-Path: <fred@cisco.com>
X-Original-To: rtg-dt-encap-considerations@ietfa.amsl.com
Delivered-To: rtg-dt-encap-considerations@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E03E21B2BC9 for <rtg-dt-encap-considerations@ietfa.amsl.com>; Thu, 23 Apr 2015 20:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level:
X-Spam-Status: No, score=-114.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, USER_IN_WHITELIST=-100] 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 uZ8H7htUNWM0 for <rtg-dt-encap-considerations@ietfa.amsl.com>; Thu, 23 Apr 2015 20:43:16 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7DBA1B2BD5 for <Rtg-dt-encap-considerations@ietf.org>; Thu, 23 Apr 2015 20:43:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2118; q=dns/txt; s=iport; t=1429846982; x=1431056582; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=czGtrqxarV7O50v3DUdQcBvnB+/VWNSwawN24B1A0bw=; b=UhTi/tmLqmeiHlXWbtZap0UgraDVW0+OI/gf+I6gKxJXsdZ7T50j54ll FSTMlxqru0w/rI7+32OrQ/N7GrXeHyRO04Sc/Z1JsQkr6N13qTGiC0mUe 4be9nLC+G8Gywilv7NBQ1oFR5Kr4o/boU/6aTrb9a8tcy292Yl9Xb+kUR 4=;
X-Files: signature.asc : 487
X-IronPort-AV: E=Sophos;i="5.11,636,1422921600"; d="asc'?scan'208";a="414337798"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-7.cisco.com with ESMTP; 24 Apr 2015 03:43:01 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t3O3h1TN024011 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Apr 2015 03:43:01 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.172]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0195.001; Thu, 23 Apr 2015 22:43:01 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Tom Herbert <tom@herbertland.com>
Thread-Topic: [Rtg-dt-encap-considerations] overlay encapsulation group
Thread-Index: AQHQfhb3LdlB0LShckKzJvuC1/xh3J1b2SYA
Date: Fri, 24 Apr 2015 03:43:00 +0000
Message-ID: <C3B06F41-562D-4EA3-94D6-D1694175F41E@cisco.com>
References: <CALx6S34H3rebaH3XbQD839Cdj7EB3L3T7iWErEmxETO2Ly+L6Q@mail.gmail.com>
In-Reply-To: <CALx6S34H3rebaH3XbQD839Cdj7EB3L3T7iWErEmxETO2Ly+L6Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.121]
Content-Type: multipart/signed; boundary="Apple-Mail=_F77B031B-B7B6-4BAD-831D-CB7A9CCAE6AC"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dt-encap-considerations/JCh6NWIuw0EkLzRfU7WZnpeie00>
Cc: "Rtg-dt-encap-considerations@ietf.org" <Rtg-dt-encap-considerations@ietf.org>, "fred.baker@cisco.com" <fred.baker@cisco.com>
Subject: Re: [Rtg-dt-encap-considerations] overlay encapsulation group
X-BeenThere: rtg-dt-encap-considerations@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Design Team on Encapsulation Considerations discussion list <rtg-dt-encap-considerations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/>
List-Post: <mailto:rtg-dt-encap-considerations@ietf.org>
List-Help: <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 03:43:18 -0000

> On Apr 23, 2015, at 3:43 PM, Tom Herbert <tom@herbertland.com> wrote:
> 
> Hi Fred,
> 
> Sorry this is a little late, but I wanted to respond to this thread.
> Please look at Identifier Locator Addressing
> (https://tools.ietf.org/html/draft-herbert-nvo3-ila-00). This is along
> the lines of using IPv6 without encapsulation for network
> virtualization (similar to your idea to use flow label in IPv6 for
> tenant ID). In ILA we encode tenant IDs the their address into IPv6
> use Identifier/Locator split (borrowing concept from ILNP).
> 
> Thanks,
> Tom

Let me be a little more clear. I ripped of the email a bit ago and then realized you guys already had the file.

I’m no longer thinking about the flow label. I have a colleague that is interested in a tripartite label, as it’s part of his Phd. However, the rest of use are putting into bits 104..127 of the address - the last 24 bits of the IID. I’m not stuck on “24”, but it seems like something the operator won’t need to change quickly. That is at the top of appendix B, and section B.5.

v2.23.0 | Report a Bug | By Email