IETF Logo Mail Archive

Re: [v6ops] Routers are hosts too! (Re: I-D Action: draft-ietf-v6ops-host-addr-availability-04.txt)

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Thu, 07 January 2016 11:58 UTC

Return-Path: <evyncke@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0538E1A891D for <v6ops@ietfa.amsl.com>; Thu, 7 Jan 2016 03:58:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Bo3VvqKpAnQZ for <v6ops@ietfa.amsl.com>; Thu, 7 Jan 2016 03:57:58 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A4551A891A for <v6ops@ietf.org>; Thu, 7 Jan 2016 03:57:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8732; q=dns/txt; s=iport; t=1452167878; x=1453377478; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=hTZH0mzfEoVnVyBbb9re78np+VhgVzJdTK1ub72R6lk=; b=TDwazGJ1jfT0jWVJxwFhNyV/bsOCsps5ujiSt2NqhNi1N/jyjY+PLcF5 vw4kHl7EmawsVioTeDSDXXRKDbZxe4dYOEp57DDHM32MqW+PPXGKNJy9R Dpw0Y/ossQE9Pkbh3s9o2AoiJPDfV8/E4DW+Nb7SBFL1o8VgVTL/NNJhj 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D1AQDoUY5W/4wNJK1egm5MgT8GiFOzUwENgWSGDwIcgQM4FAEBAQEBAQGBCoQ0AQEBBCNWEAIBCBEDAQIkBAMCAgIfERQJCAIEAQ0FiBoDErBsjWgNgm0BAQEBAQEBAQEBAQEBAQEBAQEBAQEYhlYBhH6CT4IognyBSQWTCoQBAYtdgXiOe4Zwh1wBIAEBQoIRHB2BQHIBhFiBCAEBAQ
X-IronPort-AV: E=Sophos; i="5.20,532,1444694400"; d="scan'208,217"; a="64184106"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Jan 2016 11:57:57 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u07BvvOo026160 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 7 Jan 2016 11:57:57 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 7 Jan 2016 06:57:56 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1104.009; Thu, 7 Jan 2016 06:57:56 -0500
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Mark Smith <markzzzsmith@gmail.com>, Fred L Templin <Fred.L.Templin@boeing.com>
Thread-Topic: [v6ops] Routers are hosts too! (Re: I-D Action: draft-ietf-v6ops-host-addr-availability-04.txt)
Thread-Index: AQHRSMitV7fnMhmxM0KqvFEotlF1cZ7wWE2A
Date: Thu, 07 Jan 2016 11:57:56 +0000
Message-ID: <D2B410BA.63D18%evyncke@cisco.com>
References: <CAO42Z2zU12bHqh2DiCeT2MOE6txh1cKbU9DasSjozQ166knVdQ@mail.gmail.com>
In-Reply-To: <CAO42Z2zU12bHqh2DiCeT2MOE6txh1cKbU9DasSjozQ166knVdQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.9.151119
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.56.4]
Content-Type: multipart/alternative; boundary="_000_D2B410BA63D18evynckeciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/xunj1w-C2vKsUIyDFrx5dCWUHT4>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Routers are hosts too! (Re: I-D Action: draft-ietf-v6ops-host-addr-availability-04.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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 Jan 2016 11:58:00 -0000

Mark, +1 indeed on the statement that routers are hosts (i.e. They reply to ICMP & SNMP and even generate ICMP with their own global addresses -- else RFC 7014 --LLA-only -- should have been obvious)

Now, I respectfully disagree on the fact we have experience with host doing DHCP-PD: for sure about Linux (and even it is user space) but what about Windows? Or iOS (lowercase :-) )? Or ???

-éric

From: v6ops <v6ops-bounces@ietf.org<mailto:v6ops-bounces@ietf.org>> on behalf of Mark Smith <markzzzsmith@gmail.com<mailto:markzzzsmith@gmail.com>>
Date: mercredi 6 janvier 2016 22:24
To: Fred L Templin <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>>
Cc: "v6ops@ietf.org<mailto:v6ops@ietf.org> WG" <v6ops@ietf.org<mailto:v6ops@ietf.org>>
Subject: [v6ops] Routers are hosts too! (Re: I-D Action: draft-ietf-v6ops-host-addr-availability-04.txt)


I think people might be getting a bit caught in the trap of thinking the separation between hosts and routers is a much stronger than it is.

Routers are universally hosts too. The distinction between a router and a host is that a router will also accept packets not sent to addresses assigned to the devices interfaces. It will then see what to do with them according to the route table, sending the packet where ever the  route table says or dropping them. That is all that makes it a router.

Routers are hosts too if there is anything at all above the IP layer that locally receives or locally originates packets using the router's IP addresses. So SNMP agents, ssh/telnet daemons and even BGP, OSPF and DHCPv6 processes are host processes.

People say there isn't much or any experience with hosts using addresses assigned via DHCPv6-PD. I don't agree, because every residential IPv6 CPE supporting DHCPv6 that is acquiring addresses via DHCPv6-PD, DNS settings, getting time via NTP or providing a web administrative interface is a host too.

Take one of these CPE, disable the LAN interface, attach a screen, keyboard and mouse, and run a spreadsheet or web browser on it and you have the type of host being discussed.

The only way for a router not to be a host would be if it specially didn't listen for packets addressed to its own addresses, so that all it ever did was forward non-local packets. You have no monitoring of it, no routing protocols, and would have to configure it via a serial cable.

Mark.

v2.46.0 | Report a Bug | By Email | System Status