Re: [dc] Requirement for a method to manage mac address in DC

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Thu, 02 February 2012 06:16 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: dc@ietfa.amsl.com
Delivered-To: dc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0B4D21F8A90 for <dc@ietfa.amsl.com>; Wed, 1 Feb 2012 22:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.103
X-Spam-Level:
X-Spam-Status: No, score=0.103 tagged_above=-999 required=5 tests=[AWL=-3.954, BAYES_50=0.001, CN_BODY_46=0.256, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, J_CHICKENPOX_73=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 4+TSp14zF2G3 for <dc@ietfa.amsl.com>; Wed, 1 Feb 2012 22:16:29 -0800 (PST)
Received: from mail21.messagelabs.com (mail21.messagelabs.com [85.158.143.35]) by ietfa.amsl.com (Postfix) with SMTP id 5FEF721F8A8F for <dc@ietf.org>; Wed, 1 Feb 2012 22:16:28 -0800 (PST)
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-4.tower-21.messagelabs.com!1328163384!4159764!2
X-Originating-IP: [147.234.242.234]
X-StarScan-Version: 6.5.5; banners=-,-,-
Received: (qmail 5248 invoked from network); 2 Feb 2012 06:16:25 -0000
Received: from ilptbmg01-out.ecitele.com (HELO ilptbmg01-out.ecitele.com) (147.234.242.234) by server-4.tower-21.messagelabs.com with SMTP; 2 Feb 2012 06:16:25 -0000
X-AuditID: 93eaf2e7-b7f2a6d000000e7d-1f-4f2a3649382d
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01-out.ecitele.com (Symantec Messaging Gateway) with SMTP id DE.E5.03709.9463A2F4; Thu, 2 Feb 2012 09:07:53 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.212]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 2 Feb 2012 08:16:10 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "yu.jinghai@zte.com.cn" <yu.jinghai@zte.com.cn>
Date: Thu, 02 Feb 2012 08:12:29 +0200
Thread-Topic: [dc] Requirement for a method to manage mac address in DC
Thread-Index: AczhRvWTtLFV0ruPR6KD4yZJzLZ7HwAKtwbS
Message-ID: <A3C5DF08D38B6049839A6F553B331C760116342AE4F3@ILPTMAIL02.ecitele.com>
References: <201202020107.q1217pSU061250@mse01.zte.com.cn>
In-Reply-To: <201202020107.q1217pSU061250@mse01.zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/related; boundary="_005_A3C5DF08D38B6049839A6F553B331C760116342AE4F3ILPTMAIL02e_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA6VTb1AUZRz23V3ulot1loODn0yT24Y2UDBcVHOEx/ilkg/MWdCf6Z8tdy93 O9ztXrurw9k0nf9iEkLoZBxuKENRzGxIJkenZkBRK3UKTTR1Qgf/FGCehc2cmUW7t0B86Ftf 3nne3+95nt8z77w/mrQfpvNoUdKwIglB3mKjYhOTvxe98Hihp6TjIONaPzSS5uq5u4NcSizr 7v6DWLan/za1nHgpipYIkiRrgoY5H1a9bn65Iq4SvBGeE31u3slz4aDgxSEsaW5eCIex5OMr bEv0oihxWPLKPlHyu/nKak+Ry/VYWZGTr1j8gLO03FYTEFUOF4UEMciFsKoKfszpFSOh5MM+ rk5WOC2AOeX1GBlIdF2yhH9b3TDxTps1itZoG1E6Deyj8F3LTWTiHDh5sdeyEdloOzuAYPuZ b6zmpR3B6Fc/UAbLwrqh75MRi4Gz2VLo6Wq1GphkF8L4iRhhYIrNh/beNSl+FvsUfPDrZdLk Pw37r0StJn4EOkdO6nyaZthn4PbheqNsZ5+A/uGxlH06Ww5n1m1IWSI9XPL4HsIclQsXrm4l zNDZMHrqhMXEDhi/8neayXfAj429yMhPsk0ImkcTKQHDZsKxjquUKVgAh3ado1pRTnyOb3yu Jj5HY5JkONs8ZDVxIXwY/ZMw8f2wuWl0ul4Aw7HBafwQ7Oy6Tpq4GL7ctXeaz0P887PIHLYT wY13902TnNDZ0fgfpsUwkDxEzoi3tN9KmxX3bWrUneiUOLmhZq72I2TfjRxiMKzVhvwlzmLs FTUcxMVeOdSHzC/88wF0Z2v+IGJpxGcwnzUVeOxpwio1EhpEC2iCdzB/PVjosc+vlX2RgKAG Vigrg1gdRECTfDbT9rJOZ3xCZDVW5JlWUP8DbWTePV7Z+IraitKSkv994XOZa95fquysX9+j eozDWJkZdy9N88B8XKCnzFSwHzfUiUHt3zZBpxtpM/S0AwaHUcNCSBX9Zv84KqNbxm4NIXpT 6uzZnBxCdkqSJZyXyxwxBKwhCKyUZj2N3X97ampqAuXqb5bFxAxWhr53s64T+kBCHzjPZTyP qu/+bCsvihbNE75fv/iuZ/vX9cnEp+/byvuPBuJQ0J4dPUjsX/feK9+ePzX+xfwjb205LfJ4 MmRde99PL3ZeTGQuveCqvt7STCnVry16+NLay/sqd0eO9j/X+2S3+5jaEH6DXVhemii7MYa2 1Z6rerYyeqcma/JmXc6rrc+35r95gOSvna46P1zh2MtTakBwFpKKKvwDzKGVE9YEAAA=
Cc: "dc@ietf.org" <dc@ietf.org>
Subject: Re: [dc] Requirement for a method to manage mac address in DC
X-BeenThere: dc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Data Center Mailing List <dc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dc>, <mailto:dc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dc>
List-Post: <mailto:dc@ietf.org>
List-Help: <mailto:dc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dc>, <mailto:dc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2012 06:16:30 -0000

Dear Mr. Yu (apologies if this is not the proper form of addressing),

Managing MAC addresses allocated to VMs in a DC may be a worthy objective.
But I wonder if it comes under the purview of the IETF.

Could you please elaborate?

Regards,
    Sasha


________________________________
From: dc-bounces@ietf.org [dc-bounces@ietf.org] On Behalf Of yu.jinghai@zte.com.cn [yu.jinghai@zte.com.cn]
Sent: Thursday, February 02, 2012 3:05 AM
To: dc@ietf.org
Subject: [dc] Requirement for a method to manage mac address in DC


Hi All:
   I wonder whether it is necessary to manage mac address in DC.
As you know,VM's mac is randomly generated.
The risk of mac conflict is increasing with  the amount of VMs in DC.
If there is a method to auto manage and allocate mac address,the risk maybe avoid.
That method may facilitate the operator to control network easily and other available benefits.



[cid:_2_0AFEE0640AFEDC7C0005FEE548257998]


Chinese Name:Yu JingHai 喻敬海
English name:Fisher yu
Bearer Network Product Pre-research Department 承载网预研部
[cid:_2_0AFF08740AFF04B80005FEE548257998]       Product Marketing System
产品研发体系
No.50 Ruanjiandadao Yuhuatai District Nanjing,
P.R.China, 210012
Tel:+86-025-88014226
Fax:+86-025-88014226
Email:yu.jinghai@zte.com.cn







This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof.