IETF Logo Mail Archive

Re: Routing Directorate Review for "Use of BGP for routing in large-scale data centers" (adding RTG WG)

"Acee Lindem (acee)" <acee@cisco.com> Sat, 30 April 2016 16:56 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B41F012D17E; Sat, 30 Apr 2016 09:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level:
X-Spam-Status: No, score=-15.517 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 cyhlAEWzNNJl; Sat, 30 Apr 2016 09:56:57 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25A6E12D177; Sat, 30 Apr 2016 09:56:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=884; q=dns/txt; s=iport; t=1462035417; x=1463245017; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=MfmK58RTv/0laMxoD+7n5iuoYyUs8rBuzUyBTnvpDf0=; b=L3xc2vE9h7WXDsp+tImUZvQpXxXTwt53zflEY+XTb4PiqN8QXrKKM/1q vhuw0Om4j4aU+PjCgWIKM7B18ZPTAy5+qkH3xafGNJVzoxZs5YSXR9Osq n53CEwjoTh1/b39ejtPkja+EWstir4eKtsCO8cwh1wl4TYcZKetTUBrHO w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C5BQAk4yRX/4sNJK1egziBUAa5eIF2hhACHIEFOhIBAQEBAQEBZSeEQgEBBCMRRRACAQgOCgICHwcCAgIwFRACBAENBYgqsnqQXgEBAQEBAQEBAQEBAQEBAQEBAQEBARV8iXGEPReCaYJWAQSYFAGOF4FnhE2IXY8wAScBOoI2gTVshn5/AQEB
X-IronPort-AV: E=Sophos;i="5.24,557,1454976000"; d="scan'208";a="267282189"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Apr 2016 16:56:56 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u3UGut5d031311 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 30 Apr 2016 16:56:56 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sat, 30 Apr 2016 12:56:55 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1104.009; Sat, 30 Apr 2016 12:56:55 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Jon Mitchell <jrmitche@puck.nether.net>, Alia Atlas <akatlas@gmail.com>
Subject: Re: Routing Directorate Review for "Use of BGP for routing in large-scale data centers" (adding RTG WG)
Thread-Topic: Routing Directorate Review for "Use of BGP for routing in large-scale data centers" (adding RTG WG)
Thread-Index: AQHRnxYlQYfeCPyXgkGAG4vr+m6GrZ+ekbQBgAQyt4A=
Date: Sat, 30 Apr 2016 16:56:55 +0000
Message-ID: <D34A5BAD.5ED3E%acee@cisco.com>
References: <D343C90F.5C211%acee@cisco.com> <CAG4d1rdt8jTcJ59X0fDnVn2sEERAyB=2gjjVAnqQ5SDvUxfG0Q@mail.gmail.com> <20160428005018.GB29709@puck.nether.net>
In-Reply-To: <20160428005018.GB29709@puck.nether.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7B699B3CD0B57F41B7981784443F5FD9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/iBQ-NjlpSqyztgUE6b-9xwZXn3I>
Cc: "draft-ietf-rtgwg-bgp-routing-large-dc@ietf.org" <draft-ietf-rtgwg-bgp-routing-large-dc@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Routing Directorate <rtg-dir@ietf.org>, Routing ADs <rtg-ads@tools.ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Apr 2016 16:56:58 -0000

Hi Jon, Alia, et al,

Version 10 satisfies my comments.

Thanks for the speedy and accurate resolution,
Acee 

On 4/27/16, 8:50 PM, "Jon Mitchell" <jrmitche@puck.nether.net> wrote:

>On 25/04/16 15:01 -0400, Alia Atlas wrote:
>> Hi Acee,
>> 
>> Thank you very much for your review.
>> 
>> Authors, could you please respond soon?  I am hoping to get this out to
>> IETF Last Call
>> by Thursday - and on the telechat for May 19.    That depends on timely
>> updates from
>> the authors and shepherd.
>
>Acee - thanks again for your detailed review.  Alia - we've just posted
>-10 which addresses the comments.
>
>-Jon

v2.23.0 | Report a Bug | By Email