Re: Question about TEREDO prefix described in RFC 6890
MAWATARI Masataka <mawatari@jpix.ad.jp> Fri, 31 January 2014 01:24 UTC
Return-Path: <mawatari@jpix.ad.jp>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF791A0515 for <ipv6@ietfa.amsl.com>; Thu, 30 Jan 2014 17:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.908
X-Spam-Level: **
X-Spam-Status: No, score=2.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MANGLED_NAIL=2.3, SPF_PASS=-0.001] autolearn=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 totOrP-MyvTC for <ipv6@ietfa.amsl.com>; Thu, 30 Jan 2014 17:24:29 -0800 (PST)
Received: from mail-gw.kbmail.jp (mail2052.kbmail.jp [106.187.231.52]) by ietfa.amsl.com (Postfix) with ESMTP id 98F841A0518 for <ipv6@ietf.org>; Thu, 30 Jan 2014 17:24:25 -0800 (PST)
X-matriXscan-EoH:
Received: from bmlmta011.kbmail.jp (bmlmta011-MM [10.188.50.11]) by mail-gw.kbmail.jp (kbmail) with ESMTP id EF7DE6C0003 for <ipv6@ietf.org>; Fri, 31 Jan 2014 10:24:20 +0900 (JST)
Received: from ([202.90.12.1]) by bmlmta011.kbmail.jp id 52eafb440006e135000062dc000063256800000f14f5; Fri, 31 Jan 2014 10:24:20 +0900
Date: Fri, 31 Jan 2014 10:24:19 +0900
From: MAWATARI Masataka <mawatari@jpix.ad.jp>
To: simon.perreault@viagenie.ca, brian.e.carpenter@gmail.com
Subject: Re: Question about TEREDO prefix described in RFC 6890
In-Reply-To: <52EAABE5.3060009@gmail.com>
References: <52EA5FDC.3090309@viagenie.ca> <52EAABE5.3060009@gmail.com>
Message-Id: <20140131102419.46F9.8FE1F57E@jpix.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.65 [ja]
X-MXM-DELIVERY-TYPE: 3
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 31 Jan 2014 01:24:30 -0000
Dear colleagues, Thank you very much. I didn't notice fc00::/7. Based on your comments I wrote a modified version as below. If anyone have any similar comments, I'd like to report that as an errata. Thanks in advance. +----------------------+----------------+ | Attribute | Value | +----------------------+----------------+ | Address Block | 2001::/32 | | Name | TEREDO | | RFC | [RFC4380] | | Allocation Date | January 2006 | | Termination Date | N/A | | Source | True | | Destination | True | | Forwardable | True | | Global | N/A [RFC4380] | | Reserved-by-Protocol | False | +----------------------+----------------+ Table 23: TEREDO +----------------------+----------------+ | Attribute | Value | +----------------------+----------------+ | Address Block | fc00::/7 | | Name | Unique-Local | | RFC | [RFC4193] | | Allocation Date | October 2005 | | Termination Date | N/A | | Source | True | | Destination | True | | Forwardable | True | | Global | N/A [RFC4193] | | Reserved-by-Protocol | False | +----------------------+----------------+ Table 28: Unique-Local Kind Regards, Masataka MAWATARI * On Fri, 31 Jan 2014 08:45:41 +1300 * Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > On 31/01/2014 03:21, Simon Perreault wrote: > > Le 2014-01-30 08:21, MAWATARI Masataka a ecrit : > >> The following table on the RFC 6890 says that global of 2001::/32 > >> is false. > > > > Looks to me like an errata in RFC 6890... > > Agreed. The entry for 2002::/16 is better and that approach > would work for 2001::/32, I think: N/A, see [RFC4380]. > > Both of these prefixes are routed as if they are global > but they are special, so neither True nor False is correct. > > There is the same bug for fc00::/7, which is explicitly > of global scope but special: N/A see [RFC4193]. > > Brian
- Question about TEREDO prefix described in RFC 6890 MAWATARI Masataka
- Re: Question about TEREDO prefix described in RFC… Simon Perreault
- Re: Question about TEREDO prefix described in RFC… Brian E Carpenter
- Re: Question about TEREDO prefix described in RFC… MAWATARI Masataka