IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 15 September 2016 20:53 UTC

Return-Path: <brian.e.carpenter@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 63AC312B02C for <ipv6@ietfa.amsl.com>; Thu, 15 Sep 2016 13:53:02 -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 lTEx2uARG4US for <ipv6@ietfa.amsl.com>; Thu, 15 Sep 2016 13:53:00 -0700 (PDT)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 7495912B051 for <ipv6@ietf.org>; Thu, 15 Sep 2016 13:53:00 -0700 (PDT)
Received: by mail-pf0-x22c.google.com with SMTP id z123so20126912pfz.2 for <ipv6@ietf.org>; Thu, 15 Sep 2016 13:53:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=NS/yQ8/aXQAT6/ZH3MoHLcZ4x3CkxC5G9XgNX+rgiow=; b=uuFD4RFu1sZJGOyWHhcXyQA0nFZwTSQzwDJEFog6k8Cf6fDVcc4cPLTShuqMv9vxES RxF438+4eQJIANq0M6rHxPSJ1qgL7+5kdDeBQz9RREEipYVkKLMhWBxMaMx2d8o6Uzj1 fBXkMgpk/T3vVlOBcIJvrdIxXGgU4nv3OwOUdQWUOXXIymNaW/QI9EUYv67EpNotSlgS L9N6EnG2a8bKGnH9qVyfufXc+N3c+74Kcv+Hn1cj2PmO0IBxxI9TjlxRxspjT8AIb3Q9 cu0NbclWecFzF/OpQAbdlFXcBATm+Fc3fmQUmYCM3LJtaCcIkeVsenypYfhZzXet+2s0 goxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=NS/yQ8/aXQAT6/ZH3MoHLcZ4x3CkxC5G9XgNX+rgiow=; b=iZHMxCaFPn/w86+PgONLbWR52ZRbcuaT7ha0zJmG5YZ1pdjgFEqkrfa5IZXBoBo0Tl FDhHUHilPCmrSdgviGnIbjQkPxo5a2lmXzBUKq+aN0Y3I/SThcoPrz9VQgSzs80uPP+o tEZ3TwiILE7xm6QGJx1JQC5DGhfQ8HNo63SSP9xIFYN/TcfdXs67kGAG6supi21yJ+VQ ZUHCl2EPQ/qhemeLrqjHr24NDy5Mw87s7gtuKBllSDAj+DN3+Xjj/wPsjBoIM3w0Eeqz 1/waAgvsBzjv1G7hA/mbgctL19oV0iGgPnWvtAATN0nNW4V6UVEBCQ+7ADPNP2St+uyE awDQ==
X-Gm-Message-State: AE9vXwNdm4uuP0AmyhPj5G3egBBJu9hXc3EyttF3D2dFpBmDUWqXwLddAchkC0qpYL4oYw==
X-Received: by 10.98.152.69 with SMTP id q66mr3828175pfd.176.1473972780039; Thu, 15 Sep 2016 13:53:00 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.71.236]) by smtp.gmail.com with ESMTPSA id g14sm2074062pfb.77.2016.09.15.13.52.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Sep 2016 13:52:58 -0700 (PDT)
To: 6man <ipv6@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Proposed change to draft-ietf-6man-multi-homed-host after IESG review
Organization: University of Auckland
Message-ID: <0b08b92d-ad2d-2831-dece-7c914fd94716@gmail.com>
Date: Fri, 16 Sep 2016 08:53:04 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ZsZTMNk5rjUJVt0GXkDmh4hp96o>
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 20:53:02 -0000

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

v2.23.0 | Report a Bug | By Email