Re: [sidr] WGLC for draft-ietf-sidr-bgpsec-protocol-05

"George, Wes" <wesley.george@twcable.com> Wed, 19 September 2012 17:15 UTC

Return-Path: <wesley.george@twcable.com>
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 3C4E821F86E4 for <sidr@ietfa.amsl.com>; Wed, 19 Sep 2012 10:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.462
X-Spam-Level:
X-Spam-Status: No, score=-0.462 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6gZ20G4HKe7 for <sidr@ietfa.amsl.com>; Wed, 19 Sep 2012 10:15:58 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 683A621F8526 for <sidr@ietf.org>; Wed, 19 Sep 2012 10:15:58 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,450,1344225600"; d="scan'208";a="422834099"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 19 Sep 2012 13:15:16 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Wed, 19 Sep 2012 13:15:55 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "Murphy, Sandra" <Sandra.Murphy@sparta.com>, "sidr@ietf.org" <sidr@ietf.org>
Date: Wed, 19 Sep 2012 13:15:54 -0400
Thread-Topic: WGLC for draft-ietf-sidr-bgpsec-protocol-05
Thread-Index: Ac2TN5E+gtWY3jVQTo2aIJ20K9PIbgCmdL0wAAPG+j4AKlMiMA==
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59235EFAB75F@PRVPEXVS15.corp.twcable.com>
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F706AF@CMA-MB003.columbia.ads.sparta.com>, <2671C6CDFBB59E47B64C10B3E0BD59235EFAAF6F@PRVPEXVS15.corp.twcable.com> <24B20D14B2CD29478C8D5D6E9CBB29F625F78EE0@Hermes.columbia.ads.sparta.com>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F625F78EE0@Hermes.columbia.ads.sparta.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sidr] WGLC for draft-ietf-sidr-bgpsec-protocol-05
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 19 Sep 2012 17:15:59 -0000

> From: Murphy, Sandra [mailto:Sandra.Murphy@sparta.com]
> Sent: Tuesday, September 18, 2012 5:04 PM
> To: George, Wes; sidr@ietf.org
> Subject: RE: WGLC for draft-ietf-sidr-bgpsec-protocol-05
>
> The use of pcount=0 was hoped/expected to require NO changes in the
> update validation algorithm.  If you have discovered places where it
> would require changes, it will indeed be interesting to see and discuss.

[WEG] use of pcount=0 for AS migration may not require changes to the *algorithm* itself, as much as it will simply require discussion of the process for handling pcount=0 in the cases where it is used and the neighbor is not a transparent route-server, since currently that case is discussed specifically in the draft, and there is a specific recommendation that pcount=0 updates be dropped if they didn't come from a known route-server neighbor.

That said, I'm not convinced it completely solves the problem, as I (hopefully) articulated in my pending draft, and *that* may require algorithm changes.

Wes

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.