Re: [v6ops] I-D Action: draft-ietf-v6ops-conditional-ras-01.txt

Jen Linkova <furry13@gmail.com> Wed, 21 March 2018 19:40 UTC

Return-Path: <furry13@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB5621275AB for <v6ops@ietfa.amsl.com>; Wed, 21 Mar 2018 12:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 J7FQgFqyxBZ2 for <v6ops@ietfa.amsl.com>; Wed, 21 Mar 2018 12:40:51 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 80560126C25 for <v6ops@ietf.org>; Wed, 21 Mar 2018 12:40:51 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id y2-v6so9643408lfc.5 for <v6ops@ietf.org>; Wed, 21 Mar 2018 12:40:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NeDGVqCNe5hki+n94C3hWaNzAgabclLIS6dKxjFzfgY=; b=BC4DdDcMrkC6zbM7fxPVckmDAeeROkqRBcAQk0E20f61OD/MO/naFwjNvII/rIa01G VmnstplAlESB6M/txs1i7j+ZTKFpSW1Bm3VO4Q5PXUAndqQBxy7UXOPP/PheeNeyqIP5 NRuLjpv9ZK0bFjoivML8IToekPSmgKMB4upyr5ajj2O8vORPvsTFxjfSr4zGWECfL7Vs /TArauwM8kQSFm6GEdOGzuKh3lZwPA8QVaVOT2OiCZDqNOmjt5Uq40f8xyvby/KazbMx d57XNg05txO3Jb2D71r2JapLpjwMDyQ+tLHNq8YDjd+I2HgX2B+DEHdQSNKLeEF0dIUM RRxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NeDGVqCNe5hki+n94C3hWaNzAgabclLIS6dKxjFzfgY=; b=sS+d+owMH/1UWESvDx6Zo1UtyYYFr9+iRm1w7x3NDb3a3MrNN1RIGyy7Lo8q9kaDTC l0EB/QoJCCzjtSMhYTKPgmZVixf60iH7rj3XgLSeSFGLGWmBYaq6JkPd1HrNitAPg9QM o0/r649sxk+9GyI/e3M0Bw/Krb6P/6m6zxyNq2MpLnx/6Hb11xpxiYL5Rr5jflrLKH2e 5nAbmnwnIe2+r1sraV1f+NPFyJ9uHss0P+Z+EUHDLmExFkF574EdbwpzAD+3mrnWdjTI XJE9nf452EEaLYIDUFlZqT6onIhPLZSLqyqIn7e2qL+s2VUsk2GfnnC44X4mlTLmSruK 4Kqg==
X-Gm-Message-State: AElRT7EPRMRqxZYLHUcs/9fKVU93ANckVUtiQCrcGLQGw+hl5nRaTY62 XCTUmkxpY5hLyulKGDaw1EBbTVUsLlIFObYa/tnxCxDE
X-Google-Smtp-Source: AG47ELufr9hjr5ixRpWlW6paJCShkxwO3WAyz8t2vrb91bknO0LWhsY+TwVM46Sa1vXVpXUgBGyJA/tmlU4OwV58cQU=
X-Received: by 10.46.137.13 with SMTP id d13mr7855901lji.27.1521661249589; Wed, 21 Mar 2018 12:40:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:d10a:0:0:0:0:0 with HTTP; Wed, 21 Mar 2018 12:40:28 -0700 (PDT)
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459B57DDBB@AZ-US1EXMB03.global.avaya.com>
References: <151976142032.28517.14035738749286138638@ietfa.amsl.com> <CAFU7BAR=ax86N6YMhQeN9fQTgnYO7mzyJNwK2x1OzwpXWwACYQ@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E459B55D41A@AZ-US1EXMB03.global.avaya.com> <20180302185656.GT56288@Space.Net> <9142206A0C5BF24CB22755C8EC422E459B55EA0A@AZ-US1EXMB03.global.avaya.com> <CAFU7BAR+Uyk1PrWN=UCBhuUic-+GO7fAYvSknpLKjr5YixX2iQ@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E459B560FB5@AZ-US1EXMB03.global.avaya.com> <CAFU7BARdE+pzsQVpoWMvDSF7SQpbfR_yP9Ri9xk6togRSmMRgA@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E459B562054@AZ-US1EXMB03.global.avaya.com> <CAFU7BAQ8VsK05MiOt3gjjApoU17tqQZZB2YqJmegcypfiVhbXA@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E459B57DDBB@AZ-US1EXMB03.global.avaya.com>
From: Jen Linkova <furry13@gmail.com>
Date: Thu, 22 Mar 2018 06:40:28 +1100
Message-ID: <CAFU7BASQqu8Y4eTsjisuWxrq_FziKAzmqcAgPpvnkx=9eWcs6A@mail.gmail.com>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
Cc: Gert Doering <gert@space.net>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/wd96xPSVR3EL2QQ83Mi2fWvYYhM>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-conditional-ras-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 19:40:54 -0000

Hi Dusan,

On Thu, Mar 22, 2018 at 5:22 AM, Mudric, Dusan (Dusan)
<dmudric@avaya.com> wrote:
>> Would you be able to give an example for 'most preferred'? The network
>> has two uplinks to two ISPs, two prefixes. Both uplinks can be used.
>> Each border router has a default route pointing to the uplink.
>> What prefix is 'most preferred' to reach  Internet?

> [[Dusan]] One ISP might be more reliable or can provide better QoS, for example.

In this case it comes down to 'active/backup uplink' scenario: use the
more reliable uplink, keep the second one as a backup/prefix
deprecated.

> [[Dusan]] Why the Prf from rfc4191#section-2.2 cannot be set by the router? This is not a protocol change? The flags are already defined in the RFC4191.

It can be set by a router but I'm aware of just one host OS which
supports this. So the router preference in RAs would not be recognized
by end devices.
Again, please note, that the draft documents a solution which can be
deployed *today* in SMB/Enterprise environment, where BYOD is common,
w/o upgrading/replacing host OSes.

>> > and they should have the preference assigned.
>>
>> Which hosts would not recognize.
>
> [[Dusan]] This is an implementation aspect. If hosts implement the Prf from rfc4191#section-2.2, they will recognize Rrf. You should not limit the options based on the current implementations.

It looks like I'm not explaining it properly.
*This* particular draft is written to document a solution which works
with existing hosts in existing networks today.
Solutions which do not exist right now but may be deployed in 3-5-10
years, when all hosts get new shiny features implemented are out of
scope of this particular document. As I've mentioned, a solution
similar to what you are suggesting (using 5.5 and rfc4191) is
documented in https://tools.ietf.org/html/draft-ietf-rtgwg-enterprise-pa-multihoming
.

> [[Dusan]] I think Rrf setting should be in the draft. It might not be used by the hosts today, but can be used by the hosts of tomorrow.

What would be the difference between what you are suggesting and
draft-ietf-rtgwg-enterprise-pa-multihoming?

-- 
SY, Jen Linkova aka Furry