Re: [MBONED] WGLC for draft-ietf-mboned-dc-deploy and draft-ietf-mboned-deprecate-interdomain-asm

Olufemi Komolafe <femi@arista.com> Thu, 22 August 2019 23:15 UTC

Return-Path: <femi@arista.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD152120091 for <mboned@ietfa.amsl.com>; Thu, 22 Aug 2019 16:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=arista.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 j61YdU4_fhOl for <mboned@ietfa.amsl.com>; Thu, 22 Aug 2019 16:15:52 -0700 (PDT)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 20CD5120089 for <mboned@ietf.org>; Thu, 22 Aug 2019 16:15:52 -0700 (PDT)
Received: by mail-pf1-x42b.google.com with SMTP id 196so5003324pfz.8 for <mboned@ietf.org>; Thu, 22 Aug 2019 16:15:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arista.com; s=googlenew; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FeWu6i0bzLWej7e45f2oHxHr9G7+rBNT3SRwuUXHidY=; b=S5+b6OtCjnNnr6xIxS3se2Kx7AnAM4xalLDX4OI0zr39OZJVZdf+xa6kVFOMh/fJDA s6XDLPtT4BHJDqgtF8uzNdz6fQXL5yVSfxVAHpJ2suSJQuIV3GZL01+hUlCjUApPGVhJ BaSZWGhYBbiic7dBUrKDY+jbnJHSCc7vAIwF0xPBL14Ob9JtvhfKBaZJPYJisDnCXD8i eXloZ1LiLvZRffp1Wq1Gw8yixamTw8XcLnYfFEE/VsJHKO1b3mjKX8kaBx+jIlJhlWqc MteuIm9T1+XLWwkQOq1WOrEHIj9YIP40n8DVdsZPGENkdpnOazlESPpU681hBRQT29J0 3MWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FeWu6i0bzLWej7e45f2oHxHr9G7+rBNT3SRwuUXHidY=; b=T7QxMFbA7gTqVih0YG5r5H/s5dOodRi3zPY1+er2ceMXOe6gwtOX/4HPfO1G8g+Ixv zR1V9x4m6zRSvsJLK46fSkTvVDn4dB4OM0P/RyN0swbwXqiUSgwnrHo4BXmUhRUtWGrU 6CNtNMze7us09uHyzfZ2HNFwsw6uZ4qu70yNjj80xKdnYJzTjPKvCBxAtKfR59TYQPCc IpbNq385tgvwnTnmARKj9Xj2BPOslDJeO0cyqSCtlRPVVhRQTJMmksYMXf466lLKl4yw WvJt/aOm9HmN+yZhsrPvJcsVhsm5D+7KINp22rAItxjQSWRiRDSbqUT4w6WlEokQH1JR cSyg==
X-Gm-Message-State: APjAAAXrx/mywProa3+FWbvlo3PpOqq9/nA73UZ5yLbxzPdoMIVbb1Hi yvyIN7oEbpEAu1q5+VcftEls7w==
X-Google-Smtp-Source: APXvYqxAJkSpFyGd1IaWlLSInykJOkh0Dn9iNozIE+4Cn2v6mIevhobX+vrucZiA5QJm43+Yi5et6w==
X-Received: by 2002:a63:2ec9:: with SMTP id u192mr1390361pgu.16.1566515751439; Thu, 22 Aug 2019 16:15:51 -0700 (PDT)
Received: from ?IPv6:2620:a0:4001:100::1ac? ([2620:a0:4001:100::1ac]) by smtp.gmail.com with ESMTPSA id u7sm469636pfm.96.2019.08.22.16.15.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Aug 2019 16:15:50 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Olufemi Komolafe <femi@arista.com>
In-Reply-To: <alpine.DEB.2.02.1908131224521.3023@contrail-ubm-wing.svec1.juniper.net>
Date: Fri, 23 Aug 2019 00:15:48 +0100
Cc: MBONED WG <mboned@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA4F1B39-EC06-4E7F-8484-65E5E55AF513@arista.com>
References: <alpine.DEB.2.02.1907191326110.12951@contrail-ubm-wing.svec1.juniper.net> <alpine.DEB.2.02.1908131224521.3023@contrail-ubm-wing.svec1.juniper.net>
To: Leonard Giuliano <lenny=40juniper.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/_216YxNFtc1UTr6B_ptTHsOqqFA>
Subject: Re: [MBONED] WGLC for draft-ietf-mboned-dc-deploy and draft-ietf-mboned-deprecate-interdomain-asm
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2019 23:15:54 -0000

Thanks for the good feedback Lenny.  We will make the suggested changes.

Regards,
Femi
> On 13 Aug 2019, at 20:54, Leonard Giuliano <lenny=40juniper.net@dmarc.ietf.org> wrote:
> 
> 
> <chair hat off, speaking as individual contributor>
> 
> I support publication of draft-ietf-mboned-dc-deploy as this document 
> describes a number of pertinent issues for mcast in a DC environment.
> 
> Some mostly editorial comments below:
> 
> Abstract: "judiciously" misspelled
> 
> Sect 1. Intro, 2nd para: I am confused by the tense used in this para- is 
> it talking about the current situation, or in the future or even the past?  
> If the future, how can an assumption of the future be known to be 
> incorrect in the present?  Don't we need to arrive at that future point to 
> determine how correct this assumption is?  Anyway, suggest sticking to the 
> current state of affairs.
> 
> Sect 2.1, 2nd para: "... there is a consensus..."
> 	-would "expectation" be more appropriate than "consensus"
> 
> Sect 2.2, 1st para: "... overlays mainly simply ..."
> 	-probably just "simply" would be simpler
> 
> Sect 3: "...arguably the intuitive initial course of action for a data 
> center operator..."
> 	-perhaps better to say: "it makes sense for a data center 
> operator..."
> 
> Sect 3.3, 1st para, last sentence: "Thus, PIM must be running..."
> 	-"Thus, a multicast routing protocol (typically PIM) must be 
> running..."
> 
> Sect 4.1: I thought this section was very informative and well-written
> 
> Sect 4.4, 3rd para:  "The
>   deployment envisioned with overlay networks is that the the
>   encapsulation endpoints would be the BFIR."
> 	-suggest something like the following: "The BFIRs are the 
> encapsulation endpoints in the deployment envisioned with overlay 
> networks."
> 
> 
> 
> 
> On Fri, 19 Jul 2019, Leonard Giuliano wrote:
> 
> | 
> | We would like to officially begin working group last call for BOTH
> | draft-ietf-mboned-dc-deploy and draft-ietf-mboned-deprecate-interdomain-asm.
> | Please post whether you support/oppose the advancement of either/both of the
> | drafts as well as any comments you may have to the list by Aug 16.  Also,
> | please note if you are aware of any IPR involved in this drafts (we must hear
> | from the authors about IPR).
> | 
> | Most recent version of the draft can be found here:
> | https://datatracker.ietf.org/doc/draft-ietf-mboned-dc-deploy/
> | https://datatracker.ietf.org/doc/draft-ietf-mboned-deprecate-interdomain-asm/
> | 
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned