IETF Logo Mail Archive

RE: [EXTERNAL] Re: [v6ops] draft-ietf-6man-grand : saving lookups

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 11 August 2020 14:55 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8EBA3A1125; Tue, 11 Aug 2020 07:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, 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=boeing.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 HPrFVGWMFORc; Tue, 11 Aug 2020 07:55:07 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6C323A112C; Tue, 11 Aug 2020 07:55:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 07BEt2XQ027876; Tue, 11 Aug 2020 10:55:03 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1597157703; bh=QYS7AmTkaKTK5SiehPfs4qA25QNw/gKos56uReQIxpE=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=EpLtFHgJdqYStbYrGMbGcXAZZsH1Wu6VVO7bGIBlzUuwk/TqwiJmhqWNCY4KYFNIh IWrjUZuJlRO143FZmSJ5ck/RJW8DUbxobyv4SDeaBLzIovfOqZjaAbOa1FA29ZxxpX a/FPNtP5J/ipTJ35NjIxWgYOBTFrN8CzVCq95iqp/k7sRYVSY1A4rKxMJVxx0IbbT/ WAT8TSWXBQQF8JT3LEUnBO3lv8gzOgJBfP/jIUMxTEFR3NHfYSh0Zx3TW+WaYZH1TW QQos+pYF9RPG7sJz8QvVTW0ESUDpo5uFEuXRs5hq1WlS6pB4o6xt2EdEDX27Zh+5BX UlM3rB0EA7lxg==
Received: from XCH16-07-12.nos.boeing.com (xch16-07-12.nos.boeing.com [144.115.66.114]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 07BEspQm025666 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 11 Aug 2020 10:54:51 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-12.nos.boeing.com (144.115.66.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Tue, 11 Aug 2020 07:54:50 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Tue, 11 Aug 2020 07:54:50 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>, Nick Hilliard <nick@foobar.org>
CC: IPv6 List <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Subject: RE: [EXTERNAL] Re: [v6ops] draft-ietf-6man-grand : saving lookups
Thread-Topic: [EXTERNAL] Re: [v6ops] draft-ietf-6man-grand : saving lookups
Thread-Index: AQHWbybPrOFhMkmZiUuiI7eoPNuCZqky/hVw
Date: Tue, 11 Aug 2020 14:54:50 +0000
Message-ID: <1f9fa5c8087c46939402a06557711140@boeing.com>
References: <m1k4nX7-0000ICC@stereo.hq.phicoh.net> <1D1A68AE-4C75-4DF0-8C7C-3500DB67C8FB@fugue.com> <4B1A43D0-45B1-4C73-8B09-089D4EC1FFF7@cisco.com> <17A8FA06-3776-450A-B549-958157AD5784@gmail.com> <B50732C5-4BBA-49E4-A169-74677C91B88B@cisco.com> <0A2FD466-6DB0-4378-88B7-AB99D32C2180@gmail.com> <89a4f4fc-7f4a-52c5-83b9-bd112f7a831a@foobar.org> <3D71C5A6-D7FD-45B1-B43C-5526D3A6E55C@gmail.com>
In-Reply-To: <3D71C5A6-D7FD-45B1-B43C-5526D3A6E55C@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 8BCD597B49FCAC5AE9C7BBBAE8A701F88588E2EE07B11EC2AC4A4676159E8E6C2000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/sVKE9RrzwQmdbzQpGPvAqyftGWw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2020 14:55:16 -0000

Hi Bob,

> > Maybe we need an ID which states this explicitly: "Large broadcast domains considered harmful"?  As long as we have broadcast
> domains, people will be tempted to make them too large and will express surprise that they don't scale well.
> 
> I agree on both points.   I would be willing to help write such a draft, but think it would be better with authors who have direct
> operational experience.

Some NBMA links can be *very* large, with all nodes on the link as candidates for receiving
link-scoped multicast. However, with proper controls on limiting the transmission of link
scoped multicast, the transmissions can be effectively propagated to exactly that (small)
group of nodes on the link that actually need to receive them. So, if there is going to be a
draft please make sure to add a note to the effect that properly engineered NBMA links
are an exception, and can in fact support a very large broadcast domain.

Thanks - Fred

> 
> Bob

v2.23.0 | Report a Bug | By Email