Re: [v6ops] Last Call: <draft-ietf-v6ops-6204bis-09.txt> (Basic Requirements for IPv6 Customer Edge Routers) to Informational RFC

Mark Andrews <marka@isc.org> Thu, 28 June 2012 00:31 UTC

Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E1F11E8134; Wed, 27 Jun 2012 17:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.766
X-Spam-Level:
X-Spam-Status: No, score=-1.766 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 O66l0iSB4-To; Wed, 27 Jun 2012 17:31:13 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 544AD11E8133; Wed, 27 Jun 2012 17:31:10 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 71B2A5F99B2; Thu, 28 Jun 2012 00:30:55 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:7471:6721:a784:9471]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 78635216C33; Thu, 28 Jun 2012 00:30:53 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 49AF52208913; Thu, 28 Jun 2012 10:30:51 +1000 (EST)
To: Randy Bush <randy@psg.com>
From: Mark Andrews <marka@isc.org>
References: <20120627174957.18647.15377.idtracker@ietfa.amsl.com> <m2r4t0jx2l.wl%randy@psg.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6204bis-09.txt> (Basic Requirements for IPv6 Customer Edge Routers) to Informational RFC
In-reply-to: Your message of "Wed, 27 Jun 2012 10:53:38 -1000." <m2r4t0jx2l.wl%randy@psg.com>
Date: Thu, 28 Jun 2012 10:30:51 +1000
Message-Id: <20120628003051.49AF52208913@drugs.dv.isc.org>
Cc: IETF v6ops list <v6ops@ietf.org>, The IESG <iesg-secretary@ietf.org>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 00:31:14 -0000

In message <m2r4t0jx2l.wl%randy@psg.com>, Randy Bush writes:
> > - 'Basic Requirements for IPv6 Customer Edge Routers'
> >   <draft-ietf-v6ops-6204bis-09.txt> as Informational RFC
> 
> this document persists in confusing routing and forwarding.
> 
> there are no routing protocols, a la 1812, here.  there is confused text
> such as
> 
> 4.1.  General Requirements
> 
>    The IPv6 CE router is responsible for implementing IPv6 routing; that
>    is, the IPv6 CE router must look up the IPv6 destination address in
>    its routing table to decide to which interface it should send the
>    packet.
> 
> which i thought was forwarding, not routing.

It's static routing.  And if there is down stream PD there will be
next hop routers as well as interfaces in the table.

> RA/RD doeth not a router make.
> 
> randy
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org