[BEHAVE] RFC6052, RFC5735, and "non-global IPv4 addresses" with WKP
<teemu.savolainen@nokia.com> Tue, 22 May 2012 06:38 UTC
Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 104D421F8480 for <behave@ietfa.amsl.com>; Mon, 21 May 2012 23:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XCI6-HVNcuKM for <behave@ietfa.amsl.com>; Mon, 21 May 2012 23:38:43 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 741DF21F847F for <behave@ietf.org>; Mon, 21 May 2012 23:38:43 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (in-mx.nokia.com [10.160.244.22]) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q4M6cFUQ028954 for <behave@ietf.org>; Tue, 22 May 2012 09:38:35 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.58]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 May 2012 09:37:38 +0300
Received: from 008-AM1MPN1-052.mgdnok.nokia.com ([169.254.2.148]) by 008-AM1MMR1-003.mgdnok.nokia.com ([65.54.30.58]) with mapi id 14.02.0283.004; Tue, 22 May 2012 08:37:38 +0200
From: teemu.savolainen@nokia.com
To: behave@ietf.org
Thread-Topic: RFC6052, RFC5735, and "non-global IPv4 addresses" with WKP
Thread-Index: Ac035EdMZAkwY9XkQbuhwSq5iWSzUw==
Date: Tue, 22 May 2012 06:37:37 +0000
Message-ID: <916CE6CF87173740BC8A2CE44309696204380A2B@008-AM1MPN1-052.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-titus-version: 3.3.8.1
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IpQxMUXtONfvl1934VOO1ElboOZ10+9WOY+xpTcPXUBalvop1myCjQCPWcttFSopdR45JSYd6D7P0k9sgIE94OPb8hdtCcYiigi2dXzCDt8d7+YolIEh5IwbaieNVzGPBqM8SRLiEoEgrOj5JybYFHVbAwI8mjI8n4OvL6IFtzsSIhXsxowJZ/JyzvUq69yu1bhhivoDK6/A4htDBJkKMbgDt/GQS6c7GawlRPgEvp6bJOGH7jPIBlL00Z0RQ42cig==
x-originating-ip: [10.163.19.151]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 22 May 2012 06:37:38.0877 (UTC) FILETIME=[61A3B6D0:01CD37E5]
X-Nokia-AV: Clean
Subject: [BEHAVE] RFC6052, RFC5735, and "non-global IPv4 addresses" with WKP
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 06:38:44 -0000
Hi, RFC6052 says in section 3.1: -- The Well-Known Prefix MUST NOT be used to represent non-global IPv4 addresses, such as those defined in [RFC1918] or listed in Section 3 of [RFC5735]. -- After reading the sentence, again, and few times more, does it mean WKP *can* be used to represent *global* IPv4 addresses listed in Section 3 of RFC5735? If they can be used with WKP, are all of these address blocks considered global: - 192.88.99.0/24 - 6to4 relay anycast address - these can appear in public Internet - 192.0.0.0/24 - IETF protocol assignments - The RFC5735 does not really state if that block is global or not.. - 224.0.0.0/4 multicast block I'm asking this clarification as I'm thinking what could be good IPv4 addresses for well-known names used for NAT64 heuristic discovery. And maybe if 192.0.0.0/24 can be considered global in the spirit of RFC6052, that might be best place to get addresses. Best regards, Teemu
- [BEHAVE] RFC6052, RFC5735, and "non-global IPv4 a… teemu.savolainen
- Re: [BEHAVE] RFC6052, RFC5735, and "non-global IP… Christian Huitema
- Re: [BEHAVE] RFC6052, RFC5735, and "non-global IP… teemu.savolainen
- Re: [BEHAVE] RFC6052, RFC5735, and "non-global IP… SM
- Re: [BEHAVE] RFC6052, RFC5735, and "non-global IP… Dave Thaler