[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Edits to Teredo Security concerns

To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Rémi Denis-Courmont <rdenis@simphalempin.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, James Woodyatt <jhw@apple.com>, Christian Huitema <huitema@windows.microsoft.com>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: Edits to Teredo Security concerns
From: Jim Hoagland <jim_hoagland@symantec.com>
Date: Thu, 05 Jul 2007 19:21:53 -0700
Cc: v6 ops <v6ops@ops.ietf.org>
In-reply-to: <468D39C1.9090508@ericsson.com>
User-agent: Microsoft-Entourage/11.3.3.061214

On 7/5/07 11:34 AM, "Suresh Krishnan" <suresh.krishnan@ericsson.com> wrote:

>    * It is easy to identify and filter Teredo packets
>    Action: I will replace section 3 with a simple way of identifying and
> filtering Teredo as follows
>       Inbound traffic
>       ===============
>       src_port==3544 identifies Teredo packets
> 
>       Outbound traffic
>       ================
>       dest_port==3544 identifies Teredo packets

This would only cover 3.2 (filtering).  As this does not find content
packets (only Teredo overhead packets), this cannot cover 3.1 (inspection).

-- Jim

Follow-Ups:
- Re: Edits to Teredo Security concerns
  - From: Rémi Denis-Courmont <rdenis@simphalempin.com>

References:
- Edits to Teredo Security concerns
  - From: Suresh Krishnan <suresh.krishnan@ericsson.com>

Prev by Date: Re: I-D ACTION:draft-nward-v6ops-teredo-server-selection-00.txt
Next by Date: Re: I-D ACTION:draft-nward-v6ops-teredo-server-selection-00.txt
Previous by thread: Edits to Teredo Security concerns
Next by thread: Re: Edits to Teredo Security concerns
Index(es):
- Date
- Thread