Re: Teredo for reducing search space (was: [dhcwg] Review of draft-ietf-v6ops-scanning-implications)

Alexandru Petrescu <alexandru.petrescu@motorola.com> Mon, 04 December 2006 15:38 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrFtN-0007z4-EN; Mon, 04 Dec 2006 10:38:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrFtL-0007wn-QR for dhcwg@ietf.org; Mon, 04 Dec 2006 10:38:03 -0500
Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GrFtK-0005q3-ID for dhcwg@ietf.org; Mon, 04 Dec 2006 10:38:03 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-4.tower-119.messagelabs.com!1165246584!9450746!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 17117 invoked from network); 4 Dec 2006 15:36:24 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-4.tower-119.messagelabs.com with SMTP; 4 Dec 2006 15:36:24 -0000
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id kB4FWcQg009164; Mon, 4 Dec 2006 08:32:39 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id kB4FWbjI012017; Mon, 4 Dec 2006 09:32:37 -0600 (CST)
Message-ID: <45743F95.7080409@motorola.com>
Date: Mon, 04 Dec 2006 16:32:37 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Teredo for reducing search space (was: [dhcwg] Review of draft-ietf-v6ops-scanning-implications)
References: <C6F00B58-D011-4490-BBCE-0B770644A1FB@cisco.com>
In-Reply-To: <C6F00B58-D011-4490-BBCE-0B770644A1FB@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: David Kessens <david.kessens@nokia.com>, Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org, Mark Townsley <townsley@cisco.com>, v6ops@ops.ietf.org, Stig Venaas <venaas@uninett.no>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Teredo and 6to4 are listed in "Transition Methods".

I would list knowledge of Teredo right in the section "Reducing the IPv6
Search Space".  An IPv6 worm knowing an IPv4 hitlist address could try
the full /128 IPv6 as a hitlist address too.

/64 Teredo Node Identifier not only uses the IPv4 address to derive the
IPv6 address but also a UDP port number (not mentioned in the draft, it
just says "2002:V4ADDR::V4ADDR").  Teredo also offers to discover all
Teredo Clients within a subnet, via a publicly-known reserved IPv4
multicast address.  A worm would take advantage of that too, to reduce
number of scans.

Alex

Fred Baker wrote:
> The v6ops working group is approaching a working group last call on 
> draft-ietf-v6ops-scanning-implications within the coming few weeks.
> We would appreciate a review from your working group of this document
>  before we do so. How that is done is up to you; you may designate
> one or more reviewers, or simply conduct the review on your mailing
> list, or whatever else suits you. But please respond to the authors
> copying v6ops within the coming four weeks if you would.
> 
> Thank you for your help in this.
> 
> _______________________________________________ dhcwg mailing list 
> dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
> 


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg