Re: [v6ops] Mirja Kühlewind's No Objection on draft-ietf-v6ops-conditional-ras-05: (with COMMENT)

Jen Linkova <furry13@gmail.com> Wed, 01 August 2018 11:31 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 964EA130E55; Wed, 1 Aug 2018 04:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 knBcXYpiqBYd; Wed, 1 Aug 2018 04:31:37 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 C4717130E26; Wed, 1 Aug 2018 04:31:36 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id y17-v6so16540335ljy.8; Wed, 01 Aug 2018 04:31:36 -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:content-transfer-encoding; bh=SofnNR1GcO07luTCdmJ13qdlj+fg5sc4CP/cXFMWCSo=; b=lnUCQQQrV0MCvgzW0AKVORwUIuEvLWry0ywAVdXp+V8013YtVBy7OhjnkID70SnN5E eU2sbRLdSkavoZi0sA0TJ6/dWWoyvR+1Ugx2OscapHLL1/PRLC3IDJuP3Q5CaCHqrfpe fwcM++Z+8YbVEEd/Jui3F81nMzTeZUnQVkjBxaDKsdARtuSvlMRuf0V1WbR0tXnGmfWh wYVGf38L++Uvdx/m6oFFTcAy2n80LGjA2tiI48U+Z/NzNBd4TkFRhGlIsoeYQ8248WXh UDoGrlJ6e2i+PgpVYFA94PcTA620QNTmpbf1HyUlSgKkV8Ejf0JMzri74tFv6fC2+/K7 ayeA==
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:content-transfer-encoding; bh=SofnNR1GcO07luTCdmJ13qdlj+fg5sc4CP/cXFMWCSo=; b=tJlpIIl5BuC3FdWTr6j8DRgfPjtWBHQjeyAd/f/bj4o/nxtTKBRQm7912T32A/NDWE SahNewpyINDiwMDvSCwPbsU07Lj7eVrH0/n7757r/YlGtB5kS0PCN6w0+As16eeo0xiY Li+NccQ31MV0rUnNa4GawxqB5TG7PHMurKsZDZcsiqzoL9JvkqN3FMyaQGlTCRH3pmO8 +NDUnBAyqov6FxQ1N/6A0+aBLeLM6uiCtYbje7fLug9wBxZR93FoTYNKweEg1jHrdJiL pHmrS58iOcaN9n6mFEhwyUHVTiro1S/bzWA2fC/G0bn4dGhhFI6OiZAB+0fCGUuT5Tja 7XNg==
X-Gm-Message-State: AOUpUlG6/1Zg8h9z176nT3WE2+PXx0yCTQCQZBJaceVxBtUwfvNkZHdU 15xKxfc6F/YpwN5dnBzMFx7C5RNfbx2e9XB38WjziP5/
X-Google-Smtp-Source: AAOMgpdJ3QiiStZ0dZ1/AL7KCOOBA4puUKr37MVjcF1QP7fsk6jQ85cDtGYYkBAiDh2MAVptMfbo6XfYn9osH2rvRbw=
X-Received: by 2002:a2e:8743:: with SMTP id q3-v6mr16001836ljj.139.1533123094799; Wed, 01 Aug 2018 04:31:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:1d82:0:0:0:0:0 with HTTP; Wed, 1 Aug 2018 04:31:14 -0700 (PDT)
In-Reply-To: <153257466404.7274.1932006527579909279.idtracker@ietfa.amsl.com>
References: <153257466404.7274.1932006527579909279.idtracker@ietfa.amsl.com>
From: Jen Linkova <furry13@gmail.com>
Date: Wed, 01 Aug 2018 21:31:14 +1000
Message-ID: <CAFU7BAQNKx5oaEp25sUR3XJxt3f7CSaEgPM06nt43OMhjsvPyA@mail.gmail.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>
Cc: The IESG <iesg@ietf.org>, Russ White <russ@riw.us>, v6ops-chairs@ietf.org, V6 Ops List <v6ops@ietf.org>, draft-ietf-v6ops-conditional-ras@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/2PIRNopgHX2n4w7r-EZ2_kjQp-s>
Subject: Re: [v6ops] Mirja Kühlewind's No Objection on draft-ietf-v6ops-conditional-ras-05: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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, 01 Aug 2018 11:31:39 -0000

Hi Mirja,

Thanks a lot for your feedback!
-06 version has been submitted to address your comments:
https://tools.ietf.org/html/draft-ietf-v6ops-conditional-ras-06.

Also please see my responses inline:

> 1) The shepherd write-up says "The responsible Area Director is Ron Bonica."
> and questions 7 and 8 say "TBD"

I believe Warren has fixed those issues (thanks a lot, Warren!)

>and the RFC8174 biolerplate is missing...

Fixed.

> 2) It seems that ietf-rtgwg-enterprise-pa-multihoming should maybe be a
> normative reference (and that the abstract should be updated with the
> respective RFC number as soon as ietf-rtgwg-enterprise-pa-multihoming is
> published). Any even if it is not a normative reference, should those docs be
> published together in order to refer to the RFC in the abstract (instead of an
> draft)?

Ah, that's a tricky part...Initially I wanted
ietf-rtgwg-enterprise-pa-multihoming
to be a normative reference and those two documents published as a cluster.
However the main reason for writing this draft was to document
tactical solution available
right here right now, while we are waiting for the proper one to come.
So it would make sense to publish
the conditional RAs draft reasonably quick. Unfortunately
ietf-rtgwg-enterprise-pa-multihoming
has been in 'Publication Requested ' state for the last 51 days and
I'm afraid it might take a while
before we can get it published. So it looks to me that this draft
might be published independently (while
ietf-rtgwg-enterprise-pa-multihoming contains all
justifications/explanations on 'why SLAAC and not DHCPv6/ICMP error
messages'
it's still not really necessary to read the whole
ietf-rtgwg-enterprise-pa-multihoming to understand the solution
proposed
in draft-ietf-v6ops-conditional-ras...Or am I biased here?

> 3) Would it makes sense to also discuss what to do when one ISP is down but
> packets from that address space are received at the border router? Should those
> packet be forwarded to that ISP anyway or dropped? Or should they be forwarded
> to the other ISP with or without address translation?

I've added Section 3.2.8:
https://tools.ietf.org/html/draft-ietf-v6ops-conditional-ras-06#page-15

Please let me know if it does not address your concern.

> 4) It doesn’t seem right to me that the security consideration section is empty.

Updated it:
https://tools.ietf.org/html/draft-ietf-v6ops-conditional-ras-06#section-5

> 5) Lines are too long and therefore cropped in sec 3.2.1 and 3.2.2.

Fixed.

-- 
SY, Jen Linkova aka Furry