Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt
"Jakob Heitz (jheitz)" <jheitz@cisco.com> Fri, 06 October 2017 23:35 UTC
Return-Path: <jheitz@cisco.com>
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 47A1B1321A7 for <sidrops@ietfa.amsl.com>; Fri, 6 Oct 2017 16:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 xRSA5DDVTsoc for <sidrops@ietfa.amsl.com>; Fri, 6 Oct 2017 16:35:50 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94177133065 for <sidrops@ietf.org>; Fri, 6 Oct 2017 16:35:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=592; q=dns/txt; s=iport; t=1507332950; x=1508542550; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=xA4h6YvejeoZGlT41StqOiJDirMMvMyR3VzWfPR9rmE=; b=KhdCEiaw5VoNNa/Rf1PbhinfhEFAixpNY3xTgBSdkjB4cBPEA9IG9CrF 7mjfgck0Am6HQfVI4GXLGS/WCa75hviijfqLmzw6+9dIrTzOfLofIp0z8 DIvp6z2n+5Olor+YEcp4HnECiFN3iKIBAexfHo1XEfGxLD/EEr7qXWZz+ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CfAAAJE9hZ/5NdJa1cGQEBAQEBAQEBAQEBBwEBAQEBg12BUi6OEo9qmCWCEgqFOwKEID8YAQIBAQEBAQEBayiFGQY6TwIBCDYQMiUCBAEaiiinU4s2AQEBAQEBAQMBAQEBAQEBASCDLYICgVGBaoMpingFoTMClFqCBJEPlSwCERkBgTgBHziBDngVh2aHciyBBYEQAQEB
X-IronPort-AV: E=Sophos;i="5.42,486,1500940800"; d="scan'208";a="13173275"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Oct 2017 23:35:34 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v96NZYnm010221 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 6 Oct 2017 23:35:34 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 6 Oct 2017 18:35:33 -0500
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1320.000; Fri, 6 Oct 2017 18:35:33 -0500
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: Randy Bush <randy@psg.com>, "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt
Thread-Index: AQHTCM8o/uckWQovpkasQZS9cIJoI6LX4zDQ
Date: Fri, 06 Oct 2017 23:35:33 +0000
Message-ID: <50b3ef1b548d4726a5628d5edf53cf2d@XCH-ALN-014.cisco.com>
References: <m2k22qzqm7.wl-randy@psg.com>
In-Reply-To: <m2k22qzqm7.wl-randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.131.69]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/Zlc3WB1M24-AlQZA84e7W3YZHsI>
Subject: Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.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: Fri, 06 Oct 2017 23:35:52 -0000
I'd like to add a section: ROAs and BGP announcements Every IP prefix that is matched by a ROA SHOULD be announced to BGP by the AS stated in the ROA unless that AS is AS 0. If the owner AS does not announce the prefix, then another AS can announce the prefix and simply prepend the owner ASN. Such a false announcement will pass RPKI validation. Also, there will be no legitimate announcement to compete with it. If an AS wishes to protect an IP address prefix without announcing it, then it SHOULD issue a ROA that associates the prefix with AS 0. Thanks, Jakob
- [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Randy Bush
- Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Jakob Heitz (jheitz)
- Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Randy Bush
- Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Jakob Heitz (jheitz)
- Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Randy Bush