Re: Proposed change to draft-ietf-6man-multi-homed-host after IESG review

Fred Baker <fredbakersba@gmail.com> Fri, 16 September 2016 13:38 UTC

Return-Path: <fredbakersba@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 839D112B283 for <ipv6@ietfa.amsl.com>; Fri, 16 Sep 2016 06:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 7fU0oVMigLht for <ipv6@ietfa.amsl.com>; Fri, 16 Sep 2016 06:38:15 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 A43A812B303 for <ipv6@ietf.org>; Fri, 16 Sep 2016 06:31:53 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id m11so111660105oif.1 for <ipv6@ietf.org>; Fri, 16 Sep 2016 06:31:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GCFRj3/wNjQApGx+7K0xjgZT4FZPHDLX+x7QjNcXtDk=; b=YbhMbZ9GT2986CWEodUdPc9qV9xO5Fsft/LX+jWJ95tORFntwCzO4y/VKt8TuZ8m1X siPGeArrkvZ7N50uWp+GtmC0EweFkHef0LJdcR+MXkXJEpMHQJ4OGBxbqH1sM7lC5DRc YdNqKBJ1Xp8B2hClh8PwMqlhLbjSogWKNJpZAW3mvEJygUR8ZabkgxBrtZ//D4SN12wa CIYvqxEefOonOvZJsnuMFpXgSSRfQAj68a59Gig1h4z31uMKTOnfqa3e16+eThEsQNk4 U0u3ec5PlDcJX6RoIUbeC1/HE/1x0EqBzIulyhnRP/aUe6X6XN2DfIm7i4wzci+Z5fvO 9n+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GCFRj3/wNjQApGx+7K0xjgZT4FZPHDLX+x7QjNcXtDk=; b=bHeTW3KoVFd7u3mdM6hUSMTrnhtN8SqAsPge9+LpsgckyoIOBcd2yl+ywfn+ICrQ+L bnxR6B4kRR+kQDBnzbRxg8fR2ERabhrZQzIkXHXk2m06+mAwR4WMSED2w6HmjrbS6zBY 78eD1XopblbCaWbslezF0GUS2wFZjXiegxvfVm7RLQ6rJ5FF/4FKvdDYZ8zmeHLS4eH6 6aO4l4ETG+CRzW0HBrMH+Dd9vwRB/TcIYKfEVfGH0tSLYfpqxAt9lTrA2/iaaCp10Zor wzz8WG8Lw6NAYNmgPp9SleMhFq5elkGzsHBd7IyMMFWsizOoBaUJTkruWmT0Ub/dT6tA zzMg==
X-Gm-Message-State: AE9vXwO8FKl2rGBomuuVcfWP35w3SWkLIScxwpvjpRBN2irao0rhsI9Kp17++HmR5pETjw==
X-Received: by 10.157.56.215 with SMTP id k23mr12236607ote.165.1474032712865; Fri, 16 Sep 2016 06:31:52 -0700 (PDT)
Received: from [100.175.133.60] ([172.56.7.64]) by smtp.gmail.com with ESMTPSA id k23sm2760092otd.30.2016.09.16.06.31.52 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 16 Sep 2016 06:31:52 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
Subject: Re: Proposed change to draft-ietf-6man-multi-homed-host after IESG review
From: Fred Baker <fredbakersba@gmail.com>
X-Mailer: iPhone Mail (13G36)
In-Reply-To: <0b08b92d-ad2d-2831-dece-7c914fd94716@gmail.com>
Date: Fri, 16 Sep 2016 15:31:50 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6378C64D-896B-4914-9934-4E5E3A4B3EDB@gmail.com>
References: <0b08b92d-ad2d-2831-dece-7c914fd94716@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6a0eYMij2KN4BDFWTuZiublYS6M>
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 13:38:19 -0000

The key point there is the support for source/destination routing in the forwarding plane; how the FIB obtains the route is secondary. It might be worthwhile making that point...

Sent from my iPhone

> On Sep 15, 2016, at 10:53 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Hi,
> 
> This message concerns
> https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-09 .
> 
> There is one remaining issue in the draft before it can get IESG approval.
> One of the routing ADs proposes the following change. It does not affect
> the normative content of the draft, but it is a technical change (deletion)
> so we'd like to hear if there are any objections from the WG. Please comment
> within a week (silence means no objection to this change). Some more
> background is below the proposed change.
> 
> OLD:
> 
> 2.2.  Expectations of multihomed networks
> 
>   The mechanism specified in this document requires some form of
>   support from the routing protocols used in multihomed networks.  One
>   such way of providing the requisite support in routing protocols is
>   described in a routing protocol independent fashion
>   [I-D.ietf-rtgwg-dst-src-routing].  Network designs exist that can
>   usefully limit themselves to static routing (such as a simple tree
>   network), or may internally use no routers at all, such as a single
>   LAN with two CE routers, each of which leads to a different upstream
>   network.
> 
> NEW:
> 
> 2.2.  Expectations of multihomed networks
> 
>   Network designs exist that can usefully limit themselves to static
>   routing (such as a simple tree network) or may internally use no
>   routers at all, such as a single LAN with two CE routers, each of
>   which leads to a different upstream network.  However, the
>   mechanism specified in this document may require some form of
>   support from the routing protocols used in some multihomed networks.
>   The details of such support are out of scope for this document.
> 
> You can see Alia's original DISCUSS comment dated 2016-08-02 at
> https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/history/ .
> The "SHOULD" mentioned there has already been removed, but her considered
> opinion is that the routing solution is simply out of scope for this draft.
> 
> Regards
>   Brian Carpenter
> 
>