Re: [Idr] I-D Action: draft-ietf-idr-error-handling-13.txt

Jeffrey Haas <jhaas@pfrc.org> Mon, 16 June 2014 18:47 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF7AC1A014C for <idr@ietfa.amsl.com>; Mon, 16 Jun 2014 11:47:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level:
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 X4MPYXDfM3jJ for <idr@ietfa.amsl.com>; Mon, 16 Jun 2014 11:47:26 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id F3A311A013B for <idr@ietf.org>; Mon, 16 Jun 2014 11:47:25 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 9D4BDC406; Mon, 16 Jun 2014 14:47:25 -0400 (EDT)
Date: Mon, 16 Jun 2014 14:47:25 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Chris Hall <chris.hall@highwayman.com>
Message-ID: <20140616184725.GB31387@pfrc>
References: <20140613183222.27662.91400.idtracker@ietfa.amsl.com> <48D0139F-CD0E-474C-A557-E18E6100157A@juniper.net> <CA+b+ERny4PxsQxhvwE6XOtuStzbD9WmwO9TpUdmKFJ0bHhGVjw@mail.gmail.com> <009f01cf87df$48630760$d9291620$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <009f01cf87df$48630760$d9291620$@highwayman.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/t2zgRsd9-4P3TI8CO3MfLW2rqp8
Cc: "'idr@ietf. org'" <idr@ietf.org>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-error-handling-13.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 18:47:26 -0000

On Sat, Jun 14, 2014 at 03:45:22PM +0100, Chris Hall wrote:
> I have a feeling that defining "valid host address" is more trouble
> than it is worth.

I'm also a bit concerned here.

RFC 4271 and earlier went through a lot of wrangling to end up with the idea
syntactically correct vs. semantically correct.

If it's syntactically incorrect, treat as withdraw is quite reasonable.

Semantically incorrect gets heavily tied up into how we're breaking original
rules today in a given spec.  E.g. RFC 5575 zero length.  What happens when
we decide to get clever and end up using a class D/E address in IPv4?  Etc.

For any future Clever Feature, deployment of it will need to be pervasive
enough for the networks using it to make use of it.  This means an island of
semantic correctness for something that didn't used to be that way.

If you're outside of the island, it's semantically incorrect, treat as
withdraw.

It may thus be worthwhile simplifying the section:
"If the next hop field contains a semantically incorrect address within the
context of deployed features and address family, treat as withdraw behavior
should be used."

I'd keep the section on martians.

-- Jeff