Re: [Ice] Mirja Kühlewind's Discuss on draft-ietf-ice-dualstack-fairness-04: (with DISCUSS and COMMENT)
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 05 September 2016 19:29 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ice@ietfa.amsl.com
Delivered-To: ice@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C3812B461; Mon, 5 Sep 2016 12:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 st1h5A_vSJHJ; Mon, 5 Sep 2016 12:29:34 -0700 (PDT)
Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002:c09::22f]) (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 9E9C212B058; Mon, 5 Sep 2016 12:29:34 -0700 (PDT)
Received: by mail-yb0-x22f.google.com with SMTP id x93so62804292ybh.1; Mon, 05 Sep 2016 12:29:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=b9StSOCUrSmIs4qHwSDxJDJVibZ9ZByulQUUHmf0FJQ=; b=w9Z63rmQfCy1bUMesgTMjYlyUU8JXx+/svAQJJoaB3p2lGEfYURPymbOi+sq5FvnpT YHtrE1RakoAeQDqgl7JnPHrNKuibFydcKnTYbm4QijPme/IdCOLi75HwHY3s8/E+oKJq F40dv554TsxaJuX2Nnpko4B6JXCTEAdZxYhz1UXyTDTC8P1rK+YMr5bdSW3v/HrtcnWy n6LzOxkizf1u8q49VosvZV1TWZkuSJTYETUBVN9sUBcLuX3Wq+qvrkUPT3I6q6RZL6mk RwGNqSupPGl3SIBG+t7Eb79ZNB3o31RCFrADQt5sqmnKMgLX+O7j7DAMMJoSjRNn/zT/ ktgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=b9StSOCUrSmIs4qHwSDxJDJVibZ9ZByulQUUHmf0FJQ=; b=VHzk75hS87NFZBY+rxkLrn7pI+k1r2UjtC7Hp7Z1To96Pv4FjLpwY6YnMyxMYhtCPI sTPcmJCzot5SRkER5saZrOBxcOSd26BE/1CJTS9yW4gba+twut8mXtU5J8Rnz2QDWImI ztz4TFZdB17ykCOwQKwwnDUP2aS2jvcMOlJZObp5ag8Q1cCg6+bzy+X2jL7pPazZ7elU D6jv87l9tKwq9Nr3liXHSppZ5cYgmAJvhWiwHAv9Zb7cT/7mutSo4UUrJLWMBlwWLzp+ +D+rDlX8bQg6RYkRNnRXopAzRRwgToeXaJa2Eca6zodOY6eZAq7lSVAfQOGbuwD0VNGg ORgg==
X-Gm-Message-State: AE9vXwPXw61QMCKGb4h5gRpW6v+w1UzJzH8GLn3U1gerIdiSNQw+a5E/Xz99RK+8lqQDWxCPuOeJYJNsKdgGxA==
X-Received: by 10.37.221.129 with SMTP id u123mr29036795ybg.61.1473103773730; Mon, 05 Sep 2016 12:29:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.24.86 with HTTP; Mon, 5 Sep 2016 12:29:33 -0700 (PDT)
In-Reply-To: <3D60787A-FD67-472D-8787-C5EEA6B8BB9F@cisco.com>
References: <147264668629.5913.9417537450161055669.idtracker@ietfa.amsl.com> <3D60787A-FD67-472D-8787-C5EEA6B8BB9F@cisco.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 05 Sep 2016 14:29:33 -0500
Message-ID: <CAKKJt-eLYv0XZzN6BkuXSQFOmXAh4YQ1ZtHpz2m9iPWsZ+tKtA@mail.gmail.com>
To: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
Content-Type: multipart/alternative; boundary="94eb2c0337d4268d27053bc7b344"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ice/nD0FcfUoG3xptSalwZtEYcp2Kqg>
Cc: Ari Keranen <ari.keranen@ericsson.com>, "draft-ietf-ice-dualstack-fairness@ietf.org" <draft-ietf-ice-dualstack-fairness@ietf.org>, "ice-chairs@ietf.org" <ice-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>, Mirja Kuehlewind <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
Subject: Re: [Ice] Mirja Kühlewind's Discuss on draft-ietf-ice-dualstack-fairness-04: (with DISCUSS and COMMENT)
X-BeenThere: ice@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interactive Connectivity Establishment \(ICE\)" <ice.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ice>, <mailto:ice-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ice/>
List-Post: <mailto:ice@ietf.org>
List-Help: <mailto:ice-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ice>, <mailto:ice-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Sep 2016 19:29:37 -0000
Hi, Pal, On Mon, Sep 5, 2016 at 3:23 AM, Pal Martinsen (palmarti) <palmarti@cisco.com > wrote: > > > On 31 Aug 2016, at 14:31, Mirja Kuehlewind <ietf@kuehlewind.net> wrote: > > > > > > The document, along with other ballot positions, can be found here: > > https://datatracker.ietf.org/doc/draft-ietf-ice-dualstack-fairness/ > > > > > > > > ---------------------------------------------------------------------- > > DISCUSS: > > ---------------------------------------------------------------------- > > > > I'm willing to resolve my discuss quickly but I would like to start some > > discussion: > > > > To me the recommenations given in this doc are not very clear. To my > > understanding are there two recommenations: > > > > 1) intermingle IPv4 and IPv6 addresses, and > > 2) put lower priority for adresses that are know to have connectivity > > problem. > > > Correct. > > > > However, that leaves tons of open questions to the implementor, e.g. > > - How many IPv6 addresses should I have before the first IPv4? > > - How do I measure/track that an interface has connectitivy problems: > > connectivity failed once, or twice, or X-times? How long do I keep this > > track: 1h, one day, one week, forever? > > > > Would it be possible to be more specific and give further guidance? E.g. > > how are these points implemented in the existing implementations? > > > This was the original goal when we started working on this draft. As work > progressed it was clear that getting consensus on a specific algorithm or > any specific value recommendations would be very hard to achieve. Some > people care about IPv4 others about IPv6 and so on. But I do think since > this is IETF work we have an obligation to push IPv6 friendly solutions. > > So the outcome of the work in the WG was a BCP that acknowledges that > there is a problem that implementors should be aware of with guidelines on > what values from the ICE RFC could safely be altered to fix the problem. > > I would also expect any explicit guidelines to change over time. I think > implementers are getting used to that now and are collecting metrics that > they can use to dynamically change the values. > > We can put wording like ”a good starting point might be ..”, and add some > text regarding metrics and changing conditions into the draft. This isn't my Discuss, so please focus on Mirja's feedback, but I find this explanation very helpful, and think your suggestion in this paragraph ( ^^ ) is a good one. Mirja and I did talk about this aspect of the draft during IESG evaluation, and I thought her Discuss was pointed in the right direction. So, thank you. Spencer > > > > ---------------------------------------------------------------------- > > COMMENT: > > ---------------------------------------------------------------------- > > > > Further, I think the term 'fairness' is just wrong here. The goal is to > > avoid delay in case there are connectivity problems with IPv6 in general, > > while still prioritizating IPv6. For me, that's nothing about fairness. > > > > > That is the goal, but to achieve that goal we need a “fair” distribution > if IPv4 and IPv6 candidates in the checklist. > Or a solution that is “free from bias or injustice”. (from > http://www.dictionary.com/browse/fairness) > > Based on that (I am not a native speaker..), I thought the name was fine. > I do agree that it might not be perfect or even close, so any new > suggestions would be much appreciated. > > > Thanks for thorough review. Much appreciated. > > .-. > Pål-Erik > > > > >
- [Ice] Mirja Kühlewind's Discuss on draft-ietf-ice… Mirja Kuehlewind
- Re: [Ice] Mirja Kühlewind's Discuss on draft-ietf… Pal Martinsen (palmarti)
- Re: [Ice] Mirja Kühlewind's Discuss on draft-ietf… Spencer Dawkins at IETF
- Re: [Ice] Mirja Kühlewind's Discuss on draft-ietf… Mirja Kühlewind