Re: [sidr] Request for WG Last Call fordraft-ietf-sidr-bogons-02.txt anddraft-ietf-sidr-roa-validation-01.txt

"Pradosh Mohapatra (pmohapat)" <pmohapat@cisco.com> Tue, 02 December 2008 06:52 UTC

Return-Path: <sidr-bounces@ietf.org>
X-Original-To: sidr-archive@megatron.ietf.org
Delivered-To: ietfarch-sidr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B968A3A6ABC; Mon, 1 Dec 2008 22:52:57 -0800 (PST)
X-Original-To: sidr@core3.amsl.com
Delivered-To: sidr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE8AC3A6A85 for <sidr@core3.amsl.com>; Mon, 1 Dec 2008 22:52:55 -0800 (PST)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6qXROBI9C1w for <sidr@core3.amsl.com>; Mon, 1 Dec 2008 22:52:55 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 2CD2F3A6ABC for <sidr@ietf.org>; Mon, 1 Dec 2008 22:52:55 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,701,1220227200"; d="scan'208";a="119987214"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 02 Dec 2008 06:52:51 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id mB26qpcQ019542; Mon, 1 Dec 2008 22:52:51 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mB26qpjZ007378; Tue, 2 Dec 2008 06:52:51 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 1 Dec 2008 22:52:51 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 01 Dec 2008 22:52:46 -0800
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D5408358AA0@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <FFDEAEB4-9A07-4F69-B632-2263A548DECF@apnic.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sidr] Request for WG Last Call fordraft-ietf-sidr-bogons-02.txt anddraft-ietf-sidr-roa-validation-01.txt
Thread-Index: AclUOc2vUYUdPRgfSwWmafXEAgCV5QAD6ykg
References: <C542C40B.5166%andy@arin.net><A3751517-D15C-45DD-B530-027758F36B04@apnic.net><FC10BBCC-6144-4420-ACFC-9454F26444BE@tcb.net><6F70023C-57B1-4C8D-8DDF-B9D7D8F139F9@apnic.net><56AFA6B5-BCFB-4CDC-B921-3590F71CCBA0@tcb.net><0072BC84-507D-497C-B8B6-0F26DE804316@apnic.net><19318B76-0E1E-4DC5-8017-D2350352169C@tcb.net><16C1A7B4-C46F-4354-B1F8-4AF8EB5249B9@apnic.net><C4A37FE7-88F1-4DEC-AB81-CC2EC6A96C79@tcb.net><D1AE3911-CBB9-451A-AE47-CB254E403DED@apnic.net><EC1B7F06-4137-4F97-8EE5-7676DB0E7155@tcb.net><BD48FF05-04D0-4B71-AF1B-F074E0199202@apnic.net><A09B46E4-02B0-4825-888C-CA24CD68EF50@tcb.net><CB9CD7AF-8CD3-4636-8D64-E876B9216B47@apnic.net><264FCEF8-3DD1-49AB-B41F-56FD0A1B2870@tcb.net> <76720B94-5516-48BB-9D83-F3182969A6DE@apnic.net> <04CAD96D4C5A3D48B1919248A8FE0D540835895A@xmb-sjc-215.amer.cisco.com> <3C4C05F3-8554-4F68-9508-F6B1E3E20660@apnic.net> <04CAD96D4C5A3D48B1919248A8FE0D5408358A48@xmb-sjc-215.amer.cisco.com> <FFDEAEB4-9A07-4F69-B632-2263A548DECF@apnic.net>
From: "Pradosh Mohapatra (pmohapat)" <pmohapat@cisco.com>
To: Geoff Huston <gih@apnic.net>
X-OriginalArrivalTime: 02 Dec 2008 06:52:51.0434 (UTC) FILETIME=[982F9CA0:01C9544A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1390; t=1228200771; x=1229064771; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pmohapat@cisco.com; z=From:=20=22Pradosh=20Mohapatra=20(pmohapat)=22=20<pmohapat @cisco.com> |Subject:=20RE=3A=20[sidr]=20Request=20for=20WG=20Last=20Ca ll=20fordraft-ietf-sidr-bogons-02.txt=20anddraft-ietf-sidr-r oa-validation-01.txt |Sender:=20; bh=luk4HQ1ETpPElr7FRBBPPTygOOXtDmeSWa7m/hNOpFs=; b=XenWmM+w4y6kGDADfhGbITQYUggwlI6JB6r4Jko6pDE1izXVgTv/EOKBIm MetDhFjKb95+mwyXF5LSNAs98Jk95WaG42JFuZ0HTQauJXwlWTK4txpZ+jEs FSDhT3LPho;
Authentication-Results: sj-dkim-3; header.From=pmohapat@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Cc: sidr@ietf.org
Subject: Re: [sidr] Request for WG Last Call fordraft-ietf-sidr-bogons-02.txt anddraft-ietf-sidr-roa-validation-01.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sidr-bounces@ietf.org
Errors-To: sidr-bounces@ietf.org

| > | > As others have suggested, when "I have been allocated
| > | 203.10.60.0/22",
| > | > I issue an ROA for 203.10.60.0/22-22. That automatically means
| > that
| > | > there can't be any other advertisements for this prefix or its
| > more
| > | > specifics (unless I suballocate a more specific block and a new
| > ROA
| > | > gets added to the repository for that]. Is there any case
| > | that's not
| > | > handled by doing this?
| > | >
| > |
| > | That's your _assumption_ of the sematics of a ROA. What reference 
| > | material or working group draft can you cite for semantic 
| > | interpretation of a ROA?
| > | draft-ieft-sidr-roa-validation? I don't think so. The 
| point of hte 
| > | BOA draft it that it challenges this assumption by taking the 
| > | position that such route aorigination authorities are explicitly 
| > | scoped to the authority described in the object, without the 
| > | implicit inclusion of any other authority or denial.
| >
| > So are you saying that an entity who is not owner of prefix 
| 10/8 can 
| > issue an ROA for it and it would be present in/added to the RPKI 
| > repository?
| >
| 
| The best answer I can give here is please read the sidr 
| drafts. Your question really makes me suspect that you have 
| not done so.

I have. Your response above prompted the question.
_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr