Re: [Bier] DISCUSS? SI vs. sub-domains - draft-ietf-bier-architecture-02

Caitlin Bestler <caitlin.bestler@nexenta.com> Tue, 13 October 2015 19:59 UTC

Return-Path: <caitlin.bestler@nexenta.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90CDF1A8A0C for <bier@ietfa.amsl.com>; Tue, 13 Oct 2015 12:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 sexxxB-e3UA7 for <bier@ietfa.amsl.com>; Tue, 13 Oct 2015 12:59:53 -0700 (PDT)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) (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 1BE291A8A09 for <bier@ietf.org>; Tue, 13 Oct 2015 12:59:53 -0700 (PDT)
Received: by pacex6 with SMTP id ex6so30259582pac.3 for <bier@ietf.org>; Tue, 13 Oct 2015 12:59:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=rOcxzoX5I545BUL3v+htoybxYLfZbUYYH/UBGkr5WaE=; b=PmfM0VbahLZ47gre3krYOiYLAmtl1vViHCoyhBfRotwWbU7vJwKKv8KL+RqDiG1glZ AedM/4uzJEPvwrcg3hMTaTrhKk7w5Lu95oYCJ8xmW//nxgofGW2H5MsXvO6iUxjX5vnZ XJCfOSwpjrIAkIFwENALcCp+55Hj8cD6DEinfYQ4SWmqgvtM1KE4edcwBsDpkZGbMbeO kJGK+yuBJJ8XaGtP/kbl+Ivg4RvbAzqKJo7wSJnEZ0kB+7yIkNStL8uwujmGeCzxCMcb gshJ+pqfQDT7kQlsvgDuKX/Va8OQ5xbFrxnFBpyKd8PqLl9Xtrwo430ufBHO58D06ela V1uA==
X-Gm-Message-State: ALoCoQmFR/VAZ+ogvM72hewdLPqO5uFSNG/PPPtNf0dTnsfVXZFSJ1L5U27zwIDzlwUff+igCZJo
X-Received: by 10.69.16.166 with SMTP id fx6mr42154765pbd.18.1444766392649; Tue, 13 Oct 2015 12:59:52 -0700 (PDT)
Received: from Macintosh.local (67-207-110-172.static.wiline.com. [67.207.110.172]) by smtp.googlemail.com with ESMTPSA id ss6sm5375060pbc.74.2015.10.13.12.59.51 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 13 Oct 2015 12:59:51 -0700 (PDT)
To: Toerless Eckert <eckert@cisco.com>
References: <20151013173739.GX13294@cisco.com>
From: Caitlin Bestler <caitlin.bestler@nexenta.com>
Message-ID: <561D62B6.8010304@nexenta.com>
Date: Tue, 13 Oct 2015 12:59:50 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151013173739.GX13294@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/bier/cCNbvsNopg2QVenoZk5PIFeqypw>
Cc: "bier@ietf.org" <bier@ietf.org>, Antoni Przygienda <antoni.przygienda@ericsson.com>, Eric C Rosen <erosen@juniper.net>
Subject: Re: [Bier] DISCUSS? SI vs. sub-domains - draft-ietf-bier-architecture-02
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 19:59:54 -0000

I meant to type "adjacencies". Apologies for not catching the 
auto-correction.

Anyway, from your explanation I think I have a fairly good understanding.

The key *intended* difference is that the way sub-domains are *intended* 
to be
used the end nodes would be automatically assigned to the sub-domains based
upon the routing underlay.

But the architecture document makes it clear that there *may* be 
multiple sub-domains
using the same routing underlay, in which case the assignment of end 
nodes to sub-domains
starts to look a lot like just assigning a BFR-ID.

Is there some succinct explanation as to why a deployment SHOULD NOT map 
multiple sub-domains
to a single routing underlay, but they MAY do so for the following 
reasons... ?

If sub-domains SHOULD map to a unique routing underlay while SI-subsets 
MUST map to the same
routing underlay then you have a justifiable distinction. But 
sub-domains that MAY map to the same
or different routing underlays while SI-Subsets MUST map to the same 
routing underlay as the SI just
seems like excessive detail in the API.