From melinda.shore@gmail.com Wed Dec 12 19:46:20 2012 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79B0A21F88B7 for ; Wed, 12 Dec 2012 19:46:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9wGL0K1v0mCb for ; Wed, 12 Dec 2012 19:46:19 -0800 (PST) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 81DE421F8890 for ; Wed, 12 Dec 2012 19:46:19 -0800 (PST) Received: by mail-pb0-f44.google.com with SMTP id uo1so1081846pbc.31 for ; Wed, 12 Dec 2012 19:46:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-forwarded-message-id:content-type :content-transfer-encoding; bh=DgavvB8kKJuJzF3x2MnM1ufVIk4JVtUymqWQkxgCqwQ=; b=b3DglBk5oDXi9/coyEvsKOIMnfZjeESBMhAUhlVMQGQ+iqwLJ+NCeopxYrqzmEIm4N b1D0gkj0z4RGWQr97+sHm7L+zlUnyq/Zyit6GMBdT4TJVYwYCTP9bCfDDNkBLkfMhR/2 ODA710bHI6Aovc+GpNaZ9E8yYJj9pMnFO+ahCfwMamJePZmN1rGAKjWUWhhNm6kD8Tp9 oiJ1TaAnv0x2ceOnaVp26U0bpb3NXhZVbi1y/fShXIV0hHUdP2nLb6yfcgyi9Ul42xmX 4nN7M7fN+bruJYgkPxLBBBzT/ZONXzglycpcbSqF66Ze2rdq5yRQ1VWpP3gK6Go9ra7c 9OGw== Received: by 10.68.189.163 with SMTP id gj3mr1189765pbc.110.1355370379242; Wed, 12 Dec 2012 19:46:19 -0800 (PST) Received: from spandex.local (216-67-41-130-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.41.130]) by mx.google.com with ESMTPS id v2sm415403paz.36.2012.12.12.19.46.17 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Dec 2012 19:46:18 -0800 (PST) Message-ID: <50C94F88.9030607@gmail.com> Date: Wed, 12 Dec 2012 18:46:16 -0900 From: Melinda Shore User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: "opsawg@ietf.org" References: <2B9571B6-9383-4D3E-A731-5821E9BBB57B@iab.org> In-Reply-To: <2B9571B6-9383-4D3E-A731-5821E9BBB57B@iab.org> X-Forwarded-Message-Id: <2B9571B6-9383-4D3E-A731-5821E9BBB57B@iab.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: [OPSAWG] Fwd: Feedback Requested: Proposed IEEE RAC OUI Tier Restructuring X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2012 03:46:20 -0000 Likely of interest to the OPS community. -------- Original Message -------- Subject: Feedback Requested: Proposed IEEE RAC OUI Tier Restructuring Date: Wed, 12 Dec 2012 19:37:23 -0800 From: IAB Chair To: ietf-announce@ietf.org The IEEE Registration Authority Committee (RAC) has requested IETF feedback on a proposal for restructuring of the Organizational Unique Identifier (OUI) within the IEEE 802 Medium Access Control (MAC) Address. Information on the proposal is available here: http://www.ietf.org/iesg/ieee/20120725/RAC_Virtualization_July2012.pdf http://ieee802.org/secmail/msg15524.html Comments should be sent to Glenn Parsons > and cc’d to iab@iab.org . From fred@cisco.com Thu Dec 13 00:26:15 2012 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF8B221F8AAE for ; Thu, 13 Dec 2012 00:26:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.539 X-Spam-Level: X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lWrYpzor5Ltq for ; Thu, 13 Dec 2012 00:26:15 -0800 (PST) Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 1F17021F8AAC for ; Thu, 13 Dec 2012 00:26:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2028; q=dns/txt; s=iport; t=1355387175; x=1356596775; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=FIWiF/cTw1LdQXBx1h1O8bQAMJz7WOrAfhPcpGMFZOo=; b=U6Riz+6Rlc/X7DiJhcTmno6MPrt8AX8cNP0VjZSOJQ4O2+KvyU3lHFfz wZK5Q7q79BV5FmO215nDEuUfdPx0pj8WL0ktl+yw86sSfovEF8wAvJgQ0 hnB9tMeL6xFbEJWmaikekWgyJSiyOj07/UKzhV2rm64/Yb8cgopomdIyM 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEFAPeQyVCtJXG+/2dsb2JhbAA7Cr5wFnOCHgEBAQIBAQEBAWsCDgcEAgEIEQECAQILHQcnCxQDBggCBBMIAQuHdwYMvjSMSxGDUWEDlyWPLIJzgiI X-IronPort-AV: E=Sophos;i="4.84,273,1355097600"; d="scan'208";a="152487077" Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-3.cisco.com with ESMTP; 13 Dec 2012 08:26:05 +0000 Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id qBD8Q5nZ031105 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 13 Dec 2012 08:26:05 GMT Received: from xmb-rcd-x09.cisco.com ([169.254.9.13]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Thu, 13 Dec 2012 02:26:04 -0600 From: "Fred Baker (fred)" To: "opsawg@ietf.org" Thread-Topic: [OPSAWG] Feedback Requested: Proposed IEEE RAC OUI Tier Restructuring Thread-Index: AQHN2Qt9V1JCkYu5lUG9lyincDdY3g== Date: Thu, 13 Dec 2012 08:26:04 +0000 Message-ID: <8C48B86A895913448548E6D15DA7553B710AA0@xmb-rcd-x09.cisco.com> References: <2B9571B6-9383-4D3E-A731-5821E9BBB57B@iab.org> <50C94F88.9030607@gmail.com> In-Reply-To: <50C94F88.9030607@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.86.253.224] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [OPSAWG] Feedback Requested: Proposed IEEE RAC OUI Tier Restructuring X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2012 08:26:16 -0000 On Dec 13, 2012, at 7:46 AM, Melinda Shore wrote: > Likely of interest to the OPS community. >=20 > -------- Original Message -------- > Subject: Feedback Requested: Proposed IEEE RAC OUI Tier Restructuring > Date: Wed, 12 Dec 2012 19:37:23 -0800 > From: IAB Chair > To: ietf-announce@ietf.org >=20 > The IEEE Registration Authority Committee (RAC) has requested IETF > feedback on a proposal for restructuring of the Organizational Unique > Identifier (OUI) within the IEEE 802 Medium Access Control (MAC) > Address. Information on the proposal is available here: >=20 > http://www.ietf.org/iesg/ieee/20120725/RAC_Virtualization_July2012.pdf >=20 > http://ieee802.org/secmail/msg15524.html >=20 > Comments should be sent to Glenn Parsons > and cc=92d to iab@iab.org . >=20 > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg My first thought on scanning the deck is that the problem is fundamentally = one of scaling. The reason that we structure addressing and routing as we d= o in IP is to make addressing and routing scale. The Ethernet MAC was desig= ned to identify a NIC on a physical wire, and by extension in a VLAN. It se= ems to me that the VM problem they are having derives primarily from the co= nfusion of a network attachment point on a broadcast LAN with a large scale= routing architecture. As noted, one approach is a DHCP-like assignment of MAC addresses. This doe= sn't do away with physical addresses; the DHCP-like request would come from= the physical address, and the response to it, assigning a virtual address = to a VM.=20 But it frankly seems a lot simpler to use RFC 4941 addresses layered onto t= he physical addresses and as a result a scalable routing infrastructure, ra= ther than trying to do large scale host routing. My $0.02. = From vumip1@gmail.com Sat Dec 15 13:05:06 2012 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B126A21F849A; Sat, 15 Dec 2012 13:05:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lglZkD-LK1Iv; Sat, 15 Dec 2012 13:05:05 -0800 (PST) Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0A20421F8499; Sat, 15 Dec 2012 13:05:04 -0800 (PST) Received: by mail-la0-f44.google.com with SMTP id d3so3681694lah.31 for ; Sat, 15 Dec 2012 13:05:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=AHs7b0m57G6a2C2NiK1iRSJzXTZdWS+wtiiP1c9HM1M=; b=uye8Q+YHuEj5+cV8KK1KikU48U5N0yY92VWLG76yU/1NIrBkIH4lh/WB2mjDRozmEB w3XcwBDGfyDyzn2CuNmvynsRGLWnRcyFCZe6cLCY1IamTbEj3/W81Or+qSsrV1L5yQ+K sSC0V7XPldxgP5V3t0LknqldhcvCBJ14xGneCDlO2O3CNTwlFa4gwrokPTw/QsexH9qR g03l9wvMwL4sj9ABlfWh4vHZmDrrnxpdhUCpXcC+VlGG4vkRnNgsRQl6BgtIUBq+Xzr7 qQb4Qv8EeGJ7ttCUJUNejdtMv6MOnUlj2virWsR0v0xNFYPDH8mlupdzUfXBMekuDD8t LPrw== MIME-Version: 1.0 Received: by 10.152.104.240 with SMTP id gh16mr6500565lab.56.1355605503991; Sat, 15 Dec 2012 13:05:03 -0800 (PST) Received: by 10.114.36.161 with HTTP; Sat, 15 Dec 2012 13:05:03 -0800 (PST) Date: Sat, 15 Dec 2012 16:05:03 -0500 Message-ID: From: "B.Khasnabish@ieee.org" To: nvo3@ietf.org, opsawg@ietf.org Content-Type: multipart/alternative; boundary=f46d04088e11855efd04d0ea8029 Subject: [OPSAWG] Fwd: I-D Action: draft-jin-nvo3-virb-centralized-00.txt X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Dec 2012 21:05:06 -0000 --f46d04088e11855efd04d0ea8029 Content-Type: text/plain; charset=ISO-8859-1 Hi, FYI, and comments/suggestions. Thanks. I-D Action: draft-jin-nvo3-virb-centralized-00.txt ------------------------------ - *To*: i-d-announce at ietf.org - *Subject*: I-D Action: draft-jin-nvo3-virb-centralized-00.txt - *From*: internet-drafts at ietf.org - *Date*: Thu, 13 Dec 2012 18:22:16 -0800 - *Delivered-to*: i-d-announce at ietfa.amsl.com - *List-archive*: - *List-help*: > - *List-id*: Internet Draft Announcements only - *List-post*: > - *List-subscribe*: , > - *List-unsubscribe*: , > - *Reply-to*: internet-drafts at ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Virtualized Integrated Routing & Bridging with centralized control plane Author(s) : Lizhong Jin Bhumip Khasnabish Filename : draft-jin-nvo3-virb-centralized-00.txt Pages : 10 Date : 2012-12-13 Abstract: The network in datacenter is required to provide a tenant network, which should be virtualized, and be able to provide L2 switching or L3 routing capability. A combined L2&L3 solution could provide great scalability for both Layer2 and Layer3 switching. In this document, we propose to apply centralized server to be the control plane of the combined L2&L3 solution, to provide better scalability for the control plane. The combined L2&L3 solution in this draft is named Virtualized Integrated Routing&Bridging (shorted as VIRB). The IETF datatracker status page for this draft is:https://datatracker.ietf.org/doc/draft-jin-nvo3-virb-centralized There's also a htmlized version available at:http://tools.ietf.org/html/draft-jin-nvo3-virb-centralized-00 Internet-Drafts are also available by anonymous FTP at:ftp://ftp.ietf.org/internet-drafts/ --f46d04088e11855efd04d0ea8029 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hi,

FYI, and comments/suggestions. Thanks.=

I-D Action: draft-jin-nvo3-virb-centra= lized-00.txt=20


=A0
A New Internet-Draft is available from=
 the on-line Internet-Drafts directories.


	Title           : Virtualized Integrated Routing & Bridging with centr=
alized control plane
	Author(s)       : Lizhong Jin
                          Bhumip Khasnabish
	Filename        : draft-jin-nvo3-virb-centralized-00.txt
	Pages           : 10
	Date            : 2012-12-13

Abstract:
   The network in datacenter is required to provide a tenant network,
   which should be virtualized, and be able to provide L2 switching or
   L3 routing capability.  A combined L2&L3 solution could provide grea=
t
   scalability for both Layer2 and Layer3 switching.  In this document,
   we propose to apply centralized server to be the control plane of the
   combined L2&L3 solution, to provide better scalability for the
   control plane.  The combined L2&L3 solution in this draft is named
   Virtualized Integrated Routing&Bridging (shorted as VIRB).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-jin-nvo3-virb-cen=
tralized

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-jin-nvo3-virb-centralized-=
00


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.=
ietf.org/internet-drafts/

=A0 --f46d04088e11855efd04d0ea8029--