Re: [sidr] draft-ietf-sidr-origin-validation-signaling - new version submitted recently... WGLC?

Jay Borkenhagen <jayb@braeburn.org> Thu, 24 October 2013 17:54 UTC

Return-Path: <jayb@braeburn.org>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2261411E837C for <sidr@ietfa.amsl.com>; Thu, 24 Oct 2013 10:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8vEea7YnNiez for <sidr@ietfa.amsl.com>; Thu, 24 Oct 2013 10:54:21 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 039E711E81E0 for <sidr@ietf.org>; Thu, 24 Oct 2013 10:53:31 -0700 (PDT)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 79e59625.0.4913583.00-433.13789911.nbfkord-smmo06.seg.att.com (envelope-from <jayb@braeburn.org>); Thu, 24 Oct 2013 17:53:34 +0000 (UTC)
X-MXL-Hash: 52695e9e6f949545-7e57e9e37cb9723fafa5157157e2f601d4962784
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id r9OHrRAl019096; Thu, 24 Oct 2013 13:53:27 -0400
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id r9OHrGC4018987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Oct 2013 13:53:17 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi132.aldc.att.com (RSA Interceptor); Thu, 24 Oct 2013 17:53:00 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r9OHr08C013618; Thu, 24 Oct 2013 13:53:00 -0400
Received: from oz.mt.att.com (oz.mt.att.com [135.16.165.23]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r9OHqqUo013436; Thu, 24 Oct 2013 13:52:52 -0400
Received: by oz.mt.att.com (Postfix, from userid 1000) id 71FD568203C; Thu, 24 Oct 2013 13:52:51 -0400 (EDT)
X-Mailer: emacs 23.3.1 (via feedmail 8 I); VM 8.2.0b under 23.3.1 (i686-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <21097.24175.772599.34788@oz.mt.att.com>
Date: Thu, 24 Oct 2013 13:52:47 -0400
From: Jay Borkenhagen <jayb@braeburn.org>
To: Chris Morrow <morrowc@ops-netman.net>
In-Reply-To: <5267E19C.7000208@ops-netman.net>
References: <5267E19C.7000208@ops-netman.net>
X-GPG-Fingerprint: DDDB 542E D988 94D0 82D3 D198 7DED 6648 2308 D3C0
X-RSA-Inspected: yes
X-RSA-Classifications: public
Cc: "sidr-chairs@tools.ietf.org" <sidr-chairs@tools.ietf.org>, "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] draft-ietf-sidr-origin-validation-signaling - new version submitted recently... WGLC?
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Jay Borkenhagen <jayb@braeburn.org>
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Oct 2013 17:54:27 -0000

Chris Morrow writes:
 > I believe the authors wanted this to progress, I believe there was
 > recently (8/29/2013) an updated version submitted, does it deal with the
 > outstanding comments? (the diff doesn't show much more than
 > boilerplate-like changes)
 > 
 > Should this be WGLC'd at this point?
 > 

Hi,

A couple comments.


http://tools.ietf.org/html/draft-ietf-sidr-origin-validation-signaling-03
refers to "[I-D.ietf-sidr-pfx-validate]", but that has been published
as rfc6811.

The paragraph in Section 2 where that reference occurs says:

===============

   Note that routers do not perform prefix origin validation (compute
   the validation state as defined in [I-D.ietf-sidr-pfx-validate])
   for IBGP learnt routes.

===============

... but rfc6811 does not prohibit performing prefix origin validation
for IBGP learnt routes.  In a network where all edge routers are
capable and configured to perform prefix origin validation on EBGP
learnt routes it should not be necessary to perform that function also
on IBGP learnt routes, but in general doing so should not be
prohibited.  The current statement in
draft-ietf-sidr-origin-validation-signaling-03 is too strongly
worded. 

Thanks.

						Jay B.