Re: Question for w.g. on <<draft-ietf-6man-ra-pref64-04>

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 11 September 2019 08:55 UTC

Return-Path: <alexandre.petrescu@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 674F512083B for <ipv6@ietfa.amsl.com>; Wed, 11 Sep 2019 01:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
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 0_CNb7nlk68Q for <ipv6@ietfa.amsl.com>; Wed, 11 Sep 2019 01:55:05 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAA9B1200B2 for <ipv6@ietf.org>; Wed, 11 Sep 2019 01:55:04 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8B8t2sH029047; Wed, 11 Sep 2019 10:55:02 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 135C82031C2; Wed, 11 Sep 2019 10:55:02 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 04D7A202F30; Wed, 11 Sep 2019 10:55:02 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8B8t1j9006817; Wed, 11 Sep 2019 10:55:01 +0200
Subject: Re: Question for w.g. on <<draft-ietf-6man-ra-pref64-04>
To: Bob Hinden <bob.hinden@gmail.com>
Cc: IPv6 List <ipv6@ietf.org>
References: <6C018A55-208A-4BB5-9DDD-9C035A882227@gmail.com> <ac9315f1-6708-abbd-42d9-3fe8b57cf8fa@gmail.com> <4FA67CAC-3FC3-42F0-9AD2-C754EF6717F3@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <6c1546d1-c2e7-b428-1e7c-c320b34f0886@gmail.com>
Date: Wed, 11 Sep 2019 10:55:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <4FA67CAC-3FC3-42F0-9AD2-C754EF6717F3@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0MQATn8BwOenzrYff-VvNsfzI1g>
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: Wed, 11 Sep 2019 08:55:08 -0000


Le 10/09/2019 à 17:04, Bob Hinden a écrit :
> Alex,
> 
>> On Sep 10, 2019, at 4:30 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
>>
>>
>>
>> Le 09/09/2019 à 20:38, Bob Hinden a écrit :
>>> Hi,
>>>  From my reading of the list for <draft-ietf-6man-ra-pref64-04>, we have a choice between the format described in the draft:
>>>       0                   1                   2                   3
>>>       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |     Type      |    Length     |           Lifetime            |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |                                                               |
>>>      +                                                               +
>>>      |              Highest 96 bits of the Prefix                    |
>>>      +                                                               +
>>>      |                                                               |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      | Lowest bits (96-127) of the prefix (optional, if Length > 2)  |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      | Prefix Length |                  Reserved                     |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> This format supports two lengths of the option (20 & 28 bytes) and allows for different NAT64 prefix lengths in the 28 byte version.
>>> Based on the chairs comments and list discussion, the following format has been proposed:
>>>       0                   1                   2                   3
>>>       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |     Type      |    Length     |       Lifetime          |  PL |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |                                                               |
>>>      +                                                               +
>>>      |              Highest 96 bits of the Prefix                    |
>>>      +                                                               +
>>>      |                                                               |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> This allow for the ranges of prefix lengths (32, 40, 48, 56, 64) supported by NAT64 (RFC6052) and is 20 bytes long.
>>
>> I do not understand why the 8bit boundary and why the 32bit lower 64bit upper limits.  That is my oppinion.
> 
> That how it is defined in RFC6052.   See Section 2 of RFC6052.

Thank you for the pointer.  It says that the plen can only be like that: 
32, 40, etc.  It can't be 33, for example.

Alex

> 
> Bob
> 
>