Re: [OSPF] Routing in DC RTGWG interim - updated
Greg Mirsky <gregimirsky@gmail.com> Sun, 22 January 2017 18:26 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF9B21297F7; Sun, 22 Jan 2017 10:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 PMcPdUCCSpz0; Sun, 22 Jan 2017 10:26:15 -0800 (PST)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED36C1297D6; Sun, 22 Jan 2017 10:26:14 -0800 (PST)
Received: by mail-oi0-x231.google.com with SMTP id j15so69122443oih.2; Sun, 22 Jan 2017 10:26:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u+CzmJ0XiNewhVqGPbSNw+PmOJrKBKhl7SrJBZWY7+o=; b=Z2BePVAi2PeXlX5CGD4fnlbCJ6YE16Wr2H3tZr/h34BJ7BmgumUEry+biOYHl6wYMr Ip/8bbOXqV+ZdLcv248dZlzsO+J8krx2monHFZOXyEauyH5qKE33p8xvptSc1zvgZksM OrU982gwWa1siuV7HSn0FouMUoXpXh/HbgfoBN42sQe6JeeCJX/SkEq6Fa7H07ozS1r3 PvcSRMJ1No7B7+e7MjOXThQ1KqiwOK/WzpFW9SMhGCARgVCNssqWQnp7x/WmSBvX4/tn OmK/IF0/S8JdV90jZSmxINw+ZPqnTB/fX/ukbPi8ZAywRPoLKZ77WlOIh0LDihv/maP3 USqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u+CzmJ0XiNewhVqGPbSNw+PmOJrKBKhl7SrJBZWY7+o=; b=YBATQkwAjZWx42fkTKnOB79uRO4bqGze5CW171/kmyM8l6V6GPNkEMw1L0ilWghHdY ZXIzeSwWHnbOG6zbDevw++yz136FGxPqAP3pi1l64JBA+B3h9Mj57XwOMaQmZdho4fVo dG1trxsH9OxJKqg6uv6KZGpUEiSIJ8K7iF7K9a2kB/coB8Oz+CL6QrO9ZWwfJ8WIbh8B i1qs0DPgWwpnzwTaVQx/6q47FILNpR+/4Th521kiOIaaKhZwofdq6uViPawiiMiWDkJ+ s1fa5iLQ1alSyenxSVsq6lcGVlyvJPBhfRL6trqmHcA7ZBC3QmMs+8p4JhDIXOzhlXpT 0u4Q==
X-Gm-Message-State: AIkVDXKQC2kl+CDlT2ASCUf//wauepZFx73DW1qMZ0wnQIajAnVkO08MjuW1ScBPWDCaZ+bsDDfB30+ci/hSDQ==
X-Received: by 10.202.232.83 with SMTP id f80mr7451234oih.60.1485109574294; Sun, 22 Jan 2017 10:26:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.1.103 with HTTP; Sun, 22 Jan 2017 10:26:13 -0800 (PST)
In-Reply-To: <D4A2523A.930DC%acee@cisco.com>
References: <D4A2523A.930DC%acee@cisco.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sun, 22 Jan 2017 10:26:13 -0800
Message-ID: <CA+RyBmXXDOrNj2qW1o96TcUOjhRoARsE0DT2P64Gx2gMXaiiVw@mail.gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Content-Type: multipart/alternative; boundary="001a1141b0f2a0e29d0546b304f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/C72DCT-VAUDEbQOcK9Kg26_a36s>
Cc: Isis-wg <isis-wg-bounces@ietf.org>, rtgwg-chairs <rtgwg-chairs@tools.ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "Black, David" <David.Black@dell.com>, Idr <idr-bounces@ietf.org>, RTGWG <rtgwg@ietf.org>
Subject: Re: [OSPF] Routing in DC RTGWG interim - updated
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jan 2017 18:26:16 -0000
Dear All, RTGWG chairs mentioned only 01/25 but the event stretches it over two days. Got confused. Regards, Greg On Mon, Jan 16, 2017 at 7:35 AM, Acee Lindem (acee) <acee@cisco.com> wrote: > Hi David, > The meeting is 12:00 PM - 2:30 PM EST. > Thanks, > Acee > > On 1/16/17, 6:42 AM, "OSPF on behalf of Black, David" > <ospf-bounces@ietf.org on behalf of David.Black@dell.com> wrote: > > >When: Jan 25, 2017 (all day) > >-- > >_____________________________________________ > >From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura > >Sent: Tuesday, January 10, 2017 4:19 PM > >To: RTGWG > >Cc: Isis-wg; 'rtgwg-chairs'; Idr; ospf@ietf.org > >Subject: Re: Routing in DC RTGWG interim - updated > > > > > >Hi, > > > >Please find updated agenda for 25th¹s interim > > > >Presenters: > >Problem statements: > >Petr Lapukhov - FB > >Dmitry Afanasiev - YANDEX > >Russ White/ Shawn Zandi - LinkedIn > > > >Solutions proposed: > >Keyur Patel, Arrcus - Shortest Path Routing Extensions for BGP Protocol, > >draft-keyupate-idr-bgp-spf > >Naiming Shen , Cisco - IS-IS Routing for Spine-Leaf Topology, > >draft-shen-isis-spine-leaf-ext > >Tony Przygienda, Juniper - RIFT: Routing in Fat Trees, > >draft-przygienda-rift (draft to be published later this week) > >Bhumip Khasnabish, ZTE - Generic Fault-avoidance Routing Protocol for > >Data Center Networks, draft-sl-rtgwg-far-dcn > > > > > >Thanks! > > > >Cheers, > >Jeff & Chris > > > > > >From: Jeff Tantsura > ><jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>> > >Date: Saturday, December 17, 2016 at 06:10 > >To: RTGWG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>> > >Cc: 'rtgwg-chairs' > ><rtgwg-chairs@tools.ietf.org<mailto:rtgwg-chairs@tools.ietf.org>>, Idr > ><idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>>, Isis-wg > ><isis-wg-bounces@ietf.org<mailto:isis-wg-bounces@ietf.org>>, > >"ospf@ietf.org<mailto:ospf@ietf.org>" > ><ospf@ietf.org<mailto:ospf@ietf.org>> > >Subject: Routing in DC RTGWG interim > > > >Hi Routing Protocols wg¹s, > > > >There have been number of recently published drafts and discussions on > >the topic > >As discussed in Seoul, we¹d like to have a RTGWG interim to provide the > >platform for both, draft authors and implementers to talk about what and > >why. > > > >The date we have set is January 25, 9:00AM PST. > >We will be reaching out to you. > > > >Based on our preliminary discussion in Seoul we are planning to have the > >following presenters: > > > >drafts: > >draft-keyupate-idr-bgp-spf Keyur to present > >draft-shen-isis-spine-leaf-ext Naiming? > >draft-sl-rtgwg-far-dcn -? > >Tony P? > > > >DC network designers: > >LinkedIn Shawn Z./Russ > >Yandex - Dmitry Afanasiev > > > >More to be announced > > > >Thanks, > >Jeff & Chris > >_______________________________________________ > >OSPF mailing list > >OSPF@ietf.org > >https://www.ietf.org/mailman/listinfo/ospf > > _______________________________________________ > OSPF mailing list > OSPF@ietf.org > https://www.ietf.org/mailman/listinfo/ospf >
- [OSPF] Routing in DC RTGWG interim - updated Black, David
- Re: [OSPF] Routing in DC RTGWG interim - updated Acee Lindem (acee)
- Re: [OSPF] Routing in DC RTGWG interim - updated Greg Mirsky