IETF Logo Mail Archive

Re: [i2rs] Mail regarding draft-ietf-i2rs-yang-l3-topology: Modelling of L3 links supported by a L2 broadcast network

Alia Atlas <akatlas@gmail.com> Wed, 23 October 2019 03:53 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B921012006F; Tue, 22 Oct 2019 20:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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_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=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 WJ53yIDA59ll; Tue, 22 Oct 2019 20:53:23 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 C8CD912000F; Tue, 22 Oct 2019 20:53:23 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id 89so16159867oth.13; Tue, 22 Oct 2019 20:53:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=clkYh5UH6aS1z+rP+FrA5mP9qbE4KKhfTdztKVqaZL4=; b=ce3Ulg4jDdVBHGobi0hCkKTDbZJCxJgABeR4TDGYaxiksTaeBTK2vEsD7HA/EyADlh KNw/Ozu89H7xP52hiOvZIf23M0ASYO7uYYXOZQMFXiABiRua6x9t9ZXlb0EG/JcGjdEi pzFHGqFZPkTdDc9d+HfymlrP1sQ6NNAA91zQA7S6WiPy0WvEJvN1SGZEaB9hkc+xPV7e gAEzT0D/91LJofgY/FSOByK1EtoDejnK3cMqEcaZG4gVGsTvN6MUaszKnqAHaJ7wzCcK sHLEJ5c9kkxEXg6ww+6is1NBkfPVW42fpM8cO+Pk/UddbU0A3H9UsCsXafR+gf2sBOlb yySg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=clkYh5UH6aS1z+rP+FrA5mP9qbE4KKhfTdztKVqaZL4=; b=mtMGKFHN9cRubfebt2J6vF8SNYCq+Ar+7HTwWV2mX4jjaNPtg/MQO1VMkWziapdNG7 SYgvJwsWv3WKuvRqW/IXNvP1SFExi5b/xPHl+BZXABceKSgsCEM3Ps7ZHR30Cc93Ax+N 87PSD0lW3AekGzSt+yuCZLYVD2F5WHL8B74XajxmnsB4wIjdiXOAgbq+AKHzm636nZ6/ q5K0e8mAQS0GN+khDRypNNHZlBaD9thJoNmG8Ch7wew7sqZHO6ixFmSpG40zmPPin3sL dB7FbqvHJ1MgmZ34R7PEjdCruNcr/c3R7lHl5w6cu512PBqlLvXw42Jl1P9/EvCZlPtk Nq7g==
X-Gm-Message-State: APjAAAUzaWqVUmuS/MqNFrzPSS1vLs1mSf6XYGqiQ0n/oCfGKgjPOVY7 NjXlr9xJAzGOcxkQmc3NFdLPdwleMtXfItKIy4Y=
X-Google-Smtp-Source: APXvYqxLPvpDTIQktXGrJy3QqdZ+twJ5/MOXWhMCE88ZP1Semld9xj3NQjXiAyCqABhgA6W0jC4mE1dnXN6uivEf8CA=
X-Received: by 2002:a9d:39a1:: with SMTP id y30mr5581953otb.144.1571802802831; Tue, 22 Oct 2019 20:53:22 -0700 (PDT)
MIME-Version: 1.0
References: <MWHPR2201MB1215A10308FBEFFF73E70A74996B0@MWHPR2201MB1215.namprd22.prod.outlook.com>
In-Reply-To: <MWHPR2201MB1215A10308FBEFFF73E70A74996B0@MWHPR2201MB1215.namprd22.prod.outlook.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 22 Oct 2019 23:53:11 -0400
Message-ID: <CAG4d1rd04av95h=hkV3qSwJfMKJkE+vFvLo9pViVpSusT=b-9Q@mail.gmail.com>
To: Stephen Cheng <Stephen.Cheng@aviatnet.com>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>, "draft-ietf-i2rs-yang-l3-topology@ietf.org" <draft-ietf-i2rs-yang-l3-topology@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b8858405958bdbee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/fA6NZ9rFJKhe4pil1hmbUwITUUA>
Subject: Re: [i2rs] Mail regarding draft-ietf-i2rs-yang-l3-topology: Modelling of L3 links supported by a L2 broadcast network
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2019 03:53:26 -0000

Hi Stephen,

An L2 broadcast network is usually modeled with a pseudo-node and then
separate links between that pseudonode and
each L3 device.  Please take a look at Section B.1.2 where one of the
example ospf-node-attributes is a pseudonode.

Regards,
Alia

On Tue, Oct 22, 2019 at 11:46 PM Stephen Cheng <Stephen.Cheng@aviatnet.com>
wrote:

> Authors of RFC 8346,
>
>
>
> I have a few questions regarding RFC 8346, and would appreciate your
> illumination.
>
>    1. Is RFC 8346 ietf-l3-topology intended to cover modelling of L3
>    links that is supported by a L2 broadcast network (such as an Ethernet
>    network)?
>    2. If so, would it be correct to model the L3 connection between every
>    pair of L3 device on the L2 broadcast network as a pair of unidirectional
>    l3 unicast link ? For example if there are 100 devices on 192.168.1/24
>    network, should there be 9900 unidirectional l3 unicast links?
>
> Thanks.
>
>
>
> Warm regards,
>
> Stephen Cheng
>
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>

v2.23.0 | Report a Bug | By Email