Re: Question for w.g. on <<draft-ietf-6man-ra-pref64-04>
Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 10 September 2019 11:28 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 DE20C120071 for <ipv6@ietfa.amsl.com>; Tue, 10 Sep 2019 04:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.631
X-Spam-Level:
X-Spam-Status: No, score=-1.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 OkjGRcE49eHx for <ipv6@ietfa.amsl.com>; Tue, 10 Sep 2019 04:28:54 -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 30CC512004C for <ipv6@ietf.org>; Tue, 10 Sep 2019 04:28:54 -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 x8ABSqU4028015 for <ipv6@ietf.org>; Tue, 10 Sep 2019 13:28:52 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 71D65205C06 for <ipv6@ietf.org>; Tue, 10 Sep 2019 13:28:52 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 6745C205C03 for <ipv6@ietf.org>; Tue, 10 Sep 2019 13:28:52 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8ABSqJC018486 for <ipv6@ietf.org>; Tue, 10 Sep 2019 13:28:52 +0200
Subject: Re: Question for w.g. on <<draft-ietf-6man-ra-pref64-04>
To: ipv6@ietf.org
References: <6C018A55-208A-4BB5-9DDD-9C035A882227@gmail.com> <CAAedzxohoZzHbZ0_Ny-UDXeAsXcbSPAR4EQyThk-3WQV1W2T9Q@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <1397f6f3-c70e-adb5-46e8-25f28692e29e@gmail.com>
Date: Tue, 10 Sep 2019 13:28:52 +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: <CAAedzxohoZzHbZ0_Ny-UDXeAsXcbSPAR4EQyThk-3WQV1W2T9Q@mail.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/CjHEi6gjbO06jy6gD2I4Tg9qovQ>
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, 10 Sep 2019 11:28:56 -0000
Something like this? 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Prefix Length |!=0 prefixbytes| Padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | s6_addr32_0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | s6_addr32_1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | s6_addr32_2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Le 10/09/2019 à 07:20, Erik Kline a écrit : > How about a 3rd/Nth format? One whereby it's still possible to specify > a /96 but you don't have to include all the trailing zero-valued bytes? > > My apologies if this has been raised already. > > 1st 8 bytes: { > uint8_t type = IANA_TBD; > uint8_t len = 2 || 3; /* octets */ > uint16_t lifetime; /* same as other lifetimes, no tinkering */ > > uint8_t prefix_len; /* <= 96 */ > uint8_t number_of_nonzero_prefix_bytes; /* <= 12 */ > uint16_t padding; /* send: zero, recv: ignored */ > } > > prefix_len tells a client where to append the IPv4 address, and > number_of_nonzero_prefix_bytes tells the client when it can stop copying > prefix bytes out of this option. > > 2nd 8 bytes { > uint32_t s6_addr32_0; > uint32_t s6_addr32_1; > } > > 3rd 8 bytes /* if necessary */ { > uint32_t s6_addr32_2; > uint32_t padding; /* send: zero, recv: ignored */ > } > > Note that with trivial effort we could also have some indication in the > first 8 bytes that the prefix is the WKP, and if so limit the option to > just 1 8-octet entry. > > On Mon, 9 Sep 2019 at 11:38, Bob Hinden <bob.hinden@gmail.com > <mailto:bob.hinden@gmail.com>> wrote: > > 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. > > The merits of these formats has been discussed. > > Please read the discussion and respond with your preference. It > would be good to hear from people who haven’t responded so far. > > Thanks, > Bob > > > > > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org <mailto:ipv6@ietf.org> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- >
- Question for w.g. on <<draft-ietf-6man-ra-pref64-… Bob Hinden
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Erik Kline
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Alexandre Petrescu
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Alexandre Petrescu
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Bob Hinden
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Erik Kline
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Alexandre Petrescu
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Gyan Mishra
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Jen Linkova
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Gyan Mishra
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Jen Linkova
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Ole Troan
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Bob Hinden
- Re: Question for w.g. on <<draft-ietf-6man-ra-pre… Gyan Mishra