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

Bob Hinden <bob.hinden@gmail.com> Thu, 15 September 2016 23:10 UTC

Return-Path: <bob.hinden@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 C571912B0DA for <ipv6@ietfa.amsl.com>; Thu, 15 Sep 2016 16:10:31 -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 m5RTp6Pwz5Ht for <ipv6@ietfa.amsl.com>; Thu, 15 Sep 2016 16:10:29 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (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 73D4112B0D5 for <ipv6@ietf.org>; Thu, 15 Sep 2016 16:10:29 -0700 (PDT)
Received: by mail-io0-x230.google.com with SMTP id r145so7893914ior.0 for <ipv6@ietf.org>; Thu, 15 Sep 2016 16:10:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=M7gnI9Vo3Dw5o7Ot2jGtOcnRkYkzL1aDi4N0YGdp9gk=; b=xTXXdrsXh/NR2yOY0evNPF14IgEwLYHO4DNesOMTdkACBs2bJ/px3aILpzoBYexWY8 0vqvGdGKAmWQkYKtfTGrp7mX3VCBnIlKGY3/kBIbUUMQKXN0rnhfinh7OS6IPxNFK8JC zPdxSfZAJ9QJ4P6QjFvOkdoe7G8SfsKc6MZenUXBC/BUbhbfGs7fqW496NYHd8JrWqLx oS/4oC7sWtANnTemcDKE/QZv3sBW7tGSovqO+aW5ZlKziyzny1I1tzoVyL+p0Qx7LSB3 ZJeMNBiCNaUOLOePGIxVj2KAjMsifVokF0zEU+SK3MSTfAlPRlxoPWe83ltajxOCeeMe 1+ig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=M7gnI9Vo3Dw5o7Ot2jGtOcnRkYkzL1aDi4N0YGdp9gk=; b=AYweZskJf25fhWUyEm4RSUAXR4vV+24f2DtaqqBNJCPIN933bF53eZvsFxJP4BE3FA 6heMQkm+8lNeK+jA5SsANhRDgjRuCdk4kgcfu8iwbD/dSlBUEXUtwVIXiaMGv+elIdNw ApYqH9v6sPkyuKS1jg8eMdtWW89ld7v4scv+uES8apb94WiIOgnKC4RQNrTf5uHyU3r6 1ZzhfsRFx4vHAToG/auYfM0oeaWDQAcHK3zR+uP+Q21PDhOR4rUQzyog2NNx1cgZYvNO 43bfsDahNWdst+3xrMazgsk7LrCYDFfV7fwv/78V2sqSP+4gZRijNg1Yk7gyzYqvRTCa qPYA==
X-Gm-Message-State: AE9vXwN8lKKtTnRwIfHr5mN5DKOMdNrcHygPQHQe6DygUKX7W0NMxyhpVUz7sTp5F+kPwQ==
X-Received: by 10.107.39.6 with SMTP id n6mr19987355ion.10.1473981028770; Thu, 15 Sep 2016 16:10:28 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id x79sm1851274ita.16.2016.09.15.16.10.26 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 15 Sep 2016 16:10:27 -0700 (PDT)
Subject: Re: Proposed change to draft-ietf-6man-multi-homed-host after IESG review
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_A24895B9-9841-43C1-BDBD-075D303060EF"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <0b08b92d-ad2d-2831-dece-7c914fd94716@gmail.com>
Date: Thu, 15 Sep 2016 16:10:24 -0700
Message-Id: <1C0F0FB4-C550-4DD3-8467-CE28AF7A003F@gmail.com>
References: <0b08b92d-ad2d-2831-dece-7c914fd94716@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/e_0lyzGyQbMAiLjeJ1fR_CP4NyE>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
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: Thu, 15 Sep 2016 23:10:32 -0000

Brian,

While I don’t have a strong objection to the proposed change, I am uncomfortable with what I read is a request to not even mention source-destation routing.  I agree it should not be a requirement in this document, but I don’t see anything wrong with a forward looking pointer.  Perhaps something like this (based on the NEW text):

  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.
  One approach that is being investigated to provide the requisite support
  in routing protocols is described in [I-D.ietf-rtgwg-dst-src-routing].

Or similar.

Bob


> On Sep 15, 2016, at 1: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
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------