Re: Barry Leiba's No Objection on draft-ietf-6man-ra-pref64-08: (with COMMENT)

Jen Linkova <furry13@gmail.com> Tue, 17 December 2019 06:16 UTC

Return-Path: <furry13@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 24DA11200C7; Mon, 16 Dec 2019 22:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 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_HELO_NONE=0.001, 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 6e96nt-3WISA; Mon, 16 Dec 2019 22:16:06 -0800 (PST)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 C12C8120059; Mon, 16 Dec 2019 22:16:06 -0800 (PST)
Received: by mail-qt1-x830.google.com with SMTP id j5so7870890qtq.9; Mon, 16 Dec 2019 22:16:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=D13MPRcbS5vJGFbADrFZ2RYeiZjBo7LiH6V0d/4Ti74=; b=YwNrddamxJUxWa/OoR5QKsL16tPAsBk2mknZ4h+DG+8GUY4JBH875H6QpT3MVcwHGg jAKTFWnLiNsHNHnOMgVi8lgxkBXCyEod5pUB8STaqdbSLVOfEHmlB7VMwNypdLs9aCQ9 z2g0Sj/MFvmZCRpKcSxPiD502xnw84fH5XP6kyx6fnUaxkhdRIjWNLYy7yUndnNhJ0bV xk3/tYzLt5UjHB3OjE3gdhqrXYM5+nodzEEuSiI8u5rVuwmWw4NenYwYkeAGmRkVv4bI 4bTB7sw6DE+iH9EkggqUezQccg3HbASwI3n4tBnzFxI5VjebAuPqKJ6XM0oKX4IEjXi0 4auw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=D13MPRcbS5vJGFbADrFZ2RYeiZjBo7LiH6V0d/4Ti74=; b=JPV/Ez1gii1HHho1bd2aSjMz0rnhQf69IIdBx5xfrMyA95AOOMERStmlk8BvdEXdeq gN75nLTY0vw07OLaGAXg3HFHrdYO4hYj4iFhSf7dIYe0cGXq5ay1Xa6mYOKsD9WlO4tk CA423N+uPa9Wqo2fl/L1NFvlMnOpg4VDElzI5YqbW3Q2Q0ClQhKuY6fQnfxRqJGvLFQh jfHpnTcV/xdLLGXFNaJ5gAg0/UWedP0NfT6l++r8jibprQaiQqJNwCJgQjfh0b90m151 mYFeQZrz5OjqEEM6xJjZTwf1gQ9O1Lw0ZIkG0+W9U9mvzOYA0ZBTuFcbia8I1h+uYm1E GYrQ==
X-Gm-Message-State: APjAAAX+0FMMT+hK/xW0r6d4xNUIScA2Oo47ry1jTrjVWsTmzDdQMbsL Dn9LDfkjjCMmbrU7+LD0kYj/E7uNZnsYyAUkvvI=
X-Google-Smtp-Source: APXvYqzGN1GT205oHpjr9cmHM1iZkNg9CHEr4Dq3EAw7jJiICZifiBhIC7PUYKPYj1GiWLNJz+nvI3PgWMeS8UJ8VhQ=
X-Received: by 2002:ac8:7501:: with SMTP id u1mr3091163qtq.149.1576563365812; Mon, 16 Dec 2019 22:16:05 -0800 (PST)
MIME-Version: 1.0
References: <157655824890.24496.6907121559908698996.idtracker@ietfa.amsl.com>
In-Reply-To: <157655824890.24496.6907121559908698996.idtracker@ietfa.amsl.com>
From: Jen Linkova <furry13@gmail.com>
Date: Tue, 17 Dec 2019 17:15:54 +1100
Message-ID: <CAFU7BARUBnaZ2VxH50TwEzMXdK1SUQC+Pni9pV8J9jdXbrQY4Q@mail.gmail.com>
Subject: Re: Barry Leiba's No Objection on draft-ietf-6man-ra-pref64-08: (with COMMENT)
To: Barry Leiba <barryleiba@computer.org>
Cc: The IESG <iesg@ietf.org>, 6man <ipv6@ietf.org>, 6man Chairs <6man-chairs@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, draft-ietf-6man-ra-pref64@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zpnkgKAZ4EfL6hw5XK9oGGXPFkM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 17 Dec 2019 06:16:08 -0000

Hi Barry,

On Tue, Dec 17, 2019 at 3:51 PM Barry Leiba via Datatracker
<noreply@ietf.org> wrote:
>    If the network operator desires to route different
>    parts of the IPv4 address space to different NAT64 devices, this can
>    be accomplished by routing more specifics of the NAT64 prefix to
>    those devices.
>
> What does “more specifics” mean here?  I don’t understand the sentence.

"more specific" as "more specific route".
Would the following sentence be more readable:

" If the network operator desires to route different parts of the IPv4
address space to different NAT64 devices, this can be accomplished by
routing more specific routes comprising  the NAT64 prefix to those
devices."
?

>    For example, if the operator is using the RFC1918
>    address space, e.g. 10.0.0.0/8 internally and would like to route
>    10.0.0.0/8 through NAT64 device A and the rest of the IPv4 space
>    through NAT64 device B, and the operator's NAT64 prefix is
>    2001:db8:a:b::/96, then the operator can route
>    2001:db8:a:b::a00:0/104 to NAT64 A and 2001:db8:a:b::/96 to NAT64 B.
>
> This sentence is too long and cumbersome, and would benefit from being split
> (which would also fix some awkward missing commas).  How’s this?:
>
> NEW
>    For example, suppose an operator is using the RFC1918 address
>    space 10.0.0.0/8 internally.  That operator might want to route
>    10.0.0.0/8 through NAT64 device A, and the rest of the IPv4 space
>    through NAT64 device B.  If the operator's NAT64 prefix is
>    2001:db8:a:b::/96, then the operator can route
>    2001:db8:a:b::a00:0/104 to NAT64 A and 2001:db8:a:b::/96 to NAT64 B.
> END

Sounds good, thank you for the suggestion! I'll update the text.

-- 
SY, Jen Linkova aka Furry