Re: AD Evaluation : draft-ietf-6man-ra-pref64-06

Jen Linkova <> Mon, 04 November 2019 03:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BE2BD120121; Sun, 3 Nov 2019 19:38:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.748
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vnFT1srksFyi; Sun, 3 Nov 2019 19:38:44 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 420E71200FD; Sun, 3 Nov 2019 19:38:44 -0800 (PST)
Received: by with SMTP id 205so14932109qkk.1; Sun, 03 Nov 2019 19:38:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=SwD3d5MC/6GPiZtRS84YdAmwX28i7vSl8y+O7orho3A=; b=HmMmv3jXGIPBtMrMRmEtnuGsioQR+QUaOinWkExtVCbC68ZLPrtHQB1TDKr7tBOvxP dYd8Hjij9iln7Djmv1gcd+yBA6F0Nbws/NbtZHd32c9qbTtczg2aRd+H44uDCHsrfoXK DVGoN2SA8VO8cR2zELxUiOOyP6sOlMnkpy2Pr9sxTCHvjwgYve+TIwYzdY9tdaWkh1k6 5XmGMLbsBoZDlYbJsMmYs70VUAVUHYsOWWHHxOFgSxwU1eQq4GLvhXSEbqbugoN7ONX+ 8mCdZFxdVbViDlj32ZcnZj/5ez1eVw0tbQYVRMMJ7he0kbXFkKw12nOIiEpBloi1byCq iVMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=SwD3d5MC/6GPiZtRS84YdAmwX28i7vSl8y+O7orho3A=; b=n2/zRjmEiwX5Rv8JoFXILPxtWgxTnBTLDNp12J/Z/UcKJcY6+FIPmL4ZAtBMbb6TRS hqtUomnHvG4tnqpcnBLr1r83bQc8ZjFiSyGcXmdzs3Tu9LLe4KlZ/PRCYeqiAAVI1irn 2vor1SHNR2HtN4OiYwMpEce664qBEiIDx67bWF2ZZsqQun817+T6bmCui2+Abtl4wqw0 jl8N8IjeSdvocDFMKKXpkCSyu5HDBh7IundmPFkqewXTWdJEjf6kQrq/lrgAYUmlnRpv Dg+Sb6xeb0P86gddYILbUt7OyUKWzgc6CiYh0WSxHahXSHvnkkckrlIIqzKGE2TrrceO YA2Q==
X-Gm-Message-State: APjAAAX0hGWhKvE0nqFVHqwdKJiw7luvAdzs8/1EQtoFt523aBlJaQCu MidtoSsfiOV4hrrO5YCqnVJpwcFd5Lw/rLPKyo7X5m3F
X-Google-Smtp-Source: APXvYqxbvpqvo3xRpV1WRoplulIJI8GUfY6Aw3tZb106mhP973/p8cclW00W0QUVn7BAxZgePygOZNC5mluBbH90hzU=
X-Received: by 2002:ae9:c119:: with SMTP id z25mr16506864qki.417.1572838722962; Sun, 03 Nov 2019 19:38:42 -0800 (PST)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Jen Linkova <>
Date: Mon, 4 Nov 2019 14:38:31 +1100
Message-ID: <>
Subject: Re: AD Evaluation : draft-ietf-6man-ra-pref64-06
To: Suresh Krishnan <>
Cc: "" <>, 6man WG <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Nov 2019 03:38:46 -0000

On Mon, Nov 4, 2019 at 2:08 PM Suresh Krishnan <> wrote:
> >> Please use a documentation prefix, say, instead of the RFC1918 address currently used in the example.
> >
> > Actually I'd agree with Lorenzo here..IMHO case describes a
> > realistic scenario while 192.0.2/024 would look a bit artificial.  If
> > the text was saying 'if the operator would like to route all private
> > address space  through NAT64 device A' instead of
> > 'if the operator would like to route through NAT64 device
> > A' we would not be using the example address space here, would we?
> >
> > Would it be better if that sentence says:
> > ''For example if the operator would like to route RFC1918 address
> > space, e.g.  through NAT64 device A’?
> I think this formulation is a bit better but I liked Mark Smith’s idea on my Additional Documentation Prefixes subthread (Thanks Mark!!) of using x’s instead of the 0’s here to obfuscate. Then it will be clear to readers that it is private space while not being directly usable. i.e. do something like
> "For example if the operator would like to route RFC1918 address
> space, e.g. 10.x.x.x/8  through NAT64 device A"

If '/8' is used then there is no difference between '' and
'10.x.x.x/8' and 'x.x.x' would only confuse a reader, IMHO.
Please note that we are not trying to pick up any arbitrary prefix but
instead discussing a practical example on 'how to treat NAT64 traffic
for RFC1918 address space differently from the Internet traffic. Also,
using '' is easy as it translated to 'a00' in
2001:db8:a:b::a00:0/104 which, I believe, easy to comprehend.

If you think that the explicit mention of RFC1918 makes the
formulation better, how about this:
"For example if the operator is using private address space
internally and would like to route RFC1918 addresses through NAT64
device A’

> >> * Section 5
> >>
> >> The use of the term “lifetime” or “life time” to denote both the intended period of use and the value of the Lifetime field which is one-eighth of the intended value is a bit confusing. Can you deconflict this by calling the field “ShortLifetime" or something similar?
> >
> > How about 'Lifetime Multiplier’?
> I would have assumed that the multiplier in this case would actually be 8. How about “Scaled Lifetime”? Does that work?

Heh, I was thinking the same and actually renamed it to 'Lifetime
Multiplicand' but after discussing it with Lorenzo the idea was
Scaled Lifetime would do, thanks!

SY, Jen Linkova aka Furry