Re: [EXTERNAL] Re: Limited Domains:

Gyan Mishra <hayabusagsm@gmail.com> Fri, 16 April 2021 22:35 UTC

Return-Path: <hayabusagsm@gmail.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 AC59A3A3898 for <ipv6@ietfa.amsl.com>; Fri, 16 Apr 2021 15:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 2x4fMJd3xgV8 for <ipv6@ietfa.amsl.com>; Fri, 16 Apr 2021 15:35:40 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 EDE863A3897 for <6man@ietf.org>; Fri, 16 Apr 2021 15:35:39 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id g16so5969165pfq.5 for <6man@ietf.org>; Fri, 16 Apr 2021 15:35:39 -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=84l3BUbErqlvPEKaiqX/vN+XpLFB81ZRa1z6AWdq3cM=; b=b+NYdx2BqpajaG4WLp7okxUfBh95zc7PjNqyaPgt63Xs3IDldosjkE+pzsauWSWa/H gtjiez74GqR43sC6XhWn7tPr69qEdNhNTxpOBafSixySCczqob+BNg1wLkLFEJaNfSq2 HCLfCRAHtiO19xrmBuR3U/1v/4t2S1tYLIeF+lzCgWRa9DVmfhUh9NAzfQpfOA89/tLx BSmZQx6PavLBbnb/Fa6s352xNRCpyYhOdFmRSeDK5dA7uc/VIQumXl93/EV+vp5MZOz+ e4PfDJtwz7f8dv1TgHGsRO3dEyHDD6ZRO+W1LWNGiF7+YhqLiAghtOSX6rLdhKAjsbYn Tv3w==
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=84l3BUbErqlvPEKaiqX/vN+XpLFB81ZRa1z6AWdq3cM=; b=TlVbV4cTOBuVklzWrsev6zCXnMnNPGYZn9aUI0Sx5LQQI/kOBxdh3a18EN6KERx5ED UyoAkm4VFt4TYLhvZLrZn6YWgvd8gar53pqOniFIitEAjdEKQeP0EZ0OH6UpMX33noDY MxTlqk8w0OeCiYKVkJDq4wleri5lW97mGKoJJOqSpTceDCGzGh38Omkvs9Zkzs9bzzLR 3zm6hknDE+Om+unbgsJr1qVeky6WH6aMoA6dlRDFeM8d+3hFZE1X96XBwxPN6Omj9vWy GilOpJ8K1rKezsBLOAkG613qQ03MDF24xe1nSyzytBcdLUznbZB8K4xuPsY789jE5c62 IoyA==
X-Gm-Message-State: AOAM5318gxqf0QLGvUgqhf0GNzhuqOGE2w28BH1bR0fi3t7y7xtxxMGo HshfcS37i5m8sdUj9opXq4X0rNfGL6S2Iowuklk=
X-Google-Smtp-Source: ABdhPJwnwsGnlZAwcoipxbxkzjntTnuaDBHyLgRz7NppbMlxteFLXL5Z0/20XCogZraQtI49PY9EFMNKYGwvX796M8Q=
X-Received: by 2002:a62:1b4d:0:b029:253:ccef:409d with SMTP id b74-20020a621b4d0000b0290253ccef409dmr9791606pfb.4.1618612537365; Fri, 16 Apr 2021 15:35:37 -0700 (PDT)
MIME-Version: 1.0
References: <BL0PR05MB5316991D4124AD85BC69392AAE709@BL0PR05MB5316.namprd05.prod.outlook.com> <1697a0f8-b3cd-9f7d-d610-305b5305c9a1@gmail.com> <4077E736-0092-44C6-80D1-E094F468C00C@gmail.com> <12878114-5c26-86f9-89c3-bcfa10141684@gmail.com> <CALx6S35NBfVJmjqVwhNV3nui2avUOXn6ySMG3cxx2AvGkwr_Ow@mail.gmail.com> <08A6C3D2-A81C-413A-81B3-EFAAA9DBCCE5@cisco.com> <5b68beb6-a6f9-828b-5cca-9c5ec2bfbea7@foobar.org> <126B0A5E-B421-4B1F-AAEB-ABD48FFA4289@cisco.com> <CALx6S35yxqAqWJVhav-=+TB2ZyYttAFfsLNs6Btt+QUx__aQ1w@mail.gmail.com> <9b22cfe4-22eb-3977-2d25-79eb61370291@gmail.com> <17DC585D-3378-42BF-8CD0-67676BF0CFD3@gmail.com> <CAOj+MMG2wy-ag=O7vQO+GkoW+OcAr6CN38vsMU9X0bh=LhF2wA@mail.gmail.com> <57d84a666ee94eeea600377b862d2ed7@boeing.com>
In-Reply-To: <57d84a666ee94eeea600377b862d2ed7@boeing.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 16 Apr 2021 18:35:25 -0400
Message-ID: <CABNhwV2P+_yeiwLj7QaO1OmcbkhAyHawzwrMxERWQSzjnCqmoA@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: Limited Domains:
To: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
Cc: "6man@ietf.org" <6man@ietf.org>, Robert Raszuk <robert@raszuk.net>
Content-Type: multipart/alternative; boundary="000000000000519a6605c01e992b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/4HD43oeiy03j0txFJbILLGQCvUg>
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: Fri, 16 Apr 2021 22:35:45 -0000

+1 on the different meanings to different people on limited domains

The concept of limited domains has definitely evolved and grown but I think
the main underlying theme of limited or I think a better term is “closed”
domain is simply the “operators” network whatever that encompasses which
could be a single AS or 100s of ASs that maybe have many administrative sub
domains as containers within the overall operators domain.

MPLS was a means of confining the concept of a domain but within inter AS
options the domain sprawl can still be a collection of ASs.

There are many nuances with the term limited or closed domain so can also
be very different on a case by case basis.

Also the concept of domain varies drastically even from public operators
domain verses private internal domain.  Also even within a single operators
network their maybe multiple sub domains within public and private network
within an operators overall “domain” that may be parts of different
administrative boundaries but even so they still communicate and is not a
“limited or closed” domain.  There are even case where the public and
private have peering points to each other connect at the hip over MPLS.

At a high level you can think of a corporation and all of its many sub
domains which are part of many separate administrative domains that somehow
are all interconnected public and private are now part of one very large
“limited” or “closed” domain.

There are so many variables and variations and nuances the idea of a
“limited” or “closed” domain exists which could encompass all sub domains
and thus in some cases that limited domain may not see that limited as it
could be quite massive.


Thanks

Gyan

On Fri, Apr 16, 2021 at 6:12 PM Manfredi (US), Albert E <
albert.e.manfredi@boeing.com> wrote:

> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Robert Raszuk
>
> > I think this this thread nicely demonstrates that we need to first
> define what a "limited domain" is.
> >
> > To some it seems to be 1980s definition of an IGP network boundary. More
> modern folks would consider as "limited domain" a set of IGP ASNs areas
> interconnected by p2p BGP still under the same administration.
> >
> > For me "limited domain" is an arbitrary collection of sites anywhere in
> the world using Internet for inter-connectivity.
>
> Good point! Whereas to me, "limited domain" means, only inside this
> platform.
>
> > So any protocol which claims to be defined for "limited domain" and
> which claims that it is backwards compatible with nodes not supporting it
> is equal to allow it to traverse Internet.
>
> "Backwards compatible" may mean different things to different people, and
> it seem dubious in this case (because flow label is to be a random value,
> per IPv6). My main view is, if the domain is truly limited, firewalled or
> even air gapped, then what is the motivation to seek approval in a
> standards body?
>
> Bert
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*