Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt

Job Snijders <job@ntt.net> Wed, 14 March 2018 00:20 UTC

Return-Path: <job@instituut.net>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0031126DFB for <sidrops@ietfa.amsl.com>; Tue, 13 Mar 2018 17:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
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 20nZ7S-_8PhN for <sidrops@ietfa.amsl.com>; Tue, 13 Mar 2018 17:20:57 -0700 (PDT)
Received: from mail-wr0-f177.google.com (mail-wr0-f177.google.com [209.85.128.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0286D124BFA for <sidrops@ietf.org>; Tue, 13 Mar 2018 17:20:56 -0700 (PDT)
Received: by mail-wr0-f177.google.com with SMTP id z12so2915256wrg.4 for <sidrops@ietf.org>; Tue, 13 Mar 2018 17:20:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=UdY9HWapLQJDqbMWWbY4GrVO8VIRSJ1NBlE0rXOEUEM=; b=PG+T7P9sysrPA0etszNnnqY81VWiL/uQZBLkhOGxwRG6hvY5iCk0WIFwMdvmu5Lk7h rJwCUwvvf/LRQ1ncN6PuvgU9KyxbgDEIo6ByXL5vCV/I+kA972cWEK7VIpcHD1mSpTHG 4+/+RDDhZZXJ1UiqWFve0P+FxWrTT8IoulLwPq7+M+UkEdzfFUIZzoDIuw/i1Mt6E8es Yd3owmp988a1WCnw/qKO6an7/ylQQyXcKohesXXZEVKIWE73XqKu3dAfy/ioF2qzSelQ DPni3l3/RfWYP3ZzP8LxWNNYBA+T7ZyJn9hhlhnretFXuWKIPUDfbvD8sb2OAxXnqD2Y ipaA==
X-Gm-Message-State: AElRT7FdnXzo6AXKiZd44CIpMzaTJ55wMANyrpfFtW++ZO7s5Ii/8S94 /cuuF678ttgKt1Pimf2rty715A==
X-Google-Smtp-Source: AG47ELuWH0vwuGcXEgv32Ersw62pbZCz1GYMUFPmEnAEeA2p+Hk2WlqmiaakS0JR0yEqSagoe54pIA==
X-Received: by 10.80.149.155 with SMTP id w27mr661420eda.33.1520986855315; Tue, 13 Mar 2018 17:20:55 -0700 (PDT)
Received: from vurt.meerval.net (vurt.meerval.net. [192.147.168.22]) by smtp.gmail.com with ESMTPSA id v15sm1001220ede.90.2018.03.13.17.20.53 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 13 Mar 2018 17:20:54 -0700 (PDT)
Received: from localhost (vurt.meerval.net [local]) by vurt.meerval.net (OpenSMTPD) with ESMTPA id 2bab5e2b; Wed, 14 Mar 2018 00:20:53 +0000 (UTC)
Date: Wed, 14 Mar 2018 00:20:53 +0000
From: Job Snijders <job@ntt.net>
To: Stephen Kent <stkent@verizon.net>
Cc: "Montgomery, Douglas (Fed)" <dougm@nist.gov>, "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, Tim Bruijnzeels <tim@ripe.net>, "sidrops-chairs@ietf.org" <sidrops-chairs@ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>
Message-ID: <20180314002053.GE85809@vurt.meerval.net>
References: <152029076512.12908.14537578849320525718.idtracker@ietfa.amsl.com> <BYAPR09MB2773819AB3961189CDA9B4D784D90@BYAPR09MB2773.namprd09.prod.outlook.com> <074D75CB-7D34-4838-BEAA-88AE5E044F6C@ripe.net> <BYAPR09MB27738385E28497E1EC5B32AD84DE0@BYAPR09MB2773.namprd09.prod.outlook.com> <70613650-C8D6-43D9-8643-5694B77BADA9@nist.gov> <5d2afc8e-7f9a-e2bc-fa84-88b943639bd6@verizon.net> <C92B14E7-6F48-4627-8887-776C1321E603@nist.gov> <eb8ed78d-e42f-1ed1-e94f-6821929df9c6@verizon.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <eb8ed78d-e42f-1ed1-e94f-6821929df9c6@verizon.net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/oOrB6QqfF2XMJzcyB2_uX8-6t_E>
Subject: Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2018 00:20:58 -0000

On Tue, Mar 13, 2018 at 08:13:28PM -0400, Stephen Kent wrote:
> I'm puzzled by your interpretation of RFC 7607. Specifically, Section
> 2 of 7607 says:
> 
> [...] 
> 
> This seems pretty definitive, and normative, not just a "usage
> convention" for AS 0, as you suggest.

The use of AS 0 in ROAs is not the same as the use of AS 0 in BGP UPDATE
messages. The former is allowed, the latter is not.

Kind regards,

Job