IETF Logo Mail Archive

Re: [sidr] WGLC for draft-ietf-sidr-origin-validation-signaling-04

"Roque Gagliano (rogaglia)" <rogaglia@cisco.com> Mon, 05 May 2014 16:10 UTC

Return-Path: <rogaglia@cisco.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB6091A016C for <sidr@ietfa.amsl.com>; Mon, 5 May 2014 09:10:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level:
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 gcxNZSGiWi5H for <sidr@ietfa.amsl.com>; Mon, 5 May 2014 09:10:07 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4891A037A for <sidr@ietf.org>; Mon, 5 May 2014 09:10:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3981; q=dns/txt; s=iport; t=1399306204; x=1400515804; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=oVfEbf0HJU8B6okTREXd3uQG71DZmVomlntVwXGKukU=; b=QKnHmJ/qXx6XosA3GvnJFu/po2Wp01byFZJ4aqjInFrhuX8w9SN1nXEp AZfsAi4OrfLic+XO96xkpJFSMFKIKqhBi1naa8HR4Qv3Ib/wK8UPLyenh DF++nwNFDB5ngGN3bETsSfwmVepMyKby2+a7mgW5kIMcgXll7kk8N+JvD M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlIHAGm3Z1OtJA2E/2dsb2JhbABZgwZPWKowAQIFAZEPgUIBhzqBGBZ0giYBAQQBAQFrCxACAQgECjEHJwsUEQIEDgUUiC0Ny1oXhVaIfAeDKoEVBJk0gTyROIM0gW8kHA
X-IronPort-AV: E=Sophos; i="4.97,989,1389744000"; d="scan'208,217"; a="41135416"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-1.cisco.com with ESMTP; 05 May 2014 16:10:03 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s45GA3P1013251 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 May 2014 16:10:04 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.118]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Mon, 5 May 2014 11:10:03 -0500
From: "Roque Gagliano (rogaglia)" <rogaglia@cisco.com>
To: Sandra Murphy <sandy@tislabs.com>
Thread-Topic: [sidr] WGLC for draft-ietf-sidr-origin-validation-signaling-04
Thread-Index: AQHPaHx4vZsbW7hhNkeRxV8NMyn81w==
Date: Mon, 05 May 2014 16:10:03 +0000
Message-ID: <9487C4DF-EEAF-40FE-A9CE-768D38C91DA7@cisco.com>
References: <CB23313F-4612-4B4C-B29C-A446ED5B4356@tislabs.com>
In-Reply-To: <CB23313F-4612-4B4C-B29C-A446ED5B4356@tislabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.155.144.166]
Content-Type: multipart/alternative; boundary="_000_9487C4DFEEAF40FEA9CE768D38C91DA7ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sidr/9-sn31wfDbxACkpX0B9R6FQfD3Q
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] WGLC for draft-ietf-sidr-origin-validation-signaling-04
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Mon, 05 May 2014 16:10:10 -0000

Sandra,

I support this document moving forward to the IESG.

I read the document as part of the WGLC process and I believe the text is ready for publication.

My only question is a formality from Section 3 that says:

" If a BGP router supports prefix origin validation and is configure for the extensions defined in this document, the validation step SHOULD be performed prior to any of the steps defined in the decision process of [RFC4271<http://tools.ietf.org/html/rfc4271>]."

(Roque) Should this document specifically be labeled as an update to RFC4271?

Regards,
Roque

On Apr 26, 2014, at 1:53 AM, Sandra Murphy <sandy@tislabs.com<mailto:sandy@tislabs.com>> wrote:

The authors of BGP Prefix Origin Validation State Extended Community, draft-ietf-sidr-origin-validation-signaling-04 have requested a WGLC.

This message begins a two week WGLC, to end on 9 May 2014.

The draft is available at http://tools.ietf.org/html/draft-ietf-sidr-origin-validation-signaling.

Please do send comments to the list, indicating whether you do or do not believe that the draft is ready for publication.

--Sandy, speaking as wg co-chair
_______________________________________________
sidr mailing list
sidr@ietf.org<mailto:sidr@ietf.org>
https://www.ietf.org/mailman/listinfo/sidr

v2.23.0 | Report a Bug | By Email