IETF Logo Mail Archive

Re: [Int-area] WGLC for draft-ietf-intarea-broadcast-consider

Joe Touch <touch@isi.edu> Thu, 09 March 2017 18:42 UTC

Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C024812979D for <int-area@ietfa.amsl.com>; Thu, 9 Mar 2017 10:42:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 AK0bUfgEuVJC for <int-area@ietfa.amsl.com>; Thu, 9 Mar 2017 10:42:32 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 D4D4A1296EF for <int-area@ietf.org>; Thu, 9 Mar 2017 10:42:32 -0800 (PST)
Received: from [128.9.184.163] ([128.9.184.163]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v29Ig8DR001445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 9 Mar 2017 10:42:08 -0800 (PST)
To: "t.petch" <ietfc@btconnect.com>, Juan Carlos Zuniga <j.c.zuniga@ieee.org>, int-area@ietf.org
References: <CAHLBt8305z=iXg-_SOYh_FcqrFA=Vz-9FmfcTo=PnCviKGhPsQ@mail.gmail.com> <015c01d298f8$7cf7ed60$4001a8c0@gateway.2wire.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <149f4a9d-56bb-6cbc-96d0-f66f1be9f8fe@isi.edu>
Date: Thu, 09 Mar 2017 10:42:07 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <015c01d298f8$7cf7ed60$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
X-MailScanner-ID: v29Ig8DR001445
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/ed1x-29v8TbyhPa_vJBWR1P9SfI>
Subject: Re: [Int-area] WGLC for draft-ietf-intarea-broadcast-consider
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Mar 2017 18:42:34 -0000


On 3/9/2017 9:13 AM, t.petch wrote:
> And I am surprised at the lack of mention of IPv6 which did its bit for
> the planet by eliminating broadcast.

IPv4 had two kinds of broadcast:
    - all 1's (like IPv6 all-nodes link local)
    - subnet-directed, which RFC2644 turned into a subset of all 1's on
a link

IPv6 has the following kinds of multicast that are effectively broadcast:
    - all-nodes link-local (like IPv4 all 1's)
    - all-nodes site-local (arguably similar to subnet-directed, but
un-doing the one-hop restriction of RFC2644)
    - all the multicast addresses that work over other scopes, limited
only by function
        e.g., NTP can be "broadcast" everywhere

And, depending on implementation, IPv6 anycast might use broadcast too.

So IPv6 didn't remove any of IPv4's broadcast; it just gave alternatives
that may or may not be used - some of which can "broadcast" even wider.

Joe

v2.23.0 | Report a Bug | By Email