Re: [v6ops] [homenet] Tsinghua work on source/destination routing

Jen Linkova <furry13@gmail.com> Thu, 07 November 2013 23:34 UTC

Return-Path: <furry13@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63EA321E80E6; Thu, 7 Nov 2013 15:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level:
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 P+EBk6XBGArb; Thu, 7 Nov 2013 15:34:07 -0800 (PST)
Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com [IPv6:2607:f8b0:400d:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 38A7021E80DB; Thu, 7 Nov 2013 15:34:03 -0800 (PST)
Received: by mail-qe0-f50.google.com with SMTP id 1so1268699qee.9 for <multiple recipients>; Thu, 07 Nov 2013 15:34:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=7O5+0IPZlfYycRXZ63fTXsoFEt1xEUP2gAkfLHf8VPY=; b=Y6hzgmkGthS0k7kFOnKk8ajQR+nlB6wdYgohljjOQBHSzYoWAkjeJKc6XUCKEVW0PL DeASkE/F9uKgqnDQ/Pol3VWfr0R7et5s6ORCD/2slckuIhGGphLbJF39HnX+9UODuFLI WpCI+oRzgXxv/RgMks6SuSm2LExaeRqP/evbF6zMT3N2zQMyLC1WDo7wW9qvFPYXWSTQ h7q82BzPzPhfBpbpUqOGqO8Kc7ra0yeiM7Od19u1WSNTmDeMbPriTu8CMP6uCtNp8sea F8bW0rk6y9xXKAw0STkrn8sf3SbHM1V1zmIniMgYlfggFaFFHUYNrX8TFq7AfWeLD3DQ HNPw==
X-Received: by 10.224.162.211 with SMTP id w19mr18623220qax.59.1383867240454; Thu, 07 Nov 2013 15:34:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.100.195 with HTTP; Thu, 7 Nov 2013 15:33:40 -0800 (PST)
In-Reply-To: <527BE84E.2000205@gmail.com>
References: <F7C18630-1964-4AFD-8549-559D7582B114@cisco.com> <CAFU7BAQT=+B==8pvOYSsWnCvcMEVzy2nh8dAZZXHzYjwmedRpg@mail.gmail.com> <CAJE_bqfU8C+Tc2rQCZ=vpmfTDdOiGz-sd-G4QNBpHdwXDz9bqQ@mail.gmail.com> <27F73F5B-6095-43E1-ADBE-2E05E8071E3F@cisco.com> <527BE84E.2000205@gmail.com>
From: Jen Linkova <furry13@gmail.com>
Date: Fri, 08 Nov 2013 00:33:40 +0100
Message-ID: <CAFU7BATOG_Y4UtpRM9hu1qH7rV8_cxo0XHghrNt0xr5WUZuhiQ@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Routing WG <rtgwg@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>
Subject: Re: [v6ops] [homenet] Tsinghua work on source/destination routing
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2013 23:34:08 -0000

On Thu, Nov 7, 2013 at 8:21 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> I suspect it's some of each. The host should, I should think, set the hop limit to one on any packet that is to a link-local address, to ensure that the packet is not repeated by a broken router (apart from protocols that ask to have it set to 255 and have the receiving host check for that value). Also, upstream network's BCP 38 implementation sounds suspect, and I'm with Jen in wondering why a router forwarded the packet in the first place.
>
> Are you sure these packets come from hosts? There is a known case
> which is a router generating ICMP reply packets that has no GUA
> configured since all its peers are link-local.

I saw packets with link-local source/GUA destination coming from hosts
and from routers (I analyzed EUI-64-based IIDs) back in 2011. Now
majority of such traffic is TCP to our services and, again, IID checks
shows that these packets are from hosts.

-- 
SY, Jen Linkova aka Furry