Re: RFC4941bis implementations
Gyan Mishra <hayabusagsm@gmail.com> Thu, 09 April 2020 20:35 UTC
Return-Path: <hayabusagsm@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 023CF3A0DDE; Thu, 9 Apr 2020 13:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 QjPxmpEXe-TV; Thu, 9 Apr 2020 13:35:23 -0700 (PDT)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 992FF3A0DE0; Thu, 9 Apr 2020 13:35:23 -0700 (PDT)
Received: by mail-il1-x12c.google.com with SMTP id t11so42111ils.1; Thu, 09 Apr 2020 13:35:23 -0700 (PDT)
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; bh=m4Jme3LqR663yXSrNykDEz9N3TM+U/Mot/4djtmHAPA=; b=rjKaceaoDSitSapLW8fVJFcsr7UP3cJ6MOgsLbcD0b7U06czuxs5fMDeKJFIaOzHHB +1aEjCCEVdmwcvKzeOKFjQRjSkeM5SVMH13zlAINUcrBRuyz2W2BBbiyidLmms6E94Xf YkEjv402dQBpieh6Nplo9dsd7zkXIvRQ6tpMOnigDjkFBRlJwQquVmamFVOJ3kWA25Qb Rv/b/W/hcxytUHet63Ct3rS73xCALGYodh0I1TKhBLZymBUimRIubrv2zktitwxFd0S1 3/WUTlt//mRSilmIF6t6go5LPCcinhP35Dc8BIttceP+dl+Ia4uLPsUQuE0VGRWrdJnj Lvzg==
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; bh=m4Jme3LqR663yXSrNykDEz9N3TM+U/Mot/4djtmHAPA=; b=JE7yueN0kMk4FjwOixC3a3QN3ctx5uDU3HAMlj66WPKrEYxkO5g5aSULGZt4ZMDZpc b0c9ZvkyT7+TScDaFmFys7rr93uLBJLrZP6OJYeUJmdTVp8ALaa/K6QSVUPnC/QJT14L CUt6WHHMHchguij3mIptT+slE03PLglIpQt2RvgAvGGfenAfgOaHi6AIML3xLyu+HzEy O7YvggHHS2V+/Y6VJx7Nt1pV1bU0DQ2cuQNfVeu7ai35QtSOHduWV8RYhdce3jgchrV1 e7NXQeFZKjZ1NN68htVPXvRYpSOivXiB5HICJhIgt9FKmS7ZX12QzpnANxt5HoRWlrvn Itcw==
X-Gm-Message-State: AGi0PubH4X3zU5C7gwZ/4buP9YwuriWPggSCY+Du7jwuRfhDkGQapK3v sIwXT1/GBQTb6OngjxEqRG47ifPsNcSY4rsPTQE=
X-Google-Smtp-Source: APiQypLDXgpY8lu/tWSMqtZ1uqi1L1uD5YkprWPGIwzW5FQd+I7Sh8ni1KWZqgxL+5yz+D5SJ7MaA3oS2f+fAtjKMrc=
X-Received: by 2002:a92:96c6:: with SMTP id g189mr1681490ilh.276.1586464522530; Thu, 09 Apr 2020 13:35:22 -0700 (PDT)
MIME-Version: 1.0
References: <7d65f86a-7a82-6139-b455-a27046496c52@si6networks.com>
In-Reply-To: <7d65f86a-7a82-6139-b455-a27046496c52@si6networks.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Thu, 09 Apr 2020 16:35:11 -0400
Message-ID: <CABNhwV2x0=CzV_Usc0AkuyL3eR0qngK7D=oF4tezhH+TeRPnEw@mail.gmail.com>
Subject: Re: RFC4941bis implementations
To: Fernando Gont <fgont@si6networks.com>
Cc: "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000050747f05a2e18e29"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Q26QGKB8kIFtfbcvsEpxWVYzoW4>
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: Thu, 09 Apr 2020 20:35:26 -0000
Fernando I thought for the privacy extension VL PL changes as the final changes in the discussion as we went through so many permutations and many threads just so I am clear from what I recall. So what was on the table was VL=2 PL=2. Then for a balance of issues with long lived flows using invalid address and trying to reduce the number of deprecated addresses as far down as possible that can exist to help with MTTR troubleshooting we decided on finally VL=PL=2. Reduces the default Valid Lifetime for temporary addresses: The default Valid Lifetime for temporary addresses has been reduced from 1 week to 2 days, decreasing the typical number of concurrent temporary addresses from 7 to 2. This reduces the possible stress on network elements (see Section 4 <https://tools.ietf.org/html/draft-ietf-6man-rfc4941bis-09#section-4> for further details). Thanks Gyan On Thu, Apr 2, 2020 at 1:28 PM Fernando Gont <fgont@si6networks.com> wrote: > Folks, > > FWIW, I produce a patch for Linux kernel (net-next) that implements > rfc4941bis: > https://www.gont.com.ar/code/fgont-patch-linux-net-next-rfc4941bis.txt > (up & running here). > > I've submitted it to the netdev list already. > > And should have a patch for the FreeBSD kernel today. > > Not sure if this might be useful for a "disposable" (to be removed by > the RFC-Ed section), but I guess might be of use for the shepherd's > writeup? > > Thanks! > > Cheers, > -- > Fernando Gont > SI6 Networks > e-mail: fgont@si6networks.com > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492 > > > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > -- Gyan Mishra Network Engineering & Technology Verizon Silver Spring, MD 20904 Phone: 301 502-1347 Email: gyan.s.mishra@verizon.com
- RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Alexandre Petrescu
- Re: RFC4941bis implementations Suresh Krishnan
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Florian Obser
- Re: RFC4941bis implementations Alexandre Petrescu
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Fernando Gont
- RE: RFC4941bis implementations Manfredi (US), Albert E
- Re: RFC4941bis implementations Mark Smith
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations otroan
- Re: RFC4941bis implementations Lorenzo Colitti
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Mark Smith
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Bob Hinden
- Re: RFC4941bis implementations Tim Chown
- Re: RFC4941bis implementations Gyan Mishra