Question about TEREDO prefix described in RFC 6890
MAWATARI Masataka <mawatari@jpix.ad.jp> Thu, 30 January 2014 13:21 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 9CA9B1A020C for <ipv6@ietfa.amsl.com>; Thu, 30 Jan 2014 05:21: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 Tn5JLIIwG-KA for <ipv6@ietfa.amsl.com>; Thu, 30 Jan 2014 05:21:29 -0800 (PST)
Received: from mail-gw.kbmail.jp (mail1185.kbmail.jp [106.187.230.185]) by ietfa.amsl.com (Postfix) with ESMTP id E72A41A01FC for <ipv6@ietf.org>; Thu, 30 Jan 2014 05:21:28 -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 1C84011C0002 for <ipv6@ietf.org>; Thu, 30 Jan 2014 22:21:24 +0900 (JST)
Received: from ([202.90.12.5]) by bmlmta011.kbmail.jp id 52ea51d3000a41bb000062dc000063256800000f02e5; Thu, 30 Jan 2014 22:21:23 +0900
Date: Thu, 30 Jan 2014 22:21:23 +0900
From: MAWATARI Masataka <mawatari@jpix.ad.jp>
To: ipv6@ietf.org
Subject: Question about TEREDO prefix described in RFC 6890
Message-Id: <20140130222122.3484.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
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: Thu, 30 Jan 2014 13:21:30 -0000
Dear colleagues, I have been wondering about TEREDO Prefix (2001::/32). The following table on the RFC 6890 says that global of 2001::/32 is false. But actually 2001::/32 is on the global routing table now. If they reject anycasted 2001::/32 by ingress prefix filter, will TEREDO be workable? If I have any missing points, please let me know. --- http://tools.ietf.org/html/rfc6890#section-2.2.3 <snip> +----------------------+----------------+ | 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 | False | | Reserved-by-Protocol | False | +----------------------+----------------+ Table 23: TEREDO <snip> --- Thanks in advance. Regards, Masataka MAWATARI
- 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